Key Takeaways

• The anchor date, not the calendar month, defines the cycle. A subscription anchored on the 15th runs the 15th to the 14th and its invoice never aligns with a calendar month.

• Fixed and metered charges sit on opposite edges of the same cycle. The platform fee bills for the period ahead, and usage bills for the period that just closed.

• A mid-cycle upgrade produces one net figure, not two charges. On a $100 to $250 upgrade with 10 of 30 days left, the $33.33 credit and the $83.33 new charge net to $50.00.

• Anchor dates on the 29th, 30th, or 31st have no equivalent in every month, so the cycle needs an explicit rule for February rather than an implicit one.

• Late-arriving usage lands after the cycle it belongs to has closed, which is why cycles need a defined cutoff separate from the invoice date.

How does a billing cycle work?

A cycle opens on the anchor date, accumulates charges for its duration, then closes and generates an invoice while the next cycle opens immediately.

What happens at each boundary:

• Cycle open. Charges billed in advance are assessed for the period now starting.

• During the cycle. Metered usage accumulates against the subscription, and plan changes create proration entries rather than immediate invoices.

• Cycle close. Usage stops accruing to this period, aggregation finalizes the quantity, and rating applies the price.

• Invoice generation. Advance charges for the next period and arrears charges for the period that closed combine onto one document.

The anchor date usually comes from the subscription start, which is why a book of customers who signed up on different days produces invoices every day of the month rather than one batch on the 1st.

What happens when a customer changes plan mid-cycle?

Proration splits the period, crediting unused time on the old plan and charging for remaining time on the new one.

A customer on a $100 monthly plan with a cycle running the 15th to the 14th upgrades to $250 on day 20 of a 30-day cycle, leaving 10 days:

Whether that $50.00 bills immediately or waits for the next invoice is a policy decision, and the two produce very different support volumes. Immediate charging surprises people; deferring it makes the next invoice larger than the plan price and surprises them then. Flexprice documents how proration is calculated on a mid-cycle plan change in its proration guide if you're deciding which way to configure it.

Downgrades reverse the arithmetic and raise a second question: whether the credit is refundable or only offsets future charges.

What breaks billing cycles at scale?

Ambiguous anchor dates break first, because dates past the 28th don't exist in every month.

The recurring failures:

• Month-end anchors. A cycle anchored on the 31st has to resolve to the 28th, 29th, or 30th depending on the month, and different rules produce different period lengths for the same subscription.

• Usage arriving after close. Events for the closed period keep arriving for hours or days, so a cycle that finalizes the instant it closes undercounts.

• Timezone boundaries. A cycle closing at midnight closes at 24 different moments across a global customer base, and usage timestamps have to agree with the cycle's timezone.

• Retroactive corrections. A rate corrected after the invoice went out means re-rating a closed period, which needs the historical price rather than the current one.

• Cycle alignment on multiple subscriptions. A customer with three subscriptions anchored on different dates gets three invoices unless the cycles get aligned, and aligning them means prorating two of the three.

The cutoff is the one I'd define explicitly and early. Deciding that a cycle finalizes 24 hours after it closes, and holding to it, is what makes invoices reproducible.

Related reading

Further reading on subscription periods and workflows:

• subscription management guide covers cycles inside the wider subscription picture.

• what is subscription management defines the surrounding discipline.

• billing workflow walks the sequence a cycle triggers at close.

• how to automate subscription billing workflows covers running cycles without manual steps.

• grandfathering covers keeping legacy customers on old terms across cycles.

FAQ

How long is a billing cycle?

Most run a month, but the length is set by the plan rather than by convention. Weekly, monthly, quarterly, and annual cycles all appear in production, and some contracts use a custom period tied to a fiscal calendar. What matters more than the length is that the cycle boundary is unambiguous for every month it recurs in.

Why did I get charged twice in one billing cycle?

Usually because a plan change created a proration charge alongside the regular invoice, or because a subscription that bills fixed fees in advance and usage in arrears produced two documents. A genuine duplicate is rarer than either. Checking whether the two amounts cover different periods normally identifies which of the three happened.

Can a customer's billing cycle be changed after signup?

Yes, and it requires prorating the partial period between the old anchor and the new one. Moving a customer from a 15th anchor to a 1st anchor means charging or crediting the intervening days, then starting the new cycle clean. Teams usually do this to consolidate a customer's several subscriptions onto one invoice date.

Does the billing cycle have to match the metering period?

No. Usage can be metered continuously or hourly while the cycle stays monthly, and that's the normal arrangement. The cycle decides which measured usage belongs to which invoice, so the metering just has to timestamp accurately enough for events to be assigned to the right period.