AECloud and MyInvois

AECloud is an intermediary platform between a merchant's business systems and LHDN Malaysia's MyInvois services. It is designed to reduce the amount of regulatory integration logic that every merchant, POS provider, retailer, or accounting-system provider would otherwise need to build and maintain separately.

AECloud is not LHDN, and using AECloud does not transfer responsibility for the accuracy of a merchant's transactions or tax treatment. MyInvois remains the external service that validates submitted e-Invoices.

Two different API contracts

The AECloud Integration API accepts AECloud's business-oriented JSON contract. It carries information familiar to a source system, such as the merchant company code, outlet, receipt identifier, document totals, buyer or supplier, taxes, and line items.

The MyInvois API is the regulatory interface. Its Submit Documents operation expects an approved UBL document represented as JSON or XML, together with the MyInvois submission wrapper, encoded document content, document hash, and reference number.

Do not send a MyInvois Submit Documents request to an AECloud document endpoint, and do not send an AECloud business payload directly to MyInvois.

Area AECloud Integration API MyInvois API
Intended caller Merchant POS, retail, ERP, accounting, or approved downstream system Taxpayer or authorized intermediary system implementing the regulatory interface
Request model AECloud business-document JSON MyInvois submission wrapper and supported UBL document structure
Authentication Merchant integration authenticates to AECloud Taxpayer or intermediary authenticates to MyInvois
Conversion AECloud validates, enriches, and converts supported business data Caller supplies the regulatory document
Scheduling AECloud supports immediate, merchant-setting, and approved consolidated workflows Caller implements its own orchestration around MyInvois operations
Operations Central merchant view, storage, status, reconciliation, and supported lifecycle actions Regulatory submission, retrieval, validation, rejection, and cancellation services

Why a merchant may use AECloud

Direct MyInvois integration is possible; AECloud is not a legal requirement. A merchant may choose AECloud to:

  • send a simpler business payload instead of constructing the complete regulatory document in each source system;
  • centralize validation, conversion, submission scheduling, status handling, and reconciliation;
  • maintain one integration pattern across multiple outlets or business systems;
  • reduce duplicated implementation and maintenance effort when MyInvois technical requirements change;
  • support both system integration and merchant Self-Service workflows; and
  • give authorized merchant users one console for near-real-time visibility of document activity received from their connected outlets.

AECloud centrally maintains its technical alignment with supported MyInvois requirements. This reduces the changes normally required in a connected merchant system, but a change to the AECloud business contract may still be required when new regulatory information cannot be derived from existing source data. AECloud will communicate such contract changes through the applicable release or integration process.

Authentication and authorization flow

There are two separate security relationships:

  1. The merchant's downstream system uses its AECloud OAuth2 client credential to authenticate to AECloud.
  2. AECloud uses its intermediary credentials and the taxpayer's required permission to authenticate to MyInvois and act on the taxpayer's behalf.

An AECloud client ID or secret is not a MyInvois intermediary credential. It must never be placed inside the business-document payload.

Processing and visibility

After AECloud receives a document, it authenticates the source, resolves the merchant and outlet, performs applicable checks, stores the record, prepares the supported regulatory representation, and starts or schedules processing. Authorized merchant users can then review activity across their own outlets in the Merchant Console.

This operational visibility can be close to real time after AECloud receives and processes an upload. It remains separate from MyInvois validation, which is asynchronous and may complete later. Always check the recorded final status.

Choose one authoritative submission route

Use one controlled route for each source document. Sending the same transaction through both AECloud and a direct MyInvois integration can create duplicate submissions, split operational records, and incomplete AECloud reporting. Documents submitted directly to MyInvois may not automatically appear in AECloud unless a separately approved synchronization process exists.

For the regulatory contract, refer to the official MyInvois documentation: