AeCloud by Arcos Systems · Malaysia
Send business-oriented JSON to AeCloud. We handle the supported document conversion and MyInvois submission workflow, while your team keeps control of its source transactions.
Your POS, ERP or accounting system authenticates to AeCloud using merchant OAuth2 credentials and sends the supported business JSON. AeCloud validates the request, stores the document and prepares the regulatory representation for its authorized MyInvois intermediary connection.
Submit invoices, credit notes, debit notes and refund notes, including their self-billed equivalents. Use the matching document family and original-invoice references for adjustments. Status, supported cancellation and void operations help your team manage the later document lifecycle.
A successful upload confirms initial acceptance, not final LHDN validation. Retain returned identifiers and reconcile status through the API and Merchant Console. Correct rejected data in the source system before a controlled resubmission.
AeCloud centrally maintains its supported MyInvois conversion and integration. Connected systems still provide accurate transaction data, and contract changes may be necessary when new information is required. Your developers retain responsibility for safe retries and preventing duplicates.
No. Your system sends AeCloud business JSON to AeCloud endpoints. AeCloud prepares supported regulatory documents and communicates with MyInvois separately.
Yes. The API provides self-billed invoice, credit-note, debit-note and refund-note families. Use the required supplier details and applicable original-document references.
No. Processing can continue after the upload response. Your integration must check the final recorded status.
Tell us about your source systems, outlets and document volume so we can discuss the appropriate setup.
Discuss your workflow →