The renewal was signed in April: Growth to Scale, eight seats to ten, $48K to $60K a year. The order form is countersigned and filed. The deal record reads $60,000. Commission was paid on the expansion.
This month’s Stripe invoice is $4,000. It was $4,000 in May, and June, and every month since. The subscription item still points at the Growth annual price with a quantity of 8.
Nobody made a visible error. Sales updated the contract. Billing has a live subscription and a customer who pays on time. Both systems are internally consistent, and both are wrong about the same account.
That is the shape of every unbilled upgrade: not a missing invoice, but a price that was supposed to change and did not, on a subscription that keeps working perfectly at the old number.
An upgrade is a contract change in one system and a billing change in another
Two records have to end up matching. On the CRM side there is an amount: the deal amount, the line items, the contract value against the account. On the billing side there is a subscription item, and that item is not an amount at all. It is a pointer to a price ID plus a quantity.
Nothing carries one to the other. HubSpot’s documentation is direct about the boundary: once Stripe is connected as a payment processor, invoices and subscriptions created in HubSpot are not created in Stripe, and existing Stripe subscriptions stay managed in Stripe. The CRM records what was agreed. Stripe records what will be charged. An upgrade writes to both, and only one of those writes happens on its own.
In Stripe, a price change is three writes, and two of them are easy to skip
Stripe’s documentation puts the constraint plainly: a price’s amount cannot be changed through the API. To move a subscription to a new amount you create a new price, point the subscription item at it, and deactivate the old price. Three objects, three steps, and any one of them can be missed at 6pm on the last day of the quarter.
The same documentation flags two failure modes worth knowing by name, because they are the half-applied states you are looking for.
- The item is not named, so the new price is added. Updating a subscription with a new price without passing the subscription item ID adds a new item, per Stripe, so both prices are active. Nothing looks broken. The invoice adds the two together, and every report reading the top-line amount is wrong by the size of the old plan.
- The quantity is not passed, so it resets. Stripe notes that updating a subscription price reverts the quantity to the default of 1. An account at ten seats can come out of a plan change at one, and the next invoice is smaller than the contract instead of larger.
Both are the same defect class: a change that returned 200 and did not produce the subscription the contract describes.
The proration default parks the new amount until the next invoice
Prorations are where the timing hides. Stripe’s default behavior creates proration items, and by Stripe’s documentation those items are only invoiced immediately under certain conditions. Turn prorations off to avoid a surprise mid-cycle charge, and the current invoice does not move at all: the customer is billed the full amount at the new price when the next invoice is generated.
Read that as a finance person. The price is corrected, the subscription describes the right contract, and the customer keeps paying the old amount until the next billing date. That is a real gap, sometimes a full month of it, and nothing labels it as an open item. Negative prorations are not refunded automatically either, so the timing works in reverse on a downgrade. And Stripe applies a subscription update whether or not payment on the new invoice succeeds, which is how an account ends up at the new price with the invoice still unpaid.
When the deal lives in HubSpot, the second write is a person
The CRM has no write path into a Stripe subscription unless someone built one and maintains it. A rep edits the deal amount. The subscription is untouched. The two values now disagree by $12,000 a year.
Every expansion is another occasion where a human has to remember to make the second write, in a different system, in the order above. On a good quarter that is forty chances to get it right. It is not a discipline failure when a few do not.
Four shapes the drift takes in the data
The good news is that the failure states are enumerable: every unbilled upgrade leaves one of four signatures.
- Quantity drift. Contracted seats up, subscription quantity unchanged. Usually a seat add handled in the CRM and never applied to billing, and it can sit for a year because the invoice keeps arriving without an error.
- Price drift. The tier changed, the subscription item still points at the old price ID. The customer is on Scale in the CRM and paying Growth rates, and the invoice looks ordinary.
- A second item, not a replacement. The new price was added rather than swapped, so both are active. This one reads as an add-on charge and survives an audit, because the total is higher than expected rather than lower and nobody chases an invoice that is too big.
- A coupon or ramp outliving its term. The promotional discount still applies after the period it was written for, or a scheduled ramp never stepped up. Drift runs both directions, and the direction that costs the customer money becomes a credit request mid-renewal.
A missing invoice gets escalated. A price that never changed gets renewed, at the old number, for another year.
The read-only audit, step by step
You can find all four without changing anything, in one sitting. Export both sides, join them, and compute the difference.
From Stripe, export active and trialing subscriptions with the customer ID, the item’s price ID, unit amount, quantity, currency, billing interval, and current period end. From the CRM, export the accounts or deals with contracted seats, contracted net amount, term dates, and renewal date.
Join on something stable: a customer ID stored on the account record, or the billing domain. Never the company name, since a suffix or a rebrand turns every fuzzy match into an afternoon of false positives.
Convert both sides to the same basis before subtracting: annualized, same currency, net of tax. An annual contract billed monthly is not a mismatch against a monthly subscription at one twelfth of it. It is a mismatch when the monthly charge times twelve stops matching the annual value.
Flag every account where the difference is not zero, and sort by annualized delta rather than by account size. The top of the list pays for the exercise.
Two traps will lie to you. An account that started in September has not been on the new price for twelve months, so compare what should have been billed since the change date, not since the term started. And discounts or ramps written into the contract but applied in Stripe as coupons never appear in a price-to-price comparison, so pull them as their own column and check the expiry.
Correcting the subscription is the easy decision
Once you have the list, the billing fix is mechanical: create the price, repoint the item, set the quantity, deactivate the old price. The harder question is the money already uncollected, and it is a judgment call account by account. Some contracts allow back-billing. Some relationships do not survive it. Some of it is small enough to correct forward and say nothing.
That is the argument for finding the list before the renewal conversation rather than during it. A $1,000 a month gap found in month two is a billing correction. The same gap found in month eleven is an $11,000 negotiation, quoted off a base the customer has never actually been billed, in front of someone who now has a reason to question every number on the paper.
This is the comparison Junction runs. Connect HubSpot and Stripe and the free scan reads both, matches accounts, and ranks every mismatch by dollar impact, so the top of the list is the account costing the most per year. The shape of that output is on the sample scan, no signup required.
If you want to fix a price once you have the list, a revenue agent prepares the exact subscription price correction and waits. Nothing moves in Stripe until you approve that specific change, and afterward Junction re-reads both systems and reports whether the account now matches the contract. The wider set of breaks is in Four silent revenue breaks between closed-won and cash, and the mirror-image case, a won deal that never became a subscription, is in Closed-won, never invoiced.
Start with the account you already suspect
You probably have one in mind. The expansion that felt good, the customer who never complained about the new price. Pull that account’s subscription, compare the item against the contract, and see which of the four shapes it is.
Then run the free read-only scan. It changes nothing in HubSpot or Stripe, returns in minutes, and ranks every mismatch by dollar impact, so the first account you work is the one worth the most. Sign up at app.getjunction.io/signup, or keep /resources if you would rather build the export yourself first.
Sources
- Manage products and prices (Edit a price), Stripe Documentation
- Change the price of existing subscriptions, Stripe Documentation
- Prorations, Stripe Documentation
- Pending updates, Stripe Documentation
- Connect Stripe as a payment processor in HubSpot, HubSpot Knowledge Base, September 24, 2026
- Create subscriptions, HubSpot Knowledge Base
