Skip to main content
Reconciling suits the operator well: the matching is mechanical, and the handful of judgment calls are the part you actually want to see. You hand Claude the statement. It records the period and closing balance, matches the statement’s lines against what’s already in the register, and comes back with the differences and its questions. Nothing is entered twice, and the reconciliation isn’t closed until you say so. You can also do this yourself in the app — see Reconciling an account. The two paths write to the same session, so you can start in one and finish in the other.

Handing over a statement

Give Claude the file and name the account: “Reconcile Operating Checking against this February statement.” CSV, QFX, OFX, and PDF all work. What happens next:
  1. The statement is recorded — period and closing balance, with the file itself stored against the account.
  2. A session opens, or the account’s existing open one is used. A new session opens at the statement’s closing date.
  3. Auto-match runs. Statement lines are matched to register rows, and matched rows are ticked as cleared.
  4. Nothing is entered. This path matches what’s there; it doesn’t record transactions.
Get that last point right. If the activity isn’t in your ledger yet — a new account, a gap in a feed — that’s an import, not a reconciliation. See Importing transactions. Claude confirms which one you want before it writes.

What it comes back with

Three buckets, and only two need you. Matched. Statement line, register row, ticked. Claude reports the count — “matched 47 of 52” — not the list. On the statement, not in the register. Real activity the books don’t have: a bank fee, an ACH nobody entered, a check that cleared without being recorded. These are the difference. Claude proposes a category for each from your rules and past treatment of the same payee, and enters them on your approval — cleared on the way in, since the statement already proves they cleared. In the register, not on the statement. Outstanding items. A check written on the 28th that hadn’t cleared by month end is correct and needs nothing. One from four months ago is a question. Claude flags the stale ones by age rather than listing every outstanding row.

Questions worth answering

Claude asks rather than guesses when:
  • A statement line matches two register rows within the tolerance and it can’t tell which.
  • An amount is close but not equal — a partial payment, a fee netted out, a wire cut short.
  • A payee on the statement doesn’t resolve to any vendor you have.
  • The statement’s closing balance doesn’t agree after everything it can match is matched.
Pay attention to that last one. A reconciliation that won’t foot points at a duplicate, a transposed amount, or a transaction on the wrong account, and Claude walks the difference rather than papering over it. Ask it to find the variance and it will look for a single row matching the gap, then pairs, before reporting that it can’t account for it.

Closing it out

Completing a reconciliation is a checkpoint, and Claude names it and waits. Before you say yes, ask for the numbers: statement closing balance, cleared total, and the difference between them. They should agree. Once complete, the reconciled rows are locked — a reconciled transaction can’t be deleted without un-reconciling the period first. So don’t complete one casually. If something surfaces afterwards, the session can be undone. Ask Claude to undo it and it will name what that reopens before doing it.
Editing a reconciled transaction is recorded and surfaces on the Reconciliation Exceptions report. Nothing blocks the edit — the report is how you find out it happened. See Reports.

Doing a year at once

Catching up several months runs the same way, oldest first, one statement per session. Hand Claude the folder and say so: “Here are twelve monthly statements for Operating Checking. Reconcile them in order and stop at the first one that won’t foot.” Tell it to stop at the first failure. A month that won’t foot leaves an error every later month inherits, so working forward past it multiplies the cleanup instead of finding the cause. Ask for a work-log entry per month. When you come back to this in a quarter, the log tells you which months were clean and which ones you settled with a judgment call.

Where to go next