ERP Selection Checklist for CFOs: The Complete 2026 Guide

ERP selection is fundamentally a financial decision wrapped in a technology project. Yet in most organizations, the process begins in IT and only reaches the CFO’s desk when a purchase order needs a signature. That sequence is backwards. CFOs who lead the selection process from day one deliver projects that cost 20-35% less, reach ROI 6-12 months faster, and survive board-level scrutiny because the business case was built by the person who understands capital allocation, not the person who understands database schemas.

This checklist is designed for CFOs and finance leaders who are either initiating an ERP selection or inheriting one already in progress. Every item is framed around financial governance, risk management, and measurable return. Use it as a working document from requirements gathering through post-go-live stabilization.

Why CFOs Lead ERP Selection

ERP implementations are the largest technology investment most organizations make in a decade. For mid-market companies, total cost of ownership over five years typically lands between $750K and $3M. For enterprises, the range stretches from $2M to $15M or more. These numbers place ERP squarely in the category of capital decisions that demand CFO oversight, not just CFO approval.

Three structural reasons make CFO leadership non-negotiable:

Budget accountability. ERP projects overrun initial estimates by 50-200% in roughly 55% of deployments. The CFO is the only executive with both the authority and the analytical framework to build contingency into the budget, challenge vendor pricing assumptions, and enforce financial discipline throughout the project lifecycle.

Cross-functional visibility. ERP touches every department that generates or consumes financial data: procurement, manufacturing, sales, HR, and finance itself. The CFO sees how data flows across these functions because the general ledger is where all transactions ultimately land. That vantage point is essential for defining requirements that serve the whole organization rather than a single department’s wish list.

Audit and compliance requirements. SOX compliance, revenue recognition standards (ASC 606), multi-entity consolidation, and tax reporting are not features you bolt on after go-live. They must be evaluated during selection, and only the CFO’s office has the expertise to validate that a platform meets these requirements without expensive customization.

For a detailed breakdown of what these projects actually cost, see our ERP Implementation Cost Guide.

Pre-Selection Checklist: Requirements Gathering

Before evaluating any vendor, establish the business requirements that will drive the decision. Skipping this phase is the single most expensive mistake in ERP selection; it leads to scope creep, vendor mismatch, and rework that adds 3-6 months and 25-40% to project cost.

Business Requirements

Document current-state financial processes (order-to-cash, procure-to-pay, record-to-report) with cycle times and error rates
Identify the top 10 pain points in existing systems ranked by financial impact (revenue leakage, manual reconciliation hours, reporting delays)
Define future-state requirements for the next 3-5 years, including planned acquisitions, new business lines, and geographic expansion
Establish multi-entity and multi-currency requirements with specific entity structures and intercompany transaction volumes
Document regulatory and compliance requirements (SOX, ASC 606, IFRS 15, GDPR, industry-specific mandates)
Quantify current manual workarounds and their cost in FTE hours per month
Identify integration requirements with existing systems (CRM, HRIS, banking platforms, tax engines, BI tools)
Survey department heads for must-have vs. nice-to-have features using a structured scoring matrix

Stakeholder Alignment

Appoint an executive sponsor (ideally the CFO or COO) with explicit authority over scope and budget decisions
Form a cross-functional selection committee with representatives from finance, operations, IT, and at least one end-user from each major department
Establish a decision-making framework (weighted scoring, consensus, executive override) before vendor demos begin
Set a realistic timeline: 3-4 months for selection, 6-18 months for implementation depending on complexity
Define success metrics that are measurable and time-bound (e.g., reduce monthly close from 12 days to 5 days within 6 months of go-live)

Vendor Evaluation Checklist

Organize vendor evaluation around five categories. Score each item on a 1-5 scale and weight categories based on your organization’s priorities. A vendor that scores 4.5 on features but 2.0 on financial stability is not a safe bet for a decade-long platform commitment.

Functional Fit (Weight: 30%)

Core financials: GL, AP, AR, fixed assets, bank reconciliation, multi-entity consolidation
Revenue recognition automation (ASC 606 / IFRS 15) without custom development
Budgeting, forecasting, and planning capabilities (native or integrated)
Procurement and purchase order management with approval workflows
Inventory and supply chain management (if applicable to your business)
Project accounting and job costing (for services organizations)
Real-time dashboards and self-service reporting for finance users
Audit trail and segregation of duties controls built into the platform

Technical Architecture (Weight: 20%)

Deployment model alignment: cloud, on-premise, or hybrid (see our Cloud vs On-Premise ERP comparison for detailed analysis)
API availability and quality for integrations with your existing technology stack
Data architecture supports your reporting and analytics requirements
Mobile access for approvals, expense management, and field operations
Uptime SLA of 99.9% or higher with financially-backed penalties
Data residency options that comply with your regulatory requirements
Platform extensibility without breaking upgrade paths

Vendor Viability (Weight: 15%)

Vendor annual revenue exceeding $100M (or strong growth trajectory for niche players)
Published product roadmap with quarterly or semi-annual release cadence
Customer base includes 10+ companies in your industry and size bracket
Reference customers willing to discuss their implementation experience candidly
Partner ecosystem with at least 3 qualified implementation partners in your region
No pending litigation, acquisition rumors, or product sunset announcements that could affect your deployment

Implementation Ecosystem (Weight: 15%)

At least 2-3 qualified implementation partners have responded to your RFP
Partners have completed 5+ implementations for companies of your size and industry
Partner provides fixed-fee or capped-fee engagement options (not just time-and-materials)
Partner methodology includes formal change management workstream
Partner references confirm on-time, on-budget delivery rates above 70%

User Experience (Weight: 20%)

End-user interface is intuitive enough to reduce training investment
Finance-specific workflows (journal entries, reconciliation, close tasks) require fewer than 5 clicks for common transactions
Reporting interface allows finance users to build ad-hoc reports without IT involvement
Approval workflows are configurable by business users, not just administrators

Financial Analysis Checklist

This is where CFOs add the most value. Vendor pricing is deliberately opaque, and the gap between a quote and the true five-year cost can exceed 100%.

Total Cost of Ownership (TCO)

Build a 5-year TCO model that includes every cost category. Use these benchmarks to validate vendor quotes:

Small business (25-100 users):

Year 1 total (software + implementation): $50,000 - $150,000
Annual run-rate (years 2-5): $30,000 - $100,000
5-year TCO: $170,000 - $550,000

Mid-market (100-500 users):

Year 1 total: $150,000 - $500,000
Annual run-rate: $100,000 - $400,000
5-year TCO: $550,000 - $2,100,000

Enterprise (500-5,000+ users):

ROI Calculation

Quantify hard savings: FTE reduction or reallocation, eliminated software licenses, reduced audit fees
Quantify soft savings: faster monthly close (value = controller hours x reduced days), improved cash flow from faster invoicing, reduced inventory carrying costs
Quantify revenue impact: faster quote-to-cash, improved pricing accuracy, reduced revenue leakage
Calculate payback period (industry average: 2.5-3.5 years; target under 3 years for mid-market)
Model best-case, expected-case, and worst-case scenarios with explicit assumptions documented
Validate ROI assumptions with department heads who will deliver the operational improvements

Budget Approval Process

Present TCO as a range, not a point estimate, with contingency of 15-25% above the expected case
Structure the business case around payback period and IRR, not just cost reduction
Include opportunity cost of delaying the decision (quantify the cost of staying on the legacy system for 1-2 more years)
Prepare board-ready materials that separate capital expenditure from operating expenditure implications
Identify financing options: vendor financing, subscription vs. perpetual trade-offs, phased deployment to spread cost

Implementation Readiness Checklist

A vendor selection without an implementation plan is a purchase order without a delivery address. Complete these items before signing any contract.

Define implementation phases with clear scope boundaries for each phase (finance first, then supply chain, then HR is a common and effective sequence)
Establish a governance structure: steering committee (monthly), project committee (weekly), workstream leads (daily standups)
Allocate internal resources: project manager (100%), functional leads (50-75%), subject matter experts (25-50%) for the duration of implementation
Define data migration strategy and assign a data owner for each major data domain (chart of accounts, customer master, vendor master, item master)
Establish a change management plan with communication cadence, training schedule, and resistance management protocols
Define go-live criteria that are objective and measurable (e.g., all critical transactions processed successfully in UAT, data migration accuracy above 99.5%)
Negotiate contractual protections: milestone-based payments, performance penalties, source code escrow (for on-premise), and a clear exit clause
Confirm that your IT team or managed service provider can support the technical environment (network, security, integrations) required by the platform

Risk Assessment Checklist

Every ERP implementation carries risk. The CFO’s role is not to eliminate risk but to quantify it, mitigate it, and ensure the organization can absorb it if mitigation fails.

Project Risks

Scope creep: establish a formal change request process with financial impact assessment for every scope addition
Timeline overrun: build 20-30% buffer into the project timeline and identify the critical path activities that cannot slip
Key person dependency: ensure no single internal resource or consultant is a single point of failure
Integration failure: conduct integration proof-of-concept during the selection phase, not after contract signing
Data quality: begin data cleansing immediately after vendor selection, not 2 months before go-live

Financial Risks

Vendor price increases: negotiate a multi-year price lock or cap annual increases at 3-5%
Hidden costs: require the vendor and implementation partner to disclose all fees in a single document (environment costs, API call charges, storage overages, premium support tiers)
Currency exposure: for global deployments, assess whether subscription fees are denominated in your functional currency
Opportunity cost of delayed ROI: model the financial impact of a 3-month and 6-month go-live delay

Operational Risks

Business continuity during cutover: plan a parallel-run period of 1-3 months where both old and new systems operate simultaneously
User adoption failure: set adoption targets (e.g., 90% of users logging in weekly within 60 days of go-live) and tie them to departmental KPIs
Reporting gaps: validate that all critical month-end and quarter-end reports can be produced from the new system before decommissioning the legacy platform
Audit readiness: confirm that the new system can produce audit evidence for the fiscal year spanning the transition (this often requires data from both old and new systems)

Post-Go-Live Checklist

Go-live is not the finish line. The 90 days following go-live determine whether the project delivers its promised ROI or becomes a sunk cost that the organization resents for years.

First 30 Days

Complete the first monthly close on the new system and document every workaround, error, and delay
Validate financial reporting accuracy by reconciling new-system output against legacy system output for the same period
Track support ticket volume and resolution time daily; escalate any ticket backlog exceeding 48 hours
Conduct targeted training sessions for the top 10 most-reported user issues
Verify all integrations are processing data correctly (bank feeds, CRM sync, payroll, tax engine)

30-90 Days

Reduce manual workarounds by 50% compared to the first month
Achieve user adoption targets across all departments
Complete the first quarter-end close and validate consolidated reporting
Begin measuring ROI against the business case: track cycle time improvements, error rate reduction, and FTE reallocation
Conduct a lessons-learned session with the implementation partner and internal team
Formally transition from the implementation partner to the ongoing support model (internal team, vendor support, or managed services)

90-Day Financial Review

Compare actual TCO against budgeted TCO and document variances
Validate that contracted SLAs are being met (uptime, support response time, system performance)
Assess whether Phase 2 scope (deferred features) is still justified based on actual usage patterns
Present a post-implementation report to the board or executive team with actual vs. projected metrics

Common CFO Mistakes in ERP Selection

Having reviewed hundreds of ERP business cases, these are the mistakes that cost real money:

Delegating entirely to IT. IT evaluates technology. The CFO evaluates investments. ERP is both. When IT leads alone, the selection optimizes for technical elegance rather than financial return. The result is a platform that impresses architects and frustrates accountants.

Anchoring on license cost instead of TCO. A vendor quoting $80/user/month looks cheaper than one quoting $150/user/month. But if the cheaper option requires $400K more in customization, $100K more in integration work, and 4 additional months of implementation, it is the more expensive choice by year three. Always compare 5-year TCO, never sticker price.

Skipping the reference check. Vendor-provided references are curated. Insist on speaking with customers who went live in the last 12 months, are in your industry, and are willing to share their actual project cost vs. budget. If a vendor cannot produce three such references, that is a disqualifying signal.

Underestimating change management. The software works. The people do not change. Organizations that allocate less than 10% of project budget to training and change management see adoption rates 30-40% lower than those that invest properly. For the CFO, low adoption means the ROI model was built on assumptions that will never materialize.

Negotiating price without negotiating terms. A 15% discount on license fees is worth far less than a 3-year price cap, milestone-based payment terms, or a contractual exit clause that does not strand your data. Negotiate the contract structure, not just the dollar amount. For more on where costs accumulate, review the ERP Implementation Cost Guide.

Ignoring the cost of doing nothing. Every month on a failing legacy system has a cost: manual reconciliation hours, reporting delays, audit risk, and missed operational insights. Quantify this cost explicitly. It strengthens the business case and creates urgency that prevents the selection process from stalling.

Frequently Asked Questions

How long should the ERP selection process take?

Plan for 3-4 months from initial requirements gathering to contract signing. Rushing below 8 weeks typically leads to incomplete evaluation and buyer’s remorse. Extending beyond 6 months introduces decision fatigue and the risk that requirements change before you sign. For small businesses evaluating 2-3 vendors, 6-8 weeks is achievable. See our best ERP for small business guide for streamlined recommendations.

What is the ideal selection committee size?

Five to seven members is the practical range. Include the CFO or VP Finance, the CIO or IT Director, one operations leader, one end-user champion, and optionally a procurement or legal representative. Committees larger than eight slow decision-making. Committees smaller than four miss critical perspectives.

Should we hire an independent consultant for ERP selection?

If your organization has never selected an ERP before, yes. An independent advisor (not affiliated with any vendor or implementation partner) typically charges $30K-$75K for a full selection engagement and saves multiples of that fee by preventing vendor lock-in, identifying hidden costs, and accelerating the evaluation timeline. Ensure the consultant’s compensation is a flat fee, not a commission from the vendor.

How do we compare cloud ERP vs. on-premise from a financial perspective?

Cloud ERP is operating expenditure (subscription). On-premise is capital expenditure (license + infrastructure) plus ongoing operating expenditure (maintenance, hosting, IT staff). Cloud has lower year-one cost but higher cumulative cost over 7-10 years. On-premise has higher upfront cost but can be cheaper at scale over a long horizon. The right choice depends on your capital allocation strategy, IT staffing model, and regulatory constraints. Our cloud vs. on-premise comparison provides a detailed financial analysis.

What percentage of ERP projects go over budget?

Industry data consistently shows 50-60% of ERP projects exceed their initial budget. The median overrun is 25-50% of the original estimate. Projects with strong CFO involvement from the selection phase show significantly lower overrun rates (15-25%) because the budget was realistic from the start and contingency was built in rather than wished away.

When should we involve the CFO in ERP selection?

Day one. The CFO should be involved in defining the business case, approving the selection budget, setting evaluation criteria, participating in finalist demos, and leading contract negotiations. Involving the CFO only at the purchase order stage is the organizational equivalent of asking the pilot to review the flight plan after takeoff.