Great to hear CSV exports could be getting a little bit of love.
I’d echo a lot of what @BritishLibrary has already said.
The main thing I feel is missing is unique identifiers for each pot that are not dependant on the pot name. I suspect this data lives in the backend somewhere, so a new column that exposes some of that kind of stuff would be great.
I haven’t used virtual cards yet because I’ve heard they can’t be tracked properly in the CSV, so this would be my next priority.
I know others have talked about wanting separate CSV exports for pots etc, but I think I’d personally like to see all of my monzo data in a single CSV with a column to indicate the origin of each transaction and a column to indicate the destination (with those unique IDs I mentioned). This would open the door to including transactions from pots, virtual cards, flex accounts, joint and personal accounts, even connected accounts(?), all in one ledger. The downside is that this approach would make the data less accessible as it would require a bit more work to achieve the kind of dashboards we’re currently creating:
Its too early on a monday for my brain to think it through properly, but there are probably good reasons not to follow this ‘all in one’ CSV approach. Like if I get a refund, the origin of the transaction would be the merchant and the destination would be my personal account. So to keep track of my personal account balance, I would need to be looking for all transactions where either the origin or destination columns include my personal account. Which, while probably achievable, sounds like a headache.
If you did go down this route, I’d suggest offering it as a ‘beta CVS export’ as an additional drop down option in the short term.