Send Stripe payouts to Google Sheets
The finance team reconciles Stripe to the bank in a sheet. Stripe goes into your data warehouse first, where payouts are read next to refunds and disputes in the same currency, and only then reaches the sheet.
%20scale(1.25)%22%20fill%3D%22%23fff%22%20d%3D%22M13.976%209.15c-2.172-.806-3.356-1.426-3.356-2.409%200-.831.683-1.305%201.901-1.305%202.227%200%204.515.858%206.09%201.631l.89-5.494C18.252.975%2015.697%200%2012.165%200%209.667%200%207.589.654%206.104%201.872%204.56%203.147%203.757%204.992%203.757%207.218c0%204.039%202.467%205.76%206.476%207.219%202.585.92%203.445%201.574%203.445%202.583%200%20.98-.84%201.545-2.354%201.545-1.875%200-4.965-.921-6.99-2.109l-.9%205.555C5.175%2022.99%208.385%2024%2011.714%2024c2.641%200%204.843-.624%206.328-1.813%201.664-1.305%202.525-3.236%202.525-5.732%200-4.128-2.524-5.851-6.594-7.305h.003z%22%2F%3E%0A%3C%2Fsvg%3E%0A)
StripeConnectedBalance transact…ChargesCustomersDisputes
Google SheetsIdAccou…Livem…Daily 09:00Stripe Endpoints
14 Stripe endpoints you can import. Each lands in its own table in your data warehouse.
Balance transactions
Every movement of money through the Stripe balance: charges, refunds, disputes, fees, payouts, adjustments.
16 fieldsTime seriesCharges
One row per charge attempt: amount, outcome, card details, who paid and which invoice or payment intent it belongs to.
33 fieldsTime seriesCustomers
Every customer object: identity, billing country, delinquency and balance.
17 fieldsDisputes
One row per dispute (chargeback) with its status and evidence deadline.
14 fieldsTime seriesEvents
The audit trail: every change Stripe recorded (invoice.paid, customer.subscription.updated, charge.refunded, …) with the id of the object it concerns.
11 fieldsTime seriesInvoice line items
Every line on every invoice: what was billed, for which price and product, for which period.
19 fieldsInvoices
One row per invoice with amounts, status and period.
31 fieldsTime seriesPayment intents
One row per payment attempt lifecycle: how much was asked for, how much was received, and where it stands.
22 fieldsTime seriesPayouts
One row per transfer from the Stripe balance to the bank account: amount, arrival date, status.
18 fieldsTime seriesPrices
Every price (plan) of every product, active or not, with amount, currency and billing interval.
17 fieldsProducts
The catalogue: every product, active or not.
13 fieldsRefunds
One row per refund: how much was returned on which charge, why, and the balance transaction that reversed the money.
13 fieldsTime seriesSubscription items
The lines of every subscription: which price, how many units.
14 fieldsSubscriptions
One row per subscription in any status (status=all), full refresh every run so cancellations and past-due states are current.
23 fields
Why Stripe payouts do not go straight to Google Sheets
A payout is the number the bank shows. A sheet fed from the Stripe account has that total and nothing around it. Refunds and disputes for the same period and currency are read beside it in the warehouse first.
- A payout is a net figure for the bank, not a list of what it contains
- The data analyst joins payouts, refunds and disputes by currency and controls the result
- A sheet is shared widely, so every column needs one definition
StripePayouts, arrivalsGoogle Sheets
Data warehouseJoined by idStep 1: Load Stripe into your data warehouse first
Create a Data Mart with Stripe as the source and choose where the data lands. The Stripe connector is a custom connector built in OWOX Data Marts, and the data goes into any popular data warehouse.
- Payouts is one of 14 endpoints, each in its own table
- Authorize with a restricted Stripe API key that has read access
- Open the Stripe connector for your data warehouse below
StripeData MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksstripe.payoutsStep 2: Link Stripe payouts to refunds and disputes
In your data warehouse the model joins Payouts, Refunds and Disputes on currency, so each payout can be read by arrival date beside the refunds and disputes in the same currency.
- Payouts, refunds and disputes share the currency
- arrival_date is the cash date the bank will show
- The finance close and the sheet read the same payouts
Step 3: Send Stripe data to Google Sheets
Connect a Sheets report to the Stripe Data Mart. Aliases and field descriptions arrive as notes in the column headers, so everyone reads the same definitions.
- The sheet reads your data warehouse, not the Stripe API
- Hover amount: the note says it is in the smallest currency unit, cents for USD
Google SheetsNotes in headersarrival_dateamountcurrencyStep 4: Refresh your Stripe sheet on a schedule
Set a scheduled refresh once. Daily is the usual choice and hourly is possible when you need it.
- Every refresh is logged in Run History
- Finance opens a sheet that is already up to date
Google SheetsUpdatedStep 5: Reuse Stripe payouts in other reports
The same Data Mart works in OWOX, where your assistant for data can read it. Ask about any report, then get the result in Google Sheets or Excel in one click.
- Ask which arrival date had the largest payout, then export the answer
- status is kept with every payout
Google SheetsOpen
ExcelOpen
- 0.41.0Dates from Google Sheets arrive as dates, not text
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.41.0Reuse one Google Sheets or Google Chat key across Destinations
- 0.40.0Connecting a plan from Google Sheets takes fewer guesses
- 0.40.0Warnings when a Count reads a joined Data Mart
Why OWOX for Stripe in Google Sheets
Downloading payout reports from the Stripe dashboard gives a file per period. OWOX gives a sheet that stays tied to payouts in your data warehouse.
- You own the data. Stripe lands in your own data warehouse, in tables you control.
- Payouts beside returns. Payouts sit next to refunds and disputes in the same currency, so a bank line has context.
- The whole account, not one report. 14 endpoints land as tables, from balance transactions to subscriptions.
- Notes in the headers. Field descriptions travel with the column, so the sheet defines its own terms.
- One place to fix. When Stripe changes its API, you update the connector, not your sheet.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.