.png)
Do I Need an ERP System? The CPA Framework for an Honest Answer
The ERP question comes up at every growing company at some point, usually triggered by a board member, an investor, or an ERP vendor sales motion. The honest CPA answer is that most companies asking the question would be better served by QuickBooks Online plus a well-built automation stack than by an ERP migration. The threshold where an ERP becomes genuinely the right answer is higher than the conversation usually assumes, and the cost of getting the threshold wrong runs in both directions. This guide is the framework I use when I review the question for clients.
Most companies asking "do I need an ERP system" do not need one. The genuine threshold where ERP becomes the right answer is high: typically more than $50M in revenue, multiple operating entities with complex intercompany activity, or industry-specific requirements that QuickBooks Online cannot reasonably support. Below that threshold, the better answer is almost always QBO plus a well-built automation stack. Above that threshold, the right ERP choice depends on industry, geographic footprint, and existing tech investments. The cost of migrating to an ERP prematurely is substantial: typically six-figure implementation costs, twelve to eighteen months of disruption, and lost productivity during the transition. The cost of staying on QBO too long is real but typically lower and easier to fix. When in doubt, the prudent answer is to stay on QBO and invest in automation; the ERP question rarely gets less feasible by waiting twelve months to revisit it.
Key takeaways
- ✓ The genuine threshold for ERP migration is higher than the conversation usually assumes: typically $50M+ in revenue, multiple entities with complex intercompany activity, or industry-specific requirements QBO cannot reasonably support.
- ✓ Most companies asking the ERP question are responding to perceived limits in QBO that are actually limits in their accounting workflow, fixable with automation rather than platform migration.
- ✓ Genuine triggers: multi-entity consolidation at scale, true industry-specific functionality (manufacturing inventory, project accounting, multi-currency at volume), regulatory requirements beyond QBO's scope.
- ✓ False triggers: slow close cycle, lack of management reporting, board pressure based on company stage, ERP vendor sales motions, perceived prestige.
- ✓ The QBO-plus-automation alternative handles the work that most companies think they need an ERP for, at a fraction of the cost and migration disruption.
- ✓ When the ERP question is genuinely close to right, the prudent move is usually to wait six to twelve months and revisit. The question rarely becomes less feasible with time and often resolves itself with growth or operational changes.
Why this question is being asked
The "do I need an ERP system" question almost never originates with the accounting team that owns the books. It comes from one of four sources, and recognizing the source is part of evaluating the question honestly.
The board or investor. A board member or investor, usually one who came from a larger company, observes that the finance function feels light and suggests the company is ready for "real" accounting infrastructure. The framing is well-intentioned but generally based on pattern-matching to a company much larger than the one being advised.
An ERP vendor sales motion. An ERP vendor, sometimes through a consultant partner, has engaged with the company and the sales motion has reached the implementation conversation. The vendor framing is, predictably, that an ERP is the right answer; the harder question of whether the company actually needs one is not the vendor's problem.
A new finance leader. A controller, CFO, or VP Finance has just joined and is evaluating the accounting infrastructure. If the new leader came from a larger company, the QBO baseline can feel inadequate by reference to their last environment, even when QBO is genuinely the right fit for the current company.
Genuine operational pain. The accounting team is genuinely struggling: slow close, weak reporting, manual workarounds, inability to answer basic questions about the business. This is the source where the question deserves the most careful answer, because the underlying pain is real even if ERP is not necessarily the solution.
The CPA's job, when the question lands, is to identify which source it came from and respond to that source honestly. The first three sources usually warrant a "not yet" answer; the fourth warrants careful diagnosis of whether the pain is platform-driven or workflow-driven.
What an ERP system actually is (and is not)
"ERP," enterprise resource planning, is a category, not a single product. An ERP integrates accounting, inventory management, purchasing, sales, human resources, and operations into a single platform with shared data underneath. The major mid-market ERP options in 2026 fall into a few categories: dominant cloud-native ERPs, the Microsoft-ecosystem ERP line, partner-channel cloud ERPs, and a legacy on-premise set with installed bases but few new deployments. A separate category of cloud accounting platforms sometimes gets grouped in but is positioned as a direct QBO alternative rather than as an ERP.
What an ERP genuinely provides over QBO: native multi-entity consolidation at scale, sophisticated inventory management for manufacturing or complex distribution, project accounting with WIP and revenue recognition mechanics built in, multi-currency at volume, and configuration depth that QBO's simpler model does not match.
What an ERP does not provide that the conversation sometimes assumes: better automation than QBO with the right third-party tools, faster month-end close (close speed is largely a workflow question, not a platform question), better reporting (most ERP reporting is more configurable but no more accessible than well-built QBO reporting), better accuracy (both platforms are accurate when run correctly), or any inherent reduction in finance team headcount.
The honest framing: an ERP buys you depth in specific categories where you have specific needs. It does not buy you a fundamentally better-run finance function; that comes from people, processes, and workflow automation, regardless of platform.
Genuine triggers that warrant the ERP conversation
Five categories of trigger genuinely warrant the ERP conversation:
1. Multi-entity consolidation at material scale. If the company operates three or more legal entities with substantial intercompany activity, and especially if any of the entities operate in different currencies, the QBO multi-entity workflow becomes increasingly cumbersome. An ERP with native consolidation handles this category materially better than QBO does, even with strong consolidation workpapers running alongside.
2. Manufacturing or complex inventory operations. Companies that manufacture goods, run complex distribution operations, or manage inventory with multi-step assembly and bill-of-materials tracking are genuinely above QBO's ceiling. The inventory module in QBO is adequate for simple cases; it is not adequate for manufacturing complexity. An ERP with proper manufacturing functionality is the right tool here.
3. Project accounting at scale with WIP and percentage-of-completion. Service businesses billing fixed-price multi-period projects with WIP recognition requirements (construction, engineering, large consulting engagements) face revenue recognition mechanics that QBO does not handle natively. Strong workpapers in Sheets handle this for smaller cases; at scale, the case for ERP project accounting is genuine.
4. Multi-currency at meaningful volume. Occasional foreign-currency transactions are fine in QBO. A business with significant operations in multiple currencies, revenue, expenses, intercompany, runs into QBO's edge increasingly quickly. The mechanics work but the volume of edge cases multiplies. An ERP designed for multi-currency operations handles this more cleanly.
5. Industry-specific functionality QBO does not match. Some industries have specific requirements that the major ERPs handle through industry-specific configuration or add-on modules: government contracting, healthcare, certain regulated financial services. If your industry has standardized expectations for accounting infrastructure that QBO does not match, the platform conversation is genuine.
The connecting thread across these five: they are all driven by genuine operational complexity that the QBO data model does not handle well. Not by company stage. Not by board preference. Not by what a larger company would do. By what the actual work requires.
False triggers that look like ERP needs but are not
Six patterns get mistaken for ERP needs. These are the ones where the better answer is workflow improvement or automation rather than platform migration.
1. The month-end close takes too long. Close speed is overwhelmingly a workflow question, not a platform question. Companies on QBO that close in five business days exist; companies on an ERP that close in twenty business days exist. The variables that drive close speed, accrual automation, JE workflow, reconciliation discipline, live reporting, are the same on both platforms. Migrating to an ERP without fixing the workflow produces an ERP with a slow close.
2. The reporting is not what we need. Most QBO reporting limitations are addressable with a live reporting tool pulling QBO data into Google Sheets. The reporting depth available through Sheets-based reporting on QBO data is comparable to ERP reporting for most use cases. We cover this in the QuickBooks reporting tools guide.
3. We have too many manual journal entries. Manual JE volume is addressable with JE automation tools that work on QBO. Migrating to an ERP does not eliminate the underlying JEs; it just moves them to a different platform. The volume is a workflow problem.
4. Our investors expect us to be on an ERP. This is rarely true if examined carefully. Sophisticated investors care about the quality of the finance function, accurate books, fast close, decision-grade reporting, internal controls, not the platform underneath. A well-run QBO environment with strong automation supports a credible finance function. If the investor genuinely cannot work with QBO data, that constraint is usually addressable.
5. We are growing fast and want to get ahead of the curve. Migrating "in anticipation of needing one" is one of the more expensive mistakes a growing company can make. The cost of migrating before you need it substantially exceeds the cost of migrating when you do. Wait until genuine triggers appear.
6. Our competitors are on ERPs. Competitor platform choices tell you little about your needs. Make the decision based on your operational requirements, not on what others have done.
Where the QBO ceiling actually sits in 2026
The honest QBO ceiling, the point where QBO genuinely stops being able to support a company's accounting, is higher than most ERP-conversation framings suggest. The functional ceiling I see in CPA review work in 2026:
Revenue: QBO comfortably supports companies up through roughly $50M in annual revenue, sometimes higher depending on complexity. Above $100M, the case for ERP starts to become more defensible regardless of other factors.
Transaction volume: QBO handles tens of thousands of transactions per month without issue. The performance edge is reached well above what most companies under $50M generate.
Entity count: Single entity is the sweet spot. Two or three entities with light intercompany activity is manageable. Four or more entities with material intercompany activity starts to genuinely strain the QBO workflow.
User count: QBO supports the user counts a finance team for a sub-$50M company needs. Larger user count requirements with role-based access can hit limits.
Industry-specific: Manufacturing with deep inventory, construction with WIP, certain regulated industries; these are above the ceiling on functional grounds even at lower revenue.
The point: most companies asking the ERP question are well below the genuine ceiling on every dimension. The pain they are experiencing is real but addressable on their current platform.
The QBO-plus-automation alternative
For most companies that would otherwise consider an ERP migration, the better answer is QBO plus a well-built automation stack. The automation handles the work that the company thinks an ERP would provide, at a fraction of the cost and migration disruption.
The components of the QBO-plus-automation stack:
- QuickBooks Online as the GL platform. Native bank feeds, transaction categorization, recurring transactions, native multi-entity for the two-or-three-entity case.
- Accrual automation for prepaids, deferred revenue, multi-period contract recognition. Accruer handles this category with locked-period awareness and mid-stream recalculations that ERP accrual modules sometimes do not match.
- JE automation for structured posting of recurring entries: payroll, allocations, intercompany, complex revenue mechanics. Booker handles this through Google Sheets templates with continuous sync to QBO.
- Live reporting that pulls QBO data into Sheets on demand. Wrangler handles both the polished client-facing reports and the magic-report exception detection that surfaces problems before close.
This stack produces a finance function that compares favorably with ERP-driven finance functions at companies multiple times the size, at a small fraction of the implementation cost and time. The full framework is in the accounting automation pillar and the QBO automation pillar.
A short comparison of the major ERP categories
For the smaller set of companies genuinely above the QBO ceiling, the ERP question becomes which category, then which product within it:
Dominant cloud-native ERPs. Two products anchor most mid-market deployments. Strong consolidation and multi-currency, deep configuration, substantial implementation cost and timeline. One has more configuration depth and the larger installed base; the other is lighter to implement and particularly strong in service businesses and project accounting.
Microsoft-ecosystem ERPs. Strong fit for companies already deep in the Microsoft stack. Particularly well-suited for manufacturing and complex distribution. Configuration depth and implementation cost comparable to the dominant cloud-native ERPs.
Partner-channel cloud ERPs. Newer entrants with strong manufacturing and distribution. Pricing often more favorable than the dominant cloud-native ERPs for similar functionality. More common in family-owned mid-market than venture-backed segments.
Legacy on-premise ERPs. Several product lines still have substantial installed bases. New deployments are rare; existing deployments often consider migration to one of the cloud-native categories above.
Selection depends on industry, geographic footprint, existing tech investments, and implementation-partner availability. Use an independent advisor, not the vendor's implementation partner alone, for honest comparison.
The true cost of an ERP migration
The framing that ERP vendors lead with is the software license cost. The true migration cost is substantially higher:
- Implementation services: Typically three to five times the annual software cost in year one. Mid-market ERP implementations frequently run $300K-$1M+ in services.
- Internal time: Twelve to eighteen months of substantial finance-team time on the migration. Other priorities slow or stop during this period.
- Productivity loss during transition: The finance function runs less efficiently during migration. Close cycles often slow temporarily.
- Ongoing implementation: Most ERP deployments require ongoing configuration work after go-live, additional cost in years two and three.
- Adjacent system changes: ERP migrations often force changes to payroll integration, expense management, billing, CRM. Easy to underestimate.
The total cost-of-ownership comparison between QBO-plus-automation and ERP almost always favors the QBO path until the genuine triggers are reached.
The decision framework, summarized
The framework I use when reviewing the ERP question for clients:
- Identify the source of the question. Board, vendor, new finance leader, or genuine operational pain. The first three usually resolve to "not yet"; the fourth deserves careful diagnosis.
- Check against the genuine triggers. Multi-entity at scale, manufacturing, project accounting with WIP, multi-currency at volume, industry-specific requirements. If none apply, the ERP conversation is probably premature.
- Check the QBO ceiling indicators. Revenue, transaction volume, entity count, user count, industry. If the company is well below the ceiling on every dimension, the platform is not the limiting factor.
- Diagnose the operational pain. Slow close, weak reporting, manual JEs: are these platform problems or workflow problems? Almost always workflow.
- Estimate the cost of the alternative. QBO plus an automation stack typically costs a small fraction of an ERP migration, with implementation in months rather than years.
- If still unclear, default to waiting twelve months. The ERP question rarely becomes less feasible with time. Waiting almost always either resolves the question or makes the right answer clearer.
Following this framework, the majority of ERP conversations I have with clients end with the recommendation to stay on QBO and invest in automation. The minority that proceed with ERP migration do so on solid grounds and are not surprised by the migration cost.
"Most of the companies I have advised through this question over twenty years did not need an ERP at the time they asked. The ones that pushed through anyway often regretted the migration cost and the timeline. The ones that waited and revisited usually either grew into a genuine need or, more often, found that automating their existing QBO environment solved the problem at a fraction of the cost." Tom Zehentner, CPA · Product & Growth, FinOptimal
Common mistakes
Letting board or investor pressure drive the decision
Sophisticated boards care about finance function quality, not platform choice. A well-run QBO environment supports a credible finance function for any company under the genuine ceiling. If the pressure is platform-specific, it is usually based on pattern-matching to a much larger company; push back with the operational data.
Assuming an ERP migration will fix workflow problems
Slow close, weak reporting, manual JEs: these are workflow problems. They follow the company to the ERP. Fix the workflow first; migrate to an ERP later only if genuinely warranted, by which point the workflow improvements often eliminate the need.
Underestimating the migration cost and timeline
ERP implementation services run three to five times software cost. The timeline is twelve to eighteen months. Internal time is substantial. The total true cost is several multiples of the license number that gets quoted upfront.
Migrating "in anticipation" of needing an ERP later
The cost of migrating early substantially exceeds the cost of migrating when needed. Wait until genuine triggers appear. The question rarely becomes less feasible with time.
Choosing the ERP based on the vendor's implementation partner
Vendor implementation partners are incentivized to recommend the vendor. Engage an independent advisor, a CPA firm experienced with ERP selection, not a single-vendor partner, to evaluate the choice across options.
Skipping the QBO-plus-automation evaluation
The honest alternative to an ERP migration for most companies is QBO plus a well-built automation stack. This option is rarely presented when an ERP vendor is driving the conversation. Insist on evaluating it explicitly before committing to migration.
The stack that replaces most ERP migrations
Accruer for accrual automation. Booker for JE posting and allocations. Wrangler for live reporting and exception detection. Together they handle the work most companies think they need an ERP for, at a small fraction of migration cost and timeline.
Frequently asked questions
What is the difference between an ERP and an accounting system?
An accounting system manages the general ledger: accounts, transactions, financial reporting. An ERP integrates accounting with operations: inventory management, purchasing, sales, HR, manufacturing, project management. QuickBooks Online is an accounting system with some operational add-ons. Full ERPs are different; they include native modules for operational functions integrated with accounting under one data layer. The distinction matters because companies that need only the accounting function often pay for ERP capabilities they will never use.
At what revenue does a company typically need an ERP?
There is no fixed threshold, but a useful frame: QBO comfortably supports companies up through $50M in annual revenue. Between $50M and $100M, the question becomes operational-complexity-dependent: some companies in this range are genuinely above the QBO ceiling, others are not. Above $100M, the case for ERP becomes more defensible regardless of other factors. But revenue alone is not the right test; operational complexity matters more.
Can we use QuickBooks Online with multiple entities, or do we need an ERP?
QBO handles two or three entities with light intercompany activity reasonably well, especially with strong consolidation workpapers in Google Sheets running alongside. Four or more entities with material intercompany activity starts to genuinely strain QBO's workflow. The decision depends on the entity complexity, not just the entity count: three entities with significant cross-entity transactions can be harder than five entities with simple structures.
How much does an ERP migration typically cost?
Software license is the smaller piece. Implementation services typically run three to five times the annual software cost in year one. For mid-market deployments, total year-one cost (software plus services) often runs $300K to over $1M. Add ongoing configuration, internal time, and trickle-down system changes, and total cost of ownership across the first three years is typically $750K to $3M for mid-market ERP migrations.
Will an ERP make our month-end close faster?
Probably not. Close speed is overwhelmingly a workflow question, accrual automation, JE workflow, reconciliation discipline, live reporting, not a platform question. Companies on QBO that close in five business days exist; companies on ERP that close in twenty business days exist. Migrating to an ERP without addressing workflow produces a slow close on ERP. Address workflow first.
How do the two dominant cloud-native mid-market ERPs differ?
Both are widely deployed in the same general segment. One has more configuration depth and a larger venture-backed installed base; it tends to be the default for high-growth software-and-internet companies. The other is generally lighter to implement and particularly strong in service businesses and project accounting; it tends to be more common in professional services and accounting-services-heavy businesses. The right choice depends on industry fit and existing partner relationships.
Are there meaningful accounting-platform alternatives to QuickBooks Online?
One widely-deployed cloud accounting platform is positioned as a direct QBO alternative in the same segment, not as an ERP. The choice is largely about preference, partner ecosystem, and geographic footprint (the alternative is stronger outside the U.S.; QBO dominates U.S. operations). Neither is an ERP; both face the same ceiling when operational complexity rises.
When should we revisit the ERP question if we decide to stay on QBO now?
Twelve months is a reasonable cadence. The question rarely becomes less feasible with time; companies either grow into a genuine need (at which point ERP is a clear answer) or the workflow improvements that come with automation make the question moot. Forcing the decision before the triggers are clear usually produces premature migrations. Waiting and revisiting almost always produces clearer decisions.
Where to go next
Read these next:
- The CPA firm tech stack: the pillar resource
- Accounting firm automation software
- Scaling an accounting firm without hiring
- Best accounting software for SaaS companies
Related Resources
- QuickBooks Online automation: the implementation pillar
- Accounting automation: the framework pillar
- QuickBooks reporting tools
- Accruer: accrual automation for QBO
- Booker: journal entry automation for QBO
- Wrangler: live QBO reporting in Google Sheets
Sources & References
- FASB revenue recognition guidance: see ASC 606 on fasb.org.
- IRS guidance on accounting periods and methods: see irs.gov.
- AICPA, Audit and Accounting Guide.
- FinOptimal Managed Accounting practice: implementation data across 50+ client environments, 2024-2026.
.png)
.jpg)
.png)
.png)
