The Statement a Customer Can Check
Your customer’s payables clerk reconciles your statement against their own ledger every month, line by line. A statement they can check has every line in their terms, a balance carried forward from what came before, and a way to say “this one is wrong” that stops the reminders while it is looked at.
On the third working day of the month, the payables clerk at a private hospital in Nairobi has forty-one supplier statements to reconcile before the payment run. Yours is one of them. She puts it beside the hospital’s ledger for your account and ticks down both: each invoice number, each payment, each credit. Where the two agree she moves on. Where they do not, she stops, and so does your money.
This is how most organizations of any size pay their suppliers, and it is why a statement matters more than an invoice reminder. A reminder says you are owed something. A statement shows the clerk how you arrived at that figure, in a form she can check against her own. If she can check it, the agreed lines go into the run. If she cannot, the whole statement waits until somebody on your side answers an email.
What she is checking
A supplier statement is reconciled on four things, and each needs to be on the page in a form the customer already holds.
- The opening balance, against her closing balance for your account last month.
- Each invoice number and amount, against the invoices she has received and booked.
- Each payment, with its reference, against her bank or M-Pesa record of what she paid.
- Each credit note, against the returns and price corrections she was promised.
Miss any one and she cannot finish. A statement without credit notes shows a balance higher than she owes. A statement that starts at zero for the period shows a balance lower. A payment listed by date and amount, with no reference, has to be searched for by hand among every payment the hospital made that week.
The statement in the customer portal
Customers you invite to the portal sign in with a link sent to their email, with no password to keep, and the statement is one of the pages they find there. It is built for exactly this job:
| On the statement | How it is worked out |
|---|---|
| Opening balance | Every invoice, payment and credit note dated before the period, netted |
| Invoices | Issued invoices only, never drafts or cancelled ones, by invoice number |
| Payments | Against those invoices, with the reference recorded on the payment |
| Credit notes | Issued and applied credit notes, by credit note number |
| Running balance | After every line, carried across pages |
| Closing balance | The opening balance plus everything in the period |
It opens on the last six months and takes any date range, so the clerk can ask for exactly the month she is reconciling. Within a day, invoices come first, then payments, then credit notes, so a same-day invoice and part-payment read in the order they happened. A long statement runs over pages, and each page starts from the balance brought forward from the one before, so the arithmetic can be followed from any page.
Because the opening balance is computed from everything before the period, it should match the closing balance on her side for the month before. When it does not, the difference is in an earlier month, and she knows to look there rather than at the lines in front of her.
A statement is not a demand. It is a reconciliation you have done for the customer, and it is only useful if they can redo it.
When a line is wrong
Reconciliation finds things. A box of gloves billed twice; a delivery short by two cartons; VAT charged on an exempt item. The portal lets the customer dispute that invoice from where they found it, choosing a reason, describing it, and attaching up to five files, such as the goods received note with the shortage written on it.
-
The customer opens the invoice and raises a dispute
Nine reasons cover the usual cases: pricing, quantity, damage, wrong item, not received, duplicate billing, tax, service quality and other.
-
They say how much is in dispute
The whole invoice by default, or the part they question. It cannot exceed the invoice total.
-
Reminders on that invoice stop
Dunning is paused for the disputed invoice, so the customer is not chased for money they have queried.
-
Both sides follow it in one thread
The customer sees the dispute number, its status and your replies. Your team’s internal notes and evidence stay internal.
One open dispute per invoice is allowed; a second question about the same invoice becomes a comment on the first. That keeps the conversation in one place instead of in three email threads, and the rest of the statement can still be agreed and paid while the disputed invoice is sorted out. The other invoices stay on the dunning ladder as usual; only the one in question is paused.
The statement your team sends
Some customers will never sign in, and their clerk wants the statement in her inbox. From the customer’s page, your team can email a PDF statement for any period, with copies to others, and download it as a PDF or a CSV from collections, on the web or in the app. Each email sent is recorded on the customer’s timeline with the address, the period, the closing balance and who sent it, so “which statement did we send them?” has an answer. That sent statement is built from invoices and payments, which is the difference the next section deals with; the portal statement is the complete one, and the one to point a reconciling clerk to.
Statements that close the month faster
The portal statement, disputes from the portal, and emailed and downloaded statements with a send log are in place. These are the extensions that shorten a customer’s reconciliation further.
One ledger for every statement
The emailed and downloaded statement built from the same invoices, payments, credit notes and brought-forward balance as the portal’s.
A download in the portal
The customer’s own PDF or CSV of the statement, for their file and their spreadsheet.
A balance confirmation
The customer confirming the closing balance in the portal, for audit circularisation and year-end.
What AWRA OpsHub does today
- A statement in the customer portal with an opening balance brought forward, invoices, payments and credit notes, a running balance across pages and a closing balance, for any date range.
- Only issued invoices on the portal statement, never drafts or cancelled ones.
- Disputes raised from the portal against an invoice, with a reason, an amount, up to five attachments and a shared thread.
- Dunning paused on an invoice while its dispute is open.
- Emailed PDF statements for any period, with copies, and PDF and CSV downloads on the web and in the app.
- A log of every statement sent on the customer’s timeline.
More we can add to your workspace
- One ledger for the emailed statement and the portal statement, with credit notes and the brought-forward balance on both. Commission it
- A PDF and CSV download of the statement inside the portal. Commission it
- A balance confirmation the customer signs off in the portal for audit and year-end. Commission it
- A bounced cheque shown as its own reversing line beside the original payment. Commission it
- Till sales on account carried onto the customer statement. Commission it
Where we point you to a specialist
- The statement shows what your records say. Whether a disputed amount is owed is for you and your customer to settle, and the dispute thread records that conversation rather than deciding it.
One ledger for every statement is the first thing we would build, because the portal’s query already produces the complete figures.
The short version
Give the customer a statement they can reconcile: an opening balance carried forward, every invoice, payment and credit note in their terms, and a running balance they can follow. Let them dispute the line they disagree with, from where they found it, and stop chasing that invoice while it is looked at. The clerk then agrees the rest and pays it, which is the point of sending a statement.
See customer statements
Statements of account for any period, by email, download and in the customer portal, with disputes and the record of every statement sent.
Explore customer statementsFrequently asked questions
What does the customer portal statement include?
An opening balance brought forward from everything before the period, then every issued invoice, every payment against those invoices with its reference, and every issued or applied credit note, each with a running balance, and a closing balance.
Can a customer choose the period?
Yes. The statement opens on the last six months and takes any from and to date.
Can a customer dispute an invoice from the portal?
Yes. They choose one of nine reasons, describe the problem, say how much is in dispute and can attach up to five files. Reminders on that invoice are paused while the dispute is open.
Do draft invoices appear on the customer’s statement in the portal?
No. Only issued invoices appear, never drafts or cancelled ones.
Can we see which statements were sent to a customer?
Yes. Every statement emailed is recorded on the customer’s timeline with the address it went to, the period, the closing balance and who sent it.