The Statement and the Document It Omits
The customer statement is real, it runs over any date range, it carries a running balance, it renders as a PDF and it emails without duplicating itself on a retry. It is built from invoices and payments. A credit note is neither, so it does not appear — and the balance at the bottom is higher than what the customer owes.
A statement of account is the one document your customer will read line by line, because it is the one that says how much they owe you. Everything else you send them, they check. This one, they audit.
What the statement is
An opening balance, a set of dated rows each carrying a type, a reference, a description, a debit or a credit and a running balance, and a closing figure. It can be run over any date range or over everything. Each row carries its own currency, which matters if you have invoiced the same customer in more than one.
It renders as a PDF, stores under the customer, and can be emailed. The emailing is idempotent — a retry does not send a second copy — which is the sort of detail that only gets built by somebody who has watched a connection drop halfway through a send.
Cancelled invoices are excluded. That is correct and it is worth confirming rather than assuming, because a statement that lists cancelled documents is a statement your customer will phone about.
Two sources: invoices and payments. Everything on the statement is one of those, which is also the problem.
The document that is neither
A credit note is not an invoice and it is not a payment. It is a third thing, and the statement has no row type for it.
So when you issue a credit and apply it, the invoice's balance goes down — correctly — and the statement carries on as though nothing happened. The invoice still appears at its full value as a debit. No credit row appears against it. The running balance, and therefore the closing balance, is higher than what the customer actually owes, by the total of every credit you have applied in the period.
The direction matters. You are asking a customer for more than they owe, in writing, on the one document they read carefully. They will notice, and the conversation that follows is not about the software.
| On the statement | Effect on the running balance | Correct? |
|---|---|---|
| An invoice | Increases it | Yes |
| A payment | Reduces it | Yes |
| A cancelled invoice | Excluded entirely | Yes |
| A credit note | Does not appear | No — the balance stays high |
| An invoice settled by a credit | Appears at full value as a debit | No — it reads as outstanding |
This is the mirror image of something we have published separately. Applying a credit note increases the invoice's amount-paid figure, which overstates collections — see A Credit That Reads as Cash. Here the same act understates nothing and overstates the balance. One root cause, two documents, errors in opposite directions.
Why this is worse where the statement is the collection process
In a market where collection happens by relationship and by document rather than by direct debit or automated reminder, the statement is not a summary. It is the ask.
A Sierra Leonean business chasing receivables sends a statement, and the statement starts the conversation. If the number at the bottom is wrong in your favour, one of two things happens, and both are expensive.
Either the customer spots it, and every subsequent statement you send them is treated as a first draft rather than a demand. Or they do not spot it, and they pay the wrong amount — after which you are reconciling a payment against a balance neither party agrees with.
The second is worse, and it is more likely, because a customer with a credit note in a drawer somewhere does not necessarily connect it to a line on a statement six weeks later.
A third row type
This is among the smallest things we publish about. The statement already has a row shape with a type, a reference, a debit and a credit column; credit notes already carry a customer, an amount, a date and a reference. What is missing is one more query and one more mapping.
Credit notes as statement rows
Applied credits appearing as credit rows against the period, so the running balance matches the invoices.
A reconciliation check
The statement's closing balance compared against the sum of outstanding invoice balances, with a warning where they differ. The check that would have found this.
Unapplied credits shown separately
A credit issued and not yet applied is money you owe the customer, and it belongs at the foot of the statement rather than nowhere.
No dates on a public page. If you issue credit notes regularly and collect by statement, tell us the volume and we will scope it in writing.
Scope the statementWhat AWRA OpsHub does today
- A customer statement over any date range, with an opening balance, dated rows and a running balance to a closing figure.
- Rows carrying a type, a reference, a description, debit and credit columns, and their own currency.
- Cancelled invoices excluded.
- A stored PDF per statement, filed under the customer with a timestamp.
- Idempotent emailing, so a retry does not send a duplicate.
- Receivables ageing separately, and a payments register spanning the product.
What it does not do
- Credit notes as statement rows. The statement is built from invoices and payments only.
- Any reconciliation between the statement's closing balance and the sum of outstanding invoice balances.
- Unapplied credits shown as a separate figure.
- Any grouping of the statement by payment terms, since terms are not stored on a customer.
- Scheduled statement runs — a statement is produced when somebody asks for one.
Not ours, by choice
- Everything the statement does contain is correct, and the idempotent emailing is a genuinely thoughtful detail. The gap is one omitted document type.
- The invoice itself is right — its balance and status reflect the credit. It is the statement view that does not.
- Nothing here is Sierra Leonean. It is what happens when a document type is missing from a report; a market where the statement is the collection process is where it costs the most.
Our position
Use the statement, and check it before you send it to any customer you have issued a credit note to in the period. The reconciliation is quick: compare the closing balance against the sum of their outstanding invoice balances, and the difference will be exactly your applied credits. Until credit notes appear as rows, treat that comparison as part of your collection process rather than as an optional check.
Reconcile before you send
One comparison per statement, and it takes a minute. We will show you where to pull both figures from so it becomes a habit rather than a discovery.
Set up the checkFrequently asked questions
Is the invoice balance wrong too?
No. The invoice's balance due and status both reflect the credit correctly, and the invoice is marked credited rather than paid. The gap is that the statement is assembled from invoices and payments, and a credit note is neither.
What is the quickest check?
Compare the statement's closing balance against the sum of that customer's outstanding invoice balances. If they differ, the difference is your applied credits for the period, and it will match exactly.
Can I send statements automatically each month?
A statement is produced on request rather than on a schedule, so the monthly run is a person's job. The idempotent emailing at least means a retry after a failed send does not double up, which is the failure this would otherwise produce most often.
