Contract Applied
Column definition from FOCUS v1.3. Read its requirements and implementation guidance before mapping provider data.
- Source
- FOCUS MCP snapshot
- Edition
- v1.3
- Column ID
ContractApplied- Mode
- Read-only
- Library snapshot (UTC)
- 2026-10-08
Constraints
Description
Contract Applied is a set of properties that associate a charge with one or more contract commitments, denoted as key-value pairs in a JSON object. Contract Applied allows the practitioner to track the progress of the commitments to which they have agreed with a service provider.
The FOCUS-defined properties are:
Contract ID: The unique identifier representing a single contract.Contract Commitment ID: The unique identifier representing a single contract term.Contract Commitment Applied Cost: The value of the charge applied to a single contract term.Contract Commitment Applied Quantity: The usage of the charge applied to a single contract term.Contract Commitment Applied Unit: The unit of measure for the usage of the charge applied to a single contract term.
In addition to these, a data generator may include one or more custom properties, also denoted as key-value pairs.
Requirements
Column Requirements
The ContractApplied column adheres to the following requirements:
- ContractApplied MUST be present in a Cost and Usage FOCUS dataset when the service provider supports contract commitments.
- ContractApplied MUST conform to JsonObjectFormat requirements.
- ContractApplied MUST NOT be null when one or more contract commitments are applied to the charge.
Object Schema Requirements
Contract Applied consists of a valid JSON object which contains an array of key-value objects describing the one or more contract commitments applied to the charge. Each object consists of FOCUS-defined keys but can be extended to provide additional details about the contract application.
- If ContractApplied is not null, ContractApplied adheres to the following requirements:
- ContractApplied MUST have a top-level key "Elements" which contains an array.
- ContractApplied root object MAY contain custom objects, in addition to "Elements".
- Each item in "Elements" MUST be an object.
- "Elements" objects MUST conform to KeyValueFormat requirements.
- "Elements" objects MUST contain key-value pairs (contract application properties).
- Contract application property keys SHOULD conform to PascalCase format.
- "Elements" objects MUST contain four key-value pairs, representing "ContractCommitmentID", "ContractCommitmentAppliedCost", "ContractCommitmentAppliedQuantity", and "ContractCommitmentAppliedUnit".
- "Elements" objects MAY contain custom key-value pairs, representing additional datapoints provided by the data generator.
- When custom key-value pairs within "Elements" objects are present:
- Contract application property custom key-value pairs MUST be prefixed with a consistent
x_prefix to identify them as external, custom columns and distinguish them from FOCUS columns to avoid conflicts in future releases. - Contract application property custom key-value pairs MUST be documented by the data generator.
- Contract application property custom key-value pairs MUST NOT be nested.
- Contract application property custom key-value pairs MUST be prefixed with a consistent
- FOCUS-defined contract application properties adhere to the following additional requirements:
- Contract application property key MUST match the spelling and casing specified for the FOCUS-defined property.
- Contract application property value MUST be of the type specified for that property.
- Contract application property MUST adhere to additional normative requirements specific to that property.
- Contract application property keys MUST begin with the string "x_" unless it is a FOCUS-defined allocation property.
Content Requirements
The following keys are used for contract application properties to facilitate querying data across allocations and across service providers. FOCUS-defined keys will appear in the list below, and custom keys will be prefixed with "x_" to make them easy to identify as well as prevent collisions.
<b>Contract ID</b>
Contract ID is a service-provider-assigned identifier for a contract describing the agreed terms between a service provider and a customer. Contracts can include commitment to a certain amount of spend or usage over an agreed period of time.
The "ContractId" property adheres to the following requirements:
- "ContractId" MUST be present in a Cost and Usage FOCUS dataset when the service provider supports contract commitments.
- "ContractId" MUST be of type String.
- "ContractId" MUST conform to StringHandling requirements.
- "ContractId" nullability is defined as follows:
- "ContractId" MUST be null when a charge is not related to a contract commitment.
- "ContractId" MUST NOT be null when a charge is related to a contract commitment.
- When "ContractId" is not null, "ContractId" adheres to the following additional requirements:
- "ContractId" MUST be a unique identifier within the service provider.
- "ContractId" SHOULD be a fully-qualified identifier.
<b>Contract Commitment ID</b>
A Contract Commitment ID is a service-provider-assigned identifier describing an agreement agreed between a service provider and a customer. Contracts can include commitment to a certain amount of spend or usage over an agreed period of time.
The "ContractCommitmentID" property adheres to the following requirements:
- "ContractCommitmentID" MUST be present in a Cost and Usage FOCUS dataset when the service provider supports contract commitments.
- "ContractCommitmentID" MUST be of type String.
- "ContractCommitmentID" MUST conform to StringHandling requirements.
- "ContractCommitmentID" nullability is defined as follows:
- "ContractCommitmentID" MUST be null when a charge is not related to a contract commitment.
- "ContractCommitmentID" MUST NOT be null when a charge is related to a contract commitment.
- When "ContractCommitmentID" is not null, "ContractCommitmentID" adheres to the following additional requirements:
- "ContractCommitmentID" MUST be a unique identifier within the service provider.
- "ContractCommitmentID" SHOULD be a fully-qualified identifier.
- "ContractCommitmentID" MUST have one and only one parent "ContractID".
- "ContractCommitmentID" MUST be equal to ResourceID when ChargeCategory is "Purchase".
- "ContractCommitmentID" MAY be equal to "ContractID".
<b>Contract Commitment Applied Cost</b>
Contract Commitment Applied Cost represents the cost of the charge applied to the contract line item. Contract Commitment Applied Cost is associated with the contract line item via Contract Commitment ID. Contract Commitment Applied Cost is commonly used for monitoring the progress towards fulfilling contractual commitments that may facilitate discounts for resources or services as agreed between a service provider and a customer.
The "ContractCommitmentAppliedCost" property adheres to the following requirements:
- "ContractCommitmentAppliedCost" MUST be present in a Cost and Usage FOCUS dataset when the service provider associates the charge's value with one or more contract commitments.
- "ContractCommitmentAppliedCost" MUST be of type Decimal.
- "ContractCommitmentAppliedCost" MUST conform to NumericFormat requirements.
- "ContractCommitmentAppliedCost" nullability is defined as follows:
- "ContractCommitmentAppliedCost" MUST NOT be null when "ContractCommitmentAppliedQuantity" is null.
- "ContractCommitmentAppliedCost" MAY be null in all other cases.
- "ContractCommitmentAppliedCost" MUST be a valid decimal value.
- "ContractCommitmentAppliedCost" MUST be denominated in the BillingCurrency.
<b>Contract Commitment Applied Quantity</b>
Contract Commitment Applied Quantity represents the quantity of the charge applied to the contract line item. Contract Commitment Applied Quantity is associated with the contract line item via Contract Commitment ID. Contract Commitment Applied Quantity is commonly used for monitoring the progress towards fulfilling contractual commitments that may facilitate discounts for resources or services as agreed between a service provider and a customer.
The "ContractCommitmentAppliedQuantity" property adheres to the following requirements:
- "ContractCommitmentAppliedQuantity" MUST be present in a Cost and Usage FOCUS dataset when the service provider associates the charge's quantity with one or more contract commitments.
- "ContractCommitmentAppliedQuantity" MUST be of type Decimal.
- "ContractCommitmentAppliedQuantity" MUST conform to NumericFormat requirements.
- "ContractCommitmentAppliedQuantity" nullability is defined as follows:
- "ContractCommitmentAppliedQuantity" MUST NOT be null when "ContractCommitmentAppliedCost" is null.
- "ContractCommitmentAppliedQuantity" MAY be null in all other cases.
- "ContractCommitmentAppliedQuantity" MUST be a valid decimal value.
- "ContractCommitmentAppliedQuantity" MUST be denominated in the "ContractCommitmentAppliedUnit".
<b>Contract Commitment Applied Unit</b>
The Contract Commitment Applied Unit represents a service-provider-specified measurement unit for the usage declared in Contract Commitment Applied Quantity. Contract Commitment Applied Unit complements the Contract Commitment Applied Quantity metric.
The "ContractCommitmentAppliedUnit" property adheres to the following requirements:
- "ContractCommitmentAppliedUnit" MUST be present in a Cost and Usage FOCUS dataset when the service provider associates the charge's quantity with one or more contract commitments.
- "ContractCommitmentAppliedUnit" MUST be of type String.
- "ContractCommitmentAppliedUnit" MUST conform to StringHandling requirements.
- "ContractCommitmentAppliedUnit" SHOULD conform to UnitFormat requirements.
- "ContractCommitmentAppliedUnit" nullability is defined as follows:
- "ContractCommitmentAppliedUnit" MUST be null when "ContractCommitmentAppliedQuantity" is null.
- "ContractCommitmentAppliedUnit" MUST NOT be null when "ContractCommitmentAppliedQuantity" is not null.