The 30 criteria, one by one
Cycle covered
Procure-to-pay, end to end · weight 3Yes
Order-to-cash, end to end · weight 3Yes
Close and reconciliation · weight 2PartialReconciliation of vendor statements and payment cycles, not a full month-end close suite.
Requisitions and purchase orders · weight 2Yes
Payment execution · weight 2PartialPrepares and releases payment runs through the ERP and payment partners; it is not a payment rail of its own.
Vendor statement reconciliation · weight 1Yes
Cards and employee expenses · weight 1NoNo corporate cards and no employee expense module.
How the work gets done
AI agents that execute the work · weight 3Yes
Reads non-standard documents without templates · weight 3Yes
Three-way matching · weight 2Yes
Judgment on coding and tax · weight 3Yes
Monitors and triages the AP mailbox · weight 2Yes
Autonomous exception handling · weight 2Yes
Rules written in plain English by finance · weight 3Yes
Every correction becomes a live rule · weight 3Yes
Fit with your ERP
Works across several ERPs · weight 2Yes
Writes back into the ERP natively · weight 3Yes
No replatforming, the ERP stays the system of record · weight 2Yes
Supports legacy and on-premise ERP · weight 2Yes
Supports Oracle JD Edwards · weight 2Yes
Does not need a modern API · weight 2Yes
Control and trust
Audit trail on every transaction · weight 2Yes
Scoped, revocable access · weight 2Yes
SOC 2 Type II · weight 1Yes
No model training on your data · weight 1Yes
Choice of hosting region · weight 1Yes
What you can verify
Named customer references · weight 2Yes
Published performance numbers · weight 1Yes
Published pricing · weight 1NoNo public grid. Priced per volume, on request — same as almost everyone in this table.
Live in weeks, not quarters · weight 1PartialDeliberately weeks rather than hours: history mining and a sandbox on real vouchers come first. Rivals who connect in hours skip both.