A Malaysia consolidated e-Invoice is a single e-Invoice that aggregates a month's transactions with buyers who did not ask for their own e-Invoice, submitted to the Inland Revenue Board of Malaysia (Lembaga Hasil Dalam Negeri Malaysia, or IRBM) through MyInvois within 7 calendar days after the month ends. The permission to consolidate stops where IRBM's exclusions apply: if the transaction falls into a category listed in Table 3.6, or if a single transaction exceeds RM10,000 from 1 January 2026, the supplier must issue an individual e-Invoice instead. Those two bars bind businesses whose interim relaxation period has ended. Businesses in the up-to-RM5 million implementation phase may still consolidate every transaction until 31 December 2027, and businesses with annual turnover or revenue below RM3 million are exempt from e-Invoicing altogether unless a shareholder, holding company or related company at RM3 million or more brings them into scope. For businesses in scope, the process also includes serially numbered receipts and a receipt reference number for each sale inside the consolidated submission.
Most businesses need that answer first. If your team still needs the mandate-level rollout dates, exemption thresholds, and cross-border scope that sit above these monthly rules, start with Malaysia's broader 2026 e-Invoice requirements. The harder part is applying it inside live MyInvois workflows, especially in B2C and receipt-heavy environments where thousands of transactions may move through the same point-of-sale system in a month. A retailer, service outlet, or finance team cannot decide based on "monthly consolidation is allowed" alone. The real decision depends on five checks:
- Is the business in scope for e-Invoicing, and has its interim relaxation period ended?
- Did the buyer request an individual e-Invoice within the month of the transaction?
- Does the transaction fall into a Table 3.6 exclusion?
- Does a single transaction exceed RM10,000?
- Is each serially numbered receipt reference ready to carry into the consolidated record?
This guide therefore treats the rule as an operating decision, not a headline update. The goal is to help you classify each transaction correctly, keep the right source records, and avoid mixing consolidatable and non-consolidatable sales inside the same monthly process.
When Monthly Consolidation Is Still Allowed
The baseline rule is narrower than many summaries make it sound. A supplier may issue a monthly consolidated e-Invoice when the buyer does not require an individual e-Invoice for that transaction. The buyer receives a normal receipt, and that receipt is not submitted to IRBM for validation. In practical terms, monthly consolidation is still part of the Malaysia e-Invoice framework for many lower-value, receipt-driven transactions, but only while no other override applies.
The first override is the buyer request itself. If a customer asks for an e-Invoice for a specific sale, that transaction should branch out of the monthly batch and into the individual issuance workflow. This is the part many finance teams miss when they treat consolidation as a blanket setting at the store or account level. It is not a blanket setting. It is a transaction-level outcome that depends on what happened for that sale.
The request has a cut-off: the buyer must ask within the month of the transaction, which gives the supplier a fixed point to close the month's receipts into the consolidated e-Invoice. In IRBM's own example, a buyer who asks on 1 October for an e-Invoice covering a 30 September purchase may be refused, because September's consolidated e-Invoice has already been issued. A business still in its interim relaxation period may decline individual requests altogether, provided it issues its consolidated e-Invoices.
For businesses processing high volumes of B2C transactions, the cleanest way to think about the buyer-request e-Invoice workflow is:
- Capture the sale.
- Check whether the buyer requested an individual e-Invoice within the month.
- If yes, issue individually.
- If no, test the sale against the exclusion rules and value threshold before letting it stay in the monthly consolidated pool.
That distinction matters across B2B, B2C, and B2G settings, since IRBM allows consolidation for all three. The permission to consolidate exists, but it only survives if the transaction clears the other rule gates. Once you treat buyer requests as a front-end capture issue instead of a back-office cleanup issue, the rest of the process becomes much easier to control.
What a Consolidated e-Invoice Contains and When It Is Due
A consolidated e-Invoice is due within 7 calendar days after the end of the month it covers, so September's receipts are submitted by 7 October. IRBM provides for consolidation on a monthly basis. Once validated, the consolidated e-Invoice serves as the supplier's proof of income: IRBM notifies only the supplier, and the document does not need to be shared with the buyers whose receipts it covers.
The buyer details are fixed values, set out in Table 3.5 of the IRBM e-Invoice Specific Guideline Version 4.9 (7 September 2026):
| Field | Value in a consolidated e-Invoice |
|---|---|
| Buyer's Name | General Public |
| Buyer's TIN | EI00000000010 |
| Buyer's Registration / Identification / Passport Number | NA |
| Buyer's Address | NA |
| Buyer's Contact Number | NA |
| Buyer's SST Registration Number | NA |
| Description of Product or Service | The receipt reference number for each transaction |
The code tables in IRBM's MyInvois SDK add classification code 004 (Consolidated e-Invoice) and state code 17 (Not Applicable). The supplier's own details and the remaining required fields are completed as on any other e-Invoice.
IRBM allows three ways to present the line items, alone or in combination:
- one line per receipt, carrying that receipt's summary
- one line per continuous run of receipt numbers, starting a new line wherever the number chain breaks
- a consolidated e-Invoice per branch or location, using either of the first two methods for that branch's receipts
A single submission is capped at 5MB and 100 e-Invoices, and each e-Invoice at 300KB, so a high-volume business may split one month's receipts across several consolidated e-Invoices.
Who These Rules Bind in 2026 and 2027
Two changes since the mandate's rollout decide whether the Table 3.6 and RM10,000 bars apply to a given business yet.
The first is the exemption threshold. Under section 1.6.1(e) of IRBM's e-Invoice Guideline Version 4.8 (30 August 2026), taxpayers with annual turnover or revenue below RM3 million, raised from RM1 million, are exempt from issuing e-Invoices, and IRBM confirms that exempt taxpayers are not required to issue consolidated e-Invoices either. The exemption does not apply to a business with a non-individual shareholder, a holding company, or a related company or joint venture whose own annual turnover or revenue is RM3 million or more. A business whose implementation date has been determined keeps its obligation even if its turnover later falls below RM3 million.
The second is the interim relaxation period each implementation phase received:
| Implementation phase (annual turnover or revenue) | Interim relaxation ends |
|---|---|
| More than RM100 million | 31 January 2025 |
| More than RM25 million and up to RM100 million | 30 June 2025 |
| More than RM5 million and up to RM25 million | 31 December 2025 |
| Up to RM5 million (1 January 2026 and 1 July 2026 implementation dates) | 31 December 2027 |
During relaxation, a business may issue consolidated e-Invoices for all its transactions, Table 3.6 activities and sales above RM10,000 included. It may enter any details in the Description field instead of receipt reference numbers, and it may decline a buyer's request for an individual e-Invoice. Consolidated e-Invoices must still be issued every month, not once at the end of the period. The relaxation is optional, so a business that is ready can issue individual e-Invoices now.
The Table 3.6 and RM10,000 rules below are therefore fully live for the three larger phases today, and they reach the up-to-RM5 million phase on 1 January 2028.
The Transactions That Cannot Be Consolidated
This is where Malaysia consolidated e-Invoice exclusions matter more than general summaries. The key source is Table 3.6 of the same Specific Guideline, which lists the activities that require an e-Invoice for each transaction and so cannot stay inside monthly consolidated treatment.
The most important 2026 change is direct: from 1 January 2026, any single transaction above RM10,000 requires an individual e-Invoice once the business's relaxation period has ended. That rule applies even if your business normally uses monthly consolidation for smaller transactions. A finance team that misses this threshold can end up combining records that should have been issued separately.
The exclusion list also covers categories that operators should classify carefully at source:
- automotive: the sale of any motor vehicle, trailers included
- aviation: flight tickets and private charter
- construction contracts
- licensed betting and gaming: pay-outs to winners, although casino and gaming-machine pay-outs are exempt from e-Invoicing until further notice
- payments to agents, dealers, or distributors
- electricity service providers: the distribution, supply, or sale of electricity
- telecommunication: postpaid plans, internet subscriptions, and the sale of electronic devices
- luxury goods and jewellery, a row IRBM has put on hold, so these sales may still be consolidated until further notice when the buyer does not ask for an e-Invoice
These are not minor footnotes. They change how the transaction must be routed. If you run a mixed workflow, the question is not "Do we use consolidated e-Invoices?" The better question is "Which transactions can stay in the monthly batch, and which ones must immediately branch into individual issuance?"
The electricity and telecommunication rows took effect on 1 January 2026, and both are narrower than they first look. The electricity row applies only to electricity service providers, and no other utility appears in the table. The sale of electronic devices sits in the telecommunication row, alongside postpaid plans and internet subscriptions, rather than in a general retail row. Telecom operators often process these sales through the same systems as ordinary retail or service receipts, which makes it easy to assume the same monthly method still applies. Under the guideline, they need separate classification logic. Where an individual buyer in a Table 3.6 activity has no TIN, IRBM accepts a MyKad, MyTentera, MyPR, or MyKAS number instead.
Receipt References, MSME Rules, and the Monthly Submission Record
The receipt side of the rule is what turns Malaysia consolidated e-Invoice rules into a document-control problem. According to IRBM's e-Invoice General FAQs, updated 4 September 2026, MSMEs may issue a consolidated e-Invoice for the previous month's transactions, and MSMEs with annual gross takings above RM150,000 must issue serially numbered receipts under section 82(1)(b) of the Income Tax Act 1967 and include the receipt reference number in the consolidated e-Invoice (question 109).
That receipt reference is more than an administrative field. It is the link between the monthly submission record and the underlying source transaction. If a business cannot trace the consolidated line back to the receipt, review and reconciliation become harder, especially in point-of-sale systems where many small transactions are posted every day.
The RM150,000 line now sits beneath the RM3 million exemption. A business in scope is usually there because its turnover is at least RM3 million, far above RM150,000, so the serial-receipt duty applies to almost every business that issues consolidated e-Invoices. The FAQ's other half, that MSMEs below RM150,000 need neither receipts nor a consolidated e-Invoice, matters mainly to a small business brought into scope through a shareholder, holding company, or related company.
During the interim relaxation period, the Description field does not have to carry receipt numbers. Keeping the references anyway leaves each consolidated line traceable to its sale and the process ready for the day relaxation ends.
In practice, that means your monthly file should be backed by a defensible record set: serially numbered receipts where required, source invoices or bills where relevant, exception notes for transactions moved out of the consolidated pool, and a clear mapping between receipt numbers and the data submitted through MyInvois. If your filing discipline is weak, start with a practical system for organizing invoices and receipts before month-end volumes make the gaps harder to fix.
Correcting and Self-Billing Consolidated e-Invoices
A consolidated e-Invoice is adjusted like any other: a credit note, debit note, or refund note e-Invoice can reference it, and one note can adjust several original e-Invoices at once. Transactions left out of a consolidated e-Invoice issued during relaxation are put right within IRBM's e-Invoice Special Voluntary Disclosure Programme (SVDP), which runs from 7 July 2026 to 31 December 2027. The supplier either issues a credit note against the original and a new consolidated e-Invoice covering every transaction for that period, or issues a separate consolidated e-Invoice for the omitted transactions alone.
Self-billed e-Invoices are not normally consolidated. The exceptions are payments to individuals who are not conducting a business, interest paid to the public at large, insurance claim, compensation, or benefit payments to such individuals or to government bodies, and transactions involving the taxpayer's own overseas branches or offices. A consolidated self-billed e-Invoice follows the same 7-day monthly deadline and places the fixed values on the supplier side instead: "General Public", TIN EI00000000010, and "NA" for the other identity fields. During relaxation, consolidation is open to every self-billed circumstance. The self-billing cases businesses meet most, such as foreign suppliers and imported services, are covered in Malaysia self-billed e-Invoice requirements.
How to Separate Consolidatable and Non-Consolidatable Transactions in Practice
The safest operating model is to treat consolidation as the last step, not the default from the moment a document appears. A workable workflow usually looks like this: ingest the transaction record, capture whether the buyer requested an individual e-Invoice, classify the sale against Table 3.6 and the RM10,000 threshold, route it either to individual issuance or the monthly consolidated batch, and keep the supporting files attached for review before submission. If you are designing the submission layer behind that routing, map it against a MyInvois API integration workflow for authentication, TIN checks, and polling before you lock the process.
This matters because the compliance risk is usually created by mixed data, not by one obviously wrong invoice. A point-of-sale export may contain ordinary B2C receipts, a buyer-request exception, a sale in a Table 3.6 category, and a higher-value sale that exceeds RM10,000. Self-billed payments recorded alongside them raise the same control issue. If those records move through one undifferentiated queue, the business can easily misstate which transactions were eligible for consolidation.
Teams usually get better control when they separate records by trigger:
- Buyer request within the month: issue individually.
- Table 3.6 exclusion, after relaxation: issue individually.
- Single transaction above RM10,000 from 1 January 2026, after relaxation: issue individually.
- No override and no exclusion: keep in the monthly consolidated pool.
- Receipt-reference obligation applies: preserve the serial receipt number and map it into the consolidated record.
Supporting evidence should stay with that routing logic. Receipts, invoices, utility bills, and exception logs should not sit in unrelated folders or email threads if they support monthly review. Many teams choose to automate receipt and invoice data extraction for compliance-heavy workflows so the classification file, exported fields, and supporting-document references stay easier to reconcile. In that context, Invoice Data Extraction is useful as an example because it can process mixed batches of receipts, invoices, and utility bills into Excel, CSV, or JSON, while keeping source-file and page references in the output for cross-checking during finance review.
A Quick Decision Framework for Retail, Utilities, and Regional Finance Teams
If you want a fast way to test your workflow, apply the rule to specific cases:
- Small retail sale, no buyer request, not in an excluded category: this can usually remain in the monthly consolidated e-Invoice process.
- Single sale above RM10,000 on or after 1 January 2026: this requires an individual e-Invoice once the business's relaxation period has ended, even if similar lower-value sales are still consolidated.
- Electricity sold by an electricity service provider, or a telecom postpaid plan, internet subscription, or electronic-device sale: classify it against the Table 3.6 rule set first, because these rows have applied since 1 January 2026 and should not be treated like ordinary receipt-driven sales.
- Business in the up-to-RM5 million phase: it may still consolidate all of the above until 31 December 2027, but its consolidated e-Invoice remains due every month.
- Business below RM3 million with no shareholder, holding company, or related company at RM3 million or more: it is exempt from e-Invoicing, so no consolidated e-Invoice is required.
- Buyer asks for an e-Invoice for one transaction within the month: that sale moves out of the monthly pool and into individual issuance, regardless of how the rest of the day's receipts are handled.
For most teams, the first implementation priorities are clear: confirm the business's phase and when its relaxation ends, capture buyer requests at the point of sale, flag excluded categories before month-end, monitor the RM10,000 threshold at transaction level, and preserve receipt references and supporting files in a form your finance team can actually review.
If your team works across jurisdictions, it can also help to compare how other receipt-heavy regimes structure the evidence trail, such as South Korea's cash receipt rules versus tax invoices, Vietnam's e-invoice timing and correction requirements, or Indonesia's Coretax e-Faktur workflow. Those comparisons are not substitutes for IRBM guidance, but they can sharpen how you design regional finance controls.