When you send an invoice, you want it read. Email sits in inboxes for days—if it arrives at all—and a 20% open rate is industry normal. SMS lands in a pocket, gets read within 90 seconds, and hits 80%+ open rates. The gap is not theoretical. It translates to payment speed: SMS invoices convert to paid in 3–5 days; email invoices drift to 8–12. But SMS invoicing is not a drop-in replacement for email. PDPA consent rules in Malaysia, Singapore, and Indonesia create friction that kills adoption if you get it wrong. Batch invoice limits mean SMS scales poorly for high-volume accounts receivable. And some invoice types—complex multi-currency retainers, tax-heavy corporate bills—read better on screens than in 160-character windows. Here's where each method wins, and how to avoid the compliance traps that cost time and money. Open rates, speed, and the real payment lift The numbers are stark. SMS invoicing achieves 80–98% open rates within two hours of send. Email hovers at 20–35% for business invoices, with high variance by industry and recipient seniority. If payment is your goal, the channel matters as much as the message. This speed advantage compounds in payment timing: SMS invoices: 3–5 days median time-to-payment (your reminder hits a phone in a pocket). Email invoices: 8–12 days median (invoice sits in inbox, often buried under operational noise). WhatsApp invoices: 4–7 days (higher open rate than email, but inbox clutter still applies). For retainer billing—where customers pay the same amount on a predictable schedule—SMS reminders alone can drop payment cycle by half. A B2B SaaS company billing ₹100K monthly to 50 repeat customers sees ₹12L+ in cash advance by moving to SMS, just from acceleration. Email's saving grace is context. An email invoice is a document. It sits alongside your payment terms, links to your contract, and tax detail that SMS cannot reasonably carry. For one-time invoices to new customers, or invoices over ₹50K with complex GL splits or retainer breakdowns, email's friction is worth the trust signal it carries. PDPA consent: The compliance trap that kills SMS adoption Malaysia's Personal Data Protection Act, Singapore's Personal Data Protection Act (PDPA), and Indonesia's Law No. 27 of 2022 on Personal Data Protection all require explicit prior consent before you send any marketing communication to a personal mobile number. Invoices are not marketing—but SMS invoices use personal phones, and consent audits do not split hairs. The friction is real: You cannot send an SMS invoice to a customer without documented consent to receive SMS communications. Consent can be obtained via website checkbox, verbal agreement (recorded), or email opt-in, but it must be specific to SMS invoicing or at least broad enough to cover payment notices. Generic consent buried in terms of service does not satisfy regulators in any of the three countries. If a customer receives an uninvited SMS invoice and complains to the relevant data protection authority, you face ₹50K–₹500K fines depending on jurisdiction and severity. Most businesses get consent passively: a checkbox on signup ("I want SMS payment reminders"), or an email to existing customers asking them to opt in. For customers who do not consent, SMS is off the table—and your dunning sequence loses its fastest tool. WhatsApp avoids this trap. Because WhatsApp messages are not SMS—they route over data, not telecom networks—they sit in a different consent category in most regulatory guidance. Your customer initiated contact by adding you on WhatsApp, which counts as implicit consent for you to send them invoices on that channel. WhatsApp invoicing also avoids the character limit: you can embed a full link to a branded invoice portal, tax breakdown, and payment button. Email requires no consent at all, provided you include an unsubscribe link. This is why email invoicing is the compliance-safest path for cold outreach, new customers, and high-value transactions where you want a paper trail. When SMS wins: Retainers, recurring billing, and reminder sequences SMS invoicing is purpose-built for one use case: recurring payment reminders where your customer has already said yes. Retainer billing is the most obvious. If you bill a customer ₹50K every month for a retainer, and they have consented to SMS reminders, an SMS invoice link 5 days before due date will convert 40–60% of customers to payment within 48 hours (versus 15–20% for email). For a 50-customer base, that is ₹500K–₹750K in cash pulled forward, every month. The same applies to usage-based billing where invoices are frequent and amounts are predictable. SaaS platforms, freelance marketplaces, and subscription services see the biggest lift because customers expect regular SMS from those businesses and do not have consent friction. Where SMS struggles is: First invoices to new customers. You cannot send SMS without consent. Email is faster to deploy. Complex invoices. A ₹500K invoice with three curren