The operating problem
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.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map 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.
2. Extract locally
Use an approved OCR/parser endpoint. Disable unneeded outbound traffic and confirm where temporary files, telemetry, and backups go.
3. Validate arithmetic
Normalize dates, currency, decimal separators, and debit/credit signs. Compare extracted totals to the statement rather than trusting a confidence score.
4. Review exceptions
Show source page, extracted value, and validation failure together. A reviewer resolves unreadable rows and matches the client and account.
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.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| 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 |
Acceptance checks
- 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.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.