Onboarding a client in Malaysia looks nothing like onboarding in Singapore or Indonesia. The tax IDs are different. The employment documents change. The invoicing rules shift. Yet most businesses run a single checklist and manually adapt it per country—which means missed requirements, delayed starts, and compliance gaps that surface months later at audit time. The fix is a branching onboarding workflow: one entry point, automatic country detection, conditional document collection, and a clear handoff point where human judgment replaces automation. This playbook shows you how to build it and where your platform needs to carry the load. Why a single onboarding checklist fails across the region Three countries, three tax regimes, three employment frameworks. Malaysia: Requires a valid MyInvois registration (or exemption reason), SOCSO number if paying contractors, and service tax (SST) clearance for certain sectors. Singapore: Needs UEN (Unique Entity Number), CPF clearance if hiring, and GST registration status (even if not registered yet—you need to know why). Indonesia: Requires NPWP (tax ID), SIUP (business license), and, since 2024, e-invoice reporting compliance confirmation. Collect the wrong doc and you can't invoice. Miss a tax status and you'll misfile compliance reports. Assume a contractor doesn't need SOCSO coverage in Malaysia and you've exposed yourself to labor claims. A templated checklist works until a client from a different country arrives. Then you're manually editing, forgetting steps, and creating debt to yourself—risky work done in a spreadsheet or email thread instead of a system. The three-layer branching structure Build your checklist in three layers: universal, country-specific, and manual-handoff. Layer 1: Universal intake (always required) Legal entity name and registration number (country of incorporation). Primary contact name, email, phone. Billing contact (may differ). Contract signatory (does the primary contact have authority?). Payment method and currency preference. These fields auto-collect regardless of country. No branching yet—just gather the foundation. Layer 2: Country-specific document rules Once you capture the country (or infer it from the entity registration), the checklist branches. Here's what each country triggers: Malaysia branch: MyInvois Registration Number (or exemption category if exempt). SOCSO Compliance Status (if you will pay contractors). SST Registration Status (and proof if registered). Business Activity Classification (needed for SST ruling). Authorized Signatory (separate from primary contact if corporate client). Singapore branch: UEN and ACRA registration date. GST Registration Status (registered, not applicable, or pending). CPF Contribution Compliance (if you'll employ staff or pay them). Authorized Signatory from ACRA records. Indonesia branch: NPWP (and confirmation it's active via Dirjen Pajak). SIUP and TDP (business and tax domicile licenses). E-Invoice System Readiness (confirmation they've registered with the e-invoice system if applicable). Business Sector Classification (used for e-invoice validation). Layer 3: Manual handoff triggers Not everything can auto-verify. Flag these for your compliance or finance team: Exempt from tax registration. If a client claims exemption (e.g., non-profit in Malaysia, small business in Indonesia under threshold), require written proof and legal review before you invoice. Mixed-entity structures. If the client is a holding company or has subsidiaries, your tax position changes. Stop the flow and escalate. Cross-border operations. A Singapore entity paying contractors in Malaysia or Indonesia changes withholding, invoicing, and reporting rules. Manual review required. Ambiguous sector classification. Some services sit on the border of SST exemption (Malaysia) or e-invoice scope (Indonesia). Don't guess—hand off to a human. Rule: Automation saves time on the routine. Manual handoff prevents disasters on the edge cases. Build both into your checklist from the start—don't retrofit it later. How to implement this in Orin (or similar platform) A proper CRM or all-in-one platform should let you build this without code. Step 1: Create custom fields for the branch point Add a "Country" dropdown (Malaysia, Singapore, Indonesia, Other). Make it mandatory at the first form stage. Link it to the client record for later audit. Step 2: Build conditional checklist stages Create one "Onboarding" process with multiple stages. Set stage visibility rules: if Country = Malaysia, show the Malaysia-specific checklist; if Country = Singapore, show the Singapore checklist, etc. Use automation rules to skip or auto-complete universal items once captured. Step 3: Add document collection checkpoints Create a required file field for each country-specific document (MyInvois cert, ACRA extract, NPWP copy, etc.). Mark each field as mandatory before the stage can close. Attach a small inline note: "Upload a clear scan or PDF. Our tea