ERP tech: when a software company needs one

A software or IT services firm needs an ERP when more than 25 people must use the books, when subscriptions and project billing no longer share one ledger, or when a license, implementation, and support must be split under ASC 606. QuickBooks Online Advanced lists at USD 340 per month and stops at 25 users, as of October 2026. Business Central Essentials lists at USD 80 per user per month, paid yearly, so 25 users cost USD 24,000 a year in licenses alone. Stay on accounting software if you are one entity, under that cap, with simple monthly subscriptions and a deferral schedule your accountant already keeps.

The bill changes with the business. A product company feels it in renewals and usage. A firm that also implements feels it when one contract must be allocated across obligations. An IT services firm feels it when time and milestones drive the invoice.

When accounting software is still enough

Three shapes of tech company hit three different walls, and only some of those walls justify a new system this year.

A product SaaS company lives on recurring contracts, price changes, usage, and renewals. General-purpose ERP grew up around inventory. NetSuite's software-company guide puts it this way: "Ironically, most business software was not designed with software companies in mind." If every contract is a flat monthly fee, one entity, and the accountant already spreads cash into a deferral schedule, QuickBooks Online can still close the month.

A mixed firm sells a subscription plus implementation plus support. The wall is the contract, even when the user count is still small. FASB's In Focus on ASU 2014-09 says earlier US GAAP had industry-specific software revenue rules, and Topic 606 replaced them with one model. A bundle of license, implementation, and support can contain more than one performance obligation. That is the point where a monthly deferral workbook starts to disagree with the auditor.

An IT services or managed-services firm lives on time, milestones, and project margin. The operational tool is often a PSA product. The financial step-up is the ledger that holds work in process, invoicing, and the close. Buying both without naming which system owns time is how firms pay twice. More on that in the mistakes section.

QuickBooks Online pricing, as of October 2026, is a company subscription with a user cap on each plan:

• Plus (List price: USD 140 per month · Intro price: USD 70 per month for three months · Users who can work in the books: 5 · What Intuit highlights for projects: Project profitability tracking)
• Advanced (List price: USD 340 per month · Intro price: USD 170 per month for three months · Users who can work in the books: 25 · What Intuit highlights for projects: Advanced project financials)

User caps on that page run 1 on Simple Start, 3 on Essentials, 5 on Plus, and 25 on Advanced, plus a small number of accountant seats. Paid plans have no annual contract. Intuit positions Advanced as the cloud product for companies that need automation and up to 25 users, and positions Intuit Enterprise Suite for multi-entity organizations that need heavier project costing. The pricing page does not list an Enterprise Suite dollar amount, so treat any quote for that product as a separate conversation.

You have passed the published QuickBooks Online ceiling when a 26th person needs to work in the books. You can still be under the ceiling and be ready to move if bundled contracts, usage billing, or project work-in-process no longer fit a spreadsheet beside the file. Firms earlier than that, still choosing a first system, can use our note on the best ERP for startups before they price a full ledger.

What licenses cost at 25 and 50 people

License list price is the part of the budget you can calculate before any partner sends a proposal. It is also the part finance teams under-count, because seat type changes the math more than the logo does.

Microsoft's US Business Central pricing page, as of October 2026, lists Essentials at USD 80 per user per month, Premium at USD 110, and Team Members at USD 8, all paid yearly. A 30-day trial is free. Microsoft says the figures are informational and the checkout price can differ. At those list rates, before tax, implementation, or Team Member seats:

• 25 (Monthly list: USD 2,000 · Yearly list: USD 24,000)
• 50 (Monthly list: USD 4,000 · Yearly list: USD 48,000)

That yearly column is arithmetic from the list price (users times USD 80 times 12). Microsoft calls the page informational, so checkout can still differ. Premium at USD 110 would be USD 33,000 a year for 25 users and USD 66,000 for 50. Budget Essentials unless a feature you require is sold only on Premium, and confirm that split when you check out, because subscription billing is included on the Essential license.

Odoo's US pricing page, as of October 2026, sells Standard and Custom as one per-user fee that includes all apps, with hosting, maintenance, and weekday support included. Implementation, Odoo.sh hosting, and in-app credits are excluded. The discount footnote says the discount lasts 12 months for the initial users ordered.

• Standard (What the page shows per user per month: USD 24.90 on the discounted yearly view, USD 31.10 on the yearly view, USD 38.90 on the monthly view · What you are paying for: All apps on Odoo Online)
• Custom (What the page shows per user per month: USD 49.00 and USD 61.00 on the yearly toggle, USD 61.00 and USD 76.20 on the monthly toggle · What you are paying for: Studio, multi-company, external API, and Odoo.sh or on-premise. Odoo.sh hosting is extra)
• Light user (What the page shows per user per month: USD 8.90, quoted with an advisor · What you are paying for: Time off, expenses, appraisals, attendances, referrals, planning, field service, barcode, and read-only Knowledge. Timesheets are not on that list)

Odoo defines a paying user as someone with backend access, or an employee record with no linked user. An employee who reports a timesheet is a paying user. Portal customers are not. For how those apps are phased on a services rollout, see Odoo implementation for a growing firm.

Assume 30 employees and each one either has an employee record or enters a timesheet. At the discounted yearly Standard figure of USD 24.90, 30 users cost 30 times USD 24.90 times 12, which is USD 8,964 for those initial users during the 12-month discount. At the undiscounted yearly view of USD 31.10, the same 30 users cost USD 11,196 per year. A light seat at USD 8.90 does not remove a consultant from that count, because timesheets are outside the published light-user rights.

Assume 40 people on Business Central. Eighteen need Essentials because they post invoices, projects, or time you have already confirmed requires a full user. Ten fit a Team Member seat at USD 8 for limited access you have confirmed on a test company. Twelve never log in. Licenses are 18 times USD 80 times 12, which is USD 17,280, plus 10 times USD 8 times 12, which is USD 960, for USD 18,240 a year before tax and services. If those 12 must enter timesheets and the Team Member seat cannot post project time, they become Essentials users. That adds 12 times USD 80 times 12, which is USD 11,520, and the license line becomes USD 29,760. Have that license test done before you sign the seat mix. The pricing page describes Team Members as limited access and does not, by itself, prove they can post a project timesheet.

Which three workflows the ledger has to carry

Subscription billing, project accounting, and revenue recognition are three designs. A firm can need one of them and still run the other two outside the ERP.

Subscription contracts and usage

Business Central subscription billing became generally available on 2 October 2024. The release plan states that the Essential license includes it. The module covers contracts, billing schedules, usage-based billing, automated billing, deferrals, and revenue recognition based on billing schedules.

Current subscription billing documentation, updated through 2026, stores contracts, subscriptions, and subscription lines. It can bill from imported usage data, post contract deferrals, and ship a Power BI app for monthly recurring revenue, churn, and contract growth. For a product company, the operational test is a renewal, a mid-term quantity change, and a usage file that becomes an invoice without a second billing tool.

Odoo Subscriptions advertises automated renewals, invoicing, and analytics for MRR, LTV, and retention. Those apps sit inside the per-user fee on Standard and Custom. The subscription module rides on the same seat price, and every employee who counts as a user is on that bill. That is why the timesheet rule in the previous section belongs in the same budget meeting as the MRR dashboard.

Project time, billing, and work in process

Business Central projects, with the overview updated 3 July 2026, cover budgets, resource prices, time sheets posted to a project journal, supplies, and invoicing on completion or on a schedule. Work-in-process methods include Percentage of Completion and Completed Contract. A services firm that bills on milestones and also recognizes cost as the work proceeds needs both patterns available, then needs the accountant to pick one method per job and stick to it.

Dynamics 365 Project Operations is a different app. It lists at USD 135 per user per month, paid yearly, as of October 2026, and is aimed at project-centric businesses. The pricing page covers deal management, resourcing, subcontracting, and billing. For a software firm whose projects are implementations attached to subscriptions, Business Central projects are the first thing to test. Project Operations earns a look when resourcing and subcontractors are the business, and when you are willing to add USD 135 per full user per month on top of the accounting system. Fifty Project Operations users at list would be USD 81,000 a year (50 times USD 135 times 12) before the ledger licenses.

Odoo Projects, described alongside the subscriptions materials, says customers can be billed from time on tasks or from milestones, and that project updates show profitability. The same pricing rule applies: the person who enters the time is a paying user.

Project-led firms that want a wider view of billing models can read ERP for professional services. The license math on this page is the software-company cut of that problem.

ASC 606 allocation, which is a different job from a deferral

ASU 2014-09 (Topic 606) sets the core principle: recognize revenue to depict the transfer of promised goods or services in an amount that reflects the consideration the entity expects to be entitled to. The five steps are:

1. Identify the contract.
2. Identify the performance obligations.
3. Determine the transaction price.
4. Allocate that price by relative standalone selling price.
5. Recognize revenue when or as each obligation is satisfied.

For public organizations, the standard is effective for annual periods beginning after 15 December 2017. For nonpublic entities that had not yet adopted, a 3 June 2020 deferral moved the effective date to annual periods beginning after 15 December 2019, and to interim periods within annual periods beginning after 15 December 2020. A US private software firm whose fiscal year follows that calendar is already inside the effective window. Your CPA still owns the accounting memo. The pages below stop at the operational test: can the product post the entries the memo requires?

IFRS 15 uses the same five-step model, including allocation on relative stand-alone selling prices, and is effective for annual periods beginning on or after 1 January 2018. Use it when the reporting entity applies IFRS. Do not assume a label for a Canadian private company from this page. Ask the firm's accountant which framework the statements use.

Assume a USD 30,000 contract. Standalone selling prices are USD 20,000 for a one-year subscription, USD 10,000 for implementation, and USD 10,000 for a year of support. Combined standalone price is USD 40,000. Relative allocation is 20/40 of USD 30,000 for the subscription, which is USD 15,000, and 10/40 of USD 30,000 for each of the other two obligations, which is USD 7,500 each. If implementation is delivered at signing, USD 7,500 is the amount tied to that delivery. The subscription and support amounts are recognized as those obligations are satisfied over the year. A straight-line spread of the whole USD 30,000 would book USD 2,500 a month and would never isolate the implementation delivery.

Odoo documents the straight-line job, and documents it clearly. The deferred revenue page uses a software license: a USD 1,200 one-year license is invoiced up front and recognized over 12 months, which is USD 100 a month. Entries can be generated on invoice validation or grouped manually. The page describes periodic spreading. It does not describe standalone-selling-price allocation across several performance obligations. Business Central subscription billing automates deferrals from the billing schedule. Neither of those descriptions is a certificate that the product completes all five steps. Ask for a walkthrough on a contract that looks like the USD 30,000 example, and read the journal entries yourself.

One Business Central community post is a single implementer's milestone-billing complaint, not a survey. The user wrote: "I used the milestone billing but the system is creating the full amount (36,000 at the beginning of the contract). I selected to have deferral and revenue recognition together and if I do revenue recognition monthly the remaining amount for Deferred is 6,000 however it should be zero." Treat that as a configuration risk. Put a milestone-plus-deferral case in the demo script and read the deferred balance after each monthly run.

How the three platforms fit a 20 to 100 person firm

For a single-entity software firm with subscriptions and a modest amount of implementation work, still at or near the QuickBooks 25-user cap and under Odoo's usual 50-employee Success Pack line, Business Central Essentials or Odoo Standard is the list-price pair to put on the first spreadsheet. NetSuite belongs on the short list when the revenue question is the hard part and you are ready to take a custom license quote.

• Published US seat price, as of October 2026 (Business Central: Essentials USD 80 per user per month, paid yearly · Odoo: Standard from USD 24.90 to USD 38.90 per user per month depending on the price view · NetSuite: The vendor guide leaves the seat price for a direct quote)
• Subscription billing (Business Central: Included with Essentials since 2 October 2024 · Odoo: Subscriptions app inside the user fee · NetSuite: Guide argues software firms need recurring contracts and contract changes in the ERP)
• Projects and time (Business Central: Projects, time sheets, Percentage of Completion, Completed Contract · Odoo: Time or milestones, with timesheet staff as paying users · NetSuite: Guide treats services margin as a core software-company need)
• Revenue pattern the vendor documents in public (Business Central: Deferrals and recognition from billing schedules · Odoo: Periodic deferral, illustrated with a USD 1,200 license · NetSuite: Multiple performance obligations under ASC 606 or IFRS 15)
• Who the vendor points at for implementation (Business Central: A partner or your own team. Microsoft sells the license · Odoo: Success Packs under 50 employees. A partner over 50 · NetSuite: The vendor's own planning ranges for services)

The NetSuite guide, dated 31 March 2026, says revenue tools should handle multiple performance obligations under ASC 606 or IFRS 15, and that quoting, usage rating, billing, and recognition often start in separate tools. It also says: "When quoting, billing, and revenue recognition exist in separate tools that lack strong data governance, finance teams spend more time reconciling spreadsheets." Ask Oracle for a written license quote, then lay it next to the USD 24,000 or USD 48,000 Business Central figures and the Odoo user math. Compare those written quotes. A third-party starts-at figure is someone else's estimate.

Odoo's own Success Pack page draws the line at 50 employees for how the work is staffed, and the estimator says that above 50 users the buyer should contact Odoo. A 60-person software firm can still run Odoo. Above that line, expect a partner statement of work, and ask that partner to show subscriptions, timesheets, and a multi-obligation contract on a database that looks like yours.

Business Central at 75 users keeps the same Essentials list rate unless checkout says otherwise. Seventy-five Essentials users are 75 times USD 80 times 12, which is USD 72,000 a year in licenses. At that size the strain is usually the number of contract variants and entities. The per-user list rate stays USD 80. Premium for all 75 would be 75 times USD 110 times 12, which is USD 99,000. Buy Premium only for the users whose work needs it.

What vendors publish for hours and calendar time

Ask each bidder to price a 25 to 75 user software-company project as its own statement of work. Anchor the services column to the prices the vendors publish, and keep every other cost on its own line.

Odoo Success Packs for a new customer, as of October 2026, are the published service prices:

• Basic (Price for a new customer: USD 3,060 · Hours: 25 · Notes on the page: 15 percent off the returning-customer price of USD 3,600, and only on the first pack)
• Standard (Price for a new customer: USD 5,950 · Hours: 50 · Notes on the page: One-time pack)
• Custom (Price for a new customer: USD 10,625 · Hours: 100 · Notes on the page: Includes customization)
• Pro (Price for a new customer: USD 21,250 · Hours: 200 · Notes on the page: Travel billed extra. Custom-module maintenance is an extra monthly charge)

Odoo says companies under 50 employees usually implement with Success Packs, and companies over 50 employees usually use a partner. The estimator says 80 percent of projects in that estimator's scope go to production in 200 hours or less. At an assumed 40-hour consultant week, 200 hours is five weeks of one consultant or about two and a half weeks of two, before your team's time. Odoo publishes the hours; the weeks depend on the workweek you assume. A scope that includes a chart of accounts, subscriptions, timesheets, and a straight-line deferral can fit a pack. A scope that includes standalone-selling-price allocation, usage imports from a product database, and several billing patterns may not. Ask the estimator which scope produced the 80 percent figure, and do not treat the pack price as the whole project if custom modules, Odoo.sh, or data migration sit outside it.

NetSuite's guide says implementation services typically cost two to three times the first-year license cost, suggests a 10 to 15 percent contingency, and gives 6 to 12 months for a big-bang go-live and 12 to 24 months for a phased rollout, plus three to six months of optimization. Those are that vendor's planning ranges, dated on the March 2026 guide. Use them on a NetSuite license quote. Leave them off the Business Central and Odoo columns. When someone adds only the USD 24,000 seat line to the budget, hand your CFO the line from NetSuite's guide: "Companies that budget only for software costs are quickly taken by surprise."

Our target for a first usable phase is 8 to 12 weeks. That target is ours, under the Flectic Accelerated Delivery Framework, and it covers the billing path your team uses every week, with a consultant reviewing the configuration.

If you want the surrounding delivery model, our ERP implementation approach spells out discovery, configuration, migration, training, and support after go-live as separate phases. The commercial page for this reader is ERP for professional services firms, which is where software, SaaS, and IT services companies start with us.

Where software firms pay twice

The expensive mistakes in this size range show up as a second license, a second project ledger, or a revenue workbook that survives go-live.

Budget the services lines even when the seat price looks small. Odoo's Pro pack at USD 21,250 is still a fraction of a year of a senior accountant, and it can be the wrong fraction if travel, custom-module maintenance, and migration are extra. The USD 24,000 for 25 Business Central Essentials users buys licenses alone, and configuration, data migration, and training stay unpriced until a bidder quotes them on separate lines. NetSuite's two-to-three-times planning language is one way to sketch a services budget after you have their license number. On any platform, demand separate lines for data migration, revenue configuration, integrations, training, and support after go-live. Add a contingency you can explain, in the 10 to 15 percent band NetSuite suggests or a band your CFO prefers, and label it as contingency.

Do not assume the cheap seat posts time. On Odoo the published light-user list omits timesheets, and an employee who reports a timesheet is a paying user. On Business Central, Team Members are USD 8 and limited. Until a licensing specialist shows a Team Member posting a project timesheet on your kind of job, price Essentials for everyone who must enter time. The worked example earlier moved the yearly license from USD 18,240 to USD 29,760 when twelve people flipped from no login to Essentials. That USD 11,520 gap is larger than Odoo's Standard Success Pack.

Keep PSA and ERP from both owning the project. For managed-service providers, ERP Research's IT services overview treats PSA tools such as ConnectWise, Autotask, and HaloPSA as the first system, and ERP as the financial step-up. That sequence can be right. It goes wrong when phase two rebuilds time entry inside the ERP while the PSA still bills the client. Write one sentence in the statement of work: which system is the record for time, which system creates the customer invoice, and which system holds deferred revenue. If the PSA remains the record for time, the ERP project needs an import and a reconciliation. A second timesheet in the ERP recreates the same hours.

Test milestone billing before you train the company. The report in that single post, a USD 36,000 contract landing entirely up front with a deferred balance that would not clear, belongs in the demo script. The same test belongs on Odoo if you use milestone invoicing plus a deferral. Run it on a copy of a real contract, with the amounts your auditors already know.

How to choose the platform and the first phase

Pick the platform that can post the contract you already sell. Then cut phase one until a named group of people can bill and close on it.

1. Write down the contract shapes from last quarter. Count flat monthly subscriptions, annual prepayments, usage bills, fixed-fee implementations, milestone jobs, and retainers. The shape with the most revenue is the acceptance test, whichever shape a vendor demo leads with.
2. Count heads in two columns. Column A is people who must create or approve financial entries or customer invoices. Column B is people who only enter time. Column B is where Odoo paying-user rules and Business Central seat type change the budget. Portal customers stay outside both columns.
3. Decide the revenue bar with your accountant before you watch demos. If every contract is one obligation recognized on a straight line, Odoo's USD 1,200 pattern may be the whole requirement. If you sell bundles, the bar is the five-step allocation, and the demo must show standalone selling prices next to any deferral schedule.
4. Ask each bidder for references from a software or IT services firm of similar headcount, plus the names of the people who will do the work and the hours those people will spend. Hours, names, references, and a phase plan are the buying criteria. A partner tier can sit in an appendix.
5. Split the price. Data migration, revenue setup, any integration to a PSA or a product database, training, and post-go-live support are separate lines. On Odoo, ask whether custom modules add the monthly maintenance charge described on the Pro pack, and who owns the code. On Business Central, ask whether subscription billing and projects stay inside Essentials for your roles.
6. Choose a first phase that a team can run. Finance, subscriptions or projects, and the revenue pattern you use most. Leave the second product catalog, the second entity, and the historical rebuild for a later phase unless the close is blocked without them.

Bring one real contract, last month's billing spreadsheet, and a headcount split of full users versus time-only staff. We will tell you if accounting software still fits, and if it does not, which platform and which phase to price first.

How Flectic can help

Flectic connects pipeline, delivery and finance on Dynamics 365 or Odoo for professional services firms, including IT services firms that bill projects, so the quote, the timesheet and the invoice match. Flectic sends a written proposal with a fixed price for each phase before work starts. Flectic's ERP for professional services firms covers utilization, WIP and invoicing in more detail. To start, book a free discovery call.

Sources

Dynamics 365 Business Central pricing (United States), Microsoft, October 2026

Manage subscription billing and revenue and expense recognition, Microsoft Learn, October 2024

Welcome to subscription billing, Microsoft Learn, October 2026

Project management, Microsoft Learn, July 2026

Project Operations pricing, Microsoft, October 2026

Odoo pricing, Odoo, October 2026

Odoo Success Packs, Odoo, October 2026

Deferred revenues, Odoo, October 2026

Subscriptions, Odoo, October 2026

FASB In Focus, ASU 2014-09, FASB, June 2020

IFRS 15 Revenue from Contracts with Customers, IFRS Foundation, October 2026

QuickBooks Online pricing, Intuit, October 2026

ERP for Software Companies: The Ultimate Guide, NetSuite, March 2026

Milestone billing and deferral thread, Microsoft Dynamics Community, October 2026

ERP Software for IT Services and Managed Services, ERP Research, August 2026