CSV import - can't re-import deleted transactions

I'm trying to import transactions via a CSV file but even the  most basic test cases are getting incorrectly flagged as "previously imported."

For example, this text in a CSV:

Date,Payee,Category,Memo,Outflow,Inflow
02/28/2019,Me,Income: Available this month,some description,,80.0

Gives this result:

Import Successful

1 previously imported transactions has been skipped.  

Testing a little more in another account it looks like it remembers what was imported even if it was then deleted.  I'd tried an import of a batch of transactions but deleted them so I could make some corrections pre-YNAB and then re-import.  But now how can I get myself out of this limbo and re-import successfully?  Thanks!

10replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • To prevent duplicates from importing, YNAB won’t allow importing those transactions into that account. To get around that, you can either enter those transactions yourself or create a new account. 

     

    If you create a new account, you can move all of the existing transactions over and delete the current account, that way you don't lose any transaction history. Here’s how to do that:

     

    1. Create a new account to replace the current one by clicking on Add Account > Unlinked > Enter Name & Type (You'll have to give it a slightly different name). Enter a $0 starting balance for now, since we’re going to move over all the transactions from the other account. Do this first!  

    2. Go to the original account, select all of the transactions, and move them to the new account using the Edit menu.

    3. Refresh your browser.

    4. Hover over the name of the original (now empty) account, click the edit icon, and Delete Account.

    5. Now, you can edit the name of the new account and/or set up Direct Import.

     

    Now, when you import that file, you should be able to import those missing transactions just fine.

    Like
      • Gray Snow
      • Keeper of the Ledgers
      • Gray_Snow
      • 1 yr ago
      • 1
      • Reported - view

      Chrissy thanks.  So, once I have an account in this weird state, it can't be undone without moving all transactions to a new account?   It seems like a bug, but if the workaround solves the issue for me, it I'll do that.

      Like 1
    • Gray Snow That's right, you'll have to move them to a new account. The reason that File Based Import was designed that way was to help prevent transactions you've imported or previously deleted (for any reason) for reimporting. For some people, they may get one file from their bank that has all their transactions from the 1st-15th and then the next time they download a file, they forget where they left off so they download from the 10th-30th, so the logic is in place to prevent those duplications from importing. 

      Like
      • Gray Snow
      • Keeper of the Ledgers
      • Gray_Snow
      • 1 yr ago
      • Reported - view

      Chrissy Thanks for the clarification.  The new account trick did work, though moving all the many transactions took a few tries and YNAB gave a few errors about the internets and tubes before it successfully finished them all.  I can understand the logic behind the default behavior, though I still wish there was a more elegant way to work around it when something like this comes up.

      Like
      • bevocat
      • Sometimes, It Just Sucks to Be You
      • bevocat
      • 1 yr ago
      • 2
      • Reported - view

      Gray Snow Why couldn't you do the process the other direction? Create a new temp account, do the import for the new transactions, then move them from the temp account to the existing account? Then clean up the temp account or keep it for next time you need a swap account?

      Like 2
      • Gray Snow
      • Keeper of the Ledgers
      • Gray_Snow
      • 1 yr ago
      • Reported - view

      bevocat funny you mention it, that just occurred to me in another thread.  That makes sense to me!   If that could work it could be much smoother since it would be far fewer transactions to move around.  But Chrissy will it check for duplicates when moving existing transactions, or is it just when they are first imported?

      Like
    • Gray Snow I hope you don't mind me stepping in here! Duplicates are checked for when you're importing the file. If you import in a new account, then move transactions from the original account—all of the transactions are moved over.

      If you have duplicates, you can select all the transactions you don't want to keep using the checkboxes on the left and click Edit > Delete to remove the transactions from your register.

      Like
      • Gray Snow
      • Keeper of the Ledgers
      • Gray_Snow
      • 1 yr ago
      • 2
      • Reported - view

      Nicole Yep, I tested this and it works as I'd originally expected.  Getting rid of the unwanted ones is simple so long as I can still filter by unapproved or "needs category" and just delete the whole batch.  And thanks bevocat for bringing this up here.

      Like 2
  • I got around this problem by converting the downloaded CSV with https://aniav.github.io/ynab-csv/ and reimporting it and it acted as if it was the first import.

    Like
  • I simply changed the dates of the transactions by one day and reimported the deleted transactions successfully - i have been changing them anyway because they are credit card transactions and there is a delay in their payments anyway (transaction month does not correspond to their time of payment)

    Like
Like1 Follow
  • Status Answered
  • 1 Likes
  • 3 mths agoLast active
  • 10Replies
  • 312Views
  • 6 Following