Your Customer's AP Just Hired an Agent

A founder I work with runs a 38-person marketing agency at $11M revenue. Three of her largest customers, each over 8% of her revenue, all changed their AP behavior in the last 90 days. Same invoice formats, same PO references, but invoices started getting kicked back for matching errors no human had ever flagged. Her AR clerk spent two weeks resubmitting before someone at one customer told her the truth. Their AP function had moved to an AI agent in February. The agent doesn't read context. It matches fields.

Her DSO went from 41 days to 58 days in a single quarter.

What changed

Three-way AP matching (PO plus receipt plus invoice) is one of the first agentic AI use cases to cross from pilot into production at enterprise and mid-market companies. The work is high-volume, rule-bounded, and the model doesn't need clean prose to do it. Just clean fields. By Q1 2026, early adopters were already routing incoming invoices through an agent layer that sits in front of the AP team.

Agents do what AP clerks used to do, without the soft handling. A vendor name spelled "Smith Co." on your invoice and "Smith Company LLC" in the master vendor file used to get matched by a clerk who knew it was the same vendor. The agent doesn't. It logs an exception and routes the invoice to a human review queue. That queue is now the slow path. Your invoice didn't get rejected. It got deprioritized in a queue you can't see.

Where it costs you

Your customer didn't tell you they automated AP. Your DSO told you.

Three things compound for growing companies selling into mid-market and enterprise customers.

Invoice data has to match the customer's master, not yours. The PO number, the vendor name, the remit-to address, the line-item descriptions. All of it has to tie to the version they have in their system. Anywhere there's a mismatch, the invoice falls to manual review.

Disputes used to be a phone call. They're now a portal submission with structured fields. Your relationship contact has less authority because the work moved to a different team.

Payment terms get enforced literally. If your invoice says NET 30 and the customer's master says NET 60, the agent uses NET 60. That discrepancy used to be cleaned up by an AP clerk who knew you. It's now a ticket waiting in a queue.

What to do this quarter

Pull your three largest customers and ask their AP team whether the AP function moved to an agent or automated workflow this year. If the answer is yes, ask for the exception report on your account. The exception report is the new aging report.

Then audit your invoice file against their master record. Vendor name, character for character. Remit-to address, matched to the W-9 you submitted. PO reference in the field they expect, not the memo line. Agents don't know your company. They know the master record.

Finally, build a relationship at the AP exception-clearing desk, not just with the buyer. The clerk who clears exceptions is the person who now controls your DSO with that customer. A five-minute introduction email this quarter is worth two weeks of DSO next.

Your customer's AP function got faster. Yours didn't.