How to invoice customers who pay with mobile money

Most small businesses in Uganda and Zambia get paid by mobile money, and most invoice templates were designed for somewhere else. The result is an invoice that shows a bank account nobody uses, a phone number typed into the footer as an afterthought, and a payment that lands in your wallet with no clue which customer sent it.

Here is what actually works, based on the invoices we send ourselves and the mistakes we made first.

Put the payment instructions on the invoice, not in the covering message

The covering email or WhatsApp message gets scrolled past. The invoice is the document your customer opens when they finally sit down to pay, sometimes two weeks later, and everything they need has to be on it.

For a mobile money payment, that means four things:

1. The network. Write "MTN Mobile Money" or "Airtel Money" in full. A bare phone number makes your customer guess, and guessing means a failed transfer or a call to your accounts person.
2. The number, formatted so it can be dialled. Group it the way people read it locally and include the country code for customers who may be outside the country.
3. The registered name on that number, exactly as it appears when the network shows the confirmation screen. If your line is registered to a person rather than the business, say so on the invoice. A customer who sees an unexpected name at the confirmation step often cancels the payment.
4. The reference to type, which is the invoice number.

Then keep your bank details on the same invoice. Mobile money has transaction limits, and a large invoice may have to be split or sent by bank transfer instead. Giving both avoids a phone call.

Ask for a reference your customer can actually send

This is the single change that saves the most time. Mobile money reference fields are short and are often skipped entirely, so make the reference short enough to survive: use the invoice number on its own, for example INV-0042, not the invoice number plus your company name plus the month.

Write it on the invoice as an instruction, not as a hope: "Use INV-0042 as the reference." Then, on the WhatsApp message, ask for one thing back: "Please send the confirmation message once you have paid." The forwarded confirmation carries the transaction ID, the amount and the time, which is everything you need to match the payment without waiting for a statement.

Get the VAT line right before you send

If you are VAT registered, the invoice has to show it properly, and mobile money changes nothing about that. Show the line items excluding VAT, a separate VAT line at the rate that applies, and the total including VAT, with your TIN or TPIN on the document. If some lines are exempt or zero rated, they need their own line rather than being blended into one number.

Decide early whether your prices are quoted inclusive or exclusive of VAT, and say which on the quote. Arguing about it after the customer has paid an inclusive amount you treated as exclusive is a bad week.

Mobile money charges are a separate matter. If the network deducts a fee on withdrawal, that is your cost of collecting the money, not a discount on the invoice. The invoice stays paid in full and the fee is recorded as an expense, otherwise your balances will drift by small amounts all year.

Record the payment against the invoice while you still remember

When the money arrives, record it against the invoice with three pieces of information: the amount, the date, and the transaction ID from the confirmation message. In AfriBMS this takes about fifteen seconds and turns an open invoice into a part-paid or settled one.

Part payments are normal here. A customer sending 300,000 today and the rest on Friday is not an edge case, so record both as they arrive rather than waiting for the full amount. An invoice that shows a real balance is one you can chase honestly.

The transaction ID matters more than it looks. When a customer says "we paid that in July", the ID ends the conversation in one message. Without it you are comparing two statements line by line.

Reconcile once a week, not once a quarter

Pick a day. Open the mobile money statement for the week, and walk down it against the payments you recorded. You are looking for three things: money in the statement that is not recorded anywhere, payments you recorded that never actually arrived, and amounts that are close but not equal, which usually means a network fee or a customer who paid the wrong total.

Unmatched payments are normally identifiable from the sending number, because the same customer pays from the same line every time. Once you have identified one, save that number on the customer record so the next one matches itself.

A week is short enough that you can still remember the context, and long enough that you are not doing this every day. A quarter is too long: by then the sender has changed phones and nobody remembers the deal.

Share the link on WhatsApp instead of the PDF

Most invoices in this region are opened on a phone, and a PDF attachment in WhatsApp is a download, a wait and a file in the wrong folder. A link opens immediately in the browser your customer already has, shows the amount due and your payment details at the top, and still offers the PDF for anyone who wants to print or forward it to their accountant.

It also keeps one version of the truth. An issued invoice is frozen, so a correction means voiding it and issuing a new one, and the link to the old invoice then shows that it is void. The PDF they downloaded last Thursday still looks live.

Send it with a short message: what it is for, the amount, the due date, and the reference to use. Three lines, and the person reading it on a boda in traffic can act on it.

The short version

Put the network, the number, the registered name and the reference on the invoice. Keep the reference short. Show the VAT properly. Record every payment with its transaction ID on the day it arrives. Reconcile weekly. Send a link, not a file. None of it is complicated, and together it is the difference between knowing who owes you money and guessing.