Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian IT services firms running T&M, fixed-bid, and milestone contracts in USD, EUR, and GBP simultaneously face three distinct revenue recognition profiles under Ind AS 115, layered with Ind AS 21 forex revaluation, optional Ind AS 109 hedge accounting, and a FIRC realisation chain that often lags the revenue period.
Classify each contract by performance obligation pattern (T&M hours-billed, fixed-bid cost-to-cost, milestone deliverable), translate at invoice-date spot rate under Ind AS 21, revalue receivables at closing rate, designate cash-flow hedges where derivatives are used, and reconcile revenue, billing, AR, and FIRC ledgers monthly.
Ind AS 115 five-step model, performance obligations over time, output and input measures of progress, Ind AS 21 spot rate at transaction date, closing rate at reporting date, Ind AS 109 hedge accounting designation and effectiveness testing, FIRC realisation against invoice.
Revenue recognition schedule per contract, unbilled receivable and deferred revenue ledgers, forex gain or loss split between realised and unrealised, OCI hedge reserve roll-forward, and a four-ledger month-end reconciliation.
An Indian IT services firm with a mix of T&M, fixed-bid, and milestone contracts across USD, EUR, and GBP customers carries three distinct revenue recognition profiles under Ind AS 115 in the same accounting period. Layer Ind AS 21 forex revaluation on every receivable, the optional Ind AS 109 hedge accounting election for derivative cover, and the FIRC realisation chain through the AD Category-I bank, and the month-end revenue close requires four ledgers to be reconciled before the revenue figure is signed off. The reconciliation is the operational work that protects the published revenue line from a restatement six months later when the auditor traces a single invoice from contract to cash.
How does the five-step model apply across T&M, fixed-bid, and milestone contracts?
Ind AS 115 prescribes a five-step model for revenue recognition: identify the contract with the customer, identify the performance obligations in the contract, determine the transaction price, allocate the transaction price to the performance obligations, and recognise revenue when (or as) the performance obligation is satisfied. The model is uniform; the application differs sharply across contract types.
For a T&M contract, the performance obligation is typically the provision of professional services over the engagement period. The customer simultaneously receives and consumes the benefits as the firm performs, satisfying the over-time recognition criterion. The transaction price for each billing period is the contractual rate multiplied by the hours delivered. Revenue is recognised based on hours-times-rate as services are delivered, and there is no significant work-in-progress accounting because each unit of service is invoiced as it is delivered.
For a fixed-bid contract, the firm commits to a defined scope for a fixed price. The performance obligation is still typically satisfied over time, but the measure of progress is no longer hours-billed-at-rate. The firm chooses an input method (cost-to-cost: costs incurred to date over total estimated costs) or an output method (milestones reached, deliverables accepted). Revenue is recognised based on the chosen measure of progress applied to the total transaction price, producing an unbilled receivable when recognition outpaces billing or a deferred revenue when billing outpaces recognition.
For a milestone contract, the contract structures delivery into discrete milestones with defined acceptance criteria. Where each milestone is a separate performance obligation, revenue is recognised on milestone completion (point in time). Where the milestones are payment triggers but the underlying performance obligation is a single over-time obligation, revenue is recognised over time using a measure of progress, and the milestone payments are billed but not necessarily aligned with the recognised revenue.
Quick reference: Ind AS 115, Ind AS 21, and Ind AS 109 facts
| Accounting lever | Standard | Treatment | Documentation |
|---|---|---|---|
| Performance obligation identification | Ind AS 115 paras 22-30 | Distinct goods or services in the contract | Contract review per engagement |
| Over-time recognition criteria | Ind AS 115 para 35 | Customer simultaneously receives benefit / asset created has no alternative use + enforceable right to payment | Contract clauses + IP ownership analysis |
| Measure of progress — output | Ind AS 115 paras B14-B17 | Milestones, deliverables accepted, surveys | Acceptance certificates |
| Measure of progress — input | Ind AS 115 paras B18-B19 | Costs incurred / total estimated costs | Project cost ledger + estimate-to-complete |
| Contract modifications | Ind AS 115 paras 18-21 | New contract / cumulative catch-up / prospective | Change order documentation |
| Spot rate at transaction date | Ind AS 21 para 21 | Foreign currency translated at spot rate | Invoice-date RBI reference rate |
| Closing rate at reporting date | Ind AS 21 para 23 | Monetary items at closing rate | Quarter-end revaluation register |
| Cash flow hedge accounting | Ind AS 109 paras 6.5.7-6.5.12 | Effective portion in OCI; ineffective in P&L | Hedge documentation + effectiveness test |
| Hedge effectiveness | Ind AS 109 paras 6.4.1-6.4.6 | Economic relationship, credit risk not dominant, hedge ratio aligned | Quarterly effectiveness assessment |
| Discontinuation of hedge accounting | Ind AS 109 paras 6.5.6, 6.5.7 | Forecast transaction no longer expected | Documented termination |
What changes when revenue is billed in USD, EUR, or GBP?
Under Ind AS 21, every foreign currency transaction is translated to the functional currency at the spot rate on the date of the transaction. For an Indian IT services firm, the functional currency is INR, and the spot rate is typically the RBI reference rate published for that date.
When a USD 50,000 T&M invoice is issued on 5 May at an RBI reference rate of 83.20, the booking is ₹41.6 lakh of revenue and ₹41.6 lakh of receivable. At the end of May (the reporting date for a monthly close), the receivable is revalued at the closing rate, say 83.45. The receivable is restated to ₹41.725 lakh, and the ₹0.125 lakh increase is an unrealised forex gain taken to P&L under other income. The revenue line itself does not move — Ind AS 21 anchors revenue at the transaction date, and only the monetary receivable is revalued at the reporting date.
When the customer remits USD 50,000 on 20 June, the AD bank converts the proceeds at, say, 83.30 (after deducting USD 35 of correspondent bank charges, so USD 49,965 is realised). The INR credit is ₹41.55 lakh approximately. The receivable is closed against the realisation, and the difference between the rebooked receivable (now ₹41.725 lakh after May revaluation, possibly revalued again at quarter-end) and the realised INR is a realised forex gain or loss.
The split between realised and unrealised forex is critical for the management P&L and for the disclosure under Ind AS 21. Aggregating them masks the actual cash effect of forex movements and overstates or understates the unrealised volatility against next period’s reversal.
When should hedge accounting be elected?
Indian IT services firms with material forecast foreign currency revenue often hedge a portion of the exposure through forward contracts or options. Without hedge accounting under Ind AS 109, the derivative is fair-valued through P&L at each reporting date while the underlying forecast revenue is recognised only when the performance obligation is satisfied. This creates an accounting mismatch — the derivative volatility lands in current-period P&L, while the offsetting revenue lands in a later period. Earnings volatility is amplified relative to the economic cash-flow stability the hedge is designed to deliver.
Cash flow hedge accounting under Ind AS 109 resolves the mismatch. The effective portion of the change in fair value of the hedging derivative is deferred in Other Comprehensive Income (the hedge reserve) and recycled to P&L in the period when the hedged forecast revenue is recognised. The ineffective portion is recognised immediately in P&L.
Designating a cash flow hedge requires formal documentation at inception: the risk management objective, the hedged item (the forecast foreign currency revenue, with quantification and timing), the hedging instrument (the derivative, with notional and term), and the method of assessing effectiveness. Effectiveness is reviewed at each reporting date — the economic relationship between the hedged item and the hedging instrument must hold, credit risk must not dominate the value changes, and the designated hedge ratio must be aligned with the actual risk management practice.
When the forecast transaction is no longer expected to occur (a customer cancels a contract that was being hedged), hedge accounting is discontinued and the cumulative gain or loss in the hedge reserve is recycled to P&L immediately.
Worked example: ₹180 crore T&M and ₹95 crore fixed-bid
Consider an Indian IT services firm with ₹180 crore of T&M revenue and ₹95 crore of fixed-bid revenue in the year, mixed across USD (60 per cent), EUR (25 per cent), and GBP (15 per cent) customers. The firm hedges 60 per cent of forecast USD revenue through forward contracts.
For the T&M portfolio, revenue recognition is hours-billed-at-rate. Each monthly invoice translates to INR at the invoice-date spot rate. The receivable carries until the FIRC realises typically 30 to 45 days later. At each month-end, outstanding T&M receivables are revalued at the closing rate, producing unrealised forex gains or losses on the order of ±₹0.8 to ±₹1.2 crore per month depending on rate volatility.
For the fixed-bid portfolio, the firm applies the cost-to-cost input method. Each contract has a total transaction price and a total estimated cost. At each reporting date, the firm computes costs incurred to date and divides by total estimated costs to derive the percentage of completion. Revenue is recognised at that percentage of the total transaction price.
For a fixed-bid contract of USD 1.2 million signed on 1 April with total estimated costs of USD 0.9 million, the firm books revenue at the invoice-date spot rate for billing milestones and at the corresponding spot rate for recognition events. At the end of June (Q1), 30 per cent of total estimated costs have been incurred. Revenue recognised in INR is 30 per cent of USD 1.2 million translated at the average rate for the recognition period (or at specific recognition-date rates if the firm chooses). If billings to date are USD 0.4 million, the unbilled receivable in USD is (0.30 × 1.2) − 0.4 = USD −0.04 million — a small deferred revenue. The unbilled receivable or deferred revenue in INR is translated at the closing rate at quarter-end.
The hedge portfolio sits over the top. Forward contracts hedge a portion of forecast USD revenue at predetermined strike rates. At each quarter-end, the firm tests effectiveness, books the effective portion of the change in fair value of the forwards to OCI, and recycles previously deferred amounts to P&L when the hedged revenue is recognised. The OCI hedge reserve roll-forward is a separate ledger.
At year-end, the four-ledger reconciliation closes the loop. The revenue ledger of ₹275 crore (T&M + fixed-bid) is matched against the billing ledger (separate because fixed-bid produces timing differences between recognition and billing), against the AR ledger (the outstanding receivable balance), and against the cumulative FIRC log (the cumulative INR realised against invoices issued in the year). Any unexplained variance triggers a back-trace through the invoice register and the FIRC log.
Plug in your export revenue, cloud infrastructure spend, and domestic professional services to size the GST refund pool and the working capital trapped in pending claims under Section 54.
Open the ITC Leakage Calculator →How does the new TDS payment-code era affect multi-currency revenue?
The TDS reset under Sections 393 and 394 of the Income Tax Act with the payment-code architecture 1001 to 1092 rarely touches the inbound revenue line — TDS is typically not deducted from the IT services firm’s foreign currency invoice receipt unless a specific country’s regime imposes withholding (some jurisdictions deduct WHT on services payments to non-residents, which must then be claimed as foreign tax credit under Section 91 or the relevant DTAA article).
The substantive overlap is on the procurement side — payments to overseas software licensors under Section 413 with payment code 1062, intra-group services from foreign affiliates, and equalisation levy on specified digital services. These create reconciliation items between the foreign vendor invoice register, the TDS challan register, and the books — the same multi-ledger discipline that protects the revenue line also protects the procurement-side TDS compliance.
A reconciliation software India workflow can match the revenue ledger, the billing ledger, the AR ledger, and the FIRC log in a single workflow, and a GST reconciliation software workflow can match GSTR-1 Table 6A against the books export revenue line and the FIRC realisation.
What recurring controls keep the revenue line audit-ready?
Finance teams that run multi-currency Ind AS 115 cleanly build four recurring controls. The first is a contract classification register — every contract is classified at signing into T&M, fixed-bid, or milestone, with the performance obligation analysis, the measure of progress, and the transaction price determination documented. The second is a monthly forex revaluation — every outstanding foreign currency receivable is revalued at the closing rate, with realised and unrealised split clearly. The third is a quarterly hedge effectiveness assessment — every designated cash flow hedge is reviewed for the three Ind AS 109 effectiveness criteria, with the OCI roll-forward and the recycling to P&L documented. The fourth is the four-ledger month-end reconciliation between revenue, billing, AR, and FIRC log. The Ministry of Corporate Affairs publishes the operative Ind AS notifications and the Companies (Indian Accounting Standards) Rules on its portal.
Continue reading
IT services finance teams reading this article typically also read:
- Ind AS 115 revenue reconciliation — the five-step model applied to performance obligations.
- Multi-currency reconciliation for IT services — the FIRC, EEFC, and forex revaluation chain in detail.
- SaaS subscription reconciliation India — deferred revenue and cash matching for product-SaaS companies.