Skip to content

Which customers are paying late, and how long will our cash last?

Join Stripe invoices, NetSuite cash, Salesforce renewal dates and your budget. See who pays late and how late, then run your cash runway as invoiced and as customers actually pay.

Open Querri

What you'll need

Querri (Free trial) to join the exports and run the forecast

Stripe, NetSuite, Salesforce and budget exports: Step 1 says what each adds

Your forecast rules: so both runways are built the same way

Need help?

If you have any questions, you can request a demo or email our team.

Before we begin

Every board meeting comes back to the same question: how long will the cash last? Most runway models assume customers pay on the due date, because that's what the billing schedule says. Some customers pay weeks late, every time, and the model never hears about it. The invoices are in Stripe, the cash in NetSuite and the spending plan in a workbook, so building the honest version means rebuilding the model by hand.

This playbook finds who pays late and how late, forecasts collections the way customers actually pay, and runs the runway both ways.

How it works:

  • • Upload Stripe, NetSuite, Salesforce and the budget
  • • Find who pays late, and how late
  • • Forecast collections as customers pay
  • • Run the cash runway two ways
  • • Build the call list for the week

Follow the steps

Open Querri →
1 Step 1:

Upload NetSuite, Stripe, Salesforce and the budget

Four exports, one project:

  • •

    Stripe invoices (or Maxio, Chargebee): every invoice with its due date, paid date and failed attempts.

  • •

    NetSuite (or QuickBooks): the cash balance at month end.

  • •

    Salesforce (or HubSpot): renewal dates and the owner of each account.

  • •

    Budget workbook (Excel): planned spending by month.

Add your forecast rules in a small sheet, so it's easy to change. Prefer live data? Querri connects to NetSuite, Stripe and Salesforce directly.

Tip: Pull at least a year of invoices, so every annual customer has paid at least once.

  • Stripe invoices
  • NetSuite cash
  • Salesforce accounts
  • Budget workbook
Querri One project
2 Step 2:

Find who pays late, and how late

Age the overdue invoices, and give every customer a lateness from its own history:

Prompt

"Show overdue invoices by age and by customer, and each customer's median days past due on the invoices they've paid since January 2025. How do failed card payments recover?"

Five customers hold 69% of the overdue money, and each has a history of paying late. 71 of 84 failed card invoices were collected within two weeks; 13 never were.

Find who pays late, and how late
Days past dueInvoicesOverdue
1 to 3013$317,118
31 to 602$61,515
Over 600$0
Total15$378,633

Overdue invoices on July 5, 2026, by days past due.

3 Step 3:

Forecast collections the way customers actually pay

Schedule every open and repeating invoice twice: on its due date, and on its due date plus the customer's lateness:

Prompt

"Forecast collections for July to December from open invoices and the last 12 months of invoices repeated a year later: once on the due date, and once on the due date plus each customer's usual lateness."

As customers actually pay, July to December brings in $377K less than the invoice schedule says. The money doesn't vanish; it arrives later.

Forecast collections the way customers actually pay
MonthAs invoicedAs they pay
July 2026$2,983,661$2,472,565
August 2026$1,152,057$1,112,406
September 2026$952,016$1,112,207
July to December$9,796,949$9,419,697

Expected collections, as invoiced and as customers pay.

4 Step 4:

Run the cash runway two ways

Start from the NetSuite cash balance and spend the budget, month by month, both ways:

Prompt

"Start from June's cash in NetSuite, add collections both ways and subtract the budget, held at December's level after that. Show cash at the end of September and the month cash runs out, both ways."

Paying late costs $390,555 of cash by the end of September and brings the month cash runs out forward from September to August 2027.

Run the cash runway two ways
MeasureAs invoicedAs they pay
Cash at end of September 2026$11,682,755$11,292,200
Cash falls below zeroSeptember 2027August 2027
Runway15 months14 months

Cash runway from $15,568,406 on June 30, 2026.

5 Step 5:

Produce the cash review

Four numbers for the board pack, and a call list for the week.

The narrative Querri writes:

A few customers who habitually pay late hold most of the overdue money, and their habits cost a month of runway.

What you can create or export:

Produce the cash review
CustomerOverdueUsually pays
Dalton PLC$68,47262 days late
Bauer, Hendricks and Hamilton$60,40043 days late
Jacobson-Brown$45,40028 days late
Chambers-Hill LLC$42,90023 days late

The four largest overdue invoices on the call list.

Answer the runway question the way your customers actually pay.

Try it on your own data
Querri for SaaS finance See how Querri helps finance teams bring actuals, budget and billing together. See Querri for finance

Tips for a cash forecast the board can trust

Forecast from history, not terms

Net 30 is what the contract says. Each customer's own median days late is what the bank account will see, so schedule collections with it.

Show both runways

As invoiced is the plan and as they pay is the evidence. Put them side by side and the gap becomes a collections target, not a surprise.

Teach Querri your rules once. Every answer after that follows them.

What counts as overdue, how lateness is measured, what spending to assume: say each rule once and Querri applies it to every question on that data.

Show me how

Say it in chat

Settle a rule in conversation and the Librarian records it as a fact under Facts & Rules, attached to the table it governs. Every later question on that data applies it, whoever asks, and every view built afterwards carries it.

Prompt

"A customer's lateness is the median days past due on its paid invoices since January 2025, with early payments counted as zero. Save that as a rule for the Stripe invoices table."

Or bring the document that already says it

Upload your collections policy or month-end close checklist like any other file. Querri files a From a document card in the Inbox with the statements it found, each with its page and exact words; tick the ones to keep and they become facts. The rules this playbook depends on:

  • Overdue: an open invoice past its due date
  • Days past due: paid date minus due date, early counts as zero
  • Lateness: a customer's median days past due since January 2025
  • Future billing: the last 12 months of invoices, repeated each year
  • As they pay: due date plus the customer's lateness
  • Spending: the FY2026 budget, held at December after that
  • Runway: months from July 2026 until cash falls below zero
Prompt

"Read our collections policy and propose the rules it states about payment terms, dunning and when an account goes on hold. I'll review them in the Inbox."

Where the rules reach

A rule is attached to the data, not to one person's chat, so it follows the data everywhere:

  • • Every question asked in chat, by anyone on the team
  • • Every view the Librarian builds on that data
  • • Every step of a project, including the code it writes
  • • Dashboards and scheduled runs, each time they refresh
  • • Claude and ChatGPT, when they ask Querri

You stay in control

Every rule is listed under Facts & Rules next to the data it governs, where you can edit or remove it. Rules from a document wait for your tick in the Inbox, and a Worth remembering card is how Querri offers one it noticed itself. Workspaces and roles decide who can change what. Company-wide rules go in Settings → Customize; the Library is where the rest lives.

The payoff at the board meeting

The runway question gets two honest answers and a list of the calls that close the gap. Changing the spending assumption is a sentence.

Frequently asked questions

What counts as overdue?
An open invoice past its due date on the day the exports were pulled. Here that's 15 invoices and $378,633, and $369,534 of it is on customers who pay by invoice rather than card.
How is a customer's lateness measured?
The median number of days past due on the invoices they've paid since January 2025, with early payments counted as zero. Customers with no paid invoice get the company median, and card customers count as on time because Stripe charges them.
Do failed card payments hurt cash?
Less than they seem to. 84 card invoices failed at least once; 71 were collected on Stripe's retries, all within 14 days. The 13 never collected came to $26,993. The money that moves cash is annual invoices paid weeks late.
What does as they pay mean?
Each invoice expected on its due date plus that customer's usual lateness, instead of on the due date. It's the same money arriving later, so it changes when cash comes in, not how much.
Which is the right runway number?
Both are worth showing. As invoiced is the plan; as they pay is what the payment history says will happen. Here they differ by $390,555 at the end of September and by one month of runway.
How far ahead does the forecast look?
Through December 2027. Open invoices are collected once, and every invoice from the last 12 months recurs a year later and again the year after, so nothing is counted twice. It leaves out new customers and churn on purpose, and replays last year's bills at last year's prices, so read the runway as a scenario built on the current book, not a promise.
What spending does the runway use?
The FY2026 budget for July to December, then each month held at December's budget. The rules sheet says so, and changing it is a sentence.
Who should get a call this week?
Customers with an overdue invoice, and customers who usually pay 30 days late with an invoice due this quarter. The list gives the account owner, the amount and how late they usually are, so the call starts with the facts.
How often should this run?
Monthly, after the books close, on a schedule, and weekly for the call list. A customer whose lateness changes shows up the month it happens.