Knowing a subscriber actually got the invoice

How a provider can tell whether an invoice, statement or overdue reminder e-mail really went out to a subscriber, and what to do when one did not.

By Achekam · 11 October 2026 · 5 min read · For Telecoms businesses in South Africa, Nigeria, Kenya

"I never received an invoice." Every provider hears it, usually from a subscriber whose service has just been suspended for non-payment. Sometimes it is true. Sometimes the invoice went to an old address, or into a spam folder, or was never sent at all because something failed on your side. And sometimes it is simply a way to buy time.

You cannot settle that conversation fairly without evidence. Not "our system sends invoices automatically", but a record for this subscriber, this invoice, this date, saying whether the e-mail went out.

Achekam keeps that kind of record for invoices, statements and overdue reminders. Here is what each one tells you, where its limits are, and what to do when a send fails.

Three kinds of e-mail, three records

Between them, these cover most of the paper trail for a subscriber who says they were never told.

Invoices: sent, or reported as not sent

An issued invoice can be downloaded as a PDF on the business's letterhead and e-mailed from the invoice, with or without a pay link. If the e-mail fails, the invoice is reported as not sent.

That last part is what matters in a dispute. A system that shows every invoice as "sent" regardless is no evidence at all. One that tells you when a send failed gives you something to work with: an invoice that was not flagged gives you reasonable grounds to say it went, and one that was flagged is one you should have followed up.

Statements of account

The server produces a customer statement of account as a PDF that can be e-mailed, and the screen says whether it was sent. For a subscriber who disputes several months at once, the statement is often more useful than individual invoices: one document listing everything charged and paid, with a record that it went to them.

A good habit for disputed accounts is to e-mail a fresh statement as soon as the dispute is raised. If the subscriber still says nothing arrived, confirm the address with them on the call and send it again while they are on the line. Few disputes survive a statement that lands in the subscriber's inbox while they are talking to you.

Reminders, recorded one by one

Credit control is switched on for new workspaces. Once a day it e-mails overdue reminders, by default at 7, 14 and 30 days overdue with the invoice PDF attached, and a monthly statement to customers with a balance. It never charges anyone, and it records whether each e-mail went out.

For a provider deciding whether to suspend a subscriber, that record is the history you need: which reminders were due, which went out and when. Before suspending, look at it. A subscriber who was sent three reminders and a statement has had fair notice. One whose reminders all failed has not, whatever your terms say.

E-mail settings that must work

All of this depends on e-mail actually leaving your workspace. Credit control needs working e-mail settings, and so does sending invoices and statements. If those settings are wrong or lapse, sends fail.

The good news is that failures are reported rather than hidden. The habit that turns that into protection is looking. A sudden run of not-sent invoices on the morning of your monthly billing is far more likely to be a settings problem than a hundred subscribers with bad addresses.

Note one general limit of e-mail: a message that went out can still be filtered into spam or rejected later by the subscriber's mail service. "Went out" is strong evidence that you sent it; it is not proof that the subscriber read it. Microsoft's guide to non-delivery reports and SMTP errors in Exchange Online explains what a bounce message is, what its error codes mean and how to fix the usual causes of a message that was not delivered.

What the subscriber sees

The invoice PDF carries your letterhead. The logo, brand colour and company details you set under Settings also appear on documents composed for signature, such as a service agreement, so a subscriber sees the same identity on the contract and the bill. Documents made by the server print your VAT registration number and are titled Tax Invoice only when a VAT number is set.

One limit matters most to Nigerian and Kenyan providers, and to any business without a VAT number: at the time of writing, the invoice PDF downloaded or e-mailed from the invoice screen is always headed TAX INVOICE and cites the South African VAT Act, whatever the business's country or VAT number. The server's own template handles this correctly; the browser-made PDF does not yet. Check what your subscribers receive.

When a send fails

1. Check the subscriber's e-mail address on their record. Old and mistyped addresses are common causes.
2. If many sends failed at once, check your e-mail settings before anything else.
3. Re-send the invoice or statement once the cause is fixed, and check that it now shows as sent.
4. If the subscriber is overdue, phone them before acting on the arrears. Their reminders may never have reached them.
5. Note the call on the subscriber's file.

Building it into the month

After each billing run, look for invoices reported as not sent before you do anything else, and fix them the same day. Before any suspension, check the reminder record. And when a subscriber says they never got the invoice, you can answer with dates rather than assurances. If a subscriber's real complaint is an outage, crediting subscribers for an outage last month covers the fix, and how online subscriber payments reach the books explains what happens once they pay.

General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.