Your copy. Your pace.

Bank statement & receipt parsing

Extract candidate transaction rows from statements, reconcile totals, and send uncertain records to an accountant before any ledger write. A local parser can reduce data movement, but storage, backups, logs, model calls, and network egress still need review. The accounting system remains the final record of approved entries.

Planning workbook. This file helps you document a process. It does not connect to accounts, read records, send messages, or complete external actions. It works offline and sends no entries anywhere. Entries are not saved automatically; export or print a copy before closing. Avoid entering sensitive information.

1. Define the starting point

A parser that reads a minus sign incorrectly can produce a plausible but wrong ledger. Treat extraction as a proposal: preserve document provenance and reconcile opening balance, movements, and closing balance before approving a batch.

Process owner and backup rolesWhat will count as complete?

Current handling time and exceptions

2. Walk through the process

1. Quarantine the upload

Accept an allowlisted file type and size. Scan uploads, isolate the processing worker, and assign a document checksum before parsing.

We have defined the owner, required information, and completion check for this step.Step 1 working notes

2. Extract locally

Use an approved OCR/parser endpoint. Disable unneeded outbound traffic and confirm where temporary files, telemetry, and backups go.

We have defined the owner, required information, and completion check for this step.Step 2 working notes

3. Validate arithmetic

Normalize dates, currency, decimal separators, and debit/credit signs. Compare extracted totals to the statement rather than trusting a confidence score.

We have defined the owner, required information, and completion check for this step.Step 3 working notes

4. Review exceptions

Show source page, extracted value, and validation failure together. A reviewer resolves unreadable rows and matches the client and account.

We have defined the owner, required information, and completion check for this step.Step 4 working notes

5. Post an approved batch

Use a stable batch key to prevent duplicate imports. Reconcile accepted rows against the destination and preserve a restricted approval record.

We have defined the owner, required information, and completion check for this step.Step 5 working notes

3. Check the information

Use invented references in this worksheet. Keep real documents and personal records in an appropriate private system.

Reference field	Working record	Check
document_sha256	source_key	Deduplicate the same file
statement_account_ref	account_mapping	Staff-approved destination account
transaction_date	TxnDate	Normalize timezone and locale
amount_signed	amount	Validate debit/credit convention
source_page	review_reference	Keep provenance outside public logs

Source of truth and access boundaries

4. Verify the process

Use synthetic examples. Mark a check only after recording what actually happened.

An unreadable amount blocks the batch.A repeated file produces no duplicate draft entries.A statement with an incorrect ending balance enters review.A missing destination account prevents posting.A named person can resolve an unclear or incorrect result.Work stops when the task is complete, withdrawn, or outside the agreed scope.A duplicate or interrupted handoff can be recovered without repeating a consequential action.Expected result, observed result, and recovery notes

5. Decide the next step

Your smallest reversible pilotReview date and decision

Retain qualified professional review for legal, accounting, tax, medical, financial, or other consequential decisions. This workbook does not certify compliance or guarantee results.