Malaysia — Retail & POS Localization

Malaysia is mid-rollout, and the phase you fall into decides what you must do. LHDN's MyInvois e-invoicing has arrived in turnover-banded waves; Phase 4 went live 1 January 2026 for businesses between RM1 million and RM5 million turnover, and businesses below RM1 million are exempt. Separately, from 1 January 2026 a transaction above RM10,000 can no longer be folded into a consolidated invoice — which is the rule that actually reaches the till. Note also that Malaysia levies SST, not VAT: the tax model is different in kind from most of this repository.

Verification status — partially verified, 2026-08

Phase structure checked against secondary sources. Confirm against LHDN before relying on any of it.

Resolved this pass

• Phase 1 from 2024-08-01 (turnover above RM100m); Phase 2 from 2025-01-01 (RM25m–RM100m); Phase 3 from 2025-07-01 (RM5m–RM25m); Phase 4 from 2026-01-01 (RM1m–RM5m), with a relaxation period reported to run to 2027-12-31.
• Exemption threshold raised from RM500,000 to RM1,000,000 effective 2026-01-01.
• From 2026-01-01, individual e-invoices are required for transactions above RM10,000; consolidation is no longer permitted for those.

Still open — TODO: verify

1. Current sales tax and service tax rates, and which apply to the intended catalogue. SST is not a single rate.
2. Whether the business in question is registered for sales tax, service tax, both or neither, and what that requires on the receipt.
3. What a consolidated e-invoice must contain and how often it must be submitted.
4. The exact treatment of a walk-in retail sale below RM10,000 that the customer does not request an invoice for.
5. What the relaxation period permits in practice and its precise end date.
6. Mandatory receipt fields, and whether a QR or validation link is required on the printed slip.
7. Whether cash rounding to the nearest 5 sen is mandatory or optional.
8. Taxpayer identifier (TIN) format and validation rules.

Currency

Cash rounding to 5 sen. Malaysia rounds cash totals to the nearest 5 sen while card and wallet payments settle to the exact sen — TODO: verify whether this is mandatory. As in Peru, the rounding difference must be recorded as its own amount on the sale rather than by adjusting a price, or cash takings will not reconcile against recorded sales and it will look like till shrinkage.

Tax

SST is not VAT, and the difference matters to the data model. A tax engine built around a VAT credit chain will model things Malaysia does not have and miss things it does. Sales tax is typically levied at the manufacturer or import stage rather than at each sale, so a retailer's obligation may be quite different from the VAT-style per-line output tax assumed elsewhere in this repository. TODO: verify what the specific business is actually registered for before designing the tax setup — this is the item most likely to be got wrong by assumption.

Receipt requirements

The RM10,000 rule is the one that reaches the till. From 1 January 2026, a transaction above that value needs its own individual e-invoice and cannot be swept into a consolidated submission. In practice the POS must decide, at the moment of sale, whether this sale requires buyer details captured for an individual e-invoice — which means the cashier may need to ask for a TIN mid-transaction. Design that path deliberately rather than retrofitting it.

Below the threshold, consolidated submission has been the mechanism for B2C retail — TODO: verify its current form, contents and frequency.

TODO: verify mandatory printed fields and whether a validation QR is required.

Paper widths: 80 mm (48 or 42 characters at Font A) and 58 mm (32).

Languages used in retail

Malay (Bahasa Malaysia) is the national language; English is widely used in commerce, and Chinese is in everyday commercial use in a way that is unusual among the markets in this repository. Tamil is also present.

This changes the usual pattern. Elsewhere a Chinese-language back office is paired with a local-language till out of necessity; in Malaysia a Chinese-owned business may legitimately run a Chinese till interface as well, depending on who it hires and serves. The requirement is therefore not "Chinese back office, local till" but genuine per-user language selection across a wider set — Malay, English and Chinese all plausible for either role, with the print template set independently.

Malay and English are plain Latin script with no thermal printing difficulty. Chinese on the receipt needs the same treatment as any CJK output — raster rendering is the reliable path.

Payment methods

Notes for POS implementers

Establish the phase and the registration status before anything else. Turnover band determines the e-invoicing obligation and date; SST registration determines the tax treatment. Both are facts about the specific business, not about Malaysia, and both change what the software must do.

Build for the threshold decision at the till. A sale crossing RM10,000 changes the document required. If that decision only exists in back-office logic, the cashier will discover it after the customer has left.

Time zone. UTC+8, no daylight saving.

Rounding as data. Record the 5 sen rounding as its own amount, as above.

Food service

Restaurants diverge from retail at the till, not just in the menu. Three things change: the tax treatment can depend on where the food is eaten, service charge and tips carry their own rules and their own tax questions, and the trading day routinely runs past midnight. Malaysia adds two things retail does not have to think about: a service tax that lands specifically on food service, and halal labelling.

Tax treatment

Service charge and tips

Receipt requirements specific to food service

Operating conventions

Trading day and the midnight boundary. TODO: verify. Make the boundary configurable per site.

Trading hours. TODO: verify typical local hours for the intended segment; they drive shift handover, Z-report timing and staffing, and they differ sharply between a bakery and a bar.

Kitchen ticket language. Malay, English and Chinese are all in genuine commercial use, so the kitchen, the floor and the back office may legitimately run three different languages. This is the market where per-user and per-output language selection matters most.

Notes for POS implementers

Four capabilities separate a food-service till from a retail one. They are worth naming because a retail POS typically has none of them, and retrofitting them is expensive:

• Floor plan and table state — a sale is attached to a table, not opened and closed in one pass.
• Tab allocation — one table's bill split across several payers, or one payer covering several tables. Splitting by item and splitting evenly are different operations and both get asked for.
• Guest count — needed for per-head reporting, and in some markets it appears on the document. See the receipt table above.
• Tip adjustment — the tip is frequently added after the card is authorised, so the recorded amount must be adjustable post-authorisation without reopening the sale.

Halal is a labelling and separation requirement, not a menu flag. Certification is administered by JAKIM, and the requirements reach what may be displayed and stated about a dish — TODO: verify the specific labelling obligations and what, if anything, must appear on printed output. Where a kitchen handles both halal and non-halal, the separation is operational as well as informational; a single boolean on a menu item does not capture it.

Cash rounding reaches the food-service receipt too. The nearest 5 sen rule applies to cash totals while card and wallet settle exactly, so a split bill paid partly in cash and partly by card produces a rounding difference on the cash portion only. Record it as its own amount, as in the retail sections — on split bills this is where it most often goes wrong.

Order modifiers are not discounts. "No coriander", "extra spicy", "sauce on the side" attach to a line and must reach the kitchen ticket, sometimes with a price delta and sometimes without. Modelling them as discounts or as separate products both fail — the first corrupts the tax base, the second corrupts stock.

Void before and after firing are different events. Cancelling an item that has not reached the kitchen is an edit; cancelling one already cooked is a loss that has to be recorded as such, or waste and theft become indistinguishable.

Last updated: 2026-08

Maintained by the MISAll team. Last updated: 2026-08