A recurring invoice schedule should define five things before it starts: what repeats, when the billing period begins, when the invoice is issued, when payment is due, and what happens when price, scope or payment status changes.
The recurring billing contract
| Decision | Example | Why it matters |
|---|---|---|
| Billing period | First through last day of each month | Defines what the fee covers |
| Issue timing | Five days before the period | Separates service period from invoice date |
| Due terms | Due on the first | Sets collection timing |
| Quantity rule | Fixed seats or usage in arrears | Determines whether the amount can repeat |
| End rule | Until cancelled with 30 days notice | Prevents an endless forgotten schedule |
Set up the schedule
- Create and approve the customer agreement.
- Choose the item, quantity, price, tax and currency.
- Name the service period on every invoice.
- Set start date, frequency, issue timing, due date and end condition.
- Decide whether invoices are created as drafts or sent automatically.
- Test the first cycle and a month-end boundary.
- Assign an owner for failed generation and failed payment.
How proration works
Proration charges only for the part of a billing period used. A simple daily formula is:
Prorated charge = full-period price x active days / total days in period.
A 310 monthly service starts with 10 days left in a 31-day month. The prorated charge is 310 x 10 / 31 = 100.
That is mathematically clear, but contract choices remain:
- Count the start day, end day, both or neither.
- Use calendar days or a fixed 30-day convention.
- Prorate upgrades immediately or from the next cycle.
- Credit downgrades now, next cycle or not at all.
- Round at line level or invoice total.
Write the rule. Two reasonable formulas can produce different amounts.
Price and scope changes
Do not edit an already issued recurring invoice to represent a later plan change. Change the schedule prospectively and issue a credit, debit adjustment or separate prorated line according to the agreement.
Keep the effective date, previous amount, new amount and approval. The schedule is a generator, not permission to rewrite history.
Failed invoices vs failed payments
| Failure | Meaning | Action |
|---|---|---|
| Generation failed | No invoice was created | Repair the schedule and create the missing document once |
| Delivery failed | Invoice exists but did not reach the customer | Correct the address or channel and resend the same invoice |
| Payment failed | Invoice is open and collection attempt failed | Retry under policy and begin reminder sequence |
| Payment pending | Provider has not confirmed success | Leave balance open and wait or investigate |
Dunning without duplicate billing
Retry the payment, not the sale. Keep the same invoice open, log each attempt and stop retries as soon as success is verified. A new recurring cycle can create the next invoice even while the earlier one remains overdue, but the customer balance must show both clearly.
Using Invoice Crowd
Recurring invoices generate documents on a schedule so the customer, amount and terms do not have to be re-entered each cycle. Review active schedules before holidays, price changes and contract renewal dates. A schedule is automation you should supervise, not set-and-forget accounting.
Frequently asked questions
What is a recurring invoice?
An invoice created from a schedule for a repeating customer charge. Each cycle should create its own dated sales document with the service period, amount, tax, terms and balance.
How is a prorated invoice calculated?
A common formula is full-period price multiplied by active days divided by total days in the period. The agreement must also define day counting, rounding and upgrade or downgrade timing.
Should recurring invoices be sent automatically?
Only after the schedule and first cycle are tested. Stable fixed charges can be sent automatically, while variable or approval-sensitive work is safer as a draft for review.
What happens when an automatic payment fails?
Keep the invoice open, record the failed attempt, retry under a defined policy and start the reminder sequence. Do not create a second invoice merely to retry payment.
Can I edit an old recurring invoice after a price change?
Do not rewrite an issued document. Change future schedule cycles and use a traceable credit, debit adjustment or prorated line for the effective-date difference.
How do I stop duplicate recurring invoices?
Give every cycle a unique period key, make generation idempotent, monitor failed jobs, and confirm whether the document already exists before manually rerunning a schedule.
