Lesson 04 · 6 min

Harmonizing the Data

UTI, UPI, and the CDE: one global dictionary of fields, and the package spread that finally has a home.

Same fields, everywhere

The last lesson said the rewrites brought "globally harmonized critical data elements." That phrase is this lesson. The breaks you just saw had two roots, and only one was about interpretation. The other was cruder: regimes asked for different fields. If London wants the notional as a schedule and New York wants a single current number, the same trade reported to both can never line up, no matter how carefully each side reads its own rules. So before anyone could share code, the regulators had to share a vocabulary.

They built it through CPMI and IOSCO, the global standard-setters that sit above the national regulators for exactly this kind of plumbing. Three pieces, published between 2017 and 2018 and then written into the rewrites: the UTI, which trade, one identifier both sides cite so reports can be paired, the one you have used all along; the UPI, what product, a single code standing for "USD fixed-float interest rate swap" so a product is named the same way everywhere, live in reporting since 2024; and the CDE, the critical data elements, every other field that matters, each pinned to one definition, one format, and one set of allowable values.

What harmonized buys: the package, settled

Take the earlier curve trade, the two swaps Pershing Square executed with Goldman at a single 12.5 basis point spread. The problem there was not that anyone misread the rule. It was that the 12.5 belonged to the package, every field on the report belonged to a single leg, and no agreed field held a package-level number. The harmonized dictionary closes that gap directly, and the way it does it is worth seeing in full.

{  "packageIdentifier": "GS-PKG-2026-0415-07",one id ties the two swaps' UTIs together  "leg1": {    "uti": "…K528CRV1",    "fixedRate": 0.0341,    "price": "not applicable"a vanilla IRS leg has a rate, not a price  },  "leg2": {    "uti": "…K528CRV2",    "fixedRate": 0.03535,    "price": "not applicable"  },  "packageTransactionSpread": 12.5,the 12.5, finally in a field of its own  "packageSpreadNotation": "basis points"}

Two things changed. First, the package became addressable: a Package identifier links the two swaps' UTIs, so a reader can see they are one trade in two parts, and the 12.5 moved into Package transaction spread, a field that exists precisely to hold the level a package traded at. Second, the leg reports stopped pretending to carry a price. A vanilla interest rate swap has no single price; its economics are a rate, the fixed rate on each leg plus any floating spread. So the harmonized rules mark the generic Price element not applicable for the product and let the rate fields do the work. "Report the price" was never a question an interest rate swap could answer, and the dictionary makes that official.

Where price hides, and where it does not

The Price element is not useless; it is conditional. For a cash equity or a bond, price is the number that moves, and reporting it is the point. For an FX forward it is the agreed rate. For a vanilla interest rate swap there is no such single number, so the harmonized rules carry the meaning in the fixed-rate and spread fields and mark the generic Price not applicable. Part of the CDE's job is exactly this bookkeeping: saying, per product, which fields are the real ones, so that "the price" is never left to a local guess.