The right order for a QuickBooks Online cleanup: structure, then reconcile, then summarize

When QuickBooks Online has fallen months behind, the instinct is to open the bank feed and start matching. That is usually why cleanups drag on. If the structure of the file is broken, every hour spent reconciling is spent building on a bad foundation, and the numbers still will not tie out at the end. A cleanup goes faster when you run it in a fixed order: fix the structure first, reconcile against an independent source second, and summarize what was wrong last.

Step one: fix the structure before you match anything

Before a single transaction is reconciled, look at the file on its own for structural problems. Duplicated entries inflate both sides at once. An unexplained opening balance quietly throws off every period that follows. Stale open items sit on the books long after they cleared. Changes made inside a period you thought was closed mean a report you already trusted is no longer true. None of these show up as a failed match; they hide underneath one.

This is why the first pass should be structural. In FlowLedger these surface as individual book-integrity findings, each a stored record you can open and inspect, so you resolve the foundation before you build on it. It is an internal integrity view of the file, not a credit rating, and every component is traceable.

Step two: reconcile against a second source, in dollars

Only once the structure holds does reconciliation mean anything. And reconciliation here does not mean matching the bank feed to itself. It means comparing QuickBooks to an independent record of the same money: the bank statement, the processor settlement, the raw payout file. Where they disagree, the difference is real and measurable.

Measure that difference as the leftover in dollars, not a health percentage. A grade tells you nothing you can act on; a dollar figure points straight at the transaction that is missing, doubled, or miscategorized. That is what Money Truth reports, and the reconciliation workspace lets you pair every movement and drive the leftover down to zero, with the match status persisted between sessions. Each pair carries its evidence: date, amount, reference, counterparty, so a match is something you can defend rather than assume.

For books that are months behind, the Catch-Up workspace runs this same comparison across prior periods against imported statements, so you are working overdue months to resolution rather than guessing at them.

Step three: summarize what was actually wrong

The deliverable a cleanup client actually wants is not a reconciled checkbox, it is a short, honest account of what was broken and what is now proven. Because every finding and every pair in FlowLedger is a stored record with evidence, that summary writes itself from real data: the duplicates removed, the opening balance explained, the leftover resolved to zero, the periods brought current. No invented figures, and where the evidence is not there, the line stays blank instead of being filled to look finished.

What this does not do, on purpose

FlowLedger is a proof layer on top of QuickBooks, not a replacement for the bookkeeper. It does not write back to QuickBooks, it does not categorize or re-enter transactions for you, and it does not post corrections. Those edits are made by a person inside QuickBooks Online. What FlowLedger does is turn a vague clean up the books into a finite, dollar-level, provable list, so the person doing the work knows exactly what to fix and can show that it is done.

If you would rather see the correctness question on its own first, start with how to know if your QuickBooks numbers are right. When you are ready to run it on your own file, create an organization, connect QuickBooks and one real source, and work the leftover down to zero.