ETEXPERIENCE for people ES Book a demo
AI automation

AI agents to automate processes in JD Edwards

An AI agent interprets a request and uses authorized tools in your ERP to complete a task. At End to End, every agent relies on AIS and Orchestrator, runs with the user’s identity and permissions and logs every action; sensitive operations require human approval. JD Edwards remains the system of record.

UserCFO · CIO · Operations
Teams · WhatsAppTelegram · Web
AI AgentLLM · RAG
MCP · AIS · OrchestratorJDE security & roles
JD Edwardssystem of record
The ETEXperience intelligence layer relies on the MCP server, AIS and Orchestrator, respecting the JD Edwards security model. The ERP remains the system of record.

Agents in operation

Customer onboarding from ID scan

Scans an official ID, retrieves the data and creates the customer in the JD Edwards Address Book.

Reading tax status certificates

Reads the tax status certificate (SAT) and automatically fills in the Address Book data.

Account statements and invoicing by email

Generates the customer’s account statement or invoicing and emails it automatically.

From request to execution

1 · Request
The user asks for something from Microsoft Teams, WhatsApp, Telegram or the web, in natural language.
2 · Interpretation
A language model understands the intent and selects the authorized JD Edwards orchestration through AIS.
3 · Execution
The action runs with the user’s credentials and roles, with approval where it applies, and the result returns to the same channel in seconds.

Tools: AIS and Orchestrator

Agents rely on the AIS and Orchestrator your EnterpriseOne already has; document AI runs on our ETECLOUD RAG. Everything goes through JD Edwards APIs, business functions and orchestrations: no backdoors are created.

Identity, approval and traceability

USER IDENTITY Every action runs with the identity, roles and permissions of the requesting user. No generic users.
HUMAN APPROVAL Sensitive operations require approval before they run.
AUDIT LOG Every action is logged and JD Edwards remains the system of record. We operate under ISO/IEC 27001:2022.

Compatibility and requirements

It runs on your current JD Edwards EnterpriseOne 9.2 environment (Tools 9.2.x), relying on Orchestrator and AIS. No migration or changes to your business rules or roles required; it is configured per process, with the permissions you already have.

FAQ

What is the difference between an agent and an MCP query?

The MCP server is read-only: it answers questions with traceable figures and never writes to the ERP. An agent runs a process (approve, release, onboard, reconcile) with the user’s identity and permissions, through AIS and Orchestrator, and with approval for sensitive actions.

How does an AI agent work on Orchestrator?

The agent receives the user request (via Teams, WhatsApp, Telegram or web), interprets it with a language model and runs the corresponding JD Edwards orchestration through AIS, with the user’s credentials and roles. The result returns to the same channel in seconds.

What tasks can be automated?

Today agents onboard customers from an ID scan, read tax status certificates to fill the Address Book, and generate and email account statements and invoicing. Additional automations include vendor onboarding with validation, order releases, AR reconciliation and inventory alerts.

What about JDE security and roles?

The AI layer uses the existing JD Edwards security model: every action runs with the identity and permissions of the requesting user and is logged. No backdoors or generic users.

Does it work with my current release?

Yes. It relies on Orchestrator and AIS from EnterpriseOne 9.2 (Tools 9.2.x) and your current business rules and validations. You adopt AI without changing your ERP foundations.

Automate your first process in a demo.
Book a demo