Keep the result and the source together
Start with the contained result workspace and the original statement available for comparison. A needs-review result intentionally keeps any available transaction rows visible while presenting the reconciliation findings beside them.
Avoid treating the CSV as independent evidence. The source-page reference on each row is there to make a focused comparison possible when a date, amount, description, or printed balance needs confirmation.
Read the finding before scanning every row
The finding code and account summary narrow the review. Coverage findings point toward page or account completeness, while an account balance finding points toward the transaction sequence and printed checkpoints.
Beginning with that distinction is faster than visually rechecking the entire statement. It also reduces the chance of correcting a row when the actual problem is missing evidence elsewhere in the document.
Use balances as checkpoints
Compare the beginning balance, transaction amounts, any printed running balances, and the ending balance in order. The first affected row is the most useful place to begin when the result identifies one.
If a printed checkpoint and the normalized amount disagree, return to the cited source page before editing downstream bookkeeping data. The statement remains the authority for the financial record.
Keep the poll result with the export
The job poll's report.status remains the authority for the overall result. The CSV does not include that result-wide status; each transaction row carries only its account's reconciliation status.
The current route does not run the statement again. When coverage or balance checks fail, compare the retained rows and findings with the source before using the data in downstream bookkeeping.