Review / tutorial
How to review extracted bank transactions
Use the source page, row evidence, balance sequence, and page coverage together before approving a statement export.
Watch it done
How to review bank transactions beside their source
A worked example
A correction with evidence
Fictional example · a debit sign correction
Coffee shop
03 March 2026
Debit 4.50- Draft signed amount
+4.50- Source-supported correction
- −4.50
- Before conversion export
- Review and approve the saved revision
Step by step.
Check the statement period
Confirm that the drafted rows cover the dates and pages expected from the source statement.
Inspect amounts and signs
Compare credits, debits, decimal places, and negative signs with the highlighted source evidence.
Read descriptions in context
Look for wrapped descriptions, reference numbers, and adjacent lines that may need a split or merge.
Reconcile balances
Use opening, running, and closing balances where present to catch missing or duplicated rows.
Approve only after corrections
Approval fixes the exact revision used by conversion exports.
Begin with coverage
A review can look complete while missing a page or a block of transactions. Compare the statement period, page count, and visible transaction range before correcting individual cells.
- Expected first and last transaction dates
- Every page that contains transaction rows
- Opening and closing balance sections when present
Check the fields that change the result
Dates, amount signs, and decimal placement affect sorting and totals. Descriptions often wrap across source lines, so a row may need a merge or a split even when every word was recognized.
Select a row to keep its evidence box in view. Use correction, split, merge, and undo rather than editing without a source reference.
Use reconciliation as a second check
When the statement provides balances, verify that the transaction sequence explains the movement from opening to closing balance. This can expose a duplicated row, a missing row, or the wrong debit and credit sign.
Balance checks help identify potential issues. Compare the draft with the source before approval; a matching total does not prove every row is correct.
Questions about this guide
Can I undo a row correction?
Yes. The review workflow supports undo as well as correction, split, and merge actions.
What if a scanned page needs another extraction pass?
Manual inspection and re-extraction use the same provider policy and do not consume a second page.
Which revision does the API return?
CSV, XLSX and JSON conversion exports use the approved persisted revision. The result endpoint returns the latest saved review revision and does not establish approval.