B2C E-Invoicing

Business-to-Consumer (B2C) e-invoicing covers electronic invoices issued by a business to an individual consumer (non-business buyer). In Malaysia's MyInvois framework, B2C e-invoicing has more flexible rules than B2B, recognising that individual consumers are not registered taxpayers with TINs in every case, that issuing a full MyInvois e-invoice for every cup of coffee or retail sale is impractical, and that consumers typically do not need tax invoices for personal expense deduction purposes.

For most B2C transactions, businesses have two options under the MyInvois framework. The first is to issue consolidated e-invoices — batching multiple consumer transactions into a single MyInvois submission within 72 hours. This is the standard approach for high-volume B2C businesses like restaurants, supermarkets, and petrol stations. The second is to issue individual e-invoices per consumer, which is required when the consumer specifically requests a tax invoice (for example, for medical expense claims, professional development fees, or business-related personal purchases).

A "simplified e-invoice" concept exists in LHDN's guidelines for B2C transactions below certain thresholds. Simplified invoices contain reduced mandatory fields compared to full e-invoices — for instance, the buyer's TIN may be replaced by their MyKad number or passport number, and some supplier details may be abbreviated. However, simplified invoices still need to be submitted to and validated by MyInvois to be legally valid. The simplification is in the data requirements, not in the obligation to use MyInvois.

Consumer QR code verification is an emerging feature of the B2C e-invoicing system. When a business issues a consolidated or individual e-invoice for a consumer transaction, the validated invoice in MyInvois carries a QR code. Some businesses print or display this QR code on customer receipts, allowing consumers to scan it and verify on LHDN's portal that their transaction has been properly recorded. This helps build consumer trust and deters the practice of businesses collecting payments without declaring them to LHDN.

The practical challenge for B2C businesses is the consumer request scenario. LHDN's rules require that if a consumer requests a full e-invoice, the business must provide one — and that transaction must be excluded from the consolidated invoice. This means businesses need a mechanism (typically a QR code on the receipt or a customer service process) for consumers to request individual e-invoices, and their systems must be able to generate them on demand and remove the corresponding transaction from the daily consolidated batch.