TP Defaults: Tenant-Wide Benchmarking Configuration
The tenant-wide TP defaults document in Quartyl: jurisdiction, PLI, permitted methods, arm length range and base currency, what the block records, and what the study wizard actually starts from.
TP Defaults is the tenant’s benchmarking baseline on paper: the jurisdiction the practice benchmarks in, the profit level indicator it tests by default, the methods it permits, the arm’s length range it computes, and the currency its numbers speak. It is one document inside the firm’s settings record — stored, validated, returned and reset by the firm-settings API — and it is worth being clear at the outset about what it does and does not do today, because the gap matters when a firm is onboarded.
What the block holds
The tp_defaults document carries five fields, each validated against the
platform’s allowed sets:
| Field | Default | Allowed |
|---|---|---|
| Default jurisdiction | India | every country in the platform’s ISO 3166-1 registry (the six curated regimes — India, UAE, USA, UK, Singapore, Germany — first, then alphabetical) |
| Default PLI | OP/OC | OP/OC, OP/Sales, TP/Sales, EBIT/Sales, EBITDA/Sales, Berry Ratio, EBIT/Total Assets |
| Permitted TP methods | TNMM, CUP, RPM, CPM, PSM | any non-empty subset of the five OECD methods |
| Arm’s length range | 25th–75th percentile | lower bound 5–45, upper bound 55–95, lower always below upper |
| Base currency | INR | 37 codes — the six firm-foundation currencies (INR, USD, EUR, GBP, AED, SGD) plus the major currencies of the registered jurisdictions |
Two invariants are enforced at save: the range’s lower percentile must sit below its upper, and at least one TP method must remain permitted. The range bounds (25/75 by default) are the interquartile convention — the same range the statistical results page presents for a study.
What a study actually starts from
Be precise here, because the intuitive reading is wrong: the study wizard does
not read this block. A new study opens on the platform defaults — India,
OP/OC, the 25th–75th percentile band — and every one of the five fields above
is then chosen per study in the wizard, on the study’s own record.
| Field | Where it is really set |
|---|---|
| Jurisdiction | The wizard’s jurisdiction select (every registry country, served by the study form options endpoint) |
| PLI | The wizard’s margin-type select, validated against the same seven indicators |
| Range percentiles | The wizard, with a “apply this jurisdiction’s convention” affordance where the regime prescribes one (India’s Rule 10CA 35th–65th band) |
| Permitted methods | Not constrained per tenant today — the decision is the study’s and the analyst’s |
| Base currency | The wizard’s currency select |
So today TP Defaults is a recorded standard, not a runtime input: writing a value here changes what the settings document says, not what the next study starts with. Treat it accordingly — as the firm’s declared methodology on file, alongside the parameters each study captures for itself — and if your practice relies on a house default, configure it in the wizard on each study and keep the documented standard in your own engagement letters until the two are wired together.
What the defaults deliberately would not decide, in any case, is the study-specific work: the data file and its column mapping, the tested party profile, the data years and averaging approach, the search region and size filters, and every comparable disposition. Those are per-study parameters, and each study’s configuration is part of its record — when a study departs from the firm standard, the departure is visible in the study.
Why keep the baseline anyway
- A declared methodology on file. The document records the standard the firm intends its engagements to run to, in the same settings record that carries the security policy and branding — readable, validated and reset with the tenant’s other settings.
- A guardrail on paper. Restricting the permitted method set (to TNMM and CPM, say) states which methods the firm’s methodology supports, even though the platform does not yet enforce the restriction at the wizard.
- Auditability. Because the block is part of the firm’s configuration record, a reviewer can read the declared standard and compare it against what each study actually captured.
Real consistency today comes from the wizard and from the firm’s own review tiers: the Manager sees a study that drifted from the practice standard, and the record of what was chosen sits on the study.
The PLI formulas behind the selectable indicators — what each ratio divides by and when it is the right choice — are in the PLI reference.
FAQ
If I change the default PLI here, do my open or future studies change? No. The block is not read by the wizard, so neither an open study nor a new one picks it up — set the PLI on the study.
Can the range be something other than the interquartile range? On the study, yes: the wizard takes any lower/upper pair inside the validated window (lower 5–45, upper 55–95), and a regime that prescribes its own band — India’s Rule 10CA 35th–65th — is applied per study. The settings document accepts the same window, as a declared standard.
What is the difference between this page and the wizard parameters? This page is the firm’s recorded baseline; the wizard makes the per-study decision. Where they differ, the study’s own record is what the pipeline ran and what the report reflects.
Does Reset touch this block? Yes — the Firm Settings reset returns TP
Defaults to the platform baseline (India, OP/OC, 25th–75th, all five methods,
INR) along with the security, integrations and branding documents.
See it working in your workspace
Sign in to run the steps above on a real study — or book a demo and we will walk the workflow end to end.
Related docs
Firm Settings: Tenant Configuration Overview
Overview of the Quartyl firm settings panel: the tabs, what is configured tenant-wide versus per study, secret masking, and who can read, change or reset each block.
Read docYour First Study in 10 Minutes (Quickstart)
From empty workspace to a benchmarked study: create it in the three-step wizard, upload and map the Excel dump, pick the PLI and averaging basis, run the pipeline and read the arm's length range.
Read doc