Balance error with matching uncleared transaction

damp

I have been importing some historic transactions via mint.com formatted .csv files created from old statements. I've managed to semi-automate the process and have a few years worth of data, carefully matched against each monthly statement to make sure nothing was been missed - so reconciling each statement and correcting any errors on a per statement basis.

So this was going fine, but after the last import, I noticed my balance was off by a small amount. There was also an uncleared transaction from a couple of years back, matching the amount of the error. Now I could just delete that old transaction, and the balance would now be correct. But it's a real transaction (checked against the old statement), so I don't want to do that.

Any idea why or how that might have happened, and what to do - save just throwing in an adjustment, which I don't want to do - accuracy is what I'm after here!

Many thanks.

Quicken Carlos

Hi @damp,

Thanks for reaching out to the Quicken Community.

Based on your description, since the balance discrepancy appeared after your most recent CSV import, I suggest confirming whether the duplicate transaction is included in the last CSV file you imported.

When importing a CSV file, imported transactions are always added as new transactions rather than matched to existing ones. Unlike Web Connect (.QFX) imports, CSV imports do not check for or match existing transactions. Every transaction in the file is added to the register, even if an identical transaction already exists.

I recommend reviewing the transactions in the CSV file before importing it to ensure there are no duplicate transactions and to help keep the account in balance.

You may also find it helpful to review our support article on importing a CSV file.

I hope this helps!