Importing CSV into Tracking Account
Hey, I'm using YNAB for our business and have an issue with an import to tracking account. We have set up an A/R tracking account, but needed to delete and reenter all the transactions. I exported our A/R from QB as a CSV file, deleted all entries from the A/R tracking account, then imported the new CSV file. Problem is, YNAB is skipping transactions that were previously entered even though I've deleted them. Here's the message I get after import:
"16 transactions have been successfully imported. 70 previously imported transactions have been skipped. "
I deleted those "previously imported transactions" so they don't exist in YNAB anymore and I really don't want to enter all 70 transactions manually. Does anyone know of a way to force YNAB to import all transactions?
Is this a bug that YNAB believes it should skip a transaction that doesn't exist?
Bruce This is a gooooood question! When you import transactions and then delete them, YNAB won't allow those same transactions to be imported into that account - to prevent duplicates. So this does sound expected. To get around this without manually entering them, though, you can create a new account!
You'll move all of the existing transactions over and delete the current account, so you don't lose any transaction history. Here's the step-by-step:
- Create a new account to replace the current one - choose unlinked and enter a $0 starting balance - since we’re going to move over all the transactions from the other account.
- Go to the original account, select all of the transactions, and then Edit --> Move.
- Refresh your browser.
- Then, you can delete the old account!
When you import that file again, you should see those missing transactions just fine.🤞Does this get you where you're needing to go?
Bruce This is a gooooood question! When you import transactions and then delete them, YNAB won't allow those same transactions to be imported into that account - to prevent duplicates.
Rachel This is a defect. It looks like the underlying database has a referential integrity problem. Please ask one of your database administrators to join this thread so that we can discuss the issue further and get it resolved.