Transition from Billing Entity to Contract Number

Note

Rollout for the updated commands and view updates will occur between August 24 and August 27, 2026. Customers have until October 26, 2026 to make all necessary updates to move to the new commands.

The SQL commands and relevant views for managing accounts are being updated to utilize contract numbers instead of billing entities for multi-contract organizations.

Before the change:

SQL behavior:

The following SQL returned information about the billing entity associated with the Snowflake accounts within the customer’s Organization:

The output of SHOW ACCOUNTS and SHOW ORGANIZATION ACCOUNTS included the following columns:

  • CONSUMPTION_BILLING_ENTITY_NAME
  • MARKETPLACE_CONSUMER_BILLING_ENTITY_NAME
  • MARKETPLACE_PROVIDER_BILLING_ENTITY_NAME

The following SQL accepted a billing entity as a parameter when there were multiple billing entities for the Organization:

View behavior:

The ACCOUNTS view in the Organization Usage schema included the following columns:

  • CONSUMPTION_BILLING_ENTITY_NAME
  • MARKETPLACE_CONSUMER_BILLING_ENTITY_NAME
  • MARKETPLACE_PROVIDER_BILLING_ENTITY_NAME
After the change:

SQL behavior:

  • SHOW ORGANIZATION BILLING ENTITIES is replaced by SHOW ORGANIZATION CONTRACTS, which provides information about all active contracts currently mapped to the Snowflake accounts within the customer’s organization.
  • SHOW ACCOUNTS and SHOW ORGANIZATION ACCOUNTS now return information about the active contracts that accounts within the organization are mapped to. The CONSUMPTION_BILLING_ENTITY_NAME, MARKETPLACE_CONSUMER_BILLING_ENTITY_NAME, and MARKETPLACE_PROVIDER_BILLING_ENTITY_NAME columns are removed from their output, and a CONTRACT_NUMBER column is added.
  • CREATE ACCOUNT, CREATE ORGANIZATION ACCOUNT, ALTER ACCOUNT, and ALTER ORGANIZATION ACCOUNT now accept a contract number instead of billing entity information.

Note: When creating a new account within a multi-contract organization, you must explicitly specify the corresponding contract number to map the account.

View behavior:

The following columns are removed from the ACCOUNTS view in the Organization Usage schema:

  • CONSUMPTION_BILLING_ENTITY_NAME
  • MARKETPLACE_CONSUMER_BILLING_ENTITY_NAME
  • MARKETPLACE_PROVIDER_BILLING_ENTITY_NAME

The following column is added to the ACCOUNTS view in the Organization Usage schema:

  • CONTRACT_NUMBER

What you should do:

Review any usage of the ACCOUNTS view as well as the aforementioned SQL commands, and make the changes necessary to use the contract number instead. Avoid any use of billing entity going forward. Billing entity is deprecated and you will no longer be able to use it after October 26, 2026.

For example, to list active contracts for your organization:

-- Before: listed billing entities
SHOW ORGANIZATION BILLING ENTITIES;

-- After: lists active contracts
SHOW ORGANIZATION CONTRACTS;

To create an account when your organization has multiple contracts:

-- Before: specified billing entity
CREATE ACCOUNT myaccount
  ADMIN_NAME = admin
  ADMIN_PASSWORD = 'TestPassword1'
  EMAIL = 'admin@example.com'
  EDITION = ENTERPRISE
  CONSUMPTION_BILLING_ENTITY = '<billing_entity_name>';

-- After: specify contract number
CREATE ACCOUNT myaccount
  ADMIN_NAME = admin
  ADMIN_PASSWORD = 'TestPassword1'
  EMAIL = 'admin@example.com'
  EDITION = ENTERPRISE
  CONTRACT_NUMBER = '<contract_number>';

To reference contract information in the ACCOUNTS view:

-- Before: queried billing entity columns
SELECT account_name, consumption_billing_entity_name
FROM SNOWFLAKE.ORGANIZATION_USAGE.ACCOUNTS;

-- After: query contract number column
SELECT account_name, contract_number
FROM SNOWFLAKE.ORGANIZATION_USAGE.ACCOUNTS;

Ref: 2399