Overview
Sample bank statement verification report
Illustrative structure of a GrassLedger output package—summary fields, transaction preview, reconciliation stance, review flags, and limitations. For a full static walkthrough with tables, use the longer sample report.
Extracted statement summary
Key fields taken from the statement header and summary bands (period, balances, rolled totals).
A case bundle includes normalized summary fields with source references (e.g., statement header vs. summary band). When the parser cannot tie a field to a clear printed line, the field may be absent or flagged for review—not silently guessed.
Transaction extraction preview
Ledger rows with section assignment and review hints.
Transactions are listed with dates, descriptions, amounts, and section labels where the layout supports it. Rows that need analyst attention receive review signals instead of being presented as high confidence without context.
Reconciliation result
Whether printed summary math lines up within stated tolerances and parser evidence.
Reconciliation compares extracted totals and roll-forward logic to the statement’s printed controls. A PASS means the checked relationship held for this run; a REVIEW or FAIL means human review is appropriate before relying on exports.
Review flags
Structured reasons for analyst attention—separate from authenticity or fraud claims.
Flags describe extraction coverage, section consistency, and arithmetic tension. They do not assert fraud, authenticity, or lending suitability.
Document limitations
OCR, missing sections, and policy boundaries surfaced explicitly.
Limitation codes explain what was not verified (for example, ledger availability, certain metadata, or aggressive OCR). Customers see these in the report narrative so teams know what the system did not attempt to prove.
CSV export preview
Machine-readable transaction export for spreadsheets—not a generic PDF-to-grid conversion.
Pilot exports include a transactions CSV aligned to the same rows and review metadata shown in the report. Column sets depend on statement type and validated layout—not every institution exports identical shapes.
Sample review package
Illustrative reconciliation checks, extracted summary fields, and a transactions preview—structured for analyst review, not a live customer upload.
The full sample report page shows a richer, static HTML-style walkthrough with synthetic numbers for training and workflow discussions.
Scope reminder
This overview page does not include live customer data, logos, testimonials, or institution-specific marketing claims. It only explains what categories appear in a verification package.
Want outputs on your workflow?
Founder-led pilots include real files under agreed scope—not open public self-serve for every format.