Methodology
Every vendor is scored on the same 30 criteria. A criterion is marked met (1), partial (0.5) or not met (0). The score out of 5 is weighted coverage:
score = 1 + 4 × (weight met ÷ 60)
No weight is adjusted vendor by vendor, and nobody pays to appear, to move up, or to have a limitation removed.
What the score measures, and what it does not
It measures declared functional breadth against this grid. It does not measure how well any single function is executed, how good the support is, how fast the software runs, or whether customers are happy. A narrow product that is excellent inside its lane scores low on breadth by construction — that is not a judgement on it. It is why the ranking recalculates the moment you check the criteria you actually need: that ranking is the one to read, not the general one.
How a vendor gets coded
From what the vendor says about itself: product pages, documentation, published numbers, conference material, and — where it exists — what its own users say in public community threads. Where a vendor publishes nothing on a criterion, it scores zero on that criterion, because a buyer cannot verify a silence.
Products in the same family start from a shared baseline for that family, and each entry then records what it genuinely deviates on, with the reason attached to the criterion. Those per-vendor notes are visible on each scorecard — they are the audit trail of this grid.
Where the data comes from
Market Edge competitor research for Aviron, September 2026 — 50 vendors, coded from each vendor's own public positioning, product pages and published numbers.
Criteria and weights
| Criterion | Group | Weight |
|---|---|---|
| Procure-to-pay, end to end Requisition, purchase order, receipt, invoice, voucher and payment in one flow — not one step of it. | Cycle covered | 3 |
| Order-to-cash, end to end Billing, invoicing, collections, cash application and revenue recognition on the sell side. | Cycle covered | 3 |
| Close and reconciliation Month-end close, account reconciliation, accruals, GL substantiation. | Cycle covered | 2 |
| Requisitions and purchase orders Intake, approval routing, PO creation and budget control before the invoice exists. | Cycle covered | 2 |
| Payment execution Runs the payment itself — not only the approval that precedes it. | Cycle covered | 2 |
| Vendor statement reconciliation Reconciles a supplier statement line by line against what the ERP holds. Almost nobody does this. | Cycle covered | 1 |
| Cards and employee expenses Corporate cards, expense reports, out-of-policy spend. | Cycle covered | 1 |
| AI agents that execute the work Agents that take an action and produce a record in the ERP, not a chatbot or a dashboard that advises. | How the work gets done | 3 |
| Reads non-standard documents without templates Handles a supplier's own layout, a scanned PDF, a freight bill, without a per-vendor template to maintain. | How the work gets done | 3 |
| Three-way matching Invoice against purchase order against receipt, with configurable tolerance. | How the work gets done | 2 |
| Judgment on coding and tax Decides the GL account, the cost centre and the tax treatment when the document does not say — the part OCR cannot do. | How the work gets done | 3 |
| Monitors and triages the AP mailbox Watches the shared inbox, classifies what arrives, and files it — nobody sorts email by hand. | How the work gets done | 2 |
| Autonomous exception handling Resolves the exception itself where it can, and escalates with a recommendation where it cannot. | How the work gets done | 2 |
| Rules written in plain English by finance The team writes or changes a rule in a sentence and it applies from the next document on. No developer, no ticket, no workflow builder. | How the work gets done | 3 |
| Every correction becomes a live rule A human fix is captured as a governed rule, so autonomy climbs after go-live instead of plateauing. | How the work gets done | 3 |
| Works across several ERPs Not tied to a single vendor's suite, and not a module you can only buy if you upgrade. | Fit with your ERP | 2 |
| Writes back into the ERP natively Creates the record inside the ERP through paths the ERP supports — not a file drop somebody has to maintain. | Fit with your ERP | 3 |
| No replatforming, the ERP stays the system of record You keep the ERP you have, at the version you have. | Fit with your ERP | 2 |
| Supports legacy and on-premise ERP Works on an on-premise or long-lived release, not only on the current cloud edition. | Fit with your ERP | 2 |
| Supports Oracle JD Edwards Documented support for EnterpriseOne, and ideally for World. | Fit with your ERP | 2 |
| Does not need a modern API Reaches the ERP through whatever it already exposes. No CSV over FTP, no nightly batch, no custom script to keep alive. | Fit with your ERP | 2 |
| Audit trail on every transaction The documents used, the reasoning, the approver and the timestamp travel with the record itself. | Control and trust | 2 |
| Scoped, revocable access Granted system by system by your own administrator, narrow in scope, revocable in one click. No global admin account. | Control and trust | 2 |
| SOC 2 Type II An external audit of the controls, not a self-declared security page. | Control and trust | 1 |
| No model training on your data Written into the commercial terms, not just into a FAQ. | Control and trust | 1 |
| Choice of hosting region Matters the moment a controller asks where the invoices physically sit. | Control and trust | 1 |
| Named customer references Named customers, on the record, with numbers attached to them. | What you can verify | 2 |
| Published performance numbers A published touchless rate, accuracy rate or cost per invoice — sourced, not rounded for a banner. | What you can verify | 1 |
| Published pricing A grid you can read without booking a call. | What you can verify | 1 |
| Live in weeks, not quarters Time to a first real transaction in production, with a number attached to it. | What you can verify | 1 |
Interest disclosure
STACK ERP is published by Aviron, which builds one of the 56 products compared here. Aviron gets no special treatment in the calculation: it is coded on the same grid, it sits at number 1 on breadth, and the 2 criteria it does not meet are printed on its own scorecard with the reason why — cards and employee expenses, published pricing.
If you find a rating that is out of date or wrong, that is worth more to this page than a compliment. Vendors change their pages weekly; this grid is dated September 2026.