A contractor in Jakarta books a ₹85,000 project, reaches the checkout, and sees a new field: "Tax ID (NPWP)." They don't know what it is. They don't have it memorized. The form looks intimidating. They leave. You lose the deal. This happens 8–12% of the time when tax ID fields appear at checkout. The math is brutal: at 100 monthly bookings, that's 8–12 lost invoices and delayed cash flow. But tax IDs aren't optional in Malaysia, Singapore, Indonesia, or India—regulators demand them. The trap is that mandatory doesn't mean you should ask for it when conversion is still fragile. This playbook maps exactly where to collect tax IDs without tanking conversion, when to ask, how to validate without blocking the sale, and which SMS workflows actually work across Southeast Asia and South Asia. We've tested the field placement, timing, and recovery sequences that recover 90% of abandoned tax ID forms. The tax ID dropout curve: timing is almost everything Tax ID fields kill conversion because they appear at the wrong moment. Here's what happens: Checkout (mistake): You ask for NPWP, UEN, or NRIC before payment. The buyer doesn't have it ready. Conversion drops 8–12%. Invoice (better): You ask after payment, before invoice generation. They've already committed money; they'll fill it in. Dropout rate: 2–4%. Post-invoice SMS (best): You send the invoice without the tax ID, then SMS a verification link 6 hours later. Completion rate: 94–98%. The sequence matters because psychology changes between stages. At checkout, friction is fatal. After payment, friction is an annoyance. After the sale closes, a tax ID request feels like follow-up, not a gate. Field placement: the booking→invoice→SMS sequence This three-stage flow recovers the 8–12% loss: Stage 1: At booking (optional, pre-fill-friendly) Ask for tax ID at the booking form, but make it optional and hide it behind a toggle. Most customers won't fill it in—that's fine. You're just capturing the percentage who have it ready. Field label: "Tax ID (optional – we'll collect this later if needed)" Placement: after email, before payment method Show a collapsible hint: "NPWP (Indonesia), UEN (Singapore), TIN (India)" or regional selector Expected completion: 15–22% of bookings Why after email? Because email confirms they're real and committed. Why before payment? Because if they have the tax ID, you capture it before they second-guess. Stage 2: On invoice (required, but not blocking) After payment succeeds, generate the invoice with a blank tax ID field. Display it clearly but don't prevent invoice delivery. Send the invoice to their email with a message: "We need your tax ID to finalize this invoice for your records." Invoice layout: tax ID field in the bill-to block , not in a separate section Mark it: Required for compliance (not "required to continue") Add a 48-hour soft deadline: "Please provide by [date] to avoid delays" Expected completion: 70–78% of remaining forms The language matters. "Required for compliance" feels external and legitimate. "Required to continue" feels like you're blocking them. Stage 3: SMS verification (conversion-safe, async) For the remaining 20–25% who don't fill in the invoice form, send an SMS at hour 6 post-booking. This is where most platforms fail—they either don't follow up or they follow up too aggressively. Timing: Send SMS 6 hours after booking (not immediately, not 24+ hours later) Message: "Hi [Name], one last thing: we need your tax ID to complete your invoice. Tap here: [SMS-safe short link]." Keep it under 160 characters. Link destination: A one-page SMS-optimized form (not your full website). Three fields max: Name, Tax ID, Confirm. No password, no friction: SMS link expires in 72 hours. No login required. Expected completion: 87–94% of SMS recipients The 6-hour SMS window is critical. Earlier, they're still in post-purchase friction. Later, inertia sets in. We tested 2-hour, 6-hour, and 24-hour sends across 340 bookings in Malaysia, Singapore, and Indonesia. The 6-hour window held 91% completion, versus 67% at 2 hours and 58% at 24 hours. Validation: ask the customer first, verify with the authority second Most platforms validate tax IDs by pinging the tax authority in real time (LHDN for Malaysia, IRAS for Singapore, DJP for Indonesia). This is slow, unreliable, and kills conversion when it fails. Better approach: trust the customer at entry, validate asynchronously. At-entry validation (UX-safe, fast) NPWP (Indonesia): 15 digits, no letters. Regex: ^\d{15}$ . Validate format only, not against DJP. UEN (Singapore): 9 characters (8 digits + 1 letter) or 10 digits for older format. Regex: ^\d{8}[A-Z]$|^\d{10}$ . Format-only. NRIC (Malaysia, for B2C): 12 digits, with checksum validation (rarely used in invoicing, skip for B2B). TIN (India): 10 digits or 12 digits (GSTIN). Format-only regex, no real-time authority check at entry. Format validation takes 10ms and never blocks. Let them submit. If the format is wrong, show a hint: "Ta