GIPS Compliance vs Time-Weighted Return — What Each Actually Means
GIPS compliance is a firm-level commitment to a verification regime. Time-weighted return is the calculation it requires. Why the two are distinct, and what each one actually proves.
- GIPS compliance is a firm-level commitment to construct composites, present full histories, and verify outputs against documented policies.
- Time-weighted return is the calculation GIPS requires for performance presentation. It is one piece of GIPS, not the whole standard.
- A track record can use the GIPS-style TWR calculation without the firm being GIPS-compliant. Conflating the two confuses what the verification actually proves.
- NakedPnL produces TWR using the geometric chain-linking GIPS requires. It does not, and does not claim to, perform a statutory GIPS verification engagement.
Two phrases get used interchangeably in performance-measurement marketing and they should not be. 'GIPS-compliant' is a firm-level commitment that touches composite construction, full-history presentation, fee disclosure, valuation policy, and an independent verification engagement. 'Time-weighted return' is the specific calculation GIPS requires for the performance number itself. Every GIPS-compliant presentation uses TWR; not every TWR figure has anything to do with GIPS. The conflation matters because it changes what the verification actually proves.
This guide untangles the two ideas. It explains what GIPS is in scope, what TWR is in scope, why GIPS chose TWR as the required metric, and where each one stops. It also explains what NakedPnL claims and does not claim about GIPS — a distinction that matters because the prohibited-language list in this product treats 'GIPS-compliant' as a self-referential claim that NakedPnL is not entitled to make.
What GIPS actually is
GIPS — Global Investment Performance Standards — is a voluntary firm-level standard maintained by the CFA Institute. The current version is GIPS 2020. A firm that wishes to claim GIPS compliance must implement the standard across its entire firm, not just one strategy or one composite. GIPS sets out requirements in eight broad sections: fundamentals of compliance, input data and calculation methodology, composite and pooled fund construction, presentation and reporting, real-estate and private market additions, wrap fee considerations, advertising guidelines, and verification. Compliance is not granted by an external body; the firm asserts compliance against the standard's text, and an independent verifier opines on whether the firm's policies and procedures are designed to comply with GIPS.
The hardest parts of GIPS in practice are the parts that have nothing to do with the calculation. Composites — defined groupings of similar portfolios — must be constructed from every account that meets the composite definition; you cannot keep your bad accounts out. Full firm history must be presented, not curated windows. Fees and benchmarks must be disclosed in a prescribed format. The verifier opines on whether the firm's process actually does what the firm says it does. The calculation — TWR — is a small if essential part of the whole.
What time-weighted return is
Time-weighted return is a calculation that strips the impact of cash-flow timing out of a return figure. Imagine a manager whose strategy returned exactly 0% over a year, but who received a large deposit one day before a 10% market rally. A money-weighted return (or IRR) would attribute that rally to the manager's skill because more capital was at work during the gain. TWR breaks the period into sub-periods at every external cash flow, computes a return for each sub-period without any flow effect, then chain-links the sub-period returns geometrically. The result is a figure that answers 'what did the strategy do per dollar invested across each sub-period' rather than 'what did the investor experience'. The two questions have different correct answers.
The chain-link is geometric: TWR = (1 + r1) × (1 + r2) × ... × (1 + rn) − 1. Each ri is the sub-period return computed as (end NAV − start NAV) / start NAV, with the start NAV taken after the cash flow that opened the sub-period. The arithmetic looks trivial; the discipline is in defining sub-periods correctly, valuing portfolios accurately at the moment of every flow, and using enough numerical precision that the chain-link does not drift across thousands of compounded daily steps. The methodology guide on time-weighted return explained walks the calculation step by step, and the guide on decimal precision in financial calculations covers why floating-point arithmetic is unsuitable for repeatable chain-link results.
Why GIPS chose TWR
GIPS is built around the question 'how do we compare two managers fairly?'. That question only has a clean answer if cash-flow timing is removed from the figure: a manager whose investors happened to deposit in front of a rally is not skilfuller than a manager whose investors happened to deposit before a drawdown. TWR removes the flow effect; MWR/IRR keeps it. For manager-to-manager comparison — exactly the use case GIPS exists to support — TWR is the only metric that survives. MWR is the right metric for an individual investor asking 'what did I make' but it does not answer 'which manager is better'. GIPS therefore mandates TWR with sub-period termination at every external flow.
What 'GIPS-compliant' is and is not
A firm that claims GIPS compliance has done the following: defined the firm boundary, identified every account that meets each composite definition, included those accounts in the relevant composites without exception, computed composite returns as size-weighted aggregates of constituent portfolio returns, presented the composite history with required disclosures (fees, benchmarks, dispersion measures, internal three-year standard deviation), and engaged an independent verifier to opine on whether the firm's processes meet the standard. The compliance claim is firm-wide. A firm cannot have one composite that complies with GIPS and another that does not.
What GIPS compliance does not do is opine on individual track-record figures presented by individual traders. A retail trader posting a brokerage screenshot is not a GIPS firm. Their figure may be correctly computed using the same TWR mechanics, but it is not 'GIPS-compliant' in the sense the standard uses, because GIPS compliance is a firm-level state. Similarly, a marketplace, registry, or analytics product that publishes per-trader TWR figures is not itself a GIPS firm and cannot make the trader GIPS-compliant by hosting their data.
What NakedPnL claims and does not claim
NakedPnL computes time-weighted return using the geometric chain-link method GIPS requires, with sub-period termination at every external cash flow detected from the NAV series. The arithmetic mirrors the GIPS calculation. NakedPnL does not claim to be GIPS-compliant, does not claim to perform a GIPS verification engagement, and does not represent that connected traders are GIPS-compliant by virtue of having a chain. The claim is narrower and more honest: the calculation uses the time-weighted return methodology required by GIPS, applied to the connected venue's primary records, with results re-derivable by any third party.
This distinction is enforced inside the codebase. The prohibited-language list bans the phrase 'GIPS-compliant' as a self-referential claim because NakedPnL is not the entity making firm-level compliance assertions. The user-facing copy uses formulations like 'calculated using the time-weighted return methodology required by GIPS', which is a true and verifiable statement about the calculation, not a claim about firm-level compliance. The verified-track-record glossary entry sets out the four properties (independent data, deterministic computation, append-only history, published methodology) that NakedPnL does claim, and they are different from GIPS firm-level compliance.
Where the two converge in practice
| Property | GIPS firm-level compliance | NakedPnL chained TWR |
|---|---|---|
| Calculation | TWR with sub-period termination at flows | Same — Decimal.js precision, geometric chain-link |
| Data source | Firm's own records + administrator/custodian where required | Read-only API responses from connected venue |
| Composite construction | Required — group similar portfolios, include all eligible accounts | Single account per chain; no cross-trader composites |
| History presentation | At least 5 years (or since inception) up to 10 years | Full history of every connected account, no upper bound |
| Disclosure regime | Fees, benchmarks, dispersion, standard deviation, etc. | Methodology page; no fee disclosure (NakedPnL is not a manager) |
| Independent verification | External verifier opines on firm's policies | Cryptographic — any third party re-derives via published methodology |
| Scope of claim | Firm-wide | Per-account (per-chain) |
The overlap is the calculation itself. The divergence is everything around it. GIPS is a firm-level standard with composite-construction discipline and a statutory verification engagement; NakedPnL is a per-account chain with a cryptographic verification surface. They are complementary in the sense that a GIPS firm running its calculation through NakedPnL would gain a publicly re-derivable surface for its TWR figures, but GIPS firms do not typically need that — they have their verifier's opinion. Where NakedPnL adds value is for managers and traders who are not GIPS firms but want a comparable verification surface for their TWR figures.
Why people conflate the two
The conflation is partly marketing. 'GIPS-compliant' sounds authoritative, and many marketing surfaces use it loosely to mean 'we calculate returns the way GIPS firms do'. That phrasing is misleading because compliance is firm-wide and includes much more than the calculation. The honest formulation is 'we use the calculation method GIPS requires' or 'our returns are computed using time-weighted return per GIPS methodology'. NakedPnL uses the latter formulation specifically because it is true and the broader claim would not be.
Another source of confusion is that many readers do not know GIPS is voluntary. GIPS is not a regulator; the CFA Institute does not enforce compliance with statutory penalties. Compliance is a market signal that institutional allocators look for. A firm not claiming GIPS compliance is not breaking a rule; it has chosen not to participate in the standard. Conversely, a firm claiming compliance has voluntarily put itself under a verifier's scrutiny.
What this means for trader marketing
A retail trader cannot truthfully describe their track record as 'GIPS-compliant'. They are not a GIPS firm; the standard does not apply to them; the calculation alone is not the compliance. They can truthfully say their performance is computed using the time-weighted return methodology required by GIPS, if that is what their data and computation actually do. The distinction is not pedantic — it is what allocators look for when they evaluate marketing claims, and it is what regulators (FCA in the UK, SEC in the US) look at when reviewing performance representations for misleading content.
On NakedPnL the framing is built into the surface. Traders publish a TWR figure that is re-derivable by any third party from primary records. The claim is precise: this figure was computed from this NAV series using this method. It is not a GIPS-compliance claim and is not represented as one. Allocators reviewing the chain see a calculation method they recognise (the same one GIPS requires) applied to data they can independently verify (the read-only API responses). That is a stronger position for the trader than an unsupportable 'GIPS-compliant' claim, and it does not require a verification engagement that retail traders cannot afford.
How to ask the right question of a track-record claim
When evaluating any track-record presentation, the useful questions split along the GIPS-vs-TWR axis. For the calculation: is it TWR with sub-period termination at every flow, or is it total return / IRR / something else? Is the precision sufficient (decimal arithmetic, not floating-point)? Is the methodology documented? For the firm-level posture: does the entity claim GIPS compliance, or merely the GIPS calculation? If GIPS compliance is claimed, who is the verifier and when was the most recent engagement? If only the calculation is claimed, is the underlying data third-party-verifiable, or does the viewer have to trust the entity's word?
On a NakedPnL chain, the answers are: TWR with sub-period termination at flows; Decimal.js precision; documented at /docs/verification; no GIPS firm-level claim; data third-party-verifiable from raw venue API responses through the chain bundle and the OpenTimestamps anchor. That set of answers is honest and complete. It is not equivalent to GIPS firm-level compliance, and it does not pretend to be.