Recurring charges: collections on autopilot
Most of an institution's collections are identical month to month: the same due, the same concept, the same date. And yet, in many administrations, someone types it in again every month — or worse, collects it from memory. A recurring charge is the piece that turns that repetition into a process.
What a recurring charge is
It is a rule, not a charge: «this client, this concept, this amount, every month». The system executes it and generates each period's charge automatically; the client's balance reflects it the same day and the statement tells the story afterwards. Defining the rule once replaces twelve captures a year — per client.
The difference from «remembering to collect» is not just effort: it is uniformity. A rule runs for everyone equally; memory collects first from whoever is nearby and lets the rest slip.
When it fits (and when it does not)
- Maintenance dues and monthly fees: always — they are the definition of recurring.
- Fixed contributions on a regular date: yes, even if the amount changes occasionally; the rule adjusts and keeps running.
- One-off or variable charges — an event, a repair: no. Record them as regular charges; forcing them into a rule creates exceptions nobody remembers.
The rule and the exception
Every real collection process has exceptions: the client who pays yearly, the one with a discount, the one who left in March. A good recurring-charge scheme absorbs them by editing that client's rule — pausing it, changing its amount, ending it — without touching anyone else. The acid test: client A's exception should never force you to review client B.
In the manualRecurring chargesHow to define recurring charges per client, pause them and adjust them.Closing the loop: from charge to payment
The automatic charge solves half the problem; the other half is the payment arriving just as automatically. That is where each client's payment link comes in and, for whoever authorizes it, the card on file: the month's charge generates, collects against the saved card, and the balance lands on zero without anyone touching anything — the full collection cycle, on autopilot.
In the manualThe payment portalThe payment link and the card on file, from the client's side.Where to start
Start with the concept that repeats the most: the base due. Define the rule for your current clients at their current amount and let the first month run. The exceptions surface on their own — and each one gets resolved in its own rule, not in a separate spreadsheet.
Collections where charges generate themselves and payments arrive by themselves leave the administrator exactly the work that needs judgment: the exceptions. Everything else is the rule, running.