Recurring client billing feels simple until the first run. A retainer that goes out on the 1st for one client, on the 15th for another, and "whenever someone remembers" for a third is the setup that produces month-end cleanup. When a partner or operations lead sets up repeating invoices, most of the decisions that matter are about dates. Those decisions often get made in a rush, on the afternoon the first schedule is due to go live.
Key Takeaways
- Give every recurring invoice one fixed run day that exists in every month.
- Set the billing term and its end date before the first invoice goes out.
- Store each price together with its frequency, and record every change with a date.
- Run a test cycle and check edge dates before the schedule goes live.
This post covers three date rules to settle before you switch on recurring billing for clients. None of them requires special software. They apply whether you use an accounting platform's built-in repeat feature, a payment processor's subscription tools, or a spreadsheet and a set of calendar reminders. Where I describe how a specific tool behaves, I link the official documentation so you can check the current version. Software interfaces change, so treat the examples as things to look for, not as instructions for one product's screens.
Small accounting firms face a particular version of this problem. Most clients are billed on a handful of arrangements, the same person often sets up and reviews the schedule, and the staff who answer client questions may not be the people who configured it. The rules below are meant to make the schedule readable to someone who did not build it. Before the first client is even set up, the Accounting Client Intake Checklist for a Clear Handoff covers the intake detail that makes a later handoff possible.
Rule 1: Give every recurring invoice one fixed run day
The first rule is to choose the day a recurring document is generated and keep it. Frappe's Auto Repeat documentation describes the feature this way: "Auto Repeat feature helps you create certain documents automatically in a given time period." Its example for a monthly schedule is clear. If frequency is Monthly and you enter 7, then the system "will generate recurring document on 7th of the respective month" ( Frappe, "Auto Repeat").
A fixed day is easier to reason about than a loose instruction such as "end of the first week" or "after the client sends their numbers." It gives everyone one answer to the question "when does this go out?" When a client asks why an invoice arrived on a particular date, you can point to the schedule instead of reconstructing a decision. When a bookkeeper checks whether the month's billing is complete, they know which date to look at.
Choose the day with two things in mind: your cash flow and the client's payment habits. If a client's accounts-payable team approves invoices on a regular cycle, a run date a few days before that cycle gives the invoice time to be approved and scheduled. That is a judgment about each client, not a rule from any source, so base it on your own history with them rather than on a default.
Group clients by run day where you can. If twenty clients share the same date, the review happens once, the exceptions are visible in one place, and the firm has one date to protect when a deadline gets tight. Scattered dates mean scattered checks, and scattered checks are where mistakes hide.
Consider a small example. Suppose a firm bills three clients: one on a monthly bookkeeping fee, one on a retainer for payroll support, and one on a monthly advisory fee. If all three run on the 3rd, the operations lead checks one list on one morning and sees every exception at once. If they run on three different dates, the same check takes three passes, and a missed change on the second date may not surface until a client calls. Nothing about the amounts changed. Only the number of places a person has to look did.
Decide in advance what happens when a run date falls on a day your office is closed. Whether the invoice should go out earlier or later is a firm policy choice, not something the software should decide by accident. Write the choice down next to the run day, and make sure every person who answers client questions knows it.
Now the harder part: months are not the same length, and a run day late in the month needs a test. The Frappe documentation includes an end-of-month example that shows why. It notes that "in a leap year last day of Feb is 29th, and it is 28th otherwise" ( Frappe, "Auto Repeat"). The example is about the last day of the month, and it shows that the date that counts as "end of month" changes for February from one year to the next. A fixed day such as the 7th does not raise that question, because every month has a 7th.
So before you use a late-month run date, such as the 29th, 30th, or 31st, check how your tool handles months that do not have that day. Do not assume the software will do what you expect. Create a test schedule, let it run through a short month or a leap-year February, and record the result. Write the observed behavior in your internal notes. That note answers the question the next person will ask, and it protects you when the software is updated.
Some habits make this rule stick:
- Prefer a run day that exists in every month, unless you have tested a later date and written down the result.
- Store the run day in the client record, not only in the software. If the tool is replaced, the date should survive the move.
- Note the time zone and cutoff assumptions. A job that runs late at night on a server in another zone can produce an invoice dated a day off from what your staff expects.
- Review the run day when a client's contact or their payment process changes. A date that worked for one team may not suit the next.
Rule 2: Set the billing term and its end date before the first invoice
The second rule is to decide how long a recurring arrangement lasts and what happens when it ends, before the first run. Recurring setups are easy to create without an end date, and that is convenient on the day you create them, and expensive later, when a client leaves, the scope changes, or a service ends and invoices keep going out.
Stripe's subscription schedules show the value of time-bound pieces. In Stripe's documentation, one example phase "lasts for 12 months and then releases the subscription from the schedule" ( Stripe, "Subscription schedules"). The useful part is not the specific length. It is that the end of the phase is a defined event the system acts on, not a decision someone has to remember to make.
You do not need a payment processor to apply the same idea. Write the term into the engagement letter or the client record: start date, length, and what happens at the end. Then make the recurring schedule match that term. If the engagement covers a fixed period, the billing should stop when the period ends, not at an open date that someone has to remember to close. The Engagement letter: 6 terms to settle at intake covers where this belongs.
A term also gives you a natural review point. Put the renewal review on the calendar before the final scheduled invoice of the term, so the decision to renew, change, or end is made before the next run is already queued. Renewals are a common time for prices to change, so the review and any price update should happen together rather than in separate conversations weeks apart.
Decide, too, who owns the stop. In many small firms, the person who set up a recurring item is not the person who hears about a client's cancellation. If the stop date lives only in one inbox, the invoice keeps going out. Put the end date in a shared place and name the person responsible for acting on it. A simple line in the client file works: the fee ends on a stated date, the owner is a named person, and the arrangement is reviewed before the final run.
Plan for the partial first period as well. A client may join in the middle of a month, and the first invoice may not match the regular amount. You do not need a complicated rule, but you do need one written down before the first run, so the first invoice is not improvised under pressure. The same goes for the last period. When an engagement ends partway through a cycle, the final invoice should follow a rule you can point to, not a guess.
A term shorter than a year still needs the same discipline. Short engagements are often the ones most likely to be forgotten, because nobody plans for their end. A three-month project billed monthly can run for a year if no one sets its stop date when it starts.
When a partner hands a client to a colleague, the term record should travel with the client. Include the start date, the planned end date, the renewal review date, and the name of the person who now owns the arrangement. A handoff that moves the client but not the stop date is one of the most common ways a recurring fee outlives the work it was meant to pay for. If the record cannot be handed over in a few lines, it is probably missing something the next owner will need.
Rule 3: Tie every price to a frequency, and plan changes in advance
The third rule is that the amount and the interval are one decision, not two. Stripe's Invoicing API documentation states the principle directly: "Prices define how much and how often to charge for products" ( Stripe, "Integrate with the Invoicing API"). Whatever tool you use, the amount and the frequency should be stored together, so the schedule and the price cannot drift apart.
This matters in small firms because one client often has several recurring items on different rhythms: a monthly bookkeeping fee, a quarterly review, an annual filing service. Each set up separately can end up on different days or in different batches. The fix is to write each recurring item as one line in a single register: client, service, amount, frequency, run day, term end, and owner. If you can read a line and know exactly when it will bill and for how much, you can audit the whole schedule in an afternoon.
Stripe's subscription schedules also allow more than one phase in an arrangement. The documentation says you "can include up to 10 current or future phases" ( Stripe, "Subscription schedules"). Most small firms will never need ten. The idea still matters: one phase can run for a set length, such as 12 months, so a price change can be planned as a future phase, not as an edit made on the day it takes effect. Planning the change ahead means the client sees the new amount on a date you chose in advance.
The table below pulls together the date-related facts from the sources in this post. Use it as a quick reference for what each source says, and check the current documentation before relying on any of them.
| Source | Setting | What the source says |
|---|---|---|
| Frappe Auto Repeat | Monthly run day | Entering 7 generates the document on the 7th of each month |
| Frappe Auto Repeat | End-of-month example | Last day of February is the 29th in a leap year and the 28th otherwise |
| Stripe subscription schedules | Example phase length | One phase lasts 12 months, then releases the subscription from the schedule |
| Stripe subscription schedules | Phase limit | Up to 10 current or future phases |
Price changes need the same care as the first invoice. Give notice before the new amount applies, and write the change into the client file: the new amount, the effective date, and the reason. Then check the schedule after the change is set, and confirm the new amount lands on the right run, not one cycle early or late. A price change that is correct in the software but unclear to the client still produces a dispute, so the notice matters as much as the setting.
Avoid editing a price on a live schedule without a record. A silent change makes the next audit harder and makes it harder for a colleague to explain an invoice. Keep a dated note of each change, including who approved it and who made it. In a small firm, the approver and the editor are sometimes the same person. That is acceptable, but the note should still exist.
Set a regular review of the register itself, not only of individual invoices. A short monthly pass works well for most firms: compare each line against the engagement records, confirm the run dates and amounts still match, and look for any item whose term end has passed without a decision. The review does not need to be long. Its value comes from happening on a schedule, so that a stale line is caught in the month it goes stale rather than at year end.
Before you switch on recurring billing
Run through these steps before the first automatic invoice goes out. None of them is complicated, and each one catches a problem that is much more expensive to fix after a client has seen it.
First, run a test cycle. Use a test client, a sandbox account, or a draft schedule, and let it generate at least one document. Check the date, the amount, the client name, and the description. Confirm the document looks like what a client would expect to receive. Our Invoice checks: 4 steps before sending a client bill covers that last look.
Second, test the edge dates. If your run day is late in the month, confirm what happens in a short month and in a leap-year February. This is the check the Frappe example points to: the software's handling of end-of-month dates is not something to assume.
Third, confirm the term end. Make sure the schedule stops when the engagement stops, and that a renewal reminder sits on the calendar ahead of the last run. Check that the reminder goes to a named person, not to a general inbox that nobody watches.
Fourth, name the owner. Write down who can change the schedule, who approves price changes, and who handles client questions about an invoice. Put those names in the same place as the register from the third rule.
Fifth, write the one-line record. For each recurring item, the register should show client, service, amount, frequency, run day, term end, and owner. If someone new took over tomorrow, could they find out what bills, when, and why from that line alone? If not, add what is missing.
Sixth, decide how clients will hear about the schedule. A short written notice that explains the billing date, the amount, and who to contact prevents most surprise questions. Send it before the first run, not after the first complaint.
Seventh, watch the first real run. Do not walk away after switching the schedule on. Look at the first generated invoice for each client, compare it with the register line, and confirm it appears where your team expects it. Problems found on the first live run are usually small and quick to fix. Problems found three months later are usually tangled up with other work.
Common mistakes to avoid
Several mistakes come up again and again with recurring billing, and each one is tied to one of the three rules.
The first mistake is choosing a late-month date without testing it. The fix is in Rule 1: a short test costs little, and the result is a note you can reuse.
The second is leaving the term open. An open-ended schedule feels like less work on day one, but it adds a recurring review task that someone has to remember. The fix is in Rule 2: put the end date in the record and name the owner.
The third is treating amount and frequency as separate. When the price is recorded in one place and the rhythm is stored in another, the schedule can bill correctly and still be wrong. The fix is in Rule 3: store them together and keep a dated note of changes.
The fourth is relying on memory. Small firms are busy, and memory is the first thing to fail when a partner is out or a staff member leaves. Anything that matters for billing should be in a register, a client file, or a calendar that someone else can read.
The fifth is failing to revisit the schedule when the client changes. A new contact, a new payment team, or a new services mix can all make an old run date or price stop fitting. Put a standing review on the calendar, and treat any client change as a reason to check the schedule.
Worked example
A firm runs three monthly items. All three use the 3rd as the run day, a term ending on a stated date, and a register line that names the owner. When February arrives, the late-month item is absent, so the team has already tested how the tool behaves and written the result down. The renewal review sits on the calendar before the final run of the term, so no invoice queues while a decision is still open. One list, one morning, every exception visible.
Start with the calendar, then the software
Today, pick one client and write its register line: client, service, amount, frequency, run day, term end, and owner. That single line is the whole starting move, and it needs no new software.
The three rules come down to a simple order of work. Choose the run day and test it. Set the term and the end date. Tie each price to its frequency and write down every change. Only after those are settled should you turn on automatic generation. Software carries out a schedule, but it cannot decide what the schedule should be. That decision belongs to the partners and operations leads who know the clients.
Recurring billing done this way is less exciting than adopting a new tool, and it is much harder to get wrong. Settle the dates first, and the rest of the setup gets simpler.