- Retailers with FY2022 revenue of RM1 million to RM5 million (Phase 4) must issue e-invoices from 1 January 2026, with a relaxation period running until 31 December 2027 and full enforcement from 1 January 2028. [e-Invoice Specific Guideline v4.8 (7 Jul 2026), Table 16.1]
- Any single retail transaction exceeding RM10,000 requires its own individual e-invoice. This rule applies to every business regardless of phase or relaxation status and cannot be consolidated. [e-Invoice Specific Guideline v4.8, Table 3.6]
- Once LHDN validates an e-invoice, generally in under 2 seconds, the retailer or buyer has 72 hours to cancel or reject it before a credit, debit, or refund note is required instead. [LHDN e-Invoice General FAQs, Q34, Q39–Q40]
- JomeInvoice’s pre-built POS connectors cover Loyverse, SalesPlay, Cloudbeds, Shopify, and WooCommerce; QuickBooks retailers use a guided Excel-based upload workflow, and other systems connect through file upload, SFTP, or API.
- Businesses that missed past e-invoices can back-file them penalty-free under the e-Invoice Special Voluntary Disclosure Programme (SVDP), open from 7 July 2026 to 31 December 2027; fraud, wilful default, and negligence cases are excluded. [e-Invoice Specific Guideline v4.8, Section 17]
- Failing to issue a required e-invoice carries a fine of RM200 to RM20,000 per invoice, imprisonment of up to 6 months, or both. [Income Tax Act 1967, Para 120(1)(d)]
A retail Point of Sale (POS) system handles e-invoicing in Malaysia by capturing the sale, sending the transaction to the Inland Revenue Board of Malaysia (Lembaga Hasil Dalam Negeri, LHDN) for validation through MyInvois, and sharing the validated e-invoice with the buyer, either individually or as part of a monthly consolidated e-invoice. This guide covers the full 6-step flow, which POS systems are e-invoice ready out of the box, what upgrading actually costs versus using middleware, and the consolidation rules that apply to everyday retail sales.
What Is Retail POS System e-Invoicing?
Retail POS system e-invoicing is the process of generating a structured, LHDN-validated electronic invoice directly from a point-of-sale transaction, instead of issuing a paper or PDF receipt only. The POS system captures the sale, an e-invoicing channel (the MyInvois portal, an Application Programming Interface (API) connection, or middleware) formats and submits the data, and LHDN validates it before the retailer shares the final e-invoice with the customer.
This does not replace your existing POS software. It adds a compliance layer on top of the sales data your POS already records, so items, prices, and tax lines flow into a format LHDN accepts.
How Retail POS e-Invoicing Works in Malaysia: The 6-Step Flow
Every retail transaction that becomes an e-invoice follows the same six-step path, whether it is entered manually, pushed through an API, or handled by middleware.
Step 1: Issuance at the Point of Sale
The POS system records the transaction: items sold, prices, applicable Sales and Service Tax (SST), and payment method. The retailer then generates the e-invoice through one of three channels:
- MyInvois portal: manual entry or spreadsheet upload, free but not practical at volume.
- API integration: the POS or a connected system talks directly to MyInvois using LHDN-approved specifications.
- Middleware: a connector service converts POS data into the required e-invoice format automatically, without the retailer building or maintaining the integration.
Step 2: Validation by LHDN
The e-invoice is submitted to LHDN through MyInvois. LHDN checks the data against structure and tax rules and validates it in near real time, generally in under 2 seconds. [LHDN e-Invoice General FAQs, Q34] Once validated, the e-invoice receives a Unique Identifier Number (UUID) and a QR code that lets anyone confirm its authenticity at myinvois.hasil.gov.my.
Step 3: Notification of Validation
MyInvois notifies both the retailer and the buyer that the e-invoice validated successfully, carrying the UUID and validation timestamp. There is no separate buyer-approval step here: validation confirms the invoice meets LHDN’s format and tax rules, not that the buyer has reviewed and accepted it.
Step 4: Sharing the e-Invoice with the Buyer
The retailer shares the validated e-invoice, or a visual representation carrying the QR code, with the buyer through a printed receipt, email, or a digital channel such as an app or online order confirmation.
Step 5: Rejection or Cancellation Within 72 Hours
If there is an error, the buyer can request rejection or the retailer can cancel the e-invoice within 72 hours of validation. [LHDN e-Invoice General FAQs, Q39–Q40] After that window closes, corrections go through a credit note, debit note, or refund note instead, and there is no time limit on issuing those. [LHDN e-Invoice General FAQs, Q44]
Step 6: Storage and Retrieval via MyInvois
Every validated e-invoice is stored in LHDN’s MyInvois system and remains retrievable by the retailer and buyer in PDF, XML, or JSON format, either through the portal or via API for businesses that sync records into their own accounting system.
Still typing every receipt into MyInvois by hand?
JomeInvoice connects your POS to MyInvois so every sale validates automatically.
Types of e-Invoices Retailers Issue
Retail transactions generate four document types under the e-Invoice framework:
- Invoice: the standard document for a completed sale.
- Credit note: for discounts, returns, or price corrections after the 72-hour window closes.
- Debit note: for additional charges applied to a prior transaction.
- Refund note: for an actual repayment of funds to the buyer.
B2C Sales and Consolidated e-Invoices for Retail
Most retail transactions are business-to-consumer (B2C), where the buyer does not request an individual e-invoice. For these sales, retailers issue a consolidated e-invoice: a single monthly e-invoice that aggregates every transaction where no buyer asked for one, submitted to LHDN within 7 calendar days after month end. e-Invoice Specific Guideline v4.8, Section 3.6
The consolidated route has one hard limit that retailers frequently misread: any single transaction exceeding RM10,000 must be issued as an individual e-invoice and cannot be folded into the monthly consolidation. [e-Invoice Specific Guideline v4.8, Table 3.6] This RM10,000 rule binds every business, in every phase, whether or not that business is still inside its relaxation period. The optional relaxation available to Phase 4 and new RM1M–RM5M businesses until 31 December 2027 lets them consolidate transactions from industries that normally cannot be consolidated (Section 3.7 activities) and self-billed scenarios under Section 8.3, but it does not touch the RM10,000 threshold.
Retailers running deposits, layaway plans, or partial prepayments should check the specific timing rules for those scenarios, covered in our guide to deposits versus prepayments under Malaysia’s e-invoice rules. For the full consolidated workflow, including how to handle mixed transaction sizes in one outlet, see consolidated e-invoice rules for retail in Malaysia.
Which POS Systems in Malaysia Are e-Invoice Ready?
A POS system is e-invoice ready if it can either submit directly to MyInvois via API or export transaction data in a format a middleware layer can convert into an e-invoice. The requirement is identical nationwide: an e-invoice POS system in Penang, Johor Bahru, or Kota Kinabalu follows the same MyInvois flow as one in Kuala Lumpur. Most retail POS systems in Malaysia fall short on one of five points:
- Data synchronization gaps: POS software is built to record a sale, not to structure and transmit the tax and buyer fields LHDN requires, leaving audit trail gaps unless something bridges the data.
- Legacy or no-API systems: older, offline POS terminals were never built for cloud or API connectivity, so they cannot talk to MyInvois directly.
- ERP misalignment: where POS data feeds into an Enterprise Resource Planning (ERP) system before reaching accounting, a mismatch between the ERP and the e-invoicing channel produces duplicated or rejected submissions.
- Upgrade cost: replacing a working POS purely for e-invoicing compliance is expensive and disruptive for a retailer that otherwise has no reason to switch.
- Security requirements: transmitting tax and customer data between systems needs proper encryption and authentication, which older integrations were not designed to handle.
The table below maps the four practical paths retailers use to close these gaps.
| Path | How it works | Best for |
|---|---|---|
| Native connector | POS system links directly to a middleware provider through a pre-built integration | Retailers on Loyverse, SalesPlay, Cloudbeds, Shopify, or WooCommerce |
| File/API-based integration | Transaction exports (CSV, SFTP) or a custom API link feed the e-invoicing channel | Retailers on systems without a pre-built connector |
| Middleware (no native connector) | A middleware layer converts POS exports into LHDN’s required format without custom development | Retailers on legacy or unsupported POS software |
| Manual MyInvois portal | Staff enter or upload transactions directly | Very low transaction volume only |
If your POS has no e-invoice feature at all, our dedicated guide covers exactly what to do next: what to do when your POS has no e-invoice feature.
Do You Need to Upgrade Your POS? Costs vs Middleware
Retailers facing this decision are usually weighing three routes, not two.
| Route | Upfront cost | Disruption | Best for |
|---|---|---|---|
| Upgrade the POS | Highest: hardware, licensing, retraining | High: migration and staff retraining | Systems already end-of-life for other reasons |
| Middleware | Low: monthly subscription | Low: existing POS stays in place | A POS that works fine but lacks e-invoicing |
| Manual MyInvois portal | RM0: staff time only | None to set up, heavy ongoing effort | A handful of transactions a month |
Upgrading the POS itself makes sense when the current system is end-of-life for other reasons too, such as inventory or multi-outlet limitations, and e-invoicing compliance is one more reason to move. It carries the highest upfront cost: new hardware or licensing, staff retraining, and migration time.
Adopting middleware is the lower-disruption route for retailers whose POS otherwise works fine. Middleware sits between the existing POS and MyInvois, converting sales, purchase, and self-billing data into the required format without replacing anything the retailer already uses. Ongoing middleware fees are typically lower than a full POS replacement cycle, and there is no retraining beyond the e-invoice workflow itself.
Manual entry via the MyInvois portal costs nothing beyond staff time, but it does not scale. Every consolidated submission, cancellation, and TIN check becomes a manual task, which is workable for a handful of transactions a month and unworkable for a busy retail counter.
Micro, small, and medium enterprises (MSMEs) that engaged a consultant to help plan their e-invoice implementation can also claim a tax deduction of up to RM50,000 per year of assessment for those consultation fees, under the ESG-related expenditure deduction. [Budget 2024 announcement; LHDN e-Invoice General FAQs, Q17] This applies regardless of which of the three routes above a retailer chooses.
The Middleware Role: Connecting POS, Purchasing, and Self-Billing
Most retail POS systems handle only one leg of the e-invoicing requirement: sales. Full compliance also covers purchasing (stock, rent, utilities) and self-billing (staff claims, reimbursements), neither of which a typical POS system tracks. Where a retailer’s accounting software, such as QuickBooks, AutoCount, or SQL Account, needs to reflect validated e-invoices alongside existing ledgers, that accounting data flows through the middleware layer rather than through a direct POS-to-accounting link, since POS systems are not built to manage that sync themselves.
For retailers running multiple outlets or several POS terminals, this same middleware layer is what keeps register numbers, outlet locations, and item-level data consistent across every consolidated submission, instead of reconciling separate exports by hand.
Choosing the right middleware provider matters here, since not all of them cover purchasing and self-billing at the same depth as sales. Our comparison of the leading options covers what to check before committing: best e-invoice middleware in Malaysia.
Go Deeper: Retail & POS e-Invoicing Guides
- What to do when your POS has no e-invoice feature: the practical fallback paths when your current POS cannot generate e-invoices at all.
- The retail POS e-invoice workflow, step by step: a day-to-day operational walkthrough for staff running the till.
- MyInvois e-POS versus POS e-invoice integration: how LHDN’s own e-POS tool compares to integrating your existing system.
- Consolidated e-invoice rules for retail in Malaysia: the full monthly consolidation workflow and its exceptions.
- Deposits versus prepayments under Malaysia’s e-invoice rules: timing rules for retailers who take deposits or layaway payments.
- e-Invoicing for the retail industry in Malaysia: an industry-wide overview beyond POS specifically.
- Best e-invoice middleware in Malaysia: a comparison of middleware providers for retailers evaluating options.
Retailers checking how their obligations compare with other sectors can also see our e-invoice requirements by industry in Malaysia, and businesses still confirming whether the mandate applies to them at all should start with our complete LHDN e-invoice guide for Malaysia in 2026.
How JomeInvoice Handles Retail POS e-Invoicing
Retailers do not need to choose between replacing their POS and issuing e-invoices by hand. JomeInvoice is Malaysian-built, government-certified middleware (MySTI, ISO 9001, ISO 20000-1, ISO 27001, PDPA-compliant) that connects the POS system you already run to MyInvois, then handles validation, consolidation, and storage automatically.
JomeInvoice’s pre-built connectors cover Loyverse, SalesPlay, Cloudbeds, Shopify, and WooCommerce, all available from the Basic plan and above. Retailers running QuickBooks use a guided workflow: export the Daily Sales Summary report, map it to LHDN’s required fields, and upload it directly to JomeInvoice, no custom development needed. Retailers on other systems connect through CSV upload, SFTP, or the MyInvois API without losing the automation: transactions still flow into JomeInvoice, get validated, and land on a live dashboard showing every issued, pending, or rejected e-invoice.
Because most POS systems only cover sales, JomeInvoice also handles the purchasing and self-billing side of retail compliance, so raw material purchases, rent, and staff claims sync into the same e-invoice log instead of sitting in a separate system. For retailers with several outlets, that means one consolidated view instead of reconciling exports outlet by outlet. Built-in Tax Identification Number (TIN) verification runs before submission, cutting down on rejected e-invoices from bad buyer data.
A common pattern among the retailers JomeInvoice has onboarded: they start with the MyInvois portal, manage for a month or two at low volume, then hit a wall once consolidated deadlines and TIN failures pile up during a busy sales period. Moving to middleware before that point is cheaper than fixing it after.
See how JomeInvoice fits a retail operation at our retail e-invoicing solutions page, sign up free at sme.jomeinvoice.my, or talk to our team about connecting your specific POS setup.
Let your POS handle e-invoicing on its own.
Join Malaysian retailers running e-invoice compliance on JomeInvoice.
Disclaimer: This article is for general informational purposes only and does not constitute legal or tax advice. LHDN guidelines are subject to updates. Always refer to the latest official LHDN e-Invoice Guidelines at myinvois.hasil.gov.my and consult a qualified tax professional for advice specific to your business.
Frequently Asked Questions
Does my POS need to be e-invoice compliant in Malaysia?
Yes, if your business is within a mandated phase. Established businesses with RM1M–RM5M revenue (Phase 4) must comply from 1 January 2026; your POS itself does not need built-in e-invoicing as long as an API, middleware, or the manual MyInvois portal covers the gap.
Can I use my old POS without e-invoice features?
Yes. Legacy POS systems can stay in place if middleware converts their transaction exports into LHDN’s required e-invoice format, or if staff submit manually through the MyInvois portal at low volume.
How do POS systems connect to MyInvois?
Three ways: a native connector where the POS provider or a middleware partner has a pre-built integration, a direct API connection your team builds and maintains, or manual entry through the MyInvois portal.
Do I need to issue an e-invoice for every retail sale?
No, not individually. Most B2C retail sales go into a monthly consolidated e-invoice submitted within 7 calendar days after month end. Any single transaction exceeding RM10,000 is the exception and needs its own individual e-invoice. [e-Invoice Specific Guideline v4.8, Table 3.6]
What happens if my POS can’t generate e-invoices?
You can still comply through middleware that converts POS exports into the required format, a direct API build, or manual entry via the MyInvois portal. Failing to issue required e-invoices carries a fine of RM200 to RM20,000 per invoice. [Income Tax Act 1967, Para 120(1)(d)]
How much does POS e-invoice integration cost?
From RM0: manual entry through the free MyInvois portal costs only staff time, middleware runs on a monthly subscription well below a POS replacement, and a full POS upgrade carries the highest upfront cost. MSME consultation fees qualify for a tax deduction of up to RM50,000 a year. [Budget 2024; LHDN FAQs, Q17]
Last updated: 21 August 2026 | Written by Yinn Sheng Ng, Head of Marketing