Matching imported transactions
Hi,
I developed my own interface for creating new transactions right after I pay by my credit card, and I'm using YNAB API. I'm keeping those transactions uncleared.
But when transactions are imported from the bank account official way, it is not possible to match them together. Is there any way how to mark transactions over API that is "manually inserted" and that I can match transactions later?
Thanks!
-
Why isn't it possible to match them? It shouldn't matter how the transactions got there, manual or programmatically, but they should be able to match if the payees and amounts are similar and they're within 10 days of each other, I believe.
-
Superbone After I tested that is not possible to match those transactions, I found this:
Two imported transactions can’t be matched. After all, your bank is probably pretty sure these are different transactions. And, just like different amounts, issues with balances and reconciliation can crop up if you call these two transactions one. For similar reasons, two user-entered transactions can’t be matched either.
https://www.youneedabudget.com/matchmaker-matchmaker-make-me-a-match/
-
Pevnomad Gotcha. Makes sense. Is there a way to make your programmatic transactions act like a manual entry?
-
Superbone Great question! And I'm waiting for an answer from someone, that was the reason why I created this topic 😉
-
Pevnomad Heh. Now I get it. Hopefully our discussion will help illuminate to the powers that be what your issue is and how to fix.
-
-
Hi Pevnomad
That's a great question! In YNAB, it's not possible to match two transactions that have both been imported--whether that's through the API, File Based Import, or Direct import, so your research is definitely correct.
Edit: I originally gave you some mis-information about transactions. Here's the correct information:
If import_id is omitted or specified as null, the transaction will be treated as a “user-entered” transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
Here's where that's from: https://api.youneedabudget.com/v1#/Transactions/updateTransactions
(If you toggle from example to model). So, if you go ahead and use a null "import_id" you could match that transaction.
However, I think the best course of action here is for me to pass on a request to our API Developers to take a look at allowing some change to the matching logic of two imported transactions from different sources, or to treat API transactions differently than imported transactions from other sources.
Let me know if that makes sense or if I can answer some additional questions.
-
Chrissy Thank you very much! I changed my script, created transactions without import_id, and then waited few days for bank api import, and IT WORKED!
Thanks again :)
-
Hi,
I am trying to solve similar thing - 2 import match. I have imported my bank data throught API (ynab bank connect not work with europe banks) and then I imported apple invoice transaction (similar date, same amount) with null import_id. But still no luck to get them matched.
Is there a way for it? Idea is quite simple - many payments from cards missing information for proper categorizing. So if there is source of these data I can put there duplicate payment with proper memo/payee data throught API and then just match them.
-
