Step by step
- 01
Check the statement period
Confirm that the drafted rows cover the dates and pages expected from the source statement.
- 02
Inspect amounts and signs
Compare credits, debits, decimal places, and negative signs with the highlighted source evidence.
- 03
Read descriptions in context
Look for wrapped descriptions, reference numbers, and adjacent lines that may need a split or merge.
- 04
Reconcile balances
Use opening, running, and closing balances where present to catch missing or duplicated rows.
- 05
Approve only after corrections
Approval fixes the exact revision used by exports and API results.
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.
Fulla includes reconciliation in its deterministic confidence calculation. An exact 0.80 stops the promoted chain; lower results advance or remain in review. The final decision still belongs to the reviewer.
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?
API results use the same approved persisted revision as CSV, XLSX, and JSON exports.
