I just signed up to Chase Bank and realised that it’s not possible to connect yet due to not having a API. Therefore, it would be great to be able to import my Chase spends into the app.
To make this easy might require the ability to export all the fields currently used in Emma as a blank template before import.
Hopefully this is a straight forward request others would find value you in.
There was discussion about this a few years ago…
I did search last year’s conversations and found nothing. Clearly should have gone further back.
Also I spoke to Chase Bank and there is no plan to create an open API.
This may now be the missing feature which forces me to stop being an Emma pro member.
Would be interested to know if the thoughts around implementing this had changed.
The way to fix the matching issue is the same implemented by almost all companies: allow a template of all imported fields. This allows data to be codified in a way as regular transitions, which should allow enrichment to still be possible.
The support team mentioned that Truth Layer was no longer used for enrichment. Therefore, if no API component is in use for data enhancement, a CSV (if properly organised) should work as well as a bank connection.
Still would be interested to hear Emma staff on this issue. Given then Chase is currently offering the best rates in the industry and will not be useable in the app for the foreseeable future.
Re-picking this one up as the question returns every now and then. I understand the lack of priority in offering a public API, but how about offering the ability to import a CSV into an existing account? (Could be paywalled to drive more interest to the paid plans)
I think this is something we are going to implement in the app; I don’t know where but it’s in our internal backlog and I think we should totally do it.
Best place would be the account dropdown menu (where you have the rename, change account type etc.). Have a simple CSV template that can be downloaded from a help center page.
Ideally you’d also support OB accounts to allow users to load historical transactions, but if not possible due to design then manual accounts would suffice.
Shouldn’t be too difficult to implement, you already have all the logic to apply to transactions as they come from various integrations feeds, you just need a CSV importer as another data source no?
Hey guys,
we have started designing this - I think we can release it in September or sooner; it’ll be part of offline accounts.
This will come out next week. 
This is fully live now! 
How is this done? And what’s the template for the CSV upload?
Hey @eloymora,
if you create a new offline account, it’ll ask if you want to upload transactions via CSV; you can also find this option in the settings of an offline account!
There is no template - you can just take your bank csv and upload it; we use AI to figure out what to take out from the file.
You absolutely rock
It’s working great! Would it be possible to add the category manually in the CSV and take it from this column during the CSV import process?
To be honest, we have decided to use Emma’s categorisation system, so the transactions should be categorised like the rest of the app!
Ok! So it should be learning as I recategorise from “General” to “Category X” and then categorise new uploads correctly, right?
I can check this with the team, I don’t think they have added the learning. It’s a bit complicated.
So then the majority of transactions will be categorised under General or Income? This is what happened with the uploads I did yesterday.
if that’s the case, then you need to spend time recategorising all transactions manually, which takes time.
We’ll apply our internal logic for categorisation and then if we don’t find the category, it’ll sit in general.
We are going to bring the learning as well - but have not prioritised it yet!
Thank you very much! A great job Emma team, this has been so helpful.