Home › Blog › QuickBooks › Reconcile after import: the QuickBooks checklist
A post import checklist for QuickBooks before you reconcile the month, covering counts, duplicates, direction, transfers, and the closing balance proof.
By StatementVerified Editorial · November 5, 2026 · 7 min read · Filed under QuickBooks
Importing a statement file into QuickBooks is the middle of the job, not the end. The dangerous window is the gap between a successful upload message and a reconciliation, because a file can upload successfully while carrying a duplicate block, a reversed section, a missing first row, or a payment recorded as an expense. A short, disciplined checklist in that window catches those problems while the fix is still a simple correction to fresh, uncategorized work, rather than surgery inside a closed month. This guide is that checklist, in the order an experienced bookkeeper actually runs it.
Work the steps in sequence and do not skip ahead to reconciling because the balance looks close. Close is the most expensive word in bookkeeping. A month that almost reconciles contains a specific, findable error, and the checklist is designed to surface it by category: completeness first, then duplication, then direction, then classification hazards, and only then the formal reconciliation proof. Keep the statement and your verified workpaper open beside QuickBooks for the entire pass, because every check compares the software record back to the bank evidence.
Immediately after import, compare three numbers between QuickBooks and your workpaper: the transaction count for the batch, the earliest and latest transaction dates, and the net movement for the period. All three should match exactly. A short count means rows were skipped during upload, often malformed or header confused rows, and proceeding would build the month on partial data. A date range extending beyond the statement period means a format problem pulled rows from another period or misread years. A net movement mismatch with a correct count points to an amount or sign error on one or more rows, and its size is your first diagnostic, equal to a row, double a row, or a section total, as in any balance investigation.
If any of the three disagree, stop and fix the batch before anyone categorizes a single transaction. The cheapest correction is usually to remove the flawed batch cleanly and reimport a corrected file, because at this stage the transactions carry no categories, matches, or attachments worth preserving. That calculus reverses completely once categorization begins, which is why this check must happen in the first minutes after upload, not at the end of the week. Make it a hard rule in your practice: no categorization work starts on an import whose count, range, and movement have not been signed off against the statement.
Next, sweep for duplicates while the batch is still visually fresh. Sort the review list or the register view by amount and scan identical neighbors, checking date and full description before judging any pair. Pay special attention to the seam dates at the start of the imported range, where overlap with a feed or a prior import would concentrate, and to any amount that the statement count shows once but the batch shows twice. Remove proven duplicates by the layer rule: exclude review items never added, delete bare register copies, and always protect a copy that is matched, categorized with documentation, or already reconciled in a prior period.
Then spot check direction with three known transactions chosen deliberately: the largest deposit, the largest payment, and one small fee. Trace each from the statement through the import into the register and confirm money moved the correct way and the account balance responded correctly. Direction errors that survive a totals check do so by offsetting, and a deliberate look at the extremes plus a small ordinary item catches the realistic offset patterns: a reversed fee section, a deposit recorded as a payment paired with a payment recorded as a deposit, or card style sign confusion on a bank account. Three traces take two minutes and certify the convention for the whole batch.
Review every transaction that touches another account before reconciling, because inter account activity is where imports most often create phantom income or expense. Card payments should be transfers matched to the card account, owner contributions and draws should land in their equity accounts rather than income or expense, and transfers between bank accounts should appear once as a paired movement, not as unrelated income in the receiving account. Scan the imported descriptions for payment, transfer, and the names of the business other accounts and institutions, and confirm each one is coded as a movement between balance sheet accounts where that is what it economically is.
Check matched items with equal care. QuickBooks suggests matches between imported activity and existing records such as checks written, invoices paid, and bills entered. Accepting a wrong suggestion, typically a same amount different purpose match, clears the wrong record and leaves the right one outstanding, a swap that reconciliations display as two unrelated problems. Verify matches on payee and purpose, not amount alone, especially for recurring equal amounts like rent, subscriptions, and loan payments. Unmatch any suggestion you cannot explain in one sentence. A transaction left unmatched is visible work remaining. A transaction matched wrongly is invisible error, and invisible always costs more.
Once counts, duplicates, direction, and transfers are clean, review categorization with a skeptical eye on the automatic rules. Rules are excellent for stable recurring purchases and quietly dangerous at the edges: a new vendor whose name resembles an old one, a refund that inherits the original purchase category in the wrong direction, or issuer generated card lines swept into a generic fee category. Sort the categorized batch by category and scan the largest item in each category, plus any category whose period total moved sharply compared to the prior month. You are not auditing every coffee. You are confirming that the big money is sensibly placed and that no category is silently absorbing items that belong elsewhere.
Confirm sales tax, payroll, and loan related lines received their special handling rather than a single category dump. A loan payment split between principal and interest that imports as one line must be split in the register, because categorizing the whole payment as interest overstates expenses and understates the liability paydown. Payroll gross, taxes, and net pay have the same multi part character. These are classification steps no import can perform from a bank description alone, and the checklist exists partly to force the pause where a bookkeeper, not a file, makes those calls with the supporting reports open.
Now reconcile the account to the statement inside QuickBooks, using the statement closing balance and end date as the target. With the prior steps done, the reconciliation should close with a zero difference and an outstanding list containing only genuine timing items: recent checks not yet cleared and deposits in transit at period end. Read that outstanding list as a final review. Anything old, odd, or already present on the statement does not belong there and sends you back to the relevant checklist step. A clean outstanding list, short and explainable item by item, is the signature of a healthy import and a healthy month.
File the evidence set together: the statement, the verified conversion workpaper with its balance proof, the import log entry with counts and movement, and the reconciliation report. Note any corrections the checklist produced, in plain language, on the workpaper. That bundle answers future questions in minutes, supports the tax preparer and any lender review, and gives the next bookkeeper a running start instead of a mystery. The checklist habit compounds across months exactly like reconciliation itself: each clean, documented month makes the next month faster, until the post import pass becomes the calm routine it should be.
No. A short count means rows were skipped and the month is incomplete. Stop before categorizing, identify the malformed or dropped rows, correct the file, and reimport the batch cleanly. Proceeding would attach categorization work to partial data and make the eventual fix far more expensive.
Only genuine timing items: checks issued near period end that had not cleared, and deposits recorded but not yet posted by the bank at the statement date. Each should be recent, explainable, and expected to clear next period. Old or unexplained outstanding items indicate an unresolved error.
Because a card payment or inter account transfer coded as income or expense distorts two accounts at once while still tying in total on one side. Confirming transfers are matched pairs before the proof prevents phantom income and keeps both account reconciliations clean.
QuickBooks · November 3, 2026
Fix QuickBooks Online date import errors from weekday text, mixed formats, and day month ambiguity, with a safe format choice for every converted file.
QuickBooks · November 4, 2026
Why QuickBooks shows duplicate transactions after an import, how feed overlap creates them, and the safe exclude, delete, and prevention workflow.
QuickBooks · November 5, 2026
The exact QuickBooks Online CSV format explained, including the 3-column and 4-column layouts, date and amount rules, and mapping checks before upload.
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.