Skip to main content

Price Profiles

Overview

A PriceProfile groups instruments that share the same yield conventions and curve configuration. Every instrument managed by Price Engine is associated with a profile via the profileName field in Static Data Server. If no profile is assigned, the instrument falls back to the _DEFAULT profile.

Profiles allow a desk or book to share consistent pricing conventions without configuring each instrument individually.

Field Reference

FieldDescription
nameUnique profile identifier. Read-only after creation.
bondYieldConventionYield convention used when computing yields for standard bonds (e.g. US_STREET, UK_GILTS).
billYieldConventionYield convention used for Treasury Bill instruments.
gCurveName of the G-Spread reference curve from Curve Engine. Used for G-spread analytics.
zCurveName of the Z-Spread reference curve from Curve Engine. Used for Z-spread analytics.

How Profiles Feed into Resolved Price Controls

When a ResolvedPriceControl is assembled, Price Engine fetches the PriceProfile matching the instrument's profileName and merges the following fields:

  • bondYieldConvention
  • billYieldConvention
  • gCurve
  • zCurve

If the PriceProfile is not yet available, the ResolvedPriceControl validation fails with Price profile not found and pricing is suspended until the profile arrives.

Creating a Profile

Price Profiles are created automatically when a corresponding Instrument Profile is created in Static Data Server. See Instrument Profiles for instructions.

Assigning a Profile to an Instrument

Profile assignment is managed in Static Data Server via instrument.profileName. In the Prices view, the Profile column is editable — changing it updates instrument.profileName in SDS directly.

New Instrument Defaults

When a new instrument arrives and no PriceControl record exists for it, Price Engine creates one automatically. The initial values are taken from the profile template record — the PriceControl whose instrumentId equals the profile name itself.

This mechanism lets administrators define default pricing model, price source, spread type, and workout settings for all new instruments in a given profile. Configure these defaults in the Price Profiles view under the New Instrument Defaults section.

For example, if the US-CORP profile template has priceSource = TWEB and model = SOURCE, any new instrument assigned to US-CORP will start with those values. Individual instruments can still be edited after creation.