For many organizations, Accounts Payable remains one of the most manual and labor-intensive areas of the ERP landscape. Payment batches, flat files, shared folders, bank uploads, exception handling, and manual reconciliation often create delays, increase risk, and consume valuable staff time.
At BLUEPRINT 4D 2026, Andy Cox, Technical ERP and Integration Manager at KIND, shared how his team transformed AP processing by leveraging JD Edwards Orchestrator and REST API integrations to create a fully automated, end-to-end payment process. The result is a streamlined workflow that takes approved vouchers all the way through payment confirmation and general ledger posting with minimal human intervention.
The Challenge: Too Many Manual Touchpoints
Like many organizations, KIND’s AP process relied heavily on traditional batch processing. Payment control groups had to be generated manually, payment files had to be exchanged with banking partners, and resolving exceptions often required both AP and IT personnel to become involved.
The complexity increased because KIND operates across multiple currencies and banking relationships, including U.S., Canadian, and U.K. payments. Managing different bank accounts, payment methods, and file transfers created operational overhead and unnecessary risk. When something failed, AP staff often needed access to technical systems, while IT teams found themselves troubleshooting accounting processes they shouldn’t have to manage.
The goal was straightforward: automate the entire process from voucher approval through payment execution and GL posting while maintaining complete auditability and using standard JD Edwards functionality wherever possible.
Building Automation Around JD Edwards Orchestrator
Rather than introducing third-party payment solutions, Cox’s team chose to use JD Edwards Orchestrator as the central integration engine.
The decision was driven by several advantages. Orchestrator runs natively inside JD Edwards, respects existing security models, supports event-driven processing, and eliminates the need for additional integration platforms or custom middleware. Most importantly, it allowed the team to automate processes while continuing to leverage standard AP applications, payment control groups, write programs, undo functionality, and posting processes already available within JD Edwards.
The architecture places Orchestrator at the center of the process. Outbound payments are generated from JD Edwards and transmitted to banking systems through REST APIs. Once the bank processes those payments, inbound statements and confirmations are returned through another API process, allowing JD Edwards to automatically complete payment updates, exception handling, and GL processing.
Automating the Outbound Payment Process
The outbound workflow begins after AP approves vouchers. At KIND, vouchers originating from Coupa are initially placed on hold and reviewed before approval. Once approved, the automation process can be launched manually through a form extension or automatically through a scheduled orchestration.
The orchestration validates that payments are ready for processing, creates the required payment control records, and launches standard JD Edwards payment programs. Data is then extracted and transformed before being transmitted to the bank through a REST API call.
One particularly practical aspect of the solution is the use of Groovy scripts to transform JD Edwards payment data into the exact format required by the banking partner. Rather than requiring extensive custom development, Cox demonstrated how relatively lightweight Groovy scripting can handle complex field mapping and formatting requirements.
He also noted that modern AI tools significantly reduce the effort required to create these scripts. By providing source and target data structures, AI-assisted development can generate most of the required Groovy code, making integrations more accessible to business analysts and functional teams.
Eliminating Flat Files and Improving Security
A major benefit of the new approach is the elimination of traditional payment files.
Instead of generating CSV files or transferring data through shared folders, payments are transmitted securely using REST APIs over HTTPS with OAuth authentication. Credentials are no longer stored on servers, and all communication is logged for audit and troubleshooting purposes.
This approach improves security while simplifying operations. There are no files to manage, no manual uploads, and fewer opportunities for human error.
At the same time, JD Edwards remains the system of record. Sensitive ERP tables are never exposed externally, and all processing occurs through controlled orchestration services.
Handling Inbound Bank Responses Automatically
The real innovation comes in the inbound processing workflow.
Once payments are processed, the bank returns statement information that identifies successful transactions, failures, and exceptions. Rather than forcing AP users to manually reconcile those responses, KIND created an orchestration that automatically processes every returned transaction.
The bank statement is first stored in a custom staging table. The orchestration then examines each payment record individually, matching it back to the appropriate payment control group within JD Edwards. If a matching payment is found, processing continues automatically. If no match exists, the transaction is flagged and routed through error handling procedures.
For successful payments, the orchestration executes the write process and waits for the associated JD Edwards jobs to complete before continuing. This ensures data integrity while maintaining complete automation.
When a payment fails, the orchestration automatically executes an undo process, updates payment statuses, records error information, and routes the transaction for exception review. AP users no longer spend hours manually reversing payments or researching processing issues.
Why Error Handling Was Built In From Day One
One of Cox’s strongest recommendations was to treat error handling as a core design requirement rather than a future enhancement.
Every step of the process includes validation, exception management, and logging. Custom tables provide visibility into inbound and outbound transactions, while orchestration logic captures detailed error messages and audit information. Media objects can even be used to store application-generated error details directly alongside transaction records for easier troubleshooting.
This approach allows processing to continue even when individual transactions fail. Rather than stopping an entire payment batch because of one exception, each payment is evaluated independently, ensuring all records receive the appropriate status and disposition.
Creating Visibility Through AP Dashboards
Automation alone is not enough—users also need visibility.
To support operations, KIND developed dashboards that track every stage of payment processing. These dashboards display payment status, transaction history, successful payments, rejected payments, and exception conditions. Users can quickly identify issues without needing to search through logs or involve IT support.
The dashboards are powered by lightweight custom tables that consolidate information from both outbound and inbound processing. This provides a complete operational view while keeping the underlying architecture relatively simple.
Key Takeaways for JD Edwards Customers
Cox’s presentation demonstrated that AP automation does not require a major ERP replacement or expensive third-party platform. Organizations can achieve significant efficiency gains using capabilities already available within JD Edwards.
By combining Orchestrator, REST APIs, lightweight Groovy scripting, and thoughtful error handling, KIND created a process that automates payment execution from voucher approval through GL posting. AP teams spend less time running jobs and correcting errors, while finance leaders gain better visibility, stronger controls, and faster processing.
Perhaps the most important lesson is that automation works best when exceptions—not routine transactions—become the focus of human effort. By allowing JD Edwards and Orchestrator to handle the repetitive work, AP staff can concentrate on resolving issues that truly require business judgment.
Want more?
Explore more content and resources to help you get the most from your Oracle investment:
- Visit the Quest Learn Library for blogs, how-to demos, and on-demand sessions.
- Connect with peers in one of our Quest JD Edwards Community User Groups to swap stories, ask questions, and share tips with other users facing the same challenges.
- Bookmark LearnJDE for updates from JD Edwards development.
Not a Quest member yet? Join today and tap into the ultimate Oracle customer network.