Nine published billing and reporting limits can cap or delay a quarter-end bookings count, in two ways: record caps and timing windows. According to Stripe, each customer can have up to 500 active or scheduled subscriptions, and a subscription takes up to 20 items. The timing windows in Stripe's published rules run from 1 hour to 3 days, according to Stripe. This guide sorts those figures by publisher, explains what each one measures, and shows how to compare them with your own counts.
Key takeaways: which figures cap a count and which delay it
- caps limit how many records fit: each customer can have up to 500 active or scheduled subscriptions, according to Stripe.
- item and line caps limit what one record holds: a subscription takes up to 20 items, according to Stripe, and payment mode allows a maximum of 100 line items, according to Stripe.
- timing windows delay state changes: a subscription whose first invoice is unpaid after 23 hours moves to incomplete_expired, according to Stripe.
- reporting caps apply to each report: attribution reports include up to 20 million interactions after sampling, according to HubSpot.
- credit notes can split a bookings adjustment: anything above 50 USD is added to the customer's credit balance, according to Stripe, so the refund and the balance both need a look.
Billing system limits: the short answer for a bookings count
A bookings count can draw on several kinds of record at once. Those include subscriptions and their items, the checkout sessions that created them, the invoices that bill them, the webhook messages that tell other systems what changed, and the attribution reports that credit a deal to its sources. Published ceilings or timing rules exist for some of those records, not all of them. The list here is therefore a starting set, not a full inventory of every limit a billing or reporting product applies.
Keep the two kinds of figure apart when you review a count. A cap is a number a record cannot exceed. A timing window is a period after which a record changes state or a further step runs. A record can fall outside a total for either reason, so each kind needs its own check. Treat a count that looks clean as a count you have checked against these figures, not as proof that no limit applied. Each rule in this guide is tied to the publisher named beside it, and one publisher's rule does not apply to another.
What each figure measures and who published it
Nine figures are the core of this guide, and they are the ones the title counts: the 500 active or scheduled subscriptions for each customer, the 20 subscription items, the 20 recurring line items in subscription mode, the 100 payment-mode line items, the 23 hour first invoice window, the 1 hour wait before a payment attempt, the 72 hour finalize fallback, the 3 day webhook retry period in live mode, and the 20 million attribution interactions in each report. Stripe publishes the first eight. HubSpot publishes the last one.
The nine figures fall into two groups. Five of them set a ceiling on a count: subscriptions for each customer, items in each subscription, the two Checkout line item limits, and interactions in each report. Four of them set a time window: the first invoice window, the wait before payment, the finalize fallback and the webhook retry period. Keep the two groups apart when you investigate a short count. A check against a ceiling is a count check, and a check against a window is a date check.
The figures come from different pages of the same publisher. The 23 hour window and the 500 subscription cap appear on the subscription object page, according to Stripe. The 1 hour wait, the 72 hour fallback and the 3 day retry period appear on the status transitions page, according to Stripe. Record the page name next to each figure in your reconciliation notes so the rule can be found again when you review it.
Two further rules support the count without being part of it. One is the 50 USD credit note threshold, which Stripe publishes. The other is the Chargebee month-end cut-off setting, which Chargebee publishes.
Each figure belongs to the publisher that documented it. The Stripe figures are not Chargebee or HubSpot limits. Frequency is not covered by these figures, so take it from your own data.
Subscription, line item and event type caps
The subscription cap is the first ceiling to check. Each customer can have up to 500 active or scheduled subscriptions, according to Stripe. Inside a subscription, the list holds up to 20 subscription items, each with an attached price, according to Stripe. A count that rolls up items rather than subscriptions has a different ceiling, so the unit you count in matters.
Checkout caps depend on the mode of the session. In payment mode, there is a maximum of 100 line items, and the same page recommends consolidating line items if there are more than a few dozen, according to Stripe. In subscription mode, there is a maximum of 20 line items with recurring Prices and 20 line items with one-time Prices, according to Stripe. A session that mixes recurring and one-time lines has two separate counts to check.
On the reporting side, the cap sits on the report rather than on the account. You can include up to 100 event input types in each report, according to HubSpot. Attribution reports also include up to 20 million interactions after sampling, according to HubSpot.
Sampling changes what a report shows at high volume. If an account has a very high volume of interactions, HubSpot samples high-frequency interaction types, such as email interactions and page views, to stay within the 20 million interaction limit, according to HubSpot. Your bookings reconciliation should note whether a sampled interaction type sits behind a figure before you compare it with a revenue total. See also Bookings reconciliation: 5 checks for quarter close.
Time windows: 1 hour, 23 hours, 72 hours and 3 days
The first invoice window applies to each new subscription. If the first invoice is not paid within 23 hours, the subscription transitions to incomplete_expired, according to Stripe. A subscription in that state needs a different check from one that is active, so the status belongs in the count's notes.
Before a payment attempt, Stripe waits. The wait is 1 hour after a successful response to the invoice.created event from all listening webhooks, according to Stripe. Any downstream system that listens for that event is part of the wait, so its response time belongs in your notes.
If no successful response arrives in time, the fallback runs. If Stripe does not receive a successful response within 72 hours, it attempts to finalize and send the invoice, according to Stripe. An invoice in that path may be finalized later than a reader of the subscription record expects.
Webhook failures have a longer window. In live mode, if your webhook endpoint doesn't respond properly, Stripe continues retrying the webhook notification for up to 3 days with an exponential back off, according to Stripe. A notification that fails late in a quarter may still be retried after the close, so the retry period should be read against the close date.
Chargebee's timing rules sit on a month-end cut-off. If you want to set this cut-off as the last day of the month, choose 31, according to Chargebee. Sites that signed up before May 19, 2026 use the earlier definition of day-based proration, according to Chargebee.
Illustrative example: one unpaid first invoice
Suppose a quarter-end count holds 100 new subscriptions, and 5 of them have a first invoice still unpaid 25 hours after creation. Those 5 are the first to check, because the first invoice window is 23 hours. Look at each subscription's status: one that has moved to incomplete_expired needs a different check from an active one, so note it in the count. The 100 is a total across all customers, so it does not show whether any single customer is near the 500 subscription cap. Check that cap with a count for each customer.
Measure your own counts against these figures and know their limits
Your highest subscription count for one customer is the figure to hold against 500. Pull that number from the customer grouping that your forecast uses, not from a total across all customers, because the cap applies to each customer.
Your largest subscription item count is the figure to hold against 20. Count items on each subscription rather than the number of products sold, since the cap applies to each subscription's list of items.
Start with the unit of each extract. A cap on subscriptions for each customer needs a customer key, a cap on items needs a subscription key, and a cap on interactions needs a report key. If your extract groups at a different level, the total you compare with a cap is not the number the cap measures.
Your Checkout sessions are the figures to hold against 100 in payment mode and 20 in each of the two subscription line categories. A session that exceeds those limits should be read as a separate case in the reconciliation notes, not as a regular row.
Your unpaid first invoices are the figures to hold against 23 hours. A subscription whose first invoice has been unpaid longer than 23 hours may already be in incomplete_expired. Your webhook failure log is the figure to hold against the 3 day retry period. For live-mode endpoints, a failure older than 3 days is outside the published retry period.
Your attribution report totals are the figures to hold against the 20 million interaction ceiling, and against the 100 event input types. Note whether sampling applied before you trust a total, because sampling applies at very high interaction volumes.
Your credit notes are the figures to hold against 50 USD. A credit note above that amount reaches the customer's balance, so the adjustment should be traced to both the refund record and the balance. Related checklists are Unsigned quote review: 5 checks for quarter-end records and Invoice extract reconciliation: 6 checks for bookings.
These figures are not a full list of limits. The Stripe rules do not apply to Chargebee or HubSpot accounts. A published limit is a documented ceiling or timing window. It is not a benchmark for how a healthy business should look, and this guide does not supply one.
Billing limits reference table by publisher
The other figures appear in the sections above.
| Publisher | Source page | Quoted rule |
|---|---|---|
| Stripe | Subscription object reference | Each customer can have up to 500 active or scheduled subscriptions. |
| HubSpot | Create attribution reports | Attribution reports include up to 20 million interactions after sampling. |
| Chargebee | Orders page | If you want to set this cut-off as the last day of the month, choose 31. |
Next step: pull your highest subscription count for one customer and your longest-running unpaid first invoice, then compare each with the 500 and 23 hour figures.
FAQ: billing limit questions for RevOps owners
Which billing system limits can affect a bookings count?
Subscription caps, item caps, Checkout line item limits, the first invoice window, the wait before payment, the finalize fallback, webhook retries, HubSpot attribution interaction ceilings and the credit note threshold can each affect a count. For example, each customer can have up to 500 active or scheduled subscriptions, according to Stripe. The timing figures change when a subscription or invoice changes state, while the caps change how many records fit in one count.
How many subscriptions can one Stripe customer have?
Count both active and scheduled subscriptions when you check against that figure.
How long does Stripe retry a webhook that fails?
In live mode, Stripe continues retrying the webhook notification for up to 3 days with an exponential back off, according to Stripe. This retry applies only in live mode, so note the mode of each failure in your log.
Does the HubSpot 20 million interaction limit apply to my reports?
The limit applies to attribution reports: they include up to 20 million interactions after sampling, according to HubSpot. Check whether your report is an attribution report before you apply the figure. Sampling applies to accounts with a very high volume of interactions.
What happens to a credit note above 50 USD?
Anything above 50 USD is added to the customer's credit balance and is applied to the next invoice, according to Stripe. Your reconciliation can look at both the refund record and the credit balance, since a credit note of 50 USD or less is refunded to the payment method instead.