Best AP automation software for Oracle Fusion
Senior Manager Content Marketing at Medius
Hear what's covered in this article:
Evaluating AP automation for Oracle Fusion got harder in 2026, because the usual answer stopped being true. For years the case for a third-party platform started with native invoice capture being weak. Oracle has since replaced that component, which means a comparison built on the old argument will not survive a conversation with your own Fusion administrator.
The useful question now is narrower. Oracle closed the capture gap. It did not close the approval, coding, or exception resolution gaps, and it did not change how Payables generates holds. Where a platform earns its place is in what happens after an invoice is recognized.
What Oracle Fusion automates natively
Oracle Fusion Payables handles supplier records, invoice entry, purchase order and receipt matching, holds, approval routing through BPM, payment execution, and accounting. That has been true for some time. What changed is the front end.
Intelligent Document Recognition, the capture engine most comparisons still describe, has been replaced. Document IO, delivered as part of the Payables Agent, uses large language models to interpret invoice documents rather than matching fields against supplier-anchored truth data. It arrived in release 26A under an early adoption program and became the default for most customers in 26B. Practically, it trains per invoice layout rather than per supplier, so one supplier sending three formats is tracked as three, and it handles multilingual and image-based invoices that previously needed manual correction. Oracle also added anomaly detection, invoice completion for missing internal attributes, and a consolidated exception view.
Teams that evaluated Fusion capture two years ago and found it wanting should test it again before assuming the same result.
Four gaps remain in 26B, based on Oracle’s release documentation and early-adopter reporting. Approval workflow stays in BPM, untouched by the agent. There is no AI-driven account coding for invoices without purchase orders. Exceptions are handled through the consolidated Invoice List, and the agent does not describe a bulk-resolution capability. And ingestion in 26B is email-based, with electronic invoicing limited to a single partner integration. Oracle also notes that its generative AI services are currently available only in its commercial cloud realm (OC1).
Recognition quality also depends on conditions outside the software. Supplier names and addresses need to match what appears on invoices, and purchase order formats on invoices need to match those set up in Procurement exactly.
Where built-in ends and best-in-class picks up.
See where native ERP AP stops and why the needle needs to move further.. Compare Medius to built-in ERP AP across ten capability areas, from line-level matching to non-PO invoices.
Why do invoices pile up in holds?
This is the part of Fusion AP that the Payables Agent did not change, and it is usually what determines how many people you need in accounts payable.
Match level is set on the purchase order line type rather than globally, so two-way, three-way, and four-way matching with inspection can all coexist in the same environment. When an invoice is validated, each tolerance check runs separately and produces its own system hold. Quantity ordered, amount ordered, quantity received, amount received, price, and maximum scheduled amount are distinct holds with distinct codes. A single invoice can carry several at once. System holds are normally cleared by correcting the cause and revalidating the invoice, and manual release is off by default. The Payables interface has no native bulk-release action, and workflow notifications can group only some similar holds.
Tolerances default from Manage Invoice Options in Payables and can be overridden per supplier site. The configuration carries a trap worth knowing about. Each tolerance has an enable flag, and an unchecked flag does not mean zero variance allowed, it means the rule is never evaluated. Unchecking a flag and revalidating releases existing holds of that type, and re-checking it does not reapply them. Invoices have to be revalidated individually or through a service call.
Two mechanics generate more exceptions than teams expect. Maximum scheduled amount tracks cumulative price variance across deliveries, so differences too small to trip anything individually eventually breach the limit. And Oracle prioritizes the purchase order line number on the invoice over the supplier item number, which is why electronic invoices carrying the wrong line reference match to the wrong line rather than failing cleanly.
Automated capture only checks one box. What’s left on the table?
How do your exception rates compare? See touchless and exception benchmarks from Medius customers.
How integrations connect to Oracle Fusion
Fusion exposes three supported integration surfaces. REST APIs handle transactional, real-time exchange. File-Based Data Import handles bulk loads. Oracle Integration Cloud acts as the orchestration layer Oracle points third parties toward.
The reason this matters more in Fusion than in an on-premises ERP is the release cadence. Oracle ships quarterly updates that can change APIs and data models, and those updates are not optional. Integrations built on supported interfaces carry through them. Custom extensions and anything that depends on screen behavior do not. The question worth asking a vendor is not whether they support Fusion, but how long after each quarterly release they certify against it, and what customers do during that gap.
Data has to move both directions. Suppliers, purchase orders, receipts, and the chart of accounts come out of Fusion so the platform can validate against current reality. Approved invoices, coding, approval history, and payment status go back in. In multi-entity environments the platform also has to map business units, ledgers, and legal entities correctly, which is a recurring theme in ERP and AP automation integration and a sharper one in Fusion because the structure is usually richer.
Capabilities that matter most in a Fusion environment
Since native capture is no longer the differentiator, the comparison moves downstream. These are the areas where Fusion environments still apply pressure:
Exception resolution at volume. Fusion has no native bulk-release action for holds, and hold detail is shown one invoice at a time. A platform that lets a reviewer resolve a category of exceptions together, with the invoice, order, and receipt history in one view, addresses a gap in the native solution.
Approval routing outside BPM. BPM rules are capable but maintained by IT, which makes routine changes slow. Routing that finance can adjust, with thresholds and delegation, removes a standing dependency.
Coding for invoices without purchase orders. This is an explicit gap in native functionality. Utilities, services, rent, and subscriptions need coding logic learned from history rather than configured rule by rule.
Multi-entity structure handling. Business units, ledgers, and legal entities carry different approval hierarchies, currencies, and tax treatment. These should be respected rather than flattened into a single model.
Coverage beyond Fusion. Groups that have grown by acquisition rarely run one ERP. A platform that works across multiple ERPs covers Fusion and whatever else is in the estate from one place.
Capture that still earns its keep. Document IO raised the native floor, so capture is now a question of degree. Medius reads line-level detail at invoice capture, which is what makes line-level matching possible rather than header totals alone.
What should you ask before you commit?
Fusion-specific questions separate vendors faster than general AP feature comparisons:
-
Which Fusion release are you certified against today, and how long after each quarterly update does certification follow? Ask what customers experience during that window.
-
Do you integrate through REST, File-Based Data Import, or Oracle Integration Cloud, and what specifically breaks at a quarterly update? A vendor using unsupported access has a maintenance problem they will pass to you.
-
Can match holds be worked in bulk, or one at a time? Native Fusion has no bulk-release action and ties each hold to its own invoice, so this is a real difference rather than a feature checkbox.
-
How do you map business units, ledgers, and legal entities? Ask them to walk through your actual structure, not a two-entity example.
-
How are invoices without purchase orders coded and approved? This is where most remaining manual effort sits once capture is handled.
- What changes if we add an ERP that is not Oracle? The answer reveals whether the architecture is genuinely multi-ERP or Fusion specific.
Medius in Oracle Fusion environments
Medius fits mid-market and enterprise teams running Oracle Fusion Cloud ERP, connecting through a packaged integration rather than a custom build so quarterly updates do not become projects. Matching runs at the line with deviation rules set by supplier or department, exceptions arrive with the order and receipt history attached rather than as a list of holds to clear one by one, and approval routing sits outside BPM where finance can maintain it. For groups running Fusion alongside another ERP, one platform covers both. Teams comparing broader capability can start from the full AP automation feature set.
To see how it handles your environment, book a demo and bring the invoices currently sitting in holds. Those are the ones worth watching a platform work.
Frequently asked questions
Yes, and more than it did. Payables covers invoice entry, matching, holds, approval routing through BPM, payment, and accounting, and the Payables Agent added large language model based document recognition, anomaly detection, and invoice completion. What it does not cover is approval workflow outside BPM, account coding for invoices without purchase orders, and bulk resolution of exceptions. Those gaps, rather than capture accuracy, are what third-party platforms now address.
It depends entirely on how the integration was built. Oracle supports REST APIs, File-Based Data Import, and Oracle Integration Cloud, and integrations using those surfaces generally carry through quarterly releases. Custom extensions and anything depending on screen behavior are the ones that break. Ask any vendor how quickly they certify against each release and what happens between the release and their certification.
Not in the sense of overriding them, and no platform should claim otherwise, since holds exist as controls. What a platform can do is reduce how many are created, by matching at the line with better tolerance handling, and make the remainder faster to resolve by presenting the invoice, order, receipt history, and variance together. Native Fusion requires each hold to be released individually, so the difference shows up in reviewer time rather than in the holds disappearing.
A platform that integrates through published interfaces can serve several ERPs at once, which matters for groups that have acquired companies running different systems. Invoices are captured, matched, and approved in one place, then written back to whichever ERP owns that entity. This is worth confirming specifically, because some platforms are built around a single ERP relationship and handle a second one as a separate implementation.
