Recurring invoices & subscription billing for Malaysian businesses, in plain words

Baca panduan ini dalam Bahasa Malaysia →

If you bill the same customers again and again — a monthly retainer, an annual plan, a gym membership, a maintenance contract — the invoicing itself becomes the job. Do it by hand and you will eventually miss a cycle, e-invoice one month late, or chase a payment that already came in. This guide shows how to run recurring billing properly for a Malaysian business.

The short version

Recurring billing means invoicing the same customer on a repeating schedule — a retainer, a subscription, a membership, a standing weekly order.
Five things define a cycle: the customer, the amount, the frequency, the start date, and an end date (or an open-ended “until cancelled”).
Decide auto-issue or draft-first per customer, not for the whole business. Auto-issue what never changes; keep anything variable draft-first.
If you are within the e-Invoice mandate, every issued cycle still goes to MyInvois. B2C receipts may roll into a periodic consolidated e-Invoice within LHDN’s rules (as at July 2026; source: LHDN e-Invoice guideline) — but thresholds and exceptions apply.
Caveat: billing is not revenue recognition. Billing RM1,200 for an annual plan in January does not mean you earned RM1,200 in January.
First step: list every customer you bill repeatedly, and mark each one auto or draft-first. That list is your billing schedule.

Want the number instead of the theory? Try the free deferred-revenue calculator.

What "recurring billing" actually means

Recurring billing is any arrangement where you invoice the same customer on a repeating schedule for the same (or a similar) charge.

A digital agency on a RM3,000-a-month retainer, a SaaS tool at RM99 a month, a gym at RM150 a month, a kedai supplying a café with RM800 of goods on a standing weekly order — all of them bill on a cycle rather than one-off.

The mechanics are the same whichever you are. Five things define the cycle:

The customer being billed.
The amount.
The frequency — weekly, monthly, quarterly or yearly.
The start date.
The end date — or an open-ended “until cancelled”.

Billing is not collection, and not revenue recognition

Get those five things right and the rest is discipline: issuing on time, every time, and collecting what you issued.

Recurring billing is separate from how the money arrives. You can bill on a cycle and still collect by bank transfer, by a card the customer keeps on file, or by a payment link each month.

It is also separate from revenue recognition. Billing RM1,200 for an annual plan in January does not mean you earned RM1,200 in January — that is a different discipline, covered in the deferred-revenue guide linked below.

Auto-issue or draft-first? Pick per customer, not per business

The first real decision is whether each cycle’s invoice goes out automatically, or lands as a draft for someone to check and send. Both are legitimate — the mistake is treating it as an all-or-nothing choice for the whole business.

Auto-issue suits charges that never change: a fixed RM99 subscription, a RM150 membership. The invoice generates and sends itself on the billing date, and you only look when something breaks.
It is the right default for high-volume, fixed-price plans where reviewing each one would be a waste of time.
Draft-first suits charges that move: a retainer where this month included extra hours, a supply order where the quantity varies, anything with usage or a variable line.
On draft-first, the system prepares the invoice on schedule, but a human confirms the figures before it goes to the customer.
For an agency, “draft-first on retainers, auto on the fixed add-ons” is a common and sensible split.
The practical rule: auto-issue only what you would be comfortable sending unseen. If you would want to glance at it first, keep it draft-first. Good software lets you set this per template, not force one mode on everything.

LHDN e-invoicing on a recurring cycle

If you are within the e-Invoice mandate for your turnover band, a recurring invoice is still an invoice — each cycle needs to be submitted to LHDN through MyInvois and validated, the same as a one-off sale. The recurring part automates the drafting; it does not exempt you from e-invoicing each issued document.

Where it gets easier is for business-to-consumer (B2C) recurring charges — a gym member, an individual subscriber — who typically does not ask for their own e-Invoice.

Under LHDN’s e-Invoice guidelines, a supplier may issue normal receipts to such buyers and then aggregate them into a consolidated e-Invoice for the period, within the rules and timeframe LHDN sets (as at July 2026; source: LHDN e-Invoice Specific Guideline / MyInvois).
That means your monthly memberships need not each be an individual e-Invoice — they can roll up into one periodic consolidated submission.
Caveat one: the consolidation rules carry exceptions — certain transaction types, and single transactions above a stated value threshold, still require an individual e-Invoice even in a B2C setting. Do not assume everything can be consolidated.
Caveat two: a business customer (B2B) who needs the e-Invoice to claim their own position will ask for an individual validated e-Invoice each cycle, and you must provide it.
The consolidation detail evolves as the rollout matures — always check the current LHDN e-Invoice guideline before relying on it, and confirm your own turnover band and start date.

Build for both routes, not a month-end scramble

The takeaway for a recurring biller: build your process so each cycle can produce either an individual validated e-Invoice (for B2B, or on request) or feed a periodic consolidated e-Invoice (for B2C), rather than treating e-invoicing as a separate month-end scramble.

Dunning: what to do when a recurring payment is late

“Dunning” is just the polite, systematic chasing of a payment that has not arrived. On a recurring book it is unavoidable — cards expire, transfers get forgotten, a customer disputes one month.

The businesses that collect well are not the ones with no late payers. They are the ones with a consistent, unemotional follow-up rhythm.

A simple ladder works: a friendly reminder a few days before the due date, a first chase on the due date, a firmer one a week later, and a defined point where service pauses or a call happens.
For a RM3,000 retainer the sequence might be email, email, phone call; for a RM150 membership it is usually just automated reminders until it clears or the membership lapses.
Write the ladder down once and apply it the same way to everyone — that is what keeps it from feeling personal.
Keep the tone right for the Malaysian context: warm and factual, not threatening. “Just a heads-up, invoice INV-0102 for RM3,000 is due on the 5th” collects better than a legalistic demand.
Match the follow-up effort to the amount at stake — a RM99 subscription is not worth a phone call, a RM30,000 quarterly contract is.
Tie dunning to your books. A reminder should be driven by what is actually unpaid in your accounts, not a separate spreadsheet of who-owes-what — otherwise you will eventually chase someone who already paid.

What to look for in recurring-billing software

Not every “recurring invoice” feature is equal. A few things separate software that genuinely runs your billing from software that just copies last month’s invoice. Five checks:

Per-template issue mode. Can you set auto-issue on fixed plans and draft-first on variable ones, rather than one global switch?
Handling of change. When a customer upgrades, pauses or cancels mid-term, does the schedule adjust cleanly, or do you end up editing invoices by hand?
E-invoice fit. Does each issued cycle flow into your LHDN e-Invoice process — individual for B2B, consolidated for B2C — without a separate step?
Dunning that reads your ledger. Are reminders driven by what is actually outstanding in your accounts, so a paid invoice stops chasing itself?
Recognition, if you sell annual or multi-month terms. Does the tool spread the income over the service period, or leave your P&L lumpy (see the deferred-revenue guide)? A tool that does the billing but ignores recognition solves half the problem.
Above all, it should sit on the same ledger as the rest of your accounting. When the invoice, the e-Invoice submission, the collection and the recognition live in one place, month-end is reading the books rather than reconciling four disconnected tools.

How Taokeh handles recurring billing

Taokeh, the Malaysian SME accounting software by Enya Venture, runs recurring invoices from templates you set once: the customer, the amount, the frequency and the dates.

You choose per template whether a cycle auto-issues or lands as a draft to check first — so fixed plans run themselves while variable retainers still get a human glance.
Each issued cycle sits on the same ledger as the rest of your books and feeds your LHDN e-Invoice process — an individual validated e-Invoice where a business customer needs one, or a periodic consolidated e-Invoice for B2C receipts, within LHDN’s rules.
When you chase, you chase from the truth: the A/R aging shows exactly what is outstanding per customer, and statements are one click.
You can ask your AI assistant to read the overdue list and draft the reminder email — you press send, so a settled invoice never gets chased.
Recurring invoicing and per-cycle e-invoicing come with the base plan; revenue spreading for annual and multi-month terms is the Recurring Revenue add-on you switch on only if you sell them.
That is the “don’t pay for what you don’t use” principle: one ledger, billing to books, rather than a separate subscription tool bolted onto your accounts.

Frequently asked questions

Should recurring invoices send automatically or as drafts?

Both are valid — decide per customer, not per business. Auto-issue fixed, never-changing charges (a RM99 subscription, a RM150 membership) so they run themselves. Keep draft-first any charge that varies (a retainer with extra hours, a variable supply order) so a human confirms the figures before it goes out. Good software lets you set this per template.

Do I still have to e-invoice each recurring cycle to LHDN?

Yes, if you are within the mandate for your turnover band — each cycle needs submitting to MyInvois and validating. For B2C buyers who do not need their own e-Invoice, you may issue receipts and aggregate them into a periodic consolidated e-Invoice within LHDN’s rules (as at July 2026; source: LHDN e-Invoice guideline). Certain transactions, and amounts above a stated threshold, still need individual e-Invoices.

What is dunning?

Dunning is the systematic follow-up of an unpaid invoice — a reminder before the due date, a chase on it, a firmer one later, and a defined point where service pauses or a call happens. Write the ladder down once, apply it consistently, match the effort to the amount at stake, and drive it from what is unpaid in your books.

Is recurring billing the same as revenue recognition?

No. Recurring billing is about issuing and collecting the invoice on a cycle. Revenue recognition is about earning that income over the service period — billing RM1,200 for an annual plan in January does not mean you earned RM1,200 in January. They are separate disciplines; see the deferred-revenue guide.

Updated August 2026

This guide is general information for Malaysian SMEs, not tax, legal or accounting advice. Always confirm current rules and figures with the relevant authority or your own adviser.

Recurring-revenue accounting in Taokeh — invoicing, recognition and payout reconciliation

Run the books for your Malaysian SME on one ledger — accounting, payroll and selling channels.

See how Taokeh handles it → Start your free trial