SAC E-Invoice App for Business Central

MyInvois workflow support for Dynamics 365 Business Central

The SAC E-Invoice App is designed to support controlled MyInvois workflows in Dynamics 365 Business Central. It can help Malaysian organisations validate source data, transmit eligible documents, record submission outcomes, manage exceptions and reconcile Business Central records to MyInvois statuses.

SAC is SCSB's range of applications for Dynamics 365 Business Central. The SAC E-Invoice App is developed and supported by SNCO Consulting Sdn Bhd; it is not a Microsoft or HASiL product.

The app does not determine whether an organisation, transaction or document is subject to e-Invoice requirements. Applicability, implementation dates and permitted treatments depend on current HASiL guidance and the organisation's facts. The organisation and its tax adviser remain responsible for approving those decisions.

What the SAC E-Invoice App can support

• Mapping Business Central customer, supplier, item, service and document fields to approved MyInvois requirements.
• Validation of required identifiers, classifications, addresses, amounts and document references before transmission.
• MyInvois API submission where that route is selected and approved for the implementation.
• Recording submission identifiers, validation outcomes and status changes against source documents.
• Exception queues for missing data, rejected documents, temporary technical failures and cases requiring business review.
• Controlled correction, cancellation and resubmission workflows based on approved procedures.
• Reconciliation and audit evidence linking Business Central documents to MyInvois outcomes.

Confirm applicability and current requirements

HASiL's current e-Invoice Guideline Version 4.7 phases implementation by annual turnover or revenue and describes exemptions subject to stated conditions. The e-Invoice Specific Guideline Version 4.8 addresses transaction and industry scenarios in more detail. Both documents were issued on 7 July 2026.

Implementation teams should confirm the current version and the organisation's position before configuring production rules. A website summary, generic threshold or old project brief should not be treated as the sole authority.

Implementation scope

Readiness and route selection

SCSB reviews the legal entities, implementation dates, document types, transaction volumes, systems, MyInvois access and operating responsibilities in scope. The organisation selects the Portal, API or approved combination based on its volume, integration needs and controls.

Data and field mapping

The implementation maps approved source fields and classifications to the required document structure. SCSB helps identify gaps in registration identifiers, addresses, item or service descriptions, units of measure, tax data, currency, discounts and references to earlier documents.

Validation and integration configuration

Validation rules are configured to identify incomplete or inconsistent data before submission. For API implementations, the workflow records requests, responses and document statuses without exposing credentials or unnecessary personal data.

Scenario testing

Testing covers representative and adverse cases, including different document types, foreign currency, rounding, discounts, cancellations, credit and debit adjustments, missing master data, duplicate prevention, network interruption and restricted user access where relevant.

Controlled go-live and support

Acceptance criteria should cover data completeness, mapping, validation, status visibility, error handling, reconciliation, access controls, recovery procedures and user training. Delivery timing depends on confirmed scope, data quality, customisations, integrations and the availability of business and tax decisions.

Operational controls

• Assign named owners for submission monitoring, exception resolution and master-data maintenance.
• Restrict credential, mapping and configuration changes to authorised users.
• Distinguish data errors, business-review cases and temporary technical failures.
• Reconcile MyInvois statuses to Business Central documents at an agreed frequency.
• Retain change records, submission evidence and correction history.
• Review new HASiL guideline, SDK and validation-rule releases before changing production configuration.

Automation can make the workflow more consistent, but it cannot guarantee acceptance or regulatory compliance. Management review and approved document treatment remain essential.

Commercial scope and terms

Implementation and subscription scope depend on the Business Central version, deployment model, entities, document types, transaction volume, MyInvois route, integrations, data remediation and support model. Contact SCSB for the current proposal, pricing and terms. Any demonstration, trial, refund, service level or update commitment is governed by the signed proposal and agreement.

Why work with SCSB

SCSB combines Business Central field mapping, workflow design, configuration, integration coordination, sandbox testing, user training and post-go-live support in one implementation process. The engagement is led by the organisation's approved requirements and controls, with Microsoft technology used as the supporting platform.

Discuss your MyInvois requirements

Request a consultation to review your Business Central environment, document flows and MyInvois readiness. The first step is to confirm the applicable entities, dates, document treatments, route and evidence—not to assume one standard configuration fits every organisation.