E-Invoice API notes
The e-invoice submission, cancellation, rejection and document-query endpoints are documented and verified against the backend:
The endpoints, their payloads and their error codes
Authentication, path grammar, paging, envelopes, error codes
There is one API for the whole platform and one host that serves it: every request mapping is under
/core2/ on api.akaun.com. There is no separate e-invoice host and no separate e-invoice
authentication scheme.
The API does not make submission faster. Submission to LHDN is serial on BigLedger’s side — one
document per call, no parallelism — so an integration that pushes documents in quickly still waits
on the same queue, by default at most 49 documents per run of the submitter. Plan on a few hundred documents
an hour regardless of how they arrive: the busiest days measured so far averaged at most about 640 an
hour.
Last updated on