Every accounts payable team processes supplier invoices. Few do it well. The invoices arrive by email as PDFs, in a different layout for every supplier, and someone opens each one, finds the purchase order in Oracle Fusion, checks the receipt, and types it in. The ERP is modern. The step before it is still manual.

Oracle Fusion invoice automation is about closing that step. The invoice should be read from the email, matched to the purchase order and the goods receipt in Oracle Fusion Cloud ERP, checked line by line, and entered into Payables only when it is right. That is what DOConvert does, through a direct connection to Oracle Fusion, with no middleware and no template per supplier.

This article covers what the manual process costs the team, what good automation has to do, how the DOConvert flow into Oracle Fusion works, and what to check before you choose a tool.

What the manual process looks like

One clerk, one invoice, ten minutes

Open the PDF. Read the supplier. Search the PO. Open the receipt. Compare forty lines. Type the header. Type the lines. Check the total. Attach the PDF. Next invoice. On a busy day the checks get shorter and the mistakes get in.

The same invoice twice

A supplier sends the invoice, then sends it again with a reminder. Without a check against what is already in Oracle, the second copy gets entered and sometimes paid.

Month end finds the differences

A unit price that moved, a quantity invoiced before it was received, freight that was not on the PO. By hand, these are found by the controller at month end, not when the invoice arrives.

Several entities in one mailbox

Groups running several business units in Oracle Fusion get invoices for all of them in the same inbox. Deciding which entity, which ledger and which currency is part of the manual work.

What Oracle Fusion invoice automation has to do

Read the invoice without a template

Suppliers change layouts. New suppliers appear every month. A tool that needs a template per supplier creates a setup queue that never ends. DOConvert understands the invoice as a document, so a new supplier works from the first invoice.

Find the matching record in Oracle Fusion

The purchase order and the goods receipt already exist in Oracle Fusion. The tool has to find them, by PO number when there is one and by supplier, items and amounts when there is not.

Check before entering

Lines, quantities, unit prices, currency, tax and total against the PO. Invoiced quantity against received quantity. This is the three-way match, and it has to happen before the invoice is entered, not after.

Stop exceptions with a reason

An invoice that does not match is held, with the reason in plain words. Invoiced 500, received 300. Unit price differs from PO line 4. Someone fixes one thing instead of re-checking everything.

Enter directly, with no middleware

The invoice lands in Oracle Fusion Payables with the PO and receipt references, through a direct and bi-directional connection. No Make, no n8n, no Zapier in between, and the data does not leave your environment.

How it works with DOConvert

The flow, step by step

DOConvert is the AI layer for the ERP. It is an Oracle technology partner and is listed on the Oracle Cloud Marketplace.

• The supplier invoice arrives by email, as a PDF or a scan, in any layout and any language
• DOConvert reads it and identifies the supplier, the business unit and the invoice type
• It finds the purchase order in Oracle Fusion Cloud ERP, and the goods receipt for that PO
• It checks every line, quantity, unit price, currency, tax and total against the PO and the receipt
• It checks that the same invoice is not already in Oracle
• Anything that does not match is stopped with a plain reason
• Only a matched invoice is entered into Oracle Fusion Payables, with the PO and receipt references and the PDF attached, so Oracle’s own approval flow runs on clean data

Multi-step flows

The same connection handles the whole purchase flow. Purchase order, goods receipt, invoice, as one flow. Credit notes and non-PO invoices for services follow their own rules, with the exceptions stopped the same way.

What the team sees

The accounts payable team sees a short list of exceptions with reasons, and the documents next to them. Everything else is already in Oracle Fusion. The controller stops finding differences at month end because they were stopped at the door.

Going live

A typical implementation takes about 10 business days. DOConvert runs in the cloud or on your own servers. Groups often start with one subsidiary and expand from there.

What to check before you choose a tool

Questions to ask any vendor

• Does it need a template per supplier, and who maintains them
• Does it read the PO and the receipt from Oracle Fusion before it writes anything
• Does it check the invoice against the record, or does it only extract fields
• What happens when the invoice does not match, and who sees the reason
• Is the connection to Oracle Fusion direct, or is there middleware to maintain
• Where does the data live during processing

Two pages worth reading next

For what finance teams actually need from Oracle AP automation, and what they do not, we wrote a separate piece.

For how the connection is set up without custom development, see Oracle Fusion AP integration without custom code.

Who it fits

• CFOs and VPs Finance on Oracle Fusion Cloud ERP who want invoices checked before anyone approves them
• Controllers and accounts payable managers in companies of 200 to 5,000 employees
• Groups with several business units in Oracle Fusion that get all their invoices in one mailbox
• IT or IS managers who want an Oracle connection that is direct and not another system to maintain

Questions and answers

Does DOConvert replace Oracle Fusion Payables

No. It gets the invoice into Payables already matched and checked. Oracle’s own matching, approvals and payment runs stay as they are.

Do I need to set up templates for my suppliers

No. DOConvert reads the invoice without a template, so a new supplier works from the first invoice.

What happens when an invoice does not match the purchase order

It is held with the reason in plain words. Nothing is entered into Oracle Fusion until someone corrects the document or approves the difference.

Is there middleware between DOConvert and Oracle Fusion

No. The connection is direct and bi-directional, and the data does not leave your environment.

How long does implementation take

About 10 business days for a typical setup, including the connection to Oracle Fusion Cloud ERP.

Want to see it on your own documents? Book a Demo or Get Started