Import missing a few transactions - bug or anomaly?
I’m a longtime YNAB4 user and just migrated to the new/improved nYNAB. (I think that’s what you guys are calling it).
Anyway - I linked two separate accounts last night - one Citibank Credit Card and one Bank of America Checking Account.
in BOTH cases - after the import, the reconcile didn’t match. After digging transaction-by-transaction, i found that BOTH accounts were missing a handful (4-6) transactions in the early July 2018 (first couple weeks) time frame.
Everything was there before and after those couple of weeks, and once I manually added them in YNAB, my reconciles were to the penny.
This seems really strange that it would happen on two totally different accounts/banks.
Anyone see this before?
-
Hi Fireproof !
That is definitely odd! I've heard of hiccups during migration and usually a fresh migration fixes the issue, but it's odd that those specific transactions were skipped. Was there anything special about them in YNAB 4?
Now that you've found the cause of the discrepancy, and rectified things, you should be good to go moving forward, but I like to solve mysteries when we can! :)
Reply-
Faness Agreed - it's definitely odd. I couldn't find any patterns. I'll look again and see if maybe there was anything unusual in the transaction data that might indicate something.
No worries now - I agree I should be good to go. Just wanted to alert you in case you knew of a hiccup or something. Good just be crappy wifi. haha.
thanks.
Reply -
Fireproof Sure thing! If anything else odd seems to pop up, please don't hesitate to let me know! :)
Reply
-
-
How up to date was your YNAB4 migration? The direct import is limited in how far back it can retrieve transactions.
Reply -
Oh you know what - that might be it. I wasn't up to date. So I bet those missing transactions were the GAP between my previously imported transactions in YNAB4 and the new directly imported transactions through the new Web App - only being able to go so far back.
I think you solved the mystery!
Reply -
I'm new to all this, but I found this forum post trying to solve the same issue. I started in early October. In one account, a single transaction (an inter-account transfer) was missing from a download - but another transaction on the same date was present. It's playing hell with reconciling accounts!
Reply-
Hi WormSpit !
Can you give me a few more details on those missing transactions? What bank are you seeing that issue with? Was it just the one, or are those inter-account transfers always skipped? Once is an anomaly, more than that is something we should have our Direct Import partner investigate!
Reply -
Faness It's Chase Bank. In one case, one side of the transfer showed up but the other did not; it was moving money from checking into savings, both Chase accounts in my name. It made a discrepancy in the reconciliation. I had to go back and adjust the starting balance of one account, because if I added in the transaction, it needed to be on *both* sides to be a transfer. Unfortunately, I didn't write down which ones were missing, and of course they're all corrected now.
Is there a way to make a copy of the account and try importing it all over? I'd be willing to do that, but not if it means losing the reconciled clean version I finally worked out.
Reply -
Faness I chased it down eventually. In one, it was an inter-account transfer. In another, there were two $150 transactions on the same day; both were payments. One downloaded, the other did not.
I did notice that most of the errors were early on in the account; I haven't seen them again the past couple of weeks. Then again, I've only been working with it for right at a month, so I don't have a long perspective. I think it was four or five total transactions that failed to download.Reply -
WormSpit Thank you for tracking down those details! I have a Chase account as well so I checked that transfer import, but it worked correctly on my end. It sounds like the transfer issue you ran into was caused by the Starting Balance Date (YNAB doesn't automatically import transactions from before your starting date). This shouldn't happen again.
That second payment not importing is odd. I'm curious if seeing the same $150 amount registered as a duplicate so it was skipped. Hopefully, it won't happen going forward, but can you let us know if it does? We can reach out at that point to grab a few extra details and have our Direct Import partner investigate! :)
Reply
-
-
Sorry to keep poking at this! I'm now working on updating the transaction register for a credit card. It's got a discrepancy on the current amount of almost three hundred dollars ($292.46) and I haven't entered a single transaction into this register by hand - all of it has been downloaded by import.
This is made more challenging by the fact that the credit card website doesn't show a running balance. I don't know if the "beginning balance" import matches the balance from that day on the credit card, although I assume it would be.
I did add the Toolkit to get a running balance on YNAB, because I find it helps me see where any discrepancies are. I wish it was a regular feature instead of an add-on.Reply -
It's a Capital One account, if that helps any. Also, it keeps locking me out - I have to re-enter a code each time I want to import, but I don't use it often, so it's not a huge deal, just frustrating.
Reply -
OK. I figured out what was wrong. It imported the starting balance *as of* 10/30, and there were five transactions on that day on that card. It imported two of them. I added the other three and the balances match now.
Reply
