Milestone Billing Reconciliation IT Services: Deliverable-Based Revenue Matching

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 10 April 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024

Knowledge Card

Problem

IT services companies with 40+ active fixed-price contracts have 120+ open milestones at any time, and revenue recognition depends on deliverable sign-off dates that lag invoice dates by weeks.

How It's Resolved

Match milestone sign-off to invoice generation, track partial payments against milestone value, reconcile TDS deducted by client against Form 26AS credits, validate revenue recognition timing.

Configuration

Section 194J at 10% or 194C at 1-2% depending on contract classification, milestone sign-off as revenue trigger, Form 26AS quarterly reconciliation window.

Output

Milestone-to-cash tracker, TDS receivable register by client, revenue recognition schedule aligned to sign-off dates, and contract-wise profitability report.

A mid-size Indian IT services company running 40 fixed-price contracts has a milestone billing reconciliation problem that spreadsheets cannot solve at scale. Each contract has 3 to 8 milestones, each milestone moves through deliverable completion, client acceptance, invoicing, TDS deduction, and net payment — and the status of each stage lives in a different system. Milestone billing reconciliation connects the statement of work to the bank statement, ensuring that every deliverable signed off by the client converts to recognised revenue and collected cash.

What Milestone Billing Reconciliation Involves

Milestone billing reconciliation for IT services tracks each deliverable-based payment from contract definition through to cash receipt. Unlike time-and-material billing where invoices follow a predictable monthly cycle, milestone billing depends on project execution speed, client acceptance timelines, and contractual payment terms that vary by contract.

The reconciliation confirms that: the milestone deliverable was accepted by the client (sign-off document), the invoice matches the milestone amount in the statement of work, TDS was deducted at the correct rate and section, the net payment arrived in the bank within the contractual payment period, and the TDS credit appears in Form 26AS for the correct quarter. Each of these checks involves a different data source and a different team.

How Milestone Billing Reconciliation Works

Deliverable Sign-Off to Invoice

The project manager confirms deliverable completion and submits it to the client for acceptance. The client’s contractual acceptance period is typically 7 to 15 working days. On sign-off, the finance team generates an invoice for the milestone amount specified in the SOW. The reconciliation check at this stage is: does the invoice amount match the SOW milestone value, and has the correct GST rate (18% for software development services under SAC 998314) been applied?

Invoice to TDS Deduction and Payment

The client processes the invoice under their payment terms (typically 30 to 60 days). At payment, the client deducts TDS — Section 194J at 10% for professional services or Section 194C at 1-2% for contract work. The net amount credited to the IT company’s bank account equals the invoice value minus TDS minus any GST TDS under Section 51 (if applicable for government clients). The reconciliation matches the bank credit plus TDS deduction to the original invoice value.

TDS Credit Verification in Form 26AS

The TDS deducted by the client should appear in Form 26AS within the quarter of deduction. The match key is the TDS certificate number on Form 16A issued by the client. Common mismatches include: TDS deposited under the wrong section (194C instead of 194J), TDS amount calculated on the GST-inclusive invoice value instead of the pre-GST base, and TDS deducted but deposited late by the client, causing it to appear in a different quarter.

Milestone Lifecycle and Reconciliation Checkpoints

Stage	Financial Entry	Data Source	Reconciliation Check
SOW signed	Contract value booked as contingent billing schedule	Contract management system or SOW document	Milestone amounts sum to total contract value
Deliverable accepted	Revenue recognised under Ind AS 115; unbilled revenue cleared	Client sign-off email or acceptance certificate	Sign-off date matches revenue recognition date; amount matches SOW
Invoice raised	Accounts receivable created; GST output liability recorded	Billing system (Tally, SAP, Zoho)	Invoice amount = SOW milestone value + 18% GST; correct SAC code
Client pays with TDS	Bank credit recorded; TDS receivable created	Bank statement (UTR/NEFT reference)	Bank credit + TDS amount = invoice value; TDS rate matches 194J/194C
Form 26AS updated	TDS receivable confirmed against tax credit	TRACES portal / Form 26AS download	Certificate number, amount, and section match TDS receivable ledger

India-Specific Compliance for Milestone Billing

The Section 194J versus 194C classification is the most disputed element in IT services milestone billing. The Ministry of Corporate Affairs governs the Ind AS 115 framework that determines when milestone revenue can be recognised, and the recognition date directly affects which quarter the receivable enters the books. A milestone accepted on 30 March but invoiced on 2 April creates a revenue recognition question that affects both quarterly financial reporting and TDS quarter mapping.

For IT companies with 40+ active contracts, each with different TDS treatment and payment terms, TDS reconciliation software that matches milestone invoices against Form 26AS entries by certificate number reduces the quarterly reconciliation from a multi-day exercise to exception review. The broader challenge of tracking milestone receivables alongside other revenue streams is addressed by reconciliation software India deployments that consolidate billing, bank, and tax data into a single matching workflow. The contract-level receivable tracking required for milestone billing follows the same ledger structure covered in financial reconciliation India. For contracts with non-resident subcontractors, the TDS treatment under Section 195 non-resident payments adds another reconciliation layer. IT companies running both milestone and subscription models should also review SaaS subscription reconciliation India for the deferred revenue matching process.

Below are common questions from Indian IT services finance teams about milestone billing reconciliation.

Primary reference: Ministry of Corporate Affairs — Ind AS standards and company law governing revenue recognition for IT services contracts.

Frequently Asked Questions

Is TDS on IT services contracts deducted under Section 194J or 194C?

The classification depends on the nature of the contract. Section 194J (10% TDS) applies to fees for professional or technical services — this covers software development, consulting, and technical advisory work. Section 194C (1% for individuals, 2% for companies) applies to contracts for carrying out work, which covers staff augmentation and outsourced process execution. Many IT services contracts involve both elements, and clients often classify the entire contract under one section. The reconciliation process must match the TDS rate applied by the client in Form 26AS against the rate the company expects based on the contract classification. Disputes are common and require correction returns by the deductor.

How should revenue be recognised for milestone-based IT contracts under Ind AS 115?

Under Ind AS 115, revenue for a milestone-based IT contract is recognised when (or as) each performance obligation is satisfied. For fixed-price contracts with defined deliverables, each milestone typically represents a distinct performance obligation if the client can benefit from each deliverable on its own. Revenue is recognised at the point when the client formally accepts the deliverable (sign-off). If the milestones are interdependent and the client only benefits from the completed whole, revenue is recognised over time using the input method (cost-to-cost) or output method (milestones completed as a percentage of total). The transaction price must be allocated to each milestone based on standalone selling prices.

What happens when a client withholds payment pending final milestone completion?

Many IT services contracts include retention clauses where 10-20% of each milestone payment is withheld until final delivery and acceptance. This retention creates a receivable that does not convert to cash until the project is complete, which may be 6-12 months after the milestone invoice was raised. The retention amount must be tracked as a separate receivable line item, not clubbed with the current milestone receivable. Under Ind AS 115, revenue is still recognised on milestone acceptance, but the retention receivable should be assessed for impairment if there is a significant delay in final acceptance.

How do Indian IT companies reconcile milestone invoices against Form 26AS?

Each milestone invoice triggers a TDS deduction by the client at 194J (10%) or 194C (1-2%). The deducted amount should appear in Form 26AS within the quarter it was deducted. The reconciliation matches: invoice number and amount in the billing system → TDS certificate (Form 16A) from the client → Form 26AS entry showing the certificate number, amount, and section. Common mismatches include: wrong section code (194C instead of 194J), wrong quarter of deposit by the deductor, amount mismatch due to GST inclusion in the TDS base, and TDS deducted but not deposited by the client within the due date (7th of the following month).

What is the typical milestone billing cycle for Indian IT services projects?

A standard milestone billing cycle for Indian IT services runs: deliverable completion by the project team (day 0) → internal quality review (day 1-3) → client submission and sign-off (day 3-10, contractual acceptance period is usually 7-15 working days) → invoice generation on acceptance (day 10-15) → client payment terms (30-60 days from invoice date) → TDS deduction by client at payment → net amount credited to bank. From deliverable completion to cash receipt, the typical cycle is 45-75 days. The reconciliation must track each milestone through every stage, because delays at any point — particularly client sign-off — cascade through the entire chain.

Milestone Billing Reconciliation for IT Services Companies in India