Coupa invoice automation with AI agents
We build AI agents for the invoice work around Coupa: reading invoices that arrive outside the supplier portal, creating them as draft invoices through the Coupa Core API, attaching the source file, and working the exception queue. Approvals stay in Coupa. The agents use OAuth 2.0 and OIDC clients, since Coupa no longer supports API keys.
For AP and procurement teams on Coupa whose long-tail suppliers still email PDFs, and whose exception queue of held and disputed invoices eats the week.
What we automate in Coupa
The accounts payable cycle from the invoice in the inbox to the payment batch, with your team approving what matters.
- 1
Off-portal invoice intake
Invoices from suppliers who don't use the portal are read from email and created as draft invoices, with the purchase order reference, lines and tax filled in.
- 2
Source file attachment
The original PDF is attached to the invoice through the attachments endpoint, so the approver sees the document and the entered data side by side.
- 3
Exception queue work
Invoices on hold, waiting for receipt or disputed are sorted by cause and routed to the person who can fix them. Each item shows age and owner.
- 4
Dispute drafting
When an invoice doesn't match its order, the agent drafts the dispute with the valid reason code and the differing lines. A buyer or AP lead sends it.
- 5
Approval chasing
Approvers who haven't acted get a nudge with a summary. We can add an approver through the API when your rules call for it, and we record why.
- 6
Supplier follow-up
Missing PO numbers, wrong tax details and unreadable scans become a short, specific request to the supplier, not a generic rejection.
How one Coupa run works
Each step is fixed logic, a model doing the reading, a call to the system, or a person on your team. You decide which steps wait for approval.
Capture · intake agent
Reads the emailed invoice and finds the PO number
Validate · rules engine
Checks supplier, duplicates and tax details
Create draft · coupa integration
Creates the invoice in draft status
Attach · coupa integration
Adds the source PDF to the invoice
Review · your team
AP lead checks the one flagged line, then submits
Coupa invoice, one run
Illustrative- CaptureReads the emailed invoice and finds the PO numberIntake agent
- ValidateChecks supplier, duplicates and tax detailsRules engine
- Create draftCreates the invoice in draft statusCoupa integration
- AttachAdds the source PDF to the invoiceCoupa integration
- ReviewAP lead checks the one flagged line, then submitsHuman in the loop
How the Coupa integration works
We build on the interfaces the vendor documents, and we link the documentation so you can check it.
Coupa runs its own approval chains and tolerance checks, so we don't replace them. The agents work before the invoice enters Coupa, and around the exceptions after it does.
The reference has a bypass-approvals action meant for third-party systems that need an invoice approved and paid quickly. We don't use it. Approvals stay with the people your chain names.
Invoices API
Coupa's reference says POST /api/invoices creates an invoice in draft status. Other actions include update, submit for approval, abandon, add approver, restart approvals and revalidate tolerances.
Invoice statuses
The reference lists statuses including draft, pending_receipt, on_hold, pending_approval, approved, disputed and abandoned. We use them to sort the exception queue.
Attachments API
Files are added with a POST to the invoice's attachments path, after the invoice exists, so the order of calls matters.
OAuth 2.0 and OIDC
Coupa says its Core API uses OAuth 2.0 and OIDC and that API keys are no longer supported. Customers create an OAuth client, and we hold only the client you create.
Vendor documentation we build against
Links open the vendor's own site. Interfaces change, so we confirm current behavior in a sandbox before we build.
What we read and write in Coupa
Reading is the default. Each write has a named gate, so you can see who has to agree before anything changes.
Invoice
Created in draft. Submitted only on agreed rule.
Gate: Approval by Coupa chain
Invoice lines and tax lines
Filled from the document and the PO.
Gate: Low-confidence lines reviewed
Attachment
Source file added to the invoice.
Gate: Logged with the invoice
Purchase order
Read to compare lines, prices and quantities.
Gate: Read only
Supplier
Read to match the invoice. Created only on request.
Gate: AP lead for any new supplier
Dispute
Drafted with the reason code and differing lines.
Gate: Buyer or AP lead sends
Controls and testing
People stay in charge of money and records. The system keeps the evidence.
A scoped OAuth client
Your Coupa administrator creates the client and its scopes. You can revoke it at any time, and the agents lose access at once.
Test instance first
We build against a test instance where your contract provides one, replay real invoices, and compare the drafts with those your team created.
Draft until proven
Invoices stay as drafts for a person to submit until a supplier or invoice type has a clean record. Moving it to auto-submit is your decision.
A log that lines up with Coupa
Each run stores the file, the extraction, the rules and the Coupa invoice ID, so history in Coupa and our log tell the same story.
Where we stop, and what to expect
- Coupa suppliers often send invoices through the portal or e-invoicing already. We only add value for what arrives outside it, and we say so if that is a small share.
- Compliant-invoicing rules vary by country in Coupa. We confirm the required fields for your countries from Coupa's reference, not from memory.
- Date handling is specific. Coupa's reference says to send only the date for invoice dates, since a timestamp can break credit note linking, and we follow that.
Questions about Coupa automation
Can AI automate Coupa invoices?
Around Coupa, yes. The agent reads invoices that arrive outside the portal, creates them as drafts through the Core API, attaches the PDF and works the exception queue. Coupa's own approvals and tolerance checks still run.
Does Coupa still allow API keys?
Coupa's documentation says API keys are no longer supported and that integrations must use OAuth 2.0 and OIDC clients. We set up access that way from the start.
Does this help with Coupa e-invoicing?
It helps with what e-invoicing doesn't cover. Suppliers who send structured invoices through the platform are already handled there. We deal with the PDFs that still arrive by email and the exceptions that follow any channel.
Will the agent approve invoices?
No. It creates drafts, flags problems and reminds approvers. Coupa's reference includes an action to bypass approvals for third-party systems, and we leave it unused.
Do we still need our ERP integration?
Yes. Coupa hands approved invoices to your ERP the way it does now. We work before and around that, and we check that nothing we create changes what the ERP receives.
End-to-end blueprints
Other ERP, accounting and spend integrations
All integrationsNetSuite, QuickBooks, Xero, Sage Intacct, Sage 100, Sage 300, SAP S/4HANA, SAP Concur, SAP Ariba, Microsoft Dynamics 365 Business Central, Workday, Oracle Fusion Cloud ERP, Coupa, Infor, Acumatica, Zoho Books, Zoho CRM, Pipedrive, HubSpot and Salesforce are trademarks of their respective owners. Scenox Studios is an independent company. Product names appear here only to describe the systems we integrate with, and no affiliation, partnership or endorsement is implied.
Tell us which invoices still reach your Coupa team outside the portal.
A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.
What happens next
- 1
Strategy call
We learn how the workflow runs today and what a good outcome would be.
- 2
Workflow audit
We map the process and measure where a system would save the most time.
- 3
Proposal
A written scope, timeline and fixed price for your first system. No obligation to build.