Brief

AI Collections: Payment Plans, Promises to Pay, and Escalation Rules

AI collections covers payment plans, promise dates, disputes, and escalation. How those steps run, with links to sourced vendor pages.

Chargebee Arc launch, GlobeNewswire

Open the aging list after cash application has posted, and after disputes are coded. The remaining balances are the ones collections can actually work. An AI collections system then follows a written policy. It offers a plan, records a promise date, or moves the account up the escalation path.

The category definition lives in What Is an AI Agent for Accounts Receivable?. Market context is in the AR Automation Market report. The policy-table detail for plans and promises is in Can an AI Collections Agent Offer a Payment Plan?. This page covers the operating loop around those offers, including disputes, deductions, and short pays.

Payment plans

A payment plan is a schedule of installments taken from a table the credit team already wrote. The agent reads the open balance from the AR system and offers only what that table allows. It does not invent a discount, a term, or a write-off.

Chargebee’s November 18, 2026 Arc launch describes a receivables agent that prepares collections work (vendor claim). That work includes a reply to a promise to pay, or a question about a usage charge. The release says each proposal is accepted, edited, or rejected, and that the agent works inside the company’s own rules and escalation thresholds. Arc was open for early access on that date, at witharc.ai.

If you need the stop conditions for offers that fall outside the table, use the payment plan essay. That essay is the longer treatment of what the agent can put in front of a customer.

Promise-to-pay tracking

A promise to pay is a dated commitment tied to an invoice or account. The useful record is the amount, the date, the invoice, and the customer’s words. On that date, cash application either posts the cash or it does not.

If the cash posts, the promise is complete and the account moves on. If the cash is short, collections stops the full-balance chase and treats the gap as a short pay, a deduction, or a dispute. If no cash arrives, the account follows the broken-promise rule in your policy table.

Escalation rules

Escalation is the written path from a reminder to a collector, a credit manager, or outside counsel. The agent can move an account to the next step when a trigger in that path is met. Typical triggers include a broken promise, a balance above the table, or a request to speak with someone on the team. An account already marked high risk also belongs on that list.

Versapay’s collections page, opened November 19, 2026, describes automated collections, predicted delinquencies, and prioritized high-risk accounts (vendor claim). Esker’s collections page describes configurable strategies, automated reminders, and payment predictions that can reprioritize the call list (vendor claim). Neither page is a substitute for your own escalation table.

Write the owner of each step on the table. The collector takes the account at one threshold. The credit manager takes it at another. Outside referral is a named decision, not a default overnight move.

Disputes, deductions, and short pays

A short pay is a receipt that does not cover the open invoice. A deduction or dispute is a reason attached to that gap, or to the whole invoice. Code the reason before the next reminder goes out.

Once a dispute is on the invoice, collections on that invoice waits until the dispute closes. The open, undisputed balance can still be worked. A deduction claim needs evidence, a decision, and a credit or a denial. The agent can assemble the invoice, the remittance, and the customer’s reason. It cannot grant the credit or close the claim on its own.

Esker’s AR materials describe claims and deductions management alongside collections (vendor claim). Versapay’s home page says customers can resolve disputes in its self-serve portal (vendor claim). Use those features only as the vendor describes them, then keep your own coding rules in the ERP.

What to watch

Watch whether a promise date is checked against a posted receipt, not against a reply in the inbox. Watch how short pays are classified, because a coded dispute and an unapplied underpayment need different next steps. Watch vendor escalation thresholds against your own table, especially on early-access tools such as Chargebee Arc.

Track the 60-plus balance and overall DSO. DSO is a measure across all receivables, not a figure for one aging bucket. On this site, disputed invoices are left out of that overall count, because a live dispute is claims work rather than a late agreed bill.

FAQ

What does an AI collections agent actually do?

It works the undisputed accounts that are ready for collections, under a written policy. It can offer a table plan, record a promise date, and move an account up an escalation path. It stops when the customer disputes, asks for a human, or requests terms the table does not allow.

Does a dispute stop collections on that invoice?

Collections on that invoice stops until the dispute is closed. Other undisputed invoices on the same account can still be worked. The score is cash on the agreed bills, not reminder volume.

Where do payment plans get their terms?

From a policy table the credit team maintains. The longer payment plan essay walks the offer, the promise, and the handoff in detail. Start there before you let an agent speak to a customer about terms.

How does this connect to cash application?

A promise is only kept when cash application posts the receipt. Check the bank posting before you schedule the next reminder.

Sources

  1. Chargebee Launches Arc, A New Agentic Finance Platform (GlobeNewswire, November 18, 2026)
  2. Chargebee Arc early access
  3. Versapay collections
  4. Esker Collections Management