Oracle JD Edwards and AvidXchange integration

What moves between them

Vendor master records and the chart of accounts move from Oracle JD Edwards into AvidXchange so AP staff can code and route invoices against valid payees and accounts. Invoices captured or approved in AvidXchange can be written into JD Edwards as AP vouchers through an orchestration, and after AvidPay executes a payment the settled record, including method, date, and check number or ACH trace, is read from AvidXchange and posted back into JD Edwards as an AP matching document. Vendors are pushed first because a payee must exist in AvidXchange before an invoice can be paid. JD Edwards is polled on a schedule rather than pushed to, since it has no native webhooks.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the JD Edwards side it logs in with the username and password to get a session token, sends it in the jde-AIS-Auth header on every call, and re-authenticates automatically when a request returns the invalid-token response that follows an AIS Server restart or timeout. It accepts the full AIS Server URL per customer, and because the server commonly enforces an IP allowlist the customer's CNC admin must add the connector's egress range or calls are rejected. AvidXchange tokens are sent as headers on each request. Vendors and GL codes are mapped and pushed first so every invoice line references a payee and account that already exists. Writes into JD Edwards go through orchestrations that the customer imports into Orchestrator Studio, since there is no direct table insert, and because JD Edwards has no idempotency header the connector checks for an existing document before creating one. Both systems are pull-only, so payment status and ledger changes are polled on a schedule. AIS Server load returns server errors under pressure, so the connector backs off and retries, and 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 with around four hundred employees runs Oracle JD Edwards EnterpriseOne for finance and procurement and processes several thousand vendor invoices a month across many properties. Before the integration, AP clerks keyed invoices into AvidXchange by hand and re-typed each completed payment back into JD Edwards, with the chart of accounts and vendor list maintained separately in both systems, so coding errors and missing payees were common. With JD Edwards and AvidXchange connected, vendors and GL accounts stay aligned automatically, approved invoices land in JD Edwards as vouchers, and every executed payment posts back to the ledger with its check or ACH detail. The duplicate data entry is gone and month-end close starts with AP already reconciled.

What you can do

• •Push Oracle JD Edwards supplier records into AvidXchange so invoices route to a valid payee before payment.
• •Sync the JD Edwards chart of accounts and cost centers into AvidXchange for accurate invoice coding.
• •Write approved AvidXchange invoices into JD Edwards as AP vouchers through a named orchestration.
• •Read settled AvidXchange payments and post them into JD Edwards as AP matching documents with check or ACH detail.
• •Bridge the JD Edwards session token and AvidXchange company and user tokens, polling both sides on the schedule you set.

Questions

Which direction does data move between Oracle JD Edwards and AvidXchange?

Vendors and GL codes move from JD Edwards into AvidXchange so invoices can be coded and routed. Approved invoices and settled payment records move back into JD Edwards as vouchers and AP matching documents. Payments are executed inside AvidXchange, so the connector reads the completed payment and posts it to the ledger rather than initiating payment from JD Edwards.

How does the integration handle JD Edwards being on-premises with no webhooks?

The connector accepts the customer's AIS Server hostname and port instead of a fixed URL, and the JD Edwards CNC admin must add the connector's egress IP range to the AIS Server allowlist. Because JD Edwards has no native outbound webhooks and AvidXchange has no confirmed public webhooks, the connector polls JD Edwards F-tables on the date-updated field and pulls AvidXchange payment status on a schedule you control.

How are invoices and payments written into JD Edwards?

JD Edwards does not allow direct table inserts over REST, so writes go through named orchestrations the customer imports into Orchestrator Studio, such as the pre-built supplier invoice orchestration. Since JD Edwards has no idempotency header, ml-connector checks for an existing document before creating a voucher or payment record so a retry does not produce a duplicate.