New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Two-tier ERP for company groups

Two-tier ERP keeps a headquarters ledger and a lighter system at each subsidiary. See USD and CAD license math, consolidation, and Canadian GST/HST filing.

Both platformsERP Fundamentals12 min readUpdated 15 sources

Key takeaways

  • Different market or country setup at the subsidiary, including Canadian GST/HST at a local company.
  • Standard to Custom: automatic once multi-company is turned on, except One App Free.
  • Name a golden customer, vendor, and product rule before subsidiaries create records.
  • One system: shared workflows, one integration surface, Business Central consolidation or Odoo multi-company.

What is two-tier ERP?

Two-tier ERP means a company group runs two ERP layers at the same time. Wikipedia describes it as one system at the corporate level and another at the division or subsidiary level, so regional sites can keep their own cycles and processes. TechTarget, in a definition published on 4 January 2024, puts tier 1 at corporate for financials and other shared processes, and tier 2 at divisions, subsidiaries, and smaller locations for local needs.

For an SME group in Canada or the United States, the practical version is a hub and spoke. Microsoft describes headquarters as the place that manages overall operations, with each site as a standalone entity. Sites are often geographically distributed, they need different information sharing, and they usually do not need the same complexity or the staff to run a large system.

The search phrase erp groups often lands on general ERP definitions. Those pages describe accounting and operations software. They skip the group design question: one heavy system for every company, or a headquarters ledger plus a lighter operating system. Two-tier is the second design. A single ERP that can run several workflows for the same function is the alternative Wikipedia names, because the divisions then stay in one system and skip a second integration.

Data still has to meet. Wikipedia lists the extra integration work, often enterprise application integration, as part of the pattern wherever figures must move between the two systems. TechTarget adds that master data needs diligent attention so customers, products, and accounts are not duplicated or inconsistent. The architecture is two systems with a governed handoff, and the handoff is part of the design.

Two-tier ERP and the tier labels buyers mix up

Two-tier ERP is an architecture: corporate financials in one system, local operations in another. A tier label on a product brochure is a different idea. It tries to sort whole product families by company size. That sort breaks down for an SME group buying Microsoft software, because Dynamics 365 Finance and Dynamics 365 Business Central are licensed and priced apart.

TechTarget's 4 January 2024 article discusses tier lists, including a 2023 view that places Microsoft Dynamics as a whole in tier 1. An SME group should ignore that lump. As of October 2026, Finance is USD 210 per user per month in the United States and CAD 284.90 in Canada, paid yearly. Business Central Essentials is USD 80 or CAD 108.50 on the same basis. Finance Premium is USD 300 or CAD 407. Business Central Premium is USD 110 or CAD 149.20. Those are different buying decisions.

Use the product and the job, not the tier slogan. Headquarters that needs group financials looks at Finance. An operating company that needs local orders, inventory, and statutory tax looks at Business Central, or at one Odoo database holding several companies. Odoo 19's multi-company setup is one database with aggregated figures, which is a different shape from two separate ERP products.

Governance has two common patterns in the TechTarget account. In a laissez-faire model, smaller locations pick their own ERP, and integration risk goes up. A short approved list, which can be the same vendor or a second vendor, keeps the number of mappings smaller. For a group of 20 to 100 people, the approved list is usually one headquarters product and one operating product.

How to read the names when you are buying for a group.
TermWhat it tells youWhat to do with it
Two-tier ERPCorporate system plus a subsidiary system, integratedDecide the handoff: consolidation, intercompany, and master data
Tier 1 or tier 2 as a product classA size label that can dump a whole vendor into one bucketPrice Finance and Business Central separately instead
One-database multi-companySeveral legal entities in one product, as in Odoo 19Use it when a second product would only add integration

When a second ERP at a subsidiary is the cheaper path

Wikipedia gives three reasons groups adopt two systems: manufacturing and sourcing spread across countries, faster and less costly subsidiary projects when the software suits a smaller company, and the integration work that comes with that choice. The third point is the bill you still pay. A cheaper license is only cheaper after you count the mapping, the eliminations, and the people who keep masters aligned.

TechTarget's use cases match the ways SME groups grow. A subsidiary sells into a different market. A local division needs country setup. An acquisition is too expensive to move onto the headquarters system. A site needs deeper manufacturing or supply chain function than the corporate ledger provides. Or the group wants a cloud system at some sites and keeps a legacy core at headquarters.

License math is the cleanest comparison, and it is licenses only. Assume ten full users at a subsidiary, paid yearly, as of October 2026, with no services and no tax. Ten Dynamics 365 Finance users list at USD 2,100 per month (10 times USD 210) or CAD 2,849 per month (10 times CAD 284.90). Ten Business Central Essentials users list at USD 800 per month or CAD 1,085 per month. The license gap is about USD 1,300 per month, or about CAD 1,764 per month, before the integration project. If that subsidiary would use Finance Premium instead of Finance, the headquarters-style seat is USD 300 or CAD 407, and the gap is wider.

Roll the site onto the headquarters product when the people, the chart of accounts, and the close calendar are already the same, and when you can staff the heavier system. Keep a second system when local tax, a different fiscal year, or an acquired process would force the corporate system to carry work it was not staffed for. Microsoft's hub-and-spoke note says smaller sites usually do not need that complexity or that staff.

A second system is the wrong savings story when the subsidiary is another warehouse under the same legal entity. Odoo does not create warehouses for you when you add a company. If the new activity shares the legal entity, the tax, and the currency, a warehouse and analytic accounts inside the current company avoid a second set of books.

  • Different market or country setup at the subsidiary, including Canadian GST/HST at a local company.
  • An acquisition whose move onto the headquarters system cannot be justified on cost or time.
  • A plant or warehouse that needs operating depth the corporate financial system is not staffed to run.
  • A cloud operating system beside a legacy core you are keeping at headquarters.
  • License gap on the worked example: about USD 1,300 or CAD 1,764 per month for ten users, licenses only, before integration.

What headquarters keeps and what the subsidiary runs

Headquarters keeps the work that has to be true once for the group: the consolidated ledger, the currency translation view, and the decision about which customer, vendor, and item records are shared. TechTarget assigns financials and other core common processes to that corporate layer. The subsidiary keeps local sales, purchasing, inventory, and statutory tax, because those cycles follow the local calendar and the local tax authority.

Business Central can consolidate general ledger entries from two or more companies into a consolidated company. The companies can sit in different environments, use different charts of accounts, different fiscal years, and different currencies. It can also import companies that use other accounting systems. The consolidation API is free to use. That is the feature that lets a lighter company still report upward.

After the numbers land, eliminating transactions that were recorded more than once is a manual process. You enter general journal lines, review them with the G/L Consolidation Eliminations report, then post. Budget time for that close step. A group that sells between its own companies will overstate revenue if those internal sales stay in the consolidated total.

Intercompany postings in Business Central create the sales and purchase documents and the general ledger entries across companies so the same workflow is not keyed twice. Odoo can auto-create the counterpart vendor bill, sales order, or purchase order, and it can synchronize stock moves. In both products, the documents are only as good as the fiscal positions, tax setup, and account mapping behind them.

A Business Central company can export consolidation data for a parent that uses Dynamics 365 Finance. That export is the path from a spoke company into a Finance headquarters ledger. Dual-write is a different product. It is Microsoft's near-real-time, bidirectional sync between finance and operations apps and Dataverse customer-engagement apps, covering customers, products, vendors, and prospect-to-cash. Subsidiary ledgers reach headquarters through consolidation and the Finance export.

A practical split for an SME group on Dynamics 365 or Odoo.
WorkHeadquartersOperating company
Group financialsFinance, or a Business Central consolidated companyLocal ledger, then a consolidation export or import
Chart, year, and currencyMapping and translation at consolidationLocal chart, fiscal year, and currency can differ
Internal salesElimination journals after consolidationIntercompany sales and purchase documents
Customers and productsMaster-data rules so records stay consistentLocal orders against the shared or mapped masters
Canadian taxConsolidated ledger entries only; the .tax file stays with the Canadian company.GST/HST calculation and the .tax file at the local company
CRM recordsDataverse sync where finance and operations apps use dual-writeSeparate from the ledger consolidation path

Stacks SME groups can buy with public prices

The stack the generic ERP pages skip is specific. Dynamics 365 Finance at headquarters, Business Central at the operating companies, and Business Central's consolidation export when the parent ledger is Finance. As of October 2026 the headquarters seat is USD 210 or CAD 284.90 per user per month, paid yearly. The operating seat on Essentials is USD 80 or CAD 108.50. Team Members, for lighter use, are USD 8 or CAD 10.90. Canadian list prices are plus applicable tax, and Microsoft says the listed prices are informational and may not match checkout because of currency, country, and regional variants.

Put Odoo beside that when the group wants several legal entities in one database. Odoo 19 can hold multiple companies, share products and contacts by default, keep cost company-specific, and show aggregated figures without a second product. That is one-database multi-company. It is the Wikipedia alternative in product form: configure the entities inside one system and avoid a second integration between two ERPs. Turning multi-company on for an Odoo Standard plan moves the subscription to Custom, with the exception of One App Free.

A mixed stack, Finance at headquarters and Odoo at the subsidiaries, still has the integration effort Wikipedia flags. There is no public license line for that connector. Treat the connection as a services scope, separate from either vendor's user price. Flectic sets the timeline for a first phase in the written scope. That scope covers the entities named in the phase.

Business Central online has more than 40 localized versions you install as extensions. The Canada product page says the product is trusted by 55,000 companies and is available in more than 50 languages and 157 countries. A separate pricing-overview line says more than 50,000 small and midsize businesses. The same Canada product page cites a Microsoft-commissioned Forrester Consulting Total Economic Impact study of a composite organization: more than 200 percent ROI over 3 years and a 6-month potential payback. Those two figures describe that composite study. They are not a published result for a Canadian two-tier project.

Stacks with a public license story as of October 2026.
HeadquartersOperating companiesHow the numbers meet
Dynamics 365 FinanceBusiness CentralConsolidation inside Business Central, then export for a Finance parent
Business Central consolidated companyOther Business Central companiesConsolidation across environments, charts, years, and currencies. API is free
One Odoo database on CustomCompanies inside that databaseAggregated figures in the same product. Standard upsells to Custom when multi-company is on
One ERP with several workflowsDivisions stay in that ERPWikipedia's alternative when a second system would only add integration

Business Central subsidiaries and a Finance parent

Can Business Central subsidiaries report into a parent on Dynamics 365 Finance? Yes. Microsoft says a Business Central company can export consolidation data for a parent that uses Dynamics 365 Finance. Inside Business Central, consolidation already accepts companies in different environments, with different charts of accounts, fiscal years, and currencies, and it can import companies that use other accounting systems.

The close has a manual elimination step. Internal sales that exist in both companies have to be removed or the group counts revenue twice. The sequence is: enter general journal lines, review them with the G/L Consolidation Eliminations report, then post. Put that sequence on the month-end calendar before you argue about software.

Intercompany postings create the sales document, the purchase document, and the general ledger entries across companies so staff do not key the same workflow twice. Intercompany postings record the daily trade in each company, while consolidation is the period report that rolls those books into one group total, so a group that trades internally and publishes one set of numbers needs both.

Dual-write answers a third problem. It keeps finance and operations apps and Dataverse customer-engagement apps in near-real-time sync for customers, products, vendors, and prospect-to-cash. Use it when sales records and the finance app must share those masters. Use consolidation and the Finance export when the question is the group ledger. Mixing the two names is how projects wire the wrong pipe.

Seat type still matters at the subsidiary. Essentials and Premium are the full-user prices above. Team Members are USD 8 or CAD 10.90 per user per month, paid yearly. Size the subsidiary on the work people do, then add the headquarters Finance seats only for the people who run the group ledger. A worked group is in the cost section.

GST/HST, GIFI, and consolidating Canadian companies

Business Central's Canada local functionality covers GST/HST and sales tax, use tax, electronic bank payments, and GIFI codes. For GST/HST, the product can calculate the provincial sales tax a purchaser must self-assess when the vendor charged only GST or HST. It can produce a .tax file through the GST/HST Internet File Transfer batch job. That is the filing artifact to expect from a Canadian company on Business Central.

Those tax features live on the company that has the Canadian registration. A US headquarters on Dynamics 365 Finance does not replace that local setup. The spoke company calculates and files. The headquarters company receives consolidated ledger entries, which can be in a different currency and on a different chart of accounts.

Consolidation is built for that mismatch. Two Canadian subsidiaries can use different charts and still post into one consolidated company. A Canadian company and a US company can use different currencies. Fiscal years can differ. The consolidation API is free. Eliminations stay manual, including when an intercompany sale crosses the border and would otherwise sit in both books.

Odoo's own multi-company documentation uses a US and Canada retail chain for the same reason: each country has its own tax laws, with inter-company transactions for cross-border inventory and sales in local currency. Fiscal positions and localizations have to be set or the generated documents are wrong. The Business Central Canada pages used here describe GST/HST, self-assessed provincial tax, and the .tax file.

Canadian Business Central list prices, as of October 2026, are plus applicable tax: Essentials CAD 108.50, Premium CAD 149.20, Team Members CAD 10.90, all per user per month, paid yearly. Finance is CAD 284.90 and Finance Premium is CAD 407 on the same basis. Microsoft says checkout can differ by currency, country, and regional variant.

One Odoo database versus a second ERP

Odoo 19 can hold multiple companies in one database. Products and contacts are shared by default. Cost can be company-specific. The product can generate aggregated figures without switching interfaces. That design is one-database multi-company. It is not two ERP products, and it is not the Wikipedia two-system pattern unless you also run a separate headquarters ERP beside it.

Does adding a second company force a move from Standard to Custom? On the Standard plan, turning on multi-company upsells to Custom. Yearly or multi-year contracts get an upsell order with a 30-day limit. Monthly contracts switch at the next bill. One App Free is exempt, and multi-company is allowed on that plan. One App Free is one app, unlimited users, hosted on Odoo Online, at USD 0.

For the discounted first 12 months for the initial users ordered, Standard is shown at USD 31.10 per user per month, with USD 24.90 also on the page and a struck-through USD 38.90. Custom is shown at USD 61.00, with USD 49.00 also on the page and a struck-through USD 76.20. Standard is Odoo Online and is not the multi-company plan. Custom includes multi-company, Studio, the external API, and hosting on Odoo Online, Odoo.sh, or on-premise. Odoo.sh hosting is extra. Odoo’s pricing page shows those amounts in US dollars and does not list a CAD price, so the Odoo figures in this guide stay in USD.

Inter-company settings can auto-create the counterpart vendor bill, sales order, or purchase order, and they can synchronize stock moves. Set fiscal positions and localizations first. Extra companies do not get warehouses automatically, so a new company is a setup project, not a checkbox that copies the building.

Should a new product line be a new company or another warehouse and analytic account? If it is the same legal entity, the same tax, and the same currency, keep it in the current company and add a warehouse and analytic accounts. Add a company when the unit has its own tax laws, as in Odoo's US and Canada retail example, or when records such as cost must stay company-specific. Add a second ERP product only when headquarters already standardizes on something else and the Odoo companies are the operating layer. That last choice brings the integration work Wikipedia describes.

  • Standard to Custom: automatic once multi-company is turned on, except One App Free.
  • Yearly or multi-year: upsell order with a 30-day limit. Monthly: switch on the next bill.
  • Shared by default: products and contacts. Cost can stay company-specific.
  • Light user: USD 8.90, quote required, limited to that person's own HR, expenses, point of sale, shop floor, and similar tasks.
  • Subscription plans do not include implementation services.

Master data, intercompany documents, and eliminations

TechTarget's warning is the operating rule: master data management needs diligent attention so data is not duplicated or inconsistent. Decide which records are shared, which stay local, and who may create a customer or a product. A laissez-faire model, where each site picks tools and codes, raises the integration risk. A short approved list keeps the mapping set small enough for a finance team of a few people.

How do you consolidate companies that use different charts of accounts, fiscal years, or currencies? In Business Central you consolidate into a consolidated company. The source companies may use different charts, different fiscal years, and different currencies, and they may live in different environments. Other accounting systems can be imported. The consolidation API is free. The mapping is the work: each source account still needs a target account, and each currency still needs a rate policy you can explain to an auditor.

How are intercompany sales eliminated so group revenue is not counted twice? Record the sale and the purchase through intercompany postings so both books exist. At consolidation, remove the amounts that were recorded more than once. In Business Central that removal is manual: general journal lines, the G/L Consolidation Eliminations report, then post. Skipping the journal leaves internal revenue in the group total.

Odoo inter-company automation creates the other side of the document and can sync stock moves. If the fiscal position is wrong, the bill is wrong on both sides, and the elimination has nothing clean to reverse. Extra companies still need their own warehouses. Products shared by default will show the same item in both companies, which is what you want for a group catalog and what you must override when cost is local.

Dual-write stays in its lane. It syncs finance and operations apps with Dataverse for customer-engagement records. It is the wrong tool for the question 'does this subsidiary ledger roll into headquarters?' That question is consolidation, and for a Finance parent it is the Business Central export. Sequence the project as masters first, then intercompany documents, then the consolidation and elimination close. Analytics on top of unmapped accounts will repeat the mess in a dashboard.

  • Name a golden customer, vendor, and product rule before subsidiaries create records.
  • Map charts of accounts as part of consolidation, including companies on other accounting systems.
  • Schedule elimination journals on every close, reviewed with the G/L Consolidation Eliminations report.
  • Keep dual-write on CRM and finance-app masters, and keep the group ledger on consolidation.
  • On Odoo, set fiscal positions and localizations before auto-created inter-company documents.

License math in USD and CAD, and what services cost

Separate licenses from services. As of October 2026, Microsoft publishes the user prices below, paid yearly. Canadian prices are plus applicable tax, and the Canada pricing page says listed prices are informational and may not match checkout. Odoo prices below stay in USD because the pricing page shows those amounts in US dollars and does not list a CAD price. The first-12-month discount applies to the initial users ordered. The page shows two live amounts plus a higher struck-through amount, so all three are listed.

Worked license example, assumptions stated. Headquarters has 8 Dynamics 365 Finance users. Two operating companies have 6 Business Central Essentials users each (12) and 4 Team Members each (8). The example uses Finance, Business Central Essentials, and Team Members, licenses only, paid yearly, as of October 2026. United States list: 8 times USD 210 is USD 1,680, 12 times USD 80 is USD 960, and 8 times USD 8 is USD 64. Together that is USD 2,704 per month, or USD 32,448 for a year of licenses. Canada list, before tax: 8 times CAD 284.90 is CAD 2,279.20, 12 times CAD 108.50 is CAD 1,302, and 8 times CAD 10.90 is CAD 87.20. Together that is CAD 3,668.40 per month, or CAD 44,020.80 for a year, plus applicable tax. Change the user counts and the total changes in a straight line.

The same headcount on Odoo Custom, using the USD 61.00 figure for the discounted first 12 months for initial users, is 28 users times USD 61, or USD 1,708 per month. The page also shows USD 49.00 beside USD 61.00, which would be USD 1,372 per month, and a struck-through USD 76.20, which would be USD 2,133.60 per month. That comparison is one database with multi-company, not Finance plus Business Central, and it excludes Odoo.sh hosting if you choose that option. Standard at USD 31.10, or the USD 24.90 also shown, is not the plan that includes multi-company.

Where can you get implementation services, and how much do they cost? Odoo says companies under 50 employees usually buy Success Packs directly from Odoo, companies over 50 employees usually use a partner, and companies over 250 employees should contact Odoo. Subscription plans do not include implementation. For a new customer, the first pack only is discounted 15 percent: Starter, 4 hours, USD 493; Basic, 25 hours, USD 3,060; Standard, 50 hours, USD 5,950; Custom, 100 hours, USD 10,625; Pro, 200 hours, USD 21,250. Returning-customer prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Travel time and expenses are extra. The packs are aimed at companies under 50 employees. Odoo states a 98 percent implementation success rate with a Success Pack versus 65 percent without one, and labels the comparison self-reported. For the estimator's sample scope, Odoo says 80 percent of projects are in production in 200 hours or less.

Microsoft's pricing pages publish user licenses. A services package for a Finance plus Business Central rollout is outside those pages. Flectic sets the timeline and a fixed price for each phase in the written proposal, and delivery is designed to deliver up to 3x faster than a traditional rollout. The timeline and the speed target apply to scope you agree up front. The license table stands on its own. The Forrester composite on Microsoft's Canada page is a separate study of one composite organization.

List licenses as of October 2026, per user per month, paid yearly.
LicenseUSDCAD, plus applicable tax
Business Central Essentials80.00108.50
Business Central Premium110.00149.20
Business Central Team Members8.0010.90
Dynamics 365 Finance210.00284.90
Dynamics 365 Finance Premium300.00407.00
Odoo Standard, discounted first 12 months for initial users31.10, with 24.90 also shown (struck-through 38.90)USD on the pricing page
Odoo Custom, discounted first 12 months for initial users61.00, with 49.00 also shown (struck-through 76.20)USD on the pricing page
Odoo Light User8.90, quote requiredUSD on the pricing page
Odoo One App Free0Shown as a free plan on the USD pricing page

When one system is the better group design

Wikipedia's alternative is one ERP that can configure multiple workflows for the same function. Divisions stay in that system and you do not build a second integration. Choose that path when the companies share a close, a chart you are willing to standardize, and a team that can support one product. Business Central's own multi-company consolidation exists so several Business Central companies can report together without a second vendor.

Choose Odoo multi-company on Custom, or on One App Free when that single app covers the work, if the group wants one database, shared products and contacts, and aggregated figures. Pay the Standard-to-Custom upsell with open eyes: a 30-day limit on the upsell order for yearly or multi-year contracts, or the next bill for monthly contracts. If the new work is a product line inside the same legal entity, add a warehouse and analytic accounts. A new company does not arrive with warehouses.

Choose two products when the headquarters ledger and the subsidiary operations are different jobs with different staff. Finance at USD 210 or CAD 284.90 for the group accountants, Business Central Essentials at USD 80 or CAD 108.50 for the operating users, and a written elimination step so internal sales drop out of group revenue. The integration effort Wikipedia describes is the cost of that freedom. A laissez-faire set of local systems multiplies it.

Walk away from a second system when the only goal is a lower user price and the subsidiary will still need the headquarters process, the headquarters chart, and the headquarters staff to close. In that case the license gap in the ten-user example is real, and the second implementation plus the monthly mapping can spend it. Also walk away from treating the Forrester composite, more than 200 percent ROI over 3 years and a 6-month potential payback, as the expected return on your two-tier project. Microsoft commissioned that study for a composite organization.

  • One system: shared workflows, one integration surface, Business Central consolidation or Odoo multi-company.
  • New company in Odoo: own tax or own legal entity. Warehouse plus analytic accounts: same entity, new activity.
  • Two products: headquarters financials and local operations that you cannot staff as one system.
  • Approved vendor list: fewer mappings than each site choosing its own ERP.
  • Services: quote Success Packs only for the under-50 Odoo scope they were published for.

How Flectic can help

Flectic implements Odoo and Dynamics 365 for companies of 20 to 100 people in the US and Canada, including subsidiaries that run their own system next to a group ERP. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. Read how Flectic runs an ERP implementation, then book a free discovery call to start.

Sources

  1. Two-tier ERP is two ERP systems at once, one corporate and one at division or subsidiary level, so regional sites keep their own cycles and processes. Drivers include globalization of manufacturing and sourcing, quicker and less costly subsidiary implementations, and extra integration effort. An alternative is one ERP with multiple workflows for the same function.

    en.wikipedia.orgChecked 2026-10
  2. TechTarget published 2024-01-04: tier 1 at corporate for financials and shared processes, tier 2 at divisions and smaller sites. Master data needs diligent attention. Governance is laissez-faire or a short approved list. Use cases include a different market, country customization, acquisitions, industry depth, and SaaS beside a legacy core.

    techtarget.comChecked 2026-10
  3. Hub-and-spoke: headquarters manages overall operations, each site is standalone, sites are often geographically distributed, and they usually do not need the same complexity or staff. Intercompany postings create sales and purchase documents and general ledger entries across companies.

    learn.microsoft.comChecked 2026-10
  4. Business Central online has more than 40 localized versions as extensions. Canada local functionality includes GST/HST and sales tax, use tax, electronic bank payments, and GIFI codes.

    learn.microsoft.comChecked 2026-10
  5. For Canadian GST/HST, Business Central can calculate provincial sales tax the purchaser must self-assess when the vendor only charged GST or HST, and it can produce a .tax file through the GST/HST Internet File Transfer batch job.

    learn.microsoft.comChecked 2026-10
  6. Business Central consolidates general ledger entries from two or more companies, including different environments, charts of accounts, fiscal years, and currencies, and can import other accounting systems. The consolidation API is free. Eliminations are manual via general journal lines, the G/L Consolidation Eliminations report, then post. A company can export consolidation data for a parent on Dynamics 365 Finance.

    learn.microsoft.comChecked 2026-10
  7. Dual-write is near-real-time bidirectional sync between finance and operations apps and Dataverse customer-engagement apps for customers, products, vendors, and prospect-to-cash. It does not roll a subsidiary ERP into a headquarters ledger.

    learn.microsoft.comChecked 2026-10
  8. Canada Business Central product page: trusted by 55,000 companies, 50+ languages and 157 countries. A pricing-overview line says more than 50,000 small and midsize businesses. The page cites a Microsoft-commissioned Forrester composite study showing more than 200% ROI over 3 years and a 6-month potential payback.

    microsoft.comChecked 2026-10
  9. Business Central US list prices as of October 2026, per user per month paid yearly: Essentials USD 80, Premium USD 110, Team Members USD 8.

    microsoft.comChecked 2026-10
  10. Business Central Canada list prices as of October 2026, per user per month paid yearly, plus applicable tax: Essentials CAD 108.50, Premium CAD 149.20, Team Members CAD 10.90. Listed prices are informational and may not match checkout because of currency, country, and regional variants.

    microsoft.comChecked 2026-10
  11. Dynamics 365 Finance US list prices as of October 2026, per user per month paid yearly: Finance USD 210, Finance Premium USD 300.

    microsoft.comChecked 2026-10
  12. Dynamics 365 Finance Canada list prices as of October 2026, per user per month paid yearly, plus applicable tax: Finance CAD 284.90, Finance Premium CAD 407.

    microsoft.comChecked 2026-10
  13. Odoo 19 multi-company is one database. Products and contacts are shared by default, cost can be company-specific, and aggregated figures do not require a second interface. A US and Canada retail chain is the documented cross-border case. Standard upsells to Custom when multi-company is on, with a 30-day upsell limit on yearly or multi-year contracts and the next bill on monthly contracts. One App Free is exempt. Inter-company can auto-create the counterpart document and sync stock. Extra companies do not get warehouses automatically. Fiscal positions and localizations must be set.

    odoo.comChecked 2026-10
  14. Odoo pricing as of October 2026, discounted first 12 months for initial users ordered: Standard USD 31.10 with USD 24.90 also shown and struck-through USD 38.90, Odoo Online, not a multi-company plan. Custom USD 61.00 with USD 49.00 also shown and struck-through USD 76.20, includes multi-company, Studio, external API, Odoo Online, Odoo.sh, or on-premise, Odoo.sh extra. Light user USD 8.90, quote required. One App Free USD 0, one app, unlimited users, multi-company allowed. Under 50 employees usually buy Success Packs from Odoo, over 50 usually use a partner, over 250 should contact Odoo. Plans exclude implementation services. No CAD list price was shown.

    odoo.comChecked 2026-10
  15. Odoo Success Packs, new customer first pack 15 percent off: Starter 4 hours USD 493, Basic 25 hours USD 3060, Standard 50 hours USD 5950, Custom 100 hours USD 10625, Pro 200 hours USD 21250. Returning prices USD 580, 3600, 7000, 12500, and 25000. Travel extra. Aimed at companies under 50 employees. Self-reported 98 percent success with a Success Pack versus 65 percent without. For the estimator sample scope, 80 percent of projects are in production in 200 hours or less.

    odoo.comChecked 2026-10

Frequently asked questions

What is two-tier ERP?

Two-tier ERP means the group runs a corporate ERP and a second ERP at divisions or subsidiaries at the same time. Headquarters keeps financials and shared processes. Local sites keep their own cycles. The systems have to be integrated wherever numbers move between them, which Wikipedia treats as part of the pattern.

When is a second ERP at a subsidiary cheaper than rolling that site onto headquarters?

It is cheaper on licenses when the subsidiary can run Business Central instead of Dynamics 365 Finance. Ten Essentials users list at USD 800 or CAD 1,085 per month, versus USD 2,100 or CAD 2,849 for ten Finance users, paid yearly, as of October 2026, licenses only. The second system still adds integration. It fits a different market, a country setup such as Canadian GST/HST, an acquisition that stays off the headquarters system, or a site that needs operating depth the corporate team will not staff.

How do you consolidate companies that use different charts of accounts, fiscal years, or currencies?

Business Central consolidates general ledger entries from two or more companies into a consolidated company. Those companies can use different charts of accounts, fiscal years, and currencies, and they can sit in different environments. Other accounting systems can be imported. The consolidation API is free to use. Account mapping and exchange rates are still configuration you own.

How are intercompany sales eliminated so group revenue is not counted twice?

Intercompany postings create the sales and purchase documents and the ledger entries in each company so the trade is recorded once per book. At consolidation, amounts recorded more than once are removed. In Business Central that step is manual: enter general journal lines, review them with the G/L Consolidation Eliminations report, then post.

Can Business Central subsidiaries report into a parent on Dynamics 365 Finance?

Yes. Microsoft documents an export of consolidation data from a Business Central company to a parent that uses Dynamics 365 Finance. Consolidation inside Business Central can already span companies, charts, years, and currencies. Dual-write syncs finance and operations apps with Dataverse customer-engagement apps, which is a separate path from that export.

Does dual-write connect two ERPs, or only finance and operations apps to Dataverse?

Dual-write is near-real-time, bidirectional sync between finance and operations apps and Dataverse. It covers records such as customers, products, vendors, and prospect-to-cash. Subsidiary ledgers reach a headquarters company through Business Central consolidation and the export to Dynamics 365 Finance.

What Canadian tax file does Business Central produce for GST/HST?

The GST/HST Internet File Transfer batch job produces a .tax file. Canadian local functionality also covers GST/HST and sales tax, use tax, electronic bank payments, and GIFI codes. When a vendor charges only GST or HST, Business Central can calculate the provincial sales tax the purchaser must self-assess.

Does adding a second company in Odoo force a move from Standard to Custom?

Turning on multi-company on the Standard plan upsells to Custom. Yearly or multi-year contracts receive an upsell order with a 30-day limit. Monthly contracts switch at the next bill. One App Free is exempt, and multi-company is allowed on that free plan. One App Free is limited to one app.

Where can I get implementation services, and how much do they cost?

Odoo subscriptions do not include implementation. Under 50 employees, Odoo sells Success Packs: a first-pack discount puts 4 hours at USD 493 and 200 hours at USD 21,250, with steps at 25, 50, and 100 hours. Over 50 employees, Odoo says companies usually use a partner, and over 250 they should contact Odoo. Microsoft does not publish a services price for a two-tier rollout. Flectic quotes that work as a phase, with the timeline and a fixed price in the written proposal.

Should a new product line be a new company or another warehouse and analytic account?

If it shares the legal entity, the tax, and the currency, keep it in the current company and add a warehouse and analytic accounts. Add a company when the activity has its own tax laws, which is the situation in Odoo's US and Canada retail example, or when cost and other records must stay company-specific. A new Odoo company does not receive warehouses automatically, and on Standard it upsells the database to Custom.

More on the blog: Implementation and go-live