.svg)
Consolidation solutions per ERP: Excel, consolidation tool or heavier ERP? (2026)
Per ERP, there are three paths to consolidated figures: in Excel, in a specialised consolidation tool, or via a heavier ERP with built-in consolidation. The choice that determines whether consolidation costs days or minutes per close.
.png)
Three paths to consolidated figures: Excel (3 days/month), a consolidation tool (10 minutes) or a heavier ERP (large migration project). Finstack from EUR 39/month.
Consolidation solutions per ERP: Excel, consolidation tool or heavier ERP?
Per ERP, there are three paths to consolidated figures: in Excel, in a specialised consolidation tool, or via a heavier ERP with built-in consolidation. The choice that determines whether consolidation costs days or minutes.
TL;DR
SME CFOs have three paths to consolidated figures: manually in Excel, in a specialised consolidation tool, or by migrating to a heavier ERP with built-in consolidation. For most SME groups a consolidation tool is the smartest choice: direct API integrations where available (Finstack covers a.o. Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC), and no heavy migration trajectory needed. From EUR 39/month, live within 5 minutes.
Consolidation in Excel or in a tool: the difference between days and minutes
For SME groups of two entities or more, three paths lead to consolidated figures. First path: in Excel, manually per close. Second path: in a specialised consolidation tool with direct ERP integrations and a CSV fallback for other ERPs. Third path: migrating to a heavier ERP (Oracle, SAP, MS Dynamics 365 F&O) with built-in consolidation — common at enterprises, rarely the right choice for SMEs.
The Excel path for a group with three BVs: pull a trial balance from each entity ERP (3 x 30 min = 1.5 hours), map charts of accounts to the group chart (2 hours), identify and net out intercompany (3 hours), reconcile balances (1 hour). Total: almost a full working day. With five or more entities this rises to 2-3 days — 12 times a year is a full month lost to manual work that adds zero information.
A hidden cost of Excel: because the cycle takes days and is error-prone, consolidation happens at most monthly. Intermediate figures are missing — outliers like an entity slipping in revenue or a cost category drifting from budget are only visible after month-end close, instead of a week earlier.
The tool path: a package with direct ERP integrations synchronises trial balance and general ledger entries automatically (daily at Finstack, plus manual refresh on demand by the user). Chart-of-accounts mapping is configured once and runs continuously.
Intercompany detection runs automatically through tagging on accounts or cost-centers. Elimination happens within the consolidation engine. For entities on an ERP without a direct integration: CSV upload as fallback, no roadblock. The cycle itself takes minutes, not days.
Finstack is a concrete implementation of the second path, focused on SME groups with 1-50 entities: direct API connections for, among others, Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC, CSV fallback for other ERPs, and a 10-minute close cycle for a three-entity group.
The choice between Excel, a consolidation tool or a heavier ERP isn't about technology but about time investment and cost. For SMEs the tool path usually comes out best; for groups that genuinely need a heavier ERP operationally that's the right route — though it doesn't automatically solve the consolidation question.
How a consolidation tool pulls in your ERP data: direct integration with CSV fallback
Inside a consolidation tool, your ERP data comes in two ways: via a direct API integration (the default where available) or via CSV/Excel upload as fallback for ERPs without a direct integration. Both work within the same tool — you don't have to choose upfront which path you'll follow per entity. Compared to Excel-based consolidation:
The key insight from this comparison: even the CSV fallback within a tool beats Excel consolidation by a factor of 10. An SME group with one entity on Sage and three on Exact doesn't have to choose between “migrate to one ERP” or “keep struggling in Excel”. In Finstack the three Exact entities are connected directly (daily sync, transaction level, manually refreshable) and the Sage entity gets a monthly CSV upload routine of 5 minutes. The combined result is consolidated, eliminated and reported within the same 10-minute close cycle.
Why is transaction level (in the direct integration) critical for multi-entity? Because intercompany elimination can only be clean with visibility on the transaction line: which specific sale in Pro BV corresponds with which specific purchase in Dis BV? Trial-balance level hides that distinction — tools then show the IC account at €300k but not the individual invoices underneath. With elimination mismatches you can't drill down to the source. See also transaction-level vs. trial-balance consolidation for the deeper mechanics.
Finstack delivers both options in one tool: a broad portfolio with direct API integrations at transaction level (for, among others, Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC, and more), supplemented with standardised CSV or Excel upload for ERPs outside the portfolio. For SME groups still consolidating in Excel, this means a direct gain in time and quality per close cycle.
The 5 things to check in a consolidation tool
Before you pick a consolidation tool based on “does it support my ERP”, check these five dimensions. They determine whether the tool actually works in practice — both via direct integrations and via the CSV fallback for outlier entities — or whether you still end up with manual work.
Detail level: transactions or balances
Transaction level is non-negotiable for multi-entity. Only there can you drill down from IC mismatches to the source. Trial-balance integrations are good enough for single-entity reporting, but lead to elimination errors as soon as you have three entities.
Intercompany detection method
How does the tool know what an IC transaction is? Three options: account flag (certain GL numbers are always IC), cost-center tagging (booked per project), or journal type. The best tools support all three side by side, because every entity books differently.
Elimination methods
A serious consolidation tool supports multiple elimination methods side by side: full GL account, per IC relation, per transaction, and manual IC journal. Tools with one fixed method force your entities into a uniform booking pattern — which rarely works in practice. Finstack supports all four.
Currency conversion
Which FX rate is used and when? Monthly closing rate or daily? From which source (ECB, Bloomberg, custom)? For multicurrency groups this is critical — wrong rate timing creates unnecessary translation differences in your EBITDA bridge.
Sync frequency
How often does the integration refresh? Good: daily automatic with the option to manually refresh at any time (Finstack standard). Acceptable: daily only. Too slow: weekly or only on-demand. With weekly sync you can never truly consolidate weekly — you're always working with figures that are at least a week old.
These five checks together predict whether your consolidation cycle will really take 10 minutes or whether you'll still have 1-2 days of manual work. Ask every consolidation-tool vendor concretely for these five answers — vague marketing claims like “seamless integration” mean nothing if the tool only pulls trial balances or knows just one elimination method. Finstack scores on all five: transaction level, three IC detection methods side by side, four elimination methods, ECB-based FX rates, and daily sync with manual refresh option.
Seven highlighted ERPs in the Finstack integration portfolio — plus CSV fallback
Finstack has a broad integration portfolio with direct API connections. In this article we feature seven of the most-used ERPs in the Dutch and international SME market — and the portfolio expands continuously based on customer demand. Each featured integration works at transaction level, refreshes daily automatically (and manually on demand) and supports multi-entity by default. These are the seven highlighted ERPs.
For each featured ERP a dedicated deep-dive article will come online in 2026 with specific setup steps, pitfalls and practical examples. For now: all integrations run on the same Finstack engine with identical quality of elimination, reconciliation and reporting. Beyond these seven, Finstack has more ERP integrations in the portfolio, and it keeps expanding based on customer demand.
IC detection differs per ERP. Exact and AFAS have strong GL-account conventions where IC transactions land on specific numbers — Finstack picks that up automatically. Twinfield and Odoo work with cost-centers or dimensions; Finstack supports that mapping. Xero and QuickBooks are more flexible, requiring more initial IC-detection configuration. MS Dynamics 365 BC has native multi-currency and multi-entity support, making the Finstack integration valuable for international PE portfolios.
For ERPs outside the Finstack integration portfolio (think of Pinkweb or KING) the CSV or Excel fallback serves as a direct route. Export trial balance or general ledger entries from the source ERP, upload to Finstack, normalisation to the group chart runs automatically. That way no SME group is left out — not even a holding where one outlier entity sits on a non-directly-connected system.
Multi-ERP groups — when entities run different systems
Many SME groups arise through acquisitions. The NL holding sits on Exact, the German subsidiary runs on MS Dynamics 365 BC, the Belgian entity uses AFAS, and the interim-management BV is on Xero. For manual consolidation this is a nightmare. For Finstack it's a standard configuration.
Finstack connects each entity on its own ERP via direct API. The charts of accounts — different per country, per ERP, per historical choice — map automatically to your defined group chart. Intercompany detection works cross-system: netting out a sales invoice from Exact against a purchase invoice in MS Dynamics 365 BC happens in one elimination step.
Practical example: a holding with three entities on Exact, AFAS and Twinfield respectively can be set up in Finstack within one day. From day two a 10-minute close cycle runs that delivers consolidated figures, IC elimination and parallel reports — without any entity having to switch ERPs.
Compare that to the alternative: migrate all entities to one ERP. That trajectory typically costs 6-12 months and EUR 50,000 to 200,000 in implementation, consultancy and internal time. Plus the risk that an entity with a working system is forced onto a tool that doesn't functionally fit. Multi-ERP groups that set up Finstack save that trajectory almost entirely.
For groups that do want to migrate later this is also a workable intermediate path: first automate consolidation with the current ERP mix, then carry out migration per entity when it fits. The consolidation output stays consistent — Finstack normalises the figures regardless of which ERP sits at the source. That makes ERP migration safer: you already have a stable consolidated view that serves as baseline before and after migration.
Switch to a heavy ERP with built-in consolidation, or keep your current ERP with a consolidation tool?
A question virtually every growing SME CFO faces at some point: should I switch to a heavy ERP like Oracle, SAP or MS Dynamics 365 F&O that has consolidation built in? Or do I stay on my current SME ERP and connect a consolidation tool to it? For most SME groups the second is the smarter route. Three reasons.
1. ERP migration is a substantial project. Migrating from an SME ERP to a heavy ERP typically takes 6-12 months and costs EUR 50,000 to 200,000 in implementation, consultancy and internal time — plus disruption to daily operations. For solving only a consolidation problem that's a disproportionately large investment. A consolidation tool like Finstack connects in 5 minutes, regardless of which SME ERP you run.
2. Heavy ERPs are heavy in daily use. Oracle, SAP and MS Dynamics 365 F&O are built for enterprises with complex processes — goods flows across multiple warehouses, production planning, work-in-progress positions, supply chain. Anyone who doesn't really need those functions wastes daily time on extra screens, authorisation steps and more complex bookings that an SME ERP keeps simple. For a five-entity services business that only needs administration and consolidation, a heavy ERP is overkill — and the operating overhead piles up daily.
3. Cost. Heavy ERPs typically cost EUR 100-500 per user per month, plus implementation and maintenance. An SME ERP (Exact, AFAS, Twinfield) combined with a consolidation tool like Finstack (from EUR 39/month for the first entity) is a fraction of that, with the same consolidated reporting as output.
When to migrate to a heavy ERP: when you really need specific operational functionality that an SME ERP can't handle. Think of complex goods-flow control with multi-warehouse and serial tracking, or work-in-progress positions with percentage-of-completion accounting for project-based businesses. In those cases you choose a heavy ERP for the operational functionality — not for the consolidation. Consolidation remains a separate question, solved separately.
For the rest of SME groups: keep your current SME ERP, connect a consolidation tool like Finstack, and from EUR 39/month consolidate within 5 minutes. That saves the migration, keeps daily operations simple, and delivers the same consolidated figures as a heavy ERP — at a fraction of the cost.
What a good consolidation tool must be able to do
Whichever tool you consider, these five functional requirements determine whether it works in practice for your group.
1. A broad integration portfolio with direct API connections plus a CSV fallback for ERPs outside it. Not every SME group runs on one of the biggest ERPs. A good consolidation tool combines: direct integrations with the most-used packages (Finstack connects directly with, among others, Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC — and keeps expanding the portfolio) plus a standardised CSV or Excel import for all other ERPs. That way no entity is left out.
2. Transaction level instead of trial balance only. Without transaction level no clean IC elimination, no drill-down to source, no serious audit trail. This is the most important distinction between serious consolidation tools and glorified Excel templates.
3. Elimination rules you configure once and that run automatically. Supporting four elimination methods (full GL account, per IC relation, per transaction, manual IC journal) covers every type of IC structure. See also the article on elimination methods for SME CFOs.
4. Direct Excel and Google Sheets integration. CFOs and controllers keep working in their familiar models via 2-way sync. Consolidation itself runs cleanly in the tool; analysis and presentation stay in Excel where they belong.
5. Adjustment entries (such as normalisations in private equity). For consolidation corrections that don't belong in the regular bookkeeping — goodwill amortisation, PPA adjustments after acquisition, normalisations for PE reporting — you need a dedicated booking layer for adjustment entries. A tool without such a layer forces you to push corrections into an entity ERP, which pollutes the audit trail and contaminates the entity balance sheet. Finstack supports adjustment entries natively.
Finstack delivers all five as standard for SME groups with 1-50 entities, across the integration portfolio and via CSV fallback, from EUR 39/month. Live within 5 minutes. The pillar page consolidation for SME CFOs covers the broader context; this ERP pillar addresses the integration layer.
Before switching ERP, first solve your consolidation problem with a consolidation tool — only migrate if your ERP genuinely falls short. This saves 6-12 months of migration and EUR 20,000-100,000 in implementation costs.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
3 common mistakes in consolidation for SMEs
Three patterns we see repeatedly in SME groups that struggle with consolidation. Each costs measurable time or money; each is easy to avoid once you know what to watch for.
Staying in Excel past 3 entities
The most common mistake: keeping Excel consolidation once you pass three entities. Time investment rises to 2-3 working days per close, errors slip unnoticed into trial balances, and audit trail is impossible to guarantee. The threshold to switch to a tool is low — from EUR 39/month — yet many SME CFOs delay until an error costs more than a full year of the tool.
Migrating to a heavy ERP “for the consolidation feature”
Switching to NetSuite, SAP or MS Dynamics 365 F&O for “built-in consolidation” when you don't need their operational functionality is a EUR 50,000-200,000 investment for a question that a EUR 39/month consolidation tool solves. Migrate only when you genuinely need the operational features — not for the consolidation.
Choosing a tool that does not offer transaction-level data
A tool that only pulls trial-balance level — without drill-down to the source transaction — delivers days of extra manual work as soon as IC mismatches need investigating, and makes a clean audit trail impossible. For multi-entity, transaction level isn't an option but a precondition. Ask this as the first check from the 5-point list — Finstack connects at transaction level by default.
Frequently asked questions
Can't find your question? Let us know
Which ERPs does Finstack connect directly?
Finstack focuses on SME groups with 1-50 entities and has an integration portfolio with direct API connections for among others Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC, expanding continuously. All direct integrations work at transaction level, refresh daily with manual refresh option. For ERPs outside the portfolio: standardised CSV or Excel import.
How often do ERP integrations refresh?
Finstack refreshes direct ERP integrations daily automatically, and the user can manually refresh at any time via a refresh button. At every close cycle the most recent trial balances and general-ledger entries are ready. Sync frequency has no impact on the performance of your ERP — all queries run via read-only API calls.
What is the difference between consolidating in Excel and in a tool?
Excel: for every close cycle manually export trial balances, map, net out intercompany, merge — 3-5 working days per month for three entities, error-prone, no audit trail. A consolidation tool automates this: direct ERP integrations where available, CSV fallback for other ERPs. Result: 10 minutes per close, complete audit trail. Finstack from EUR 39/month.
Can I consolidate if my entities run different ERPs?
Yes. Finstack connects each entity on its own ERP. An NL holding on Exact, a German subsidiary on MS Dynamics 365 BC and a Belgian entity on AFAS run in one consolidated report. Charts of accounts map automatically, intercompany detection works cross-system — saving multi-ERP groups often 100k+ in migration costs.
What if my ERP isn't supported by Finstack?
For non-supported ERPs (think Pinkweb or KING) a CSV or Excel import works as direct solution. Finstack accepts trial balances in standard format, normalises to your group chart and runs the same eliminations as with direct integrations. Time difference: manual sync per close cycle (5-15 minutes) versus daily automatic.
Should I switch to a heavy ERP with built-in consolidation, or keep my current ERP with a consolidation tool?
For most SME groups, keeping the current ERP plus connecting a consolidation tool is the smarter choice. Three reasons: ERP migration is a 6-12 month project of EUR 50-200k; heavy ERPs are heavy in daily use; costs are substantially higher. Switching to a heavy ERP is only worthwhile for specific operational functionality — not for the consolidation.
How secure is the ERP integration?
All ERP integrations use OAuth 2.0 or API keys with read-only scope: Finstack can only pull data, never make or modify entries in your ERP. Data is encrypted in transit (TLS) and at rest (AES-256). Finstack is ISO 27001 certified and hosted in the EU. Per-user access via SSO and MFA. Complete audit log of who viewed what and when.
CFO turned Founder - Finstack
Sources and provenance
- Finstack — Integrations with Exact, AFAS, Twinfield, Odoo, Xero, QuickBooks and MS Dynamics 365 BC: finstack.io/solutions/integrations
- Finstack Help Center — Sources & connections (sync frequency, security): help.finstack.io
- Finstack — Pricing (from EUR 39/month): finstack.io/pricing
Last reviewed: 28 June 2026 · Next review: September 2026
Consolidated reporting and forecasting.
