Statements that get you paid

A statement is how account customers settle: not one invoice, but the position — what was owed, what was paid, what remains, aged. SeroBooks generates it per customer from the live ledger, so the statement a customer receives is the same truth your Receivables screen shows, to the cent, at the moment you sent it.

Statements are built from documents, not balances alone: each line traces to an invoice, credit note or payment, so when a customer queries a line, you open the document behind it while they are still on the phone.

Every statement goes out as a PDF to print or attach, as an email drafted and addressed in your mail app, or as a WhatsApp message ready to send. For a trade counter, the WhatsApp statement is usually the fastest chase there is — it arrives where the customer already talks to you.

The Statements screen shows every customer owing at once, with an Email All for month-end runs, and flags customers who owe money but have no email address on file — add one, or print for the driver to hand over.

The screen is built for a monthly discipline: pick the period, review the list, send everything, then work the exceptions. Because it reads the same aging as Receivables, the follow-up call happens with the full picture — the overdue bucket, the credit limit, the last payment — one row deep.

Every send is logged against the customer, so 'we never received a statement' has an answer, with a date on it.

Because statements read the ledger directly, they cannot disagree with your books — there is no statement module to reconcile against accounting. A payment recorded at the till appears on the very next statement; a credit note issued this morning nets today.

That is the quiet advantage of one system over a POS bolted to an accounting package: every customer-facing document and every internal figure comes from the same place.