Acumatica · Recurring bills

Recurring bills in Acumatica and the duplicates they cause

Recurring bills in Acumatica are AP bills generated on a schedule from a template. The duplicates they cause usually come from the schedule and a manual entry both reaching the ledger.

What Acumatica's documentation says

  1. Recurring bills are scheduled on the Recurring Transactions (AP203500) form; only Balanced documents can be scheduled, and a scheduled document becomes a template with the Scheduled status. Source 1 (opens in a new tab)
  2. Documents generated from recurring schedules do not trigger the Raise an Error on Duplicate Vendor Reference Number error, even though they carry the original's Vendor Ref. number. Source 2 (opens in a new tab)

Checked against the vendor's documentation on Nov 7, 2026. Products change; the vendor's current help is the final word.

How recurring bills work in Acumatica

In Acumatica Cloud ERP, recurring bills are scheduled on the Recurring Transactions (AP203500) form. Only Balanced documents can be scheduled, so the bill has to be complete and in balance before Acumatica will accept it as a schedule. Once it is scheduled, the document becomes a template with the Scheduled status, and Acumatica generates the bills from that template on the dates you set.

That template is the part AP teams underuse. It holds the vendor, the amount, the account coding and the Vendor Ref. number, and it keeps producing bills until someone changes or stops it. The supplier invoice number sits in the Vendor Ref. field on the bill.

There is one behavior worth knowing before you build a control around it. Documents generated from recurring schedules do not trigger the Raise an Error on Duplicate Vendor Reference Number error, even though they carry the original's Vendor Ref. number. The duplicate check that protects manual entry does not fire on scheduled output. If your team relies on that error to catch repeats, it will not catch this kind.

How recurring bills get paid twice

The common case is a schedule that keeps running after the arrangement changes. A lease ends, a subscription is cancelled, a retainer is renegotiated, and the template still sits there with the Scheduled status. Acumatica produces the bill on time, the vendor sends a statement that does not show it, and AP pays the schedule and the statement line both. Nothing in the run flags it because the two entries are not identical in every field.

Re-keyed invoice numbers do the rest. A supplier sends INV-1043 for $2,400 and the clerk keys it as 1043. The schedule carries INV-1043. Now you have two bills for $2,400 with Vendor Ref. values that a person reads as the same and a system reads as different. The same thing happens when the number picks up a space, a leading zero or a suffix like -A.

The vendor record is the other quiet source. The same supplier set up twice under slightly different names, say "Northline Services" and "Northline Services Inc", splits the history. A recurring template points at one record, the manual bill goes to the other, and neither vendor's activity shows the full picture. Re-sent payment runs and statements paid as well as invoices add to it. So do credits that arrive and never get applied, which leave a balance that looks open when it is not.

None of this is exotic. It is ordinary AP work done at speed, and recurring bills make it easier because part of the volume arrives without anyone deciding to enter it.

Controls that help

Start with a schedule owner. Every recurring template on the Recurring Transactions (AP203500) form should have a named person who reviews it each period and confirms the arrangement is still live. That review is cheap and it catches the cancelled subscription before the bill is generated, not after it is paid.

Do not lean on the duplicate reference error as your only check. Since scheduled documents carry the original's Vendor Ref. number and do not trigger the Raise an Error on Duplicate Vendor Reference Number error, build a second pass. Run a match on vendor, amount and a date window, for example plus or minus 10 days, and look at the results before the payment run. Two bills to the same vendor for the same amount inside that window deserve a look, whatever the Vendor Ref. says.

Keep the vendor master tidy. One record per supplier, with the legal name and any trading name recorded so a second setup gets caught at the point of creation. When a supplier statement arrives, reconcile it line by line against the bills in Acumatica rather than paying the statement total. If the statement shows an invoice that is already in the ledger, you have found a duplicate before it costs you.

Finally, clear credits. A credit note sitting unapplied is money you have already been promised. Match it to the open bill it belongs to, and if the bill was already paid, ask the supplier for a refund.

Reviewing recurring vendors

Pull the list of vendors with recurring activity and sort by annual spend. The top of that list is where a duplicate hurts most, and it is usually short enough to review in an afternoon. For each one, confirm the schedule is still needed, the amount is current and the Vendor Ref. number matches what the supplier actually sends.

Then look at payment history for the same vendor and amount appearing twice within a few weeks. A worked case: a monthly retainer of $1,850 runs on a schedule. In March the clerk also enters the supplier's emailed invoice for $1,850 as a manual bill. Both pass, both get paid, and the March statement shows one charge. That is $1,850 to recover, and the supplier will usually credit it once you send the two payment references.

When you find a duplicate, ask the supplier for a credit or a refund in writing and quote both payment dates and amounts. Keep a log of what you have asked for and what came back, because unrecovered credits are the easiest loss to forget. If a bill needs to be voided or reversed, check Acumatica's own help for how that document behaves afterwards rather than assuming. Treat any recovery as working capital and compare it with your own cost of funds before deciding what to do with it.

On a bill in Acumatica, the supplier's invoice number goes in the Vendor Ref. field. Any paid-bills export that includes it, the vendor, dates and amounts can be checked for duplicates.

Questions

Why did Acumatica not flag my duplicate recurring bill?

Documents generated from recurring schedules do not trigger the Raise an Error on Duplicate Vendor Reference Number error, even though they carry the original's Vendor Ref. number. The duplicate check does not fire on scheduled output, so you need a separate review on vendor, amount and date.

Where do I set up a recurring bill in Acumatica?

Recurring bills are scheduled on the Recurring Transactions (AP203500) form. Only Balanced documents can be scheduled, and once scheduled the document becomes a template with the Scheduled status.

What field holds the supplier invoice number on an Acumatica bill?

The supplier invoice number goes in the Vendor Ref. field on the bill. Re-keyed numbers such as INV-1043 and 1043 in that field are a common reason two bills for the same charge both get through.

How do I recover money paid twice to a recurring vendor?

Gather both payment dates, amounts and references, then ask the supplier in writing for a credit or refund. Log the request and the response, and reconcile the next statement line by line against the bills in Acumatica so the credit gets applied.

Updated Nov 21, 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.