Importing bank transactions doesn't detect transactions that have been previously imported

1

Hi there, I’m having a frustrating issue where when I import my credit card transactions (on either CSV or OFX) it doesn’t recognize previously imported transactions, even if I have already imported 80% of the transactions shown on the statement.

I often have to import before my credit card statement date, and it would be great if I could then import the statement to only capture what I have missed. As it stands I have to manually check all of the transactions - hence the frustration.

2

@Mick - Sorry for the trouble importing your transactions. It sounds like you’re saying Goodbudget isn’t recognizing that you’ve already imported certain transactions in your imported file and is marking them as new transactions.

Your bank gives each transaction in your OFX file that you download a unique number called a FITID. When you import that file, Goodbudget records that FITID so it can keep track of which transactions you’ve imported before, so you don’t import the same one more than once. However, if your bank changes the way they create FITIDs, then Goodbudget won’t be able to recognize those transactions as already imported creating this kind of problem. Unfortunately, if the FITID values are different, Goodbudget will be unable to recognize that you’ve already added a transaction previously.

However, if you’re bank is changing the way they generate FITIDs in their OFX files, you can mitigate importing or seeing duplicates by only importing with files that have date ranges that don’t overlap with your currently existing imported transactions. For example, if you already imported up through April 1, your next file should start on April 2 through current.

Further, be sure to ALWAYS use the same file type to import with going forward. If you prefer using OFX, stick with that file type. CSV files do not have FITIDs (Goodbudget manually generates them using each transation’s Name, Date and Amount), so switching between these files types will definitely cause this kind of issue.

I hope this helps!
Karisa

3

Hi Karisa,

Thank you very much - I think this explains where the issue is coming from. My credit card statements can be exported in OFX but if I export the transactions manually then the bank doesn’t support OFX and it has to be CSV - so that is where the mixture of file formats is introduced. Going forward I will stick with CSV across the board (unfortunately, given OFX is just easier) and see if that fixes it.

Thanks again,

Mick

4

Hi Karisa,

Also whilst I’m here I thought it would be worthwhile to note that I would be a guaranteed premium subscriber if syncing with New Zealand bank accounts was available.

From what I can see in other threads this isn’t something that there is a timeline on.

You might already be aware of this, but the following is a service that provides open banking connectivity with New Zealand’s financial institutions, and is what is used by PocketSmith.

Fingers crossed this is something that becomes available in the future - thanks again.

Mick