Indonesian finance teams face a recurring problem: their accounting software works fine until they need to close a tax period. That's when LHDN compliance hits—and most tools suddenly need consultants, API bridges, or manual CSV uploads. We tested Xero, SAP, Wave, and one native Indonesian alternative against three real compliance gates: native e-Faktur submission to LHDN MyInvois, NPWP validation on every invoice, and tax-period closing without manual reconciliation. One platform passes all three. The others require workarounds you'll pay for monthly. The core problem: e-Faktur submission is not optional Indonesia's LHDN (Direktorat Jenderal Pajak) requires all invoices above Rp 5 million to submit as e-Faktur through MyInvois. This is not a suggestion. If your invoicing software cannot validate NPWP, match the company tax ID to the invoice, and submit the XML directly to LHDN's API—you are generating rejected invoices. Late or rejected invoices trigger: Audit flags on your tax returns (and your customer's, if they're the buyer) Penalties ranging from Rp 500,000 to Rp 5 million per invoice Cash flow delays (buyers won't pay until the invoice is valid in MyInvois) Manual correction work that scales with invoice volume This is why accounting software choice in Indonesia is not a feature comparison—it's a compliance decision. Xero: works, but requires integration setup Xero handles NPWP validation and e-Faktur submission, but not out of the box. Here's what actually happens: NPWP validation: Supported via custom field or Xero's Indonesia tax module. You must map your customer NPWP to the contact record. If you miss one, that invoice fails validation. e-Faktur submission: Xero does not submit directly to LHDN. Instead, you integrate via a third-party bridge (commonly Javan, Kledo, or Incodoc). These APIs pull invoice XML from Xero and push it to MyInvois. Submission happens within 24 hours, usually. Tax-period closing: Manual work. You must download all invoices, verify they passed MyInvois, reconcile rejections, and resubmit. For teams with 50+ invoices per month, this takes 3–5 hours. Cost reality: Xero (USD 11–62/month) + e-Faktur bridge (typically USD 10–30/month) + your team's integration time (8–16 hours setup, 2–4 hours monthly maintenance). For small teams, the bridge subscription is non-negotiable. When Xero works: If you already have an accounting person who understands NPWP matching and e-Faktur flow, and you're willing to pay for a bridge integration, Xero is functional. It's not native, but it's reliable once set up. SAP: overkill for most Indonesian SMBs, but native compliance SAP (any version: S/4HANA, Business One) includes native LHDN e-Faktur modules. NPWP validation, MyInvois submission, and tax-period reporting are built in. No third-party bridge required. The catch: SAP costs USD 3,000–15,000 per month for a company under 100 staff. Implementation takes 3–6 months. Training eats another 2–4 weeks. And you will need a dedicated SAP accountant. SAP makes sense if you have: Multi-entity invoicing (different NPWP per branch or legal entity) Complex inter-company transactions High invoice volume (1,000+ per month) Existing SAP infrastructure For a 10-person team invoicing 100 customers? SAP is a sledgehammer. Wave: free, but breaks on tax compliance Wave is popular because it costs nothing. But in Indonesia, it breaks on every tax requirement: NPWP validation: Not built in. You can add a custom field, but Wave has no logic to validate the format or cross-check it against LHDN's database. e-Faktur submission: Wave does not support MyInvois integration. You cannot submit directly to LHDN from Wave. You must export as CSV, import into another tool, or manually enter data into MyInvois portal. Tax-period closing: Wave tracks invoices, but not their LHDN submission status. You have no way to know if an invoice was accepted or rejected without logging into MyInvois separately. Wave works for US or Canadian teams invoicing in USD. It does not work for Indonesian tax compliance. The native option: ERPNext and Javan (Indonesia-focused stack) ERPNext is open-source accounting software. On its own, it has no LHDN integration. But if you deploy it with Javan (an Indonesia-native e-Faktur API), you get: Native NPWP validation (ERPNext + Javan logic) Direct e-Faktur submission to MyInvois (within 30 minutes of invoice creation) Tax-period reports showing LHDN acceptance/rejection status Compliance audit trail (which invoices were submitted, when, status) Cost: ERPNext hosting (USD 20–100/month depending on provider) + Javan API (USD 10–30/month based on invoice volume). Total: USD 30–130/month. Trade-off: ERPNext requires technical setup or a consultant to implement (1–3 weeks). It's not a point-and-click SaaS. But once live, it requires almost no ongoing integration work. This is the option most Indonesian finance teams should evaluate but don't, because ERPNext isn't marketed to SMBs the way Xero and Wave