Duplicate Transaction in Spending Data
Christopher T
Hello,
I noticed my spending for this month in YNAB vs Lumy was off with Lumy’s spending total being greater than YNAB. When investigating, I found a duplicate transaction in Lumy that isn’t in YNAB. This isn’t the full discrepancy, but it’s a large amount of it. Please let me know if you need anything else to review.
Thank you,
Chris
Brandon Trautmann
Christopher T thanks for the report. This has been on the radar for a bit but I haven’t yet been able to confirm the root cause is what I think it is.
Can you do me a favor? Can you check in YNAB to see if there is any transaction within YNAB that is PENDING that is related to/matched with this transaction? For context, here is a blurb from the YNAB API team regarding one reason that we may see duplicate transactions:
“Generally, it is not expected that pending transactions will show up at all in the API because they are not synced down. We have updated the endpoint description in our API documentation to make this more clear. For example, the GET transactions endpoint now states that it "Returns budget transactions, excluding any pending transactions."
However, there is one exception. When a pending transaction matches with a user-entered transaction, you will see a temporary pending transaction labeled with a "P" in the import_id field (as you suspected, that does indicate a pending transaction!). So here's where things get a little funky.
After the matching cleared transaction imports, YNAB then rejects the pending match and replaces the matched transaction with the cleared match. This deletes the matched pending transaction, which is why those transactions are automatically cleared out after some time.
This is on our developer's radar, but because of the system currently in place and the limitations of the API, we don't have a workaround or exact definition of the lifecycle of pending transactions to offer at this time.”