Operational Transfer Pricing for Captives: A Quiet March Close

Every March, Indian subsidiaries of global groups go through the same ritual. Finance switches into “close mode.” Excel turns into a contact sport. Everyone finds a new reading of the same number. Ledgers get locked. Provisions get booked. Intercompany balances are “reconciled” (sometimes spiritually). And the audit calendar starts pressing on everyone.

And yet, many captive units — distributors, manufacturers, service centres — treat March close as a pure accounting exercise. Transfer pricing is parked for “later.” The TP study will happen after year-end, right?

That is how companies end up with the most avoidable transfer pricing problem of all: a year-end TP adjustment that could have been prevented. It brings further trouble: interest exposure, longer audits, paperwork firefights, and the awkward board conversation where someone asks, “So… why didn’t we see this coming?”

This is where Operational Transfer Pricing (OTP) stops being a buzzword. It becomes a survival tool.

What “Operational Transfer Pricing” actually means

People usually talk about transfer pricing as if it lives in a report: a benchmarking study, a set of comparables, a range, a case for the price. That is “paper TP.”

Operational transfer pricing is different. It is the practice of making sure your books show what your intercompany agreements and TP policy say, in real time or close to it. Then the year-end close is not a rush to force numbers into line.

Think of it like this. Your TP policy is the recipe. Operational TP is cooking the dish every day, so you are not throwing raw ingredients into the oven at 11:55 pm on 31 March and hoping for dinner.

Why March (and the next couple of months) is the danger zone

For Indian captives, March is not just the end of the financial year. It’s when three worlds collide:

The statutory audit wants clean financials and defensible provisions. The tax team wants certainty and few disputes. The group wants results that align with its global operating model.

Transfer pricing sits right at that point. And here is the uncomfortable truth: if your margins drift from the TP model all year, the year-end close is where that drift shows up — and costs money.

The classic captive reality

Most captive subsidiaries in India fall into one of these buckets:

A limited-risk service provider (IT, ITES, R&D support, engineering design, shared services) on a cost-plus mark-up. A limited-risk distributor with a target operating margin or return on sales. A contract manufacturer with a target return on costs or on operating profit.

In each case, the TP model should deliver a steady profit in India, in line with the functions performed and the risks assumed. But the real drivers — pricing, allocations, credit notes, cost pools, capacity utilisation, FX impact — do not behave just because your TP report wants them to.

If you do not track and steer to the target outcome, you end up with “policy vs reality.” Indian TP audits are not kind to that gap.

The cost of getting it wrong: it's not just "an adjustment"

A TP adjustment is rarely a neat single line item. It tends to come with layers.

First comes the adjustment itself. It adds to taxable income when the tested party’s margin falls below the arm’s-length outcome.

Then comes the knock-on effect. There is interest exposure, dispute time, management time, and the internal question, “why did Finance not flag this earlier?”

If the adjustment is large, or it repeats, expect closer checks in later years. There will be more questions on comparables and more documentation requests. Sometimes the inquiry spills into related areas: PE risk for visiting group employees, or treating certain payments as FTS or royalty.

So “we’ll fix it in the TP study” is not a strategy. It is an expensive form of optimism.

The hidden reason: close processes aren't designed for TP

Most finance close processes are built around accounting accuracy and audit readiness. Transfer pricing needs something else: a feedback loop.

Operational TP works only when the close process asks questions like:

Did we hit the target margin for the tested party this quarter? If not, why—volume mix, idle capacity, unexpected costs, FX movement, or pricing leakage? Are the intercompany charges aligned to the contract, and is the contract aligned to conduct? Have we reconciled management accounts (used for group reporting) with statutory books (used for tax)? Do we need a year-end true-up, and if yes, does the mechanism exist contractually and operationally?

When those questions aren’t embedded into the close calendar, TP becomes an afterthought. And afterthoughts are where tax disputes are born.

Operational TP in practice: what it looks like for each captive type

Captive service providers: cost-plus isn’t as simple as it sounds

Service captives often assume that “cost-plus” is automatic: take costs, apply markup, invoice the AE, done.

Except it’s rarely that clean. The most common OTP failure points are:

The cost base is not defined the same way each time. Some teams include bonuses and depreciation; others leave them out. Intercompany allocations arrive late. The contract and the actual delivery also diverge: scope grows, but the price does not move. FX gains and losses can swing margins sharply, and nobody agrees whether FX belongs in operating profit. One-time costs distort the base too: attrition spikes, severance, a tool rollout, relocation.

The practical fix is to treat the year as a series of small closes. Check the margin each quarter, or at least twice a year. Keep agreed levers ready: credit notes, extra invoices, or cost pool fixes. That makes the March close boring, which is the best outcome.

Limited-risk distributors: the margin gets eaten quietly

Distribution entities in India suffer from “silent margin erosion.” The TP policy might state a target EBIT margin. But actual operations add complications:

Discounts and rebates are booked in different ways. Warranty provisions spike late in the year. Marketing spend is booked locally, with no clear answer on whether it gets reimbursed. Inventory write-downs arrive without warning. Pricing decisions are taken at regional level, but the tax risk lands in India.

Operational TP here means lining up commercial governance with the TP result — not by dictating prices, but by making the policy say how unusual items are treated, and how support and reimbursement should flow.

Contract manufacturers: capacity utilisation can wreck your model

Contract manufacturing margins are sensitive to capacity. A policy built on steady utilisation breaks when demand moves.

Idle capacity costs can sit in the Indian books with nothing to offset them. The entity’s margin then drops below the arm’s-length range. The year-end “true-up” gets messy, because it looks like income shifting unless the contract and the documentation clearly support it.

For manufacturers, operational TP often means one thing: track capacity and allocate it with care. If the group controls capacity decisions, the policy must say how idle capacity is borne. The accounting must then follow that logic in the same way every month.

Why intercompany agreements matter more in March than June

The practical building blocks of OTP are contracts, invoices, credit notes, and the records that make the year-end numbers hold up.

This is the part teams underestimate. You can’t just do a year-end adjustment because a spreadsheet says so. You need:

A contract that allows true-ups or price adjustments. A clear basis for the adjustment: service scope, how the price is set, the cost base definition. Evidence that independent parties would act the same way. A clean audit trail of approvals, calculations and intercompany emails.

Otherwise, you must explain to auditors and tax authorities why a large March credit note turned up like a tax-season miracle.

How to build an OTP calendar that actually works

A workable model looks like this:

Early in the year, match the TP policy to what the ERP can actually do. If your system cannot track costs by service line, do not write a policy that needs it.

Through the year, set reviews: monthly for large captives, quarterly for smaller ones. Each review should test the tested party margin against the policy outcome.

At each review, decide whether the gap is normal business noise or a structural drift. Leave noise alone. Drift needs a fix.

Before the March close, run a “pre-close TP health check.” Here you test whether the year-end is likely to land inside the target range, and what to do before the books are locked.

After the close, record the story: what happened, why, and how the intercompany adjustments, if any, reflect the policy.

The punchline: operational TP is boring—until you don't do it

The most honest way to describe operational transfer pricing: it is the accounting version of flossing. Nobody wants to do it daily. But the other choice is painful and expensive. It usually ends with someone asking, “How did this get so bad?”

The goal is simple. For global groups with captive units in India — and for Indian groups with overseas subsidiaries too — make transfer pricing a management discipline, not a post-mortem report.

Because if your books don’t align with your TP model, your TP model won’t save your books.

A takeaway worth remembering

March close is not just about finishing the year. It is about the position you want to be in. One is clean and defensible. The other brings a year of follow-up notices, adjustments and interest, with senior management time spent on issues that should have never come up.

Treat operational TP as a year-round process and your March gets quieter. Audits get shorter. Your TP study becomes what it was meant to be: documentation of a compliant outcome, not a rescue mission.