The 26 criteria, one by one
How it touches JDE
Runs inside JD Edwards · weight 3Yes
Creates the voucher in JDE · weight 3Yes
Goes through paths JDE supports · weight 3Yes
No file transfer, no nightly batch · weight 3Yes
Survives ESUs and Tools Releases · weight 2Yes
Supports JD Edwards World · weight 2Yes
Publishes its IT-time cost · weight 1No
What it actually does
Agents that execute, not advise · weight 3PartialOracle supplies the bricks — orchestration, document understanding — not the agent that does the work. Medium-term risk, not immediate.
AP end to end: capture to payment · weight 3NoShops wiring OCI Document Understanding into Orchestrator themselves discover that extraction is about 20% of the problem. That is the moment to talk to them.
Beyond AP: requisitions, receipts, statements · weight 2Partial
Order-to-cash on JDE · weight 2Partial
Triages the AP mailbox · weight 2No
Judgment on coding, AAI and tax · weight 3Partial
Resolves exceptions itself · weight 2No
Handles freight and non-PO invoices · weight 2No
Knowledge that stays
Your shop's rules in plain English · weight 3NoNothing captures the shop's rules in plain English, and nothing learns from a correction.
Corrections become governed rules · weight 3No
Starts from your history, not a blank template · weight 2No
Control and proof
Audit trail on the voucher · weight 2Yes
Scoped, revocable access · weight 2Yes
SOC 2 Type II · weight 1Yes
Hosting region you choose · weight 1Yes
Oracle Validated Integration · weight 1Yes
Named JD Edwards customers · weight 2Yes
Published performance numbers · weight 1Partial
Present where JDE people are · weight 1YesSupport through 2037 is a gift to the argument: it kills the “it is going to be replaced anyway” objection.