> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# JD Edwards

> Monk integration with Oracle JD Edwards EnterpriseOne

# JD Edwards EnterpriseOne

Monk connects to JD Edwards EnterpriseOne through the AIS (Application Interface
Services) REST server. The integration reads Address Book, Customer Ledger, and
Receipts data so Monk mirrors your receivables without any development work on
the JDE side.

## Supported entities

| Monk entity         | JD Edwards entity                                 |
| ------------------- | ------------------------------------------------- |
| Customer            | Address Book (F0101) + Customer Master (F03012)   |
| Customer contacts   | Who's Who (F0111) + electronic addresses (F01151) |
| Invoice             | Customer Ledger document (F03B11)                 |
| Invoice line        | Sales Order History (F42119)                      |
| Payment             | Receipt Header (F03B13)                           |
| Payment application | Receipt Applications (F03B14)                     |
| Credit memo         | Customer Ledger credit memo (RM)                  |
| Payment terms       | Payment Terms (F0014)                             |

## Authentication

* Connect from **Integrations → JD Edwards** in Monk with five fields: AIS
  server URL, a dedicated service-account username and password, the E1
  environment, and the sign-in role.
* Monk validates the credentials against the live AIS server before saving
  anything; the password is stored encrypted.
* The service account needs read access to Accounts Receivable and Address Book
  data plus Data Browser access — configuration only, no installs.

## Multi-entity, currency, and parent-child

* **Companies:** One Monk org maps to one JDE company. Companies within an
  installation can keep books in different currencies, so each gets its own
  Monk org; use Monk's org hierarchy for roll-up.
* **Currency:** JDE stores every amount in both domestic and foreign currency.
  Monk reads the customer's transaction currency and derives the exchange rate
  from the two amounts, so foreign-currency invoices are never mis-stated.
* **Documents and pay items:** One JDE document (company + document type +
  number) becomes one Monk invoice; its pay items become the invoice's
  installments. Line detail comes from Sales Order History.
* **Discounts:** Discounts actually taken at receipt time are recorded as
  earned-discount adjustments on the invoice rather than as payments.
* **Customer hierarchy:** Monk imports JDE customers as top-level accounts; use
  Monk's customer relationships for roll-up.

## Configuration options

* **Environment and role:** choose which E1 environment and sign-in role the
  service account uses.
* **Historical cutover date:** limit how far back Monk imports invoices and
  receipts.
* **Auto-import:** enable or disable automatic import of new JDE invoices and
  customers.

## Sync and reliability

* Incremental sync on JDE modification dates, with per-table cursors.
* Automatic retry with backoff on transient AIS errors.

## Frequently asked questions

**Do I need to install anything in JD Edwards?**
No. Monk uses the standard AIS REST server. Your administrator creates a
service account and grants Data Browser access — no custom objects.

**Which JDE versions are supported?**
Any EnterpriseOne release that runs an AIS server.

**Can one Monk org sync more than one JDE company?**
One Monk org connects to one company. Connect additional Monk orgs for
additional companies.