Farin Farin
Accounting

Reconcile statements and resolve exceptions

Upload the statement first, review the matching results, work the exception queue, and close the session only after the checks pass.

6 min read Updated Mar 18, 2026 Managers and bookkeepers closing the month

Use this article at month-end or anytime you need to prove the statement, feed, and ledger are aligned.

The normal workflow starts in Reconciliation with a statement PDF upload, then moves through matching, exception review, and final close.

Quick facts

Start here

  • Reconciliation is upload-first, but there is a paper and manual fallback when needed.
  • High-confidence account matches can continue without a prompt. Lower-confidence matches ask for confirmation.
  • The exception queue focuses on unresolved issues like missing, extra, or ambiguous items.
  • Closing is ledger-driven, so some feed-only issues may not block the session when the ledger checks pass.

Step 1: Start the session with a statement upload

  • In manual mode, enter the statement balances and date range directly.
  • Use no-feed mode only when the account really does not have reliable feed data for that period.

Upload the PDF or switch to Paper / Manual

Open Reconciliation.

Upload the bank statement PDF first, or use Paper / Manual when no PDF is available.

The reconciliation page starts with statement intake, then moves into matching, exception review, and close checks.

Step 2: Review the account match and auto-match results

After the statement is parsed, confirm the inferred account if the app asks.

Then let the app compare the statement, feed, and ledger and build the session review.

  • If the feed mapping is wrong, fix that instead of pushing forward with the wrong account.
  • If the app finds sync-backed accounts, it may resync and reload data automatically.
Use the account-level feed detail when the reconciliation session needs proof that the imported rows and mapped account are correct.

Step 3: Work the exception queue

Fix the cause, not only the symptom

Open Bank Feeds for feed issues and the transaction detail page for ledger issues when the exception points upstream.

That keeps the same mismatch from coming back next month.

  • Use missing exceptions when the statement or feed points to something the ledger does not yet have.
  • Use extra exceptions when the ledger has something the statement window does not support.
  • Use ambiguous exceptions when the app found more than one possible match and you need to choose.
The reconciliation session groups missing, extra, and ambiguous exceptions so you can work the queue methodically before close.

Step 4: Close only after the session checks pass

  • Make sure the summary checks, coverage, and unresolved-exception counts are in a safe state before you finalize.
  • Use Session History to reopen recent sessions when you need to continue later.
  • Closed sessions stay in history for audit review.
Close the reconciliation session only after the summary checks and unresolved exception counts are in a safe state.

Related guides

Keep going

Routes and transfers 6 min read

Create, fulfill, receive, and finalize internal transfers

Mark an order as an internal transfer, fulfill it at the source, receive it at the destination, and resolve report warnings before finalizing accounting.

transfersinventoryfulfillmentaccounting
Accounting 5 min read

Set up chart of accounts, tax components, and sales channels

Build the accounting base first so sales, payouts, tax, and receivables can post to the right places.

accountingsetuptaxsales
Accounting 5 min read

Record journals, sales, payouts, and memorized transactions

Choose the right accounting workflow for each entry, keep transactions balanced, and save recurring work as memorized templates.

accountingtransactionssalestemplates
Accounting 4 min read

Import bank activity and review bank feeds

Connect or review the bank feed, inspect one account at a time, and fix bad ledger entries before reconciliation starts.

bank-feedsaccountingimportssync