Indonesia's Direktur Jenderal Pajak (DJP) will enforce the MyInvois mandate across all invoice sizes in 2025. Every e-invoice must submit directly to LHDN with the correct structure, valid tax IDs, and serialized reference numbers—or your invoice is not legally valid for deduction. We tested Xero, QuickBooks Online, Jurnal, and Orin to see which platforms handle native MyInvois submission, which require workarounds, and where the gaps will cost you penalties and audit risk. What MyInvois actually requires from your accounting software MyInvois is not optional invoicing software. It is a DJP-mandated submission protocol. Every invoice you issue must: Serialize with a unique reference number assigned by LHDN at submission time Submit to LHDN immediately at point of issue (not batch later) Validate buyer tax ID against DJP registry in real time Comply with UKM-specific rules if buyer has no NPWP Store a digitally signed PDF returned by LHDN Audit trail every reissue, cancellation, and correction with DJP timestamps This is not a report you file monthly. This is a transaction requirement your accounting software must enforce at the point of creation. If your software cannot submit to LHDN's API on invoice save, you are manually exporting data to a separate portal—which means missed validations, missed timestamps, and missed audit trails. Xero: Native integration, but validation gaps remain Xero built MyInvois submission into the Indonesian version of its platform in late 2024. When you create an invoice in Xero (Indonesia), it automatically submits to LHDN and returns a valid reference number. What works: Invoices serialize automatically on save LHDN reference number populates immediately Signed PDF stores in document history Batch corrections route through LHDN with proper versioning Where the gaps appear: Buyer NPWP validation happens at submit time, not before. If a buyer's tax ID fails DJP validation, the invoice has already been created (though marked invalid in LHDN). You will need to issue a corrected invoice, which creates audit noise. UKM invoice rules (invoices under Rp. 5M from UMKM sellers) are not pre-checked in the UI. You may create an invoice that should have been issued under UKM rules, realize it after submission, and then correct it. Multi-currency invoices require manual DJP approval before submission; Xero does not block or warn you on save. Xero's integration is the most complete among major Western platforms, but it is not foolproof. You still need a trained admin who understands NPWP validation and UKM thresholds before the invoice hits LHDN. QuickBooks Online: No native integration—manual export required QuickBooks Online does not have a native MyInvois connector. You create invoices in QB, then manually export them to the LHDN e-Faktur portal or a third-party bridge. What this means in practice: Invoice is created in QB with your own reference number You export to LHDN (or use a paid integration like Aspire or other local bridges) LHDN returns a serialized reference number You manually import the LHDN reference back into QB, or reconcile it manually during month-end Audit trail between QB and LHDN is your responsibility—it exists in two systems, not one This workflow is slower, more error-prone, and creates reconciliation debt. If a QB invoice is not exported within 24 hours of creation, you risk penalty exposure. If the exported invoice fails LHDN validation, you will not see the error in QB—you will see it in the LHDN portal, then have to go back and correct the QB record manually. QB remains popular in Indonesia because of its wider feature set and USD pricing, but MyInvois compliance is not its strength in 2025. Jurnal (Indonesia-native): Built for compliance, but limited to SMBs Jurnal is an Indonesia-first accounting platform owned by PT. Fintech Karya Indonesia. It was built with MyInvois in mind and has native DJP submission at its core. Jurnal's native strengths: Invoices submit to LHDN on save; no export step required NPWP validation is pre-checked against DJP registry before invoice creation UKM rules are built into the invoice form; the system guides you to the right invoice type Audit trail and corrected invoice versioning are automatic Pricing is local and invoice-volume based (not per-user) Where Jurnal falls short: Feature breadth is much smaller than Xero or QB. Multi-currency support is limited. Advanced reporting is basic. Integration with third-party tools (CRM, payment platforms, inventory) is sparse If you run a multi-regional business (Indonesia + Singapore + Malaysia), Jurnal is Indonesia-only API access for custom integrations is not well documented or supported Jurnal is excellent if you are a pure Indonesia SMB that invoices in IDR and does not need deep cross-border or inventory management. If you have any operational complexity beyond that, its gaps will become painful within 6–12 months. Orin: Unified invoicing with native MyInvois and local payment rails