E-Invoicing Malaysia: Handling B2C Transactions and Consolidated E-Invoices
Introduction
For retailers processing hundreds or thousands of consumer transactions every day, e-Invoicing creates a practical question: does every receipt need to become an individual e-Invoice?
Under E-invoicing Malaysia guidelines, the answer depends partly on whether the buyer requests an e-Invoice and whether the transaction is eligible for consolidation. Where permitted, businesses can continue issuing normal receipts to consumers who do not request individual e-Invoices and later aggregate those transactions into a monthly consolidated e-Invoice.
For high-volume retailers, managing this correctly requires a clear process between the Point-of-Sale (POS), customer requests and LHDN's MyInvois system. QR Retail Automation (QRRA) addresses this through AgoraCloud E-Invoice (ACE), which supports B2C transactions from POS and e-commerce systems.
TL;DR
Under LHDN guidelines, eligible B2C transactions where buyers do not request individual e-Invoices can be aggregated into a consolidated e-Invoice. The consolidated document must be submitted to LHDN within seven calendar days after month-end. Buyers who want individual e-Invoices should request them within the transaction month.
Consumers can request individual e-Invoices for their eligible purchases.
Normal receipts can still be issued when no e-Invoice is requested.
Eligible unrequested transactions can be consolidated monthly.
Consolidated e-Invoices must be submitted within seven calendar days after month-end.
Certain activities and transactions cannot use consolidated e-Invoices.
How Does E-Invoicing Malaysia Apply to B2C Transactions?
E-invoicing Malaysia covers Business-to-Consumer (B2C) transactions alongside B2B and B2G transactions. For B2C sales, LHDN provides different processes depending on whether the consumer requires an individual e-Invoice or is satisfied with a normal receipt.
For retailers, this creates two common B2C scenarios:
The customer requests an e-Invoice: The retailer obtains the required buyer information and issues an individual e-Invoice for the transaction.
The customer does not request an e-Invoice: The retailer can issue a normal receipt and, where consolidation is permitted, include the transaction in a consolidated e-Invoice.
LHDN states that a normal receipt issued when the buyer does not require an e-Invoice does not itself need to be submitted for validation because that receipt is not an e-Invoice.
This allows retailers to maintain a familiar checkout experience while meeting their e-Invoicing obligations through the appropriate process.
What Happens When a B2C Customer Requests an Individual E-Invoice?
When a customer requires an e-Invoice, the supplier needs to obtain the required buyer details and submit an individual e-Invoice to LHDN for validation. Once a transaction has been issued as an individual e-Invoice, it should not also be included in the consolidated e-Invoice for that period.
For high-volume retailers, collecting customer details manually at the checkout can create delays. Digital self-service provides another approach.
AgoraCloud E-Invoice (ACE) allows customers to request an individual B2C e-Invoice by scanning a QR code on their receipt and entering the necessary details.
The process can therefore work as follows:
Customer completes the purchase.
Retailer's POS generates the receipt.
Customer scans the QR code to request an e-Invoice.
Customer enters the required information.
ACE processes the request and submits the e-Invoice for validation.
The validated e-Invoice is delivered to the customer.
QRRA states that individual B2C e-Invoices processed this way are excluded from the month-end consolidated report, preventing the same transaction from being included twice.
How Long Does a Customer Have to Request an E-Invoice?
LHDN states that a buyer who initially receives a normal receipt can request an individual e-Invoice within the month in which the transaction takes place. Buyers are encouraged to make the request as soon as possible so suppliers have sufficient time to process it.
For example, suppose a customer purchases an item on 15 August but does not request an e-Invoice at checkout. If the customer later decides that an e-Invoice is required, the request should be made by 31 August.
LHDN uses this monthly cut-off so suppliers can determine which receipts should be included in their consolidated e-Invoice.
Once the transaction month has ended and the receipt has been included in a consolidated e-Invoice, a later request may be denied in accordance with LHDN's guidance.
For retailers, having a clearly communicated request process and cut-off can reduce confusion for both customers and staff.
What Is a Consolidated E-Invoice?
A consolidated e-Invoice combines eligible transactions from buyers who did not request individual e-Invoices into a single e-Invoice submission. It allows businesses handling high volumes of B2C transactions to report those sales without generating a separate individual e-Invoice for every eligible consumer purchase.
Under LHDN's process, the retailer continues issuing normal receipts during the month.
After the month ends, eligible receipts that have not already been converted into individual e-Invoices are aggregated. The supplier then creates and submits the consolidated e-Invoice to LHDN.
The validated consolidated e-Invoice serves as the supplier's proof of income and does not need to be shared with individual customers.
When Must a Consolidated E-Invoice Be Submitted?
LHDN requires suppliers to submit their monthly consolidated e-Invoice within seven calendar days after the end of the month. Retailers therefore need to identify eligible transactions, remove those already issued as individual e-Invoices and prepare the remaining receipts for consolidation within this period.
A simplified timeline could look like this:
Stage | Example |
Consumer transactions | 1–31 August |
Individual e-Invoice requests | Within August |
Month closes | 31 August |
Eligible receipts consolidated | After month-end |
Submission deadline | Within 7 calendar days after 31 August |
The exact submission process should follow the latest LHDN e-Invoice guidelines.
LHDN also allows different approaches for presenting transactions in a consolidated e-Invoice. For example, businesses can present the summary of each receipt as separate line items or group continuous receipt reference numbers according to the permitted methods.
Whichever method is used, the relevant receipt reference numbers must be captured in the consolidated submission.
What Buyer Information Is Used for a Consolidated E-Invoice?
Because a consolidated e-Invoice represents transactions involving consumers who did not request individual e-Invoices, LHDN provides standard buyer information that suppliers use instead of entering the details of each individual consumer.
Under the current LHDN guideline, key details include:
Buyer name: General Public
Buyer TIN: EI00000000010
Registration/Identification/Passport Number: NA
Buyer address: NA
This distinguishes consolidated transactions from individual e-Invoices issued to specifically identified buyers.
The MyInvois classification code list also includes Code 004 for Consolidated e-Invoice, which businesses need to account for when configuring their submission processes.
Retailers should ensure their e-Invoicing systems follow the latest LHDN field requirements rather than manually applying outdated values.
Can Every B2C Transaction Be Included in a Consolidated E-Invoice?
No. LHDN identifies certain activities and transactions for which consolidated e-Invoices are not permitted. Businesses undertaking these activities may be required to issue an individual e-Invoice for each applicable transaction instead.
The current LHDN Specific Guideline lists restricted activities or transactions in areas including:
Sale of motor vehicles
Sale of flight tickets and private charters
Certain construction activities
Licensed betting and gaming payouts
Payment to agents, dealers and distributors
Distribution, supply or sale of electricity
Certain telecommunications services and electronic device sales
The exact restrictions and effective dates vary by category. For example, LHDN states that the restriction involving luxury goods and jewellery remains on hold until further notice, meaning consolidation is currently permitted when buyers do not request an individual e-Invoice.
Retailers should therefore check the latest LHDN Specific Guideline before assuming that every B2C receipt can be included in a consolidated submission.
What Is the Difference Between Individual and Consolidated B2C E-Invoices?
Individual and consolidated e-Invoices both form part of the Malaysian e-Invoicing framework, but they serve different situations. The key distinction is whether an e-Invoice is being issued to a specific buyer or used to aggregate eligible transactions where buyers did not request one.
Area | Individual B2C E-Invoice | Consolidated E-Invoice |
Buyer | Specific consumer | General Public |
When used | Customer requests an e-Invoice | Customer does not request one |
Buyer information | Customer details required | Standard consolidated details used |
Timing | Processed for the individual transaction | Submitted monthly |
Customer receives e-Invoice | Yes | No |
Included in consolidation | No | Represents eligible unrequested transactions |
Validation | Submitted to LHDN | Submitted to LHDN |
The appropriate treatment depends on the transaction and current LHDN consolidation rules.
For retailers, keeping these two workflows properly separated is essential. An individual transaction that has already received a validated e-Invoice should not also appear in the month-end consolidation.
Why Can B2C E-Invoicing Become Difficult for High-Volume Retailers?
B2C e-Invoicing becomes more complicated as transaction volume increases because retailers need to track which receipts remain eligible for consolidation and which customers have requested individual e-Invoices. Manual processing can become difficult when thousands of transactions are generated across stores and digital channels.
Consider a retailer operating dozens of outlets.
Throughout one month, it may need to manage:
Thousands of daily POS transactions
Customer e-Invoice requests
Buyer information
LHDN validation statuses
Rejected or invalid submissions
Receipts eligible for consolidation
Transactions that must be excluded from consolidation
Month-end reporting
If these processes depend heavily on manual checking, finance teams may spend significant time reconciling transaction records before the seven-day submission deadline.
Connecting POS, e-commerce and e-Invoicing systems can reduce the amount of manual intervention required.
How Can Automation Simplify B2C and Consolidated E-Invoices?
Automation can connect transaction data from POS and e-commerce systems with the e-Invoicing workflow, reducing the need to manually identify, prepare and track every submission. This is particularly useful for retailers processing large numbers of B2C transactions across multiple channels.
QRRA's AgoraCloud E-Invoice (ACE) supports B2C transactions from POS and e-commerce platforms.
For individual B2C requests, customers can scan a QR code and submit their information. ACE then handles the e-Invoice process while excluding that transaction from the month-end consolidated report.
For wider e-Invoice processing, ACE also provides:
Pre-submission error validation
LHDN submission and validation tracking
Notifications when errors require correction
Automatic delivery of validated e-Invoices
Real-time invoice status dashboards
Integration with multiple billing systems
End-of-day e-Invoice status summaries
This helps retailers create a clearer separation between individual customer requests and transactions that remain eligible for consolidation.
What Should Retailers Check Before Month-End Consolidation?
Retailers should confirm that the transactions being consolidated are eligible, complete and have not already been issued as individual e-Invoices. They also need sufficient time to prepare and submit the consolidated e-Invoice within LHDN's seven-calendar-day deadline.
A practical month-end review should cover:
Which receipts have already been converted into individual e-Invoices?
Which customers did not request individual e-Invoices?
Are any transactions subject to restrictions on consolidation?
Are receipt reference numbers properly recorded?
Are individual e-Invoices excluded from the consolidated report?
Does the consolidated document contain the required buyer information?
Are validation errors being identified before submission?
Can the final submission be completed within seven calendar days?
For retailers with multiple outlets, establishing this workflow before month-end can reduce the amount of reconciliation required during the submission window.
Frequently Asked Questions
1. Do retailers need to issue an e-Invoice for every B2C transaction?
Not necessarily. Under LHDN guidelines, where consolidation is permitted and a buyer does not request an individual e-Invoice, the supplier can issue a normal receipt and later include the eligible transaction in a monthly consolidated e-Invoice. Certain activities and transactions are excluded from consolidation.
LHDN states that a buyer can request an e-Invoice after receiving a normal receipt within the month of the transaction. Buyers are encouraged to make requests as soon as possible. This cut-off allows suppliers to determine which receipts should subsequently be included in the consolidated e-Invoice.
When must businesses submit a consolidated e-Invoice?
A consolidated e-Invoice must be submitted to LHDN within seven calendar days after the end of the month. It covers eligible transactions from the previous month where buyers did not require individual e-Invoices. Businesses should allow enough time for reconciliation and validation before the deadline.
Does a consolidated e-Invoice need to be sent to every customer?
No. LHDN states that the validated consolidated e-Invoice serves as the supplier's proof of income and does not need to be shared with individual buyers. It is issued to the General Public rather than a specific consumer.
Can a transaction appear in both an individual and consolidated e-Invoice?
It should not. Once an individual e-Invoice has been issued for a B2C transaction, that transaction should be excluded from the consolidated submission. QRRA's ACE solution specifically excludes individual B2C e-Invoices from the month-end consolidated report to help maintain this separation.
Conclusion
Managing B2C transactions under E-invoicing Malaysia requires retailers to separate customers who request individual e-Invoices from eligible transactions that can be consolidated. Under the current LHDN guideline, buyers can request an individual e-Invoice within the transaction month, while eligible remaining receipts can be aggregated and submitted within seven calendar days after month-end.
For retailers processing high transaction volumes, the challenge is not simply generating an e-Invoice. It is keeping POS transactions, individual requests, validation statuses and month-end consolidation properly connected.
QR Retail Automation's AgoraCloud E-Invoice (ACE) supports B2C consolidation alongside individual B2C e-Invoice requests from POS and e-commerce transactions. If your business needs a more automated way to manage LHDN e-Invoicing requirements, request a demo from QRRA to explore how ACE can integrate with your existing billing environment.
Comments