Toast Analytics model

Payouts

Toast card payouts per settlement date: card payments, refunds, processing fees, withholdings and what landed in the bank, with the effective fee rate.

Grain
settled date x restaurant
Built from
  1. 1
    Raw tables
  2. 1
    Staging
  3. 1
    Core
  4. 1
    Analytics
Reads from Toast Analytics
analytics_payout_by_settled_date
Ships as
Weld and dbt SQL, open source on GitHub
core.toast_analytics.payouts
1-- core.toast_analytics.payouts
2-- Toast card payouts per settlement date: card payments, refunds, processing fees,
3-- withholdings and what landed in the bank, with the effective fee rate.
4-- Grain: settled date x restaurant.
5--
6-- Use this to reconcile Toast deposits on your bank statement. The effective fee
7-- rate is fees over payments on the row; over a period, sum both and divide.
8
9SELECT
10    settled_date,
11    restaurant_id,
12    restaurant_name,
13    payout_status,
14    sales_period_start_at,
15    sales_period_end_at,
16    transactions,
17    payment_amount,
18    refund_amount,
19    fee_amount,
20    withholding_amount,
21    payout_amount,
22    SAFE_DIVIDE(ABS(fee_amount), payment_amount)   AS effective_fee_rate
23FROM {{staging.toast_analytics.payout}}

This model and the 2 it depends on. Deploy them together; refs like {{staging.…}} resolve to the matching folders in Weld, and the dbt view uses source() and ref().

Notes

How it counts. And where it stops.

Use this to reconcile Toast deposits on your bank statement. The effective fee rate is fees over payments on the row; over a period, sum both and divide.

Raw tables it reads

  • raw.toast_analytics.analytics_payout_by_settled_date

Put Toast Analytics in front
of your agents.

Connect Toast Analytics, deploy the models, and ask questions in Claude, Cursor or ChatGPT. Free for 14 days, no credit card.