You saved an invoice last Tuesday with a tax ID that looked correct. Your accountant filed it Thursday. Monday morning, LHDN rejected it. The tax ID was forged—a single digit shifted, or a duplicate from a contractor flagged six months ago. By then you're in remediation: file an amendment, contact your client, re-invoice, explain the delay to tax authorities. Two weeks of your time. A compliance black mark. Real-time tax ID validation stops this. Not after you file. At save. Before the invoice ever reaches your accountant's inbox. The fraud patterns LHDN catches (and you miss) Batch validation—running overnight checks after invoices are already filed—catches maybe 60% of tax ID fraud. LHDN audits catch the rest, and by then you're liable. Here are the three most common patterns: Forged NPWP (Malaysia). A contractor supplies an 12-digit ID that passes basic length checks but fails the Ministry of Finance checksum. Batch systems often skip checksum validation. Real-time validation catches it before you hit save. Mismatched UEN (Singapore). The UEN doesn't match the registered business name in ACRA. Your invoice has Company X, but the UEN points to Company Y—a shell or closed entity. IRAS flags it as high-risk. Duplicate tax IDs. The same NPWP or UEN appears on two invoices to different vendors in the same fiscal period. A sign of identity fraud or a compromised contractor account. Real-time checks across your invoice history catch it instantly. Real-time validation at invoice save blocks 98% of tax ID fraud before it reaches your accountant. Batch checks miss 14% of forged IDs and 22% of duplicates flagged within 72 hours. How real-time validation works: three integration patterns You don't need to wait until invoicing happens to validate. Validation can trigger the moment a tax ID enters your system—in your accounting software, CRM, or booking tool. Here are the three most common setups: Pattern 1: Native validation in Orin invoicing Orin's invoicing module includes real-time tax ID validation for Malaysia (NPWP), Singapore (UEN), and Indonesia (NPWP) out of the box. When you enter a tax ID and hit save, the system checks it against Ministry databases in under two seconds. If it fails, the invoice won't save—you get a reason code (checksum error, not registered, duplicate on file). This is the fastest path: no third-party integrations, no API calls, pure speed. Setup cost: zero. Activation: immediate, no configuration needed for Malaysian and Singapore invoices. For Indonesia, you'll need to whitelist your tax ID with the Ministry's API first (a 15-minute one-time step). Pattern 2: Zapier + API for QuickBooks or Xero If you use QuickBooks or Xero, you can layer real-time validation on top using Zapier and the Orin API . The flow: Invoice is created in QuickBooks/Xero. Zapier webhook fires immediately. Orin API validates the tax ID against government databases. If validation fails, Zapier creates a task in your CRM or posts to Slack, blocking the invoice from being marked as sent. If validation passes, Zapier adds a tag ('tax-id-verified') and the invoice proceeds normally. Setup cost: ₹2,000–4,000 for integration configuration. Monthly cost: Zapier Standard (₹1,500/month) + Orin API calls (₹200–400/month depending on invoice volume). Activation: 2–3 hours. This pattern works well if you're already on QuickBooks or Xero and want to keep your accounting stack unchanged. Pattern 3: Integromat (Make) for complex workflows If you need conditional logic—e.g., validate contractor tax IDs only, or validate only invoices above ₹50,000—Make (formerly Integromat) is cheaper and more flexible than Zapier at scale. The flow: Invoice created in your accounting software. Make webhook fires. Make filters: if vendor type = contractor AND amount > threshold, proceed to validation. Orin API validates tax ID. If invalid: Make creates a PDF exception report and emails your accountant. If valid: Make updates a compliance log in Airtable or Google Sheets. Setup cost: ₹1,500–3,000. Monthly cost: Make Free tier (up to 100 invoice validations/month), or Make Standard (₹800/month) for 1,000+ monthly validations. This is the most cost-effective path for mid-size teams with high invoice volume. Building your audit trail for compliance Real-time validation is useless if you can't prove you did it. Tax authorities want three things: When you validated. A timestamp for each tax ID check, logged at invoice save, not afterward. What you checked. The exact tax ID, the business name, the invoice date. What the system returned. Pass, fail, and the reason code (checksum error, not registered, duplicate). All three integration patterns above log this automatically. In Orin native invoicing, it's built into the invoice audit trail. In Zapier or Make, configure your logging to send every validation result to a Google Sheet or Airtable base—this becomes your compliance report. Most tax audits last 4–6 weeks; this log proves you were diligent from da