Your contractor submits an invoice Monday morning. You run the tax ID batch check that evening. The system reports back Wednesday. Payment clears Friday. Your contractor waits 72 hours for a valid NPWP check that could have run in 90 seconds. This is not a friction problem. It is a cash-flow and fraud problem baked into how most accounting platforms handle tax ID validation in Indonesia, Malaysia, and Singapore. Batch NPWP checks—weekly or daily sweeps that validate contractor tax numbers against government databases—cost you three days of float while missing 14% of forged IDs that real-time validation would catch instantly. The gap matters because contractor payments are your fastest cash-to-counterparty handoff. A late payment creates friction; a forged tax ID creates a withholding liability you discover months later during audit. How batch NPWP validation wastes 72 hours Most platforms batch-process tax ID validation for cost and infrastructure reasons. The cycle looks like this: Monday 09:00 : Contractor submits invoice with NPWP. Monday 23:00 : System queues invoice for batch validation run. Tuesday 02:00 : Batch job executes. Government API responds. Invoice validation stored in queue. Wednesday 09:00 : Accounting team reviews batch report. NPWP marked valid (or invalid). Wednesday 14:00 : Payment initiated. Friday : Funds arrive. Three delays nest inside this flow: Queue wait (14+ hours): Invoice sits until the next scheduled batch run. Batch processing (2–6 hours): The job runs at off-peak times, not on demand. Review lag (6–24 hours): Batch results require human review before payment clears. For a single contractor, 72 hours is inconvenience. For a team managing 50–200 monthly invoices, batch validation means a contractor queue permanently sits 1–3 days behind submission. Cash-on-hand shrinks because you are funding two days of float for every invoice processed. Why batch checks miss forged tax IDs The second cost is invisible until audit. Batch validation queries government databases (Dirjen Pajak in Indonesia, LHDN in Malaysia, DGT in Singapore) once per run. If the database is down, slow, or the query fails partially, the batch marks the NPWP as valid by default—a fail-open design that prioritizes throughput over accuracy. Real data from Indonesia's e-Faktur system shows batch NPWP validation misses 14% of forged or inactive tax IDs because: Database lag : Government systems update in real-time for active IDs but delay deactivations by 24–48 hours. A batch run Tuesday morning will not catch an NPWP deactivated Monday afternoon. Timeout handling : When API requests exceed 5 seconds, most batch systems mark the record as pending (not rejected). Pending invoices stay in your system and get paid anyway. Partial dataset queries : Batch jobs validate the tax number itself but often skip secondary checks—director name match, address cross-reference—because they slow the batch cycle. No real-time revocation check : If a contractor's NPWP is revoked mid-day, a batch process running that night will not catch it. The invoice pays normally. By contrast, real-time validation queries the government database on demand, at invoice submission, with full timeout enforcement and fallback rules that require manual review if the API fails. Forged IDs are caught before the invoice enters your accounting system. Real-time NPWP validation cuts payment to 2 hours A real-time flow collapses the delays: Monday 09:00 : Contractor submits invoice with NPWP. Monday 09:02 : System validates NPWP in real-time against government database. Response confirms active, valid ID. Monday 09:05 : Invoice approved automatically. Payment queued. Monday 14:00 : Payment clears (same-day or next-day depending on payment rail). The second contractor in your queue sees the same 2-hour turnaround. By Wednesday, all 15 invoices submitted over the week are paid, instead of 5 or 6 sitting in batch-validation limbo. Real-time validation requires three components: Synchronous API integration with government tax databases (not asynchronous batch jobs). Dirjen Pajak, LHDN, and DGT all expose NPWP lookup APIs; most platforms do not integrate them this way because of infrastructure cost. Hard timeout enforcement : If the API does not respond in 5 seconds, the invoice is flagged for manual review—not auto-approved. Cross-field validation : Match not just the NPWP but the registered director name and business address against the invoice submitter. A real NPWP paired with mismatched details is a fraud signal. Platforms that implement this (like Orin's real-time invoicing validation ) can validate an NPWP while the contractor is still filling out the invoice form—giving them instant feedback if the ID is invalid, rather than discovering it three days later. Integration with government databases: What it takes Real-time NPWP validation means directly hitting these APIs: Country API Query Speed Revocation Update Lag Indonesia Dirjen Pajak NPWP lookup 1–3 sec