The OFX reader rejects a file that repeats a transaction reference. Each structured bank transaction must have a unique source reference within the file so the movements remain identifiable.
- Obtain a fresh export for the same account and period to check whether the repeated reference came from a damaged or combined file.
- Compare the source transaction count and statement activity.
- If the bank’s export still repeats references, contact support or use another supported export while retaining the original evidence.
Do not append arbitrary characters to repeated references solely to pass validation. That creates new identifiers without establishing whether the rows are separate real transactions.
Separate a repeated record from a repeated amount
Two legitimate purchases may share a date and amount but should still have their own source evidence. A repeated reference is a different issue from the possible-duplicate decisions shown later in the row import.
If you switch to CSV, review its duplicate candidates carefully rather than assuming the format change resolved the underlying data problem. Keep the original structured file and identify the affected references so the final accounting record can be traced to actual bank movements.
Was this article helpful?
Tell us whether this answered the question you came with.