Read the opening and closing balance, amount due, transactions, aging buckets, and open invoice lines from a customer statement of account PDF. No signup.
The full guide: Statement of account, opening to closing balance
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
A customer statement is the statement of account a supplier sends a customer summarizing activity over a period — opening balance, charges, payments, and closing balance across many invoices — rather than a single invoice or an internal aging report. The extractor reads the buyer name, account number, and address, the supplier name and address, and the period start and end dates.
The opening balance, closing balance, total charges, total payments, total adjustments, and the amount due at the statement date, plus the due date, payment terms (Net 30, Due on receipt), currency (ISO 4217), and the statement type (regular, final, corrective, duplicate).
Yes. A transactions table gives each entry's ID, date, type, reference, description, debit and credit amounts, and running balance; an invoice lines table lists each open invoice's number, date, description, quantity, unit price, amount, amount paid, and amount due.
An aging detail table returns each bucket (current, 30+, 60+, 90+ days) with its day range, amount, and percentage of the balance, and a text aging summary field carries the overall aging narrative when the statement prints one.
One PDF up to 10MB and 100 pages. Processed via the Talonic API for extraction only, not retained for training, and not shared. Export as CSV, XLSX, or JSON.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See invoice data extraction if you run this for finance and AP teams, or the extraction API if you are building it in.