If your Malaysian F&B business turns over between RM1 million and RM5 million, LHDN e-Invoice became mandatory for you on 1 January 2026 — and the six-month penalty relaxation period ended on 30 June 2026. From July 2026 onward, that band is exposed to enforcement for the first time. Three things decide whether this applies to you:
- Below RM1,000,000 annual turnover, you are fully exempt. In December 2025 the exemption threshold was raised from RM500,000 to RM1 million, and the planned Phase 5 for businesses under RM1 million was cancelled. Many Malaysian F&B operators are legitimately outside the regime entirely.
- Above RM1 million, you are already in a mandated phase, and your relaxation period has passed.
- For F&B, the working mechanics are consolidated B2C submission within 7 calendar days after month end, an individual e-invoice for any single transaction exceeding RM10,000, and an individual e-invoice whenever a customer requests one at the counter.
Confirm your own band and current obligations at hasil.gov.my before acting.
What actually changed on 1 July 2026
For most Malaysian restaurant, café and kopitiam owners, e-Invoice has felt like somebody else's problem for two years. Phase 1 hit the very large corporates in August 2024. Phase 2 caught mid-size groups in January 2025. Phase 3 landed in July 2025. Each time, the threshold sat comfortably above the typical single-outlet or few-outlet F&B business, and it was reasonable to file the whole thing under "later".
Later arrived on 1 January 2026, when Phase 4 brought businesses with annual turnover between RM1 million and RM5 million into scope. That band is where the bulk of Malaysia's serious F&B SMEs actually live — the two-outlet café group, the busy kopitiam, the bubble tea chain with four stores, the bistro doing steady dinner covers.
And like every phase before it, Phase 4 came with a six-month relaxation period. That relaxation ended on 30 June 2026.
This is the part that gets misread, so it is worth being precise about it.
The relaxation period was never a delay of the obligation. During those six months, businesses in Phase 4 were still required to issue e-invoices. What was relaxed was enforcement — penalties were not being pursued while businesses got their systems and processes working. The duty existed from 1 January 2026. The consequence of failing it was held back until 1 July 2026.
So the honest summary of where we are, as at July 2026: if you are in the RM1m–RM5m band, you have been required to issue e-invoices for over six months, and from this month the protective cushion is gone.
If that describes you and you are not yet running e-invoices properly, this is not a catastrophe and it is not a reason to panic. It is a reason to fix it in the next few weeks rather than the next few months. The rest of this guide is a practical, plain-English walk through exactly what compliance means for a food business, what your point-of-sale system has to do about it, and — just as importantly — whether it applies to you at all.
Before anything else: check your turnover band. A large number of Malaysian F&B businesses are now permanently outside this regime, and nobody should be spending money or losing sleep on an obligation they do not have. The next two sections deal with that directly.
Direct answers to the questions buyers ask
These are the exact questions Malaysian F&B operators are searching in 2026, each answered so the answer stands on its own.
Do I need LHDN e-Invoice for my restaurant? It depends on one number: your annual turnover. If your annual turnover is below RM1,000,000, you are fully exempt — the exemption threshold was raised from RM500,000 to RM1 million in December 2025, and the planned Phase 5 that would have captured businesses under RM1 million was cancelled. If your annual turnover is RM1 million to RM5 million, you are in Phase 4: mandatory since 1 January 2026, with the six-month relaxation period ended on 30 June 2026. Above RM5 million, you were brought in earlier — RM5m–RM25m from 1 July 2025, RM25m–RM100m from 1 January 2025, above RM100m from 1 August 2024 — and all of those relaxation periods have long closed. Confirm your own position at hasil.gov.my, because thresholds in this regime have changed more than once.
Is the e-Invoice grace period over? For every phase currently in force, yes. Each phase carried a uniform six-month relaxation period during which penalties were not enforced, although e-invoices still had to be issued. Phase 1's ended 31 January 2025, Phase 2's 30 June 2025, Phase 3's 31 December 2025, and Phase 4's ended 30 June 2026. Phase 4 is the one that matters for most F&B SMEs, because it covers the RM1m–RM5m turnover band. From July 2026, businesses in that band face enforcement for the first time. There is no remaining relaxation window for anyone currently in scope.
What is the e-Invoice exemption threshold in Malaysia? RM1,000,000 in annual turnover. Businesses below that figure are fully exempt as of 1 January 2026. This is a change from the earlier position: the exemption threshold was RM500,000 and was raised to RM1 million in December 2025. At the same time, the planned Phase 5 — which would have brought businesses up to RM1 million into scope from 1 July 2026 — was cancelled. If you run a single kopitiam, a hawker unit, a food truck or a small café turning over less than RM1 million a year, the current rules do not require you to issue e-invoices. Verify your position at hasil.gov.my, and re-check if your turnover grows.
How does e-Invoice work for a restaurant when most customers are walk-ins? Through consolidated B2C submission. You do not issue a validated e-invoice for every plate of nasi lemak. For ordinary dine-in and takeaway where the customer does not ask for an e-invoice, you issue your normal receipt at the time of sale, and then aggregate those transactions into a single consolidated e-invoice submitted within 7 calendar days after the end of the month. Three situations break out of the consolidation: a customer who requests a validated e-invoice, any single transaction exceeding RM10,000, and any business-to-business sale where the buyer needs the invoice for their own records. Those require individual e-invoices.
What is the RM10,000 e-Invoice rule? Since 1 January 2026, any single transaction exceeding RM10,000 requires its own individual e-invoice and cannot be placed in a consolidated e-invoice — even in a pure business-to-consumer setting where the customer has not asked for anything. For most F&B businesses this is not a daily event, but it is not rare either: a wedding banquet, a large corporate function, a private-hire dining room, a big catering order, a year-end company dinner. If your business ever writes a bill above RM10,000, your point-of-sale process needs a defined path for it. Confirm the current threshold at hasil.gov.my before relying on it.
What happens if a customer asks for an e-invoice at the counter? You must issue an individual e-invoice for that transaction. It cannot be folded into the month-end consolidation. This is the single most common real-world trigger in F&B — a corporate customer expensing a business lunch, a sales team claiming a client dinner. Practically, it means your till needs to capture the buyer's required details and produce a validated e-invoice without stopping the queue. This is the moment to test in any POS demo, because it is the one that happens during service, in front of other customers, at speed.
Does my POS need to do this, or can I use the MyInvois portal? LHDN provides an official route, and for a business with a handful of qualifying invoices a month, manual submission is workable. The reason F&B operators generally want it inside the POS is volume and timing: consolidated B2C means aggregating an entire month of transactions accurately, and counter requests happen mid-service. A POS that generates and submits automatically removes both the month-end data-assembly job and the "how do I do this while six people are waiting" problem. Whichever route you choose, the obligation and the deadlines are the same.
What does a compliant F&B POS actually need to do? Vendor-neutrally, five things. It must (1) generate e-invoices in the required format and submit them to LHDN for validation, (2) produce and submit the consolidated B2C e-invoice within 7 calendar days after month end, (3) issue an individual e-invoice on request at the counter without collapsing your service flow, (4) automatically route any single transaction exceeding RM10,000 out of consolidation and into an individual e-invoice, and (5) deliver the validated invoice to the customer and keep a retrievable record. Anything less and you are doing part of the job by hand.
Who must comply: the implementation phases in full
LHDN rolled e-Invoice out in turnover bands. Here is the complete picture as it now stands, including the phase that no longer exists.
| Phase | Annual turnover band | Mandatory from | Relaxation period ended |
|---|---|---|---|
| Phase 1 | Above RM100 million | 1 August 2024 | 31 January 2025 |
| Phase 2 | RM25 million – RM100 million | 1 January 2025 | 30 June 2025 |
| Phase 3 | RM5 million – RM25 million | 1 July 2025 | 31 December 2025 |
| Phase 4 | RM1 million – RM5 million | 1 January 2026 | 30 June 2026 |
| Phase 5 | Would have covered up to RM1 million from 1 July 2026 | Cancelled | — |
Below RM1,000,000 annual turnover: fully exempt as of 1 January 2026.
Three things in that table deserve explanation, because they are where operators get confused.
1. Every phase had the same six-month relaxation structure
This was consistent throughout the rollout. A phase became mandatory on a date; six months later, the relaxation period closed. During the relaxation window, penalties were not enforced, but e-invoices still had to be issued. The relaxation was a grace on consequences, not a postponement of the requirement.
That distinction matters retrospectively. If you are in Phase 4 and you have issued nothing since January, you have not simply been "early"; you have had an unmet obligation for six months that was shielded from penalty. The practical response is the same either way — get compliant now — but it is worth understanding correctly rather than assuming the clock only started in July.
2. Phase 5 was cancelled, and the exemption threshold doubled
This is the single most under-communicated change in the whole programme, and it is good news for a very large number of small F&B businesses.
The original plan had a Phase 5 bringing businesses up to RM1 million into scope from 1 July 2026. In December 2025, two decisions landed together: the exemption threshold was raised from RM500,000 to RM1 million, and Phase 5 was cancelled.
The effect is that the smallest tier of Malaysian business — including a great many single-outlet kopitiams, hawker operations, food trucks, small cafés and neighbourhood eateries — is now outside the e-Invoice regime entirely rather than facing a deadline this month.
We want to be blunt about this because the incentive in our industry runs the other way. There is a whole category of marketing that benefits from every small operator believing they have an imminent compliance emergency. They largely do not. If you turn over less than RM1 million a year, the current rules do not require you to issue e-invoices. Do not buy anything on the strength of a deadline that does not apply to you.
3. Your band is about turnover, not outlet count or headcount
Operators routinely assume that "small business" means "few outlets" or "small team". The phase bands are drawn on annual turnover. A single high-volume outlet in a good location can clear RM1 million comfortably; a three-outlet group of small kiosks might not. Count the money, not the shopfronts.
If you are near the line, treat it as a live question rather than a settled one. Turnover moves. A business that was exempt last year may not be this year, and the sensible posture near a threshold is to know where you stand at each financial year end and confirm the current rules for your band at hasil.gov.my.
An honest caveat about dates and thresholds
We are going to state this plainly rather than bury it, because it is genuinely useful to you.
The rules in this programme have changed more than once, and LHDN's portal was recently restructured. The RM500,000 → RM1 million threshold change in December 2025 is a live example: an operator who read a guide written in mid-2025 would have come away believing they faced a July 2026 deadline that no longer exists.
Everything in this guide reflects the position as we understand it in July 2026. But the correct instruction to any operator is the same one we would give about our own pricing page: confirm it at source for your own turnover band before you act on it. The official guidance is published by the Inland Revenue Board of Malaysia at hasil.gov.my.
That is not a disclaimer to protect us. It is the actual, practical advice. A tax obligation is not something to take from a vendor's website — including this one — without checking the authority that sets it.
Who is exempt, and why that is not a loophole
If your annual turnover is below RM1,000,000, you are fully exempt from the e-Invoice requirement as of 1 January 2026.
Being exempt does not mean being invisible. It means you are not required to issue e-invoices under this regime. Several practical implications follow, and they are worth thinking through rather than filing away.
You still keep proper records. Exemption from e-Invoice is not exemption from bookkeeping, from SST obligations if they apply to you, or from being able to substantiate your income. Your normal receipting and record-keeping duties continue exactly as before. If anything, an exempt business benefits from being able to demonstrate its turnover cleanly, because turnover is precisely the number that determines whether the exemption still applies.
Your business customers may still ask. A corporate customer who expenses a meal at your restaurant may request an e-invoice regardless of your exemption status, because they want it for their own claim. Being exempt means you are not obliged to have a system that produces one. It does not stop the conversation happening at your counter, and it is worth deciding in advance how you want your staff to answer it. A polite, informed "we're below the threshold and not in the e-Invoice system, here's a full receipt with our business details" is a much better customer experience than a shrug.
Crossing the threshold is a change of status. If your turnover grows past RM1 million, your position changes. Nobody sends you a letter the day it happens. This is an argument for knowing your annual figure properly rather than approximately, and for checking hasil.gov.my when you are approaching the line.
Growth-minded operators sometimes choose to be ready early. This is a genuine judgement call, not a sales pitch. If you are at RM800,000 and growing 30% a year, you will likely be in scope at your next financial year end. Some operators in that position prefer to have the capability sitting in their system, dormant, rather than to change systems under deadline pressure later. Others sensibly decide to deal with it when it happens. Both are defensible. What is not defensible is being told you have an emergency when you do not.
How consolidated B2C e-invoicing actually works in F&B
This is the mechanic that makes e-Invoice workable for food service, and it is the part most operators find reassuring once they understand it.
The fear on first contact with e-Invoice is: "Do I have to submit a government-validated invoice for every teh tarik?" No.
The normal flow
For ordinary dine-in and takeaway where the customer does not request an e-invoice:
- During the month, you trade normally. Customer orders, you ring it up, you issue your usual receipt. Nothing changes at the counter. No pause, no extra data capture, no queue.
- At month end, those transactions are aggregated. All the ordinary consumer sales that did not require an individual e-invoice are consolidated.
- You submit one consolidated B2C e-invoice. This must be submitted within 7 calendar days after the end of the month.
That is the entire shape of it for the vast majority of F&B revenue. The counter experience for a normal customer is unchanged.
What the 7-day deadline really means operationally
"Within 7 calendar days after the end of the month" is a short window, and it is calendar days, not working days. A month ending on a Sunday with a public holiday in the first week does not extend it.
This is where the practical risk sits for most operators — not in the concept, but in the recurring monthly discipline. Twelve times a year, on a fixed short deadline, an accurate aggregation of every consolidatable transaction has to be assembled and submitted. It is exactly the sort of task that gets done reliably for four months and then missed in the month you open a second outlet, or the month your bookkeeper is on leave, or the month Chinese New Year lands in the first week.
There are three ways operators handle it:
- Manually. Export sales, assemble the consolidation, submit through the official route. Workable, but it is a real recurring job with a hard deadline, and its quality depends on whoever is doing it that month.
- Through your accountant or tax agent. Sensible for many businesses, but note that your accountant needs your data early enough in the window to act, which pulls your internal deadline forward, not back.
- Automatically from your POS. The transactions already live there, correctly categorised, so the aggregation is a system function rather than a person's monthly task.
None of these is universally right. What we would say plainly is that the failure mode in all three is the same — it is a deadline you have to hit every single month, and the risk is not conceptual difficulty but ordinary human slippage. Whatever route you choose, decide who owns it, put it on a calendar, and make the internal deadline earlier than the legal one.
What must break out of the consolidation
Three categories cannot sit inside the consolidated B2C submission:
- Any single transaction exceeding RM10,000 (since 1 January 2026).
- Any transaction where the buyer requests a validated e-invoice.
- Business-to-business transactions, where the buyer needs the e-invoice for their own compliance and records.
Each of these needs an individual e-invoice. The next two sections cover the first two, because they are the ones that happen at your counter.
The RM10,000 rule, explained for food businesses
Since 1 January 2026, any single transaction exceeding RM10,000 requires its own individual e-invoice and cannot be included in a consolidated e-invoice — even in a pure B2C setting, and even if the customer does not ask for anything.
Read that carefully, because there is a trap in it. The rule is not "if a business customer spends over RM10,000". It is about the transaction value, regardless of who the buyer is. A private individual paying RM12,000 for a family celebration dinner triggers the same requirement as a company would.
Where this actually shows up in F&B
Most restaurants will not hit RM10,000 on a walk-in table. But this is far from a theoretical rule for the sector:
- Wedding and engagement banquets. Routine territory for Chinese restaurants, hotels and banquet halls.
- Corporate functions and year-end dinners. A company booking out your dining room in December.
- Large catering orders. Office events, product launches, festive corporate gifting of food.
- Private dining and buy-outs. Whole-venue hire for a private party.
- Steamboat and buffet group bookings. Large parties on a per-head charge add up faster than operators expect.
- Bulk or wholesale supply. A bakery supplying a hotel or a café group.
If any of that is part of your business, even occasionally, you need a defined path for it — not an ad-hoc scramble on the night of the banquet.
The operational failure mode to design against
The dangerous version of this is not the RM50,000 wedding that everybody knows is coming and plans for. It is the unplanned large transaction: the group that walks in and turns out to be twenty covers on one bill, the last-minute catering order taken over WhatsApp on a Friday, the corporate customer who adds three bottles of something expensive.
The failure looks like this. The transaction is rung up normally. Nobody notices it crossed the threshold. It lands in the consolidated pool at month end, where it does not belong. You do not find out until somebody reconciles, or does not.
The design principle is that the system should catch it, not the cashier. A cashier during service is not a reliable threshold monitor, and it is unfair to make them one. Ask any POS vendor directly: when a single transaction exceeds RM10,000, does your system prevent it entering the consolidation automatically, and what does the cashier see?
Also confirm the current threshold at hasil.gov.my. It is set by LHDN, not by your POS vendor, and figures in this programme have moved before.
When a customer asks for an e-invoice at the counter
This is the everyday reality of e-Invoice in F&B, and it is worth thinking about properly because it happens during service.
If a buyer requests a validated e-invoice, you must issue an individual e-invoice for that transaction. It cannot be folded into the monthly consolidation.
Why this happens more than you would expect
Malaysian corporate expense culture runs on documentation. Once a company's own finance team is in the e-Invoice regime, their staff start being told to obtain proper e-invoices for claimable spending — and business meals are one of the most common claimable categories there is.
So the request comes from ordinary customers in ordinary situations:
- A sales team having lunch with a client
- Someone entertaining a supplier
- A consultant grabbing dinner on a project
- A company card paying for a team meal
- A regular who has just been told by their accounts department to start asking
None of these people are being difficult. They have a requirement, and you are the one who can satisfy it.
What the moment actually requires
To issue an individual e-invoice you need the buyer's details captured accurately at the point of sale, the invoice generated in the required format, submitted to LHDN for validation, and delivered to the customer.
The operational question is: how long does that take, and does the queue stop?
This is where the difference between "our POS supports e-Invoice" and "our POS handles e-Invoice well" becomes visible. A system where the cashier must exit the sale, open a separate portal, rekey the transaction and manually enter buyer details is technically compliant and operationally miserable at 12:45pm. A system where it is a step inside the existing payment flow, with the customer's details captured once and the validated invoice delivered automatically, is the same obligation with none of the pain.
Staff training is half the answer
Whatever your system does, your people need three things:
- A clear answer to "can I have an e-invoice?" — yes, and here is what we need from you.
- The exact sequence on the till, practised before it happens live, not discovered during a rush.
- A fallback for when the request arrives after payment has been taken, or when connectivity is down.
That third one is worth planning explicitly. The customer who remembers halfway to the car park is a real scenario. Decide now what your staff do about it rather than improvising.
A note on delivery
Once validated, the invoice has to reach the customer. In practice this is usually by email or by a QR code presented at checkout that the customer scans to retrieve their invoice. The QR route is a genuinely good fit for a busy counter — it hands the retrieval step to the customer instead of holding your queue while somebody spells out an email address.
What your POS actually needs to do — a vendor-neutral checklist
This section is deliberately written so you can apply it to any system, including ours. If you are shopping for a POS on compliance grounds, these are the capabilities that matter. Take it into every demo you attend.
1. Generate and submit e-invoices to LHDN for validation. Not "export a file you then upload somewhere". Ask to see the submission happen and the validated result come back.
2. Produce and submit the consolidated B2C e-invoice on the monthly cycle. Ask to see a real consolidation run, end to end, on a month of data. This is the single most important thing to witness, and the one most commonly demonstrated as a screenshot rather than a working process.
3. Handle a counter request for an individual e-invoice inside the payment flow. Time it. Count the taps. Ask what happens to the queue.
4. Automatically break out any single transaction exceeding RM10,000. The system should enforce this, not rely on cashier vigilance.
5. Handle B2B transactions properly, capturing the buyer details an individual e-invoice requires.
6. Deliver the validated invoice to the customer by email or QR, without a manual step per invoice.
7. Show you the status of submissions. You need to be able to answer "did this month's consolidation actually go through?" without phoning anyone. Ask what the system does when LHDN rejects a submission — this is the question that separates a real implementation from a demo. Rejections happen. What matters is whether you find out immediately or at year end.
8. Keep records you can retrieve. Your e-invoice records need to be accessible for your own accounting and for any future query.
9. Keep working when the internet drops. Connectivity in Malaysia is good but not perfect, and a POS that cannot take an order during an outage costs you real revenue regardless of tax rules. Ask specifically which modules work offline — the answer is rarely "all of them", from any vendor — and what happens to e-invoice submissions queued during the outage.
10. Not charge you a surprise for any of the above. Ask directly whether e-Invoice functionality is included in the quoted price or is a paid module, and get the answer in writing.
Questions worth asking that vendors do not volunteer
- Does the system handle credit notes and refunds correctly for e-Invoice purposes? Voids and refunds are routine in F&B and they have to be reflected properly.
- What happens if you need to correct an invoice after submission?
- Who is responsible if a submission fails — is there a support path, and what are its hours?
- Is there anything about the compliance workflow that requires you to log into a separate system every month?
- If you leave the vendor, can you export your own e-invoice records?
Answer those ten plus five for any shortlisted system and you will know considerably more than the average buyer walking into this decision.
How Popcorn POS handles LHDN e-Invoice
We build Popcorn POS, a Malaysian F&B cloud point-of-sale system, and this section is what we do about e-Invoice. It is here because it is relevant, not because the guide was written to arrive at it. If you are exempt below RM1 million, none of this is urgent for you.
Popcorn POS is LHDN MyInvois Compliant and SST Ready. E-invoice is activated under Outlet Setting.
How it works in practice:
- Real-time generation with automatic submission to LHDN. Invoices are generated and submitted as part of the transaction flow rather than as a separate manual job.
- Consolidated B2C submitted via the Popcorn backend before the 7th of each month. This is worth stating factually against the rule: LHDN requires the consolidated B2C e-invoice within 7 calendar days after the end of the month; Popcorn POS submits before the 7th. That is a straightforward alignment between the product cycle and the regulatory deadline — no more and no less than that.
- The customer receives their invoice by email or by QR at checkout, which keeps the delivery step off your counter staff.
The rest of the platform, for context, since compliance is never the only reason anyone buys a POS:
- Cashier POS — the core till, cloud-based with offline mode and automatic sync. Offline is scoped to the Cashier till; do not assume every module in any POS, ours included, behaves identically without connectivity.
- Waiter App — tableside order-taking.
- Kitchen Display — digital kitchen order management.
- Edge By Popcorn — the owner dashboard: gross profit, product, attendance and per-outlet reports.
- Plus QR e-menu self-ordering, multi-outlet centralised management, cash / card / e-wallet / DuitNow QR payments and split payments.
Credentials: LHDN MyInvois Compliant, SST Ready, VAPT Security Certified, PSG Pre-Approved, with 24/7 support.
Positioning, plainly: Popcorn POS is the "F&B Revenue Optimizer", built for Malaysia rather than adapted from abroad, designed around getting from order to payment in three seconds. It is a product of Rockbell Software, with offices in Johor Bahru, Puchong and Singapore.
Pricing: from RM90/month, no lock-in. One honest qualification, which we would want stated on any vendor's page including ours: RM90 is the entry price for the core Cashier module. It should not be read as "the entire suite for RM90". Ask us for a written quote covering your exact configuration — your outlets, your terminals, the modules you actually need — exactly as you should ask every other vendor on your shortlist.
Segments we serve: restaurants, kopitiams, cafés, fast food, bubble tea, food trucks, bakeries, pubs, bistros, and steamboat and buffet operations.
And the same instruction we have given throughout this guide applies to us: do not take a compliance capability on trust from a vendor's website. Ask us to show you the consolidated submission running, the counter request flow, and the RM10,000 break-out — in a demo, on screen. If we cannot show it, you should not believe it.
Common mistakes Malaysian F&B operators are making right now
These are the recurring patterns worth checking yourself against.
1. Assuming the obligation started when the relaxation ended. For Phase 4 businesses, the requirement began 1 January 2026. The relaxation suspended penalties, not the duty to issue e-invoices. If you have issued nothing since January, your position is not "starting on time" — get moving now.
2. Assuming you are in scope when you are exempt. Below RM1 million in annual turnover you are fully exempt. A meaningful number of small operators are spending money and worry on an obligation they do not have, largely because the December 2025 threshold change was poorly publicised.
3. Assuming you are exempt when you are not. The mirror error. RM1 million of annual turnover is roughly RM83,000 a month. A single busy outlet in a good location clears that. Check the actual number rather than the impression.
4. Treating "e-Invoice ready" on a feature list as proof. Almost every POS in the Malaysian market carries that phrase somewhere. It tells you nothing about whether the consolidated monthly submission actually runs, what happens on rejection, or how a counter request behaves during a lunch rush. Insist on seeing it.
5. Not designing for the RM10,000 break-out. The transaction that quietly crosses the line and lands in the consolidation is the most likely single compliance error in a food business. Make the system catch it.
6. Leaving the month-end submission unowned. Twelve hard deadlines a year with no named owner is a process that will fail eventually. Put a name and a calendar reminder against it, dated earlier than the legal deadline.
7. Being unable to answer a customer at the counter. Your staff will be asked. Decide the answer, the sequence and the fallback before it happens live.
8. Treating compliance as the whole POS decision. E-Invoice is table stakes in this market now — most credible vendors clear the bar. Do not let it crowd out the things you will live with daily: speed at the till, offline reliability, modifier handling, kitchen coordination, whether you can see gross profit by product, and total cost of ownership over twelve months.
9. Reading a guide from 2025 and acting on it. The rules have changed. Anything written before December 2025 will tell you the exemption threshold is RM500,000 and that Phase 5 is coming in July 2026. Both are now wrong.
10. Taking any of this — including this page — as tax advice. We are a POS company writing a practical operator's guide. For your own position, confirm at hasil.gov.my and speak to your accountant or tax agent.
Choosing an approach by business type
The regime is the same for everyone in scope. The practical shape of the problem is not.
Kopitiams and coffee shops
The compliance question is first a turnover question. Many single-outlet kopitiams sit below RM1 million and are fully exempt. Check before doing anything. A high-traffic kopitiam in a strong location may well be above the line, in which case Phase 4 applies and the relaxation has ended.
If you are in scope, your profile is high transaction count at low ticket value, which means almost everything consolidates. The daily counter experience barely changes; the work is the monthly submission. The one thing to get right is speed — your staff turnover is high and your till has to be learnable in an hour. Do not accept a compliance workflow that adds taps to every sale, because at kopitiam volume, seconds compound into a queue out the door.
Cafés and dessert shops
Similar consolidation profile, but with a higher likelihood of corporate customers requesting individual e-invoices — remote workers on company cards, small teams meeting over coffee. Test the counter request flow specifically. Menu changes are frequent in this format, so also check that your compliance setup does not add friction every time you change the menu.
Bubble tea and beverage chains
Heavy modifiers and usually multi-outlet ambitions. The compliance question here is largely a multi-outlet one: is the consolidated submission handled per outlet or centrally, and who is responsible for each? A three-store operator with three separate monthly submissions and no central visibility has three times the chance of missing one. Ask how consolidation works across outlets, and make sure someone can see at a glance that all of them went through.
Full-service restaurants and bistros
The most mixed profile, and therefore the one that needs the most complete capability. You will have ordinary walk-in covers that consolidate, corporate diners requesting individual e-invoices, and occasionally a large group or private booking that crosses RM10,000. You need all three paths working. Split bills add a wrinkle worth testing directly: if one person at a table of six needs an e-invoice for their share, what does the system do? Ask that question in the demo; it is a good test of how deeply a vendor has thought about F&B specifically.
Fast food and quick service
Throughput is everything and virtually all revenue consolidates. Your requirement is that compliance costs you zero seconds on the standard transaction. Test under a simulated rush — ten orders in three minutes — and confirm the e-invoice layer is invisible in the normal flow.
Steamboat, buffet and banquet
The format most exposed to the RM10,000 rule. Per-head charging on large parties reaches five figures faster than operators expect, and banquet bookings are core business rather than an exception. Make the individual-invoice path for large bills a primary requirement, not an afterthought, and confirm how deposits and staged payments are treated.
Bakeries
Watch for the wholesale and B2B side. Supplying cafés, hotels or offices is business-to-business, which means individual e-invoices with proper buyer details rather than consolidation. A bakery with a retail counter and a wholesale book is running both models simultaneously and needs both to work.
Food trucks and small mobile vendors
Most are below RM1 million and exempt. If that is you, this is not your problem right now — and anyone telling you otherwise is worth questioning. If you are above the line, the material issue is connectivity: you cannot depend on stable internet at a night market. Confirm that the till keeps selling offline and that submissions queue and go through once connectivity returns.
Multi-outlet groups
Turnover aggregates faster than owners expect, so multi-outlet groups are frequently in Phase 4 or above. The core requirement is central visibility: one place where you can confirm every outlet's consolidated submission went through, rather than trusting each site to handle its own. Ask specifically how consolidation is structured across outlets and who holds the deadline.
A practical catch-up plan if you are behind
If you are in Phase 4, in scope, and not yet compliant, here is a sensible sequence. This is process guidance, not a promise about outcomes — how quickly any of it moves depends on your business, your vendor and your accountant.
Step 1 — Establish your band with certainty. Get your actual annual turnover figure. Not an estimate. This single number determines whether you have an obligation at all. Confirm the current threshold and phase position for that band at hasil.gov.my.
Step 2 — If you are in scope, talk to your accountant or tax agent this week. They deal with this across multiple clients and will know your specific position. Ask them directly what your exposure is for the period since your phase began, and what they recommend you do about it. This is the conversation to have first, before you buy anything.
Step 3 — Audit what your current POS can actually do. Not what the brochure says. Ask your existing vendor, in writing, the ten questions in the checklist above. Many operators discover their current system does more than they realised, and the fix is configuration rather than replacement. That is the cheapest possible outcome and worth checking before anything else.
Step 4 — Identify your break-out scenarios. List where individual e-invoices arise in your business: counter requests, transactions above RM10,000, any B2B supply. These are the paths that need to work at the till, not just at month end.
Step 5 — Name an owner for the monthly consolidation. One person. On the calendar. With an internal deadline earlier than the legal one, so a public holiday or a leave day does not sink it.
Step 6 — Train your counter staff on the request flow. Run it as a drill during a quiet period. The first time a staff member handles an e-invoice request should not be during Friday dinner service.
Step 7 — Only then consider changing systems. If your current POS genuinely cannot do the job, replace it — but decide on the full picture, not compliance alone. You will live with the till's speed, offline behaviour and reporting every single day, and with the compliance layer for about ten minutes a month.
Step 8 — Verify the first cycle end to end. Do not assume the first month's submission worked because nobody said otherwise. Check that it went through, and check what the system shows you if it does not.
Glossary — the terms you will encounter
- e-Invoice. A digital invoice in a prescribed format, submitted to and validated by LHDN, rather than a plain receipt or a PDF.
- LHDN. Lembaga Hasil Dalam Negeri — the Inland Revenue Board of Malaysia, the authority behind the e-Invoice regime. Official guidance is published at hasil.gov.my.
- MyInvois. LHDN's e-invoicing system, through which e-invoices are submitted and validated.
- Validation. LHDN's confirmation that a submitted e-invoice is accepted. An invoice is not a compliant e-invoice until it is validated.
- B2C. Business to consumer — an ordinary sale to an individual customer, which is the bulk of F&B revenue.
- B2B. Business to business — a sale to another business, which typically needs an individual e-invoice for the buyer's own records.
- Consolidated e-invoice. A single e-invoice aggregating multiple B2C transactions, submitted periodically rather than one per sale. For F&B, this is the mechanism that makes the regime workable.
- The 7-day rule. The consolidated B2C e-invoice must be submitted within 7 calendar days after the end of the month.
- The RM10,000 rule. Since 1 January 2026, any single transaction exceeding RM10,000 requires its own individual e-invoice and cannot be consolidated.
- Individual e-invoice. An e-invoice issued for a single specific transaction, as opposed to one included in a consolidation.
- Implementation phase. The turnover band determining when e-Invoice became mandatory for a given business.
- Relaxation period. The six-month window following each phase's mandatory date, during which penalties were not enforced although e-invoices still had to be issued.
- Exemption threshold. The annual turnover level below which a business is not required to issue e-invoices — raised from RM500,000 to RM1 million in December 2025.
- Annual turnover. Total revenue over a year — the measure that determines your phase, not outlet count or headcount.
- SST. Sales and Service Tax, Malaysia's consumption tax regime — a separate obligation from e-Invoice.
- POS. Point of sale — the system that takes orders, processes payment and records the transaction.
- Consolidation window. The period between month end and the 7-day deadline, during which the consolidated submission must be prepared and sent.
- Offline mode. A POS's ability to keep selling when the internet drops, syncing when the connection returns.
- DuitNow QR. Malaysia's national interoperable QR payment standard.
Sources
Official LHDN e-Invoice and MyInvois guidance is published by the Inland Revenue Board of Malaysia (Lembaga Hasil Dalam Negeri, LHDN). The specific pages behind this guide:
- Implementation timeline — phases, turnover thresholds and the exemption: https://www.hasil.gov.my/en/e-invois/pelaksanaan-e-invois-di-malaysia/garis-masa-pelaksanaan-e-invois/ — this is the source of the phase table above and of the rule that taxpayers with annual turnover or revenue of less than RM1,000,000 are exempted from e-Invoice implementation. LHDN records this timeline as updated on 7 December 2025.
- e-Invoice Guideline and e-Invoice Specific Guideline — relaxation periods, consolidated e-invoice rules and the individual-invoice threshold: https://www.hasil.gov.my/en/e-invois/rujukan-pelaksanaan-e-invois/garis-panduan/
- MyInvois Portal: https://www.hasil.gov.my/en/e-invois/portal-myinvois/mengenai-portal-myinvois/
- LHDN main portal: https://www.hasil.gov.my/
Note on the relaxation-period dates: the phase dates and the RM1,000,000 exemption above are taken directly from LHDN's published implementation timeline. The six-month relaxation periods are set out in LHDN's e-Invoice Guideline rather than on the timeline page — check the current version of that Guideline for the wording that applies to your phase.
Popcorn POS product, compliance and pricing information is from https://popcorntek.com.my.
This guide reflects our understanding of the position as at July 2026 and is written to help F&B operators understand the practical shape of the requirement. It is not tax advice. Thresholds and dates in this programme have changed more than once and LHDN's portal was recently restructured — confirm the current rules for your own turnover band at hasil.gov.my, and speak to your accountant or tax agent about your specific position.
