The 26 criteria, one by one
How it touches JDE
Runs inside JD Edwards · weight 3Partial
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 2No
Publishes its IT-time cost · weight 1No
What it actually does
Agents that execute, not advise · weight 3No
AP end to end: capture to payment · weight 3Partial
Beyond AP: requisitions, receipts, statements · weight 2NoStructurally it stops at the voucher. No mailbox triage, no requisition, no receipt, no statement reconciliation, no O2C.
Order-to-cash on JDE · weight 2No
Triages the AP mailbox · weight 2No
Judgment on coding, AAI and tax · weight 3Partial
Resolves exceptions itself · weight 2Partial
Handles freight and non-PO invoices · weight 2Partial
Knowledge that stays
Your shop's rules in plain English · weight 3No
Corrections become governed rules · weight 3NoNo enterprise memory. No human correction ever becomes a rule.
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 1Yes
Oracle Validated Integration · weight 1No
Named JD Edwards customers · weight 2No
Published performance numbers · weight 1Yes
Present where JDE people are · weight 1YesThe most dangerous competitor on content: it names the tables and the programs, which buys instant credibility with a JDE reader. Aviron has to match that level of specificity.