Internal controls: the ones that work are the ones that leave evidence
A control that happens but leaves no trace cannot be relied on by anyone outside the room. Designing for evidence is what separates a control from a habit.
A statement of account shows the whole relationship, not one invoice. Sent on a schedule, it resolves most payment queries before anyone has to make a call.
A statement of account is a periodic summary a supplier sends a customer listing everything outstanding: invoices issued, credit notes applied, payments received, and the balance remaining. Unlike an invoice, it demands nothing new — it simply shows both parties the same picture of where the account stands.
That shared picture is what makes it effective. Most late payments are not refusals; they are invoices that never reached the right inbox, were logged against the wrong entity, or are sitting in an approval queue nobody is watching. A statement surfaces all three without anyone having to accuse anyone of anything.
Two formats exist and they are not interchangeable. An open-item statement lists unpaid invoices only, and is what most business customers want. A balance-forward statement shows a brought-forward figure plus the period’s activity, which is common in retail and consumer accounts but nearly useless to a payables clerk trying to match a payment run.
Statements work because they are routine. A statement that only appears when the supplier is worried reads as pressure, and the customer treats it as the opening move in a dispute. A statement that arrives on the same day every month is administrative furniture — the payables team files it, reconciles against it, and asks about anything missing.
A statement is not a demand for payment and should not read like one. Its power comes from being neutral: here is what we show, tell us what you show. Adding threatening language to a routine statement converts a reconciliation tool into a dispute and usually delays the payment it was meant to accelerate.
The valuable part of statementing is the reply. Customers respond with the invoices they do not have, the ones they show as paid, and the ones they are disputing. Each reply is a specific, fixable problem, and dealing with them monthly stops an account from quietly ageing into a write-off.
Where the ledger already holds every invoice, payment and credit note, producing statements is a scheduling decision rather than a project. Ettex Books issues the statement straight from the customer ledger, so what the customer receives and what the account shows are the same thing, and credit control works from the replies rather than from a spreadsheet rebuilt each month.
An invoice bills for one transaction and creates the obligation to pay. A statement summarises the whole account and creates no new obligation — it reports what is already outstanding.
Monthly is standard. Weekly can be justified for high-volume accounts, but sending more often than the customer’s payment run is usually noise.
They can decline to pay against a statement alone, and many payables systems require the underlying invoice. That is normal: the statement identifies what is missing, and the invoice is then resent.
One that lists individual unpaid invoices rather than a rolled-forward balance. It is the format business customers can actually reconcile against their own ledger.
A control that happens but leaves no trace cannot be relied on by anyone outside the room. Designing for evidence is what separates a control from a habit.
A payment without a remittance advice leaves the supplier guessing which invoices it covers. That guess becomes your chase email three weeks later.
The bank flags items that do not match your issue file. If nobody decides by the cut-off, the default in your agreement decides for you.