CDMO Margin and Transfer Pricing: The Piramal and Syngene Playbook

The Tier-1 slice of the Indian pharma CDMO/CRAMS industry — Piramal Pharma Solutions (the Piramal Pharma listed-entity CDMO arm operating from Digwal in Telangana, Ennore near Chennai, Aurora in the US and the Torcan Chemical facility near Toronto), Syngene International (the Biocon Ltd subsidiary listed on the NSE, operating from Bengaluru with a global innovator customer base spanning the US, EU and Japan), Divi’s Laboratories, Laurus Labs and Aragen Life Sciences — runs contract books an order of magnitude larger than the Tier-2 CRAMS operator persona documented in the API CDMO margin reconciliation cost-plus fixed-price milestone Wave B walkthrough. At Tier-1 scale, a diversified CDMO contract book approaches Rs 4,000 crore to Rs 6,000 crore in aggregate FY value, spans intra-group backward-integration contracts to parent-group formulation entities alongside third-party contracts with global innovator originators, and carries a Section 92BA Specified Domestic Transaction perimeter that runs into the low thousands of crore of aggregate intra-group billing across multiple associated-enterprise pairs. The CDMO margin transfer pricing Piramal Syngene pharma playbook is the standing monthly close discipline that pulls the Ind AS 115 revenue-recognition tracker, the per-contract-type margin variance table, the Section 194Q payment code 1031 TDS credit reconciliation, the Section 92BA intra-group contract register with Rule 10D three-tiered documentation, and the annual report Ind AS 24 related-party disclosure feed into a single reconciliation surface that survives both the statutory audit cycle and the transfer pricing scrutiny defence.

Quick reference

The reconciliation in one paragraph

A Tier-1 pharma CDMO runs a five-surface reconciliation cascade at monthly close. Surface one is the contract master — every active CDMO contract tagged with contract type, intra-group flag, Section 92BA marker if applicable, associated-enterprise identification for intra-group contracts, principal-entity identification (PAN and GSTIN) for third-party contracts, contract-life value, and budgeted margin. Surface two is the Ind AS 115 revenue-recognition tracker — cost-plus contracts recognised over time via the input method with margin overlay, fixed-price contracts recognised over time via the cost-to-cost input method against the fixed contract price, and milestone contracts recognised at point in time on customer acceptance of each deliverable. Surface three is the per-contract-type margin variance table — budgeted margin against actual margin at contract level, aggregated by type, with a root-cause flag on every variance above threshold and an estimate-at-completion refresh triggering the Ind AS 37 completed-contract loss provision alert on fixed-price contracts where the forecast crosses the contract price. Surface four is the Section 194Q TDS credit register per principal — the CDMO’s expected 194Q calculation against Form 26AS credit against the principal’s Form 26Q return line. Surface five is the Section 92BA intra-group contract register per associated-enterprise pair — the Rs 20 crore aggregate threshold test, the Rule 10D three-tiered documentation status (master file, local file, benchmarking study), the feed into the annual Form 3CEB accountant’s report, and the feed into the annual report Ind AS 24 related-party disclosure that must reconcile to Form 3CEB at year-end.

What the scenario looks like in India — the Piramal and Syngene playbook

Two illustrative Tier-1 personas anchor this playbook: Piramal Pharma Solutions and Syngene International. Both operate at the top of the Indian pharma CDMO/CRAMS league table, both are listed entities inside larger promoter groups (the Piramal Group and the Biocon Group), and both hold intra-group backward-integration contracts alongside a large global-innovator third-party book. The specifics of each real entity’s contract mix, associated-enterprise pairings, and transfer pricing benchmarking narrative are the subject of their own annual reports and their own tax filings and are not the subject of speculative recomputation here — the persona is illustrative and the reconciliation surface is what this article walks through.

Piramal Pharma Solutions operates a globally distributed CDMO footprint spanning Digwal in Telangana (integrated API, formulation and pharmaceutical development), Ennore near Chennai (API), Ahmedabad and Aurora in the US, and the Torcan Chemical facility near Toronto acquired through the Piramal Torcan Chemicals arrangement. The Digwal site historically covers a mix of intra-group backward-integration API supply for the Piramal Group’s own formulation entities and third-party CDMO contracts with global innovator customers. The intra-group flow triggers the Section 92BA Specified Domestic Transaction perimeter for the resident-associated-enterprise pairs and the transfer pricing scrutiny for cross-border flows to the Piramal international entities.

Syngene International operates a differently shaped CDMO/CRO stack from Bengaluru — the CRO clinical-trial services and discovery-chemistry work sit alongside the CRAMS chemistry services and the API manufacturing work at the Mangalore SEZ. Syngene’s customer base skews heavily to global innovator originators (US, EU and Japan pharma majors) that prefer fixed-price whole-life contracts with milestone gating on development-stage compounds. The intra-Biocon flow — where Biocon’s biosimilars R&D operation contracts Syngene for chemistry services or where Biocon Ltd runs shared-service cost cross-charges to Syngene — sits inside the Section 92BA specified-domestic-transaction perimeter for the resident-entity pairs.

For the reconciliation walkthrough, the reference persona is a Tier-1 CDMO at the illustrative scale of a Rs 4,200 crore FY 2026-27 contract book. The book breaks down as follows: approximately 45 percent cost-plus (Rs 1,890 crore) at an average 18 percent margin, approximately 30 percent fixed-price (Rs 1,260 crore) at an average 32 percent margin, and approximately 25 percent milestone-based (Rs 1,050 crore) at an average 28 percent margin. Of this, approximately 15 percent (Rs 630 crore) is intra-group backward-integration billing across multiple associated-enterprise pairs, with the remaining Rs 3,570 crore being third-party contracts with global innovator originators and unrelated domestic pharma principals. This persona shape is broadly representative of a Tier-1 Indian pharma CDMO in the Piramal or Syngene bracket; the exact numbers are illustrative and are not derived from any specific real entity’s disclosed contract-mix breakdown.

The regulatory overlay — Section 92BA, Rule 10D three-tiered documentation, Ind AS 115, Section 194Q, Ind AS 24

Five regulatory anchors govern the Tier-1 pharma CDMO reconciliation, and each maps to a specific reconciliation surface.

Section 92BA of the Income-tax Act 2025 (recodified from Section 92BA of the erstwhile Income-tax Act 1961) triggers the transfer pricing documentation regime under Rule 10D when the aggregate value of specified domestic transactions between two associated enterprises resident in India exceeds the notified threshold in a financial year. The current threshold is Rs 20 crore aggregate per associated-enterprise pair per financial year (this threshold has been revised over the scheme’s history and must be verified against the current CBDT notification at filing time). For a Tier-1 CDMO with intra-group backward-integration billing of Rs 630 crore across, illustratively, five to eight associated-enterprise pairs, almost every pair crosses the threshold and must be documented under Rule 10D and reported in the annual Form 3CEB accountant’s report filed with the tax return. Third-party contracts (with unrelated global innovator originators or unrelated domestic pharma principals) fall outside Section 92BA and require only ordinary arm’s length pricing evidence for regular tax scrutiny.

Rule 10D of the Income-tax Rules prescribes the three-tiered transfer pricing documentation aligned with the OECD BEPS Action 13 framework. The master file (Form 3CEAA) sits at the top and covers the multinational group as a whole — the organisational structure, the global business overview, the intangibles held across the group, the intra-group financial arrangements, and the consolidated financial position. For a Tier-1 pharma CDMO inside a listed promoter group (Piramal Group or Biocon Group persona), the master file gives auditors and revenue officers the group-level context in which the Indian CDMO’s intra-group contracts sit. The local file (the Rule 10D compliance file) covers the Indian assessee in detail — a description of the Indian CDMO’s business, a list of controlled transactions with associated enterprises, a functions-assets-risks (FAR) analysis of the Indian CDMO’s role in the value chain, and the arm’s length method adopted for each controlled transaction. The benchmarking study is the third tier — a comparable-uncontrolled-price (CUP), transactional-net-margin (TNMM) or cost-plus (CPM) method analysis with comparable third-party contracts sourced from Prowess, Capitaline or an equivalent comparables database, applied per Rule 10CA to compute an arm’s length range with a median tested against the taxpayer’s actual price. All three tiers must be maintained contemporaneously and must reconcile to each other — the master file’s consolidated intra-group flow must tie to the local file’s controlled-transactions list which in turn must tie to the benchmarking study’s tested-transaction population.

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, and recognise revenue when (or as) each performance obligation is satisfied. The three CDMO contract types each satisfy a different over-time or point-in-time trigger: cost-plus contracts satisfy paragraph 35(b) (asset created that the customer controls, enforceable right to reimbursement of costs plus margin) and are recognised over time via the input method as costs are incurred; fixed-price contracts satisfy paragraph 35(c) (no alternative use, enforceable right to payment for performance completed to date) and are recognised over time via the cost-to-cost input method per paragraph B14; milestone contracts do not satisfy any over-time criterion for each individual milestone deliverable and are recognised at a point in time on customer acceptance sign-off per paragraph 38. The API CDMO margin reconciliation cost-plus fixed-price milestone Wave B walkthrough covers the paragraph-by-paragraph Ind AS 115 method application in operational depth for the Tier-2 CRAMS operator persona.

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, reported under payment code 1031 in the recodified Section 393 Serial 8 (ii) mapping. On a Tier-1 CDMO’s third-party book of Rs 3,570 crore, the number of principals crossing the Rs 50 lakh threshold is large — likely fifty to a hundred principals across domestic pharma buyers and Indian arms of global innovator customers. The CDMO’s Form 26AS aggregates the credit; the reconciliation surface is a per-principal TDS credit register that ties the CDMO’s own invoice-level 194Q-expected calculation to the Form 26AS credit and to the principal’s Form 26Q return line.

Ind AS 24 (Related Party Disclosures) requires the listed CDMO’s annual report to disclose the nature of the related party relationship, the aggregate billing per related party, the outstanding balance at reporting date, and any provision for doubtful debts. The same intra-group contract population that feeds the Section 92BA Form 3CEB filing feeds the Ind AS 24 disclosure — the two surfaces must reconcile per associated-enterprise pair. A variance between the Form 3CEB and the Ind AS 24 disclosure is an audit finding waiting to happen.

A worked example — Tier-1 CDMO monthly close on the Rs 4,200 crore contract book

Illustrative — the following figures represent the operating pattern of a Tier-1 Indian pharma CDMO at the persona scale relevant to Piramal Pharma Solutions or Syngene International. Public disclosures do not reveal per-contract-type margin structure or per-associated-enterprise-pair intra-group billing at the granularity below; cross-verify against your own contract register and revenue ledger before action.

The Tier-1 CDMO closes March 2027 with the following FY 2026-27 aggregate contract-book position:

Of the Rs 1,890 crore cost-plus book, approximately 60 percent (Rs 1,134 crore) is intra-group backward-integration billing to five associated-enterprise pairs of the promoter group and 40 percent (Rs 756 crore) is third-party cost-plus with domestic pharma principals. Of the Rs 1,260 crore fixed-price book, essentially all is third-party — global innovator originators and unrelated domestic pharma buyers — with none of the associated-enterprise pairs. Of the Rs 1,050 crore milestone book, approximately 10 percent (Rs 105 crore) is intra-group development-stage work between the CDMO and a group R&D entity, and 90 percent (Rs 945 crore) is third-party. Aggregate intra-group billing across the book is Rs 1,134 crore (cost-plus) plus Rs 105 crore (milestone) = Rs 1,239 crore. However, this billing is distributed across six associated-enterprise pairs, and only the pair aggregates that individually cross the Rs 20 crore threshold fall inside the Section 92BA perimeter.

The Section 92BA intra-group contract register at year-end (illustrative):

The five above-threshold pairs feed the year-end Form 3CEB accountant’s report. The Ind AS 24 related-party disclosure in the annual report lists the same six pairs (including the below-threshold sixth pair), disclosing aggregate billing per pair and outstanding balance at 31 March 2027. The Form 3CEB total for the five above-threshold pairs reconciles to the Ind AS 24 disclosure aggregate for the same five pairs, with the below-threshold pair sitting only in the Ind AS 24 disclosure. Any variance between the two surfaces is investigated and reconciled before both the tax return and the annual report are filed.

The Section 194Q credit register at year-end (illustrative aggregate across the third-party fixed-price and milestone book):

The Rs 4 lakh reconciliation gap is investigated at the per-principal level in the register; typically a few principals have deducted TDS on advance received but not yet reflected against the invoice, or a few principals have crossed the threshold in the closing weeks of the FY but not yet filed Form 26Q for the March quarter. The reconciliation surface exposes the gap by principal and lets the CDMO chase each principal’s Form 26Q filing status before finalising the year-end tax provisioning.

Common reconciliation breakages

Four breakages recur across Tier-1 pharma CDMOs running the Piramal/Syngene playbook, each mapping to a specific control failure.

• Section 92BA per-pair aggregate misread as a book aggregate. The Rs 20 crore threshold applies per associated-enterprise pair per financial year, not to the aggregate intra-group billing across all pairs. A CDMO that aggregates all intra-group billing into a single number (Rs 1,239 crore in the illustration) and treats the entire population as above-threshold over-documents (includes below-threshold pairs in the Form 3CEB filing that should not be there); one that aggregates the population and treats it as below-threshold in the absence of any single pair crossing the threshold under-documents. Reconciliation discipline: the intra-group contract register must aggregate per associated-enterprise pair and test each pair individually against the current threshold, with the above-threshold pairs feeding Form 3CEB and the below-threshold pairs sitting only in the Ind AS 24 disclosure.

• Rule 10D three-tiered documentation gap between tiers. The master file, local file and benchmarking study must reconcile — the master file’s consolidated intra-group flow must tie to the local file’s controlled-transactions list which must tie to the benchmarking study’s tested-transaction population. Gaps between tiers (a controlled transaction in the local file that does not appear in the benchmarking study’s tested population, or a benchmarking study using comparables at a different value than the transaction actually documented in the local file) are the single most common transfer pricing adjustment ground at scrutiny. Reconciliation discipline: the intra-group contract register is the single source that feeds all three tiers, with the same per-associated-enterprise-pair aggregate value carried through master file, local file and benchmarking study.

• Ind AS 24 to Form 3CEB reconciliation break. The annual report Ind AS 24 related-party disclosure and the Form 3CEB accountant’s report both draw from the same intra-group transaction population but on different aggregation logic — Ind AS 24 typically aggregates per related party across all transaction categories, whereas Form 3CEB aggregates per specified-domestic-transaction line. A CDMO that runs the two reports from different underlying data (Ind AS 24 from the financial reporting stack, Form 3CEB from a separate tax-filing-time reconstruction) creates a variance that surfaces at year-end audit. Reconciliation discipline: the intra-group contract register feeds both reports from a single source, with a documented reconciliation between the Ind AS 24 aggregation logic and the Form 3CEB aggregation logic that survives auditor questioning.

• Ind AS 37 completed-contract loss provision missed on cross-border fixed-price contracts. Fixed-price contracts with global innovator originators are frequently denominated in USD or EUR with a whole-life price fixed at contract signing — the CDMO absorbs both cost-overrun risk and FX risk (unless hedged). A weakening rupee against the invoicing currency creates a windfall gain; a strengthening rupee creates a squeeze that can trigger an Ind AS 37 onerous-contract provision even without operational cost overrun. Finance teams that refresh the estimate-at-completion cost forecast only in rupee terms (against the historical hedged rate) miss the trigger when the effective rupee realisation falls below the cost forecast. Reconciliation discipline: the monthly estimate-at-completion refresh on every fixed-price contract carries both a rupee-denominated cost forecast and a currency-of-invoicing revenue expectation, marked to the current FX rate (or the current hedge cover) with the completed-contract loss provision alert firing on either metric. Terra Insight’s reconciliation failure-mode analysis for India methodology treats the FX-adjusted estimate-at-completion refresh as a specific failure mode with a documented control test.

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, the principal-side TDS credit statements, and the group’s associated-enterprise master — and produces a contract-wise Ind AS 115 revenue-recognition tracker that applies the method appropriate to each contract type, a per-contract-type margin variance table at monthly close, a Section 194Q payment code 1031 TDS credit reconciliation per principal against Form 26AS, and a Section 92BA intra-group contract register that aggregates per associated-enterprise pair, tests each pair against the Rs 20 crore threshold, links to the Rule 10D three-tiered documentation (master file, local file, benchmarking study), and feeds both the Form 3CEB annual filing and the annual report Ind AS 24 related-party disclosure from the same underlying data. The platform automates the monthly estimate-at-completion refresh on every fixed-price contract in both rupee and invoicing-currency terms, and raises a completed-contract loss provision alert when either metric 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 a standing infrastructure investment for a Tier-1 pharma CDMO in the Piramal or Syngene bracket rather than a spreadsheet substitute.

Cross-cluster bridges and where to read next

The Tier-1 CDMO transfer pricing playbook in this article sits alongside two Wave B pharma companions in the API operations sub-theme: the API CDMO margin reconciliation cost-plus fixed-price milestone walkthrough (Tier-2 CRAMS operator persona at Rs 650 crore scale) and the backward-integration API manufacturing transfer pricing walkthrough (the same Section 92BA perimeter from the vertically integrated formulator angle rather than the CDMO angle). The loan-licensing manufacturing and pharma CDMO reconciliation guide Wave A cornerstone covers the Section 143 CGST Act 2017 job-work provisions for the alternative contract-manufacturing model where the principal holds the manufacturing licence and the CDMO manufactures on the principal’s licence. 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 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 failure-mode discipline that structures the Section 92BA and Ind AS 24 reconciliation as controlled surfaces sits in the reconciliation failure-mode analysis for India design pillar. The commercial pillar for the pharma sub-cluster is Pharma reconciliation software India; the broader authority is reconciliation software India.

The five FAQs below address the operational questions Tier-1 CDMO finance controllers, transfer pricing leads and statutory auditors ask most often when building a standing monthly close discipline that survives both the tax scrutiny and the annual report audit.

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 16 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