Automotive
Sale of motor vehicles — cars, motorcycles, lorries. Each unit is an individual e-invoice, regardless of buyer type.
If you run a kopitiam, a kedai runcit, or any business that sells over the counter, you don't issue a MyInvois e-invoice for every teh ais. You roll them up — once a month, one submission, a few hundred receipts collapsed into a single document. Here's exactly how that works.
×3,000+ like this, every month.
One monthly submission.
Updated July 2026 · Reviewed by MIA-registered accountants
A consolidated e-invoice is one monthly MyInvois submission that summarises every counter sale where the customer didn't ask for an individual e-invoice.
You submit it within 7 calendar days of the following month. Sales in April → submit by 7 May.
The buyer's TIN is a generic 'EI00000000010' and the buyer name is 'General Public'. You don't need to know who bought what.
You still keep the underlying receipts — POS Z-reports, till tapes, or your own log. LHDN can ask to see them in an audit.
Some industries cannot consolidate (automotive, aviation, luxury, construction, licensed gaming, commission-paid agents). For them, every sale is an individual e-invoice.
If a customer asks for an individual e-invoice mid-month, you issue it on the spot — and exclude that sale from the month-end rollup.
A consolidated B2C e-invoice is LHDN's concession to reality: you can't realistically issue a separate MyInvois submission for every walk-in customer who bought RM3.50 worth of teh tarik. So the rule is: you issue one rolled-up e-invoice per month that covers all those small, anonymous counter sales together, and submit it to MyInvois within 7 days of month-end.
The receipt your customer gets at the counter doesn't change. Your till / POS still prints whatever it prints. What's new is that at the start of every month, you summarise last month's counter takings and send that summary (not the individual receipts) to LHDN.
Most micros can. But LHDN has carved out a handful of industries where individual e-invoices are mandatory — even for a single RM50 transaction, even if the customer hasn't asked. If you're in one of these, consolidated B2C is off the table.
Sale of motor vehicles — cars, motorcycles, lorries. Each unit is an individual e-invoice, regardless of buyer type.
Flight tickets and aviation services. Applies to airlines and to travel agents reselling flights.
Jewellery, gems, precious metals sold as luxury goods, and similar high-value items.
Construction contractors and related billed services. Construction materials are still consolidable — the services are not.
Lotteries, number-forecast operators, licensed betting, and gaming outlets.
Payments to commission agents, dealers, and distributors — typically insurance, MLM, property.
Every month looks the same. You collect receipts all month, then have a one-week window after month-end to submit. Miss it and the submission counts as late — same penalty exposure as any other missed e-invoice.
Your till / POS / manual receipt book captures every walk-in sale. Keep the Z-reports, till tapes, or a signed log. This is your audit trail — not the consolidated e-invoice itself.
Total up the month. Separate consolidated-eligible sales from any B2B invoices you already issued individually, and from any opt-in requests you handled mid-month.
Generate a single MyInvois submission: buyer = General Public, TIN = EI00000000010, description = summary or receipt-range, amount = total. Submit by day 7 or you're late.
LHDN returns a UUID and a QR code. Nothing to hand out — the buyer is the public. But keep the validated PDF with your records. Auditors will want to match it to the till tapes it summarises.
Note Recommended cadence: pick the 3rd or 4th of the month to submit, not the 7th. Gives you a buffer if the MyInvois API has a bad day — which it does, a few times a year.
A consolidated e-invoice uses the same Peppol schema as any other MyInvois submission. The values below are the ones that specifically identify it as a consolidated B2C.
EI00000000010
General Public
NA
NA
NA
Receipt range or summary
One line per category
Per your industry
If registered
To make it concrete. Pak Lim runs a 4-table kopitiam in Pudu — comfortably under the RM1m exemption. But his one corporate regular (a nearby office that orders lunch for 15 every Friday) needs e-invoices to claim the expense, so Pak Lim opted in. Once you opt in, every sale counts, including hundreds of walk-ins. Here is how consolidation keeps that sane.
April 2026. 30 days. Roughly 3,200 counter transactions averaging RM8 each. Total counter revenue: RM26,400. Plus 4 invoices to the office regular for RM420 each. Plus one off-menu catering job for an old friend who asked for an e-invoice.
Rolled into one e-invoice dated 30 April, submitted by 7 May. Buyer: General Public. Lines: "F&B dine-in — RM19,800", "F&B takeaway — RM6,600". TIN: EI00000000010.
Already issued live each Friday. Buyer TIN = the office's corporate TIN. Each submission has its own UUID. Don't include these in the consolidated rollup.
The friend asked for an e-invoice with her TIN for claim purposes. Pak Lim issued it on the spot. Also excluded from the consolidated rollup.
The deadline is 7 calendar days after the calendar-month-end. Not 30 days. Not end of next month. Put it on your phone as a recurring reminder for the 4th of every month.
Any sale you already issued an individual e-invoice for (mid-month B2B, opt-in requests) must be excluded from the consolidated total. Your POS probably doesn't flag these automatically; you have to track it.
The buyer name is a specific, literal string. Variations fail validation. Same for the placeholder TIN — it's exactly EI00000000010, with the zeros, no spaces, no dashes.
The consolidated e-invoice summarises your till tapes, Z-reports, and receipt books; it doesn't replace them. If LHDN audits, they want to see both the submission and what it's built from.
The pillar guide. Read it first if nothing above made sense.
Exempt, or in scope? Where a micro lands.
The other micro-oriented workflow. Different beast.
Forward your daily Z-report into WhatsApp, or let Kiira pull from your POS. On day 1 of the following month, Kiira builds the consolidated e-invoice for you (total, line items, receipt range) and waits for your tap before it hits LHDN.