Scope and publisher
This view covers 24 entries across 26 criteria for the JD Edwards ecosystem. The underlying research snapshot is dated September 2026. The scoring method was updated on September 25, 2026.
StackERP is published by Aviron, a vendor included in the comparison. The same formula and weights apply to every entry within a dataset. The choice of criteria, their weights and the underlying assessments remain editorial decisions made from the publisher’s perspective.
How scoring works
Each criterion receives an assessment of 1 for coverage, 0.5 for partial coverage or 0 when coverage is not established in the dataset. Criterion weights range from 1 to 3. A criterion with weight 3 contributes three times as much as one with weight 1 within the same calculation.
Overall coverage: the complete research grid
Multiply each coverage assessment by its criterion weight, add the results, then divide by the total weight. This produces a coverage fraction between 0 and 1, which can also be displayed as a percentage.
The total weight for this grid is 55. A score of 1 means no coverage is recorded; 5 means full coverage across the grid. This is the score shown on individual vendor scorecards and in the comparator when no requirements are selected.
Weighted fit: your requirements plus overall coverage
When requirements are selected, the fit score combines two components. 70% comes from coverage of the selected requirements, using their original relative criterion weights. 30% comes from coverage of the complete grid.
Fit score = 1 + 4 × fit coverage
This keeps the selected workflow as the main factor while retaining information about the broader platform. Covering one selected requirement completely no longer produces an automatic 5.00/5. The overall component still includes the selected criteria, so those requirements intentionally contribute through both components.
The 70/30 split is an editorial weighting, not a statistically validated measure of quality. All calculations use the unrounded coverage fractions. Only the final score is rounded to two decimal places. Vendors with identical weighted coverage can still receive the same score; no arbitrary bonus or decimal is added to break a tie.
These scores measure assessed coverage. They do not measure execution quality, support, customer satisfaction or security. The overall component can lower the fit score of a specialist that covers your selected workflow well. Decimal precision describes the calculation, not the certainty of the underlying research.
Voucher creation example
With only “Creates the voucher in JDE” selected, the current dataset produces the following results. The fit score combines the selected and overall coverage percentages with the same 70/30 weighting for every provider.
| Provider | Selected coverage | Overall coverage | Fit / 5 |
|---|---|---|---|
| Aviron | 100.00% | 88.18% | 4.86 |
| ERP Suites | 100.00% | 43.64% | 4.32 |
| Circular Edge | 50.00% | 40.00% | 2.88 |
Evidence and uncertainty
The original research draws on vendor positioning, product pages, documentation and public discussions. Some entries begin from a shared product-family baseline, then include adjustments. Not every value has an individual source URL or a verification record attached.
A zero can mean a capability is absent, outside the product’s scope, or simply not established by the research. It should not be read as proof that a vendor cannot meet the requirement. Likewise, a positive assessment is not a certification that the capability works in your environment.
Reported performance figures are statements recorded in the research, not measured results from a StackERP benchmark. Differences in volume, workflow and definitions can make vendor figures incomparable. The updated weighting does not change these underlying assessments or strengthen their evidence.
How filters work
Selecting requirements keeps entries with at least partial assessed coverage of every selected criterion. Their displayed score uses the weighted-fit formula above. Selecting additional criteria changes the selected component; clearing all requirements returns to the overall coverage score.
The home-page explorer uses the same fit calculation as the full comparator for the same selected requirements. Its default list is a curated selection; you can also sort by fit score or name. Individual vendor scorecards always display the overall score across the complete grid.
Aviron’s featured placement does not change its calculated score. If it does not match a selection, it remains in a separately labelled featured section. Other results in the full comparator are ordered by the displayed score.
Product categories are combined with “or”, as are workflow tags. Different filter groups are combined with “and”. The score-band filter always uses the overall score, even when a filtered result displays a fit score.
Criteria and weights
The current JD Edwards grid is below. Percentage shares are calculated from the criterion weight divided by 55. Displayed percentages are rounded; calculations use the original weights.
| Criterion | Group | Weight | Share of overall coverage |
|---|---|---|---|
| Runs inside JD EdwardsUses JDE's own technology, screens or tables. Not a separate application that happens to exchange data with it. | How it touches JDE | 3 | 5.45% |
| Creates the voucher in JDEThe end product is a posted voucher in JDE with its batch and its match ; not a recommendation for a clerk to key in. | How it touches JDE | 3 | 5.45% |
| Goes through paths JDE supportsOrchestrator, AIS, business services, table interfaces, Batch Voucher Processor. No core modification. | How it touches JDE | 3 | 5.45% |
| No file transfer, no nightly batchExchanges transactions without relying on scheduled file transfers or overnight batches. | How it touches JDE | 3 | 5.45% |
| Survives ESUs and Tools ReleasesAn upgrade is a test cycle, not a re-integration project. | How it touches JDE | 2 | 3.64% |
| Supports JD Edwards WorldAssesses support for JD Edwards World separately from EnterpriseOne. | How it touches JDE | 2 | 3.64% |
| Publishes its IT-time costProvides an estimate of the IT resources required for implementation. | How it touches JDE | 1 | 1.82% |
| Agents that execute, not adviseIt takes the action. A chatbot that answers questions about JDE is a different product. | What it actually does | 3 | 5.45% |
| AP end to end: capture to paymentDocument in, voucher out, payment released ; not one slice of the middle. | What it actually does | 3 | 5.45% |
| Beyond AP: requisitions, receipts, statementsRequisitions, receipts, contract and price validation, vendor statement reconciliation. | What it actually does | 2 | 3.64% |
| Order-to-cash on JDECovers sell-side workflows such as billing, collections and cash application. | What it actually does | 2 | 3.64% |
| Triages the AP mailboxWatches the shared inbox, classifies what lands in it, and files it against the right supplier. | What it actually does | 2 | 3.64% |
| Judgment on coding, AAI and taxApplies account, Automatic Accounting Instruction (AAI) and tax decisions to the transaction. | What it actually does | 3 | 5.45% |
| Resolves exceptions itselfTolerance variance, PO not found, suspected duplicate ; handled, or escalated with a recommendation. | What it actually does | 2 | 3.64% |
| Handles freight and non-PO invoicesHandles freight, utilities, non-PO invoices and tax variances. | What it actually does | 2 | 3.64% |
| Your shop's rules in plain EnglishA readable, editable record of how this shop actually works ; which supplier hits which AAI, how freight is coded, which approval goes where. | Knowledge that stays | 3 | 5.45% |
| Corrections become governed rulesRecords and governs human corrections for use in future processing. | Knowledge that stays | 3 | 5.45% |
| Starts from your history, not a blank templateMines what your shop has already done, rather than asking you to configure a generic package. | Knowledge that stays | 2 | 3.64% |
| Audit trail on the voucherDocuments, reasoning, approver and timestamp attached to the transaction ; not in a separate log. | Control and proof | 2 | 3.64% |
| Scoped, revocable accessGranted one system at a time by your administrator, narrow, revocable in a click. No global admin account. | Control and proof | 2 | 3.64% |
| SOC 2 Type IIExternally audited, with a status you can check. | Control and proof | 1 | 1.82% |
| Hosting region you chooseOn-premise, your cloud, or a region you name. | Control and proof | 1 | 1.82% |
| Oracle Validated IntegrationHas an Oracle Validated Integration relevant to the product and version under consideration. | Control and proof | 1 | 1.82% |
| Named JD Edwards customersA named JDE shop on the record. Anonymised counts as half. | Control and proof | 2 | 3.64% |
| Published performance numbersRecords performance figures with their definitions, scope and supporting source. | Control and proof | 1 | 1.82% |
| Present where JDE people areHas identifiable technical contributions in JD Edwards user communities. | Control and proof | 1 | 1.82% |
Corrections and source submissions
Send the product name, the relevant criterion, the page URL and a current supporting source. Changes should address the underlying evidence, rather than a request for a higher rank.
Submit a correction · Explore sources and coverage · Return to the comparison