Malaysia MyInvois and PINT MY 1.3.1: SAP Changes for September and October 2026

Malaysia now has two different SAP change calendars that must not be collapsed into one “e-Invoice version.” PINT Malaysia Billing and Self-Billing 1.3.1 become mandatory on 7 September 2026 for Peppol business-document exchange. Separately, HASiL will activate new MyInvois field constraints on 23 October 2026, including a 26-digit maximum for listed monetary fields and a 12-character maximum for PASSPORT identification values.

SAP Document and Reporting Compliance, Cloud Edition added PINT Malaysia 1.3.1 validation support on 18 August 2026. The SAP validator baseline is therefore available before the Peppol mandatory date, but customer readiness still depends on Business Partner identity data, source-field domains, profile selection, MyInvois clearance logic and end-to-end rejection handling.

MyInvois and PINT Malaysia are different integration layers

MyInvois is the authority-facing clearance and validation process operated by HASiL. PINT Malaysia is the Peppol profile used to exchange structured business documents with trading partners. The same SAP invoice can participate in both processes, but the document versions, response models, participant addressing and legal statuses are different.

SAP billing or accounting document
        |
        +--> MyInvois authority submission and clearance
        |
        +--> PINT MY business-document exchange through Peppol
        |
        +--> SAP operational status, correction and evidence

Do not select a PINT profile because the MyInvois document version changed. Do not treat a successful Peppol delivery as evidence that HASiL cleared the invoice. Keep independent identifiers, payload fingerprints, responses and statuses for each layer.

What PINT Malaysia 1.3.1 changes

OpenPeppol lists PINT BIS Billing Malaysia 1.3.1 and PINT BIS Self-Billing Malaysia 1.3.1 as mandatory from 7 September 2026. The release aligns the Malaysian specialization with PINT General 1.1.3 and corrects several validation and documentation defects.

PINT change	Likely SAP impact
Updated EAS, ICD and currency code lists	Endpoint, legal-identifier and currency lookup tables must match the current profile rather than a generic global list.
Missing mandatory cac:TaxScheme/cbc:ID corrected in relevant tax-currency structures	Custom mappings must populate the tax scheme where the structure is used. A blank or omitted value may now fail the corrected validator.
Credit Note interpretation of IBT-003 corrected	Credit-note type-code documentation and test expectations should be checked independently from ordinary invoices.
Exempt-tax Schematron logic corrected	Document and line tax totals need tests covering zero and non-zero reference tax amounts with exemption reasons.
Redundant or false-failure rules corrected	Old negative-test expectations may no longer be valid. Compare rule IDs and outcomes between 1.3.0 and 1.3.1.

Billing and Self-Billing need separate certification

A successful PINT Billing invoice does not prove readiness for Self-Billing. The source parties, responsibility for document creation, document types, participant capabilities and business response ownership differ. Run at least four independent paths:

• Supplier invoice and supplier credit note
• Self-billed invoice and self-billed credit note
• Exempt and standard-rated tax cases
• Domestic, foreign and one-time Business Partner scenarios in scope

Also perform actual Peppol discovery. XML validation does not prove that the receiver advertises the required PINT Billing or Self-Billing capability.

TIN and BRN validation belongs in Business Partner governance

Since 1 August 2026, HASiL validates the combination of TIN, identification type and identification value, including Business Registration Number. The official guidance recommends validating when the buyer is created or maintained in the ERP and caching the result, rather than calling the authority API before every invoice.

A practical SAP validation envelope should retain:

TIN
identification type
identification value or BRN
validation result
validation timestamp
MyInvois environment
validated value fingerprint
revalidation-required flag

Revalidate when an identity field changes, when a defined age threshold is exceeded or when MyInvois rejects a document for an identity mismatch. Do not make every billing document wait for a synchronous lookup. That design increases latency and creates avoidable exposure to API throttling or authority downtime.

The 23 October amount-field limit requires a domain audit

HASiL will apply a maximum length of 26 digits to the listed invoice-level and line-level monetary fields from 23 October 2026. The affected set includes prepayments, totals, tax amounts, taxable amounts, exemption amounts, unit price, subtotals, discounts and charges. PASSPORT identification values will be limited to 12 characters.

The work is not limited to adding an XML length check. SAP teams should compare authority limits with:

• DDIC domains and custom extension fields
• Currency decimals and conversion results
• High-value invoices and accumulated document totals
• Unit-price calculations with many decimal places
• Business Partner passport values and data-cleaning rules
• Serialization logic that might use scientific notation

MyInvois does not support scientific notation for numeric values. A valid SAP decimal value can therefore still fail if the integration serializes a large or small number as an exponent string. Test the final JSON or XML representation, not only the ABAP or Java numeric value.

SAP-side validation should happen before authority submission

The production validations activated on 15 August cover date formatting, invoice-number length, bank accounts, Incoterms, payment terms, units, Malaysian postcodes and controlled country, payment, tax and currency codes. These checks should run before eDocument submission, ideally before the business process reaches a legally relevant output state.

Map each authority rule to an operational correction point:

Failure type	Preferred correction point	Owner
Invalid TIN or BRN combination	Business Partner master-data workflow	Master data and tax
Invoice number or reference too long	Source-document validation or controlled mapping	SAP functional and development
Unsupported code	Versioned code-list mapping	Tax and integration
Invalid postcode or passport value	Address and identity maintenance	Master data
Amount exceeds serialized limit	Pre-submission payload validation and exception handling	Finance, tax and integration

SAP DRC support and the customer evidence boundary

SAP’s 18 August change log confirms PINT Malaysia 1.3.1 Schematron support. This removes the earlier vendor-version uncertainty, but five customer-specific points still require evidence:

1. The source-to-PINT mapping selects the right Malaysian profile and document type.
2. The Business Partner identifiers and schemes pass current validation.
3. The Access Point and receiver advertise the required capability.
4. MyInvois clearance identifiers and Peppol transport identifiers remain separately traceable.
5. Rejections update the correct SAP operational queue without confusing authority and network statuses.

Regression matrix

Scenario	Boundary to test	Evidence to retain
Standard invoice	MyInvois clearance and PINT Billing exchange as separate results	Source key, both payloads, authority result and network acknowledgement
Credit note	Correct IBT-003 interpretation, references and signs	Original invoice link, profile validation and receiver result
Self-billed invoice	Party roles, profile capability and self-billing-specific rules	SMP discovery, payload and business acknowledgement
Exempt transaction	Exemption reason, actual or reference tax amount, line and document totals	Tax decision, calculation trace and Schematron output
High-value foreign-currency invoice	26-digit limit, conversion, rounding and non-scientific serialization	Calculation record and final serialized values
Passport-identified buyer	12-character limit and identity-validation behavior	BP validation envelope and submission result
Invalid BRN negative test	Master-data rejection and prevention of downstream invoicing	API result, blocked process and correction audit

Recommended SAP action sequence

1. Now: inventory PINT Billing and Self-Billing scenarios, endpoint schemes and active SAP DRC validator results.
2. Before 7 September: certify invoices, credit notes and both self-billing document types against PINT MY 1.3.1 and real SMP discovery.
3. During September: audit SAP numeric domains, passport values and serialization behavior for the 23 October rules.
4. Before 23 October: deploy SAP-side prevalidation, negative tests and operational correction ownership.
5. After deployment: monitor authority and Peppol rejections separately, retaining rule IDs and payload versions.

For the wider rollout, document types and integration choices, review Malaysia E-Invoice for SAP: Scope, Timeline and API.

Primary sources

• HASiL: MyInvois SDK 1.0 release and validation updates
• OpenPeppol: Post-Award documentation and mandatory dates
• OpenPeppol: PINT Malaysia 1.3.1 specification
• SAP: What’s New for SAP Document and Reporting Compliance, Cloud Edition

PINT mandatory date: 7 September 2026. MyInvois October validation date: 23 October 2026. Article verified: 24 August 2026.