A contractor submits an invoice with a fake tax ID on Tuesday at 2 p.m. Your batch validation runs Wednesday morning at 9 a.m. The fake invoice sits in your system for 19 hours, moves through approval, gets coded to the GL, and triggers a payment. By the time your batch check flags it, the money is already moving and your compliance officer is writing apology emails to tax authorities. This is not hypothetical. Batch tax ID validation—the default for most accounting software, CRM platforms, and invoicing tools—creates a 12- to 24-hour window where fraud, mismatched identities, and invalid registrations live unmolested inside your system. Real-time validation APIs close that window to seconds, but they cost more and require integration work. The question is not whether real-time is better. It is whether the cost of a compliance fine, a delayed payment, or a rejected invoice dwarfs the cost of real-time infrastructure. Why batch checks fail: The 19-hour fraud window Most platforms validate tax IDs in one of two ways: batch jobs that run once or twice daily, or manual verification by your team. Here is what actually happens: Batch jobs. Your accounting software (Xero, QuickBooks, FreshBooks) syncs supplier or contractor records to a tax authority database once a day, typically between 9 p.m. and 4 a.m. If a record is invalid, you get an email the next morning. By then, the invoice is already in your approval queue. Manual verification. Your team spot-checks tax IDs as they enter the system. This works if you have three contractors per month. It fails at scale—ten per week, fifty per month, or worse, if your CRM or invoicing tool auto-imports supplier lists from your marketplace or partner network. No verification. Many small platforms (including early-stage CRMs and lightweight invoicing tools) do not validate at all. The tax ID field accepts anything. Real-time validation APIs query a live database—such as Malaysia's MyInvois , Singapore's ACRA , or Indonesia's Indigo —the moment a tax ID is entered or an invoice is submitted. If the ID is invalid, the form blocks submission. If it is valid but mismatched to the company name, the API returns a red flag before the record reaches your GL. Real-time APIs: Indigo, MyInvois, and the cost per validation The three largest real-time tax ID validation APIs in Southeast Asia are: MyInvois (Malaysia) MyInvois is Malaysia's real-time e-invoice system operated by the Royal Malaysian Customs Department (RMCD). It validates SSID (Service and Sales Tax identification) and company registration numbers in real time. Cost per validation: ₹0–₹2 (free for registered e-invoice providers; small premium for ad-hoc queries). Latency: 200–500 ms (acceptable for form submission, problematic for bulk batch imports). Coverage: Malaysia only. API limit: 1,000–5,000 requests per day for free tier; unlimited for enterprise licenses. MyInvois returns a structured response: valid/invalid, company name, tax status, and compliance alerts (e.g., revoked license, delinquent filing). You can block or flag invoices before they hit your GL. Indigo (Indonesia) Indigo is Indonesia's tax authority API for NPWP (Nomor Pokok Wajib Pajak) validation. It requires direct registration with Indonesia's Directorate General of Taxes. Cost per validation: ₹1.50–₹5 (per query; bulk contracts are cheaper). Latency: 300–800 ms (slower than MyInvois; requires VPN or whitelisted IP). Coverage: Indonesia only. API limit: Usually 500–2,000 requests per day; exceptions for high-volume partners. Indigo is stricter than MyInvois. It validates NPWP format, cross-references business type (CV, PT, PPN-registered, etc.), and flags dormant or inactive registrations. An invalid NPWP rejection from Indigo is final—no workaround. ACRA (Singapore) Singapore's Accounting and Corporate Regulatory Authority (ACRA) does not offer a public API, but several third-party providers (Stripe, GoCardless, Orin) integrate with ACRA's database through enterprise agreements. Cost per validation: ₹0.50–₹1.50 (bundled into platform fees; rarely itemized). Latency: 100–300 ms (fastest of the three). Coverage: Singapore company registration numbers only. API limit: Unlimited for registered partners. ACRA validation is fast and reliable, but only covers Singapore entities. If you invoice Malaysian suppliers or Indonesian contractors, ACRA is worthless without MyInvois and Indigo in parallel. Integration cost and time: Orin, Stripe, QuickBooks Real-time validation only works if it is wired into your invoicing, CRM, or contractor-onboarding flow. Here is the integration burden for three platforms: Orin (native real-time validation) Orin has built-in real-time tax ID validation through Orin Billing and Orin CRM . When a supplier is added or an invoice is created, the tax ID is validated against MyInvois, Indigo, and ACRA APIs in parallel. Setup time: 5–15 minutes (enable validation in supplier settings; configure which APIs to use based on country). Cos