Tax ID collection at signup feels inevitable. You need it to invoice, to comply with regional tax authorities, to validate who the client actually is. But ask for it on the first screen, and you watch your conversion rate crater—especially in Southeast Asia, where clients distrust forms and expect instant, friction-free onboarding. The solution isn't to skip tax ID collection. It's to move it. And to make it conditional, validated in real time, and introduced only when the friction is bearable. When to collect: intake versus invoice time Your first instinct—grab the tax ID at signup—is also your worst one. Here's why: Signup is not identity verification time. A prospect entering your form hasn't yet committed to buying. They're exploring. Asking for a 15-digit NPWP right then feels like a security interrogation, not a welcome. Tax IDs vary by region and entity type. A freelancer doesn't have a UEN. A sole trader in Malaysia may not have registered for GST. A corporate buyer has multiple possible identifiers. Asking for one format at signup creates a validation wall that stops 15–30% of traffic before they can even proceed. You often don't need it until invoice time. If a prospect is still in discovery or evaluation, their tax ID doesn't matter to you yet. You need it when you create an invoice. Collecting it earlier costs you conversions for no functional gain. The pattern that works: Collect contact basics at signup (name, email, phone). Defer tax ID to the invoice workflow. In Orin's invoicing system , that means a triggered moment—the first time someone creates an invoice or you generate one for them—when you ask for the missing field. By then, they're committed. They're ready to move forward. The friction is justified by the next step. Progressive disclosure: reveal fields only when needed If you must collect tax ID earlier (e.g., for compliance with local laws, or because your accounting system requires it before creating a contact), use progressive disclosure. Show fields in stages, not all at once. Step 1: Entity type. Ask one question first: "Are you a business or a sole trader?" This is binary, low-friction. A radio button. No shame in answering wrong—they can change it. Step 2: Country. Next: "Where are you based?" This determines which tax ID formats are even relevant. A business in Indonesia doesn't need a UEN; they need an NPWP (Nomor Pokok Wajib Pajak). Step 3: Conditional tax ID field. Only now show the tax ID field—and show the right one. Label it with the actual name: "NPWP" if they picked Indonesia, "UEN" if they picked Singapore. Include a short helper text: "Format: 15 digits" or "9 digits, no hyphens." This flow cuts form abandonment by 20–35% compared to showing all three fields at once. Why? Because people aren't overwhelmed. Each step feels finite. And by the time they reach the tax ID field, they already know why it matters—the form has scaffolded them toward that moment. Real-time validation: fail fast, help immediately The worst tax ID form shows an error only after submission. Client enters a 14-digit NPWP (missing one digit), clicks submit, and waits three seconds for a red error message. Now they're frustrated, confused, and likely to drop out. Real-time validation catches the error as they type. After they've entered enough characters, check the format instantly. If it's wrong, show a specific hint: "NPWP must be 15 digits. You've entered 14." Validation rules by region: Indonesia (NPWP): 15 digits, no spaces or hyphens. Format: XXXXXXXXXXXXXXX. Some platforms also validate against the National Tax Office (Ditjen Pajak) API for real ownership, but client-side format validation alone prevents 90% of abandonment. Singapore (UEN): 9 characters, format varies. Businesses: 8 digits + 1 letter. Non-profits and sole proprietors: 7 digits + 1 letter, starting with S or T. ACRA publishes a checksum algorithm; implement it to validate before submission. Malaysia (SST ID / Tax ID): 12 digits for SST (Sesuatu Satu Tanda). Format: XXXXXXXXXX-XX. Some larger entities also have a 10-digit BRN (Business Registration Number). Ask which applies; don't force both. Thailand (TIN): 13 digits. Grouped as X-XXXX-XXXXX-XX in display, but stored without hyphens. Vietnam (Tax Code): 10 or 14 digits depending on entity type. Ask entity type first, then validate against the right length. Build this validation into your intake form using a regex or a lightweight library (e.g., libphonenumber for phone, similar open-source tax ID validators for your regions). Show feedback inline, before they submit. If they can't get the format right, offer a link: "Not sure of your tax ID? Look it up here ." (Ditjen Pajak in Indonesia, ACRA in Singapore, etc. all have public lookup tools.) Conditional fields: don't ask for what you don't need A sole trader in Malaysia doesn't have a BRN. A freelancer in Singapore likely doesn't have a UEN. A micro-enterprise in Indonesia may not yet be registered with tax authorities at