Multi-entity consolidation in under a day.
Multi-entity consolidation is one of those topics that sounds technical and inside-baseball until you actually live it. Then it becomes the difference between a finance team that can run a multi-country business and a finance team that spends every close fighting their own books.
This post is about how Peaky handles consolidation, why it takes a day instead of months, and what changes for a finance team that lives in a multi-entity world.
What consolidation actually is
Most companies start as a single legal entity. One country. One bank account. One chart of accounts. Finance is hard, but it is hard in one shape.
Companies that grow internationally, or that acquire, or that spin off subsidiaries, end up with multiple legal entities. Each one has its own accounting platform, or its own instance, or its own chart of accounts. Each one closes on its own schedule. Each one reports in its own currency.
Consolidation is the work of stitching these entities back together into a single financial picture. You take the per-entity numbers. You convert currencies. You eliminate intercompany transactions. You apply ownership percentages. You produce a consolidated P&L, balance sheet, and cash flow that represents the whole company as one thing.
This is necessary, foundational work. It is also the work most consolidation tools take three to six months to set up.
Why traditional consolidation is painful
The traditional consolidation flow has three pain points.
Setup time. Most consolidation tools require an implementation project. Map the chart of accounts per entity. Define the currency translation rules. Configure the intercompany elimination logic. Validate against historical periods. Train the team. Three months is fast. Six is common.
Cadence. Once set up, consolidation runs on a schedule. Usually monthly, sometimes quarterly. Each cycle requires the per-entity books to close first, then the consolidation runs, then the consolidated statements are produced. The team waits for each step.
Brittleness. Adding a new entity, moving a chart of accounts, or restructuring ownership tends to break the consolidation model. Each structural change becomes a small project. The team learns to avoid structural changes whenever possible, which means the structure stops reflecting how the business actually runs.
For a scaling company that may add a new entity every other quarter, this brittleness is especially costly.
How Peaky does it
Peaky’s multi-entity consolidation has three properties that are different from the traditional flow.
Setup is hours, not months. The ledger-mapping agent handles the per-entity chart of accounts. The forecasting agent builds the consolidation logic. The team confirms the structure, sets the currency translation rules, and the consolidation runs.
Cadence is continuous. The consolidated view updates whenever any of the underlying entities update. You do not run a consolidation. You open the consolidated view and it is current.
Structural changes are absorbed. A new entity gets added by connecting its accounting platform. Peaky proposes the mapping. The model absorbs it. The consolidated view expands without requiring a project.
Total time to a working multi-entity consolidation: usually under a day, depending on how many entities and how clean the per-entity books are.
What this unlocks
A finance team that lives in a multi-entity world experiences a few specific changes when consolidation becomes continuous.
The board view becomes current. Most multi-entity boards see consolidated numbers that lag the per-entity closes by weeks. With continuous consolidation, the board view is as fresh as the underlying entities. The lag disappears.
Currency exposure becomes visible. Currency translation differences show up in real time, not at quarter-end. Hedging conversations can happen before exposures compound rather than after.
Intercompany work shrinks. The elimination logic runs continuously. The team is not reconciling intercompany balances at the end of every cycle. They are watching for anomalies as they happen.
The consolidated forecast becomes possible. Building a consolidated forecast in a traditional flow is a major exercise because the per-entity forecasts have to align before they can be rolled up. With continuous consolidation, the rollup is automatic and the forecast can be maintained at the consolidated level natively.
For a company at Series B or C scale with multiple legal entities, these changes compound into a meaningful operational advantage.
Who this is for
Peaky’s multi-entity consolidation is built for companies between two and twenty legal entities. That covers most Series A to C scaling companies with operational complexity.
If you have a single entity, this is not relevant yet. Wait until you add a second.
If you have fifty entities and operate across thirty currencies with deeply complex intercompany arrangements, you likely need a heavier enterprise consolidation system. Peaky is not trying to replace that.
The middle is where the cost of slow consolidation hits hardest, because the entities are too many to manage manually but too few to justify the cost of a dedicated enterprise consolidation deployment.
Where this fits in the product
Multi-entity consolidation is part of the Pro tier of Peaky. It is shipped, working, and being used by customers today.
The Strategic tier extends consolidation further: more entities, external signal integration, deeper sensitivity analysis. Most customers reach Pro by Series B and Strategic by Series C, in line with how their operational complexity expands.
What to do next
If you are running multi-entity finance today and the consolidation work is taking longer than it should, you can connect Peaky to your entities and see a working consolidated view by the end of the day.
You can start a trial at peaky.ai. Bring as many entities as you want. Peaky’s agents will handle the rest.
The financial infrastructure for scaling without surprises.


