self billed invoice Malaysia, e-Invoice self billing

This short guide explains how a buyer can issue a self-billed e-invoice under the LHDN rollout. A self-billed e-invoice is used when a supplier does not produce a validated document. The buyer issues the e-invoice so the expense is recorded correctly for tax purposes.

The process uses MyInvois and gives each document a Unique Identification Number and QR code. That validation proves the transaction to LHDN and helps with ensuring compliance. If you skip this step, expense claims may be disallowed.

Use this guide to learn when a self-billed e-invoice applies — for foreign suppliers, agent commissions, e-commerce settlements, dividends or interest. You’ll see step-by-step options: portal entry or API calls, plus how to correct mistakes without triggering audits.

Key Takeaways

• Buyer-issued e-invoices let businesses document expenses when suppliers don’t issue one.
• Validated e-invoices include a UIN and QR code for audit-proof records.
• Common cases: cross-border suppliers, agent fees, e-commerce settlements, dividends and interest.
• Issue via MyInvois portal or API; follow the same validation rules as standard e-invoicing.
• Correct errors quickly to avoid disallowed deductions and compliance issues.

Self-billed e-invoice in Malaysia explained

A buyer-created e-invoice records expenses when a supplier cannot issue a validated document. This type of self-billed e-invoice document lets the purchaser capture the cost and keep tax records accurate.

Definition of a buyer-issued electronic document

A self-billed e-invoice document is an electronic record created by the payer to reflect a payable where the supplier does not submit an e-invoice. It uses the same data fields and technical standards as a regular e-invoice. The goal is consistent reporting and tax readiness.

How it differs from supplier-issued records

A regular e-invoice is created and submitted by the supplier. A buyer-created document flips that role: the buyer issues and sends the file for validation. Despite different issuers, both must follow the same core data rules and formats.

IRBM validation and why UIN + QR matter

Documents are submitted via MyInvois — either through the myinvois portal or an integrated system — for inland revenue board validation. The revenue board checks format and data, then returns a Unique Identification Number and QR code.

• Why UIN and QR matter: They make the record verifiable, tamper-resistant, and easy to retrieve for audits.
• Key terms to follow later: issuer, buyer, supplier, validated, rejected, cancelled.

Why self-billed e-invoices are required for tax purposes

A validated buyer-created e-document helps businesses prove costs and avoid disputes over deductions. LHDN expects every material payment to be recorded so taxable expenses are clear and verifiable for tax purposes.

Proof of expense and audit-ready documentation

Traceable validation turns a plain payment record into audit-ready evidence. When submitted for approval, the inland revenue board returns a UIN and QR code that make the e-invoice traceable.

“Validated records remove doubt. They show the company paid, when it paid, and what was bought.”

What can happen if you don’t issue required records

Failing to issue a self-billed e-invoice required by rules can lead to disallowed deductions and compliance exposure. An expense without a validated e-invoice is easier to challenge during an audit.

Note: Required status is scenario-based, not every payment needs a validated e-invoice. Later sections list exact situations and exceptions. Treat self-billing as part of controls, not just extra admin.

What Is Self-Billed Invoice in Malaysia?

The responsibility can shift to the buyer when a supplier cannot provide a validated e-invoice. This responsible issuing ensures the payment is recorded and validated so the expense counts for tax purposes.

When the buyer becomes responsible for issuing

If the supplier is outside MyInvois or is exempt, the issued buyer must issue the e-invoice. Common triggers include foreign suppliers not on the portal and individuals not carrying on business.

How the rule applies to domestic and cross-border transactions

Self-billing applies to both local and cross-border purchases. Cross-border scenarios are frequent because overseas vendors often cannot join MyInvois, so the buyer must issue self-billed records to document the cost.

• Goods services covers tangible goods, professional work, rentals and other expense types.
• Accurate transaction details — classification, tax type and totals — drive validation and avoid rejections.
• Sanity check: if you cannot secure a supplier-issued e-invoice but LHDN expects reporting, you must issue the validated document.

“Make data accuracy part of the issuing duty — the document is only as useful as the details it contains.”

When you must issue a self-billed e-invoice

Some transaction types require the purchaser to create the validated e-document to secure tax relief. Below is a clear checklist to help you map common payments to LHDN expectations.

• Payments to agents, dealers, and distributors: commission and incentive payments often mean the payer must issue a self-billed e-invoice so the expense is recorded correctly.
• Purchases from foreign suppliers: when the overseas seller is outside MyInvois, the Malaysian buyer must self-bill for goods services to keep the cost deductible and traceable.
• Profit distributions and dividends: some dividend-related payouts require buyer-issued documents; note exemptions for entities listed on Bursa Malaysia.
• E‑commerce settlements: marketplaces or platforms may generate self-billed e-invoices for merchant payouts; check who holds issuing responsibility.
• Betting and gaming payouts: most payouts require records, though certain casino machine and betting payouts remain exempt until further notice.
• Acquisitions from individuals: ad‑hoc purchases or rentals from non-business individuals can trigger a need to issue a self-billed e-invoice to document the payment.
• Interest payments: many interest payments require self-billing, but exclude interest charged by public financial institutions, employee-to-employer interest, and interest paid by foreign payors to Malaysian taxpayers.

Practical tip: maintain a short checklist at payment approval to decide whether you must issue self-billed e-invoice before submitting for validation.

Parties and roles in issuing self-billed e-invoices

Roles must be clear: who supplies the goods or service, who pays, and who becomes the issuer for validation. LHDN guidance usually assigns the buyer as the issuer for defined scenarios.

Buyer and supplier responsibilities

The buyer must collect supplier details, create the document, submit it for validation, and keep the validated record. The supplier then keeps the returned validated e-invoice for their accounts and tax files.

Intermediaries and payments agents

Marketplaces or platforms that control settlements often act as the issued buyer and will issue self-billed e-invoices for merchant payouts.

Payments agents that collect and disburse funds add complexity. Clear role mapping avoids duplicate or missing e-invoices and prevents disputes over who must submit and retain records.

• Map roles so each party knows who will issue and keep records.
• Where platforms act as issuer, they must share validated e-invoices with merchants.
• For foreign suppliers, notifications may be optional, so internal sharing is essential.

Role complexity often drives automation decisions such as portal api integration for faster, error-free issuing self-billed documents.

Details required to generate a self-billed e-invoice

Gather complete supplier and line-item fields before you submit for validation. Doing this reduces rework and speeds approval.

Supplier identification fields

At minimum include supplier name, TIN or approved fallback TINs and an address or NA placeholder if unavailable. For foreign sellers, use guideline fallback values such as “EI00000000030” when a local TIN is absent.

Use registration ID or passport fields, and put NA only when the supplier cannot provide the data. This keeps records consistent and avoids empty fields that trigger validation errors.

Transaction details that drive validation

Accurate transaction details are the most common pass/fail points. Provide a 3-digit classification code, clear description, quantity, unit price, tax type, tax rate and tax amount, and correct totals.

Validation checks arithmetic and classification. If totals or tax types mismatch, the e-invoice will be rejected. Ensure the e-invoice aligns with accounting entries for goods services and other categories.

Optional but useful fields

Include SST registration number (or NA), MSIC code, business activity description, and an internal reference. These help with audits, reconciliation, and supplier queries.

Practical tip: standardize master data for recurring vendors. A maintained supplier file reduces errors when you generate self-billed records and helps ensure each e-invoice document must pass validation on the first attempt.

How to issue a self-billed e-invoice via MyInvois Portal

A simple, step-driven portal process turns a payable into an auditable, validated e-invoice ready for sharing and record-keeping.

Prepare and submit the self-billed e-invoice document data

Confirm the transaction needs buyer-issued validation and collect supplier details, including fallback TINs or NA where allowed. Complete each line item: classification code, description, quantity, unit price, tax type and totals.

Key into the myinvois portal or upload a supported file. Review arithmetic and required fields before you submit to avoid rejections.

Receive IRBM validation, then share the validated invoice with the supplier

When you submit, the portal sends the document to the inland revenue. The result is either validated with a UIN and QR or rejected with error reasons.

If validated, download the validated e-invoice and log the UIN in your accounting system. Share the file with the supplier by email or portal link, and keep an internal copy for reconciliation.

Practical tip: assign finance/AP ownership and add the portal step to your month-end SOP so issuing self-billed e-invoices via myinvois portal never gets missed.

How to issue self-billed e-invoices via API or e-invoicing middleware

For companies that handle many settlements, replacing manual portal steps with an API workflow saves hours each month. Large firms and platforms can automate issuance, validation, and posting so teams spend less time on data entry and more on exceptions.

When portal vs API makes sense for sdn bhd and high-volume businesses

Portal is ideal for low-volume use or occasional payments. It suits small teams that can review and submit documents by hand.

API or middleware fits an sdn bhd with frequent payouts, cross-border buys, or marketplace settlements. Automation handles bulk uploads, supplier syncs, and repeatable templates.

What “real-time validation” means operationally

Real-time validation means your system submits an e-invoice and receives the IRBM response quickly. The UIN and QR return can then be posted back to your ERP without manual steps.

This enables immediate posting, faster supplier sharing, and automated status flags for exceptions.

Automation also improves exception management. Rejection messages arrive via API so systems can flag records, suggest fixes, and resubmit without rekeying.

Internal control benefits include consistent templates, full audit trails, and easier retrieval across thousands of self-billed e-invoices. Choose the route that matches volume, complexity, and resource capacity.

Step-by-step workflow for issuing self-billed e-invoices

Start by checking whether the payment fits a category that requires buyer-issued documentation under LHDN rules. This saves time and avoids surprises during month-end close.

Identify the transaction and confirm requirements

Step 1: Confirm the transaction type — commission, foreign vendor payout, platform settlement, dividend, or interest — and verify whether a self-billed e-invoice required applies.

Collect supplier data and placeholders

Step 2: Gather supplier name, TIN or fallback TIN, address and other mandatory fields. For overseas sellers use approved placeholders or NA where allowed to prevent validation errors.

Create and submit for validation

Step 3: Build the e-invoice with accurate transaction details: classification code, tax type, unit amounts and totals. Submit the file via myinvois portal or API to the inland revenue board for validation.

Handle outcomes, notifications, and resubmission

Step 4: If validated, the revenue board returns a UIN and QR. If rejected, correct the flagged fields and resubmit quickly. Assign clear ownership so AP or treasury teams receive alerts and act fast.

Share, retrieve, and store for audit readiness

Step 5: Share the validated e-invoice with the supplier and internal stakeholders. Retrieve and archive the validated record and status logs to support audits and reconciliations.

Quick reminder: Turn this flow into a short SOP for AP and finance. A consistent process reduces month-end stress and strengthens deduction defensibility.

Self-billed e-invoice example for a foreign supplier transaction

This short example shows how a buyer records an imported machinery purchase when the overseas seller cannot use MyInvois.

Scenario: Malaysian buyer acquiring machinery from an overseas supplier

ABC Sdn Bhd buys machinery worth RM50,000 from a foreign vendor outside MyInvois. The buyer must create a validated self-billed e-invoice so the cost is deductible and traceable.

Fields to include: supplier name, fallback TIN, classification, tax, and totals

Complete each required field; do not leave mandatory items blank. Use guideline placeholders where data is missing.

• Supplier name: full trading name.
• Fallback TIN: use EI00000000030 when no local TIN is available.
• NA entries: permitted for address or registration when unavailable.
• Classification code: 3-digit MSIC code for goods services.
• Line details: description, quantity, unit price, tax type and tax amount, then totals.

Submit the e-invoice document via portal or API to generate the validated record. After validation, the IRBM returns a UIN and QR code.

“Store the validated file and share it with the supplier so payments are supported and audit-ready.”

Result: a clean, validated e-invoice helps secure tax relief and makes month-end reconciliations simpler for the buyer.

Self-billed e-invoice exemptions you should know

Not every payout needs buyer-issued validation. This short checklist helps busy finance teams avoid over-issuing validated records and wasting effort on routine entries.

Payments excluded from validation

Certain routine payments are out of scope. Salaries and employment-related pay, pension disbursements, alimony or maintenance, and zakat do not require a validated file.

Mark payroll, benefits, and charitable zakat receipts as exempt, but keep supporting records for audit queries.

Dividend and profit distribution nuances

Profit distributions may be exempt depending on status and tax rules. Businesses that are listed bursa malaysia often fall outside the self-billing rule for dividends.

Taxpayers not entitled to deductions under Section 108 may also have different treatment. Always confirm if an e-invoice required applies before issuing a validated record.

• Quick filter: check the transaction category first, then apply exemptions.
• Scenario-specific: exemptions can vary—map transactions to the latest LHDN guidance to avoid misclassification.
• Keep evidence: retain board resolutions, payroll registers, pension slips, and zakat receipts even when exempt.

“When in doubt, verify the category rather than assuming every payout needs validation.”

Practical tip: use this section as a stop-you-from-over-issuing checklist. It reduces admin and keeps compliance teams focused on payments that truly need validated records.

Correcting mistakes: rejection, cancellation, and reissuance rules

Mistakes can be fixed quickly if you act within a strict timeframe. The system allows cancellations or rejections only during the first 72 hours after validation.

The 72-hour window and allowed actions

Within 72 hours you may reject or cancel a validated record and then reissue a corrected self-billed e-invoice. Use this window to amend supplier identifiers, correct classification codes, or fix totals.

After the window closes: corrected records and credit/refund notes

Once 72 hours pass, you generally cannot cancel the original. Instead, prepare a corrected e-invoice that references the validated document. If amounts change, also issue a credit note or refund note that links to the original filing.

Common rejection causes and prevention

Top causes: wrong TIN or fallback value, misuse of NA, missing mandatory supplier fields, wrong classification, incorrect tax type, and math errors.

“Keep a clean correction trail — auditors focus on exceptions, not just perfect records.”

Practical tip: run a quick master data validation before you issue e-invoices and log any inland revenue board responses so reissues are fast and auditable.

Compliance and record-keeping best practices for self-billed e-invoices

Link validated records to payments and contracts so your books tell a single, verifiable story. Store every validated e-invoice with its UIN/QR and attach it to the payment voucher, PO or GL posting.

Storing validated documents and building an audit trail

Good compliance hygiene means keeping an internal trail that shows who prepared and who approved each filing. Log submission timestamps and the validation status returned from the myinvois portal.

Keep digital copies in a structured folder by month, supplier, and category. Tag files with UIN and payment batch for quick retrieval during audits.

Keeping rejected and cancelled versions for transparency

Rejected or cancelled records matter. Retain them alongside corrected filings to show the evolution of a document and to support any challenge to an expense claim.

• Archive validated, rejected, cancelled, and corrected versions together.
• Reconcile e-invoices to bank settlements on a regular schedule.
• Assign clear owners (AP, tax, procurement) and set cut-off timelines.

“Retention of every version proves you attempted compliance and makes audit responses far simpler.”

Conclusion

Clear rules mean buyers must treat certain payments as audit‑grade records, not optional paperwork,

Self-billed e-invoice and self-billed e-invoices are mandatory for defined scenarios. They deliver UIN + QR validation that proves an expense and protects deductions.

Remember when you must issue: foreign vendors, agent commissions, platform payouts, specified profit distributions and many interest cases. Keep a short checklist at approval to decide fast.

Process discipline matters. Use correct supplier IDs (fallback TINs), accurate classification and timely submission to cut rejections and rework. Choose MyInvois portal for low volume or API/middleware for scale and real‑time validation.

Practical habit: store validated files and retain rejected, cancelled and corrected trails so you can defend every claim. Standardize the workflow and self-billing becomes routine, not a scramble.