AS | Ankit Sarawagi|Founder, CFOmatrix·July 2026·10 min read | Cash & Billing |
- The stack runs one loop: subscribe, meter, invoice, collect, dun, recognise. Every leak in SaaS cash traces back to one of these six steps.
- Meter per customer from day one. Tag every unit of usage by customer, because the same data gives you the invoice AND per-customer gross margin.
- The stack must flex with pricing. Per-seat, tiered, consumption and hybrid all need different metering and invoicing, and pricing is migrating toward consumption and outcome.
- Use a prepaid wallet, never bill usage in arrears. Arrears billing on variable consumption is a collections nightmare.
- Dunning protects NRR, GST protects cash. Recover failed payments with retries, and get GST, LUT and e-invoicing right or you forfeit real money.
| 6 steps Subscribe, meter, invoice, collect, dun, recognise | Per-customer Tag usage from day one for margin, not just invoices | 18% / 0% GST on domestic sales vs zero-rated exports (with LUT) |
What a Billing Stack Actually Does
A billing stack is the set of systems that carries a customer from a signed contract all the way to cash in the bank and revenue in the books. People call it quote-to-cash. Under the jargon it is a single loop that repeats for every customer, every billing period: subscribe, meter, invoice, collect, dun, recognise. Skip or fumble any one step and you get the same symptoms every time, wrong invoices, disputed GST, cash that never arrives, and a P&L that does not reconcile.
The mistake founders make is treating billing as a checkout button rather than a finance system. The checkout is step four of six. Get the whole loop right and your invoices, your cash and your books all tell the same story. Get it wrong and you spend board meetings explaining why three numbers disagree.
The Components You Actually Need
You do not need to build all of this from scratch, and you should not. Many billing platforms bundle several components. But you own the design and, critically, the reconciliation back to your books. Here are the six pieces and what each one is responsible for.
| Component | What it does |
| Subscription / billing management | Plans, contracts, proration, upgrades, renewals and cancellations |
| Payment gateway | Charges cards, mandates and bank transfers, in INR and USD |
| Usage metering | Tracks consumption per customer for consumption and hybrid pricing |
| Dunning & retries | Recovers failed payments, prompts card and mandate updates |
| Tax & GST / e-invoicing | Applies 18% domestic GST, zero-rates exports, issues e-invoices |
| Revenue-recognition integration | Posts deferred and recognised revenue into the accounting system |
Notice how the first and last components are the bookends: subscription management defines what the customer owes, and revenue recognition defines what you have earned. The four in between move the money and keep it compliant. AI SaaS operators feel the metering component most, because variable compute means the meter is not a nice-to-have, it is the thing that keeps your invoices and your margin honest.
Plan Types the Stack Has to Support
Your stack is only as flexible as the pricing it can bill. Four plan types cover most SaaS, and the stack must handle all of them because pricing is migrating: from per-seat to consumption, and toward outcome. If your billing can only do per-seat, you cannot ship the pricing your market is moving to. Build for the move now.
| Plan type | How it is billed | What the stack needs |
| Per-seat | Price × number of users | Seat counts, proration on add/remove |
| Tiered | Fixed price per plan tier | Plan catalogue, upgrade and downgrade logic |
| Consumption | Per-unit of usage consumed | Accurate metering, wallets, rate cards |
| Hybrid | Base fee plus usage on top | Both subscription and metering together |
The migration is not academic. Per-seat pricing is disconnected from a variable compute cost, so it quietly erodes margin as heavy users consume more than they pay for. Consumption pricing reconnects price to cost, and outcome pricing anchors to the value delivered. Whatever you charge today, your stack should be able to bill usage tomorrow. The full playbook is in AI SaaS pricing.
Metering: Tag Usage by Customer from Day One
Metering is the component founders underestimate and AI SaaS operators cannot live without. The rule is simple: tag every unit of usage by customer from the very first day. Not because the invoice needs it, though it does, but because the same tagged data is the only way to see per-customer gross margin. In an AI business one customer can consume ten times the compute of another on the same price, and blended margin hides it completely.
“The metering you build to send invoices is the exact same metering that tells you which customers are actually profitable. If you tag usage by customer from day one, you get billing and per-customer margin for free. Retrofit it later and you get neither cleanly.”
Ankit Sarawagi, from working across SaaS and AI SaaS startupsThis is the AI-SaaS operator’s edge. Variable compute means metering and prepaid wallets matter far more than they ever did for classic per-seat SaaS. The teams that instrument usage per customer early can reprice loss-making accounts at renewal, negotiate volume commitments that unlock vendor discounts, and defend their gross margin account by account. The teams that do not are flying blind on the one number investors trust most. Go deeper in deferred revenue and billing.
The Prepaid Wallet Model: Never Bill Usage in Arrears
Once you meter usage, you have to decide how the customer pays for it. There are two clean ways and one that wrecks your cash. For enterprise, take a volume commitment. For everyone else, use a prepaid wallet: the customer tops up a balance and usage draws it down. What you must avoid is billing usage in arrears, delivering first and invoicing a variable amount at month end.
- Customer tops up, usage draws it down
- You are paid before you deliver
- Un-consumed balance is deferred revenue
- No collections risk, no disputed invoices
- You deliver first, invoice at month end
- Every invoice is a different size
- Customers dispute unexpected spikes
- You finance their usage and chase payment
In the AI SaaS companies I have worked with, arrears billing on variable usage is the fastest route to a cash and collections mess. Every invoice is a different size, customers dispute the spikes, and you are effectively lending them the compute while you wait to be paid. Default to a prepaid wallet, or a volume commitment for enterprise, and keep arrears off the table entirely.
The volume commitment has a second benefit beyond cash: when an enterprise customer commits to a minimum volume, you can commit that volume to your compute and model vendors, unlock a discount, and pass part of it back. It is the same commitment chain that makes consumption pricing work. Master the full mechanics in deferred revenue and billing.
Dunning: Recover Failed Payments, Protect NRR
The quietest revenue leak in SaaS is the failed payment. A card expires, a charge is declined, and a paying customer silently drops off, not because they wanted to leave but because the payment never went through. This is involuntary churn, and it is a fixable finance problem, not an unavoidable loss. The system that fixes it is dunning, and good dunning directly protects net revenue retention.
Because net revenue retention is the single most important SaaS number, and failed payments quietly drag it down, dunning earns its place in the stack. Every payment you recover is revenue you already sold, kept without any new sales effort. Read how retention compounds in the SaaS finance pillar guide.
India Specifics: GST, Currency and Exports
An Indian SaaS billing stack has to get tax right automatically, because the rules differ by customer location and currency. Domestic sales carry 18 percent GST on a compliant tax invoice, and e-invoicing applies once turnover crosses the notified threshold. Exports of services are generally zero-rated, but only if a Letter of Undertaking (LUT) is filed, and only from the date it is in place.
“Set the billing system up so tax follows the customer automatically. Domestic gets 18 percent GST, exports are zero-rated once your LUT is in, and the currency follows too. Do it by rule, not by hand, and file the LUT before the first export invoice of the year.”
Ankit SarawagiThe billing stack is where these rules either work quietly in the background or blow up into disputed invoices and forfeited credit. Configure the treatment by customer location and currency, INR for domestic and typically USD for exports, and let the system apply it. The full detail is in GST for SaaS.
Frequently Asked Questions
What is a SaaS billing stack?
A billing stack is the set of systems that carry a customer from signing up to cash in the bank and revenue in the books, sometimes called quote-to-cash. It runs the full loop: subscribe (create the plan and contract), meter (track usage per customer), invoice (raise a compliant tax invoice), collect (charge the payment method), dun (retry and recover failed payments), and recognise (post revenue over the service period). For a fixed subscription the metering step is light; for usage-based AI SaaS it is the heart of the system, because your invoice, your gross margin and your revenue recognition all depend on accurate per-customer usage data.
What components do I need in a SaaS billing stack?
Six components cover most SaaS and AI SaaS businesses: subscription and billing management (plans, contracts, proration, renewals), a payment gateway (to charge cards, mandates and bank transfers), usage metering (to track consumption per customer for consumption pricing), dunning and retries (to recover failed payments and prompt card updates), tax and GST handling (correct GST on domestic invoices, zero-rating on exports, and e-invoicing where applicable), and a revenue-recognition integration (to post deferred and recognised revenue into the accounting system). You can buy a billing platform that bundles several of these, but you still own the design and the reconciliation to your books.
How do I bill usage-based pricing?
Start with metering: tag every unit of usage by customer from day one, because that same data drives the invoice, per-customer gross margin and revenue recognition. Then choose how the customer funds it. For enterprise, take a volume commitment so you can commit that volume to your compute vendors and unlock discounts. For everyone else, use a prepaid wallet where the customer tops up a balance and usage draws it down. Avoid billing pure usage in arrears, where you deliver first and invoice a variable amount at month end, because that becomes a collections nightmare with disputed spikes and cash you are financing yourself.
What is a prepaid wallet model in billing?
A prepaid wallet, or top-up model, is where the customer loads a credit balance in advance and their usage draws it down, like a metered prepaid account. When the balance runs low they top up again. It suits usage-based AI SaaS where consumption varies month to month and the customer will not sign a fixed commitment. It keeps you cash-positive because you are paid before you deliver, and the un-consumed balance sits as deferred revenue until the usage is actually consumed. It is the cleanest way to get the cash advantage of subscriptions onto variable usage pricing.
How do I recover failed SaaS payments?
Failed payments, mostly expired or declined cards, are a silent drain on recurring revenue, so build dunning into the stack. Use smart retries that reattempt the charge on a schedule timed to when funds are likely present, prompt customers to update card details before and after a failure, handle mandate and card expiry proactively, and escalate through email and in-product nudges before you suspend service. Good dunning recovers a meaningful share of otherwise-lost revenue, which directly protects net revenue retention. Treat involuntary churn from failed payments as a fixable finance problem, not an unavoidable loss.
How do I handle GST on SaaS invoices in India?
Domestic sales to Indian customers attract 18 percent GST, which your billing system must add and show correctly on a compliant tax invoice, and e-invoicing rules apply once your turnover crosses the notified threshold. Sales to customers outside India are generally an export of services and are zero-rated, but only if a Letter of Undertaking (LUT) is filed, and only from the date it is in place, so file it at the start of the financial year before you invoice. Configure the stack to apply the right treatment automatically by customer location and currency, INR for domestic and typically USD for exports, and to capture vendor GST numbers so you do not forfeit input tax credit.
This is general educational information for founders, current to mid-2026, drawing on the author’s experience across SaaS and AI SaaS startups, and is not legal, tax or investment advice. GST treatment, e-invoicing thresholds, LUT requirements and revenue recognition under Ind AS 115 depend on your specific facts and change over time; verify the current position or consult a professional before acting on a specific matter.
Deferred Revenue and Billing
GST for SaaS in India
AS | Founder, CFOmatrix | Finance Strategy & Equity Compliance CFOmatrix is a knowledge platform focused on how finance actually works inside growing companies. This post draws on hands-on experience building SaaS and AI SaaS billing stacks, from subscription and usage metering to prepaid wallets, dunning and GST-compliant invoicing for domestic and export customers. |