API CDMO Margin Reconciliation: Cost-Plus, Fixed-Price, Milestone

The CRAMS (Contract Research and Manufacturing Services) sub-sector of Indian pharma is where the domestic backward-integration push (Indian formulators sourcing active pharmaceutical ingredient from Indian CDMOs rather than Chinese-origin bulk-drug suppliers in Zhejiang, Jiangsu and Shandong provinces) and the global innovator-outsourcing push (US and European originator companies outsourcing API and intermediate manufacturing to Indian CDMOs for cost, capacity and regulatory-quality reasons) meet. A Tier-2 CRAMS operator running an active-pharmaceutical-ingredient CDMO (Contract Development and Manufacturing Organisation) plant closes its books for October 2025 with a diversified contract book of the order of Rs 650 crore in FY 2025-26 run-rate. The book is split across three principal contract types: cost-plus (actual cost pass-through plus agreed margin, typically at a 10 to 25 percent margin band) at roughly 40 percent of aggregate value at an illustrative 18 percent average margin; fixed-price (whole-life contract quote absorbing cost-overrun risk in exchange for a wider 20 to 40 percent margin band) at roughly 35 percent of aggregate value at an illustrative 32 percent average margin; and milestone-based (staged development-batch, validation-batch and commercial-launch-batch deliverables with per-milestone payment cycles) at roughly 25 percent of aggregate value at an illustrative 28 percent average margin. Each contract type carries a different Ind AS 115 revenue-recognition method — cost-plus over time via an input method as costs are incurred, fixed-price over time via the cost-to-cost input method, milestone at a point in time on customer acceptance of each deliverable. Every intra-group contract inside the book (the parent pharma company sourcing API from its wholly owned CDMO subsidiary) must be flagged at inception under Section 92BA of the Income-tax Act 2025 for Rule 10D transfer-pricing documentation and the annual Form 3CEB filing. Every third-party principal contract that crosses Rs 50 lakh in aggregate FY billing invokes Section 194Q on the buyer side — the principal deducts 0.1 percent TDS under payment code 1031 in the recodified Section 393 Serial 8 (ii) mapping, and the CDMO tracks the deduction as credit against its own Form 26AS. API CDMO margin reconciliation cost plus fixed price milestone is the standing monthly close discipline that pulls all four layers — contract-wise revenue recognition, per-contract-type margin variance, Section 92BA intra-group flag, and Section 194Q TDS credit register — into a single reconciliation pack.

Quick reference

The reconciliation in one paragraph

A CRAMS operator running a diversified CDMO contract book must recognise revenue under Ind AS 115 differently for each of the three principal contract types it holds — cost-plus, fixed-price, and milestone — must classify every intra-group manufacturing contract under Section 92BA of the Income-tax Act 2025 as a Specified Domestic Transaction with Rule 10D documentation and the annual Form 3CEB filing, must track the Section 194Q payment code 1031 TDS credit that its principal buyers deduct on aggregate contract billing above Rs 50 lakh per financial year, and must run a per-contract-type margin variance analysis at monthly close to catch cost creep on fixed-price contracts before it becomes a completed-contract loss provision under Ind AS 37. The three contract types carry structurally different economics — cost-plus at a transparent 10 to 25 percent margin band, fixed-price at a 20 to 40 percent margin band that reflects the CDMO’s cost-overrun risk premium, and milestone-based at a 25 to 30 percent band with staged deliverable-linked payment cycles — and the reconciliation surface where finance controllers earn their keep is the contract-wise revenue-recognition tracker keyed to the Ind AS 115 method appropriate to each contract type, combined with the per-contract-type margin variance table that surfaces the estimate-at-completion drift on fixed-price contracts before it lands as a year-end provision.

What the scenario looks like in India

The Indian CRAMS industry — Contract Research and Manufacturing Services, the phrase that captures both the contract-research-organisation clinical-trial work and the contract-development-and-manufacturing-organisation active-pharmaceutical-ingredient work — is one of the fastest-growing pharma sub-sectors. It operates at the intersection of the domestic backward-integration story and the global innovator-outsourcing story. The CDMO sub-slice of the sector — the API and intermediate contract manufacturing work — sits on the same plant floor as the captive-manufacturing base of the vertically integrated formulators but runs under a distinct commercial and revenue-recognition regime because the customer (the principal) controls the specification, the dossier, and the release testing while the CDMO controls only the manufacturing process itself.

Illustrative Tier-2 pharma CRAMS operators running multi-contract-type CDMO books at the scale relevant to this reconciliation include Suven Life Sciences and Suven Pharmaceuticals (the demerged entities running the CRAMS book from the Suryapet and Pashamylaram plants in Telangana), Neuland Laboratories (Hyderabad-anchored API CDMO), Piramal Pharma (multi-site global CDMO with Indian plants at Ennore, Ahmedabad, Digwal and Aurora), Laurus Labs (Vishakhapatnam-anchored API and formulation CDMO), Divi’s Laboratories (Hyderabad-Vishakhapatnam axis at scale), Syngene International (Biocon’s CRO-CRAMS arm at Bangalore), and Aragen Life Sciences (formerly GVK Bio, headquartered at Hyderabad). Each operates a differentiated contract mix — some skew heavily to fixed-price innovator work, others carry a larger cost-plus intra-group book from parent-company backward integration, and a few carry a meaningful milestone-based portfolio linked to development-stage compounds that transition through validation and commercial launch.

For the reconciliation this article walks through, the reference persona is a Tier-2 CRAMS operator running a Rs 650 crore per year CDMO contract book — illustratively split roughly 40 percent cost-plus at an average 18 percent margin (Rs 260 crore of aggregate FY value), roughly 35 percent fixed-price at an average 32 percent margin (Rs 227.5 crore), and roughly 25 percent milestone-based at an average 28 percent margin (Rs 162.5 crore) — across a mix of intra-group backward-integration contracts (which trigger Section 92BA Specified Domestic Transaction documentation) and third-party principal contracts (which fall outside Section 92BA but are subject to Section 194Q TDS deduction on the principal’s purchase side above Rs 50 lakh aggregate per financial year).

The regulatory overlay

Three regulatory anchors define the CDMO margin reconciliation cycle. Ind AS 115 governs the revenue-recognition method for each contract type. Section 92BA of the Income-tax Act 2025 (recodified from the Income-tax Act 1961) sets the Specified Domestic Transaction documentation regime for intra-group contracts. Section 194Q of the Income-tax Act 2025 sets the buyer-side TDS obligation on principal-side purchases above Rs 50 lakh.

Ind AS 115, Revenue from Contracts with Customers, applies the five-step model — identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price to the performance obligations, and recognise revenue when (or as) each performance obligation is satisfied. Paragraph 35 sets the three criteria under which a performance obligation is satisfied over time (the customer simultaneously receives and consumes the benefits; the entity’s performance creates or enhances an asset that the customer controls; or the entity’s performance does not create an asset with alternative use and the entity has an enforceable right to payment for performance completed to date). If none of the three criteria applies, revenue is recognised at a point in time under paragraph 38.

For a cost-plus CDMO contract, the customer typically controls the API being manufactured — the CDMO produces to the principal’s specification with the principal’s regulatory dossier — and the CDMO has an enforceable right to reimbursement of costs plus the agreed margin at each cost-incurrence step. The contract satisfies paragraph 35(b), and revenue is recognised over time using an input method as costs are incurred, with the margin overlay applied at the same cadence. The reconciliation surface is the actual-costs-incurred ledger against the customer-approved cost pass-through and the agreed-margin calculation.

For a fixed-price CDMO contract, the API specification is bound to the principal’s product (no alternative use) and the CDMO has an enforceable right to payment for performance completed to date. The contract satisfies paragraph 35(c), and revenue is recognised over time using the cost-to-cost input method per paragraph B14 — the ratio of costs incurred to date over expected total costs at completion, applied to the fixed contract price. The CDMO absorbs cost overruns and retains cost savings inside the fixed price. The reconciliation surface is the estimate-at-completion cost forecast against the fixed contract price, refreshed at every reporting date, with a completed-contract loss provision recognised under Ind AS 37 paragraphs 66 to 69 when the expected total costs exceed the contract price.

For a milestone-based CDMO contract, each milestone (typically a development-scale batch delivery supporting early formulation-development work, a validation-scale batch delivery of 100 kg to 500 kg supporting the regulatory dossier submission, and a commercial-launch-scale batch delivery of tonnes for the principal’s launch inventory) is a distinct performance obligation with a distinct point-in-time revenue-recognition trigger under paragraph 38. Revenue is recognised at each milestone completion when control of the milestone deliverable transfers to the principal — the control transfer point is customer acceptance sign-off against the pharmacopoeial specification referenced in the contract, issued after the principal’s quality team completes the release-testing cycle on the delivered batch.

Section 92BA of the Income-tax Act 2025 defines Specified Domestic Transactions between associated enterprises that trigger the transfer-pricing documentation regime under Rules 10D and 10AB. When a CDMO contract sits inside a group — a parent pharma company contracting its wholly owned CDMO subsidiary to manufacture API for the parent’s formulation plants — the intra-group manufacturing charge crosses the SDT perimeter above the aggregate value threshold and requires arm’s length pricing evidence, a comparable-uncontrolled-price or transactional-net-margin benchmarking study, and an annual Form 3CEB filing with the tax return signed by an accountant. The backward-integration API manufacturing transfer pricing walkthrough covers the intra-group perimeter in operational depth. Third-party CDMO contracts (with unrelated principal buyers) fall outside Section 92BA and require only ordinary arm’s length pricing evidence for regular tax scrutiny. The reconciliation discipline is to flag every intra-group contract at contract inception with a Section 92BA marker so the year-end Form 3CEB compilation is a one-click extract from the contract master rather than a reconstruction exercise.

Section 194Q of the Income-tax Act 2025 requires the buyer to deduct TDS at 0.1 percent (5 percent if the seller has not furnished a PAN) on the aggregate value of goods purchased from a single resident seller above Rs 50 lakh in a financial year. The TDS is reported under payment code 1031 in the recodified Section 393 Serial 8 (ii) mapping — the TDS payment code 1031 Section 393 Serial 8 walkthrough covers the deduction mechanics in operational depth. On the CDMO side, the principal pharma company that buys the API contract-manufactured output above Rs 50 lakh from a single CDMO deducts 194Q at 0.1 percent on the aggregate FY billing beyond the threshold; the CDMO tracks the deducted TDS as credit against its own tax liability by reconciling the deducted amount to its Form 26AS and to the principal’s TDS return in Form 26Q. Section 206C(1H) is the mirror-image seller-side TCS provision at 0.1 percent — the CBDT tie-breaker circular applies so both are not triggered on the same transaction, but the CDMO’s TCS-collection register (where the CDMO is the seller) and the principal’s 194Q-TDS-deduction register (where the principal is the buyer) must reconcile at month-end to avoid a double-count or a leak.

A worked example

Illustrative — the following figures represent the operating pattern of a Tier-2 CRAMS operator running a diversified CDMO contract book at the scale that Indian mid-cap listed CDMOs operate. Public disclosures do not reveal per-contract-type margin structure at the granularity below; cross-verify against your own contract register and revenue ledger before action.

The CRAMS operator closes October 2025 with the following CDMO contract-book position, converted to Rs crore for the FY 2025-26 aggregate run-rate. The book is split across three principal contract types.

Within the cost-plus book, roughly 65 percent (Rs 169 crore) is intra-group backward-integration contracts — the CRAMS operator supplying API to a group formulation entity. These carry the Section 92BA Specified Domestic Transaction marker and feed the Rule 10D documentation and the Form 3CEB annual filing. The remaining 35 percent (Rs 91 crore) is third-party cost-plus with domestic pharma principals; these fall outside Section 92BA.

Within the fixed-price book, all Rs 227.5 crore is third-party contracts with domestic and export principals. Twelve individual fixed-price contracts each exceed Rs 5 crore in FY 25-26 aggregate billing; ten of these principals cross the Rs 50 lakh Section 194Q threshold and deduct 0.1 percent TDS on the aggregate purchase, reported under payment code 1031 in their Form 26Q filings. The aggregate 194Q TDS credit accruing to the CRAMS operator across these ten fixed-price principals for FY 25-26 is illustratively of the order of Rs 0.19 crore — 0.1 percent applied to approximately Rs 190 crore of aggregate billing above the Rs 50 lakh per-principal threshold.

Within the milestone book, seven active contracts each carry a three-stage milestone schedule — development batch, validation batch, commercial launch batch. Two contracts have completed the development milestone in October 2025 (recognising Rs 3.8 crore aggregate revenue at point-in-time), one has completed the validation milestone (Rs 6.2 crore recognised), and none have hit the commercial-launch milestone in the month. The Ind AS 115 point-in-time trigger for each milestone is customer acceptance sign-off — a formal quality-release certificate against the pharmacopoeial specification referenced in the contract, issued after the principal’s quality team completes the release-testing cycle on the delivered batch.

At month-end close the finance team runs a per-contract-type margin variance table:

The 360-basis-point negative variance on the fixed-price book is the single largest attention item. A per-contract analysis reveals two fixed-price contracts where the estimate-at-completion cost forecast has crossed the fixed contract price — the CRAMS operator must recognise a completed-contract loss provision under Ind AS 37 paragraphs 66 to 69 for the full expected loss on each. Illustratively, the two contracts together carry a Rs 2.4 crore completed-contract loss provision, which flows to the P&L as an accelerated recognition of the entire expected loss in the current tax period rather than staged over the remaining performance-obligation cycle.

The API yield loss and solvent recovery reconciliation walkthrough covers the plant-operations reconciliation surface — theoretical yield versus actual yield on the Chapter 29 API step, and the Chapter 27 solvent recovery cycle — that drives the cost-of-goods figure feeding every one of these margin variance lines.

Common reconciliation breakages

Four breakages recur across Indian CDMO/CRAMS operators running a diversified contract book, and each maps to a specific control failure at the interface between the contract master and the revenue-recognition ledger.

• Ind AS 115 method drift across contract types. The most common failure mode is a single revenue-recognition method applied uniformly across cost-plus, fixed-price and milestone contracts — usually the cost-to-cost input method extended to all three regardless of contract structure. Cost-plus contracts do not use cost-to-cost (they use costs-incurred with margin overlay); milestone contracts do not use cost-to-cost (they use point-in-time at deliverable acceptance). Applying the wrong method distorts the revenue-recognition timing, inflates or defers reported revenue against the true Ind AS 115 pattern, and creates a restatement risk at year-end audit. Reconciliation discipline: the contract master carries an explicit revenue-recognition method field per contract, populated at contract inception, and the revenue ledger draws only from the method-appropriate calculation.

• Section 92BA intra-group contract flag missed at inception. The Specified Domestic Transaction perimeter is triggered by intra-group status plus aggregate-value threshold — but the flag must be captured at contract inception, not reconstructed at year-end. Contracts that miss the flag at inception generate a scramble at Form 3CEB filing time, incomplete Rule 10D documentation, and a transfer-pricing addition risk at scrutiny. Reconciliation discipline: the contract master carries an explicit intra-group flag and Section 92BA marker per contract, populated at inception against the group-entity list, and the year-end Form 3CEB compilation is a one-click filter on the flag rather than a reconstruction exercise.

• Section 194Q TDS credit unreconciled per principal. Principal-side buyers deduct 0.1 percent TDS on aggregate purchases above Rs 50 lakh and report the deduction in their own Form 26Q under payment code 1031. The CDMO’s Form 26AS shows the aggregate credit but does not always tie cleanly to the CDMO’s own contract-billing register — timing differences (deduction on advance versus deduction on invoice), threshold-crossing timing (the first invoice that crosses Rs 50 lakh in the FY versus subsequent invoices), and Section 194Q-versus-206C(1H) classification (Section 206C(1H) applies on the CDMO’s TCS-collection side and the CBDT tie-breaker circular determines which of the two applies to any transaction) all create reconciliation gaps. Reconciliation discipline: a per-principal TDS credit register that reconciles the CDMO’s own invoice-level 194Q-expected calculation to the Form 26AS credit and to the principal’s Form 26Q line, month by month.

• Fixed-price completed-contract loss provision recognised late. Ind AS 37 paragraphs 66 to 69 require the CDMO to recognise a provision for the full expected loss on a fixed-price contract as soon as the expected total costs at completion cross the fixed contract price — not staged over the remaining performance-obligation cycle. Finance teams that discover the cost overrun only at year-end (rather than at monthly close via the per-contract estimate-at-completion refresh) recognise the provision late, restate prior-quarter interim reports, and take an audit finding. Reconciliation discipline: the monthly estimate-at-completion refresh on every fixed-price contract, with an automated trigger when the refreshed forecast crosses the contract price.

How a reconciliation platform handles this

A purpose-built pharma reconciliation platform ingests the CDMO contract master, the per-contract cost ledger, the per-contract billing register, and the principal-side TDS credit statements — and produces a contract-wise revenue-recognition tracker that applies the Ind AS 115 method appropriate to each contract type (cost-plus input method, fixed-price cost-to-cost, milestone point-in-time), a per-contract-type margin variance table at monthly close, a Section 92BA intra-group contract register with the Rule 10D documentation link and Form 3CEB feed, and a Section 194Q payment code 1031 TDS credit reconciliation per principal against the Form 26AS credit. The platform automates the monthly estimate-at-completion refresh on every fixed-price contract and raises a completed-contract loss provision alert when the forecast crosses the contract price. Match rate improvement of 51 to 88 percent on the CDMO billing to principal-side TDS credit reconciliation, combined with an ISO 27001:2022 posture and DPDP Act 2023 aligned data handling, is what makes the platform an infrastructure investment for a Tier-2 CRAMS operator running a diversified CDMO contract book rather than a spreadsheet substitute.

Cross-cluster bridges and where to read next

The CDMO margin reconciliation documented in this article sits alongside two Wave B pharma companions in the API operations sub-theme. The backward-integration API manufacturing transfer pricing walkthrough covers the same Section 92BA Specified Domestic Transaction perimeter from the intra-group transfer-pricing angle for the vertically integrated formulator that runs its own captive CDMO subsidiary. The API yield loss and solvent recovery reconciliation walkthrough covers the plant-operations reconciliation surface that drives the cost-of-goods figure feeding every CDMO contract’s margin calculation.

The Theme 3 Wave A cornerstone API vs formulation HSN 2941/3003/3004 reconciliation guide is the pillar reference for the API-and-formulation HSN classification map that underpins every CDMO contract’s GST treatment. The cross-cluster TDS reference for the payment code 1031 mechanic sits at TDS payment code 1031 Section 393 Serial 8 — the same code that principals deduct on CDMO API purchases above the Rs 50 lakh threshold.

The methodology framework for the contract-wise revenue-recognition tracker, the per-contract-type margin variance analysis, and the monthly estimate-at-completion refresh cycle sits in Terra Insight’s reconciliation playbook for monthly close operations pillar. The commercial pillar for the pharma sub-cluster is Pharma reconciliation software India; the broader authority for the platform is reconciliation software India.

The five FAQs below address the operational questions Indian CRAMS finance controllers ask most often when building a standing monthly CDMO margin reconciliation cycle across cost-plus, fixed-price and milestone contract mixes.

Terra Insight Editorial Team Reconciliation Infrastructure

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

Published 15 July 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

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024