Adding agents next to Coupa without re-platforming

Coupa remains the system of record

Coupa publishes REST APIs for core procurement objects such as requisitions, purchase orders, invoices, and suppliers. Official documentation describes authentication, pagination, and object fields; it does not prescribe how a third party should run match logic. Stellitron is not claiming a Coupa partnership — connectors are built with your tenant during a pilot, using the scopes your security team approves.[1]

In practice, AP teams already treat Coupa as the place approvals and invoice status live. A useful agent layer reads those same facts, applies your tolerances and contract checks, and prepares an exception packet. Payment timing and supplier communication stay in Coupa unless you explicitly enable a narrow write-back after sign-off.[1]

Choose the objects and the batch

Start with one company code and one supplier category where three-way match pain is visible every month. The read set usually includes purchase orders (header and lines), receiving or accrual evidence, open invoice lines, supplier master identifiers, and the approval state your buyers trust today. Map Coupa field names to the keys your AP export already uses so reviewers can reconcile agent output to the P2P screen they know.

Define the pilot batch upfront: for example every non-PO invoice over a threshold, or all invoices for ten strategic suppliers in the last quarter. Synthetic or anonymised copies of the same shapes are fine for week one. Production pulls wait until field mapping is signed off and the integration user has read-only scopes only.

Name the ProcureAI agents in scope. The Invoice Agent handles line-level match and payment holds when variance exceeds policy. The Contract Agent links price drift to clause language when a PDF is on file. The Recovery Audit Agent can run on an AP payments export in parallel to surface duplicate pairs your team may have missed — still read-only relative to Coupa until you approve any status change.

Where agents sit in the buyer’s day

Agents run in a workspace your AP lead can open beside Coupa. Rules execute first: quantity, unit price, extended amount, duplicate invoice checks. Stellitron Intelligence must quote the PO line, receipt quantity, and invoice line for every finding; a verifier drops claims that are not visible on the documents pulled from Coupa or your export.

Buyers see holds with the same references they would search in Coupa — PO number, invoice number, supplier ID — plus the delta that triggered policy. They release or escalate inside your existing approval path. If you later enable write-back, a payment block or hold reason code posts through Coupa’s API only after that human action, with the agent trace stored next to the write.

Keep contract PDFs and email intake outside the critical path until match is trusted. Many teams stage documents in a secure folder or CLM link the Contract Agent can read while invoice facts still come from Coupa. That separation makes it obvious what is authoritative for quantity and price versus what is interpretive clause text.

Pilot plan and exit criteria

Week zero: security review of the integration user, sandbox sample, and network path if ProcureAI runs in your VPC. Weeks one–two: map fields and replay ten historic exceptions your AP team already resolved — measure whether the agent finds the same break without inventing lines. Weeks three–six: run the live batch in shadow mode (agent proposes, Coupa workflow unchanged), then allow optional hold write-back for a named approver group.

Success means a buyer can open one case, see quoted evidence, and explain the decision in an audit sentence without opening a second system of record. Failure modes to track separately: connector gaps (missing receipts), extraction errors, and narrative claims the verifier correctly removed. Do not expand scope to sourcing or supplier onboarding until match accuracy on the batch is stable.

This article describes a deployment pattern Stellitron uses in enterprise pilots; it is not a guarantee of Coupa API coverage on your edition or region. When a scope is unavailable, exports and scheduled files remain a valid read path while you prove value.