For two decades, a lot of Oracle shops ran accounts payable on WebCenter — Imaging for invoice capture and storage, Forms Recognition for data extraction, and a web of routing and annotation tooling bolted onto E-Business Suite. It worked. AP teams built their entire operating rhythm around it.
Then the move to Oracle Fusion Cloud ERP begins, and a quiet problem surfaces: the AP automation layer doesn't make the trip.
What actually leaves with WebCenter
WebCenter wasn't a single feature you could check off and replace. For AP, it was doing several jobs at once:
- Capture — turning a PDF or scanned image into structured invoice data.
- Storage and retrieval — the searchable archive of every invoice image, linked to the transaction.
- Recognition — Forms Recognition learning supplier layouts over time.
- Routing — getting the right invoice in front of the right approver.
When the ERP underneath moves to Fusion, that stack is what you're decommissioning. The instinct is to assume Fusion "has AP built in," so the gap will close itself. It doesn't — not the way an experienced AP team needs it to.
The Fusion gap most teams underestimate
Oracle Fusion Cloud ERP is an excellent system of record. It has a capture capability — Intelligent Document Recognition — that handles the OCR step well. But invoice capture is only the first stage of AP. The operational work that consumed your team on WebCenter still has to happen somewhere:
- Coding non-PO invoices to the right account, cost centre, and project.
- Tolerance-aware three-way matching, and a real queue for the exceptions that fail it.
- Approval routing that reflects how your organization actually delegates authority.
- And the part nobody markets: the supplier email. Status chasing, missing PO numbers, duplicate submissions, banking-change requests — the inbox work that happens before an invoice is ever clean enough to enter a workflow.
A capture engine doesn't resolve any of that. So teams migrate to Fusion expecting parity and instead find they've traded a mature, if dated, automation layer for OCR plus manual effort.
What "good" looks like after the migration
The goal isn't to recreate WebCenter. It's to land on Fusion with an AP operation that's more automated than the one you left — using integration methods Oracle actually supports, so you're not carrying upgrade risk forward.
In practice that means:
- Capture and code invoices automatically, PO and non-PO alike.
- Match and route with tolerance handling and structured, per-approver queues — not a shared pile everyone can pick through.
- Prevent exceptions upstream by resolving supplier email with live ERP context, before invoices enter the workflow.
- Post natively into Fusion via FBDI load with real-time validation over Oracle Integration Cloud (OIC) REST — no custom base-table writes, no brittle middleware.
That last point matters more than it sounds. Integration that respects Oracle-supported patterns is what keeps your quarterly Fusion updates boring — which is exactly what you want them to be.
Treat it as a re-platforming, not a like-for-like swap
The migration is the moment to fix the things WebCenter never did well, not to faithfully reproduce them. A few decisions tend to pay off:
- Clean the supplier master first. Most matching and routing pain traces back to messy vendor data. The cutover is your chance.
- Map approval authority explicitly. WebCenter routing often encoded years of undocumented exceptions. Re-derive it deliberately so the new queues are correct on day one.
- Decide where the image lives. Your auditors still expect every invoice image attached to the transaction and retrievable. Confirm that's handled before go-live, not after.
- Sequence around the ERP cutover. Run the new AP layer in a sandbox against a representative invoice sample well before Fusion goes live, so AP isn't learning two systems at once.
Where EZ Cloud fits
This WebCenter-to-Fusion transition is the exact problem EZ Cloud was built for. We post into Oracle Fusion using Oracle-supported methods, deploy OCI-native inside your tenancy, and add the operational layer Fusion doesn't — structured approval queues, exception handling, and AI email exception prevention that takes the supplier inbox off your team's plate.
We're published on the Oracle Reference Architecture for OCI and featured in Oracle's own technical case studies — and our roots are in Oracle AP, going back to the WebCenter era this article is about.
If a Fusion migration is on your roadmap, the best time to plan the AP layer is before the cutover, not after the gap shows up. That's a conversation worth having early.