Vendor profiles, head-to-head comparisons and a published cost model for the systems that run the finance function. Every fact cites its source. Nothing is ranked for a fee.
55 systems across 10 categories, every record with its sources. Costs as modelled bands. No placement sold.
Four observations supported by the profiled records, with the counts behind them. They change when the data changes.
44 of the 55 systems profiled state a fit for a company of around 600 employees. Buyers in that band should expect to shortlist by deployment model and vertical depth, not by whether a system claims to fit.
27 systems are offered exclusively as multi-tenant cloud. Private-cloud and on-premise remain available mainly at the enterprise band (8 systems), where regulated and heavily customised estates still require them.
23 systems document an AI layer. The gap between what is demonstrated and what is generally available to every customer is wider here than in any other module; the demo questions on the AI module page are written to close it.
No vendor profiled publishes a list price for the configurations buyers actually run. Stackmark therefore records a cost band per system and models a range from stated assumptions, rather than reproducing a figure it cannot cite.
One bar per profiled system, from the smallest to the largest company the vendor states a fit for. Tint is the cost band. Nothing here is a judgement: the bars are the vendors' own claims, placed on one axis. Move the marker to your own headcount and the systems that reach it stay lit.
51 of 55 systems state a fit at 500 employees.
Compare the 51 that fitFilter by company size, industry and deployment model. The state lives in the URL, so a shortlist is shareable with the committee by copying the address.
Five steps: the business, the modules in scope, must-have against nice-to-have, notes, then a Markdown or CSV export. The draft stays in the browser; nothing is sent.
Software, implementation and annual run cost from users, entities, modules and deployment. The model that produced each range is printed beneath it.
Coverage of the dataset by cost band and deployment, always against the total profiled. It is not market share, and the page says so.
A record that breaks one fails the build. The rest are editorial policy, published here so a reader can hold the site to them.
Each vendor, module and partner record lists the URLs it was built from. A fact that cannot be cited is not recorded.
Positioning statements and demo questions are Stackmark’s own. Nothing is reproduced from a vendor page or a competing directory.
The estimator publishes its assumptions beside every range. A quote comes from a vendor; Stackmark does not simulate one.
The benchmark counts profiled systems that fit a stated profile, always against the total profiled. Stackmark holds no adoption data and reports none.
Vendor directories publish no quality data Stackmark can stand behind, so partner lists are alphabetical and say so.
A sponsored placement is labelled Sponsored and its link is marked as paid. Sponsorship never alters a profile, a comparison or a result.
Observations from the dataset, guides for the committee, and the reasoning behind the methods. Guest contributions are labelled.
2 runs
Spreading rent by headcount or IT by users is standard in a finance system. What differs is which basis the run reads, and what a second run does after someone corrects it.
0 of 9
Nine of the 55 systems Stackmark profiles name intercompany in their records, and none says how the second entity's entry gets made. Two vendors' own help pages show why that is the question to ask before the demonstration.
1 of 55
Every ERP will report by department, location and product. Where that detail sits decides whether adding a new cut next year is a setup change, a batch job that locks the ledger, or a fresh implementation.
No. Stackmark publishes structured, sourced research on ERP and finance software in the form an analyst note would take (vendor profiles, head-to-head comparisons, module coverage, a cost model) without briefings, paid inclusion or a ranking. Every claim on the site can be traced to a cited source or to the published model.
Coverage follows the categories in the dataset (ERP, accounting, close, AP and AR automation, spend, payroll, planning, tax and treasury), and a system is profiled when its facts can be sourced. 55 systems meet that bar today. Inclusion cannot be bought.
A score implies a judgement Stackmark has not made and cannot cite. What the site does instead is state each fact with its source, show where two systems differ, and count coverage against a visible denominator, so a buying committee can form its own judgement on evidence.
The dataset is committed to a repository and the whole site is rebuilt from it. The current build was reviewed in November 2026. When a record changes, every page that reads it changes with it.
Filter 55 profiled systems by size, industry and deployment, then open the head-to-heads the shortlist produces.