Connect AutoCount to LHDN MyInvois without rebuilding your stack.
AutoCount has a wide install base across Malaysian SMEs and mid-market businesses. If you're already on AutoCount, the bridge accepts its standard CSV export so the LHDN side can be turned on without changing how your team issues invoices today.
Where AutoCount users hit MyInvois compliance.
- 01
Custom workflows need flexible field mapping
Every AutoCount setup has been customised slightly — invoice number prefixes, tax categories, item codes. The bridge's 65+ accepted CSV columns can absorb most variations; the parser falls back gracefully on optional fields.
- 02
Cancellations have a 72-hour clock
LHDN allows cancellation only within 72 hours of approval. If your AutoCount workflow runs a daily reconciliation, the bridge surfaces the cancellation window and the `OperationPeriodOver` error if you've already missed it.
- 03
Multi-company SST tracking is a chore
If you run multiple AutoCount companies (group entities, white-labelled subsidiaries), each one needs its own LHDN onBehalfOf TIN. The bridge's multi-company tenancy isolates each one at the query level so submissions never cross.
We pick up where the export stops.
Export from AutoCount on whatever cadence you already use. The bridge takes the CSV, runs per-row validation, generates UBL 2.1 with the right MSIC + tax codes, submits, and watches the cancellation window if you ever need to retract a document.
Last updated · May 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.