Bi-directional ERP integration means the document automation system both reads from the ERP and writes to it. It reads the purchase order, the goods receipt or the customer record to check an incoming document, and then writes the finished record back, so the ERP stays the single source of truth and the check happens before anything is entered.
One-way integration only writes. The system reads the invoice, extracts the fields and creates a record. It never saw the PO, so it cannot know the price is wrong. That difference is what separates an AI layer for the ERP from a capture tool with an export button.
One-way versus two-way, on one supplier invoice
One-way
The invoice is read. Supplier, date, lines and total are extracted and sent to the ERP. A person then opens the new record, finds the PO, and compares. The keying is gone, the checking is not.
Two-way
The invoice is read. The system identifies the supplier, pulls the open POs and receipts from the ERP, compares each line, stops what does not match with a reason, and enters what does. The checking happened before the record existed.
What the read side makes possible
Matching
Three-way matching needs the PO and the receipt. Without read access there is nothing to match against.
Identification
The sender’s email and the document point to one supplier or customer record. Reading the ERP master data is how the system knows which one.
Duplicate detection
Was this invoice number already entered? Only a system that can read entered invoices can answer.
Updates, not only new records
A supplier’s order confirmation changes a delivery date or a price on an existing PO. Handling purchase order confirmations means updating a record, which needs both reading it and writing to it.
What the write side has to do
Create native records
A purchase invoice, a sales order, a goods receipt, created the way a user would create them, linked to the PO and the receipt, visible to every ERP report.
Carry the decisions
When a buyer approves a price difference, the record shows it. The audit trail lives in the ERP, not in a side system.
Respect ERP rules
Permissions, mandatory fields, validations. A direct connection goes through the ERP’s own logic instead of around it.
How it works with DOConvert
DOConvert is the AI layer for the ERP. It connects directly to Priority through the DOConvert Priority connector, which is bi-directional, and to Oracle Fusion Cloud ERP and Infor M3 the same way, with no middleware. Here is the two-way flow on one invoice.
The invoice arrives and the supplier is identified
From the sender and the document, with no template. The supplier record is read from the ERP.
The PO and the receipt are read
Open purchase orders and goods receipts for that supplier are pulled through the connector.
Every line is compared
Price, quantity, unit and currency against the PO, received quantity against the receipt. Oracle Fusion invoice matching and Priority matching run on the same principle.
Exceptions stop, the rest is written back
What does not match waits for a person with a reason. What matches is created in the ERP as a native record. DOConvert’s listing on the Oracle Cloud Marketplace describes exactly this, bi-directional document processing for Oracle ERP, and the older piece on bi-directional integration with Priority ERP covers the Priority side.
Who it fits
Controllers who want invoices checked against the PO before they are in the ERP, not after.
IT and IS managers comparing a capture tool with an export against a direct, two-way connector.
Operations managers whose supplier confirmations and delivery notes update existing orders.
Companies on Priority ERP, Oracle Fusion Cloud ERP or Infor M3 with 200 to 5,000 employees.
Questions and answers
Is an API connection the same as bi-directional integration?
Not by itself. An API can be used for writing only. Bi-directional means the system actually reads records to check documents before writing.
Does reading the ERP slow the process down?
No. The read happens at the moment the document arrives, and it replaces the minutes a person would spend opening the PO.
Does two-way integration need middleware?
No. DOConvert connects directly, with no Make, n8n or Zapier in between, and the data stays in your environment.
How long does implementation take?
A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers.
Want to see it on your own documents? Book a Demo or Get Started