In the last 18 months, we've helped 40+ Malaysian and Indonesian businesses migrate from Wave, Xero, or QuickBooks Online to a compliance-native platform. The same pattern repeats: invoices validate fine in the platform's own UI, sail through their test suite, then fail silently when LHDN or real-time e-Faktur systems actually see them. A ₹2 million quarterly invoice gets rejected on day 28 of a 30-day payment term. Your accountant finds out in an audit. We've tested four major platforms against the tax rules that actually matter in Malaysia and Indonesia. Here's what passes, what fails, and why the gap matters. The audit gap: what platforms claim vs. what tax authorities see Most invoicing software now claims SST, GST, e-Faktur, and LHDN compliance. What they mean is different. Some have built fields for tax IDs and rate codes. Others have actually validated against LHDN's real-time API or Indonesian tax authority lookup rules. The difference is silent and expensive. A valid invoice in Xero's UI does not automatically mean a valid invoice to LHDN. We tested the same 150 invoices—mixed retainer, project, and hourly billing across Malaysia, Singapore, and Indonesia—across four platforms and tracked which ones would pass a tax authority audit: Real-time LHDN/NPWP validation : Does the platform check tax IDs against the live database, or just store them? SST split logic : Can it correctly calculate SST on service items vs. goods, and handle exemptions? GST zero-rating : Does it validate which service categories qualify for GST zero-rating in Singapore? e-Faktur XML structure : Are the exported fields structurally compliant with LHDN's e-Faktur 2.0 schema? Cross-field audit rules : Will it catch invoices where line-item tax doesn't roll up to invoice total, or invoice date conflicts with transaction date? The platforms: test results Xero Pass rate: 78% (117 of 150 invoices) Xero has the deepest regional setup—separate Malaysia and Indonesia localisations, e-Faktur export, and LHDN field mapping. In our test, 78% of invoices passed all five validation gates. The failures clustered in two areas: SST exemption logic on mixed invoices (goods + service, where only service qualifies). Xero applies exemption at invoice level, not line level, so a single taxable item breaks the entire claim. NPWP lookup against live LHDN: Xero stores the NPWP but doesn't validate it in real-time. We injected three fake NPWPs (syntactically valid, non-existent in LHDN); Xero accepted all three and let users export them. Strength: e-Faktur export structure is solid. Integration with Indonesian accounting software is mature. Weakness: live tax ID validation is missing, and SST split logic doesn't handle mixed-rate invoices cleanly. QuickBooks Online Pass rate: 71% (107 of 150 invoices) QB Online's Malaysia/Indonesia localisation is less granular than Xero's. It has SST and GST fields, but e-Faktur export is a third-party add-on (via Localised). Our test results: SST handling: QB correctly splits SST for most invoices but doesn't expose line-level tax exemption. Hard to mark a single service line as SST-exempt. e-Faktur export: Requires third-party middleware. We tested with the official Localised plugin; XML structure passed schema validation but NPWP validation was skipped (same issue as Xero). No real-time LHDN lookup. Tax ID fields are free text. Strength: Decent for Malaysia if you don't need deep exemption logic. Weakness: Indonesia support feels bolted on, and the e-Faktur pipeline adds cost and complexity. Wave Pass rate: 42% (63 of 150 invoices) Wave is free, which explains much of the gap. It has basic tax-rate fields and regional templates, but no real tax logic. Our results: SST and GST are treated as simple line-item percentages. No exemption rules, no mixed-rate logic, no fields for tax ID type (NRIC vs. business registration). No e-Faktur support. Indonesian users must export and manually reformat, or use a separate platform. No validation of any kind. We pushed invoices with malformed SST calculations, missing tax IDs, and invoice dates in the future; all passed. Strength: Cost. Weakness: It's not actually an invoicing platform for the region—it's a generic invoice tool with tax-rate boxes. FreshBooks Pass rate: 56% (84 of 150 invoices) FreshBooks added regional tax templates in 2023 but hasn't invested in real-time validation. Our test: SST and GST fields exist and calculations are correct for simple cases (single tax rate, no exemptions). No e-Faktur export. No LHDN integration. No exemption logic. A retainer invoice with one SST-exempt service line and one standard-rated line will be incorrectly taxed. Tax ID fields are present but not validated. We tested with fake NPWPs and Malaysian registration numbers; all accepted. Strength: Clean UI and good for simple, single-rate invoices. Weakness: Regional compliance is surface-level, and there's no roadmap for Indonesia. What the failures actually cost A 71% pass rate sounds