Testing and Go-Live

Build a test matrix

Test every document family and operation that the production integration will use. Do not certify an invoice-only test when production will also issue adjustment or self-billed documents.

At minimum, test:

  • OAuth2 token acquisition, reuse, expiry, and invalid credentials;
  • GET /version/ and every required reference-code endpoint;
  • valid and invalid TIN combinations;
  • one-line and multi-line invoices;
  • taxed and tax-exempt lines used by the business;
  • discounts, charges, and rounding used by the source system;
  • individual immediate submission;
  • merchant-setting scheduled submission;
  • consolidated flow, if approved;
  • each required credit, debit, and refund-note flow;
  • each required self-billed flow;
  • status by GUID and by date range;
  • response loss and safe retry;
  • void before submission;
  • cancellation of an eligible document;
  • cancellation rejection or expired cancellation period; and
  • credential rotation.

Validate monetary consistency

For each test case, independently reconcile:

  • line quantity multiplied by unit price;
  • line discount and line subtotal;
  • line amount excluding tax;
  • line tax amount and tax rate;
  • tax totals grouped by tax type;
  • document total excluding tax;
  • document total including tax;
  • document-level discount and charges;
  • rounding adjustment; and
  • grand total.

Do not rely on AECloud to repair inconsistent source totals.

Test timestamps and scheduling

Send sales.documentDate in the required UTC timestamp shape with milliseconds and Z. Verify that the source transaction time is converted correctly from the outlet's local time.

Test all requested preferred_submission_on values and confirm:

  • now starts immediate processing when LHDN submission is yes;
  • setting follows the merchant's configured individual submission time; and
  • conso follows the configured consolidated day only for an approved consolidated workflow.

Compare systems

For each accepted test document, compare:

  1. source POS or ERP values;
  2. AECloud Merchant Console document values;
  3. API status response; and
  4. the final validated e-Invoice result.

Check party roles especially carefully for self-billed documents and source references for adjustment documents.

Production-readiness checklist

  • Production base and token URLs are stored separately from sandbox.
  • Production client credentials are in an approved secret store.
  • The merchant, LHDN configuration, subscription, and outlets are active.
  • Reference codes have been refreshed.
  • TIN master-data validation is implemented and cached.
  • Stable document and QR GUID generation is deployed.
  • Submission responses and identifiers are persisted transactionally.
  • Bounded retries and status reconciliation are operational.
  • Logs redact secrets and personal information.
  • Monitoring alerts on authentication, backlog, invalid status, and reconciliation gaps.
  • Void and cancellation actions require appropriate business authorization.
  • A rollback and credential-rotation procedure exists.
  • Business owners have signed off the document and total mappings.

First production transactions

Begin with a controlled set of real transactions during a monitored period. Verify each result end to end before increasing volume. Keep the integration team, merchant operator, and AECloud support contact available during the initial window.