The sample checker explicitly reports No records were saved. It validates the fictional sample’s rows and balances for inspection, so you should not expect those rows to appear in Transactions afterward.
Uploading a sample statement is a separate action. That path uses the statement processing workflow and can create unposted review records in the selected company.
Choose the right exercise
- Use Preview sample checks when you only want to see expected source fields and arithmetic.
- Use the sample download links to inspect the PDF and CSV locally if helpful.
- If you deliberately upload a sample to practice category review, keep its fictional status and test context clear before proceeding.
Do not repeat the nonmutating sample check in an attempt to make transaction rows appear. The absence of saved records is the intended result.
For a real statement, start from Upload statement or its existing document entry and follow Extract transactions. Confirm the selected company and account first. Treat any sample balances, merchants and amounts as demonstration data, and keep them out of reports used to represent the company’s actual financial position.
Was this article helpful?
Tell us whether this answered the question you came with.