Statement Matching and Reconciliation

I want to set up the Statement Matching Pack and reconcile my first real statement against my ledger before the close. Walk me through it step by step, one question at a time, and wait for my answer before moving on. I am a CFO, controller, or fund accountant, not a developer. Define every term once. Keep me to one action per message.

## What this produces
A statement matched to my ledger in seconds, with only the breaks coming back for me to review: duplicates, timing differences, missing wires, amount mismatches, each with a reason. The extraction runs offline on my own machine, so the statements never leave the building. A footing proof at the end shows the reconciliation actually ties before anything books.

## Step one, ask me this first, nothing else
"Is the statement you want to match a clean digital export (CSV or native PDF), or a scanned or photographed PDF? Either works. I just need to know whether we turn on the offline reader for scans."

Wait for my answer. Then continue, one step per message:

## The path you walk me down
- Classify my setup as CLI plus chat (we install the offline reader once, then everything else is in Claude). Tell me the one command to install it, where to paste it, and what success looks like.
- Have me extract one statement with a single command, then check the extracted closing total against the printed total on the statement before we go further. Stop me if it does not match and help me fix the extraction.
- Walk me through creating a Claude Project named "Recon Desk" and pasting the house rules (match on amount, date, reference; never invent a transaction; never mark a break resolved on your own; mask account numbers to last four; list everything that does not match and why).
- Have me load the two inputs: the extracted statement rows and my ledger export.
- Run the first match with me on a small set, then read the break list together so I trust it before I run the full statement.
- Set my tolerances (how many days counts as a timing difference, how many cents counts as a near match) from what my own data shows, not a guess.
- Finish with the footing proof: opening plus matched activity plus or minus breaks equals closing. If it does not foot, name the exact gap.

## The first session drill
By the end of this session I should have: one real statement extracted offline, matched against my ledger, a break report with every account number masked to last four, and a footing proof that ties. Then show me the one line command and the prompt order so next month's close is a checklist, not a rebuild.

Before you tell me the reconciliation is done, re derive the matched total and the break total, confirm matched plus unmatched equals the total on both sides, and confirm it foots. Do not say it is ready until that check is clean. I review every break and sign the reconciliation myself.