Distribution of schedule details

By default, the option to distribute schedule details is disabled in the configuration of Core Consolidation in Business Modeling. When enabled, the Data Entry Schedule Detail Distribution option is displayed in the navigation panel and on the Trial Balance card. Check rules and, for each main schedule, the default detail element for detail distribution are created. The Manual Detail Distribution adjustment level is also created.

Schedule detail distribution is useful if you do not use schedules during the year and distribute the differences at the end of the year. Or, if you do not have schedule detail information from the source system and distribute the details later in the year.

With this option enabled, you always import the closing balances of group accounts that have schedule details without those details, with partly delivered details, or with a full set of details without the opening balance. You can distribute the remaining schedule details at a later point in time. Or, you can distribute the schedules before you import the finance data. In this case, do not change the already distributed schedules.

Import cube routing

When the option to distribute schedule details is enabled in Business Modeling, the import target cube depends on the presence of schedule details.

The row with an empty ScheduleDetail value (the closing balance is required) is imported into the main cubes (TFINANC, TSEGMC).

Detail rows with a ScheduleDetail value (the movement detail is optional) are imported into the detail cubes (TDETAIC, TSEGMOVC).

Import routing is determined automatically by the presence or absence of the ScheduleDetail field value.

Importing closing balances for accounts with schedule details

The closing balance element (<ScheduleID>_CB) is a system-calculated total element in the DDETAIL dimension and does not support direct data import.

To import a closing balance for a group account that uses a schedule, leave the ScheduleDetail field empty in the import file. An empty ScheduleDetail value is interpreted as the closing balance, and the corresponding _CB total element is populated automatically.

Note: 

Do not specify the _CB element, such as E_CB, in the ScheduleDetail column because it results in this validation error:

Mismatch with schedule detail configuration. The Group Account <L110100 - Share Capital> uses the schedule <E - Equity> but it does not contain the source schedule detail < E_CB>.

When only some schedule details are available, import detail rows and the closing balance row in the same file. Specify the name of the schedule detail element for detail rows, and leave ScheduleDetail empty for the closing balance row.

Examples

Scenarios 1-4 are about the RU0001 (Genesis Cars) entity that imports data for the L110100 (Share Capital) account, which uses the Equity (E) schedule. The import includes three movement detail rows and the closing balance row.

This table shows schedule details of the Equity schedule that are used in scenarios 1-4:

Schedule detail Description
72 Increases
79 Dividends Paid
81 Net Profit (Loss) for the Period
E_NA Equity - Difference to Distribute (system-calculated, cannot be imported directly)
E_CB Equity - Closing Balance (system-calculated total, cannot be imported directly)
Note: E_NA and E_CB are system-calculated total elements that cannot be the import targets in the ScheduleDetail column. The closing balance is imported by leaving ScheduleDetail empty. The E_NA element is derived automatically.

This table shows adjustment levels that are used in scenarios 1-4:

ID Name Type Allows rollover?
HB I Imported Data Import
Reclassification Reclassifications Journal ✔
Correction Corrections Journal ✔
Test Test Import
Note: Only import-type levels accept data rows from import files. Journal-type levels, such as Reclassification or Correction, can't be used as import targets when import level is set to False. Rows that specify journal levels generate a warning and are skipped. The closing balance row with an empty ScheduleDetail value is restricted only to the default HB I import level.

Scenario 1 (correct): Closing balance is imported with an empty ScheduleDetail value

Period Year Entity Intercompany Account ScheduleDetail Currency Level Value
12 2026 RU0001 External L110100 72 EUR 150,000.00
12 2026 RU0001 External L110100 79 EUR -50,000.00
12 2026 RU0001 External L110100 81 EUR 150,000.00
12 2026 RU0001 External L110100 EUR 1,173,356.95

In this scenario, schedule detail 72 records increases, for example, a capital raise, schedule detail 79 records dividends paid, and schedule detail 81 records the net profit or loss for the period. The closing balance of 1,173,356.95 EUR is imported by leaving the ScheduleDetail column empty.

The undistributed amount (E_NA) is calculated as the difference between the closing balance and the sum of all imported detail elements: 1,173,356.95 − 250,000.00 = 923,356.95. This remaining difference can be distributed later in the Data Entry Schedule Detail Distribution report.

Scenario 2 (incorrect): E_CB is specified directly in the ScheduleDetail column

Period Year Entity Intercompany Account ScheduleDetail Currency Level Value
12 2026 RU0001 External L110100 72 EUR 150,000.00
12 2026 RU0001 External L110100 79 EUR -50,000.00
12 2026 RU0001 External L110100 81 EUR 150,000.00
12 2026 RU0001 External L110100 E_CB EUR 1,173,356.95

This results in these errors:

  • Mismatch with schedule detail configuration. The Group Account <L110100 - Share Capital> uses the schedule <E - Equity> but it does not contain the source schedule detail <E_CB>. (1 occurrences)
  • Import of data mapped to group account <L110100 - Share Capital> for version <V01 - Actual>, entity <RU0001 - Genesis Cars>, <December 2026>, level <HB I - Imported Data> requires a closing balance value. (1 occurrences)

E_CB is a system-calculated total element and can't be used as an import target. Because the row with the E_CB value is rejected, no valid closing balance row exists in the import, which results in the error about data import.

Scenario 3 (incorrect): No closing balance row is included

Period Year Entity Intercompany Account ScheduleDetail Currency Level Value
12 2026 RU0001 External L110100 72 EUR 150,000.00
12 2026 RU0001 External L110100 79 EUR -50,000.00
12 2026 RU0001 External L110100 81 EUR 150,000.00

This results in this error:

Import of data mapped to group account <L110100 - Share Capital> for version <V01 - Actual>, entity <RU0001 - Genesis Cars>, <December 2026>, level <HB I - Imported Data> requires a closing balance value. (1 occurrences)

When the option to distribute schedule details is enabled in Business Modeling, a closing balance row is required for every group account with a schedule. Importing movement details without a closing balance row is not supported.

Scenario 4 (incorrect): Empty ScheduleDetail value is imported at the custom level

Note: This scenario applies only when the option to distribute schedule details is enabled in Business Modeling.

Import of an empty ScheduleDetail value (total balance) is valid only at the HB I (Imported Data) level. This behavior differs from earlier releases in which an empty ScheduleDetail value at the HB I level caused a validation error. Now, an empty ScheduleDetail value at the HB I level is required for closing balance imports.

Note: Import with an empty ScheduleDetail value at any other level than HB I fails.

This table shows an example of what happens when rows are imported at the custom or invalid levels:

Period Year Entity Intercompany Account ScheduleDetail Currency Level Value
12 2026 RU0001 External L110100 72 EUR Reclassification 150,000.00
12 2026 RU0001 External L110100 79 EUR Test -50,000.00
12 2026 RU0001 External L110100 81 EUR Correction 150,000.00
12 2026 RU0001 External L110100 Empty EUR Test 1,173,356.95

These results are displayed:

Row Level type Result
72 (Reclassification level) Journal Warning: Invalid value <Reclassification - Reclassifications> in column <Level>. Level import is set to false. Records will be skipped. (1 occurrences)

Journal levels such as Reclassification generate warnings and the rows are skipped. The rows aren't valid import targets because they are at the journal-type levels and import level is set to False.
79 (Test level) Import Correct.

The import-type custom level (Test) accepts detail rows with an explicit ScheduleDetail value, for example, 79.
81 (Correction level) Journal Warning: Invalid value <Correction - Corrections> in column <Level>. Level import is set to false. Records will be skipped. (1 occurrences)

Journal levels such as Correction generate warnings and the rows are skipped. The rows aren't valid import targets because they are at the journal-type levels and import level is set to False.
Empty (Test level) Import Error: Import of data mapped to group account <L110100 - Share Capital> and custom import level <Test - Test> requires an explicit detail to be specified. Schedule detail distribution is only valid for the default import level. (1 occurrences)

The import-type custom level (Test) rejects empty ScheduleDetail rows. An empty ScheduleDetail value (closing balance) is only valid at the default HB I level. If you specify any other import-type level for the ScheduleDetail row, an error occurs.

The empty ScheduleDetail (closing balance) row is only valid at the HB I (Imported Data) level. Any other levels are rejected.

Distribution of schedule details enabled vs. disabled - summary

When the option to distribute schedule details is enabled, these changes apply to the data import and processing:

  • Closing balances are required in every import. You can't import schedule details without the corresponding closing balance for the same context. Otherwise, an error occurs.
  • At the imported data level, undistributed amounts are calculated as the difference between the closing balance and the total of all detail amounts, including opening balances.
  • The schedule alignment process isn't performed at the imported data level after import because the imported closing balance is treated as an authoritative value. This prevents schedule alignment from overwriting imported values.

These changes ensure that the imported closing balance is always the leading value and that schedule detail distribution is applied consistently to imported data.

If the option to distribute schedule details is disabled in Business Modeling, the Data Entry Schedule Detail Distribution option is not available in Financial Consolidation. Only members of the Consolidation Modeler and Business Modeling Administrator roles can disable the option to distribute schedule details.

Note: Specifying schedule detail amounts for rule-calculated accounts and *_FX_Subgroup schedule details is disabled to maintain data integrity and prevent data inconsistencies, especially during OLAP synchronization. To identify *_FX_Subgroup schedule details, use the Group to Entity Detail (Business Modeling property) or G2C_* (DDETAIL OLAP property). Schedule details that are selected as Group to Entity Detail or G2C_* have Write access disabled. These rule-calculated accounts are available:
  • L110520: Profit (Loss) for the Period or Balance Sheet Profit/Loss
  • L110310: FXDiff Balance
  • L110320: FXDiff GuV
  • L110511: Carry Forward Entity, Carry Forward Group, Retained Earnings - Profit, or Retained Earnings - Loss