Midmarket ERP: requirements checklist
From the guide at bestfinancesoftware.com/guides/midmarket-erp, published 29 October 2026. Use your browser's print command; the site header and footer are left off the page.
| Requirement | Vendor A | Vendor B | Vendor C |
|---|
| Must have |
|---|
| Multi-entity accounting with intercompany entries and eliminations, or a clear plan for where consolidation happens. | | | |
| Role-based access, approval workflows and an audit trail that an auditor can test. | | | |
| A documented API and export, so data can reach planning, close and reporting tools. | | | |
| Named implementation resources, with their experience in your industry, in the statement of work. | | | |
| A data migration plan that says which history moves, who cleans it and who signs off. | | | |
| Depends on you |
|---|
| Revenue recognition schedules, if you sell contracts or subscriptions. | | | |
| Inventory, manufacturing or warehouse management, if you carry inventory. | | | |
| Project accounting and time, if you bill for services. | | | |
| Local tax and statutory reporting, if you have entities outside your home country. | | | |
Questions to ask in the demo
- Run a scripted scenario we send you, with our entities and our transactions, not your demo company.
- Show an intercompany sale, its elimination and the consolidated statements.
- Show who can post a journal entry, who approves it, and the log of both.
- What changed in the last two upgrades, and did customers have to retest anything?
- Which parts of this demo are standard and which were configured or built for it?
- Introduce me to the people on our project, and to two customers your team implemented.
Back to the guide, with the reasons behind each item and the vendors described from their own pages.