The 26 criteria, one by one
How it touches JDE
Runs inside JD Edwards · weight 3No
Creates the voucher in JDE · weight 3Partial
Goes through paths JDE supports · weight 3No
No file transfer, no nightly batch · weight 3NoIts own JDE page describes a file-based integration that syncs coding and payment data. The word “file”, on their page, is the literal proof of Aviron's argument.
Survives ESUs and Tools Releases · weight 2No
Supports JD Edwards World · weight 2No
Publishes its IT-time cost · weight 1Yes
What it actually does
Agents that execute, not advise · weight 3No
AP end to end: capture to payment · weight 3Yes
Beyond AP: requisitions, receipts, statements · weight 2No
Order-to-cash on JDE · weight 2No
Triages the AP mailbox · weight 2No
Judgment on coding, AAI and tax · weight 3No
Resolves exceptions itself · weight 2Partial
Handles freight and non-PO invoices · weight 2No
Knowledge that stays
Your shop's rules in plain English · weight 3No
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 2Partial
Scoped, revocable access · weight 2Partial
SOC 2 Type II · weight 1No
Hosting region you choose · weight 1Partial
Oracle Validated Integration · weight 1No
Named JD Edwards customers · weight 2Partial
Published performance numbers · weight 1No
Present where JDE people are · weight 1Partial