The India SaaS Tax
There's a set of features that every SaaS product targeting Indian businesses needs, and none of them are covered in the typical SaaS startup playbook written from a US perspective. We call it the "India SaaS tax" — it's not a literal tax (though GST compliance is part of it), but a set of engineering requirements that add 4-6 weeks to your initial build. Ignore them and your Indian customers will look elsewhere.
UPI Autopay: Not Like Card Subscriptions
UPI Autopay (officially called UPI Mandate) is how most Indian businesses want to pay for SaaS subscriptions. But UPI Autopay has quirks that card-based recurring billing doesn't. First, there's a mandate creation flow: the user initiates the mandate, approves it in their UPI app (GPay, PhonePe, Paytm), and then you can charge against the mandate for future billing cycles. This approval can take anywhere from instant to 48 hours, depending on the bank.
Second, UPI Autopay has a mandate amount limit. When the customer approves the mandate, they approve a maximum charge amount. If your pricing changes or the customer upgrades, you might need a new mandate if the new amount exceeds the original limit. We set mandate amounts 2x the current plan price to provide headroom for price increases, but this shows the higher amount in the customer's UPI app, which sometimes causes confusion.
Third, UPI mandate execution failures are more common than card failures. We see about 8-10% failure rates on first attempts, primarily due to insufficient balance (UPI doesn't have the "retry later" intelligence that credit cards do) and bank-side technical issues. We implement retry logic with exponential backoff: retry after 24 hours, then 48 hours, then 72 hours, with customer notification at each step. Our integration uses Razorpay's subscription API which handles most of this, but the edge cases still require custom handling.
GST Invoicing: The Compliance Minefield
If you're charging Indian customers, you need GST-compliant invoices. This means: proper GSTIN validation (18-character alphanumeric with checksum), correct GST rate application (18% for software services), HSN/SAC code inclusion (SAC 998314 for software licensing), place-of-supply rules (CGST+SGST for intra-state, IGST for inter-state), and a sequential invoice numbering scheme that follows the financial year format.
We built a GST invoicing module that's now reused across all our India-facing SaaS products. It validates GSTIN against the government's API (yes, there's an API — it's slow and occasionally down, so we cache valid GSTINs), calculates the correct tax split based on the customer's state, generates PDF invoices with all required fields, and integrates with the payment provider to match invoices to payments.
The gotcha that caught us: reverse charge mechanism for certain services. If your SaaS company is outside India but serving Indian customers, the customer might be responsible for paying GST under reverse charge. Your invoice needs to reflect this. We learned this from an accountant after a client's CA flagged incorrect invoicing. Build the invoicing system with a tax rules engine, not hardcoded rates.
INR Pricing: The Psychological Game
Pricing in INR instead of USD isn't just about conversion rates — it's about perception. ₹999/month feels very different from $12/month, even though they're roughly equivalent. For the Indian SMB market, we've found that ₹X,999 pricing (₹1,999, ₹4,999, ₹9,999) converts better than round numbers. We also offer quarterly and annual billing with discounts (10% for quarterly, 20% for annual), which aligns with how Indian businesses budget.
Technically, INR billing means your entire billing stack needs to handle a zero-decimal currency (Stripe treats INR as zero-decimal, so ₹999 is sent as 999, not 99900). Your invoicing needs to handle paise for calculations but display in whole rupees. And your reporting dashboard needs to show both INR (for Indian metrics) and USD (for investor reporting, if applicable). We maintain exchange rate snapshots at the time of each transaction for accurate USD reporting.
Other India-Specific Requirements
Two more things that trip up SaaS builders targeting India. First, TDS (Tax Deducted at Source): enterprise Indian customers will deduct 2% TDS on your invoice and pay you only 98%. You need to track TDS certificates, reconcile them quarterly, and claim TDS credits in your tax filing. Build TDS tracking into your billing system from day one. Second, Indian businesses expect NEFT/RTGS bank transfer as a payment option alongside UPI and cards. This means manual payment reconciliation for offline bank transfers. We auto-reconcile by matching payment amounts and reference numbers from our bank statement (fetched via banking API) against outstanding invoices.