Bank statements, with every row in view.

01Choose statement fields

The statement template captures the account information and printed summary totals:

• Bank
• Account name
• Account number
• Currency
• From
• To
• Opening balance
• Closing balance
• Total money out
• Total money in

It also creates a Transactions list, with one row per transaction and these columns:

• Date
• Description
• Money out
• Money in
• Balance

Edit, remove or add fields to suit your task. To extract only an account number and closing balance, keep just those fields.

02Unify different bank layouts

Banks use different layouts and labels: Debit/Credit, Withdrawals/Lodgements, or one signed amount column. Describe what each value means rather than fixing its position, so the results can share a consistent set of columns.

If a bank uses an unfamiliar label, add it to the Money out or Money in instruction, then process the statement again.

03Handle longer statements

Files may contain up to 100 pages, with up to 50 files in one batch. Transactions across a document form one list in the printed order.

Expand the transaction list into individual Excel rows for sorting, filtering and reconciliation.

• The PDF your bank sends is the best copy. It is sharp on every page.
• A printed statement can be scanned or photographed one page at a time. The photo guide shows how.
• A screenshot from a bank app is read like any page, but a screenshot that cuts off part of the table can only give the part it shows.

04Review the reconciliations

Compare total debits and credits calculated from the extracted transactions with the statement’s printed summaries. Agreement is a useful check, though it cannot by itself prove every transaction is correct.

A difference is labelled Doesn’t match, with calculated and printed totals shown together. Source amounts are retained. Fields absent from the statement remain blank with the status Not on the page.

05Confirm before exporting

Statements may support lending, month-end reporting or client accounts, where one incorrect digit can matter. A person must review and confirm the file before its values are exported.

Edits keep the initial reading alongside the correction and mark the value Corrected. After confirmation, the reviewed rows can be exported to Excel, CSV or JSON.

06Handle statements carefully

Statements reveal account identifiers and personal spending. Limit access and retain them only for the purpose you need.

• Use the deployed HTTPS connection and review the Azure and hosting data-handling terms before uploading statements. This page does not promise a processing region, provider retention period or model-training policy.
• Give each person the smallest role they need. Viewers can read; Reviewers can upload, review, confirm and export. Admins and Owners manage broader workspace controls.
• Only upload statements you are allowed to handle: your own, or a client's who has agreed.
• Move a file to Trash when it should leave active work. Trash is reversible and retains originals and history; permanent erasure, account deletion and deletion receipts are not implemented.

07Check before uploading

1. Use the PDF from the bank when you have it, not a photo of the screen.
2. Keep every page of the statement in one file, in order.
3. Make sure the printed totals page is included, so the checks have something to compare with.
4. Upload only statements you are allowed to handle.