Statement of Account Methodology — Complete Guide
Tip: Chasing money that is already invoiced? Use our free Statement of Account to list the open invoices, deduct what has been paid, and send a clean PDF in seconds.
CalculatorAI's reference for statements of account that actually get paid: what belongs on one, how open-item and balance-forward formats differ, how ageing buckets work, and the sending rhythm that turns a statement into collected cash.
What a statement of account is (and what it isn't)
A statement of account is a periodic summary a supplier sends a customer showing the invoices raised, the payments received against them, and the balance still outstanding.
The distinction that matters: a statement never creates a new debt. Every figure on it has already been invoiced. That is exactly why it works — the customer cannot dispute the amount without disputing an invoice they already accepted, and the conversation moves from "how much do we owe you?" to "which of these four lines is holding things up?"
- Invoice — creates the obligation. One transaction, one document, entered into the ledger as a receivable.
- Statement of account — restates obligations already created. Nothing is entered into the ledger from it.
- Dunning letter / demand — a legal escalation with consequences attached. A statement is the friendly step before that, and sending statements consistently means you rarely need the escalation.
- Remittance advice — travels the other way, from the customer, saying which invoices a payment covers.
Because a statement is not a demand, it is also not a tax document. It does not need a tax number, and it should not restate tax as though it were being charged again.
The two formats, and which one to use
Open-item lists each unpaid invoice individually — number, date, amount, days outstanding — and shows the sum. This is the format for business-to-business trade, and it is the one to use in almost every case, because it points at specific documents the customer's accounts payable system can match against its own.
Balance-forward shows an opening balance, the period's charges and payments as a running list, and a closing balance. It suits high-volume consumer accounts where itemising every transaction would be unreadable. Its weakness in B2B is exactly the thing that makes a statement effective: nobody can act on "opening balance 14,200" without going and looking up what it consists of.
If in doubt, use open-item. A customer who can see the four invoice numbers can pay three of them today and query the fourth, instead of paying nothing while somebody investigates.
What belongs on the statement
- Both parties, with the accounts payable contact. A statement sent to a general company address will sit unread; sent to the person who runs the payment run, it goes into the next one.
- A statement date. "As at" is the whole meaning of the document, and without it the customer cannot tell whether last week's payment is reflected.
- One line per open invoice: the invoice number first, then its date, then a short description, then the amount. The number goes first because it is the field the customer will search on.
- Payments received during the period, so the customer can see their money was recognised. Nothing sours a relationship faster than being chased for an invoice you already settled.
- The balance outstanding, stated once, in a size that can be read at a glance.
- How to pay, repeated on the statement. Removing one step of friction removes one reason for delay.
- An invitation to query. A line saying which contact to reply to about a disputed item gets you an answer instead of silence.
Ageing buckets, and what they are for
Grouping the outstanding balance by how long it has been owed — current, 1–30, 31–60, 61–90, 90+ days — is standard practice, and it serves two audiences at once.
For the customer, seeing an amount sitting in the 90+ column is more persuasive than the same amount with no context. For you, the ageing profile is a forecast: the further right the weight sits, the lower the probability of collection, and the sooner the account needs a different conversation. A balance that keeps sliding one bucket to the right every month is not a slow payer, it is a bad debt forming.
Ageing is normally measured from the invoice due date rather than the invoice date, so terms are respected — a Net 60 invoice is not "30 days overdue" on day 31.
The sending rhythm
Statements work through consistency rather than force.
- Send monthly, on a fixed day, ideally a few days before the customer's payment run. Predictability trains the other side's process; an unpredictable statement is treated as an interruption.
- Send even when the balance is zero for active accounts. A statement that only ever appears when something is wrong reads as an accusation; one that always appears is just process.
- Do not restate disputed lines as though undisputed. Mark the line as in query. Ignoring an open dispute is how a customer justifies paying none of it.
- Escalate on the calendar, not on mood. Statement, reminder, phone call, formal demand — each at a set interval. Collections done on a schedule stay professional; collections done when frustration peaks do not.
Reconciliation: the other reason to send one
Beyond collections, a statement is the instrument both sides use to confirm their ledgers agree. At period end, the customer compares your open items against their own payables and reports differences — an invoice they never received, a credit note you never applied, a payment you did not allocate.
In some jurisdictions this exchange is formalised: a reconciliation document is signed by both sides and returned, and it can carry evidentiary weight in confirming what is owed. Even where it is informal, a customer who has agreed in writing that they owe four invoices has removed their own most convenient defence.
Digital signatures (Signature Canvas)
- Drawing a signature: enable "Show Signature" in the settings drawer on the right. A dashed placeholder appears beneath the notes area in the preview; click it (or "Draw Signature" in the sidebar) to sign with a mouse, trackpad or touch screen.
- Privacy-first storage: the signature is stored locally as a base64-encoded PNG inside the document draft itself. It is never uploaded to a public folder or a shared asset server.
- PDF rendering: once saved, it is rendered at the foot of the preview and embedded into all 5 PDF themes on download.