Contract R&D: Research Performed for the Client, Routine Return

Definition

Contract R&D is the research and development performed for a client (another group entity, or an external customer) under contract — the research entity performs the R&D function (the development, the testing, the regulatory work, the research to the client’s specification) using, in the classic form, the client’s direction (the research plan, the IP that is the output — the client’s or the contract’s ownership, the client’s specification), and earns, for the function, a cost-based return — the [cost plus method] (/docs/glossary/cost-plus) (the cost base plus the arm’s length mark-up) or the [TNMM] (/docs/glossary/tnmm) [benchmarked] (/docs/benchmarking/benchmarking-study-guide) return on the contract R&D comparables. Contract R&D’s FAR is the routine research services profile: the function is the research (the development, the testing, the regulatory work — the R&D performed to spec), the assets are the research base (the lab, the equipment, the research staff — the operating assets; the IP output is the client’s/the contract’s, not the researcher’s), and the risks are the operational risks (the research risk — the development failing to meet the spec, the regulatory work’s execution risk) — not the entrepreneurial risks (the IP risk — the value of the output, the market risk of the product the IP enables — the client’s/the entrepreneur’s). The line is the [DEMPE] (/docs/glossary/dempe) analysis: the contract R&D entity performs the D (the Development, the E — Enhancement, in the performance sense) but does not control the D/E/M/P/E (the Development/Enhancement/ Maintenance/Protection/Exploitation — the control of the IP’s value creation is the client’s/the entrepreneur’s), and it does not own the output’s value (the [residual profit] (/docs/glossary/residual-profit) — the IP value — is the entrepreneur’s). The [contract R&D guide] (/docs/transactions/contract-rd-tp) carries the full treatment: the routine vs entrepreneurial line, the [DEMPE/control] (/docs/glossary/dempe) analysis, the [cost-based return] (/docs/glossary/cost-plus), the IP ownership (the contract’s ownership clause), and the [documentation] (/docs/transactions/contract-rd-tp) (the research agreement, the cost base, the mark-up). The Indian [safe harbour] (/docs/glossary/safe-harbour) regime prescribes the contract R&D return (the Rule 10AB family’s contract R&D entry — the OP/OC ≥24% for the software and the generic pharma contract R&D, the [safe harbour guide] (/docs/documentation/safe-harbour-india)’s table) — the prescribed return for the slice that qualifies.

Contract R&D, in one profile:
  1. The function (the research — the development, the testing, the regulatory work — to the client's specification)
  2. The assets (the research base — the lab, the equipment, the staff — not the IP output, the client's/contract's)
  3. The risks (the operational — the development/regulatory execution — not the IP value, not the market of the product)
  4. The return (the cost-based — the cost plus the arm's length mark-up, or the benchmarked/prescribed return)

The element	The content
The function	The research — the development, the testing, the regulatory work, the R&D to the client’s specification (the FAR function set)
The assets	The research base — the lab, the equipment, the research staff (the operating assets) — not the IP output (the client’s/the contract’s ownership)
The risks	The operational — the development failing to spec, the regulatory execution — not the entrepreneurial (the IP value, the market of the product — the client’s/the entrepreneur’s)
The return	The cost-based — the cost base + the arm’s length mark-up (the cost plus), the TNMM benchmarked return, or the prescribed (the Indian safe harbour)

The working read (the contract R&D guide): contract R&D’s [transfer price] (/docs/glossary/alp) is the price of the research services (the client’s payment for the R&D performed — the cost base plus the mark-up, the [cost plus method] (/docs/methods/cost-plus-method) applied, or the [benchmarked] (/docs/benchmarking/benchmarking-study-guide) return), and its defensibility rests on the routine characterization (the routine research services — the DEMPE analysis: the performance of the D/E (the development/enhancement) without the control (the control of the IP’s value creation the client’s/the entrepreneur’s), the no ownership of the output’s value (the residual profit the *entrepreneur’s)) and the cost base (the research cost — the direct, the allocated overheads, the excluded items — the base designed and documented). The routine vs entrepreneurial line is contract R&D’s standing examination question (the [contract R&D guide] (/docs/transactions/contract-rd-tp)’s core): the entity that performs the research (the contract R&D — the routine return) vs the entity that controls the research (the entrepreneurial R&D — the [residual profit] (/docs/glossary/residual-profit), the [profit split] (/docs/glossary/profit-split) territory) — the [DEMPE/control] (/docs/glossary/dempe) analysis the line, the [IP ownership] (/docs/transactions/contract-rd-tp) clause the contract’s statement of it, and the documentation (the research agreement, the cost base, the mark-up) the file’s core. The Indian safe harbour (the Rule 10AB family’s contract R&D entry — the OP/OC ≥24%, the software and the generic pharma, the [safe harbour guide] (/docs/documentation/safe-harbour-india)) is the prescribed return for the slice that qualifies (the [Form 3CEFA] (/docs/documentation/safe-harbour-india) election) — the certainty end, the benchmark fight ended.

Example

An Indian entity, the group’s contract R&D centre for a software product: the overseas principal (the entrepreneur) owns the product IP (the platform, the product design — the principal’s), directs the research plan (the development roadmap — the principal’s direction), and owns the output (the developed features, the IP generated — the contract’s ownership clause, the principal’s). The Indian entity performs the development (the coding, the testing, the quality — to the principal’s specification), holds the research base (the lab — the dev environment, the staff — the operating assets), and bears the operational risk (the development failing to spec, the execution risk) — not the IP risk (the value of the developed features — the principal’s), not the market risk (the product’s market — the principal’s). The FAR: the research function (the development, the testing — the performance of the D/E), the research base (the operating assets, the IP the principal’s), the operational risks (the development/regulatory execution). The [DEMPE] (/docs/glossary/dempe): the Indian entity performs the D/E (the development/enhancement) without the control (the control the principal’s), does not own the output’s value (the [residual profit] (/docs/glossary/residual-profit) the principal’s) — the routine research services [characterization] (/docs/fundamentals/routine-vs-entrepreneurial). The [tested party] (/docs/glossary/tested-party) is the Indian entity (the routine side), the PLI is the [OP/OC] (/docs/glossary/op-oc) (the TNMM — the Indian practice) or the cost plus on the research cost base (the direct

• the allocated overheads, the excluded items documented), the comparables are the contract R&D entities of the same function class (the [search design] (/docs/benchmarking/search-design), the [screens] (/docs/benchmarking/quantitative-screening), the [accept-reject matrix] (/docs/glossary/accept-reject-matrix) recording the entrepreneurial rejects — the IP-owning entities the [qualitative screen] (/docs/benchmarking/qualitative-screening) separates), and the arm’s length range is the comparables’ [IQR] (/docs/glossary/interquartile-range) on the OP/OC — or the prescribed OP/OC ≥24% (the Rule 10AB safe harbour, the Form 3CEFA elected) where the slice qualifies.

See also

• Contract R&D TP Guide
• DEMPE
• Cost Plus Method
• Routine vs Entrepreneurial

FAQ

What is the difference between contract R&D and entrepreneurial R&D? The DEMPE control and the ownership of the output’s value: the contract R&D entity performs the research (the development, the testing — the D/E performance) for the client, without the control (the control of the IP’s value creation the client’s/the entrepreneur’s), and without the ownership of the output’s value (the residual profit the entrepreneur’s) — the routine research services, the cost-based return. The entrepreneurial R&D entity controls the research (the direction, the decision — the D/E/M/P/E control), owns the output’s value (the [residual profit] (/docs/glossary/residual-profit), the IP value), and earns the entrepreneurial return (the [profit split] (/docs/glossary/profit-split) territory, the [residual] (/docs/glossary/residual-profit)). The line is the [DEMPE/control] (/docs/glossary/dempe) analysis — the [contract R&D guide] (/docs/transactions/contract-rd-tp)’s core — and the characterization (which the entity is) documented in the [Local File] (/docs/glossary/local-file-rule-10d) is the [defensibility] (/docs/benchmarking/defending-accept-reject) (the assertion supported, the DEMPE facts, the [IP ownership] (/docs/transactions/contract-rd-tp) clause, not assumed).

What is the DEMPE analysis, and why does it decide the contract R&D return? DEMPE — the Development, Enhancement, Maintenance, Protection, Exploitation — is the OECD intangibles framework’s analysis of who performs and controls the IP’s value creation (the five functions, the performance vs the control the distinction, the residual profit the control of the value). For the contract R&D entity: it performs the D/E (the development, the enhancement — the research work) but does not control the D/E/M/P/E (the control — the direction, the decision of the IP’s value creation — the client’s/the entrepreneur’s), and does not own the output’s value (the [residual profit] (/docs/glossary/residual-profit) the entrepreneur’s) — the routine characterization, the cost-based return. The [DEMPE/control] analysis is the line between the routine (the cost-based) and the entrepreneurial (the residual, the profit split) — the contract R&D’s return (cost-based vs entrepreneurial) decided by the control (the DEMPE facts, the [IP ownership] (/docs/transactions/contract-rd-tp) clause), and the [documentation] (/docs/transactions/contract-rd-tp) the file’s core (the research agreement, the DEMPE analysis, the [cost base] (/docs/glossary/cost-plus), the mark-up).

Is contract R&D a safe-harbour-eligible transaction in India? Yes — the Indian safe harbour regime (the Rule 10AB family, the [safe harbour guide] (/docs/documentation/safe-harbour-india)’s table) prescribes the contract R&D return: the OP/OC ≥24% for the software contract R&D and the generic pharma contract R&D (the eligible transactions, the ≤₹300 cr, the [prescribed circumstance] (/docs/documentation/safe-harbour-india)) — the prescribed return for the slice that qualifies (the [Form 3CEFA] (/docs/documentation/safe-harbour-india) election, the benefits and trade-offs the safe harbour guide carries). The prescribed OP/OC ≥24% is the certainty end (the no comparables, no [range] (/docs/glossary/arms-length-range), no TPO scrutiny of the contract R&D pool) — the benchmark fight ended for the slice; the characterization (the routine contract R&D — the DEMPE facts, the no control, the no ownership) is the common foundation, with or without the safe harbour.