JD Edwards Release 26 in Action: Orchestrator Automation, Approval Delegation Deep Dive & More

JD Edwards Release 26 delivers more than a handful of application updates, it represents a meaningful step forward in how organisations can automate, integrate, and govern their operations inside JDE. While some enhancements are incremental improvements to existing functionality, others reflect years of customer feedback finally making it into the product.

This article accompanies our recent webinar, JD Edwards Release 26 in Action, where our senior consultant Anne Thiele walked through the practical application enhancements and demonstrated real-world Orchestrator automations that Ndevr has built for customers across Australia and New Zealand.

What follows covers the enhancements and examples that deserve more airtime than a single webinar can give them.

What Happens to Orders Already Waiting for Approval When a Delegation Becomes Active?

Based on testing conducted during the webinar, the current behaviour appears to be that existing open orders remain visible to the original approver – they are not automatically reassigned. However, the delegated approver gains the ability to action those orders directly. This means the delegation doesn’t change the approval route or the approver on record; it grants the nominated delegate the authority to approve on behalf of the original approver.

New orders raised during the delegation period are where behaviour differs. Testing after the webinar shows that new orders are assigned to the nominated delegate. Similarly, the routing of workflow notifications and work centre messages during the delegation period are routed to the delegate.

For organisations where there are still gaps, there is a practical bridge available. The JD Edwards Orchestrator can be used to complement the native delegation process – for example, by automatically updating approver assignments when a delegation becomes active, or by sending targeted reminders to the delegate when orders are awaiting their attention. This kind of lightweight orchestration can close the gaps without requiring custom development or waiting for a future release to address them.

The delegation history screen itself is a genuine step forward for governance. It records which orders were delegated, to whom, and when they were actioned, giving auditors and compliance teams a clear, reliable record that simply didn’t exist in earlier releases.

JD Edwards Orchestrator in Action: Four Real-World Automation Examples

One of the most valuable sections of the webinar was a look at what Ndevr’s customers are actually doing with the JD Edwards Orchestrator today, not in theory, but in production. These examples illustrate the breadth of what’s possible when Orchestrator is treated as a serious automation and integration platform rather than a niche add-on.

Automated CPI Rent Escalation for Property and Real Estate Operations

Lease escalations based on Consumer Price Index movements involve a repetitive, time-sensitive process that is easy to get wrong manually, and the consequences of errors can be significant. For one of our property clients, we built an orchestration that retrieves the latest CPI rates directly from an external website, updates the relevant tables in JD Edwards, checks the escalation schedule for new leases, runs the escalation process, and notifies the responsible user when the process is complete.

What began as a complex orchestration has been progressively simplified using logic extensions, which have matured significantly in recent releases. The result is a fully automated end-to-end process that removes manual steps, eliminates the risk of human error, and ensures escalations are applied consistently and on time.

Real-Time Budget Synchronisation Between a Property Development System and JD Edwards

Keeping two systems in sync is one of the most common integration headaches across many organisations. For a property development client running a specialist project management platform alongside JD Edwards, the two systems were chronically out of step, making it difficult to trust the data in either one.

The solution was a two-way Orchestrator integration. When a budget is updated in the property development system, it automatically triggers an orchestration that updates the corresponding budget in JD Edwards. In the reverse direction, at scheduled intervals – and on-demand when needed – JD Edwards assembles Accounts Payable data including payment information and pushes it back to the property system. Both platforms stay current with minimal human intervention, and finance teams can rely on a single source of truth for reporting and decision-making.

Streamlined Billing Runs with Proof-Then-Final Logic

Weekly billing runs were a source of stress and delay for one of our clients, particularly because they operate on direct debits with strict banking windows. Any issues discovered late in the process meant payment delays, compliance risk, and significant pressure on the billing team.

The automation built for this client runs a proof billing cycle automatically at 2:00am on every billing day, and delivers the results directly to the responsible person’s inbox before they arrive at work. If the proof run is clean – which it frequently is, they simply click a button in the email to trigger the final billing run. If there are issues, they can resolve them and still initiate the final run from the same email, at whatever time suits them. The orchestration includes logic to prevent duplicate billing runs, manage billing date updates, and handle edge cases in the process. The outcome has been a material reduction in stress for the billing team and a consistently faster path to getting funds cleared.

Third-Party Procurement Software Integration

Not every JD Edwards customer uses JDE’s native procurement module exclusively. For clients with specialist procurement needs third-party procurement platforms are sometimes the right answer.

Integrating those platforms with JD Edwards has historically been a significant technical undertaking. Using Orchestrator, Ndevr built a bi-directional integration for one such client that handles supplier master data and contract information flowing into JD Edwards, and delegation of authority data and financial information flowing back to the procurement platform. The integration is fully automated, handles the business logic required to reconcile differences between the two systems’ data models, and operates without manual intervention.

JD Edwards Enterprise Process Modeller: Now Covering the Full Procurement Lifecycle

The Enterprise Process Modeller has been evolving steadily across recent releases, and Release 26 brings a meaningful expansion to what it can map and analyse. Where previous versions allowed modelling of requisitions, purchase orders, and sales orders independently, and a subsequent release introduced the ability to connect requisitions through to purchase orders as a single flow, Release 26 now extends that chain to include approvals, receipts, and voucher matching.

The practical significance of this is considerable. Organisations can now model their entire procurement process – from the moment a requisition is raised through every approval step, the generation of the purchase order, goods receipt, and final invoice matching — and use the analytics layer to identify where bottlenecks are occurring in practice. This kind of end-to-end process visibility has historically required external process mining tools or significant manual analysis. Having it available natively within JD Edwards, drawing on live transaction data, is a genuine capability uplift for procurement and operations teams.

JD Edwards Release 26 Sustainability Framework: What Organisations Should Know

Oracle has significantly expanded the sustainability framework in Release 26, providing a broader platform for organisations to capture the relevant data from across their organisation, measure, and report on environmental, social, and economic impacts. While adoption among JD Edwards customers is still in its early stages, this is an area that is likely to attract growing interest as ESG reporting obligations continue to develop across Australian and New Zealand industries.

For organisations that are beginning to think about how JD Edwards can support their sustainability reporting requirements, this is worth exploring sooner rather than later. Contact our team if you’d like to understand what the expanded framework covers and how it might apply to your organisation.

Additional JD Edwards Release 26 Application Enhancements Worth Noting

Beyond the headline items, Release 26 includes several targeted enhancements across other modules that are worth being aware of.

In Sales Order Management, users working with Return Material Authorisation processes now have greater control over where location data is retrieved from. A new processing option on the RMA Revisions application allows organisations to choose between pulling location information from the sales ledger or from the RMA default location — giving teams more flexibility in how returned goods are processed and tracked.

In Real Estate and Lease Accounting, organisations can now account for Guaranteed Residual Value across both the right-of-use asset and the lease liability, rather than the lease liability only. This is enabled via a processing option on the Lease Master Maintenance program and will be of direct relevance to organisations with significant lease portfolios where residual value treatment has an impact on reported asset values.

In Transportation, the integration with Oracle Transportation Management Cloud has been updated to align with OTM Cloud Release 23C, ensuring that customers running this integration remain current and supported.

JD Edwards Orchestrator as the Enabler for AI in JDE

One point that is easy to overlook is that the JD Edwards Orchestrator is not just an automation tool, it is the mechanism through which Oracle delivers AI capabilities into JD Edwards. Document Understanding and OCI AI services, are all surfaced through the Orchestrator framework.

This has practical implications for how organisations should think about their Orchestrator maturity. Businesses that invest now in building Orchestrator capability, whether through internal development or with the support of a specialist partner, are not just solving today’s automation problems. They are building the foundation on which AI-powered workflows will run when those capabilities are ready to be deployed in their environment.