Hi Jarkko Salo,

Yes, this can be achieved within a single Planning Sheet using the Row Model. Your Account × Time layout can remain unchanged, with the row types determining whether a value is entered manually or calculated.

Start with the following Planning Sheet layout:

• Rows: Cost Centre, Account
• Columns: Date Hierarchy
• Values: Amount

Then, in the Model tab, enable the Row Model for the sheet and configure it as follows:

1. Cost Centre

In the Row Model hierarchy, Cost Centre sits above Account, since we assigned them in that order (Cost Centre → Account).

You can still use a Cost Centre filter or filter context in the Planning Sheet, allowing users to focus on a single Cost Centre at a time (for example, CC200) while viewing and planning values specific to that Cost Centre.

2. Accounts on Rows

No change is needed here. Accounts remain on rows under each Cost Centre.

3. Time and Scenario

Time stays on columns.

If Scenario (Actual, Budget, Forecast) is required as a regular dimension for context, I would recommend placing it on rows rather than columns. This keeps the allocation flow cleaner, as the allocation formula can be evaluated independently for each scenario.

If Scenario is time-dependent and each scenario has its own forecast horizon, it's generally better to model it as a Forecast Measure rather than a Scenario dimension. In that setup, the opening period can be defined either as a data input or through a formula, depending on your planning process.

4. Allocation

Since all Cost Centres (CC) share the same Account structure, the Row Model can be used to template the allocation logic:

For example,

• CC100 -> Account 6100 could be configured as a Data Input row, so users can enter a value directly, say 100,000.
• CC200 -> Account 6100 could be configured as a Formula row using a calculation such as (CC100 -> Acccount 6100) × 60%, This would return 60,000 for CC200 -> Account 6100.

The allocated accounts remain read-only because they're formula-driven, while Data Input rows stay editable. Any updates to the value entered in CC100 or to the allocation percentages will automatically flow through to CC200.

5. Storage

Write-back will retain both the latest and previous values. If you also need to compare against the original plan, you can maintain the original figures in a separate baseline scenario alongside the working scenario.

Hope this helps! This approach works well when the account structure is consistent across Cost Centres, as it keeps the setup centralized while still allowing users to plan and maintain allocations efficiently.