QBO File Merger

Why merge QBO files?

Banks hand out history in slices. You wanted a year of transactions; the download page offered a month at a time, and now twelve QBO files sit in a folder, each waiting for its own import, its own review, its own chance to be the one you forgot. Or a bookkeeper receives a client's statements as four quarterly files when the engagement needs one continuous year. Importing slice by slice works — QuickBooks accepts each file — but every seam is a place for overlap, gaps, and doubt.

Merging first turns the pile into a single statement: one file, one import, one period to reconcile. The merger pools the transactions from every file, sorts them by date, and rebuilds a clean OFX 1.02 QBO around them — the mirror image of the QBO splitter, which cuts one file down to a chosen date range.

The overlap problem, and how duplicates are removed

The risk in any merge is the seam. Bank downloads rarely tile perfectly: February's file starts on January 30th, and suddenly three days of transactions exist twice. Import both copies and QuickBooks' own FITID protection catches most of it — but "most" is doing heavy lifting, and cleaning up afterwards inside QuickBooks is slow.

So the merger dedupes before anything is built, on a strict rule: a row is dropped only when another row matches its transaction ID, its date, and its amount. All three together are the fingerprint of the same bank transaction downloaded twice. Anything weaker — same amount, same day, same shop — is kept, because real life is full of identical-looking purchases that are genuinely two transactions. Rows whose files carried no FITID are never removed at all. The summary tells you exactly how many rows were dropped, so the merge is auditable, not magic.

What the merged file carries

One account at a time — the rule that matters

A QBO file is married to one account: its header names the account every transaction belongs to. The merged file inherits a single account number, so everything you pool must belong to that account. Merging two accounts' downloads would not produce a combined statement — it would produce one account's file containing another account's transactions, and QuickBooks would file them all under the wrong account. Merge per account: checking with checking, each credit card with itself.

Merging across a bank change

If the account moved banks mid-year — an acquisition, a rebrand, a new download portal — the two halves are still the same account, but the older files may carry the old bank's identity and a different account-number format. Merge those with extra care: check the per-file counts and the merged period in the summary, and run the result through the QBO File Checker before importing, so any identity mismatch surfaces before QuickBooks sees the file.

After the merge

The merged QBO imports exactly like a file from your bank — one Web Connect import covers the whole period. Because FITIDs survive the merge, importing it after some of the original files were already imported does not double-post: QuickBooks recognises the transactions it has. If you need the combined data as a spreadsheet instead — for a review pack or a migration — the CSV download holds the same merged, deduped rows in the same columns as the QBO to CSV converter. And if a merged file turns out to span more than you need, the splitter trims it back to the exact dates you want.