Schema:

BILLING

FOCUS_COST_USAGE_V1_3 view¶

The FOCUS_COST_USAGE_V1_3 view in the BILLING schema exposes cost and usage data formatted to the FinOps Open Cost and Usage Specification (FOCUS) v1.3 (https://focus.finops.org). It provides daily granular charge line items covering Snowflake credit consumption across all sub-accounts within a billing account.

This view is the primary source for FOCUS-compliant cost analytics, enabling practitioners to perform invoice reconciliation, cost allocation, rate optimization, and FinOps reporting using a standardized schema.

Access¶

Access is restricted to org-enabled accounts and requires the ORGANIZATION_BILLING_VIEWER database role on the SNOWFLAKE shared database.

-- Grant the database role to a user role
GRANT DATABASE ROLE SNOWFLAKE.ORGANIZATION_BILLING_VIEWER TO ROLE <role_name>;

-- Query the view
USE ROLE <role_name>;
SELECT * FROM SNOWFLAKE.BILLING.FOCUS_COST_USAGE_V1_3 LIMIT 10;

Grain¶

• One row per daily charge line item per sub-account, service, and charge type.
• ChargePeriodStart and ChargePeriodEnd represent inclusive start / exclusive end of a 24-hour period.
• BillingPeriodStart and BillingPeriodEnd represent the calendar month billing period (inclusive start / exclusive end).

Columns¶

FOCUS standard columns¶

Snowflake custom columns¶

Custom columns are Snowflake-specific extensions to the FOCUS schema. Per FOCUS spec, custom columns use the x_ prefix to distinguish them from standard FOCUS columns.

Cost and quantity relationships¶

Quantity columns¶

ConsumedQuantity and PricingQuantity may differ in both value and unit:

• ConsumedQuantity (up to 9 decimals): How the underlying resource was metered.
• PricingQuantity (rounded to 3 decimals): How Snowflake prices the consumption for billing.

For example, storage is metered in TiB-Days (ConsumedQuantity) but priced in TiB-Months (PricingQuantity = TiB-Days ÷ days in month). For compute, both are in Credits and typically equal.

Cost columns¶

ListCost           = ListUnitPrice × PricingQuantity              (rack rate, up to 9 decimals)
ContractedCost     = ContractedUnitPrice (2dp) × PricingQuantity  (precise mathematical product, up to 9 decimals)
BilledCost         = rounded to 2 decimals — what is actually billed after rounding
EffectiveCost      = rounded to 2 decimals — same as BilledCost

Savings analysis: ListCost - ContractedCost shows savings from negotiated discounts.

Sample queries¶

For additional use cases and sample queries, see the FOCUS Use Cases library (https://focus.finops.org/use-cases/?version=v1-3&use_case=analyze-costs-by-service-name).

Total monthly spend by service¶

SELECT
    DATE_TRUNC('month', "ChargePeriodStart")::DATE AS month,
    "ServiceName",
    SUM("BilledCost") AS total_billed_cost
FROM SNOWFLAKE.BILLING.FOCUS_COST_USAGE_V1_3
GROUP BY 1, 2
ORDER BY 1 DESC, 3 DESC;

Daily spend by sub-account¶

SELECT
    "ChargePeriodStart"::DATE AS charge_date,
    "SubAccountName",
    "x_ServiceLevel",
    SUM("BilledCost") AS daily_cost
FROM SNOWFLAKE.BILLING.FOCUS_COST_USAGE_V1_3
GROUP BY 1, 2, 3
ORDER BY 1 DESC, 4 DESC;

Spend by cloud provider region¶

SELECT
    "HostProviderName",
    "RegionName",
    SUM("BilledCost") AS total_cost
FROM SNOWFLAKE.BILLING.FOCUS_COST_USAGE_V1_3
GROUP BY 1, 2
ORDER BY 3 DESC;

Current billing period summary¶

SELECT
    "BillingPeriodStart"::DATE AS billing_period,
    COUNT(*) AS line_items,
    SUM("BilledCost") AS total_billed,
    SUM("EffectiveCost") AS total_effective,
    SUM("ListCost") AS total_list
FROM SNOWFLAKE.BILLING.FOCUS_COST_USAGE_V1_3
WHERE "BillingPeriodStart"::DATE = DATE_TRUNC('month', CURRENT_DATE)
GROUP BY 1;

Known limitations¶

Usage notes¶

• The view refreshes hourly, but latent usage activity may take up to 72 hours before it is reflected in the data.
• Until month close, data for a given day in a month can change to account for any end-of-month adjustments, mid-month contract amendments, latent usage, or Snowflake account transfers from one organization to another.
• Historical data is available from January 1, 2026 onwards.

Related views¶