Skip to content

What moved ARR this month, and does it tie to billing?

Build June's ARR roll-forward from Stripe and check it against Salesforce and NetSuite. See new, expansion, contraction and churn by customer, with billing corrections pulled out before the number goes to the board.

Open Querri

What you'll need

Querri (Free trial) to join the exports and build the roll-forward

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

Your ARR rules: so every month is measured the same way

Free resources

Start your free trial here →

Sample data sets

Synthetic data for a made-up software company. Not real customer data.

Need help?

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

Before we begin

Every month someone in finance signs the ARR number, and every month someone asks why the CRM, the billing system and the board deck show three different figures. Most of the gap isn't lost revenue; it's timing and clean-up. A seat count fixed two days after month end looks like a downgrade, and a cancellation on the 30th isn't in the CRM yet. Sorting that out by hand takes a day of spreadsheets.

This playbook builds the roll-forward from billing, pulls the corrections out, and ties the result to Salesforce and NetSuite.

How it works:

  • • Upload Stripe, Salesforce and NetSuite
  • • Build June's roll-forward from billing
  • • Take billing corrections out of contraction
  • • Tie billing ARR to the CRM and the ledger
  • • Produce the board ARR page

Follow the steps

Open Querri →
1 Step 1:

Upload Stripe, Salesforce and NetSuite

Three exports, one project:

  • •

    Stripe subscription change events (or Maxio, Chargebee): every start, seat change and cancellation, with its MRR.

  • •

    Salesforce (or HubSpot): the ARR field, seats and owner for every account.

  • •

    NetSuite (or QuickBooks): subscription revenue by customer and month.

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

Tip: Pull the change events from the first subscription, not just this year, so every customer has an opening balance.

  • Stripe change events
  • Salesforce accounts
  • NetSuite revenue
Querri One project
2 Step 2:

Build June's roll-forward from billing

Take each subscription's MRR at the start and end of the month, and sort every change:

Prompt

"Build June's ARR roll-forward from the Stripe change events: opening, new, expansion, contraction, churn and closing, with customer counts. Then NRR and GRR for the trailing 12 months."

New customers added $2.39M. Contraction and churn took out $417K, more than ten times expansion. Trailing 12-month NRR comes out at 99.9%.

Build June's roll-forward from billing
LineCustomersARR
Opening ARR, May 31$21,677,189
New45+$2,386,570
Expansion6+$37,331
Contraction20-$204,893
Churn9-$212,200
Closing ARR, June 30$23,683,997

June 2026 ARR roll-forward, as billing reports it.

3 Step 3:

Take billing corrections out of contraction

Find seat reductions that came back within 60 days, and give them their own line for finance to confirm:

Prompt

"List every seat reduction that was reversed within 60 days. Which ones sit inside June's roll-forward, how much of June's contraction are they, and what are NRR and GRR without them?"

Six customers lost seats on June 29 or 30 and got them back by July 3. That's 68% of June's contraction, and NRR moves from 99.9% to 102.5%.

Take billing corrections out of contraction
MeasureAs reportedCorrections out
Contraction$204,893$65,035
Closing ARR$23,683,997$23,823,855
NRR, trailing 12 months99.9%102.5%
GRR, trailing 12 months93.1%95.4%

June with and without the six billing corrections.

4 Step 4:

Tie billing ARR to the CRM and the ledger

Match every account to Salesforce, check June against NetSuite, and give each gap a reason:

Prompt

"Compare billing ARR with the Salesforce ARR field account by account, and June MRR with NetSuite subscription revenue. List the accounts more than 2% apart with a reason for each."

Salesforce is $675,967 higher on 47 accounts. Some of it is timing, and some is seats or prices billing never picked up, so each one needs a look. For customers with no change in June, the ledger ties within 1.5% in total.

Tie billing ARR to the CRM and the ledger
ReasonAccountsCRM higher by
Cancelled or cut seats on June 29 or 3023$277,234
No subscription billing yet4$229,000
Fewer seats in Stripe13$106,623
Lower price in Stripe7$63,110

The gap between Salesforce and billing ARR, by reason.

5 Step 5:

Produce the board ARR page

Four numbers for the board pack, and the accounts to fix before it goes out.

The narrative Querri writes:

Adjusted closing ARR is $23.82M once six end-of-quarter seat corrections are confirmed and put back.

What you can create or export:

Produce the board ARR page
AccountSalesforce ARRWhy billing ARR is $0
Yu, Davidson and Leonard$86,000Billing starts in July
Williams and Sons$62,000Not billing yet
Wilson and Sons$55,500Billing starts in July
Lopez, Hernandez and Morris$31,900Cancelled June 30

The four largest gaps. Billing ARR on June 30 is $0 for each.

Sign the ARR number knowing what moved it and where it ties.

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 an ARR number the board can trust

Treat billing as the source

The CRM records what was sold; billing records what is charged. Build ARR from billing and use the CRM field as the check.

Look at the last days of the month

Seat clean-ups and cancellations bunch up at quarter end. A reduction reversed a few days later is probably a correction, not a downgrade; confirm it before adding it back.

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

What ARR means, when a reduction is a correction, how NRR is measured: 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 billing correction is a seat reduction reversed within 60 days. Report corrections on their own line, not as contraction. Save that as a rule for the Stripe change events table."

Or bring the document that already says it

Upload your revenue policy or board metrics definitions 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:

  • ARR: MRR on the last day of the month, times 12
  • New and churn: customers with no ARR at one end of the month
  • Expansion and contraction: the change for everyone else
  • Billing correction: a seat reduction reversed within 60 days, confirmed by finance
  • NRR and GRR: the customers who had ARR 12 months ago
  • CRM tie: billing ARR within 2% of the Salesforce field
  • Ledger tie: June MRR within 2% of June subscription revenue
Prompt

"Read our board metrics definitions and propose the rules they state for ARR, NRR and GRR. 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

One ARR number, a roll-forward that adds up, and an answer ready for why the CRM says something else.

Frequently asked questions

Where does ARR come from here?
From billing. Every subscription start, seat change and cancellation in Stripe carries its MRR after discounts, so ARR on any date is the latest MRR of each subscription times 12. The Salesforce ARR field is checked against it, not the other way round.
What counts as new, expansion, contraction and churn?
New is ARR from customers who had none at the start of the month. Churn is the ARR of customers who have none at the end. Expansion and contraction are the change for customers with ARR at both ends, split by sign.
What is a billing correction?
A seat reduction that is reversed within 60 days: the same subscription gets the same seats back. It shows up as contraction in a month-end snapshot, so it gets its own line, and finance confirms it was a correction, not a real downgrade followed by a new purchase, before adding it back. In June, six of them made up $139,858 of the $204,893 contraction.
How are NRR and GRR measured?
On the customers who had ARR 12 months ago. NRR is their ARR today divided by their ARR then. GRR is the same, but no customer counts above its starting ARR, so expansion can't hide losses.
Why doesn't Salesforce match billing?
Here the CRM is $675,967 higher on the 47 accounts that don't tie, for four reasons: cancellations and seat cuts on June 29 and 30 not yet in the CRM, deals that aren't billing yet, expansions booked but not added in Stripe, and discounts agreed outside the CRM. Some of that is timing; some is seats or prices that billing never picked up, so each account needs a look.
Why compare with NetSuite revenue?
Recognized revenue is the ledger's view of the same subscriptions. It isn't ARR, so the tie is June MRR against June subscription revenue for customers with no change in the month, within 2%. Here the total for those customers is within 1.5%. Account by account, 53 are more than 2% apart, so they get their own review list.
What if a customer has no Salesforce ID in Stripe?
The prompt matches on the ID first, and on the customer name where the ID is blank, ignoring a suffix like Inc or LLC. Four Stripe customers here have no ID; matched by name, they tie.
Which number goes to the board?
Adjusted closing ARR, $23.82M: closing ARR with the six corrections added back once finance confirms them, shown on their own line so anyone can see what changed. The accounts that don't tie go to their owners to fix in Salesforce.
How often should this run?
Monthly, after the books close, on a schedule. A correction made in the last days of a month is caught before the board pack, not a quarter later.