Every finance team on Oracle Fusion has looked at Oracle AP automation at some point. Usually after a month-end where half the supplier invoices were still sitting in an inbox, waiting for someone to find the purchase order and key them into Payables.
The problem is that most of what gets sold as AP automation starts after the invoice is already in Oracle. Approval routing, payment runs, supplier portals. All useful, none of them touch the part that eats the most hours, which is getting the invoice from the email into Payables correctly. This article is about that part, how Oracle Fusion invoice automation fits into the wider AP process, and what to check before you buy anything.
It is written for CFOs, VPs of Finance, controllers and the IT or IS managers who own the Oracle Fusion environment, in companies of 200 to 5,000 employees.
What Oracle AP automation usually covers
Approval workflows
Oracle Fusion Payables already routes invoices for approval. Most AP automation projects start by tuning that, which helps, but only once the invoice exists in the system.
Payment runs and supplier portals
Scheduling payments, early payment discounts, suppliers uploading invoices themselves. Good for the suppliers who use the portal. Most suppliers keep emailing PDFs.
The gap
Between the email and the Payables form sits a person. They open the PDF, find the PO, check the receipt, key the lines, fix the total. That is where the hours go, and it is the step most AP automation leaves alone.
Where the hours actually go
Finding the purchase order
The invoice has a PO number, or it does not. When it does not, someone searches by supplier and amount. When it does, the PO may be in another business unit.
Checking against the receipt
Three-way matching means comparing the invoice to the PO and to the goods receipt. Quantities invoiced against quantities received, prices against the PO, in the right unit of measure. Done by eye, across three screens.
Fixing it after the fact
If an invoice is entered first and checked later, every mismatch becomes a hold, a credit memo or a call to the supplier. Each one costs more than the keying it replaced.
What to look for in Oracle AP automation
It starts at the email
The invoice should be read from the AP inbox without anyone forwarding, saving or uploading it.
It identifies the supplier without a template
A new supplier should work from their first invoice. If each supplier needs a layout set up, you will be maintaining templates instead of processing invoices.
It checks against Oracle before it enters
The PO, the receipt, the lines, the prices, the totals. Anything that does not match should stop with a plain reason, before it reaches Payables. Our Oracle Fusion invoice matching guide walks through what gets compared.
It connects directly
No middleware, no generic automation platform in between, nothing that moves your invoices through someone else’s server. In Oracle Fusion that means a supported integration path, which is what Oracle AP integration without custom development looks like in practice.
It handles more than one business unit
Groups on Oracle Fusion usually run several legal entities. The invoice has to land in the right one, with the right PO. Multi-entity invoice capture is where many tools quietly fail.
How it works with DOConvert
DOConvert is the AI layer for the ERP. It connects directly to Oracle Fusion Cloud ERP, is listed on the Oracle Cloud Marketplace, and DOConvert is an Oracle technology partner. No middleware, and the data stays in your environment. Here is one supplier invoice, from the inbox to Payables.
The invoice arrives
In the AP mailbox, as a PDF, a scan or an attachment. Nobody touches it.
DOConvert identifies the supplier
From the sender address and the document itself. No template. A new supplier works from the first invoice.
DOConvert finds the PO and the receipt in Oracle Fusion
Through its bi-directional connection it reads the purchase order and the goods receipt for that supplier, in the right business unit.
The check
Lines, quantities, prices, currency and totals are compared against the PO and the receipt. A mismatch stops with a short reason, for example a quantity invoiced that was never received.
The entry
Only when everything matches, the invoice is entered into Oracle Fusion Payables, matched to the PO. The AP team sees it in the usual Payables screen and handles only the exceptions. Typical implementation is about 10 business days, cloud or on premises.
Who it fits
- Finance teams on Oracle Fusion Cloud ERP receiving hundreds or thousands of supplier invoices a month by email
- Controllers and VPs of Finance who want every invoice checked against the PO and receipt before it is in Payables
- IT and IS managers who want a direct, supported Oracle integration rather than a custom build or a middleware layer
- Groups with several business units or legal entities on one Oracle Fusion instance
Questions and answers
Does this replace Oracle Fusion Payables approval workflows?
No. Approval workflows carry on as they are. DOConvert takes care of the step before, reading, checking and entering the invoice, so approvals start with a correct invoice.
What happens to an invoice with no purchase order?
It stops with a reason, and the AP team decides. Nothing is entered into Payables until it passes the checks you set.
Do suppliers have to change anything?
No. They keep emailing PDFs as they do today. There is no portal to onboard them to and no template to set up.
Does invoice data leave our environment?
No. DOConvert connects directly to Oracle Fusion, with no middleware, and can run in the cloud or on your own servers.
How long does it take to go live?
About 10 business days for a typical implementation. You can start with one mailbox or one business unit and extend from there.
Want to see it on your own documents? Book a Demo or Get Started