Submission Modes
AECloud can start processing immediately or retain an eligible document for the merchant's approved schedule. The selected mode must match the merchant configuration and the intended business treatment.
Immediate submission
Immediate mode asks AECloud to start the individual e-Invoice processing path after the request passes the initial checks and LHDN submission is enabled for the document.
Immediate does not mean that every external validation step completes synchronously. The first response can confirm receipt or contain identifiers while later processing is still underway. Continue monitoring until a terminal result is recorded.
Merchant-setting submission
Merchant-setting mode stores the eligible individual document for the merchant's next configured submission time. If the configured time for the current day has passed, processing can occur at the next applicable configured time.
The merchant's Submission On (Hourly) setting controls this schedule. Changing it affects later processing and should be performed only as part of an approved operational change.
Consolidated submission
Consolidated mode retains eligible records for the merchant's configured monthly consolidated-submission schedule. It must be used only where the merchant's business process and the applicable e-Invoice rules permit consolidation.
The merchant's Consolidated On (Monthly) setting controls the configured day. Consolidated processing is not simply a delayed individual submission: eligible records are grouped into a consolidated e-Invoice process, and some individual operations—such as voiding or cancellation through the integration endpoints—are restricted.
Non-e-Invoice records
An integrated document can be stored with LHDN submission disabled. Such a record can be identified as Non E-Invoice and does not enter the normal LHDN submission path. This is separate from immediate, scheduled, and consolidated e-Invoice processing.
Mode comparison
| Mode | Initial outcome | Later action | Monitoring requirement |
|---|---|---|---|
| Immediate | Validate and store, then start processing when enabled | AECloud communicates with MyInvois without waiting for the configured schedule | Reconcile until final status |
| Merchant setting | Validate and store as pending for the configured individual time | Scheduled processing selects the eligible record | Check after the expected schedule and continue to final status |
| Consolidated | Validate and retain as eligible for consolidation | Scheduled processing groups applicable records | Monitor the consolidated outcome; do not assume an individual result |
| Non e-Invoice | Store with submission disabled | No normal LHDN submission is started | Retain the recorded business outcome |
Integration values
The current API represents these choices with preferred_submission_on values:
nowfor immediate processing;settingfor the merchant's configured individual schedule; andconsofor the configured consolidated schedule.
The sales.lhdnSubmission value controls whether the document is intended for the LHDN path. Developers must follow the accepted values and conditions in the Payload Reference; unlike the lowercase submission-mode values, the implemented yes or no comparison is case-insensitive.
Operational checks
Before changing a mode or schedule:
- confirm the merchant and outlet;
- confirm whether the document is individual or consolidatable;
- confirm that customer or supplier information is appropriate for the selected path;
- check for documents already pending under the previous setting;
- ensure integration and merchant teams understand the effective change time; and
- monitor the first affected processing cycle.
Do not resubmit a scheduled document merely because it does not yet have a final LHDN status.