THE LINUX FOUNDATION PROJECTS
Docs navigation
On this page

    3.4.17 Payment Currency Billed Cost

    Dataset: Invoice Detail
    Column Type: Metric
    Feature Level: Conditional
    Data Type: Decimal
    Since: 1.4

    Payment Currency Billed Cost represents the Billed Cost as expressed in Payment Currency. This metric is essential for organizations that need to reconcile their financial records in the currency used for actual settlement, especially when it differs from the currency used for initial billing.

    3.4.17.1 Requirements

    PaymentCurrencyBilledCost MUST adhere to the following requirements:

    • PaymentCurrencyBilledCost MUST be of type Decimal.
    • PaymentCurrencyBilledCost MUST conform to NumericFormat requirements.
    • PaymentCurrencyBilledCost MUST NOT be null.
    • PaymentCurrencyBilledCost MUST be denominated in the PaymentCurrency.
    • PaymentCurrencyBilledCost MUST be the PaymentCurrency-denominated equivalent of BilledCost.
    • PaymentCurrencyBilledCost MAY be non-zero while BilledCost is 0 when PaymentCurrencyBilledCost represents the aggregation of BilledCost amounts (denominated in PaymentCurrency) stated in other records.
    • PaymentCurrencyBilledCost MAY be 0 while BilledCost is non-zero when BilledCost (denominated in PaymentCurrency) is represented in a separate aggregate record.

    3.4.17.2 Examples

    3.4.17.2.1 Example 1: Consistent Grain

    In this scenario, the invoice issuer performs currency conversion at the individual line-item level. The grain of the payment currency matches the grain of the billing currency exactly.

    • Billing Currency: USD
    • Payment Currency: EUR
    • Exchange Rate: 1.00 USD = 0.92 EUR
    Column Value
    InvoiceDetailId ID-001
    ChargeCategory Usage
    BillingCurrency USD
    BilledCost 100.00
    PaymentCurrency EUR
    PaymentCurrencyBilledCost 92.00
    PaymentCurrencyInvoiceDetailId ID-001

    Note: Because the conversion is 1:1, the PaymentCurrencyInvoiceDetailId points to the record's own InvoiceDetailId.

    3.4.17.2.2 Example 2: Divergent Grain

    In this scenario, the invoice issuer tracks usage in the billing currency at a granular level but represents that cost in the payment currency as a separate aggregate record.

    • Billing Currency: USD
    • Payment Currency: EUR
    • Effective Exchange Rate: 1.00 USD = 0.92 EUR
    Column A-101 A-102 Z-999
    InvoiceDetailId A-101 A-102 Z-999
    InvoiceDetailDescription Compute Instance A Compute Instance B Usage in Payment Currency
    BilledCost 45.00 55.00 0.00
    PaymentCurrencyBilledCost 0.00 0.00 92.00
    PaymentCurrencyInvoiceDetailId Z-999 Z-999 Z-999

    Logic Breakdown:

    • Rows A-101 & A-102: These are "child" records. Their PaymentCurrencyBilledCost is 0, so they provide a pointer in PaymentCurrencyInvoiceDetailId to Row Z-999, where the financial settlement value is stored.
    • Row Z-999: This is the "parent" record. It aggregates the costs of the children. To identify itself as the root of this conversion, its PaymentCurrencyInvoiceDetailId matches its own InvoiceDetailId.
    • Reconciliation: A practitioner can now sum all BilledCost values where PaymentCurrencyInvoiceDetailId is Z-999 to verify that the $100.00 total is equal to the 92.00 EUR settlement using the expected exchange rate.

    3.4.17.5 Description

    The Billed Cost as expressed in Payment Currency.

    Constraints

    Property Value
    Column Type Metric
    Feature Level Conditional
    Allows Nulls No
    Data Type Decimal
    Value Format Numeric Format
    Number Range Any valid decimal value