Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Contract modifications mid-project (scope changes, rate revisions) require reassessment of performance obligations under Ind AS 115, and failure to track these creates material misstatement risk in revenue.
Map each contract to performance obligations, track modifications against the five-step model, recalculate transaction price allocation on scope changes, reconcile cumulative revenue against cash and receivables.
Ind AS 115 five-step model, variable consideration constraints, contract modification prospective vs cumulative catch-up treatment, MCA notification requirements, ICAI guidance notes.
Contract-level revenue reconciliation, modification impact analysis, remaining performance obligation disclosure, and disaggregated revenue report by type and geography.
An IT services company running 80 contracts across fixed-price, time-and-material, and managed services engagements generates revenue under three different recognition patterns simultaneously. If a fixed-price project receives a scope change in month four, the revenue recognized in months one through three may need recalculation under Ind AS 115. Without contract-level Ind AS 115 revenue reconciliation, the gap between what the finance team reports and what the standard requires grows silently until the statutory audit surfaces it as a qualification risk.
What Ind AS 115 Revenue Reconciliation Requires
Ind AS 115 revenue reconciliation is the process of matching revenue recognized in the general ledger to the contract-level calculations prescribed by the five-step model. Unlike the old Ind AS 18 framework where revenue was recognized on delivery or percentage of completion, Ind AS 115 requires identification of distinct performance obligations, allocation of transaction price to each obligation, and recognition based on the pattern of transfer. The ICAI has published implementation guidance notes specific to the Indian IT and software services industry, covering common scenarios like bundled contracts, variable pricing, and contract modifications. For Indian companies, this reconciliation feeds directly into the Schedule III disclosures filed with the MCA, making accuracy a compliance requirement rather than an internal preference.
Applying the Five-Step Model to IT and SaaS Revenue
Step 1-2: Contract and Performance Obligation Identification
A single IT services master agreement may contain a software development deliverable (distinct, milestone-based), ongoing maintenance (distinct, recognized monthly), and a licence grant (distinct, recognized at delivery). Each is a separate performance obligation. The reconciliation starts by mapping every active contract to its constituent obligations, with the contract register serving as the source of truth.
Step 3-4: Transaction Price and Allocation
The transaction price includes fixed fees plus variable consideration — milestone bonuses, SLA penalties, and volume discounts. For an IT company with a ₹1 crore contract that includes a 10% early delivery bonus, the reconciliation must track whether the bonus has been included in the transaction price (constrained by the probability of a significant reversal). Allocation to each obligation uses standalone selling prices, which Indian IT companies typically derive from their published rate cards or historical pricing for similar services.
Step 5: Revenue Recognition and Period Matching
Revenue is recognized as each obligation is satisfied — at a point in time (licence delivery, project completion) or over time (subscription access, maintenance). The reconciliation verifies that the revenue recognized in each period matches the proportion of the obligation satisfied, using input methods (cost incurred vs total cost) for fixed-price projects or output methods (milestones delivered) where applicable.
Ind AS 115 Five-Step Model Reconciliation Checkpoints
| Step | What to reconcile | Data source | Common error |
|---|---|---|---|
| 1. Identify contract | Signed contract exists and meets Ind AS 115 criteria (enforceable rights, commercial substance) | Contract management system, legal records | Recognizing revenue on unsigned amendments or expired contracts |
| 2. Identify performance obligations | Each distinct deliverable is tracked separately | Statement of work, project plan | Bundling implementation and subscription as a single obligation |
| 3. Determine transaction price | Fixed fees + estimated variable consideration (bonuses, penalties) | Contract terms, project status reports | Excluding variable consideration entirely or not constraining estimates |
| 4. Allocate to obligations | Transaction price split by standalone selling price | Rate cards, historical pricing, third-party evidence | Using contract price allocation instead of standalone selling price |
| 5. Recognize revenue | Recognition matches pattern of transfer (point in time or over time) | Timesheet system, milestone tracker, billing records | Recognizing fixed-price project revenue on billing date instead of percentage of completion |
India-Specific Compliance Context
Indian IT and SaaS companies face audit scrutiny on Ind AS 115 disclosures because the standard requires granular disaggregation of revenue that was not mandated under the old Ind AS 18 framework. Statutory auditors routinely test the contract-to-cash reconciliation by sampling active contracts and tracing from signed agreement to performance obligation identification to revenue recognized in the ledger. Companies with milestone billing reconciliation processes must ensure that billing milestones align with performance obligation satisfaction, not merely with project manager approval.
The reconciliation also intersects with TDS compliance: revenue recognized under Ind AS 115 must match the gross revenue reported for TDS purposes. If a client deducts TDS under Section 194J at 10% on a ₹10 lakh invoice but the company recognizes only ₹6 lakh as revenue in the current period (with ₹4 lakh deferred), the TDS credit of ₹1 lakh still applies to the current year’s Form 26AS. TDS reconciliation software must handle this timing difference between tax credit recognition and revenue recognition. For companies managing financial reconciliation India processes across multiple contract types, reconciliation software India that maps revenue schedules to contract-level performance obligations reduces the manual effort of quarterly Ind AS 115 compliance from weeks to exception review. The deferred revenue reconciliation for SaaS process is a subset of this broader Ind AS 115 reconciliation for subscription-based revenue.
Below are common questions finance teams ask about Ind AS 115 revenue reconciliation.