Under Chargebee's earlier renewal definition, a term starts at the beginning of the renewal day and ends at the last millisecond of the day before. The answer also depends on the system that wrote the date and on how that system defined the edge of a term. Chargebee's proration page describes an earlier renewal definition in which a term has two boundary times, and they fall on different calendar days. Read one date from an export without knowing that, and you can place a term end a day off, or misjudge whether two back-to-back terms overlap.
Key takeaways
- A term starts at the beginning of the renewal day.
- A term ends at the last millisecond of the day before the renewal.
- The two stamps are one millisecond apart, so the terms meet without a gap or an overlap.
- Renewal work can keep running for 2–3 hours after the start stamp.
- Check the clock time in your export before you report a term end date.
Both boundaries are exact, and an export is only as useful as the clock time it keeps. This post walks through both boundary times using one example case. It then shows how to check your own export before you rely on the dates it contains.
The example case is a subscription on a site created before May 19, 2026. That date is the one the proration page singles out, and we come back to it later. The subscription renews on May 19, 2026. We want to know two things: when the term before that renewal ends, and when the renewal term begins.
The first boundary: where a term starts
Under the earlier definition, all start timestamps are set to the beginning of the day. The proration page applies this to subscription start, activation, renewal, and trial start. For our subscription, the renewal that opens the new term is stamped at the start of May 19, 2026. Read literally, the new term opens at the first instant of May 19, 2026.
Most people expect this boundary. A term that starts at midnight looks tidy, and an export that shows May 19, 2026 with no clock time looks just as tidy. The catch is that the time is not absent from the stored value. It is zero. If your export drops the time column and keeps only the date, a start stamped at midnight becomes indistinguishable from any other event logged on that date. Your report will still be right about the day, but it will have lost the detail that shows the boundary is exact.
The second boundary: where a term ends
The second boundary sits at the other end of the term, and it causes most of the confusion. Under the same definition, all term-end timestamps are set to the end of the previous day. For our subscription, the term that runs up to the May 19 renewal closes at the last millisecond of May 18, 2026. The end is recorded on the calendar day before the day the next term starts, not on the day the renewal happens.
That changes how a date reads. A reader who sees May 18, 2026 in an end column may assume the term stopped sometime during the 18th, with the usual vagueness about the hour. The record actually holds the last thousandth of a second of that day. A value of May 19, 2026 in that column for this term is a sign that you are looking at a different definition, or at a different term. The check is the clock time: the last millisecond of the day, on the day before the renewal.
Why the two boundaries nearly touch
Put the two boundaries side by side. The old term's closing stamp and the new term's opening stamp are separated by a single millisecond. The old term ends on May 18, 2026, and the new term opens on May 19, 2026. Nothing is recorded in between, so the two terms meet without overlapping and without a gap you could fill with a whole day.
| Stamp | Calendar day | Clock time | What it means |
|---|---|---|---|
| Previous term end | May 18, 2026 | Last millisecond of the day | Old term closes |
| Renewal term start | May 19, 2026 | First instant of the day | New term opens |
| Renewal work | May 19, 2026 | Runs 2–3 hours after the start | Records may still be written |
This is why the earlier definition is easy to misread. Each boundary is exact on its own terms, but a reader who looks only at calendar dates sees a term that ends on the 18th and another that starts on the 19th, and may conclude the two are separated by a full day. Under the stamped view they are not separated by a day at all. They are separated by one millisecond that falls on the line between two calendar dates.
The precision also matters if your tool treats time as a count of milliseconds. A system that keeps the thousandths keeps the final millisecond of one day and the first instant of the next apart. A system that works in whole days cannot, and that is the case the proration page warns about. We come back to that warning below. For a related check on precision, see call log timestamps for fractional seconds.
Renewal takes hours to finish
The boundary stamp and the renewal work are not the same event. The proration page says that although renewal times are aligned with the start of the day under this definition, the renewal can take 2–3 hours to complete due to the volume of operations. So for our subscription, the new term is stamped at the start of May 19, while the renewal itself may keep running for two to three hours afterward.
Exact wording matters when you record that window. PostgreSQL's date and time documentation shows how short forms can be read: "For example, '1 12:59:10' is read the same as '1 day 12 hours 59 min 10 sec'." If your team stores the window as a duration, write it out in full in the notes so nobody has to decode the shorthand.
For a revenue leader this means two things. First, the stamp tells you when the term is considered to begin, not when every record tied to the renewal has been written. Second, a report pulled during the renewal window can mix states: some renewal records look finished and others do not yet. If the export shows a May 19 start while the renewal is still running, a figure built from it may be incomplete for that subscription.
The safe habit is simple. Choose a pull time later than the 2–3 hours the page describes, and record that time next to the export. The date on the file tells you when it was taken, which matters as much as the values inside it.
Reading the example in your export
In an export that keeps full timestamps, the example's key values are the following. Use your own column names. The values are what matter. The previous term's end value holds the closing stamp for May 18, 2026. The renewal term's start value holds the opening stamp for May 19. The renewal note tells you not to trust a pull taken too early in that day.
Consider what happens when a colleague asks why a subscription seems to show two terms that meet at the same date line. Without the full values, the question looks like a data error. With them, the answer is visible in the export: one term closed just before midnight on May 18, 2026, and the next opened at the first instant of the following day. The two rows never overlap. What looked like a duplicate is the normal edge between two terms, and you can say so with the two values in front of you.
If your export has only dates, you cannot see the closing stamp or the opening stamp, and you lose the reason the two boundaries are exact. In that case you can still report the dates, but say so in the report. Write that the term ends on the 18th at the end of the day and that the next term begins on the 19th at the start. That sentence is accurate under the earlier definition, and it is short enough to put in a CRM note.
Illustrative example: a 5-renewal sample
In this illustrative sample, 5 renewals are pulled and 4 rows match the earlier definition. Each of those shows a start stamp at the beginning of the renewal day and an end stamp at the last millisecond of the day before. The fifth row shows a term ending on the renewal day itself. That pattern does not fit the earlier definition, so check its clock time and the proration mode before using it. Report the four matching rows with their times, and hold the fifth until its source is traced.
Proration and switching modes
The proration page includes a warning that matters for exports pulled over time. For sites created before May 19, 2026, switching from millisecond-based to day-based proration results in the loss of timestamp information. A switch can therefore remove the clock detail that made the closing and opening stamps meaningful.
Apply this to our example. Suppose you pulled the export before a switch and saw the May 18 end at its closing stamp. After a switch, the same term may appear only as a date. A later export is then not a like-for-like copy of the earlier one, even though the subscription and the renewal have not changed. If you compare the two files to check whether a renewal happened, the difference may come from the switch, not from the renewal.
Keep the earlier export. Do not overwrite it with the later pull. Label each file with the date it was taken and the proration mode in effect at that time. That way you can always go back to the full timestamps.
Checking your own export
Before you rely on any end date, run a short check on a few rows. You can confirm the definition your site uses on the proration page. The page labels this one as the earlier definition, so confirm that it applies to you before you assume the pattern below holds.
- Pull a sample of renewals and look at the start values. If they show a stamp at the first instant of the day, the start boundary matches the earlier definition.
- Look at the end values for the same subscriptions. If they show the last millisecond of the day before the renewal, the end boundary matches too.
- Confirm your export keeps the clock time. If it shows only dates, ask for the full timestamp before you build a report on it.
- Check the site's proration mode and when it last changed. A switch from millisecond-based to day-based proration can remove timestamp detail for sites created before May 19, 2026.
- Note the pull time and compare it with the 2–3 hour renewal window.
Also check how your import tool reads shorthand. The same PostgreSQL page explains that "a combination of years and months can be specified with a dash; for example '200-10' is read the same as '200 years 10 months'." A field that looks like a date can be parsed as a duration, so confirm the interpretation before you compare values across systems.
If a row fails any of these checks, do not guess. Mark the row, and trace the value back to the subscription record and the renewal activity before you use it in a report.
Passing the boundary into a CRM
Many teams do not read exports directly. They import the file into a CRM, where a date field may hold only a day. When the field keeps only the date, our example turns into May 18 for the end and May 19 for the start. The CRM then has no record of the one-millisecond gap, and it shows the two terms as neighboring days.
That may be fine for most purposes. Renewal reporting by day is common, and a day-level view can answer which quarter a renewal fell in. It becomes a problem when someone later needs to tell whether a renewal event happened before or after the term closed. If that question depends on the order of events within a single day, a date-only field cannot answer it.
For a CRM, consider storing the full timestamp in a separate column, labeled with the definition the vendor used. Keep the date-only field for day-level views. The two fields then answer two different questions, and nobody has to guess which one a number came from.
Who owns the definition
A renewal end date is clear only when the definition behind it is written down, and in most companies that definition lives in a few people's heads. The billing team knows the vendor's setting. The RevOps team owns the CRM field. Finance uses the figure in a board pack. Each group may read the same date differently, and nobody has recorded which clock time the date stands for.
Assign one owner for the convention. That owner records the vendor name, the definition in use, the proration mode, and the date the setting was last checked. The record should sit where the export is documented, not in a message thread. When a new export arrives, the owner can confirm that the columns still mean what the record says.
The owner should also review the record when the vendor changes a setting. The proration page shows that settings change over time, so the convention needs a date on it.
What this post does not cover
This post covers one definition: the one the proration page calls earlier. It does not describe the current behavior of every site, and it does not explain how any later definition handles term boundaries. If your site runs under a different definition, the two stamps in our example may not appear at all. Check the proration page for the definition your site uses before applying the example.
The post also leaves out time zones and database settings, which depend on the systems in your stack. It notes that the TimeZone configuration parameter can be given in postgresql.conf or in any of the other standard ways described in Chapter 19. The same page adds that "Neither timezone names nor abbreviations are hard-wired into the server; they are obtained from configuration files stored under .../share/timezone/ and .../share/timezonesets/ of the installation directory."
If your export shows times in a zone different from the one the vendor used, confirm the offset with the vendor or with your own system's documentation before you compare dates across files.
Which time to report
When you write a term end into a report, state the convention you used, and state the time, not only the date. For our example, that means writing that the old term closes at its closing stamp on May 18, 2026, and that the next term opens at its opening stamp on May 19, 2026. Anyone reading the report can then see that the two boundaries sit one millisecond apart, and they will not need to rebuild the definition from memory.
Next step: today, pull 5 renewals from your export and run the checks in the list above, starting with the clock time on each end value.
Related guides: Commission accrual: 3 mistakes before quarter-end close · Commission payout time: 5 checks for your monthly run · Compare close dates: 3 rules for date and time fields.
Frequently asked questions
When does a term end under Chargebee's earlier renewal definition?
It ends at the last millisecond of the day before the renewal day. For the example subscription, that is the last millisecond of May 18, 2026.
Do the old and new terms overlap?
No. The old term closes at the last millisecond of May 18, 2026, and the new term opens at the first instant of May 19, 2026, so the two meet without a gap or an overlap.
Can a date-only export show the boundary?
Only partly. It keeps the days but not the clock time, so the closing and opening stamps cannot be seen. Ask for the full timestamp before you build a report on it.