Use case · Group planning
Planning across dozens of entities, without the inbox as your filing system.
Pre-fill, send out, chase, collect, correct: this loop costs your team days every round. CORE takes it over – entity by entity. Anyone not yet moved across keeps sending their Excel package as before.
No sign-up · read-only · sample group with five entities
The loop
Six steps that repeat every single round.
Not one of them produces an insight. Together they absorb most of the time your department spends on planning.
Pre-filling
Master data and actuals are copied into each entity's package by hand. Every round from scratch, and again after every correction.
Sending out
The packages go out by email. From that moment there are as many versions of the truth as there are inboxes.
Collecting
Returns trickle in over days, at different revisions, some of them twice. Which one counts gets settled on the phone.
Correction loops
Every query restarts the cycle for that entity – file out, file in, compare revisions.
Bringing it together
The group picture is assembled by hand from the approved versions. A transposed figure here surfaces much, much later.
Reconciling IC
Who owes what to whom is settled between two controllers on a call. The outcome lives in no file anyone can look up afterwards.
The effort
Work it out once, with your own numbers.
The size of the problem comes down to three figures you already know. We are not supplying any of them.
Budget, forecast I, forecast II …
Everyone who receives a package.
Pre-filling, chasing, checking, consolidating.
The move
Entity by entity. Never all at once.
At no point do you lose the ability to run a round. Whoever has moved across plans in CORE. Whoever has not sends their package as before – CORE reads it in and counts it.
Pilot with the awkward ones
Not the easiest entity first, but the ones carrying the special cases: a different financial year, their own chart of accounts, dense IC relationships. Whatever holds there holds everywhere afterwards.
Run both in parallel
Pilot entities plan in CORE, everyone else keeps sending their package. Both routes feed the same group accounts. The round runs through as if nothing had changed.
Follow at your own pace
Each further entity moves when it suits their calendar – between two rounds, never in the middle of one. There is no cut-over date on which everything has to work at once.
A round today
- Pre-fill packages and send them out
- Collect returns, compare revisions
- Correction loops per entity
- Reconcile IC on the phone
- Assemble the group picture by hand
A round running in parallel
- Open the round – it arrives pre-filled
- Those moved across plan directly, the rest send packages
- One valid version per entity, visible to everyone
- Differences sit in the round, not in a phone call
- The group picture stands as soon as the last version lands
IC reconciliation
The difference sits in the round, not in a phone call.
As long as two entities plan different figures, the relationship stays visibly open – with the amount, the counterparty and the timestamp. Nobody has to ring around to find out who booked what.
- Every IC relationship with both sides side by side
- A difference shown as an amount, not a question mark
- Visible since when it has been open
- Eliminated account by account once agreed, balance 0.00
| Relationship | Account | Amount | Status |
|---|---|---|---|
| Sales South → Group AG IC receivable |
20201 | +2,380,000 | ✔ agreed |
| Services Ltd → Group AG Counterparty plans 1,900,000 |
20201 | +2,140,000 | ▲ 240,000 open |
| Production East → Sales South IC revenue |
80001 | +840,000 | ✔ agreed |
| Not yet agreed | 240,000 | 1 relationship | |
For IT
Two questions your IT asks first.
More on data ownership, AI and connectivity on the home page under “For IT”.
“Do we have to unify our charts of accounts?”
No. A mapping per entity sits between your source system and the calculation model. Every entity keeps its own chart of accounts, and the model still adds up as one group.
- Account mapping per entity
- Existing charts of accounts stay as they are
- Non-ERP entities via a dedicated screen
“Can every entity see the others' figures?”
Only where they should. A role and permission model decides who sees what – by entity, by area, by role. The group view stays with the people who need it.
- Role-based access RBAC
- Views by entity and by role
- An immutable record of every change
Next step
Look at a round that is already running.
The sample group is ready, with no sign-up and nothing to install. Or let us show you in 30 minutes what the round looks like on your own structure.
or simply by email: kontakt@justexperts.de