If a person can do it in JD Edwards, an agent can automate it — any application, any batch process, any module. And because work doesn't stop at the ERP's edge, agents also handle the steps around it: email, approvals, reconciliations, documents, and reporting.
Agents operate JD Edwards the way your users do — through E1 applications and batch jobs — so there's no workflow they can't reach. And they keep working where the ERP stops.
If it has a screen, an API, or a batch job — an agent can run it. The same framework that clears an AP inbox can release backorders, chase open POs, or close a period.
AP vouchers, AP reconciliation, and year-end 1099s — built first because they're high-volume and painful. They're examples of the pattern, not the limits of it.
Reads the AP inbox, parses supplier invoices, verifies posted receipts, runs voucher match in P4314 against tolerance, and posts clean vouchers. Exceptions are held with Pay Status H and escalated to your AP Manager by email — the agent executes whichever resolution they pick.
Ties out open AP against the G/L and payment activity: pulls F0411 vouchers and F0414 payments, compares them to the trade-payables accounts in F0911, isolates out-of-balance items by document and supplier, and delivers a reconciliation workpaper with every variance explained or flagged for review.
Runs the full A/P Ledger Method year-end sequence — submits R04514FP and R045151, monitors job queues, pulls the facsimile PDF, then generates one IRS-compliant 1099 form per supplier and emails the batch. A week of January closes in one run.
Agents talk to E1 through the AIS REST layer too: query any table, call business functions, submit UBEs, and run Orchestrator Studio orchestrations on demand — acting on JDE data without screen-driving wherever an API path exists.
Anything requiring judgment goes to a human: structured email with the exact discrepancy and numbered resolution options — the agent executes the reply. Every run closes with a PDF + Excel report tying each action to JDE document keys and who authorized it.
Sales order release, backorder clearing, item master updates, supplier onboarding, period close checklists — any process your team runs in E1 can be decomposed into skills and handed to an agent. Pick the workflow that hurts most.
No middleware rip-and-replace. Agents operate JD Edwards through the same web client your team uses — or through AIS when an API path exists. Below: the AP voucher pipeline as a worked example.
The agent watches the AP inbox, pulls supplier invoices, and parses them into validated, JDE-mapped records — with duplicate checks before anything touches E1.
It signs into the E1 web client, verifies receipts in P43214, and runs voucher match in P4314 — evaluating quantity, price, and extended-amount variances against your tolerances.
Clean matches post automatically. Exceptions are classified (E1–E8), held on payment hold, and escalated to a human with concrete resolution options. The agent never guesses a financial decision.
Every run closes with a full audit report — what matched, what was held, who approved what, and the JDE keys to prove it.
Scripted bots fail on the first unexpected popup. Agents read the screen, understand the business process, and handle the edge cases — escalating to humans only when judgment is required.
Financial decisions are never guessed. Exceptions go to your AP Manager with numbered options; the agent executes only what a human chooses.
No custom objects, no ESUs, no middleware. Agents use the standard E1 web client and the AIS layer Oracle already ships.
Every action lands in standard JDE tables with standard documents — plus a run report tying each step to who (or what) performed it.
Year-end 1099 processing, AP inbox clearing, exception chasing — work that consumed analyst-days becomes a supervised batch run.
Each business process is decomposed into composable skills — small, testable units a Claude-powered agent orchestrates. Add a workflow by adding a skill, not by re-engineering the platform.
Book a working session: watch an agent clear an AP inbox, tie out a reconciliation, or run year-end 1099s live in JD Edwards — then tell us which of your workflows should be next.