Skip down to the research record

Failed payment: 2 subscription changes to check

Quota Forecast Editorial Team · Published · 11 min read

A failed payment can block a new subscription or plan change; check billing before counting either as booked.

Key takeaways

  • Check whether the failed signup created a subscription.
  • Compare a requested upgrade with the plan recorded in billing.
  • Agree on booking dates with finance.
  • Check shipping dates when a late payment can affect delivery.

A subscription sale feels finished the moment a customer clicks "subscribe" or agrees to move to a bigger plan. But the money has not moved yet, and in some billing systems the subscription itself has not been set up. When the first payment fails, the question for a revenue leader stops being only about the customer. It becomes a question about the books. Does this count as booked revenue? Does it count toward bookings for the period? Or is it still an open deal that happens to look closed in the sales system?

This post covers two cases where a failed payment blocks a subscription change. The first case is a new subscription whose first payment fails. The second case is an existing subscription that tries to change plans, where the new charge is declined. For each case, we look at what the billing platform is documented to do, what that means for the sale, and what a finance or revenue team should decide in advance.

The examples below draw on public documentation from Stripe and Chargebee. Your own billing setup may behave differently, depending on the product, the settings, and the way your company has configured its platform. Treat this post as a checklist of questions, not as a rulebook.

Why the billing system matters for the booking decision

Suppose your dashboard counts a subscription as won when a contract is signed or a form is submitted. The billing system records a different set of facts. It records whether a charge succeeded, whether a subscription exists, and what the customer will be billed on each date.

The practical starting point is knowing how your billing platform handles a failed payment at signup and at a plan change. Stripe's Subscription object reference describes both situations, and it is worth reading before you write any policy.

The Orders documentation from Chargebee approaches the problem from the fulfillment side. It shows how billing dates and shipping dates can be set apart, and how a late payment can change what happens to a shipment. That matters if your subscription delivers physical goods, because a booking decision that ignores fulfillment can leave you counting revenue for a box that never ships.

The goal is to write down, in one place, what your system does and what your finance team has agreed to count. Once that is written, the rest of the conversation becomes simpler. Use a bookings reconciliation checklist when comparing the sales and billing records.

The first case: a new subscription whose first payment fails

A customer fills in a signup form, chooses a plan, and submits a payment method. The first charge is declined. The customer's intent may not have changed, and the sales rep may already have sent a welcome email. But the subscription has not been paid for, and the billing system may not have a subscription at all.

Stripe's reference addresses this situation directly. It says: "If payment fails, return an HTTP 402 status code and don’t create the subscription." There is no active subscription to point to and no renewal schedule to forecast from. Anything your team built on the assumption that the deal was live now rests on something the billing system does not contain.

For a revenue leader, this has three consequences.

The first is that there is no recurring revenue to book from that signup. If the sales team counts the deal as closed-won on form submission, the billing record will not back that up. That gap should be settled by policy, not left to each rep. Reps measured on closed deals will naturally want the deal counted, and a written policy protects both the rep and the forecast.

The second is that a forecast built from billing records will not show a subscription that was never created. A failed first payment can make the deal vanish from the forecast, which can look like a sudden drop in pipeline when it is really a timing question.

The third is that the failed creation attempt left no subscription. A subsequent subscription-creation attempt must succeed before you can count on a subscription existing. Decide in advance whether the booking date is the original signup date or the date the subscription exists. The safer rule is usually the second, because it is a date anyone can check in a billing record. A close date change log can help explain why the sales record's date moved.

For this first case, your team should decide at least four things:

  • Whether a signup counts as booked before a payment clears. The billing record suggests no, because no subscription is created when the first payment fails, but the decision belongs to your finance team and your accounting rules.
  • Which date counts as the booking date: the signup date, or the date the first payment succeeds and the subscription exists.
  • How long a failed signup stays open before sales closes it out or returns it to the pipeline. Choose a period that fits your collection process and write it down.
  • Who is told about the failed payment, and how quickly, so the rep can contact the customer about another payment method while interest is still high.

The second case: an existing subscription whose plan change fails

The second case concerns a declined plan change. A customer already pays for a subscription and asks to move to a higher-priced plan. The system calculates the new amount, and the payment for that change is declined.

Stripe's reference covers this too, and the wording differs from the first case. It says: "If payment fails, return an HTTP 402 status code and don’t update the subscription." The customer does not get the upgrade in the billing system, even if the sales conversation treated it as agreed.

This is where the booking decision gets harder. The old subscription is still live and generating revenue. The question is whether the upgrade counts as booked at all, and if so, whether the additional revenue counts from the request date or from the date the new plan takes effect. A careless team can double count: once for the old plan that continues, and again for an upgrade that was never applied.

Two principles help here.

First, keep the old revenue and the new revenue separate in reporting. The existing subscription keeps counting as it always has, because the customer is still paying for it. The upgrade counts only once the change is applied in billing. A declined upgrade is not an upgrade, however enthusiastic the customer sounded on the call.

Second, expect the amount of a plan change to depend on dates and settings. Stripe's reference includes a worked example of a mid-cycle change. A customer signs up on May 1 for a 100 USD price and is billed 100 USD immediately. If on May 15 they switch to a 200 USD price, then on June 1 they are billed 250 USD: 200 USD for the renewal, plus a 50 USD prorating adjustment for half of the previous month's 100 USD difference. These are illustrations, so the exact figures in your system depend on your product and configuration.

The same reference shows that a different option produces a different result. With that option, the customer is billed 100 USD on May 1 and 200 USD on June 1. The amount a customer sees on an invoice depends on which billing option the company has set, so finance and sales need to agree on that option before building a forecast that depends on the timing of an upgrade.

For this second case, your team should decide at least four things:

  • Whether an upgrade counts as booked only after the change is applied in billing. A reasonable default, given how the failed change is described, is to book the upgrade only once the billing system shows the new plan.
  • Whether the old plan's revenue stays in the forecast at the old rate while the upgrade is open. Check the forecast against the rate the billing system is actually charging.
  • Whether the sales team earns credit when the upgrade is applied or when it was agreed. This is a compensation question as much as an accounting one, so settle it with the people who set commission rules.
  • What happens to an open upgrade if the customer does not pay the new amount: whether it closes, stays open for a set period, or moves back into a renewal conversation.

Illustrative example: compare the requested and recorded plans

An illustrative subscription has a 100 USD price, and the customer requests a 200 USD plan. The charge for the change fails, and billing still shows the old plan. Compare that record with the sales record before including the requested increase in your forecast.

The timing problem: when a late payment changes the picture

The Orders documentation from Chargebee adds a timing layer that is easy to miss. It uses a six-month subscription for a monthly magazine as an example, with billing on the 25th and shipping on the 10th of each month. The billing date and the shipping date do not have to match.

The same example describes cancelling the first shipment if payment is delayed beyond the 15th. The late payment becomes a reason to change what happens to a shipment. A failed or delayed payment may affect delivery as well as the billing record.

That has a direct effect on booking. If your company ships goods, the decision about when to book revenue should be made together with the decision about when to ship. A subscription booked on signup but cancelled before its first shipment may need different treatment from one that ships on schedule. Make sure the people deciding when revenue counts and the people deciding when product leaves the warehouse are in the same conversation.

Timing also changes how you read a failed payment report. A payment that fails on the billing date may still be recovered before the shipping date, or it may not. The report should show both dates. Without that, a manager sees a failed payment and assumes the worst, or sees nothing and assumes all is fine.

A simple decision rule for your team

Policy does not have to be complicated to be useful. The steps below are a reasonable starting point. They are recommendations, not requirements from either vendor, and your accounting team should review them against your own rules.

  • Write down what counts as booked. For each product line, choose a booking point after the subscription exists in billing. Different product lines often need different rules, so write the answer for each line.
  • Book new subscriptions only when they exist in billing. A signup without a subscription stays open in the pipeline until one exists.
  • Keep the old plan's revenue in place while an upgrade is open.
  • Set a time limit for open failed payments. When a payment fails and the customer does not respond, decide when the deal closes or moves back. Pick a period that fits your collection process.
  • Send failed-payment lists to sales and finance on a regular schedule. If sales sees a deal as closed and finance sees a failed charge, the first conversation will be about who is right, not about fixing the payment.
  • Coordinate with fulfillment where goods ship. If a payment problem can cancel a shipment, the booking and shipping decisions should follow the same rules.
  • Review the rules after the first full quarter. Sample some failed payments and check whether booking decisions matched what billing recorded. Adjust the rules where they did not.

What this post does not settle

This post does not tell you how your accounting standard treats a failed payment, and it does not replace advice from your auditors or finance team. Ask your finance team which revenue-recognition rules apply. The points here concern the billing side: what the platform records, and what that means for the decision your team must make.

Vendor documentation describes expected behavior, and a live system depends on how it has been configured. If your platform differs, the same questions still apply. What does the system record when a payment fails? Does it create a subscription, or leave the old one in place? When does the new amount take effect? Your own documentation should answer those questions, and the answers should drive the policy.

Finally, the figures here are round numbers to make the logic easy to follow. Real amounts include taxes, discounts, credits, and other adjustments, so check any number against your own billing data before using it in a forecast.

Where to start

Start by reading Stripe's Subscription object reference and the Chargebee Orders documentation with your billing lead in the room. Ask them to show, in your own system, what happens when a first payment fails and when a plan change fails. Ask them to confirm the answers in a test account, not from memory.

Then pull a sample of recent failed payments. For each, check three things. Did the deal count as booked in the sales system? What did the billing system record? Did the customer later pay, and if so, when? The answers will show where your current process differs from your written policy, which is usually the most useful place to begin.

Once the team agrees on the rules, write them in one short document that sales, finance, and fulfillment can all read. A clear rule applied consistently is worth far more than a detailed policy nobody follows.

Today, choose a recent failed payment and compare its sales status with its billing record. Write down any difference and ask your billing lead to confirm what happened.

Questions about booking decisions

Who should decide whether a failed payment counts as booked?

Your finance team should agree on the booking policy with sales. Include fulfillment when payment timing can affect shipping.

How should the team check its billing setup?

Ask your billing lead to demonstrate failed signup and plan-change attempts in a test account. Compare the results with your written policy.

Sources