Duration: 3

Governance tells you how much Snowflake CoCo costs. Chargeback answers who owes what — and lets you recover it.

In this quickstart you'll deploy the chargeback and cost-attribution layer of CoCo Control Hub — a Streamlit-in-Snowflake app — and produce a real, itemized bill for CoCo usage. You'll attribute usage with a confidence-labeled waterfall, pick the adoption model that matches your engagement, and export an internal showback statement or an external invoice as a branded PDF. No data leaves Snowflake.

By the end you will have generated, from your own account's data:

GitHub (Snowflake-Labs): https://github.com/Snowflake-Labs/sfquickstarts/tree/master/site/sfguides/src/cortex-code-control-hub-chargeback/assets/code

Duration: 3

The three adoption models are presets of two knobs — what you group by (attribution dimension) and who you're billing (internal vs external) — not separate code paths.

Each usage row is attributed by the highest-confidence signal available; anything left over is quarantined rather than billed:

LLM token credits are priced at a flat AI list rate (April 2025: $2.00 global / $2.20 in-region, editable); warehouse compute is priced at your contract credit rate — so the bill reflects the true blended cost of CoCo.

Duration: 8

Download the assets/code folder from the Source Code link above. Set your target in snowflake.yml (the only file you edit — or ask CoCo to fill it):

Expected result: the command prints a URL to the deployed Streamlit app under your database/schema.

Open the app in Snowsight and go to Setup. Run each phase in order (all idempotent):

1. Run Check — verifies required objects
2. Create Missing Objects — runs prerequisites.sql; creates all CC_* tables, stored procedures, and tasks (including the chargeback tables and the cost-tag sync procedure)
3. Seed Default Settings — pricing + config defaults
4. Run Initial Data Refresh — backfills usage and warehouse-attribution summaries

Expected result: Setup shows all checks green, and the Cost Attribution page shows usage for the last 30 days. If it's empty, confirm the account has recent CoCo usage (see Prerequisites).

Duration: 5

Open Attribution & Tags.

1. Review the waterfall panel — see how each signal (service account, then user tag, then role) is applied and what lands in the Unattributed queue.
2. In the cost-tag editor, assign each active CoCo user a Vertical (e.g., Data Platform, Marketing) and set the Partner flag where relevant.
3. Click Save.

Expected result: the grid persists to CC_COST_TAGS, and the Vertical and Partner flag dimensions become selectable on the Chargeback page (they're greyed out until at least one tag exists).

Duration: 6

Open Chargeback. First pick an adoption model, then walk the four steps.

Choose a model — click the M1 · Internal Cross-Charge card. This pre-fills Bill by = Vertical and Audience = Internal showback.

1. Bill by — leave as Vertical (or choose User/Role to try without tags).
2. Scope — set Lookback = 30 days.
3. Audience — Internal · showback is selected; enter a Prepared for value (e.g., Data Platform team).
4. Generate.

Expected result:

Duration: 5

Now bill an outside party from the same data.

Choose a model — click M3 · Partner on Customer Account (pre-fills Bill by = User, Audience = External invoice).

1. Audience — confirm External · invoice; set Margin % = 15.
2. Fill Bill to (e.g., Acme Corp), an Invoice #, and Prepared by.
3. Generate.

Expected result:

Duration: 3

Open Model Bake-off to keep spend efficient:

Duration: 2

Attribution-as-configuration — one app, two knobs (dimension x audience) — generalizes beyond CoCo to any usage you need to split across teams, customers, or partners.