If you have run accounts payable on Oracle WebCenter, you already know it was never one product. It was a stack: WebCenter Imaging (WCI) holding the invoice images, WebCenter Forms Recognition (WFR) pulling the data off them, WebCenter Enterprise Capture (WEC) bringing documents in by scan and email, and Managed Attachments linking every image back to the E-Business Suite transaction. AP teams spent a decade building their operating rhythm on top of all of it.
Then Fusion enters the roadmap, and a hard fact surfaces that vendors tend to soften: there is no WebCenter in the cloud. When you move to Oracle Fusion Cloud ERP, that AP imaging and forms-recognition layer has no like-for-like cloud successor. You are not upgrading WebCenter. You are decommissioning it.
This isn't a reason to panic. It is a reason to plan deliberately — capability by capability — instead of assuming Fusion "has AP built in."
What WebCenter was actually doing for AP
Before you can replace it, name it. For an AP operation, the WebCenter stack did four distinct jobs:
- Capture — WEC ingested invoices via scanner and the Capture Email Import Processor, turning paper and PDFs into documents in the system.
- Recognition — WFR read those documents, learned supplier layouts over time, and presented the data in a verifier application for an operator to confirm.
- Routing — coding and approval moved through workflow, often handing off to EBS Approvals Management (AME) for the actual invoice approval hierarchy.
- The archive — WCI and WebCenter Content stored every image, and Managed Attachments kept each one retrievable from inside the EBS invoice record for audit.
Each of these is a separate problem on Fusion. The mistake is treating "replace WebCenter" as one line item on the migration plan.
This post goes one level deeper than our overview of the move — if you want the broader picture first, start with Migrating AP from Oracle WebCenter to Fusion Cloud.
Capture: WEC has a partial cloud answer
On Fusion, the closest native capability to WEC plus WFR is Intelligent Document Recognition (IDR) — Fusion's built-in invoice capture and OCR. It handles the front of the funnel: take a PDF, extract header and line data, create an interface record.
What changes:
- Email import moves from WEC's import processor to Fusion's IDR email channel. The plumbing is different; the concept survives.
- Scanning of physical invoices is no longer a first-class WebCenter feature — you scan to PDF and feed the same channel.
What does not fully survive is the depth WFR gave you. IDR is a capable OCR engine, but it is the first stage of AP, not the whole thing. The operational work that filled your team's day still has to live somewhere.
Recognition: WFR's learning loop doesn't transfer
WFR's real value wasn't the OCR. It was the verifier and the way the engine learned supplier layouts over years of corrections. That accumulated learning does not migrate. You start the recognition relationship with each supplier over again.
This is the moment to decide whether you want to recreate "OCR plus a verifier operator," or move to a model where:
- Extraction confidence is scored, and only low-confidence fields surface for review.
- Corrections feed back into accuracy automatically, so the system gets better the way WFR used to — without an operator babysitting every invoice.
Legacy OCR of the WFR generation commonly landed in the 40–70% straight-through range. Modern AI extraction does materially better, which is the difference between a verifier queue that shrinks and one that never does.
Routing: AME is gone — model authority deliberately
WebCenter routing, often feeding EBS AME, encoded years of undocumented approval exceptions. None of that comes with you. Fusion has its own approvals framework, and rebuilding your hierarchy there is unavoidable work.
Treat it as a feature, not a chore. The cutover is your one clean chance to:
- Re-derive who can approve what, explicitly, instead of inheriting rules nobody remembers writing.
- Replace the shared work pile with structured, per-approver queues, so an invoice sits in front of exactly one accountable person.
- Decide where exceptions go before they pile up — a real exception queue, not an inbox.
The archive: Managed Attachments has no direct twin
This is the capability most teams forget until an auditor asks for an image. Managed Attachments made every invoice document retrievable from inside the EBS form. On Fusion, you attach documents to the transaction differently, and the underlying store is typically OCI Object Storage rather than WebCenter Content.
The requirement is unchanged even though the mechanism is: every invoice image must remain attached to its Fusion transaction and retrievable for audit. Confirm this is handled and tested before go-live, not discovered after — image continuity is exactly the kind of gap that doesn't show up until quarter-end.
What "good" looks like on Fusion
The goal is not to rebuild WebCenter feature-for-feature. It is to land on Fusion more automated than you left, using methods Oracle actually supports so your quarterly Fusion updates stay boring. In practice:
- Capture and code invoices automatically — PO and non-PO alike — past what raw OCR delivers.
- Match and route with tolerance handling and per-approver queues, not a shared pile.
- Prevent exceptions upstream by resolving the supplier inbox — status chasing, missing PO numbers, duplicates — against live ERP data before invoices ever enter a 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 is what carries forward the one thing WebCenter taught us the hard way: integration that respects Oracle-supported patterns is what keeps upgrades from breaking AP. For the connection model, see our Oracle EBS & Fusion integration detail.
Where EZ Cloud fits
Our roots are in Oracle AP going back to the WebCenter era — WCI, WFR, WEC, Managed Attachments, the Financial Image Processing Solutions Accelerator (FIPSA), and the AME workflows behind them. We have lift-and-shifted these workloads to OCI and rebuilt the AP operation on Fusion when WebCenter had no cloud successor to migrate.
We deploy OCI-native inside your tenancy, post into Fusion using Oracle-supported methods, and add the operational layer Fusion doesn't ship: structured approval queues, exception handling, and AI email exception prevention that takes the supplier inbox off your team. We're published on the Oracle Reference Architecture for OCI and featured in Oracle's own technical case studies.
If there's no WebCenter waiting for you in the cloud, the smart move is to map every capability you're losing before the Fusion cutover — and decide, on purpose, what replaces each one. That's a conversation worth having early.