# CSV Exports **URL:** \ **Category:** Monzo Chat\ **Created:** [16 January 2020 11:25 UTC](https://community.monzo.com/t/csv-exports/89487 "2020-01-16T11:25:26Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![bruno](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/bruno/32/27588_2.png) [@bruno](https://community.monzo.com/u/bruno)\ **Post date:** [16 January 2020 11:25 UTC](https://community.monzo.com/t/csv-exports/89487/1 "2020-01-16T11:25:26Z")
The data structure of our existing CSV export is a bit out of date. **If you could change anything in the data structure, what would you do?** ---
**Author:** ![Revels](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/revels/32/120556_2.png) [@Revels](https://community.monzo.com/u/Revels)\ **Post date:** [16 January 2020 12:00 UTC](https://community.monzo.com/t/csv-exports/89487/2 "2020-01-16T12:00:43Z")
Date & time in separate columns would be a good start. I realise it’s easy enough to extrapolate it yourself, but it’s easier if it’s done for you. ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [16 January 2020 13:02 UTC](https://community.monzo.com/t/csv-exports/89487/3 "2020-01-16T13:02:22Z")
> [@CSV Output field formatting](https://community.monzo.com/t/csv-output-field-formatting/63057): > > Can we get a better date format than the current one used in the CSV export. Excel doesn’t really know what 2019-02-07T09:33:50Z is, and I’m not even sure why there is a T and Z in there. Can we get it to be just 2019-02-07 09:33:50 (or some other agreed format that is recognised by other apps?) I think options built around where the output will be used is the best route forward? CSV for Excel CSV for [finance app A] But the date/time piece is probably key. So, is this part of a ‘What’s Next’ piece of work? #soon ---
**Author:** ![anon95680666](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@anon95680666](https://community.monzo.com/u/anon95680666)\ **Post date:** [16 January 2020 13:12 UTC](https://community.monzo.com/t/csv-exports/89487/4 "2020-01-16T13:12:59Z")
use of colours to differentiate categories ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [16 January 2020 13:25 UTC](https://community.monzo.com/t/csv-exports/89487/5 "2020-01-16T13:25:48Z")
But what happens when (if?!) we get custom categories? Hmmm set them to match the colour in the app I guess? ---
**Author:** ![Rjevski](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/rjevski/32/45968_2.png) [@Rjevski](https://community.monzo.com/u/Rjevski)\ **Post date:** [16 January 2020 16:50 UTC](https://community.monzo.com/t/csv-exports/89487/6 "2020-01-16T16:50:19Z")
I don’t think you can do that in a CSV. ---
**Author:** ![anon95680666](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@anon95680666](https://community.monzo.com/u/anon95680666)\ **Post date:** [16 January 2020 16:54 UTC](https://community.monzo.com/t/csv-exports/89487/7 "2020-01-16T16:54:25Z")
🤷‍♂️😀 ---
**Author:** ![RogerB](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/rogerb/32/24254_2.png) [@RogerB](https://community.monzo.com/u/RogerB)\ **Post date:** [16 January 2020 16:58 UTC](https://community.monzo.com/t/csv-exports/89487/8 "2020-01-16T16:58:11Z")
> [@gmclean](#): > > T09:33:50Z I would suggest - **T** ime is 09:33:50 **Z** ulu - a term for UCT as used in Military and Aviation settings. R- ---
**Author:** ![Lewis\_P](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/lewis_p/32/73433_2.png) [@Lewis\_P](https://community.monzo.com/u/Lewis_P)\ **Post date:** [16 January 2020 18:05 UTC](https://community.monzo.com/t/csv-exports/89487/9 "2020-01-16T18:05:19Z")
Personally I found the ‘description’ column problematic. It’s tricky to extract a list of retailers from this column since its used for other info such as whether its a pot transfer. I found a workaround that involved showing only the items that included a bunch of spaces, since the retailer information is typically formatted with large spaces between the name, region and nation. Perhaps a column could be added that provides the type of transaction; Pot Transfer, Faster Payment, P2P payment, Direct Debit, Card Check, card payment, cash withdrawal. So that this is kept separate from the retailer, payer and recipient information. I also agree that the time date format for the “created” column is not very user friendly when brought into google sheets or excel. ---
**Author:** ![Nsteer](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/nsteer/32/25875_2.png) [@Nsteer](https://community.monzo.com/u/Nsteer)\ **Post date:** [16 January 2020 18:26 UTC](https://community.monzo.com/t/csv-exports/89487/10 "2020-01-16T18:26:44Z")
> [@RogerB](#): > > I would suggest - **T** ime is 09:33:50 **Z** ulu This is correct, it’s an ISO (International Organization for Standardization) date/time format, it’s the standard we use at work too. > **[ISO 8601](https://en.m.wikipedia.org/wiki/ISO_8601)** > > 2023-11-30T13:37:27+00:00 UTC+00:00 \[refresh\] > ISO 8601 is an international standard covering the worldwide exchange and communication of date and time-related data. It is maintained by the International Organization for Standardization (ISO) and was first published in 1988, with updates in 1991, 2000, 2004, and 2019, and an amendment in 2022. The standard provides a well-defined, unambiguous method of representing calendar dates and times in worldwide communications, especially to avoid misinter... ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [16 January 2020 20:57 UTC](https://community.monzo.com/t/csv-exports/89487/11 "2020-01-16T20:57:40Z")
I know WHAT it is but no idea why it’s in a CSV export from a consumer app. User friendly date preferred even if it doesn’t conform to an ISO standard ---
**Author:** ![Js38wju3jda](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/js38wju3jda/32/41768_2.png) [@Js38wju3jda](https://community.monzo.com/u/Js38wju3jda)\ **Post date:** [16 January 2020 23:15 UTC](https://community.monzo.com/t/csv-exports/89487/12 "2020-01-16T23:15:15Z")
Please please keep ISO 8601. I have transactions in multiple time zones. If the data is split it makes my life harder. - MCC codes - TX type (Contactless, Apple Pay, Mag Stripe, Chip) Lloyds does this one well. - CVM method ---
**Author:** ![RogerB](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/rogerb/32/24254_2.png) [@RogerB](https://community.monzo.com/u/RogerB)\ **Post date:** [17 January 2020 07:34 UTC](https://community.monzo.com/t/csv-exports/89487/13 "2020-01-17T07:34:31Z")
My apologies - I misunderstood. R- ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [17 January 2020 08:10 UTC](https://community.monzo.com/t/csv-exports/89487/14 "2020-01-17T08:10:54Z")
No worries! ---
**Author:** ![swok1080](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/swok1080/32/24954_2.png) [@swok1080](https://community.monzo.com/u/swok1080)\ **Post date:** [17 January 2020 09:15 UTC](https://community.monzo.com/t/csv-exports/89487/15 "2020-01-17T09:15:14Z")
> [@gmclean](#): > > User friendly date preferred > [@Js38wju3jda](#): > > I have transactions in multiple time zones. This is the point of using iso8601 formatting; it avoids any ambiguity. I’d prefer it to stay as it is but having an extra “Readable” version probably wouldn’t hurt. > [@gmclean](#): > > I think options built around where the output will be used is the best route forward? > CSV for Excel > CSV for [finance app A] I get what you’re saying but I’d be really interested in how much of the user base actually bothers exporting transactions and (we’ll never get data on this) how many of these aren’t familiar enough with Excel to achieve what they want. ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [17 January 2020 09:17 UTC](https://community.monzo.com/t/csv-exports/89487/16 "2020-01-17T09:17:22Z")
No reason they can’t do both. For those of us who Excel now and then, a nicer format for that would help. For those who need the ISO style data, then retain that. I’m in the ‘give me it like a bank statement’ side of the argument, and they never ever come with timezone info in them (historically/legacy etc I know). But yeah, no reason they can’t do both/all/more. ---
**Author:** ![swok1080](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/swok1080/32/24954_2.png) [@swok1080](https://community.monzo.com/u/swok1080)\ **Post date:** [17 January 2020 09:20 UTC](https://community.monzo.com/t/csv-exports/89487/17 "2020-01-17T09:20:13Z")
The PDF export does have a more readable date if that works for you? ![Screenshot_20200117-091901](https://global.discourse-cdn.com/monzo/original/3X/b/b/bb9d6dad002a4c4e67668f9f33c79aed93010310.jpeg) ---
**Author:** ![gmclean](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/gmclean/32/47932_2.png) [@gmclean](https://community.monzo.com/u/gmclean)\ **Post date:** [17 January 2020 09:29 UTC](https://community.monzo.com/t/csv-exports/89487/18 "2020-01-17T09:29:07Z")
Ehhh thanks, I’m aware of the options, but I can’t (easily) import a PDF into Excel. Personally I want the lowest friction solution. Export to XLS, open in Excel and have the data ‘understood’ without having to do any formatting/transformations. Anyway, what other options do other people want? ---
**Author:** ![bruno](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/bruno/32/27588_2.png) [@bruno](https://community.monzo.com/u/bruno)\ **Post date:** [17 January 2020 10:43 UTC](https://community.monzo.com/t/csv-exports/89487/19 "2020-01-17T10:43:06Z")
> [@Js38wju3jda](#): > > I have transactions in multiple time zones. If the data is split it makes my life harder. I thought the date was always in UTC regardless of the local time at the merchant location? 🤔 > [@Js38wju3jda](#): > > - MCC codes This seems overkill? There’s so many MCC (Mastercard Merchant Codes - [list](https://www.mastercard.us/content/dam/mccom/en-us/documents/rules/quick-reference-booklet-merchant-edition.pdf)) that it makes them of little use to look at aggregate data, also lots of merchants have the wrong MCC. > [@Js38wju3jda](#): > > - TX type (Contactless, Apple Pay, Mag Stripe, Chip) Lloyds does this one well. > - CVM method What’s the use case for these two? > [@swok1080](#): > > I’d be really interested in how much of the user base actually bothers exporting transactions and (we’ll never get data on this) Very few customers do a manual export, more people use the IFTTT integration to auto-export (and that’s also low). ---
**Author:** ![Lewis\_P](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/lewis_p/32/73433_2.png) [@Lewis\_P](https://community.monzo.com/u/Lewis_P)\ **Post date:** [17 January 2020 10:52 UTC](https://community.monzo.com/t/csv-exports/89487/20 "2020-01-17T10:52:27Z")
> [@bruno](#): > > Very few customers do a manual export, more people use the IFTTT integration to auto-export (and that’s also low). Is there a reason why the IFTTT auto-export contains less information than the manual export? [Next page](https://community.monzo.com/t/csv-exports/89487.md?page=2)