MyInvois 2026 phase rollout — what Malaysian F&B owners should do this quarter
The next MyInvois phase is pulling smaller Malaysian F&B businesses in. Here are the six operational steps that separate a smooth rollover from a sandbox-rejection scramble on go-live day.
LHDN’s MyInvois rollout has been working its way down the revenue thresholds since 2026, and the next phase pulls in a lot of smaller Malaysian F&B operators. If your café or restaurant hasn’t set it up yet, this is the year to do it before the deadline rather than the week after.
Where the phased rollout stands in 2026
LHDN has been onboarding businesses in revenue bands. The large-enterprise band went live first; mid-market followed; the small-business and micro-business bands are the ones every café and salon owner is asking about right now. The exact threshold and date applicable to your business is on the official LHDN timeline at mytax.hasil.gov.my — check it directly, because LHDN has adjusted the schedule more than once and a six-month-old article will be wrong.
What “ready” means in practice
Operationally, MyInvois readiness for an F&B operator means five things, in roughly this order:
- You can produce a structured record of each sale or daily summary in the LHDN-accepted format.
- You have a registered MyInvois account, your client ID and secret, and you’ve submitted at least a handful of sandbox invoices and seen them validate.
- Your POS knows the difference between sandbox and production mode, and you’ve verified live submissions land in your production view.
- Your finance flow handles credit notes / cancellations through MyInvois rather than ad-hoc on paper.
- Someone on your team knows what to do when LHDN rejects a submission (it happens; the most common cause is a TIN format or SST mismatch).
Six things to do before your band activates
1. Confirm your eligibility band
Log into MyInvois under your SSM credentials and read the scheduled go-live for your registered turnover. Note that the band you’re in today may be different from what it was at the last rollout — turnover bands shift annually.
2. Get your TIN, BRN, and MSIC code right now
These three numbers go into every single submission. Get them somewhere written down and verified — the most painful sandbox rejections come from a typo in the BRN or an MSIC code that doesn’t match your SSM record.
3. Generate sandbox credentials
Even if your live deadline is months away, run sandbox now. Sandbox catches operational gaps you won’t spot in the UI — what happens when the kitchen prints a refund slip, how you reissue a corrected invoice, who’s authorised to cancel.
4. Decide on per-transaction vs daily summary
For consumer transactions where the buyer isn’t requesting a personalised e-invoice, LHDN allows daily consolidated submissions. For a 150-cover café this dramatically reduces the API call volume — but you need your POS to support it.
5. Train your cashier on the new artefacts
Customers will start asking for their personal e-invoice. Receipts still print as usual; the structured record sits in MyInvois. Make sure your cashier knows the difference between “here’s your receipt” and “I’ll submit a personalised e-invoice for you”.
6. Verify rejection handling
Your POS should retry on transient errors and log the rejection reason for permanent ones. Train someone (manager, owner) to read the daily rejection list and act on it. A rejected submission isn’t auto-fixed by LHDN — it’s on you to correct and resubmit.
What Timeo handles for you
- Per-tenant client ID + secret, encrypted at rest.
- Sandbox / production toggle with explicit confirm — no accidental live submissions during testing.
- OAuth token refresh, retry-on-transient, structured logging of rejections in the dashboard.
- Daily consolidated submission for orders where the customer didn’t request a personal e-invoice.
Two months out, not two weeks
Every band rollout we’ve helped tenants through has the same shape: businesses that started two months early are running smoothly the week of go-live, businesses that started two weeks early are sandbox-rejecting on the morning of and calling support. Set a calendar reminder for 60 days before your band activates and start the operational steps above.