Would be great if the transaction IDs were consistent on the exports. When I run two exports for overlapping date periods, the same transactions have different transaction IDs. This defeats the point of assigning them a unique code, and makes it impossible to use features like vlookup when you’re dashboarding or further analysing your spend, post-export.
Hi @esdellert,
thanks for sharing this!
Transactions change all the time, so this is insanely difficult; I’m going to pass it to the product team, but as I mentioned we are ware of it. 
Yes, if you’re attempting to perform anything significant with the data in a BI tool like Excel, this is a major hassle. honestly, if the export isn’t producing reliable transaction IDs, your only remedy right now is to construct your own “hash” of the transaction — like concatenate date, amount, merchant — essentially anything that’s unique enough to track it between exports. not complete, but at least vlookup and pivoting become functional. would love if emma really simply made the txn ID immutable, that’s a table-stakes feature for meaningful spend statistics.
There are a lot of issues here that are difficult to solve. This is mostly due to banks deleting transactions all the time and re-creating them, but also pending transactions change references all the time. 
This is also the main reason why pending transactions are not editable.