The Inland Revenue Board (LHDN/IRBM) requires structured, machine-readable invoices with real-time checks via MyInvois starting 1 August 2024. This change affects B2B, B2C, and B2G flows and brings a new Unique Identifier Number plus QR code for each validated document.
Who must act? Businesses with annual turnover above RM1,000,000 join the phased rollout by turnover band. Those below the threshold have an exemption for now, but rules can change.
Day-to-day, mandatory means your billing must be structured data sent for instant validation. Expect adjustments to AR/AP workflows, reporting, and vendor integration.
This guide previews format rules, required fields, the MyInvois portal versus API options, consolidation rules, and self-billing cases. It also outlines penalties under the Income Tax Act 1967 and possible tax incentives to offset implementation costs.
Key Takeaways
- Real-time validation via MyInvois becomes active from 1 Aug 2024 for phased groups.
- Structured e-invoicing replaces PDFs; each invoice gets a Unique Identifier and QR code.
- Turnover determines your start date; RM1,000,000 is the current exemption threshold.
- Non-compliance risks fines and possible imprisonment under tax law.
- Prepare AR/AP systems now; API or portal options support different business needs.
Malaysia e-Invoicing mandate overview from LHDN and the Inland Revenue Board
LHDN now requires invoices to pass a clearance check through MyInvois before they count as validated tax documents. This clearance-style model means submitted billing data is checked and stamped with a Unique Identifier, a timestamp, and a QR code when accepted.
What real-time validation through MyInvois means for businesses
The process runs like a gateway. You submit invoice data, receive an acceptance or rejection, and then continue with delivery or fix errors.
This avoids delayed revenue recognition when systems handle failures quickly. Notifications go to supplier and buyer via portal or Notification API depending on the chosen route.
Scope: which transactions are covered
All B2B, B2C, and B2G transactions are validated near real time. Selected non-business transfers between individuals may also be covered.
- Gain: a stronger audit trail and standardized data for tax checks.
- Trade-off: tighter timing and higher data discipline across quote-to-cash and procure-to-pay workflows.
- Submission paths: portal for manual/bulk uploads; API for automated high-volume flows.
| Feature | Result | Impact |
|---|---|---|
| Clearance model (LHDN) | Unique Identifier + QR | Better auditability |
| Real-time checks | Immediate accept/reject | Faster error handling |
| Covered transactions | B2B, B2C, B2G | Broad taxpayer reach |
Is e-Invoice Mandatory in Malaysia?
Start by checking whether your yearly sales cross the RM1,000,000 line — that figure decides your scope. If annual turnover meets or exceeds rm1 million, the clearance requirement applies under the phased rollout. Businesses below that mark are exempt for now.
The RM1 million annual turnover revenue threshold and who is exempt
Key threshold: obligation kicks in when annual turnover revenue is RM1,000,000 or above; below that, firms remain outside the requirement per current guidance.
Common exemptions include individuals not carrying on a business and certain statutory or international bodies with limited treatment. Mixed entities should confirm their taxable activity to avoid surprises for taxpayers annual reporting.
When voluntary participation makes sense
Opting in early helps test data quality and smooth processes before your mandated phase. Consider this if you have high invoice volume, multi-branch operations, ERP readiness, or strong customer demand to issue e-invoice validated documents.
- Criteria: invoice volume, multi-site billing, ERP integration, audit posture.
- Implementation note: prepare buyer details, required fields, and rejection handling workflows.
“Confirm your turnover and choose a path that matches operational readiness and compliance appetite.”
How the phased implementation timeline works (August 2024 through January 2026)
The rollout unfolds across four clear windows, each tied to annual turnover bands and firm start dates.
Below is a simple guide to match your turnover band to the mandate date. Use this to set milestones and assign owners.
- Phase 1 — > RM100 million: 1 August 2024 (relaxation until 31 January 2025).
- Phase 2 — RM25m to RM100m: 1 January 2025 (relaxation until 30 June 2025).
- Phase 3 — RM5m to RM25m: 1 July 2025 (relaxation until 31 December 2025).
- Phase 4 — RM1m to RM5 million: 1 January 2026, with an extended relaxation window through 31 December 2026.
What the interim relaxation period means: this window gives businesses time to stabilise systems and workflows after the official start date.
Still, aim for compliance before the end of the relaxation. Early readiness reduces rejection risks and lowers remediation costs.
“Treat the timeline as a project plan: map data, test systems, train users, and onboard partners ahead of your date.”
Action tip: schedule backward from your phase date for data mapping, integration, training, and vendor testing. Next, confirm how LHDN defines annual turnover to determine your exact start date.
How to determine your annual turnover and your start date
Confirming which financial year LHDN uses is the first step to pinpoint your start date. The authority will use audited financial statements for FY2022 where available. If audited accounts are not available, the annual revenue shown on the YA2022 tax return is used instead.
Documents and the year of assessment
Pull audited accounts, company financials, and YA2022 tax filings now. These documents establish your official annual turnover for phasing. If your accounting year-end changed, LHDN prorates the figure to a 12-month comparable basis.
The “second year after” rule
Plan ahead: if your revenue crosses the threshold in Year X, you start compliance in Year X+2. That gives smaller firms time to budget and test systems.
Sole proprietors and aggregation
Sole proprietors must combine revenue across all owned businesses. Aggregated turnover revenue can move a taxpayer into scope even if each business alone sits below the line.
Once in scope, you stay in scope
Once required to implement, a taxpayer remains subject to the rules even if annual turnover later falls below RM1,000,000. Use this rule to avoid false assumptions after a slow year.
Action tip: verify audited accounts and YA figures today to lock in the correct start date and avoid mis-phasing.
Core LHDN e-Invoice requirements you must meet
Start with the technical baseline: every billing document must be issued as structured UBL 2.1 using XML or JSON. PDFs or image files alone will not meet the requirements for submission and clearance.
Required fields and common gaps
Each e-invoice contains 55 fields; sources note about 37 are strictly mandatory. Prepare seller and buyer identifiers, item codes and descriptions, quantities, unit prices, tax calculations, totals, and payment terms.
Frequent data gaps that delay validation include missing buyer TIN or address, inconsistent item descriptions, incorrect tax totals, and rounding mismatches between systems.
Digital signature and certificate
All e-invoices must be digitally signed with a Digital Certificate issued by IRBM. The certificate ties to the taxpayer TIN, verifies document integrity, and supports non-repudiation during API or portal submission.
“Keep master data clean, assign owners, and treat the digital certificate as a critical control.”
Minimum viable compliance checklist
- Produce UBL 2.1 XML/JSON output from your billing system.
- Populate the 55 fields; verify the 37 mandatory ones first.
- Apply IRBM Digital Certificate for signing before submission.
- Assign data stewards for customer/vendor master records.
- Log and act on validation errors; use credit/debit notes for post-acceptance fixes.
| Item | Requirement | Common issue | Fix |
|---|---|---|---|
| Format | UBL 2.1 XML or JSON | PDF sent as “e-invoice” | Export structured file from ERP |
| Fields | 55 fields (≈37 mandatory) | Missing buyer TIN/address | Centralize master data |
| Signature | IRBM Digital Certificate | Unsigned payloads | Install cert and automate signing |
Note: These points form the minimum checklist that applies whether you use the MyInvois Portal or an API.
Choose your submission model: MyInvois Portal vs Application Programming Interface
Pick a submission model that balances speed and technical effort for your billing flows.
MyInvois Portal is free to use and best for low-volume teams. Manual entry works for occasional invoices. The portal also supports bulk upload via a prescribed spreadsheet format. That lets SMEs reduce repetitive typing without a full integration.
When to choose API integration
An application programming interface links your ERP, billing, or accounting software directly to MyInvois. This route automates invoice generation, transmission, and real-time response handling.
Tradeoffs: API needs upfront engineering, monitoring, and a digital certificate. It pays off when volume, speed, or multi-entity billing makes manual work impractical.
Reduce effort with the SDK
LHDN provides a Malaysia e-Invoice SDK to standardize mapping and validation logic. The SDK shortens development time and eases integration with different software stacks.
“Choose model, confirm digital certificate readiness, map required fields, run pilots, then scale after stable validation.”
- Quick start: use the portal and bulk upload for low volume.
- Scale: adopt the application programming interface for automation and high transaction load.
- Speed up integration: use the SDK to reduce engineering effort and errors.
Step-by-step e-Invoicing process for B2B transactions
A reliable step-by-step flow helps suppliers move invoices from draft to accepted status without delays.
Issuance: create and submit
1) Supplier generates the e-invoice in XML/JSON from the billing system or via manual entry on the myinvois portal.
2) Submit the file through the portal or the API endpoint provided by the myinvois system.
Validation and identifiers
IRBM validates the payload in real time and returns a status. On acceptance, a Unique Identifier Number, timestamp, and QR code are attached.
Why this matters: these items form an auditable trail and let anyone verify the invoice status quickly.
Notifications and delivery
Supplier and buyer receive notifications via portal, email, or Notification API depending on the chosen route. Check both AR inboxes and the myinvois portal for status updates.
Human-readable copies
After validation, suppliers may send a PDF or JPG copy to the buyer for filing. The structured e-invoice remains the legal record; the human-readable copy is for convenience.
Rejection and the 72-hour window
Buyers may request rejection and suppliers can cancel an accepted submission within 72 hours with written justification.
After 72 hours the document is treated as accepted. If changes are needed, issue a new invoice or a credit/debit note per tax rules.
- Set internal SLAs for handling rejections within 24 hours.
- Monitor validation failures daily and assign an approver for cancellations.
- Keep a clear log of justification when cancelling inside the 72-hour window.
Operational tip: automate alerts from the myinvois system and map roles for fast remediation to reduce revenue impact.
How to handle B2C and B2G transactions without slowing down operations
Frontline checkouts must stay swift while back-office controls gather required data for compliance. Keep customer flow fast and collect extra buyer details only when necessary. Use optional prompts at point of sale so most transactions finish in seconds.
When the buyer requests an e-invoice
If a buyer asks for a validated document, capture their TIN, name, and contact quickly. Trigger the myinvois portal or API to generate and submit the structured payload in real time. On acceptance, share the validated copy and QR/Unique Identifier with the buyer via email or SMS.
When the buyer does not request an e-invoice
Most consumers will accept a standard receipt. Continue issuing fast receipts at checkout and tag those transactions for later aggregation.
At night, consolidate receipts into a single monthly submission. This preserves a quick customer experience while keeping your invoicing records compliant.
B2G and stronger documentation needs
Government buyer transactions usually need stricter proof and faster traceability. For these, prefer API automation over manual portal steps to reduce errors and delays.
Operational tip: use POS prompts, optional data fields, and nightly reconciliation jobs to balance speed and compliance.
| Scenario | Frontline action | Back-office handling |
|---|---|---|
| Buyer requests validated invoice | Capture TIN, name, contact; call myinvois portal/API | Submit real-time, share validated copy |
| Buyer does not request | Issue standard receipt quickly; tag for consolidation | Aggregate monthly, submit consolidated e-invoice |
| B2G transaction | Collect full documentation at sale | Prefer API automation; reconcile immediately |
Next step: see the consolidated invoicing rules for timing, the RM10,000 threshold from Jan 2026, and restricted industries that affect monthly aggregation.
Consolidated e-invoice rules and the RM10,000 change effective January 2026
Consolidated filing keeps high-volume retail flows efficient while preserving a clear audit trail.
What a consolidated document is and why it exists
A consolidated e-invoice bundles multiple small sales into one structured record for reporting. LHDN allows this to speed checkout and reduce overhead for high-volume sellers.
Major rule change for high-value sales
From 1 January 2026, any transaction above RM10,000 must be issued as an individual e-invoice. Update POS logic so large lines auto-split or trigger a separate issuance immediately.
Industry limits and the key exception
Certain sectors cannot use consolidation: automotive, aviation, luxury goods/jewellery, construction, licensed betting/gaming, and agent/distributor payments.
Electricity providers and postpaid telecom/device plans also move to individual documents from the same date.
Exception: wholesalers and retailers of construction materials may consolidate unless a single transaction exceeds RM10,000 or the buyer asks for an individual record.
Submission timing and operational tips
Consolidated e-invoices must be filed within seven calendar days after month-end. Set internal cutoffs earlier and run reconciliation checks before submission.
- Tag eligible sales at POS.
- Auto-separate >RM10,000 lines.
- Run month-end validation and submit within the seven-day window.
“Treat monthly consolidation as a compliance task with fixed cutoffs and clear owner responsibility.”
| Rule | Action | Impact |
|---|---|---|
| Transaction > RM10,000 | Issue individual e-invoice | Immediate POS change; fewer consolidations |
| Restricted industries | No consolidation allowed | Issue individual records for most sales |
| Consolidated filing deadline | 7 calendar days after month-end | Set earlier internal cutoffs to avoid late submission |
Types of e-invoices you must be able to issue and manage
Your finance team must support more than sales invoices; adjustments and buyer-issued records matter too.
Required documents include standard invoices and self-billed invoices that prove income or record expenses. Self-billed documents arise when the buyer issues the invoice for purchases, often for agent, consignment, or import scenarios.
Credit, debit and refund notes for post-issuance adjustments
After the 72-hour acceptance window, you cannot edit the original validated record. Instead issue a credit note to reduce value, a debit note to increase charges, or a refund note to document money returned.
Examples: a returned product uses a credit note; a missed fee needs a debit note; a paid refund triggers a refund note. Each must reference the original Unique Identifier and reason code.
Governance and audit trail
Keep a clean chain: always link adjustment documents to the accepted e-invoice. Avoid manual edits that break the validation chain and complicate tax audits.
“Reference the original validated invoice on every adjustment and retain signed payloads for audit.”
- Ensure systems generate invoices, self-billed invoices, credit notes, debit notes, and refund notes in UBL 2.1.
- Validate each document through MyInvois and capture status, Unique Identifier, and timestamp.
- Store signed XML/JSON payloads and human-readable copies for audit support.
| Document type | When used | Audit note |
|---|---|---|
| Invoice | Standard sales; proof of income | Link to Unique Identifier; keep signed payload |
| Self-billed invoice | Buyer issues for expenses (agents, imports) | Buyer must retain proof and mapping to supplier |
| Credit/Debit note | Post-acceptance price correction or return | Reference original document; include reason code |
| Refund note | Cash refunds or returned payments | Record refund method and link to original invoice |
Cross-border and self-billed scenarios Malaysian taxpayers should prepare for
When foreign suppliers cannot issue a local validated record, the onus often shifts to the Malaysian purchaser. This creates a common compliance gap for taxpayers handling imports or cross-border services.
Imports and foreign suppliers: when buyers must self-bill
If a nonresident supplier cannot submit a compliant payload, the domestic taxpayer must generate a self-billed e-invoice that meets clearance rules. Collect seller identity, tax identifiers, shipment details, item descriptions, values, and tax treatment before issuing the document.
How it becomes proof: sign and submit the structured file, capture the Unique Identifier, and retain the signed payload as expense evidence for tax audits.
Common self-billing situations and sensitive cases
Frequent scenarios include agent fees, dealer commissions, marketplace payouts for e-commerce, and some cross-border service fees. These transactions recur daily and need clear templates to avoid errors.
Handle high-risk categories—insurance claims, betting payouts, profit distributions, and capital events—with stricter approvals and audit trails because volume and scrutiny rise quickly.
Operational guidance and data readiness
- Assign AP to trigger self-billing; require finance approval before submission.
- Standardize descriptions and map payment references into the 55-field structure to avoid duplicates.
- Keep a control log to prevent double charging when suppliers later send their own paperwork.
Tip: prepare master data early, test self-billing templates, and document who owns each step to keep transactions clean and auditable.
Compliance planning checklist for businesses in Malaysia
Begin your compliance plan with a clear project owner and measurable milestones. Treat readiness as three pillars: People, Process, and Technology. This short checklist helps teams move from awareness to action before their phase date.
People: who owns what
Assign a finance lead and an IT lead as accountable owners. Train AR and AP teams on rejection, cancellation, and correction workflows.
Tip: align sales and operations to capture buyer data at point of sale.
Process: map changes and controls
Document invoice-to-cash and procure-to-pay flows. Mark where validation sits and how month-end consolidation works.
Define controls for cancellations within 72 hours and for issuing credit, debit, and refund notes.
Technology: data, integration and monitoring
Decide portal or API integration. Confirm master data covers the 55 required fields and automate digital signing.
Set up monitoring for failed validations, retries, and alerts to owners.
Penalties and incentives
Penalty risk: an offence under Section 120(1)(d) can carry fines from RM200 to RM20,000 and/or up to six months’ imprisonment per instance. Volume makes this a real exposure for high-frequency businesses.
Incentives: plan budgets around a tax deduction up to RM50,000 per year (2024–2027) and accelerated capital allowance for ICT software and equipment with a two-year claim period.
“Assign owners, map your flows, and confirm system readiness — then test before your start date.”
- Appoint finance and IT leads and train teams.
- Map end-to-end processes and document validation touchpoints.
- Choose portal or API, verify master data, and enable monitoring.
- Set governance for 72-hour cancellations and retain signed payloads for audit.
- Apply available deductions and plan capital claims to offset implementation cost.
Conclusion
strong, A quick checklist—confirm your phase, pick portal or API, and run a short pilot—keeps rollout manageable.
What, who, and when: phased e-invoicing applies by turnover bands starting 1 Aug 2024. Check your annual band and schedule your date. Prepare for near-real-time validation via MyInvois and aim for early readiness.
Key levers: (1) confirm your phase using audited figures; (2) build operational readiness for clearance checks. Core rules to embed: 55 required fields, UBL 2.1 XML/JSON structure, a digital certificate, realtime notifications, and the 72-hour cancellation window.
Use consolidation for B2C where allowed but plan for the RM10,000 split rule from Jan 2026. Next step: choose the myinvois portal or API, pilot your flows, fix data gaps, and train teams so implementation runs smoothly and audits cause less disruption for your companies.
FAQ
Malaysia e-Invoice mandatory, LHDN e-Invoice requirement?
The Lembaga Hasil Dalam Negeri (LHDN), also known as the Inland Revenue Board, has introduced a national e-invoicing mandate requiring specified taxpayers to submit electronic invoices via the MyInvois system or API. The program enforces real-time validation, standard data formats, and unique identifiers so tax and transactional data are consistent and auditable.
Malaysia e-Invoicing mandate overview from LHDN and the Inland Revenue Board?
The mandate standardizes invoice data, mandates UBL 2.1 XML or JSON formats, and routes submissions through MyInvois for validation. It applies in phases based on annual turnover, covers B2B, B2C and B2G where applicable, and requires a digital certificate for signing documents. Businesses must adopt either the portal or API submission path and ensure compliance with required fields and validation rules.
What “real-time validation” through the MyInvois system means for businesses?
Real-time validation means invoices are checked immediately on submission for format, required fields, tax codes, unique identifier numbers, timestamps and digital signatures. Accepted invoices get a Unique Identifier Number and QR code. Rejected items return error codes so companies can fix and resubmit without delay to keep transactions compliant.
Transactions covered now: B2B, B2C, and B2G (including selected non-business cases)?
The system covers business-to-business sales by default and many B2C and B2G situations depending on industry and buyer requests. Selected non-business cases such as certain government procurements and regulated sectors are included. Where buyers do not require immediate e-invoices, suppliers can use consolidated monthly submissions for eligible retail transactions.
The RM1 million annual turnover revenue threshold and who is exempt?
The initial threshold for mandatory scope is RM1 million annual turnover for many categories. Entities below that level are typically out of scope until phased in. Exemptions or later phases may apply to small businesses, charities, or certain sectors subject to administrative relief. Check LHDN guidance for sector-specific carve-outs and precise calculation rules.
When voluntary participation makes sense (before your mandated phase)?
Voluntary participation helps firms test API integrations, streamline billing, and gain early compliance experience. Businesses that expect rapid growth, use ERP systems, or handle large transaction volumes should adopt earlier to avoid rushed integrations during their mandated window.
Phase for annual turnover above RM100 million starting August 2024?
Large taxpayers above RM100 million annual turnover began mandatory submissions in August 2024. These entities were expected to connect via API or the MyInvois portal, ensure digital certificates, and meet all required data fields from the start to enable immediate validation and issuance.
Phase for RM25 million to RM100 million starting January 2025?
Companies with turnover between RM25 million and RM100 million entered the mandate in January 2025. They needed to complete system readiness, validate data formats, and choose either portal or API to submit invoices on the MyInvois platform.
Phase for RM5 million to RM25 million starting July 2025?
Medium-sized businesses from RM5 million to RM25 million were scheduled for mandatory compliance in July 2025. This phase stressed integration testing, staff training, and accounting process changes to handle real-time validations and unique identifiers.
Phase for RM1 million to RM5 million starting January 2026 (relaxation extended to December 2026)?
Businesses with annual turnover between RM1 million and RM5 million were slated to start January 2026. LHDN allowed a relaxation or extended onboarding period through December 2026 for some taxpayers, giving more time for MyInvois portal adoption or API integration depending on volume and readiness.
Which year of assessment and documents LHDN uses (audited financial statements vs tax return)?
LHDN determines turnover using the most recent year of assessment and supporting documents such as audited financial statements, tax returns, or statutory accounts. The authority will specify which document takes precedence for determining the phased start date and ongoing scope.
What happens if you cross RM1 million later: the “second year after” rule?
If a taxpayer exceeds the RM1 million threshold during a given year, the mandate typically activates in the second year after the exceedance. That delay gives businesses time to prepare systems, obtain certificates, and plan integration before mandatory submission starts.
Sole proprietors: combining revenue across all owned businesses?
Sole proprietors must combine turnover from all businesses they operate when determining the threshold. LHDN treats personal proprietorship income aggregated for scope decisions, so multiple small ventures under one owner can push the owner into the e-invoicing requirement.
Once in scope, you stay in scope even if turnover later drops below RM1 million?
Yes. After a taxpayer enters the mandate based on turnover, they generally remain in scope even if their revenue later falls below the threshold. LHDN retention rules prevent frequent in-and-out status changes and maintain consistent reporting coverage.
Accepted formats and standards: UBL 2.1 in XML or JSON?
MyInvois requires invoices to conform to UBL 2.1 schema provided by LHDN, available as XML or JSON payloads. Using these standards ensures interoperability, accurate parsing, and smooth validation when submitted via portal or API.
The 55 required data fields (mandatory vs optional) and common data gaps?
The e-invoice payload includes 55 key fields such as supplier and buyer IDs, tax codes, line item details, totals, timestamps and digital signature info. Common gaps include incomplete tax identifiers, missing item descriptions, incorrect tax rates, and absent buyer details. Validate data rigorously before submission to avoid rejections.
Digital signature and Digital Certificate issued by IRBM?
Digital signatures are mandatory for authenticated e-invoices. LHDN issues or approves digital certificates (often through recognized certificate authorities) that businesses must install to sign invoices. This ensures invoice authenticity and non-repudiation during validation.
MyInvois Portal for manual and bulk upload submissions (best for lower volumes)?
The MyInvois portal supports manual invoice creation and CSV or XML bulk uploads, ideal for smaller companies or those without integrated billing systems. It offers a straightforward path to compliance for low-volume users and provides validation feedback directly in the interface.
API integration for automated invoicing at scale (ERP, billing, accounting systems)?
API integration suits high-volume businesses that require automated, real-time invoice issuance from ERPs, POS, or accounting platforms. APIs let companies send structured UBL payloads, receive validation responses, and automate QR code and UID handling without manual steps.
Using the Malaysia e-Invoice SDK to reduce integration complexity?
The Malaysia e-Invoice SDK packages libraries, sample code and validation tools to simplify connections to MyInvois. SDKs reduce development time, handle common schema mapping, and help generate compliant signatures and payloads for API submissions.
Issuance: creating and sending the e-invoice via portal or API?
Issuance starts with generating an invoice in compliant UBL format, signing it with the digital certificate, and submitting it to MyInvois either through the portal or API. Once submitted, the system validates and returns a unique identifier or rejection.
Validation: Unique Identifier Number, timestamp, and QR code generation?
After successful validation, MyInvois issues a Unique Identifier Number, confirms the timestamp, and a QR code is generated for the invoice. These elements authenticate the document and must appear on human-readable copies for buyer verification and audits.
Notifications to supplier and buyer through MyInvois?
MyInvois sends status notifications to both supplier and buyer including acceptance, rejection, or cancellation events. Notifications help accounting teams reconcile transactions and take corrective steps when submissions fail validation.
Sharing human-readable copies (PDF/JPG) after validation?
Businesses can share PDF or JPG copies of the validated e-invoice for the buyer’s records. The human-readable copy should include the UIN, QR code and key invoice details while the machine-readable UBL payload remains the authoritative tax record.
Rejection and cancellation window: the 72-hour rule and justification?
Rejection and cancellation rules often require suppliers to correct errors promptly. LHDN typically enforces a 72-hour window for cancellations or amendments with required justifications. After the window, special procedures or approvals may be needed to alter submitted invoices.
When the buyer requests an e-invoice vs when they don’t for B2C and B2G?
For B2C, suppliers must issue an e-invoice if the buyer requests one or if transaction types fall under mandatory rules. For many B2G purchases, the government requires electronic invoices by default. When buyers don’t request e-invoices, sellers may still use consolidated monthly submissions where allowed.
Monthly consolidated e-invoice for buyers who don’t need an e-invoice?
Consolidated invoicing lets suppliers batch many low-value B2C transactions into a single monthly e-invoice for buyers who do not require immediate individual invoices. This reduces processing overhead while maintaining compliance, subject to thresholds and industry exclusions.
Transactions above RM10,000 require individual e-invoices starting January 2026?
From January 2026, any single transaction over RM10,000 must be issued as an individual e-invoice. This change restricts consolidated reporting for high-value sales and ensures higher-value transactions are tracked at the invoice level for better auditability.
Industries restricted from consolidated e-invoices and key exceptions?
Certain sectors—such as financial services, government procurement, and regulated utilities—may be barred from using consolidated e-invoices due to compliance or regulatory tracking needs. Check sector-specific LHDN guidance for precise restrictions and exceptions.
Submission timing: consolidated e-invoices due within seven calendar days after month-end?
Consolidated monthly e-invoices must generally be submitted within seven calendar days after month-end. This timing ensures timely reconciliation and allows buyers and tax authorities to access consolidated transactional records promptly.
Invoices and self-billed invoices for proof of income and proof of expense?
Businesses must issue standard invoices and accept self-billed invoices where permitted. Self-billing occurs when buyers generate invoices on behalf of suppliers; these documents still require UBL compliance, signatures, and must be linked to appropriate tax and payment records.
Credit notes, debit notes, and refund notes for post-issuance adjustments?
Credit, debit and refund notes must be issued as e-documents with references to the original invoice UIN. Adjustments follow strict validation and timing rules to ensure accurate tax calculation and clear audit trails for both parties.
Imports and foreign suppliers: when Malaysian buyers must self-bill?
Malaysian buyers may have to self-bill for imports or when foreign suppliers cannot issue compliant MyInvois documents. Self-billing ensures local tax reporting and invoicing obligations are met; buyers must follow LHDN rules for content, signatures and submission timing.
Common self-billing situations: agents, commissions, e-commerce, and certain payments?
Self-billing commonly applies for agent commissions, marketplace sellers, cross-border e-commerce, and scenarios where the supplier lacks access to MyInvois. Buyers generate compliant invoices, record VAT or SST where applicable, and retain supporting documentation for audits.
People: assigning owners and training teams on new workflows?
Assign clear owners for e-invoicing compliance, train finance and IT teams on MyInvois processes, and document new invoice-to-cash and procure-to-pay workflows. Role-based training reduces errors and improves validation success rates.
Process: mapping invoice-to-cash and procure-to-pay changes (AR/AP impact)?
Map how e-invoicing affects accounts receivable and payable, update reconciliation steps, and align billing cycles with validation timelines. Adjust approval flows to prevent delays caused by rejections or correction windows.
Technology: data readiness, system integration, and validation monitoring?
Ensure master data quality for customers, products, tax codes and GL mappings. Integrate ERPs or accounting packages via API or use the portal for uploads. Implement monitoring to catch validation errors, track UIN issuance, and log MyInvois responses.
Penalties for non-compliance under tax law (fines up to RM20,000 and possible imprisonment)?
Non-compliance can lead to fines, penalties and in severe cases criminal sanctions under tax law. Monetary penalties may reach significant amounts and could include imprisonment for deliberate fraud. Maintain timely submissions and accurate records to avoid enforcement action.
Incentives to offset cost: deductions and accelerated capital allowance (2024-2027)?
The government has offered incentives like tax deductions or accelerated capital allowances to help businesses invest in systems and integration between 2024 and 2027. Check current LHDN announcements for eligible expenditures and application rules.
