Skip to main content

Organization Usage Views (ORGANIZATION_USAGE)

As your company's Snowflake footprint grows, you will likely create multiple Snowflake accounts. For example, a large enterprise in India might have one account in AWS ap-south-1 (Mumbai) for production, another account in Azure Central India (Pune) for a specific subsidiary, and a third account for development.

The ORGANIZATION_USAGE schema provides a centralized, global view of usage, billing, and contracts across all accounts within your entire organization.

Topics Covered​

  • ACCOUNT_USAGE vs ORGANIZATION_USAGE
  • The ORGADMIN Role
  • Key Organization Views
  • Cross-Account Spend Reporting

ACCOUNT_USAGE vs ORGANIZATION_USAGE​

FeatureACCOUNT_USAGEORGANIZATION_USAGE
ScopeOnly the specific account you are logged into.All accounts within the entire Organization.
Data Latency45 minutes to 2 hours.2 hours to 24 hours (depending on the view).
Primary Use CaseQuery performance tuning, local security auditing, local warehouse costs.Global financial reporting, contract balance tracking, cross-account cost rollups.
Required RoleACCOUNTADMINORGADMIN

The ORGADMIN Role​

By default, the SNOWFLAKE.ORGANIZATION_USAGE schema is only accessible to the ORGADMIN role. Unlike ACCOUNTADMIN, the ORGADMIN role is global—it can create new accounts, view the overall contract, and monitor organization-wide spend.

(To ensure you have the ORGADMIN role, you can check your current user and active role. Run SELECT CURRENT_USER(); and SELECT CURRENT_ROLE(); to verify).

Hands-On Demonstration: Cross-Account Spend Reporting​

Let's simulate how a central FinOps team would use the ORGANIZATION_USAGE views to track costs across all their Snowflake accounts.

1. Database & Schema Setup​

While you query the native views directly, let's create a database to store a materialized reporting table for our FinOps dashboard.

Copy and paste the following code into your Snowflake worksheet.

USE ROLE ORGADMIN;

CREATE DATABASE IF NOT EXISTS BEEMS_FINOPS_DB;
USE DATABASE BEEMS_FINOPS_DB;

CREATE SCHEMA IF NOT EXISTS GLOBAL_BILLING;
USE SCHEMA GLOBAL_BILLING;

2. Querying Organization Spend (USAGE_IN_CURRENCY_DAILY)​

The USAGE_IN_CURRENCY_DAILY view is the single most important view for financial reporting. It translates Snowflake Credits into actual currency (e.g., USD or INR depending on your contract) across all your accounts.

-- View the total spend per account over the last 30 days
SELECT
ACCOUNT_NAME,
USAGE_DATE,
USAGE_TYPE,
CURRENCY,
USAGE_IN_CURRENCY AS DAILY_COST
FROM SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY
WHERE USAGE_DATE >= DATEADD(day, -30, CURRENT_DATE())
ORDER BY USAGE_DATE DESC, ACCOUNT_NAME;

3. Simulating Cross-Account Reporting​

Since we cannot generate real organization data in a sandbox, let's create a simulated reporting table that shows how this data typically looks for a multi-region Indian enterprise.

CREATE OR REPLACE TABLE GLOBAL_BILLING.MONTHLY_ACCOUNT_SPEND (
REPORTING_MONTH DATE,
ACCOUNT_NAME STRING,
CLOUD_REGION STRING,
DEPARTMENT STRING,
TOTAL_SPEND_USD NUMBER(10,2)
);

INSERT INTO GLOBAL_BILLING.MONTHLY_ACCOUNT_SPEND VALUES
('2023-10-01', 'PROD_MUMBAI', 'AWS_AP_SOUTH_1', 'Core Engineering', 12500.50),
('2023-10-01', 'DEV_MUMBAI', 'AWS_AP_SOUTH_1', 'R&D', 3200.00),
('2023-10-01', 'PROD_PUNE', 'AZURE_CENTRALINDIA', 'Marketing Analytics', 4100.75),
('2023-10-01', 'PROD_DELHI', 'GCP_ASIA_SOUTH2', 'Logistics', 8900.20);

You can build a view over this data to forecast future spend or assign chargebacks to specific departments (like the Logistics team in Delhi).

-- Calculate percentage of total organization spend by account
SELECT
ACCOUNT_NAME,
TOTAL_SPEND_USD,
RATIO_TO_REPORT(TOTAL_SPEND_USD) OVER() * 100 AS PCT_OF_TOTAL_ORG_SPEND
FROM GLOBAL_BILLING.MONTHLY_ACCOUNT_SPEND
ORDER BY TOTAL_SPEND_USD DESC;

4. Tracking Your Contract Balance (REMAINING_BALANCE_DAILY)​

If your company purchased a Snowflake Capacity Contract (e.g., a $100,000 upfront commitment), you need to know how fast you are burning through it.

-- Query the remaining balance of your Snowflake contract
SELECT
DATE,
CONTRACT_NUMBER,
CURRENCY,
FREE_USAGE_BALANCE,
CAPACITY_BALANCE,
REMAINING_BALANCE
FROM SNOWFLAKE.ORGANIZATION_USAGE.REMAINING_BALANCE_DAILY
ORDER BY DATE DESC
LIMIT 10;

Summary​

  • ORGANIZATION_USAGE provides a global view of all accounts; ACCOUNT_USAGE is limited to one account.
  • You must use the ORGADMIN role to access these views.
  • Use USAGE_IN_CURRENCY_DAILY to build centralized financial reporting dashboards.
  • Use REMAINING_BALANCE_DAILY to monitor your overall Snowflake contract consumption.