Definition
A bill for the same charge every period, such as rent, a subscription or a service contract, often entered from a template or scheduled in the ERP instead of keyed each time.
Also called: recurring bill, repeating bill, memorized bill, subscription invoice
What it means
A Recurring invoice is the bill you expect to see again. The vendor is the same, the purpose is the same, and the amount often stays the same until someone changes it. Rent and subscriptions are the usual examples. Service contracts too. AP teams also call it a recurring bill, a repeating bill, a memorized bill or a subscription invoice. The label matters less than the setup: the charge is entered from a template or scheduled in your ERP rather than keyed from scratch each period.
The template or schedule is an instruction, not a contract. It tells your ERP to create a bill on a cadence with set coding, terms and often a set amount. That saves time on routine payables. It also means the bill can post without anyone looking at the supplier's latest invoice, the current contract or the vendor record. A Recurring invoice is still a bill. It sits in accounts payable like any other bill and goes through payment unless someone stops it.
Recurring invoices are common on non-PO spend. There is no purchase order to match against, so the control is the schedule itself and the review around it. That is fine when the schedule is accurate. It becomes a problem when the schedule and a supplier invoice both arrive for the same charge, or when the schedule keeps running after the reason for it has gone.
How it works in practice
In practice, someone sets up the template with the vendor, the amount, the coding and the payment terms. Then the schedule posts bills on its cadence. Some teams route each generated bill for approval. Others let it post straight through because it is routine. Either way, the supplier may still send an invoice. That is the point where duplicate payments start. An AP clerk receives the invoice, does not see the schedule, and keys it as a normal non-PO invoice. The schedule has already created a bill for the same service. The vendor record now holds two liabilities for one charge.
Say a service contract is set to recur each period. The supplier emails an invoice each period as well. The clerk keys the email invoice because it is in the inbox. The schedule posts the same charge on its own date. Both bills get approved in different batches. Both get paid. That is a duplicate payment, and it can stay hidden until the supplier statement or the next review exposes it.
Price changes and contract ends are the other daily issue. A vendor raises a price, but the schedule still posts the old amount. Or the contract ends, and the schedule keeps posting because no one stopped it. A Recurring invoice does not know the contract has ended. It only knows the instruction you gave it. At period end, the schedule should be compared with the contract and the supplier's statement of account. That comparison is where stale amounts and stale schedules show up.
Where it goes wrong
A common mistake is treating the schedule as the only source. The supplier invoice arrives, and AP keys it without searching the vendor record for an active schedule. The charge is entered twice: once from the schedule, once from the invoice. That is a classic duplicate payment on recurring spend. It often happens when the invoice goes to a shared inbox and the clerk has no reason to suspect a schedule exists.
Another mistake is letting a schedule outlive its reason. A contract ends, a service is cancelled, or a project closes. The schedule keeps posting. The bill looks normal because the amount and vendor are unchanged. No one flags it. Later, someone compares the vendor statement with the general ledger and finds payments for something the company no longer receives. By then, recovery takes time.
Stale amounts cause trouble too. The supplier changes the price, but the template still carries the old figure. The schedule posts the old amount. The supplier sends an invoice for the new amount, and AP keys it as well. Now there are two bills, and neither matches the contract. Coding can drift the same way. The schedule may post to the same department or account long after the cost should have moved. Recurring invoices deserve a periodic look at amount, vendor, coding and contract status, not just a check that the bill posted.
What to check
Before keying any supplier invoice, search the vendor record for an active schedule. Look for the same vendor and service in the same period. If a schedule exists, do not key the invoice. Compare the invoice with the scheduled bill and decide which one is correct. If the invoice reflects a price change, update the schedule and handle the invoice through the normal approval route. If the invoice is a duplicate, void or hold it before it reaches payment.
At period end, review every active Recurring invoice against the contract and the supplier's statement of account. Confirm the amount and coding. Check the vendor and the end date. Stop schedules when the contract ends. Update them when the price changes. Ask who owns each schedule, because a schedule without an owner is a schedule that keeps running. A short review each period is cheaper than a recovery project later.
Each year, compare recurring charges with the contract and the supplier's statement. This is not a full review. It is a practical check that the schedule still matches what the business agreed to buy. Pay attention to non-PO invoices that repeat. They are easy to pay and easy to duplicate. Keep the vendor record clean, and the schedule will stay useful instead of becoming a source of duplicate payments.
Questions
What is a recurring invoice in accounts payable?
A Recurring invoice is a bill for the same charge every period, such as rent, a subscription or a service contract. AP often sets it up from a template or a schedule in the ERP instead of keying it each time. It is still a bill and still needs review.
How do recurring invoices cause duplicate payments?
The schedule creates a bill, and the supplier also sends an invoice. If AP keys the supplier invoice without checking the vendor record, the same charge is entered twice. Both bills can be approved and paid. Searching for an active schedule before keying prevents most of these duplicates.
Should I stop a recurring invoice when a contract ends?
Yes. A schedule keeps posting until someone stops it or updates it. When a contract ends, stop the schedule and confirm the vendor statement shows no further charge. If the price changes, update the schedule so it matches the contract.
Updated Nov 15, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.