Matching API Transactions

What are the limitations on matching for API transactions?

Just had one imported, and i want to match it with a Scheduled transaction, but it will not let me.

22replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Good question - I'm just checking on this for you Scott Robertson !

    Reply Like
  • I just confirmed that API transactions are treated as manually entered transactions. You can only match a scheduled or manually entered transaction with one that was imported, which is why it's not an option to match those two transactions.

    It's definitely something that's on our radar to investigate!   

    Reply Like
    • Angela at YNAB Ah damn... i guess for most people that will be fine,  but it messes things up for me. Here is why:

      • I get realtime webhooks from my bank. As soon as they happen, i push them into YNAB
      • I then periodically run my importer, which i then sometime end up with duplicates

      Basically now, i cannot merge them duplicates as they are both API transactions :( 

      Reply Like 1
    • Scott Robertson Hmmm ... yes, that doesn't work well for the way you have things set up. I'm wondering about (and I'm hesitant to even ask in case it's a dumb question - so apologies in advance) the reasoning behind pulling in transactions by both methods? Is it possible one method will miss transactions? 

      This is something they're still discussing internally, so we may be able to find a solution that will work for your setup eventually. 

      Reply Like
    • Angela at YNAB It's possible that it could miss transaction, yeah. If YNAB end up implementing https://support.youneedabudget.com/t/36pjm0/import-transaction-id then this problem is moot :)

      If not, then I am sure I can work something out. It makes total sense why you limit the matching in the way you do.

      Reply Like
  • Hey everyone.

    So, we're building a importer for banks here in Brazil that you currently don't support. And it'd be great for us if the API did the matching logic by itself. Right now, if the I have added manually some transaction using the app or the the site, and latter  the importer, I get a a duplicate transaction without the possibility to match those transactions. 

    Reply Like
    • Pedro Lauro You can use the import_id field when posting transactions (check out the Model tab) to specify whether a transaction brought in through the API should be treated as imported or manually entered. 

      If you specify an import_id other than null, you would be able to match transactions brought in through the API to your manually entered transactions :) 

      I hope that helps!

      Reply Like
    • Angela We're already using the import_id field, with the id transaction value provided by the bank's API. YNAB does enable the `match` option so I can do it manually. But what I was looking for was the automatic apply of matching rules, just like when I manually import an OFX file. Here's an example:

      First image: before import 

      Second image: after import (using `/budgets/{budget_id}/transactions/bulk` API)

      Reply Like
  • Ohhh ...  Pedro Lauro  - I totally misunderstood the last line of your message. Okay, I can add that to our list of feature requests! 
     

    Reply Like 2
  • @angela_ynab Any changes here? I'm running into the same thing (I think); I hand-enter transactions, but when the API bulk-creates them based on info from the bank, I never see the match icon (chain) as I do if importing a CSV. `import_id` is set.

    Reply Like
    • Kevin K. You should still be able to select a manually entered transaction and one imported through API (import_id specified) and manually match them using that option from the Edit menu when both are selected.  The ability to automatically match when importing through the API is still on our request list. 

      Reply Like 1
      • Kevin K.
      • kkaland
      • 6 mths ago
      • Reported - view

      Brady Thanks for the reply! That works. Auto-matching via API will be great.

      Reply Like
      • chbndrhnns
      • Cloud Test Engineer
      • Magenta_Deer_43f0695638
      • 4 mths ago
      • Reported - view

      Brady I would also very welcome auto-matching for API-imported transactions.

      Reply Like
    • Brady  Adding my vote for Auto-matching transactions via the API. It would be super useful

      Reply Like
    • Brady   +1 vote

      Reply Like
  • Update - we are actively working on Matching support for the API.

    Reply Like 4
  • The manual workaround worked for me for now. But, +1 for the auto matching! Thanks YNAB dev!

    Reply Like
  • Matching is now supported!  When specifying an import_id when creating a transaction, we'll attempt to match to a user-entered, non-imported transaction on the same account, with the same amount, within a +/-10 day window.  If matched, the new matched_transaction_id field will be populated and the imported and user-entered matched transactions will be returned in the response.  Only the user-enter side of the match is visible in the client apps.

    Reply Like 2
  • Thanks, that's great news !

    Would it set the 'cleared' flag ? Or it that up to the API user when you return it's been matched ?

    Reply Like
    • berksgr Good question - just like the client apps, if the user-entered transaction is not already cleared, it will be marked cleared as part of the matching process.  If it is marked reconciled, it will stay reconciled.

      Reply Like
      • berksgr
      • berksgr
      • 7 days ago
      • Reported - view

      Brady Great ! 🙂

      Reply Like
  • Great work Brady!

    Reply Like
Like3 Follow
  • Status Answered
  • 3 Likes
  • 7 days agoLast active
  • 22Replies
  • 1735Views
  • 11 Following