Check whether expected Stripe payments cover the next four weeks of spending.
Put Stripe payouts on their way and open invoices next to the payments your team has planned in Google Sheets. See which week gets closest to your cash buffer, which single invoice it depends on and which overdue or failing payments are not safe to count.
Bank balance Nov 15 · Weeks Nov 16–Dec 13 · Stripe read Nov 15, 12:00 UTC
Over the next four weeks, $54,420 is expected from Stripe payouts and open invoices against $74,900 of planned payments. Cash stays above the $25,000 buffer every week, but the payroll week of Nov 30 ends only $4,020 above it and relies on Halcyon Partners paying $18,000 on time. Another $13,200 is overdue or failing and is not counted.
WHERE THE RESULT GOES
Google Sheets
Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.
Example use case
Ask. Follow up. Take the next step.
✦ AI assistantSample use case
YOU
Will our invoiced cash cover the next four weeks?
✦
Over the next four weeks, $54,420 is expected from Stripe payouts and open invoices against $74,900 of planned payments. Cash stays above the $25,000 buffer every week, but the payroll week of Nov 30 ends only $4,020 above it and relies on Halcyon Partners paying $18,000 on time. Another $13,200 is overdue or failing and is not counted.
01
Nov 30–Dec 6 · $4,020 above the bufferPayroll and rent week · Ends at $29,020 · Depends on invoice NW-2090Confirm this payment
This week pays $44,900, including $38,000 of payroll on Nov 30. The only money expected in is Halcyon Partners’ $18,000 invoice, due Nov 28 and counted as reaching the bank on Dec 1 after the Sheet’s 3-day payout lag. If that payment slips by a week, the balance after payroll falls to $11,020, $13,980 below the buffer.
NextAsk the account owner to confirm Halcyon’s payment date this week. If it is not confirmed by Nov 25, the finance lead and founder decide together. In this example, collecting the two overdue invoices ($10,800) and moving the $6,000 ad budget marked as movable in the Sheet would bring the week back to $27,820, above the buffer.
02
3 invoices · $13,200 not countedOakridge Supply · Fenwick Studio · Juniper HealthChase now
Oakridge Supply’s $7,200 invoice is 16 days past due and Fenwick Studio’s $3,600 is 3 days past due. Juniper Health’s $2,400 renewal is charged automatically, but two payment attempts have already failed and Stripe will retry on Nov 20. None of these is in the weekly totals.
NextSend the two overdue invoices to their account owners for a reminder today, and ask Juniper Health to update its card before the next retry. Each payment that arrives adds headroom to every week from the date it lands.
03
Left out of the plan · Shown separately€5,000 in EUR · $3,600 draft · Renewals not yet invoicedDecide how to treat
Kestrel Tours owes €5,000, but the cash plan is kept in USD and the example does not convert currencies. Saltmarsh Coffee’s $3,600 invoice is still a draft, so the customer has not received it. Subscription renewals that Stripe has not invoiced yet are not in this read at all.
NextFinance decides whether the EUR payment belongs in the plan and at which rate, and whether the draft should be sent this week. Add expected renewals to the Sheet yourself if you want them counted.
Bank balance Nov 15 · Weeks Nov 16–Dec 13 · Stripe read Nov 15, 12:00 UTC
01 · CONNECT YOUR DATA
Your tools. One place to ask.
2 of 3 Free data sources No credit card · Daily refresh
DatapipeYour project
✦Your AI assistantor a report in Sheets / Data Studio
Create your free workspace
Sign up with your company email. Your first project opens on Data sources.
Add the data sources
Choose the accounts for this use case. Authorize access and select the property or site.
Bring your question
Connect your project to a supported AI assistant, or build your source reports.
Email/password signups confirm their email first. Use Google signup with a company account if you prefer.
Stripe: Authorize the intended Stripe account using its supported sign-in or dedicated read-key setup. Setup guide ↗
Google Sheets: Authorize Google Sheets with an account that can open the file, then paste the spreadsheet link and select the intended tab and columns. Setup guide ↗
Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.
02 · ASK A USEFUL QUESTION
Start with a prompt. Follow the evidence.
Copy these in order into your connected assistant. Each builds on the answer before it.
01
Read our cash plan and confirm its assumptions
Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.
From the connected Google Sheet, find the tab that holds our cash plan and show me its headers. Return the bank balance and the date it was taken, the minimum cash buffer, the days we allow between a customer paying and the money reaching our bank, and every planned payment with date, label, amount, currency and whether it can move. Group the payments into Monday-to-Sunday weeks for the next four weeks and total each week. Flag rows with no date, no amount, a currency other than the plan’s, or dates before the balance date. If a header differs from what you expect, ask me how to map it rather than guessing. This Sheet is the plan our team maintains, not an export.
02
Find the Stripe money that can arrive in those weeks
Read the full prompt
From the connected Stripe account, read the invoice resource for a 120-day creation window ending today in UTC and show the boundaries. Return invoice.id, invoice.number, invoice.customer_name, invoice.created, invoice.status, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.collection_method, invoice.attempt_count and invoice.next_payment_attempt. Then, as a separate read, return payout.id, payout.amount, payout.currency, payout.status, payout.created and payout.arrival_date for the last 14 days. Convert amounts from the smallest currency unit and timestamps to UTC dates. Tell me if any open invoice was created on the first day of the window, because older unpaid invoices may be missing. Do not add amounts across currencies.
03
Prepare the four-week cash view
Read the full prompt
Using the Sheet’s balance, buffer and payout lag, build a table for the next four weeks with cash in, planned out, ending balance and the difference from the buffer. Count pending and in_transit payouts on their arrival date. Count open invoices that are not yet due on their due date plus the payout lag. List separately, and leave out of the totals: past-due invoices with days overdue, automatic charges with failed attempts and their next retry, drafts, voided or uncollectible invoices, and any currency other than the plan’s. For the week with the least headroom, name the invoices it depends on and show the ending balance if the largest one arrives a week late. Mark which planned payments the Sheet says can move. Draft this in our conversation; do not send reminders, change invoices or edit the Sheet.
Build the weekly view, then review the tight week.
01
Read the cash plan your team keeps in Google Sheets.
02
Read open invoices and payouts on their way from Stripe.
03
Build the weekly view, then review the tight week.
↗
Check the result at your next review.
At the next weekly review, read both sources again. Compare what actually reached the bank with this week’s $14,920 expected, check whether Halcyon Partners confirmed or paid, and see how much of the $13,200 at-risk list has been collected. Then roll the plan forward a week and look at the new tightest week.
Implementation tips for this use case
Count pending and in_transit payouts on their arrival_date; paid payouts are already in the bank balance. Count open invoices that are not yet due on their due date plus your payout lag. Keep past-due invoices and automatic charges with failed attempts in a separate at-risk list, and keep drafts, voided invoices and other currencies out of the totals. Subtract each week’s planned payments and compare the ending balance with the buffer. Take the tight week and the at-risk list to the finance review, where the account owners confirm payment dates and the founder decides whether to move any payment.
WHEN YOU NEED MORE CONTEXT
Go a little deeper.
The method and reporting checks behind this example.
How to check whether Stripe collections cover the cash plan in Google Sheets
Read the cash plan your team keeps in Google Sheets.
Add the Stripe account you bill from and the Google Sheet with your cash plan to one project. Discover the actual tab and headers. The example tab has one row per line, with line_type, date, label, amount, currency and can_move: the bank balance and its date, the minimum cash buffer, the number of days your team expects between a customer paying and the money reaching the bank, and every planned payment with its date. These are inputs your team owns; Stripe does not know about payroll, rent or contractors.
Read open invoices and payouts on their way from Stripe.
Read the invoice resource with invoice.id, invoice.number, invoice.customer_name, invoice.created, invoice.status, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.collection_method, invoice.attempt_count and invoice.next_payment_attempt for a creation window that reaches back to your oldest unpaid invoice. Then read the payout resource with payout.id, payout.amount, payout.currency, payout.status, payout.created and payout.arrival_date for the last two weeks. Stripe reads one resource per report and filters by creation date in UTC. Amounts are in the smallest currency unit, so divide USD by 100. The example reads invoices created Jul 19–Nov 15 and payouts created Nov 2–15.
Build the weekly view, then review the tight week.
Count pending and in_transit payouts on their arrival_date; paid payouts are already in the bank balance. Count open invoices that are not yet due on their due date plus your payout lag. Keep past-due invoices and automatic charges with failed attempts in a separate at-risk list, and keep drafts, voided invoices and other currencies out of the totals. Subtract each week’s planned payments and compare the ending balance with the buffer. Take the tight week and the at-risk list to the finance review, where the account owners confirm payment dates and the founder decides whether to move any payment.
See the complete example report
EXAMPLE REPORT
Will our invoiced cash cover the next four weeks?
Bank balance Nov 15 · Weeks Nov 16–Dec 13 · Stripe read Nov 15, 12:00 UTC
Will our invoiced cash cover the next four weeks?
Week
Cash in
Planned out
Ending cash
Nov 16–29
$24,420
$16,500
$55,920
Nov 30–Dec 6
$18,000
$44,900
$29,020
Dec 7–13
$12,000
$13,500
$27,520
WHAT TO LOOK ATOver the next four weeks, $54,420 is expected from Stripe payouts and open invoices against $74,900 of planned payments. Cash stays above the $25,000 buffer every week, but the payroll week of Nov 30 ends only $4,020 above it and relies on Halcyon Partners paying $18,000 on time. Another $13,200 is overdue or failing and is not counted.
Build the weekly view, then review the tight week.
This week pays $44,900, including $38,000 of payroll on Nov 30. The only money expected in is Halcyon Partners’ $18,000 invoice, due Nov 28 and counted as reaching the bank on Dec 1 after the Sheet’s 3-day payout lag. If that payment slips by a week, the balance after payroll falls to $11,020, $13,980 below the buffer. Oakridge Supply’s $7,200 invoice is 16 days past due and Fenwick Studio’s $3,600 is 3 days past due. Juniper Health’s $2,400 renewal is charged automatically, but two payment attempts have already failed and Stripe will retry on Nov 20. None of these is in the weekly totals. Kestrel Tours owes €5,000, but the cash plan is kept in USD and the example does not convert currencies. Saltmarsh Coffee’s $3,600 invoice is still a draft, so the customer has not received it. Subscription renewals that Stripe has not invoiced yet are not in this read at all.
Try the example with sample CSVs
Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.
Data method, reporting checks & sources
Add the Stripe account you bill from and the Google Sheet with your cash plan to one project. Discover the actual tab and headers. The example tab has one row per line, with line_type, date, label, amount, currency and can_move: the bank balance and its date, the minimum cash buffer, the number of days your team expects between a customer paying and the money reaching the bank, and every planned payment with its date. These are inputs your team owns; Stripe does not know about payroll, rent or contractors. Read the invoice resource with invoice.id, invoice.number, invoice.customer_name, invoice.created, invoice.status, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.collection_method, invoice.attempt_count and invoice.next_payment_attempt for a creation window that reaches back to your oldest unpaid invoice. Then read the payout resource with payout.id, payout.amount, payout.currency, payout.status, payout.created and payout.arrival_date for the last two weeks. Stripe reads one resource per report and filters by creation date in UTC. Amounts are in the smallest currency unit, so divide USD by 100. The example reads invoices created Jul 19–Nov 15 and payouts created Nov 2–15. Count pending and in_transit payouts on their arrival_date; paid payouts are already in the bank balance. Count open invoices that are not yet due on their due date plus your payout lag. Keep past-due invoices and automatic charges with failed attempts in a separate at-risk list, and keep drafts, voided invoices and other currencies out of the totals. Subtract each week’s planned payments and compare the ending balance with the buffer. Take the tight week and the at-risk list to the finance review, where the account owners confirm payment dates and the founder decides whether to move any payment.
Paid payouts are already in the bank balance, so only pending and in_transit payouts are counted, on their arrival date. Past-due invoices and automatic charges with failed attempts are listed as at risk and kept out of the weekly totals. Stripe amounts are converted from the smallest currency unit, and EUR is never added to a USD plan. Invoices are selected by creation date in UTC, so the window has to reach back to the oldest unpaid invoice.
Paid payouts are already in the bank balance, so only pending and in_transit payouts are counted, on their arrival date.
Past-due invoices and automatic charges with failed attempts are listed as at risk and kept out of the weekly totals.
Stripe amounts are converted from the smallest currency unit, and EUR is never added to a USD plan.
Invoices are selected by creation date in UTC, so the window has to reach back to the oldest unpaid invoice.
Access to the intended Stripe account or property.
Access to the intended Google Sheets account or property.
Paid payouts are already in the bank balance, so only pending and in_transit payouts are counted, on their arrival date.
For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.
Stripe knows what customers owe, when invoices are due and when payouts reach your bank. It knows nothing about payroll, rent or contractor payments. Your cash plan holds those, plus the balance and buffer your team works to. Only together do they show whether a particular week is covered.
Why are paid payouts left out?
A paid payout is already in your bank account, so it is part of the balance you enter in the Sheet. Counting it again would overstate cash. Check that the balance date in the Sheet is after the arrival date of the last paid payout.
Why add a payout lag to invoice due dates?
When a customer pays an invoice, the money first lands in your Stripe balance and reaches your bank with a later payout. The lag in the example is the team’s own estimate from its payout schedule; set yours from your Stripe payout settings. Pending and in-transit payouts already have an expected arrival date, so no lag is added to them.
Are failed or overdue payments ever counted?
Not in the weekly totals. They are listed with how late they are or when Stripe will retry, so the team can chase them. When one is paid, it shows up in the next read as a payout.
Does this include subscription renewals?
Only renewals Stripe has already invoiced. Upcoming renewals without an invoice are not in this read. Add them to your Sheet as expected income if you want them in the plan.
Does the assistant send reminders or move payments?
No. It prepares the weekly view and the at-risk list in your conversation. Account owners contact customers, and the finance lead decides whether a planned payment moves.
YOUR NEXT STEP
Try it with your own data.
Start free with up to 3 data sources. No credit card.