What is a Recurring Invoice?
A recurring invoice is an invoice a supplier issues for the same goods or services at regular intervals, such as monthly rent, software subscriptions, retainers, and utilities. Also called a recurring bill, it is predictable by contract, so accounts payable can validate it against the agreement and the previous period rather than against a fresh purchase order each time.
Why a Recurring Invoice Matters
Recurring invoices are among the easiest invoices to process, but they are also easy to process incorrectly. As a result, AP may overlook a subtle price increase, continue paying for a cancelled service, or pay a duplicate invoice for a period already settled. Moreover, these invoices are usually non-PO, so AP has no purchase order to match against and must rely on the contract.
AP manages the recurring invoice register, while the contract owner confirms that each service is still active. For example, a company with 120 recurring vendors averaging $2,500 per month could lose $15,000 monthly if just 5% of them continue billing after cancellation. In addition, supplier statements will not flag these charges because the suppliers believe the services are still active.
How a Recurring Invoice Works
A recurring invoice is validated against the contract and the previous period rather than a purchase order.
- The company records each contract or subscription in a register, including the supplier, amount or rate, billing frequency, start and end dates, price-change terms, and assigned cost centre.
- For each billing period, AP matches the invoice against the register to verify the supplier, service, expected amount within tolerance, and correct billing period.
- A duplicate check confirms the period has not already been invoiced; the commonest recurring-invoice error is the same month billed twice under a new number, a duplicate invoice by another route.
- Invoices inside tolerance and inside the contract term are approved on a light-touch rule, as a non-PO invoice with a known owner; variances route for review.
- Once approved, the invoice posts with the coding stored in the register, and the system marks the period as billed.
- When a period’s invoice is late at month-end, the register drives the accrued expense, because the cost is known even though the document is not.
Recurring Invoice vs Recurring Payment
Frequency |
Recurring invoice |
Recurring payment |
|---|---|---|
| What it is | A document the supplier issues each period | A standing instruction to pay each period |
| Control point | Validation and approval before payment | The authorisation given when the instruction was set up |
| Amount | Can vary with usage or indexation | Usually fixed, or taken as billed |
| Visibility in AP | Each period reviewed and posted | Appears on the bank statement; matched afterwards |
| Risk | Paying a cancelled or duplicated period | Paying without seeing the invoice at all |
A recurring invoice keeps AP in the loop; a recurring payment removes it. Therefore, use standing payments only when the contract fixes the amount and AP still receives the invoice and matches it to the debit afterwards.
Example
Assume a software subscription contract at $4,800 a month, billed on the 1st, with a 5% indexation clause that takes effect in January.
Period |
Invoice amount |
Register expects |
Result |
|---|---|---|---|
| November | $4,800 | $4,800 | Auto-approved |
| December | $4,800 | $4,800 | Auto-approved |
| December, second copy, new number | $4,800 | Already billed | Held as duplicate |
| January | $5,040 | $5,040 (indexed) | Auto-approved |
| February | $5,280 | $5,040 | Held, $240 above contract |
The December duplicate and the February overbilling are the two errors a familiar-looking invoice hides in this example. The register catches both, and the February variance goes to the contract owner with the indexation clause attached.
Common Mistakes
- Approving on sight. An invoice that looks identical to last month’s can still hide a price increase or a cancelled service that the company continues to pay for.
- Leaving recurring invoices out of the duplicate check. Identical amounts and descriptions every month make the period, not the amount, the thing to test.
- Setting up standing payments instead of receiving invoices. The bank pays, AP never sees the document, and the tax invoice needed for recovery may never be collected.
- Forgetting the end date. As a result, invoices may continue arriving even after contracts expire or services are cancelled, unless someone regularly checks the register.
How Reconiva Handles Recurring Invoices
Reconiva’s capture agent recognises a recurring invoice by vendor and pattern, and the approval routing agent applies the rule set for it: expected amount, period and cost centre, with light-touch approval inside tolerance and routing to the contract owner on a variance. Duplicate checks verify the billing period as well as the amount. Consequently, the system holds any invoice that bills for the same month twice, while approved invoices post to the connected ERP with their predefined coding. See approval routing in Reconiva.