Quick start.

1. Install

Go to centproof.com/download and click Download CentProof.dmg. The file is ~80 MB; the download takes 20-60 seconds on most connections.

Open the .dmg, drag the CentProof icon to the Applications folder, then eject the disk image. Launch CentProof from Applications (or Spotlight: ⌘ Space → CentProof).

The first launch shows macOS's standard Gatekeeper confirmation because the app is from outside the App Store — click Open. CentProof is signed with Apple's Developer ID and notarized by Apple, so this is a one-time prompt, not a security warning. If you want to verify the signature yourself before opening, the Security page shows you three short Terminal commands.

2. Get a statement

CentProof reads PDF statements that you download from your bank's online portal — there's no aggregator, no bank-password login, no Plaid. Anything you can already download from your bank works.

Sign in to your bank or credit-card portal, find the Statements & Documentssection (or similar), and download one month's PDF. Save it anywhere you can find — Downloads is fine. For a complete first try, pick a recent month that has both deposits and withdrawals so you see the full picture.

3. Drop it into CentProof

Two ways:

• Drag and drop. Drag the PDF from Finder onto the CentProof window. Anywhere on the window works.
• Add Statement button. Click the Add Statement button (top-left) or press ⌘ N and pick the file from the standard Mac file picker.

CentProof reads the PDF's text, identifies which bank it's from, extracts every transaction, and runs the math against the opening and closing balance the statement prints. All of this happens locally on your Mac in a few seconds — no upload, no network call, no aggregator involved.

If your bank isn't supported yet (CentProof launched with nine major US banks; more are added in maintenance releases), you'll see a dialog with three choices: cancel, try a generic best-effort extraction, or send us a redacted sample so we can add a verified parser. See Importing statements for the full walkthrough.

4. Review the import

After parsing, CentProof opens the Review screen. The left half shows the original PDF; the right half shows what CentProof extracted:

• Account Summary panel— opening balance, closing balance, and a line-by-line breakdown that mirrors the statement's own summary block (e.g. for Chase Total Checking: Deposits and Additions, ATM & Debit Card Withdrawals, etc.).
• Transactions table — every row CentProof extracted, with date, description, amount, and direction (debit/credit).
• Reconciliation status — green ✓ if the math works to the cent, red ✗ otherwise.

The big green ✓ is the key signal. It means: opening balance + credits − debits = closing balance, exactly. If you see it, the data CentProof extracted matches what your bank printed. You can trust the rest.

If you see a red ✗ instead, the math is off — usually because the parser missed a row or grabbed an extra one. See Reviewing and reconciling for what to do.

5. Commit

Click Commit at the bottom of the Review screen. CentProof saves the statement and its transactions to a local SQLite database (in ~/Library/Application Support/com.javamantra.pdfapp/), encrypts a copy of the PDF for offline reference, and takes you to the Transactions tab.

That's the loop. The next month's statement follows the same five steps — except by then, CentProof has learned your merchants and most rows auto-categorize.

What to do next

Once you have a few statements imported, the most valuable next move is to tag a few transactions so future imports auto-categorize them. See Tagging entities and categories.

Then try Ask CentProof with a plain-English question about your spending. The answer comes back with source rows, all computed locally on your Mac — no cloud calls.