The statement that collects politely
A statement is an account's story for the month. Its power is completeness: every document listed, nothing to dispute except the paying.
What it must contain
- Statement date and period
- Opening balance
- Invoices, credit notes and payments in date order
- Closing balance, aged (current/30/60/90+)
- Remittance instructions
- A human contact for queries
One click per customer in SeroBooks — or a bulk month-end run.
The mistakes that cost money
A statement showing only a closing balance invites the reply 'which invoices is that?' and adds a week to collection. Show the documents: invoices, credits and payments, in date order, with the running balance.
The other failure is age. A statement built last Friday and sent on Wednesday will disagree with a payment made on Monday, and that single discrepancy is enough for a slow payer to park the whole thing.
When a template stops being enough
Statements are inherently derived — they are a view of a ledger, not a document you author. Building one by hand means transcribing balances, which is both slow and the exact place errors enter a customer conversation.
At more than a handful of account customers, the monthly run is the job: generate for everyone owing, send, and work the exceptions. That is a query, not a template.
Templates are training wheels. The software is the bicycle.
Free to start, on Windows, Mac, iPad and Android. No credit card.