Tax ID validation on WhatsApp

Q: What if a client doesn't have a tax ID yet?

In Malaysia, sole proprietors operating below the SST threshold don't need registration. In Indonesia, some very small businesses may not have NPWP. In these cases, you can issue a domestic invoice without a tax ID, but confirm with your accountant first. Store a note in your CRM explaining why the field is blank—this protects your audit trail.

Q: Can I validate tax IDs in real time on WhatsApp?

Malaysia and Singapore have public lookup databases (Royal Malaysian Customs, ACRA). Indonesia's e-Faktur system allows NPWP verification, but it requires login. For most SMBs, format validation + document verification is sufficient. Deeper checks are optional but useful for high-value contracts.

Q: What if a client has multiple legal entities?

Create a separate contact record for each entity in your CRM. Link them to the same 'parent' account or company so you can see the relationship. When invoicing, always confirm which entity you're billing and use that entity's tax ID.

Q: How long should I keep tax ID records?

Keep them for at least 7 years in most of Southeast Asia—this matches standard corporate tax record retention. Store them securely in your CRM or accounting system, with an audit log showing when they were verified and by whom.

Your invoice sits unsigned in a client's inbox. Three days later, their finance team rejects it because the tax ID doesn't match their registration. You send a follow-up asking for the correct number. A week passes. Cash flow stalls. This happens because tax IDs are collected late, validated later, or not validated at all. In Southeast Asia—where Malaysia enforces SST registration, Indonesia mandates NPWP submission, and Singapore requires UEN on every B2B invoice—a wrong or missing tax ID doesn't just delay payment. It can trigger audit flags and make the invoice non-deductible on the buyer's side. The fix is simple: collect tax IDs early over WhatsApp, validate them in your CRM before you draft the invoice, and keep a clean audit trail. This guide shows you how. Why tax ID validation matters in Southeast Asia Each country in the region has its own tax ID requirement, and they're not optional. Here's what each one is: Malaysia: Service and Sales Tax (SST) Registration Number (usually 12 digits). Required for any B2B invoice where the seller is SST-registered. Indonesia: Nomor Pokok Wajib Pajak (NPWP)—15 digits. Mandatory for invoicing and e-Faktur submission to the tax authority. Singapore: Unique Entity Number (UEN)—8 or 9 alphanumeric characters. Required on invoices for GST-registered businesses. Thailand: Tax Identification Number (TIN)—13 digits. Needed for VAT invoicing and corporate tax filing. If you invoice without matching the buyer's registered tax ID, two things happen: the buyer's accountant flags the invoice as non-compliant (delaying their payment approval), and you create audit risk for yourself. In Indonesia, a missing or mismatched NPWP blocks e-Faktur submission entirely. Collecting the right tax ID on day one saves a 7–14 day follow-up loop later. It also eliminates rejected invoices and reduces your audit surface. Build a WhatsApp tax ID collection checklist The best time to ask for a tax ID is during first contact or contract signing—not when you're about to invoice. Use your WhatsApp workflow to collect it alongside other onboarding details. For Malaysia (SST) Send: "Hi [Name], to process your invoice, we'll need your SST Registration Number (usually on your invoice header or MySST portal). Format: 12 digits." Receive and ask: "Is this a sole proprietor (no SST), a small business with SST, or a corporate account?" This shapes what you ask for. Validate: Check against the Royal Malaysian Customs Department's online SST lookup (optional but thorough). Most accountants can verify format quickly. Store in CRM: Add a custom "SST Registration" field and mark it verified. For Indonesia (NPWP) Send: "We need your NPWP (Nomor Pokok Wajib Pajak) to complete your invoice. It's 15 digits and usually in your e-Faktur account or tax ID card." Receive: Ask for a photo of their tax ID card or tax filing document if you're uncertain. Validate: Check format (15 digits, often formatted XX.XXX.XXX.X-XXX.XXX). Cross-reference against their company name in your system—mismatches flag potential data entry errors. Store in CRM: Create an "NPWP" field, attach the verification document, and link it to the contact. For Singapore (UEN) Send: "Please share your UEN (Unique Entity Number) for invoicing. You can find it on your ACRA registration or invoice header." Receive: UEN is usually 8–9 characters (e.g., 123456789A). Validate: Optionally check against ACRA's online database, but format is usually enough for most invoicing workflows. Store in CRM: Add "UEN" field and note the verification date. For Thailand (TIN) Send: "We need your Thai Tax ID (TIN) for VAT invoicing. It's 13 digits, usually on your tax filing documents." Receive: Format is typically XX-XXX-XXXXX-XX. Validate: Confirm format and ask for a supporting document if the number looks unusual. Store in CRM: Add "TIN" field to your contact record. Validate in your CRM before invoicing Once you've collected the tax ID, your CRM should validate it before you generate an invoice. Here's how to set this up: Create a validation checklist in your contacts view Add a custom field to your CRM contacts for each region's tax ID. Mark it as "required" before you can move a contact to "ready to invoice." Your CRM should flag incomplete or mismatched data. Build a pre-invoice automation Set up a workflow that: Triggers when you're about to create an invoice Checks: Is the tax ID field populated? Checks: Does the format match the country's standard (15 digits for Indonesia, 12 for Malaysia, etc.)? Checks: Does the name on the tax ID match the contact name in your system? If any check fails: pause the invoice draft and send a notification to you (not the client) with the mismatch details If all checks pass: allow invoice generation This takes 2–3 minutes to configure in most CRMs and saves hours of back-and-forth later. Use a data audit trail Log when the tax ID was collected, who verified it, and which document it came from. If your CRM supports activity history,