The Monthly Invoice Run: Issuing for Every Subscriber Without Typing

In a business with twenty subscribers, issuing invoices by hand is an evening's work each month. With two hundred, it is a job. The monthly run - issuing, sending, and handling what failed - is exactly the kind of process that should run by itself, because it repeats, it is predictable, and it is prone to human error.

What does the monthly run have to do?

The sixth row is the difference between a run that works and one that looks like it worked. A failure list nobody opens is worth exactly as much as no list.

How to build it in stages

No project required. You can progress in stages, each standing on its own:

1. Gather every subscriber in one place - even a spreadsheet, at first.
2. Issue from the list rather than from memory. That alone prevents most omissions.
3. Connect charging to the clearing system, so the document is created from the transaction.
4. Turn on automatic sending at the moment of issue.
5. Build a failure report sent to a named person.
6. Add reminders for whoever has not paid, on a defined ladder.

Step three saves the most and is also the most common capability in Israeli systems - linking clearing to documents so every charge produces a document, as covered in payment-to-invoice automation.

What to do with failures

Every monthly run has failures, and that is normal. What is not normal is nobody seeing them. Three categories, each handled differently:

• A charge failure - the card declined. That enters the recovery ladder, covered in the failed standing-order recovery ladder.
• An issuing failure - the customer is missing details, or the amount is not configured. Needs a data fix.
• A sending failure - a wrong address or a full mailbox. Handled like any delivery problem, covered in emailing invoices and proving delivery.

Separating the three matters because they need different people: the first is collections, the second is data, and the third is technical.

What to check after each run

Three minutes and three numbers: how many active subscribers there were; how many documents were issued; how many charges succeeded. If the first two differ, somebody was forgotten or charged twice. If the second and third are too far apart, there is a collections problem to handle now rather than next month.

Mid-month changes

This is where automated runs break, so decide in advance:

• A customer who joined mid-month - charged pro rata, or from next month?
• A customer who cancelled mid-month - charged for the current month?
• An amount change - effective this month or next?
• A pause - what happens during it and what happens on return?

Those four decisions need writing down, because without them every case is decided afresh and differently - and then similar customers get different treatment.

When it stops being manual

The practical sign is when the monthly issuing takes more than an hour, or when a customer has already been forgotten. Either justifies building a run, and the investment repays itself by month two. Under ten subscribers, manual with an orderly list is still reasonable.

What if the amounts differ each month

Many businesses assume a monthly run only suits a fixed amount, which is untrue. Three common patterns still fit a run:

• A fixed base plus usage - a monthly subscription plus accumulated items. The run collects the extras before issuing.
• An amount varying by quantity - by user count, for example. The quantity is read from the system rather than typed.
• Temporary discounts - a three-month discount that must stop by itself. Exactly what gets forgotten when working manually.

The third is the best illustration of why a defined run pays: a forgotten discount runs for a year, and nobody notices because the amount simply looks right.

The three mistakes that cost most

• A cancelled subscription still in the run. The result is an invoice to a customer who left, sometimes a charge too - an awkward conversation ending in a refund.
• A price change effective in the wrong month. Discovered from the customer rather than from a report.
• A document issued and never sent. The money was collected, the customer has no document, and they find out at year end when they go looking.

All three are prevented by the same check: comparing the active subscriber count, the documents issued, and the documents sent. If the three numbers agree, the run is healthy.

What issuing day looks like

In an organised business, issuing day looks like this: the run fires in the morning; a report shows how many documents were issued and how many charges succeeded; somebody reviews the failure list - usually five to ten lines; and the sending goes out. All of it takes twenty minutes. In a business that never built it, the same day is four hours of typing and checking, and one customer still gets missed.

Sources

• PayPlus - standing order management system
• Morning - document issuing and collection
• SUMIT - retainer and standing order system