SaaS Billing Basics: Plans, Trials, Wallets and GST Invoices

What does SaaS billing actually involve?

Billing is more than taking a payment. It covers presenting plans, starting a trial, converting it to a paid subscription, charging on renewal dates, handling upgrades and downgrades mid-cycle, retrying failed payments, issuing invoices and recording everything for accounts. Each of these paths needs a defined rule and a tested implementation.

Because customers judge a product partly by how fairly it bills, mistakes are costly. A double charge, a missing invoice or a surprise renewal creates support tickets and lost trust. Treat billing as a core product feature with its own design, testing and monitoring, not as something to bolt on shortly before launch.

How should you structure plans and pricing?

Common models include per-user pricing, tiered plans with feature limits, usage-based charging, or a mix. The right one tracks how your customers receive value. A team collaboration tool fits per-user pricing, while a messaging product with variable volume may suit a base plan plus usage.

Keep plans simple enough to explain in a sentence. Too many tiers confuse buyers and complicate the code. Define limits clearly, such as contacts, seats or messages, and decide what happens when a limit is reached: block, warn, or offer an upgrade or top-up. Store plan rules as configuration so you can change them without a rebuild.

• Per-user or per-seat pricing.
• Tiered plans with feature and volume limits.
• Usage-based charges for variable consumption.
• Monthly and annual billing options.
• Clear behaviour when a limit is reached.

How do free trials work in billing?

A trial lets prospects experience the product before paying. Decide its length, which features are included, and whether a card or mandate is required upfront. Requiring none usually brings more sign-ups; requiring one often brings fewer but more committed users. There is no universal answer, so test with your audience.

Plan the end of the trial just as carefully. Send reminders before it expires, make the upgrade path obvious, and define what happens to data afterwards: read-only access, a grace period or suspension. Clear, honest communication here prevents resentment and reduces cancellations that stem from confusion.

What is a prepaid wallet and when should you use one?

A wallet lets customers load credit in advance and spend it as they use the product, for example on messages, calls or add-ons. It suits usage-based services and customers who prefer controlling spend. It also reduces failed-payment issues, because money is collected first.

Technically a wallet is a ledger, and it must be designed with the care of an accounting record. Every credit and debit should be an immutable entry with a timestamp and reference, so balances can always be reconstructed. Protect against double spending, race conditions and duplicate payment callbacks so the balance can never be overdrawn or credited twice.

• Append-only ledger of credits and debits.
• Idempotent handling of payment callbacks.
• Checks that prevent overdrawing the balance.
• Receipts and statements for the customer.
• Low-balance alerts and easy top-up.

How do you handle renewals and failed payments?

Renewals can be automatic through recurring payment mandates, or manual through reminders and payment links. Indian payment rules around recurring charges include additional authentication and notification steps, so check your payment gateway's current requirements. Always remind customers before charging and make cancellation simple.

For failed payments, build a gentle sequence: retry on a schedule, notify the customer by email or WhatsApp, offer an easy way to update the payment method, and allow a short grace period before restricting access. This process, often called dunning, recovers many accounts that would otherwise lapse by accident.

What should GST invoices and records include?

Business customers in India usually need proper tax invoices for input credit purposes. Invoices typically show your business details and GSTIN, the customer's details, invoice number and date, description, taxable value, tax split and totals. Numbering should be sequential and reliable, and credit notes should handle refunds and corrections.

GST rules change, and details depend on your business. Treat this article as general information and confirm current requirements on the official portal and with your chartered accountant. Automating invoice generation and syncing with your accounting software, for example through Tally integration, removes manual errors and month-end stress.

Frequently asked questions

Should I use a payment gateway or build billing myself?

Use an established gateway such as Razorpay or Stripe for collecting payments, and build the plan, invoice and entitlement logic around it to fit your product.

Should free trials require a card?

It depends. Skipping the card tends to increase sign-ups, while requiring one filters for intent. Test both with your target customers.

How do I handle refunds and credit notes?

Record them as separate, traceable entries linked to the original invoice, and follow your refund policy. Your accountant can confirm the correct tax treatment.

Can billing be changed after launch?

Yes, but changing plans for existing customers needs care. Keep pricing rules in configuration and decide how legacy customers are migrated or grandfathered.

Need help with this? See our SaaS Product Development service or talk to Yash Parikh.