THE LINUX FOUNDATION PROJECTS
Docs navigation
On this page

    3.4.9 Invoice Detail Grain

    Dataset: Invoice Detail
    Column Type: Dimension
    Feature Level: Mandatory
    Data Type: JSON
    Since: 1.4

    Invoice Detail Grain represents the set of key-value pairs that defines the granularity of an invoice line item. The grain may vary from one record to the next, both within a single invoice and across invoice issuers, and key-value pairs are used instead of separate columns to accommodate this variability.

    This gives FinOps practitioners a single point of reference for all possible Invoice Detail granularities (e.g., SKU, service, resource, custom dimension), supporting downstream data transformations such as reconciliation and cost allocation.

    3.4.9.1 Requirements

    InvoiceDetailGrain MUST adhere to the following requirements:

    • InvoiceDetailGrain MUST be of type JSON Object (serialized as a String where necessary).
    • InvoiceDetailGrain MUST conform to StringHandling requirements.
    • InvoiceDetailGrain MUST conform to KeyValueFormat requirements.
    • InvoiceDetailGrain MUST NOT be null when one or more properties uniquely define the granularity of the invoice line item.
    • InvoiceDetailGrain MUST contain the set of all properties that uniquely define the granularity of the invoice line item.
    • InvoiceDetailGrain SHOULD use the applicable FOCUS-defined Invoice Detail Grain properties listed below to represent the granularity of the invoice line item.
    • InvoiceDetailGrain MUST include all custom Invoice Detail Grain properties that are applicable to the granularity of the invoice line item when there is no equivalent FOCUS-defined property.
    • InvoiceDetailGrain property keys SHOULD conform to PascalCase format.
    • InvoiceDetailGrain property keys MUST begin with the string "x_" unless it is a FOCUS-defined property.
    • FOCUS-defined InvoiceDetailGrain properties MUST adhere to the following requirements:
      • Property key MUST match the spelling and casing specified for the FOCUS-defined property.
      • Property value MUST be of the type specified for that property.

    3.4.9.2 FOCUS-Defined Properties

    The following keys should be used when applicable when a relevant concept is represented on an invoice. For more information, see the relevant Cost and Usage column entry.

    3.4.9.3 Examples

    {
        "ServiceName": "Elastic Cloud Server",
        "ResourceType": "Cloud Host",
        "x_BillingMode": "Pay-per-Use"
    }
    

    3.4.9.6 Description

    The set of key-value pairs that defines the granularity of the invoice line item.

    Constraints

    Property Value
    Column Type Dimension
    Feature Level Mandatory
    Allows Nulls Yes
    Data Type JSON
    Value Format Key-Value Format