Recurring Invoices Explained: Billing Cycles, Retainers and Subscriptions

Some customers buy once. Others pay you every month, every term or every quarter for as long as the relationship lasts. Recurring invoices are how you bill that second group without rebuilding the same invoice from scratch each time, and without quietly copying last cycle's mistakes into the next one.

Three shapes of recurring revenue

Most recurring billing in Nigerian businesses falls into one of three shapes. They look alike on a bank statement, but they behave differently when something changes.

The word that matters is agreed. A recurring invoice is not a guess about what the customer owes. It's the agreement, repeated on schedule.

The pieces of a billing cycle

Every recurring arrangement can be described with five facts. Write them down once and most billing disputes disappear.

1. Who is billed: the customer, plus the billing contact who receives the invoice. For a company, that's often an accounts mailbox, not the person who signed.
2. What they're billed for: the service, with a description the payer's accountant will recognise.
3. How much: the agreed amount per cycle, before VAT.
4. How often: monthly, termly, quarterly or yearly, and on which date.
5. Until when: an end date, or "until cancelled", with the notice period.

When those five facts live in one place, next cycle's invoice can be generated from them. When they live in a spreadsheet tab, an email thread and someone's memory, each cycle is rebuilt by hand.

A worked example: one month, three customers

Chiamaka Obi runs billing at a facilities firm in Lekki. On 1 December 2026 she has three recurring customers.

Two things changed since November, and both are the kind of change that slips through:

• The residents’ association added generator-room cleaning from December at ₦40,000 a month. The retainer is now ₦640,000, so the correct total is ₦688,000, not ₦645,000.
• Lekki Heights asked for invoices to go to a new bursar's email address.

If Chiamaka duplicates November's invoices, the association is undercharged by ₦43,000 (₦40,000 plus ₦3,000 VAT) and the school's invoice lands in an inbox nobody reads. Neither error is dramatic. Both cost money, and both repeat every month until someone notices.

Why copying last month's invoice is risky

Duplicating the previous invoice is the most common way to "do" recurring billing. It works until it doesn't, and it fails in predictable ways:

• Changes don't stick. A one-off discount from last month is copied into this month.
• Ended customers keep getting billed. Nobody removes the line when the contract ends, and the first sign is an angry call.
• Dates drift. "Monthly" quietly becomes the 3rd, then the 5th, then whenever someone remembers.
• Numbers collide. Copying an invoice sometimes copies its number too. Our guide to invoice numbering covers why that matters.

The fix isn't a cleverer copy. It's separating the agreement (who, what, how much, how often) from the invoice (one cycle of it).

A pre-run checklist for each cycle

Before recurring invoices go out, run through this. It takes ten minutes and catches most of the problems above.

• New agreements since last cycle are added, with their start date.
• Ended agreements are closed, so they don't produce an invoice.
• Price changes take effect from the right cycle, not retrospectively.
• Billing contacts are current, including CC addresses.
• One-off charges or credits from last cycle are not carried forward.
• Each invoice is reviewed by someone other than the person who prepared the run, at least for the largest amounts.
• Totals for the run are compared with last cycle. A big swing has an explanation.

That last check is the cheapest control you have. Chiamaka's December run is ₦1,150,250 and November's was ₦946,000. She should be able to name the ₦204,250 difference in one sentence: the quarterly pest-control invoice (₦161,250) and the new generator-room cleaning (₦43,000 with VAT).

Retainers: bill the base, then the extras

Retainers cause the most confusion because the customer pays a fixed fee and sometimes more. Keep them on separate lines, or separate invoices, so the customer's accountant can see what's routine and what isn't.

Retainer, December 2026: ₦750,000 Additional: court appearance, Federal High Court Lagos, 9 December: ₦250,000

A single line for ₦1,000,000 invites a query. Two lines with dates rarely do.

When a cycle is due but you shouldn't invoice

Not every due date should produce an invoice. A customer might have paid a year upfront, paused their membership, or be in a dispute. Decide in advance who can hold a cycle, and record why. An invoice raised and then voided is worse than one never raised, because it still appears in reports and statements until someone explains it.

How Flux helps

In Flux, recurring billing starts from enrolments: each one links a customer to a service with an agreed amount and billing cycle. Next-cycle invoices are generated from the previous one, so you review what changed rather than rebuilding it. They then go through the same approval workflow as any other invoice before they're emailed, each with a Pay online link for card or bank transfer. Statements show every cycle's invoice and payment in one place. See how it works for subscriptions, memberships and cycles.