Why convert a statement of account to a spreadsheet
A statement of account lists everything outstanding between two parties — invoices, credits and payments with a running balance — but as a PDF it's a fixed page you can't reconcile. When a supplier sends a month-end statement, someone has to check it line by line against the purchase ledger, and in a PDF that means re-keying every document number and amount before the comparison can even start.
Converting the statement to a spreadsheet turns that list into live data: one row per item, the charge, payment and running balance captured, ready to match against your ledger. Whether you're in accounts payable reconciling a supplier statement, in accounts receivable chasing what's owed, or preparing an aged view, the spreadsheet is what the next step needs — and a converter gets you there in seconds.
Because FlowParse is a universal financial-document extractor, statements of account are squarely in scope: it reads the header and the transaction table by meaning, keeps every line, and produces a faithful copy you can reconcile and age.
What a statement of account contains
A statement of account pairs an account header with a dated list of everything that has moved the balance. FlowParse reads both, so the whole statement becomes structured data you can reconcile against your own records.
| Field | Where it sits | Why it matters |
|---|---|---|
| Account holder / supplier | Header | Whose account the statement is for |
| Statement date & period | Header | The point the balance is struck at |
| Opening / closing balance | Header / footer | The control figures for reconciliation |
| Document number | Line | Invoice, credit note or payment reference |
| Charge / payment | Line | What increased or reduced the balance |
| Running balance / age | Line / footer | The amount outstanding and how old it is |
What FlowParse extracts from a statement
Every statement of account is a header plus a dated list of items, and FlowParse pulls each into structured form. The account holder, statement date, opening and closing balance and currency come across as header fields; every line becomes its own row with date, document number and type, the charge or payment, and the running balance.
The order of items is preserved, an ageing summary (current, 30, 60, 90 days) is captured where present, and extra columns — a reference, a due date — are kept. The result is a spreadsheet that mirrors the statement, which is what lets you reconcile and age it without rebuilding the list by hand.
How to convert a statement of account to Excel
Upload the statement PDF
Drop the statement of account into the converter. A supplier email attachment or a scan works too — it runs through OCR first.
Let the AI read it
The account header, every document line and the running balance are detected by meaning, not by a fixed template, so any statement format converts without setup.
Review the editable preview
Check the figures in the editable preview; the movements are checked against opening and closing balances and low-confidence values are flagged.
Reconciling a supplier statement
The reason a statement of account is worth converting is to reconcile it — to prove that what the supplier says you owe matches what your ledger says. Done from a PDF, that's a line-by-line hunt: read a document number, find it in the purchase ledger, tick it off, and chase the ones that don't match. On a busy account it's slow and easy to get wrong.
With the statement as structured rows, reconciliation becomes a match. Line the document numbers up against your ledger, and the exceptions fall out immediately: an invoice on the statement you haven't received, a credit you're missing, a payment they haven't applied, a mismatched amount. The opening and closing balances give you control totals, so you know when the account fully ties out rather than hoping it does.
The same works for a customer statement you've issued — confirm what a customer has been sent and paid, and identify exactly what's still open, without reading down a page.
Ageing outstanding items and collections
A statement of account is also the basis for chasing what's overdue, and that needs the items aged. Once the lines are structured — each with a date and an amount — bucketing them into current, 30, 60 and 90 days is a formula, so the overdue balance and the worst offenders are visible at a glance instead of buried in a printed list.
That turns a statement into a collections tool: sort by age, total the overdue amount, and prioritise the calls. For payables, the same view shows which supplier invoices are due when, so payment runs are planned against real dates rather than a rough read of a PDF.
Any format — supplier statements to customer statements
Statements of account arrive in every shape: a supplier's month-end statement from their ERP, a customer statement you've issued, a portal download, a scanned copy. A template-based tool breaks the moment the layout shifts; FlowParse reads by meaning, locating the account header and the transaction table wherever they sit, so all of these convert the same way.
That matters because supplier statements come from your suppliers, not from you — you don't control the format, and every one looks different. Reading by meaning means a statement you've never seen converts as cleanly as a familiar one, with no configuration.
Scanned and image-based statements
Plenty of statements arrive as scans — a posted statement scanned into the inbox, a printout photographed, an image forwarded through several people. The OCR stage handles those: it converts the image to text, coping with skew and moderate quality, and the AI then structures the recognised text into the same header and transaction lines.
Where a read is uncertain — a faint document number, a cramped column — the field is flagged with a low confidence score rather than guessed, so you verify just those values. Digital PDFs convert fastest, but a scanned statement is no barrier to reconciling it.
Why the balance reconciles
A statement of account has a built-in control: the opening balance plus the charges less the payments equals the closing balance. FlowParse uses that to check itself — after extraction it confirms the movements tie the opening balance to the closing balance, so a misread amount or a dropped line is flagged in review rather than quietly breaking your reconciliation.
Everything is reviewable and editable before export, with per-field confidence scores on anything uncertain. FlowParse reaches around 98% field-level accuracy on standard statements, and because you confirm the figures in the editable preview, what lands in Excel matches the statement — which matters when the numbers drive a payment or a chase.
Who converts statements of account
Accounts payable teams convert supplier statements to reconcile them against the purchase ledger, catching missing invoices and unapplied credits before they become disputes. Accounts receivable teams and credit controllers convert customer statements to see exactly what's outstanding and age it for collections. Finance teams convert them at period end to confirm creditor and debtor balances.
Bookkeepers reconciling client accounts convert the statements their clients receive, and anyone taking on a new supplier or customer relationship converts the opening statement to start from a clean position. In each case the structured statement is what the task needs, and converting the PDF removes the retyping.
Tying statements to invoices and payments
A statement of account references invoices and payments, and the full picture comes from tying it to those documents. Convert the statement to get the outstanding list, convert the invoices to get the line-level detail, and the remittance advice to see what a payment settled — and the document numbers connect them.
With all three as structured data, a query that used to mean shuffling papers — which invoices make up this balance, was this payment applied, why doesn't the statement agree — becomes a lookup. Converting the statement is the entry point to reconciling the whole account cleanly.
Convert many statements at once
One statement is quick; a supplier-statement run at month end is a stack. When dozens of statements arrive to be reconciled in a few days, the volume is the problem, and an unreconciled statement is a risk of duplicate payment or missed credit. Smart Merge takes up to 100 statement PDFs and consolidates them into one structured workbook, each row tagged by source so any line traces back to its statement.
That turns a pile of separate statements into a single dataset you can sort, total and match in one pass — the difference between days of manual ticking and a few minutes of upload-and-review. Duplicate detection means a re-sent statement doesn't get processed twice.
Automate statement extraction
For steady volume, the same conversion runs over the document extraction API: post a statement PDF and receive structured JSON — the account header and an array of transaction lines — per page, billed per page, with the balance reconciliation built in. That turns statement intake into a pipeline step, so a supplier statement can be reconciled the moment it lands in a shared inbox.
Because the output is clean JSON, it feeds an AP automation, a reconciliation engine or a data warehouse directly. The parsing guide covers the pattern, and the same engine reads the invoices and remittances the statement references.
{
"account": "Meridian Supplies Ltd",
"statement_date": "2026-06-30",
"opening_balance": 1200.00,
"lines": [
{ "date": "2026-06-05", "document": "INV-3310", "type": "invoice", "charge": 644.40, "payment": 0, "balance": 1844.40 },
{ "date": "2026-06-22", "document": "PAY-8801", "type": "payment", "charge": 0, "payment": 1200.00, "balance": 644.40 }
],
"closing_balance": 644.40
}To Excel, CSV or structured JSON
The same extraction powers every export. Take the data to Excel for reconciliation and ageing, to CSV for importing into your accounting system, or as structured JSON over the API when a workflow needs to ingest it automatically.
Because the account header and transaction lines come out labelled and aligned, they map cleanly into whatever you're feeding next, with no rebuilding of the layout. One conversion, every downstream format — and the statement's structure intact in all of them.
Disputes, queries and unallocated items
The items on a statement of account that matter most are the ones in dispute — an invoice you're querying, a credit you're owed but can't see, a payment the supplier hasn't applied, a charge you don't recognise. Those are the lines that hold up a payment run or a collection, and picking them out of a printed statement means reading every row against your records.
With the statement as structured data, the disputed and unmatched items separate cleanly from the settled ones. Match what you can against the ledger, and what's left is your query list — the exact items to raise with the counterparty, totalled and dated. That turns a vague 'the account doesn't agree' into a specific, evidenced set of exceptions, which is what actually gets a dispute resolved.
Brought-forward balances and the opening position
A statement of account opens with a brought-forward balance — everything outstanding before the current period — and that opening figure is the anchor the whole reconciliation hangs on. If it's misread or the prior items behind it are unclear, nothing after it ties out, which is why capturing the opening balance correctly is as important as the transaction lines.
FlowParse captures the opening and closing balances as control figures and confirms the movements tie one to the other, so the brought-forward position is validated rather than assumed. When you take on a new supplier or customer relationship, converting the first statement gives you a clean, checked opening position to start from — the foundation every later reconciliation builds on.
Your account data stays private
Statements of account carry supplier, customer and balance detail, so they're handled accordingly. Uploads run over TLS, processing happens on EU-hosted infrastructure, the original PDF is deleted immediately after processing, and your documents are never used to train AI models.
You review and edit the data in the browser before anything is exported, and download only the spreadsheet you need. Nothing about the statement is retained once the conversion is done.
Convert your statements of account in seconds
Upload a statement PDF and get a clean, structured spreadsheet — every invoice, credit and payment with the running balance intact, ready to reconcile and age.