Key takeaways
- At enterprise scale, choose an ERP by how it models legal entities, ledgers and accounting standards, and by how it fits your integration platform, not by module count.
- SAP S/4HANA and Oracle Fusion Cloud ERP are the broadest suites for global, multi-industry groups; Dynamics 365 Finance and Supply Chain Management is the natural fit for Microsoft-centric enterprises and the only one here with public list prices.
- Workday suits finance- and HR-led service enterprises; Infor and IFS suit companies whose industry, such as manufacturing, distribution or asset-intensive operations, is the main requirement.
- GAAP and IFRS are handled differently: SAP uses parallel ledgers fixed at scoping, Oracle uses primary and secondary ledgers, Dynamics 365 uses posting layers, Workday uses book codes. Decide this design before go-live.
- Licenses are rarely the largest cost. Implementation, data migration, integrations and the internal ERP team usually decide the total.
The best enterprise ERP is the one that fits your entity structure, accounting standards and integration landscape. SAP S/4HANA and Oracle Fusion Cloud ERP are the broadest suites for global, multi-industry groups. Microsoft Dynamics 365 Finance and Supply Chain Management is the natural fit for enterprises built on Microsoft 365 and Azure. Workday Financial Management suits finance- and HR-led service enterprises, and Infor CloudSuite and IFS Cloud suit companies whose industry processes come first.
We build integrations and custom services around ERP and CRM platforms, so this guide looks at each suite the way an integration engineer does: how it models ledgers and entities, how it connects to the rest of your landscape, and where custom work tends to land. We resell none of these products and are not a certified partner of any vendor. Prices are list prices as of November 2026; only Microsoft publishes them, and we say where a product is quote-based.
Quick picks
| Best for | Pick | Multi-GAAP approach | Starting price |
|---|---|---|---|
| Global, multi-industry groups | SAP S/4HANA Cloud | Parallel ledgers, set at scoping | Quote-based |
| Finance-led global enterprises | Oracle Fusion Cloud ERP | Primary and secondary ledgers | Quote-based |
| Microsoft 365 and Azure enterprises | Dynamics 365 Finance + SCM | One ledger, up to 10 posting layers | $210/user/month each, annual |
| Service enterprises on Workday HCM | Workday Financial Management | Book codes | Quote-based |
| Manufacturing and distribution verticals | Infor CloudSuite | Multiple financial sets of books (CloudSuite Industrial) | Quote-based |
| Asset-intensive, project and service businesses | IFS Cloud | Ask | Quote-based |
Take the fit check before comparing features. It shows whether the suite itself is the main decision or whether your integration layer deserves as much attention.
How enterprise ERPs handle entities, ledgers and standards
At enterprise scale, the ERP’s financial design matters more than any single feature. Four questions decide most of it.
- Legal entities and ledgers. How many legal entities share one instance, how charts of accounts are shared or mapped, and how intercompany transactions are recorded on both sides.
- Accounting standards. A group reporting under IFRS with subsidiaries filing local GAAP, or a US group with IFRS reporting abroad, needs every difference, such as leases, revenue and fixed asset depreciation, recorded somewhere auditable. The suites do this differently, and the choice is often hard to change later.
- Consolidation. Currency translation, eliminations, minority interest and the timing of the close, often in a separate group reporting tool.
- Two-tier landscapes. Subsidiaries on smaller ERPs that feed the group system, with their own mappings and cutoffs.
SAP’s help documentation for S/4HANA Cloud describes parallel accounting through parallel ledgers, with a leading ledger and optional IFRS and US GAAP ledgers chosen during scoping; SAP recommends assigning the group standard to the leading ledger for groups, and ledgers cannot be removed after activation. Microsoft Learn says each legal entity in Dynamics 365 Finance has one ledger, with up to 10 posting layers to track the adjustments for additional standards, and gives an IFRS 16 lease example using a custom layer. Workday describes book codes that let one transaction be reported on IFRS, local GAAP or a management basis without duplicating data.
None of these is wrong. Parallel ledgers give full balances per standard at the cost of more data. Posting layers and book codes keep one set of transactions and add adjustments. What matters is that your accounting team designs it with the implementer before configuration starts.
The shortlist in depth
SAP S/4HANA Cloud: best for global, multi-industry groups
Fits: large manufacturers, distributors, utilities and conglomerates running many entities and complex supply chains, and companies already on SAP ECC.
Strengths: the broadest functional scope here, with deep finance, procurement, manufacturing, supply chain and industry solutions. Parallel ledgers support several accounting standards, and SAP offers Group Reporting for consolidation. SAP Integration Suite and a very large partner ecosystem cover most integration needs.
Limits: the public cloud edition favors standard processes; the private edition allows more flexibility at higher cost. Ledger design is fixed early: SAP’s help says activated ledgers cannot be removed later. Migrations from ECC are multi-year programs.
Pricing: quote-based. SAP does not publish list prices for S/4HANA Cloud; licensing is usually sold through RISE with SAP and based on usage metrics rather than plain named users.
Integration note: decide early which integrations go through SAP Integration Suite and which through your existing platform. Running both without a rule creates two places where record ownership lives.
Oracle Fusion Cloud ERP: best for finance-led global enterprises
Fits: global enterprises where finance, procurement, planning and project accounting drive the selection, and companies already on Oracle E-Business Suite.
Strengths: Oracle’s financials page describes a single cloud platform for multi-entity, multi-currency and multi-GAAP operations. Fusion uses primary and secondary ledgers and reporting currencies for multi-GAAP, and the suite includes planning and close tools under the same vendor. Quarterly updates arrive on a fixed schedule.
Limits: supply chain and manufacturing are strong but a separate buying decision. Oracle’s price lists use metrics such as hosted employees for many services, which makes comparisons with per-user quotes harder.
Pricing: quote-based in practice. Oracle publishes a Fusion Cloud global price list, but enterprise deals are negotiated and depend on metrics and bundles.
Integration note: Oracle Integration is the first-party integration platform. Check bulk import limits and the scheduling of file-based data imports if subsidiaries post high volumes.
Dynamics 365 Finance and Supply Chain Management: best for Microsoft-centric enterprises
Fits: enterprises on Microsoft 365, Entra ID and Azure, with complex manufacturing, warehousing or many legal entities.
Strengths: deep finance and supply chain on the Microsoft stack, with Power BI, Power Platform and Dataverse alongside. Multi-GAAP works through posting layers within each legal entity’s ledger, and Microsoft documents dual reporting for IFRS 16 leases. It is the only suite here with public list prices.
Limits: one ledger per legal entity means multi-GAAP relies on posting layers and report design, which your accountants should review early. Implementations need an experienced partner, and quality varies widely.
Pricing: Finance $210 and Supply Chain Management $210 per user per month, billed yearly; Finance Premium and Supply Chain Management Premium $300. Microsoft’s licensing guide describes cheaper licenses for additional apps and light users.
Integration note: respect Dataverse and service API limits in bulk integrations; our enterprise CRM guide lists the default limits. Dual-write keeps Finance and Dynamics 365 Sales in sync, but it is still an integration with its own failure modes.
Workday Financial Management: best for service enterprises on Workday HCM
Fits: professional services, financial services, education, healthcare and other service enterprises where people costs dominate and Workday HCM already runs HR.
Strengths: Workday describes real-time consolidation across entities, currencies and books, with intercompany eliminations generated as transactions occur, plus currency translation, noncontrolling interest and equity pickup. Book codes support reporting under several standards. Finance and HR share one data model.
Limits: Workday is not built for manufacturing or complex inventory. Companies with physical supply chains pair it with another system, which adds integration.
Pricing: quote-based, sold directly by Workday.
Integration note: Workday offers its own integration tooling and web services. Plan how operational systems, such as procurement, billing or projects, post to Workday’s ledger and where their detail lives.
Infor CloudSuite: best for manufacturing and distribution verticals
Fits: manufacturers and distributors in industries Infor targets with dedicated suites, such as industrial manufacturing, food and beverage, fashion and distribution.
Strengths: industry functionality that other suites cover through partners or add-ons. Infor’s documentation for CloudSuite Industrial describes multiple financial sets of books, each with its own fiscal calendar, chart of accounts and currency. Infor ION is its integration middleware.
Limits: each CloudSuite is a different product with its own history, so capabilities vary by suite. Check that the multi-book and consolidation features you need exist in the specific CloudSuite you are buying.
Pricing: quote-based.
Integration note: if you already run an enterprise integration platform, decide how ION fits beside it before go-live.
IFS Cloud: best for asset-intensive, project and service businesses
Fits: aerospace and defense, energy, utilities, construction and engineering, and service-heavy manufacturers.
Strengths: enterprise asset management, field service and project-based ERP in one platform, which suits companies whose revenue depends on assets and service contracts as much as on products.
Limits: we did not find official documentation of a dedicated multi-GAAP ledger design, so ask IFS how IFRS and local GAAP are run in parallel and see it demonstrated. The partner ecosystem is smaller than SAP’s, Oracle’s or Microsoft’s.
Pricing: quote-based.
Integration note: ask for API documentation and event options early; asset and service data often feed several other systems.
Also worth a look: NetSuite OneWorld is common in companies at the boundary between mid-market and enterprise, with multi-subsidiary consolidation through OneWorld and Multi-Book. None of our published case studies covers NetSuite; see our NetSuite integration guide and the mid-sized ERP guide.
Comparison: enterprise capabilities
| SAP S/4HANA | Oracle Fusion | D365 F&SCM | Workday | Infor CloudSuite | IFS Cloud | |
|---|---|---|---|---|---|---|
| Multi-GAAP design | Parallel ledgers | Primary and secondary ledgers | Posting layers | Book codes | Multiple sets of books (Industrial) | Ask |
| Consolidation | Group Reporting | Yes | Yes | Real-time, vendor claim | Ask | Ask |
| Manufacturing and supply chain | Very strong | Strong | Strong | Not a focus | Strong, by industry | Strong for assets and projects |
| First-party integration platform | SAP Integration Suite | Oracle Integration | Power Platform, Azure | Workday integration tools | Infor ION | Ask |
| Partner ecosystem | Largest | Large | Large | Workday and partners | Medium | Medium |
| Public list prices | No | Price list, negotiated | Yes | No | No | No |
This table summarizes vendor documentation. Confirm specifics, especially multi-GAAP and consolidation, for the edition you are buying.
Planning the program: integrator, phases and the integration layer
Enterprise ERP projects are programs, not installations. Three decisions shape them more than the product does.
The systems integrator. Ask for named leads in finance, supply chain, data migration and integration, references from companies with a similar entity structure, and a clear split between what the integrator builds and what your team owns after go-live. Integrators are usually strongest in configuration; check their integration and data migration track record separately.
The rollout sequence. Most groups go live in waves: the financial core and group reporting first, or one region or business unit as a pilot, followed by the rest. Each wave means a period when old and new ERPs run side by side and both feed consolidation. That interim state needs its own mappings, reconciliations and monitoring, and it often lasts longer than planned.
The integration layer. Decide before the first wave which platform carries integrations, which events and APIs each system publishes, and which system owns customers, suppliers, items, prices and open documents. Without that, every wave adds point connectors that are hard to retire. Write the ownership rules down in one place and make the integrator follow them.
A useful test of readiness: can your team draw the landscape on one page, with every interface, its direction, its owner and how failures are reported? If not, the program will discover the answers during testing, which is the most expensive time to do it.
What it costs over three years
For an enterprise ERP with 500 users, licenses are the smaller part of the bill. A systems integrator, data migration, testing, integrations, change management and an internal ERP team usually exceed licenses over three years, often by a wide margin. The calculator uses Microsoft’s list prices and labeled assumptions for the quote-based suites; the setup and yearly figures are placeholders you should replace with your own quotes. Our ERP implementation cost guide breaks down where implementation money goes.
When a custom layer is the better answer
Large companies should buy their financial core. Ledgers, consolidation, tax and audit trails are mature in these suites and costly to rebuild. Custom software earns its place around them:
- An integration layer you own. Record ownership, ID mapping, retries and monitoring in one place, rather than scattered across connectors from each vendor. This matters most in two-tier landscapes and during a multi-year migration, when old and new ERPs run side by side.
- Portals for many light users. Dealers, suppliers or field staff who need a few screens. A portal that reads and writes ERP data through an API, with single sign-on, can cost less than ERP licenses for each of them. OSKI developers built modules for the HS High Stake business portal, which links a German division, its dealers and its employees, on .NET with IdentityServer4 and Hangfire.
- Unique planning or matching logic. Scheduling, allocation or pricing that defines your business is easier to build and test as services than as ERP customizations, as on the EM2 event platform, where 8 .NET microservices on Azure handle scheduling and attendee matching.
- Data migration tooling. Moving years of history and open items needs repeatable, logged pipelines, not one-off scripts.
Before you sign: a checklist
Ask for a sandbox and run these tests with your own structure, data and identity provider:
- Model your real entity structure, including one subsidiary under local GAAP and the parent under IFRS. Post a lease and a revenue contract, and produce both sets of statements.
- Run a consolidation with currency translation, intercompany eliminations and a minority interest. How long does it take, and what is manual?
- Sign in through your identity provider and remove a test user there. Does ERP access end without manual steps? Does segregation of duties reporting catch a conflicting role?
- Load 1 million journal lines through the bulk import or API. How long does it take, and where are rejected lines reported?
- Connect your CRM or one subsidiary ERP through your integration platform. Which side owns customers, items and prices, and how are conflicts resolved?
- Push a configuration change from a test environment to production. Is it repeatable and auditable?
- Ask for the full price of your configuration in writing: licenses, environments, storage, integration platform, support tier and renewal caps.
Where OSKI fits
OSKI is a software engineering company, not an ERP reseller or certified partner, so we do not sell licenses or run ERP implementations. We help enterprises with the work around the platform: integrations and event-driven services, .NET development and cloud and DevOps for the services and portals that sit next to the ERP, and custom ERP modules where the suite does not fit. Send us your landscape and we will tell you where custom work pays off and where configuration is enough.
- Each standard has its own ledger
- Full balances per standard
- SAP: ledgers fixed during scoping
- One ledger per legal entity
- Up to 10 layers for adjustments
- Reports combine layers per standard
- One transaction, tagged by book
- Adjustments recorded per standard
- Report on IFRS or local basis
From SAP Help, Microsoft Learn and Workday product pages, as summarized in this article. Infor CloudSuite Industrial documents multiple financial sets of books.
Microsoft US list prices per user per month, billed yearly, November 2026. SAP, Oracle, Workday, Infor and IFS are quote-based.
- Identity provider → SSO, roles and segregation of duties ERP
- ERP ⇄ Events and APIs, one owner per record Integration layer
- Integration layer ⇄ Customers, orders, credit status CRM
- Dealer portal ⇄ Light users, no ERP license each Integration layer
- Subsidiary ERPs → Two-tier: mapping and timing of consolidation ERP
- CRM ⇄ Direct point connectors scatter ownership rules ERP
● Works natively● Partial or one-way● Needs custom work
Architecture pattern drawn from this article and our integration work.
Buy, connect or build: which enterprise ERP setup fits you?
Six questions about your entities, standards and landscape. The result shows how strongly your answers point to an ERP suite as-is, a suite plus an integration layer, or custom services around it.
Answer all questions to see your result.
What it costs over the years you keep it
- Licenses
- —
- Setup and upkeep
- —
- Total
- —
- Per user per month
- —
Dynamics 365 figures are Microsoft US list prices in November 2026, billed yearly, before taxes, negotiated discounts and Microsoft's cheaper attach and light-user licenses. SAP, Oracle and Workday are quote-based and often licensed by full-use equivalents or employees rather than named users, so their figures are planning assumptions from third-party estimates, not vendor prices. Infor and IFS are quote-based and not included. Setup and yearly figures are illustrative placeholders for a systems integrator, data migration, integrations and an internal ERP team; replace them with your own quotes.
Sources
Based on the following official vendor and regulator materials:
- SAP Help: Parallel accounting in SAP S/4HANA Cloud
- Oracle: Financial management
- Microsoft: Dynamics 365 Finance pricing
- Microsoft Learn: Post fixed asset transactions to posting layers
- Workday: Financial close and consolidation
- Infor Documentation: Multiple financial sets of books


