Documente Academic
Documente Profesional
Documente Cultură
CONSOLIDATION 10.0,
VERSION FOR SAP NETWEAVER, POWERED BY HANA
Copyright
Legal
Disclaimer
No part of this starter kit may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
The information in this starter kit is proprietary to SAP. No part of this starter kits content
may be reproduced, copied, or transmitted in any form or for any purpose without the
express prior permission of SAP AG. This starter kit is not subject to your license agreement
or any other agreement with SAP. This starter kit contains only intended content, and precustomized elements of the SAP product and is not intended to be binding upon SAP to
any particular course of business, product strategy, and/or development. Please note that
this starter kit is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this starter kit. SAP does not
warrant the accuracy or completeness of the information, text, pre-configured elements, or
other items contained within this starter kit.
SAP DOES NOT PROVIDE LEGAL, FINANCIAL OR ACCOUNTING ADVISE OR
SERVICES. SAP WILL NOT BE RESPONSIBLE FOR ANY NONCOMPLIANCE OR
ADVERSE RESULTS AS A RESULT OF YOUR USE OR RELIANCE ON THE STARTER
KIT.
THIS STARTER KIT IS PROVIDED WITHOUT A WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
SAP SHALL HAVE NO LIABILITY FOR DAMAGES OF ANY KIND INCLUDING WITHOUT
LIMITATION DIRECT, SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES THAT
MAY RESULT FROM THE USE OF THIS STARTER KIT. THIS LIMITATION SHALL NOT
APPLY IN CASES OF INTENT OR GROSS NEGLIGENCE.
The statutory liability for personal injury and defective products (under German law) is not
affected. SAP has no control over the use of pre-customized elements contained in this
starter kit and does not endorse your use of the starter kit nor provide any warranty
whatsoever relating to third-party use of the starter kit.
TABLE OF CONTENTS
A.
1.
1.1.
1.2.
1.3.
2.
2.1.
2.2.
2.3.
2.4.
3.
3.1.
3.2.
4.
4.1.
4.2.
4.3.
4.4.
4.5.
4.6.
4.7.
4.8.
4.9.
4.10.
4.11.
4.12.
5.
5.1.
5.2.
5.3.
6.
B.
1.
2.
2.1.
2.2.
2.3.
2.4.
3.
3.1.
3.2.
4.
4.1.
4.2.
5.
5.1.
5.2.
5.3.
6.
7.
C.
1.
1.1.
1.2.
2.
2.1.
2.2.
2.3.
2.4.
3.
3.1.
3.2.
4.
4.1.
4.2.
5.
5.1.
5.2.
5.3.
6.
7.
8.
D.
1.
1.1.
1.2.
2.
2.1.
2.2.
2.3.
2.4.
3.
3.1.
3.2.
4.
4.1.
4.2.
5.
5.1.
5.2.
5.3.
6.
7.
A.
ACTUAL CATEGORY
1.
1.1.
Data input forms are organized into workbooks, which are again organized into folders, according to their
content. For example, the input form Financial Receivables belongs to the workbook Financial Assets which
is placed in the subfolder Flow Analysis.
The input forms are organized into one folder, ACTUAL, and three subfolders according to the recommended
order of data entry:
Subfolder
Description
Balances
Input forms for entering main balances for profit and loss, assets and
equity and liabilities.
Flow Analysis
Input forms for analyzing the variations between opening and closing for
balance sheet accounts.
Intercompany
Input forms for entering breakdown details by partner for both balance
sheet and income statement accounts.
The data input forms can be accessed via the Data Entry Business Process Flow or directly in the different
subfolders of the server input form folder.
1.2.
Graphic Charter
The formatting imposes certain rules on the presentation of the input forms in order to keep the data entry
coherent and guide the business end-user through the data entry process.
Data should not be entered in a cell if any of the following applies:
The given account/flow cross-over is not authorized. For example, an increase in depreciation (flow F25)
is not relevant for tax accounts.
The cell contains a calculation formula, for instance an aggregation.
The cell contains opening balance data on the opening flow.
The actual format of the cells indicates the data type:
Cell format
1.3.
Description
Hatched
Colored fill
and bold font
The cell contains a subtotal resulting from a calculation formula, for instance
an aggregation.
Intercompany Breakdown
To help users identify intercompany accounts, an additional column with the abbreviation IC indicates when
entering breakdown details by partner is relevant.
For income statement accounts, this information is shown in the balance input form.
For balance sheet accounts, this information is shown in the flow analysis input forms.
2.
2.1.
Signs
Assets are entered as positive amounts, except for depreciations, amortizations and provisions which are
entered as negative amounts.
Equity and liabilities are entered as positive amounts.
Expenses and income figures are entered as positive amounts.
2.2.
The Business Process Flow for data entry and the organization of the different input forms into subfolders
guide the end-user through a step-by-step approach for entering data:
The order is:
Closing balances (Profit & Loss, Assets, Equity and Liabilities)
Period movements (breakdown by flow)
Intercompany details
2.3.
Flow Entry
Analyzing data by flow makes it possible to identify variations in the balance sheet between the opening and
closing position, and thus enable the calculation of statement of cash flows line items. Flows available in data
input forms are classified into the following categories:
Flows for current transactions
Flows for specific operations
Consolidation flows dedicated to companies using the equity method which are themselves holder of
consolidated investments
2.3.1.
2.3.2.
F50: reclassification
F70: mergers
These transactions can be entered in each input form or in a dedicated input form, Specific Operations.
The balance of flows F09 and F50 (assets = liabilities) as well as the balance of flow F70 (assets - liabilities =
impact on account P1620 - Merger result) are subject to controls. For more information about data validation
controls, see the section on Data Validation.
2.3.3.
Consolidation flows dedicated to companies using the equity method which are holders of consolidated
investments relate to:
2.4.
Local Adjustments
Data entry is normally done using the INPUT Input Data audit ID. However, local adjustments can also be
entered in input forms using the audit ID INPUT11 Adjustment to Group accounting policies.
The audit ID can be selected in the EPM context pane.
Only one leaf level audit ID (INPUT or INPUT11) must be selected for data entry and it is possible to retrieve
the sum of the audit IDs INPUT and INPUT11 by selecting the node ALL_INPUT.
3.
The starter kit for IFRS contains a preconfigured Business Process Flow (BPF) for data entry dedicated to
the Actual category named L1 Data Entry.
This BPF guides the business end-user through the data collection process and the different data input
forms. Moreover, it helps understanding the logical order of the data entry forms, how to run the validation
controls as well as the actions to be performed once the data entry and validation has been completed.
3.1.
Identification
Dimension
3.2.
Description
Category
The reporting scenario for which data is entered (ACTUAL Actual from GL)
Entity
Time
Detailed Activities
Activities
Description
Import Data
Enter Data
Balance
Non-Current, Non-Financial Assets
Activities
Description
Financial Assets
Other Assets
Net Equity
Net Equity for EMs
Liabilities
Specific Operations
Intercompany (Balance Sheet, P&L, Controls)
Validate Data
Run Controls
Interco Reports
Submit Data
4.
Data Input
Description
Purpose
Prerequisites
List of input forms to be completed first in order for the given input form
to be relevant
Subsequent data
requirements
entry
Note
4.1.
Balance
This example illustrates how to balance the balance sheet entered by business unit using balancing
accounts, and how to transfer the net income of each business unit to the net equity of the primary business
unit.
Subsidiary S is split between business units S1 and S2, and the net income of the data entry period is
assigned to S2.
Closing balances are as follows:
Profit and loss
Unit S1
Unit S2
The net income of business unit S2 is transferred to the net equity of the primary business unit S1 via the
net income balancing account.
Assets
Unit S2
Unit S2
The balance sheets of the primary business unit and the other business units are balanced assets versus
liabilities in the balance sheet balancing account.
4.2.
The following input forms allow for the analysis of changes in the balance sheet between opening and
closing of the data entry period.
The principles are:
For all balance sheet accounts, flow F15 Net variation is calculated as the difference between opening
and movement flows.
The analysis of changes by flow is required for most assets and liabilities in order to build the statement
of cash flows. For these accounts, the flow F15 Net variation identifies the total variation to be broken
down by flow. In the input forms, the flow F15 will in this case be placed at the end of the expansion in the
Control column. Moreover, the data cells will be hatched indicating a non-authorized account/flow pair.
For certain assets, like receivables, and liabilities, like loans, the distinction between increase and
decrease is not necessary. The variation between the opening and closing positions is thus fully allocated
to the flow F15 - Net variation. In the input forms, the flow F15 will in this case be placed at its natural
position in the expansion.
The flow analysis input forms should be completed after entering the closing balances (Balance input form).
In the event that a change in accounting policies or a merger transaction takes place during the data entry
period, it is recommended to enter data in the input form Specific Operations before completing the other
input forms.
All input forms are outlined below with each worksheet appearing according to how it is organized in the
workbook.
4.3.
4.3.1.
Purpose
Analysis of the changes in property, plant and equipment.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Data entry principles
10
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
4.3.2.
Investment Property
Purpose
Analysis of the changes in investment property.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Data entry principles
11
*Specific operations can also be entered in the input form Specific Operations.
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
4.3.3.
Intangible Assets
Purpose
Analysis of the changes in intangible assets.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Data entry principles
Biological Assets
Purpose
Analysis of the changes in biological assets.
Prerequisites
Input form Balance, worksheet Assets
12
4.4.
Financial Assets
4.4.1.
Investments in Subsidiaries
Purpose
Analysis of variation in value of investments in subsidiaries.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Transactions entered for account A1810 - Investments in subsidiaries, JV and associates and A1812 Investments in subsidiaries, JV and associates, Impair. must be broken down by share in the input form IC
Balance Sheet, located in the Intercompany subfolder
Data entry principles
13
The breakdown by share of investments in subsidiaries in the input form IC Balance Sheet for entity A is
entered as follows:
Example 2: Investments previously held in an entity which enters the group consolidation scope
Entity A has bought securities in company B in N-2 for 500. Company B enters the consolidation scope on
01/01/N.
For entity A, data entry period N, the worksheet Investments in subsidiaries is entered as follows:
The breakdown by share of the investments in subsidiaries in the input form IC Balance Sheet for entity A is
entered as follows:
14
Note
The Control column, which shows the difference between the total variation and variations analyzed by
flow, must equal 0 for all shares and for the account total.
The total amount declared by share must not exceed the total of the account.
4.4.2.
Financial Receivables
Purpose
Analysis of the changes in financial receivables.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Breakdown of financial receivables by partner in the input form IC Balance Sheet
Data entry principles
For receivables gross value, changes are allocated to flow F15. It is possible to post manually all or any
of the variation on other flows, and flow F15 is updated automatically.
For allowances for bad debts:
Flow F25 is used for the allowance of the data entry period,
Write-backs should be entered on the flow F35.
Flow F55 is used for the impact of the fair value.
Flow F50* is used for account reclassification. It is notably used when transferring a non-current asset
into a current asset.
Flow F09* records the impact of a change in accounting policies
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for the bad debts account allowances.
4.4.3.
Purpose
Analysis of the changes in other financial assets:
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
15
Purpose
Analysis of the changes in cash and cash equivalents.
Prerequisites
Input form Balance, worksheet Assets
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Data entry principles
The variation between the opening and closing position is automatically posted on flow F15. It is possible
to manually post all or any of the variation on other flows and flow F15 will automatically be updated.
Flow F55 is used for the possible impact of fair value
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification.
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
16
4.5.
Other Assets
4.5.1.
Inventories
Purpose
Analysis of the changes in inventories.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Data entry principles
The variation between the opening and closing position is automatically posted on flow F15. It is possible
to manually post all or any of the variation on other flows and flow F15 will automatically be updated.
Flow F25 is used for inventory depreciation
Flow F35 is used for write-back of inventory depreciation
Flow F55 is used for the possible impact of fair value
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification, notably when transferring a non-current asset into a
current asset
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
4.5.2.
Other Assets
Purpose
Analysis of the changes in other assets.
Prerequisites
Input form Balance, worksheet Assets
Input form Specific Operations (if relevant)
Data entry principles
The variation between the opening and closing position is automatically posted on flow F15, except for
the accounts A3000 Non-current assets and disposal groups held for sale and A3100 Non-current
assets and disposal groups held for distribution to owners. It is possible to post manually all or any of the
variation on other flows and flow F15 will automatically be updated.
Flow F30 is used for the disposal of assets or groups of assets
Flow F55 is used for the possible impact of fair value
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification, notably when transferring a non-current asset into a
current asset. Accounts A3000 Non-current assets and disposal groups held for sale and A3100 Noncurrent assets and disposal groups held for distribution to owners are entered using the flow F50 to
reclassify assets or liabilities.
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
17
Note
The F15 Net variation column, which shows the difference between the total variation and variations
analyzed by flow, must equal 0 for accounts A3000 Non-current assets and disposal groups held for sale
and A3100 Non-current assets and disposal groups held for distribution to owners.
4.6.
Net Equity
4.6.1.
Equity Statement
Purpose
Analysis of variation of shareholders equity.
Prerequisites
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Breakdown of dividends paid per shareholder in the input form Net Equity, worksheet Dividends paid
Data entry principles
Flow F06 records distributions made during the data entry period. The total distribution is calculated on
the fly (with opposite sign) and presented within the same input form in the worksheet Dividends Paid
where you can enter the analysis of dividends paid by shareholder.
Flow F10 corresponds to the net income flow and therefore only relates to account E1610 - Retained
earnings. It is automatically filled in when the income statement is entered.
Flow F40 is used to recognize capital increases or reductions made in cash, however:
Capital increases made by incorporation of reserves or loans are recorded on flow F50 (see example 1)
Capital increases in the form of assets contributed in kind or in the context of mergers are recorded on
flow F70
Reductions in capital by offsetting debit retained earnings are recorded on flow F50*
For treasury shares (Account E1310): the flow F20 is used for purchase and the flow F30 is used for
disposal of treasury shares (see example 2).
For revaluation surplus (accounts E1510 - Revaluation surplus, before tax and E1511 - Income tax on
revaluation surplus):
The flow F55 is used to enter the impact on reserve of fair value adjustment for property plant and
equipment and intangible assets (when the entity chooses the revaluation model as its accounting policy)
and the related tax effect.
The flow F50* is used to transfer revaluation surplus into retained earnings (account E1610), due to the
disposal of the revalued asset or due to the asset depreciation.
For actuarial gains and losses (accounts E1520 - Actuarial gains and losses, before tax and E1521 Income tax on actuarial gains and losses):
The flow F55 is used to enter the share of actuarial gains and losses on retirement benefit obligations
recorded in comprehensive income according to the option proposed by IAS 19 (Article 93) and the
related tax effect.
The flow F50* is used to transfer these amounts into retained earnings in order to empty the suspense
account (see example 3).
For hedging reserves (accounts E1540 - Hedging reserve, before tax and E1541 - Income tax on hedging
reserve):
The flow F55 is used to enter the share of gains or losses on hedging instrument that is determined to be
an effective hedge and the related tax effect.
The flows F20 and F30 allow reclassification adjustment (recycling):
18
F20 is used to remove any gain or loss that was previously recorded from hedging reserves and to
include it in the initial cost of the acquired asset or liability
F30 is used to transfer the gain or loss previously recorded in equity to profit and loss in the same period
in which the hedged cash transaction affects profit and loss
For fair value reserves (account E1550 - Fair value reserve, before tax and E1551 - Income tax on fair
value reserve):
The flow F55 is used to enter the impact of fair value changes on available for sale financial assets,
The flow F30 is dedicated to reclassification adjustment (recycling) of the cumulative gain or loss when
the asset is disposed of (see example 4).
Flow F09* records the impact of a change in accounting policies
Flow F70* records capital increases in the form of assets contributed in kind or in the context of mergers
*Specific operations can also be entered in the input form Specific Operations.
Example 1: Seesaw effect on capital
Company A increases its capital by incorporating a loan for the parent company for the amount of 1000, then
reduces it by the same amount to offset the debit balance brought forward.
Extract of input form Liabilities, worksheet Other Financial Liabilities:
19
20
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
4.6.2.
Dividends Paid
Purpose
Analysis of dividends paid by shareholder.
Prerequisites
Input form Net Equity, worksheet Equity statement
Data entry principles
The total amount of dividends paid populates the first row of the worksheet. It is calculated on the fly on the
basis of flow F06 (with opposite sign) from the net equity accounts.
Dividends paid by shareholder should be entered for the holding companies receiving dividends. Dividends
paid to non-consolidated companies should not be entered.
Note
The total amount declared by intercompany must not exceed the total dividends paid calculated on the fly.
4.7.
Net Equity EM
4.7.1.
Purpose
Analysis of variation of shareholders equity. This input form is dedicated to companies using the equity
method only.
21
Prerequisites
None
Subsequent data entry requirements
Breakdown of dividends paid by shareholder in the input form Net Equity EM, worksheet Dividends paid
Data entry principles
In addition to the accounts and flows presented in the standard net equity input form, the Equity Statement
for Equity Method Companies includes additional consolidation accounts, including foreign currency
translation reserves and non-controlling interests, and also consolidation flows.
Flow F10 corresponds to the net income flow and therefore only relates to account E1610 Retained
earnings and E2010 Non-controlling interests - reserves and retained earnings. Account E1610 Retained
earnings is automatically filled in with the net income from the dedicated account XP000 Profit (loss) - EM
and possibly reduced by the share of non-controlling interest entered in account E2010 Non-controlling
interests - reserves and retained earnings.
Flow F80, currency translation adjustment, is used for exchange difference variation
Impact of scope changes should be entered on the following flows:
o Flow F01 is used for incoming entities
o Flow F92 is used for changes in financial interest of full consolidated entities
o Flow F98 is used for outgoing entities
Note
The Control column, which shows the difference between the total variation and variations analyzed by
flow, must equal 0 for all shares and for the account total.
4.8.
Liabilities
4.8.1.
Provisions
Purpose
Analysis of the changes in provisions.
Prerequisites
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Analysis of intercompany provisions by partner in the input form IC Balance Sheet
Data entry principles
Flow F25 corresponds to allocations over the data entry period
Flow F35 corresponds to write-back over the data entry period
For provisions for employee benefits, flow F55 is used for entering the impact of actuarial gains and
losses included in comprehensive income (see the example for the input form Equity statement)
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification, notably when transferring a non-current provision into a
current provision
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
22
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
4.8.2.
Purpose
Analysis of the changes in debts on purchase of assets and payables.
Prerequisites
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Analysis of intercompany debts and payables in the input form IC Balance Sheet.
Data entry principles
The variation between the opening and closing position is automatically calculated on flow F15. It is
possible to post manually all or a part of the variation on other flows and flow F15 will automatically be
updated.
Flow F55 is used for the possible impact of fair value
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification, notably for the transfer of a non-current borrowing to a
current borrowing
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
4.8.3.
Purpose
Analysis of the changes in other financial liabilities, like borrowings, convertible bonds, and derivatives.
Prerequisites
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Subsequent data entry requirements
Intercompany other financial liabilities in the input form IC Balance Sheet.
Data entry principles
23
Note
The Control column, which shows the difference between the total variation and variations analyzed by flow,
must equal 0 for all accounts.
4.8.4.
Other Liabilities
Purpose
Analysis of the changes in other liabilities, like deferred tax and deferred income.
Prerequisites
Input form Balance, worksheet Equity and Liabilities
Input form Specific Operations (if relevant)
Subsequent data entry requirements
None
Data entry principles
The variation between the opening and closing position is automatically calculated on flow F15 Net
variation. It is possible to post manually all or a part of the variation on other flows and flow F15 will
automatically be updated.
Flow F30 is used for the removal of liabilities included in the disposal of assets
Flow F55 is used for the possible impact of fair value
Flow F09* records the impact of a change in accounting policies
Flow F50* is used for account reclassification, particularly for the transfer of a non-current borrowing to a
current borrowing
Flow F70* is used in the context of merger operations
*Specific operations can also be entered in the input form Specific Operations.
Note
The F15 Net variation column, which shows the difference between the total variation and variations
analyzed by flow, must equal 0 for account L3000 - Liabilities included in disposal groups classified as held
for sale.
4.9.
Specific Operations
Purpose
Enter the impact of changes in accounting policies and merger operations on the balance sheet.
Prerequisites
None
Subsequent data entry requirements
None
24
Prerequisites
Input form Financial Assets, worksheets Investments in Subsidiaries, Financial Receivables and Other
Financial Assets (accounts with a blue arrow)
Input form Liabilities, worksheets Provisions, Debts and Payables and Other Financial Liabilities (accounts
with a blue arrow)
Subsequent data entry requirements
None
Data entry principles
Data entered in the flow analysis input forms populates the upper part of this input form with the detail by
flow for each balance sheet account.
To enter breakdown details, partners should be added in the dedicated lower part using one of the following
EPM Add-In functionalities:
Insert members: right click and choose EPM -> Insert Members to insert one or several partners.
Member recognition: simply type in the code of the partner entity and a new data entry line will
automatically be added for this partner.
Note
The total amount declared for intercompany must not exceed the total of the account.
25
Dividends received
Prerequisites
Input form Balance, worksheet Profit & Loss (accounts with a blue arrow)
Subsequent data entry requirements
None
Data entry principles
Data entered in the flow analysis input forms populates the upper part of this input form with the detail by
flow for each balance sheet account.
To enter breakdown details, partners should be added in the dedicated lower part using one of the following
EPM Add-In functionalities:
Insert members: right click and choose EPM -> Insert Members to insert one or several partners.
Member recognition: simply type in the code of the partner entity and a new data entry line will
automatically be added for this partner.
Note
The total amount declared for intercompany must not exceed the total of the account.
Purpose
This control report retrieves all intercompany balance sheet accounts by partner:
Prerequisites
Input form Balance, worksheets Assets and Equity and liabilities
Input form Financial Assets, worksheets Investments in Subsidiaries, Financial Receivables and Other
Financial Assets
Input form Liabilities, worksheets Provisions, Debts and Payables and Other Financial Liabilities
Input form IC Balance Sheet
Principles
Data entered in the flow analysis and intercompany input forms populates this report for each balance sheet
account with the detail by flow and by partner.
26
This report allows checking that the relevant breakdown by partner has been entered and that the total
amount declared for intercompany does not exceed the total of the account.
4.12.2.
Purpose
This control report retrieves all intercompany profit and loss accounts by partner:
Income and expenses
Dividends received
Prerequisites
Input form Balance, worksheet Profit & Loss
Input form IC Profit and Loss
Principles
Data entered in the input form Balance, worksheet Profit & Loss, and in the intercompany input forms
populates this report for each profit and loss account.
This report allows checking that the relevant breakdown by partner has been entered and that the total
amount declared for intercompany does not exceed the total of the account.
5.
Data Validation
5.1.
Controls
A number of controls have been configured in the starter kit to validate the coherence of data entered in the
input forms.
These controls are grouped within one control set for actual data, A Control set for Actual data. They are
organized logically, following the order of data entry, and can be carried out progressively throughout the
data entry process.
All controls and all entities are associated to the Basic control level.
These controls validate data entered on audit IDs included in the node ALL_INPUT All local input (INPUT
Input Data and INPUT11 Local adj. to Group accounting policies), either audit ID by audit ID or all audit IDs
aggregated.
The controls are all blocking controls which, if not validated, prevent the submission of data for approval in
the workflow process for the given data region (Category, Time, Entity).
5.2.
Types of Controls
The controls are codified according to the type of data they control.
5.2.1.
Controls prefixed with the letter A are basic accounting controls that are applied to the opening and closing
position of the data entry period. Controls on the opening position deal more specifically with companies
entering the consolidation scope since opening data for other companies is pre-entered by copying the
closing balance of the previous period.
27
Controls prefixed with the letter B ensure that flows are used correctly, in particular:
Exhaustive analysis of changes in balance sheet items, meaning the Control column equals 0
The balance between assets and liabilities for reclassifications (flow F50) and changes in accounting
policies (flow F09)
The equation assets liabilities = merger result (flow F70)
5.2.3.
Intercompany Controls
Controls on the intercompany breakdown are prefixed with the letters C, D and E according to the type of
data they control:
Controls prefixed with the letter C check the basic account reconciliation at breakdown level, for example
that the gross value is greater than the provisions for each partner.
Controls prefixed with the letter D check the exhaustive flow analysis by partner for balance sheet items.
Controls prefixed with the letter E check that the sum of the totals declared by intercompany is not greater
than the total sum of the account in question at opening and at closing respectively (ALL_INTERCO <
I_NONE).
5.3.
Controls are run from the Control Monitor which can be accessed directly from the Validate Data step of the
Data Entry Business Process Flow or via the Consolidation Central on the web.
Once the controls have been run, the details for each control can be viewed in the control results.
A control can have one of the following three statuses:
To be executed
Passed
Failed
To correct a control that has failed, the following information is available:
A detailed description of the control, when possible including the ID and label of the accounts that are
processed by the control
The equation that corresponds to the type of control (equal to, greater than etc.)
The result which indicates the calculated difference
In the section Documents for are links to the input form(s) in which an eventual error can be visualized and/or
corrected.
Once all errors have been corrected, the controls must be run again to change the status to Passed for the
entity in question.
6.
Data Submission
Once input data validation is finalized, the local data entry user can submit the data for approval. This is
done in two steps:
Change the work status from Started to Submitted to lock further data input for the local user
28
Submit the Data Entry Business Process Flow (by clicking the Submit button) in order to activate the
reviewing process
Following, the reviewer/manager in charge of the data approval can rerun the controls, verify data
consistency, enter and correct data.
If the reviewer approves the data input for the data region in question, he should change the work status
from Submitted to Approved, which will lock further data entry for all users, and complete the Business
Process Flow.
If the reviewer rejects the data input, he should change the work status from Submitted to Rejected and
reject the Business Process Flow in order to reopen the data entry for the local data entry user which will
then be able to repeat the validation steps.
29
B.
1.
Overview
CONSOLIDATION MODEL
IC MATCHING MODEL
BA (Y+1)
BA (Y+1)
1
F09 (Y)
1. Fill in the opening Cash & Cash Equivalent of the Annual Budget from the Forecast category .
2. Load / Input data for Annual Budget.
2
2.
Principles
2.1.
The input forms are organized into one folder named BA. They can be accessed via a dedicated Business
Process Flow or directly in the different subfolders of the server input form folder.
The end-user should fill in the Balances (Profit & Loss and Cash Flows) first and then complete the
Intercompany details input form.
2.2.
The Page Axis displays the relevant data entry region as selected in the EPM Context bar:
30
2.3.
Graphic Charter
2.4.
Periodicity
The data is supposed to be entered / loaded on a yearly basis and on a single period (December).
3.
The starter kit for IFRS contains a preconfigured Business Process Flow (BPF) for data entry dedicated to
the Annual Budget named 0BA Annual Budget Local.
3.1.
Identification
Dimension
3.2.
Description
Category
The reporting scenario for which data is entered (BA Annual Budget).
Entity
Time
Detailed Activities
Activities
Import Data
Enter Data
Description
Import external data
-
Validate Data
Run Controls
Interco Reports
Submit Data
31
4.
Data Input
4.1.
BA_Balance
4.1.1.
Prerequisites
1. Ensure the data region (Entity, Time and Audit ID) defined in the EPM Context bar is correct.
2. Refresh Worksheet.
3. Ensure the column F09 (September Forecast Y) is already filled in.
Annual budget
data to be
entered / loaded
Forecast data
(read only)
Intercompany
accounts
Subtotals
(automated
calculation)
4.1.2.
Prerequisites
1. Refresh Worksheet.
2. Ensure the column F09 (September Forecast Y) is already filled in.
3. Ensure the P&L data has been saved in order to automatically fill in the following accounts:
32
Forecast data
(read only)
Cells
automatically
filled in
Intercompany
accounts
Subtotals
(automated
calculation)
4.2.
BA_INTERCOMPANY
Purpose
Analysis of a single profit and loss or Cash Flow account by partner:
P&L
Reciprocal income and expenses
Dividends received
Cash Flow
Dividends (received, paid)
Proceeds from sale and purchase of short term investments
33
Intercompany
detail must be
entered
5.
Data Validation
5.1.
Controls are grouped within one control set for Annual Budget data named 0BA Set of Controls for Annual
Budget. They are organized logically, following the order of data entry, and can be carried out progressively
throughout the data entry process.
These controls validate data entered on audit IDs included in the node ALL_INPUT All local input (INPUT
Input Data and INPUT11 Local adj. to Group accounting policies), either audit ID by audit ID or all audit IDs
aggregated.
The controls are all blocking controls which, if not validated, prevent the submission of data for approval in
the workflow process for the given data region (Category, Time, Entity).
5.2.
Controls prefixed with 0BA_A1_... are basic accounting controls between P&L and SCF.
34
5.3.
Intercompany Controls
Control prefixed with 0BA_C1_02 checks that the partner detail entered on dividends received is similar
between P&L and SCF.
P&L accounts controls prefixed with 0BA_ E2_... check that the sum of the totals declared by
intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE).
SCF accounts controls prefixed with 0BA_ E4_... check that the sum of the totals declared by
intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE).
6.
Intercompany Reports
The owner of the data entry can access intercompany reports stored in the ICMatching Model, in order to
check possible discrepancies with partners declarations.
Folder: named BUDGETFORECAST
Report: BF Reconciliation for one entity
7.
Data Submission
Once input data validation is finalized, the local data entry user can submit the data for approval.
This is done in two steps:
Change the work status from Started to Submitted to lock further data input for the local user
Submit the Data Entry Business Process Flow (by clicking the Submit button) in order to activate the
reviewing process
35
The reviewer/manager in charge of the data approval can rerun the controls, verify data consistency, enter
and correct data.
If the reviewer approves the data input for the data region in question, he should change the work status
from Submitted to Approved, which will lock further data entry for all users, and complete the Business
Process Flow.
If the reviewer rejects the data input, he should change the work status from Submitted to Rejected and
reject the Business Process Flow in order to reopen the data entry for the local data entry user which will
then be able to repeat the validation steps.
36
C.
1.
Overview
The Monthly Budget category as implemented in the Starter Kit proposes two ways to enter data:
A Year To Date approach to be performed in the Consolidation Model
A Periodic approach to be performed in the PeriodicEntry Model
In any case, the consolidated data is provided on a year to date basis in the Consolidation model.
1.1.
IC MATCHING MODEL
CONSOLIDATION MODEL
3
2
BM (Y+1)
BM (Y+1)
1
Actual (Y)
1. Fill in the opening Cash & Cash Equivalent of the Monthly Budget (March) from the Actual category
37
1.2.
Periodic approach
CONSOLIDATION MODEL
IC MATCHING MODEL
4
5
BM (Y+1)
BM (Y+1)
PERIODICENTRY MODEL
Actual (Y)
1
BM (Y+1)
BA (Y+1)
1. Fill in the opening Cash & Cash Equivalent of the Monthly Budget (March) from the Actual category .
4
2.
Principles
2.1.
The input forms are organized into two folders named BM (YTD) for the year to date approach and BM
(PER) for the periodic approach.
The end-user should fill in the Balances (Profit & Loss and Cash Flows) first and then complete the
Intercompany details input form.
2.2.
The Page Axis displays the relevant data entry region as selected in the EPM Context bar:
38
Periodic approach:
Measure: data is entered in the PeriodicEntry Model on a PER basis.
Time: Total year (e.g. TOTAL 2018).
Entity: for which data is being entered / loaded
AuditID: Data is normally input using the INPUT Input Data audit ID. However, local adjustments can
also be entered in input forms using the audit ID INPUT11 Adjustment to Group accounting policies.
Only one leaf level audit ID (INPUT or INPUT11) must be selected for data entry and it is possible to
retrieve the sum of the audit IDs INPUT and INPUT11 by selecting the node ALL_INPUT.
Flow: No FLOW dimension in the PeriodicEntry Model
Interco: All input forms (Balance and Intercompany) are locked on I_NONE- No intercompany member.
Currency: Local currency
Consoscope: G_NONE
2.3.
Graphic Charter
2.4.
Periodicity
3.
The starter kit for IFRS contains two preconfigured Business Process Flows (BPF) for the Monthly Budget
data entry:
0BM Monthly Budget Local YTD, to enter / load data according to the YTD approach
0BM Monthly Budget Local PER, to enter / load data according to the Periodic approach
3.1.
Identification
Dimension
Description
Category
The reporting scenario for which data is entered (BM Monthly Budget)
Entity
Time
39
3.2.
Detailed Activities
3.2.1.
Activities
Import Data
Description
Import external data
Enter Data
Validate Data
Run Controls
Interco Reports
Submit Data
3.2.2.
Import Data
Description
Import external data
Enter Data
Validate Data
Run Controls
Submit Data
Transfer data in
YTD
Interco Reports
4.
Data Input
4.1.
BM_Balance_YTD or _PER
4.1.1.
Prerequisites
1. Ensure the data region (Entity, Time and Audit ID) defined in the EPM Context bar is correct.
2. Refresh Worksheet.
3. Ensure the column BA (Annual Budget) is already filled in.
40
4.1.2.
Prerequisites
1. Select the Cash Flow tab.
2. Refresh Worksheet.
3. Ensure the column BA (Annual Budget) is already filled in.
41
4. Ensure the P&L data has been saved in order to automatically fill in the following accounts:
42
4.2.
BM_INTERCOMPANY_YTD or _PER
Purpose
Analysis of a single profit and loss or Cash Flow account by partner on 12 months or 4 quarters:
P&L
Reciprocal income and expenses
Dividends received
Cash Flow
Dividends (received, paid)
Proceeds from sale and purchase of short term investments
Proceeds from issuing shares
Prerequisites
Input forms in BM_BALANCE_YTD or _PER (accounts flagged with IC + blue arrow)
Data entry principles
Data entered in the BM_BALANCE forms populates the upper part of this input form (I_NONE).
To enter breakdown details, partners should be added in the dedicated lower part using one of the following
EPM Add-In functionalities:
1. Select the correct sheet (P&L or SCF).
2. Select values in the EPM context (the account, time, category).
3. Refresh worksheet.
4. Insert members (partners).
5. Enter amounts:
Warning: expenses are displayed as positive amounts unlike in the balance input form. Nevertheless, the
detail by partner should be entered as positive amounts.
43
The total amount declared for intercompany (ALL_INTERCO) must not exceed the total of the account
(I_NONE).
Intercompany
detail must be
entered
5.
Data Validation
5.1.
Controls are grouped within two control sets for Monthly Budget data named:
0BM_YTD Set of Controls for Monthly Budget entered in YTD.
1BM_PER Set of Controls for Monthly Budget entered in Periodic.
They are organized logically, following the order of data entry, and can be carried out progressively
throughout the data entry process.
Due to cross controls between P&L and Cash Flow accounts, they must only be run for quarters March,
June, September and December (SCF is entered on a quarterly basis).
These controls validate data entered on audit IDs included in the node ALL_INPUT All local input (INPUT
Input Data and INPUT11 Local adj. to Group accounting policies), either audit ID by audit ID or all audit IDs
aggregated.
The controls are all blocking controls which, if not validated, prevent the submission of data for approval in
the workflow process for the given data region (Category, Time, Entity).
5.2.
Controls prefixed with 0BM_A1_... and 1BM_A1_... are basic accounting controls between P&L and SCF.
These controls notably check that:
5.3.
Intercompany Controls
Controls prefixed with 0BM_C1_02 and 1BM_C1_02 check that the partner detail entered on dividends
received is similar between P&L and SCF
For P&L accounts, controls prefixed with 0BM_ E2_... and 1BM_ E2_... check that the sum of the totals
declared by intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE).
For SCF accounts, controls prefixed with 0BM_ E4_... and 1BM_ E4_... check that the sum of the totals
declared by intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE).
44
6.
Intercompany Reports
The owner of the data entry can access intercompany reports stored in the ICMatching Model, in order to
check possible discrepancies with partners declarations.
Folder: named BUDGETFORECAST
Report: BF Reconciliation for one entity
7.
Data Submission
Once input data validation is finalized, the local data entry user can submit the data for approval.
This is done in two steps:
Change the work status from Started to Submitted to lock further data input for the local user
Submit the Data Entry Business Process Flow (by clicking the Submit button) in order to activate the
reviewing process
The reviewer/manager in charge of the data approval can rerun the controls, verify data consistency, enter
and correct data.
If the reviewer approves the data input for the data region in question, he should change the work status
from Submitted to Approved, which will lock further data entry for all users, and complete the Business
Process Flow.
If the reviewer rejects the data input, he should change the work status from Submitted to Rejected and
reject the Business Process Flow in order to reopen the data entry for the local data entry user which will
then be able to repeat the validation steps.
8.
As explained previously, whatever data entry approach is chosen, consolidated data is created in the
Consolidation Model. In case of a Periodic approach for data collection, the script BM_PER_TO_YTD must
be run to transfer monthly budget data from the PeriodicEntry Model to the Consolidation Model in the same
category BM.
To run the script, values to be selected are:
Entity
Time = December
This script performs the following actions:
Cumulate and transfer month per month P&L data into category BM
Cumulate and transfer quarter per quarter SCF data into category BM
45
D.
FORECAST CATEGORY
1.
Overview
The September Forecast category as implemented in the Starter Kit proposes two ways to enter data:
A Year To Date approach to be performed in the Consolidation Model
A Periodic approach to be performed in the PeriodicEntry Model
In any case, the consolidated data is provided on a year to date basis in the Consolidation Model.
1.1.
CONSOLIDATION MODEL
Actual
IC MATCHING MODEL
1
F09
F09
1. Fill in the opening Cash & Cash Equivalent of the Forecast from the Actual category at end of
5
September .
2. Load / Input data for the last quarter.
5
46
1.2.
Periodic approach
5
CONSOLIDATION MODEL
IC MATCHING MODEL
PERIODICENTRY MODEL
F09
F09
4
F09
Actual
1
BM
1. Fill in the opening Cash & Cash Equivalent of the September Forecast from the Actual category at end
of September
6
6
2. Fill in the last quarter of the Monthly Budget into the Forecast .
3. Load / Input data, or modify Forecast data for the last quarter.
4. Transfer Forecast data from the PeriodicEntry Model to the Consolidation Model.
6
2.
Principles
2.1.
The input forms are organized into two folders named F09 (YTD) for the year to date approach and F09
(PER) for the periodic approach.
The end-user should fill in the Balances (Profit & Loss and Cash Flows) first and then complete the
Intercompany details input form.
2.2.
The Page Axis displays the relevant data entry region as selected in the EPM Context bar:
47
Periodic approach:
Measure: data is entered in the PeriodicEntry Model on a PER basis.
Time: Total year (e.g. TOTAL 2018).
Entity: for which data is being entered / loaded
AuditID: Data is normally input using the INPUT Input Data audit ID. However, local adjustments can
also be entered in input forms using the audit ID INPUT11 Adjustment to Group accounting policies.
Only one leaf level audit ID (INPUT or INPUT11) must be selected for data entry and it is possible to
retrieve the sum of the audit IDs INPUT and INPUT11 by selecting the node ALL_INPUT.
Flow: NO FLOW.
Interco: All input forms (Balance and Intercompany) are locked on I_NONE- No intercompany member.
Currency: Local currency
Consoscope: G_NONE
2.3.
Graphic Charter
2.4.
Periodicity
3.
The starter kit for IFRS contains two preconfigured Business Process Flows (BPF) for data entry:
0F09 Forecast Local YTD, to enter / load data according to the YTD approach
0F09 Forecast Local PER, to enter / load data according to the Periodic approach
3.1.
Identification
Dimension
Description
Category
The reporting scenario for which data is entered (F09 September Forecast)
Entity
Time
48
3.2.
Detailed Activities
3.2.1.
Import Data
Description
Import external data
Enter Data
Validate Data
Run Controls
Interco Reports
Submit Data
3.2.2.
Activities
Import Data
Description
Import external data
Enter Data
Validate Data
Run Controls
Submit Data
Transfer data in
YTD
Interco Reports
4.
Data Input
4.1.
F09_Balance_YTD or _PER
4.1.1.
Prerequisites
1. Ensure the data region (Entity, Time and Audit ID) defined in the EPM context is correct.
2. Refresh Worksheet.
3. Ensure data from January to September is already filled in.
4. Ensure the last quarter is already filled in with the last quarter of the Monthly Budget if need be, for a
periodic approach only.
49
Intercompany
accounts
Subtotals (automated
calculation)
4.1.2.
Prerequisites
1. Refresh Worksheet.
2. Ensure data from March, June and September is already filled in.
3. Ensure the P&L data has been saved in order to automatically fill in accounts:
50
4.2.
F09_INTERCOMPANY_YTD or _PER
Purpose
Analysis of a single profit and loss or Cash Flow account by partner on 3 months or 1 quarter:
P&L
Reciprocal income and expenses
Dividends received
Cash Flow
Dividends (received, paid)
Proceeds from sale and purchase of short term investments
Proceeds from issuing shares
Prerequisites
Input forms in F09_BALANCE_YTD or _PER (accounts flagged with IC + blue arrow)
Data entry principles
Data entered in the F09_BALANCE forms populates the upper part of this input form (I_NONE).
To enter breakdown details, partners should be added in the dedicated lower part using one of the following
EPM Add-In functionalities:
1. Select the correct sheet (P&L or SCF).
2. Select values in the EPM context (the account, time, category).
3. Refresh worksheet.
4. Insert members (partners).
5. Enter amounts.
Warning: expenses are displayed as positive amounts unlike in the balance input form. Nevertheless, the
detail by partner should be entered as positive amounts.
51
The total amount declared for intercompany (ALL_INTERCO) must not exceed the total of the account
(I_NONE).
5.
Data Validation
5.1.
Controls are grouped within two control sets for September Forecast data named:
0F9_YTD Set of Controls for September Forecast entered in YTD.
1F9_PER Set of Controls for September Forecast entered in Periodic.
They are organized logically, following the order of data entry, and can be carried out progressively
throughout the data entry process.
They must only be run for quarters (March, June, September and December).
These controls validate data entered on audit IDs included in the node ALL_INPUT All local input (INPUT
Input Data and INPUT11 Local adj. to Group accounting policies), either audit ID by audit ID or all audit IDs
aggregated.
The controls are all blocking controls which, if not validated, prevent the submission of data for approval in
the workflow process for the given data region (Category, Time, Entity).
5.2.
Controls prefixed with 0F9_A1_... and 1F9_A1_... are basic accounting controls between P&L and SCF.
These controls notably check that:
5.3.
Intercompany Controls
Controls prefixed with 0F9_C1_02 and 1F9_C1_02 check that the partner detail entered on dividends
received is similar between P&L and SCF
P&L accounts controls prefixed with 0F9_ E2_... and 1F9_ E2_... check that the sum of the totals
declared by intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE)
SCF accounts controls prefixed with 0F9_ E4_... and 1F9_ E4_... check that the sum of the totals
declared by intercompany is not greater than the total sum of the account (ALL_INTERCO < I_NONE)
Intercompany Reports
The owner of the data entry can access intercompany reports stored in the ICMatching Model, in order to
check possible discrepancies with partners declarations.
Folder: named BUDGETFORECAST
6.
Data Submission
Once input data validation is finalized, the local data entry user can submit the data for approval.
This is done in two steps:
Change the work status from Started to Submitted to lock further data input for the local user
Submit the Data Entry Business Process Flow (by clicking the Submit button) in order to activate the
reviewing process
52
The reviewer/manager in charge of the data approval can rerun the controls, verify data consistency, enter
and correct data.
If the reviewer approves the data input for the data region in question, he should change the work status
from Submitted to Approved, which will lock further data entry for all users, and complete the Business
Process Flow.
If the reviewer rejects the data input, he should change the work status from Submitted to Rejected and
reject the Business Process Flow in order to reopen the data entry for the local data entry user which will
then be able to repeat the validation steps.
7.
As explained previously, whatever data entry approach is chosen, consolidated data is created in the
Consolidation Model. In case of a Periodic approach for data collection, the script F09_PER_TO_YTD must
be run to transfer Forecast data from the PeriodicEntry Model to the Consolidation Model in the same
category F09.
To run the script, values to be selected are:
Entity
Time = December
This script performs the following actions:
Aggregate (Actual + Forecast), cumulate month per month and transfer into the category F09
Aggregate (Actual + Forecast), cumulate quarter per quarter and transfer into the category F09
53
www.sap.com