Modernizing Procure-to-Pay: Coupa + Oracle EBS Cloud Integration

The brief: keep the books, change the front door

Procure-to-pay sits at the intersection of two worlds. The front door — requisitions, sourcing, purchase orders, supplier collaboration — is where employees, line-of- business managers and suppliers actually work. The back office — invoicing, accruals, approvals, payments, reporting — is where finance keeps the books.

Modernizing P2P at a Big-Five bank meant moving the front door to a best-in-class cloud platform (Coupa) without disturbing the back office: Oracle E-Business Suite, hosted by a third party, in the middle of an upgrade to release 12.2.4. The bank wasn't replacing EBS — it was getting a much better user experience in front of it.

The integration shape: cloud front, on-prem hub, hosted back-end

Three planes had to agree on every requisition, purchase-order, invoice and payment.

• Coupa (cloud): the source of truth for requisitions, POs, supplier records and approvals.
• On-prem data hub: the integration conductor, owned by the bank. It receives Coupa events via API, applies bank-specific transformations, then ships the canonical document to EBS.
• Oracle EBS 12.2.4 (third-party hosted): the system of record for accounting, payables, payments and asset-tracking.

The data hub was non-negotiable. With Oracle EBS hosted outside the bank's perimeter, we needed a controlled, auditable point of mediation. Every PO and invoice crossing the boundary passes through it; every transform is versioned; every payload is replayable.

Re-platforming the imaging stack alongside

Invoice imaging didn't escape the program. The existing imaging and workflow system (a Kofax-family P2P automation product, deeply integrated with the prior EBS front-end) had to be re-integrated with Coupa for capture and routing, and with the upgraded EBS for posting and archive.

This was the easy thing to underestimate. Imaging is rarely glamorous on the project plan, but invoice processing volumes are unforgiving: a broken imaging pipeline shows up immediately as late payments and supplier complaints. We treated imaging as a first-class workstream — separate cutover plan, separate parallel run, separate Architecture Review Board approval — not a footnote on the EBS page.

SSO and mobile, in the same delivery

Two enterprise capabilities lived inside the program because their value depends on the front door being modern. Single sign-onfrom the bank's identity provider into Coupa eliminated yet another login, brought session control under enterprise security, and made supplier collaboration feel like an extension of the bank's own intranet.

Mobile was the second big win. Approvals, expense submission and PO acknowledgement on a phone — gated by enterprise mobility management — turned P2P from something people did at a desk into something that fit between meetings. Adoption metrics moved immediately.

Architecture governance as a delivery accelerator

Every major design decision in the program — the data hub shape, the imaging re-integration, the SSO trust boundaries, the cloud egress patterns into the hosted EBS — went through the bank's Architecture Review Board. That sounds slow. It isn't. Used right, the ARB is the fastest way to get alignment across infrastructure, security, data, operations and finance.

The trick is to bring the ARB problems, not solutions. Walk in with the trade-offs, the rejected alternatives, and the recommendation; walk out with an aligned decision and a queue of stakeholders who now own the answer with you. We mentored junior architects through this process during the program — it's a skill that transfers across every enterprise initiative.

Lessons that travel to other P2P modernizations

• Mediate every cloud↔on-prem boundary. An on-prem data hub between Coupa and EBS was the most important architectural decision in the program.
• Imaging is not a footnote.Plan its cutover with the same rigour as the ERP's.
• Bundle SSO and mobile.They're the visible win for end users — and they're much cheaper to deliver in flight than after.
• Treat ARB approval as a forcing function. The reviews caught issues that would have surfaced in production six months later.
• Don't couple to EBS schemas. The hosted EBS will move underneath you. Couple to its documented APIs and supported integration points.

Considering Coupa, SAP Ariba, or another P2P move?

SEYSO has architected and delivered P2P modernizations integrated with Oracle EBS at Tier-1 banks. If you're evaluating Coupa, SAP Ariba, or another cloud P2P platform — and you've got an existing EBS or SAP back-end you can't disturb — we can help you scope the architecture, govern the program, and deliver the integration backbone.