What these examples are
Two one-page chequing statements in CAD with selectable text, as you would download them from online banking. Every name, account number and transaction in them is made up, and every page is marked as synthetic. They are separate statements, not a before-and-after pair.
Example 1: a complete statement
- Transactions read
- 18
- Result
- Converted
Every transaction is read and the balances add up, so the statement is ready to export. Compare the rows with the PDF before you rely on them: matching balances alone do not prove every date and description.
Example 2: a transaction is missing
- Transactions read
- 17
- Result
- Flagged for review
One transaction was removed from this statement, so its balances no longer add up. Statement2Sheet does not invent a replacement: it marks the statement for review so you can check it against the PDF.
Try it yourself
- Download either PDF above.
- Upload it and open the review screen.
- Compare the rows with the PDF. For the second example, the statement stays flagged until you resolve the missing transaction.
Building an integration? Start with the API quickstart.
What to check before using the output
A matching closing balance does not rule out offsetting missing transactions, wrong dates or wrong descriptions. Follow the row-by-row review checklist and choose the export using the CSV, OFX and QBO comparison.