You're invoicing a client in Malaysia, another in Singapore, a third in Indonesia. Same product, three different tax codes, three compliance regimes. Your CRM says it supports invoicing. Your accountant says it doesn't understand any of it. This is the moment most all-in-one platforms reveal their gaps. MyInvois (Malaysia's e-invoice mandate), SST/GST rate rules, NPWP tax ID validation for Indonesia—these aren't edge cases. They're baseline compliance. And most CRMs handle them poorly, forcing you into spreadsheets or manual tax code entries that guarantee errors when auditors come. Let's map what each platform actually does, where it falls short, and when you'll need accounting software alongside your CRM. Why SEA invoicing breaks most CRMs A typical CRM invoicing module assumes one tax rate. Maybe two if you're lucky. SEA markets don't work that way. Malaysia requires MyInvois e-invoice submission for invoices over RM 5,000. Not optional. The invoice must carry a unique long number, XML structure, and digital signature. Fail to submit, face penalties. Your CRM either generates that automatically or it doesn't. Singapore uses GST at 8%, but exemptions abound: financial services, residential property, imported digital services. A single invoice can have mixed-rate line items. And GST registration thresholds matter—miss one, you're non-compliant retroactively. Indonesia layers NPWP (tax ID) validation onto every B2B invoice. The buyer's NPWP must match their business entity in tax records. Submit a mismatch, the invoice is rejected. PPN (value-added tax) sits at 12%, but zero-rated and exempted categories require explicit coding. A CRM that forces you to manually enter tax codes for each invoice, or worse, applies one default rate to all transactions, guarantees compliance gaps. Xero: Native support for all three markets, but not in one workspace Xero has country-specific versions: Xero Malaysia, Xero Singapore, Xero Indonesia. They're separate instances. You can't invoice across all three from one dashboard. What Xero does well: MyInvois automation (Malaysia): Xero auto-generates XML, submits invoices, and stores the UIN (unique invoice number). No spreadsheet workaround needed. GST rules (Singapore): Tax codes branch by exemption status. You assign the right code per line, Xero calculates correctly. NPWP and PPN (Indonesia): Tax ID fields validate format. PPN rates auto-apply by transaction type. Where Xero fails: You manage three separate logins, three separate charts of accounts, three separate audit trails. Consolidating revenue or margins across markets requires manual export and reconciliation. CRM integration is thin. Xero's native CRM features don't exist; you'll plug in a separate CRM like HubSpot or Pipedrive. Now you're syncing contact data across three Xero instances, a CRM, and hoping nothing drifts. Multi-currency invoicing works, but forex gains/losses don't auto-adjust tax bases in Malaysia or Singapore. You'll reclass entries manually. Xero is technically compliant per market, but operationally fragmented. Good if you're a finance team. Painful if you're a sales ops person wanting a single source of truth. Zoho Books + Zoho CRM: Built for bundling, but tax depth varies Zoho offers country-specific editions, and they do sync within Zoho's ecosystem. A Zoho CRM contact in Malaysia flows into Zoho Books Malaysia. No export-import shuffle. What Zoho handles: MyInvois (Malaysia): Zoho Books Malaysia can auto-generate and submit, but only in the Malaysia instance. The e-invoice compliance story is newer than Xero's; bugs and feature gaps still appear. GST (Singapore): Tax rate assignment per line item is possible, but the UI assumes most invoices are single-rate. Mixed-rate invoices require manual coding. NPWP (Indonesia): Format validation exists. PPN rates auto-apply, but zero-rating logic is manual—you code transactions, Zoho doesn't infer them. Where Zoho lags: Multi-country workflows inside one Zoho Books account are experimental. If you try to invoice from one workspace across three countries, tax rules can collide. A Singapore invoice might inherit Malaysia's default tax code. Zoho CRM and Zoho Books sync works, but it's one-way (mostly). Change a tax code in Books; CRM doesn't know. Create a contact in CRM; Books might not inherit all fields. The mobile app doesn't handle tax-coded invoicing well. Field reps can't capture NPWP at point of sale; you'll re-enter it in the office. Zoho is cheaper than Xero ($15/month for Books, add CRM separately or via Zoho One). But you're paying for convenience that isn't fully there yet. Orin: All-in-one workflow, but tax requires you to own the design Orin's approach is different. One unified invoicing system with a native CRM . You own the tax code structure—Orin doesn't pre-bake country rules, but it doesn't break them either. What you get: Custom tax codes and rates: You define tax rules once (MyInvois flag, SST category, NPWP validation rule). Orin