Set monthly client billing dates in Stripe by choosing an anchor date, checking short-month behavior, and confirming the stored time zone.
Key takeaways
- Record the agreed billing date and its reason.
- Explain shorter-month dates before the first charge.
- Check the stored time and name the time zone.
Many of the problems firms run into are not about the amount. They come from the date: a charge that lands earlier than the client expected, or a month-end charge that falls on a different day than the team had written down. A few settings made at the start can head off much of that confusion, and they are easier to set correctly than to explain afterward.
Stripe's documentation explains how the renewal date is set. This post turns that material into 3 rules for monthly fees. Each rule opens with a specific behavior from Stripe's page on setting the subscription billing renewal date. The advice after each rule is general guidance you can adapt to your firm. It goes no further than the quotes it sits beside.
This post covers only how the renewal date is set. It is not legal, tax, or accounting advice about your client agreements, and it does not replace reading the documentation before you configure a live client.
Rule 1: Give each monthly client one anchor date
Each monthly client should have one billing cycle anchor date, set once when the subscription is created. Stripe's documentation states that "A monthly subscription with a billing cycle anchor date of September 2 always bills on the 2nd day of the month." That is the core of this rule.
The anchor is a business choice, so make it on purpose. Consider three things before you pick a day:
- When the client is usually able to pay, based on what you already know about their cash flow.
- When your firm needs the money in the account for payroll or its other bills.
- Which day keeps your month-end close simple for the person who reconciles the account.
Once you have picked a date, write the reason next to it in your client list. A date with no stated reason is easy to change by mistake later, when someone does not know why it was set that way. The reason also helps the next person who takes over the account. Use your client intake checklist to keep the agreed date with the handoff record.
If your clients are spread across several dates, your team can see when cash comes in each month and plan follow-ups for the days before each charge. For example, a firm might anchor one group of clients to the 2nd, another group to the 15th, and a smaller group to a later date. Each group then has a predictable billing day, and the team can plan around those days instead of reacting to them.
Talk to the client before the first charge. If the client has a specific request, such as wanting the charge a few days after their own payroll runs, note the request and the date you agreed on. A written record of the agreed date makes it easier to answer questions in the months that follow.
The same documentation gives a weekly example: a subscription with a billing cycle anchor date of Friday, June 3, "bills every Friday thereafter." That example is about weekly billing, not monthly fees, but it shows that the anchor date is the starting point the schedule follows.
Here is a short checklist for this rule:
- Write the anchor date and the reason in your client list, not only in your billing tool.
- Pick the date with the client's payment pattern and your close schedule in mind.
- If you ever need to change an anchor, tell the client before the next charge so they are not surprised.
Rule 2: Use day_of_month 31 for month-end fees
If a fee should renew at the end of each month, Stripe's documentation says to "Set day_of_month to 31 to create a monthly subscription that renews at the end of the month, even in months with less than 31 days." The same page adds: "If a month has less than 31 days, the subscription renews on the last day of that month."
Your client should know how shorter months affect the date before the first short month arrives, and your team should be able to answer the question quickly when it comes up.
The documentation also gives a different example that uses an anchor date instead of the day setting. It says that "A monthly subscription with a billing cycle anchor date of January 31 bills the last day of the month closest to the anchor date, so February 28 (or February 29 in a leap year), then March 31, April 30, and so on." Read that as a separate example from the day_of_month rule. Before you rely on either setup, check the dates it produces against the examples in the documentation.
Here is how to apply this rule to your client list:
- Decide for each client whether the fee should follow a fixed day of the month or the end of the month.
- For month-end clients, write the expected date for the first short month in the client list.
- Tell the client, in plain words, how shorter months affect their charge date. A short note at setup can save a question later.
Month-end billing is also easy to misread on a calendar, because the date changes from month to month. Keep the rule written down next to the client's name, not only in your head. When a team member is out, the next person should be able to see the expected date without guessing.
Illustrative example: review a client group
Suppose you review 10 monthly subscriptions. Of these, 5 need month-end billing and the remaining 5 use a fixed day. Record the expected first short-month date for the month-end group. For the fixed-day group, compare each agreed date with its stored anchor. Check the stored time and zone for both groups, then note any mismatch beside the subscription before explaining the schedule to the client.
Rule 3: Check the stored time and time zone
Confirm the stored time, not only the day, because Stripe's documentation gives an example of a time recorded in a different zone. It says: "if you create a subscription using billing_cycle_anchor_config at 5 PM EST without specifying the hour, the time is recorded in the system as 10 PM UTC."
In that example the date stays the same, and only the clock time changes. A renewal that you think happens in the late afternoon may look different when you read the record in UTC. This is the reason to check the time as well as the day when you set up a client. The day can look right while the hour is read in the wrong zone.
When the time zone matters for a client, a simple habit is to write the hour in both the local zone and UTC on the client list. That note lets anyone reading the stored record match it to the time the client has in mind.
Here is how to apply this rule:
- Agree within your team which time zone you will read renewal times in, and write that zone on the client list.
- When you set up a subscription, check the stored time as well as the day.
- If your firm and a client are in different zones, name the zone whenever you talk about the charge date, so both sides mean the same hour.
Check what your own account view shows, and do not assume it matches the UTC value in the example.
Today, choose a monthly client and compare the agreed billing schedule with the subscription's stored settings. Record any difference before answering a question about the next charge.
What should the team tell a client who asks about the date?
Give the client the anchor date or month-end rule for their subscription, along with the next expected charge date from your client list. Answer in plain words, and say which setting produces the date, so the client can see it is planned rather than arbitrary.
Do not promise when the client's bank or card issuer will show the charge. The advice in this post covers only how the renewal date is set. Keep the answer to the date your own records show.
If the question is about a date that does not match the client list, do not guess. Check the subscription's anchor date, day setting, and stored time first, then reply with the cause you found. If the cause is not clear, record the question and the subscription so it can be looked at before the next charge.
Do the weekly and yearly examples change the monthly rules?
No. The weekly and yearly examples in Stripe's documentation are about other billing cycles, so they do not change the monthly rules above. They are still useful for understanding how anchor dates and day settings work.
The yearly example says: "To cycle your yearly subscriptions on the first of July, create a yearly subscription with a month of 7 and day_of_month of 1." The documentation also gives a two-month example: "assume that you create a two-month interval subscription in February and you cycle it at the end of every month by setting day_of_month to 31."
If your firm only bills monthly fees, you can skip these examples. Keep the page bookmarked anyway, in case your package structure changes later and you add annual or multi-month plans. When that happens, read the matching example before you set up the new plan, rather than copying the monthly settings across.
How to set up each client in one pass
For each client, record one anchor date, one month-end decision, and one time check before the subscription goes live. Doing all three at once is easier than fixing them after the first charge, and it leaves one clear record for the team.
- Pick the anchor date and write the reason next to it, as described in Rule 1.
- Decide whether the fee follows a fixed day of the month or the end of the month, as described in Rule 2.
- Check the stored time and note the time zone you will read it in, as described in Rule 3.
- Add a line to the client list with the first short-month date you expect, so anyone answering a question can check it quickly.
A small table keeps that record in one place. The row below illustrates the format only, not settings for any client.
| Client | Anchor date | Month-end fee | Time zone noted | First short-month date |
|---|---|---|---|---|
| Example | Date agreed with client | Decision recorded | Zone recorded | Expected date checked |
Keep the client list in one place your whole team can see. A list that lives in one person's notebook can be hard to use when that person is away. The list should also show the date each subscription was set up, so you can tell which settings were made before a later review. Keep this schedule alongside your bank reconciliation checks when reviewing client records.
Check the first renewals after go-live
After a subscription goes live, compare its first renewal dates with the dates you wrote down. Check at least one renewal that falls in a short month, since that is where the month-end rule shows its effect. If your setup lets you test before going live, run the same comparison there first.
If a date does not match, check the anchor date, the day setting, and the time zone before drawing a conclusion. Write the cause in the client list next to the subscription. That note helps the next person who looks at the account, and it shows whether the same mistake could affect other clients.
If the first renewal matches but a later one does not, look at that subscription's settings before you change the rule itself. A mismatch on one account is a reason to check that account's settings first.
Related guides: Client retainers: 3 rules for booking earned income · Accountable plan tests: 3 rules before a reimbursement.