Skip to content
MYOB

Connect MYOB to LHDN MyInvois without rebuilding your stack.

MYOB users in Malaysia often inherited the install from an earlier era when MYOB owned the SME accounting market — the books work, the workflow's familiar, but MyInvois compliance was never on the roadmap. The bridge picks up where MYOB stops and runs the LHDN side end to end.

The friction

Where MYOB users hit MyInvois compliance.

  1. 01

    MYOB's CSV export is straightforward; the LHDN fields aren't there

    MYOB emits a clean invoice CSV, but it predates LHDN's structured-tax-classification expectations. The bridge supplements MYOB's columns with the missing LHDN fields (MSIC, tax classification, structured tax category) at parse time.

  2. 02

    AccountRight vs. Essentials emit different exports

    MYOB AccountRight (desktop) and MYOB Essentials (cloud) emit different CSV shapes. The bridge handles both — pick the variant in your dashboard mapping, the parser routes accordingly.

  3. 03

    Item codes need MSIC mapping

    MYOB's item codes don't carry MSIC industry codes natively. Map your MYOB item codes to MSIC once in the bridge's product catalog; every invoice that references that item picks up the right MSIC code automatically.

Where Bridge fits

We pick up where the export stops.

Export from MYOB AccountRight or Essentials on your monthly close cadence. The bridge picks up the CSV, supplements the LHDN fields from your dashboard mapping + product catalog, generates UBL 2.1, submits, and reflects status back. Your MYOB books stay the source of truth; the bridge keeps LHDN current.

Last updated · May 2026

Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.