Skip down to the research record

Cancellation billing day: 8 steps to check credit

Quota Forecast Editorial Team · Published · 9 min read

The cancellation time can decide the billing day

In Chargebee's example, cancellation time determines which billing day counts as remaining and affects the credit.

Key takeaways

  • Record the cancellation time alongside the date.
  • Compare it with the subscription's creation time.
  • Identify the billing window before counting remaining days.
  • Recalculate the credit using your own dates and rate.

Chargebee's proration documentation walks through this with a worked example, and this post goes through it step by step.

The example belongs to Chargebee. It is one vendor's documentation, not a general rule for every billing system. Use its numbers to understand the logic, then check how your own system records cancellations before you rely on any figure from it. Proration, in this context, means adjusting an amount for the part of a billing period that has or has not been used.

The example starts with a plan change

The example opens with a plan change: "The customer decides to update their plan on July 15." It then moves to the invoice and the cancellation setting: "The $300 invoice is paid, and the cancellation date is set to be billed in the subscription cancellation settings." Both quotes come from Chargebee, Proration Mode.

The second quote is the one to keep in mind. In this example, the cancellation date is set to be billed through the subscription cancellation settings. If your system controls billing for the cancellation date the same way, a reviewer needs to know where that setting lives and who can change it.

A 9:00 AM cancellation falls before the creation time

The first case is a same-day cancellation: "Same-day cancellation: The customer cancels on September 21, 2025, at 09:00 AM." Chargebee, Proration Mode

The example compares that time with the subscription's creation time, which it gives as 10:00 AM. The source explains the result this way: "Because 09:00 AM is before the 10:00 AM creation time, it falls within the September 20, 10:00 AM – September 21, 10:00 AM billing day, so the cancellation is treated as occurring on September 20 and that day counts as remaining." Chargebee, Proration Mode

Read that sentence in three steps. First, the example compares the cancellation time with the creation time. Second, the earlier time places the cancellation inside the billing day that runs from September 20 at 10:00 AM to September 21 at 10:00 AM. Third, the cancellation is treated as occurring on September 20, and that day counts as remaining.

The cancellation is dated September 21, but the example does not use that calendar date for the count. It uses September 20, the start of the billing day that the 9:00 AM time falls in. For a deal review, that means the date on a cancellation record and the date used in the calculation can differ. For related record checks, see date and time formats.

The 10:00 AM creation time sets the billing window

The billing day in this example runs from 10:00 AM to 10:00 AM, the same clock time as the creation time the source gives. In this example, the creation time and the window's start and end times line up.

That makes the creation time a number to pull before any review. A reviewer who has the cancellation date but not the creation time cannot tell which window the cancellation belongs to, at least under the logic this example shows.

If another system anchors its billing days to a different clock time, the same calendar cancellation can land in a different window. Confirm the anchor time in your own system instead of assuming it matches this example.

The window sets the remaining days and the credit

The example then counts the remaining days and the credit: "Remaining days = September 20–30 = 11 days, so the prorated credit = $10 × 11 = $110." Chargebee, Proration Mode

The count starts on September 20 because the 9:00 AM cancellation was treated as occurring that day. It runs through September 30, which the source counts as 11 days. The source then multiplies $10 by 11 to get a $110 credit.

Two points follow from that arithmetic. The credit depends on where the count starts as well as on the rate. And the $110 figure belongs to this example. Do not carry it into another deal. Rebuild the count from that deal's own dates and its own rate.

Illustrative example of checking the multiplication

For an illustrative arithmetic check, assume 10 remaining days and a daily rate of $30. Multiply $30 by 10 to get $300. This checks the multiplication only; first confirm which days count under your system's settings.

The clock time separates the two cases

The two cases in the example share a calendar date, September 21, 2025, and differ in clock time. The 9:00 AM case is labeled same-day, and the 2:00 PM case is labeled next-day.

Case in the exampleCancellation time (September 21, 2025)
Same-day cancellation09:00 AM
Next-day cancellation02:00 PM

Set the rows next to each other and the variable a reviewer should check first is the clock time. Read the full example on Chargebee's Proration Mode page before you cite an outcome for the 2:00 PM cancellation.

Build the timeline in the order the example uses

The example runs in this order: a plan change, a paid invoice, a cancellation with a time, a billing window, a day count, and a credit. Writing it out in that order gives a reviewer a line for each fact:

  1. Plan change: July 15.
  2. Invoice and setting: the $300 invoice is paid, and the cancellation date is set to be billed in the subscription cancellation settings.
  3. Creation time: 10:00 AM.
  4. Cancellation: September 21, 2025, at 09:00 AM.
  5. Billing window: September 20, 10:00 AM to September 21, 10:00 AM.
  6. Treated date: September 20, which counts as remaining.
  7. Count: September 20–30, 11 days.
  8. Credit: $10 × 11 = $110.

Build your own timeline with the same steps, using your system's facts in place of the example's. If a line cannot be sourced from your system, mark it as unverified rather than filling it in. A timeline with one gap is more useful in a review than a clean one with a guess in it.

Today, choose a cancellation record and write its timestamp, creation time, and billing window together before checking the credit.

Does the calendar date alone decide the billing day?

No, not in Chargebee's example. The 9:00 AM cancellation is dated September 21, but the example compares its time with the 10:00 AM creation time, and that comparison places it in the billing day that begins September 20 at 10:00 AM.

Can a cancellation be treated as occurring on an earlier day?

In Chargebee's example, yes. The 9:00 AM cancellation on September 21 is treated as occurring on September 20, and that day counts as remaining.

How many remaining days does the example count?

The example counts 11 remaining days, from September 20 through September 30.

What credit does the example produce?

The example produces a $110 credit, calculated as $10 × 11.

Is this a rule for every billing system?

No. The example comes from Chargebee's proration documentation, so its results hold for that example and should not be stated as a general rule.

Write the cancellation time into the deal record

Write the cancellation time into the deal record next to the date, because the example's result depends on the clock time as well as the day. A date alone does not carry the step the example uses to choose a billing day.

A short record for each subscription could hold these lines: the cancellation date and time, the time zone, the creation time, the billing window the cancellation falls in, the day the system treats the cancellation as occurring on, the remaining-day count, and the credit. Each line should point to a source in your own system. If a line depends on a setting, write down the setting's name and the person who can confirm it.

This record does two jobs. It lets a reviewer follow the amount from start to finish, and it shows which line changed when a cancellation time moved. If the record is missing a line, the review should say so rather than fill the gap from the example. For changes to a deal's close date, use a close date change log.

What to check before a deal review

Start with the facts the example depends on. Each item below is something to pull from your own system, not a value copied from Chargebee's example.

  • The exact cancellation timestamp. Get the time of day, not only the date. The example's two cases differ by clock time, so a date without a time leaves the outcome open.
  • The time zone. Confirm which time zone the timestamp uses. A timestamp without one can be read more than one way.
  • The subscription's creation time. The example compares the cancellation time with a 10:00 AM creation time. Pull the creation time for the subscription in front of you.
  • The billing window. Work out which billing day the timestamp falls in before calculating any credit.
  • The setting that controls billing for the cancellation date. The example says the cancellation date is set to be billed in the subscription cancellation settings. Find that setting in your system and confirm who can change it.
  • The day count. Count the remaining days from the day the system treats the cancellation as occurring, then recalculate the amount from that count.

Do not use the calendar date as the billing day

Using only the calendar date skips the step this example depends on, which is comparing the clock time with the creation time. In the example, a September 21 cancellation at 9:00 AM leads to a count that starts on September 20, so a reviewer who reads only the date may get a different starting day.

The fix is simple but easy to forget. Before the review, write down the cancellation timestamp, the creation time, and the billing window the timestamp falls in. Then check the count against those three facts, not against the date on the record.

Questions to ask the billing team

Bring these questions to the billing team, and get written answers before the review:

  • Which clock time starts each billing day for this subscription?
  • Is the cancellation timestamp stored with a time zone?
  • Which day does the system treat the cancellation as occurring on?
  • Where does the remaining-day count start, and does it match that day?
  • Can the team show the credit calculation line by line?

How to explain it in the room

If a reviewer asks why the amount moved, answer with the timeline: which timestamp was used, which billing window it falls in, which day the cancellation was treated as occurring on, and which count followed. Each answer should come from the record. Any answer you cannot source should be called unknown, not estimated.

Keep the example in its place

Your review should name Chargebee's example whenever it uses those numbers. Write "Chargebee's example shows" rather than "billing systems do." The example uses one creation time, two cancellation times, and one rate. Any amount in a deal review that depends on the cancellation time should trace back to your own timestamps, your own creation time, and your own cancellation setting. Then the amount can be explained, even when it moved.

Sources