Document guide
Account or card statement
Turn account and card transactions into tables your team can filter and cross-check. Retain dates, descriptions, debits, credits and balances without retyping every line.
Explore fields and examples ↓The information your team needs.
Transactions, dates, amounts and stated balances. Each value retains its document reference so the team can return to the source during review.
Illustrative fields · Fictional data. Fields and output are configured for the supplied documents and agreed workflow.
| Field | What it contains | Example |
|---|---|---|
| Account and holder | Account or card reference and stated holder. | Account ending 0042 |
| Period | Statement start and end dates. | 1–30 Sep 2026 |
| Transaction dates | Transaction and value dates, kept separate. | Transaction: 15 Sep · value: 16 Sep |
| Description | Transaction text and available reference. | Instalment payment · OP-0042 |
| Debits and credits | Amount, sign and currency of each transaction. | Credit: €150.00 |
| Balances | Stated opening, closing and running balances. | Closing balance: €3,200.00 |
Connect the data. Find what needs attention.
Identify incomplete periods and possible duplicate transactions in overlapping statements.
Cross-check balances against certificates and the datatape using the same date, currency and included components.
An unreadable transaction is flagged for review. Missing periods are not filled with assumed transactions.
Information ready for your workflow.
A transaction table linked to the account, period and document. Receive an Excel or CSV file for review, or structured data in the format agreed for your system.
Use it in these solutions
Try it with a batch of your documents. We agree the sample, fields and confidentiality before starting.
Discuss my batch →