Supported business processes

The process flow, supported document types, invoice formats, and use cases for Malaysia e-invoicing.

Malaysia uses a three-corner clearance model, where Inland Revenue Board of Malaysia (IRBM) must preapprove every invoice through the MyInvois platform.

Process flow

The outbound invoice flow follows these steps:

The supplier creates the invoice and submits it to Sovos in the Standard Business Document (SBD) format.
Sovos maps the invoice data to the IRBM-required Malaysian UBL 2.1 format.

Note:
Sovos skips this step if the SBD already contains the local format.
Sovos validates the invoice against IRBM business rules, including required fields, tax ID formats, and tax calculations.
Sovossigns the invoice using the taxpayer's digital certificate.
Sovosbatches the signed invoices and sends them to IRBM through the MyInvois API.
IRBM validates the schema, business logic, signature, taxpayer information, and checks for duplicates.
IRBM returns a clearance response: Acceptance with UUID, Long ID, and QR code validation link, or rejection with error details.
Sovos generates a PDF and returns the application response to you.

Format support

Sovos accepts invoices in the Sovos Canonical Invoice (SCI) format and transforms them to the IRBM-required Malaysian UBL 2.1 format before submission. SCI follows the UBL 2.1 structure and works across all Sovos-supported markets.Sovos also accepts invoices submitted in native Malaysian UBL 2.1 XML format.

Note:

Local format submissions must be only in XML.

Supported documents and products

Supported document types

Sovos supports the following document types for Malaysia e-invoicing:


Document type	Code	Description
Invoice	01	Standard tax invoice issued to a buyer.
Credit note	02	Adjustment that reduces the amount of a previously issued invoice.
Debit note	03	Adjustment that increases the amount of a previously issued invoice.
Refund note	04	Document issued for refund of a previously paid amount.
Self-billed invoice	11	Invoice created by the buyer on behalf of the supplier.
Self-billed credit note	12	Credit note for a self-billed invoice.
Self-billed debit note	13	Debit note for a self-billed invoice.
Self-billed refund note	14	Refund note for a self-billed invoice.

Note:

The Code column reflects the IRBM document type code, which you must include in the InvoiceTypeCode field.

There is support for consolidated invoices but they are not an e-invoice type. For consolidated invoices, use the general public buyer Tax Identification Number (TIN) EI00000000010.

Integration models

Basic integration: Your organization obtains credentials directly from IRBM and uploads them to Sovos. You manage your IRBM Client ID, Client Secret, and signing certificate.
Intermediary integration: You register Sovos as your authorized intermediary with IRBM. Sovos manages IRBM authentication on your behalf. This model reduces ongoing credential management.

Note:

To switch from basic to intermediary integration after initial setup, contact the Sovos Professional Services team.

To use intermediary integration, register Sovos as your authorized intermediary in MyInvois using the following values.


Property	Value
TIN	C58775637030
BRN	202401023235
Name (UAT)	SXXX_XXXXD
Name (Production)	SOVOS COMPLIANCE SDN. BHD.

Product IDs


Product ID	Use	Direction
my_UBLInvoice_1.0	Issuing invoices as a supplier	Outbound
my_UBLInvoice_Polling_1.0	Receiving invoices as a buyer	Inbound