Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
SaaS companies collect annual subscriptions upfront but must recognize revenue monthly under Ind AS 115, creating a deferred revenue liability that diverges from cash receipts over the subscription lifecycle.
Match cash receipt to subscription contract, generate monthly revenue recognition schedule, reconcile deferred revenue balance against P&L recognized revenue and bank collections.
Ind AS 115 five-step model, GST 18% on SaaS (SAC 998314), LUT for export services, FIRC for USD collections, monthly recognition schedule.
Deferred revenue aging report, MRR-to-cash reconciliation, Ind AS 115 disclosure schedule, and GST output liability register.
Most Indian SaaS companies track MRR with precision but never reconcile the deferred revenue schedule against actual cash in the bank. SaaS subscription reconciliation closes that gap — matching what was billed, what was recognised as revenue, and what was received as cash, across multiple currencies and billing cycles. Finance teams at subscription businesses with 100+ customers and mixed annual-monthly plans face this every month-end.
What SaaS Subscription Reconciliation Is
SaaS subscription reconciliation is the process of matching three financial views of each customer account: the subscription invoice (what was billed), the revenue recognition schedule (what was earned under Ind AS 115), and the cash receipt (what arrived in the bank). For Indian SaaS companies billing in USD or EUR, a fourth element enters — the forex conversion recorded on the FIRC from the receiving bank.
The reconciliation confirms that the deferred revenue balance on the balance sheet accurately reflects unearned subscription revenue, that recognised revenue matches the performance obligation delivery period, and that cash receipts are allocated to the correct customer and invoice. When these three ledgers diverge, the month-end close cannot be completed without manual investigation.
How SaaS Subscription Reconciliation Works
Matching Invoices to Revenue Schedules
Each subscription invoice generates a revenue recognition schedule. An annual plan billed at ₹6,00,000 on 1 April creates 12 monthly revenue entries of ₹50,000 each. The reconciliation matches each month’s recognised revenue against the schedule, confirms the deferred revenue balance decreases by the correct amount, and flags any schedule that was modified mid-period due to upgrades, downgrades, or cancellations.
Matching Cash Receipts to Invoices
Cash receipts must match to specific invoices. For domestic customers paying via NEFT or UPI, the UTR number in the bank statement is the match key. For international customers paying via wire transfer, the FIRC reference and the converted INR amount must reconcile against the USD invoice value at the receipt-date exchange rate. Partial payments, advance payments, and credit notes each require separate matching logic.
Handling Mid-Cycle Changes
Upgrades, downgrades, and cancellations mid-subscription create amended revenue schedules. A customer who upgrades from a ₹5,00,000 plan to a ₹8,00,000 plan in month 4 requires the original schedule to be closed and a new schedule created for the remaining 8 months at the revised rate. The deferred revenue balance must reflect the difference — and the cash receipt for the upgrade must be matched to the amended invoice.
Subscription Billing Scenarios and Reconciliation Treatment
| Billing Type | Revenue Recognition | Deferred Revenue Treatment | Reconciliation Trigger |
|---|---|---|---|
| Annual upfront (INR) | Straight-line over 12 months under Ind AS 115 | 11 months deferred at billing; decreases monthly | Monthly schedule vs. GL deferred revenue balance |
| Annual upfront (USD) | Straight-line at invoice-date INR rate | Deferred revenue in INR; forex revaluation at each reporting date | FIRC amount vs. invoice; unrealised forex gain/loss at quarter-end |
| Monthly recurring (INR) | Recognised in billing month | No deferred revenue if billed monthly | Cash receipt vs. invoice; aging of overdue invoices |
| Quarterly advance (INR) | Straight-line over 3 months | 2 months deferred at billing | Quarterly schedule vs. GL; mid-quarter upgrade adjustments |
| Usage-based (metered) | Recognised on usage calculation | Advance deposits held as deferred until usage is measured | Metered usage report vs. invoice vs. deposit drawdown |
India-Specific Compliance Considerations
Indian SaaS companies face compliance requirements that directly affect subscription reconciliation. Under Ind AS 115, each contract must be evaluated for distinct performance obligations — a subscription bundled with implementation services requires allocation of the transaction price across obligations based on standalone selling prices. The ICAI has published implementation guidance specifically for technology companies applying Ind AS 115.
For export revenue, the company must hold a valid LUT (Letter of Undertaking) filed under Form GST RFD-11 to zero-rate export invoices. If the LUT lapses, IGST at 18% must be charged on all export invoices until renewal, creating a refund claim cycle that adds reconciliation complexity. GST on domestic subscriptions at 18% is payable on the full invoice value at billing, regardless of the revenue recognition schedule — producing a permanent timing difference between the GST return and the P&L.
Companies reconciling subscription revenue across domestic and export customers benefit from reconciliation software India that handles both INR and multi-currency matching in a single workflow. For the GST timing difference between upfront billing and monthly revenue recognition, GST reconciliation software automates the GSTR-1 to books comparison. The forex conversion chain for USD-billed subscriptions follows the same FIRC matching process covered in forex reconciliation India. For SaaS companies evaluating deployment models, the trade-offs between cloud-hosted and self-managed reconciliation tools are covered in SaaS vs on-premise reconciliation. The receivable aging and customer-level balance verification process aligns with debtors and creditors reconciliation practices for subscription businesses.
Below are the most common questions Indian SaaS finance teams ask about subscription reconciliation.