Oracle E-Business Suite and AvidXchange integration

What moves between them

Two directions. From Oracle E-Business Suite into AvidXchange, ml-connector pushes vendor master records and GL code combinations so invoices can be coded and routed to valid payees and accounts, then submits approved or validated AP invoices, including the PO reference for matching. From AvidXchange back into Oracle E-Business Suite, it pulls settled payment records, the check number, ACH trace, or virtual-card detail, and stages them so the ledger reflects what AvidPay actually paid. Vendors and GL codes sync first as reference data; invoices then payments follow on a cadence tied to your AP cycle. Approval routing stays inside AvidXchange, so only the resulting status and payment come back.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the EBS side it logs in for a session token, sends it as a cookie, and attaches the operating-unit and responsibility context on every call, re-authenticating when EBS returns 401 on an expired session. On the AvidXchange side it sends the Company and User tokens on each request. Vendors and GL code combinations are synced first, because a missing vendor in AvidXchange means a payment cannot be routed and an unknown GL code blocks coding. Invoices are submitted as a batch and the connector polls the AvidXchange payment endpoint for status, since there is no webhook on either side. Writing payments back into EBS uses the open interface table, so a 200 from EBS means the row was staged, not posted, and the connector confirms the concurrent program ran before marking the record complete. EBS has no rate limiter and no idempotency key, so ml-connector keeps concurrency low to protect the shared instance and sets the interface SOURCE column plus a natural key to detect duplicate payments. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized property management firm of roughly four hundred staff runs Oracle E-Business Suite for procurement and payables across several legal entities and uses AvidXchange to capture and pay supplier invoices. Before the integration, AP clerks re-keyed vendor changes and GL codes into AvidXchange by hand, exported approved invoices to a file, and typed settled check and ACH detail back into EBS at month-end, which left the payables ledger lagging the bank and prone to duplicate or mis-coded entries. With Oracle E-Business Suite and AvidXchange connected, vendors and GL codes stay current in AvidXchange, approved invoices submit automatically, and settled payments post back into the EBS payment interface against the right operating unit. The manual re-keying is gone and the ledger tracks actual payments.

What you can do

• •Push Oracle E-Business Suite vendor master and GL code combinations into AvidXchange so invoices code to valid payees and accounts.
• •Submit approved AP invoices, with PO reference for matching, from Oracle E-Business Suite into AvidXchange.
• •Pull settled check, ACH, and virtual-card payment detail from AvidXchange and stage it into the EBS AP payment interface.
• •Bridge the EBS session token and operating-unit context with AvidXchange Company and User tokens on every call.
• •Poll on a schedule with low concurrency, duplicate detection, and a full audit trail on every record.

Questions

Which direction does data move between Oracle E-Business Suite and AvidXchange?

Both ways. Vendor master records, GL code combinations, and approved AP invoices move from Oracle E-Business Suite into AvidXchange, and settled payment detail moves from AvidXchange back into EBS. GL accounts are read-only inside AvidXchange, and approval routing stays there, so only the resulting status and payment return to EBS.

How are payments written back into Oracle E-Business Suite?

EBS writes are two-step. ml-connector inserts the settled payment into an open interface table, so a 200 response means the row was staged, not posted. The connector then confirms the concurrent program ran before marking the record complete, and it sets the interface SOURCE column plus a natural key so the same payment is never imported twice.

Do either of these systems support webhooks, or is this polling?

It is polling. Oracle E-Business Suite has no self-service webhook, and AvidXchange has no confirmed public webhook, so ml-connector reads EBS open interface views filtered on last update date and polls the AvidXchange payment endpoint after each batch. The sync runs on a schedule you set, tied to your AP cycle.