Recurring Client Billing for an Accounting Practice

You have forty-three clients on monthly retainers. The 1st falls on a Saturday. Two clients changed their billing entity last quarter, one wants a PO number on every invoice now, and your senior accountant is on leave. The billing run still has to go out Monday morning, and AP at the larger clients will not pay anything dated later than the 5th. Here is how to run that cycle without it eating a full day.

Lock the client billing register before the month starts

The week before billing day, open your client register and confirm three things per client: the fee for the upcoming period, the billing entity (legal name plus address), and the AP contact. These are the fields that quietly drift. A client restructures, splits a holding company, moves AP from an inbox to a portal, and you only find out when an invoice bounces.

For each client, note the engagement type. A flat monthly retainer bills the same amount every cycle. A tiered retainer changes when transaction volume crosses a threshold. Project work billed alongside the retainer needs separate line items so AP can code it to the right cost centre. If you handle any of this for clients in regulated industries, also confirm whether they need a PO number this month, because procurement policies change at fiscal year boundaries. Our guide to purchase orders covers why this matters more than most senders assume.

Build the template once, clone it every cycle

Set up one master invoice template per client during onboarding, not at billing time. The template carries the client's billing entity, AP contact, payment terms, currency, your bank details, and a standing line item for the retainer. When the cycle starts, you clone the template, set the issue date, increment the invoice number, and you are done with the mechanical part in under a minute per client.

Two things make this work in practice. First, a numbering scheme you can actually scale: a client code plus a year and sequence, like ACME-2025-014, so each client has its own clean series. Second, locked sender details so a junior team member cannot accidentally edit your firm's bank account on an outgoing invoice. JupiterInvoice locks invoice number, issue date, sender details, and bank details once an invoice is issued, which means the cloned template stays safe even if half a dozen people on your team touch it.

Send on the same day, every month

Pick a billing day and hold it. The 1st is conventional but lands on a weekend twice a year and runs into bank holidays. Many firms use the last working day of the prior month for retainers covering the upcoming month, and the 5th for retainers covering the prior month. Either works. What does not work is sliding the date around, because AP teams notice cadence and start querying anything that breaks pattern.

On send day, each invoice goes out as a private link to the client's primary contact and their AP inbox. The link is the part that does the real work. The client opens it without signing up for anything, sees the invoice in their browser, and can add a PO number, update their billing entity, or set a different AP contact directly. You get a notification when they do. If their procurement team needs a specific PO format, the client adds it themselves without a back-and-forth email. The forward to AP step happens on their side, not yours.

Handle the exceptions that show up every month

Three exceptions reliably appear in any recurring book. A client asks to change a line item or a fee mid-cycle. A client adds a PO number after the invoice was sent. A client's billing entity changed and the invoice has the old name on it.

The first creates a new invoice version. The client requests the change, you approve or decline, and if approved the invoice moves from V1 to V2 with a full history. The second and third are amendments to the current version. The client edits the PO or billing entity directly, you get notified, and you can revert with one click if something looks wrong. Keeping versions for content changes and amendments for header fields stops your numbering from getting polluted with cancelled and reissued invoices. Versions versus amendments is worth reading if your current process reissues an invoice every time a client wants a PO added.

Reconcile and chase on a fixed schedule

Two weeks after send, pull a status report. Invoices sitting at Sent (never opened) get a polite nudge to the primary contact. Invoices at Viewed but not Approved get a chase to AP with the link reattached. Invoices at Approved but unpaid get matched against your bank feed on the due date. Doing this on a fixed weekday means nothing rots for a month before you notice.

For firms running this across a full book, our notes on invoicing for accountants and bookkeepers goes into the collaborative parts in more detail. If you handle multi-currency clients, also keep a reference for payment term conventions on hand, because Net 30 in the UK and Net 30 in France are not the same instruction in practice.

When to automate the send step

Once you are past twenty recurring clients, the cloning step is the bottleneck. At that point, the REST API and MCP server let you script the monthly run: pull the client list from your practice management system, generate the invoices, and have the links waiting in your outbox by 8am on billing day. You still review each one before sending. The machine handles the typing, you handle the judgement.

Start your next billing cycle by drafting one invoice from scratch and saving it as your master template for that client. The second month is where the time savings show up.