According to Stripe, you can only define up to 10 current or future phases at a time on a subscription schedule. That is the direct answer to the subscription schedule phase limit question, and it is Stripe's figure.
Key takeaways
- According to Stripe, a planned Stripe change should be checked against a cap of up to 10 current or future phases.
- According to Chargebee, a subscription change can be scheduled up to 5 years (1830 days) from the current date, so check the date against that window.
- According to Stripe, keys from Phase 1 are added to the record fields of a subscription that a schedule created, so note which subscriptions came from a schedule.
- According to Stripe, a new invoice is finalized approximately 1 hour after creation, so treat draft figures as provisional until then.
- The effect of each change on the forecast date needs your own records.
Why a schedule's phase cap matters for the forecast
A subscription that changes on a set future date brings two planning figures into a forecast: how many phases its schedule can hold and how far ahead a change can be placed. The two figures come from different products, so this article keeps them apart and ties each one to the page it came from. Revenue leaders can then check every planned change against the right limit before the change is counted.
According to Stripe, subscription schedules automate changes to subscriptions over time. That makes a schedule a planned series of future changes rather than a single edit. Each planned Stripe schedule's phase count is worth keeping beside its expected revenue line, so the number is visible when the forecast is reviewed in a meeting.
The table below gives the quoted rule for each publisher, so every entry can be traced back to its own page. Each row keeps the publisher's own wording, with no combined figure. The two rows describe different products and different kinds of limit, so compare the cells one by one rather than adding or ranking them.
| Publisher | Source | Quoted limit or rule |
|---|---|---|
| Stripe | Stripe subscription schedules documentation | "You can only define up to 10 current or future phases at a time on a subscription schedule." |
| Chargebee | Chargebee subscriptions documentation | "You can schedule changes to a subscription for any specific date up to 5 years (1830 days) from the current date." |
The Stripe and Chargebee rows are separate limits on separate products, so the figures should not be merged into one rule. Merging the 10 phases with the 5 years would produce a figure that no quoted rule gives. Keep the rows apart in the forecast notes, and write the product name beside each figure so that the number is never read out of context.
The 10-phase cap on one subscription schedule
The count joins current and future phases together, so a planned change should be counted against the combined figure rather than against the phases still ahead. According to Stripe, the wording ties the figure to one subscription schedule, which matters when a team plans several schedules side by side.
Before a planned Stripe change is recorded, its phase count is worth comparing with the cap of 10. A count written in the change log, next to its date, lets the reviewer see the distance to the cap without reopening the billing tool.
According to Stripe, the cap is up to 10, so a schedule already at 10 phases has reached the limit the page states. Splitting a longer plan across several schedules is an editorial option, not a documented step.
Each schedule's count belongs on its own line in the notes. When two schedules share one customer, check each schedule's phase count on its own, since the cap applies to a subscription schedule. Adding those counts into one total would blur the figure the cap actually measures.
Illustrative example: phase count against the cap
Suppose a schedule holds 7 phases and a planned change adds 2 more. The total is 9, which is 1 below the cap of 10, so the change can go into the forecast after the phase check. This example uses round numbers for practice only and describes no real tool.
The 1830-day window for scheduled changes
According to Chargebee, a change can be scheduled for a specific date up to 5 years (1830 days) from the current date. That describes a window for dates rather than a count of phases.
According to Chargebee, the window runs from the current date. Dates entered long before the forecast meeting deserve a second look. The date should be measured against the window as it stands when the forecast is prepared.
Before a change enters the forecast, compare its date with the window measured from the current date. A date that falls outside the window cannot be scheduled under that figure, so it should be moved, questioned, or left out of the number until it is confirmed. Keep a note of which dates were checked, so the next review starts from the same record.
If the schedule ties to a multi-year contract, the note on multi-year deal billing figures is a useful next read. Keeping a short list of such notes in the forecast file gives the reviewer a place to start when a date is questioned. The list can be short, with one line for each recurring type of schedule and one for each vendor.
The window sets how far ahead a change can be placed. A planned date inside the window still needs its own forecast treatment, because placement and effect are separate questions for the forecast team. Keeping those two questions separate in the notes gives each one its own answer.
What Phase 1 adds to a subscription's record fields
According to Stripe, when this schedule creates a new subscription and the subscription enters Phase 1, the three keys in Phase 1 are added to the subscription’s record fields. That sentence ties this to two events: the schedule creating the subscription and the subscription entering Phase 1.
A forecast note should record the three keys as they appear on the subscription rather than assume what they mean. Pulling the list of keys from one sample subscription is a practical way to start that note. That gives later reviewers the same starting point.
Once those keys are on a subscription, a forecast owner can search for subscriptions that a schedule created. That search is an editorial suggestion. Running it before each forecast meeting gives the owner a current list of schedule-created subscriptions to review against the limits.
The date each subscription enters Phase 1 is worth noting in your records, because the quoted sentence ties the record fields to that event. A record of that date sits beside the schedule's phase count and the change date, so the three can be read as one line. In a spreadsheet, that means one row for each schedule, with the entry date in its own column.
A forecast owner should review these subscriptions at the same time as the schedule's phase count, so the two checks stay together. The review can use the same meeting as the rolling check later in this article, which keeps the work in one place. Each review should end with a short list of subscriptions that need a follow-up, even if that list is empty.
The invoice that follows a new schedule
According to Stripe, the invoice begins in a draft status and is finalized by Stripe approximately 1 hour after creation. In a forecast, that means a newly created invoice should not be read as final on the day it appears.
A draft has not reached the finalized state, so a draft figure stays provisional until the invoice is finalized in the billing tool. Teams that record bookings from new schedules should mark those draft figures as provisional in the forecast. The mark gives reviewers a way to see which figures can still change before the meeting.
Because the quoted wait is approximately 1 hour, a forecast built right after the invoice is created may still rely on a draft. Building the forecast a few hours later avoids that case. A short note with the invoice creation time beside the forecast entry is enough to show whether the wait has passed.
Before the forecast is locked, look for the finalized invoice and replace the draft figure with it. If the finalized invoice is not yet visible, keep the draft figure marked as provisional and note the date of the check. That note tells the next reviewer when the figure was last checked, so no one has to guess. For period-end figures, see quarter-end bookings.
Rolling 7-day check and the limits of these figures
The check below looks back over recent changes, so the review stays focused. It works on the forecast's own records, not on a subscription setting.
A rolling check can cover the last 7 days of changed records, using a relative date filter in your own tool. Each run lists the records that changed in that window, which gives the reviewer a short set to compare against the phase cap and the window. Running the check each week keeps that set current, and it is an editorial recommendation rather than a documented product feature. A related read on forecast data refresh limits can sit beside this routine.
Every changed record on the list should be checked for its phase count and its date before it stays in the forecast. A record that moves outside either limit is worth raising in the forecast meeting. The list is a working tool, not a confirmation, so the billing tool still needs a final look before a number is marked final.
The phase cap, the window, and the invoice timing should be checked together, rather than trusted as a single answer. A revenue leader who reads this article should treat the three checks as inputs to the forecast, not as the forecast itself.
Next step: In your billing tool, open one scheduled subscription change and compare its phase count and effective date with the limits in this article before you record it in the forecast. If the change sits in Stripe, check its phase count against the cap of 10; if it sits in Chargebee, check its date against the window of 1830 days.
FAQ: subscription schedule limits
How many phases can one Stripe subscription schedule hold?
According to Stripe, a subscription schedule can hold up to 10 phases, counting current and future ones. That ceiling is the figure to check a planned Stripe change against before it enters the forecast.
How far ahead can a Chargebee subscription change be scheduled?
According to Chargebee, a change can be scheduled for any specific date up to 5 years (1830 days) from the current date. That window moves with the current date, so a planned date should be checked again before it is counted.
Can a schedule be added to a subscription that already exists?
Yes, according to Stripe, you can add a schedule to an existing subscription instead of creating subscriptions directly through a schedule. Each schedule's creation route is worth noting in the forecast records.
When does Stripe finalize a new subscription invoice?
According to Stripe, the invoice is finalized approximately 1 hour after creation, after it begins in draft status. Until finalization, the figure should be treated as provisional.
What does Phase 1 add to a subscription's record fields?
According to Stripe, keys from Phase 1 are added to the subscription once a schedule creates it and the subscription enters Phase 1. The forecast note is more accurate when it lists the keys as they appear on a live subscription.
Does the Stripe phase cap apply to Chargebee?
The 10-phase cap is quoted for Stripe subscription schedules, so check Stripe changes against it. For a Chargebee change, check the date against the window of 5 years (1830 days) from the current date.