SCSB Guide to Business Central E-Invoicing in Malaysia

Compliance guide

Business Central e-Invoice implementation for Malaysia

Malaysia's e-Invoice programme changes how affected taxpayers prepare, transmit and retain transaction data. For organisations using Dynamics 365 Business Central, the work is broader than connecting an endpoint. It includes determining the applicable implementation date, reviewing master data, mapping document fields, choosing a transmission route, testing exception scenarios and establishing day-to-day controls.

SCSB helps Malaysian organisations assess and configure these workflows. The objective is a controlled implementation aligned with the organisation's transactions, documented business rules and the latest HASiL material.

Start with the current HASiL position

HASiL's published implementation timeline, updated on 7 December 2025, places taxpayers into phases based on annual turnover or revenue. It shows 1 January 2026 for taxpayers with turnover or revenue up to RM5 million and states that taxpayers below RM1 million are exempt from implementation. Earlier phases applied to larger taxpayers.

Turnover is not the only consideration. New businesses, related entities, changes in revenue and transaction-specific rules may affect the analysis. Confirm the organisation's position against the current HASiL implementation timeline and obtain tax advice where the facts are unclear.

HASiL also updates its detailed material. At the time of this review, the official guidelines page listed e-Invoice Guideline Version 4.7 and e-Invoice Specific Guideline Version 4.8, both published on 7 July 2026. Implementation teams should work from the current versions rather than an older project brief or a previously downloaded PDF.

Choose the appropriate transmission route

HASiL describes two transmission mechanisms: the MyInvois Portal and an Application Programming Interface (API). The portal is available to taxpayers and can suit lower-volume or more manual operations. The API supports direct transmission between the taxpayer's system and MyInvois and may be more appropriate where transaction volume, integration needs or operating controls justify it.

A Business Central project should document why the chosen route fits the organisation. The decision should consider transaction volume, document types, operating hours, internal technical capability, error-resolution responsibilities, business-continuity needs and the cost of maintaining the integration.

Business Central readiness checklist

Reliable submission starts with reliable source data. Before configuring an integration, review the fields and processes that generate invoices, credit notes, debit notes and other relevant documents.

Organisation data: legal name, registration identifiers, tax identifiers, addresses and contact information.
Customer and supplier data: identifiers, registration details, address fields and processes for incomplete or disputed records.
Item and service data: descriptions, classification codes, units of measure, tax treatment and supporting reference data.
Document data: dates, currency, exchange rate, payment terms, line values, discounts, taxes and references to earlier documents.
Process ownership: who creates, reviews, submits, cancels, rejects, corrects and reconciles each document type.
Access controls: who can view credentials, change mappings, resubmit documents or override exceptions.

Data-quality issues should be corrected at source wherever practical. Repeatedly patching missing information during submission creates fragile operations and weakens the audit trail.

Design the MyInvois workflow

A controlled workflow separates document creation from validation, transmission and monitoring. The exact configuration depends on the organisation, but the design should address the following stages.

1. Document creation and validation

Business Central should capture the required information before a document is released for transmission. Validation rules can identify missing identifiers, invalid formats, incomplete addresses, unsupported classifications and inconsistent totals. Exceptions should be visible to the responsible user with a clear correction path.

2. Submission and status handling

For API implementations, the integration should record submission time, response status and the identifier returned by MyInvois. It should distinguish between validation failures, temporary technical errors and documents requiring business review. Automatic retries should only be used where they will not create duplicates or conceal unresolved data problems.

3. Rejection, cancellation and correction

The project should map each correction scenario to the applicable HASiL treatment and the organisation's approval process. Users need to understand when to correct source data, issue a new document, reference an earlier document or escalate the matter for tax review.

4. Reconciliation and evidence

Finance teams should be able to reconcile Business Central documents to MyInvois statuses. A useful control view shows documents awaiting submission, validated documents, rejected documents, unresolved errors and corrections. Logs should retain enough information to explain what occurred without exposing credentials or unnecessary personal data.

Testing before production

Testing should use representative scenarios rather than one successful invoice. A test plan may include domestic and cross-border customers, different document types, discounts, foreign currency, rounding, cancellations, credit and debit adjustments, incomplete master data, duplicate prevention, network interruption and user-access restrictions.

Acceptance criteria should be agreed before go-live. They should cover data completeness, correct mapping, status visibility, error handling, reconciliation, access controls, recovery steps and user training. Tax-sensitive scenarios should be reviewed by the organisation's tax adviser or responsible finance professional.

Operating controls after go-live

An e-Invoice implementation becomes an operating process once production starts. Assign named owners for daily monitoring, exception resolution, master-data maintenance, credential administration and regulatory updates.

Review failed and pending submissions at an agreed frequency.
Reconcile MyInvois outcomes to Business Central documents.
Restrict configuration and credential changes to authorised users.
Retain change records for mappings, validation rules and integration versions.
Test recovery procedures and monitor API or service changes.
Review current HASiL guidelines whenever the programme or SDK changes.

Dashboards can support these controls, but they do not replace review. Management should define which exceptions require finance, tax, IT or vendor escalation.

How SCSB supports the implementation

SCSB can help with readiness assessment, Business Central field mapping, workflow design, configuration, integration coordination, sandbox testing, user training and post-go-live support. The scope should state the entities, document types, systems, environments, responsibilities and acceptance criteria included.

Before committing to a delivery plan, SCSB should confirm the organisation's Business Central version, deployment model, transaction profile, MyInvois access, data quality and existing customisations. Timelines and fees depend on that confirmed scope; this guide does not promise a fixed implementation period, price or regulatory outcome.

Questions to resolve during discovery

Which legal entities and implementation dates are in scope?
Which document types and transaction scenarios occur in practice?
Will the organisation use the MyInvois Portal, an API, or a controlled combination?
Which source systems create customer, supplier and item data?
Who owns tax treatment, data correction and submission monitoring?
What evidence is required for internal review and audit support?
How will regulatory, SDK and Business Central changes be assessed?

Official references and review date

Review HASiL's e-Invoice Guideline Version 4.7 and e-Invoice Specific Guideline Version 4.8 before making implementation decisions.

Last reviewed: July 2026. HASiL requirements and technical specifications can change. Confirm the current position for the organisation's facts before production use.

Discuss your Business Central e-Invoice requirements

Request a consultation with SCSB to review your Business Central environment, transaction flows and MyInvois readiness. The first step is to define the applicable scope and evidence—not to assume a standard configuration fits every organisation.