The money Snowflake sends you for an invoice is less than the invoice, and the gap is bigger than Snowflake’s fee. Take a sample invoice: Globex, a consumer of your paid listing, was billed $25,980.00 on a private offer paid in two installments, and the two payouts against it came to $21,870.00. If Snowflake’s two views count the invoice the same way, which a check below tests on your own data, the $4,110.00 between them is three amounts: the consumer’s sales tax, which was never yours; Snowflake’s fee; and sales tax on that fee, which you owe Snowflake.
Neither number is wrong. Snowflake reports the invoice in one view and the payout in another, each with its own formula, and neither formula alone gets from one number to the other. Snowflake Marketplace payout reconciliation is the work of laying the two side by side. This post builds that bridge on the sample invoice, ranks the reasons it fails to close, and says which view to trust for each month-end question. Snowflake processes provider payouts through Stripe, into the Stripe Express account a paid listing needs, which how you get paid on Snowflake Marketplace covers; here the money is already counted.
Why is a Snowflake Marketplace payout less than the invoice?
Because three amounts come off the invoice total before Snowflake pays you: the consumer’s sales tax, Snowflake’s fee, and the sales tax on that fee, assuming Snowflake’s two views count the invoice the same way. Snowflake’s provider-payout rules also net payouts of “any permitted adjustments,” which neither view breaks out, so an adjustment is a fourth possible difference. The first two are subtracted in the MARKETPLACE_LISTING_INVOICE_STATUS view, which calls the result the expected payout. The third is subtracted in MARKETPLACE_DISBURSEMENT_REPORT, which calls its result the net amount. Snowflake gives a formula for each:
- Invoice-status view.
EXPECTED_PAYOUT_AMOUNTis “Calculated asTOTAL_BILLED_AMOUNT-SALES_TAX_AMOUNT-FEE,” and the total billed “includes the consumer’s taxes and provider fees.” - Disbursement report. “
NET_AMOUNT=GROSS-FEES-TAXES,” whereTAXESis “Sales tax (on the fees), owed to Snowflake by the provider.”
The invoice-status view ties the two together itself. Its PROVIDER_SALES_TAX_AMOUNT “Corresponds to TAXES” in the disbursement report, and its DISBURSEMENT_AMOUNT “Corresponds to NET_AMOUNT.” Read in order, and provided the disbursement report’s GROSS equals SUBTOTAL_AMOUNT and its FEES equals FEE, which you can test with the check below, the bridge runs:
| Step | Subtract | Result |
|---|---|---|
| Start | — | TOTAL_BILLED_AMOUNT |
| 1 | SALES_TAX_AMOUNT, the consumer’s sales tax | SUBTOTAL_AMOUNT |
| 2 | FEE, Snowflake’s fee | EXPECTED_PAYOUT_AMOUNT |
| 3 | PROVIDER_SALES_TAX_AMOUNT (TAXES in the disbursement report), the tax on Snowflake’s fee; holds only if GROSS equals SUBTOTAL_AMOUNT and FEES equals FEE | DISBURSEMENT_AMOUNT (NET_AMOUNT in the disbursement report) |
Step 1 is Snowflake’s own arithmetic: SUBTOTAL_AMOUNT is “Calculated as TOTAL_BILLED_AMOUNT - SALES_TAX_AMOUNT.” Step 2 is the expected-payout formula. Step 3 is the one that catches finance out, because the expected payout is not what arrives: it is what arrives plus the tax on the fee. Step 3 also rests on the assumption about GROSS and FEES, set out below.
A sample invoice across two report dates
The sample invoice comes from a private offer with two installments, so the invoice-status view returns it as two rows; Snowflake says its rows “are at line-item grain (one invoice can span multiple rows, for example installments).” Each installment was paid out on its own date. The installment schedule itself is set on the offer, as covered in installments on a Snowflake private offer. Every figure is sample data, and the fee and the tax on it are illustrative round figures, not Snowflake’s rates.
The invoice-status view, for sample invoice 7C1E40A2-0012:
| Column | Installment 1 | Installment 2 | Invoice total |
|---|---|---|---|
TOTAL_BILLED_AMOUNT | 12,990.00 | 12,990.00 | 25,980.00 |
SALES_TAX_AMOUNT | 990.00 | 990.00 | 1,980.00 |
SUBTOTAL_AMOUNT | 12,000.00 | 12,000.00 | 24,000.00 |
FEE | 1,000.00 | 1,000.00 | 2,000.00 |
EXPECTED_PAYOUT_AMOUNT | 11,000.00 | 11,000.00 | 22,000.00 |
PROVIDER_SALES_TAX_AMOUNT | 65.00 | 65.00 | 130.00 |
DISBURSEMENT_AMOUNT | 10,935.00 | 10,935.00 | 21,870.00 |
DISBURSEMENT_DATE | 2026-09-14 | 2026-10-15 | — |
The disbursement report, for the same invoice:
EVENT_DATE | STRIPE_DISPLAY_NUMBER | GROSS | FEES | TAXES | NET_AMOUNT |
|---|---|---|---|---|---|
| 2026-09-14 | 7C1E40A2-0012 | 12,000.00 | 1,000.00 | 65.00 | 10,935.00 |
| 2026-10-15 | 7C1E40A2-0012 | 12,000.00 | 1,000.00 | 65.00 | 10,935.00 |
On the invoice total the bridge closes: 25,980.00 less 1,980.00 of consumer tax is 24,000.00; less 2,000.00 of fee is the 22,000.00 expected; less 130.00 of tax on the fee is 21,870.00, the sum of the two NET_AMOUNT rows.
Two readings go wrong on this invoice. A September close that sets the invoice against September’s disbursement events sees 10,935.00 against an expected 22,000.00 and calls half the invoice unpaid, when the second installment simply hasn’t been paid out yet. Snowflake’s own example warns of this: “the invoice period could be spread out over multiple report dates.” And a close that sets expected payout against the disbursement sees a 130.00 shortfall that is the tax on the fee, owed, deducted and correct.
The GROSS assumption, and how to check it
The sample assumes the disbursement report’s GROSS equals the invoice’s SUBTOTAL_AMOUNT, the billed amount less the consumer’s tax, and Snowflake doesn’t say whether it does. Its definition, “Gross amount billed to the consumer,” reads either way. The two formulas agree only if GROSS leaves out the consumer’s sales tax and FEES equals FEE, so check your own data before you rely on step 3:
- For invoices that are fully disbursed, sum
SUBTOTAL_AMOUNTandFEEperINVOICE_NUMBERin the invoice-status view, andGROSSandFEESperSTRIPE_DISPLAY_NUMBERin the disbursement report. - If
GROSSmatchesSUBTOTAL_AMOUNTandFEESmatchesFEE, the bridge holds, and expected payout less disbursement should equalPROVIDER_SALES_TAX_AMOUNT. - If
GROSSmatchesTOTAL_BILLED_AMOUNTinstead, the disbursement includes an amount the expected payout left out, and the difference is the consumer’s sales tax. Don’t force the bridge: ask Snowflake which figure is right before you book either.
Why doesn’t the bridge close?
Check timing and grain before you suspect the money: the payout may not have reached the view yet, or one line item is being compared with a whole invoice. The causes below are ranked roughly by likelihood, cheapest checks first, so work down them in order:
| Cause | How to check | Fix |
|---|---|---|
| The invoice spans line items and report dates | The invoice has more than one row, INSTALLMENT_NUMBER is set, or the disbursement report shows it on more than one EVENT_DATE | Sum every row per invoice in both views before comparing, and compare only line items that are disbursed |
| The payout hasn’t reached the view | The payment fell in the last two days of the period | Re-run after the lag: up to 48 hours for the account-level disbursement report, up to 24 hours for the other two views |
| The join drops rows | Count the invoices in each view with no match in the other | The disbursement report has no INVOICE_NUMBER; match its STRIPE_DISPLAY_NUMBER to the invoice view’s INVOICE_NUMBER |
| The invoice was voided or replaced | INVOICE_STATUS is void or rebilled | Leave void rows out; find a rebilled invoice’s replacement, which carries a new invoice number |
| The invoice closed without payment | INVOICE_STATUS is closed, CONSUMER_PAID_IN_FULL_DATE is NULL, and BALANCE_AFTER_MCD isn’t 0 | Closed means “paid, credited, or written off”; a credited or written-off line may pay nothing, so check its disbursement before you count it short |
| Paid, not yet disbursed | DISBURSEMENT_STATUS is Not disbursed | Snowflake makes provider payouts “30 days after payment is received in full”; past that, raise it with Snowflake |
| The payout aged out | The payment event is more than 365 days old | Read DISBURSEMENT_DATE and DISBURSEMENT_AMOUNT from the invoice-status view, which keeps 7 years |
GROSS isn’t the subtotal | The check in the section above fails | Ask Snowflake; don’t force the bridge |
The closed-without-payment test follows Snowflake’s own cash-flow example, which counts a line as collected when CONSUMER_PAID_IN_FULL_DATE is set or Marketplace Capacity Drawdown covered the whole amount (BALANCE_AFTER_MCD = 0). A rebilled invoice is “replaced by a new invoice,” but no column points from the old invoice to the new one, so treat consumer account, listing and billing period as leads to the replacement, and confirm its invoice number before you reconcile against it.
MARKETPLACE_DISBURSEMENT_REPORT vs MARKETPLACE_LISTING_INVOICE_STATUS: which view to trust?
Trust the invoice-status view for what was billed and what to expect, the disbursement report for what was paid and when, and only the invoice-status view for anything older than a year. Snowflake publishes the disbursement report twice, once in each account’s Data Sharing Usage schema and once in Organization Usage for every account in the organization, and the three views differ in ways that set your close calendar:
| Disbursement report (Data Sharing Usage) | Disbursement report (Organization Usage) | Invoice-status view (Data Sharing Usage) | |
|---|---|---|---|
| Latency | Up to 48 hours | Up to 24 hours | Up to 24 hours |
| Retention | 365 days | 365 days | 7 years |
| One row per | Payment event | Payment event | Invoice line item |
| Invoice key | STRIPE_DISPLAY_NUMBER | STRIPE_DISPLAY_NUMBER | INVOICE_NUMBER |
| Only this view has | — | LISTING_OWNER_ACCOUNT_NAME, for several provider accounts | The consumer’s tax, EXPECTED_PAYOUT_AMOUNT, INVOICE_STATUS, DUE_DATE |
Then match each month-end question to the view that answers it:
| Month-end question | View | Columns |
|---|---|---|
| What did we bill, and what was the consumer’s tax? | Invoice status | TOTAL_BILLED_AMOUNT, SALES_TAX_AMOUNT |
| What should this invoice pay us? | Invoice status | EXPECTED_PAYOUT_AMOUNT less PROVIDER_SALES_TAX_AMOUNT, once the GROSS and FEES checks pass |
| What did Snowflake pay, and on which day? | Disbursement report | NET_AMOUNT by EVENT_DATE, where EVENT_TYPE is payment |
| What is still unpaid? | Invoice status | Open line items, by DUE_DATE: an aging list, not a balance |
| What was paid more than a year ago? | Invoice status | DISBURSEMENT_DATE, DISBURSEMENT_AMOUNT |
Four rules for the close follow from those two tables:
- Close on the third day of the month or later. The account-level disbursement report can lag up to 48 hours, so a payment on October 31 may not show until November 2.
- Keep your own history. Both disbursement reports keep 365 days. For older payouts, read the invoice-status view’s disbursement columns, or copy the disbursement report into a table you own each month.
- Don’t read
BALANCE_AFTER_MCDas what’s owed. In Snowflake’s words it “reflects MCD only. It doesn’t include other payments, so it isn’t the outstanding balance.” Work receivables from open line items instead. - Expect one currency. The invoice-status view’s currency is “Always USD,” and the disbursement report lists USD as its only value, so there is no exchange-rate step inside Snowflake’s numbers.
A monthly Snowflake Marketplace payout reconciliation query
Six steps, run on the third of the month or later, turn the two views into a close. In outline:
- Join on the invoice number. That is
INVOICE_NUMBERin the invoice-status view andSTRIPE_DISPLAY_NUMBERin the disbursement report, which Snowflake says have “the same value” today. Count unmatched invoices every month rather than assume it stays true. - Sum before you compare. Total every line item and every payment event per invoice; never compare one row with another.
- Flag the breaks. For each fully disbursed invoice, check that
GROSSequalsSUBTOTAL_AMOUNTandFEESequalsFEE; where both hold, expected payout less disbursement should equal the provider’s tax on fees. List every invoice where any of the three fails. - List paid invoices still waiting. Closed line items whose
CONSUMER_PAID_IN_FULL_DATEis more than 30 days old and whoseDISBURSEMENT_STATUSis stillNot disbursed. Snowflake makes provider payouts “30 days after payment is received in full,” so the clock starts at the paid-in-full date. A line paid with Marketplace Capacity Drawdown also waits until “the related capacity invoice” is paid in full, which neither view shows, so list lines with anMCD_APPLIED_AMOUNTseparately and ask Snowflake before you call one late. - Drop void, follow rebilled. Leave void invoices out, and recalculate a rebilled invoice’s expected payout from its replacement invoice rather than carrying the old figure over.
- Keep
BALANCE_AFTER_MCDout of receivables. It reflects Capacity drawdown only.
A sketch of steps 1 to 3, to adapt rather than run as is. It reads invoices from the last eleven months, because an invoice whose first payout has aged out of the disbursement report would look short:
-- Fully disbursed invoices where the bridge does not close
WITH inv AS (
SELECT invoice_number,
SUM(subtotal_amount) AS subtotal,
SUM(fee) AS fee,
SUM(expected_payout_amount) AS expected_payout,
SUM(provider_sales_tax_amount) AS tax_on_fee,
COUNT_IF(disbursement_status = 'Disbursed') = COUNT(*) AS fully_disbursed
FROM snowflake.data_sharing_usage.marketplace_listing_invoice_status
WHERE invoice_status = 'closed'
AND invoice_date >= DATEADD('month', -11, CURRENT_DATE())
GROUP BY invoice_number
),
paid AS (
SELECT stripe_display_number AS invoice_number,
SUM(gross) AS gross,
SUM(fees) AS fees,
SUM(net_amount) AS net_amount
FROM snowflake.data_sharing_usage.marketplace_disbursement_report
WHERE event_type = 'payment'
GROUP BY stripe_display_number
)
SELECT i.invoice_number,
i.subtotal, p.gross, i.fee, p.fees,
i.expected_payout, p.net_amount, i.tax_on_fee,
i.expected_payout - p.net_amount - i.tax_on_fee AS unexplained
FROM inv i
JOIN paid p ON p.invoice_number = i.invoice_number
WHERE i.fully_disbursed
AND (ABS(i.subtotal - p.gross) > 0.01
OR ABS(i.fee - p.fees) > 0.01
OR ABS(i.expected_payout - p.net_amount - i.tax_on_fee) > 0.01);
An empty result is the goal. A row with unexplained near zero but gross off from subtotal is the GROSS question above, not a missing payment.
How Fours records a Snowflake payout
Fours syncs both views and joins them by invoice number, so each Snowflake invoice becomes a revenue record that carries the invoice’s amounts and the payouts against it. In Fours’ documentation of Snowflake Marketplace revenue, the record’s fields map to Snowflake’s columns this way:
- Billed is
total_billed_amount. - Collectable is
expected_payout_amount: the billed amount less the consumer’s sales tax and Snowflake’s fee. - Tax is
sales_tax_amount, the consumer’s tax on the invoice. - Disburse amount is the sum of
net_amountacross the invoice’s disbursement events, and Disburse date is the latest event’s date. - Void invoices stay on the record for auditability, with their amounts zeroed.
The records are under Revenue → Revenue Records with the Channel filter set to Snowflake. Once both installments are paid out, the sample invoice’s record would read Billed 25,980.00, Tax 1,980.00, Collectable 22,000.00 and Disburse amount 21,870.00. When Collectable and Disburse amount differ on a fully paid Snowflake record, the provider’s tax on fees is the first place to look.
What Fours leaves to you: the record’s Tax is the consumer’s sales tax, not the tax on Snowflake’s fee, so the step 3 check and the GROSS check stay queries against Snowflake’s views. And Fours shows only what Snowflake has published; if an invoice or payout is missing, confirm it in your Snowflake account first.
What Snowflake’s pages leave open
Four things the three view pages don’t settle, each worth a check rather than an assumption:
- What
GROSSincludes. “Gross amount billed to the consumer” doesn’t say whether the consumer’s sales tax is in it, and the bridge depends on the answer. - Whether
FEEandFEESare one number. The invoice-status view’sFEEis “Provider fees owed to Snowflake”; the disbursement report’sFEESare “Pre-tax fees.” The bridge assumes they match. - How long the join key holds.
STRIPE_DISPLAY_NUMBERhas the same value asINVOICE_NUMBER“today,” and the disbursement report carries only the first. - Which invoice replaced a rebilled one. No column links the two.
If Snowflake is one of several marketplaces you sell through, why your marketplaces report different numbers covers how the others’ payouts differ and how to build a reconciliation that converges.
Sources
Primary sources for the platform rules cited above. Last verified November 6, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- Snowflake Documentation: MARKETPLACE_LISTING_INVOICE_STATUS view — Line-item grain (one invoice can span several rows, for example installments); EXPECTED_PAYOUT_AMOUNT calculated as TOTAL_BILLED_AMOUNT - SALES_TAX_AMOUNT - FEE; SUBTOTAL_AMOUNT as TOTAL_BILLED_AMOUNT - SALES_TAX_AMOUNT; PROVIDER_SALES_TAX_AMOUNT corresponding to TAXES and DISBURSEMENT_AMOUNT to NET_AMOUNT in the disbursement report; INVOICE_NUMBER as the join identifier, with STRIPE_DISPLAY_NUMBER a legacy column of the same value today; the open, closed, void and rebilled statuses and the 30-day disbursement of paid invoices; CONSUMER_PAID_IN_FULL_DATE, DISBURSEMENT_STATUS and DISBURSEMENT_DATE; BALANCE_AFTER_MCD not the outstanding balance; Always USD; latency up to 24 hours; retained 7 years
- Snowflake Documentation: MARKETPLACE_DISBURSEMENT_REPORT view (Data Sharing Usage) — NET_AMOUNT = GROSS - FEES - TAXES; GROSS as the gross amount billed to the consumer; FEES as pre-tax fees and TAXES as sales tax on the fees, both owed to Snowflake by the provider; STRIPE_DISPLAY_NUMBER, EVENT_DATE, EVENT_TYPE payment and CHARGE_TYPE; an invoice period spread over multiple report dates; latency up to 48 hours; retained 365 days
- Snowflake Documentation: MARKETPLACE_DISBURSEMENT_REPORT view (Organization Usage) — The same columns and NET_AMOUNT formula for all accounts in the organization, plus LISTING_OWNER_ACCOUNT_NAME; latency up to 24 hours; retained 365 days
- Snowflake Documentation: Snowflake Marketplace Provider Expectations for Transactions, Invoicing, and Collections — Snowflake Marketplace uses Stripe to process provider payouts, into a Stripe Express connected account; payouts are net of Snowflake fees, applicable taxes and any permitted adjustments; with Marketplace Capacity Drawdown the related capacity invoice must be paid in full before payout; provider payouts are made 30 days after payment is received in full
- Fours docs: Snowflake Marketplace Revenue — Fours behaviour: syncs MARKETPLACE_LISTING_INVOICE_STATUS and MARKETPLACE_DISBURSEMENT_REPORT and joins them by invoice number; Billed, Collectable, Tax, Disburse amount and Disburse date mapped to Snowflake’s columns; void invoices kept with amounts zeroed; Revenue Records with the Snowflake channel filter; Fours surfaces only what Snowflake has published
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn