01
What creates what is a billing statement??
A billing statement is prepared at a chosen cut-off, often month end, or when a customer asks where the account stands. It draws on documents that already exist: issued invoices, credit and debit notes and verified payments within the period, plus the balance carried forward from the previous statement.
Start with the underlying commercial or statutory event rather than the label placed on a document or report. Record the parties, date, period, amount basis, source and responsible owner so another reviewer can reproduce why the state exists.
- Name the event and effective date.
- Retain the source and calculation.
- Identify the accountable owner.
- Keep later changes traceable.
Put this into practice with what is an invoice.
02
How the working method fits together
Start from the closing balance of the last statement, add invoices and debit notes issued in the period, subtract credit notes and verified payments, and show the result as the closing balance with each line traceable to its source document. Many statements also age the open amount by due date so the customer can see what is overdue. In Invoicera, customers can see their account statement history in the client portal.
Work from source evidence to classification, calculation, review and final record in that order. A familiar label or precise number does not correct a missing source, wrong period, unsupported assumption or unauthorised change.
- Collect the source records.
- Confirm scope and classification.
- Calculate with visible assumptions.
- Review and retain the result.
Put this into practice with what is accounts receivable.
03
What to keep distinct
Keep the billing statement separate from the invoice, the payment receipt and the ledger. An invoice requests payment for a specific supply; a receipt confirms money received; a statement summarises both for a period. A statement that disagrees with the customer's records is a prompt to reconcile individual documents, not a new demand.
Related records can share amounts while proving different things. State whether a value represents an authorised order, delivered work, outgoing invoice, customer balance, payment instruction, verified cash event, tax report or ledger conclusion before using it in another process.
- Intent is not delivery.
- An invoice is not cash.
- A payment notice is not settlement.
- Billing evidence is not a ledger conclusion.
Put this into practice with accounts receivable aging report.
04
Worked example
The example demonstrates the sequence and arithmetic, not a universal legal, tax or accounting treatment. Replace every assumption with the facts and current rules that apply to the actual transaction.
A reviewer should be able to move from the final number back to each source record without reconstructing the decision from email or memory.
- Opening balance on 1 September: $4,200
- Invoices issued in September: $6,500
- Credit note for a returned item: $300
- Payments received and matched: $5,000
- Closing balance on 30 September: $5,400, of which $1,200 is more than 30 days overdue
Put this into practice with payment reminders.
05
Review before relying on the result
Check the parties, direction, relevant period, source completeness, classification, currency, arithmetic, status and approval. Where a law, filing or accounting policy controls the outcome, use the current official source or the responsible qualified reviewer.
Correct the record through the appropriate controlled process. Do not silently overwrite an issued document, change a historical status without explanation or present an illustrative value as though it were verified evidence.
- Treating the statement as a new invoice
- Leaving out credit notes or unmatched payments
- Changing the cut-off date between statements
- Showing a balance that cannot be traced to documents
- Sending a statement while a disputed line is unresolved without saying so
Put this into practice with customer portal.
Continue in context
