AECloud System Overview
AECloud is an e-Invoice intermediary platform that connects merchants, their business systems, customers, and LHDN Malaysia's MyInvois services. Subject to the merchant's authorization, AECloud receives business documents, prepares the required e-Invoice representation, submits it to MyInvois, and records the resulting status. It also provides separate workspaces for partner administration, merchant operations, customer e-Invoice requests, and system-to-system integration.
This overview explains how those parts relate to one another. It is intended for merchants, implementation teams, support personnel, and integration developers who need the complete picture before using a console or implementing an API connection.
What AECloud does
Depending on the approved merchant workflow, AECloud can:
- receive sale and self-billed documents from an integrated POS, retail, ERP, accounting, or other downstream system;
- let a merchant prepare documents manually or by supported bulk import;
- let an eligible customer request an individual e-Invoice from a receipt QR code;
- validate and store business-document data before submission;
- convert supported business data into the applicable e-Invoice document structure;
- process documents immediately, at the merchant's configured individual-submission time, or through an approved consolidated-submission schedule;
- record submission identifiers, status, and validation results; and
- provide controlled void, cancellation, status, reporting, and reconciliation functions.
An upload or manual submission entering AECloud is not, by itself, proof that LHDN has validated the e-Invoice. The final result must be checked in the appropriate console or through API status reconciliation.
In this overview
- Platform architecture
- Document sources and workspaces
- Submission modes
- End-to-end data flows
- Document lifecycle
- AECloud and MyInvois
Choose the appropriate guide
| Reader or task | Guide |
|---|---|
| Distributor maintaining its organization and resellers | Distributor Console User Guide |
| Reseller registering and maintaining merchants | Reseller Console User Guide |
| Merchant preparing documents and monitoring submissions | Merchant Console User Guide |
| Customer requesting an e-Invoice from an eligible receipt | Customer Console User Guide |
| Developer integrating a downstream business system | API Integration Developer Guide |
The Admin Console guide is restricted to authorized AECloud operational personnel and is not a general merchant or partner guide.
Important boundaries
- The business relationship is AECloud -> Distributor -> Reseller -> Merchant. A customer is the merchant's buyer and is not another partner-administration tier.
- A distributor may represent an appointed state, territory, or business region and manages its appointed resellers. Unless separately stated in an agreement, the coverage description is not a technical geographic restriction enforced by the console.
- Distributor and reseller consoles are partner and merchant-account administration workspaces. They do not provide access to merchant sales transaction records.
- Distributor users do not manage merchant outlets, subscriptions, or merchant LHDN configuration. Reseller users may maintain those merchant settings when authorized.
- The Merchant Console's Self-Service workspace prepares documents. LHDN Submission is the operational workspace used to monitor documents after they enter the submission path.
- An API integration sends a document directly into AECloud's operational processing path. It does not create a Self-Service draft for later completion.
- A customer QR-code journey is tied to a particular eligible merchant receipt. It is not a general customer account or unrestricted invoice-entry screen.
- AECloud centrally maintains the technical integration and conversion layer as MyInvois requirements evolve. The merchant remains responsible for accurate source data, business treatment, and timely review of processing results.
- AECloud processes and records the interaction, while LHDN/MyInvois determines the external validation result.
The diagrams in this overview contain only generic system roles and flows. They do not contain screenshots, credentials, customer identities, or transaction data.