Supplier invoices arrive by email as PDFs. Someone in accounts payable opens each one, looks up the purchase order in Oracle Fusion, checks the receipt, compares the lines, and enters the invoice. On a quiet day it takes a few minutes per invoice. On a busy day the pile grows and the checks get thinner.

Oracle Fusion invoice matching can run automatically. DOConvert reads the invoice from the email, identifies the supplier, finds the purchase order and the goods receipt in Oracle Fusion Cloud ERP, checks lines, quantities, prices and totals, stops anything that does not match with a plain reason, and only then enters the invoice. The connection to Oracle Fusion is direct, with no middleware, and DOConvert is listed on the Oracle Cloud Marketplace.

Below is a plain explanation of what three-way matching is, where it breaks when done by hand, and how the DOConvert flow into Oracle Fusion works.

Three-way matching in plain words

Three documents that should tell the same story

The purchase order says what you ordered and at what price. The goods receipt says what actually arrived. The supplier invoice says what the supplier wants to be paid. When all three agree, the invoice can be approved and paid.

What is compared

• Supplier and PO number
• Item, quantity and unit of measure per line
• Unit price and currency
• Received quantity against invoiced quantity
• Tax, freight and the invoice total

Where Oracle Fusion fits

Oracle Fusion Cloud ERP holds the PO and the receipt. Payables does the final match and the approvals. The gap is getting the invoice from a PDF in an inbox into Payables with the right PO and the right lines, without someone typing it.

What goes wrong when it is done by hand

The PO number is missing or wrong

Many invoices carry no PO number, or the wrong one. The clerk searches by supplier and amount, guesses, and sometimes picks the wrong PO. The match looks fine until the next invoice for the same PO arrives.

Partial deliveries and partial invoices

A PO for 1,000 units ships in three lots. Each lot has its own receipt and its own invoice. Matching lot two by hand means finding the right receipt among three, and the sums rarely line up on the first try.

Price and quantity differences are found late

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

Multi-entity and multi-currency

Groups with several business units in Oracle Fusion get invoices for different entities in the same mailbox. The clerk has to work out which entity, which ledger, which currency, before the match even starts.

How it works with DOConvert

The flow into Oracle Fusion Cloud ERP

DOConvert is the AI layer for the ERP. No template per supplier, so a new supplier works from the first invoice.

• 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, by PO number when there is one, otherwise by supplier, items and amounts
• It finds the goods receipt for that PO and checks received quantities against invoiced quantities
• It checks each line, unit price, currency, tax and total against the PO
• Anything that does not match is stopped with a plain reason, for example invoiced 500 units, received 300, or unit price differs from PO line 4
• Only after the invoice matches, DOConvert enters it into Oracle Fusion Payables with the PO and receipt references, so the approval flow in Oracle runs on clean data

What the accounts payable team sees

Instead of a pile of PDFs, the team sees a short list of exceptions, each with a reason in plain words and the documents next to it. They approve or correct. The matched invoices are already in Oracle Fusion.

Direct connection, no middleware

DOConvert connects to Oracle Fusion Cloud ERP directly through its bi-directional connector. It reads the PO and the receipt and writes the invoice back in the same connection. No Make, no n8n, no Zapier in between, and the data does not leave your environment. DOConvert is an Oracle technology partner and is listed on the Oracle Cloud Marketplace. A typical implementation takes about 10 business days.

For the technical side of the connection, see Oracle Fusion AP integration without custom code.

For groups with several entities, read about Oracle Fusion invoice capture for multi-entity AP.

Who it fits

• CFOs and VPs Finance on Oracle Fusion who want invoices matched before anyone approves them
• Controllers tired of finding price and quantity differences at month end
• Accounts payable teams in companies of 200 to 5,000 employees, including groups that start with one subsidiary
• IT managers who want an Oracle connection they do not have to build or maintain

Questions and answers

Does DOConvert replace the matching in Oracle Fusion Payables

No. It gets the invoice into Payables with the right PO and receipt, already checked line by line. Oracle’s own match and approval flow then runs on data that is correct.

What if the invoice has no PO number

DOConvert looks for the PO by supplier, items, quantities and amounts. If it cannot find a single clear match, the invoice is stopped with that reason rather than guessed.

How are partial deliveries handled

DOConvert checks the invoiced quantity against what was actually received on the PO, so a second invoice for the same PO is matched against the remaining received quantity.

Does it work with invoices in other languages and currencies

Yes. The invoice is read in its own language and currency and checked against the PO currency in Oracle Fusion.

Is there any middleware between DOConvert and Oracle Fusion

No. The connection is direct and bi-directional, and the data stays in your environment.

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