Setting Up Recurring Billing for Monitoring Clients
Billing · 8 min read
Recurring billing is the entire financial engine of a monitoring agency. Unlike a one-off service, your revenue is the product of caseload size, rate, and — critically — the number of billing cycles that actually get invoiced and collected. Miss a week of invoicing across forty clients and you have lost several thousand dollars that is very hard to recover after the fact.
This guide covers how to set recurring billing up properly: choosing cycles, handling mid-cycle events, automating the invoice and reminder flow, and building the reconciliation loop that keeps every balance accurate.
Pick the cycle per client, not per agency
Weekly is the most reliable cycle for participant-pay monitoring because it mirrors how most participants earn. A $75 weekly invoice is a manageable ask; the same money as a $325 monthly invoice frequently is not. Biweekly suits participants paid on a two-week schedule and halves your invoice volume. Monthly is right for stable earners, third-party payers, and agency or county contracts. Daily billing appears where a court has ordered a specific per-diem rate.
Set the cycle on the participant record at enrollment based on how they get paid, and be willing to change it. If someone is consistently paying half of a monthly invoice, moving them to weekly usually fixes the problem outright rather than escalating it into a collections issue.
Handle enrollment day and proration deliberately
Almost nobody enrolls on the first day of a clean billing period. Decide once how you handle it and apply it consistently: either prorate the first partial period to the actual number of days, or collect a full first period at intake and align the cycle from that date forward.
The second approach is simpler operationally and easier to explain to participants, and it means you have money in hand before equipment goes into the field. Whichever you choose, state it in the intake fee agreement so the first invoice never comes as a surprise. Surprises on the first invoice sharply reduce the odds of ever collecting the second.
Automate invoice generation
Invoices should generate themselves. A scheduled process should run every day, find every active participant whose next billing date has arrived, create an invoice at that participant's rate, set the due date, and send it by email and SMS with a payment link — with no staff member involved.
The rules that matter around that core loop are the exceptions. Paused participants should not accrue invoices; when a case is continued or a participant is temporarily off equipment, pausing must actually stop billing rather than silently accumulating a balance. Discharged participants should stop billing on their end date. A participant with two devices should get one invoice covering both lines, not two disconnected invoices. And the system should never double-generate for a period, even if the job runs twice.
Layer automated reminders on top
An invoice sent once and never followed up is a suggestion. Build a fixed reminder cadence: a notice a few days before the due date, one on the due date, and follow-ups at three and seven days past due. Every message should include the amount, the period it covers, and a one-tap payment link.
Send by both email and SMS, respecting per-participant channel preferences and opt-outs. And make absolutely certain reminders stop the moment an invoice is paid — chasing someone who already paid is the fastest way to make a compliant participant stop trusting your records.
Offer autopay for long placements
For placements measured in months, autopay converts your most predictable revenue into revenue you never chase. The participant authorizes a card on file at intake or through a secure enrollment link, and the system charges it automatically on each cycle date, posting the payment and advancing the due date without any staff involvement.
Handle failures gracefully. Cards decline for ordinary reasons — insufficient balance on payday-timing, expired card, prepaid card limits. The system should retry on a sensible schedule, notify the participant with a link to update the card, and surface a clear list of failed enrollments for staff follow-up rather than silently letting a balance grow.
Close the loop with automatic reconciliation
Recurring billing is only trustworthy if payments post back to the right invoice. The moment a participant pays online, the payment should attach to that specific invoice, mark it paid or partially paid, recompute the client's balance, and advance the next due date. Partial payments in particular need first-class handling — they are extremely common in this industry, and a system that only understands paid-or-unpaid will misreport balances constantly.
Keep a weekly review rhythm regardless: check past-due invoices, clients whose balance is growing across multiple cycles, and any payment not matched to an invoice. In a well-wired system that last list stays empty on its own. Tether Pay runs this entire loop — generation, reminders, autopay, and reconciliation — and pairs it with integrated payment processing so the invoice and the payment are never in two different systems.