Home › Blog › Reconciliation & Verification › What reconciled, flagged, and unverified actually mean
Understand what reconciled, flagged, and unverified verification outcomes mean for a converted statement, and what to do next with each one.
By StatementVerified Editorial · November 3, 2026 · 7 min read · Filed under Reconciliation & Verification
When a statement is converted from a PDF into a spreadsheet, the most important question is not whether the file opens. It is whether the numbers inside it still prove themselves against the statement they came from. StatementVerified reports one of three outcomes for that proof, and each outcome asks for a different response. Treating all three as a generic success message defeats the purpose. A clear outcome label tells the bookkeeper whether the file can go straight to import, whether it needs a focused review of specific rows, or whether it should not be trusted at all yet.
This guide explains each outcome in plain terms, what checks sit behind it, and what to do next in each case. The underlying idea is the same one that governs a bank reconciliation. The statement prints an opening balance, a list of transactions, and a closing balance. A faithful conversion must preserve that arithmetic. If opening plus every signed transaction equals closing, the conversion agrees with its own source. If it does not, something was dropped, duplicated, misread, or mis signed along the way, and the honest response is to say so before the file reaches any accounting system.
Reconciled means the converted transactions, added to the statement opening balance, produce exactly the statement closing balance. Every row was read, every sign was applied as the statement presents it, and the running balance, where the statement prints one, agrees row by row as well as in total. That is a strong result because an error would have to cancel itself out perfectly to hide, which is rare. Two compensating errors of exactly equal and opposite size can theoretically pass a totals check while a running balance check would still catch them, which is why both checks matter when the data allows them.
For a reconciled file, the correct next step is to proceed with confidence but not with carelessness. Still confirm the account, the period, and the file format before import, and still review the import preview in QuickBooks Online, QuickBooks Desktop, or Xero before accepting it. Reconciled speaks to fidelity to the statement. It does not certify that the client categorized expenses correctly, that a transaction belongs in this entity rather than another, or that the statement itself was the right document. Those are bookkeeping judgments that no converter can make for you, and they remain your job on every file.
Flagged means the conversion is largely sound but one or more specific checks raised a question that a person should review. Examples include a running balance that steps out of line at one row and then recovers, a date that falls just outside the statement period, a transaction description that was difficult to read, or a totals check that agrees while a secondary check, such as a count of transactions or a section subtotal, does not line up cleanly. The value of a flag is its specificity. It should point at the row and the reason, so review takes minutes instead of a full manual recheck of every line.
Work a flagged file by going straight to the flagged rows and comparing each one against the PDF, character by character for amounts and dates. Most flags resolve as a legitimate statement quirk, such as a pending item listed separately, a correction entry, or a fee section presented apart from the main activity list. Some resolve as a genuine read error that you can correct in the spreadsheet before import, after which you should recheck the totals by hand. If you correct a value, note what you changed and why. Never clear a flag by deleting the row or adjusting an unrelated amount to make the totals agree, because that trades a visible question for an invisible error.
Unverified means the conversion could not be proven against its source. That happens when the statement does not print both an opening and a closing balance in a readable form, when pages are missing, when the document is a partial export rather than a full statement, or when the arithmetic simply does not tie and no specific single cause can be isolated. Unverified is not an accusation that every number is wrong. Many rows may be perfectly accurate. It is a statement about evidence: the file as a whole has not earned trust, so importing it without further work would move unproven data into the books.
Treat an unverified file as a starting draft. First, check the document itself. Confirm you uploaded every page, that no page is a duplicate of another, and that the period covers a complete statement cycle. If the bank offers a fresh download, get it, because a reissued statement sometimes resolves a truncated or damaged file. Then work the file against the PDF in sections, using any printed subtotals or running balances as checkpoints. If you cannot bring the file to a tie, the safest course for client books is to key or verify the activity manually rather than import and hope the reconciliation at month end will sort it out. It rarely sorts itself out without the same work, done later and under more pressure.
The three outcomes exist because the cost of a bad import is asymmetric. Catching a dropped row before import takes a minute. Finding it after import, after categorization, after a reconciliation has been forced around it, can take an hour and can leave corrections scattered across two periods. A clear label at conversion time moves the cheapest check to the earliest moment. It also creates a defensible workpaper trail. When a client, a tax preparer, or a reviewer asks how you know the imported activity was complete, a reconciled result tied to a specific statement is a real answer, while a memory of eyeballing a spreadsheet is not.
It also protects against the most dangerous conversion failure, which is the plausible file. A spreadsheet that looks tidy, sorts well, and imports without a single software complaint can still be missing the last transaction on a page or carrying a duplicated block from a repeated page. Accounting software validates file structure, not completeness against a PDF it has never seen. Only a balance proof compares the file to its source. That is why an outcome label grounded in arithmetic deserves more weight than a clean import message, and why flagged and unverified results should slow an import down rather than be clicked through.
Build the outcome into your standard intake routine so no file skips it. On receipt, record the account, period, opening balance, and closing balance from the statement itself. Run the conversion, note the outcome, and file the statement with the result. Reconciled files go to import with a normal preview review. Flagged files get a row level review first, with any correction documented on the workpaper. Unverified files stay out of the accounting system until they are proven in sections or rebuilt from a complete statement. The routine takes little extra time on good files and saves the most time exactly where files are bad.
Over a few months this habit produces a useful pattern record. If one bank layout repeatedly flags, you learn to watch its fee section or its pending transaction block. If scanned statements from one client repeatedly arrive unverified, you can ask for original downloads instead of scans and fix the problem at its source. The labels stop being per file trivia and become process intelligence. That is the real payoff of honest verification language: not just a verdict on one conversion, but a steadily cleaner intake process for every statement that follows it into your practice.
No. Reconciled means the converted amounts and dates faithfully reproduce the statement and its balances tie. Categorization, tax treatment, and whether a transaction belongs to this business at all are separate bookkeeping decisions that still require your review after import.
Yes, after you review each flagged row against the statement PDF and correct or confirm it. Document what you checked. A flag is a pointer to specific rows, not a rejection of the whole file, but importing without that review discards the protection the flag exists to provide.
Incomplete or unreadable source material is the most common reason, such as missing pages, a partial period export, or a scan where balances cannot be read reliably. The next most common is a genuine arithmetic gap with no single isolatable cause, which needs section by section checking.
Reconciliation & Verification · November 2, 2026
Find a missing transaction fast by bisecting the statement balance, comparing mid period checkpoints, and narrowing the window until the row appears.
Reconciliation & Verification · November 4, 2026
Use opening and closing balance checks and month to month continuity to prove a full year of statements has no gaps, overlaps, or missing periods.
Reconciliation & Verification · November 5, 2026
How the row by row running balance check works, why it localizes a conversion error to a single row, and how to use it in your own review each month.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.