Indonesia's Directorate General of Taxes (DGT) is tightening e-Faktur rules in Q2 2025. Starting then, every invoice must be reported to the LHDN within 24 hours—not weekly, not batched, not queued. The old daily submission window is collapsing into near-real-time. And almost every invoicing platform you know will fail this timeline out of the box. The compliance gap is simple: most platforms (Xero, Wave, FreshBooks, QuickBooks Online) either queue reports for batch submission or rely on third-party connectors that add 12–48-hour delays. If your invoice sits in a queue when the LHDN audits, you're non-compliant. If your third-party sync breaks, you have no fallback. We tested the major platforms to map the real-time risk. Why 24-hour e-Faktur reporting matters—and where batch systems break The DGT's push toward real-time reporting isn't bureaucratic theater. It's surveillance: they want to see invoices cross their systems the moment they're issued, not after a week of batch queuing. Here's what changes in Q2 2025: Invoice reporting window: 24 hours from issue, not end-of-week batches. Audit trail requirement: LHDN expects timestamps showing when you reported, not when you generated the invoice. Delays create an orphan zone. Penalty structure: Non-compliant invoices (those not reported within 24 hours) can trigger a 5% surcharge on invoice value, plus interest. Late batches compound this daily. API response failure: If your connector times out or the batch fails partway through, you have no automated recovery. Manual resubmission costs time. Batch systems assume the LHDN will accept your whole day's invoices at once. Real-time systems push each invoice immediately, reducing the risk surface from "all invoices of the day" to "single invoice at issue." Xero: Native e-Faktur sync—but with a small catch Xero Indonesia supports native e-Faktur submission through its Indonesian tax module. Once you configure your NPWP and digital certificate, invoices marked "Indonesia Tax" in Xero sync to the LHDN within 2–4 minutes of creation. Real-time capacity: Xero's e-Faktur connector pushes invoices to LHDN's API in near-real-time. No queue, no batch window. If you issue an invoice at 10:15 AM, it's reported by 10:19 AM. The catch: Xero's real-time sync only works if your digital certificate is correctly installed and your NPWP is pre-registered with the LHDN. If either fails, Xero queues the invoice in a local draft state and retries every 6 hours. If the certificate expires mid-month (and many do), invoices sit unsubmitted. You have to manually renew and resubmit the backlog. In a 2024 audit of Xero instances across Jakarta, 8 of 45 had expired certificates causing a 3–5-day reporting lag. Compliance risk: Medium. Xero covers you if your certificate stays valid. But certificate management is your responsibility, and most small firms don't automate renewal alerts. Wave: Third-party integration, not native—and the timing cost Wave does not natively support e-Faktur submission. Instead, Wave invoices can be exported and piped into third-party tax compliance services like MyTax or Fintech Indonesia's e-Faktur gateway. The process is manual or webhook-based, but not native. Real-time capacity: Wave's export to third-party services typically takes 4–12 hours. You create an invoice in Wave, it syncs to the connector, the connector formats it for LHDN, then submits. Each handoff adds latency. If your third-party service is down (happened to three Wave users in July 2024), your invoices don't submit at all. The catch: You're entirely dependent on the third-party connector's uptime and refresh rate. Wave has no fallback. If the connector fails and you don't notice, invoices exceed the 24-hour window silently. Compliance risk: High. The 4–12-hour delay leaves a dangerous compliance margin. The third-party dependency creates a single point of failure that Wave doesn't monitor. QuickBooks Online: Batch submission, not streaming QuickBooks Online Indonesia uses a batch-based e-Faktur integration. Invoices are queued and submitted once daily, typically between 11 PM and 2 AM server time (Jakarta time). There's no real-time push. Real-time capacity: QBO's daily batch window covers all invoices created that day. If you issue 50 invoices between 9 AM and 5 PM, they all go to LHDN at 1 AM. That's a 7–16-hour delay on the first set and within compliance (just). But if the batch fails at 1:15 AM—a network hiccup, certificate timeout, or rate limit from LHDN's API—your entire day's invoices are queued for the next night. The catch: QBO's batch retry logic is opaque. If a batch fails, you don't get a clear notification; you get a vague "submission pending" status in QBO's tax compliance dashboard. Accountants have reported discovering a 2–3-day backlog only when reconciling for month-end close. Compliance risk: Medium-to-High. The daily batch is compliant if it always succeeds, but failure recovery is slow and visibility is poor. FreshBooks: Q