“Transactions are in the wrong order”
Order matters most when you are reconciling against a paper statement line by line. Imports rarely scramble anything at random — they sort by a field you may not have expected, and same-day transactions are where that becomes visible.
Symptoms
Same-day transactions appear in a different sequence than on the statement The running balance moves up and down illogically within a day The register order changes after a re-sort and will not stay put
What actually causes it
Statement formats carry no ordering
A file is a set of transactions, each with a date. Nothing states which came first within a day, so software falls back on file order, entry order or transaction id — and different programs choose differently.
Times are absent or all identical
Where dates include a time, same-day ordering is possible. Many banks write midnight for every transaction, which removes the only tiebreaker.
Posting order differs from the order you remember
Banks post in batches, so three purchases made in sequence can post in any order. The statement itself may not be chronological in the sense you expect.
How to fix it
- Drop the file into the fixer below to see what the date fields actually contain — dates alone or dates with times decides whether ordering is even possible.
- Sort the register by a stable secondary field such as the transaction id rather than fighting the display order.
- For reconciliation, match on amount and payee rather than position; same-day order is not information the bank sent.
- Do not reorder by editing dates: the next import will bring the original order back.
Related import problems
Skip the manual edit — fix it automatically
The fixer shows whether the dates carry times, which is what determines if same-day ordering can be preserved at all. Free, no signup, no upload.
Open the fixer