# Lucanet Support Documentation
> Official product documentation for the Lucanet CFO Solution Platform —
> Administration, Consolidation & Financial Planning, Disclosure Management,
> ESG Reporting, Lease Accounting, xP&A and more. Maintained by the Lucanet
> knowledge management team. Source of truth: https://support.lucanet.com.
>
> This file is the entry point for LLMs. Every link below points to a Markdown
> version of a page (URL + `.md`). Strip `.md` to read the same page in a
> browser. A full-corpus single file is available at /llms-full.txt.
## Getting Started
Enjoy a seamless user experience and effortless financial management. The new Lucanet Cloud Platform provides a smooth, standardized UX with uniform functions for all the solutions you run on it.
---
title: "Basic Configuration"
description: "On this page, you will find an overview of basic settings and key system information in the Lucanet CFO Solution Platform. You can change the language of the user interface, configure date and number formats, change your password, view your user profile, manage consents you have granted for external services, see the current Lucanet version, and, as an administrator, download SBOM files in JSON format."
source_url: https://support.lucanet.com/en/documentation/getting-started/basic-configuration
language: en
last_updated: 2026-08-31
---
# Basic Configuration for the Lucanet CFO Solution Platform
## Overview
On this page, you will find an overview of basic settings and key system information in the Lucanet CFO Solution Platform. You can change the language of the user interface, configure date and number formats, change your password, view your user profile, manage consents you have granted for external services, see the current Lucanet version, and, as an administrator, download [SBOM](https://support.lucanet.com/en/documentation/glossary.md#software-bill-of-materials-sbom) files in JSON format.
The following functions are available to you:
## Changing the User Interface Language
You can change the user interface language in the **User account** area in the main menu.
To change the language of the user interface:
1. Click the **user account** area (avatar, name, and language indicator) at the bottom of the main menu. The **account menu** is displayed as follows, for example:
User acount area and the account menu
2. Select your desired language from the **Language** drop-down list.
## Configuring the Date and Number Format
To configure the format of numbers and dates on the Lucanet CFO Solution Platform:
1. Click the **user account** area (avatar, name, and language indicator) at the bottom of the main menu. The **account menu** is displayed as follows, for example:
User acount area and the account menu
2. Click **Formatting preferences**. The **Formatting Preferences** dialog is displayed as follows:
'Formatting Preferences' dialog
3. Configure your preferred date and number format.
4. Click **Save**.
## Changing Your Password
### Changing Your Password Voluntarily
You can change your password at any time through your profile settings.
To change your password:
1. Click the **user account** area (avatar, name, and language indicator) at the bottom of the main menu. The **account menu** is displayed as follows, for example:
User acount area and the account menu
2. Click **Change password**. The **Change Password** dialog is displayed as follows:
'Change Password' dialog
3. Change your password.
4. Click **Save**.
> **Warning:** **Important Notes:**
>
> - You can only change your password **twice per day** for security reasons.
> - Your new password cannot be the same as any of your **previous 5 passwords**.
>
> For detailed password requirements, see our [Password Policy](https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform.md#password-policy).
### What Happens When Your Password Expires
Passwords expire after **90 days** for security reasons. To help you prepare, you will receive notifications **30, 14, 7, and 1 day(s)** before your password expires.
The password expiration reminder e-mails include a direct link to the login page of the Lucanet CFO Solution Platform. Click the link in the e-mail to open the login page and change your password.
When your password expires and you attempt to log in:
- You will be automatically redirected to the password reset page.
- A verification code will be automatically sent to your registered e-mail address.
Please enter the verification code and set your new password following the on-screen instructions.
> **Tip:** **Tip**
>
> We recommend changing your password **before it expires** to avoid any interruption to your access. You can change your password at any time using the steps in [Changing Your Password Voluntarily](#changing-your-password) above.
## Viewing Your User Profile
On the Lucanet CFO Solution Platform, you can access your user profile for purposes such as checking your saved e-mail address.
To access your user profile:
1. Click the **user account** area (avatar, name, and language indicator) at the bottom of the main menu. The **account menu** is displayed as follows, for example:
User acount area and the account menu
2. In the account menu, click the user info area at the top. The **My Profile** dialog is displayed as follows, for example:
'My profile' dialog
## Managing Consents for External Services
You can view and manage consents you have granted for external websites and applications (such as the Consensus platform for our solution demos).
To access consent management:
1. Click the **user account** area (avatar, name, and language indicator) at the bottom of the main menu. The **account menu** is displayed as follows, for example:
User acount area and the account menu
2. In the account menu, click the user info area at the top. The **My Profile** dialog is displayed.
3. Click **Manage consent**. The **Manage consent** section is displayed as follows, for example:
Managing consent in the 'My Profile' dialog
The consent list displays the following information for each granted consent:
- **Solution or service user gave consent for**: The external website or application name
- **Last updated**: Date when consent was granted or revoked
- **Action**: Button to revoke the consent. After revoking consent, the consent dialog will be displayed again when you access the service.
If an external service updates its privacy policy, your consent may be automatically revoked and you will need to provide consent again.
## Viewing Product Versions
To access your current Lucanet versions:
1. Click **Support and Customer Portal** or the help main menu icon in the main menu.
2. Choose **About Lucanet** from the context menu.
'About Lucanet' option in the main menu
The **About Lucanet** dialog will be displayed as follows, for example:
'About Lucanet' dialog
You can expand each solution and **Platform Services** to view the version of the subcomponents. The information is read-only and can be copied for reference.
> **Note:** The **SBOM** column is only available for administratiors. See [Accessing and Downloading SBOMs](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#accessing-and-downloading-sboms) for more information.
## Accessing and Downloading SBOMs
The Lucanet CFO Solution Platform provides comprehensive [Software Bill of Materials (SBOM)](https://support.lucanet.com/en/documentation/glossary.md#software-bill-of-materials-sbom) documentation to enhance security, transparency and compliance. This information is exclusively available to administrators via the **About Lucanet** option in the main menu.
To access SBOM information:
1. Click **Support and Customer Portal** or the help main menu icon in the main menu.
2. Choose **About Lucanet** from the context menu.
'About Lucanet' option in the main menu
The **About Lucanet** dialog will be displayed as follows, for example:
'About Lucanet' dialog with downloadable SBOMs
For releases where an SBOM is available for download, you will see an the download sbom icon in the SBOM column. Releases without downloadable SBOMs display an the info icon instead.
Click the download sbom icon next to the desired component to download the SBOM file in JSON format.
---
---
title: "Differences Between Lucanet.Financial Client and CFO Solution Platform"
description: "This article addresses users migrating from Lucanet.Financial Client to the CFO Solution Platform. It provides an overview of the key differences, such as access and login, administration, renaming, and functional differences."
source_url: https://support.lucanet.com/en/documentation/getting-started/differences-lnfc-platform
language: en
last_updated: 2026-09-01
---
# Differences Between Lucanet.Financial Client and CFO Solution Platform
## Overview
This article is intended for users who are **migrating** from **Lucanet.Financial Client** to the **CFO Solution Platform**. It provides an overview of the key differences, such as **access and login, administration, renaming**, and **functional differences.**
> **Warning:** Please note that this list is not exhaustive, but contains only a selection of the most important changes.
> **Note:** For getting started with our CFO Solution Platform, the following courses are available in our **Lucanet Learning Space**:
>
> - [Onboarding Journey | Lucanet CFO Solution Platform](https://learning.lucanet.com/cstart/course/750)
> - [Migrate to the CFO Solution Platform | Consolidation & Financial Planning](https://learning.lucanet.com/catalog/view/course/id/785)
## Differences in Access and Login
The CFO Solution Platform is not installed locally on your computer; instead, it is accessed via a web browser.
To do this, enter the URL of the CFO Solution Platform into your browser’s address bar and log in using your credentials.
For more information, see [Opening the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform.md).
## Differences in Administration
Several administrative functions are now configured globally at the **platform level**, including **user management, notifications**, and the **Task Center**.
Below is an overview of the structural changes to the administration:
Differences in Administration
| Lucanet.Financial Client | Lucanet CFO Solution Platform |
|---------|---------|
| **Users and user groups** were displayed in the **Administration** folder in the overview. | **Users and user groups** are managed in the cross-platform **Administration** section of the main menu. |
| The **Corporate design** could be changed in the workspace of the same name in the **Administration** folder in the overview. | **Customer-specific changes,** such as the corporate design, can be made in the cross-platform **Administration** section under **Platform Management**. |
| **Tasks** were managed in the folder of the same name in the overview. | Tasks are managed in the **Task Center**. |
| The workspaces were configured in the **Administration** folder within the **Workspaces** workspace. | The workspaces are configured under **Workspace Configuration** at the bottom of the structure view of the **Consolidation & Financial Planning** solution. |
## Differences on the User Interface
The user interface of Consolidation & Financial Planning has been redesigned to be more intuitive, and making it easier to navigate. For example, the following structural changes and/or renaming have been made:
| Lucanet.Financial Client | Lucanet CFO Solution Platform |
|---------|---------|
| **Postings** workspace | **Journals** workspace |
| **Audit Trails** workspace | **Period locks** workspace |
| Function **Print** | Function **Export** |
| Planning wizard Reconiliation of the general leder | Planning wizard Transfer from Actual Balance to Plan |
| Function **Configuration of the view** that was located in the toolbar of the Lucanet.Financial Client | Function is now called **Display settings** and can be accessed via the header of a ledger oir schedule |
| Folders in the workspaces could be formatted in the same way as ledgers. | Folders can now only be formatted using bold text and highlighting. |
## Functional Differences
Lucanet is working to provide value parity for the functions on the CFO Solution Platform compared to Lucanet.Financial Client, i.e.:
- Many features that were available in Lucanet.Financial Client are already available in the **Consolidation & Financial Planning** solution on the CFO Solution Platform.
- Some features that were available in Lucanet.Financial Client are **not yet** available on the CFO Solution Platform.
- Some functions that were available in Lucanet.Financial Client will be transferred **to other solutions** on the CFO Solution Platform.
- Some functions that were available in Lucanet.Financial Client will **not** be transferred to the CFO Solution Platform.
Below is an overview of the **functional differences** by **functional area**:
### Basic Functions
Most of the basic functions in Lucanet.Financial Client have been transferred unchanged to the Consolidation & Financial Planning solution or have been modified only slightly:
- Reporting enties, cost centers, and organization elements
- Adjustment levels, data levels, partners, and transaction types
- Currencies and exchange rate tables
- General ledger, subledgers, schedules, and statistical ledgers (including formulas)
- Account properties (e.g., debit/credit shift)
- Importing data into reproting entities (including assignment tables)
- Postings and historical exchange rates
- Period locks (i.e., former audit trails)
- Directory structures (note that no reports, files, or text documents can be created here)
### Consolidation
During integration into the CFO Solution Platform, the consolidation functions were incorporated into the **Consolidation & Financial Planning** solution. As part of this process, **Consolidation 2** underwent a comprehensive overhaul. The following key changes were made:
**‘Consolidated Financial Statements’ Workspace**
The **Consolidated financial statements** workspace has been redesigned to provide greater transparency in the consolidation process and simplify access to individual elements:
'Consolidated financial statements' workspace
**Master Data Administration**
In the **Master Data Administration**, you can now create and download an **organization chart** for the group based on the entered ownership interests – a feature that was previously only available in Lucanet.Financial Client via a separate app.
Additionally, master data administration in the CFO Solution Platform is not provided as an app but is selected as an element in the dimension bar.
**Consolidation Apps**
- The **legacy apps** of Consolidation 2 are **not supported** on the CFO Solution Platform. It is therefore recommended to switch to the corresponding **Next Generation** apps as soon as possible
- All **Consolidation 2 Next Generation apps** that were available on the Lucanet.Financial Client are supported on the CFO Solution Platform.
- The app used to **Adjust and reclassify values in consolidation areas** is available for the first time in a **Next Generation** version on the CFO Solution Platform
- Also the **app for equity elimination** is available for the first time in a **Next Generation** version on the CFO Solution Platform, though currently with **limited functionality** (see [Equity Elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md)). The scope of functionality will be expanded gradually.\
\
**\
\
Recommendation:** If you are using the app for **equity elimination** in Lucanet.Financial Client, you should postpone migrating this app to the CFO Solution Platform until all the functions you require are available. The legacy Consolidation 2 app in Lucanet.Financial Client can continue to be used until then.
### Planning
During integration into the CFO Solution Platform, the planning functions were transferred to the **Consolidation & Financial Planning** solution.
Many of the planning functionalities were transferred **unchanged** from Lucanet.Financial Client to the platform, such as planning data levels, accounting rules, and planning wizards.
However, a significant change in planning is the replacement of **planning forms** with **Sheets**. This means that the following planning forms previously used in Lucanet.Financial Client and the wizards they contain can now be replicated using sheets:
- Standard
- Quantity x price
- Subject to a different figure
- Monthly residual value interest
- Tax calculation
- Balance sheet adjustment
- Forecast wizard
- Seasonality wizard
Sheets can be created on the CFO Solution Platform in the **Import and Journals** workspace for a combination of **planning data level** and **reporting entity** or **consolidation area**. For more information, see [Planning Using Sheets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets.md).
Planning using Sheets
The planning forms previously created in Lucanet.Financial Client are displayed in read-only mode on the CFO Solution Platform.
### Reporting
Many reporting functions from Lucanet.Financial Client have been transferred unchanged to the **Consolidation & Financial Planning** solution on the CFO Solution Platform, including **ad-hoc exports to Excel** and **Lucanet.Excel Reporting.**
The following functions have been incorporated into the platform with minor changes:
**Lucanet.Excel Add-in**
The **Lucanet.Excel Add-in** has been revised and adapted to the technical requirements of the CFO Solution Platform and is now available as the **CFP Add-in for Excel 365**. The new CFP Add-in for Excel 365 is the only tool used to retrieve data from the Consolidation & Financial Planning solution in the Lucanet CFO Solution Platform.
**Access to Exports**
The **Print** function has been renamed **Export** and moved from the toolbar to the header of a ledger or trial balance:
'Export' function
> **Warning:** The **BI integration** available in Lucanet.Financial Client will not be transferred to the CFO Solution Platform.
### Lucanet.Group Report
The **Lucanet.Group Report** module will not be migrated to the Consolidation & Financial Planning solution on the CFO Solution Platform.
Instead, separate solutions— **Data Collection** and **IC Reconciliation**—will soon be available to cover this functional area on the platform in the future.
### Lucanet.E-Bilanz
The **Lucanet.E-Bilanz** module will not be migrated to the Consolidation & Financial Planning solution on the CFO Solution Platform.
Instead, the [Tax Balance](https://support.lucanet.com/en/documentation/income-taxes/tax-balance.md) module from our **Tax Compliance & Reporting** solution is available for this purpose, as it covers this functional area on the platform.
---
---
title: "Getting Started"
description: "Enjoy a seamless user experience and effortless financial management. The new Lucanet Cloud Platform provides a smooth, standardized UX with uniform functions for all the solutions you run on it."
source_url: https://support.lucanet.com/en/documentation/getting-started
language: en
last_updated: 2026-05-30
---
# Getting Started
## The Lucanet CFO Solution Platform: Your Seamless Solution for All Your Financial Needs
Enjoy a seamless user experience and effortless financial management. The new CFO Solution Platform provides a smooth, standardized UX with uniform functions for all the [solutions](https://support.lucanet.com/en/documentation/glossary.md#solution) you run on it.
## First Steps with the Lucanet CFO Solution Platform
Our instructions will help you get started with the Lucanet CFO Solution Platform in next to no time:
- [Opening Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform.md)
- [User Interface of the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/getting-started/user-interface.md)
- [Basic Configuration for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md)
---
---
title: "Non-Production Environments"
description: "Lucanet offers non-production environments for customers with an existing production license. These environments are isolated copies of your production system and allow you to test safely without affecting your live data or configuration.\nTwo types of non-production environments are available for limited solutions:\nTest Update Environment and Sandbox Environment."
source_url: https://support.lucanet.com/en/documentation/getting-started/non-production-environments
language: en
last_updated: 2026-05-28
---
# Non-Production Environments
## Overview
Lucanet offers non-production environments for testing without affecting your live data or configuration. These environments are isolated copies of your production system. Two types are available for limited solutions:
- **Test update environment**: runs the **next** planned software version
- **Sandbox environment**: runs the **same** software version as production
## Test Update Environment
The test update environment allows you to test an upcoming software release before it becomes available in the production system. Lucanet provides this environment ahead of a planned production update.
**This environment is particularly relevant if your business processes are subject to legal or compliance requirements**, where pre-release validation helps ensure continuity before the update takes effect.
At the end of the testing period, your production system is updated to the new software version.
## Sandbox Environment
The sandbox environment reflects your current production version. It can be used for testing configurations, training, or validating workflows before applying changes to production. Unlike the test update environment, it is not tied to a release cycle and remains available on an ongoing basis.
## Getting Access
Non-production environments can be purchased as an add-on to your existing license. For information on availability and pricing, please contact your account manager.
Once your environment is provisioned, the designated initial user receives an e-mail with the URL to the environment and login credentials. Note that each test environment is provided with its **own URL** and **separate credentials**, which differ from those used for the production system.
The initial user can activate other users, who then receive an e-mail invitation with their login details.
---
---
title: "Opening CFO Solution Platform"
description: "The Lucanet CFO Solution Platform is displayed in your browser. You can open it by entering the corresponding URL. There are several different ways of opening the Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform
language: en
last_updated: 2026-08-31
---
# Opening the Lucanet CFO Solution Platform
## Overview
The **Lucanet CFO Solution Platform** is displayed in your browser. You can open it by entering the corresponding **URL**. There are several different ways of opening the Lucanet CFO Solution Platform.
## Getting the URL for the Lucanet CFO Solution Platform
### From the Lucanet.Financial Client
Click the menu command **Start Lucanet CFO Solution Platform** in the menu bar of Lucanet.Financial Client.
Menu command 'Start Lucanet CFO Solution Platform' in Lucanet.Financial Client
> **Note:** If you open the Lucanet CFO Solution Platform from Lucanet **.Financial Client**, you do not need to log in to the Lucanet CFO Solution Platform again.
### With the Provided URL
To open the Lucanet CFO Solution Platform, you will initially receive an e-mail with a link to the Lucanet CFO Solution Platform. Click on the link and log in with your SSO or your Lucanet credentials.
> **Note:** To make sure the invitation e-mail and other platform e-mails (for example, password reset or expiration notices) are delivered reliably, ensure that your spam filter or e-mail gateway does not block messages from **`no-reply@platform.lucanet.cloud`**. These e-mails are sent via the Amazon e-mail service Amazon SES (`amazonses.com`).
## Log in to the Lucanet CFO Solution Platform
Login dialog of the Lucanet CFO Solution Platform
Depending on whether external authentication is activated for you or not, you have the following options for logging in to the Lucanet CFO Solution Platform:
If external authentication is activated for you:
1. Click **Log in with SSO**.
2. Log in with the access data of your identity provider.
If no external authentication is activated for you:
1. Enter the following in the login dialog:
- Your **User name or e-mail address**
- Your **Password**
2. Click **Log in**.
## Multi-Factor Authentication with an Authenticator App
If your administrator has activated multi-factor authentication (MFA) for your user account, you need your user name, your password, and a six-digit code from an authenticator app to log in.
> **Note:** Multi-factor authentication applies only if you log in with a user name and password. If external authentication is activated for you, you log in through your identity provider, and multi-factor authentication is handled there.
### Setting Up the Authenticator App
The first time you log in after your administrator has activated multi-factor authentication, you must set up an authenticator app. The page is displayed as follows, for example:
Message that multi-factor authentication is required
Click **Set up now**. The setup page is displayed as follows, for example:
Page for setting up the authenticator app
To set up the authenticator app:
1. Install an authenticator app on your mobile device, for example Google Authenticator, Microsoft Authenticator, or Authy.
2. Open the authenticator app, add an account, and scan the QR code.
If you cannot scan the QR code, enter the setup key below the QR code manually in the authenticator app.
3. Click **I have scanned it. Continue.**
4. Enter the six-digit code from your authenticator app, and then click **Verify and complete setup**.
The page for entering the verification code is displayed as follows, for example:
Page for verifying the authenticator app
> **Note:** Only one authenticator app can be linked to your user account.
### Logging In with a Code
Once you have set up the authenticator app, you must enter a code every time you log in with your user name and password. The page is displayed as follows, for example:
Page for entering the authentication code
To complete the login, enter the six-digit code from your authenticator app, and then click **Verify**.
> **Note:** The code in the authenticator app changes every 30 seconds. If the code has expired, open the authenticator app again and enter the new code.
> **Warning:** If you no longer have access to your authenticator app, contact your administrator. Your administrator can reset the multi-factor authentication for your user account so that you can set up an authenticator app again. For more information, see [Creating and Editing Users for the Lucanet CFO Solution Platform | Resetting TOTP MFA](https://support.lucanet.com/en/documentation/administration/user-management/users.md#resetting-totp-mfa).
## Password Policy
To ensure the security of your account, passwords must meet the following requirements:
**Complexity Requirements:**
- Minimum of **14 characters** in length
- Must contain characters from **at least three (3)** of the following four categories:
- English uppercase letters (A-Z)
- English lowercase letters (a-z)
- Numbers (0-9)
- Special characters (e.g., ! @ # $ % ^ & \*)
**Password Lifecycle and Security Policies:**
- **Password expiration:** Passwords expire after **90 days** for security reasons. You will be prompted to change your password when it expires.
- **Password history:** Your new password cannot be the same as any of your **previous 5 passwords**.
- **Change frequency limit:** You can change your password a maximum of **twice per day**.
**Password Expiration Notifications:**
To help you maintain uninterrupted access to your account, you will receive advance notifications to change your password:
- **Email notifications** will be sent **30, 14, 7, and 1 day(s)** before your password expires.
- **In-app notifications** will appear in the platform at the same intervals.
We recommend changing your password before it expires to avoid any service interruption.
**Account Security Controls:**
Automated security measures protect your account from unauthorized access: after **5 consecutive incorrect login attempts**, your account is automatically locked for **30 minutes**.
## Forgot Your Password
If you have forgotten your password, you can click **Forgot your password** in the login dialog. Enter your user name or e-mail address to have an e-mail sent to you to reset your password.
> **Warning:** The **Forgot your password** function is not available if external authentication is used.
---
---
title: "User Interface"
description: "The Lucanet CFO Solution Platform is the user interface for end users and Lucanet administrators in the web view. This page contains information about the structure of the user interface and the most important elements."
source_url: https://support.lucanet.com/en/documentation/getting-started/user-interface
language: en
last_updated: 2026-09-08
---
# User Interface of the Lucanet CFO Solution Platform
## Overview
The **Lucanet CFO Solution Platform** is the user interface for end users and Lucanet administrators in the web view. This page contains information about the structure of the user interface and the most important elements.
## Structure of the User Interface
After you log in, the homepage of the Lucanet CFO Solution Platform is displayed next to the **main menu**.
If you open any solution or the **Administration** section, the user interface will be displayed in three areas: **main menu**, **menu**, and **detail view**. For example, the **Consolidation & Financial Planning** solution is displayed as follows:
User interface of the Lucanet CFO Solution Platform
### Main Menu
The following elements are available in the main menu:
| Element | Description |
|---|---|
| **Home** | Returns you to the homepage of the Lucanet CFO Solution Platform. |
| **[Notifications](https://support.lucanet.com/en/documentation/global-functions/notifications.md)** | Centralized interface for managing notifications from platform features and your licensed solutions. Unread notifications are indicated by a number behind the menu item. |
| **[Task Center](https://support.lucanet.com/en/documentation/global-functions/task-center.md)** | Provides a unified interface for managing tasks across the Lucanet CFO Solution Platform. You can easily create, organize, and monitor tasks in one place here. |
| **Your Solutions** | Contains the overview of all the solutions available to you within the scope of your license. |
| **Discover More Solutions** | Contains all unlicensed solutions of the Lucanet CFO Solution Platform. Clicking on a solution opens the corresponding demo page. For more information, see [Discover More Solutions](#discover-more-solutions). |
| **[Lume](https://support.lucanet.com/en/documentation/lume.md)** | (If available) The conversational layer of the Lucanet CFO Solution Platform: ask questions in plain language and Lume provides instant answers or routes your request to the right workflow agents behind the scenes. It is the starting point for orchestrating everything the Intelligence Core of Lucanet provides. |
| **[Data Hub](https://support.lucanet.com/en/documentation/data-hub.md)** | (If available) The central data-integration function of the Lucanet CFO Solution Platform: create connections to external source systems, define which data to import, and run and track the imports. |
| **[Administration](https://support.lucanet.com/en/documentation/administration.md)** | Serves as the central hub for user management and platform administration. Is displayed only for users with access to the **Administration** module. |
| **Support and Customer Portal** | Provides access to Support, the Customer Portal, and About Lucanet. For more information, see [Support and Customer Portal](#support-and-customer-portal). |
| **Knowledge Base** | Opens the Knowledge Base with the documentation and guides for the Lucanet CFO Solution Platform and its solutions. |
| **User Account** | Displays your avatar, name, and selected UI language at the bottom of the main menu, and opens the account menu. For more information, see [User Account](#user-account). |
#### Discover More Solutions
Contains all unlicensed solutions of the Lucanet CFO Solution Platform. Clicking on a solution opens the corresponding demo page with options to watch an interactive demo, access documentation, contact experts, or view resources:
Sample demo page for xP&A displayed from the 'Discover more solutions' section
When you click **Watch a demo**, a consent dialog is displayed requesting your permission to redirect to the external Consensus platform (operated by Consensus, Inc, South Jordan, UT, USA). The dialog provides information about data processing in accordance with Art. 6 para. 1 lit. a GDPR and includes a link to the [Consensus Privacy Policy](https://consensus.app/home/privacy-policy/).
To proceed to the demo, activate the consent check box and click **Continue**. To decline, click **Decline** or close the dialog. Your consent is stored and you will not see the dialog again unless you revoke your consent via **Account menu | My Profile | Manage Consent**.
For more information, see [Managing Consents for External Services](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#managing-consents-for-external-services).
##### Contacting a Sales Expert
On each demo page, you can click the **Contact an expert** button to request assistance or more information about unlicensed solutions. A contact form is displayed as follows, for example:
'Contact a Sales Expert' form
Your contact information is automatically filled from your profile. After submitting your request, one of our sales representatives will contact you shortly to discuss your requirements.
#### Support and Customer Portal
Provides access to the following options:
- **Support**
- **Customer Portal**
- **About Lucanet** \- displays current product versions; administrators can additionally download [SBOM](https://support.lucanet.com/en/documentation/glossary.md#software-bill-of-materials-sbom) files.
For more information, see [Viewing Product Versions](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#viewing-product-versions) and [Accessing and Downloading SBOMs](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#accessing-and-downloading-sboms).
#### User Account
Displays your avatar, name, and selected UI language at the bottom of the main menu. Click anywhere in this area to open the **Account menu**, as displayed in the following example:
User account area and the account menu
The following options are available in the account menu:
| Option | Description |
|---|---|
| **User info (avatar, name, e-mail address)** | Displays your avatar, first name, last name, and e-mail address. Click this area to open your profile, where you can view your user name and e-mail address and manage your consents for external services. For more information, see [Viewing Your User Profile](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#viewing-your-user-profile) and [Managing Consents for External Services](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#managing-consents-for-external-services). |
| **Language** | Allows you to select your preferred user interface language. For more information, see [Changing the User Interface Language](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#changing-the-user-interface-language). |
| **Formatting preferences** | Allows you to configure your preferred date and number format. For more information, see [Configuring the Date and Number Format](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#configuring-the-date-and-number-format). |
| **Change password** | Allows you to change your login password. For more information, see [Changing Your Password](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#changing-your-password). |
| **Log out** | Logs you out of the Lucanet CFO Solution Platform. |
### Menu
The **Menu** provides an overview of the selected licensed solution or the **Administration** section. What is displayed in the menu depends on which solution or section has been chosen. For example, the menu can display:
- Licensed and unlicensed modules within the selected solution
- Functional areas and workspaces of the selected solution
- Other configuration options
### Detail View
The detail view displays specific information and functions related to the currently selected element in the menu.
> **Note:** For more information on the user interface of each solution, see:
>
> - [Lucanet xP&A User Interface](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/user-interface-xPA.md)
> - [User Interface of Lucanet Consolidation & Financial Planning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/user-interface-cfp.md)
> - [User Roles and User Interface in ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting/user-roles-esgrep.md)
> - [Lucanet Disclosure Management User Interface](https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt.md)
> - [User Interface of the Lucanet XBRL Tagger](https://support.lucanet.com/en/documentation/xbrl-tagger/user-interface-xbrltagger.md)
> - [User Interface of Data Collection](https://support.lucanet.com/en/documentation/data-collection/user-interface-dc.md)
## Changing the Display of the Menus
The following options are available to change the display of the main menu or the menu:
| Element | Description |
|---|---|
| Main menu | • Click the arrow right icon or the arrow left icon to expand or collapse the main menu. • Drag and drop the dividing line between the main menu and the menu to hide or show the element names in the main menu. |
| Menu | • Click the double chevron right icon or the double chevron left icon to show or hide the menu. • Drag and drop the dividing line between the menu and the detail view to resize the width of the menu. |
---
## Global Functions
Global functions in the Lucanet CFO Solution Platform can be used independently of individual solutions. These functions are available in the main menu and support you with cross-platform tasks.
---
title: "Dashboard Widgets"
description: "Overview of the available widget types (KPI, bar, line, static bar, waterfall, pie, listogram, and text box) and how to add and configure widgets."
source_url: https://support.lucanet.com/en/documentation/global-functions/dashboards/widgets
language: en
last_updated: 2026-10-07
---
# Dashboard Widgets
## Overview
Widgets are the building blocks of a dashboard. You can position and resize each widget on the dashboard grid. Most widget types visualize data from a single data source; the **Text box** widget instead holds free-form text. This page describes the available widget types and how to add, configure, and edit a widget.
## Widget Types
The following widget types are available:
| Widget type | Description |
|-------------|-------------|
| KPI | Displays a single key figure as a card. |
| Bar | Displays values over time as a bar chart. |
| Line | Displays values over time as a line chart. |
| Static bar | Displays values compared across categories as a bar chart. |
| Waterfall | Displays the effect of a series of positive and negative changes on an initial value. |
| Pie | Displays values as proportions of a whole. |
| Listogram | Displays values as a ranked list. |
| Text box | Displays free-form text, such as notes or commentary. |
## Adding a Widget
To add a widget to a dashboard:
1. Open the dashboard and click **Add widget**. The list of widget types is displayed as follows, for example:
List of widget types
2. Select a widget type. The **New Widget** dialog is displayed as follows, for example:
'New Widget' dialog
3. Select the **Chart type** and enter a **Title**. The title can have up to 100 characters.
4. Click **Continue**.
5. Configure the widget on the **General**, **Data**, and **Appearance** tabs (see below). A live preview on the left updates as you adjust the configuration.
6. Click **Add widget** to place the widget on the dashboard.
The **New Widget** dialog organizes the configuration into three tabs.
### General
The **General** tab contains the widget's **Title** and an optional **Description**. For a **Text box** widget, the **General** tab instead contains a **Headline** and a **Text** field. For each, you can set the **font size** (**S**, **M**, or **L**) and **bold formatting**.
### Data
The **Data** tab defines which data a widget displays. It is available for all widget types except **Text box**. For a widget with the source **CFP**, you can configure the following:
- **Ledger**: the ledger from which the values are taken.
- **Element**: the account, item, or formula whose values are displayed.
- **Transaction currency**, **Partner**, **Adjustment level**, and **Data level**: the Lucanet dimensions applied to the values. For more information, see [Dimensions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions.md).
The available options differ by widget type:
- **KPI** additionally provides a **Transaction type** option.
- **Pie** and **Listogram** provide a **Break down by** option (**Accounts/items** or **Organization elements**).
- **Waterfall** does not use a single **Element**. Instead, it provides a **Waterfall flow** in which you select a **Start point** and an **End point** and add up to 18 elements in between that make up the change from the start value to the end value. For example, a waterfall can show the path from revenue as the start point to net income as the end point, with items such as cost of goods sold, operating expenses, and taxes as the contributions in between.
> **Note:** - The **Time period**, **Organization element**, and **Currency** are determined by the dashboard filters, not set per widget. For more information, see [Managing Dashboards](https://support.lucanet.com/en/documentation/global-functions/dashboards/managing-dashboards.md).
> - The **Source** field defines the widget's data source. It cannot be changed while creating or editing the widget.
#### Comparing Data Levels
For the **KPI**, **Bar**, **Line**, **Static bar**, and **Listogram** widget types, you can select up to three data levels in the **Data level** option and compare them in a single widget, for example one actual data level and two planning data levels.
The **Data level** option is displayed as follows, for example:
'Data level' option with three selected data levels
The following applies to all selected data levels:
- All other options of the widget and all dashboard filters apply to every data level. The data level is the only dimension in which the compared values differ.
- The period of the widget covers the periods of all selected data levels.
How the comparison is displayed depends on the widget type:
- **KPI**: The data level that is selected first is displayed as the main value. Each further data level is displayed below the main value with its own value and the difference from the main value, as an absolute value and as a percentage.
- **Bar**, **Line**, **Static bar**, and **Listogram**: Each data level is displayed as a separate series in a color of the selected color palette. The legend identifies each series by the name of the data level.
A **KPI** widget with three data levels is displayed as follows, for example:
'KPI' widget with three data levels
> **Note:** At least one data level must be selected. For the **Pie** and **Waterfall** widget types, the comparison is not available.
### Appearance
The **Appearance** tab contains the **Colors** option, where you choose a color palette for the widget. The widget cycles through the colors if there are more data points than colors. The **Appearance** tab is not available for the **KPI** and **Text box** widgets.
## Editing a Widget
Each widget has a three-dot menu the three dot menu icon with **Edit** and **Delete** options. **Edit** reopens the widget configuration; **Delete** removes the widget from the dashboard and **cannot be undone**.
Only the dashboard **owner** can edit or delete widgets. Viewers and administrators see the configured widgets only, without being able to edit or delete them.
---
---
title: "Dashboards"
description: "The Dashboards global function provides a dedicated space in the Lucanet CFO Solution Platform where you can build, share, and analyze interactive dashboards."
source_url: https://support.lucanet.com/en/documentation/global-functions/dashboards
language: en
last_updated: 2026-10-07
---
# Dashboards
## Overview
The **Dashboards** global function provides a dedicated space in the Lucanet CFO Solution Platform where you can build, share, and analyze interactive dashboards. You can combine widgets such as KPI cards and charts to visualize your financial data and share dashboards with other users for collaborative analysis.
> **Note:** - Currently, dashboards use **Consolidation & Financial Planning (CFP)** data as their data source.
> - Using **Dashboards** requires a **Consolidation & Financial Planning** license. Without this license, the function is not displayed in the main menu.
## Navigation
**Dashboards** can be found in the **main menu** of the Lucanet CFO Solution Platform. The dashboards you have access to are displayed as follows, for example:
Dashboards start page in card view
## Viewing Dashboards
On the Dashboards start page, you can open, create, and manage your dashboards.
### Tabs
The following tabs are available:
| Tab | Description |
|-----|-------------|
| All dashboards | Displays every dashboard you have access to, including your own and dashboards shared with you. |
| Your dashboards | Displays only the dashboards you own. |
| Shared with you | Displays only the dashboards that other users have shared with you. |
### Display Options
In the top-right corner, the following display options are available:
| Option | Description |
|--------|-------------|
| Cards / Table | Switches between a card view and a table view. |
| Sort | Sorts the dashboards by **Last modified**, **Creation date (newest first)**, or **Creation date (oldest first)**. |
### Card View and Table View
Your dashboards are displayed as a card view or a table view. Dashboards that you own are marked with an the owner icon.
Each dashboard provides a three-dot menu the three dot menu icon with quick actions:
- For dashboards you own: **Duplicate**, **Share**, and **Delete**
- For dashboards shared with you: **Duplicate**
For details, see [Managing Dashboards](https://support.lucanet.com/en/documentation/global-functions/dashboards/managing-dashboards.md).
Both views display the same information for each dashboard:
- **Name**: the name of the dashboard
- **Created by**: the user who created the dashboard
- **Last modified by**: the user who last modified the dashboard
- **Last modified on**: the date the dashboard was last modified
- **Shared with**: the users the dashboard is shared with, or **Private** if it is not shared
In the table view, this information is displayed as columns; in the card view, as one card per dashboard.
The table view is displayed as follows, for example:
Dashboards start page in table view
## Working With Dashboards
When you open a dashboard, you can add widgets, apply dashboard filters, and share, export, or edit the dashboard. An open dashboard is displayed as follows, for example:
Open dashboard with several widgets
The following pages describe these tasks in detail:
- [**Managing Dashboards**](https://support.lucanet.com/en/documentation/global-functions/dashboards/managing-dashboards.md): create, duplicate, share, export, and filter dashboards, and edit their details
- [**Dashboard Widgets**](https://support.lucanet.com/en/documentation/global-functions/dashboards/widgets.md): add and configure the widgets that visualize your data
---
---
title: "Global Functions"
description: "Global functions in the Lucanet CFO Solution Platform can be used independently of individual solutions. These functions are available in the main menu and support you with cross-platform tasks."
source_url: https://support.lucanet.com/en/documentation/global-functions
language: en
last_updated: 2026-10-07
---
# Global Functions
Global functions in the Lucanet CFO Solution Platform can be used independently of individual solutions. These functions are available in the main menu and support you with cross-platform tasks.
The following global functions are currently available:
- [**Notifications**](https://support.lucanet.com/en/documentation/global-functions/notifications.md): Centralized interface for managing notifications from the Task Center and Administration
- [**Task Center**](https://support.lucanet.com/en/documentation/global-functions/task-center.md): Central management and tracking of all tasks in the CFO Solution Platform
- [**Dashboards**](https://support.lucanet.com/en/documentation/global-functions/dashboards.md): Interactive dashboards that visualize your financial data using widgets
Global functions in the main menu
[Request demo](https://www.lucanet.com/en/request-demo/)
---
---
title: "Managing Dashboards"
description: "Creating, duplicating, sharing, exporting, and editing dashboards, and managing the related access roles (owner and viewer)."
source_url: https://support.lucanet.com/en/documentation/global-functions/dashboards/managing-dashboards
language: en
last_updated: 2026-10-07
---
# Managing Dashboards
## Overview
You can create, duplicate, share, export, and delete dashboards, edit their details, and apply dashboard filters. This page describes how to manage dashboards. For details on adding and configuring widgets, see [Dashboard Widgets](https://support.lucanet.com/en/documentation/global-functions/dashboards/widgets.md).
## Creating a Dashboard
To create a dashboard:
1. On the Dashboards start page, click **New**. The **New Dashboard** dialog is displayed as follows, for example:
'New Dashboard' dialog
2. Enter a **Name** for the dashboard. The name is required.
3. Enter a **Description**. The description is required and can have up to 500 characters.
4. Click **Create**. The dashboard is created and opened so that you can add widgets.
## Applying Dashboard Filters
When a dashboard is open, you can use the dashboard filters to control the data displayed across all widgets at once. The following filters are available:
| Filter | Description |
|--------|-------------|
| Time period | Defines the reporting period for the dashboard. You can display the data split by month, quarter, or year. |
| Organization element | Defines the organization element whose data is displayed, for example an organization group. |
| Currency | Defines the display currency for the dashboard values. |
> **Note:** The **Organization element** and **Currency** drop-down lists display only the values you are permitted to see in Consolidation & Financial Planning (CFP). For example, if you only have access to one organization element or one currency in CFP, only that value is available here.
## Access and Permissions
A dashboard has two access roles:
| Role | Description |
|------|-------------|
| Owner | The user who created the dashboard. The owner can configure, edit, share, duplicate, export, and delete the dashboard. There is one owner per dashboard. |
| Viewer | A user the dashboard has been shared with. A viewer has read-only access: a viewer can view and duplicate the dashboard, but cannot change, share, or delete it. A dashboard can have multiple viewers. |
Users with the **Administrator** role have access to all dashboards, including dashboards created by other users and dashboards that have not been shared with them. Administrators can open, edit, share, export, and delete any dashboard. If a dashboard loses its owner, for example because the owner's account is deleted, an administrator is notified and can take over managing the dashboard. The dashboard remains available to its viewers.
> **Note:** If you do not have permission to view a widget's underlying data, either as a viewer or as an administrator, the widget is displayed blurred, with a message to request the required permissions.
## Duplicating a Dashboard
To create a copy of a dashboard, select **Duplicate** from the dashboard's three-dot menu the three dot menu icon on the Dashboards start page, or open the dashboard and click **Duplicate** in the toolbar. A copy of the dashboard is created, including its widgets and configuration.
If the copy contains widgets whose underlying data you do not have permission to view, those widgets remain blurred, and the only available action is **Delete**, so you can remove them and clean up the dashboard.
## Sharing a Dashboard
When you share a dashboard, the selected users become viewers with read-only access.
To share a dashboard:
1. Select **Share** from the dashboard's three-dot menu the three dot menu icon on the Dashboards start page, or open the dashboard and click **Share** in the toolbar. The **Share** dialog is displayed as follows, for example:
'Share' dialog
2. In the **Select user** field, select the users you want to share the dashboard with.
3. Click **Save changes**. The selected users receive read-only access and are notified that the dashboard has been shared with them.
> **Note:** When a dashboard is shared with you, you receive a notification by e-mail and in the [**Notifications**](https://support.lucanet.com/en/documentation/global-functions/notifications.md) section. You can then duplicate the dashboard but not change it. If you duplicate a shared dashboard, you become the owner of the copy and can choose whether the copy stays shared with the original users or becomes private.
To stop sharing a dashboard, open the **Share** dialog. To remove access for a single user, click the delete icon next to that user. To remove all sharing at once, select **Make private**. Click **Save changes** to apply the change.
## Exporting a Dashboard
You can export a dashboard as a file. To do so, open the dashboard, click **Export** in the toolbar, and select one of the following options:
- **Export as PDF**
- **Export as PowerPoint**
## Editing Dashboard Details
To view a dashboard's details or edit the name and description, open the dashboard and click **Settings** in the toolbar. The **Settings** dialog displays the following information:
- **Created by** and **Created at**
- **Last modified by** and **Last modified at**
- **Owner**
- **Shared with**
- **Name** and **Description**
Edit the **Name** or **Description** as needed and click **Save changes**.
## Arranging Widgets
On an open dashboard, you can arrange the widgets on the dashboard grid. Drag a widget to move it to a different position, and drag the edges of a widget to resize it.
## Deleting a Dashboard
To delete a dashboard, select **Delete** from its three-dot menu the three dot menu icon on the Dashboards start page. Only the dashboard owner and administrators can delete a dashboard. Viewers cannot delete a dashboard that has been shared with them.
---
---
title: "Notifications"
description: "The Notifications section provides a centralized interface for managing notifications from your licensed solutions as well as global and administrative functions, i.e., Task Center and Administration. You can view and manage all your notifications in one convenient location, ensuring you never miss important updates about your work."
source_url: https://support.lucanet.com/en/documentation/global-functions/notifications
language: en
last_updated: 2026-05-01
---
# Notifications
## Overview
The **Notifications** section provides a centralized interface for managing notifications from your licensed solutions as well as global and administrative functions, i.e.:
- [Task Center](https://support.lucanet.com/en/documentation/global-functions/task-center.md)
- [Administration](https://support.lucanet.com/en/documentation/administration.md)
You can view and manage all your notifications in one convenient location, ensuring you never miss important updates about your work.
## Navigation
The **Notifications** section can be found in the main menu of the Lucanet CFO Solution Platform and is displayed as follows, for example:
'Notifications' section in the main menu
When you have unread notifications, a numbered badge appears to indicate the number of unread notifications.
## Viewing Notifications
The **Notifications** section displays your notifications in a centralized list. You only see notifications from the areas you have access to. A detailed list of which events can trigger notifications can be found in the [**Notification Settings**](https://support.lucanet.com/en/documentation/global-functions/notifications/.md#configuring-notification-preferences) dialog.
Unread notifications are marked with a purple dot in the top-right corner.
For longer notifications, the title and message are displayed in a shortened form. Click **Show more** to display the full content, and **Show less** to collapse it again.
## Managing Notifications
The following options are available for managing your notifications:
#### Filter notifications
Filter notifications by source. The available filter options depend on the solutions and modules you have access to.
Notification filter
#### Mark as read
Mark individual notifications as read.
#### Mark as unread
Mark individual notifications as unread.
#### Mark all as read
Mark all notifications as read.
#### Mark all as unread
Mark all notifications as unread.
#### Navigate to source
Click the notification to **navigate to the section** where it was generated.
## Configuring Notification Preferences
To configure your notification preferences:
1. Open the **Notifications** section and click the settings white icon in the top-right corner. The **Notifications Settings** dialog will be displayed as follows, for example:
'Notifications Settings' dialog
2. Expand each section to view detailed events for which you can set up notifications.
3. For each event, choose to receive notifications via **E-mail** and/or **In App**.
4. Click **Save** to apply your settings.
---
---
title: "Task Center"
description: "The Task Center provides a unified interface for managing tasks across the Lucanet CFO Solution Platform and is accessible directly from the main menu. Each task is assigned a unique task identifier (for example, T1234) for easy reference and tracking."
source_url: https://support.lucanet.com/en/documentation/global-functions/task-center
language: en
last_updated: 2026-05-01
---
# Task Center
## Overview
The **Task Center** provides a unified interface for managing tasks across the Lucanet CFO Solution Platform and is accessible directly from the main menu.
Each task is assigned a unique task identifier (for example, T1234) for easy reference and tracking.
## Navigation
The **Task Center** can be found in the **main menu** of the Lucanet CFO Solution Platform and is displayed as follows, for example:
User interface of the Task Center
## Viewing Tasks
In the Task Center, tasks are organized into two workspaces:
| Workspace | Description |
|---------|---------|
| Active tasks | Displays all tasks with status **To do** or **In progress**. |
| Closed tasks | Displays all tasks with status **Done** or **Canceled**. |
For each task, the following information is displayed:
Task Information displayed on the Task Center dashboard
- **Priority**: Labelled with the respective priority icon (see [Creating a Task](https://support.lucanet.com/en/documentation/global-functions/task-center/.md#priority) for details)
- **Status**: Labelled with the respective status icon (see [Creating a Task](https://support.lucanet.com/en/documentation/global-functions/task-center/.md#status) for details)
- **Title**: The title of the task
- **Link**: Displayed if a link is attached to the task
- **Tags**: Displayed if tags have been added to the task
- **Due date**: The due date for the task
- **Assignee**: Displayed as an icon. When you hover over the icon, the user’s name is displayed.
## Filtering Tasks
You can filter the task list using the **Filters** button:
Filter options in the Task Center
The following filter options are available:
- **Assigned to me**: Displays only tasks that are assigned to you
- **Created by me**: Displays only tasks that you have created
- **Status**: Filter by task status
- **Priority**: Filter by priority level
- **Privacy**: Filter by public or private tasks
- **Tag**: Filter by specific tags
- **Assignee**: Filter by assigned user
- **Created by**: Filter by the user who created the task
## Creating a Task
To create a task, click the **\+ New task** button. The dialog for creating a new task is displayed as follows:
Dialog for creating a task
The following options are available:
#### Task title
Name or brief description of the task (required, maximum 40 characters)
#### Description
Additional details or context for the task
#### Assignee
Responsible user for the task. The default assignee is the task creator.
#### Status
The current status of the task. The following options are available:
Task status options
#### Priority
The priority of the task. The following options are available:
Priority options
#### Due date
The due date for the task, which can be selected from a calendar window
#### Add tag
Tags for categorizing the task. Currently, licensed solutions are available for selection as tags, and multiple tags can be selected.
#### Private
Toggle to set the task as **private** or **public**(default: public)
- **Public tasks** are visible and editable by all users.
- **Private tasks** are visible and editable only by the task creator, the assigned user, and platform administrators.
You can also add file attachments and links when creating a task by switching to the **File attachments** or **Links** tab. For details on adding and managing attachments and links, see [Attachments](#attachments).
Click **Create task** to save the task. The task will be displayed on the dashboard, and the assignee will receive an e-mail notification.
## Managing a Task
To manage a task, click the desired task on the dashboard. The task details page will be displayed as follows, for example:
Options for managing a task
The following options are available on the task details page:
#### Edit task
Click the relevant area within the task details to edit the task. Editing works in the same way as when creating a task.
> **Note:** When a task is edited, the reporter and assignee may be notified based on who made the change and their individual notification preferences configured in the **Notifications** section (see [Configuring Notification Preferences](https://support.lucanet.com/en/documentation/global-functions/notifications.md#configuring-notification-preferences)).
#### View task activity
The **Activity** section provides a complete history of the task, including all actions performed, changes made, related users, timestamps, and other relevant task events.
#### Copy task link
Use the **Copy task link** option in the context menu of the three dot icon next to the task identifier to copy the task link to your clipboard.
#### Delete task
Use the **Delete task** option in the context menu of the three dot icon next to the task identifier to delete the task.
> **Warning:** Only the task creator and platform administrators can delete tasks.
### Attachments
The **Attachments** area on the task details page shows all files and links associated with the task and is displayed as follows, for example:
'Attachments' area on the task details page
**File Attachments**
You can attach files to tasks to provide additional context or documentation. Files can be added when creating a new task (via the **File attachments** tab) or added later on the task details page.
You can upload up to 10 files per upload session. Supported file formats: .pdf, .jpg, .png, .docx, .xlsx.
**To add file attachments to an existing task:**
1. Click the **+** button in the **Attachments** area.
2. Select the **File attachments** tab.
3. Drag and drop files into the designated area, or click **choose a file** to select files from your device.
4. Click **Save**.
Click the three dot icon next to the file and select **Download** or **Remove** to download or remove file attachments.
**Links**
You can add multiple URL links to tasks to reference external resources or related content. Links can be added when creating a new task (via the **Links** tab) or added later on the task details page.
**To add links to an existing task:**
1. Click the **+** button in the **Attachments** area.
2. Select the **Links** tab.
3. Enter the URL.
4. Click **Add link** or press **Enter** to save the link. If necessary, add more links.
5. Click **Save** to save the link(s).
**To manage links:**
Click the three dot icon next to a link and select one of the following options:
- **Open**: Opens the link in a new browser tab
- **Edit**: Allows you to modify the URL
- **Remove**: Deletes the link from the task
---
## Lucanet Lume
Lucanet Lume is the conversational layer of the Lucanet CFO Solution Platform: ask questions in plain language and Lume provides instant answers or routes your request to the right workflow agents behind the scenes. It is the starting point for orchestrating everything the Intelligence Core of Lucanet provides.
---
title: "Agents"
source_url: https://support.lucanet.com/en/documentation/lume/agents
language: en
last_updated: 2026-05-01
---
# Agents
## Overview
Agents are specialized intelligent assistants within Lume, each purpose-built for a specific workflow in the Lucanet CFO Solution Platform. Unlike the general Lume chat, agents guide you step by step through complex tasks — such as building financial models — using plain-language instructions.
## Accessing an Agent
To access an agent in Lume:
1. Click **Lume** in the main menu.
2. Open the **Agents** panel from the Lume sidebar. The panel may take a few seconds to load.
The list of available agents is displayed.
Agents panel in Lume
3. Select the agent you want to use.
The agent opens in the chat window, ready to guide you step by step. Suggested prompts help you get started.
Modeler Agent opened in Lume
> **Note:** You can use an agent either directly in Lume or in the solution it is built for. When you use an agent in Lume, it provides direct links to guide you to the relevant results in the solution.
## Lucanet's Agents Family
Our Agents family is actively growing. More and more agents for your most important workflows will be available in Lume shortly — so you can get more done, faster.
### Available Today
The following agents are already available:
| Agent | Description |
|---------|---------|
| **ESG Emission Agent** | Automates mapping of consumption data to GHG emission factors and scopes, generating a full carbon footprint significantly faster than manual creation. For more information on using the agent, see [Import of Footprints from MS Excel Using ESG Emission Agent](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/fill-out-emission-module.md#import-of-footprints-from-ms-excel-using-esg-emission-agent). |
| **Modeler Agent** | Lets xP&A users build and modify financial models through natural language, drastically reducing the time needed for model creation. For more information on using the agent, see [Creating a New Model Using the Modeler Agent](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md#creating-a-new-model-using-the-modeler-agent). |
| **Tagger Agent** *Available in XBRL Tagger only* | Automates IFRS taxonomy tagging of financial reports (Word and PDF), cutting the process from days to hours. For more information, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md). |
| **Analyst Agent** | Ask questions about your Consolidation & Financial Planning and xP&A data, explore trends across periods and entities, and generate charts — all in natural language. For more information, see [Analyst Agent](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent.md). |
### Coming Soon
Our Agents family is actively growing. Purpose-built intelligent assistants for your most important workflows will be available in Lume shortly — so you can get more done, faster.
| Agent | Description |
|---------|---------|
| **Close Agent** | Orchestrates the month-end close — auto-imports data, proposes account assignments, detects anomalies and drafts correction emails to local accountants. |
| **Report Agent** | Accelerates annual-report authoring with continuous terminology consistency checks, narrative generation and disclosure suggestions. |
---
---
title: "Analyst Agent"
source_url: https://support.lucanet.com/en/documentation/lume/agents/analyst-agent
language: en
last_updated: 2026-09-16
---
# Analyst Agent in Lume
## Overview
The **Lucanet Analyst Agent** lets you ask questions about your **Consolidation & Financial Planning (CFP)** and **xP&A (Extended Planning & Analysis)** data in plain language and get back a narrative answer, a chart, or a downloadable file — instead of building a report by hand.
The Analyst Agent is aimed at FP&A and Controlling professionals who want a faster path from a question to a defensible answer — whether that is a recurring monthly variance question, an ad-hoc request from a stakeholder, or a chart for a board deck.
> **Note:** - The Analyst Agent can only access data you have permission to see.
>
> - The Analyst Agent only reads your data; it never writes back to CFP or xP&A. Any file it creates — for example a PowerPoint or Excel file — is a download only and has no effect on your CFP or xP&A data.
## Opening the Analyst Agent
If you ask a question elsewhere in Lume that the Analyst Agent should answer, Lume can open the Analyst Agent for you automatically.
To open the Analyst Agent directly in Lume:
1. Click **Lume** in the main menu.
2. Open the **Agents** panel from the Lume sidebar. The panel may take a few seconds to load.
The list of available agents is displayed.
3. Select **the Analyst Agent**.
The Analyst Agent opens in the chat window, ready to guide you. Suggested prompts help you get started.
The Analyst Agent opened in Lume
## What You Can Do with the Analyst Agent
With the Analyst Agent open, you can do the following:
- You can ask a question in natural language about your CFP or xP&A data, scoped to a specific area and referencing exact elements with "/". You can also attach your own file, such as a list of production quantities or vendor information, for the Analyst Agent to combine with your CFP or xP&A data. To learn how to phrase and scope a question and use your own files as context, see [Asking Analyst Agent a Question](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/asking-a-question.md).
- You can follow the steps the Analyst Agent takes while it works, answer any clarifying questions it asks, and rate its response. To learn how to read a response and give feedback, see [Evaluating Analyst Agent Responses](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/reading-the-response.md).
- You can turn an analysis into a chart, a PowerPoint or Excel file, or an interactive simulation. To learn how to generate and export these results, see [Visualizing and Exporting Results](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/visualizing-and-exporting-results.md).
- You can have the Analyst Agent remember your preferences, such as your preferred branding for generated decks, across conversations. To learn how to manage what it remembers, see [Personalizing Analyst Agent with Memories](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/personalizing-with-memories.md).
## Analyst Agent Limitations
The Analyst Agent currently has the following limitations:
- The Analyst Agent builds a [Lucanet data model](https://support.lucanet.com/en/documentation/glossary.md#lucanet-data-model) of your CFP and xP&A structures the first time you use it each day. This can take up to 15 minutes, depending on the number of dimensions and models; every following question that day uses the already-built model.
- The data model is specific to you and reflects your permissions, so it cannot be shared across users.
- The data model is rebuilt once a day. A model, account, ledger structure, or entity that was created or renamed after the last rebuild is not yet known to the Analyst Agent. To force an update, ask the Analyst Agent to "rebuild the graph."
- The Analyst Agent interface is currently available in English only, regardless of which language you have set for the Lucanet CFO Solution Platform. This means, the descriptions, example prompts, and buttons remain in English, but you can ask your questions in any language and the agent will answer in your language.
---
---
title: "Asking Analyst Agent a Question"
source_url: https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/asking-a-question
language: en
last_updated: 2026-09-16
---
# Asking Analyst Agent a Question
## Overview
To interact with the Analyst Agent, simply type your question in the message field in natural language, for example "How did operating expenses change over the last 3 months? Break it down by category." If you are not sure where to start, select one of the example prompts on the start screen.
## Scoping Your Question in the Analyst Agent
Use the **Analyze in** toggle above the message field to choose whether the Analyst Agent should look at **CFP** (Consolidation & Financial Planning), **xP&A** (Extended Planning & Analysis), or both. Both are selected by default.
> **Note:** The **Analyze in** toggle only appears if you have access to both CFP and xP&A. If you have access to only one of them, the Analyst Agent analyzes that solution automatically and does not show the toggle.
The "Analyze in" toggle
## Referencing Specific Elements with "/" in the Analyst Agent
Type **"/"** in the Analyst Agent's message field to open a drop-down list of dimensions for the solution you are analyzing. For **CFP**, this includes dimensions such as accounts, adjustment levels, data levels, organization elements, or partners. For **xP&A**, this includes the model as well as its dimensions and dimension items.
Select a dimension to open a second drop-down list showing only the elements relevant to it, for example the individual companies, groups, or consolidation views under **Organization elements** in CFP. Selecting an element inserts a precise reference into your question, so the Analyst Agent asks fewer clarifying questions.
Referencing a CFP dimension with "/"
## Example Questions for the Analyst Agent
The following examples illustrate the types of questions you can ask the Analyst Agent. The agent's capabilities keep expanding, so if you want to know what it can currently do, simply ask it directly.
| Type of question | Example |
|---|---|
| Variance and breakdowns | "Break down OPEX by child account for July 2026, Actual vs. FC 6+6 2026." |
| Comparisons | "What are the drivers behind the variance between Actual and Budget on Total Revenues for Q2 2026?" |
| Charts | "Create a waterfall chart showing revenue to EBITDA for the last quarter." |
| Planning and xP&A models | "What would ARR look like if churn rate increased to 5% in the Revenue SaaS Model?" |
| Simulations | "Create a simulation to model how EBITDA develops with different Order Intake levels." |
| Artifact generation (PowerPoint, MS Excel, HTML) | "Turn this analysis into a PowerPoint slide." / "Export this breakdown as an Excel file." / "Create an HTML report of this analysis." |
## Using Your Own Files as Context in the Analyst Agent
The Analyst Agent's message field includes an attachment icon . Click it to attach an Excel or CSV file to your question and enrich your analysis with data from external systems, for example a list of production quantities or vendor information. The Analyst Agent combines the file with your CFP or xP&A data for the analysis.
You can also attach a PowerPoint or Excel file as a **styling template**, for example "Use this PowerPoint as the template for the slide deck." The Analyst Agent then uses that file's layout for any file it generates in the conversation.
## Next Steps
Refer to [Evaluating Analyst Agent Responses](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/reading-the-response.md) to learn how the Analyst Agent explains its steps, when it asks a clarifying question, and how to rate an answer.
---
---
title: "Chat and History"
source_url: https://support.lucanet.com/en/documentation/lume/chat
language: en
last_updated: 2026-09-04
---
# Chat and History
## Overview
The Lucanet Lume chat interface lets you have natural-language conversations with the Lucanet CFO Solution Platform. All conversations are saved as searchable threads so you can return to any previous discussion at any time.
When opened in full-screen mode, the Lume window is displayed as follows:
Lume in full-screen mode
## Chat Functions
### General Chat Functions
The following chat functions are available to you regardless of which solution you are using.
| Function | Description |
|---------|---------|
| **Suggested prompts** | When you open Lume, a welcome screen with suggested prompts is displayed to help you get started. |
| **Start a new chat** | Use the **+** button in the sidebar to start a new conversation without losing your previous threads. |
| **Stop a response** | While Lume is generating a response, click **Stop** to end the process immediately. The partial response stays in the conversation, marked as stopped, and any text you started typing while Lume was answering remains in the input field. You can send your next message once the response has stopped. |
| **Browser notifications** | When a chat finishes processing a request, Lume sends a browser notification. You receive the notification when you have minimized the browser or switched to another tab or application outside the Lucanet CFO Solution Platform. The notification includes the chat's title or a short summary; clicking it opens the corresponding chat directly. On first use, Lume asks for permission to show notifications; if you deny permission, you are not asked again. |
| **Conversation history** | All your conversations are saved as separate threads. The history panel is searchable and grouped by recency. A chat remains accessible for **up to 30 days**. After 30 days, a chat is automatically deleted from your history. |
| **Rename a thread** | Threads are automatically named after your first message. If you want to rename a chat, open the chat from the history, hover over the three-dot menu, and choose **Rename**. |
| **Delete a thread** | If you want to permanently remove a chat, open the chat from the history, hover over the three-dot menu, and choose **Delete**. |
| **Full-screen mode** | Select the expand icon in the top toolbar to expand the Lume panel to full screen for more space during longer or more complex conversations. |
### Solution-Specific Chat Functions
The following chat functions are only available in specific solutions.
| Function | Description |
|---------|---------|
| **Referencing dimensions** | You can reference dimensions from **Consolidation & Financial Planning** in your Lume prompts using a forward slash ("/"). When typing a forward slash, a drop-down list of available dimensions such as account, data level, or organization element appears. You can select any dimension to narrow your request. After selecting a dimension, another drop-down list is displayed, showing only elements that are relevant to that dimension. |
| **Transferring user roles** | In **Disclosure Management**, you can ask Lume to transfer a user's document- and chapter-level roles to another user. Lume first shows a preview of the changes, then, once you confirm, adds the missing roles to the target user; the target user's existing roles and global roles are not affected. For more information, see [Transferring User Roles to Another User with Lucanet Lume](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/transfer-user-roles-lume-disclmgmt.md). |
| **Re-pointing references** | In **Disclosure Management**, you can ask Lume to re-point references to a different source document, for example when the original source document has been updated. Lume re-points all references that point to the same old source document together to the new source document. For more information, see [Re-Pointing Word References with Lucanet Lume to a New Source Document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/use-word-references.md#repointing-word-references-with-lucanet-lume-to-a-new-source-document). |
---
---
title: "Evaluating Analyst Agent Responses"
source_url: https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/reading-the-response
language: en
last_updated: 2026-09-16
---
# Evaluating Analyst Agent Responses
## Overview
While the Analyst Agent works, it displays the steps it is taking, for example exploring your CFP (Consolidation & Financial Planning) data or finding the relevant dimensions and accounts. If your question is ambiguous — for example if it does not specify which organization or adjustment level to use — the Analyst Agent asks one or more clarifying questions with selectable answer options before continuing.
Once the Analyst Agent has an answer, it displays a narrative explanation, often with a suggested follow-up question you can select to continue the analysis.
An Analyst Agent response confirming a calculation approach before continuing
## Giving Feedback on an Analyst Agent Response
Use the thumbs up or thumbs down icon below any Analyst Agent response to rate it. Rating a response attaches your feedback directly to that answer.
## Next Steps
Refer to [Visualizing and Exporting Results](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/visualizing-and-exporting-results.md) to turn an analysis into a chart, a PowerPoint or Excel file, or an interactive simulation.
---
---
title: "Lucanet Lume"
description: "Lucanet Lume is the conversational layer of the Lucanet CFO Solution Platform: ask questions in plain language and Lume provides instant answers or routes your request to the right workflow agents behind the scenes. It is the starting point for orchestrating everything the Intelligence Core of Lucanet provides."
source_url: https://support.lucanet.com/en/documentation/lume
language: en
last_updated: 2026-09-28
---
# Lucanet Lume
## Lucanet's Conversational Layer of the CFO Solution Platform
Lucanet Lume is the conversational layer to interact with the Lucanet CFO Solution Platform through a single interface.
Ask a question in plain language and Lucanet Lume handles the rest; providing instant answers or routing to the right workflow agents behind the scenes with no prompt engineering required.
You can query, instruct, and review without switching tools or leaving the workflow. It's the starting point for orchestrating everything the Intelligence Core of Lucanet provides.
#### What kind of questions can I ask Lucanet Lume?
Lume's capabilities depend on your license and permissions, and evolve frequently. To see what's available to you, just ask Lume: "What can you do?"
> **Note:** Please note that the use of Lume is limited. For more information, please speak to your Lucanet contact.
> **Note:** Lucanet Lume is only available if the AI features of the Lucanet CFO Solution Platform are activated. Users with the **License Manager** role can activate and deactivate the AI features in the **Lucanet licenses** workspace. For more information, see [Managing Lucanet Licenses | Activating and Deactivating the AI Features](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md#activating-and-deactivating-the-ai-features).
## Chat and History in Lume
The Lucanet Lume chat interface lets you have natural-language conversations with the Lucanet CFO Solution Platform. All conversations are saved as searchable threads so you can return to any previous discussion at any time.
For more information, see [Chat and History](https://support.lucanet.com/en/documentation/lume/chat.md).
## Agents in Lume
Lucanet's family of agents is actively growing. The first purpose-built intelligent assistants for your most important workflows are already available, with more assistants coming to Lume soon — so you can get more done, faster. For an overview of the assistants, see [Agents](https://support.lucanet.com/en/documentation/lume/agents.md).
> **Warning:** While Lume is designed to provide accurate and helpful answers, it may occasionally make mistakes. We recommend double-checking all answers and insights provided to ensure their accuracy.
## Opening Lucanet Lume
To open Lucanet Lume choose one of the following options:
- Go to the **Home** area to open the Lume welcome page.
- Click **Lume** in the main menu. The **Lume** panel is displayed as follows, for example:
Type your question in simple language. For example, you can ask about specific data points or request insights on your Consolidation & Financial Planning reports.
If you are not sure where to start, the system provides context-aware prompt suggestions to help guide your queries.
---
---
title: "Personalizing Analyst Agent with Memories"
source_url: https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/personalizing-with-memories
language: en
last_updated: 2026-09-16
---
# Personalizing Analyst Agent with Memories
## Overview
The Analyst Agent can remember facts you state explicitly in a conversation and reuse them in later conversations.
A memory entry for the Analyst Agent can be, for example:
- a preferred color palette for generated slide decks
- a certain file structure to be used
- writing style guides
- analytical presentation conventions
- currency handling preferences
- etc.
Memories are private to you and are never shared with other users.
## Displaying Your Analyst Agent Memories
To review or manage what the Analyst Agent has remembered, select **Memories** at the bottom of the Lume sidebar, then open the **Analyst Agent** tab. The tab label displays how many memory entries currently exist for the Analyst Agent.
Memories panel in Lume
### Adding an Analyst Agent Memory Manually
Click **+ Add** and type the fact you want the Analyst Agent to remember, for example a formatting rule or a default currency. The new entry is added to the list immediately and is used in your next conversation with the Analyst Agent.
### Adding an Analyst Agent Memory During a Conversation
You can also ask the Analyst Agent directly to remember something, for example **"Remember that I prefer amounts shown in thousands."** The Analyst Agent then suggests saving it as a memory entry.
### Editing or Deleting an Analyst Agent Memory Entry
Hover over an Analyst Agent memory entry to reveal its options icon, **…** the options icon, on the right. Click it, then select **Edit** to change its text or **Delete** to remove that entry.
Editing or deleting a single memory entry
To remove every memory entry for the selected agent at once, click **Delete all** above the list.
### Deactivating Analyst Agent Memory Collection
Use the **Deactivate memory collection** toggle to stop the Analyst Agent from creating new memories. Existing entries are kept until you delete them; reactivate the toggle at any time to resume memory collection.
---
---
title: "Visualizing and Exporting Results"
source_url: https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/visualizing-and-exporting-results
language: en
last_updated: 2026-09-16
---
# Visualizing and Exporting Analyst Agent Results
## Overview
Besides a narrative answer, the Analyst Agent can turn an analysis into a downloadable **chart**, a **PowerPoint or Excel file**, or an **interactive HTML simulation**.
## Charts in the Analyst Agent
You can ask the Analyst Agent to visualize a result and it adds a chart to its response. You can download the chart image, copy it, or expand it to full size using the icons in its top-right corner.
A chart generated by the Analyst Agent
## PowerPoint and Excel Exports from the Analyst Agent
You can ask the Analyst Agent to turn an analysis into a PowerPoint or Excel file, for example:
**"Please provide this as a board PowerPoint slide deck."**
The Analyst Agent builds the file and offers it as a download; opening it works like any other downloaded PowerPoint or Excel file.
A PowerPoint file generated by the Analyst Agent, ready to download
> **Tip:** You can define the layout of the generated PowerPoint or Excel file, for example your company's font and color palette, in two ways: attach an example file to use its layout for the current conversation only, or add an entry to the Analyst Agent's memory to reuse it across future conversations. See [Personalizing Analyst Agent with Memories](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/personalizing-with-memories.md) to learn how to add and manage memories.
## Interactive Simulations in the Analyst Agent
You can ask the Analyst Agent to build a simulation, for example:
**"Create an HTML simulation with a slider to change the drivers for DSO and DPO and the resulting cash flow impact."**
The Analyst Agent opens the simulation as a report with adjustable sliders for the scenario inputs, the resulting impact, and an explanation of how the simulation works.
An interactive simulation built by the Analyst Agent
## Next Steps
Refer to [Personalizing Analyst Agent with Memories](https://support.lucanet.com/en/documentation/lume/agents/analyst-agent/personalizing-with-memories.md) to have the Analyst Agent remember your preferences, for example a brand color palette for generated decks, across conversations.
---
## Administration
The Administration area of the Lucanet CFO Solution Platform acts as a central hub for user management and the administration of the Lucanet CFO Solution Platform.
---
title: "Administration"
description: "The Administration area of the Lucanet CFO Solution Platform acts as a central hub for user management and the administration of the Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/administration
language: en
last_updated: 2026-05-30
---
## Administration
The **Administration** area of the Lucanet CFO Solution Platform acts as a central hub for user management and the administration of the Lucanet CFO Solution Platform.
- In the **[User Management](https://support.lucanet.com/en/documentation/administration/user-management.md)** section, you can create users and user roles, and assign these to higher-level permissions. It is ensured that administrators of the Lucanet CFO Solution Platform have the necessary tools to create and update user accounts in a few steps within minimum time.
- The **[Platform Management](https://support.lucanet.com/en/documentation/administration/platform-management.md)** area provides:
- An overview of the solutions you have purchased and their associated [license](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md) packages, as well as the number of users who have access to each [solution](https://support.lucanet.com/en/documentation/glossary.md#solution)
- Access to the configuration of [external authentication](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md)
- [Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md) that are used to install SEA in Lucanet.Software Manager and to configure SEA applications in Consolidation & Financial Planning solution of the Lucanet CFO Solution Platform
- [Customizations](https://support.lucanet.com/en/documentation/administration/platform-management/customization.md) that allow the administrator to adapt certain elements of the Lucanet CFO Solution Platform to your corporate design
- In the **[Exchange Rate Management](https://support.lucanet.com/en/documentation/administration/exchange-rate-management.md)** section, you can configure the exchange rates that solutions on the Lucanet CFO Solution Platform use to convert between currencies. For each currency combination, you choose whether the rates are retrieved automatically from the European Central Bank or from an Excel file you upload yourself.
Administrative notifications are managed through the [Notifications](https://support.lucanet.com/en/documentation/global-functions/notifications.md) section, where you can view system updates, user management events, and other administrative activities.
User interface of the administration on the Lucanet CFO Solution Platform
[Request demo](https://www.lucanet.com/en/request-demo/)
## Functional Areas in the Administration Section
- [User Management](https://support.lucanet.com/en/documentation/administration/user-management.md)
- [Managing the CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/platform-management.md)
- [Exchange Rate Management](https://support.lucanet.com/en/documentation/administration/exchange-rate-management.md)
---
---
title: "Assigning Reporting Entities to Lease Accounting Users"
description: "In the Users workspace of the Administration area, you can define which reporting entities a user can access in Lease Accounting when you edit the user."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/users/assigning-reporting-entities
language: en
last_updated: 2026-09-30
---
# Assigning Reporting Entities to Lease Accounting Users
## Overview
In the **Users** workspace of the **Administration** area, you can define which reporting entities a user can access in **Lease Accounting**. In addition to the permissions of the user role, the user then only works with the data of the assigned reporting entities.
By default, all reporting entities are assigned to a user. Access is only restricted once you remove reporting entities from the user.
> **Note:** You can only assign reporting entities when you edit an existing user.
## Assigning Reporting Entities
To assign reporting entities to a user:
1. In the **Users** workspace, select the user to whom you want to assign reporting entities.
2. Click **Edit user**.
3. Below the user roles for **Lease Accounting**, remove the reporting entities that the user should not have access to.
The **Select reporting entities** option is displayed as follows, for example:
'Select reporting entities' option in the 'Edit User' side panel
4. Click **Save**.
To grant the user access to all reporting entities again, select **All entities**.
At least one reporting entity must be selected.
If you change the user role of a user, the assignment is reset and the user can access all reporting entities again.
---
---
title: "Change Log"
description: "As an administrator, you can use the change log to efficiently monitor and manage all changes to user management. You can view a user's change log or an overview of all user changes."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/users/change-log
language: en
last_updated: 2026-05-01
---
# Change Log
## Overview
As an administrator, you can use the **change log** to efficiently monitor and manage all changes to users. You can display a user's change log or an overview of all user changes.
In the change log table, you can find detailed information about the changes that have been made. This includes the date of the change, who performed the change, how the change was authenticated, the action, the user impacted (in the general change log only), the exact change, and the old and new values of the changed settings.
User groups have their own change log, which you open from the **User groups** list. For more information, see [Managing User Groups](https://support.lucanet.com/en/documentation/administration/user-management/user-groups.md).
> **Note:** The **Authenticated as** column indicates how a change was authenticated: **Portal** for changes made by a user who is signed in to the CFO Solution Platform, or the type of API access used for programmatic changes. For changes made through the Platform API, the **Performed by** column displays the name of the API token that was used instead of a user name. For more information on API tokens, see [Managing API Tokens](https://support.lucanet.com/en/documentation/administration/user-management/api-token-management.md).
## Opening the Change Log
To open the change log for all users or for a single user:
1. Navigate to **Administration | User management | Users** to open the list of users.
2. Do one of the following:
- Click **General change log** above the list of users to open the change log for all users. The general change log is displayed as follows, for example:
Change log for all users
- Click the three dot icon in a row in the list of users to open the change log for that user. The change log for a single user is displayed as follows, for example:
Change log for a single user
## Configuring the Change Log
You have the following options for configuring the display of the change log:
#### Specify time period
Using the drop-down list next to **Show changes from**, you can specify the time period for displaying changes.
If you choose **Custom** from the drop-down list, a calendar will appear in which you can specify the time period you want to view. The setting is displayed as follows, for example:
Specify a time period for the change log
#### Sort by date
By clicking the sort user list icon in the header of the **Date** column, you can sort the change of date in ascending or descending order.
#### Filter
You can use the user mgmt hamburger icon in the relevant column header to filter the data to display specific changes:
- in the **Performed by**, **Authenticated as**, **Action**, **Impacted user**, and **Exact change** columns in the general change log
- in the **Performed by**, **Authenticated as**, **Action**, and **Exact change** columns of a single user's change log
---
---
title: "Configuring Customizations"
description: "In the Customization workspace, you as an administrator can customize certain elements of the Lucanet CFO Solution Platform to match your corporate design. Currently, you can upload your company logo and configure it for use in e-mail templates."
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/customization
language: en
last_updated: 2026-10-05
---
# Configuring Customizations in the Lucanet CFO Solution Platform
## Overview
In the **Customization** workspace, you as an **administrator** can customize certain elements of the Lucanet CFO Solution Platform to match your corporate design. Currently, you can upload your company logo and configure it for use in e-mail templates.
## Opening the 'Customization' Workspace in the CFO Solution Platform
To open the **Customization** workspace in the Lucanet CFO Solution Platform:
1. Click **Administration** in the main menu of the CFO Solution Platform.
2. Open the **Platform management** area and click **Customization**. The **Customization** workspace is displayed as follows:
Workspace 'Customization'
## Uploading and Applying Company Logo in the CFO Solution Platform
To upload and apply your company logo to e-mail templates in the Lucanet CFO Solution Platform:
1. Click **browse** or drag and drop the file into the appropriate field. Make sure the following requirements are met:
- The file size must not exceed 128 KB.
- Only PNG or SVG format is permitted.
- Images must be vertically aligned.
2. If necessary, click **Preview** to preview the logo after the file has been uploaded.
Show preview
3. Click **Apply changes** to apply the logo to the e-mail templates.
## Replacing and Removing the Company Logo in the CFO Solution Platform
To replace or remove the uploaded company logo in the Lucanet CFO Solution Platform, hover the mouse over the uploaded file. The following two options are available:
| Option | Description |
|---------|---------|
| the replace icon | Replaces the file with another file. |
| the delete icon | Removes the file. Once the file has been removed, the option to upload a file will be displayed again. |
## Resetting to Default Settings in the CFO Solution Platform
To remove all custom settings and return to the default configuration in the Lucanet CFO Solution Platform, click **Reset to default** in the **Customization** workspace.
---
---
title: "Configuring External Authentication"
description: "In the External authentication workspace of the Lucanet CFO Solution Platform, you can configure that a user is authenticated via a central instance in the network. The separate maintenance of the password for access to the CFO Solution Platform can then be omitted."
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication
language: en
last_updated: 2026-10-05
---
# Configuring External Authentication
## Overview
In the **External authentication** workspace of the **Lucanet CFO Solution Platform**, you can activate or deactivate an external identity provider. This means that a password no longer needs to be maintained separately for accessing the CFO Solution Platform.
External authentication using [OIDC](https://support.lucanet.com/en/documentation/glossary.md#oidc) (OpenID Connect) and [SAML](https://support.lucanet.com/en/documentation/glossary.md#saml) (Security Assertion Markup Language) is possible for the Lucanet CFO Solution Platform, with identity providers such as Microsoft Entra ID, Okta, or a custom provider.
## Activating External Authentication
To activate external authentication for the Lucanet CFO Solution Platform:
1. Click **Administration**.
2. Open the **External authentication** workspace in **Platform management**:
Open 'External authentication' workspace
3. Activate the **Activate external authentication** check box.
4. Under **Please choose the authentication procedure**, select the combination of authentication protocol and identity provider that matches your setup:
'Please choose the authentication procedure' menu
The configuration form then displays the fields and provider-specific hints for your selection.
5. Configure the displayed fields:
- **OIDC** (see [Configuring OIDC](#configuring-oidc))
- **SAML** (see [Configuring SAML](#configuring-saml))
6. Click **Apply** to save your configuration.
## Configuring the Connection Details
The options you configure depend on the authentication protocol and identity provider you selected. Hover over the info icon next to a field to see provider-specific guidance.
### Configuring OIDC
If you selected an **OIDC** combination, the following options are displayed:
Options for the configuration of 'OIDC'
To configure external authentication with **OIDC**:
| Option | Description |
|---|---|
| Client ID | Enter the OIDC **Client ID**.
**Note:** The client can be represented by different concepts in different identity providers, for example: • [App registration (Microsoft Entra ID)](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-OIDC.md) • OIDC app integration (Okta) |
| Client secret | Enter the **secret** for the OIDC client.
**Note:** For security reasons, the full client secret cannot be displayed after activation. |
| Issuer URL | The base address from which your identity provider's well-known OIDC metadata endpoints (including the OIDC configuration and the JSON Web Key Set) are exposed.
The required format depends on your identity provider: • **Microsoft Entra ID**: https://sts.windows.net/*{tenant-id}*/ • **Okta**: https://*{your-okta-domain}*/oauth2/default
**Note:** The Issuer URL is validated in real time. If the value does not match the expected format for the selected identity provider, a validation message is displayed and you cannot save until you correct it. For a **Custom** provider, no provider-specific format is enforced. |
| Authorized scopes | The **authorized scopes** represent the level of access to your users' profiles that is requested by the Lucanet CFO Solution Platform. This must be configured correctly in the OIDC client.
Copy the **authorized scopes** displayed and paste them into the configuration of your OIDC client. |
| Sign-in redirect URL(s) | The **sign-in redirect URL** is the address to which users are redirected after authentication with your identity provider. It must be configured in the OIDC client.
Copy the displayed **sign-in redirect URL** and paste it into the configuration of your OIDC client. |
> **Tip:** For more information on configuration steps in Microsoft Entra ID/Azure, see [Configuring Lucanet OIDC Authentication with Microsoft Entra ID/Azure](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-OIDC.md).
### Configuring SAML
If you selected a **SAML** combination, the following options are displayed:
Options for the configuration of 'SAML'
To configure external authentication with **SAML**:
| Option | Description |
|---|---|
| Metadata document URL | The **metadata document URL** is the address via which the SAML configuration document is accessible.
Enter the metadata document URL for the SAML implementation of your identity provider.
**Note:** Each identity provider uses a different format for the metadata URL, for example: • **Microsoft Entra ID**: https://login.microsoftonline.com/*{tenant-id}*/ FederationMetadata/2007-06/FederationMetadata.xml?appid=xxxxxx • **Okta**: https://*{your-okta-domain}*/app/*{app-instance-id}*/sso/saml/metadata |
| Attribute | • The name of the e-mail attribute sent by your identity provider to the Lucanet CFO Solution Platform. • The canonical name is: **http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress**, which is pre-filled by default. |
| Reply URL | • The URL where the SAML response is sent by your identity provider. It must be configured in the SAML integration that represents the Service Provider of the Lucanet CFO Solution Platform to your identity provider. • The reply URL is also known as the **Assertion Consumer Service (ACS) URL** or **Single Sign-On URL**.
**Note:** The SAML integration can be represented by various concepts in different identity providers, for example: • [App registration (Microsoft Entra ID)](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-saml.md) • SAML app integration (Okta)
Copy the displayed **reply URL** and paste it into your SAML integration. |
| Entity ID | The unique identifier for the Lucanet CFO Solution Platform Service Provider. It must be configured in the SAML integration that represents the Lucanet CFO Solution Platform to your identity provider. This is also known as the **Audience URI**.
Copy the displayed **entity ID** and paste it into the SAML configuration of your service provider. |
> **Warning:** **Keep your SAML signing certificate valid.** Lucanet reads the SAML signing certificate from the metadata document URL you configured. Before that certificate expires, Lucanet sends you a reminder e-mail. Renew or rotate the certificate at your identity provider in good time and make sure the metadata document served at your URL contains the new certificate before the current one expires. Otherwise, users may be unable to sign in with SAML.
> **Tip:** For more information on configuration steps in Microsoft Entra ID/Azure, see [Configuring Lucanet SAML Single Sign-On with Microsoft Entra ID/Azure](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-saml.md).
> **Warning:** In order to use external authentication of users, it must be activated in a further step in the properties of the desired user.
>
> To do this, navigate to the **User** workspace and edit the properties of the users who are to log in to the **Lucanet CFO Solution Platform** using external authentication. For additional information see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md).
>
> When you activate external authentication for a user, the user receives an invitation e-mail with a **Log In** button that links directly to the login page.
## Global Authentication Settings
In the **Global authentication settings** section of the **External authentication** workspace, you can define how the users of the Lucanet CFO Solution Platform authenticate.
The section is displayed as follows:
'Global authentication settings' section
The following options are available:
| Option | Description |
|---|---|
| **External authentication by default** | Preselects **External authentication** as the authentication method when you create a user, so the user does not receive Lucanet login credentials. If a user should log in with a user name and password instead, deactivate **External authentication** when you create the user.
The setting does not affect existing users. You can still change the authentication method of existing users. |
| **Enforce external authentication** | Requires all users to use external authentication. The Lucanet CFO Solution Platform automatically converts all existing users who log in with a user name and password.
For more information, see [Enforced External Authentication](#enforced-external-authentication). |
Only one of the two settings can be activated at a time. Both settings require external authentication to be activated and configured successfully.
To activate or deactivate one of the settings:
1. Open the **External authentication** workspace in **Platform management**.
2. In the **Global authentication settings** section, activate or deactivate the required setting.
A dialog is displayed that describes the consequences of the change.
3. Confirm the change.
### Enforced External Authentication
If external authentication is enforced, the following applies:
- The Lucanet CFO Solution Platform converts all existing users who log in with a user name and password to external authentication and sends them the invitation e-mail for external authentication. These users can then only log in through your identity provider.
- Users who already use external authentication remain unchanged.
- A locked user is only converted once you unlock the user.
- When you create a user, **External authentication** is preselected as the authentication method and cannot be changed.
- The **TOTP MFA (authenticator app code)** authentication method cannot be activated or deactivated. For more information, see [Creating and Editing Users for the Lucanet CFO Solution Platform | Authentication Methods](https://support.lucanet.com/en/documentation/administration/user-management/users.md#authentication-methods).
> **Warning:** Make sure that external authentication works correctly before you enforce it. Otherwise, users may no longer be able to log in.
The conversion runs in the background. Users who are logged in at that time are not signed out. While the conversion is running, you cannot change the global authentication settings or deactivate external authentication.
If the conversion fails, the Lucanet CFO Solution Platform deactivates the **Enforce external authentication** setting again and resets all converted users to their previous authentication method.
#### Ending the Enforcement of External Authentication
The **Enforce external authentication** setting cannot be deactivated directly. To end the enforcement, deactivate external authentication. The options in the **Global authentication settings** section are deactivated in the process. You can then activate external authentication again if required.
> **Warning:** If you deactivate external authentication while it is enforced, the Lucanet CFO Solution Platform switches all users to logging in with a user name and password: every user receives a new invitation e-mail with a temporary password and can no longer log in through your identity provider.
---
---
title: "Configuring Lucanet OIDC Authentication with Microsoft Entra ID/Azure"
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-OIDC
language: en
last_updated: 2026-08-31
---
# Configuring Lucanet OIDC Authentication with Microsoft Entra ID/Azure
## Overview
If you use **Microsoft Entra ID** as your identity provider and choose the **OIDC** method for **external authentication** of the Lucanet CFO Solution Platform, you must first register Lucanet as an app in Microsoft Entra ID.
After successful registration and configuration, you can copy the authentication parameters in Microsoft Entra ID and paste them into the Lucanet CFO Solution Platform to complete the configuration of the external authentication.
## Creating an App Registration for Lucanet in MS Entra ID
To create an app registration for Lucanet at the MS Entra admin center:
1. Open the Microsoft Entra admin center at [https://entra.microsoft.com](https://entra.microsoft.com).
2. Go to **Applications | App registrations**.
'App registrations' workspace at the Microsoft Entra admin center
3. Click **New registration**.
Button used to register a new app
The page **Register an application** is displayed.
4. Enter the display name of the app in the field under **Name**.
Entering the display name of the app
5. Choose the option **Accounts in this organizational directory only (** __ **only - Single tenant)** under **Supported account types**.
Selecting the supported account type
6. Copy the URI under **Sign-In Redirect URL(s)** in the **External authentication** workspace on the Lucanet CFO Solution Platform.
Copying the redirect URL from the Lucanet CFO Solution Platform
If necessary, choose the URI from the **Web** drop-down list in the **Redirect URI (optional)** area and enter it in the field behind **Web** in MS Entra ID.
Configuration of the redirect URI
7. Click **Register**.
Completing the app registration
## Configuring Lucanet in MS Entra ID
Go to the newly created app registration and perform the following steps to configure Lucanet as an app in MS Entra ID:
### Activating ID Tokens
Activate the **ID tokens** for the app registration. Proceed as follows:
1. Navigate to **Manage | Authentication**.
'Authentication' workspace on the navigation bar
2. Activate the **ID tokens (used for implicit and hybrid flows)** check box in the **Implicit grant and hybrid flows** area.
Activating 'ID tokens'
### Creating a Client Secret
Create a **client secret** for Lucanet. Proceed as follows:
1. Navigate to **Manage | Certificates & secrets**.
'Certificates & secrets' workspace on the navigation bar
2. Click the button the client secret button.png "scale:2.5" icon on the **Client secrets** tab:
3. Enter a name or description for the secret in the **Description** field in the **Add a client secret** area and, if necessary, choose a validity period for the secret from the **Expires** drop-down list:
Settings in the 'Add a client secret' area
4. Click **Add**. A client secret is generated, which is displayed in the **Value** column on the **Client secrets** tab:
Copying a client secret from MS Entra ID
5. Paste the value in the **Client secret** field in Lucanet CFO Solution Platform.
'Client secret' field in Lucanet
### Configuring Optional Claims
You can configure optional claims for Lucanet as an app in MS Entra ID. Proceed as follows:
1. Navigate to **Manage | Token configuration**.
'Token configuration' workspace on the navigation bar
2. Click the button the add optional claim button.png "scale:2.5" icon.
3. Choose the **ID** token type and activate the **email** check box in the **Claim** column.
Setting for the 'ID' token type
4. Choose the **Access** token type and activate the **email** check box in the **Claim** column.
Setting for the 'Access' token type
5. Click **Save**. The optional claims are added and displayed, for example, as follows:
Optional claims configured
### Setting Up API Permissions
Set up the API permissions. Proceed as follows:
1. Navigate to **Management | API Permissions**.
'API permissions' workspace on the navigation bar
2. Click the button the add a permission button.png "scale:2.5" icon in the **Configured permissions** area.
3. Click **Microsoft Graph** on the **Microsoft APIs** tab.
'Microsoft Graph' on the 'Microsoft APIs' tab
4. Click **Delegated permissions**.
'Delegated permissions' option
5. Activate the **email** and **openid** check boxes in the **OpenId permissions** area.
Settings in the 'OpenId permissions' area
6. Click **Add permissions**.
7. Click **Grant Admin consent for __** in the **Configured permissions** area.
Button used to grant admin consent
8. Click **Yes** in the displayed dialog **Grant admin consent confirmation**.
9. The set-up permissions are displayed, for example, as follows:
API permissions in MS Entra ID
> **Note:** You can find additional information on how to configure the app registration in MS Entra ID in the [documentation from Microsoft](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app).
## Configuring Authentication Parameters for the Lucanet CFO Solution Platform
After configuring the enterprise application and Single Sign-On in Azure/Microsoft Entra ID, you need to retrieve specific authentication parameters and add them to the Lucanet CFO Solution Platform to complete the external authentication setup.
To configure authentication parameters for the Lucanet CFO Solution Platform:
1. Get the **Client ID** from Azure Portal/Microsoft Entra ID:
You can find the Client ID behind **Application (client) ID** in the **Essentials** area on the **Overview** page:
'Overview' section in Azure
Copying the client ID from MS Entra ID
2. Paste the Client ID in the **Client ID** field in the Lucanet CFO Solution Platform.
'Client ID' field in Lucanet
3. Paste the Client secret value in the **Client secret** field in the Lucanet CFO Solution Platform, if not already configured in previous steps (see [Creating a Client Secret](#creating-a-client-secret)).
4. Get the **Issuer URL** from Azure Portal/Entra ID Admin Center:
In the **App registrations**, select your application. On the **Overview** page, click **Endpoints**.
'Overview' section in Azure
'Endpoints' button on the 'Overview' page
In the **Endpoints** panel, copy the tenant ID from the **Authority URL (Accounts in this organizational directory only)** field. Use the part highlighted in the red box in the screenshot example below (the tenant ID after https://login.microsoftonline.com/).
The Issuer URL has the following notation:
**https://sts.windows.net**/< _Your tenant ID in MS Entra ID_ >
Example:
If your tenant ID is **123bfsd-as34-sd34-34fg-f35gh67h8**, the issuer URL will be **https://sts.windows.net/123bfsd-as34-sd34-34fg-f35gh67h8**.
'Endpoints' area on the 'Overview' page in MS Entra ID
5. Add the Issuer URL in the **Issuer URL** field in the Lucanet CFO Solution Platform.
'Issuer URL' field in Lucanet
> **Warning:** **Attention**: The e-mail address of a user on the **Lucanet CFO Solution Platform** must be identical to the e-mail address in **Azure/MS Entra ID**. The upper and lower case of e-mail addresses must match exactly.
You can find additional information on how to use the parameters when configuring the external authentication for the Lucanet CFO Solution Platform with the OIDC method in the section [Configuring OIDC](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md#configuring-oidc) in **Configuring External Authentication**.
> **Warning:** If your **User principal name** and your **e-mail address** in Azure/MS Entra ID are different, the OIDC configuration will not work as described on this page. Please choose **SAML** as the authentication method instead.
---
---
title: "Configuring Lucanet SAML Single Sign-On with Microsoft Entra ID/Azure"
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication/entra-id-registration-saml
language: en
last_updated: 2026-08-31
---
# Configuring Lucanet SAML Single Sign-On with Microsoft Entra ID/Azure
## Overview
If you use **Azure/Microsoft Entra ID** as your identity provider and choose the **SAML** method for **external authentication** of the Lucanet CFO Solution Platform, you must first register Lucanet as an enterprise application in the Azure Portal/Microsoft Entra ID Admin Center.
After completing the registration and configuration in Azure Portal/Microsoft Entra ID, you can copy the authentication parameters from Azure/Microsoft Entra ID and paste them into the Lucanet CFO Solution Platform to complete the configuration of external authentication.
## Creating an Enterprise Application for Lucanet in Azure/MS Entra ID
To create an Enterprise application for Lucanet in Azure/Microsoft Entra ID:
1. Open the [Azure Portal](https://portal.azure.com/#home) or the Microsoft Entra Admin Center at [https://entra.microsoft.com](https://entra.microsoft.com/).
2. Navigate to **Enterprise applications**. Click **\+ New application.**
'Enterprise applications' Workspace in Microsoft Azure
3. On the displayed page **Browse Microsoft Entra Gallery**, click **Create your own application**.
'Create your own application' button
4. Enter a name for the application (e.g., _Lucanet CFO Platform Authentication SAML 2_) and choose **Integrate any other application you don't find in the gallery (Non-gallery)**.
Creating your own application
5. Click **Create**.
### Changing Properties
We recommend setting **Assignment required** to **No** in the **Properties** to simplify the configuration and reduce administrative effort. This allows all users in your Microsoft Entra ID organization to access the application automatically, without the need to manually assign individual users or groups.
However, if your organization requires stricter access control for security or compliance reasons, you can keep the setting at **Yes**.
To configure user assignment:
1. In the created enterprise application, navigate to **Manage | Properties**.
'Properties' section
2. Set the **Assignment required** toggle based on your requirements:
Setting 'Assignment required' to 'no'
3. Click **Save**.
## Configuring Single Sign-On in Azure/Microsoft Entra ID
Go to the newly created enterprise application and perform the following steps to configure Single Sign-On for Lucanet in Azure/Microsoft Entra ID:
1. Navigate to **Manage | Single sign-on**.
'Single sign-on' workspace in Azure Portal
2. Select **SAML** as the single sign-on method.
Selecting 'SAML' as the single sign-on method
The options for the **Basic SAML Configuration** are displayed as followed:
Options for Basic SAML Configuration on the 'Set up Single Sign-On with SAML' page
3. Copy the **Entity ID** from the **External authentication** workspace in the **Lucanet CFO Solution Platform**.
'External authentication' workspace in Lucanet
Copying the 'Entigy ID' from Lucanet CFO Solution Platform
4. In the **Basic SAML Configuration** area in the Azure Portal, click **Add identifier** under **Identifier (Entity ID)**.
Button for adding Entity ID in the Azure Portal
5. Paste the **Entity ID** copied from Lucanet into the corresponding field.
Entity ID added in Azure Portal
6. Copy the **Reply URL** from the **External authentication** workspace in the **Lucanet CFO Solution Platform**.
'External authentication' workspace in Lucanet
Copying the 'Reply URL' from the Lucanet CFO Solution Platform
7. In the **Basic SAML Configuration** area in the Azure Portal, click **Add reply URL** under **Reply URL (Assertion Consumer Service URL)**.
Button for adding reply URL in the Azure Portal
8. Paste the **Reply URL** copied from Lucanet into the corresponding field.
Reply URL added in the Azure Portal
9. Click **Save**.
## Configuring Authentication Parameters for the Lucanet CFO Solution Platform
After configuring the enterprise application and Single Sign-On in Azure/Microsoft Entra ID, you need to retrieve specific authentication parameters and add them to the Lucanet CFO Solution Platform to complete the external authentication setup.
To configure authentication parameters for the Lucanet CFO Solution Platform:
1. Get the **App Federation Metadata Url** from Azure Portal/Microsoft Entra ID:
In the Enterprise application for Lucanet, navigate to **Manage | Single sign-on | Set up Single Sign-on with SAM** L. In the **SAML Certificates** area, copy the **App Federation Metadata Url**.
Copying App Federation Metadata URL
2. Add the **App Federation Metadata Url** to the Lucanet CFO Solution Platform:
In the Lucanet CFO Solution Platform, navigate to the **External authentication** workspace.
'External authentication' workspace in Lucanet
Paste the **App Federation Metadata Url** into the **Metadata document URL** field.
'Metadata document URL' field in Lucanet
3. Get the **Attribute** value from Azure Portal/Entra ID Admin Center:
In the Enterprise application for Lucanet, navigate to **Manage | Single sign-on | Set up Single Sign-on with SAML**.
'Single sign-on' workspace in Azure Portal
In the **Attributes & Claims** area, click **Edit**. The **Attributes & Claims** page will be displayed as follows, for example:
'Attributes & Claims' page in the Azure Portal
In the **Additional claims** area, click the row with the value **user.mail**. The **Manage claim** page will be displayed as follows, for example:
'Manage claim' page with the claim 'Name' and the 'Namespace'
Copy the **Namespace** field value and the **Name** field value. Combine them to create the **Attribute** value using the following structure:
**Namespace/Name**
Example in the screenshot above:
- **Namespace**: http://schemas.xmlsoap.org/ws/2005/05/identity/claims
- **Name**: emailaddress
- **Attribute**: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
4. Add the **Attribute** value to the Lucanet CFO Solution Platform:
In the Lucanet CFO Solution Platform, navigate to the **External authentication** workspace.
'External authentication' workspace in Lucanet
Paste the **Attribute** value into the **Attribute** field.
'Attribute' field in Lucanet
> **Warning:** **Attention**: The e-mail address of a user on the **Lucanet CFO Solution Platform** must be identical to the e-mail address in **Azure/MS Entra ID**. The upper and lower case of e-mail addresses must match exactly.
You can find additional information on how to use the parameters when configuring the external authentication for the Lucanet CFO Solution Platform with the SAML method in the section [Configuring SAML](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md#configuring-saml) in **Configuring External Authentication**.
---
---
title: "Creating and Editing Users"
description: "The user management in Administration allows you to create, manage and delete users for the Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/users
language: en
last_updated: 2026-10-05
---
# Creating and Editing Users for the Lucanet CFO Solution Platform
## Overview
In the **Users** workspace of the **Administration** area, you can create, manage, and delete users for the Lucanet CFO Solution Platform.
In this workspace, you can configure the following settings:
- Which users can access the different solutions and/or act as an administrator on the Lucanet CFO Solution Platform
- User roles for each of the different solutions
- Presets such as the display language and formatting displayed for the users
## Creating Users
As a user with access to the **Administration** area, you can create new users for the Lucanet CFO Solution Platform. To do this, go to **Administration | User management | Users** and click **Create User**. The options for **Creating users** are displayed in the panel on the right side of the window, as follows, for example:
'Create User' side panel
### 'General' Tab
You can use the **General** tab to configure the following options for all users:
| Option | Description |
|---|---|
| First name | The user's first name |
| Last name | The user's last name |
| User name | The user's login name
**Note:** Usernames cannot contain spaces. |
| E-mail address | The user's e-mail address |
| Enable authentication | Defines how the user authenticates.
For more information on the available authentication methods, see [Authentication Methods](https://support.lucanet.com/en/documentation/administration/user-management/users/.md#authentication-methods). |
| Lucanet.Certified Professional | Creates a Lucanet.Certified Professional user account. In the user overview, Lucanet.Certified Professional users are indicated by the lucanet certified professional icon.
You can find more information on Lucanet.Certified Professional user accounts in the online help tool for Lucanet.Financial Client, under **Complete description \| Administration \| Administration at database level \| User management \| Lucanet.Certified Professional**.
**Note:** No licenses are required for Lucanet.Certified Professional users. This means that Lucanet.Certified Professional users can be assigned roles in a solution for which there are no more license slots available. |
| Select user access | Defines which solutions you want the user to be able to access, and whether you want to grant the user access to the **Administration** section of the Lucanet CFO Solution Platform.
The following solutions are currently available on the CFO Solution Platform: • Consolidation & Financial Planning • Lease Accounting • xP&A • ESG Reporting • Disclosure Management • XBRL Tagger • Tax Compliance & Reporting • Banking & Cash Management • Data Collection
Which solutions are available to choose from depends on your license scope.
**Note:** If you use Lucanet.Financial Client, users created on the Lucanet CFO Solution Platform are automatically synchronized with Lucanet.Financial Client. |
| Select user roles | Defines a user role for each selected solution and, where applicable, user roles for the **Administration** area.
For more information on the available user roles, see [User Roles in the CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management/users/user-roles.md).
For the following solutions, you can define further settings in addition to the user role: • **Consolidation & Financial Planning**: Detailed permissions for accessing the data model (see [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md)) • **Lease Accounting**: The reporting entities that the user can access (see [Assigning Reporting Entities to Lease Accounting Users](https://support.lucanet.com/en/documentation/administration/user-management/users/assigning-reporting-entities.md))
**Note:** User roles for whom the last license slot is available are indicated with the warning yellow icon. If there are no license slots left for a user role, it will be grayed out. |
| Lock the user permanently | Locks users from accessing the Lucanet CFO Solution Platform. Locked users are indicated by the locked icon in the user overview. By deactivating this check box, you will be able to unlock locked users.
**Note:** This option is only visible when editing a created user. |
#### Authentication Methods
If the **Enable authentication** check box is activated, you must select one of two authentication methods. The methods are displayed as follows, for example:
Authentication methods in the 'General' tab
**External authentication**: The user logs in through the configured identity provider. This method requires an authentication protocol to be configured in the **External authentication** workspace. In the list of users, these users are indicated by the external authentication icon. If external authentication is set as the default for new users, this method is preselected and can be deactivated. For more information, see [Configuring External Authentication | Global Authentication Settings](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md#global-authentication-settings).
**TOTP MFA (authenticator app code)**: The user logs in with user name and password and must enter a six-digit code from an authenticator app at every login. The user receives an e-mail and sets up an authenticator app the next time they log in. In the list of users, these users are indicated by the totp mfa icon. For more information, see [Opening the Lucanet CFO Solution Platform | Multi-Factor Authentication with an Authenticator App](https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform.md#multifactor-authentication-with-an-authenticator-app).
> **Note:** If external authentication is enforced, **External authentication** is preselected for every new user and cannot be changed, and the **TOTP MFA (authenticator app code)** authentication method cannot be activated or deactivated. For more information, see [Configuring External Authentication | Enforced External Authentication](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md#enforced-external-authentication).
If you deactivate the **Enable authentication** check box when editing a user with [TOTP](https://support.lucanet.com/en/documentation/glossary.md#totp) MFA, the user logs in with user name and password only and is no longer asked for a code.
> **Warning:** If you activate the multi-factor authentication for this user again later, the user must set up an authenticator app again. The previous entry in the authenticator app no longer works.
### 'Language and Formatting' Tab
Use the **Language and formatting** tab to configure the language and formatting used to display the software to the user. The tab is displayed as follows:
‘Language and formatting’ Tab
> **Warning:** Users can change their display language and formatting at any time using the options in the top bar (see [Basic Configuration for the Lucanet CFO Solution Platform)](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md). If a user has changed these settings in their **User Account**, you can no longer change them as an administrator.
Once a user has been successfully created, they will automatically receive an invitation e-mail with the following information:
- A link to the **Lucanet CFO Solution Platform**
- A temporary password with which the user should log in for the first time if no external authentication is activated for them.
- Links to access Lucanet.Financial Client if the customer is licensed for **Lucanet Consolidation & Financial Planning** and the user has access to **Lucanet Consolidation & Financial Planning** or **Administration**.
> **Warning:** **Note**: New users must change their temporary password upon first login. For complete information on password requirements and lifecycle policies, see [Opening the Lucanet CFO Solution Platform | Password Policy](https://support.lucanet.com/en/documentation/getting-started/opening-cfo-solution-platform.md#password-policy).
## More User Management Options
By default, the most recently updated users appear at the top of the list of users. You can use the menu of the three dot icon to perform the following actions:
- Edit user
- Resend an invitation e-mail to the user. This option is available when the user has not yet logged into the Lucanet CFO Solution Platform, or when external authentication (SSO) is activated for the user, in which case it remains available even after the user's first login.
- View a user's change log to obtain detailed information about the changes made (for more information on the change log in user administration, see [Change Log](https://support.lucanet.com/en/documentation/administration/user-management/users/change-log.md))
- Reset the TOTP MFA of a user (for more information, see [Resetting TOTP MFA](https://support.lucanet.com/en/documentation/administration/user-management/users/.md#resetting-totp-mfa))
- Delete user.
More user management options
> **Warning:** - The option for activating Lucanet.Certified Professional is only available when creating a user. It is not possible to change this option when editing a user at a later data.
> - Administrators can delete their administrator permissions when editing their own accounts. However, there must still be at least one user in the system who has access to the **Administration** functions.
> - It is possible for multiple users with Administration permissions to edit the same user account simultaneously. Whoever changes are saved first will be applied.
### Resetting TOTP MFA
You can reset the multi-factor authentication for a user, for example if the user no longer has access to their authenticator app or wants to use a different device. The authenticator app is then unlinked, and the user sets up a new authenticator app the next time they log in. The user receives an e-mail with instructions.
To reset the multi-factor authentication for a single user, click **Reset TOTP MFA** in the menu of the three dot icon. The dialog is displayed as follows, for example:
Dialog for resetting TOTP MFA
To reset the multi-factor authentication for several users at the same time, activate the check boxes in front of the users and click **Reset TOTP MFA** (for more information, see [Managing Multiple Users at Once](https://support.lucanet.com/en/documentation/administration/user-management/users/.md#managing-multiple-users-at-once)). The dialog then displays the number of selected users instead of their names, as follows, for example:
Dialog for resetting TOTP MFA for several users
Click **Reset MFA** to confirm.
> **Note:** The **Reset TOTP MFA** option is only available for users for whom multi-factor authentication is activated. Resetting the multi-factor authentication does not change the user's password.
## Filtering Users
You can use the filter icon in the column heading in the user overview to filter the users that have been created so far by **user name**, **e-mail address** or **user role**. This is useful if you only want to view users with a specific role, for example. The filtered column is indicated by the filter icon.
Filtering users
Additionally, it is possible to filter and display the following user attributes using the filter above the list of users:
| Label | Users |
|---------|---------|
| the totp mfa icon | Users for whom TOTP MFA is activated |
| the external authentication icon | Users for whom external authentication is activated |
| the lucanet certified professional icon | Lucanet.Certified Professional users |
| the locked icon | Permanently locked users |
| the license manager icon | Users with the **License Manager** role |
The user labels are displayed as follows, for example:
User labels in the 'Filter by user labels' drop-down list
## Managing Multiple Users at Once
To make user management more efficient, you can select multiple users in the list of users and perform various actions simultaneously. Proceed as follows:
1. Navigate to the workspace **Administration | User management | Users**.
2. In the list of users, activate the check boxes in front of the users you want to manage. If you want to activate multiple check boxes at the same time, you have the following options:
- Activate the check box in the first row to activate all check boxes at the same time.
- Activate the first check box, press the **Shift** key, and then activate the last checkbox.
The number of selected users and the action buttons are then displayed as follows, for example:
Manage multiple users simultaneously
3. Click the appropriate button to perform the following actions:
- Edit users (for more information, see [Bulk Edit Options](https://support.lucanet.com/en/documentation/administration/user-management/users/.md#bulk-edit-options))
- Resend an invitation e-mail to the users. This option is available when the users have not yet logged into the Lucanet CFO Solution Platform, or when external authentication (SSO) is activated for the users, in which case it remains available even after their first login.
- Reset the TOTP MFA of the users (for more information, see [Resetting TOTP MFA](https://support.lucanet.com/en/documentation/administration/user-management/users/.md#resetting-totp-mfa))
- Delete users
### Bulk Edit Options
The following options are available for simultaneous editing of multiple users:
#### Access and roles
Grants or revokes access to a specific solution or to the **Administration** area for all selected users
When granting access, you must define a user role for the respective solution and/or for **Administration**.
Edit user access and user roles for multiple users
#### Other settings
- Enables or disables external authentication for the selected users if an authentication method is configured in the **External Authentication** workspace
- Enables or disables the **Require MFA (authenticator app code)** setting for the selected users. Regardless of the current setting of the selected users, **No changes** is preselected.
- Locks or unlocks all selected users
Edit other settings for multiple users
#### Language and formatting
Defines the default settings for language and formatting, if these settings have not been changed by the user
Change language and formatting settings for multiple users
---
---
title: "Defining Permissions for CFP Data Model Roles"
description: "In the User management workspace of the CFO Solution Platform, you can define read and/or write permissions for data model roles when editing Consolidation & Financial Planning users."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions
language: en
last_updated: 2026-09-30
---
# Defining Permissions for CFP Data Model Roles
## Overview
In the **User management** workspace of the **CFO Solution Platform**, you can define read and/or write permissions for **data model roles** when editing **Consolidation & Financial Planning** users.
> **Warning:** All settings made in the user management of the **CFO Solution Platform** are automatically synchronized with the user management in **Lucanet.Financial Client**, provided that the platform administrator is also assigned the role of **Master** in Lucanet.Financial Client.
## Defining Permissions for CFP Data Model Roles
To define permissions for data model roles:
1. In the **User management** workspace, select the user whose permissions you want to define.
2. Select **Consolidation & Financial Planning,** then use the toggle button to enable **Data model roles.**
3. Select a user role. The **Permissions** link will be displayed at the top right:
User roles for Consolidation & Financial Planning
4. Click **Permissions** to open the dialog for assigning the permissions:
'Permissions' dialog
5. (Optional) Activate the **Grant user full read and write permissions** option, if you want to grant the user full read and write permissions. Note that only **Editor** user roles can be granted full read and write permissions.
6. Define specific permissions in the **My set permissions** column:
- Activate the **Read** check box for the areas where the user is to receive read permission.
- Activate the **Write** check box for the areas where the user is to receive write permission.\
\
For more information on the available categories and permissions, see [Categories and Permissions](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions/.md#categories-and-permissions).
> **Tip:** **Notes on User Permissions:**
>
> - All subordinate and dependent permissions are activated automatically.
> - If a **Write** permission is activated, the **Read** permission will be automatically activated and locked for editing.
> - Users with **Editor** role can be assigned both **Read** and **Write** permissions. Users with **Observer** and **Group report data collector** can only be assiged **Read** permissions.
> - If you set a permission for a section on the **Workspaces** tab that also exists on the **Data Access** tab, the permission will be automatically set for that section too, and vice versa.
## Categories and Permissions
**Permissions** are assigned within **categories**. The relationship between category and permission is as follows:
| Category | Permission |
|---------|---------|
| Workspaces | Defines which **workspaces** and **elements** are visible to the user and which elements in a workspace the user is permitted to create, change, or delete. |
| Data access | Defines which **values** are displayed and which values the user can enter, change, or delete. |
| Other permissions | Defines which **administrative activities** the user can perform and what **additional information** they can access. |
These permission categories and symbols also apply when you configure permissions for a user group (see [Managing User Groups](https://support.lucanet.com/en/documentation/administration/user-management/user-groups.md)).
## Permissions Symbols
'Permissions' table
The following table describes what each symbol in the **Permissions** table represents:
| Symbol | Description |
|---|---|
| the manual permission icon | The permission was activated manually and applies only to the selected element. |
| the automatic permission icon | The permission was activated automatically. It is part of a superordinate permission. |
| the paired permissions icon | The permission was activated automatically. The permission applies to the element and all subordinate elements. |
| the expand permissions icon | Expands all levels in the permissions list. |
| the collapse permissions icon | Collapses all levels to the top level in the permissions list. |
| the display permissions icon | Allows selecting which permissions will be displayed. The following options are available: • **All** - displays all permissions. • **Not set** - displays an overview of all areas that permissions can be assigned for • **My set permissions** - displays only those permissions that have already been assigned to the user. • **Inherited** - displays the permissions inherited from [user groups](https://support.lucanet.com/en/documentation/administration/user-management/user-groups.md). |
| the selected permissions icon | Shows that at least one **read** or **write** permission has been selected in the permissions list. |
---
---
title: "Exchange Rate Management"
description: "The Exchange rate management functional area allows you configure the exchange rates that product solutions on the Lucanet CFO Solution Platform use to convert between currencies."
source_url: https://support.lucanet.com/en/documentation/administration/exchange-rate-management
language: en
last_updated: 2026-06-01
---
# Exchange Rate Management
## Overview
The **Exchange rate management** functional area allows you to configure the exchange rates that solutions on the Lucanet CFO Solution Platform use to convert between currencies. For each currency combination, you choose whether the rates are retrieved automatically from the **European Central Bank** or from an **Excel file** you upload yourself.
> **Note:** Exchange rate management is currently used by the solution Lease Accounting only.
## Prerequisites
To use the **Exchange rate management** functional area, your user account must have access to the **Administration** module in the platform (see [User Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/user-roles.md)).
Exchange rate management is available in the menu under **Administration | Exchange rate management** and contains two workspaces:
- **Exchange rates** — manage currency combinations and view their corresponding rates.
- **Custom upload of exchange rates** — upload your own exchange rate file and review past uploads.
## Adding and Configuring Currency Combinations
> **Warning:** Configuring currency combinations is mandatory. Set up a currency combination for every currency pair that occurs in your lease contracts. Missing combinations affect the calculations for lease components in a foreign currency.
To add one or more currency combinations:
1. Navigate to **Administration | Exchange rate management | Exchange rates**. The **Exchange rates** workspace is displayed as follows, for example:
'Exchange rates' workspace
2. Click **Add currency combinations**. The **Create New Currency Combination(s)** dialog is displayed:
'Create New Currency Combination(s)' dialog
3. In the dialog, fill in the following fields:
- **Currency 1** — the source currency. Start typing to search the list of ISO 4217 currency codes (for example, _EUR - Euro_).
- **Currency 2** — the target currency. Search the same way.
- **Source** — choose where the rates for this combination are retrieved from:
- **European Central Bank** — rates are pulled automatically from the ECB.
- **Exchange rate upload** — rates come from the Excel files you upload in the **Custom upload of exchange rates** workspace (see the following section).
4. Click **Add combination**. The combination is added to the pending list inside the dialog and the input fields are cleared.
Repeat the previous step for every combination you want to add.
5. Once the pending list contains all the combinations you want, click **Save**.
> **Note:** Each combination is bidirectional. When you add **EUR → USD** with the European Central Bank source, **USD → EUR** is configured automatically with the same source. Only one row per pair is displayed in the table, marked with a double-way arrow.
## Uploading Exchange Rates
If any of your currency combinations use the **Exchange rate upload** source, you must provide the rates yourself by uploading an Excel file in the **Custom upload of exchange rates** workspace on a regular basis.
### Downloading the Exchange Rate File Template
Before you upload an exchange rate file for the first time, download the official exchange rate template to make sure your file matches the required structure. To download the exchange rate template:
1. Navigate to **Administration | Exchange rate management | Custom upload of exchange rates**.
2. Click **Download template**. An .XLSX file is downloaded to your computer.
'Custom upload of exchange rates' workspace with the 'Download template' link
3. Open the downloaded exchange rate template and fill in your exchange rates.
Exchange rate file template
> **Note:** The template uses the same structure as the exchange rate file used in Consolidation & Financial Planning. If you already work with that file, you can reuse it directly.
### Uploading the Exchange Rate File
To upload the exchange rate file:
1. In the **Custom upload of exchange rates** workspace, choose one of the following options to upload the file:
- Drag and drop the file onto the upload area.
- Click **choose a file** and pick the file from your file browser.
Only .XLSX files are supported. The maximum file size is approximately 10 MB.
The system validates the file. If any issues are detected, a validation summary is displayed listing the affected rows and the **Import exchange rates** button appears below the summary, or at the bottom of the page, if no summary is shown.
An example of a validation summary after uploading an exchange rate file
2. Click **Import exchange rates.** This triggers the following:
- The validation summary updates to show how many exchange rates were saved. Any skipped rows remain listed in the validation summary.
- The uploaded exchange rate file appears in the **Upload history** table at the bottom of the **Custom upload of exchange rates** workspace.
- The imported exchange rates are stored in the **Exchange rates** workspace under their respective currency combination.
> **Note:** Only exchange rates whose period is up to the current date are imported. Future periods are listed in a warning and skipped automatically.
>
> Exchange rates for currency combinations whose source is set to **European Central Bank** are also skipped — the configured source always takes precedence. You can change the source of a combination in the **Exchange rates** workspace by deleting the combination and re-creating it with the desired source.
## Viewing Exchange Rates for a Currency Combination
Each currency combination accumulates many exchange rates over time — one per date and exchange rate type. These exchange rates appear in the currency combination as soon as they are used in one of your solutions — currently, only in Lease Accounting. You can review the stored rates directly in the **Exchange rates** workspace:
1. Navigate to **Exchange rate management | Exchange rates** and select the currency combination you want to inspect.
2. Review the exchange rates. The detail view includes the date, the rate value, the rate type, and the source.
Exchange rates are sorted by date in descending order by default. Use the filters, sorting, and pagination controls to narrow down what you see.
Detail view of an exchange rate
## Deleting a Currency Combination
To remove a currency combination you no longer need:
1. Navigate to **Administration | Exchange rate management | Exchange rates**.
2. In the **Existing combinations** table, click the **Delete** icon on the row of the combination you want to remove. The **Delete Currency Combination** dialog is displayed:
'Delete Currency Combination' dialog
3. In the **Delete currency combination** dialog, review the consequences listed below, then click **Delete** to confirm:
- Historical exchange rates and any calculations based on historical rates **are not** removed.
- Exchange rates that have already been used in product solutions **remain** in those solutions.
- Future uploads for the deleted combination are blocked until you re-create it.
> **Warning:** Before deleting a currency combination, review which product solutions depend on it. Deleting a combination prevents future exchange rate uploads for that currency pair, but existing values used in dependent solutions are kept as they are.
---
---
title: "Generating and Downloading SEA Certificates"
description: "The Certificates workspace allows administrators to generate and download certificates for Lucanet.Script Execution Application (SEA). These certificates are used to install SEA in Lucanet.Software Manager and to configure SEA applications in Consolidation & Financial Planning within Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/certificates
language: en
last_updated: 2026-05-01
---
# Generating and Downloading SEA Certificates
## Overview
**Lucanet Script Execution Application** ( **SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script.
The **Certificates** workspace allows administrators to generate and download SEA certificates using instances. These certificates are used to install SEA in Lucanet.Software Manager and to configure SEA applications in **Consolidation & Financial Planning** solution of the Lucanet CFO Solution Platform.
## Navigation
To open the **Certificates** workspace:
1. Click **Administration** in the main menu of the CFO Solution Platform.
2. Open the **Platform Management** area and click **Certificates**. The **Certificates** workspace is displayed as follow:
'Certificates' workspace
## Creating an SEA Instance
When generating an SEA instance, the respective certificates are generated for the instance and can be downloaded. To create an SEA instance:
1. Click **Generate instance**.
2. In the displayed **Generate Instance** dialog, enter the name of the instance.
3. Click **Generate**.
> **Warning:** The instance name must adhere to the following criteria:
>
> - The instance name must be unique.
> - Only alphanumeric characters and the special characters '-' and '\_' are allowed.
> - The maximum length is 50 characters.
After an instance is generated, it is displayed in the overview table. The following information is available in the overview table:
| Column | Description |
|---------|---------|
| User name | The user who created the instance. |
| Instance | The name of the SEA instance |
| Activated | The date the instance was created. Once an instance is created, the instance is automatically activated. |
## Downloading Certificates
Click the three dot icon to download the certificates. The following options are available:
| Option | Description |
|---------|---------|
| Download sender | Download the sender certificate for the instance as a ZIP file. This certificate is required for the configuration of the instance in the **Scripts** workspace in the **Import and Journals** functional area in the Consolidation & Financial Planning solution. |
| Download receiver | Download the receiver certificate for the instance as a ZIP file. This certificate is required for the installation of SEA in Lucanet.Software Manager. |
> **Note:** For more information on how to install and update SEA, see [Installing and Updating Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md).
>
> For SEA system requirements, topology, and the ports and endpoints that need to be allowed in your firewall, see [Lucanet SEA: System Requirements and Network Configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea/sea-system-requirements.md).
---
---
title: "Managing API Tokens"
description: "API tokens let you access the user management of the Lucanet CFO Solution Platform programmatically through the Platform API, without an interactive login. Each token is granted specific permissions and can be revoked at any time."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/api-token-management
language: en
last_updated: 2026-06-19
---
# Managing API Tokens
## Overview
An **API token** is an alternative authentication method for accessing the Lucanet CFO Solution Platform programmatically through the Platform API, without an interactive login session. API tokens are typically used to automate user and access management, for example, to connect your central identity system and create, update, or deactivate users automatically.
Each API token has the following characteristics:
- It is **scoped**: each token is granted specific permissions that restrict which endpoints it can access.
- It is tied to a specific **user** and **tenant**. Any action performed with a token is attributed to the user who created it and is recorded in the [Change Log](https://support.lucanet.com/en/documentation/administration/user-management/users/change-log.md).
- It can be given an **expiration date** and can be **revoked** at any time.
> **Warning:** Your API tokens need to be treated as securely as any other password. Anyone who has a token can act on your behalf within the scope granted to it.
## Accessing API Token Management
To open the **API token management** workspace:
1. Click **Administration** in the main menu of the CFO Solution Platform.
2. Open the **User management** area and click **API token management**.
The workspace has two tabs:
| Tab | Content |
|---|---|
| **Tokens** | The list of API tokens that currently exist for your tenant, where you create and revoke tokens |
| **API documentation** | The reference documentation for the Platform API: authentication, available scopes, endpoints, and example requests and responses |
## Viewing Your API Tokens
The **Tokens** tab lists all API tokens for your tenant. The **API token management** workspace is displayed as follows, for example:
The 'API token management' workspace
The following information is available for each token:
| Column | Description |
|---|---|
| Token name | The name given to the token when it was created |
| Created | The date and time the token was created |
| Expires | The date and time the token expires. A dash (—) indicates that the token has no expiration date. |
| Token type | The permissions (scopes) granted to the token: **Read**, **Write**, and/or **Read and write** |
| Actions | The option to revoke an active token. Tokens that can no longer be used are displayed as **Expired** or **Revoked** instead. |
## Creating an API Token
> **Note:** You can only create a maximum of 25 API tokens at a time. New tokens may take up to a minute to work after they have been created.
To create an API token:
1. On the **Tokens** tab, click **Create API token**. The **Create API Token** dialog is displayed as follows, for example:
'Create API Token' dialog
2. Enter a **Token name**. The name must contain at least 8 characters.
3. Optional: Select an **Expiration date**. Tokens without an expiration date are less secure, so we recommend setting one.
4. Under **Scopes of user management**, select the permissions the token should have. You must select at least one scope.
| Scope | Description |
|---|---|
| **Read** | Read-only access to User Management endpoints. |
| **Write** | Write access to User Management endpoints. |
| **Read and write** | Access to User Management bulk operations. |
5. Click **Create**.
6. In the **API Token Created** dialog, click **Copy** to copy the token, and store it in a secure location.
'API Token Created' dialog
7. Select the check box to confirm that you have copied and securely stored the token, and click **Done**.
> **Warning:** The token value is displayed only once, immediately after creation. Copy it before you close the dialog. A lost token value cannot be retrieved; in that case, you have to create a new token instead.
## Revoking an API Token
Revoke a token when it is no longer needed or might be compromised.
1. On the **Tokens** tab, find the token you want to revoke and click **Revoke** in its row.
2. In the **Revoke Token** dialog, click **Revoke token** to confirm.
> **Warning:** Revoking a token cannot be undone. Any integration that uses the token stops working within 60 seconds. The action is recorded in the change log. After revoking, the token is displayed as **Revoked** in the list.
## API Documentation
Open the **API documentation** tab for the full Platform API reference, where API tokens are referred to as **Personal Access Tokens (PATs)**. It includes:
- **Authentication**: pass the token in the `Authorization` header as a Bearer token, in the form `Authorization: Bearer pat__`.
- **Available scopes**: `um:read`, `um:write`, and `um:bulk`, which correspond to the **Read**, **Write**, and **Read and write** options in the token dialog. A token can have one or more scopes. A request to an endpoint the token is not scoped for is rejected with **403 Forbidden**.
- **Endpoints**: the available user management operations (read, write, and bulk), with example requests, responses, and error codes.
Because every action performed with a token is attributed to the user who created it, you can trace API-driven changes in the [Change Log](https://support.lucanet.com/en/documentation/administration/user-management/users/change-log.md).
---
---
title: "Managing Lucanet Licenses"
description: "Overview of licensed solutions, license packages, and license slots in the Lucanet CFO Solution Platform, and self-service license upgrades by License Managers."
source_url: https://support.lucanet.com/en/documentation/administration/platform-management/licenses
language: en
last_updated: 2026-09-30
---
# Managing Lucanet Licenses
## Overview
The **Lucanet licenses** workspace provides an overview of your licensed solutions, their license packages, the used license slots per user role, and their licensed units, where applicable. Each licensed solution is displayed as an expandable card. Users with the **License Manager** role can request license upgrades directly from the Lucanet CFO Solution Platform.
## Navigation
The **Lucanet licenses** workspace can be found under **Administration | Platform management** and is displayed as follows, for example:
'Lucanet licenses' workspace
## Viewing Your Licenses
Your licensed solutions are listed on the **Licensed solutions** tab. The number next to the tab indicates how many solutions you are licensed for.
Use **Expand all** or **Collapse all** in the top right corner to open or close all cards at once, or click the arrow on an individual card to expand it.
An expanded solution card is displayed as follows, for example:
Expanded solution card
Each card displays the following information:
| Element | Description |
|---|---|
| Solution name and icon | The licensed solution |
| License package | The package you have purchased for the solution (for example, **Basic**, **Professional**, or **Advanced**), displayed as a badge next to the solution name. For more information on our license packages, see [Find the perfect solution for your business needs](https://www.lucanet.com/en/pricing/). |
| User role/Usage | The license slots per user role, displayed as *used/total* with a usage bar. When a user role has unlimited license slots, the usage is displayed as *used*/**Unlimited**, and the usage bar remains unfilled. |
| Other/Licensed units | Additional licensed units for the solution, for example the licensed **Reporting entities** for Consolidation & Financial Planning. |
| Upgrade | The option for users with the [License Manager](https://support.lucanet.com/en/documentation/glossary.md#license-manager) role to request a license upgrade for the solution (see [Requesting a License Upgrade](#requesting-a-license-upgrade)). |
> **Note:** **Lucanet.Certified Professional** users do not require license slots. They are not counted in the license overview.
## Usage Limit Warnings
When the license slots for a user role of a solution are used up or are running low, the solution card displays a **Usage limit** badge next to the solution name, together with a warning banner for each affected user role:
| Banner | Description |
|---|---|
| Red | All license slots for the user role are used up. |
| Orange | The user role is about to use up all its license slots. |
If both a red and an orange banner apply at the same time, the **Usage limit** badge reflects the more critical (red) state.
Usage limit warnings are displayed as follows, for example:
Solution card with usage limit warnings
To resolve a limit warning, a user with the **License Manager** role can request a license upgrade for the solution (see [Requesting a License Upgrade](#requesting-a-license-upgrade)).
## Requesting a License Upgrade
You can request license upgrades directly from the Lucanet CFO Solution Platform. The request is automatically forwarded to Lucanet and triggers the relevant approval and provisioning processes.
> **Warning:** **Important:** All license upgrades, extensions, and amendments initiated via the Lucanet CFO Solution Platform are legally binding. License upgrades can therefore only be requested by users with the **License Manager** role (see [User Roles | License Manager](https://support.lucanet.com/en/documentation/administration/user-management/users/user-roles.md#license-manager)). Make sure that the person requesting the upgrade is authorized to make contractual commitments.
To request a license upgrade:
1. Navigate to **Administration | Platform management | Lucanet licenses**.
2. On the card of the desired solution, click **Upgrade**. The **Request License Upgrade** dialog opens and is displayed as follows, for example:
'Request License Upgrade' dialog
3. In the **Order details** area, specify the desired components and quantities. The available components depend on the respective solution. The prices displayed are based on your current contract.
4. In the **Summary** area, review the automatically calculated overview of the selected components and the monthly total fee.
5. Optional: In the **Purchase order** field, enter a purchase order number that should appear on your invoice.
6. Activate the check box to confirm that the automated upgrade request via the Lucanet CFO Solution Platform constitutes a binding contract amendment.
7. Click **Send request**.
You will receive an e-mail and an in-app notification once your request has been processed. After the upgrade is activated in your environment, the additional license slots and reporting entities are displayed in the **Lucanet licenses** workspace.
> **Warning:** - In the Lucanet CFO Solution Platform, you can only add license slots. To reduce or remove license slots, please contact your Lucanet representative.
> - Only one license upgrade request per solution can be processed at a time. While an upgrade request is being processed, the **Upgrade** option for the respective solution is disabled. Once the request is completed, you can submit a new request.
## Activating and Deactivating the AI Features
On the **AI in the CFO Solution Platform** card, users with the **License Manager** role can activate and deactivate [Lucanet Lume](https://support.lucanet.com/en/documentation/lume.md), the [agents](https://support.lucanet.com/en/documentation/lume/agents.md), and all other AI features. For all other users, the card only displays the current status of the AI features. For more information, see [User Roles | License Manager](https://support.lucanet.com/en/documentation/administration/user-management/users/user-roles.md#license-manager).
The card is displayed as follows, for example:
'AI in the CFO Solution Platform' card with the status 'On'
To activate or deactivate the AI features:
1. Navigate to **Administration | Platform management | Lucanet licenses**.
2. On the **AI in the CFO Solution Platform** card, change the status.
3. Confirm the change with **Proceed**.
When you activate the AI features, you consent to the use of AI across your Lucanet solutions.
> **Warning:** If you deactivate the AI features, all users lose access to Lucanet Lume and to all agents. You can activate the AI features again at any time.
The change is processed in the background. During this time, the status cannot be changed again, also not by other License Managers.
> **Note:** All users receive a notification when the AI features are activated or deactivated.
>
> For users who log in after the change, the new status applies immediately. For users who are logged in at the time of the change, the new status applies as soon as their session ends. To apply the new status right away, these users can log out and log in again.
---
---
title: "Managing the CFO Solution Platform"
description: "The ‘Platform management’ functional area of the Administration area in the Lucanet CFO Solution Platform allows you to view your license information and manage your external authentication."
source_url: https://support.lucanet.com/en/documentation/administration/platform-management
language: en
last_updated: 2026-10-05
---
# Managing the CFO Solution Platform
## Overview
The **Platform Management** allows you to configure central settings for the Lucanet CFO Solution Platform and includes the following workspaces:
- The **Lucanet licenses** workspace provides an overview of your licensed solutions, their license packages, the used license slots per user role, and the licensed reporting entities. Users with the **License Manager** role can request license upgrades directly from the Lucanet CFO Solution Platform (see [Managing Lucanet Licenses](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md)).
- In the **External Authentication** workspace, you can configure that a user is authenticated via a central instance in the network (see [Configuring External Authentication](https://support.lucanet.com/en/documentation/administration/platform-management/configure-ext-authentication.md)).
- The **Certificates** workspace allows administrators to generate and download SEA certificates using instances. These certificates are used to install SEA in Lucanet.Software Manager and to configure SEA applications in **Consolidation & Financial Planning** solution of the Lucanet CFO Solution Platform (see [Generating and Downloading SEA Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md)).
- In the **Customization** workspace, you as an **administrator** can customize certain elements of the Lucanet CFO Solution Platform to match your corporate design. Currently, you can upload your company logo and configure it for use in e-mail templates (see [Configuring Customizations](https://support.lucanet.com/en/documentation/administration/platform-management/customization.md)).
---
---
title: "Managing User Groups"
description: "With user groups, you can combine Consolidation & Financial Planning users and assign shared permissions to all members at once, instead of configuring each user individually."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/user-groups
language: en
last_updated: 2026-09-17
---
# Managing User Groups
## Overview
With user groups, you can combine Consolidation & Financial Planning users and assign shared permissions to all members at once, instead of configuring each user individually. You can create and manage user groups in **Administration | User management | User groups**.
For each user group, you can:
- Define **permissions** for the data model (Workspaces, Data access, and Other permissions).
- **Transfer** the group's permissions to individual users or other user groups, optionally for a limited period.
- **Receive** permissions from other user groups (inheritance).
- Review the **change log** of the group.
> **Note:** Currently, user groups manage permissions for **Consolidation & Financial Planning** and are available to platform administrators with the **Administrator** or **Master** role for Consolidation & Financial Planning. For users who only have the **Observer** role for user management, the **User groups** menu item is not displayed. All settings made for user groups on the Lucanet CFO Solution Platform are automatically synchronized with Lucanet.Financial Client, provided that the platform administrator is also assigned the **Master** role in Lucanet.Financial Client.
## Creating a User Group
To create a user group:
1. Navigate to **Administration | User management | User groups**.
2. Click **Create new user group**. The **Create User Group** panel is displayed as follows, for example:
'Create User Group' side panel
3. Enter a name in the **User group name** field. The name is mandatory and must be unique.
4. Click **Save**.
The user group is created and displayed in the list of user groups. You can now configure the group's permissions and assign users (see [Configuring User Group Permissions](#configuring-user-group-permissions)).
## Working with the User Groups List
The list of user groups displays the following information:
| Column | Description |
|---|---|
| User group | The name of the user group |
| Users and user groups | The number of users and user groups that the group's permissions are transferred to |
| Last edit date | The date and time the user group was last changed |
By default, the most recently edited user groups are displayed at the top of the list. You can filter the list by user group name and sort by last edit date.
To manage an existing user group, open the menu of the three dot menu icon in the group's row:
- **Edit user group** opens the **Edit User Group** panel (see [Configuring User Group Permissions](#configuring-user-group-permissions)).
- **Change log** opens the change log of the group (see [Viewing the Change Log of a User Group](#viewing-the-change-log-of-a-user-group)).
- **Delete user group** deletes the group after you confirm.
To delete several user groups at once, activate the check boxes in front of the relevant groups and click **Delete user groups** at the top right.
## Configuring User Group Permissions
To configure a user group, select the user group in the list to open the **Edit User Group** panel. In addition to the **User group name**, the panel provides the following tabs:
| Tab | Description |
|---|---|
| Workspaces | Defines which workspaces and elements the group's permissions apply to |
| Data access | Defines which values the group can display, enter, change, or delete |
| Other permissions | Defines which administrative activities the group can perform and what additional information it can access |
| Permissions transferred | Transfers the group's permissions to users or other user groups (see [Transferring Permissions](#transferring-permissions)) |
| Permissions received | Receives permissions from other user groups (see [Receiving Permissions](#receiving-permissions)) |
To define permissions, open the **Workspaces**, **Data access**, or **Other permissions** tab and activate the **Read** and/or **Write** check boxes in the **My set permissions** column for the relevant areas. Permissions inherited from other user groups are displayed in the **Inherited** column.
The **Workspaces** permission tab is displayed as follows, for example:
'Workspaces' permission tab of a user group
> **Note:** The permission categories (**Workspaces**, **Data access**, **Other permissions**) and the permission symbols work exactly the same way as when you define permissions for an individual user. For a description of the categories and symbols, see [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md).
## Transferring Permissions
On the **Permissions transferred** tab, you can transfer the user group's permissions to individual users or to other user groups, optionally for a limited period. The tab is displayed as follows, for example:
'Permissions transferred' tab
To transfer the group's permissions:
1. In the **Edit User Group** panel, open the **Permissions transferred** tab.
2. Click **+ Add row(s)** and select the **user or user group** that should receive the permissions.
3. (Optional) Limit the validity period by entering a date in the **Assigned since** and **Assigned until** columns. If you leave **Assigned until** empty, the permissions are assigned with no end date (Unlimited).
4. Click **Save**.
> **Warning:** A user group's permissions are added to a user's own permissions, but a user can never receive more permissions than their **user role(s)** allow. For example, a user with the **Observer** role keeps read-only access even if a user group transfers write permission to that user.
## Receiving Permissions
On the **Permissions received** tab, a user group can inherit the permissions of one or more other user groups. The columns work the same way as on the **Permissions transferred** tab, except that only **user groups** can be selected. The tab is displayed as follows, for example:
'Permissions received' tab
To receive permissions from another user group:
1. In the **Edit User Group** panel, open the **Permissions received** tab.
2. Click **+ Add row(s)** and select the **user group** whose permissions should be inherited.
3. (Optional) Limit the validity period by entering a date in the **Assigned since** and **Assigned until** columns. If you leave **Assigned until** empty, the permissions are assigned with no end date (Unlimited).
4. Click **Save**.
> **Warning:** Changes to user group permissions take effect only after the affected users have logged out and logged back in.
## Viewing the Change Log of a User Group
To review the changes made to a user group, click the three dot icon in the group's row and choose **Change log**. The **Change Log** dialog is displayed as follows, for example:
'Change Log' dialog for a user group
The change log lists actions such as a user group being created or edited, elements (users or user groups) being added to or removed from the group, and the user group itself being added to or removed from another user group. Depending on the action, the **Name**, **Element**, **Group**, and **Parent** columns identify the affected user group, member, or related group. You can sort and filter the **Time**, **User**, and **Action** columns.
> **Note:** Changes to read and write permissions are not recorded in the user group change log.
---
---
title: "User Management"
description: "In the 'User management' section of the Administration area, you manage users, user groups, and API tokens for the Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/administration/user-management
language: en
last_updated: 2026-06-23
---
# User Management
## Overview
In the **User management** section of the **Administration** area, you can manage who can access the Lucanet CFO Solution Platform and what they are allowed to do. It includes the following workspaces:
- In the **Users** workspace, you can create and edit users, grant access to solutions and the Administration area, assign user roles, and review the change log of the changes made to users. For Consolidation & Financial Planning users, you can also define data model permissions (see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management/users.md)).
- In the **User groups** workspace, you can combine Consolidation & Financial Planning users into groups and assign shared permissions to all members at once, instead of configuring each user individually (see [Managing User Groups](https://support.lucanet.com/en/documentation/administration/user-management/user-groups.md)).
- In the **API token management** workspace, you can create and revoke scoped API tokens for automating user and access management through the Platform API (see [Managing API Tokens](https://support.lucanet.com/en/documentation/administration/user-management/api-token-management.md)).
---
---
title: "User Roles"
description: "Overview of all user roles in the Lucanet CFO Solution Platform: roles for Administration (Administrator, License Manager) and solution-specific roles."
source_url: https://support.lucanet.com/en/documentation/administration/user-management/users/user-roles
language: en
last_updated: 2026-09-30
---
# User Roles in the CFO Solution Platform
## Overview
There are two types of user roles in the Lucanet CFO Solution Platform:
- **User roles for Administration**: Control access to the workspaces under **Administration**.
- **User roles for individual solution**: Determine permissions within an individual solution. They are assigned individually per solution.
## User Roles for Administration
User roles for Administration are assigned when you grant a user access to the **Administration** area. The following user roles are available for Administration:
### Administrator
Users with the **Administrator** role manage the Lucanet CFO Solution Platform and have access to all workspaces under **Administration**:
- **User management**: Creating, editing, and deleting users and user groups
- **Platform management**: Viewing Lucanet licenses, configuring external authentication, managing certificates, and configuring customizations
For the **Consolidation & Financial Planning** solution, an Administrator also needs the CFP role **Master** or **Administrator** to manage user roles.
### License Manager
Users with the **License Manager** role act as authorized representatives with contractual authority. They are authorized to initiate binding license upgrades, extensions, and changes via the Lucanet CFO Solution Platform. All actions performed by **License Manager** users are legally binding. Grant this role only to users authorized to enter into contractual commitments.
**Permissions:**
The permissions of a License Manager depend on whether they also have the **Administrator** role:
- **License Manager only** (without **Administrator**): Sees only the **Lucanet licenses** workspace in the **Administration** area and can request license upgrades there (see [Managing Lucanet Licenses](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md)).
- **License Manager and Administrator**: Can additionally assign the **License Manager** role to other users and perform all other Administrator tasks.
A License Manager can also activate and deactivate the AI features of the Lucanet CFO Solution Platform in the **Lucanet licenses** workspace. For more information, see [Managing Lucanet Licenses | Activating and Deactivating the AI Features](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md#activating-and-deactivating-the-ai-features).
The initial assignment of the **License Manager** role is made by Lucanet during onboarding.
> **Warning:** There must always be at least one user with the **License Manager** role in your environment.
## User Roles for Individual Solutions
Each solution has its own user roles, which define which tasks a user can perform within that solution.
### Consolidation & Financial Planning
There are two sets of user roles available for the Consolidation & Financial Planning solution:
- **Data model** roles
- **Editor**: Editors have read and write permissions for all workspaces or certain workspaces within the Lucanet data model.
- **Group Report data collector**: Group report data collectors have read permission for the Lucanet data model. They can also execute all tasks required to collect data in relation to Lucanet.Group Report.
- **Observer**: Observers have read permission for all workspaces or certain workspaces within the Lucanet data model.
> **Note:** You can assign detailed permissions for accessing the data model in the CFO Solution Platform for users created in **Consolidation & Financial Planning** (see [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md)).
- **User management** roles
- **Master**: Masters have unrestricted write and read permissions for user management. There must be at least one Master per database.
- **Administrator**: Administrators have write and read permissions for user management. Administrators can, similarly to the master role, manage all users and user groups, but have more limited permissions than masters. An administrator is only able to assign the permissions defined by the master.
- **Observer**: Observers have read permission for user management.
> **Warning:** These **user management roles** apply to user management in Lucanet.Financial Client. In the Lucanet CFO Solution Platform, access to **Administration** is required to manage users. To manage Consolidation & Financial Planning roles and permissions, platform administrators also need either the **Master** or **Administrator** user management role described above.
### Lease Accounting
- **Data collector**: The **Data collector** role is designed for users responsible for gathering and entering lease contract information into the system.
- **Executive reviewer**: The **Executive reviewer** role is intended for users who oversee lease accounting processes, approve critical operations, and perform final steps including posting.
- **Lease operations administrator**: The **Lease operations administrator** role is designed for users who manage day-to-day lease accounting operations with extensive functional access, comprising the permissions of both Data collector and Executive reviewer roles.
- **Auditor**: The **Auditor** role provides comprehensive read access across the system for audit and compliance purposes.
- **Settings administrator**: The **Settings administrator** role is specialized for users responsible for system configuration and maintenance.
- **Full access administrator**: The **Full access administrator** role provides the highest level of system access for comprehensive administration. Full access administrators can create, assign, update, and manage users for the Lease Accounting solution from the Administration workspace in the platform.
> **Note:** In addition to the user role, you can define which reporting entities a user can access in **Lease Accounting** (see [Assigning Reporting Entities to Lease Accounting Users](https://support.lucanet.com/en/documentation/administration/user-management/users/assigning-reporting-entities.md)).
### xP&A
- **Administrators:** Administrators can:
- Create, edit, and share models.
- Add and remove people to and from the organization
- Create teams, e.g. **Finance Team** or **Marketing** Team.
- **Editors**: Editors can:
- Create, edit, and share models
- Create proposals and accept proposals on the model
- **Data collectors**: Data collectors can propose edits to models with some other actions allowed. They **can:**
- Write comments
- Annotate charts
- Propose changes to variables and dimension items
- Propose to add, rename, delete or link dimension items\
\
But they **cannot:**
- Add, delete, or update visuals, variables, groups, and sections
- Add, delete, or update models, folders, or data sources
- **Viewers**:
- **Can** view dashboards shared with the organization but **cannot** access underlying models to make changes.
- **Can** create their own models, but **cannot** share models with the organization.
> **Note:** **Notes**:
>
> - You can add viewers to your organization for free.
> - If a user is a **viewer**, they will only ever be able to view the model dashboards of the models that are shared within the organization.
> - If a user is an **editor**, they will have view and edit access to models or views shared within the organization.
### ESG Reporting
**Administrator**: Users with the **ESG Administrator** user role can perform the following tasks:
- Accessing the ESG reports overview and the state of data collection
- Creating new ESG reports
- Administrating master data
- Configuring the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) questionnaire
- Checking, approving and rejecting submitted ESG reports
- Starting data aggregation
**Data collector**: Users with the **ESG Data collector** user role can perform the following tasks:
- Entering data in the ESG report to which the Data Collector has been assigned
- Submitting data for checking
- Viewing the state of data collection for the ESG report to which the Data Collector has been assigned
For more information on user roles in the **ESG Reporting** solution, see [User Roles and User Interface in ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting/user-roles-esgrep.md).
### Disclosure Management
- **Administrator**: Automatically receives the role of **Global Administrator** within the Disclosure Management solution, along with all solution-wide and cross-document administrative permissions.\
\
This means he can, for example, display, edit, and delete all documents, edit the global settings, and assign user roles to himself and all other users within Disclosure Management.\
\
At least one user with the **Administrator** role must be created for Disclosure Management.
- **Editor**: Automatically receives the role of **Global Editor** within the Disclosure Management solution.
- **Reviewer**: Automatically receives the role of **Global Reviewer** within the Disclosure Management solution.
- **Reader**: Automatically receives the role of **Global Reader** within the Disclosure Management solution.
- **No specific role**: These users initially receive no specific role within the Disclosure Management solution. Only when a user role is assigned by a **Global Administrator** can different permissions be assigned.
For more information on the specific permissions of each role, see [Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md).
### XBRL Tagger
**Administrator**: Users with the **Administrator** role have full access to all documents in the XBRL Tagger. They can view and perform all actions on all documents in the company, and assign roles and documents to other users.
**Editor**: The **Editor** is the standard user role. Users with this role can perform all available actions within the documents they have created or to which they have been invited.
### Banking & Cash Management
- **Administrator**: Users with the **Administrator** role are granted comprehensive access to Banking & Cash Management. Administrators can view all data, including financial figures and identities, and access all configuration settings—such as users, channels, bank profiles, and accounts. This is the most powerful role in the solution and becomes fully operational after completing the initial user creation process.
- **No specific role**: Users assigned with **No specific role** receive the **Essential** role within the Banking & Cash Management solution and have only the most basic permissions. This allows access to the user interface and their own profile, without permission to view data or use any functions.\
\
For a user with **No specific role** to be able to access data or perform any actions in the solution, the **Administrator** must grant the necessary permissions. Depending on requirements, the Administrator can enable access to selected identities, functionalities (such as processing payments or reviewing account statements), or authorization processes.
### Data Collection
**Administrator**: The **Administrator** role is designed for users responsible for setting up and managing the **Data Collection** environment. Administrators configure all elements required before data collection can begin, including form templates, validation rules, and reporting packages.
**Data Collector**: The **Data Collector** role is designed for users who participate in the data collection process. Data Collectors do not have access to the **Administration** section (form templates, validation rules, reporting entities, and reporting packages). Depending on their reporting entity-level assignment, **Data Collectors** can enter data, submit forms for approval, or review and approve submitted data.
For more information on user roles in the **Data Collection** solution, see [User Roles in Data Collection](https://support.lucanet.com/en/documentation/data-collection/user-roles-in-data-collection.md).
---
## Data Hub
Data Hub brings the management of external data integrations together in one central place on the Lucanet CFO Solution Platform. You connect to external source systems, define which data to import, run imports, and monitor their results.
---
title: "Data Hub"
description: "Data Hub brings the management of external data integrations together in one central place on the Lucanet CFO Solution Platform. You connect to external source systems, define which data to import, run imports, and monitor their results."
source_url: https://support.lucanet.com/en/documentation/data-hub
language: en
last_updated: 2026-09-18
---
# Data Hub
## Overview
Data Hub brings the management of external data integrations together in one central place on the Lucanet CFO Solution Platform. You can open **Data Hub** from the main menu.
Data Hub is displayed as follows, for example:
Data Hub in the main menu of the Lucanet CFO Solution Platform
Data integration in Data Hub follows three steps, each covered on its own page:
1. [**Managing Connections**](https://support.lucanet.com/en/documentation/data-hub/managing-connections.md): A connection specifies the authentication settings Data Hub uses to access an external source system, such as SAP S/4HANA, Microsoft Dynamics 365, or an SQL database accessed through JDBC.
2. [**Managing Source Datasets**](https://support.lucanet.com/en/documentation/data-hub/managing-source-datasets.md): A source dataset specifies which data is to be imported. Each source dataset relates to one connection.
3. [**Importing Data**](https://support.lucanet.com/en/documentation/data-hub/importing-data.md): An import extracts and loads the data from the source system and records each execution in the execution history, where you can track its progress and results.
> **Note:** Data Hub supports connections to SAP S/4HANA, Microsoft Dynamics 365, and SQL databases. Support for additional source systems and Lucanet solutions is planned. Data Hub is activated by Lucanet and is being rolled out gradually, so it is not yet visible for every customer.
---
---
title: "Importing Data"
description: "An import extracts the data defined in a source dataset from the source system and loads it into the Lucanet solutions that use the data. You can start imports at any time and track their results in the execution history."
source_url: https://support.lucanet.com/en/documentation/data-hub/importing-data
language: en
last_updated: 2026-09-09
---
# Importing Data
## Overview
An import extracts the data defined in a source dataset from the source system and loads it into the Lucanet solutions. You can start an import at any time and track its progress and results in the execution history of the source dataset.
If the source dataset uses variables, you can select which data to import every time you start the import, for example the data of a specific period or company. For more information, see [Variables](https://support.lucanet.com/en/documentation/data-hub/managing-source-datasets.md#variables).
## Starting an Import
To start an import:
1. On the **Integrations** page, click the three dot icon in the row of the source dataset you want to import.
2. Select **Start import**. If the source dataset uses no variables, Data Hub executes the import immediately.
If the source dataset uses variables, the **Start Import Execution** dialog is displayed as follows, for example:
'Start Import Execution' dialog of a source dataset with two variables
3. In the **Start Import Execution** dialog, select a value for every variable of the source dataset, then click **Execute**.
Data Hub imports the data and records the execution in the execution history of the source dataset.
> **Note:** For a source dataset with variables, every combination of values is imported separately. A source dataset with the variables `Period` and `Company` imports the data of one period for one company at a time, for example. If you start the import again with the same two values, the new data replaces the data of the previous import. If you start the import for another period, the data of that period is added to the data that is already there. This way, you can update the data of a single period for a single company without importing everything again.
## Viewing Execution Details
The execution details show the results of the imports of a source dataset. To open the execution details, click the three dot icon in the row of the source dataset and select **View execution details**.
The execution details are displayed as follows, for example:
Execution details of a source dataset
The top of the page displays the source system, the user who created the source dataset, and the time of the last execution. The **Execution history** table below lists every execution:
| Column | Description |
|---|---|
| Start date | Date and time the import started |
| End date | Date and time the import ended |
| Duration | Duration of the import |
| Triggered by | User or process that started the import |
| Status | Result of the import |
| Execution ID | Unique identifier of the import execution |
## Import Statuses
An import can have one of the following statuses:
| Status | Description |
|---|---|
| Running | The import is currently in progress. |
| Succeeded | The import completed successfully. |
| Failed | The import did not complete because an error occurred. |
| Aborted | The import was stopped before it completed. |
---
---
title: "Managing Connections"
description: "A connection specifies the authentication settings Data Hub uses to access an external source system such as SAP S/4HANA or Microsoft Dynamics 365. You can create and manage connections on the 'Integrations' page."
source_url: https://support.lucanet.com/en/documentation/data-hub/managing-connections
language: en
last_updated: 2026-09-09
---
# Managing Connections
## Overview
A connection specifies the authentication settings Data Hub uses to access an external source system, such as SAP S/4HANA, Microsoft Dynamics 365, or an SQL database accessed through JDBC.
You can manage connections on the **Integrations** page, which you open from the **Data Hub** in the main menu. The page lists every connection together with its source datasets: each connection is a parent row that you can expand to display the source datasets that use it.
The **Integrations** page is displayed as follows, for example:
Connections and their source datasets on the 'Integrations' page
The overview table on the **Integrations** page provides the following information for each connection:
| Column | Description |
|---|---|
| Connection name, Number of associated data sources | Name of the connection and the number of source datasets that use it |
| Source system | External system the connection is established to, for example SAP S/4HANA, Microsoft Dynamics 365, or an SQL database |
| Status | Status indicating whether the connection is active or inactive |
| Created by | User who created the connection |
| Import | Status of the most recent import of the connection's source datasets |
## Creating a Connection
To create a connection:
1. In the main menu, select **Data Hub**. The **Integrations** page is displayed.
2. In the top-right corner, click **Create new connection**. The connection form is displayed as follows, for example:
Connection form with the source-system selection
3. Select the source system you want to connect to: **SAP S/4HANA**, **Microsoft Dynamics 365**, **Microsoft SQL Server (JDBC)**, **Oracle Database (JDBC)**, or **PostgreSQL (JDBC)**.
For the selected source system, the **Version** of its connection template is displayed in the top-right corner of the **Source system** area.
4. Enter the connection settings for the selected source system. For more information, see [Connection Settings](#connection-settings) below.
5. Click **Create**. The connection is created and displayed on the **Integrations** page.
## Connection Settings
The connection settings depend on the source system you want to extract the data from.
### General Settings
The following options are the same for every source system:
| Option | Description |
|---|---|
| Connection name | Name that identifies the connection on the **Integrations** page. Required. |
| SEA instance | Instance of the **Lucanet.Script Execution Application** ([SEA](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)) that runs the connection. Required. |
| Description | Optional description of the connection |
### System-Specific Settings
All other settings are provided by the connection template of the selected source system and are grouped by purpose. The values for these settings come from the source system.
The connection settings are displayed as follows, for example:
Connection settings of an SAP S/4HANA connection
#### SAP S/4HANA
**'General' Area**
The following option is available in the **General** area:
| Option | Description |
|---|---|
| Language | Login language for the SAP system |
**'Authentication' Area**
The following options are available in the **Authentication** area:
| Option | Description |
|---|---|
| Host | Host name or IP address of the SAP server |
| Instance number | Two-digit instance number of the SAP application server, for example 00 |
| Client | Three-digit number of the SAP client that the login refers to, for example 100 |
| User | User name for the login to the SAP system |
| Password | Password of that user |
#### Microsoft Dynamics 365
**'Authentication' Area**
The following options are available in the **Authentication** area:
| Option | Description |
|---|---|
| Endpoint | URL of the Microsoft Dynamics 365 service the data is read from |
| Client ID | ID of the application that Data Hub signs in with |
| Client Secret | Secret of that application |
| Tenant ID | ID of the tenant of your Microsoft Dynamics 365 environment |
| Resource | Resource the access is requested for |
| X-API-Key | API key that the endpoint requires |
**'Network' Area**
The following options are available in the **Network** area:
| Option | Description |
|---|---|
| Connection timeout | Time after which establishing the connection is aborted |
| Read timeout | Time after which reading the data is aborted |
#### SQL Databases
The SQL databases **Microsoft SQL Server (JDBC)**, **Oracle Database (JDBC)**, and **PostgreSQL (JDBC)** are connected through JDBC. The same settings are available for all three source systems.
**'Connection' Area**
The following option is available in the **Connection** area:
| Option | Description |
|---|---|
| URL | JDBC connection URL of the database, including the host, the port, and the name of the database |
The format of the URL depends on the database, for example:
- Microsoft SQL Server: `jdbc:sqlserver://hostname:1433;databaseName=myDatabase`
- Oracle Database: `jdbc:oracle:thin:@//hostname:1521/servicename`
- PostgreSQL: `jdbc:postgresql://hostname:5432/mydatabase`
**'Authentication' Area**
The following options are available in the **Authentication** area:
| Option | Description |
|---|---|
| User | User name for the login to the database |
| Password | Password of that user |
## Additional Options for a Connection
You can manage an existing connection from the three dot icon in the row of the connection on the **Integrations** page. The following options are available:
| Option | Description |
|---|---|
| Edit | Option to view and change the connection's settings |
| Create new dataset | Option to define a source dataset for the connection. For more information, see [Managing Source Datasets](https://support.lucanet.com/en/documentation/data-hub/managing-source-datasets.md). |
| Deactivate / Activate | Option to set the connection to **Inactive** or back to **Active**. While a connection is inactive, it cannot be used for imports, and all its source datasets are inactive as well. |
| Delete | Option to delete the connection. You can only delete a connection which is not used by any source dataset. |
> **Warning:** When you deactivate a connection that still has active source datasets, you must confirm the change, and the connection together with all its source datasets is set to **Inactive**. Activating a connection again does not automatically reactivate its source datasets. You cannot deactivate a connection or source dataset while one of its imports is running or queued.
---
---
title: "Managing Source Datasets"
description: "A source dataset specifies which data to import from a source system. You can define one or more source datasets for a connection, with configuration options that depend on the source system."
source_url: https://support.lucanet.com/en/documentation/data-hub/managing-source-datasets
language: en
last_updated: 2026-09-09
---
# Managing Source Datasets
## Overview
A source dataset specifies which data to import from a source system. Each source dataset belongs to a connection, and a connection can have one or more source datasets. On the **Integrations** page, each source dataset is displayed as a child row of the connection it uses.
## Creating a Source Dataset
To create a source dataset:
1. On the **Integrations** page, click the three dot icon in the row of the connection you want to use to import data and select **Create new dataset**.
2. Specify the options of the source dataset.
3. Click **Create**. The source dataset is created and displayed under the selected connection on the **Integrations** page.
The following options are available for a source dataset:
| Option | Description |
|---|---|
| Name | Name that identifies the source dataset on the **Integrations** page. Required. |
| Connection | Connection to the system the data is imported from. Required.
**Note:** The connection you create the source dataset from is preselected. If necessary, you can select a different connection from the drop-down list. The **Configuration** area then displays the options of the selected source system. After the source dataset is created, the connection can no longer be changed.
|
| Namespace | Technical identifier for the source dataset, used to reference its data tables in SQL queries against the [Data Lake](https://support.lucanet.com/en/documentation/glossary.md#data-lake) (for example, namespace.table_name). The namespace can have up to 255 characters and must be SQL-safe, with no spaces or unsupported special characters. Required. |
| Variables | Optional placeholders in the configuration whose values are selected every time an import is started. For more information, see [Variables](#variables) below. |
| Configuration | Data to import from the source system. Required. For more information, see [Source Dataset Configuration](#source-dataset-configuration) below. |
## Variables
A variable is a placeholder in the configuration of a source dataset. Instead of a fixed value, you can enter the variable in the configuration and select a value for the variable every time you start an import. This way, a single source dataset can import the data of a specific period or a specific company, without a separate source dataset for every combination.
The **Variables** area is displayed as follows, for example:
Variables area of a source dataset
You can define the variables either while you create the source dataset or later, using the **Edit** option. Click **Add variable** and specify the following for each variable:
| Option | Description |
|---|---|
| Variable name | Name of the variable, used to reference the variable in the configuration of the source dataset |
| Display name | Name that is displayed for the variable when an import is started, for example `Period` |
| Data type | Data type of the values. Currently, only **String** is available. |
| Selection type | Number of values that can be selected for one import: • **Single value**: Exactly one value can be selected. • **Set of values**: Several values can be selected. The import extracts the data for each of the selected values separately. |
To define the values that can be selected for a variable:
1. In the row of the variable, click **Configure values**.
2. Click **Add value** and specify the following:
- **Label**: Text that is displayed for the value when an import is started, for example `January`.
- **Value**: Value that replaces the variable in the configuration when the import is executed, for example `01`.
3. Click **Save**.
The allowed values of a variable are displayed as follows, for example:
Allowed values of the variable 'Period'
To remove a variable from the source dataset, click the trash bin icon in the row of the variable.
In the options of the **Configuration** area, you can enter a variable in a text field or in a table cell. Write the variable name in double curly brackets, for example `{{PERIOD}}`.
> **Note:** Every variable of a source dataset requires a value before an import can be executed. For more information, see [Importing Data](https://support.lucanet.com/en/documentation/data-hub/importing-data.md).
## Source Dataset Configuration
The configuration of a source dataset defines which data is imported. The connection template of the source system determines which tabs the **Configuration** area displays and which options each tab contains. The configuration of an SAP S/4HANA source dataset therefore differs from the configuration of a Microsoft Dynamics 365 source dataset, and the options can change with the version of the connection template.
The **Configuration** area of an SAP S/4HANA source dataset is displayed as follows, for example:
Configuration of an SAP S/4HANA source dataset
The following tabs are available in the **Configuration** area:
| Tab | Description |
|---|---|
| General configuration | Technical settings of the import |
| Custom RFC | Settings for importing the result of a function module that is implemented in the SAP system |
| EXECUTE_SELECT query | Settings for importing the result of an SQL query against the tables of the SAP database |
The options of the configuration can contain variables. For more information, see [Variables](#variables).
## Additional Options for a Source Dataset
You can manage an existing source dataset from the three dot icon in the row of the source dataset on the **Integrations** page. The following options are available:
| Option | Description |
|---|---|
| Start import | Option to start an import for the source dataset. For more information, see [Importing Data](https://support.lucanet.com/en/documentation/data-hub/importing-data.md). |
| View execution details | Option to display the execution history of the source dataset. For more information, see [Importing Data](https://support.lucanet.com/en/documentation/data-hub/importing-data.md). |
| Edit | Option to display and change the settings of the source dataset |
| Deactivate / Activate | Option to set the source dataset to **Inactive** or back to **Active**. An inactive source dataset cannot be imported. |
| Delete | Option to delete the source dataset |
> **Warning:** After the first import, a source dataset can no longer be edited. Before the first import, all options except the connection can still be changed.
---
## Consolidation & Financial Planning
Visualize data on the go, present analyses and reports simply at the touch of a button, put business decisions on a valid basis: With Lucanet Consolidation & Financial Planning, you have exactly the right tool for this. Display the most important key figures and comparison views in a dashboard. Access your reporting data in the shortest possible time - with maximum data security.
---
title: "Accounting Rules"
description: "The Accounting rules workspace is used for configuring rules for automatic contra entries. For each combination of data level and reporting entity, a journal exists in this workspace which contains all of the accounting rules for the respective combination pair."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules
language: en
last_updated: 2026-05-01
---
# Accounting Rules
## Overview
The **Accounting rules** workspace is used for configuring rules for automatic contra entries. For each combination of data level and reporting entity, a journal exists in this workspace which contains all of the accounting rules for the respective combination pair.
In Lucanet, one-sided postings (only one account is addressed on the credit or debit side) can be made by means of **Sheets** or **Excel** using the keyword **auto posting**. However, since postings in Lucanet can only be saved if the credit side matches the debit side, an automatic contra entry must be made at the same time in case of a one-sided posting. This entry is made by the system using accounting rules that were defined for the corresponding accounts in the **Accounting rules** workspace. The system uses automatic contra entries in the following cases:
- Data imports of import type **Automatic posting**
- Excel postings using the keyword **Auto posting**
- Sheets (except **Balance sheet adjustment**)
- Posting with access to the account hierarchy _name of the general ledger_ **incl. subledgers (automatic posting)**
Automatic contra entries can be used to plan only one profit and loss statement from which a planning balance sheet and a planning cash flow statement are automatically created by the system based on defined accounting rules.
## Navigation
The **Accounting rules** workspace can be found in the **Overview** under the **Planning** folder and is displayed as follows:
'Accounting rules' workspace
## Formatting general ledger, subledgers, accounts and items
The following formatting options are available:
| Formatting | Description |
|---------|---------|
| red | Applies only to accounts, items or folders and it means they are not activated. |
| red + matt | The configuration of the superordinate item applies (the contra entry of the superordinate item is **not** activated). |
| black + bold | An accounting rule is defined for the general ledger, subledger, item or account. |
| grey | The configuration of the superordinate item applies (the accounting rule of the superordinate item is activated). |
> **Note:** The general ledger, subledger(s), and statistical ledger(s) are always black, even if they are **not** activated.
## Accounting Rule Types
The following accounting rule types are available:
| Accounting rule type | Description |
|---------|---------|
| [Payment](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-payment.md) | Used for all accounts and items relating to business transactions with a cash flow impact. It is the most frequently occurring rule in the P&L. **Note**: Only available for accounts and items with the period type **Transaction figure**. |
| [Investment](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-investment.md) | Used to plan new investments and their depreciation/amortization. The configuration specifies the bank account, value-added tax, and cash flow impact. Furthermore, the depreciation/amortization rule including the useful life and the accounts for the accumulated depreciation/amortization are determined on the balance sheet and the expense in the P&L. **Note**: Only available for accounts and items with the period type **Balance with carry-forward from previous period**. |
| [Accruals and deferrals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-accruals-deferrals.md) | Used for entering business transactions for the appropriate period in Lucanet, e.g. to plan business transactions in which services are purchased or sold in advance while the payment is made as a one-off advance payment. If the process is repeated at particular intervals and with a specific amount, the planning can be repeated automatically, e.g. for insurance premiums paid annually in advance. **Note**: Only available for accounts and items with the period type **Balance with carry forward from previous period**. |
| [Contra entry](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-contra-entry.md) | Used for recording postings within or between P&L and balance sheet, e.g. for depreciation in fixed assets. Depreciations do not have a cash flow impact, but reduce the value of the fixed assets (accumulated depreciation) in the balance sheet, and thus require a contra entry. **Note**: Available for accounts and items with the period type **Balance with carry forward from previous period** and **Transaction figure**. |
---
---
title: "Adding Additional Information to an Element"
description: "Financial data, planning assumptions, and consolidation entries are often complex. Using the Additional information tab, you can add notes and file attachments directly to elements in Consolidation & Financial Planning, without switching systems, so you can document why adjustments were made, which assumptions underlie a plan, or which supporting documents are relevant."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/add-further-information-to-elements
language: en
last_updated: 2026-05-28
---
# Adding Additional Information to an Element
## Overview
Financial data, planning assumptions, and consolidation entries are often complex. Using the **Additional information** tab, you can add **notes** and **file attachments** directly to elements in Consolidation & Financial Planning. This allows you, for example, to clearly document why you made certain adjustments, what assumptions underlie a plan, or which supporting documents are relevant.
Your team members can view this information at any time and build on it.
> **Note:** The content on the **Additional information** tab in Consolidation & Financial Planning differs from the content on the corresponding tab in Lucanet.Financial Client. This means that the content is only visible in the environment in which it was entered.
## Instruction
To add additional information to an element, open the **Additional information** tab in the element's detail view and click **Edit**. The tab is displayed as follows, for example:
'Additional information' tab
In edit mode, you can add additional information in the form of **text** using the text editor and/or as **file attachments**.
---
---
title: "Additional Accounting Rule Options"
description: "The additional accounting rule options allow you to streamline your accounting configurations by using rules from superordinate elements, applying rules across different journals without recreating them, and efficiently organizing or removing rules within a journal. These features help save time, reduce duplication of work, and ensure consistency across your financial data."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/accounting-rules-other-journals
language: en
last_updated: 2026-05-01
---
# Additional Accounting Rule Options
## Overview
The additional accounting rule options allow you to streamline your accounting configurations by using rules from superordinate elements, applying rules across different journals without recreating them, and efficiently organizing or removing rules within a journal. These features help save time, reduce duplication of work, and ensure consistency across your financial data.
## Using Superordinate Configurations
Items and accounts can be configured so the accounting rule of the parent ledger, folder, or superordinate item applies. This is suitable, for example, if the rule applies to the majority of the subordinate items or accounts. Deviations from the superordinate accounting rule can be configured in the subordinate accounts or items.
To use the accounting rule of the parent ledger, folder, or superordinate item:
1. In the tree view, select the account or item for which the superordinate configuration should apply.
2. In the **Type** drop-down list, select the **Superordinate** configuration type. The detail view is displayed as follows, for example:
Detail view of a superordinate configuration
## Applying Accounting Rules to Other Journals
The rules for automatic contra entries always apply to a journal, i.e. a particular combination of **data level** and **reporting entity**. To avoid creating a new configuration for each journal, you can **copy** the rules if they also apply to other journals. It is possible to adopt all saved accounting rules from general ledgers and subledgers or individual accounting rules from folders, items or accounts.
To apply accounting rules to other journals:
1. In the tree view, select the general ledger and/or one or more subledgers, folders, items or accounts whose accounting rule(s) you want to transfer to other journals.
2. Click **Apply accounting rules to other journals** in the dimension bar. The **Apply Accounting Rules to Other Journals** dialog is displayed:
'Apply accounting rule to other journals' dialog
3. Select the **Data levels** and the **Reporting entities** into which the accounting rules are to be transferred.
4. If applicable, activate the **Apply for all subordinate items and accounts** check box to transfer not only the rules of the selected folder, item or account but also those of all subordinate items and accounts.
5. Click **Save**.
## Copying and Moving Accounting Rules Within a Journal
The accounting rules in a journal can be moved to other items or accounts in the journal using the mouse or keyboard.
To copy or move accounting rules:
1. Select the account or item for which you want to copy or move the accounting rule.
2. Choose **Copy/Cut** from the context menu.
3. Select the accounts or items which you want to transfer the accounting rule to.
4. Choose **Paste** from the context menu.
## Deleting Accounting Rule Configurations
The accounting rule configurations in a journal (combination of **data level** and **reporting entity**) can be deleted if they are not being used in any postings — or if the associated postings are deleted first.
To delete an accounting rule configuration:
1. Select the accounts or the item for which you want to delete the accounting rule configuration.
2. Right-click the marked accounts or items.
3. Choose **Delete** from the context menu.
The superordinate configuration is automatically allocated to the selected accounts and items.
---
---
title: "Adjust and Reclassify Values in Consolidation Areas"
description: "Using the Adjust and Reclassify Values in Consolidation Areas app, account values can be adjusted and reclassified for each consolidation area. For example, you can:\nCorrect erroneous values at the partner, cost center, and transaction type levels\nReclassify account values from the general ledger or subledger to a statistical ledger\nDistribute values across multiple accounts"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/adjust-and-reclassify-values-in-consolidation-areas
language: en
last_updated: 2026-05-01
---
# Adjust and Reclassify Values in Consolidation Areas
## Overview
The app **Adjust and reclassify values in consolidation areas** allows you to selectively adjust and reclassify account values for each consolidation area. The app supports the following use cases, among others:
- Correcting errors in values at the partner, cost center, and transaction type levels
- Reclassifying account values from the general ledger or subledger to a statistical ledger
- Allocation of values across multiple accounts
## Configuring the App 'Adjust and Reclassify Values in Consolidation Areas'
To configure the app **Adjust and reclassify values in consolidation areas**, click the app in the structure view and click **Edit** in the displayed dialog.
Then configure the steps as described below.
### Settings
In the **Settings** step, specify the general settings for the configuration:
Step 'Settings'
| Option | Description |
|---------|---------|
| Posting | Period for which the values are to be adjusted or reclassified |
| Consolidation area | Selection of the consolidation area for which the values are to be adjusted or reclassified |
### Adjustment scenarios
In the **Adjustment scenarios** step, create the required adjustment scenarios.
Step 'Adjustment scenarios'
| Option | Description |
|---|---|
| Scenario name | Unique name for the adjustment scenario. Used for identification and reference in the **Basis and target** step. |
| Description | Optional description of the scenario. Used for documenting the purpose or the adjustment logic. |
| + Add row | Adds a new empty row to the table to add another adjustment scenario |
### Basis and target
In the **Basis and target** step, specify the **base value dimensions** to be adjusted or reclassified as well as the **posting** **target dimensions** for each scenario.
Step 'Basis and target'
The following options are available in the **Base value dimensions** table:
| Option | Description |
|---|---|
| Scenario | Adjustment scenario for which the dimensions of the base values are to be defined. All scenarios that were defined in the **Adjustment scenarios** step can be selected. |
| Account or item | Account or item whose values are used as the basis for the adjustment or reclassification. If an item is selected, the values of the underlying accounts are used. |
| Adjustment level | Adjustment level(s) or adjustment level group whose values are used as the basis |
| Consolidation unit | Consolidation unit(s) that contain the base values. The default setting **All** includes all consolidation units that are contained in the consolidation area selected in the **Settings** step. Alternatively, you can select individual consolidation units whose values are to be used as the basis. |
| Partner | Partner company or companies whose values are considered as the basis. The default setting **All** includes all partner companies that are assigned to the consolidation area selected in the **Settings** step. Alternatively, you can select **individual** partner companies or partner groups whose values are to be used as the basis. If a partner group is selected, all partner companies contained in the respective group are considered. |
| Transaction type | Transaction type(s) in which the base values were posted. The default setting **All** includes all transaction types that are assigned to the consolidation area selected in the **Settings** step. Alternatively, you can select **individual** transaction types or transaction type groups as the basis. If a transaction type group is selected, the calculation considers the values of all transaction types contained in the respective group. |
| Period type | Selection of the period type of the base values: **Transaction figure**, **Start balance of the period**, **End balance of the period** |
| + Add row | Adds a new row for an additional base data record |
The following options are available in the **Posting target dimensions** table:
| Option | Description |
|---|---|
| Scenario | Adjustment scenario for which the dimensions of the target values are to be defined. All scenarios that were defined in the **Adjustment scenarios** step can be selected. |
| Account | Target account to which the adjusted and/or reclassified values are posted |
| Adjustment level | Adjustment level on which the target posting is made |
| Consolidation unit | Consolidation unit for the target posting. The default setting **According to basis** applies the selection from the base table. Alternatively, you can select a different consolidation unit to which the values are to be reclassified. |
| Partner | Partner company for the target posting. The default setting **According to basis** applies the selection from the base table. Alternatively, you can select a different partner company to which the values are to be posted. |
| Transaction type | Transaction type for the target posting. The default setting **According to basis** applies the selection from the base table. Alternatively, you can select a different transaction type for the target posting. |
| Factor | Percentage factor for the adjustment (default value: 100%). Allows the values to be adjusted to a higher or lower percentage. |
| Debit/credit | Specifies whether debit values, credit values, or all values are considered (default value: **All**) |
| Posting text | Optional posting text for the generated posting |
| + Add row | Adds a new row for an additional target posting |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the App 'Adjust and Reclassify Values in Consolidation Areas'
You can execute the app **Adjust and reclassify values in consolidation areas** either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Executing the Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md).
- Date of the **last execution** that created the element
Tab 'Created elemens'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the app is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Adjust and Reclassify Values in Reporting Entities"
description: "You can use the Adjust and reclassify values in reporting entities app to adjust and reclassify account values per reporting entity. For example, it is possible to:\n- Correct incorrect values at partner, cost center, and transaction type level\n- Reclassify account values from the general ledger or a subledger to a statistical ledger\n- Distribute values to several accounts\nYou can model the adjustments and reclassifications in freely definable scenarios with separate dimensions for the base values and the target postings."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures/adjust-and-reclassify-values-in-reporting-entities
language: en
last_updated: 2026-05-01
---
# Adjust and Reclassify Values in Reporting Entities
## Overview
You can use the **Adjust and reclassify values in reporting entities** app to adjust and reclassify account values per reporting entity. For example, it is possible to:
- Correct incorrect values at partner, cost center, and transaction type level
- Reclassify account values from the general ledger or a subledger to a statistical ledger
- Distribute values to several accounts
You can model the adjustments and reclassifications in freely definable scenarios with separate dimensions for the base values and the target postings.
## Creating the 'Adjust and Reclassify Values in Reporting Entities' App
The **Adjust and reclassify values in reporting entities** app can be created in any directory structure, provided that the element type **Next Generation App** has been [enabled](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) for this directory structure.
To create the app, proceed as follows:
1. Navigate to the [directory structure](https://support.lucanet.com/en/documentation/glossary.md#directory-structure) under which you want to create the app.
2. Select the **root folder** of the directory structure or a **folder** under which you want to create the app, and select **Create | App** from the context menu.
The **Create Next Generation App** dialog is displayed:
Create Next Generation app
3. From the **App type** drop-down list, select the app **Adjust and reclassify values in reporting entities**.
4. If necessary, change the **name** of the app.
5. Click **Save** to create the app and configure it as described below.
## Configuring the 'Adjust and Reclassify Values in Reporting Entities' App
To configure the **Adjust and reclassify values in reporting entities** app, click the app in the tree view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the posting details and the relevant reporting entity. The step is displayed, for example, as follows:
'Settings' step
#### Posting
| Option | Description |
|---|---|
| Data level | Data level at which the reclassification is to be performed. Closed or archived data levels cannot be selected. |
| Period | The app reads out the values from the selected period and reclassifies them within this period. |
#### Reporting entity
Reporting entity for which the values are to be adjusted and reclassified
### Adjustment scenarios
In the **Adjustment scenarios** step, create the required adjustment scenarios. The step is displayed, for example, as follows:
Step 'Adjustment scenarios'
| Option | Description |
|---------|---------|
| Scenario name | Unique name for the adjustment scenario |
| Description | Optional description of the adjustment scenario |
| Add row | Inserts a new empty row in the table to add another adjustment scenario |
### Basis and target
In the **Basis and target** step, specify the details for the adjustment and posting for each scenario. The step is displayed, for example, as follows:
Step 'Basis and target'
The following options are available in the **Base value dimensions** table:
| Option | Description |
|---|---|
| Scenario | Adjustment scenario for which the base value dimensions are to be defined. All scenarios that were defined in the **Adjustment scenarios** step can be selected. |
| Account or item | Account or item whose values are to be used as the basis for the adjustment or reclassification. If you select an item, the values of the underlying accounts are used. |
| Adjustment level | Adjustment level(s) or adjustment level group whose values are to be used as the basis |
| Cost center | Cost center(s) whose values are to be used as the basis. The default **All** includes all cost centers assigned to the reporting entity selected in the **Settings** step. Alternatively, you can select **individual** cost centers or cost center groups whose values are to be used as the basis. If you select a cost center group, all cost centers contained in the respective group are considered. |
| Partner | Partners whose values are to be used as the basis. The default **All** includes all partners assigned to the reporting entity selected in the **Settings** step. Alternatively, you can select **individual** partners or partner groups whose values are to be used as the basis. If you select a partner group, all partners contained in the respective group are considered. |
| Transaction type | Transaction type(s) in which the base values were posted. The default **All** includes **all** transaction types assigned to the reporting entity selected in the **Settings** step. Alternatively, you can select **individual** transaction types or transaction type groups as the basis. If you select a transaction type group, the values of all transaction types contained in the respective group are considered. |
| Period type | Period type of the base values. The following period types can be selected: **Transaction figure**, **Start balance of the period**, **End balance of the period** |
| + Add row | Adds a new row for another base record. |
The following options are available in the **Posting target dimensions** table:
| Option | Description |
|---|---|
| Scenario | Adjustment scenario for which the posting target dimensions are to be defined. All scenarios that were defined in the **Adjustment scenarios** step can be selected. |
| Account | Target account to which the adjusted and/or reclassified values are to be posted. |
| Adjustment level | Adjustment level at which the target posting is to be performed. |
| Cost center | Cost center at which the target posting is to be performed. The default **According to basis** adopts the selection from the basis table. Alternatively, you can select a different cost center to which the values are to be reclassified. |
| Partner | Partner to which the target posting is to be performed. The default **According to basis** adopts the selection from the basis table. Alternatively, you can select a different partner company to which the values are to be reclassified. |
| Transaction type | Transaction type for the target posting. The default **According to basis** adopts the selection from the basis table. Alternatively, you can select a different transaction type for the target posting. |
| Factor | Percentage factor for the adjustment; allows the values to be adjusted to a higher or lower percentage. |
| Debit/Credit | Defines whether debit values, credit values, or all values are considered. |
| Posting text | Optional posting text for the created posting |
| + Add row | Adds a new row for another target record. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the 'Adjust and Reclassify Values in Reporting Entities' App
You can execute the **Adjust and reclassify values in reporting entities** app either **separately** or together with other apps in an **executable folder**.
### Executing an app separately
To execute the app separately, click **Execute** at the top right of the **app's editing dialog**:
'Execute' button in the app's editing dialog
### Combining Apps and Executing Them Together
For better organization, you can create as many folders as you like in a directory structure.
You can group multiple apps together in folders and execute them together. Proceed as follows:
1. Ensure that, in the [workspace configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche.md), the object type Folder for the directory structure has been [enabled](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md).
2. In the **tree view**, select the **element** under which you want to create the folder and choose **Create | Folder** from the context menu.
3. In the **Create folder** dialog, enter a **Name** and select a desired **Behavior** if there should be an error during execution of the folder:
- **Continue execution**
- **Cancel execution**
4. **Save** the executable folder.
5. Paste the apps to be combined into the folder. Choose one of the following options:
- Add existing apps using the context menu commands **Cut** and **Paste**.
- Create new apps in the folder using the **Create** context menu command.
6. Execute the folder and all elements contained in it by clicking **Execute all subordinate elements** in the detail view of the folder:
Combining apps and executing them together
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created. When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
> **Note:** For a detailed history of past executions, including the process log of each run, open the **Execution log** tab in the app's change log. For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
Tab 'Created Elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Adjustment Levels"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels
language: en
last_updated: 2026-05-01
---
# Adjustment Levels
## Overview
The **Adjustment levels** workspace is used to create, administrate, and delete [adjustment levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/manage-adjustment-levels.md), [adjustment levels for consolidation postings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/create-configure-adjustmentlvl-consolidation-postings.md), and [adjustment level groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/create-configure-adjustmentlvl-groups.md).
---
---
title: "Administrating Master Data"
description: "To create consolidated financial statements, you first have to define the master data that form the basis for consolidation of a company within a group."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration
language: en
last_updated: 2026-10-01
---
# Administrating Master Data
## Overview
To create consolidated financial statements, you first have to define the master data that form the basis for consolidation of a company within a group.
The **master data administration** is used to enter, display, and save the following issues within a group:
- **Investment relationships** within a group in the form of shares and their changes over time
- **Changes in investors** in the event of group-internal share acquisitions from one or more investors in an investment
- **Consolidation methods** for including consolidation units in consolidation areas and their evolution over time
- **Fair value of non-controlling interests** for including fully consolidated subsidiaries using the full goodwill method
- **Increase and decrease in capital** for fully consolidated subsidiaries
- **Periods** and **accounts** for the **amortization of goodwill**
- **Translation with historical exchange rates** for foreign currency companies
> **Note:** - For every group and every data level, you must create a master data administration that is used for all consolidated financial statements of the group.
> - When configuring the master data for planning data levels, you can use already configured master data from the actual data level by means of synchronization (see [Synchronizing Actual Master Data for Planning Data Levels](#planning)).
## Creating the Master Data Administration
Select one of the following options to create the master data administration for a combination of group and data level:
- **In the ‘Groups’ workspace**
Select the desired group in the overview and navigate to the **Master data administration** tab in the detail view. Then click **Create master data administration**.
Creating master data administration in the ‘Consolidated financial statements’ workspaces for the desired data level.
- **In the ‘Consolidated financial statements’ workspace**
Select the desired combination of **group** and **data level** in the dimension bar and click **Create** in the **Master data administration** field.
Creating master data administration in the detail view of a group
After that, enter a name for the master data administration in the **Create element** dialog and click **Save**.
'Create master data administration’ dialog
> **Note:** The master data administration is shown both in the **Groups** workspace and in the **Consolidated financial statements** workspace for the selected combination of group and data level and can be configured and edited subsequently in **both** workspaces.
## Configuring Master Data Administration
To configure the master data administration, select the element in the **Groups** workspace or in the **Consolidated financial statements** workspace and click **Edit** in the upper right corner of the edit dialog.
The following options are available for the master data administration:
> **Note:** The tabs **Investments** and **Consolidation methods** must be configured to enable correct consolidation by the [Consolidation apps](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps.md).
>
> The tabs **Corporate actions**, **Goodwill** and **Historical exchange rates** only need to be configured if the issues are relevant in the group.
### ‘Investments’ tab
On the **Investments** tab, the intercompany **investment relationships** are defined. Enter the percentage ownership interest of each investor in an investment, taking into account the relevant period.
For each investment, add a new row using the command **Add period** and configure the required columns.
The ownership interest applies from the specified period until you enter a new participation rate for the combination of investor and interest in a subsequent period. Whether the change is applicable from the start or end of the period depends on the point in time selected in the consolidation methods for this investment.
‘Investments’ tab
The following columns are available on the **Investments** tab:
| Column | Description |
|---|---|
| Period | Period from which an investment in an economic entity exists. |
| Investor | [Consolidation dimension element](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) for the investor.
**Note:** By selecting multiple entries in the drop-down menu, you can enter all investments for an investor during a period. |
| Investment | [Consolidation dimension element](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) in which the investor holds the investment. |
| Ownership interest in % | Percentage share of each investor in an investment.
**Note:** The ownership interest applies from this period until you enter a new ownership interest for the combination of investor and investment in a subsequent period. Whether the change is applicable from the start or end of the period depends on the period selected in the **consolidation methods** for this investment. |
| IC share acquisition | Activate the check box if an increased ownership interest in the investment partially or fully results from an IC share acquisition, and configure the displayed **details on the IC purchase of shares**. |
Click the **question mark** icon to obtain information about the configuration of the tab. Click the **trash bin** icon to delete a row.
### 'Consolidation methods' tab
On the **Consolidation methods** tab, the complete history of the inclusion of the companies in the consolidated financial statements is defined.
For every consolidation method of a consolidation unit within the consolidation area, add a new row using the **Add period** command, and configure the required columns.
If the consolidation method of a consolidation unit changes, you must enter a new issue for this period.
> **Tip:** **Automatic determination of consolidation methods**
>
> You have the option to insert the consolidation methods automatically based on the information provided on the **Investments** tab.
>
> To do this, click **Determine consolidation methods automatically** and then select a period for the automatic determination.
>
> **Note**: During the automatic determination of the consolidation methods, all existing table entries for the specified period are deleted and determined again, based on the entries made on the **Investments** tab. This action cannot be undone!
Consolidation methods tab
The following columns are available on the **Consolidation methods** tab:
| Column | Description |
|---|---|
| Period | Period as of which the consolidation method applies for the consolidation unit. |
| Time | Choose whether the time of the change of the consolidation method shall apply from the **start** or from the **end of the selected period**.
**Note:** The same setting will be applied to subsequent changes in ownership interests without a change in the consolidation method. |
| Consolidation unit | [Consolidation unit](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) for which you want to define the consolidation method. |
| Consolidation area | [Consolidation area](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) to which the selected consolidation unit belongs. (Is inserted automatically.) |
| Consolidation method | Consolidation method that applies to the consolidation unit from this period and this time. You can choose the following consolidation methods: - **Full consolidation** - **Proportionate consolidation**\* - **Equity method**\* - **–** (not consolidated)
\*Cannot be selected for default consolidation units and consolidation units of investors.
**Note:** In the event of disposal of a consolidation unit from the group, the '–' consolidation method must be selected as well as the period and time. |
| Full goodwill method | Activate the check box if the full goodwill method is to be applied for fully consolidated subsidiaries as part of equity elimination of the investment.
**Note:** If you activate the **full goodwill method** option for a row, you must additionally specify the **fair value of non-controlling interests** in the following column. |
| Fair value of non-controlling interests | Fair value of the non-controlling interests at the time of acquisition in the currency of the consolidation area. Only needs to be specified if you have activated the option **Full goodwill method**. |
Click the **question mark** icon to obtain information about the configuration of the tab. Click the **trash bin** icon to delete a row.
### ‘Corporate actions’ tab
On the **Corporate actions** tab, you specify whether capital increases and reductions should be included in the consolidation process for fully consolidated subsidiaries.
- If you use the [app for equity elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md) in the CFO Solution Platform, you **do not** need to configure this tab, as this configuration step is no longer necessary within the master data administration when the app for equity elimination in the CFO Solution Platform is used.
- If you are using the legacy app for equity elimination in Lucanet.Financial Client, you must configure this tab in case of corporate actions. To do this, activate the check box **Configure consolidation of corporate actions**. After that, for each corporate action to be consolidated, add a new row using the command **Add period** and configure the required columns.
Corporate actions tab
The following columns are available on the **Corporate actions** tab:
| Column | Description |
|---------|---------|
| Period | Period in which a corporate action is to be consolidated |
| Investment | [Consolidation unit](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) for which the corporate action is to be defined |
| Corporate action | Choose here, whether the corporate action is a: - **Capital increase** - **Capital reduction** |
> **Tip:** The consolidation of corporate actions is carried out using the app for the **equity elimination**.
>
> Only the capital increases and reductions entered on the **Corporate actions** tab in the master data administration are included in the consolidation process by the app for equity elimination.
### ‘Goodwill’ tab
On the **Goodwill** tab, you specify whether goodwill or negative consolidation differences recognized in the balance sheet from the equity elimination are to be amortized on a straight-line basis.
If yes, activate the check box **Configure straight-line amortization of goodwill** and configure the options subsequently displayed.
‘Goodwill’ tab
The following options are available:
| Option | Description |
|---|---|
| **Default values** | Enter the **amortization period (in months)** and a profit and loss **account** to be used by default for the straight-line amortization of goodwill or the negative consolidation differences recognized in the balance sheet resulting from equity elimination. |
| **Deviating values** | If a different amortization period applies for an investment in a certain period, activate the check box **Deviating values**.
After that, for each deviating issue, add a new row using the command **Add period** and configure the required columns.
**Note:** The specified period must be the one in which the goodwill arose.
**Example**: If goodwill arose for Subsidiary 1 in 02.2025, 02.2025 and Subsidiary 1 must be specified, as well as a deviating account and/or deviating amortization period if applicable. |
### ‘Historical exchange rates’ tab
On the **Historical exchange rates** tab, you specify the issues that are to be translated from the local currency of a foreign currency company into the group currency using a historical exchange rate.
If this is the case, activate the check box **Configure translation with historical exchange rates.** After that, for each issue, add a new row using the command **Add element** and configure the required columns.
‘Historical exchange rates’ tab
The following columns are available on the **Historical exchange rates** tab:
| Column | Description |
|---|---|
| Issue | Double-click in the **Issue** column and enter a **name** for the issue. |
| Type | Type of the historical exchange rate fixation: - **Shares and equity** - **Differential** arising during equity elimination |
| Period | Period for which the translation with historical exchange rates is to be defined. |
| Consolidation unit | [Consolidation unit](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) for which the translation with historical exchange rates is to be defined. |
| Consolidation area | [Consolidation area](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) to which the selected consolidation unit belongs. (Is inserted automatically.) |
| Transaction currency | [Transaction currency](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation.md) used for the historical exchange rate fixation. |
| Details of the issue | For each **display currency** for which a historical exchange rate is to be fixed, add a row in the displayed table and enter the historical exchange rate. If you have selected as the **type** of historical exchange rate fixation **Shares and equity**, you also need to specify the **accounts or items** to be calculated using the historical exchange rate in the table additionally displayed, and select the desired **transaction type** for each account or item. |
### ‘Overview’ tab
On the **Overview** tab you can view a summary of the investment relationships defined in the master data administration. The tab is only visible in display mode, but not in edit mode, and is divided into the following sections:
#### Overview
In the **Overview** section, you can use the **Generate report** command to generate and display a report listing all investment relationships in table format. This report contains the following figures.
Overview of investment relationships
The following columns are available in the report:
| Column | Description |
|---------|---------|
| Ownership interest in % | Displays the rates of the economic entity held by the investor. |
| Effective group share investor in % | Displays the effective group share of the investor. The effective group share of the investor is determined mathematically. |
| Effective share in % | Displays an investor's effective share of equity in an economic entity across all group levels. The effective share is calculated from the effective group share of the investor multiplied by the direct share of the investor in the economic entity. |
| Direct group share investment in % | Displays the direct group share in the economic entity. The direct group share in the investment is calculated as the total direct shares of all investors in the economic entity. |
| Effective group share investment in % | Displays the effective group share in the economic entity. The effective group share in the investment is calculated as the total effective shares of all investors in the economic entity. |
You can export the report in **XLS** and **XLSX** format using the **Export** command on the top right of the section.
> **Warning:** **Notes**:
>
> - To ensure that the information displayed is **up to date**, a report that has already been created will be automatically deleted as soon as the user edits the tabs **Investments** and/or **Consolidation methods**. In this case, a new report can be generated by clicking the **Generate report** button.
> - The app for **equity elimination** accesses the data of the master data administration report. If no report has been created yet for the master data administration when executing this app, the report will be automatically generated by the app and then displayed here on the **Overview** tab.
#### Investment Relationships
In the **Investment Relationships** section, you can visualize your investment relationships in a chart.
To do so, select the **Consolidation dimension** and the **Period** for which you would like to visualize the investment relationships. The diagram is displayed as follows, for example:
Visualization of investment relationships
Once the chart is visible, you can:
- **Refresh** the chart to reflect changes made to the investment relationship configured in Master data administration
- **Search** for entities within the chart
- Adjust the **decimal places** used for displaying the ownership percentages
- **Copy** the chart to the clipboard using the copy clipboard icon
- Save the chart as **PNG** or **JPEG** file or **print** the chart (using the three-dot menu the three dot icon ).
### 'Properties' tab
The following is displayed on this tab:
- **Type** of the element
- **Version** of the element If a new version of an app is available, the command **Refresh** is shown, which can be used to refresh the app to the latest version. In addition, you can access the **Release Notes** of the currently used version of the master data administration via a link.
- Command to **synchronize** the master data of a planning data level with the master data of the actual data level. For additional information on this, see the following chapter.
‘Properties’ tab
## Synchronizing Actual Master Data for Planning Data Levels
If you want to configure the master data administration for **planning data levels** of a group, you have the option of synchronizing and adopting master data that you have already configured for the actual data level for this group.
To do so, navigate to the **Properties** tab and click **Synchronize with actual master data**.
Synchronize with actual master data
The master data configured for the actual data level of the group are transferred to the selected planning data level for all periods before the start of the planning data level. From the start period of the planning data level onward, the master data are defined as part of the planning. To define deviating details for the master data of the planning data level, proceed as described under [Configuring Master Data](#configuring-master-data-administration).
## Validating and Publishing Master Data Administration
Validate or publish master data
**Validate**
After entering data for the master data administration, you can validate the configuration. Up to the time of the validation, you can close and reopen the app configuration at any time without executing a validation in the background.
To validate, open the edit mode of the master data administration and click **Validate** in the upper right corner. Any configuration errors are then displayed on the respective tabs. You can fix them and re-validate the configuration.
**Publish**
In order to use the master data in consolidated financial statements, you must **publish** the master data in a final step. Only then can the consolidation apps access the master data.
To do this, open the **Edit mode** of the master data administration and click **Publish** in the top right corner.
> **Note:** You can also publish the configuration of the master data without prior validation. A validation is also carried out in this case before publication.
## Exporting Master Data
You can export the data that you have entered on the individual tabs in the master data administration, as well as the report generated on the **Overview** tab in Excel format at any time.
To do this, click **Export** above the configuration table on the right and choose whether you want to create the export in **XLS** or **XLSX** format.
After that, the export will be available in your download directory.
Exporting master data
---
---
title: "All Steps at a Glance"
description: "Before the import into reporting entities is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/all-steps-consolidation-1
language: en
last_updated: 2026-05-01
---
# All Steps at a Glance – Consolidation 1
## Overview
Before you can perform **Consolidation 1**, you must create and configure the necessary objects. The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined.
### Step 1: Optional: Creating requirements
Before you begin setting up the consolidation, you must first ensure that the necessary prerequisites are in place. This includes:
**Create Accounting Structures**
Display the accounting structure of your enterprise. The elements that need to be created depend on the structure of your enterprise.
**Items and accounts in the general ledger**
Create the items and accounts for the general ledger (see section [Elements in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules.md)).
**Subledgers**
Create one or more subledgers and the corresponding items, accounts, and references therein.
**Statistical ledgers**
Create one or more statistical ledgers and the corresponding items, accounts and references (see section [Creating and Configuring a Statistical Ledger](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-statistical-ledger.md)).
**Schedule**
Create the required schedules if necessary.
**Defining Reporting Entities and Importing Financial Data**
In the **Reporting entities** workspace, reporting entities into which your financial data are imported, are defined.
**Defining reporting entities**
In the **Reporting entities** workspace, create elements to which postings can be made in Lucanet, i.e., reporting entities, cost center groups, cost centers as well as subtotals and totals (see section [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities.md)).
**Consolidation reporting entities**
In the **Reporting entities** workspace, create consolidation reporting entities to which consolidation postings can be made (see section [Creating and Configuring Consolidation Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)).
**Importing financial data**
Import your financial data into reporting entities (see section [Importing Data into Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities.md)).
**Defining Partners**
Partners are used for the consolidation in order to add partner information to postings and data imports for the **internal cost allocations**.
You can create and configure partners in the workspace of the same name (see Section [Partner](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners.md)).
**Optional: Configuring Currency Translation**
If transactions can be executed in multiple currencies in your enterprise, you must first create the possible transaction and display currencies (see section [Creating and Configuring Currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)) as well as define exchange rate tables for the currencies (see section [Creating and Configuring Exchange Rate Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md)).
Once all necessary prerequisites for your company have been met, you can proceed as follows with the configuration and execution of the consolidation:
### Step 2: Assigning Partners
Partners can be created and assigned in the **Partner** workspace (see section [Creating and Configuring Partners](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners/manage-partners.md)).
### Step 3: Defining Consolidation Areas
Define the organization elements that you want to consolidate together (see section [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)).
### Step 4: Defining and Activating Period Locks
To ensure that the consolidation can be executed along with the relevant postings, the corresponding **period locks** must be defined and activated in the **Period locks** workspace (see section [Configuring Period Locks](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks.md))
### Step 5: Defining Configuration
Define the configuration for the elimination of intercompany debt, the elimination of intercompany income and expense, or inventory consolidation (see section [Creating and Editing Configurations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configurations-consolidation-1.md)).
### Step 6: Configuring Consolidation Wizards
Configure the wizards for elimination of intercompany debt, elimination of intercompany income and expense, or inventory consolidation (see section [Creating and Configuring Consolidation Wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards.md)).
Once a consolidation wizard has been created, the consolidation is executed and a new posting is generated in the [Import and Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals.md) workspace.
---
---
title: "All Steps at a Glance"
description: "Before you can perform consolidation using Lucanet Consolidation 2, you must first create and configure the necessary elements and apps.\nWhich elements you need to create depends on the organization and the structure of your company and on the chosen consolidation method."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/all-steps-consolidation-2
language: en
last_updated: 2026-09-29
---
# All Steps at a Glance – Consolidation 2
## Overview
Before you can perform consolidation using Lucanet Consolidation 2, you must first create and configure the necessary **elements** and **apps.**
Which elements you need to create depends on the organization and the **structure of your company** and on the chosen **consolidation method**.
As the required elements are based on and linked to each other, we recommend that you follow the sequence of steps described here.
### Step 1: Create prerequisites
Before you set up the consolidation, you must first create the necessary prerequisites on the Lucanet CFO Solution Platform. This includes:
**Creating Accounting Structures**
Map the accounting structure of your enterprise. The elements that need to be created depend on the structure of your enterprise.
**Items and accounts in the general ledger**
Create the items and accounts for the general ledger (see section [Elements in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules.md)).
**Subledgers**
Create the subledger(s) and the corresponding items, accounts and references. (The procedure for this is described in the Lucanet Financial Client online help.)
**Statistical ledgers**
Create one or more statistical ledgers and the corresponding items, accounts and references (see section [Creating and Configuring a Statistical Ledger](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-statistical-ledger.md)).
**Schedules**
If necessary, create the required schedules (see section Creating and Configuring Schedules).
**Defining Reporting Entities and Importing Financial Data**
In the **Reporting entities** workspace, reporting entities into which your financial data are imported, are defined:
**Define reporting entities**
Define all companies of your group as reporting entities (see section [Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md)).
**Import financial data**
Import your financial data into reporting entities (see section [Importing Data Into Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities.md)).
**Optional: Defining Partners**
Partners are used during consolidation to provide partner information for the **intercompany transactions** for postings and data imports.
You can create and configure partners in the workspace of the same name (see section [Partners](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners.md)).
**Optional: Configuring Currency Translation**
If transactions are made in different currencies in your company, you must first create the possible transaction and display currencies (see Section [Creating and Configuring Currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)) and define exchange rate tables for the currencies (see Section [Creating and Configuring Exchange Rate Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md)).
If all requirements necessary for your company have been set up, you can proceed as follows with the configuration and execution of the consolidation:
### Step 2: Defining the Group Structure
Define your group structure in the **Groups** workspace.
**Create a group**
The group is the basic element of your company for consolidation (see section [Defining the Group Structure](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure.md)).
**Create consolidation dimensions and consolidation dimension elements**
Consolidation dimensions are used to define all the elements of an enterprise that can be consolidated together, such as **companies**, or other **entities that are economically related**.
For each of these elements within a consolidation dimension, a consolidation dimension element must be created (see section [Consolidation Dimensions and Dimension Elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md)).
**Create consolidation area(s)**
Consolidation areas are the object of consolidation in which the consolidation is executed. **Consolidation areas** are used to summarize all consolidation units that are to be consolidated together.
If a group consists of several foreign currency companies, all relevant **exchange rate tables** of the individual consolidation units must also be stored here (see section [Consolidation Areas and Units](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md)).
### Step 3: Defining Organization Elements
Create the following in the **Organization elements** workspace:
- References to consolidation areas, consolidation units, or consolidation unit groups
- References to reporting entities to reporting entity, cost centers or cost center groups
For more information, see [Organization Elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md).
### Step 4: Defining adjustment level(s) for consolidation postings
Define the adjustment levels in the **Adjustment levels** workspace on which the postings related to consolidation are made (see section [Creating Adjustment Levels for Consolidation Postings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/create-configure-adjustmentlvl-consolidation-postings.md)).
### Step 5: Defining Consolidation Apps
The **investment relationships** and **consolidation methods** as well as the **amortization of goodwill** and, if necessary, the **translation with historical exchange rates**, are adminstrated in the master data (see section [Administrating Master Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md)).
### Step 6: Creating Consolidated Financial Statements
Create a Consolidated financial statements element for each time period and data level to be consolidated (see section [Creating Consolidated Financial Statements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/creating-consolidated-financial-statements.md)).
### Step 7: Creating and Configuring Apps for Consolidation
With the app for **Data transfer and proportioning** you can automatically transfer the **single-entity financial statement figures** according to the **investment relationships** and prepare them for consolidation, including transaction type adjustments (see section [Creating and Configuring Data Transfer and Proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md)).
Depending on the method required for consolidation in your group, create the necessary consolidation apps (see section [Creating and Configuring Consolidation Apps](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps.md)).
The following apps are currently available in the Lucanet CFO Solution Platform:
- Debit/credit shifts in consolidation area
- Elimination of income from investments
- Elimination of intercompany debt
- Elimination of intercompany income and expense
- Elimination of intercompany profit or loss in current assets
- Equity elimination
- Reclassification of profit or loss from previous year in consolidation areas
- Adjust and reclassify values in consolidation areas
- Copy postings into other consolidation areas
### Step 8: Executing the Consolidation
Execute the consolidation, i.e. The consolidated financial statements and all apps contained therein, and thus generate the consolidation postings and reports (see section [Executing the Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md)).
You can display the postings and reports that were created via the **Created elements** tab in the respective app or from the overview table.
---
---
title: "All Steps at a Glance"
description: "Before the import into Lucanet.Financial Warehouse is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/all-steps-data-import-lnfwh-entities
language: en
last_updated: 2026-05-01
---
# All Steps at a Glance - Importing Data into Lucanet.Financial Warehouse
## Overview
Before the import into Lucanet.Financial Warehouse is performed, the objects required for this must be created and configured based on their data source(s). Because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined.
### Step 1: Preliminary Considerations
Before configuring the import and creating objects in Lucanet, consider and define the following:
- Are the technical conditions for the data import met?
- Do two databases and a technical user with read and write permission exist for these databases?
- Is Lucanet.Financial Warehouse already set up?
- Is [SEA](https://support.lucanet.com/en/documentation/glossary.md#sea) required? If so, has SEA already been installed? (see [Installing and Using Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md).)
> **Note:** **SEA** (Lucanet Script Execution Application) is a Lucanet application that is required when ERP/financial source systems are operated on-premises and data from these systems needs to be imported into the Lucanet CFO Solution Platform via script.
- What are the content requirements?
- Are there one or more source system(s)?
- Per source system:
- Is there a script used to connect the source system?
- Which transformations need to be performed for the data when writing to Lucanet.Financial Warehouse?
- For which elements of the Lucanet data model (data levels, reporting entities, etc.) are the transformed data to be prepared?
### Step 2: Uploading Scripts
Using **scripts**, data from various source systems can be read, changed, optionally augmented, and imported into Lucanet Financial Warehouse.
Load scripts into the **Scripts** workspace (see [Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)).
### Step 3: Defining a Data Source
In order to import data from an source system, the source of the data must be defined. To do so, a data source used to import an Excel file must be created in the tree view of the workspace **Importing data into Lucanet.Financial Warehouse**.
Create a data source and configure the data source (see [Defining Data Sources](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh.md)).
### Step 4: Defining Data Transformation(s) (Optional)
**Transformation rules** in **data transformations** are optional. Transformation rules determine how the data from the source system are to be transformed before they are written to Lucanet.Financial Warehouse.
If necessary, create at least one data transformation (see [Creating and Configuring Data Transformations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-data-transformation.md)).
### Step 5: Defining Execution Settings
For which elements of the Lucanet data model (data levels, adjustment levels, reporting entities, fiscal years, and accounting periods) the data are to be imported is specified for a selected data source in the execution settings.
Define execution settings (see [Creating and Configuring Execution Settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-execution-settings.md)).
### Step 6: Creating and Executing the Data Import
The import is started with the **Execute** function in the detail view of execution settings or folders.
Import the data (see [Executing the Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/execute-data-import.md)).
### Step 7: Editing Period Locks (Optional)
The data import can only take place if the import of data into the desired reporting entities for the desired period is allowed. If periods into which you want to import data are locked, you will not be able import the data. You will then have to unlock the desired periods in the **Period locks** workspace.
If necessary, edit the period locks (see [Period Locks](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks.md)).
---
---
title: "All Steps at a Glance"
description: "Before the import into reporting entities is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/all-steps-data-import-reporting-entities
language: en
last_updated: 2026-09-04
---
# All Steps at a Glance - Importing Data into Reporting Entities
## Overview
Before the import into reporting entities is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined.
### Step 1: Preliminary Considerations
**Before** configuring the import and creating objects in Lucanet, consider and define the following:
- Which data are to be imported?
- From which Excel file are the data to be derived?
- Has the Excel file already been filled with values?
- Which elements of the Lucanet data model (data levels, reporting entities, etc.) are to be filled with the data?
### Step 2: Creating an Assignment Table
**Assignment tables** are used to save all elements imported from the source systems (accounts, reporting entities and cost centers, partners, transaction currency, transaction types, data levels, adjustment levels) and their assignment to elements in the **Lucanet database**. Assignments are defined during the data import and can then be changed or deleted **at any time**.
If necessary, create an assignment table (see chapter [Creating an Assignment Table](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-assignment-table.md)).
### Step 3: Defining and Configuring Data Sources
In order to import data from an source system, thesource of the data must be defined. For this purpose, a **data source** for importing an Excel file must be created in the tree view for the **Importing data into reporting entities** workspace.
Create a data source and configure the data source (see chapter [Defining Data Sources](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).
### Step 4: Editing the Audit Trail (Optional)
The data import can only take place if the import of data into the desired reporting entities for the desired period is allowed by the corresponding [audit trail](https://support.lucanet.com/en/documentation/glossary.md#period-lock).
If necessary, edit the audit trail in Lucanet.Financial Client.
> **Note:** Audit trails are configured under the **Posting and planning** folder in the **Audit trails** workspace, by default.
### Step 5: Creating and Executing the Data Import
All data that is imported into reporting entities is transferred to the current Lucanet database using **data imports**. The **Data import** element is used to determine which data source and assignment table are to be used during the import.
The actions in the detail view of the data import are used to execute the data import, create assignments in the assignment table used and save the data import. You can create any number of data imports.
Create a data import (see chapter [Creating and Executing a Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
### Step 6: Assigning Data
If, during a data import, new elements have been read in for the first time from the dimensions **Accounts**, **Reporting entities** and **cost centers**, **Partner**, **Transaction currency**, **Data levels**, **Adjustment levels**, or **Transaction types**, these elements must be **assigned** (only once).
The data cannot be imported if there are any **assignment errors**. Assignment errors are displayed in the data import object.
- Check the assignments and/or rectify any faulty assignments (see chapter [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)).
- Import the data (see chapter [Creating and Executing a Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
### Step 7: Updating the Data Import (Optional)
The data import can be updated **manually** or **automatically** in connection with the **Lucanet job control**.
- The data import is updated manually by importing the data again (see section [Creating and Executing a Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
- The automatic update must be configured in **Lucanet.Server Administrator** in the job control.
> **Note:** Job control is configured in Lucanet.Server Administrator.
### Step 8: Finalizing Data Import
Every data import can be **finalized** in order to prevent it from being changed or deleted.
If necessary, close the data import (see chapter [Finalizing the Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/completing-data-import.md)).
---
---
title: "All Steps at a Glance - Planning"
description: "Before you can perform your planning in Lucanet Consolidation & Financial Planning, the required objects must be created and configured in Lucanet. The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined on this page."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/all-steps-planning1
language: en
last_updated: 2026-09-29
---
# All Steps at a Glance - Planning
## Overview
Before you can perform your planning in **Lucanet Consolidation & Financial Planning**, the required objects must be created and configured in Lucanet. The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined.
### Step 1: Creating Prerequisites
The organization and structure of your enterprise determine the elements that must be created in order to recreate your enterprise structure. Before you start planning, you must first create the necessary prerequisites on the CFO Solution Platform. These include:
**Creating Accounting Structures**
Display the accounting structure of your enterprise. Which elements need to be created depends on the structure of your company:
**Items and accounts in the general ledger**
Create the items and accounts for the general ledger (see [Elements in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules.md)).
**Subledgers**
Create one or more subledgers and the corresponding items, accounts, and references (see Creating and configuring a subledger).
**Statistical ledgers**
Create one or more statistical ledgers and the corresponding items, accounts, and references (see Creating and configuring a statistical ledger).
**Schedules**
If necessary, create the required schedules (see Creating and configuring schedules).
**Defining the Organization Structure**
Define your organization structure:
**Reporting entities**
In the **Reporting entities** workspace, create objects to which postings can be made in Lucanet, i.e., reporting entities, cost center groups, cost centers as well as subtotals and totals (see [Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md)).
**Organization elements**
In the **Organization elements** workspace, map the structure of your organization using references to reporting entities, cost centers, and cost center groups (see [Organization Elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md)).
**Optional: Configuring Currency Translation**
If the transactions in your company can be carried out in different currencies, you must first create the possible transaction and display currencies (see [Creating and Configuring currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)) and define exchange rate tables for the currencies (see [Creating and Configuring Exchange Rate Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md)).
Once you have created all the necessary prerequisites for your company, you can proceed with the planning as follows:
### Step 2: Defining Planning Data Level(s)
Define the planning data levels containing the planning figures in the **Data levels** workspace (see [Creating and Configuring Planning Data Levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/create-configure-planning-datalvls.md)).
### Step 3: Defining Adjustment Level(s)
Define the adjustment levels for planning in the **Adjustment levels** workspace (see [Creating and Configuring Adjustment Levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels.md)).
### Step 4: Defining Accounting Rules
In Lucanet, one-sided postings can be made using **Sheets** or **Excel**. However, since postings in Lucanet can only be saved if the credit side matches the debit side, an automatic contra entry must be made at the same time in case of a one-sided posting. This is done by the system using accounting rules defined for the corresponding accounts in the **Accounting rules** workspace (see [Accounting Rules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules.md)).
### Step 5: Defining Period Locks
Define the corresponding period locks in the **Period locks** workspace to ensure that planning can be carried out with the relevant postings (see [Period Locks](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks.md)).
### Step 6: Carrying out Planning
Carry out planning by:
- Using Sheets (see [Plannning Using Sheets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets.md))
- Using planning wizards (see [Planning Using Planning Wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards.md))
- Creating manual postings (see [Creating and Configuring Postings in Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/create-configure-posting-reporting-entity.md))
- Importing data (see [Planning Using CFP Add-in for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-excel-add-in.md))
### Step 7: Displaying Planning Data
Visualize your planning data by:
- Configuring the [display of the general ledger or subledger](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules.md)
- Using views (see [Creating a View](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views.md))
- Using the dimension bar (see [Dimension Bar](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-dimension-bar.md))
---
---
title: "Analyzing Databases"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database
language: en
last_updated: 2026-10-01
---
# Analyzing Databases
## Overview
With the **Analyze database** function, you can execute your own SQL queries against a connected database and display the result directly in Lucanet Consolidation & Financial Planning, without using a separate database tool.
Typical use cases for the **Analyze database** function are:
- Verifying the correctness of imported data by querying specific values and comparing the values of related tables
- Analyzing the database of a source ERP system when investigating a data import problem
Access to the databases during the analysis is read-only.
The following databases can be analyzed with the **Analyze database** function:
| Database | Description |
|---|---|
| Lucanet.Financial Warehouse | The temporary and the persistent Lucanet.Financial Warehouse |
| Database of a source system | Any database that you can connect in Lucanet Consolidation & Financial Planning, for example the database of an ERP system.
The database can be located in the cloud or in your local network. |
## Accessing the Analyze Database Function
In Lucanet Consolidation & Financial Planning, the **Analyze database** button is displayed in the detail view of the following elements:
- Element of type **Connection** (see [Elements in Directory Structures](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures.md))
- Data source for importing data into Lucanet.Financial Warehouse, once for the temporary and once for the persistent Lucanet.Financial Warehouse (see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh.md))
- Data source of type **Lucanet.Financial Warehouse (#2068)** for importing data into reporting entities (see [Lucanet.Financial Warehouse (#2068)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md))
In the detail view of an element of type **Connection**, the button is displayed as follows, for example:
'Analyze database' button in the detail view of a connection
> **Note:** No separate permission is required for the **Analyze database** function. Access to the workspace that contains the respective element is sufficient.
## Opening the Query Window
To open a query window in Lucanet Consolidation & Financial Planning:
1. Click **Analyze database**.
2. If credentials are required for the database, the **Connect** dialog is displayed as follows, for example:
'Connect' dialog
Enter the credentials, select the application, and click **Connect** (for more information, see [Options in the 'Connect' Dialog](#options-in-the-connect-dialog)).
3. The **Analyze database** dialog is displayed as follows, for example:
'Analyze database' dialog
4. If necessary, in the **Catalog** field, specify the catalog of the database to which the queries are to be restricted.
The catalog is taken from the connection, if a catalog is configured there.
5. If necessary, in the **Schema** field, specify the schema of the database to which the queries are to be restricted.
A database can contain several schemas, for example one schema per Lucanet.Financial Warehouse. The schema is taken from the connection, if a schema is configured there.
6. Click **Query**.
The query window is displayed as follows, for example:
Query window before the first query
Under **URL**, the database against which your queries are executed is displayed. The **Records limit** field contains the maximum number of records that are displayed in the **Results** area: **500**.
### Options in the 'Connect' Dialog
The **Connect** dialog is displayed if credentials are required for the database. The following options are available in the dialog:
| Option | Description |
|---|---|
| **User name** | The name of the database user with which the queries are executed.
The user name is taken from the connection and can be changed. |
| **Password** | The password of the database user |
| **Application** | The execution target of the queries. Select one of the following options: - **Execute on the server** (default): for databases that are reachable from Lucanet.Cloud - Name of a Lucanet.Script Execution Application (SEA): for databases in your local network. One entry is displayed per SEA application that is created in your environment (see [Installing and Updating Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)). |
## Running a Query
To run a query in Lucanet Consolidation & Financial Planning:
1. Specify the desired statement in the **SQL query** field.
Lucanet does not restrict the SQL statements. Which tables and data you can query does not depend on your permissions in Lucanet, but on the permissions of the database user that is configured in the connection.
For sample queries, see [SQL Queries for Lucanet.Financial Warehouse](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database/sql-queries-fwh.md).
2. Click **Run query**.
The result is displayed in the **Results** area below the field as follows, for example:
Query window with the result of a statement
Above the result, the total number of records read is displayed. Below the column headers, the data type of each column is displayed.
The **Records limit** applies to the display only and cannot be changed. The query itself always runs to completion on the database, which is why the total number of records read can be higher than the number of records displayed.
If the statement cannot be executed, an error message is displayed in the **Results** area. The message comes from the database and can be a technical message.
> **Warning:** Queries on very large tables can return several million records. Restrict the result set in the statement itself using the syntax of the target database, for example `LIMIT` in PostgreSQL or `TOP` in MS SQL Server.
## Comparing Data in Multiple Windows
In Lucanet Consolidation & Financial Planning, you can open multiple query windows at the same time and position them next to each other, so that you can compare the data of related tables side by side. Each window keeps its own connection, statement, and result. Opening a new window does not affect the windows that are already open.
---
---
title: "Assigning Data"
description: "If, during a data import, new elements have been read in for the first time from the dimensions Accounts, Reporting entities and cost centers, Partner, Transaction currency, Data levels, Adjustment levels, or Transaction types, these must be assigned (only once)."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data
language: en
last_updated: 2026-05-01
---
# Assigning Data
## Overview
If, during a data import, new elements have been read in for the first time from the dimensions **Accounts**, **Reporting entities, Cost centers**, **Partners**, **Transaction currencies**, **Data levels**, **Adjustment levels**, or **Transaction types**, these must be assigned (only once).
## Missing Assignments
The data cannot be imported until all missing assignments have been rectified. If there are any assignment errors, these assignment errors will be displayed in the detail view of a **data import**, for example as follows:
Display of missing assignments in a data import
## Assigning Data
To edit missing assignments:
1. Click **2\. Assign** in the detail view of the import.
The **assignments** are displayed, for example as follows:
Assignment table with missing assignments
2. A summary of the missing assignments of the import process is displayed in the **Missing assignments** area. In each case, the system displays the number and dimension (of the assignment area) of the elements from the data source that could not be assigned to any element in the Lucanet database.
Missing assignments must be edited on the tabs with the name displayed in red.
3. Click **Edit**.
4. If necessary, activate the check box **Apply descriptions from the data source during assignment** if the descriptions are to be copied from the data source during assignment. By default, the description of the element is used in the Lucanet database.
5. If necessary, in the **Target** area, click the show ledgers icon to show further ledgers. All subledgers and all statistical ledgers released as a target for data imports can be selected.
6. Assign all elements of the data source to elements of the Lucanet database. The assignment is made using the same principle. The following options are available:
- If necessary, click **Assign automatically** in order to create the missing assignments automatically (see section [Assigning Elements Automatically](#assign_automatic)).
- Assign every element in the **Data source** area manually to an element in the **Target** area (see section [Assigning Elements Manually](#assign_manually)).
7. Click **Save** to save the assignments. The assignments are performed automatically when the data import is updated.
## Assigning Elements Automatically
To assign elements automatically:
1. Click **Assign automatically**.
Assigning elements automatically
2. The **Assign automatically** dialog is displayed:
'Assign automatically' dialog
3. Choose one of the following assignment options:
## Assignment Options
The following assignment options are available:
| Option | Description |
|---|---|
| **Assignment dependent on homonymous names** | For this assignment type, the system searches the Lucanet database for elements with the same name. Leading spaces and zeroes are removed during the search. When elements with the same name are found, a corresponding dialog is opened.
Click **Assign** to copy the proposed assignments.
**Note:** - If several matches are found, then the object cannot be assigned automatically from the data source. - If no match is found, the comparison is repeated without differentiation between upper and lower case. If the system still cannot find a match, a search is then performed without special characters. If this comparison still provides no result, then the element cannot be assigned automatically. |
| **Assignment dependent on identical account numbers** | For this assignment type, the system searches the Lucanet database for elements with the same account numbers. Only the part of a name up to the first blank is checked. All characters other than figures are deleted from this part. Leading zeros are then removed. These extracted numbers are compared directly.
If matching numbers are found, a dialog will be displayed, in which you can specify the suggestions you want to accept.
**Note:** If several matches are found (e.g. identical account numbers for the representation of cost centers and cost carriers), the element cannot be assigned automatically from the data source. |
| **Assignment according to chart of accounts** | With this assignment type, the assignment is made using a chart of accounts.
If you choose this option, select the applicable chart of accounts from the **Chart of accounts** drop-down list.
During assignment, the following dialog is displayed: |
## Assigning Elements Manually
To assign elements manually:
1. In the **Data source** area, click the desired element(s).
2. Do one of the following:
- If a new element is to be created for the element in the Lucanet database, in the **Target** area, select the item or the folder under which the element is to be created and click **Assign and create** (the assign and create icon).
- To assign the element to an element in the Lucanet database, select the desired element in the Target area and click **Assign** (the assign icon).
Assign elements
3. Repeat steps one and two for each element or the elements to be assigned together.
## Additional Icons and Functions in Assignment Tables
The following additional icons and functions are available in assignment tables:
| Icon/function | Description |
|---|---|
| Search field | Displays a search field above the **Data source** area and the **Target** area. Enter a search term and press **Enter** to run the search for an element. |
| the notassigned allassigned icon | Switch between the display of unassigned elements and all elements. |
| the partner icon | Displays the **Partner** column in the data source area. An existing partner can then be chosen from a drop-down list in the column.
**Note:** The partner column can be displayed only on the **Accounts** tab. |
| the warning yellow icon | Indicates that the name of the elements are not identical, i. e. the element in the Lucanet database has a different name than in the source system. |
| the info icon | The element has not been assigned. |
'Show target' in the 'Data source' area of an assignment table
The following commands are available in the context menu of an element:
**Show target**: shows the element assigned to an element from the data source in the Lucanet database in the **Target** area.
**Remove assignment**: revokes an existing assignment.
**Delete current row**: deletes the current row from the assignment table. The deleted element will not be imported.
## 'Uses' Tab
By which elements the assignment table is used is displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column.
---
---
title: "Automatic Cancellation in the First Planning Month"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/cancellation-inthefirst-planning-month
language: en
last_updated: 2026-05-01
---
# Automatic Cancellation in the First Planning Month
## Overview
In the **Import and Journals** workspace, automatic cancellation of postings in the first month of the planning data levels can be configured in the journal of a consolidation reporting entity with a posting of type **Automatic cancellation in the first planning month**. A cancellation is necessary to prevent already consolidated figures from being consolidated again during consolidation in the planning data level.
## Creating the 'Automatic Cancellation in the First Planning Month' Posting
The posting **Automatic cancellation in the first planning month** is created automatically in the journal of a **consolidation reporting entity** if the actual data level contains elimination of intercompany debt wizards or inventory consolidation wizards that post to the last month before the beginning of the planning data level.
Additionally, one of the following actions must be performed:
| Action | Also perform cancellation in planning |
|---------|---------|
| Synchronize planning data level with actual data level | For new lines, cancellation is activated automatically in the planning data level. |
| Creating a planning data level without template | For all lines, cancellation is activated automatically in the planning data level. |
| Creating a planning data level with template | For lines that already exist in the template, the configuration is copied from the template. For new lines, cancellation remains deactivated in the plan. |
## Configuring the 'Automatic Cancelation in the First Planning Month' Posting
To configure automatic cancellation in the first planning month:
1. If necessary, navigate to the **Journals** workspace.
2. From the drop-down lists in the tree view, choose a **planning data level** and a **consolidation reporting entity**.
3. Select the posting **Automatic cancellation in the first planning month** in the tree view.
4. Click **Edit** to open the editing mode.
5. The detail view of a posting of the type **Automatic cancellation in the first planning month** is displayed as follows, for example:
Posting 'Automatic cancellation in the first planning month'
6. If necessary, configure the posting (see following section).
## Options in the 'Automatic Cancelation in the First Planning Month' Posting
The following options are available in a posting of the type **Configure automatic cancellation in the first plan month**.
| Option | Description |
|--------|-------------|
| Postings in actual data level | **Also perform cancellation in planning**: Activate the check box for postings to be canceled in the first month of the planning data level. |
| Update list now and execute cancellation in the planning | Click **Update list now and execute cancelation in the planning** to execute the cancelation.
**Note:** The link **Update list now and execute cancelation in the planning** is only available when the posting is not (or no longer) in editing mode. |
| Synchronize planning data level with actual data level | If necessary, click **Synchronize planning data level with actual data level** to synchronize the planning data level with the actual data level (see section [Synchronizing Planning Data Levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/synchronize-planning-data-level.md)).
**Note:** The link **Synchronize planning data level with actual data level** is only available when the posting is not (or is no longer) in editing mode. |
---
---
title: "Basic Configuration"
description: "This page provides an overview of the basic configurations for Consolidation & Financial Planning, enabling you to adapt the solution to your needs."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp
language: en
last_updated: 2026-05-01
---
# Basic Configuration
## Overview
This page provides an overview of the basic configurations for Consolidation & Financial Planning, enabling you to adapt the solution to your needs. The following links will take you directly to the detailed descriptions:
- Change the language of the data model (see [Changing the Data Model Language on the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configure-webclient0.md)).
- Configure the date and number format (see [Basic Configuration for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md)).
- Install and update Lucanet SEA if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script (see [Installing and Updating Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)).
---
---
title: "Basic Elements"
description: "This page describes the most important elements in Consolidation 2."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/basic-elements-conso-2
language: en
last_updated: 2026-05-01
---
# Basic Elements of Consolidation 2
## Overview
The following section describes the most important elements in Consolidation 2. For further details, see the links below.
## Basic Elements
The following elements are used in Consolidation 2:
| Element | Description | More information |
|---|---|---|
| Group | A group includes the totality of all units to be consolidated.
The **group structure** can be defined using consolidation dimensions and consolidation areas. | [Defining the Group Structure](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure.md) |
| Consolidation dimension | All elements of an enterprise that you wish to consolidate together, e.g., **companies**, **segments** or **business areas**, are summarized in [consolidation dimensions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md). The consolidation dimension serves as a link between the [organization elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md) and the consolidation areas and specifies how data of a corporate group are to be segmented. | [Consolidation Dimensions and Dimension Elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) |
| Consolidation dimension element | Consolidation dimension elements represent **economic units** such as companies, segments, or business units.
Any number of consolidation dimension elements can be created and grouped together in each consolidation dimension. | [Consolidation Dimensions and Dimension Elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) |
| Consolidation area | The consolidation areas are the **object of the consolidation**, i.e. the consolidation is performed in the consolidation areas.
The values from the referenced organization elements are transferred to the consolidation areas with the app for [data transfer and proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md). | [Consolidation Areas and Units](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) |
| Consolidation unit | Consolidation units **represent the consolidation dimension elements** in consolidation areas.
A **default consolidation unit** is to be defined for each consolidation area. In addition to the default consolidation unit, any number of **consolidation units** can be assigned to a consolidation area. | [Consolidation Areas and Units](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) |
| Consolidation unit group | To simplify administration, consolidation units can be **grouped** into consolidation unit groups. | [Consolidation Areas and Units](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) |
| Master data administration | To create consolidated financial statements, you must first define the master data that forms the basis for Consolidation 2.
Using the master data management, the following issues within a group are defined, displayed and saved: - **Investment relationships** in the form of ownership interests - **Consolidation methods** for the consolidation area - **Amortization** of goodwill - **Translation with historical exchange rates** for foreign currency companies | [Master Data Administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md) |
| Consolidated financial statements | The **consolidated financial statements** provide a comprehensive overview of the economic situation of a group.
During consolidation, all results of the affiliated companies are combined and intercompany transactions are eliminated.
An **consolidated financial statements element** is created for each consolidated financial statements and **time period**.
In the consolidated financial statements element, all relevant **consolidation apps** are created and configured, and finally [executed](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md). | [Creating Consolidated Financial Statements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/creating-consolidated-financial-statements.md) |
| Data transfer and proportioning | With the **Data transfer and proportioning**, the values of the general and subledger are transferred from the organization elements to the consolidation areas. All dimensions (such as transaction types, partners and currencies) are taken into account **based on transaction figures**.
Furthermore, the values transferred from the single-entity financial statements are prepared for consolidation according to the consolidation method defined in the [master data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md).
Partner assignments can be updated and data from statistical ledgers adopted during the data transfer if desired. | [Data Transfer and Proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md) |
| Consolidation apps | The consolidation apps are used to perform the actual consolidation. Depending on the desired method for the consolidation different apps can be created and executed.
The following apps are currently available in the Lucanet CFO Solution Platform: - [Adjust and reclassify values in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/adjust-and-reclassify-values-in-consolidation-areas.md) - [Elimination of intercompany income and expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-income-and-expense.md) - [Elimination of intercompany debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-intercompany-debt.md) - [Elimination of intercompany profit or loss in current assets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-profit-or-loss-in-current-assets.md) - [Elimination of income from investments](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-income-from-investments.md) - [Equity elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md) - [Reclassification of profit or loss from previous year in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/reclassification-of-profit-or-loss-in-consolidation-areas.md) - [Debit/credit shifts in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/debit-credit-shifts-in-consolidation-areas.md) - [Copy postings into other consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/copy-postings-into-other-consolidation-areas.md) | [Creating and Configuring Consolidation Apps](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps.md) |
---
---
title: "CFP Add-in for Excel 365"
description: "Lucanet CFP Add-in for Excel 365 is an add-in that makes it possible to access data in the Lucanet.Financial OLAP Server from MS Excel."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in
language: en
last_updated: 2026-05-01
---
# Lucanet CFP Add-in for Excel 365
**Lucanet CFP Add-in for Excel 365** is an add-in that makes it possible to access data in the Lucanet.Financial OLAP Server from MS Excel. The CFP Add-In for Excel 365 makes it possible to query data from MS Excel and to transfer data from MS Excel to Lucanet.Financial OLAP Server. The add-in can be used to access figures and other information in Lucanet directly from an Excel workbook. The add-in also makes it possible to import Excel plannings or postings into the Lucanet database.
## Supported Excel Versions
Depending on the operating system, CFP Add-In for Excel 365 supports the following Excel versions:
| MS Windows | macOS |
|---|---|
| MS Excel 365/MS Excel 2021 or higher Excel for the Web | MS Excel for macOS 365/MS Excel for macOS 2021 or higher |
> **Warning:** The Lucanet CFP Add-in for Excel can only be used with the **Consolidation & Financial Planning** solution in the **Lucanet CFO Solution Platform**. The add-in cannot be used with Lucanet.Financial Client.
>
> Customers who used the integrated Lucanet.Excel.Add-in (XLAM) in Lucanet.Financial Client, can use a migration assistant to convert legacy formulas to the formula syntax used by the Lucanet CFP Add-in for Excel 365. For more information, see [Migrating From Integrated Excel.Add-in to CFP Add-in for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/migrating-from-integrated-to-cfp-add-in.md).
- [Querying Data from Lucanet](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data.md)
- [Transferring Data from MS Excel to Lucanet](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet.md)
- [Installing the CFP Add-In for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/installing-cfp-add-in.md)
---
---
title: "Changing the Data Model Language of Consolidation & Financial Planning"
description: "In the overview of Consolidation & Financial Planning, you can set the language of the data model. The language of the data model includes all language-dependent elements created by the user, e. g. items and accounts."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configure-webclient0
language: en
last_updated: 2026-05-01
---
# Changing the Data Model Language of Consolidation & Financial Planning
## Overview
In the overview of Consolidation & Financial Planning, you can set the language of the data model.
The language of the data model includes all language-dependent elements created by the user, such as items and accounts.
Only those languages are displayed for which a language attribute has been created in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace, i.e., an attribute for which the **Attribute can be selected as display language** option has been activated.
To change the language of the data model:
1. In the overview of **Consolidation & Financial Planning**, click on the name of the language in which the data model is currently being displayed.
Option for changing the data model language
2. Choose the desired language in the displayed **Element name** menu.
---
---
title: "Changing the Display"
description: "On the toolbar of a ledger or schedule, special display modes are available in the dimension bar, which you can use to adjust the display as required."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/change-view
language: en
last_updated: 2026-05-01
---
# Changing the Display
## Overview
On the toolbar of a ledger or schedule, special display modes are available in the dimension bar, which you can use to adjust the display as required.
## Changing the Display
The desired display mode can be chosen from the **Change display** drop-down list:
List of display modes
## Display Modes
The following display modes are available for ledgers and schedules:
| Option | Description |
|---------|---------|
| Period view | The tree view is displayed as a period view. All periods of the chosen time period are displayed in the columns of the view. |
| Organization element | Only the organization element currently chosen in the dimension bar is displayed. The values of the last chosen period under consideration are displayed in a column. |
| Abbreviated consolidation overview | Activates the abbreviated consolidation overview; only the columns for the subtotals and the group total of the chosen element from the **Organization elements** workspace are displayed. |
| Complete consolidation overview | Activates the complete consolidation overview; all elements from the **Organization elements** workspace are displayed that are directly subordinate to the organization element chosen in the dimension bar. |
| Adjustment levels in columns | All adjustment levels of the value range are displayed. |
| Partner in columns | All of the created partners of the value range are displayed. |
---
---
title: "Configuring Accruals and Deferrals"
description: "The Accruals and deferrals accounting rule type is used to enter business transactions for the appropriate period in Lucanet. Using this accounting rule type, for example, it is possible to plan business transactions in which the services are purchased or sold in advance whereas the payment is made as a one-off payment in advance."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-accruals-deferrals
language: en
last_updated: 2026-05-01
---
# Configuring Accruals and Deferrals
## Overview
The **Accruals and deferrals** accounting rule type is used to enter business transactions for the appropriate period in Lucanet. Using this accounting rule type, for example, it is possible to plan business transactions in which the services are purchased or sold in advance whereas the payment is made as a one-off payment in advance.
If the accruals and deferrals process is repeated at particular intervals and with a specific amount, then the planning can be repeated automatically. This is practical when recurrent business transactions are involved, e.g. insurance premiums that have to be paid annually in advance.
## Configuring Accruals and Deferrals
To configure an accounting rule of the type **Accruals and Deferrals**:
1. In the dimension bar, select the combination of **data level** and **reporting entity** for which the accounting rule should apply.
2. In the tree view, select the desired element (ledger, account, or item).
3. Click **Edit** in the top right to open editing mode.
4. If you selected a ledger, open the **Balance with carry forward from previous period** tab.
5. Select **Accruals and deferrals** as the accounting rule from the **Type** drop-down list.
6. Add or delete a **time period** to, e.g., configure seasonal differences within a planning period.
> **Note:** Notes on the **add/delete time period** options:
>
> - Newly added time periods are displayed on the **Configuration** tab.
> - When deleting a time period, the currently selected tab is always deleted.
## Options on the Configuration Tab
Configuration options for Accruals and deferrals
The following options are available on the **Configuration** tab:
### VAT/Input Tax Configuration
Optionally, you can select a VAT/input tax configuration from the drop-down list (see [VAT/input tax administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax.md)).
### Period
In the **Period** field, specify the period in months during which the prepaid expenses/deferred charges should be resolved.
### Automatically Repeat Planning
Activate the **Automatically repeat planning** check box if the accruals and deferrals process is repeated at particular intervals and with a particular amount.
Once the checkbox is activated, you can enter a percentage relative to the original value. This allows you to account for both price increases and reductions.
### Payment Type
The following payment types are available:
| Payment type | Description |
|---------|---------|
| With immediate cash flow impact | If the payment will be received or made within the same month |
| Time-delayed payment | If the incoming or outgoing payments are made at different times |
| Down payment transaction | If a down payment is required when the transaction is completed |
### Cash Flow Impact
> **Note:** The **Cash flow impact** section is only visible if you selected **Time-delayed payment** or **Down payment transaction** from the payment type drop-down list.
In the **Cash flow impact** section, specify a due date for the payment, along with percentage of the outstanding receivable or liability to be paid in each case.
#### Due by date
- Enter 0 for immediate payments.
- Enter a positive number for a subsequent payment, e.g. 2 = 2 months later.
- Enter a negative number for an earlier payment, e.g. -2 = 2 months earlier.
> **Tip:** To see an example of how average incoming payments can be entered on the **Month** basis, check [Cash Flow Example](#cashflowexample).
#### Share
Enter what percentage of the outstanding receivable or liability will be paid by the specified date.
### Post to
Specify the accounts to which postings will be made in the **Post to** section.
The accounts to be specified depend on the chosen payment type.
The following options are available for the **Post to** section:
| Option | Description |
|---|---|
| **With immediate cash flow impact** | - **Bank account**: An account for the contra entry - **P&L account**: An account to which the accrued account is posted |
| **Time-delayed payment** | - **Bank account**: An account for the contra entry - **Receivables or liabilities account**: An account to which the corresponding value is posted until the cash flow impact takes effect - **P&L account**: An account to which the accrued amount is posted |
### Cash Flow Example
Customers pay after 15 days on average
Example setting for the cash flow impact
Customers pay after 30 days on average
Example setting for the cash flow impact
Customers pay after 45 days on average
Example setting for the cash flow impact
---
---
title: "Configuring Attributes"
description: "Attributes are used to define multilingual descriptions or customer-specific information for Lucanet elements.\nFor example, you can use attributes to define the names of your accounts in multiple languages."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes
language: en
last_updated: 2026-05-01
---
# Configuring Attributes
## Overview
Attributes are used to define multilingual descriptions or customer-specific information for Lucanet elements.
For example, you can use attributes to define the names of your accounts in multiple languages.
For an attribute to be available and definable for a Lucanet element, it must be created and activated for the dimension of that element.
The value of an attribute can then be defined in the element properties.
This chapter describes how to create an attribute and activate it for a dimension.
## Navigation
Attributes are managed in the **Attributes** workspace. By default, the workspace is located in the Overview under the **Administration** folder, and is displayed as follows:
'Attributes' workspace
> **Note:** The overview and all folders and workspaces contained therein can be freely defined in the [Workspace configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche.md). This means that the workspaces in your Lucanet environment may have a different name and/or be found in a different location in your overview.
## Creating an Attribute
To create an attribute:
1. Open the **Attributes** workspace and right-click the **Attributes** root folder or a folder.
2. Choose **Create | Attribute** from the context menu.
The **Create Attribute** dialog is displayed:
Create attribute
3. Configure the available options as described below.
4. Click **Save**.
## Available Options
The following options are available when creating attributes:
| Option | Description |
|---|---|
| **Type** | Type of the attribute. The following types are available: - String - Integer - Floating point number - Date - True/False |
| **Name** | Name of the attribute |
| **Key** | Key under which the attribute values are to be saved |
| **Icon** | Icon to be displayed in front of the attribute name in the user interface |
| **Attribute can be selected as display language** | Activate if you want to use this attribute to assign an alternative description to your Lucanet elements in a different language.
If this option is activated, the new display language can then be selected as the **data model language** at the bottom of the menu (see [Changing the Data Model Language on the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configure-webclient0.md)).
**Note:** This check box is only available for attributes of type **String**. |
## Configuring Attributes and Activating for a Dimension
An attribute is only available for the Lucanet elements for whose dimensions this attribute is activated.
I.e. if you want to specify descriptions for data levels in other languages, then the attribute for this language must be activated for the **Data levels** dimension.
To configure an attribute and activate it for one or more dimension(s):
1. Choose the attribute in the tree view.
2. Click **Edit** at the top right of the detail view.
The editing mode is displayed as follows, for example:
Configuring the properties of an attribute
3. If necessary, change the general properties of the attribute in the upper area (see [Available Options](#options)).
4. On the **Uses** tab, specify the dimensions for whose elements the attribute can be used, by activating the corresponding check box(es).
The values of the attribute can then be defined in the element properties on the **Attributes** tab.
5. Click **Save**.
## Exporting and Importing Attribute Values
To avoid entering attribute values individually for each Lucanet element, you can export all attribute values to an Excel file, complete them there, and import them again.
For an export of attribute values to be possible, at least one attribute must have been created.
## Exporting Attribute Values
To export attribute values:
1. Open the **Attributes** workspace and click **Export attribute values** at the top of the detail view.
2. The **Export Attributes to MS Excel** dialog is displayed.
Exporting attribute values
3. Select the dimensions for whose elements the attribute values should be exported.
4. Specify the **File name** of the export file.
5. Choose the desired export format.
6. Click **Export**.
The export file is saved in your download directory and you can add, change, or delete the attribute values for all elements of the selected dimensions.
## Importing Attribute Values
The attribute values that you have edited in an export file can be imported into Lucanet again at any time. To do this, click **Import attribute values** in the **Attributes** workspace and upload the desired file.
After the import, the import status is displayed in a separate dialog as follows, for example:
Importing attributes
---
---
title: "Configuring Contra Entries"
description: "The Contra entry accounting rule type is used for recording postings within or between P&L and balance sheet. This type of contra entry is used with depreciation in the fixed assets, for example."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-contra-entry
language: en
last_updated: 2026-05-01
---
# Configuring Contra Entries
## Overview
The **Contra entry** accounting rule type is used for recording postings within or between P&L and balance sheet. This type of contra entry is used with depreciation in the fixed assets, for example.
Depreciations do not have a cash flow impact, but reduce the value of the fixed assets (accumulated depreciation) in the balance sheet, and thus require a contra entry.
## Configuring Contra Entries
To configure an accounting rule of the type **Contra entry**:
1. In the dimension bar, select the combination of **data level** and **reporting entity** for which the accounting rule should apply.
2. In the tree view, select the desired element (ledger, account, or item).
3. Click **Edit** in the top right to open editing mode.
4. If you selected a ledger, open the **Balance with carry forward from previous period** or the **Transaction figure** tab.
5. Select **Contra entry** as the accounting rule from the **Type** drop-down list.
## Options on the Configuration Tab
Configuration options for a contra entry
The following options are available on the **Configuration** tab:
| Option | Description |
|---|---|
| **Account** | Account for the contra entry |
| **Partner** | Partner for the contra entry.
**Note:** You can only define a partner if the **Create postings on the contra account using the partners from this account** check box is deactivated. |
| **Transaction type** | Transaction type from the account’s transaction type category, used to ensure associated schedules are updated in the plan when selected.
**Note:** **Additional notes:** - Transaction types can only be selected with contra entries relating to **schedule-relevant** accounts or items. - The **transaction type** field becomes editable once an account is selected. |
---
---
title: "Configuring Database Connections"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh/datenbankverbindungen-konfigurieren
language: en
last_updated: 2026-05-01
---
# Configuring Database Connections
## Overview
This section describes the parameters that must be specified for database connections to help importing data into Lucanet.Financial Warehouse.
## Configuring Connection Information
You must configure one database connection for the **temporary** Lucanet.Financial Warehouse and one for the **persistent** Lucanet.Financial Warehouse when importing data into Lucanet.Financial Warehouse.
The following table shows the default parameters that must be specified depending on the chosen database:
| Element | Description |
|---|---|
| **Abas** | **Host**: IP address or host name of the server **Port**: Port of the server; default port: **6550** **Database:**: Name of the database **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **AS 400/DB 2** | **Host**: IP address or host name of the server **Port**: Port of the server; default port: **449** **Database:**: Name of the database **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **H2 (File-Based)** | **Database file**: Absolute path to the database file; **Note**: If the file is not present, it will be created as an empty H2 database file. **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **H2 (In-Memory)** | **Database:**: Name of the database **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **Informix** | **Host**: IP address or host name of the server **Port**: Port of the server **Database:**: Name of the database **Server**: Name of the Informix server **Identifier in double quotes**: Parameter to be defined if identifiers are parsed in double quotes **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **MS SQL Server** | **Host**: IP address or host name of the server **Port**: Port of the server; default **1433** (see also: [SQL Server: Frequently Used Ports](https://learn.microsoft.com/en-us/archive/technet-wiki/13106.sql-server-frequently-used-ports)) **Database:**: Name of the database **Instance**: Name of the instance; default: empty ( **MSSQLSERVER** is used) **Charset**: Name of the character set used; default: empty (the character set of the database is used) **Additional URL parameters**: If the SQL server is configured to accept only secure connections, you must add the following parameter: **`ssl=require`** |
| **My SQL** | **Host**: IP address or host name of the server **Port**: Port of the server; default default port: **3306** **Database**: Name of the database **useUnicode**: Activates the use of Unicode; default: Yes **characterEncoding**: See default: empty **Additional URL parameters:** - Current MySQL versions often require a time zone setting: `serverTimezone=UTC` - The following parameters can be used to resolve heap issues: `defaultFetchSize=500;useCursorFetch=true` - If the SQL Server is set to accept only secure connections, you need to add the following parameters: `useSSL=true;BrequireSSL=true;verifyServerCertificate=false` |
| **ODBC** | **Data source name**: Name of the data source specified in the ODBC Data Source Administrator **Additional URL parameters**: No additional URL parameters are necessary for the use with Lucanet |
| **Oracle** | **Host**: IP address or host name of the server **Port**: Port of the server; default port: **1521** **System ID (SID)**: SID of the server; usually three or four letters **Database:**: Name of the database **Note**: For some Oracle versions, the name must also be entered in the **Schema** field. |
| **SAP** | **Host**: IP address or host name of the server **Note**: The use of route strings for **SAProuter** is also supported **Port**: Port of the server; Does not normally have to be specified, because Lucanet chooses the port according to the instance number (33xx). **Instance number**: Two numbers that represent the instance to which a connection is to be established. **Note**: Do not use the three-digit SAP SID! |
---
---
title: "Configuring Display Settings"
description: "General display settings, which you only have to configure once, can be defined for ledgers and schedules. The display settings automatically apply to all ledgers and schedules in the Reporting and analyzing workspace."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings
language: en
last_updated: 2026-05-01
---
# Configuring Display Settings
## Overview
General display settings, which you only have to configure once, can be defined for ledgers and schedules. The display settings automatically apply to all ledgers and schedules in the **Reporting and analyzing** workspace.
## Display Settings Shown as a Video
The following video gives you an overview of the **display settings**:
Video: https://player.vimeo.com/video/858589589?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
## Opening Display Settings
The display settings for ledgers and schedules are opened via the context menu of the **three dots icon** the three dots icon in the header of the first column of a ledger or schedule:
Context menu used to open the display settings
The **Display settings** dialog is then displayed as follows, for example:
Display settings dialog
## Configuring Display Settings
The following options are available in the **Display settings** dialog:
| Option | Description |
|---|---|
| **Hide empty rows and columns** | - **Accounts/items dimension** — elements whose rows or columns are to be hidden if they contain zero values - **Other dimensions** — additional dimension elements whose rows or columns are to be hidden if they contain zero values
**Note:** If any check box under **Hide empty rows and columns** is activated and you then use the search for elements in a ledger or a schedule, a dialog asks whether to turn off this setting so all search results become visible. For details, see [Searching in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/search-ledgers-schedules.md).
|
| **Filter accounts** | Defines the display of accounts: - **Show all accounts** — Accounts without postings are also displayed. - **Display accounts with posting only** |
| **Show additional columns** | Defines whether and which additional columns are to be displayed in the periods view: - **Between the periods** — display of differences between the periods - **Other columns** — display of subtotals and/or the total amount |
| **Number format** | Defines the display of numbers: - **Number display in** — formatting of the displayed values - **Decimal places** — number of displayed decimal places |
---
---
title: "Configuring Investments"
description: "The Investment accounting rule type can be used to plan new investments and their depreciation/amortization. The configuration specifies the bank account, value-added tax and cash flow impact. Furthermore, the rule including the useful life and the accounts for the accumulated depreciation/amortization in the balance sheet and the expense in the P&L are determined."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-investment
language: en
last_updated: 2026-05-01
---
# Configuring Investments
## Overview
The **Investment** accounting rule type can be used to plan new investments and their depreciation/amortization. The configuration specifies the bank account, value-added tax and cash flow impact. Furthermore, the rule including the useful life and the accounts for the accumulated depreciation/amortization in the balance sheet and the expense in the P&L are determined.
## Configuring Investments
To configure an accounting rule of the type **Investment**:
1. In the dimension bar, select the combination of **data level** and **reporting entity** for which the accounting rule should apply.
2. In the tree view, select the desired element (ledger, account, or item).
3. Click **Edit** in the top right to open editing mode.
4. If you selected a ledger, open the **Balance with carry forward from previous period** tab.
5. Select **Investment** as the accounting rule from the **Type** drop-down list.
6. **Add** or **delete a time period** to, e.g., configure seasonal differences within a planning period.
> **Note:** Notes on the **Add/Delete time period** options:
>
> - Newly added time periods are displayed on the **Configuration** tab.
> - When deleting a time period, the currently selected tab is always deleted.
## Options on the Configuration Tab
Configuration options for an Investment
The following options are available on the **Configuration** tab:
### VAT/Input Tax Configuration
Optionally, you can select a VAT/input tax configuration from the drop-down list (see [VAT/input tax administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax.md)).
### Depreciation/Amortization Rule
The following depreciation/amortization rules are available:
| Rule | Description |
|---------|---------|
| No depreciation/ amortization | If the investment is not to be depreciated/amortized |
| Immediate depreciation/ amortization | If the depreciation/amortization is to take effect immediately |
| Straight-line depreciation/ amortization | If the investment is to be depreciated in equal monthly amounts over its useful life |
| Declining balance method of depreciation/ amortization: | If the investment is to be depreciated using a fixed annual percentage rate |
### Useful Life
In the **Useful life** field, you can enter the term of the depreciation/amortization in months.
> **Note:** This field is only visible if you selected either **Straight-line depreciation/amortization** or **Declining balance method of depreciation/amortization**.
### Percentage
In the **Percentage** field, you can enter the percentage for calculating the annual depreciation/amortization amount.
> **Note:** This field is only visible if you selected **Declining balance method of depreciation/amortization.**
### Payment Type
The following payment types are available:
| Payment type | Description |
|---------|---------|
| With immediate cash flow impact | If the payment will be received or made within the same month |
| Time-delayed payment | If the incoming or outgoing payments are made at different times |
| Down payment transaction | If a down payment is required when the transaction is completed |
### Cash Flow Impact
> **Note:** The **Cash flow impact** section is only visible if you selected **Time-delayed payment** or **Down payment transaction** from the payment type drop-down list.
In the **Cash flow impact** section, specify a due date for the payment, along with percentage of the outstanding receivable or liability to be paid in each case.
#### Due by date
- Enter 0 for immediate payments.
- Enter a positive number for a subsequent payment, e.g. 2 = 2 months later.
- Enter a negative number for an earlier payment, e.g. -2 = 2 months earlier.
> **Tip:** To see an example of how average incoming payments can be entered on the **Month** basis, check [Cash Flow Example](#cashflowexample).
#### Share
Enter what percentage of the outstanding receivable or liability will be paid by the specified date.
### Post to
Specify the accounts to which postings will be made in the **Post to** section.
The accounts to be specified depend on the chosen depreciation/amortization rule and the payment type.
The following options are available for the **Post to** section:
| Option | Description |
|---|---|
| **No depreciation/ amortization** | - **Bank account**: An account for the contra entry - **Receivables or liabilities account**: An account to which the corresponding value is posted until the cash flow impact takes effect.
(Only with **time-delayed** payment type) |
| **Immediate, straight-line and declining balance method of depreciation/ amortization** | - **Bank account**: An account for the contra entry - **Receivables or liabilities account**: An account to which the corresponding value is posted until the cash flow impact takes effect
(Only with **time-delayed** payment type) - **Accumulated depreciation/amortization in the balance sheet**: An account used for correcting the asset value reduced by depreciation - **Depreciation/amortization in the P&L**: An account where the depreciation/amortization is to be posted
(Only with **time-delayed** payment type) - **Account for payment received or made:** An account to which the down payment will be posted until the service is provided
(Only with **down payment transaction** payment type) |
### Cash Flow Example
Customers pay after 15 days on average
Example setting for the cash flow impact
Customers pay after 30 days on average
Example setting for the cash flow impact
Customers pay after 45 days on average
Example setting for the cash flow impact
---
---
title: "Configuring Payments"
description: "The Payment accounting rule type is used for all accounts and items relating to business transactions with a cash flow impact. The Payment type is the most frequently occurring rule in the P&L."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-payment
language: en
last_updated: 2026-05-01
---
# Configuring Payments
## Overview
The **Payment** accounting rule type is used for all accounts and items relating to business transactions with a cash flow impact. The **Payment** type is the most frequently occurring rule in the P&L.
## Configuring Payments
To configure an accounting rule of the type **Payment**:
1. In the dimension bar, select the combination of **data level** and **reporting entity** for which the accounting rule should apply.
2. In the tree view, select the desired element (subledger, account, item, or folder).
3. Click **Edit** in the top right to open editing mode.
4. If you selected a subledger, open the **Transaction figure** tab.
5. Select **Payment** as the accounting rule from the **Type** drop-down list.
6. **Add** or **delete a time period**,to,e.g., configure seasonal differences within a planning period.
> **Note:** Notes on the **Add/Delete time period** options:
>
> - Newly added time periods are displayed on the **Configuration** tab.
> - When deleting a time period, the currently selected tab is always deleted.
## Options on the Configuration Tab
Configuration options for a Payment
The following options are available on the **Configuration** tab:
### Basis
In the **Basis** drop-down list, select the periodicity for the payment calculation.
The available options vary depending on the starting month of the fiscal year.
**If the fiscal year starts in January,** the following options are available:
- Month, Quarter, Trimester, Semester.
**If the fiscal year starts in any month other than January**, the following options are available:
- Month, Quarter, Trimester, Semester, Calendar year, Quarter in the fiscal year, Trimester in the fiscal year, Semester in the fiscal year, Fiscal year.
### VAT/Input Tax Configuration
Optionally, you can select a VAT/input tax configuration from the drop-down list (see [VAT/input tax administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax.md)).
### Payment Type
The following payment types are available:
| Payment type | Description |
|---------|---------|
| With immediate cash flow impact | If the payment will be received or made within the same month |
| Time-delayed payment | If the incoming or outgoing payments are made at different times |
| Down payment transaction | If a down payment is required when the transaction is completed |
### Cash Flow Impact
> **Note:** The **Cash flow impact** section is only visible if you selected **Time-delayed payment** or **Down payment transaction** from the payment type drop-down list.
In the **Cash flow impact** section, specify a due date for the payment, along with percentage of the outstanding receivable or liability to be paid in each case.
How you configure the cash flow impact depends on the selected **Basis**.
#### Due by date:
Month basis
- Enter 0 for immediate payments.
- Enter a positive number for a subsequent payment, e.g. 2 = 2 months later.
- Enter a negative number for an earlier payment, e.g. -2 = 2 months earlier.
> **Tip:** For an example of how average incoming payments can be entered on the **Month** basis, see [Cash Flow Example](#cashflowexample).
#### Due by date:
Quarter, Trimester, Semester, Calendar Year basis
The column displays the **due by date** with the notation **a+b** or **a-b**.
- For a, enter the month of the date of payment, e.g. 4 for April.
- Specify the time offset for b. The time offset depends on what periodicity you have set. Proceed as follows:
- For a later payment, enter +, e.g. 4+2 = 4th month (April), 2 quarters, trimesters, semesters or calendar years later.
- For an earlier payment, enter -, e.g. 4-2 = 4th month (April), 2 quarters, trimesters, semesters or calendar years earlier.
#### Share
Enter what percentage of the outstanding receivable or liability will be paid by the specified date.
### Post to
Specify the accounts to which postings will be made in the **Post to** section.
The accounts to be specified depend on the chosen payment type.
The following options are available for the **Post to** section:
| Option | Description |
|---|---|
| **With immediate cash flow impact** | - **Bank account**: An account for the contra entry |
| **Time-delayed payment** | - **Bank account**: An account for the contra entry - **Receivables or liabilities account**: An account to which the corresponding value is temporarily posted until the cash flow impact takes effect |
| **Down payment transaction** | - **Bank account**: An account for the contra entry - **Receivables or liabilities account**: An account to which the corresponding value is temporarily posted until the cash flow impact takes effect - **Account for payments received or made**: An account to which the down payment is temporarily posted until the service is provided. |
### Cash Flow Example
Customers pay after 15 days on average
Example setting for the cash flow impact
Customers pay after 30 days on average
Example setting for the cash flow impact
Customers pay after 45 days on average
Example setting for the cash flow impact
---
---
title: "Configuring Period Locks"
description: "Period locks are used to lock and unlock all postings in Lucanet. All data imports, postings, data transfers from MS Excel, and entries in exchange rate tables must be permitted for the combination of data level, adjustment level, time and consolidation unit."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks
language: en
last_updated: 2026-09-29
---
# Configuring Period Locks
## Overview
**Period locks** are used to lock and unlock all postings in Lucanet.
All data imports, postings, data transfers from MS Excel, and entries in exchange rate tables must be permitted for the combination of **data level**, **adjustment level**, **time** and **consolidation unit**.
There are two types of period locks:
- In **period locks for postings**, the periods for each data level, each reporting entity and each consolidation area are defined for the periods in which postings can be made.
- The periods in which exchange rates can be created are defined for a combination of the data level and time dimensions in **Period locks for exchange rates**.
If the status, postings, or exchange rates are edited, these **changes are logged** and displayed under the period locks.
## Creating Period Locks
To create a period lock:
1. In the **Import and Journals** folder, open the **Period locks** workspace.
2. In the drop-down list of the tree view, choose the data level for which you want to create a period lock.
3. Right-click a folder in the tree view and select **Create | Period lock - postings** or **Create | Period lock - exchange rates**:
Creating period locks
4. The **Create Period Lock** dialog is displayed.
5. Enter a **name** for the period lock and **save** your entries.
6. Configure the period lock (see following section).
## Configuring Period Locks
You can configure period locks as follows:
### Period lock for Postings
You can define the **dimension** to which the period lock is to apply and in which **periods** postings, data imports, and data transfers from MS Excel are allowed to be performed and changed in the detail view of a **period lock for postings**.
Proceed as follows:
1. In the detail view of the desired period lock, click **Edit**.
2. If necessary, configure the general options in the top area of the detail view (see [General Options](#general_options)).
3. Lock or unlock the desired periods (see [Locking or Unlocking Periods](#lock_or_unlock)).
### General Options
The following options are available in period locks for postings in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Change the name of the period lock. |
| **Edit time period** | Click the edit icon to edit the period covered by the period lock. - **Entire data level** — All periods of the data level for which the period lock was created are monitored. - **Individual selection** — Activates the period selector, in which you can choose the period of the data level that monitors the period lock. |
| **Edit adjustment levels** | Click the edit icon to edit the adjustment levels to which the period lock is to apply. - **All adjustment levels** — The period lock applies to all defined adjustment levels. - **Individual selection of adjustment levels** — Activates a table in which you can choose the adjustment levels that the period lock is to monitor. |
| **Activating/Deactivating a Period Lock** | A period lock can be **activated** or **deactivated**. The following options are available: - **Period lock is activated** — The period lock monitors the postings for the respective dimension configuration.
**Note:** As soon as you reactivate a deactivated period lock, a dialog will appear in which you must enter a reason for the reactivation. - **Period lock is deactivated** — The period lock does not monitor the postings for the respective dimension configuration.
**Note:** Deactivated period locks are indicated by a lock icon in the tree view. |
| **Edit Reporting Entities and Consolidation Areas** | Click **Edit Reporting Entities and Consolidation Areas** to add or remove reporting entities and/or consolidation areas. - **All reporting entities and consolidation areas** — The period lock applies to all reporting entities and consolidation areas. - **Individual selection** — Activates a table in which you can choose the reporting entities and consolidation areas to which the period locks are to apply.
**Note:** You can also choose **folders with reporting entities and/or consolidation areas** in the table. The period lock will then apply to all reporting entities and/or consolidation areas contained in this folder. The period lock will be dynamically adjusted if the content of the respective folder in the **Reporting entities** and/or **Groups** workspace changes. |
### Locking or Unlocking Periods
- Periods are **unlocked** for postings by **activating** the check boxes.
- Periods are **locked** for postings by **deactivating** the check boxes.
The icon indicates for which elements in a period the **creation**, **changing**, or **deletion** of postings is permitted or not permitted (see section [Status display](#status))
### Period Lock for Exchange Rates
The **Exchange rates and periods** area in the detail view of a **period lock for exchange rates** defines the periods in which exchange rate tables can be changed or new ones created, and the periods in which no entries and changes are allowed.
Proceed as follows:
1. In the detail view of the desired period lock, click **Edit**.
2. If necessary, configure the general options in the top area of the detail view, (see [General Options](#general_options_exchangerates)).
3. Lock or unlock the desired periods (see [Locking or Unlocking Periods](#locking-or-unlocking-periods-1)).
### General Options
The following options are available in the top area of the detail view in **Period locks for exchange rates**:
| Option | Description |
|---|---|
| **Name** | Change the name of the period lock. |
| **Edit time period** | Click the edit icon to edit the period covered by the period lock. - **Entire data level** — All periods of the data level for which the period lock was created are monitored. - **Individual selection** — Activates the period selector, in which you can choose the period of the data level that monitors the period lock. |
| **Activating/Deactivating a Period Lock** | A period lock can be **activated** or **deactivated**. The following options are available: - **Period lock is activated** — The period lock monitors the postings for the respective dimension configuration.
**Note:** As soon as you reactivate a deactivated period lock, a dialog will appear in which you must enter a reason for the reactivation. - **Period lock is deactivated** — The period lock does not monitor the postings for the respective dimension configuration.
**Note:** Deactivated period locks are indicated by a lock icon in the tree view. |
### Locking or Unlocking Periods
- Periods are unlocked by activating the check boxes.
- Periods are locked by **deactivating** the check boxes.
The icon indicates for which elements in a period the creation, changing, or deletion of postings is permitted or not permitted (see section [Status display](#status))
## Status Display
The icon indicates for which elements in a period the **creation**, **changing**, or **deletion** of postings is permitted or not permitted:
Displaying for which elements in a period creating, changing, and deleting postings is permitted
The following table shows the meaning of the icons:
| Icon | Description |
|---------|---------|
| the audit trail open icon | The creation, changing, and deletion of postings or exchange rates is permitted. |
| the audit trail notallowed icon | The creation, changing, and deletion of postings or exchange rates is not permitted. |
| the audit trail notall elements icon | The creation, changing, and deletion of postings or exchange rates is only permitted for individual elements below a root folder or for individual periods. This icon is only displayed for root folders and for the **All periods** column. |
## Displaying the Change Log
If the status, postings, or exchange rates are edited, these **changes are logged** and displayed under the period locks.
To open the change log, navigate to the desired period lock and, in the detail view, open the **Audit trail** tab. The tab is displayed as follows, for example:
'Audit Trail' Tab
To start logging changes from a specific point in time, you can set **checkpoints**. As soon as you create a checkpoint, postings and exchange rate tables that are changed are listed again in the log.
To do this, click **Add checkpoint** on the **Audit trail** tab and, when creating the checkpoint, enter a name and, if necessary, a note for the checkpoint.
The checkpoint is then displayed in the change log as follows:
New checkpoint
---
---
title: "Configuring Residual Amounts"
description: "Residual amounts are created automatically in the Organization elements workspace when displaying a group by levels using nested consolidation areas."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/configure-residual-value
language: en
last_updated: 2026-05-01
---
# Configuring Residual Amounts
## Overview
Residual amounts are created automatically in the **Organization elements** workspace when displaying a group by levels using nested consolidation areas. Residual amounts can correct possible multiple recordings of consolidation units. One residual amount is created per consolidation unit which was recorded several times, containing the reference to consolidation unit and the associated reference to consolidation unit cancellation. Residual amounts **cannot** be deleted.
## Configuring Residual Amounts
Edit a residual amount
To configure a residual amount:
1. In the tree view, click a residual amount.
2. Click **Edit** at the top right to open the editing mode.
3. Activate the check box **Specify name, icon, formatting and attributes individually** if you wish to define these properties individually for the reference and not adopt them from the referenced cost center.
4. Click **Save**.
---
---
title: "Configuring the Dimension Bar"
description: "The dimension bar can be used to configure the display as required. The settings made and the chosen dimensions determine the display in the tree view."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-dimension-bar
language: en
last_updated: 2026-05-01
---
# Configuring the Dimension Bar
## Overview
The **dimension bar** can be used to configure the display as required. The settings made and the chosen dimensions determine the display in the **tree view**.
## Dimension Bar in the Reporting and Analyzing Workspace
The dimension bar is displayed in the ledgers and schedules, for example as follows:
Dimension bar in the Reporting and analyzing workspace
## Settings and Dimensions
The following settings and dimensions are available in the dimension bar of ledgers and schedules:
#### Search
Lets you find ledger elements — such as items, accounts, formulas, folders, references, and total lines — directly in the tree view (see [Searching in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/search-ledgers-schedules.md)).
#### Change display
Changes the display mode in ledgers and schedules (see [Changing the display](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/change-view.md)).
#### the switch to transaction figures icon
or
Switches between the display of balances and transaction figures.
> **Warning:** The button has no effect on accounts and items that contain only transaction figures.
#### View
The choice of [view](https://support.lucanet.com/en/documentation/glossary.md#view) defines which dimensions can be configured in the dimension bar. Additional views can be added or existing views edited at any time (see [Creating and configuring views](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views.md)).
> **Note:** If **Hide fixed or unused dimensions** is activated for the selected view, the drop-down lists for dimensions that are fixed to a single element or not used in the dimension bar are hidden. For details, see [Creating and Configuring Views](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views.md).
#### Time period
Setting of the period for which values are to be displayed in the columns of the tree view. The period that can be chosen depends on the time periods defined for the set data level. In account hierarchies (balance sheet, profit and loss statement, derived hierarchies, schedules, etc.), you can switch between the monthly, quarterly and yearly view.
#### Adjustment level, data level, organization element, transaction currency, display currency, partner
Additional dimensions for the configuration of the desired display
---
---
title: "Configuring Values of Attributes"
description: "Attributes are used to define multilingual descriptions or customer-specific information for Lucanet elements. The configuration of attributes is generally possible for all dimensions, except for fiscal years. However, only the attributes that were defined in Lucanet.Financial Client in the Attributes workspace and have been activated for a dimension are displayed and can be edited."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/configure-attribute-values
language: en
last_updated: 2026-05-01
---
# Configuring Values of Attributes
## Overview
Attributes are used to define multilingual descriptions or customer-specific information for Lucanet elements.
The configuration of attributes is generally possible for all dimensions, except for fiscal years.
However, only the attributes that were defined in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace and have been activated for a dimension are displayed and can be edited.
## 'Attributes’ Tab
All attributes that were defined and activated for a dimension in Lucanet.Financial Client in the **Attributes** workspace are displayed on the **Attributes** tab in the detail view.
'Attributes' Tab
## Configuring Values of Attributes
You can edit the value of an attribute by opening the edit mode of the element and clicking in the corresponding cell in the **Value** column.
If the option **Attribute can be selected as display language** has been activated in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace, the configured display languages are displayed in the upper table on the tab and can be edited there.
In addition, the following types of attributes are available:
- **String**
- **Integer**
- **Floating point number**
- **Date**
- **True/False**
---
---
title: "Configuring Workspaces"
description: "To enable the creation of Excel reporting templates in a workspace, a directory structure must exist in this workspace and that directory structure must contain object type Lucanet.Excel-Reporting."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/configure-workspace-excel-reporting
language: en
last_updated: 2026-05-01
---
# Configuring Workspaces
## Overview
To enable the creation of Excel reporting templates in a workspace, a directory structure must exist in this workspace and it must be possible to create the object type **Lucanet.Excel-Reporting** in this directory structure.
## Creating a Directory Structure
To create a directory structure:
1. Right-click the root folder or a folder in the **Workspace configuration** and select **Create | Directory structure** from the context menu.
Creating a directory structure
2. Enter the **name** of the directory structure.
3. Click **Save**.
## Adding Object Type for Excel Reporting
To add an object of type Lucanet-Excel-Reporting in a directory structure:
1. Click the name of the desired directory structure in the **Workspace configuration**.
2. Click **Edit**.
3. Click the **Object type** column and choose **Lucanet.Excel-Reporting** from the drop-down list.
Selecting the object type 'Lucanet.Excel-Reporting'
4. Click **Save**.
The directory structure is then displayed as a workspace in the overview, and an element of type **Lucanet.Excel-Reporting** can be created and edited there.
---
---
title: "Consolidation"
description: "The Lucanet.Financial Consolidation allows you to consolidate your enterprise. \nThe Consolidation 1 enables wizard-based elimination of intercompany debt and elimination of intercompany income and expense.\nConsolidation 2 is an enhancement of Consolidation 1 that offers new functions as well as comprehensive automatic consolidation."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation
language: en
last_updated: 2026-05-01
---
# Consolidation
## Overview
The **Lucanet.Financial Consolidation** allows you to consolidate your enterprise. The following consolidation options are available:
The [Consolidation 1](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1.md) enables **wizard-based** elimination of intercompany debt and elimination of intercompany income and expense.
[Consolidation 2](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2.md) is an enhancement of Consolidation 1 that offers new functions as well as comprehensive automatic consolidation. Various apps make it possible to perform consolidation and generate a range of reports.
- [Consolidation 1](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1.md)
- [Consolidation 2](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2.md)
---
---
title: "Consolidation & Financial Planning"
description: "Visualize data on the go, present analyses and reports simply at the touch of a button, put business decisions on a valid basis: With Lucanet Consolidation & Financial Planning, you have exactly the right tool for this. Display the most important key figures and comparison views in a dashboard. Access your reporting data in the shortest possible time - with maximum data security."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning
language: en
last_updated: 2026-06-03
---
## Consolidation & Financial Planning
Import or visualize data on the go, present analyses and reports simply at the push of a button, provide a valid basis for business decisions: With **Lucanet Consolidation & Financial Planning**, you can access data in the Lucanet.Financial Client from the comfort of your browser. This is just as easy to do as in Lucanet.Financial Client. **Lucanet Consolidation & Financial Planning** and Lucanet.Financial Client work based on the same data. If data are changed in Lucanet.Financial Client, these changes will also be visible in **Lucanet Consolidation & Financial Planning** and vice versa.
Balance sheet in the 'Consolidation & Financial Planning' solution
[Request demo](https://www.lucanet.com/en/request-demo/)
The Lucanet Consolidation & Financial Planning [solution](https://support.lucanet.com/en/documentation/glossary.md#solution) offers you:
- [Visualization made simple with dashboards:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard.md) You can display the key indicators and comparative views on a dashboard.
- [Fast and secure reporting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze.md): Access your reporting data in minimum time – and with maximum data security. Create manual postings or detailed posting reports.
- [Data import and journal management:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals.md) Import data into reporting entities or Lucanet.Financial Warehouse, centrally manage journal entries and data imports, and flexibly control access to period-specific data.
- [Planning Functions:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning.md) Plan flexibly by month, quarter, or year, use automatic accounting rules, flexible revenue and tax configurations, and planning wizards for complex calculations. Benefit from sheets that offer advanced possibilities for your financial planning and formula creation in natural language.
- [Consolidation Functions:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation.md) Consolidate your company with wizard-based debt, expense, and income consolidation. Use advanced features and a wide range of apps for comprehensive, automatic consolidation and efficient creation of customized reports.
- [Dimension Management:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions.md) Individually manage and customize Lucanet dimensions. Various dimensions such as reporting entities, organizational elements, currency translation, partners, data levels, adjustment levels, transaction types, and fiscal years are available to you.
- [CFP Add-in for Excel 365:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in.md) Use the Lucanet CFP Add-in for Excel 365 to access your data in Lucanet.Financial OLAP Server directly from Excel. Transfer data between Excel and Consolidation & Financial Planning, and conveniently import planning data or journal entries into your Lucanet database.
- [Workspace Configuration:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche.md) Customize the Consolidation & Financial Planning overview by creating and configuring user-defined folders, ledgers, schedules, or directory structures.
> **Note:** With the arrival of the **Lucanet CFO Solution Platform**, Lucanet. **Web Client** now has a new name: **Lucanet Consolidation & Financial Planning**.
## First Steps with Consolidation & Financial Planning
Our instructions will help you get started with **Lucanet Consolidation & Financial Planning** in next to no time:
- [User Interface of Lucanet Consolidation & Financial Planning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/user-interface-cfp.md)
- [Basic Configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp.md)
---
---
title: "Consolidation 1"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1
language: en
last_updated: 2026-05-01
---
# Consolidation 1
## Overview
The **Consolidation 1** enables **wizard-based elimination of intercompany debt**, **elimination of intercompany income and expense**, and **inventory consolidation**.
You must generally perform the following steps to configure and execute Consolidation 1:
- [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)
- [Creating and Editing Configurations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configurations-consolidation-1.md)
- [Creating and Configuring Consolidation Wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards.md)
- [Automatic Cancellation in the First Planning Month](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/cancellation-inthefirst-planning-month.md)
---
---
title: "Consolidation 2"
description: "Lucanet Financial Consolidation is your solution for seamless and efficient financial consolidation.\nAutomate the entire consolidation process with Consolidation 2 using apps and benefit from maximum transparency, accuracy and user-friendliness."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2
language: en
last_updated: 2026-05-01
---
# Lucanet Consolidation 2
## Overview
**Lucanet Financial Consolidation** is your solution for seamless and efficient financial consolidation.
Automate the entire consolidation process with Consolidation 2 using apps and benefit from maximum transparency, accuracy and user-friendliness.
The solution offers the following functions:
- Mapping group structures over time
- Master data administration
- Proportional transfer of consolidation data to consolidation areas according to the investment relationships within the group
- Automatic consolidation including:
- [Debit/credit shifts in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/debit-credit-shifts-in-consolidation-areas.md)
- [Elimination of income from investments](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-income-from-investments.md) (incl. report on consolidation differences)
- [Elimination of intercompany income and expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-income-and-expense.md) (incl. report on consolidation differences)
- [Elimination of intercompany debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-intercompany-debt.md)(incl. report on consolidation differences)
- [Equity elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md) (currently with limited functionality)
- [Reclassification of profit or loss from previous year in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/reclassification-of-profit-or-loss-in-consolidation-areas.md)
- [Adjust and reclassify values in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/adjust-and-reclassify-values-in-consolidation-areas.md)
- [Elimination of intercompany profit or loss in current assets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-profit-or-loss-in-current-assets.md)
- [Copy postings into other consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/copy-postings-into-other-consolidation-areas.md)
> **Warning:** We recommend that customers who have used the apps of **Consolidation 2** or **Consolidation 2 Next Generation** in **Lucanet.Financial Client** read the following notes before using Consolidation 2 in the CFO Solution Platform:
>
> [Notes on Migration from Lucanet.Financial Client](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/migration-from-lnfc.md)
---
---
title: "Consolidation Areas and Units"
description: "Consolidation areas are used to summarize all consolidation units that are to be consolidated together. This could be groups or sub-groups, for example."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2
language: en
last_updated: 2026-05-01
---
# Consolidation Areas and Units
## Overview
Consolidation areas are used to summarize all **consolidation units** that are to be consolidated together. This could be groups or sub-groups, for example.
To facilitate administration, elements can also be grouped into **consolidation unit groups**.
Additionally, **total lines** can be used to display the total values for each consolidation area and consolidation unit group.
> **Note:** Consolidation areas are the **object of consolidation**, i.e. consolidation is performed in the consolidation areas. The values from the referenced organization elements are transferred to the consolidation areas using the app for [Data transfer and proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md). Based on the clear assignment of organization elements to [consolidation dimension elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) and consolidation units, it is always possible to determine which values come from which organization elements.
>
> A single consolidation dimension element (e.g., a company) can be included in multiple consolidation areas.
>
> If a group consists of several **foreign currency companies**, all relevant **exchange rate tables** have to be stored for the individual consolidation units.
## Creating a Consolidation Area
To create a new consolidation area, select the folder **Consolidation areas** in the **Groups** workspace and choose **Create | Consolidation area** from the context menu.
The **Create Consolidation Area** dialog is displayed as follows:
'Create consolidation area’ dialog
Please configure the following options:
| Option | Description |
|---|---|
| Name | Name of the consolidation area |
| Default consolidation unit | Selection of the [consolidation dimension element](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) that are to be used as the default consolidation unit of the consolidation area.
**Note:** The default consolidation unit defines the highest-level **parent company in the consolidation area**. Based on this element, the effective ownership interests are calculated. All [consolidation dimension elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) are available for selection that have been configured beforehand. A subsequent change of the default consolidation unit is **not** possible. |
| Consolidation dimension | The dimension under which the previously selected consolidation dimension element was created is automatically used as the [consolidation dimension](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md). |
| Start of the fiscal year | Start of the [fiscal year](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/fiscal-years.md) of the consolidation area |
| Default currency | [Default currency](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation.md) to be used for the consolidation area |
## Configuring a Consolidation Area
In addition to the default consolidation unit, you can configure the following for a consolidation area:
### Adding Further Consolidation Units
In each consolidation area, consolidation units can be created in addition to the default consolidation unit.
The number of consolidation units is limited to the number of consolidation dimension elements that were selected when creating the consolidation area.
Proceed as follows:
1. Select the **consolidation area** under which the consolidation unit is to be created in the structure view and do one of the following:
- Choose **Create | Transaction currency** from the context menu
- Click **Create consolidation unit** in the detail view
2. The **Create consolidation unit** dialog is displayed as follows:
Create consolidation unit
3. Select the **consolidation dimension element(s)** to be referenced as consolidation unit in the drop-down list and click **Apply**.
4. Click **Save**.
### Grouping Consolidation Units
All defined consolidation units are shown directly below their consolidation area. To **facilitate administration**, elements can also be grouped into consolidation unit groups.
Proceed as follows:
1. In the structure view, select the **consolidation area** under which the consolidation unit group is to be created and select the **Create | Consolidation unit group** from the context menu.
2. Enter a **name** for the consolidation unit group and save it.
3. In the structure view, select the **consolidation unit group** and create the desired consolidation units below the group as described under [Adding Further Consolidation Units](#add).
### Adding Currency Translation
Currency translation within a consolidation area is always necessary if there are **foreign currency companies** in the group. If a group consists of several foreign currency companies, all relevant exchange rate tables of the individual consolidation units must be included.
To create an **exchange rate table**, proceed as follows:
1. In the structure view, highlight the **consolidation area** under which the exchange rate table is to be created, and click **Edit** in the detail view.
2. Click **Add element** below the exchange rate table and select the desired exchange rate tables:
Add exchange rate table
.
3. Click **Apply** and **Save**.
### Adding a Total Line
In order to display **total values**, any number of total lines can be created for every **consolidation area** and every **consolidation unit group**.
Select the element under which you want to create a total line and select **Create | Total line** from the context menu.
In the detail view of a total line, you can also define whether you want to **calculate the subtotal until the previous total line**.
'Create total line’ dialog
## Deleting an Element
To delete an element in the **Consolidation areas** workspace, right-click the desired element and choose **Delete** from the context menu.
---
---
title: "Consolidation Dimensions and Consolidation Dimension Elements"
description: "The consolidation dimension acts as an important link: It connects your existing organization elements with the consolidation areas. Organization elements represent, e.g., companies, business units, segments or cost centers."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2
language: en
last_updated: 2026-05-01
---
# Consolidation Dimensions and Consolidation Dimension Elements
## Overview
The consolidation dimension acts as an important link: It connects your existing [organization elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md) with the [consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md). Organization elements represent, e.g., companies, business units, segments or cost centers.
The consolidation dimension defines whether the consolidation is to take place by companies, by business units or according to another scheme.
All similar consolidation dimension elements are summarized in a consolidation dimension.
During configuration, consolidation dimension elements can be linked to the organization elements of the single-entity financial statements by a unique reference. For the consolidation, the consolidation dimension elements adopt the data from the organization elements.
> **Note:** The consolidation dimension element itself does not contain values in the form of figures or the like; it primarily determines the configuration of the consolidation dimension element with regard to partners and currency.
## Creating a Consolidation Dimension
To be able to create consolidation dimension elements, you must first create the corresponding consolidation dimension.
Do one of the following:
- Right-click the **Consolidation dimensions** folder in the tree view and choose **Create | Consolidation dimension** from the context menu.
- Select the group under which the consolidation dimension is to be created and click **Create consolidation dimension** in the detail view.
Create consolidation dimension
Enter a **name** for the element and click **Save**.
> **Note:** When [creating a new group](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure.md), the consolidation dimension **Legal consolidation** is automatically created, which can be deleted or renamed as required.
## Deleting or Editing a Consolidation Dimension
To delete a consolidation dimension, right-click the desired element and select **Delete** from the context menu.
To edit the **name** of a consolidation dimension, click **Edit** in the detail view of the element.
## Creating a Consolidation Dimension Element
To create one or several consolidation dimension elements:
1. Select the consolidation dimension under which the consolidation dimension element is to be created in the structure view and choose one of the following options:
- From the context menu, select **Create | Consolidation dimension element**.
- In the detail view, click **Create consolidation dimension element**.
The **Create consolidation dimension element** dialog is displayed as follows:
Create consolidation dimension element
2. In the drop-down list, select the **organization element(s)** that you want to reference as consolidation dimension elements and click **Apply selection**.
3. Select if you want to **Create and assign a partner automatically**.
If you do **not** activate the option, you can subsequently create the partner manually and/or assign it to already created partners (see _Deleting or Editing Consolidation Dimension Element_).
4. Click **Save**.
The consolidation dimension elements are created and the detail view of the consolidation dimension is shown as follows, for example:
Details of a configured consolidation dimension
> **Note:** If a consolidation dimension element is **incompletely configured**, because, for example, no partner could be adopted from the referenced organization element, the icon of the consolidation dimension element is displayed in the tree view with a warning triangle the black triangle icon.
>
> You can complete the details by editing them as described in the following section.
## Deleting or Editing a Consolidation Dimension Element
To delete a consolidation dimension element from a consolidation dimension, right-click the desired consolidation dimension element and select **Delete** from the context menu.
To edit the details of a consolidation dimension element, click **Edit** in the detail view of the element. The following details can be edited:
Edit details of a consolidation dimension element
---
---
title: "Copy Postings into Other Consolidation Areas"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/copy-postings-into-other-consolidation-areas
language: en
last_updated: 2026-08-11
---
# Copy Postings into Other Consolidation Areas
## Overview
Postings made manually in one consolidation area do not automatically apply to other consolidation areas.
Use the app **Copy postings into other consolidation areas** to avoid copying these postings manually from one consolidation area to another, which is tedious and error-prone. The app takes over that work: configure it once, and use the app to copy **manual postings** and **translations with historical exchange rates** into other consolidation areas with a single execution, as often as you need.
> **Note:** You can create the app as a subordinate element of a **Consolidated financial statements** element. Multiple instances of the app can coexist for the same **Consolidated financial statements** element, for example to copy postings between several pairs of consolidation areas.
## Configuring the App 'Copy Postings into Other Consolidation Areas'
To configure the app **Copy postings into other consolidation areas**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the base and target consolidation areas and the consolidation-unit assignment between them:
Step 'Settings'
The following options are available in the **Settings** step:
| Option | Description |
|---|---|
| Base consolidation area | Consolidation area from which the postings are copied. |
| Target consolidation area | Consolidation area into which the postings are copied. The target consolidation area must differ from the base consolidation area. |
| Consolidation unit assignments | By default, consolidation units are assigned by matching name between the base and target consolidation areas. If no consolidation unit with a matching name exists in the target consolidation area, the corresponding postings are skipped.
If necessary, activate the **Specify individual consolidation unit assignments** check box to explicitly assign each base consolidation unit to a target consolidation unit in the displayed table. |
### Postings
In the **Postings** step, specify which types of postings are copied and the folders involved:
Step 'Posting types'
The following options are available in the **Postings** step:
| Option | Description |
|---|---|
| Manual postings | Activate to copy manual postings from the base consolidation area to the target consolidation area.
| Translations with historical exchange rates | Activate to copy postings from the translation with historical exchange rates. Requires an exchange rate table to be configured on the target consolidation area. |
| Source folder(s) | Folder(s) in the base consolidation area that contain the postings to be copied. You can choose one or more source folders. |
| Target folder | Folder in the target consolidation area in which the copied postings are created. Only one target folder can be chosen. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the copypostings red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the copypostings green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the App 'Copy Postings into Other Consolidation Areas'
You can execute the app **Copy postings into other consolidation areas** either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Executing the Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
On execution, the app copies the selected postings from the base consolidation area to the target consolidation area for the period range of the **Consolidated financial statements** element. Each execution first deletes the postings that the app created during a previous run and then creates them again based on the current configuration and current data. This makes it safe to execute the app repeatedly.
> **Note:** The execution completes successfully even if no postings match the current configuration for the selected period.
>
> If name-based assignment is used and no target consolidation unit with a matching name is found for a base consolidation unit, the corresponding postings are skipped and a note is displayed.
> **Warning:** The execution fails with an error if:
> - The **Specify individual consolidation unit assignments** check box is activated and a base consolidation unit has no corresponding entry in the assignment table.
> - The adjustment level for consolidation postings on the target consolidation area is locked for postings.
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created. When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md).
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the app is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name.
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Creating a Postings Report"
description: "In Lucanet Consolidation & Financial Planning, you can create and download a Postings report to analyze, audit, and share posting data."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/create-postings-report
language: en
last_updated: 2026-05-28
---
# Creating a Postings Report
## Overview
In **Lucanet Consolidation & Financial Planning**, you can create and download a **Postings report** to analyze, audit, and share posting data. You can set the following for the report:
- Filter the data to be exported by data level, period, posting types, reporting entities and/or consolidation areas
- Define the sort order of the exported data
- Choose **Excel** or **Text** output format
## Creating a Postings Report
A postings report can either be created from the **overview** of the Lucanet Consolidation & Financial Planning solution or from the **Journals** workspace:
- In the **overview** of the Lucanet Consolidation & Financial Planning solution, open the **Extras** menu at the bottom and select **Postings Report**:
Creating a postings report from the 'Extras' menu
- In the **Journals** workspace, select the data level and reporting entity or consolidation area for which you want to create the report and click **Postings Report** at the top right:
Creating a postings report form a journal
The **Postings Report** dialog is displayed as follows, for example. Configure the options for the report as described in the following section.
'Postings Report' dialog
## Configuring and Downloading a Postings Report
Before you download the report, you can configure the following options for the report:
## Output format
File type of the export ( **Excel** or **Text**)
## File name
File name of the export. The correct extension is appended automatically.
## Data level
**Data level** for which the posting report is to be created
## Period
**Period** for which the posting report is to be created
## Posting type check boxes
Selection of the posting types to be included in the posting report:
- **Manual postings**
- Postings created by **Forms/Sheets**
- **Excel postings**
- Postings created by **apps**
- Postings created by **data imports**
- Postings created by **planning wizards**
In addition, you can **only include finalized postings** and/or **only include postings from the general ledger and the subledger.**
## Sorting
Options for sorting the postings in the report. You can sort:
- **By posting date**
- **By date of last change**
- **By posting number**
## Reporting entities tree
Reporting entities for which the posting report is to be created.
You can also **select all reporting entities** at once.
## Consolidation areas tree
Consolidation areas for which the posting report is to be created.
You can also **select all consolidation areas** at once.
Once all options are configured, click **Download report** and the report file will be saved to the **Downloads** folder in your file system.
The report is structured as follows, for example, depending on the options you selected:
Example of a postings report
---
---
title: "Creating and Configuring a Structure"
description: "The structure of your enterprise is recreated in the Organization elements workspace."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-configure-structure
language: en
last_updated: 2026-05-01
---
# Creating and Configuring a Structure
## Overview
The structure of your enterprise is recreated in the **Organization elements** workspace.
## Creating and Configuring a Structure
You can set up not only one but any number of structures, because there is no limit to the number of references that can be created to the elements from the [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) and the [Groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) workspace, nor to the combinations that can be formed from them.
To create and configure a structure:
1. If needed, create a folder in which the structure is to be set up:
2. Create the desired **organization group(s)/reference(s)/total line(s)**.
3. Move individual organization elements between the hierarchy levels with the context menu commands **Cut** and **Paste**.
4. Define the sequence of the organization elements of a level with the help of the context menu command **Change order.**
The 'Change Order' dialog
5. Delete individual organization elements using the menu command **Delete**.
---
---
title: "Creating and Configuring Accounts"
description: "All postings in Lucanet are made to accounts. Accounts are only changed by postings and therefore behave the same way as accounts in conventional financial accounting systems."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-accounts
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Accounts
## Overview
All [postings](https://support.lucanet.com/en/documentation/glossary.md#posting) in Lucanet are made to [accounts](https://support.lucanet.com/en/documentation/glossary.md#account). Accounts are only changed by postings and therefore behave the same way as accounts in conventional financial accounting systems.
## Accounts in Lucanet
Besides user-defined accounts in [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger), there are also accounts in Lucanet that are automatically created and have special tasks. The following accounts are available in Lucanet:
| Option | Description |
|---------|---------|
| Item account | Because it is not possible to post to [items](https://support.lucanet.com/en/documentation/glossary.md#item), an item account is created automatically if the item is affected by a data import, for example. |
| Transfer account | Each subledger is assigned a transfer account to the general ledger. All postings to subledger accounts are automatically made to the respective transfer account also in the general ledger. |
| Debit/credit shift account | A debit/credit shift can be set up for each general ledger account in Lucanet. When a debit/credit shift is performed, the respective account is disclosed either on the assets side or the equity and liabilities side of a balance sheet structure, depending on the balance (credit or debit). |
| Account for rounding errors | These accounts disclose rounding errors resulting from currency translations or proportionate consolidations. |
| Account for differences from currency translation | Differences from the currency translation are incurred whenever different exchange rates are used for the translation of financial statements of foreign subsidiaries into a single group currency. For example, in accordance with the temporal method, some accounts are translated at closing exchange rates and other ones at historical exchange rates. The resulting differences are automatically entered on the respective accounts for differences from the currency translation by Lucanet if the respective option has been chosen for the account. |
## Creating an Account
You can create an account from the context menu of an item or from the context menu of the root folder in ledgers and schedules.
To create an account:
1. Open the ledger (general ledger, subledger, or statistical ledger) and navigate to the item or root folder under that you want to create the account.
2. Right-click the item or root folder and choose **Create | Account** from the context menu.
Creating an account at an item
Creating an account in the root folder
## Configuring an Account
Different options are available for configuring an account, depending on the ledger (general ledger, subledger, or statistical ledger) in which you create the account:
### General
The **General** tab is displayed as follows, for example:
'General' tab in the 'Create Account' dialog
The following options are available on the **General** tab:
| Option | Description |
|---|---|
| **Type** | Element type |
| **Located in** | Shows where the account is located |
| **Name** | Account name |
### Data type
The **Data type** tab is displayed as follows, for example:
'Data type' tab in the 'Create Account' dialog
The following options are available on the **Data type** tab:
| Option | Description |
|---|---|
| **Data type** | Regardless of the ledger in which it was created, every account in Lucanet can have one of the following data types: - **Currency amount** — The value is displayed as currency amount. Accounts of type **Currency amount** are used to display business transactions in ledgers. - **Percentage** — The value is displayed as a percentage. Accounts of type **Percentage** are used to display percentages of amounts, such as utilization rates. - **Decimal number** — The value is displayed as a decimal number. Accounts of type **Decimal number** are used to display statistical values, such as the number of employees.
**Note:** Accounts created under an item take on the data type properties of the directly superordinate item. |
| **Debit/Credit** | Choose whether it is a debit or credit account: - **Debit** — Positive values are considered as debit values, negative values as credit values - **Credit** — Positive values are considered as credit values, negative values as debit values
**Note:** Accounts created under an item adopt the debit/credit setting of the directly superordinate item. |
| **Period type** | Choose the period type of the account: - **Transaction figure** — The value of the account is a transaction figure. - **Balance** — The value of the account is a balance. - **Balance with carry forward from previous period** — The value of the account is a balance with carry forward from the previous period.
In general ledgers, the period type is, by default, a **Balance with carry forward from the previous period** and cannot be changed.
**Note:** Accounts created under an item take on the period type of the directly superordinate item. |
### Partners
The **Partners** tab is displayed as follows, for example:
'Partners' tab in the 'Create Account' dialog
The following options are available on the **Partners** tab:
| Option | Description |
|---|---|
| **Partners** | Shows the partner assignment of the account. |
### Value transfer (in subledgers only)
The **Value transfer** tab is displayed as follows, for example:
'Value transfer' tab in the 'Create Account' dialog
The following options are available on the **Value transfer** tab:
| Option | Description |
|---|---|
| **Transfer account** | Choose a general ledger account to that the transfer of the subledger account is to be posted. |
| **Transaction type** | Transaction types provide information on the reason for changes to an account. Choose a transaction type for the transfer. The choice of transaction type depends on the transaction type category of the subledger account. |
### Transaction type category
The **Transaction type category** tab is displayed as follows, for example:
'Transaction type category' tab in the 'Create Account' dialog
The following transaction type categories are available:
| Option | Description |
|---|---|
| **Uncategorized** | The account does not have any category. |
| **Fixed assets** | All transaction types defined for the **Fixed assets** transaction type category are available for the account. The fixed assets are created from items and accounts with this category. |
| **Provisions** | All transaction types defined for the **Provisions** transaction type category are available for the account. The provisions are created from items and accounts with this category. |
| **Loans** | All transaction types defined for the **Loans** transaction type category are available for the account. The loans are created from items and accounts with this category. |
| **Equity** | All transaction types defined for the **Equity** transaction type category are available for the account. The statement of changes in equity is created from items and accounts with this category. |
> **Warning:** The transaction type category is taken from the superordinate item.
### Currency translation
The **Currency translation** tab is displayed as follows, for example:
'Currency translation' tab in the 'Create Account' dialog
> **Warning:** The currency translation is available only for accounts with the data type **Currency amount** and the period type **Balance** or **Balance with carry forward from previous period**.
The following options are available on the **Currency translation** tab:
| Option | Description |
|---|---|
| **Display adjustment to closing exchange rate on a separate account** | The exchange difference in equity (adjustment to the closing exchange rate) can be disclosed on a separate account for each account with the data type **Currency amount** and the period type **Balance** or **Balance with carry forward from previous period**. If you activate the check box, an account will be automatically created under the item of the account that the differential is posted to. You can change the account name if necessary.
**Note:** Once you have saved your configuration, the account name is displayed as a link on the **Currency translation** tab in the **Account Properties** dialog. You can navigate to the account by clicking the link. |
### Debit/credit shift
The **Debit/credit shift** tab is displayed as follows, for example:
'Debit/credit shift' tab in the 'Account Properties' dialog
Debit/credit shifts are configured so that negative values for each debit/credit shift are posted as positive values on a contra account. The following options are available:
| Option | Description |
|---|---|
| **Activate debit/credit shift** | When the check box is activated, further configuration options are displayed. |
| **Account display** | Define whether the debit or credit value is to be disclosed on the debit/credit shift item. |
| **Debit/credit shift item** | Contra item in the general ledger |
| **Transaction types** | Click **Show** to define the transaction types on the debit account and the transaction types on the credit account: - **Transaction types on debit account:** Define for which transaction types the debit/credit shift to the initial item is to be performed. - **Transaction types on credit account:** Define for which transaction types the debit/credit shift to the debit/credit shift account is to be performed. |
| **Debit/credit shift per partner** | If you activate the check box, the debit/credit shift is performed at partner level. |
> **Warning:** The **Debit/credit shift** tab is only displayed for already created accounts.
>
> The debit/credit shift can only be deactivated for accounts in the general ledger.
After saving the configuration, the balance is disclosed under the contra item if a negative value is created in the initial account. To display the values, a debit/credit shift account is automatically created under the configured contra item, for example:
Example of an activated debit/credit shift at account level
### Number format
The **Number format** tab is displayed as follows, for example:
'Number format' tab in the 'Create Account' dialog
On the **Number format** tab, the way numbers are displayed for a formula can be configured. The following options are available:
| Option | Description |
|---|---|
| **Apply number format** | Applies the number format that is different from the display settings |
| **Number display** | Formatting of the displayed values |
| **Decimal places** | Number of displayed decimal places |
> **Warning:** The **Number format** tab is only displayed for formulas in statistical ledgers.
>
> Configurations on the **Number format** tab overwrite the number format defined in the [display settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md).
>
> As soon as a different number format has been configured, the icon is displayed in the account line.
### Attributes
The **Attributes** tab is displayed as follows, for example:
Attributes
**Attributes** are used to define multilingual or customer-specific names for Lucanet elements.
The **Attributes** tab displays all attributes that have been defined in Lucanet.Financial Client in the Attributes workspace and are enabled for this dimension.
You can edit the value of an attribute by opening the element's edit mode and clicking on the corresponding row in the **Value** column.
---
---
title: "Creating and Configuring Adjustment Level Groups"
description: "You can create and configure any number of adjustment level groups in Lucanet. To view the cumulative postings/values of the individual adjustment levels and adjustment levels for consolidation postings, you can consolidate adjustment levels and adjustment levels for consolidation postings into adjustment level groups."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/create-configure-adjustmentlvl-groups
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Adjustment Level Groups
## Overview
You can create and configure any number of adjustment level groups in Lucanet. To view the cumulative postings/values of the individual adjustment levels and adjustment levels for consolidation postings, you can consolidate adjustment levels and adjustment levels for consolidation postings into **adjustment level groups**.
This is advisable because IFRS-compliant annual financial statements in Lucanet also comprise adjustment postings in accordance with IFRS guidelines in addition to the purely data imports. If you create an adjustment level group that contains the adjustment level for data imports as well as the adjustment level for IFRS adjustments, you can display the IFRS consolidated financial statements by selecting the corresponding adjustment level group in the dimension bar.
## Creating Adjustment Level Groups
To create an adjustment level group:
1. Right-click the **Adjustment level groups** root folder and choose **Create | Adjustment level group** from the context menu. The **Create Adjustment Level Group** dialog is displayed:
Creating an adjustment level group
2. Enter the name of the element in the **Element name** field.
3. Click **Save**.
## Configuring Adjustment Level Groups
Dialog for editing an adjustment level group
To configure an adjustment level group:
1. Click the name of the adjustment level group in the tree view.
2. Click **Edit** at the top right to open the editing mode.
3. On the **Assigned adjustment levels** tab, assign all the adjustment levels and adjustment levels for consolidation postings to the adjustment level group that are to be regarded together, e.g. all the adjustment levels and adjustment levels for consolidation postings for a single accounting standard.
4. Click **Save**.
---
---
title: "Creating and Configuring Adjustment Levels"
description: "You can create and configure adjustment levels in Lucanet. Adjustment levels determine the guidelines according to which a value is posted and measured."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/manage-adjustment-levels
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Adjustment Levels
## Overview
You can create and configure adjustment levels in Lucanet. **Adjustment levels** determine the guidelines according to which a value is posted and measured. There is at least one adjustment level on which all data imports are saved by default. In general, it is useful to reserve an adjustment level for the data imports from the financial accounting source system. This ensures that the values on this adjustment level in Lucanet precisely match the data of internal accounting. Any adjustment postings (HGB, IFRS, US-GAAP or corporation valuation adjustment postings in connection with the consolidated financial statements) should then be made on adjustment levels created specifically for this purpose.
## Creating Adjustment Levels
To create an adjustment level:
1. Right-click the root folder **Adjustment levels** or another folder.
2. Choose **Create | Adjustment level** from the context menu. The **Create Adjustment Level** dialog is displayed:
Creating an adjustment level
3. Specify the name of the element.
4. Activate the **Data imports will be saved in this adjustment level by default** check box if you want to use the adjustment level as the adjustment level for data imports.
5. Click **Save**.
## Configuring Adjustment Levels
Dialog for editing an adjustment level
To configure an adjustment level:
1. In the tree view, right-click the name of the adjustment level.
2. Click **Edit** at the top right to open the editing mode.
3. If needed, change the **name** of the element.
4. Activate the **Data imports will be saved in this adjustment level by default** check box if you want to use the adjustment level as the adjustment level for data imports.
5. Activate the **Lock adjustment level for other postings** check box if you want to block the adjustment level for all postings except data imports. In this way you can calibrate whether the import data matches the data of the source system.
6. Click **Save**.
> **Note:** Notes on adjustment levels:
>
> - There is exactly one adjustment level for data imports that cannot be deleted.
> - If the adjustment level is defined as a data import adjustment level, then the option **Lock adjustment level for other postings** is displayed.
---
---
title: "Creating and Configuring Adjustment Levels for Consolidation Postings"
description: "Adjustment levels for consolidation postings are used to post consolidation postings if the Consolidation 2 is used for consolidation."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels/create-configure-adjustmentlvl-consolidation-postings
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Adjustment Levels for Consolidation Postings
## Overview
Adjustment levels for consolidation postings are used to post consolidation postings if [Consolidation 2](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2.md) is used for consolidation.
## Creating Adjustment Levels for Consolidation Postings
To create an adjustment level for consolidation postings:
1. Right-click the **Adjustment levels** root folder.
2. Choose **Create | Adjustment level for consolidation postings** from the context menu. The **Create Adjustment Level For Consolidation Postings** dialog is displayed:
Creating an adjustment level for consolidation postings
3. Specify the name of the element.
4. Click **Save**.
> **Note:** After creating an adjustment level for consolidation postings, you can configure this adjustment level and change its name.
---
---
title: "Creating and Configuring Consolidation Apps"
description: "After you have defined the master data of your group and configured the app for data transfer and proportioning, you can now continue with the configuration of the consolidation apps."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Consolidation Apps
## Overview
After you have defined the master data of your group and configured the app for data transfer and proportioning, you can now continue with the configuration of the **consolidation apps**.
Which apps you configure depends on the consolidation method(s) to be applied.
The following apps are currently available in the Lucanet CFO Solution Platform:
- [Adjust and reclassify values in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/adjust-and-reclassify-values-in-consolidation-areas.md)
- [Copy postings into other consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/copy-postings-into-other-consolidation-areas.md)
- [Debit/credit shifts in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/debit-credit-shifts-in-consolidation-areas.md)
- [Elimination of income from investments](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-income-from-investments.md)
- [Elimination of intercompany income and expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-income-and-expense.md)
- [Elimination of intercompany debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-intercompany-debt.md)
- [Elimination of intercompany profit or loss in current assets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-profit-or-loss-in-current-assets.md)
- [Equity elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md)
- [Reclassification of profit or loss from previous year in consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/reclassification-of-profit-or-loss-in-consolidation-areas.md)
> **Warning:** For customers who have previously used apps of **Consolidation 2** or **Consolidation 2 Next Generation** in the **Lucanet.Financial Client**, we recommend reading the following notes before using Consolidation 2 on the CFO Solution Platform:
>
> [Notes on the migration from Lucanet.Financial Client](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/migration-from-lnfc.md)
## Creating a Consolidation App
To create a consolidation app, proceed as follows:
1. Open the **Consolidated financial statements** workspace.
2. Select the combination **group** and **data level** from the dimension bar for which you want to create a consolidation app.
3. Select the desired **Consolidated financial statements** element or folder and choose **Create | App** from the context menu.
4. In the displayed dialog, choose the desired **app type**:
Create app
5. Enter a **name** for the element.
6. **Save** the element.
The app will then be displayed below the Consolidated financial statements element.
---
---
title: "Creating and Configuring Consolidation Areas"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas
language: en
last_updated: 2026-06-03
---
# Creating and Configuring Consolidation Areas
## Overview
**Consolidation areas** contain organization elements (e.g. reporting entities, cost centers or subordinate consolidation areas) and can be used to display group and subgroup structures in Lucanet.
**Consolidation areas** are required for the wizard-assisted consolidation using Consolidation 1 and can be created in the **Consolidation areas** workspace, where the corresponding reporting entities can be assigned.
## Creating a Consolidation Area
Consolidation areas are created in the **Consolidation areas** workspace. To create a consolidation area:
1. Open the **Consolidation areas** workspace in the **Consolidating** folder.
2. Right-click the **Consolidation areas** folder or a folder and choose **Create | Consolidation area** from the context menu:
Create a consolidation area
3. The **Create consolidation area** dialog is displayed:
Dialog 'Create consolidation area'
4. Enter a name for the consolidation area in the **Name** field.
5. Select the **transaction currency** in which the consolidation is to take place. **Caution**: The transaction currency cannot be changed anymore after being created!
6. Click **Save**.
The consolidation area is created.
7. In the detail view of the new consolidation area, click **Edit** and configure the consolidation area (see following section).
'Edit' button in the details view of a consolidation area
## Configuring a Consolidation Area
The detail view of a consolidation area is displayed as follows:
Detail view of a consolidation area
The following options for consolidation areas must be configured:
#### General
- **Name**: Name of the consolidation area
- **Consolidation reporting entity**: The organization element in which the consolidation postings are to be made
#### Organization elements
Composition of the consolidation area. In the table, choose:
- **Assigned organization elements**: Organization elements that are directly assigned to the consolidation area
- The **parent company**
- **Proportional**: Proportionally consolidated consolidation units
- **Percentage**: Percentage for proportionally consolidated consolidation units
- **Subordinate consolidation areas**: Consolidation areas that are subordinate to the consolidation area (= subgroups)
---
---
title: "Creating and Configuring Consolidation Reporting Entities"
description: "Consolidation reporting entities are used for postings during the consolidation."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Consolidation Reporting Entities
## Overview
**Consolidation reporting entities** are used for postings during the consolidation and are assigned to consolidation areas in the [Consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md) workspace.
## Creating Consolidation Reporting Entities
To create a consolidation reporting entity:
1. Right-click a folder and choose **Create | Consolidation reporting entity** from the context menu **.** The **Create Reporting Entity** dialog is displayed:
Creating a consolidation reporting entity
2. Specify the **name** of the element.
3. Choose the **start of the fiscal year** and the **default currency** in which the transactions of the reporting entity are to be executed.
4. Click **Save**.
## Configuring Consolidation Reporting Entities
Konfiguration eines Buchungskreises für Konsolidierungsbuchungen
To configure a consolidation reporting entity:
1. Click a consolidation reporting entity in the tree view.
2. Click **Edit** at the top right to open the editing mode.
When configuring a reporting entity, the following options are available:
#### Start of the financial year
Allows selection of the first month of the fiscal year from a drop-down list.
#### Default currency
Allows selection of the currency in which transactions of the reporting entity will be executed.
#### Partner
Partners can be assigned to reporting entities in the detail view of the respective partner (see [Creating and Configuring Partners](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners/manage-partners.md)).
#### Cost centers tab
- **Create default cost center:** Creates a default cost center if none exists.
- **Balance sheet planning per cost center:** Accumulates planning values at the individual cost center level instead of using the default cost center.
#### Currency translation tab
Allows selection of **exchange rates** created in the **Currency Translation workspace** (see [Creating and Configuring Exchange Rate Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md))
> **Note:** The message **The changes shown in red will take effect only after exporting and importing the database** is displayed when adding or deleting exchange rate tables. This indicates that the changes will not take effect until the current database is re-exported and re-imported. If needed, contact your Lucanet administrator.
#### Carry forward account tab
- Specify an **account** and a **transaction type** for the cancellation of the carry forward when importing cumulative balances.
- **Activate historical exchange rate translation:** Allows automatic translation of historical exchange rates for the next balance import.
Note: This option is only available if at least one active exchange rate table is assigned to the reporting entity.
---
---
title: "Creating and Configuring Consolidation Wizards"
description: "In Lucanet, it is possible to perform the elimination of intercompany debt, elimination of intercompany income and expense, and inventory consolidation in connection with the elimination of intercompany profit or loss by means of consolidation wizards."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Consolidation Wizards
## Overview
In Lucanet, it is possible to perform the elimination of intercompany debt, elimination of intercompany income and expense, and inventory consolidation in connection with the elimination of intercompany profit or loss by means of **consolidation wizards**. The wizards are executed on the basis of the **configurations** created in the **Consolidation areas** workspace (see [Creating and Editing Configurations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configurations-consolidation-1.md)).
## Creating a Consolidation Wizard
To create a consolidation wizard:
1. Choose one of the following options:
- Open the **journal** for the desired **data level** and **consolidation area** and select **Create** from the context menu of a folder:
Create consolidation wizard
- Open a **ledger** for the desired **data level** and **consolidation area**, right-click in the row of the ledger hierarchy for which the wizard should be created and choose **Create**:
Creating a consolidation wizard from a ledger
- In the **Show postings** dialog, click **Create posting**:
Creating a consolidation wizard from the 'Show postings' dialog
2. Choose the desired **consolidation wizard** from the **Create** menu.
3. The **Create Consolidation Wizard** dialog is displayed as follows, for example:
'Create Consolidation Wizard' dialog
4. In the **Period** drop-down list, specify the period to be taken into account for the consolidation.
5. Choose the desired configuration in the **Configuration** drop-down list.
6. Click **Continue**.
7. Configure the selected wizard (see section [Configuring Consolidation Wizards](#configuring-consolidation-wizards)) and then save the wizard.
## Available Consolidation Wizards
The following consolidation wizards are available:
| Element | Description |
|---------|---------|
| Paired elimination of intercompany debt | The **Paired elimination of intercompany debt** wizard enables the wizard-assisted elimination of debts and receivables between affiliated companies. Pair combinations of accounts are formed between reporting entities or cost centers based on settings previously made (see [Wizard for Paired Elimination of Intercompany Debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-debt.md)). |
| Lump sum elimination of intercompany debt | The **Lump sum elimination of intercompany debt** wizard allows you to perform a wizard-assisted elimination of debts and receivables between affiliated companies. This involves offsetting accounts previously defined in the **Consolidation areas** workspace against one another on a lump sum basis (see [Wizard for Lump Sum Elimination of Intercompany Debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-debt.md)). |
| Paired elimination of intercompany income and expense | The **Paired elimination of intercompany income and expense** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. Pair combinations of accounts between reporting entities or cost centers are formed based on settings previously made (see [Wizard for Paired Elimination of Intercompany Income and Expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-income-expense.md)). |
| Lump sum elimination of intercompany income and expense | The **Lump sum elimination of intercompany income and expense** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. This involves offsetting accounts previously defined in the **Consolidation areas** workspace against one another on a lump sum basis (see [Wizard for Lump Sum Elimination of Intercompany Income and Expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-income-expense.md)). |
| Elimination of intercompany income and expense based on group-internal revenue | The **Elimination of intercompany income and expense based on group-internal revenue** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. In this case, (revenue) accounts previously defined in the **Consolidation areas** workspace are offset with one or more expense accounts with allocation of a percentage (see [Wizard for Elimination of Intercompany Income and Expense Based on Group-internal Revenue](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-elimination-intercompany-income-expense-group-internal-revenue.md)). |
| Inventory consolidation | The **Inventory consolidation** wizard enables the wizard-assisted elimination of intercompany profit or loss contained in stock (inventory) between affiliated companies. Intercompany relationships are formed between reporting entities based on settings previously made in the **Consolidation areas** workspace (see [Wizard for Inventory Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-inventory-consolidation.md)). |
## Configuring Consolidation Wizards
The options to be configured depend on the selected wizard. Each wizard type has its own **General** properties, its own **Values** tab, and — for some wizards — its own **Updating Wizard** procedure. These details are documented on a dedicated page per wizard type:
| Wizard | What it configures |
|---|---|
| [Wizard for Paired Elimination of Intercompany Debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-debt.md) | Pair combinations of debt and receivable accounts between reporting entities or cost centers. |
| [Wizard for Lump Sum Elimination of Intercompany Debt](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-debt.md) | Lump-sum offsetting of debt and receivable accounts. |
| [Wizard for Paired Elimination of Intercompany Income and Expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-income-expense.md) | Pair combinations of income and expense accounts between reporting entities or cost centers. |
| [Wizard for Lump Sum Elimination of Intercompany Income and Expense](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-income-expense.md) | Lump-sum offsetting of income and expense accounts. |
| [Wizard for Elimination of Intercompany Income and Expense Based on Group-internal Revenue](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-elimination-intercompany-income-expense-group-internal-revenue.md) | Offsetting of revenue accounts against one or more expense accounts with a percentage allocation. |
| [Wizard for Inventory Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-inventory-consolidation.md) | Elimination of intercompany profit or loss contained in inventory between affiliated companies. |
> **Warning:** If you change the **configuration** of a wizard in the [Consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md) workspace and the change should take effect in the posting, the posting must be deleted in the journal and then created again because the **Update wizard** function only updates the values, but not the structure of the wizard-assisted posting.
---
---
title: "Creating and Configuring Cost Centers and Cost Center Groups"
description: "To describe in detail which costs have resulted where, it is possible to divide a reporting entity into cost centers. By using cost center groups, it is possible to group cost center sub-groups and/or cost centers together."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-cost-centers
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Cost Centers and Cost Center Groups
## Overview
To describe in detail which costs have resulted where, it is possible to divide a reporting entity into **cost centers**. By using **cost center groups**, it is possible to group cost center sub-groups and/or cost centers together.
## Creating Cost Centers and Cost Center Groups
> **Note:** When cost centers are used, it is always necessary to create a **default cost center** in Lucanet. All values which do not contain cost center information are posted to this cost center. The name of the default cost center can be selected as required.
To create a cost center or a cost center group:
1. Right-click a reporting entity or a cost center group.
2. Select **Create | Cost center** or **Cost center group** from the context menu. The **Create Cost Center** dialog is displayed:
Creating a cost center
3. Specify the element name and, optionally, add cost centers.
4. Click **Save**.
> **Note:** If you create a default cost center in a reporting entity in which postings have already been made, the message **The changes shown in red will take effect only after exporting and importing the database** is displayed. This means the default cost center will not become visible until you reimport the current database. If needed, contact your Lucanet administrator.
## Configuring Cost Centers and Cost Center Groups
Configure a cost center
To configure a cost center or a cost center group:
1. Click the name of the cost center or cost center group in the tree view.
2. Click **Edit** at the top right to open the editing mode.
3. If needed, change the **name** of the element.
4. Assign one or more **partners** to the cost center.
5. Click **Save**.
---
---
title: "Creating and Configuring Currencies"
description: "In Lucanet, a distinction is made between transaction currencies and display currencies. Transaction currencies are the currencies in which postings are made."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Currencies
## Overview
In Lucanet, a distinction is made between **transaction currencies** and **display currencies**. Transaction currencies are the currencies in which postings are made. Display currencies are the currencies in which amounts are displayed. To display values, postings in transaction currency are translated into the display currency using exchange rate tables.
## Creating Currencies
To create a currency:
1. Right-click one of the two root folders **transaction currency** or **display currency.**
2. Choose **Create | Transaction currency** or **Display currency** from the context menu. The dialog **Create Transaction Currency** or **Create Display Currency** is displayed:
Creating a currency
3. Specify the **name** of the element.
4. If needed, change the **Number of decimal places**.
5. Click **Save**.
> **Note:** **Notes on the number of decimal places:**
>
> - The number of decimal places cannot be changed subsequently.
> - The specified number refers to the rounded display of values in ledgers and schedules and not to the number of decimal places for the input of exchange rates that are applied for the currency translation.
> - The number of decimal places is limited to ten.
> **Note:** **Note on currency configuration:**
>
> After creating a currency, you can configure it and change its name.
---
---
title: "Creating and Configuring Current Account Interest Wizards"
description: "The wizard for the current account interest can be used in Lucanet to plan the automatic interest return of giro accounts and overdraft facilities."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/current-account-interest
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Current Account Interests
## Overview
The wizard for the current account interest can be used in Lucanet to plan the automatic interest return of giro accounts and overdraft facilities.
The wizard can be created for all reporting entities for values of ledgers and schedules in planning data levels, either within a **journal** or from a **ledger**.
## Creating a Current Account Interest Within a Journal
To create a current account interest within a journal:
1. Open the **Journals** workspace.
2. In the dimension bar, select the combination of a **planning data level** and **reporting entity** for which a current account interest wizard should be created.
3. Right-click the root folder and choose **Create | Current account interest** from the context menu. The **Create Current Account Interest Wizard** dialog is displayed:
Creating a current account interest wizard
4. Specify the **name** of the element and click **Continue**.
## Creating a Current Account Interest From a Ledger
To create a current account interest from a ledger:
1. Select the desired ledger (general ledger, sub-ledger or statistical ledger).
2. In the dimension bar, select the combination of **planning data level** and **reporting entity** for which the wizard should be created.
3. Right-click in the row of the ledger hierarchy for which the wizard should be created and choose **Create | Current account interest**.
Creating a wizard from a ledger
4. The **Create Current Account Interest Wizard** dialog is displayed:
Creating a current account interest wizard
5. Specify the **name** of the element and click **Continue**.
## Configuring a Current Account Interest
To configure a current account interest, click the name of the desired element in the tree view, and then click **Edit** in the top right. The configuration is divided into general properties in the header and three configuration steps in the main section of the editing mode.
### General Properties
Configuration of general properties for a current account interest
The following properties can be configured in the header:
| Property | Description |
|---------|---------|
| Element name | Name of the wizard |
| Cost center | Cost center in which the posting is to be performed by the planning wizard |
| Currency | Currency in which the posting is to be performed by the planning wizard |
| Adjustment level | Adjustment level in which the posting is to be performed by the planning wizard |
| Basis | Adjustment level (group) used as the planning basis |
### Step 'Master data'
Configuration of master data in a current account interest
The following options can be configured in the **Master data** step:
### Calculation basis
#### Account or item
Accounts and/or items that should be taken into account when calculating the interest expense or interest income
#### Balance option
Balance to be used as the calculation basis. The following options are available:
- **Balance at start of month**
- **Balance at end of month**
- **Average balance of the month**
### Interest
#### Interest rate table
- If the interest rate is always the same irrespective of the account balance, specify the desired interest rate.
- If the interest rate is dependent on the account balance, i.e. if different interest rates apply to different account balances:
1. Click the **Interest rate (%)** column and specify the desired interest rate.
2. Click **\+ Add row.**
3. Enter the value up to which the specified interest rate applies in the original row in the **To (exclusive)** column.
The value is transferred to the new row as the starting value for the value range.
4. In the new row, click the **Interest rate (%)** row and specify the desired interest rate.
5. If applicable, add further rows and follow steps 2 to 4 in each case.
> **Note:** In the column **Interest rate**, you can also specify negative interest.
> **Note:** **Note on adding a new time period in the Interest table**
>
> If different interest rates apply to the same values for specific time periods in the planning data level, add and configure these periods as needed. Select **+Add time period**. In the **New Time Period** dialog, choose the first and last period for the time range with the deviating interest rates. The new period appears in the **Interest** table, where you can configure the interest rates as required.
#### Calculate interest per value range
Activate, if the interest should be calculated for each value range. In this case, the interest is based on the value of the calculation basis per value range and the interest rate of the respective value range.
> **Note:** If the check box is not activated, the interest is calculated on the total balance of the calculation basis with the interest rate of the value range within which the total balance is situated.
#### Interest credit option
Allows selecting when the interest credits should be posted. The following options are available:
- **Every month**
- **Every last month of the calendar quarter**
- **Every last month of the calendar year**
#### Presentation in P&L
Allows selecting when the interest expense/income should be posted to the ledger. The following options are available:
- Present interest expense or income in each month
- Only present interest expense/income in the month of the interest credit
> **Note:** This option is only available if **Every last month of the calendar quarter** or **Every last month of the calendar year** is selected from **Select interest credit option.**
### Step 'Posting'
Configuration of posting details in a current account interest
In the **Posting** step, you specify the affected **accounts.**
If applicable, you can also select the desired **partner** from the drop-down list. The partner field is pre-populated with the default partner.
The following **accounts** must be specified:
| Option | Description |
|---|---|
| **Interest income (balance sheet account)** | Balance sheet account to which the interest income is posted |
| **Interest income (P&L account)** | Income account on which the interest income is shown |
| **Interest expense (balance sheet account)** | Balance sheet account from which the interest payments are posted
**Note:** If the check box is not activated, the interest is calculated on the total balance of the calculation basis with the interest rate of the value range within which the total balance is situated. |
| **Interest expense (P&L account)** | Expense account on which the interest expenses are shown |
| **Accrual account for interest (Balance sheet account)** | Balance sheet account to which the accrual for the interest is posted
**Note:** This option is only available if **Present interest expense/income in each month** is selected from **Presentation in P&L** from the **Master data** step **.** |
### Step 'Summary'
In the last step, a summary of the calculated interest amounts is displayed:
Summary of the calculated interest amounts
## Troubleshooting for Invalid Configuration due to Subsequent Debit/Credit Shift Activation
The configuration of the **Current account interest** wizard may become invalid due to a wrong **debit/credit shift** setup.
The error arises when the **Current account interest** wizard has been set up for an account for which a **debit/credit shift** is activated **subsequently** in its superordinate item, and in case that the specified accounts for the **interest income** and **interest expense** are in the same item as the debit/credit shift that was set up subsequently.
In this case, the wizard is displayed with a red warning icon:
Shows a journal and the details of a current account interest wizard. Highlighted in red are the wizard element with the red warning icon and the command 'Show error description'
To see the details of the error, click the command **Show error description** in the detail view of the wizard. The following message is displayed:
Error message
To fix the error, you can do one of the following:
- Deactivate the debit/credit shift for the respective account.
- Include the opposite side of the debit/credit shift account to the wizard's calculation basis.
- Change the accounts used for posting the interest income and interest expense.
---
---
title: "Creating and Configuring Data Transfer and Proportioning"
description: "The first step in configuring consolidated financial statements is the provision of the data basis in the consolidation areas."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning
language: en
last_updated: 2026-05-01
---
# Transferring and Proportioning Data
## Overview
The first step in configuring consolidated financial statements is the provision of the **data basis** in the [consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md).
With the app for **Data transfer and proportioning**, the values of the general, sub, and statistical ledgers of the single-entity financial statements are transferred from the [organization elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md) to the consolidation areas. In doing so, all dimensions (e.g. transaction types, partners and currencies) are taken into account based on transaction figures.
Additionally, the values transferred from the individual financial statements are prepared for consolidation according to the **consolidation method** defined in the [master data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md). This includes:
- For all investments, the addition to and disposal from the respective consolidation area are recognized using the corresponding transaction types.
- Investments are transferred proportionally according to their group shares
- For associated companies consolidated using the equity method, the transferred balances and transaction figures are first canceled so that they can subsequently be recognized and updated by the [app for equity elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md) at the equity value.
## Creating Data Transfer and Proportioning
Proceed as follows to create the app for data transfer and proportioning:
1. Open the **Consolidated financial statements** workspace.
2. Select the combination **group** and **data level** from the dimension bar for which you want to transfer and proportion the data.
3. Select the desired Consolidated financial statements element or folder and choose **Create | App** from the context menu.
4. In the displayed dialog, choose the app type **Data transfer and proportioning**.
5. Optionally, enter an individual **name** for the element.
6. **Save** the element.
The app will then be displayed below the **Consolidated financial statements** element.
## Configuring Data Transfer and Proportioning
To configure the app for **data transfer and proportiining**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, you configure general settings for the data transfer.
Step 'Settings'
#### Data transfer includes
In the **Data transfer includes** area, specify whether you want to include the **general ledger and subledgers**, **historical exchange rates**, and/or **statistical ledgers** in the data transfer and proportioning.
> **Note:** - The **Historical exchange rates** check box can only be activated together with **General ledger and subledgers**. If you deactivate **General ledger and subledgers**, **Historical exchange rates** is automatically deactivated as well. There is no dependency between **Historical exchange rates** and **Statistical ledgers**.
>
> - If no historical exchange rate has been maintained for an account in the [master data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md), the app automatically derives the historical exchange rate from the period's transaction figures for all accounts where the option **Display adjustment to closing exchange rate on a separate account** has been activated in the [account settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-accounts.md#currency-translation). In this case, the historical exchange rate is calculated as the transaction figure in the transaction currency divided by the transaction figure in the group currency. Minor deviations in the last decimal places may occur due to rounding.
**Advanced settings for statistical ledgers**
By default, the app includes all statistical ledgers and applies proportioning according to the respective consolidation method of the consolidation unit:
- **Full consolidation**: 100% data transfer
- **Proportionate consolidation**: Data transfer and proportioning according to the group share in the consolidation unit
- **Equity method**: Data transfer and 100% proportioning of data (cancellation)
If necessary, activate the option **Advanced settings for statistical ledgers** if you want to configure an individual proportioning for statistical ledgers and/or if you only want to include part of the statistical ledgers. After that, configure the displayed table:
#### Consolidation area
Consolidation areas to be included in the data transfer and proportioning:
**By default**, **all** consolidation areas within the group are included in the data transfer and proportioning.
If you only want to include certain consolidation areas in the data transfer and proportioning, activate the **Individual selection** check box and select one of the following options:
- **Include**: In the table, select individual consolidation areas to be included in the app execution.
- **Exclude**: In the table, select the consolidation areas that are to be excluded from the app execution.
### Adjustment levels
In the **Adjustment levels** step,you specify the adjustment levels for the data transfer and proportioning.
Step 'Adjustment levels'
#### Adjustment levels for the data transfer
In this table, assign the adjustment levels for the data transfer:
| Option | Description |
|---|---|
| **Basis** | Adjustment level group(s) from which the data is to be transferred |
| **Target** | Target adjustment levels to which the data is to be transferred.
**Note:** You can either **manually** select the elements in the **Target** column or click **Assign automatically** to assign the adjustment levels automatically based on **similar names**. |
#### Adjustment levels for the proportioning
In this table, assign the adjustment levels for the proportioning:
| Option | Description |
|---|---|
| **Basis** | Adjustment level group without proportioning or consolidation adjustment levels as the basis for the consolidation process. The basis for proportioning selected here must contain the target adjustment levels from the previous step. |
| **Target** | Target adjustment level for posting the adjustment to the consolidation method (proportional adjustment) |
| **Account for rounding errors** | Account for the balancing of rounding errors from proportioning |
### Organization elements
In the **Organization elements** step, you configure the data basis, i.e. the underlying organization element of the consolidation dimension elements.
It can also be defined which **currency** is to be taken into account for the data transfer.
Step 'Organization elements'
#### Data transfer from organization elements to consolidation dimension elements
In this table, assign the organization elements to the consolidation dimension elements for the data transfer:
| Option | Description |
|---|---|
| **Organization element(s)** | Organization element(s) from which the data is to be transferred |
| **Consolidation dimension element** | Consolidation dimension element to which the data is to be transferred.
**Note:** You can either **manually** select the elements in the **Consolidation dimension elements** column or click **Assign automatically** to assign the consolidation dimension elements automatically based on **similar names**. The selected consolidation dimension elements must have been defined in the **Investor** or **Investment** column on the **Investments** tab in the master data administration (see [Administrating Master Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md)). |
| **Currency** | For each entry, choose the currency that the values are to be transferred in. |
#### The data transfer includes business units or segments
Activate this check box in case of a data transfer of business units or segments (**segment consolidation**).
As these do not necessarily have the same debit and credit balances, you must then choose a **balancing account**. Any debit-credit differences in the consolidation unit will be recognized on this balancing account.
### Partners
By default, consolidation units use the same partner as the base organization element.
In the **Partner** step, you can configure the following deviations from the default:
- Define partners that will be replaced by another partner during data transfer
- Assign several partners to another partner
‘Partner’ step
To do so, activate the option **Specify individual partner assignments** and configure the assignments in the table.
You can either select the elements **manually** or click **Assign partner of a partner group automatically** to replace all partners of a partner group in the consolidation units with a partner with the name of the partner group.
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Data Transfer and Proportioning
You can execute the app for data transfer and proportioning either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md).
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Creating and Configuring Data Transformations"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-data-transformation
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Data Transformations
## Overview
**Transformation rules** determine how the data from the source system are to be transformed before they are written to Lucanet.Financial Warehouse.
Transformation rules are assigned in the **Data Transformations** workspace in Lucanet. Any number of data transformations can be created and configured.
If further transformation rules are also required, these must also be implemented, if necessary, by Lucanet.Consulting using corresponding wizards (scripts).
## Available Data Transformations
The following transformation rules can be used in data transformations:
| Transformation rules | Description |
|---------|---------|
| Adjusting posting entries and opening balance sheet values | Using this rule, posting entries and opening balance sheet values are adjusted by filling a target dimension with values based on a dimension. Information is only added if the target dimension is empty. With this transformation rule, it is possible to derive the partner code from a subledger account, for example. |
| Drill down by contra account | With this rule, a posting is used to check whether the specified dimension has been uniquely filled. If this is the case, the information is added to all further posting entries of the posting. If the specified dimension is not unique, a dummy code is used. This transformation rule makes it possible to copy the partner code to all posting entries of a posting, for example. |
| Adjusting posting headers | Using this rule, certain information is changed in the posting header (e.g. the adjustment levels or data levels to which the posting belongs). |
## Creating a Data Transformation
To create a data transformation:
1. Click the workspace **Importing data into Lucanet.Financial Warehouse** in the **Import and Journals** folder in the overview.
2. In the tree view of the workspace, right-click **Data transformations** and select the following from the context menu: **Create | Data transformation**:
Create a data transformation
3. The **Create Data Transformation** dialog is displayed:
'Create Data Transformation' dialog
4. Specify the name of the data transformation in the **Element name** field.
5. Choose the desired transformation in the **Transformation rule** drop-down list.
6. Click **Save** or press **Enter** to create the data transformation.
7. Click **Edit** in the detail view of the data transformation and configure the chosen transformation rule (see **Configuring Transformation Rules**).
## Configuring Transformation Rules
To configure the transformation rules:
### Adjusting posting entries and opening balance sheet values
The following areas must be configured:
| Area | Description |
|---|---|
| **Application range** | **Dimension**: dimension to which the data transformation is to apply **Data type**: data type (numeric or alphanumeric) **From/To**: area for which the data are to be transformed |
| **Base and target dimension** | **Basis**: dimension to be used to fill the target dimension This dimension contains the values to be checked. **Data type**: **data type** of the base dimension **Target**: dimension to be filled. The values are written in this dimension. |
| **Assignments** | **Basis Column**: **From/To**: value range that the base dimension must contain so that the target dimension is filled. **Target column**: - **Code**: value (maximum of 20 characters) to be written into the target dimension - **Name**: (optional) descriptive name for the code |
| **Filter** | **Dimension**: dimension to be filtered by **Data type**: data type to be filtered by **From/To**: value range to be filtered by |
### Drill down by contra account
| Area | Description |
|---------|---------|
| Application range | **Dimension**: dimension to which the data transformation is to apply **Data type**: data type (numeric or alphanumeric) **From/To**: area for which the transformation is to be performed |
| Dimension | Dimension to be filled |
| Dummy code | **Code**: Description to be set if the dimension is not filled with unique values. **Name**: (optional) descriptive name for the code |
| Filter | **Dimension**: dimension to be filtered by **Data type**: data type to be filtered by **From/To**: value range to be filtered by |
### Adjusting posting headers
| Area | Description |
|---------|---------|
| Application range | **Dimension**: dimension to which the data transformation is to apply **Data type**: data type (numeric or alphanumeric) **From/To**: area for which the transformation is to be performed |
| Adjustments to the posting header | **Dimension**: dimension to be changed. Available for selection are **AdjustmentLevel** and **DataLevel**. **Code**: code to be written into the dimension (maximum of 20 characters) **Name**: (optional): descriptive name for the code |
| Filter | **Dimension**: dimension to be filtered by **Data type**: data type to be filtered by **From/To**: value range to be filtered by |
## 'Uses' Tab
By which elements the data transformation is used is displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column:
---
---
title: "Creating and Configuring Directory Structures"
description: "Directory structures are workspaces that are used for creating and editing elements such as apps, scripts, or Lucanet.Excel-Reporting files. In the Workspace configuration, you can create any directory structures and individually configure which elements can be created within a directory structure. In the Overview, each directory structure is displayed in the folder as a workspace in which it was created."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Directory Structures
## Overview
Directory structures are workspaces that are used for creating and editing elements such as apps, scripts, or Lucanet.Excel-Reporting files.
In the **Workspace configuration**, you can create any directory structures and individually configure which elements can be created within a directory structure.
In the Overview, each directory structure is displayed in the folder as a workspace in which it was created.
> **Note:** Customers who have already used directory structures in Lucanet.Financial Client, can view and edit all directory structures created there in the CFO Solution Platform.
## Creating a Directory Structure
To create a directory structure:
1. Right-click the root folder or a folder in the **Workspace configuration** and select **Create | Directory structure** from the context menu. The **Create Directory Structure** dialog is displayed:
Creating a directory structure
2. Enter the **name** of the directory structure.
3. Click **Save**.
> **Note:** Directory structures can only be created below the **root folder** or a **folder**. Creating directory structures below other element types is not possible.
## Configuring Directory Structures
To configure a directory structure, click the name of the directory structure in the tree view and then at the top right click **Edit** to open the editing mode:
Editing a directory structure
If necessary, use the **Elements** tab to define which elements can be created in the directory structure. The available **object types** are described in the following section.
### Available Object Types
The following object types can be enabled in a directory structure.
| Element | Description |
|---|---|
| **App** | Used to create an app as a functional extension of the Lucanet software.
Currently, the app for [Reclassification of profit or loss from previous periods in reporting entitites](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures/reclassification-of-profit-or-loss-in-reporting-entities.md) is available. |
| **Connection** | Used to create connections that contain connection information for SQL databases |
| **Script** | Used to create scripts (see [Creating and Executing Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)) |
| **Lucanet.Excel-Reporting** | Used to create Excel reports within Lucanet.Excel-Reporting |
| **Folders** | Used to create folders |
| **Workflow** | Used to create workflows to automatically execute executable elements such as scripts, or data imports into Lucanet.Financial OLAP Server in a fixed sequence.
**Note:** (Currently, this object type can only be created but cannot yet be used.) The use of a workflow will only be available with a later version of the CFO Solution Platform. |
---
---
title: "Creating and Configuring Exchange Rate Tables"
description: "The exchange rates between currencies are defined in exchange rate tables. Lucanet offers the option of storing year-to-date exchange rates for currency translation for all exchange rate relationships (transaction currencies and display currencies) in addition to average exchange rates, closing exchange rates, and historical exchange rates."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Exchange Rate Tables
## Overview
The exchange rates between currencies are defined in **exchange rate tables**. Lucanet offers the option of storing year-to-date exchange rates for currency translation for all exchange rate relationships (transaction currencies and display currencies) in addition to average exchange rates, closing exchange rates, and historical exchange rates. You can create any number of exchange rate tables in order to model variants of the same exchange rate connections with different exchange rates in Lucanet, for example.
## Creating Exchange Rate Tables
To create one or more exchange rate table(s):
1. Right-click the **Exchange rate tables** root folder.
2. Choose **Create | Exchange rate table** from the context menu. The **Create Exchange Rate Table** dialog is displayed:
Creating an exchange rate table
3. Specify at least one **transaction currency** and one **display currency**.
4. Click **Save**.
> **Note:** An exchange rate table is created automatically for each combination of different transaction currencies and display currencies. If you have, for example, selected both EUR and USD as both transaction currency and display currency, then two exchange rate tables will be created: EUR -> USD and USD -> EUR.
## Configuring Exchange Rate Tables
Configure an exchange rate table
To configure an exchange rate table:
1. Click the name of the exchange rate table in the tree view and then click **Edit** at the top right.
2. On the **Exchange rates** tab, choose the data level for which exchange rates are to be defined from the drop-down list **Data level**.
3. Define the **currency detail**:
Retain the preselection if the exchange rate display is to take place from the view of the transaction currency (= one currency unit of the transaction currency corresponds to x currency units of the display currency).
Choose the other option if the exchange rate display is to take place from the view of the display currency (= one currency unit of the display currency corresponds to x currency units of the transaction currency).
4. Deactivate the check box **Show max. 5 decimal places** if all decimal places are to be displayed for each exchange rate.
Usually, the Lucanet software rounds the complete exchange rates in accordance with commercial principles.
5. Enter the exchange rate settings for each period (see [Defining Exchange Rate Settings for the Actual Data Level](#actualdatalevel)/ [Defining Exchange Rate Settings for Planning Data Levels](#planningdatalevel)).
### Defining Exchange Rate Settings for the Actual Data Level
The following exchange rate settings are available for the actual data level for each period:
#### Closing exchange rate
Closing exchange rate can be imported from the European Central Bank or from MS Excel (see [Importing Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/import-exchange-rates.md)).
#### Average exchange rate
Average exchange rate can be imported from the European Central Bank or from MS Excel (see [Importing Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/import-exchange-rates.md)).
> **Note:** The value is automatically determined by clicking **Calculate**.
#### Year-to-date exchange rate
Used to enter the year-to-date exchange rate.
> **Note:** The value is automatically determined by clicking **Calculate**.
#### Year-to-date start
Used to configure the beginning of the fiscal year and the determination of the year-to-date exchange rate to this period.
> **Note:** The **Year-to-date start** cell is active only if the **On account level with year-to-date exchange rate** value is selected as the default conversion type for transaction types.
>
> The month for which the switch-over to the conversion with the **Year-to-date exchange rate** was selected is at the same time the beginning of the fiscal year for the aggregation of the year-to-date values to be converted.
#### Default translation type for transactions
The following options are available:
- **On document level with average or historical exchange rate:** The average exchange rate or the historical exchange rate is used for the conversion.
- **On account level with year-to-date exchange rate:** The exchange rate stored in the Year-to-date exchange rates column or the historical exchange rate is applied for the conversion.
> **Note:** If you change the translation type for transactions and if postings already exist for reporting entities that use this exchange rate table, then the message **The changes shown in red will take effect only after a reorganization of the database** is displayed. This means that this change will have no effect until the current database is exported and then imported again.
### Defining Exchange Rate Settings for Planning Data Levels
The following exchange rate settings are available for the planning data level for each period:
#### Closing exchange rate
The closing exchange rate can be imported from the European Central Bank or from MS Excel (see [Importing Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/import-exchange-rates.md)).
#### Average exchange rate
The average exchange rate can be imported from the European Central Bank or from MS Excel (see [Importing Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/import-exchange-rates.md)).
> **Note:** The value is automatically determined by clicking **Calculate**.
---
---
title: "Creating and Configuring Execution Settings"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-execution-settings
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Execution Settings
## Overview
For a selected data source, an **execution setting** is used to specify for which elements of the Lucanet data model the import is to be executed. For every data source, any number of execution settings can be created.
## Creating Execution Settings
To create an execution setting:
1. In the **Import and Journal** folder in the **Overview**, click the **Importing data into Lucanet.Financial Warehouse** workspace.
2. In the tree view of the workspace, right-click **Execution settings** and choose **Create | Execution settings** from the context menu:
Create execution settings
3. The **Create Execution Settings** dialog is displayed:
'Create Execution Settings' dialog
4. Enter the name of the execution setting in the **Element name** field.
5. Choose the desired data source in the **Data source** drop-down list. All data sources created in the **Data sources** root folder are available for selection.
6. Click **Save** or press **Enter** to create the execution setting.
7. In the detail view of the execution setting, click **Edit** and configure the execution settings (see following section **Configuring Execution Settings**)
## Configuring the Execution Settings
The following options for execution settings must be configured on the **Configuration** tab:
| Option | Description |
|---|---|
| **Data levels, adjustment levels, reporting entities** | Data level, adjustment levels, and reporting entities for which the data are to be imported
**Note:** For reporting entities, the technical ID of the reporting entity must be specified in the source system, if necessary, depending on the script used. |
| **Fiscal year** | Fiscal year from which the data are to be exported |
| **Accounting periods** | Accounting periods whose values are to be imported
If you only want to specify one period, enter the same number in both fields. |
| **Update opening balance sheet values** | Activate this option if opening balance sheet values are to be copied (updated) |
## Viewing the Execution History
To perform the import, select the execution setting and click **Execute** in its detail view (see [Executing the Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/execute-data-import.md)). Each time an execution setting is executed, the run is recorded on its own change log.
Open the **Execution log** tab in the execution setting's change log to see when it was last executed, whether the run succeeded, and to open the detailed process log for that run.
For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
---
---
title: "Creating and Configuring Fiscal Years"
description: "If one or more reporting entities of your enterprise have a different fiscal year, then you can define the different fiscal year(s) in Lucanet."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/fiscal-years/create-configure-fiscal-years
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Fiscal Years
## Overview
If one or more reporting entities of your enterprise have a different fiscal year, then you can define the different fiscal year(s) in Lucanet.
The **default fiscal year** with the first month January is preconfigured as the element **Calendar year** in every Lucanet database.
## Creating Fiscal Years
To create a fiscal year:
1. Right-click the **Fiscal years** root folder.
2. Choose **Create | Fiscal year** from the context menu **.** The **Create Fiscal Year** dialog is displayed:
Creating a fiscal year
3. Enter the **name** and the **fiscal year abbreviation**. The abbreviation is displayed when you specify the period in the dimension bar.
4. Choose the **first month of the fiscal year** from the drop-down list. If there is already a fiscal year that starts with this month, an error message is displayed.
5. Click **Save**.
## Configuring Fiscal Years
To configure a fiscal year:
1. Click the name of the fiscal year in the tree view.
2. Click **Edit** at the top right to open the editing mode.
Editing a fiscal year
3. If needed, change the **name, abbreviation** and the **first month** of the fiscal year.
4. On the **Periodicities** tab, specify which time views will be available in the dimension bar of account hierarchies and schedules. By default, the periodicities **monthly**, **quarterly**, and **annual** are preselected.
5. Click **Save**.
---
---
title: "Creating and Configuring Formulas"
description: "Controlling indicators such as the absolute liquidity ratio, the equity ratio, and the return on sales can be created in Lucanet using formulas. Formulas can be used in all ledgers and schedules to calculate any values."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-formulas
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Formulas
### Overview
Controlling indicators such as the absolute liquidity ratio, the equity ratio, and the return on sales can be created in Lucanet using [formulas](https://support.lucanet.com/en/documentation/glossary.md#formula). Formulas can be used in all [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger) and [schedules](https://support.lucanet.com/en/documentation/glossary.md#schedule) to calculate any values. A formula comprises **variables** and mathematical **operators**. Each variable of a formula can apply to an [item](https://support.lucanet.com/en/documentation/glossary.md#item), an [account](https://support.lucanet.com/en/documentation/glossary.md#account), a different formula, a time series, or a total line in the Lucanet database.
## Variables and Operators in Formulas
The following variables and operators can be used in formulas:
| Element | Description |
|---|---|
| **Variables** | The variables of a formula can be an item, an account, a different formula, a time series, or a total line. Variables can be named arbitrarily. |
| **Operators** | The following operators can be used in a formula: = > < <\> >= <= ( ) AND OR IF + - / \* LM LAST_MONTH |
How to use **IF**, **LM** and **LASTMONTH** is described in detail in _Special formulas_.
## Creating and Configuring a Formula
How to create and configure a formula is described in the following section. Alternatively, you can find the information in the following video:
Video: https://player.vimeo.com/video/859429411?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Creating Formulas
To create a formula:
1. Open the ledger ([general ledger](https://support.lucanet.com/en/documentation/glossary.md#general-ledger), [subledger](https://support.lucanet.com/en/documentation/glossary.md#subledger), or [statistical ledger](https://support.lucanet.com/en/documentation/glossary.md#statistical-ledger)) and navigate to the item where you want to create the formula.
2. Right-click the item and choose **Create | Formula** from the context menu.
Creating a formula
### Configuring Formulas
The following options are available in the **Create formula** dialog:
### General
The **General** tab is displayed as follows, for example:
Dialog 'Create formula' - 'General' tab
The following options are available on the **General** tab:
| Option | Description |
|---|---|
| **Type** | Element type |
| **Name** | Name of the formula |
| **Formula** | Variables, operators, and, if necessary, values of the formula. The entered variables are transferred to the following table. |
| **Formatting** | Formatting options for display: **Font color, background color, icon** and if the element is to be formatted bold. |
The table contains the configuration of the variables:
| Column | Description |
|---|---|
| **Variable** | All variables entered in the **Formula** field are automatically transferred to this column. |
| **Elements** | Elements that represent the variables. Possible elements are items, accounts, time series, total lines, and formulas. |
| **Transaction type** | Transaction type to be used for the calculation |
| **Period type** | The period type of the chosen account or chosen item is preset by default. The following options are available: - Start balance of the period: The balance at the beginning of the period is used. - End balance of the period: The balance at the end of the period is used. - Transaction figure of the period: The transaction figure of the period is used. - Transaction/balance mode set by user — If the button **Display transaction figures** the transaction figures icon is activated, the transaction figure of the period is used. If the button **Display transaction figures** the transaction figures icon is deactivated, the balance at the end of the period is used. |
| **Year-to-date** | Year-to-date value from that the calculation is to be made up to the current period. Otherwise the value will be calculated for the current period. |
### Value type
The **Value type** tab is displayed as follows, for example:
Dialog 'Create formula' - 'Value type' tab
**Value type**
Specification of the value type for the output value of the formula. The following options are available:
- **Number**:The output value is displayed as a number.
- **Percent values**: The output value is displayed as a percentage value.
- **Checksum**: The output value is displayed as a checksum.
The checksum in the event of a successful check must be **0**. In this case the output value is displayed in green. Otherwise, the value is displayed in red:
Display of checksums
**Decimal places**
Specification of the decimal places for the output value of the formula. The following options are available:
- **Dependent on variable**: The display of the decimal places is taken over by the variable.
**Note**: This value is available only for the **Number** and **Checksum** value types.
- **User-defined**: Enter the number of decimal places in the displayed input field.
### Number format
The **Number format** tab is displayed as follows, for example:
Dialog 'Create formula' - 'Number format' tab
On the **Number format** tab, the way numbers are displayed for a formula can be configured. The following options are available:
| Option | Description |
|---|---|
| **Apply number format** | Applies the number format that is different from the display settings |
| **Number display** | Formatting of the displayed values |
| **Decimal places** | Number of displayed decimal places |
> **Warning:** The **Number format** tab is only displayed for formulas in statistical ledgers.
>
> Configurations on the **Number format** tab overwrite the number format defined in the [display settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md).
>
> As soon as a deviating number format has been configured, the icon is displayed in the row of the formula.
### Attributes
The **Attributes** tab is displayed as follows, for example:
Attributes
**Attributes** are used to define multilingual or customer-specific names for Lucanet elements.
The **Attributes** tab displays all attributes that have been defined in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace and are enabled for this dimension.
You can edit the value of an attribute by opening the element's edit mode and clicking on the corresponding row in the **Value** column.
## Special Formulas
### LM and LAST MONTH
With **LM** or **LAST_MONTH**, previous period values can be considered in a cumulative form (e. g. the last six months). The general structure of a formula with **LM** or **LAST_MONTH** is as follows:
```
LM(number of months;a) or
```
```
LAST_MONTH (number of months;a)
```
> **Tip:** **Example 1**
>
> Calculation of the revenue of the last six months, with the variable a standing for the revenue item. In this case, the formula is as follows:
>
> LM(6;a)
### IF formula
An **IF formula** can be used, for example, to calculate interest if a different interest rate is to be applied to positive than to negative balances on the account. The general structure of an **IF formula** is as follows:
IF(condition;then value;else value)
> **Tip:** **Example 1**
>
> In the following formula, b is output if a = 10 applies. C is output in the event of any other value:
>
> IF (a=10;b;c)
>
> **Example 2**
>
> In the following formula, b is output if a is smaller than 10 or a is greater than d. C is output if both conditions do not apply:
>
> IF (a<10 OR a>d;b;c)
>
> **Example 3**
>
> The following video shows the development of a formula for the interest:
>
> Video: https://player.vimeo.com/video/859378540?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
---
---
title: "Creating and Configuring Items"
description: "In Lucanet, items are used for a better overview and better structuring of ledgers and schedules. Each account is assigned to an item in Lucanet. The value at the item level is always the total of all subordinate items and accounts."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-items
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Items
## Overview
In Lucanet, items are used for a better overview and better structuring of [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger) and [schedules](https://support.lucanet.com/en/documentation/glossary.md#schedule). Each account is assigned to an item in Lucanet. The value at the item level is always the total of all subordinate items and accounts.
## Creating an Item
Items can be created in ledgers and schedules from the context menu of items and the context menu of the root folder in ledgers and schedules.
To create an item in the **Reporting and analyzing** workspace:
1. Open the ledger (general ledger, subledger, or statistical ledger) and navigate to the item or root folder under which you want to create the item.
2. Right-click the item or root folder and choose **Create | Item** from the context menu.
Creating an item from an existing item
Creating an item from the root folder of a ledger
## Configuring Items
You have the following options for configuring items:
### General
The **General** tab is displayed as follows, for example:
'General' tab in the 'Create Item' dialog
The following options are available on the **General** tab:
| Option | Description |
|---|---|
| **Type** | Element type |
| **Located in** | Displays the ledgers and/or schedules that contain the item. |
| **OID** | [Object identifier](https://support.lucanet.com/en/documentation/glossary.md#oid) for the element that is automatically generated when creating the element |
| **Name** | Name of the item |
| **Formatting** | Formatting options for display: **Font color, background color, icon** and if the element is to be **formatted bold**. |
### Data type
The **Data type** tab is displayed as follows, for example:
Reiter 'Datentyp' im Dialog 'Position erstellen"
The following options are available on the **Data type** tab:
| Option | Description |
|---|---|
| **Data type** | Regardless of the ledger in that it is created, one of the following data types is available for each item in Lucanet: - **Currency amount (all ledgers)** — The value is displayed as currency amount. - **Decimal number (statistical ledgers only)** — The value is displayed as a decimal number. If necessary, change the number of decimal places in the displayed input field. - **Percentage (statistical ledgers only)** — The value is displayed as a percentage. If necessary, change the number of decimal places in the displayed input field.
**Note:** Data types can be edited only for items created directly under the root element of a ledger. All other items inherit the data type of the superordinate item. |
| **Debit/Credit** | You can use the two options to switch between debit and credit. - **Debit (+ Debit, - Credit)** — Positive values are considered as debit values, negative values as credit values. - **Credit (+ Credit, - Debit)** — Positive values are considered as credit values, negative values as debit values. |
| **Period type** | The following period types are available, depending on the ledger where it is created: - **Transaction figure (only subledgers and statistical ledgers)** — Positive values are considered as debit values, negative values as credit values. - **Balance with carry forward from previous period (all ledgers)** — Positive values are considered as credit values, negative values as debit values. - **Balance** — The value is a balance, which should not be transferred to the next period. |
### Transaction type category
The **Transaction type category** tab is displayed as follows, for example:
'Transaction type category' tab in the 'Create Item' dialog
A transaction type category can be defined for each item. The transaction type category determines the transaction types to that the item can be posted. The following categories are available:
| Option | Description |
|---|---|
| **Uncategorized** | The account does not have any category. |
| **Fixed assets** | All transaction types defined for the **Fixed assets** transaction type category are available for the item. The fixed asset schedule is created from items and accounts with this category. |
| **Provisions** | All transaction types defined for the **Provisions** transaction type category are available for the item. The provision schedule is created from items and accounts with this category. |
| **Loans** | All transaction types defined for the **Loans** transaction type category are available for the item. The loan schedule is created from items and accounts with this category. |
| **Equity** | All transaction types defined for the **Equity** transaction type category are available for the account. The statement of changes in equity is created from items and accounts with this category. |
### Debit/credit shift
The **Debit/credit shift** tab is displayed as follows, for example:
'Debit/credit shift' tab in the 'Item properties' dialog.
Debit/credit shifts are configured so that negative values for each debit/credit shift are posted as positive values on a contra account. The following options are available:
| Option | Description |
|---|---|
| **Activate debit/credit shift** | When the check box is activated, further configuration options are displayed. |
| **Account display** | Define whether the debit or credit value is to be disclosed on the debit/credit shift item. |
| **Debit/credit shift item** | Contra item in the general ledger |
| **Transaction types** | Click **Show** to define the transaction types on the debit account and the transaction types on the credit account: - **Transaction types on debit account:** Define for which transaction types the debit/credit shift to the initial item is to be performed. - **Transaction types on credit account:** Define for which transaction types the debit/credit shift to the debit/credit shift account is to be performed. |
| **Debit/credit shift per partner** | Activate the check box if you want the system to perform the debit/credit shift at partner level. |
| **Consolidation of debit/credit shifts** | Consolidation groups that you want to include in the debit/credit shift |
> **Warning:** - The **Debit/credit shift** tab is only displayed for already created items.
>
> - The **debit/credit shift** can only be activated if the item is in the general ledger and there are no references below the item.
After saving the configuration, the balance is disclosed under the contra item if a negative value is created under the original item. Because it is not possible to post to items, debit/credit shift accounts are created automatically under the initial item and the configured contra item. E.g.:
Example of an activated debit/credit shift on item level
> **Warning:** Attention when you configure a debit/credit shift for items containing accounts that are used in a planning wizard for **Current account interest:**
>
> If you set up a debit/credit shift for the superordinate item of the accounts specified for the **interest income** and **interest expense** after you have configured the wizard, the configuration of the wizard will become invalid. In this case, a warning icon will be displayed in front of the wizard in the Journal for which it has been set up. For a description on how to resolve the configuration errors, see [Troubleshooting for Invalid Wizard Configuration Due to Retroactive Debit/Credit Shift](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/current-account-interest.md#invalidconfig)).
### Number format
The **Number format** tab is displayed as follows, for example:
'Number format' tab in the 'Item properties' dialog
On the **Number format** tab, the way numbers are displayed can be configured differently from the display settings. The following options are available:
| Option | Description |
|---|---|
| **Apply number format** | Applies the number format that is different from the display settings |
| **Number display** | Formatting of the displayed values |
| **Decimal places** | Number of displayed decimal places |
> **Warning:** - The **Number format** tab is only displayed for items in statistical ledgers.
>
> - Configurations on the **Number format** tab overwrite the number format defined in the [display settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md).
>
> As soon as a different number format has been configured, the icon is displayed in the item line.
### Attributes
The **Attributes** tab is displayed as follows, for example:
Attributes
**Attributes** are used to define multilingual or customer-specific names for Lucanet elements.
The **Attributes** tab displays all attributes that have been defined in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace and are enabled for this dimension.
You can edit the value of an attribute by opening the element's edit mode and clicking on the corresponding row in the **Value** column.
---
---
title: "Creating and Configuring Loan Wizards"
description: "The Loan planning wizard allows both received loans and issued loans to be defined for reporting entities. Lucanet regards a received loan as borrowing from outside or inside your company. An issued loan is regarded as loan issuance. Received and issued loans can be defined for different loan types."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/loan-wizard
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Loan Wizards
## Overview
The **Loan** planning wizard allows both received loans and issued loans to be defined for reporting entities.
Lucanet regards a received loan as borrowing from outside or inside your company. An issued loan is regarded as loan issuance. Received and issued loans can be defined for different loan types.
The wizard can be created for all reporting entities for values of ledgers and schedules in planning data levels, either within a **journal** or from a **ledger**.
> **Note:** **Notes on internal company loans**
>
> - If you have defined an internal company loan, all configuration settings of the selected, i.e. drawn-down, loan are transferred to the new loan.
> - Internal company loans cannot be copied or transferred to journals with another data level. Alternatively, you can create a new planning data level based on the data level containing the loan in order to transfer the loan to another data level.
> - When deleting, internal company loans are not deleted on both sides, i.e. on the borrower and the lender side but only on the side where the loan element was deleted, i.e. on the borrower or the lender side.
> - An intercompany issued loan can only have one corresponding received loan configured in the database.
## Creating a Loan Wizard Within a Journal
To create a loan wizard within a journal:
1. Open the **Journals** workspace.
2. In the dimension bar, select the combination of a **planning data level** and **reporting entity** for which a loan should be created.
3. Right-click the root folder and choose **Create | Loan** from the context menu. The **Create Loan Wizard** dialog is displayed:
Creating a loan wizard
4. Specify the **name** of the element.
5. Select the **loan type**:
- **Loan issued**: if you want to define a loan issuance in which the reporting entity should function as a lender for another reporting entity, for example.
- **Loan received:** if you want to define a borrowing. Proceed as follows if an internal company loan is to be defined, i.e. the lender is not an external institution such as a bank, but is another reporting entity:
- Activate the check box **Lender within this database**.
- In the **Lender** drop-down list, select the reporting entity which is functioning as the lender.
- In the **Loan** drop-down list, select the loan that should be drawn down. The drop-down list displays all loans that have been defined as **Loans issued** to the selected reporting entity.
## Creating a Loan Wizard From a Ledger
To create a loan wizard from a ledger:
1. Select the desired ledger (general ledger, sub-ledger or statistical ledger).
2. In the dimension bar, select the combination of **planning data level** and **reporting entity** for which the wizard should be created.
3. Right-click in the row of the ledger hierarchy for which the wizard should be created and choose **Create | Loan**.
Creating a wizard from a ledger
4. The **Create Loan Wizard** dialog is displayed:
Creating a loan wizard
5. Specify the **name** of the element.
6. Select the **loan type**:
- **Loan issued**: if you want to define a loan issuance in which the reporting entity should function as a lender for another reporting entity, for example.
- **Loan received:** if you want to define a borrowing. Proceed as follows if an internal company loan is to be defined, i.e. the lender is not an external institution such as a bank, but is another reporting entity:
- Activate the check box **Lender within this database**.
- In the **Lender** drop-down list, select the reporting entity which is functioning as the lender.
- In the **Loan** drop-down list, select the loan that should be drawn down. The drop-down list displays all loans that have been defined as **Loans issued** to the selected reporting entity.
## Configuring a Loan Wizard
To configure a loan wizard, click the name of the desired element in the tree view, and then click **Edit** in the top right. The configuration is divided into general properties in the header and four configuration steps in the main section of the editing mode.
### General Properties
General properties of a loan
The following properties can be configured in the header:
| Property | Description |
|---------|---------|
| Element name | Name of the wizard |
| Cost center | Cost center in which the posting is to be performed by the planning wizard |
| Currency | Currency in which the posting is to be performed by the planning wizard |
| Adjustment level | Adjustment level in which the posting is to be performed by the planning wizard |
### Step 'Master data'
Configuration of master data in a loan
The following options can be configured in the **Master data** step:
| Option | Description |
|---|---|
| **Lender/ Borrower** | Label depends on the **loan type** selected during the creation of the loan.
**Note:** If a lender was selected from the database, the field is automatically populated with the **lender** and **loan name** and is set to read-only. Otherwise, the field remains blank and editable. |
| **Repayment type** | Drop-down menu with two options as loan types: - **Annutiy loan:** Select this type if a loan should be defined with a constant repayment amount (installment). The installment is the sum of the redemption and interest portions. In contrast to the installment loan type, the amount of the installment to be paid (annuity) remains the same over the entire duration (if a fixed interest period was agreed throughout the entire term). - **Installment loan:** Select this type if a loan should be defined with a constant repayment portion. The repayment amount decreases continuously over the entire term (if a fixed interest period was agreed throughout the entire term). |
| **Loan amount** | Specify what (nominal) amount (without fees/debt discount) should be issued or received.
If **Loan issued/Loan received** was selected in the creation step without activating the **Lender within this database** checkbox, the field is pre-populated with '10.000,00' is editable.
If **Loan received** was selected in the creation step and the **Lender within this database** was activated, the field is pre-populated with the selected loan amount and is not editable. |
| **Remaining debt** | Amount which should have to be paid as remaining debt at the end of the loan term |
| **Date of borrowing** | Expected date of borrowing
**Note:** If the borrowing period is before the planning period, i.e. in the **Actual data level**, this date can be entered and the software automatically calculates the remaining debt in the plan. In this way, it is possible to plan the continuation of already existing loans. |
| **Loan term in months** | Specify the term in months |
| **Month of last installment** | Specify the last month of the loan term |
| **Method of interest calculation** | The following calculation methods are available: - **30/360 (German method)** — In the German (commercial) method, each interest month is assumed to have 30 days, and each interest year 360 days. Interest is charged on either the first investment day or the last. - **Act/360** (French method) — In the day-count convention (or the French interest method), the interest days are calculated exactly according to the calendar, and the base year is assumed to have 360 days. In the day-count convention, interest is charged on the first investment day but not on the last; in the French interest method, interest is charged on the last investment day but not on the first. - **Act/365** (English method) — In the English interest method, the interest days are calculated exactly according to the calendar, which means the interest year has 365 or 366 days. The base year is assumed to have 365 days. Interest is charged on the last investment day but not on the first. - **Act/Act** (method based on the actual number of days) — In the effective interest method or the interest method based on the exact number of days, the interest days, interest year and base year are determined exactly according to the calendar. In this method, interest is not charged on the first investment day but on the last. |
| **Additional options** | Activate the check box for every additional option that you would like to configure for the loan. The following options are available: - **Commitment interest** — frequently charged by banks for medium or long-term bank loans - **Fees** — Lucanet does not regard fees for a loan as being the total amount of all interest and thus normal interest payments, but rather special services. - **Unscheduled repayments** — that go beyond the current installments agreed in the loan contract - **Subsequent borrowing** — increasing the loan amount during the loan term
Once activated, the corresponding step will be displayed on the user interface. |
### Step 'Current installment'
Configuration of current installment in a loan
### Current Installment
The following options must be configured in the **Current Installment** section:
| Option | Description |
|---|---|
| **From/To** | - **From**: Date of borrowing or Date of loan issuance - **To**: Month of last installment |
| **Pay installment** | - The list contains 3 folders — **Individual, Once per calendar quarter, Once per calendar year**—each providing different configuration options. - Choose **No** under **Individual** if there should be neither redemption nor interest payments during the loan term. |
| **Installment includes repayment** | - Only with **Annuity** loan type - Deactivate the check box if only interest should be paid with each installment. |
| **Annuity** | - Only with **Annuity** loan type - Specify the repayment amount per installment |
| **Add row** | Add additional rows if the payment modalities should be different for one or more time periods of the payment period. |
| **Last installment repays the loan** | Activate if the remaining debt existing at the end of the loan term should be repaid with the last installment, irrespective of its value.
**Note:** If a value greater than zero was specified in the **Remaining debt at the end of loan term** field of the **Master data** tab, the **Last installment repays the loan** option is displayed at this item. Activate the check box if the outstanding repayment amount should be repaid down to the defined remaining debt with the last installment. |
| **Value date of repayment** | - Only with **Installment** loan type - Select the day in the month on which the repayment should be posted |
| **Repayment portion** | - Only with **Installment** loan type - Enter the repayment amount - Keep the **Without repayment** default setting if the repayment should not take place using the current installment. |
### Interest
The following options must be configured in the **Interest** section:
| Option | Description |
|---|---|
| **From/To** | - **From**: Date of borrowing or Date of loan issuance - **To**: Month of last installment |
| **Interest rate (%)** | - Enter the desired interest rate. - Add additional rows if the interest rate should be different for one or more time periods of the payment period. |
| **Calculation basis for values** | The following options are available: - Calculate interest based on the exact to the day remaining debt - Calculate interest based on the remaining debt at the end of the month - Calculate interest based on the remaining debt at the start of the month |
| **Take interest on interest into account** | The following options are available: - No, accrue calculated interest until the repayment - Yes, add the calculated interest to the payment of the remaining debt
**Note:** These options are only available when **Pay installment** field is populated with any value except for **Every month**. |
#### Show interest calculation
Click to see a detailed breakdown of how the loan interest is calculated:
Interest calculation
### Step 'Commitment interest'
Configuration of commitment interest in a loan
The following options can be configured in the **Commitment interest** step:
### Duration
The following options must be configured in the **Duration** section:
| Option | Description |
|---|---|
| **From/To** | Period during which the commitment interest is charged
The dates are prefilled depending on the dates defined in the **Master data** step and can be edited manually. |
| **Until the day before borrowing/ The day before loan issuance** | Activate the check box if the calculation period should end on the day before the day that has been defined in the **Master data** step as the **Date of borrowing/Day of loan issuance**. |
### Interest rate and interest payment
The following options must be configured in the **Interest rate and interest payment** section:
| Option | Description |
|---|---|
| **From/To** | Period for which the interest rate and payment applies
You can add additional rows if the interest rate and/or the payment modalities should be different for one or more time periods of the payment period. |
| **Interest rate (%)** | Applicable interest rate |
| **Pay interest** | When the interest should be paid: - You can select a date of payment on a **monthly, quarterly** or **annual** basis. - Choose **No** if there should not be any interest payments. |
| **Calculation basis for values** | Amount the interest calculation is based on |
| **Initial loan amount** | Activate the check box to transfer the value that is defined as the **Loan amount** in the **Master data** step. |
### Step 'Fees'
Configuration of fees in a loan
The following options can be configured in the **Fees** step:
| Option | Description |
|---|---|
| **Date** | Due date for the fee |
| **Fee** | Amount of the fee |
| **In % of the loan amount** | Percentage of the loan amount |
| **Add fees to remaining debt** | Activate the check box if the fees should be added to the remaining debt. |
| **Presentation in P&L** | How the fees should be shown in the P&L. Choose one of the following options: - **Present interest for each month** if the fees should be presented evenly distributed in each month of the loan term - **Present interest only in the payment month** if the fees should only be presented in the month of the payment. |
### Step 'Unscheduled repayment'
Configuration of unscheduled repayments in a loan
The following options can be configured in the **Unscheduled repayments** step:
| Option | Description |
|---------|---------|
| Date | Due date for the unscheduled repayment |
| Amount | Amount of the unscheduled repayment |
| In % of the loan amount | Percentage of the loan amount |
### Step 'Subsequent borrowing'
Configuration of subsequent borrowings in a loan
The following options can be configured in the **Subsequent borrowing** step:
| Option | Description |
|---------|---------|
| Date | Date when the subsequent amount is borrowed or lent |
| Amount | Amount of the subsequent borrowing |
| In % of the loan amount | Percentage of the loan amount |
### Step 'Posting'
Posting details in a loan
In the Posting step, the affected accounts can be specified:
1. For each row, select the desired **account** from the drop-down list.
2. If applicable, select the desired **partner** from the drop-down list. The partner field is pre-populated with a default partner.
The following accounts must be specified, depending on the options you configured for the wizard:
| Option | Description |
|---|---|
| **Loan account** | Liabilities account for the borrowing.
This account is selected right from when the loan is created, but can be changed at any time in the configuration. |
| **Contra account for borrowing** | Bank account for the borrowing/loan issuance |
| **Contra account for ongoing redemption** | Bank account from which the redemption is deducted |
| **Current interest (bank account)** | Bank account from which the current interest is taken |
| **Current interest (P&L account)** | Expense account to which the interest expenses are posted |
| **Fees (Bank account)** | Bank account from which the fees are taken |
| **Fees (P&L account)** | Expense account to which the fees are posted |
| **Accrual account for interest and fees** | Accruals and deferrals account for the period-specific accrual and deferral of the interest and fees |
| **Commitment interest (Bank account)** | Bank account from which the commitment interest is taken |
| **Commitment interest (P&L account)** | Expense account to which the commitment interest is posted |
| **Unscheduled repayments** | Bank account from which the unscheduled repayments are deducted |
### Step 'Summary'
In the last step, a summary of the calculated payments and interest amounts for the entire loan duration is displayed.
> **Note:** If the loan dates fall outside the date range of the Planning data level (e.g., a loan starts before the start date or ends after the end date of the Planning data level), the summary table will indicate this by greying out the respective periods.
Loan summary
---
---
title: "Creating and Configuring Organization Groups"
description: "Organization groups are used in structures to combine all of the organization elements of the entire structure or of substructures that belong together."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-configure-org-groups
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Organization Groups
## Overview
Organization groups are used in structures to combine all of the organization elements of the entire structure or of substructures that belong together. For example, all of the organization elements of a group can be combined in one organization group and all of the organization elements from subgroups can be combined in separate organization groups.
## Creating an Organization Group
To create an organization group:
1. Right-click the root folder **Organization elements**, a folder, or anOrganization group **.**
2. Choose **Create | Organization group** from the context menu **.** The **Create Organization Group** dialog is displayed:
Creating an organization group
3. Specify the name of the element.
4. Choose the currency to be used as the default display currency from the **Default display currency** drop-down list. A selection can be made from all of the display currencies that have been created in the **Currency translation** workspace (see [Creating and Configuring Currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)).
> **Note:** If you create the organization group under a different organization group, then the currency settings of the higher-level organization group will be applied. The **Default display currency** drop-down list will not be displayed in this case.
## Configuring an Organization Group
Edit an organization group
To configure an organization group:
1. Click the name of the organization group in the tree view.
2. Click **Edit** at the top right to open the editing mode.
3. Optionally, change the name of the element and choose another currency from the **Default display currency** drop-down list.
4. On the **Performance** tab, choose the display currency or currencies in which values are to be stored to accelerate the display of these values in these currencies.
5. Click **Save**.
## Automatic Organization Groups
When generating references to consolidation areas in the **Organization elements** workspace, automatic organization groups are generated for the drill down **Adjustment levels separated – default hierarchy of the consolidation area** that contain all references to consolidation units with the adjustment level **Consolidation postings**. The element **Organization group (automatic)** **cannot** be deleted.
If the drill down is changed, the **Organization group (automatic)** element is changed into an **organization group**.
> **Note:** An automatic organization group can be configured like a regular organization group using the **Edit** button.
---
---
title: "Creating and Configuring Partner Groups"
description: "You can use partner groups to group partners hierarchically. In the event of a value query of a partner group, the aggregated value of all partners is displayed."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners/partnergruppen-anlegen-und-konfigurieren
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Partner Groups
## Overview
You can use partner groups to group partners hierarchically. In the event of a value query of a partner group, the aggregated value of all partners is displayed.
## Creating a Partner Group
To create a partner group:
1. Right-click the **Partners** root folder, another partner group, a folder, or an individual partner.
2. Choose **Create | Partner group** from the context menu.The **Create Partner Group** dialog is displayed:
Creating a partner group
3. Specify the **name** of the element.
4. Click **Save**.
> **Note:** After creating a partner group, you can configure it and change the name of the partner group.
---
---
title: "Creating and Configuring Partners"
description: "You can create and configure partners in Lucanet. Partners are used for the consolidation in order to add partner information to postings and data imports for the internal cost allocations."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners/manage-partners
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Partners
## Overview
You can create and configure partners in Lucanet. Partners are used for the consolidation to add partner information to postings and data imports for the internal cost allocations.
## Creating Partners
To create a partner:
1. Right-click the root folder **Partner**, a partner group,a folder, or an individual partner.
2. Select **Create | Partner** from the context menu **.** The **Create Partner** dialog is displayed:
Creating a partner
3. Specify the **name** of the element.
4. Assign all of the consolidation units, reporting entities, cost centers, cost center groups, or organization groups to the partner for which the postings or data imports can occur with this partner.
5. Click **Save**.
> **Note:** After creating a partner, you can configure this partner and subsequently assign additional consolidation units, reporting entities, cost centers, cost center groups, or organizational groups to the partner, as well as change the partner's name.
---
---
title: "Creating and Configuring Planning Data Levels"
description: "Planning data levels are used for recreating your corporate planning. With the aid of planning data levels, you can create not only the general planning but also scenarios and forecasts."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/create-configure-planning-datalvls
language: en
last_updated: 2026-09-30
---
# Creating and Configuring Planning Data Levels
## Overview
Planning data levels are used for recreating your corporate planning. With the help of planning data levels, you can create not only the general planning but also scenarios and forecasts.
There is exactly one actual data level and up to 254 planning data levels with different descriptions. The planning data levels are based on the actual data level. This means the opening balance sheet of the planning data level corresponds to the closing balance sheet of the actual data level.
## Creating Planning Data Levels
To create a planning data level:
1. Right-click the **Data levels** root folder.
2. Choose **Create | Planning data level level** from the context menu.
The following options are available in the **Create Planning Data Level** dialog:
Create a planning data level
| Option | Description |
|---|---|
| **Element name** | Name of the element |
| **Template** | Existing planning data levels as templates: - Keep the default setting if you want to adopt **planning data, planning wizards**, and **accounting rules**. - Select **Planning wizards and accounting rules** or **Accounting rules only** to restrict the scope of the data to be transferred accordingly. |
| **Period** | **Start** and **end period** of the data level |
> **Note:** - No data is transferred for elements of type **Group**.
> **Warning:** If you specify a template and then change the period, only the data of the template data level that is in the selected period will be copied.
## Configuring Planning Data Levels
When configuring a data level, the following options are available:
Editing a planning data level
| Option | Description |
|---|---|
| **Period** | **Start period** and **end period** of the data level |
| **Data level closed** | The planning data level can be closed in order to block an entire data level against postings. This prevents plannings from being inadvertently altered afterwards. |
| **Data level archived** | Planning data levels can be archived in such a way that they cannot be selected in the dimension bar. This is useful when outdated plannings are retained but should no longer be visible. |
> **Note:** You can cancel the archiving at any time by deactivating the check box.
### Planning Data Level Status
Each planning data level has one of the following statuses, which is shown on the **Status** tab.
| Element | Description |
|---|---|
| **Data level is synchronized with the actual data level** (the data level synchronized icon) | This data level is synchronised with the actual data level. Furthermore, all periods before the start of this data level are closed in the actual data level. This ensures that the actual data level can no longer be changed before the start of this data level, meaning that the planning data level would no longer be synchronized with the actual data level. |
| **Open periods in the actual data level before the start of the planning data level** (the warning yellow icon) | Periods prior to the start of the planning data level are open in the actual data level. It is possible that the actual data level can be changed before the start of the planning data level, meaning that the planning data level would no longer be synchronized with the actual data level.
**Note:** Open the **Period locks** workspace to close the open periods of the actual data level. Please note that you can only view, create, and/or edit period locks if you have the appropriate permissions (see [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md)). |
| **The planning data level is not synchronised with the actual data level** (the warning yellow icon) | Since the creation or since the last synchronization, changes have taken place in the actual data level before the start of the planning data level. To transfer the changes to the planning data level, the planning data level must be synchronized.
**Note:** The data level can be synchronized at any time with the actual data level (see [Synchronizing Planning Data Levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/synchronize-planning-data-level.md)). |
---
---
title: "Creating and Configuring Postings in Journals"
description: "Manual postings can be created for all reporting entities or consolidation areas in the Journals workspace, for periods that are not locked for editing."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/create-configure-posting-reporting-entity
language: en
last_updated: 2026-09-29
---
# Creating and Configuring Postings in Journals
## Overview
In Consolidation & Financial Planning, manual postings can be created for all reporting entities or consolidation areas in the **Journals** workspace, for periods that are not locked for editing.
In addition, manually cretaed postings can be reversed by means of cancellation.
> **Tip:** To analyze, review, or share posting data, you can generate a report of all postings. For instructions on how to do this, see [Creating a Posting Report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/create-postings-report.md).
## Creating a Posting
To create a posting for a reporting entity or consolidation area:
1. In the dimension bar, select the combination of **data level** and **reporting entity** or **consolidation area** for which a posting should be created.
2. Right-click any folder and choose **Create | Posting**.
The **Create Posting** section is displayed:
Creating of a posting for a reporting entity
3. Specify the **name** of the element.
4. If applicable, change the **currency** in which the posting is to be made.
5. If applicable, change the **period** for the posting.
6. If applicable, change the **adjustment level.**
7. Click **Continue** and follow the steps below to configure the posting.
## Configuring a Posting
To configure a posting, click the name of the desired posting in the tree view, and then click **Edit** in the top right.
Configuration of general properties of a posting
### General Properties
The following properties can be edited in the header:
| Property | Description |
|---------|---------|
| Name | Name of the posting |
| Currency | Currency in which the postings are to be made |
| Adjustment level | Adjustment level in which the postings are carried out |
### Values Tab
The following options are available on the **Values** tab:
Configuration of the 'Values' tab in a posting
### Toolbar
The following options are available in the toolbar of the **Values** tab:
| Option | Description |
|---|---|
| Show and hide account hierarchies | Allows showing or hiding additional account hierarchies for account selection. The ledgers specified here are displayed in the table below. By default, the general ledger is available for account selection which is assigned to the reporting entity or consolidation area for which the posting is created. When creating a new posting, the general ledger account hierarchy (including all subledgers) is automatically selected if the user has the necessary permissions. |
| Edit value columns | Allows editing the value columns of the posting mask. A dialog is opened, in which you can add or remove value columns, and store a comment such as the specific posting date for each value column. |
| Show cumulated | Displays cumulated values in the posting columns, i.e. the total for all posting entries. If this button is not activated, all values of the posting entries of a posting are listed separately. |
| Resolve difference | Resolves differences (values) within the posting. |
| D/C recording | Switches the view from plus and minus recording to the entry of accounting values in debit and credit. |
| Historical exchange rate translation | Activates the historical exchange rate translation for this posting. Check [Historical Exchange Rate Translation](#historical-exchange-rate) to see how to configure the section. |
| Cost center/Partner/Transaction type | Toggles visibility of the respective columns in the table. **Note:** Hiding these columns does not affect the data stored in them — the system retains the information and uses it when generating the posting. |
### Posting Data
#### Account
Selection of an account or item for creating a posting
You can display only those accounts that contain postings for selection by clicking the drop-down list in the **Account** column and selecting the **Show only accounts with postings** option:
Show only accounts with postings
> **Note:** **Notes on the **D/C recording** button**
>
> - When the **D/C recording** button is **deactivated**, the general ledger account hierarchy (including all subledgers) is split into two blocks representing the **debit and credit sides** of the same posting:
>
> In the **Debit** posting block, only debit accounts that can be debited are shown.
>
> In the **Credit** posting block, only credit accounts that can be credited are shown.
>
> - When the **D/C recording** button is **activated**, all entries are shown in a single table. You can select **D** (debit) or **C** (credit) for each line, and the account list includes all valid accounts.
#### Cost center/ Partner/ Transaction type
Allows selection of a cost center/partner/transaction type from the respective drop-down lists
#### Value columns
Allows entering values that should be posted
Value columns are identified by the periods to which the postings should be made.
#### Posting text
Description for the posting
### Historical Exchange Rate Translation
To activate historical exchange rate translation for a posting:
1. Select the cell with the posting value that you wish to define a historical exchange rate translation for.
2. Click the **Historical exchange rate translation** button above the table. A **Historical exchange rate translation** section is displayed under the table.
3. Activate the option **Activate historical exchange rate translation** **for the selected posting value**.
4. In the table, specify the desired exchange rate for each of the displayed currencies.
**Note:** For undefined exchange rates, the exchange rate **1.0** is fixed by default.
> **Note:** **Notes on historical exchange rate translations:**
>
> - The **Historical exchange rate translation** button is only displayed if at least one currency translation has been configured in a reporting entity or consolidation area. To configure currencies and currency translations in reporting entities or consolidation areas, see [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities.md) and [Creating And Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md).
> - Historical exchange rate translations can only be defined for accounts of type **Currency amount**.
> - When copying the posting document to another journal, the fixed exchange rates are retained, provided the same currency translations have been configured in the target journal.
> - When historical exchange rate translation is defined for a cell's posting value, a purple chat symbol appears to the left of the posting value in that cell.
## Cancelling postings
You can use the **Cancel posting** function to reverse a manually created posting. The cancellation can be cumulative after the last month or after each month.
Canceling a posting does not create a new, separate posting, but rather “reverses” the posting values defined in the posting within the defined period.
To cancel a posting:
1. In the **journal**, select the desired posting and click **Edit** to open the edit mode.
2. Activate the **Cancel posting** option and select one of the following options:
- **Cumulative after the last month**, if the cancellation is to be carried out cumulatively after the last month of the defined period that contains values
- **After every month**, if the cancellation of the posting values is to be carried out individually in each subsequent month
Cancel posting
3. Click **Save**.
The posted values are cancelled by the system.
## Finalizing Postings
Postings in the **actual data level** can be finalized, as a result of which they can neither be deleted nor changed. Finalized postings can only be undone using cancellation postings.
To finalize a posting, right-click the name of the desired posting in the Journal and choose **Finalize posting** from the context menu. Confirm the displayed message:
Security prompt when completing a posting
As soon as the posting has been finalized, a lock icon is displayed next to it in the tree view:
Finalized posting in the journal
---
---
title: "Creating and Configuring References"
description: "References are links to elements that were previously defined in the Reporting entities or the Groups workspace."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-references
language: en
last_updated: 2026-05-01
---
# Creating and Configuring References
## Overview
[References](https://support.lucanet.com/en/documentation/glossary.md#reference) are links to elements that were previously defined in the [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) or the [Groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) workspace. Each object can be referenced a multiple number of times, which means that it is possible to set up several structures in the **Organization elements** workspace.
## Possible References
The following references can be created:
| Element | Description |
|---|---|
| **Reporting entity** | Used for creating references to reporting entities and consolidation reporting entities from the **Reporting entities** workspace |
| **Cost center** | Used for creating references to cost centers from the **Reporting entities** workspace |
| **Cost center group** | Used for creating references to cost center groups from the **Reporting entities** workspace: - **Drill down by cost centers - default hierarchy of the reporting entity** — Used for applying the hierarchy of the cost centers and cost center groups of the reporting entity - **Drill down by cost centers - specify hierarchy individually** — The hierarchy of the cost centers and cost center groups is created individually or converted to individual hierarchy. In doing so, all the cost center groups of the default hierarchy (= hierarchy in the reporting entity) are created as organization groups and all the cost center references are sorted in accordance with the default hierarchy. |
| **Consolidation area** | Used for creating references to consolidation areas from the **Groups** workspace |
| **Consolidation unit** | Used for creating references to consolidation units from the **Groups** workspace |
| **Consolidation unit - Cancellation** | This reference is automatically created when selecting the nested display in the Organization elements workspace. It serves as a reference to a canceled consolidation unit from the **Groups** workspace. |
| **Consolidation unit group** | Used for creating references to consolidation unit groups from the **Groups** workspace |
| **Total line** | References to total lines are created automatically if a reference to the consolidation area, consolidation unit group, reporting entity, or cost center group containing the total line is created in the **Organization elements** workspace. |
## Creating References
To create one or more references:
1. Right-click the root folder **Organization elements**, a folder, or an organization group.
2. Choose **Create | Reference** from the context menu. The **Create Reference** dialog is displayed: _ the create reference icon Creating a reference_
3. Choose all the elements in the displayed drop-down list that are to be inserted as references, or search for specific items under **Referring to** in the search bar.
4. Click **Save**.
## Configuring References
To configure a reference, click the name of the reference and then click **Edit** in the top right corner.
Edit a reference to reporting entity
### General Properties
In the editing mode in the header, you can change the **name** of the reference by activating the check box **Specify name, icon, formatting, and attributes** **individually**.
> **Note:** Currently, only the name of the element can be edited.
For direct **references to consolidation units** and **consolidation unit groups**, you can, if necessary, change the adjustment level(s) to be displayed for the reference. Choose one of the following options from the **Adjustment levels** drop-down list:
- **Consolidated financial statements and consolidation postings**: All postings from the adjustment level containing the postings for the consolidated financial statements and from the adjustment level for consolidation postings containing the consolidation postings are displayed.
- **Consolidated financial statements**: All postings from the adjustment level containing the postings for the consolidated financial statements are displayed.
- **Consolidation postings**: All postings from the adjustment level for consolidation postings containing the consolidation postings are displayed.
### Further Configuration Options
Depending on the selected reference, additional tabs may be displayed under the general information. Configure the tabs as follows:
#### Consolidation rate
If applicable, change the consolidation rate on the **Consolidation rate** tab.
> **Note:** - The consolidation rate is only available for **references to reporting entities** and **cost center groups**.
> - This setting is only relevant if you perform consolidation using Consolidation 1. You can specify a value between 1 and 100 that determines with which percentage share the reporting entity is included in the consolidation.
#### Drill down options for references to cost center groups and reporting entities
The drill down determines whether and how the cost centers and cost center groups of a reporting entity are inserted into the organization elements.
| Option | Description |
|--------|-------------|
| — | This setting applies for reporting entities and/or cost center groups without cost centers (cost center groups) or can be selected so that the cost centers and cost center groups of the reporting entity and/or cost center group are not adopted in the structure. |
| Drill down by cost centers – default hierarchy of the reporting entity | The hierarchy of the cost centers and cost center groups of the reporting entity is applied. |
| Drill down by cost centers – specify hierarchy individually | The hierarchy of the cost centers and cost center groups is created individually or converted to individual hierarchy. In doing so, all of the cost center groups of the default hierarchy (= hierarchy in the reporting entity) are created as organization groups and all of the cost center references are sorted in accordance with the default hierarchy.
**Note:** The setting has no effect on reporting entities and/or cost center groups without cost centers and cost center groups. If cost centers and/or cost center groups are created afterwards under the reporting entity or the cost center group, then these will be included in the organization elements in accordance with the setting. |
#### Drill down options for references to consolidation areas
The drill down determines whether and how the adjustment levels of a consolidation area are inserted in the organization elements.
##### Adjustment levels separated – default hierarchy of the consolidation area
The **Financial statements** and **Consolidation postings** adjustment levels for consolidation units and consolidation unit groups of a given consolidation area are displayed as two separate blocks, for example:
Drill down option ‘Adjustment levels separated – default hierarchy of the consolidation area’
The references of the first block contain the consolidation units with the **Financial statements** adjustment level. The references of the second block can be found in the automatically created organization group **Consolidation** _name of consolidation area_ and contain the consolidation units with the **Consolidation postings** adjustment level.
> **Note:** - The total lines **Total** _Name of consolidation area_ each display the total of all postings of the adjustment levels **Financial statements** and **Consolidation postings**.
> - The total line **Total before consolidation** _Name of consolidation area_ shows the total of all postings before the consolidation.
> - The **Group result** _Name of consolidation area_ total line shows the total of all postings after the consolidation.
> - The total lines are displayed in ledgers if you click the abbreviated overview icon **abbreviated consolidation view** or the abbreviated overview icon **complete consolidation overview** on the toolbar of the respective ledger.
##### Adjustment levels separated – specify hierarchy individually
The consolidation area is displayed in the same way as the **Adjustment levels separated – default hierarchy of the consolidation area** drill down. In this drill down, you may create new **organizational groups** and **total lines** under the **consolidation group** as needed. The hierarchy of the consolidation units and consolidation unit groups is created individually or converted to an individual hierarchy. The drill down is displayed as follows, for example:
Drill down option ‘Adjustment levels separated – specify hierarchy individually’
##### Adjustment levels together – default hierarchy of the consolidation area
The **Financial statements** and **Consolidation postings** adjustment levels for consolidation units and consolidation unit groups of a given consolidation area are displayed together, for example:
Drill down option ‘Adjustment levels together – default hierarchy of the consolidation area’
The references to the consolidation units contain all postings for the **Financial statements** and **Consolidation postings** adjustment levels.
##### Adjustment levels together – specify hierarchy individually
The consolidation area is displayed in the same way as the **Adjustment levels together – default hierarchy of the consolidation area** drill down. In this drill down, you may need to create new organization groups and total lines under the consolidation area. The hierarchy of consolidation units and consolidation unit groups is generated individually or converted to an individual hierarchy. The drill down is displayed as follows, for example:
Drill down option ‘Adjustment levels together – specify hierarchy individually’
#### Drill down options for references to consolidation unit groups
The drill down determines whether and how the consolidation units of a consolidation unit group are inserted into the organization elements.
| Option | Description |
|--------|-------------|
| — | This setting applies to consolidation unit groups without consolidation units or can be selected to prevent the consolidation units from being added to the structure. |
| Default hierarchy of the reporting entity | The hierarchy of the consolidation units of the consolidation area is applied. |
| Specify hierarchy individually | The hierarchy of the consolidation units is created individually or converted to an individual hierarchy. |
---
---
title: "Creating and Configuring References"
description: "References are links that refer to items or accounts in general ledgers, subledgers, and statistical ledgers. References can be used to create derived structures in Lucanet (e.g. a derived IFRS balance sheet). A distinction is made between direct and indirect references."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-references
language: en
last_updated: 2026-05-01
---
# Creating and Configuring References
Last modified on 20.06.2024
## Overview
References are links that refer to [items](https://support.lucanet.com/en/documentation/glossary.md#item) or [accounts](https://support.lucanet.com/en/documentation/glossary.md#account) in [general ledgers](https://support.lucanet.com/en/documentation/glossary.md#general-ledger), [subledgers](https://support.lucanet.com/en/documentation/glossary.md#subledger), and [statistical ledgers](https://support.lucanet.com/en/documentation/glossary.md#statistical-ledger). References can be used to create derived structures in Lucanet (e.g. a derived IFRS balance sheet). A distinction is made between **direct** and **indirect** references.
- A **direct reference** always contains all subordinate items and accounts of the default item. If a change is made within the structure of the default item, this change will also be applied to the reference.
- In contrast, an **indirect reference** allows exceptions to be defined for the display of the subordinate items and accounts.
## Creating a Reference
To create a reference:
1. Mark the item or account for which a reference is to be created.
2. Right-click the name of the item or account and choose **Copy** from the context menu.
3. Open the ledger or schedule into which the reference is to be pasted.
4. Right-click the name of the item under which the reference should be added, and choose **Paste as reference** from the context menu.
Context menu command 'Paste as reference'
The item or account, including all subitems and subaccounts of the original structure, is pasted under the desired item. Each item and each account that is a reference is marked with an arrow pointing to the right:
References in the fixed asset schedule
> **Warning:** - Items or accounts can be pasted as references in a **schedule** only if the items or accounts in the ledger are assigned to the correct transaction type category.
> - No references can be pasted under items with an **activated debit/credit shift**!
## Configuring a Reference
To configure a reference:
1. Navigate to the desired reference.
2. Right-click the reference and choose **Properties** from the context menu.
The following options are available:
### General
The **General** tab is displayed as follows, for example:
'General' tab in the 'Reference properties' dialog
The following properties and options are available on the **General** tab:
| Option | Description |
|---|---|
| **Type** | Element type |
| **OID** | **Object identifier** for the element that is automatically generated when creating the element |
| **Reference source** | Shows the referenced item or account |
| **Reference name** | Name of the reference |
| **Reference type** | - **Direct reference to the selected item or account** — This is the default type. Direct references contain all subordinate items and accounts of the referenced item. If a change is made within the structure of the referenced item, this change will also be applied to the reference. - **Indirect reference to all child items and accounts** — Indirect references do not have to contain all subordinate items and accounts of the referenced item, because individual items and accounts can be removed from the display (see **Child elements** tab). |
| **Display child elements** | The check box can be deactivated if no child elements are to be displayed. |
| **Multiply value by -1** | All values of the original item or original account are multiplied by -1 to display the reference. |
| **Formatting** | Formatting options for display: **Font color, background color, icon** and if the element is to be **formatted bold**. |
### Transaction type
The **Transaction type** tab is displayed as follows, for example:
'Transaction type' tab in the 'Reference properties' dialog
If necessary, change the permitted transaction types for indirect references. The following options are available:
| Option | Description |
|---|---|
| **All** | All transaction types of the item or account for the reference are permitted. |
| **Individual** | Not all transaction types of the item or account for the reference are permitted. |
> **Warning:** The **Transaction type** tab is displayed only if the transaction type can be changed.
### Child elements
The **Child elements** tab is displayed as follows, for example:
'Child elements' tab in the 'Reference properties' dialog
Which direct child elements of the reference element are not to be displayed in the reference can be defined on the **Child elements** tab. Furthermore, the names of the child elements can be edited. The following columns are displayed in the table:
| Column | Description |
|---|---|
| **Original name** | Name of the original element |
| **New name** | The name of the original element can be overwritten in the **New name** column. |
| **Exceptions** | If the **Do not reference** check box is activated, the element will not be displayed in the reference. |
> **Warning:** The child elements can be edited only if the option **Indirect reference to all child items and accounts** is chosen under **Reference type** on the **General** tab.
### Number format
> **Warning:** The **Number format** tab is only displayed for references in statistical ledgers.
The **Number format** tab is displayed as follows, for example:
Number format' tab in the 'Reference properties' dialog
On the **Number format** tab, the way numbers are displayed can be configured differently from the display settings. The following options are available:
| Option | Description |
|---|---|
| **Apply number format** | Applies the number format that is different from the display settings |
| **Number display** | Formatting of the displayed values |
| **Decimal places** | Number of displayed decimal places |
> **Warning:** Configurations on the **Number format** tab overwrite the number format defined in the [display settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md).
>
> As soon as a deviating number format has been configured, the icon is displayed in the row of the reference.
---
---
title: "Creating and Configuring Reporting Entities"
description: "Reporting entities are elements to which postings can be made. Reporting entities are used as organization units when setting up group structures."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Reporting Entities
## Overview
[Reporting entities](https://support.lucanet.com/en/documentation/glossary.md#reporting-entity) are elements to which postings can be made. Reporting entities are used as organization units when setting up group structures.
## Creating Reporting Entities
To create a reporting entity:
1. Right-click a folder and choose **Create | Reporting entity** from the context menu **.** The **Create Reporting Entity** dialog is displayed:
Creating a reporting entity
2. Specify the **name** of the element.
3. Select the **start of the fiscal year** and the **default currency** in which the transactions of the reporting entity are to be executed.
4. Click **Save**.
## Configuring Reporting Entities
Edit a reporting entity
To configure a reporting entity:
1. Click a reporting entity in the tree view.
2. Click **Edit** at the top right to open the editing mode.
When configuring a reporting entity, the following options are available:
| Option | Description |
|---|---|
| **General area** | - **Start of the fiscal year:** Allows selection of the first month of the fiscal year - **Default currency:** Allows selection of the currency in which transactions of the reporting entity will be executed - **Partner:** Partners can be assigned to reporting entities in the detail view of the respective partner (see [Creating and Configuring Partners](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners/manage-partners.md)). |
| **'Cost centers' tab** | - **Create default cost center:** Creates a default cost center if none exists - **Balance sheet planning per cost center:** Accumulates planning values at the individual cost center level instead of using the default cost center |
| **'Currency translation' tab** | Allows selection of exchange rates created in the **Currency Translation** workspace (see [Creating and Configuring Exchange Rate Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md))
**Note:** The message **The changes shown in red will take effect only after exporting and importing the database** is displayed when adding or deleting exchange rate tables. This indicates that the changes will not take effect until the current database is re-exported and re-imported. If needed, contact your Lucanet administrator. |
| **'Carry forward account' tab** | - Allows selection of an **account** and **transaction type** for the cancellation of the carry forward when importing cumulative balances - **Activate historical exchange rate translation:** Allows automatic translation of historical exchange rates for the next balance import
**Note:** This option is only available if at least one active exchange rate table is assigned to the reporting entity. |
---
---
title: "Creating and Configuring Schedules"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-schedules
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Schedules
## Overview
**Schedules** can be reflected in Lucanet. In the **Overview**, each schedule is displayed in the folder as the workspace in which it was created.
## Creating a Schedule
To create a schedule:
1. Right-click the desired folder in the **Workspace configuration** and select **Create | Schedule** from the context menu. The **Create Schedule** dialog is displayed:
Creating a schedule
2. Specify the **name** of the schedule.
3. Enter an **abbreviation** for the schedule.
4. From the **Icon** drop-down list, choose the icon to be displayed in front of the schedule name in the user interface.
5. In the **Transaction type category** area, select the schedule type. You can select from all the transaction type categories in the [Transaction types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types.md) workspace. The following preconfigured transaction type categories are available:
- **Accounts without category**: Used for accounts that are not assigned to a specific category.
- **Fixed asset schedule**: Used to define a fixed asset schedule. The fixed asset schedule indicates the reasons for the changes of fixed assets within a period.
- **Provision schedule**: Used to define a provision schedule. The provision schedule indicates the reasons for the changes to provisions within a period.
- **Statement of changes in equity**: Used to define a statement of changes in equity. The statement of changes in equity indicates the reasons for the changes of equity within a period.
- **Loan schedule**: Used to define a loan schedule. The loan schedule indicates the reasons for the changes of liabilities from loans within a period.
6. Click **Save**.
## Configuring a schedule
To configure a schedule, click the name of the scheudle in the tree view and then at the top right click **Edit** to open the editing mode:
Bearbeiten eines Spiegels
## Options
The following options are available for schedules:
### General properties
The following general properties can be configured for subledgers:
| Option | Description |
|---------|---------|
| Element name | Name of the schedule. If necessary, specify the country-specific language descriptions for the display languages available for the Lucanet user interface. |
| Abbreviation | Abbreviation of the schedule |
| Transaction type category | Shows the transaction type category assigned to the schedule |
| Formatting Options | If necessary, choose another icon from the drop-down list. |
### 'Elements' tab
On the **Elements** tab, the element which elements can be created in the schedule are displayed:
- [Item](https://support.lucanet.com/en/documentation/glossary.md#item)
- [Reference](https://support.lucanet.com/en/documentation/glossary.md#reference)
- [Total line](https://support.lucanet.com/en/documentation/glossary.md#total-line)
- [Formula](https://support.lucanet.com/en/documentation/glossary.md#formula)
- [Time series](https://support.lucanet.com/en/documentation/glossary.md#time-series)
- [Separator](https://support.lucanet.com/en/documentation/glossary.md#separator)
If references are permitted as elements: If necessary, activate the **Restrict the origin of references** check box if you only want to enable references to certain workspaces. Then, click **\+ Add** and select the workspaces for which references can be created.
---
---
title: "Creating and Configuring Statistical Ledgers"
description: "Statistical ledgers can be used to create account hierarchies that need not be subject to the rules of double-entry accounting (e.g. derived general ledger and subledger structures, indirect cash flow statement and direct liquidity planning). In the Overview, each statistical ledger is displayed in the folder as a workspace in which it was created."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-statistical-ledger
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Statistical Ledgers
## Overview
Statistical ledgers can be used to create account hierarchies that need not be subject to the rules of double-entry accounting (e.g. derived general ledger and subledger structures, indirect cash flow statement and direct liquidity planning). In the **Overview**, each statistical ledger is displayed in the folder as a workspace in which it was created.
## Creating Statistical Ledgers
To create a statistical ledger:
1. Right-click the desired folder in the Workspace configuration and select **Create | Statistical ledger** from the context menu. The dialog **Create Statistical Ledger** is displayed:
Creating a statistical ledger
2. Specify the **name** of the statistical ledger.
3. Enter an **abbreviation** for the statistical ledger.
4. From the **Icon** drop-down list, choose the icon to be displayed in front of the statistical ledger name in the user interface.
5. Click **Save**.
> **Note:** For postings to accounts with the data type **Currency account** in a statistical ledger, the rules of double-entry accounting do not need to be observed.
## Configuring Statistical Ledgers
To configure a statistical ledger:
1. Click the name of the statistical ledger in the tree view.
2. Click on **Edit** at the top right to open the editing mode.
## Options
The following options are available for statistical ledgers:
### General properties
You can configure the following general properties for statistical ledgers:
| Option | Description |
|---------|---------|
| Element name | Name of the statistical ledger. If necessary, specify the country-specific language descriptions of the statistical ledger for the display languages available for the Lucanet user interface. |
| Abbreviation | Abbreviation of the statistical ledger |
| This workspace can be selected as a target during data import | Activate the check box if the workspace should be available as a target when importing data into reporting entities during data import. |
| Formatting options | If necessary, choose another icon from the drop-down list. |
### 'Elements' tab
On the **Elements** tab you can define which elements can be created in the ledger:
- To delete elements from the **Elements** list, click the delete icon next to the element you want to delete.
- To add elements to the **Elements** list, click **\+ Add row** and choose the desired element in the displayed drop-down list. The following elements are available:
- [Item](https://support.lucanet.com/en/documentation/glossary.md#item)
- [Account](https://support.lucanet.com/en/documentation/glossary.md#account)
- [Reference](https://support.lucanet.com/en/documentation/glossary.md#reference)
- [Total line](https://support.lucanet.com/en/documentation/glossary.md#total-line)
- [Formula](https://support.lucanet.com/en/documentation/glossary.md#formula)
- [Time series](https://support.lucanet.com/en/documentation/glossary.md#time-series)
- [Separator](https://support.lucanet.com/en/documentation/glossary.md#separator)
- Folder
- If references are permitted as elements: Activate the **Restrict the origin of references** check box if you only want to enable references to certain workspaces. Then, click **\+ Add** and select the workspaces for which references can be created.
> **Note:** If an object type is removed from the ledger's configuration, no further elements of this type can be created in the ledger. Elements previously created in the ledger with the removed object type are retained and can be edited, copied, moved, or deleted.
---
---
title: "Creating and Configuring Subledgers"
description: "Subledgers serve to supplement and explain the general ledger. A subledger is used, for example, to store the structure of the P&L based on your main structure.\nIn subledgers, original accounts from the financial accounting source systems are created, assigned and managed, and manually created accounts and items are administrated."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-subledger
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Subledgers
## Overview
Subledgers serve to supplement and explain the general ledger. A subledger is used, for example, to store the structure of the **P&L** based on your main structure.
In subledgers, original accounts from the financial accounting source systems are created, assigned and managed, and manually created accounts and items are administrated.
In the **Overview**, each subledger is displayed in the folder as a workspace in which it was created.
## Creating Subledgers
To create a subledger:
1. Right-click the desired folder in the **Workspace configuration** and select **Create | Subledger** from the context menu. The **Create subledger** dialog is displayed:
Creating a subledger
2. Specify the **name** of the subledger.
3. Enter an **abbreviation** for the subledger.
4. From the **Icon** drop-down list, choose the icon to be displayed in front of the subledger name in the user interface.
5. Click **Save**.
## Configuring a Subledger
To configure a subledger, click the name of the subledger in the tree view and then at the top right click **Edit** to open the editing mode:
Editing a subledger
## Options
The following options are available for subledgers:
### General properties
The following general properties can be configured for subledgers:
| Option | Description |
|---------|---------|
| Element name | Name of the subledger. If necessary, specify the country-specific language descriptions for the display languages available for the Lucanet user interface. |
| Abbreviation | Abbreviation of the subledger |
| General ledger | Shows the related general ledger. This field cannot be edited. |
| Formatting Options | If necessary, choose another icon from the drop-down list. |
### 'Elements' tab
On the **Elements** tab, you can define which elements can be created in the ledger:
- To delete elements from the **Elements** list, click the delete icon next to the element you want to delete.
- To add elements to the **Elements** list, click **\+ Add row** and choose the desired element in the displayed drop-down list. The following elements are available:
- [Item](https://support.lucanet.com/en/documentation/glossary.md#item)
- [Account](https://support.lucanet.com/en/documentation/glossary.md#account)
- [Reference](https://support.lucanet.com/en/documentation/glossary.md#reference)
- [Total line](https://support.lucanet.com/en/documentation/glossary.md#total-line)
- [Formula](https://support.lucanet.com/en/documentation/glossary.md#formula)
- [Time series](https://support.lucanet.com/en/documentation/glossary.md#time-series)
- [Separator](https://support.lucanet.com/en/documentation/glossary.md#separator)
- Folders
- If references are permitted as elements: If necessary, activate the **Restrict the origin of references** check box if you only want to enable references to certain workspaces. Then, click **\+ Add** and select the workspaces for which references can be created.
> **Note:** If an object type is removed from the ledger's configuration, no further elements of this type can be created in the ledger. Elements previously created in the ledger with the removed object type are retained and can be edited, copied, moved, or deleted.
### 'Transfer' tab
On the **Transfer** tab you can define which transfer account and which transaction type are to be used as default values for the transfer when creating accounts in the subledger:
'Transfer' tab
The following options are available on the **'Transfer'** tab:
| Option | Description |
|---|---|
| **Transfer account** | General ledger account for the transfer from the subledger. |
| **Transaction type** | Transaction type for the transfer
You can only select transaction types that belong to the transaction type category of the transfer account. The specified transaction type can be changed for each account at a later time. |
| **Subledger accounts with the same transaction type category as the transfer account use the transaction type of the posting instead of the default transaction type** | Activate the check box if the transaction type of the postings of the subledger account is to be defined as transaction type for the transfer.
This specification applies only to subledger accounts with the same transaction type category as the transfer account. |
| **Include 'Partner' dimension in the transfer** | Activate the check box if the partner information of the subledger accounts is to be transferred to the transfer account in the general ledger |
---
---
title: "Creating and Configuring Total Lines"
description: "Total lines are used for calculating totals or subtotals in structures."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-configure-total-lines
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Total Lines
## Overview
Total lines are used for calculating totals or subtotals in structures.
## Creating a Total Line
To create a total line:
1. Right-click an **Organization group** or a **Reference** that is configured with one of the following drill down options (see [Drill Down Options](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-references.md#drill-down)):
- **Drill down by cost centers - specify hierarchy individually**
- **Adjustment levels separated - specify hierarchy individually**
- **Adjustment levels together - specify hierarchy individually**
2. Choose **Create | Total line** from the context menu **.** The **Create Total Line** dialog is displayed:
Creating a total line
3. Specify the name of the element in the **Name** area.
4. Click **Save**.
## Configuring Total Lines
Edit a total line
To configure a total line:
1. Click the name of the total line in the tree view and then **Edit** at the top right.
2. If needed, change the **name** of the total line.
3. Activate the check box **Calculate total ending with previous total line** if you wish to calculate a subtotal for all structure units below the previous total line.
4. Click **Save**.
## Automatic Total Lines
When creating references to consolidation areas in the **Organization elements** workspace, automatic total lines that **cannot** be deleted are created under every adjustment level.
Automatically generated total lines are only generated if a reference to one of the following drill downs is selected in the superordinate **Reference to consolidation area**:
- **Adjustment levels separated - default hierarchy of the consolidation area**
- **Adjustment levels together - default hierarchy of the consolidation area**
If the drill down is changed into one of the following drill downs, the **Total line (automatic)** element is changed into a total line:
- **Adjustment levels separated - specify hierarchy individually**
- **Adjustment levels together - specify hierarchy individually**
> **Note:** An automatic total line can be configured like a regular total line using the **Edit** button.
---
---
title: "Creating and Configuring Total Lines"
description: "Total lines are used for calculating totals or subtotals in structures. Total lines can be created in the context of reporting entities and cost center groups."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/create-configure-total-lines
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Total Lines
## Overview
Total lines are used for calculating totals or subtotals in structures. Total lines can be created in the context of reporting entities and cost center groups.
## Creating Total Lines
To create a total line:
1. Right-click a **reporting entity** or a **cost center group** and choose **Create | Total line** from the context menu. The **Create Total Line** dialog is displayed:
Creating a total line
2. Specify the name of the element.
3. Activate the check box **Calculate subtotal until previous total line** if you wish to calculate a subtotal for all structure units below the previous total line.
4. Click **Save**.
> **Note:** After creating a total line, you can configure this total line and activate or deactivate the option **Calculate subtotal until previous total line** as well as change the name of the total line.
---
---
title: "Creating and Configuring Total Lines"
description: "Total lines are items whose values are based on the total of all items of the same level above the totals item."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-total-lines
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Total Lines
## Overview
Total lines are [items](https://support.lucanet.com/en/documentation/glossary.md#item) whose values are based on the total of all items of the same level above the totals item.
## Creating a Total Line
Total lines can be created in [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger) and [schedules](https://support.lucanet.com/en/documentation/glossary.md#schedule) from the context menu of items and the context menu of the root folder:
To create a total line:
1. Open the ledger ([general ledger](https://support.lucanet.com/en/documentation/glossary.md#general-ledger), [subledger](https://support.lucanet.com/en/documentation/glossary.md#subledger), or [statistical ledger](https://support.lucanet.com/en/documentation/glossary.md#statistical-ledger)) and navigate to the item or root folder under which you want to create the total line.
2. Right-click the item or root folder and choose **Create | Total line** from the context menu.
Creating a total line at an item
Creating a total line in the root folder
## Configuring Total Lines
The following options are available in the **Create Total Line** dialog:
### General
The **General** tab is displayed as follows, for example:
'Create Total Line' dialog
The following options are available on the **General** tab:
| Option | Description |
|---|---|
| **Type** | Element type |
| **Name** | Name of the total line |
| **Calculate subtotal until previous total line** | Calculates only the total up to the previous total line |
| **Formatting** | Formatting options for display: **Font color, background color**, and if the element is to be **formatted bold**. |
### Attributes
The **Attributes** tab is displayed as follows, for example:
Attributes
**Attributes** are used to define multilingual or customer-specific names for Lucanet elements.
The **Attributes** tab displays all attributes that have been defined in the [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) workspace and are enabled for this dimension.
You can edit the value of an attribute by opening the element's edit mode and clicking on the corresponding row in the **Value** column.
---
---
title: "Creating and Configuring Transaction Type Categories"
description: "In Lucanet, the required transaction type categories can be created with the necessary transaction types and assigned to the relevant accounts/ items, depending on the schedule desired. Only the transaction types of the selected transaction type category are available for posting to these accounts."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types/transaction-type-categories
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Transaction Type Categories
## Overview
In Lucanet, the required [transaction type categories](https://support.lucanet.com/en/documentation/glossary.md#transaction-type-category) can be created with the necessary transaction types and assigned to the relevant accounts/ items, depending on the schedule desired. Only the transaction types of the selected transaction type category are available for posting to these accounts.
The following transaction type categories are predefined in Lucanet:
- Fixed asset schedule
- Provision schedule
- Loans
- Equity
In addition to the predefined transaction type categories, an unlimited number of other transaction type categories can be created for the modeling of schedules.
## Creating Transaction Type Categories
To create a transaction type category:
1. Right-click the **Transaction types** root folder.
2. Choose **Create | Transaction type category** from the context menu. The **Create Transaction Type Category** dialog is displayed:
Creating a transaction type category
3. Specify the name of the element.
4. Choose an **icon** from the drop-down list.
5. Activate the check box **Divide transaction type category into two transaction type groups (fixed asset schedule),** if you wish to create the transaction type category for a fixed asset schedule.
> **Note:** The transaction type groups **Group 1** (intended for transaction types for costs) and **Group 2** (intended for transaction types for depreciation and amoritzation) are created automatically when the element is created.
## Configuring Transaction Type Categories
Editing a user-defined transaction type category
> **Note:** This section applies to both **predefined** and **user-defined** transaction type categories.
To configure a transaction type category:
1. Click the name of the transaction type category in the tree view.
2. Click **Edit** at the top right to open the editing mode.
The following options are available:
#### Formatting options
Allows selection of an icon
#### Initial consolidation and deconsolidation tab
Allows selection of transaction types for entries into or exits from the consolidation group
> **Note:** Notes:
>
> - These settings are used for data import as initial consolidation and for the wizard-assisted deconsolidation.
> - On the one hand, the specification of individual transaction types for the cases mentioned ensures that the indirect cash flow statement also records initial consolidation and deconsolidation effects correctly. On the other hand, these effects are also displayed in the respective schedules in separate transaction types.
#### Balance sheet planning with accounting rules tab
Allows selection of new transaction types for **debit** or **credit postings**
> **Note:** The specified transaction types are always used for the automatic contra entry and then for manual postings if no transaction type has been specified.
#### Import of balances tab
Allows selection of a new transaction type for posting differences in the opening balance
> **Note:** The starting balance from the data import is compared with the Lucanet balance of the previous period. If there is a difference, then it will be posted to the transaction type pre-set for differences.
---
---
title: "Creating and Configuring Transaction Types"
description: "Transaction types provide information on the reason for changes to an account. As a result, transaction types allow for seamless integration of schedules and cash flow statements in Lucanet on the level of the individual and consolidated financial statements, e.g. simultaneously in accordance with HGB, IFRS and US GAAP."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types/transaction-type-types
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Transaction Types
## Overview
**Transaction types** provide information on the reason for changes to an account. As a result, transaction types allow for seamless integration of schedules and cash flow statements in Lucanet on the level of the individual and consolidated financial statements, e.g. simultaneously in accordance with HGB, IFRS and US GAAP.
## Types of Transaction Types
### Default transaction type
| Name | Uses |
|---------|---------|
| 000 | During data imports or for manual postings without transaction type assignment, this transaction type accumulates all values that must be subsequently transferred, either manually or using suitable interfaces, to the financial accounting source system for maintenance of schedules. |
### Transaction type for the currency translation of balance accounts
| Name | Uses |
|---------|---------|
| Currency difference | Adjustments to the closing exchange rate are posted by the system to this transaction type for all balance accounts of the chosen transaction type category. It is also possible to post transaction types of type **currency difference**. They can be the target of a data import, for example, and can be chosen from the assignment table. |
| Currency difference | Adjustments to the closing exchange rate are posted by the system to this transaction type for all balance accounts of the chosen transaction type category. It is also possible to post transaction types of type **currency difference**. They can be the target of a data import, for example, and can be chosen from the assignment table. |
### Value query
| Name | Uses |
|---------|---------|
| Default | This transaction type is used for querying values. |
| Default | This transaction type is used for querying values. |
| Start | This transaction type is used for querying the balances of the previous period. When viewing schedules, this transaction type is queried, for example, to display the balance of a balance account at the beginning of the period. |
| TF | This transaction type is used for querying values. When viewing the transaction balance sheet, this transaction type is queried, for example to display the transaction figure on a balance account. |
| Balance | This transaction type is used for querying values. When the balance sheet is viewed, this transaction type is queried, for example, to display the balance on a balance account at the end of the period. |
### User-defined transaction type
| Name | Uses |
|---------|---------|
| _User-defined_ | In order to recreate customer-specific requirements for each schedule, you can create any number of individual, user-defined transaction types in each transaction type category. |
| _User-defined_ | In order to recreate customer-specific requirements for each schedule, you can create any number of individual, user-defined transaction types in each transaction type category. |
## Creating Transaction Types
To create a transaction type:
1. Right-click the transaction type category under which the transaction type is to be created.
2. Select **Create | Transaction type** from the context menu **.** The **Create Transaction Type** dialog is displayed.
Creating a transaction type
3. Specify the name of the element.
4. Activate the check box **Suppress automatic hiding of rows and columns with zero values** if lines and columns with zero values are also to be displayed.
5. Click **Save**.
> **Note:** After creating a transaction type, you can configure this transaction type and subsequently enable or disable the option **Suppress automatic hiding of rows and columns with zero values** as well as change the name of the transaction type.
---
---
title: "Creating and Configuring Transfer Actual Balance to Plan Wizards"
description: "The wizard can be used to transfer existing account balances from actual to planning periods for reporting entities."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/creating-and-configuring-transfer-actual-balance-to-plan-wizards
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Transfer Actual Balance to Plan Wizards
## Overview
The wizard can be used to transfer existing account balances from actual to planning periods for reporting entities.
The wizard can be created for all reporting entities for values of ledgers and schedules in planning data levels, either within a **journal** or from a **ledger**.
## Creating a Transfer Actual Balance to Plan Wizard Within a Journal
To create a transfer actual balance to plan wizard within a journal:
1. Open the **Journals** workspace.
2. In the dimension bar, select the combination of a **planning data level** and **reporting entity** for which a transfer actual balance to plan wizard should be created.
3. Right-click the root folder and choose **Create | Transfer actual balance to plan** from the context menu.
4. The system checks whether the selected planning data level is synchronized with the actual data level. If it is not, the **Edit Transfer Actual Balance to Plan** dialog is displayed:
Synchronizing the planning data level with the Actual data level
5. Click **Synchronize**.
6. The **Create Transfer Actual Balance to Plan Wizard** dialog is displayed:
Creating a transfer actual balance to plan wizard
7. Specify the **Element name** and click **Continue**.
## Creating a Transfer Actual Balance to Plan Wizard From a Ledger
To create a transfer actual balance to plan wizard from a ledger:
1. Select the desired ledger (general ledger, sub-ledger or statistical ledger).
2. In the dimension bar, select the combination of **planning data level** and **reporting entity** for which the wizard should be created.
3. Right-click in the row of the ledger hierarchy for which the wizard should be created and choose **Create | Transfer actual balance to plan**.
Creating a wizard from a ledger.
4. The system checks whether the selected planning data level is synchronized with the actual data level. If it is not, the **Edit Transfer Actual Balance to Plan** dialog is displayed:
Synchronizing the planning data level with the actual data level
5. Click **Synchronize**.
6. The **Create Transfer Actual Balance to Plan Wizard** dialog is displayed:
Creating a transfer actual balance to plan wizard
7. Specify the **Element name** and click **Continue**.
## Configuring a Transfer Actual Balance to Plan Wizard
To configure a transfer actual balance to plan wizard, click the name of the desired element in the tree view, and then click **Edit** in the top right. The configuration is divided into general properties in the header and two configuration steps in the main section of the editing mode.
### General Properties
General properties of a transfer actual balance to plan wizard
The following properties can be configured in the header:
| Property | Description |
|---------|---------|
| Element name | Name of the wizard |
| Cost center | Cost center in which the posting is to be performed by the planning wizard |
| Currency | Currency in which the posting is to be performed by the planning wizard |
| Adjustment level | Adjustment level in which the posting is to be performed by the planning wizard |
| Basis | Adjustment level (group) used as the planning basis |
### Step 'Configuration'
Configuration of the transfer actual balance to plan wizard
The following options can be configured in the **Configuration** step:
#### Account or item
An account or item that should be transferred
#### Transfer based on subledgers
In the subledger-based configuration, you can either define rules for items and accounts that differ from the existing accounting rules manually or adopt the accounting rules that have already been defined.
Transfer based on subledgers
**Defining accounting rules manually**
The following needs to be specified:
- **Account or item:** Select an account or item to be transferred from the drop-down list.
- **Basis:** Select the value that corresponds to the period to which the transfer should apply.
- **VAT/input tax configuration**
- **Cash flow impact**
- **Bank account:** Select the account to which the transfer amount is to be posted.
- **Do not consider values of subordinate items or accounts with accounting rules:** This option determines whether the accounting rules of subordinate items and accounts are considered. The checkbox is activated by default.Deactivate the checkbox to reconcile only the difference between the selected item or account and its subordinate items or accounts with their own accounting rules, instead of the entire value.
**Adopting accounting rules**
Click the **Adopt accounting rules** to automatically add all accounting rules of type **Payment** with a time offset ( **Time-delayed payment** or **Down payment transaction**) to the table, provided the receivables or liabilities account matches the one being configured. Any existing accounts in the table will be removed.
#### Transfer according to rule
In the rule-based reconciliation, it is possible to specify a user-defined rule for the reconciliation of the general ledger. This option should be used if an accounting rule from the planning data level must be corrected, for example because a different payment modality was assumed in the original planning.
Transfer according to rule
The following needs to be specified:
- **Basis:**
Choose **Month of the planning** to enter the number of calendar months from the beginning of the planning data level.
Choose **Calendar year** to enter certain calendar months for the cash flow impact.
- **Cash flow impact:**
If **Month of the planning** was previously selected, enter the number of calendar months to calculate the cash flow impact from the beginning of the planning data level to the entered number of calendar months.
If **Calendar year** was previously selected, enter the calendar month to calculate the cash flow impact of the calendar months you entered (see Cash flow impact).
- **Bank account:** Select the account to which the transfer amount is to be posted.
#### Manual transfer
It is possible to adapt individual accounts using the manual transfer.
Select the **Bank account** to which the transfer amount is to be posted.
> **Note:** The **Tranfer according to rule** and **Manual transfer** options are mutually exclusive.
### Step 'Values'
After configuring the **Transfer balance to plan wizard**, open the **Values step** to view the calculated amounts to be transferred in a table. The table includes a column for the **Partner** and one or more groups of columns. Each group represents a period from the wizard's data level, starting with the first period. The number of column groups depends on the accounting rules selected in the **Configuration** step and their **Cash flow impact** settings.
'Values' step in 'Transfer actual balance to plan' wizard
The following elements are available in the **Values** step:
| Element | Description |
|---|---|
| **Add/remove period** | - Only available if you have activated the **Manual transfer** option in the **Configuration** step - Can be used to add or remove additional periods |
| **Eliminate residual values** | - Only available if you have activated the **Manual transfer** option in the **Configuration** step - Can be used to clear any remaining balance from the selected period |
| **Partner** | The partner(s) used for the postings that create the balance that is to be transferred. If multiple partners were used, they are shown in separate rows in the table. |
| **Start value** | - Added only to the first month column and corresponds to the first month at the planning data level. - It displays the balance of the account or item whose balance is to be transferred using the wizard. The displayed value represents the balance from the last month of the actual data level. |
| **P&L** | - Added to all displayed months - Calculates the amount to be transferred from the account or item selected in the **Account or item** field to the account selected in the **Bank account** field within the **Transfer based on subledgers** table. The calculation is based on the rules configured in the **Accounting rules** workspace using the items selected in the configuration table. - If you hover over a cell in this column, a tooltip displays a breakdown of the calculation based on the different accounting rules selected during the configuration step.
**Note:** This column is visible only if you selected the **Transfer based on subledgers** option during the **Configuration** step. |
| **Balance** | - Added to all displayed months - For the first month, it calculates the difference between the **Start** **value** and the amount in the **P&L** column for that group. - For subsequent months, it calculates the difference between the **Balance** column from the previous month and the **P&L** amount for the current month. |
| **Manual** | - Added to all displayed months - Manually enter the amount to be transferred for the selected month. You can enter numbers with up to two decimal places; values are rounded from the third decimal (e.g. 0.044 rounds down to 0.04, while 0.045 rounds up to 0.05). You can also use basic mathematical operations: +, -, \*, /, parentheses (), the equals sign =, and decimal separators.
**Note:** This column is visible only if you selected the **Manual transfer** option during the **Configuration** step. |
| **Rule** | - Added to all displayed months - Calculates the amount to be transferred from the account or item selected in the **Account or item** field to the account selected in the **Bank account** field within the **Transfer according to rule** table. The calculation is based on the rules defined in the **Transfer according to rule** section, using the items selected in the configuration table.
**Note:** This column is visible only if you selected the **Transfer according to rule** option during the **Configuration** step. |
---
---
title: "Creating and Configuring Views"
description: "Choosing a view in the tree view of a ledger or schedule displays the associated dimension bar."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Views
## Overview
Choosing a **view** in the tree view of a ledger or schedule displays the associated **dimension bar**. The configuration of the view defines which dimensions can be configured in the dimension bar.
In **Lucanet Consolidation & Financial Planning** you can create and configure your own views with any desired **columns**. In addition to the default view for displaying time series, organization elements and adjustment levels, any desired multi-column **comparative views** can also be displayed for all evaluations.
For columns in views, there are five different **column types** that can be assigned to a **column** (see [Column Types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spaltentyp) and [Configuring Columns](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spalte-konfig)). The following figure shows a view with four columns. The first two columns are **value columns**. The third column is a column of type **Absolute difference**, the fourth column is of type **Difference %**.
View with column types
## Creating a New View
To create a new view in Consolidation & Financial Planning, proceed as follows:
1. Click in the dimension bar in the **Reporting and analyzing** workspace the **View** drop-down list and click **Configure views**.
'Configure views' in the 'View' drop-down list
2. In the tree view, right-click the **Public** or **Private** folder and choose **New | View** from the context menu. The **Create View** dialog is displayed as follows:
Dialog for creating a new view
3. Enter a name and click **Save**.
The view is created and appears in the tree view.
## Configuring a View
To configure a view in Consolidation & Financial Planning, navigate to the newly created view in the tree view and click **Edit** in the detail view:
Edit mode of a view
1. Change the **Name** of the view, if required.
2. Activate **Hide fixed or unused dimensions**, if desired, to hide the drop-down lists for dimensions that are fixed to a single element or not used in the dimension bar.
3. Click **Add column** to add a column to the view (see [Additional Options](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spalten)).
4. Configure the column by defining the column type (see [Column Types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spaltentyp)) and its options (see [Configuring Columns](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spalte-konfig)).
5. If necessary, add more columns and configure them the same way.
### Column Types
For each column, choose the desired column type from the column types drop-down list (see [Additional Options](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spalten) for adding a column). The following column types are available:
Column types for views
| Column type | Description |
|---------|---------|
| **Value** | Is used to display a value from the data model in a column. |
| **Absolute difference** | Is used to display the difference between the values of two columns in a single column in the tree view. |
| **Difference in %** | Is used to display the relative difference between the values of two columns in a single column in the tree view. |
| **Value in %** | Is used to display the value of a column as a percentage of a reference column in a single column in the tree view. |
| **Exchange rate** | Is used to display the exchange rate between the display currencies of two columns in a single column in the tree view. |
> **Note:** The column types **Absolute difference** and **Difference in %** are only available for selection if there are at least two columns.
### Configuring Columns
Click the **plus icon** next to a column to expand its configuration details. The configuration options for a column differ depending on which column type is selected (see [Column Types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views/.md#spaltentyp)):
#### Value
The following figure shows the configuration options for the column type **Value**:
Column settings for the column type 'Value'
The following options are available for the column type 'Value':
| Dimension | Reference |
|---------|---------|
| **Time** | Dimension bar row to which the period window should belong. If necessary, enter a time offset in **Time offset (in months)** — with a time offset of twelve months, for example, you can configure the display of values from the previous year. Reset the time offset with the input 0. Activate **Fixed period** to use a fixed period instead of a dimension bar row. |
| **Adjustment level** | Dimension bar row to which the adjustment level should belong, or a fixed adjustment level |
| **Data level** | Dimension bar row to which the data level should belong, or a fixed data level |
| **Organization element** | Dimension bar row to which the organization element should belong, or a fixed organization element |
| **Transaction currency** | Dimension bar row to which the transaction currency should belong, or a fixed transaction currency |
| **Display currency** | Dimension bar row to which the display currency should belong, or a fixed display currency |
| **Partner** | Dimension bar row to which the partner should belong, or a fixed partner |
| **Year-to-date** | Displays year-to-date values in the column |
| **Heading** | Customized column heading |
#### Absolute difference
The following figure shows the configuration options for the column type **Absolute difference**:
Column settings for the column type 'Absolute difference'
The following options are available for the column type 'Absolute difference':
| Dimension | Reference |
|---------|---------|
| **Comparison value** | Column that contains the comparison value |
| **Reference value** | Column whose value is to be subtracted from the value of the **Comparison value** column |
| **Heading** | Customized column heading |
#### Difference in %
The following figure shows the configuration options for the column type **Difference in %**:
Column settings for the column type 'Difference in %'
The following options are available for the column type 'Difference in %':
| Dimension | Reference |
|---------|---------|
| **Comparison value** | Column that contains the comparison value |
| **Reference value** | Column whose value is to be subtracted from the value of the **Comparison value** column |
| **Formatting** | Defines whether the percentage value is to be displayed **Without decimal places**, with **One decimal place**, or with **Two decimal places**. |
| **Heading** | Customized column heading |
#### Value in %
The following figure shows the configuration options for the column type **Value in %**:
Column settings for the column type 'Value in %'
The following options are available for the column type 'Value in %':
| Dimension | Reference |
|---------|---------|
| **Reference value** | Column whose value is used as the basis for the percentage display |
| **Formatting** | Defines whether the percentage value is to be displayed **Without decimal places** or with **Two decimal places**. |
| **Heading** | Customized column heading |
#### Exchange rate
The following figure shows the configuration options for the column type **Exchange rate**:
Column settings for the column type 'Exchange rate'
The column shows the read-only formula **Display currency (quote) / display currency (base)**, followed by the following options:
| Dimension | Reference |
|---------|---------|
| **Display currency (quote)** | Column whose display currency is used as the quote currency in the exchange rate |
| **Display currency (base)** | Column whose display currency is used as the base currency in the exchange rate |
| **Heading** | Customized column heading |
### Additional Options
The following additional options are available for columns when configuring a view:
| Option | Description |
|---------|---------|
| **Change order** | Changes the order of the columns. Only available if the view contains at least two columns. |
| **Eye icon** | Hides or shows the column |
| **Three-dot menu** | Opens a menu with **Duplicate** and **Delete**. **Delete** is only available if the view contains more than one column. |
| **Plus/minus icon** | Expands (**+**) or collapses (**−**) the column's configuration details |
Click **Save** to apply your changes, or **Cancel** to discard them.
## Activating Views for Lucanet Consolidation & Financial Planning
Views for configuring the [dimension bar](https://support.lucanet.com/en/documentation/glossary.md#dimension-bar) in account hierarchies can be defined in both **Lucanet.Financial Client** and **Lucanet Consolidation & Financial Planning**. The views defined in **Lucanet.Financial Client** can be activated for use in **Lucanet Consolidation & Financial Planning**.
To activate a view from **Lucanet.Financial Client** for use in **Lucanet Consolidation & Financial Planning**:
Video: https://player.vimeo.com/video/859278661?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
---
---
title: "Creating and Editing Configurations"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configurations-consolidation-1
language: en
last_updated: 2026-05-01
---
# Creating and Editing Configurations
## Overview
Before you can execute the consolidation wizards of Consolidation 1, you must create **Configurations** on the basis of which the consolidation wizards are executed.
## Creating Configuration
To create a configuration:
1. Open the **Consolidation areas** workspace in the **Consolidating** folder.
2. Select the desired consolidation area for which you want to create a configuration and select the desired configuration from the **Create** context menu:
Create configuration
3. Enter a **name** for the configuration.
4. Select the desired consolidation type (Only for **Elimination of intercompany debt** and **Elimination of intercompany income and expense**).
5. Click **Save** or press **Enter**.
6. In the detail view of the configuration, click **Edit** and configure the configuration (see section [Editing Configuration](#editing-configuration))
## Available Configurations
The following configurations are available:
| Element | Description |
|---------|---------|
| Paired elimination of intercompany debt | **Paired elimination of intercompany debt** allows you to configure a wizard-supported elimination of debts between affiliated companies of a consolidation area. Pair combinations are formed of all reporting entities or cost centers that are assigned to the consolidation area (see section [Paired elimination of intercompany debt](#paired-elimination-of-intercompany-debt)). |
| Lump sum elimination of intercompany debt | **Lump sum elimination of intercompany debt** allows you to perform a wizard-supported elimination of debts and accounts receivable between affiliated companies. The accounts defined in the wizard configuration are offset against one another on a lump sum basis. By contrast to paired elimination of intercompany debt, no partner information is required for lump sum elimination of intercompany debt (see section [Lump sum elimination of intercompany debt](#lump-sum-elimination-of-intercompany-debt)) |
| Paired elimination of intercompany income and expense | **Paired elimination of intercompany income and expense** allows you to perform a wizard-supported elimination of income and expenses between affiliated companies of a consolidation area. Combined pairs of accounts are formed between reporting entities or cost centers based on pre-assigned partner information as well as the settings made in the configuration (see section [Paired elimination of intercompany income and expense](#paired-elimination-of-intercompany-income-and-expense)). |
| Lump sum elimination of intercompany income and expense | **Lump sum elimination of intercompany income and expense** allows you to perform a wizard-supported elimination of income and expense between affiliated companies. The accounts defined in the wizard configuration are offset against one another on a lump sum basis. By contrast to paired elimination of intercompany income and expense, no partner information is required for lump sum elimination of intercompany income and expense (see section [Lump sum elimination of intercompany income and expense](#lump-sum-elimination-of-intercompany-income-and-expense)) |
| Elimination of intercompany income and expense based on group-internal revenue | **Elimination of intercompany income and expense based on group-internal revenue** allows you to perform a wizard-supported elimination of income and expenses between affiliated companies. The group-internal revenue accounts defined in the wizard configuration are offset against one or more expense accounts stating a percentage (see section [Elimination of intercompany income and expense based on group-internal revenue](#elimination-of-intercompany-income-and-expense-based-on-groupinternal-revenue)). |
| Inventory consolidation | **Inventory consolidation** allows you to configure a wizard-supported elimination of intercompany profit or loss contained in stock (inventory) between affiliated companies of a consolidation area. Pair combinations are formed of all reporting entities or cost centers that are assigned to the consolidation area (see section [Inventory consolidation](#inventory-consolidation)). |
## Editing Configuration
The options for the configurations depend on the selected configuration and the selected consolidation type:
### Paired elimination of intercompany debt
The **configuration for the paired elimination of intercompany debt** is displayed as follows, for example:
Paired elimination of intercompany debt: 'General' tab
The following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the paired elimination of intercompany debt:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
#### Default values
The default configuration for all pair combinations of the consolidation area is performed on the **Default values** tab:
Paired elimination of intercompany debt: 'Default values' tab
**Area 'Assigned balance sheet items'**
The following options are available in the **Assigned balance sheet items** area:
| Option | Description |
|---|---|
| **Balance sheet items** | Balance sheet items to be consolidated.
Click **\+ Add row** to add balance sheet items. |
| **Threshold value for display** | If a difference exceeds the entered value, the difference is displayed in red. |
| **Incorporate deferred tax** | Activate the check box if deferred tax should be incorporated. |
| **Tax rate (in percent of the profit/loss)** | Tax rate for deferred tax. Displayed when the **Incorporate deferred tax** check box is activated. |
**Area 'Post to'**
The following categories are available in the **Post to** area:
| Category | Description |
|---|---|
| **Default difference account** | Default difference accounts to be used to clear the arising differences |
| **Deferred tax** | Accounts on which the deferred taxes are to be presented. The row **Deferred tax** is only displayed when the check box **Incorporate deferred tax** is activated. |
If necessary, add **Partners** and **Transaction types** for each category for the postings.
> **Note:** Transaction types can only be selected for schedule-relevant accounts or items.
#### Deviating values
Individual configurations can be created for each pair combination on the **Deviating values** tab:
Paired elimination of intercompany debt: 'Deviating values'
**Area 'Deviating values per pair combination'**
- **Pair combination**: Select the desired pair combination you want to configure.
**Area 'Details on the pair combination'**
The following options are available in the **Details on the pair combination** area:
| Option | Description |
|---|---|
| **Define deviating values** | Activate the check box if deviating values are to be taken into account for the selected pair combination |
| **Threshold value for the display** | If a difference exceeds the value entered for the elimination of intercompany debt, the difference is displayed in a red font. |
| **Tax rate (in percent of the profit/loss)** | Tax rate for deferred tax. Displayed when the **Incorporate deferred tax** option is activated. |
**Area 'Post to'**
The following categories are available in the **Post to** area:
| Category | Description |
|---|---|
| **Default difference account** | Default difference accounts to be used to clear the arising differences for the selected pair combinations. |
| **Deferred tax** | Accounts on which the deferred taxes are to be presented. The **Deferred taxes** row is displayed when the option **Incorporate deferred tax** is activated. |
If necessary, add **Partners** and **Transaction types** for each category for the postings.
> **Note:** Transaction types can only be selected for schedule-relevant accounts or items.
### Lump sum elimination of intercompany debt
The **configuration for the lump sum elimination of intercompany debt** is displayed as follows, for example:
Lump sum elimination of intercompany debt: 'General' tab
The following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the lump sum elimination of intercompany debt:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
#### Accounts
The default configuration for all pair combinations of the consolidation area is performed on the **Accounts** tab:
Lump sum elimination of intercompany debt: 'Accounts' tab
| Option | Description |
|---|---|
| **Threshold value for display** | If a difference exceeds the entered value, the difference is displayed in red. |
| **Difference account (debit posting/credit posting)** | Accounts for postings in debit and credit to which any arising differences are to be posted |
| **Accounts to be accumulated** | Select an account to be accumulated and specify the organization elements to be consolidated in the details window. The following options are available: - **All direct organization elements of the consolidation area**, to consolidate only those consolidation units that are directly assigned to the consolidation area (excluding sub-groups). - **All direct and indirect organization elements of the consolidation area**, to consolidate also consolidation units in subordinate consolidation areas (including sub-groups; see section [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)). - **Individual**, to compile the consolidation units to be consolidated in the **Organization elements** list. |
### Paired elimination of intercompany income and expense
The **configuration for the paired elimination of intercompany income and expense** is displayed as follows, for example:
Paired elimination of intercompany income and expense: 'General' tab
The following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the paired elimination of intercompany income and expense:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings. |
| **Target** | Adjustment level on which postings are to be made |
#### Default values
The default configuration for all pair combinations of the consolidation area is performed on the **Default values** tab:
Paired elimination of intercompany income and expense: 'Default values' tab
**Area 'Assigned P&L items'**
The following options are available in the **Assigned P&L items** area:
| Option | Description |
|---|---|
| **P&L items** | P&L items to be consolidated. Click **\+ Add row** to add P&L items |
| **Threshold value for display** | If a difference exceeds the entered value, the difference is displayed in red. |
**Area 'Post to'**
In the **Account** column, specify the default difference account to which any differences should be posted. Add **Partner** and **Transaction type** if necessary.
> **Note:** Transaction types can only be selected for schedule-relevant accounts or items.
#### Deviating values
Individual configurations can be created for each pair combination on the **Deviating values** tab:
Paired elimination of intercompany income and expense: 'Deviating values' tab
**Area 'Deviating values per pair combination'**
- **Pair combination**: Select the desired pair combination you want to configure.
**Area 'Details on the pair combination'**
The following options are available in the **Details on the pair combination** area:
| Option | Description |
|---|---|
| **Define deviating values** | Activate the check box if deviating values are to be taken into account for the selected pair combination |
| **Threshold value** | Threshold value for the display. If a difference exceeds the value entered for the elimination of intercompany income and expense, the difference is displayed in a red font. |
| **Tax rate (in percent of the profit/loss)** | Tax rate for deferred tax. Displayed when the **Incorporate deferred tax** option is activated. |
**Area 'Post to'**
In the **Account** column, specify a deviating default difference account for the selected pair combination. Add **Partner** and **Transaction type** if necessary.
> **Note:** Transaction types can only be selected for schedule-relevant accounts or items.
### Lump sum elimination of intercompany income and expense
The **configuration for the lump sum elimination of intercompany income and expense** is displayed as follows, for example:
Lump sum elimination of intercompany income and expense: 'General' tab
The following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the lump sum elimination of intercompany income and expense:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
#### Accounts
On the **Accounts** tab, specify the accounts to be accumulated:
Lump sum elimination of intercompany income and expense: 'Accounts' tab
| Option | Description |
|---|---|
| **Threshold value for display** | If a difference exceeds the entered value, the difference is displayed in red. |
| **Difference account** | Account to which the arising differences are to be posted |
| **Accounts to be accumulated** | Select an account to be accumulated and specify the organization elements to be consolidated in the details window. The following options are available: - **All direct organization elements of the consolidation area**, to consolidate only those consolidation units that are directly assigned to the consolidation area (excluding sub-groups). - **All direct and indirect organization elements of the consolidation area**, to consolidate also consolidation units in subordinate consolidation areas (including sub-groups; see section [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)). - **Individual**, to compile the consolidation units to be consolidated in the **Organization elements** list. |
### Elimination of intercompany income and expense based on group-internal revenue
The **configuration for the elimination of intercompany income and expense based on group-internal revenue** is displayed, for example, as follows:
Elimination of intercompany income and expense based on group-internal revenue: 'General' tab
For **elimination of intercompany income and expense based on group-internal revenue**, the following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the elimination of intercompany income and expense based on group-internal revenue:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
#### Base and target accounts
On the **Base and target accounts** tab, specify the accounts for reporting the group-internal revenue (**base accounts**) and the contra accounts (**target accounts**). Define the **share** in percent of the target account.
elimination of intercompany income and expense based on group-internal revenue: 'Base and target accounts' tab
| Option | Description |
|---|---|
| **Base accounts** | Accounts for the calculation of group-internal revenue |
| **Target accounts** | Accounts for the contra entry |
| **Share** | Percentage share of the target account |
**Organization elements to be consolidated**
You must specify the organization elements to be consolidated for each base account. As soon as you select a base account, more options are displayed:
| Option | Description |
|---|---|
| **All direct organization elements of the consolidation area** | Only those consolidation units that are directly assigned to the consolidation area (excluding sub-groups) are consolidated. |
| **All direct and indirect organization elements of the consolidation area** | Consolidation units in subordinate consolidation areas are also consolidated (including sub-groups; see [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)). |
| **Individual** | Individual selection of the consolidation units in the **Organization elements** list. |
### Inventory consolidation
The **configuration for inventory consolidation** is displayed as follows, for example:
Inventory consolidation: 'General' tab
The following options must be configured:
#### Name
Name of the configuration
#### General
In the **General** area, edit the general properties of the inventory consolidation:
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings
**Note:** Cost centers can be created for the individual consolidation steps below the consolidation reporting entity (see section [Creating a Consolidation Reporting Entity](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)). |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
#### Default values
The default configuration for all pair combinations of the consolidation area is performed on the **Default values** tab:
Inventory consolidation: 'Default values' tab
**Area 'Assigned balance sheet items'**
The following options are available in the **Assigned balance sheet items** area:
| Option | Description |
|---|---|
| **Balance sheet items** | Balance sheet items to be consolidated.
Click **\+ Add row** to add balance sheet items. |
| **Contained profit or loss portion** | Percentage of the assigned balance sheet items that contains intercompany profit or loss (negative values are also permitted). |
| **Incorporate deferred tax** | Activate the check box if deferred tax should be incorporated. |
| **Tax rate** | Tax rate for deferred tax, in percent of the profit/loss. Displayed when the **Incorporate deferred tax** check box is activated. |
| **Reclassifications within P&L** | Activate the check box if the eliminated profit or loss should be reclassified within the profit and loss statement. **Amount to be moved**, in percent of the capitalized inventory, is displayed when the check box is activated. |
| **Reclassifications within balance sheet** | Activate the check box if the eliminated profit or loss should be reclassified within the balance sheet. **Amount to be moved**, in percent of the capitalized inventory, is displayed when the check box is activated. |
**Area 'Post to'**
The following categories are available in the **Post to** area:
| Category | Description |
|---|---|
| **Profit and loss portion** | P&L account to which the eliminated profit or loss is posted. |
| **Deferred taxes** | Balance sheet accounts (debit posting and credit posting) and a P&L account on which the deferred taxes are to be presented. Only displayed when the check box **Incorporate deferred tax** is activated. |
| **Reclassification within the P&L** | Difference accounts (debit posting and credit posting) for the reclassification within the P&L. Only displayed when **Reclassifications within P&L** is activated. |
| **Reclassifications within the balance sheet** | Difference accounts (debit posting and credit posting) for the reclassification within the balance sheet. Only displayed when **Reclassifications within balance sheet** is activated. |
If necessary, add **Partners** and **Transaction types** for each category for the postings.
> **Note:** Transaction types can only be selected for schedule-relevant accounts or items.
#### Deviating values
Individual configurations can be created for each pair combination on the **Deviating values** tab:
Inventory consolidation: 'Deviating values' tab
**Area 'Deviating values per pair combination'**
- **Pair combination**: Select the desired pair combination you want to configure.
**Area 'Details on the pair combination'**
The following options are available in the **Details on the pair combination** area:
| Option | Description |
|---|---|
| **Define deviating values** | Activate the check box if deviating values are to be taken into account for the selected pair combination. The current settings from the **Default values** tab are applied as the starting values. |
| **Contained profit or loss portion** | Percentage for the selected pair combination (negative values are also permitted). |
| **Tax rate** | Tax rate for deferred tax, in percent of the profit/loss. Displayed when the **Incorporate deferred tax** option is activated on the **Default values** tab. |
| **Amount to be moved within the P&L** | In percent of the capitalized inventory. Displayed when **Reclassifications within P&L** is activated on the **Default values** tab. |
| **Amount to be moved in the balance sheet** | In percent of the capitalized inventory. Displayed when **Reclassifications within balance sheet** is activated on the **Default values** tab. |
> **Note:** Pair combinations for which deviating values have already been configured are displayed in **bold** in the drop-down list, and the number of pair combinations with configured deviating values is displayed in the tab name. Subsequent changes to the **Default values** tab do not affect pair combinations for which deviating values have already been configured.
---
---
title: "Creating and Executing Scripts"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts
language: en
last_updated: 2026-05-01
---
# Creating and Executing Scripts
## Overview
In the **Scripts** workspace as well as in [directory structures](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md), scripts can be created, edited, and executed.
Scripts can be used to read out, change, augment, and import data from different systems. Each script contains all instructions required to execute a specific task (e. g. import data into Lucanet.Financial Warehouse).
The **Application** function is also available in the **Scripts** workspace. This function can be used to load **Lucanet.Script Execution Application** (SEA for short) into the workspace.
> **Warning:** The scripts used to import data into Lucanet.Financial Warehouse are usually created by Lucanet.Consulting. If necessary, get in touch with your Lucanet contact.
## Creating and Configuring a Script as a Video
The video provides you with the most important information on the topic of **creating a script and configuring it with the values from its script documentation**:
Video: https://player.vimeo.com/video/1201751077?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The second part of the video configures one specific script, **DATEV Kanzlei-Rechnungswesen pro (#3021-FI-GDPdU.FWH)**, as a worked example. Each script comes with its own documentation that describes the parameters of that script, so the values differ per script.
## Creating a Script
To create a script:
1. In the overview, click the **Import and Journals** workspace.
2. In the tree view of the workspace, right-click **Scripts** or a folder and select the following from the context menu: **Create | Script**:
Create a new script
3. Choose one of the following options to load the script into the **Scripts** workspace in the subsequent dialog:
- **Drag and drop** the desired script into the dialog.
- Click **browse** and navigate to the desired script.
4. The script is created.
5. In the detail view of the script, click **Edit** to configure the script (see following section).
## Options for Scripts
The following options are available for scripts:
| Option | Description |
|---|---|
| **Execute** | Execute the script (see following chapter)
**Note:** If necessary, values required for execution of the script must be specified on the **Configuration** tab. |
| **Edit** | Open edit mode for the script: - **Name**: name of the script - **Configuration**: values required to execute the script
**Note:** There is usually a separate documentation for scripts, which describes the configuration of the script. |
> **Note:** The **Uses** tab shows which Lucanet objects (e.g. data sources) access this script.
## SEA used to import data into Lucanet.Financial Warehouse
> **Note:** **Lucanet Script Execution Application** ( **SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script.
If you want to import data from ERP source systems and these source systems are operated on premises, you must perform the following steps before importing via script:
1. Create SEA certificate (see [Generating and Downloading SEA Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md)).
2. Install SEA (see [Installing and Using](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md) [Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)).
3. Create SEA in the **Scripts** workspace as an application (see [Installing and Using Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)).
4. Assign SEA as an application in the **data source** (see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh.md))
## Executing Scripts
You can manually execute either individual scripts or all scripts in a folder at the same time.
### Executing Individual Scripts
To manually execute individual scripts:
1. In the **Scripts** workspace, select the script you would like to execute. The detail view is displayed as follows, for example:
Executing a script
2. If applicable, choose the **Execution location** of the script. To do so, open the edit mode and choose if you want to execute the script **on the server** or on any configured **Script Execution Application (SEA)**.
(For more information on SEA, see the previous chapter and [Installing and Updating Lucanet Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md).)
3. Click **Execute**.
4. If applicable, specify the configuration values in the **Execute - _script name_** dialog.
5. Click **Start** to start the execution.
### Executing All Scripts in a Folder Together
You can also choose to execute all scripts in a folder or below the root folder at the same time. In this case, the scripts are executed one after another in the order in that they are arranged under the folder or root folder. Proceed as follows:
1. Select the root folder or folder of the scripts you would like to execute together. The detail view is displayed as follows, for example:
Executing all scripts of a folder
2. If necessary, change the sequence of the scripts using the context menu command **Change order**.
3. Define whether to continue executing scripts in the event of an error:
- Retain the preconfigured **Execute** option if scripts must always be executed, even if an error occurs during execution.
- Select the option **Do not execute** if subsequent scripts are not to be executed when one or more errors arise during execution of a script.
**Note**: To define the behavior in the event of errors when executing folders with subordinate scripts in **directory structures**, choose either the **Continue execution** or **Cancel execution** option.
4. Click **Execute**.
5. If applicable, specify the configuration values in the **Execute - _script name_** dialog.
6. Click **Start** to start the execution.
> **Note:** For a detailed history of past executions, including the process log of each run, open the **Execution log** tab in the script's change log. For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
## 'Uses' Tab
By which elements the script is used is displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column:
---
---
title: "Creating and Executing the Data Import"
description: "All data that is imported into reporting entities is transferred to the current Lucanet database using data imports. The data import object is used to determine which data source and assignment table are to be used during the import."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import
language: en
last_updated: 2026-05-01
---
# Creating and Executing the Data Import
## Overview
All data that is imported into reporting entities is transferred to the current Lucanet database using data imports. The **data import** object is used to determine which data source and assignment table are to be used during the import.
The actions in the detail view of the data import are used to execute the data import, create assignments in the assignment table used and save the data import. You can create any number of data imports which can be updated at any time and combined in data import folders.
## Creating a Data Import
To create a data import:
1. Choose the command **Create | Data import** from the context menu of the **Data imports** root folder or a data import folder.
Creating a data import
2. Enter a name for the data import in the **Create data import** dialog and click **Save**.
The data import is created. The **detail view** of the data import is displayed as follows:
Detail view of a data import
3. If necessary, activate the **Execute data import as initial consolidation check box**, if all items of the general ledger are to be posted automatically to the corresponding **transaction type category** with transaction type **Addition to consolidation area**. This ensures that the effects of the initial consolidation are displayed correctly also in the cash flow statement.
Detail view of an import with activated 'Execute data import as initial consolidation' check box
When activating the check box, three drop-down lists are displayed:
- Choose the accounting period (posting month) and carry forward account for P&L values from the **Accounting period** and **Carry forward account** drop-down lists displayed.
- If necessary, choose a subledger in the **P&L** drop-down list. All subledgers can be selected.
4. Configure the data import (see section [Configuring the Data Import](#configure_import)).
5. Import the data (see section [Executing the Data Import](#excecute_import)).
## Configuring the Data Import
Click **Edit** to configure the data import. The following options are available in the detail view of a data import:
| Option | Description |
|---------|---------|
| Name | Name of the data import |
| Data source | The data source to be used. You can choose from all data sources in the **Data sources** root folder. |
| Configure | Opens the dialog with the properties of the data source. Used to check or change the **data source**(see chapter [Defining the Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)). |
| Assignment table | The **assignment table** to be used. You can choose from all assignment tables in the **Assignment tables** root folder. |
> **Note:** If necessary, a description of the data source is displayed on the **Additional information** tab. The description of a data import is optional and can currently be entered only in Lucanet.Financial Client.
## Importing Data
To import data:
1. Click **1\. Import**. The **Configuration** dialog is displayed:
Dialog for the configuration of the import parameters
2. Enter the **data level** and the desired **adjustment level** and add the Excel file to be imported in the **Data source** field.
3. Click **Save**. If there are any missing assignments, these assignments will be displayed in the detail view of the import:
Detail view with the display of missing assignments
4. Click **2\. Assign**. The **assignments** are displayed, for example as follows:
Assignment table with missing assignments
5. Check the assignments and, if necessary, edit any missing assignments (see chapter [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)).
6. Save the data import by clicking **3\. Save**.
> **Warning:** - Every newly-created data import can only be saved when the import has been successfully performed and all elements have been assigned so that debit = credit is guaranteed in the general ledger (assets side = equity and liabilities side).
> - If a data import is to be performed for a period, a reporting entity, a data level or a adjustment level disabled by any **audit trail**, an error message is displayed. If necessary, switch to Lucanet.Financial Client to edit the relevant audit trail.
> **Note:** As soon as a data import has been successfully saved, the data of the created postings are displayed on the **Postings** tab. You can open the details of each posting by clicking the corresponding link in the **Posting** column.
>
> Furthermore, the **data source** and **assigment table** used for this import can be accessed via a link in the general properties of the data import.
>
> the detail view of a data import with 'postings' tab. tab heading is outlined in red. a posting is displayed on 'postings' tab. icon
> 'Postings' tab with a created posting
> **Note:** For a detailed history of past executions, including the process log of each run, open the **Execution log** tab in the data import's change log. For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
---
---
title: "Creating Assignment Tables"
description: "Assignment tables are used to save all elements imported from the source systems (accounts, reporting entities/cost centers, partners, transaction currency, transaction types, data levels, adjustment levels) and their assignment to elements in the Lucanet database."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-assignment-table
language: en
last_updated: 2026-05-01
---
# Creating an Assignment Table
## Overview
**Assignment tables** are used to save all elements imported from the source systems (accounts, reporting entities/cost centers, partners, transaction currency, transaction types, data levels, adjustment levels) and their assignment to elements in the Lucanet database. Assignments are defined during the data import and can then be changed or deleted at any time.
## Creating an Assignment Table
To create an assignment table:
1. In the tree view, right-click the **Assignment tables** folder and choose **Create | Assignment table** from the context menu.
Creating an assignment table
2. The **Create element** dialog is displayed:
Dialog 'Create element'
3. Specify the name of the assignment table in the **Name** field.
4. Click **Save** or press **Enter**.
5. The assignment table is displayed in the tree view and can be selected when defining data imports.
> **Note:** The assignments are configured during the data import (see chapter [Creating and Executing a Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)). You can find detailed instructions on the configuration of an assignment table in [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md).
---
---
title: "Creating Consolidated Financial Statements"
description: "After you have defined the structure and master data of your group, you can configure the app-supported consolidation of your group in the Consolidated financial statements workspace."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/creating-consolidated-financial-statements
language: en
last_updated: 2026-05-01
---
# Creating Consolidated Financial Statements
## Overview
After you have defined the structure and master data of your group, you can configure the app-supported consolidation of your group in the **Consolidated financial statements** workspace.
To do so, first create a so-called consolidated financial statement element in the **Consolidated financial statements** workspace for the desired combination of **group and data level** and define the **time period** of the consolidated financial statements. This chapter describes how to proceed.
Subsequently, in these consolidated financial statements elements, you can:
- Transfer the [proportioned data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md) from the organization elements in the consolidation areas
- Configure all consolidation apps needed for the consolidated financial statements
- Execute the [consolidated financial statements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md)
> **Warning:** **Notes for customers who have used apps of the Consolidation 2 or Consolidation 2 Next Generation in Lucanet.Financial Client**
>
> - Elements of type **File** and **Text document** cannot be displayed and/or edited in the **Lucanet CFO Solution Platform**
> - For information on the apps supported in the CFO Solution Platform, please read the [Notes on Migration From Lucanet.Financial Client](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/migration-from-lnfc.md).
## Creating a Consolidated Financial Statements Element
To create a Consolidated financial statements element, proceed as follows:
1. Open the **Consolidated financial statements** workspace.
2. In the dimension bar, select the combination of **group** and **data level** for which you wish to create the consolidated financial statements.
3. If you have not yet defined master data for this combination of **group** and **data level**, click **\+ Create** in **Master Data Administration** and configure the master data as described under [Administrating Master Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md).
If you have already defined Master Data, a link to the corresponding **Master Data Management** is displayed.
4. Highlight the root folder **Consolidated financial statements** and select **New | Consolidated financial statements** from the context menu.
5. Configure the options in the **Create consolidated financial statements** dialog as described below **.**
6. Save the element.
## Options
The following options are available:
Create consolidated financial statements
| Option | Description |
|---|---|
| **Name** | Group financial statements name |
| **Period** | Period of the consolidated financial statements.
**Note:** The time period must lie within the time period of the selected data level. |
| **Behavior in case of error** | Choose the desired behavior if an error occurs during execution of the consolidated financial statements: - **Continue execution** - **Cancel execution** |
| **Use template** | Activate this option if you would like to use a template for the consolidated financial statements. Then, in the **Journal** select the desired combination of **data level** and **group** and from the drop-down list the desired **consolidated financial statements** to be used as a template.
**Note:** In Lucanet CFO Solution Platform only templates can be used that exclusively contain consolidation apps of the Next Generation. |
---
---
title: "Creating Postings in Ledgers and Schedules"
description: "Manual postings can be created directly from any cell in a ledger or schedule"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/creating-postings-in-ledgers-schedules
language: en
last_updated: 2026-05-01
---
# Creating Postings in Ledgers and Schedules
## Overview
In Consolidation & Financial Planning, manual postings can be created directly from any cell in a ledger or schedule for reporting entities, consolidation reporting entities, cost centers, consolidation areas, or consolidation units.
> **Tip:** To analyze, review, or share posting data, you can generate a report of all postings. For instructions on how to do this, see [Creating a Posting Report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/create-postings-report.md).
## Creating a Posting
To create a posting from a ledger or schedule:
1. Open the ledger or schedule.
2. Right-click on the cell for which you want to create a posting and and choose **Create | Posting** from the context menu.
The **Create Posting** dialog is displayed:
'Create Posting' dialog
3. Specify the **name** of the element.
4. If necessary, change the **period** for the posting.
5. If necessary, change the **currency** in which the posting is to be made.
6. If necessary, change the **adjustment level.**
7. Click **Continue** and follow the steps below to configure the posting details.
## Configuring a Posting
To configure a posting, click the name of the desired posting in the tree view, and then click **Edit** in the top right.
Configuration of general properties of a posting
### General Properties
The following properties can be edited in the header:
| Property | Description |
|---------|---------|
| Name | Name of the posting |
| Currency | Currency in which the postings are to be made |
| Adjustment level | Adjustment level in which the postings are carried out |
### Values Tab
The **Values** tab is displayed as follows, for example:
Configuration of the 'Values' tab in a posting
### Toolbar
The following options are available in the toolbar of the **Values** tab:
| Option | Description |
|---|---|
| **Show and hide account hierarchies** | Allows showing or hiding additional account hierarchies for account selection
The ledgers specified here are displayed in the table below. By default, the general ledger is available for account selection which is assigned to the reporting entity or consolidation area for which the posting is created. When creating a new posting, the general ledger account hierarchy (including all subledgers) is automatically selected if the user has the necessary permissions. |
| **Edit value columns** | Allows editing the value columns of the posting mask. A dialog is opened, in which you can add or remove value columns, and store a comment such as the specific posting date for each value column |
| **Resolve difference** | Resolves differences (values) within the posting |
| **Show cumulated** | Displays the values in the posting columns cumulated. As a result, the total is displayed over all posting times.
If the option is not activated, all values of a posting are listed separately per posting time. |
| **D/C recording** | Switches the view from plus and minus recording to the entry of accounting values in debit and credit. |
| **Historical exchange rate translation** | Activates the historical exchange rate translation for this posting. Check [Historical Exchange Rate Translation](#historical-exchange-rate) to see how to configure the section. |
| **Cost center/Partner/Transaction type** | Toggles visibility of the respective columns in the table
**Note:** Hiding these columns does not affect the data stored in them — the system retains the information and uses it when generating the posting. |
'Show and Hide Account Hierarchies' dialog
### Posting Data
The following options are available in the **Posting Data** section of the **Values** tab:
| Option | Description |
|---|---|
| **Account** | Selection of an account or item for creating a posting
You can display only those accounts that contain postings for selection by clicking the drop-down list in the **Account** column and selecting the **Show only accounts with postings** option:
**Note:** **Notes on the **D/C recording** button:** - When the **D/C recording** button is **deactivated**, the general ledger account hierarchy (including all subledgers) is split into two blocks representing the **debit and credit sides** of the same posting: - In the **Debit** posting block, only debit accounts that can be debited are shown. - In the **Credit** posting block, only credit accounts that can be credited are shown. - When the **D/C recording** button is **activated**, all entries are shown in a single table. You can select **D** (debit) or **C** (credit) for each line, and the account list includes all valid accounts. |
| **Cost center/ Partner/ Transaction type** | Allows selection of a cost center/partner/transaction type from the respective drop-down lists |
| **Value columns** | Allows entering values that should be posted
Value columns are identified by the periods to which the postings should be made. |
| **Posting text** | Description for the posting |
Show only accounts with postings
### Historical Exchange Rate Translation
To activate historical exchange rate translation for a posting:
1. Select the cell with the posting value that you wish to define a historical exchange rate translation for.
2. Click the **Historical exchange rate translation** button above the table. A **Historical exchange rate translation** section is displayed under the table.
3. Activate the option **Activate historical exchange rate translation** **for the selected posting value**.
4. In the table, specify the desired exchange rate for each of the displayed currencies.
**Note:** For undefined exchange rates, the exchange rate **1.0** is fixed by default.
> **Note:** **Notes on historical exchange rate translations:**
>
> - The **Historical exchange rate translation** button is only displayed if at least one currency translation has been configured in a reporting entity or consolidation area. To configure currencies and currency translations in reporting entities or consolidation areas, see [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities.md) and [Creating And Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md).
> - Historical exchange rate translations can only be defined for accounts of type **Currency amount**.
> - When copying the posting document to another journal, the fixed exchange rates are retained, provided the same currency translations have been configured in the target journal.
> - When historical exchange rate translation is defined for a cell's posting value, a purple chat symbol appears to the left of the posting value in that cell.
---
---
title: "Creating Reporting Templates"
description: "In Lucanet, Excel reports are always generated based on a reporting template. Reporting templates are Excel files that contain tilde formula(s) with functions, statements, and parameters that define the content of the Excel report queried from Lucanet. Each dimension that is queried using a tilde formula in an Excel reporting template is displayed in the detail view of the reporting template in Lucanet and can be selected there for report generation."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/create-and-edit-reporting-templates
language: en
last_updated: 2026-05-01
---
# Creating Reporting Templates
## Overview
In Lucanet, Excel reports are always generated based on a reporting template.
Reporting templates are Excel files that contain tilde formula(s) with functions, statements, and parameters that define the content of the Excel report queried from Lucanet.
Each dimension that is queried using a tilde formula in an Excel reporting template is displayed in the detail view of the reporting template in Lucanet and can be selected there for report generation.
In this chapter you will learn how to create, replace, or download a reporting template.
To learn how to use tilde formulas within reporting templates, see [Working with Tilde Formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas.md).
> **Note:** Changes to the reporting template directly in Lucanet are currently not possible. This means the reporting template that you create for the report must already contain the required tilde formulas.
>
> If you want to update a reporting template that has already been created in Lucanet, you must [replace the file](#replace).
## Supported Excel Versions
**XLS, XLSX, and XLSM files** from the following Excel versions can be used as reporting templates:
- MS Excel 2016 to 2021 for Windows
- MS Excel 365 for Windows
- MS Excel 2021 for macOS
- MS Excel 365 for macOS
## Creating Reporting Templates
To create a reporting template:
1. Open the workspace in which you want to generate Excel reports.
2. Choose **Create | Lucanet.Excel-Reporting** from the context menu. The **Create Excel Reporting** dialog is displayed:
Creating Excel reporting template
3. Insert the desired Excel file via **Drag & Drop** or **browse** your file directory and upload the file.
4. If necessary, change the **name** of the reporting template.
5. Click **Save**.
> **Tip:** After creation, the **Template properties** and **Placeholders** tabs of the reporting template are populated with fields and information from the tilde formulas contained in the Excel file.
>
> the shows detail view of a reporting template with information already transferred from excel file using tilde formulas. icon
> Display of the reporting template with tilde formulas after creation
## Downloading Reporting Template
You can download a reporting template from Lucanet to, for example:
- Modify the content of the file, i.e., the tilde formulas it contains
- Use the file as a template for a new reporting template
- Send the file to someone
To do this, select the desired reporting template and click **Download reporting template** in the detail view. The file will be saved in your download directory.
## Replacing Reporting Template
To make a modified reporting template available as the basis for an Excel report, it must be updated in Lucanet, i.e., the outdated version of the file must be replaced.
To do this, select the desired reporting template and click **Replace Reporting** Template in the detail view. Then add the updated Excel file via drag and drop or browse your file directory and click **Save**.
---
---
title: "Currency Translation"
description: "The Currency translation workspace is used to create, edit and delete transaction currencies, display currencies, and exchange rate tables in Lucanet."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation
language: en
last_updated: 2026-05-30
---
# Currency Translation
## Overview
The **Currency translation** workspace is used to create, edit and delete [transaction currencies](https://support.lucanet.com/en/documentation/glossary.md#transaction-currency), [display currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md),and [exchange rate tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md) in Lucanet.
Every posting in Lucanet must contain information about the currency in which the posting is to be performed. To this end, any number of **transaction currencies** are created in the **Currency translation** workspace. When creating a reporting entity, one of the defined transaction currencies is defined as **default currency**. The default currency for reporting entities is then automatically set for every posting within that reporting entity. In currency translation, the values of an organization element can be viewed in the transaction currency or in previously defined **display currencies**.
## Elements of the Workspace
The **Currency translation** workspace contains the following elements:
#### [Transaction currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)
The transaction currency determines in what currency an amount is posted.
The following elements are always available in the **Transaction currencies** folder and cannot be deleted:
- **All transaction currencies:** The element **All transaction currencies** is used to calculate the total for all values independent of the transaction currency employed. The element **All transaction currencies** is used in the Lucanet CFO Solution Platform and in the CFP Add-in for Excel 365 when requesting values. No postings can be created for the element **All transaction currencies**.
- **Default transaction currency**: The element **Default transaction currency** is used as a reference to the default currency for a reporting entity.
#### [Display currencies](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)
The display currency determines the currency in which an amount is displayed. The following element is always available in the **Display currency** folder and cannot be deleted:
- **Default currency**: The **Default currency** element is used to query values and can be used in the Lucanet CFO Solution Platform and in the CFP Add-in for Excel 365.
#### [Exchange rate table](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-currency.md)
The exchange rates between currencies are defined in exchange rate tables. For currency translations, Lucanet allows **year-to-date exchange rates** to be stored in addition to **average exchange rates** and **closing exchange rates** for all exchange rate relationships (transaction currencies and display currencies). You can create any number of exchange rate tables in order to model variants of the same exchange rate connections with different exchange rates in Lucanet, for example.
---
---
title: "Dashboards"
description: "In the Dashboards workspace, you can use widgets to visualize any values of accounts or items clearly and individually."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard
language: en
last_updated: 2026-05-01
---
# Dashboards
In the **Dashboards** workspace, you can use widgets to visualize any values of accounts or items clearly and individually. Widgets can be placed in a grid on the dashboard.
Widgets can show performance over a given period and track that performance against another time period. To display a comparison between planned and actual values, or between different planning scenarios, for example, the performance between two data levels can be compared.
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
Video: https://player.vimeo.com/video/854918461?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
- [Displaying and Configuring Dashboards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/display-configure-dashboard.md)
- [Editing Dashboards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/edit-dashboard.md)
---
---
title: "Data Levels"
description: "The Data levels workspace is used to create, manage, and delete data levels."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels
language: en
last_updated: 2026-05-01
---
# Data Levels
## Overview
The **Data levels** workspace is used to create, manage, and delete data levels. In Lucanet, a distinction is made between the following two data level types in which the data is stored:
- Actual data level
- Planning data level
While there is exactly one actual data level, you can create up to 254 planning data levels in Lucanet. Planning data levels are always based on the actual data level starting at a certain point in time.
In this article, the configuration of the **actual data level** is described. Creating and configuring the **Planning data level** is explained in [Creating and Configuring Planning Data Levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/create-configure-planning-datalvls.md).
## Configuring the Actual Data Level
Edit the actual data level
To configure the actual data level:
1. In the tree view, click the name of the actual data level and then **Edit** at the top right.
2. If needed, change the **name** of the actual data level.
3. Click **Save**.
4. Click the pencil icon next to the period.
5. Select the new **start and end periods**.
6. Click **Save**.
---
---
title: "Debit/Credit Shifts in Consolidation Areas"
description: "The aim of the app Debit/credit shifts in consolidation areas is to automatically standardize the debit/credit presentation of financial values across the consolidated group by generating the necessary shift entries to ensure each balance appears on a single side in the consolidated financial statements.\n\nThe Debit/credit shifts in consolidation areas are calculated based on the values of an adjustment level group and posted to an adjustment level for consolidation postings that is included in this adjustment level group. Optionally, it is possible to define whether individual consolidation areas should be excluded from execution."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/debit-credit-shifts-in-consolidation-areas
language: en
last_updated: 2026-05-01
---
# Debit/Credit Shifts in Consolidation Areas
## Overview
The aim of the app **Debit/credit shifts in consolidation** **areas** is to automatically standardize the debit/credit presentation of financial values across the consolidated group by generating the necessary shift entries to ensure each balance appears on a single side in the consolidated financial statements.
The **debit/credit shifts in consolidation areas** are calculated based on the values of an adjustment level group and posted to an adjustment level for consolidation postings that is included in this adjustment level group. Optionally, it is possible to define whether individual consolidation areas should be excluded from execution.
## Configuring Debit/Credit Shifts in Consolidation Areas
To configure the app for **debit/credit shifts in consolidation areas**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the general settings for the configuration:
Debit/Credit shifts
The following options are available:
| Option | Description |
|---|---|
| Consolidation includes debit/credit shifts | Choose whether the consolidation should include only debit/credit shifts that are **configured on items**, only those **configured on accounts**, or both.
**Note:** If you activate the checkbox **Configured on accounts**, the app will compare the balances of the debit/credit shift accounts with the balances of the debit/credit shift items configured in the [account properties](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-accounts.md) of the debit/credit shift accounts on the **Debit/credit shift** tab. Activate both checkboxes if you want to take into account debit/credit shifts configured at the account level as well as those configured at the item level during the consolidation. |
| Consolidation areas | The consolidation areas that are to be included in the app execution. **By default, all** consolidation areas of the group are included. Choose **Individual selection** and click **Add rows** to choose individual consolidation areas in the table that is subsequently displayed. - **Include**: In the table, select individual consolidation areas to be included. - **Exclude**: In the table, select the consolidation areas that are to be excluded. |
### Adjustment levels
In the **Adjustment levels** step, specify the adjustment levels that should be taken into account when performing the debit/credit shifts.
> **Note:** The app also carries out postings at adjustment levels that are locked for other postings.
Tab 'App configuration'
The following options are available:
| Option | Description |
|---|---|
| Consolidated | Adjustment level group including all adjustment levels for data imports, proportioning, and consolidation postings. Please ensure that the target adjustment level is included in this adjustment level group. This will be the basis for the consolidation of debit/credit shifts. |
| Target | Adjustment level for consolidation postings to be used for the debit/credit shift consolidation postings. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Debit/Credit Shifts in Consolidation Areas
You can execute the app for the **Debit/credit shifts in consolidation areas** either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created. When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md).
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Defining a Data Source"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh
language: en
last_updated: 2026-09-11
---
# Defining a Data Source
## Overview
In the **data source**, it is indirectly determined from which source system data are to be applied by specifying scripts. This is also where all transformation rules to be applied to the source data and the data for the Lucanet databases (temporary database for imports and Lucanet.Financial Warehouse) are specified.
## Creating a Data Source
To create a data source for importing data into Lucanet.Financial Warehouse:
1. Open the **Importing data into Lucanet.Financial Warehouse** workspace in the **Import and Journals** folder.
2. Right-click **Data sources** and choose **Create | Data source** from the context menu in the tree view of the workspace.
Creating a new data source
3. The **Create data source** dialog is displayed.
4. Specify the name of the data source in the **Element name** field.
5. Click **Save** or press **Enter** to create the data source.
6. In the detail view of the new data source, click **Edit**.
Open the editing mode of a data source
7. Then configure the data source (see **Configuring a Data Source**).
## Configuring a Data Source
### 'Configuration' Tab
The following options must be specified on the **Configuration** tab:
| Option | Description |
|---|---|
| **Add a script** | **Script**: Scripts that are executed during the import to Lucanet.Financial Warehouse
All scripts from the **Scripts** workspace are available. |
| **Application** | Location where the script is to be executed.
**Note:** If you have set up and are using **SEA**, you must choose the created **application** (see [Creating SEA Applications on the CFO Solution Platform](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md#creating-sea-applications-in-the-cfo-solution-platform)) in the **Application** drop-down list.
**SEA** (Lucanet Script Execution Application) is a Lucanet application that is required when ERP/financial source systems are operated on-premises and data from these systems needs to be imported into the Lucanet CFO Solution Platform via script. |
| **Add data transformation** | Data transformations that are executed during the import to Lucanet.Financial Warehouse. All data transformations from the **Data transformation** folder are available (see [Creating Data Transformations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-data-transformation.md)). |
### 'Database' Tab
You must configure one database connection for the **temporary** Lucanet.Financial Warehouse and one for the **persistent** Lucanet.Financial Warehouse when importing data into Lucanet.Financial Warehouse.
The following options must be specified on the **Database** tab for both the temporary and persistent Lucanet.Financial Warehouse:
| Option | Description |
|---|---|
| **Database** | The desired database system |
| **Database parameters** | Configuration of the required database parameters and the access data of the technical user ( **User** and **Password**)
The parameters to be specified depend on the chosen database.
**Note:** In the section [Configuring Database Connections](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh/datenbankverbindungen-konfigurieren.md), you can find a table with the default parameters that must be specified, depending on the selected database. |
| **Test connection** | Test whether a connection can be established with the configured database. |
| **Analyze database** | Run read-only SQL queries against the configured database, for example to verify that data was imported correctly.
For more information, see [Analyzing Databases](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database.md). |
| **Create tables** | Used to create all necessary tables in Lucanet.Financial Warehouse and in the temporary database for new imports.
If the tables already exist, they and their content are deleted by this action. |
| **Save** | Saves the current settings |
### 'Uses' Tab
The elements that use the data source are displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column.
'Uses' tab
---
---
title: "Defining a Data Source"
description: "To import data from various sources into the current Lucanet database, a data source must first be created."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source
language: en
last_updated: 2026-05-01
---
# Defining the Data Source for the Import
## Overview
To import data from various sources into the current Lucanet database, a data source must first be created. Depending on the origin of the data, different data source types are available.
## Creating a Data Source
To create a data source:
1. Open the **Importing data into reporting entities** workspace in the **Import and Journals** folder.
2. Right-click **Data sources** and choose **Create | Data source** from the context menu in the tree view of the workspace.
Creating a new data source
3. The **Create data source** dialog is displayed:
Dialog 'Create Data Source'
4. Choose the desired data source type from the **Origin of the data** drop-down list (see [Available Data Source Types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/.md#types)).
5. Specify the name of the data source in the **Element name** field.
6. Click **Save** or press **Enter** to create the data source.
7. The detail view of the data source is displayed. Configure the data source according to the selected type:
- [MS Excel file (.xls, .xlsx) (#1000)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-excel.md)
- [Provision via script (#2075)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-script.md)
- [Lucanet.Financial Warehouse (#2068)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md)
## Available Data Source Types
Data sources for Lucanet can be created in the **Data Sources** root folder. Depending on the origin of the data, different data source types are available. The configuration options vary depending on the selected type.
The following data source types are available:
| Data source | Description |
|---------|---------|
| MS Excel file (.xls, .xlsx) (#1000) | Used for importing data from Excel files (e.g. Excel reporting packages) |
| Provision via script (#2075) | Used to import data via a script |
| Lucanet.Financial Warehouse (#2068) | Used to import data from Lucanet.Financial Warehouse |
---
---
title: "Defining Properties of Return Values"
description: "The properties of return values can be specified using texts and parameters. The return values for the Value and Rate functions can be changed with any desired formula."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/define-properties-of-return-values
language: en
last_updated: 2026-05-01
---
# Defining Properties of Return Values
## Overview
Placeholders and functions can be extended with text and parameters to control the display of their return values. The extension is made with an arrow (->).
The return values for the **Value** and **Exchange rate** functions can be changed using any formula.
## Return Values for Placeholders
Placeholders in tilde formulas can be assigned a text and parameters for the properties of the return values.
To define the properties of the return value of a placeholder, an arrow ( -> ) is added to the tilde formula followed by a text and/or a parameter.
### Structure of the Tilde Formula with Placeholders
The tilde formula must be structured as follows:
**~Placeholder->"Text %short/%long"**
It is possible to attach any desired text to a placeholder. The entered text is retained when the report is generated.
> **Note:** The return values of the placeholders for **periods** and **data levels** can be specified with additional parameters A detailed description will be available shortly.
### Keywords in Tilde Formulas with Placeholders
The keywords **%short** and **%long** specify the return value of a placeholder as **name** or as **full name** for **data level**, **adjustment level**, and **organization element**.
> **Note:** You can only export the full name if an attribute exists in Lucanet with the **long_name** key and it is used in the **Data level, Adjustment level**, and **Organization elements** dimensions.
### Example for Tilde Formulas with Placeholders
The Excel worksheet contains two tilde formulas with placeholders for an organization element:
Placeholders extended to include %short and %long
The placeholders are replaced based on the tilde formulas:
Result with name and complete name
## Return Values for Data Levels
The return values of the placeholders for **data levels** can be specified with additional parameters:
You can use the **Period** parameters to dynamically assign a heading to the columns of a time series. When the **Period** parameter is used in the tilde formula for data levels, the return value of the placeholder **%short** and **%long** depends on the selected period.
**Structure of the Tilde Formula with Placeholder 'Data level' and Parameter 'Period'**
The tilde formula must be structured as follows:
~Data level->"_text:%short/%long_";period
**Return Values of the Actual Data Level**
Specifying a period for actual data levels gives the following return values:
- If the period lies completely within the actual data level, the return value is **Actual**.
- If the period lies partially outside the actual data level, the return value is **Partly outside of Actual**.
- If the period lies outside the actual data level, the return value is **Outside of Actual**.
**Return Values for Planning Data Levels**
Specifying a period for plan data levels returns the following values:
- If the period lies completely within the plan data level, the return value is **Planning**.
- If the period lies before the plan data level and completely within the actual data level, the return value is **Actual**.
- If the period lies completely within both the actual and plan data levels and intersects both, the return value is **Actual/forecast**.
- If the period lies partially outside the plan data level, the return value is **Partly outside of Planning**.
- If the period lies outside the plan data level, the return value is **Outside of Planning**.
**Example: Return Value Depending on the Period**
The Excel worksheet contains three placeholders for data levels that are specified before generation of the Excel report in Lucanet. **~quarter** is used as a placeholder for the period:
Period in tilde formulas for data levels
The first quarter of 2018 is selected as the period:
Selection during report generation
In the Excel worksheet, the data levels are displayed as follows:
Result with period Q1 2018
The actual data level comprises all of 2018. Therefore, the period **Q1.2018** falls completely within the actual data level and **Actual** is the return value issued.
The period **Q1.2018** falls completely outside **Planning DataLevel.Plan1**, as this only covers the time interval until the end of the year 2017.
**Planning data level.Plan2** only covers the time interval up to February 2018. The return value shows that the period falls **partly outside the planning data level**.
**Planning DataLevel.Plan2** delivers a changed result if you choose the fourth quarter of 2017 as the period:
Result with period Q4.2017
The **Q4.2017** period is completely within **planning data level.plan1** and within **planning data level.plan2**.
## Return Values for Periods
The return value for periods can be influenced using the help of parameters. The case of the parameter defines whether the first or last month of the time interval is displayed in MS Excel.
Unlike for all other parameters, a distinction is made between upper case and lower case.
**Structure of the Tilde Formula for a Period with Optional Parameter**
The tilde formula must be structured as follows:
**~Period->"_Text_ Parameter"**
**First Month in the Time Interval**
If the period is to refer to the first month of a time interval, the keyword for the parameter is written in **lower case**. The following keywords are available:
- **%d**: Returns the first day of the time interval (one-digit or two-digit)
- **%dd**: Returns the first day of the time interval (two-digit)
- **%m:**: Returns the first month of the period as one or two digit(s)
- **%mm**: Returns the first month of the period as two digits
- **%mmm**: Returns the abbreviation for the first month of the period range
- **%mmmm**: Returns the name of the first month of the period range
- **%yy**: Returns the year of the first month of the duration in two digits
- **%yyy**: Returns the year of the first month of the period range as four digits
- **%q**: Returns the quarter of the first month of the period range as Arabic numeral
- **%qq**: Returns the quarter of the first month of the period as a Roman numeral
**Last Month in the Time Interval**
If the period is to refer to the last month of a time interval, the keyword for the parameter is written in **upper case**. The following parameters are available:
- **%D**: Returns the last day of the time interval (one-digit or two-digit)
- **%DD**: Returns the last day of the time interval (two-digit)
- **%M**: Returns the last month of the period as one or two digits
- **%MM**: Returns the last month of the period range as two digits
- **%MMM**: Returns the abbreviation for the last month of the period range
- **%MMMM**: Returns the name of the last month of the period range
- **%YY**: Returns the year of the last month of the duration in two digits
- **%YYYY**: Returns the year of the last month of the period range as four digits
- **%Q**: Returns the quarter of the last month of the period as an Arabic numeral
- **%QQ**: Returns the quarter of the last month of the period range as Roman numeral
**Default Display for Periods**
If no parameter is specified, then periods are displayed as follows:
- Month: **Jan 2017**
- Quarter: **Q1.2017**
- Year: **2017**
If the time interval comprises several periods, the time period is displayed as follows:
- Several months: **Jan 2017-Feb 2017**
- Several quarters: **Q1.2017-Q2.2017**
- Several years: **2017-2018**
**Examples**
The Excel worksheet contains different tilde formulas for displaying the period:
Tilde formulas for returning various periods
These values are displayed in MS Excel when **August 2017** is displayed as the period:
Return of various periods
## Value of an Attribute
Tilde formulas with placeholders can be used to display the value of an [attribute](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) in MS Excel. The **attribute key** is used as a parameter for returning the attribute value.
**Structure of the Tilde Formula for Returning the Value of an Attribute**
The tilde formula must be structured as follows:
**~Placeholder->"_Text %short/%long_";Attribute key**
**Note**: Only attribute values of [attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/configuring-attributes.md) that can be selected as display language and that are used in the corresponding dimension can be read in to MS Excel.
**Example**
The **~data level** placeholder is used without an attribute and with the attribute keys **name_eng** and **long_name**:
Tilde formulas for returning attribute values
The generated report is displayed as follows:
Return of attribute values
> **Note:** When an attribute key is specified in the formula, the parameters **%long** or **%short** are not taken into account and are overwritten by the value of the attribute.
## Return Values for Functions
The return values for the **Value** and **Exchange rate** functions can be changed using any formula.
## Tilde Formula Structure
The tilde formula must be structured as follows:
**~Rate/~Value(Parameter_1 ... Parameter_n)->"1/x"**
The letter **x** represents the return value of the function, while **1/x** represents a possible formula.
## Example
The Value function in row 2 returns the unchanged value.
In row 4, the return value is changed with **x/1000**:
Property for function 'Value'
The generated report appears as follows:
Property of the value in an Excel report
---
---
title: "Defining the Group Structure"
description: "A group includes the totality of all units to be consolidated.\nThe group structure is defined using consolidation dimension and consolidation dimension elements and consolidation areas."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure
language: en
last_updated: 2026-05-01
---
# Defining the Group Structure
## Overview
A group includes the **totality of all units** to be consolidated.
The **group structure** is defined using the following **consolidation components**:
**Consolidation dimension and consolidation dimension elements**
- The [consolidation dimension](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-dimensions-and-elements-conso-2.md) acts as an important link: It connects your existing [organization elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md) with the [consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md). Organization elements represent, e.g., **companies**, **business units**, **segments** or **cost centers**.
- The **consolidation dimension** defines whether the consolidation is to take place by companies, by business units or according to another scheme.
- All similar consolidation dimension elements are summarized in a consolidation dimension.
- During configuration, consolidation dimension elements can be linked to the organization elements of the single-entity financial statements by a unique reference. For the consolidation, the consolidation dimension elements adopt the data from the organization elements.
**Consolidation areas**
- The [consolidation area](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure/consolidation-areas-and-units-conso-2.md) defines a group or sub-group. The default consolidation unit of this consolidation area prepares consolidated financial statements for all consolidation units included - regardless of whether this is prepared for internal reporting purposes or due to legal regulations.
- Consolidation is executed within these consolidation areas.
- A consolidation unit is defined as a consolidation dimension element within a specific consolidation area (values from the referenced organization elements are transferred to the consolidation areas with the app for [Data transfer and proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md).
- A single consolidation dimension element (e.g., a company) can be included in multiple consolidation areas.
> **Tip:** In a **legal consolidation**, the consolidation dimension **Legal consolidation** contains **all legal units** (companies) as consolidation dimension elements.
>
> During a **consolidation of segments**, the consolidation dimension **Segments** contains **all business units** as consolidation dimension elements.
## Creating a Group
Do one of the following to create a group in the **Groups** workspace:
- Select the **Groups** root folder and choose **Create | Group** from the context menu.
Creating a group via the context menu
- Click **Create group** in the detail view of the workspace.
Creating a group from detail view
Enter a **name** for the element and click **Save**.
The group is created, and the following non-deletable subfolders are created automatically:
- **Consolidation dimensions** with the predefined consolidation dimension for **Legal consolidation**
- **Consolidation areas**
Group created
## Deleting or Editing a Group
To delete a group, right-click the desired element and select **Delete** from the context menu.
If you want to edit the **name** of a group, click **Edit** in the detail view of the element.
Edit group
---
---
title: "Dependent Business Transactions"
description: "If accounts or items are planned on the basis of additional planning dimensions, then the business transactions that are dependent on them must be recalculated when these planning dimensions are changed."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets/dependent-business-transactions
language: en
last_updated: 2026-05-01
---
# Dependent Business Transactions
## Overview
If accounts or items are planned on the basis of additional planning dimensions, then the business transactions that are dependent on them must be recalculated when these planning dimensions are changed.
In Lucanet, a function can be activated that ensures the **automatic recalculation of dependent business transactions**. Alternatively, the recalculation of dependent business transactions can be initiated **manually**.
## Recalculation of All Business Transactions
To recalculate all business transactions:
Click **Dependent business transactions** in the menu bar. A context menu with the following options opens:
Menu options under 'Dependent business transactions'
Select one of the options:
- Select **Recalculate dependent business transactions** **automatically** to automatically recalculate transactions if their basis changes, considering the number of iterations set in the system.
- Select **Recalculate now** to initiate the recalculation of all dependent business transactions.
- Select **Configure iterations** to set or modify the number of recalculation iterations.
'Configure Iterations' dialog
## Recalculation of a Single Business Transaction
Business transactions with an obsolete calculation basis are indicated by the icon .
To recalculate a single business transaction, right-click an indicated business transaction and choose **Recalculate business transaction** from the context menu:
### Circular References
In some cases, a **circular reference** can appear between business transactions.
A circular reference can, for example, arise between the **Current account interest** planning wizard and the **Tax calculation** planning form. They cannot be dissolved by Lucanet. The following example shows a circular reference:
#### Tax calculation
- The tax calculation is based on the **Earnings before income taxes** total line in the P&L.
- The tax calculation planning form generates a posting on the bank account.
#### Current account interest
- The interest expense or income from the Current account interest wizard is posted to an account which is included in the **Earnings before income taxes** total line.
- The **Earnings before income taxes** total line is used as basis for the **Tax calculation** planning form, thus creating a circular reference.
### Resolving Circular References
To resolve a circular reference, you can do one of the following:
- Change the account used for **Taxes** so it is not included in the basis of calculation of the **Current account interest** wizard,
- Change the calculation basis for the **Current account interest** wizard,
- Or increase the number of **iterations** that can be applied to dependent business transactions before a circular reference is detected.
> **Note:** An iteration is a recalculation loop that continues until all values stabilize and no longer change between cycles (after the second decimal). If values don’t stabilize after the allowed iterations, the system triggers a circular reference error.
---
---
title: "Dimensions"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions
language: en
last_updated: 2026-05-01
---
## Dimensions
In the **Dimensions** workspace, the Lucanet dimensions can be administrated and modified in accordance with the specific user. The following dimensions are available:
- [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md)
- [Organization elements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements.md)
- [Currency translation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation.md)
- [Partners](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners.md)
- [Data levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels.md)
- [Adjustment levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/adjustment-levels.md)
- [Transaction types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types.md)
- [Fiscal years](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/fiscal-years.md)
Arbeitsbereich 'Dimensionen'
---
---
title: "Display in Ledgers and Schedules"
description: "The display in schedules and mirrors can be configured with various functions."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules
language: en
last_updated: 2026-05-01
---
# Display in Ledgers and Schedules
## Overview
The display in ledgers and schedules can be configured with the following functions:
- [Changing the Display](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/change-view.md)
- [Configuring Display Settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md)
- [Formatting Numbers and Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/format-numbers-dates.md)
- [Configuring the Dimension Bar](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-dimension-bar.md)
---
---
title: "Displaying and Configuring Charts"
description: "Values of items and accounts from ledgers and schedules can be visualized in Charts as column, bar, pie or line charts. To visualize comparisons, the values of multiple items or accounts can be displayed in a chart at the same time."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/display-configure-diagrams
language: en
last_updated: 2026-05-01
---
# Displaying and Configuring Charts
## Overview
Values of [items](https://support.lucanet.com/en/documentation/glossary.md#item) and [accounts](https://support.lucanet.com/en/documentation/glossary.md#account) from [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger) and [schedules](https://support.lucanet.com/en/documentation/glossary.md#schedule) can be visualized in **Charts** as column, bar, pie or line charts. To visualize comparisons, the values of multiple items or accounts can be displayed in a chart at the same time.
Alternatively, you can find the information in the following video:
Video: https://player.vimeo.com/video/852368020?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
## Opening Chart
Charts can be opened from the context menu for items and accounts in the side panel or as a pop-up window:
Opening a chart via the context menu
For comparisons, several items or accounts can be included in a chart at the same time. To display two or more accounts or items in a chart, you must select these accounts or items while holding down the **CTRL** button:
Opening a chart for two items
The chart is then displayed as follows:
Displaying fixed assets and current assets as a chart
## Configuring Charts
The toolbar of a chart is displayed as follows, for example:
Toolbar of a chart
The following options are available in the toolbar of a chart:
| Option | Description |
|---|---|
| **Display/hide values** | Shows or hides the values of bars, columns, pie segments, or lines |
| **Drop-down list** | Changes the position of the chart |
| **Print (print icon)** | Opens the operating system's print dialog from where the chart can be printed |
| **Download (download icon)** | Downloads the chart in PNG format |
| **More options (three dots icon)** | The following additional options are available per chart: - **Settings** — Choice of chart type (e.g. column, bar, pie, line) - **Data** — Show or hide data for an item or account from the chart - **Format** — Chart type-specific settings for the chart layout. For example, in a bar chart the following elements can be configured: Title, Padding, Background, Labels, Shadow, Navigator |
---
---
title: "Displaying and Configuring Dashboards"
description: "In the Dashboards workspace, the dashboard is displayed and edited. The dimension bar can be used to configure the value display in the widgets."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/display-configure-dashboard
language: en
last_updated: 2026-06-03
---
# Displaying and Configuring Dashboards
## Overview
In the **Dashboards** workspace, the dashboard is displayed and edited. The **dimension bar** can be used to configure the value display in the widgets.
## Creating a Dashboard
By default, there is one dashboard in the Lucanet CFO Solution Platform. In Lucanet.Financial Client, you can create additional dashboards under **Administration | Workspaces** to then use these dashboards in the Lucanet CFO Solution Platform.
> **Tip:** More information on this can be found in the Lucanet online help under: **Complete description | Administration | Administration at database level | Workspaces | Elements | Creating and configuring dashboards**.
## Displaying Dashboards
Dashboards are displayed in the **Consolidation & FInancial Planning** menu in the **Dashboards** workspace:
'Dashboards' workspace in the overview
A dashboard is displayed as follows, for example:
Dashboard with all widgets
## Configuring Dashboards
In the **dimension bar**, you can configure the dimensions for displaying the values in the dashboard widgets. Changes to dimensions affect all **widgets** in the dashboard.
Dimension bar of the 'Dashboards' workspace
The **Time period** and **Data level** dimensions are available in two variants in the dimension bar for dashboards and can be used to display comparisons (deltas).
- **Time period (base)**: Period for which values are displayed in the widgets and, if applicable, base period for displaying comparisons (deltas).
- **Time period (delta)**: To track the performance of a particular account or item in a given period compared to the **Time period (base)**, it is possible to specify a positive or negative offset in months under **Time period (delta)**. When a delta is specified, the **Offset** prefix is displayed in widgets that are configured to display a delta (see [Editing Dashboards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/edit-dashboard.md)):
Widget with a comparison of time periods
- **Data level (base)**: Data level for which values are displayed in the widgets and, if applicable, base data level for displaying comparisons (deltas).
- **Data level (delta)**: To display a comparison between planned and actual values, or between different planning scenarios, for example, you can use **Data level (delta)** to choose the level to be compared with the **Data level (base)**. In widgets configured to display a delta (see [Editing Dashboards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/edit-dashboard.md)), the delta is displayed as follows:
Widget with a comparison of data levels
All other dimensions match the dimensions that can be configured by default in dimension bars.
## Go to Workspace
If you click the icon at the top right of the widget, the workspace containing the element selected for the widget will be displayed in a new browser tab. The item or account displayed in the widget is highlighted.
'Go to workspace' option on a widget
---
---
title: "Displaying the Change Log"
description: "The change history of an element is displayed in its Change Log. It shows what changed, when, and whether a user or the system did it, covering new entries, updates, and moves."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log
language: en
last_updated: 2026-06-01
---
# Displaying the Change Log
## Overview
The change history of an element is displayed in its **Change log**.
The change log displays what changed, when, and whether a user or the system made the change, covering new entries, updates, and moves.
You can open the change log from each workspace and it lists:
- The element
- Its unique identifier
- Its parent when relevant
- The action performed on the element
- Depending on the workspace, additional columns
Change log entries for **manual** and **Excel Add-in postings** additionally offer a version link that opens the previous version in a new window, so you can compare what changed without leaving your audit trail.
For **Apps**, **Scripts**, **Data Imports**, and **Execution settings**, the change log additionally offers an **Execution log** tab, which lets you open detailed information on each execution and a process log generated for each run. For details, see [Viewing the Execution Log and Process Logs](#viewing-the-execution-log-and-process-logs) below.
## Tracked Elements
In the change log, create, update, and move actions are tracked for the following elements:
| Category | Tracked elements |
|---|---|
| Reporting and analyzing | Folder Item Account Reference Formula Total line |
| Journals | Folder Posting Data import Posting (Excel-Add-In) Posting (App) Posting (Script) Translation with historical exchange rates Current account interest wizard Loan wizard Transfer actual balance to plan wizard Sheets Elimination of intercompany debt Elimination of intercompany income and expense Inventory consolidation |
| Reporting entities | Folder Reporting entity Consolidation reporting entity Cost center Cost center group Total line |
| Organization elements | Folder Organization group (including automatic) Reference to reporting entity Reference to consolidation reporting entity Reference to cost center Reference to cost center group Reference to consolidation area Reference to consolidation unit Reference to consolidation unit group Residual amount Reference to total line Total line (including automatic) |
| Adjustment levels | Folder Adjustment level Adjustment level for consolidation postings Adjustment level group |
| Transaction types | Transaction type category Transaction type group Transaction type |
| Currency translation | Folder Transaction currency Display currency Exchange rate table |
| Workspace configuration | Folder General ledger Subledger Statistical ledger Schedule Directory structure |
| Attributes | Folder Attribute |
| Scripts | Executable folder Script |
| Importing data into Lucanet.Financial Warehouse | Folder Data source Data transformation Executable folder Execution settings |
| Importing data into reporting entities | Folder Executable folder Data import Data source Assignment table |
| Directory structure | Executable folder Script App (Next Generation) Connection Lucanet.Excel-Reporting Workflow |
| Accounting rules | Folder accounting rule configuration Item accounting rule configuration Account accounting rule configuration VAT configuration |
| Consolidation areas | Folder Consolidation area Elimination of intercompany debt Elimination of intercompany income and expense Inventory consolidation |
| Consolidated financial statements | Master data administration Folder (user-created, executable) Reports folder (auto-created) App (Next Generation) Report Consolidated financial statements |
| Groups | Root folder Group Folder (user-created) Consolidation dimensions folder (auto-created) Consolidation dimension Consolidation dimension element Consolidation areas folder (auto-created) Consolidation area Consolidation unit Consolidation unit group Total line |
| Period locks | Folder Audit trails - posting Audit trails - exchange rates |
| Partners | Folder Partner group Partner |
| Data levels | Folder Actual data level Planning data level |
## Opening the Change Log
The way to open the **change log** depends on the element type for which you want to open it.
## Opening the Change Log for an Item or an Account
To open the change log for an item or an account:
1. Right-click the item or account you want to open the change log for and choose **Properties** from the context menu.
2. In the **Account Properties** dialog, click the **change log** icon.
Dialog 'Account Properties'
3. The change log of the account or item is displayed as follows, for example:
Change log of an account
## Opening the Change Log for All Other Elements
To open the change log for all elements other than an item or an account:
1. In the tree view, navigate to the element you want to open the change log for.
2. At the top right of the detail view, click the purple **Change Log** icon.
Change Log icon
3. The **Change Log** dialog is displayed as follows, for example:
Change Log overview
## Comparing a Version of a Posting in its Change Log
If a manual posting or an Excel posting was changed, the change log of the posting allows you to compare the current version with the previous one. To do so, simply click the **Predecessor** link shown in the **Version** column of the change log:
Link 'Predecessor'
> **Note:** **If Version or Predecessor is missing:**
>
> - Note that the change log can still list changes without a **Version** column or without links — do not assume every change includes a viewable previous version.
> - Use the other columns (**Date and time**, **User**, **Action**, **Parent**) when no **Predecessor** link is available.
## Viewing the Execution Log and Process Logs
For executable elements, i.e. **Apps**, **Scripts**, **Data Imports**, and **Execution settings**, the change log includes the **Execution log** tab. Open this tab to find out when an element was last executed, whether the run succeeded, and to open the detailed **process log** generated for that run listing all the steps of the process.
> **Note:** The **Execution log** tab is available for:
>
> - Apps and scripts in a **directory structure** and the **Scripts** workspace
> - Data imports in the **Importing data into reporting entities** workspace
> - Execution settings in the **Importing data into Lucanet.Financial Warehouse** workspace
> - Apps in **Consolidated financial statements**
>
> It is not available for folders, workflows, or drilldown scripts, or when a grouping element (such as a folder, Consolidated financial statement element, or workflow) is executed — in that case, open the execution log of the individual executed element instead.
### Opening the Execution Log
To open the execution history of an executable element:
1. In the tree view, navigate to the element you want to open the execution log for.
2. At the top right of the detail view, click the purple **Change Log** icon.
Change Log icon
3. Click the **Execution log** tab.
The **Execution log** is displayed as follows, for example:
Execution log
4. The execution log lists every run of the element within the retention period:
| Column | Description |
|---|---|
| Date/Time | When the execution was performed |
| User | Who started the execution |
| Status | The outcome of the execution: **Success** or **Failed** |
| Process Log | A **View log** link that opens the detailed process log for that run |
You can sort, filter, and, if there are more records than fit on one page, page through the list, just as in the **Change log** tab.
> **Note:** The execution log only shows runs from the last 30 days. Runs older than that are automatically removed from the execution log, but remain visible as an **Executed** entry on the **Change log** tab for as long as your contract's retention period applies — just without a process log to open.
### Opening a Process Log
To open a process log for an execution, in the **Execution log** tab, click **View log** in the row of the run you want to inspect.
Process log
The process log opens in a new window, showing the individual steps of the run as an expandable tree.
Process log with default columns
By default, the following columns are shown:
| Column | Description |
|---|---|
| Description | The name of the step, indented to show its position in the run's hierarchy |
| Time | The timestamp of the step |
| Total Duration | The cumulative duration of the step, including any sub-steps |
| Progress | The step's progress, for example a percentage or a status such as running, completed, or failed. Not all steps report progress. |
Activate **Show debug messages** to display two more columns with additional technical detail:
| Column | Description |
|---|---|
| Duration of Execution | The time taken by this step alone, excluding any sub-steps |
| Details | Additional technical information, debug messages, or error details for the step |
#### Downloading a Process Log
To keep a copy of a process log, for example to share it with support, you can download the log as a text file (.txt) or an Excel file (.xlsx).
The file is saved with a name in the format `process_log_export_yyyy_mm_dd`, to the location configured in your browser's download settings.
---
---
title: "Drill Down in Ledgers and Schedules"
description: "For items and accounts, drill down can be used to define how subordinate items or postings are displayed."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drill-down
language: en
last_updated: 2026-05-01
---
# Drill Down in Ledgers and Schedules
## Overview
For [items](https://support.lucanet.com/en/documentation/glossary.md#item) and [accounts](https://support.lucanet.com/en/documentation/glossary.md#account), a **drill down** can be used to define how subordinate items or postings are displayed.
## Executing a Drill Down
To execute a drill down for an item or account:
1. Right-click the desired item or account and choose **Drill down** from the context menu.
2. Choose the desired drill down.
Context menu for the drill down for an item
Result of the drill down for an item by partners
## Drill Downs for Accounts and Items
Depending on the element, the following drill downs are available:
| Drill Down | Description | Availability |
|---|---|---|
| By items | Default drill down for **items**. All sub-items are displayed. | Items only |
| By organization elements | Default drill down for **accounts**. The display depends on which organization element is selected in the dimension bar. | Accounts only |
| By adjustment levels | The drill down by adjustment levels is displayed. | Only if an adjustment level group is selected in the dimension bar |
| By partners | Displays all partners for which postings have been made under the item. | Only if at least one user-defined partner has been defined |
> **Warning:** The **drill down by partners** is only available if at least one user-defined partner has been defined.
> **Note:** When drilling down by partner, adjustment level or organization element, the default elements, such as the default cost center, are checked as displayed below: the default element icon.
---
---
title: "Drilling Down to Original Posting Level"
description: "For a posting with a DMS code, you can open the corresponding original document directly from the Show Postings dialog in your Document Management System."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level
language: en
last_updated: 2026-07-15
---
# Drilling Down to Original Posting Level
## Overview
If your organization uses a Document Management System (DMS) to store source documents such as invoices or receipts, you can open the original document for a posting directly from its posting data, without leaving Lucanet Consolidation & Financial Planning.
> **Note:** Drilling down to the original document is currently supported for cloud- and web-based Document Management Systems, including SharePoint.
>
> Drill-down to on-premise Document Management Systems is not yet supported.
## Prerequisites
Drilling down to the original document is only available for a posting if it was imported through a data source with a DMS script assigned in the **Display scanned documents** field **and** it has a **DMS code** populated during import (see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).
> **Note:** Configuring the DMS script and connecting it to your Document Management System is done by an administrator in the **Scripts** workspace (see [Creating and Executing Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)). Contact your Lucanet consultant if this has not yet been set up for your organization.
## Opening the Original Document
To open the original document for a posting:
1. In a ledger or schedule, double-click the desired account value to open the **Show Postings** dialog (see [Show Postings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/postings.md)).
2. In the value column, click the link of the value for which you want to view the posting data.
Link of a value to open its posting details
3. In the **Drill down to posting level** dialog, select the value for which you want to display the original document and click the link behind **Posting**.
The Posting link in the 'Details on selected posting' section
**Note:** Posting is only displayed as a link if the prerequisites listed above are fulfilled. Otherwise, the posting is displayed as plain text.
4. In the **Show Source Document** dialog, select the desired execution location for the script configured in the [data source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md) for displaying scanned documents. The drop-down list is pre-filled with the default configured for the data source.
**Note:** For scripts that require execution on the local machine, you need to select your on-premise [Script Execution Application (SEA)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md) instance.
Show Source Document dialog
5. Click **Open**.
The original document opens in a new browser tab.
## Troubleshooting
If the original document cannot be opened, an error message is displayed, for example:
| Message | Cause |
|---|---|
| System cannot find the file specified | The document could not be located in the document management system, for example because the DMS code does not match a document, or you do not have access to the file. |
| Other error messages | Any other error returned while the DMS script was executed. |
If the error persists, contact your administrator to check the configuration of the DMS script.
---
---
title: "Editing Dashboards"
description: "In the dashboard, you can add new widgets and edit or delete existing ones. You can also lock dimensions to prevent incorrect dashboard configurations."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/edit-dashboard
language: en
last_updated: 2026-05-01
---
# Editing Dashboards
## Overview
In the dashboard, you can add new widgets and edit or delete existing ones. You can also lock dimensions to prevent incorrect dashboard configurations.
## Activating Editing Mode
To edit the dashboard, you must first put it in editing mode. At the top right of the dimension bar, right-click **Edit**.
Button for editing a dashboard
The following functions are available in the dashboard:
### Locking or Unlocking Dimensions
You can lock dimensions to prevent unintentional display of incorrect values in the widgets.
To lock dimensions:
- To lock specific dimensions, click the lock open icon to the right of a dimension.
- To lock all dimensions, click the three dots icon and choose **Lock all**.
To unlock dimensions:
- To unlock specific dimensions, click the lock closed icon to the right of a dimension.
- To lock all dimensions, click the three dots icon and choose **Lock all**.
Dimension bar with functions for locking or unlocking dimensions
### Adding Widget
To add a widget:
At the bottom right, click **\+ Add widget**.
Button for adding a widget
The following options are available in the **Create widget** dialog:
'Create widget' dialog
| Option | Description |
|---|---|
| **Widget type** | Type of widget |
| **Element** | Element to be displayed in the widget |
| **Select deltas** | Optionally, delta values can be displayed in the widget. The following options are available: - **Time period** — Enables the comparison of two time periods. The delta values are displayed in the widget based on the Time period (base) dimension and the Time period (delta) configured in the dimension bar. - **Data level** — Enables the comparison of two data levels. The delta values are displayed in the widget based on the Data level (base) dimension and the Data level (delta) configured in the dimension bar.
You can find out more about configuring the dimension bar in [Displaying and Configuring Dashboards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/display-configure-dashboard.md). |
| **Number format** | Options for displaying and specifying decimal places of values in the widget |
### Editing or Deleting Widgets
You can edit or delete widgets in your dashboard at any time.
To edit or delete a widget:
1. Click **Edit** in the dimension bar of the dashboard.
2. Click the three dots icon on the widget and choose **Edit widget** or **Delete widget** from the context menu.
Widget with menu commands 'Edit widget' and 'Delete widget'
### Arranging Widgets
You can arrange widgets anywhere within the specified grid in the dashboard using drag and drop.
1. Left-click the widget that you want to move.
2. Hold down the left mouse button and move the widget to the desired position.
3. Release the mouse button.
Moving a widget
---
---
title: "Editing the Properties of the General Ledger"
description: "The general ledger is used to keep and display accounts and items in Lucanet. The account structure of a balance sheet is stored in the general ledger. In the general ledger, the original accounts from the financial accounting source systems are recreated, assigned, and maintained, and manually created accounts and items are managed.\n\nBy default, the general ledger is displayed as a workspace in the overview in the Reporting and analyzing folder.\n\nThe properties of the general ledger can be edited in the Workspace Configuration as described below."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/edit-general-ledger-details
language: en
last_updated: 2026-05-01
---
# Editing the Properties of the General Ledger
## Overview
The **general ledger** is used to keep and display accounts and items in Lucanet. The account structure of a balance sheet is stored in the general ledger. In the general ledger, the original accounts from the financial accounting source systems are recreated, assigned, and maintained, and manually created accounts and items are managed.
By default, the general ledger is displayed as a workspace in the overview in the **Reporting and analyzing** folder.
The properties of the general ledger can be edited in the **Workspace Configuration** as described below.
## Editing the Properties of the General Ledger
To edit the properties of the general ledger:
1. In the structure view of the **Workspace Configuration**, click the name of the general ledger.
2. Click **Edit** in the upper right corner to open the edit mode.
Edit mode of the general ledger
## Options
The following options are available for the general ledger:
### General properties
You can configure the following general properties for the general ledger:
| Option | Description |
|---------|---------|
| Element name | Name of the general ledger. If necessary, specify the country-specific language descriptions of the general ledger for the display languages available for the Lucanet user interface. |
| Abbreviation | Abbreviation of the general ledger |
| Abbreviation incl. subledgers | Abbreviation for the general ledger and all subledgers assigned to it. |
| Formatting options | If necessary, choose another icon from the drop-down list. |
### 'Elements' tab
On the **Elements** tab you can define which elements can be created in the ledger:
- To delete elements from the **Elements** list, click the delete icon next to the element you want to delete.
- To add elements to the **Elements** list, click **\+ Add row** and choose the desired element in the displayed drop-down list. The following elements are available:
- [Item](https://support.lucanet.com/en/documentation/glossary.md#item)
- [Account](https://support.lucanet.com/en/documentation/glossary.md#account)
- [Reference](https://support.lucanet.com/en/documentation/glossary.md#reference)
- [Total line](https://support.lucanet.com/en/documentation/glossary.md#total-line)
- [Formula](https://support.lucanet.com/en/documentation/glossary.md#formula)
- [Time series](https://support.lucanet.com/en/documentation/glossary.md#time-series)
- [Separator](https://support.lucanet.com/en/documentation/glossary.md#separator)
- Folders
- If references are permitted as elements: Activate the **Restrict the origin of references** check box if you only want to enable references to certain workspaces. Then, click **\+ Add** and select the workspaces for which references can be created.
> **Note:** If an object type is removed from the ledger's configuration, no further elements of this type can be created in the ledger. Elements previously created in the ledger with the removed object type are retained and can be edited, copied, moved, or deleted.
### 'Rounding errors' tab
Configure the following on the **Rounding errors** tab:
- **Account for presentation of the rounding error from proportionate consolidation**
- **Account for presentation of the rounding error from currency translation**
---
---
title: "Elements in Directory Structures"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures
language: en
last_updated: 2026-09-07
---
# Elements in Directory Structures
## Overview
In directory structures, elements such as apps, scripts, or connections can be grouped together in a structured manner.
A directory structure can be created under any workspace; which elements can be created in the respective directory structure depends on the configuration of the directory structure (see section [Creating and Configuring a Directory Structure](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md)).
In this chapter, you will learn which elements are available in directory structures, provided that they have been enabled in the configuration.
## Available Object Types
The following object types can be enabled in a directory structure.
| Object type | Description |
|---|---|
| Next-Generation App | Used to create an app as a functional extension of the Lucanet software. Currently, the following apps are available: - [Reclassification of profit or loss from previous periods in reporting entitites](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures/reclassification-of-profit-or-loss-in-reporting-entities.md) - [Adjust and reclassify values in reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures/adjust-and-reclassify-values-in-reporting-entities.md) |
| Connection | Used to create connections that contain connection information for SQL databases. The connected database can be queried directly (see [Analyzing Databases](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database.md)) |
| Script | Used to create scripts (see [Creating and Executing Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)) |
| Lucanet.Excel-Reporting | Used to create Excel reports within Lucanet.Excel-Reporting (see [Lucanet.Excel-Reporting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting.md)) |
| Folders | Used to create folders |
| Workflow | Used to create workflows to automatically execute executable elements such as scripts, or data imports in a fixed sequence (see [Executing Multiple Elements Using Workflows](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/executing-elements-using-workflows.md)) |
---
---
title: "Elements in Ledgers and Schedules"
description: "The structure of ledgers and schedules is displayed in the tree view. All structures are composed of the same elements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules
language: en
last_updated: 2026-05-01
---
# Elements in Ledgers and Schedules
## Overview
The structure of ledgers and schedules is displayed in the tree view. All structures are composed of the same elements.
## Elements
Ledgers and schedules are composed of the following elements:
| Element | Description |
|---------|---------|
| Item | In Lucanet, items are used for a better overview and better structuring of ledgers and schedules. The value at the item level is always the total of all sub-items or accounts (see section [Creating and Configuring Items](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-items.md)). |
| Account | All postings in Lucanet are made to accounts. Accounts are changed only by postings and therefore behave in the same way as in conventional financial accounting systems (see section [Creating and Configuring Accounts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-accounts.md)). |
| Reference | References are links to items or accounts in general ledgers, subledgers, or statistical ledgers. References can be used to create derived structures (e.g. a derived IFRS balance sheet) in Lucanet (see section [Creating and Configuring References](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-references.md)). |
| Formula | A formula is a calculated item. The formula used to calculate the value can be specified by the user. Each variable of the formula must refer to an item or account in the Lucanet database (see section [Creating and Configuring Formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-formulas.md)). |
| Total line | Total lines or subtotal lines are items whose values are based on the total of all items of the same level above the totals item (see section [Creating and Configuring Total Lines](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/create-configure-total-lines.md)). |
---
---
title: "Elimination of Income from Investments"
description: "The goal of the app for Elimination of income from investments is to automate the elimination of investment income recorded by the parent company against the subsidiary's dividend distributions or profit transfers in the same period.\n\nElimination can be executed per period or accumulated across several periods.\n\nNon-controlling interests can be considered. They are considered based on the ownership interests stored in the master data or based on individual specifications made on the app interface."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-income-from-investments
language: en
last_updated: 2026-05-01
---
# Elimination of Income from Investments
## Overview
The goal of the app for **Elimination of income from investments** is to automate the elimination of investment income recorded by the parent company against the subsidiary's dividend distributions or profit transfers in the same period.
Elimination can be executed per period or accumulated across several periods.
Non-controlling interests can be considered. They are considered based on the ownership interests stored in the [master data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md) or based on individual specifications made on the app interface.
## Configuring the Elimination of Income from Investments
To configure the app for the **Elimination of income from investments**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the general settings for the configuration:
'Settings' step
The following options are available on the **Settings** step:
| Option | Description |
|---|---|
| **Create postings** | Time of consolidation: - **Per month**: The app eliminates intercompany transactions in each month of the consolidation period and creates monthly elimination postings. - **Accumulated at the end of the period**: The app cumulatively eliminates intercompany transactions in the last month of the consolidation period and creates an accumulated elimination posting only in the last month of the consolidation period.
**Note:** For any consolidation unit deconsolidated in the consolidation period, an accumulated elimination will be performed in the last month of the consolidation unit's inclusion in the consolidation area. |
| **Elimination options** | - **Profit or loss transfers**: To eliminate profit or loss transfers between investment and investor in the same period. - **Distributions from retained earnings**: To eliminate distributions from retained earnings in income and equity. |
| **Consolidation area and/or unit** | The consolidation areas and/or units that the elimination is to be performed for. **By default all** consolidation areas and units of the group are included. If you only want to include certain consolidation areas and/or units, activate the **Individual selection** check box and select one of the following options: - **Include**: In the table, select individual consolidation areas and/or units to be considered. - **Exclude**: In the table, select the consolidation areas and/or units that are to be excluded. |
### Adjustment levels
In the **Adjustment levels** step, specify the adjustment levels that should be taken into account for the elimination.
> **Note:** The app also carries out postings at adjustment levels that are locked for other postings.
'Adjustment levels' step
The following options are available on the **Adjustment levels** step:
| Option | Description |
|---|---|
| **Basis** | Adjustment level group including all non-consolidation adjustment levels for data imports and postings you want to include in the elimination. Please ensure that the adjustment level for proportioning is included in the adjustment level group. |
| **Target** | Adjustment level for consolidation postings to be used for the postings. |
### Elimination
In the **Elimination** step, specify how to deal with income from investments.
'Elimination' step
The following options are available on the **Elimination** step:
| Option | Description |
|---|---|
| **Income from investments** | The investor's accounts and/or items for eliminating income from distributions or profit/loss transfers received |
| **Post differences** | Account and transaction type for posting elimination differences.
**Note:** The account itself may not contain intercompany transactions to be eliminated. |
| **Advanced settings** | If you want to define different accounts or transaction types for certain intercompany relationships, activate the option **Advanced settings**. After that, in the **Intercompany relationship** column, select the two related companies for which you want to define different values and configure a deviating **account** and/or a deviating **transaction type**. |
### Profit or loss
The **Profit or loss** step is only displayed if you chose **Profit or loss transfers** as elimination option in the **Settings** step:
'Profit or loss' step
The following options are available on the **Profit or loss** step:
| Option | Description |
|---|---|
| **Eliminate profit or loss transfers** | Accounts and/or items of the investment that contain the amounts of the profit or loss transferred to be eliminated |
| **Configure compensation to non-controlling interests** | Activate this option if you want to recognize compensation payments to non-controlling interest and choose the accounts and/or items that contain the compensation to other investors.
**Note:** Compensation payments recognized on the chosen accounts and/or items will be reclassified to profit or loss attributable to non-controlling interests in the statement of profit or loss. |
| **Profit or loss attributable to non-controlling interests** | Account that the profit or loss from non-controlling interests is to be posted to |
### Distributions
The **Distributions** step is only displayed if you chose **Distributions from retained earnings** as elimination option in the **Settings** step:
'Distributions from retained earnings' step
The following options are available on the **Distributions from retained earnings** step:
| Option | Description |
|---|---|
| **Eliminate distributions from retained earnings** | The investment's **accounts and/or items** in equity and the **transaction type** on which distributions are posted. Only distributions posted on this transaction type will be eliminated. |
| **Non-controlling interests** | Activate this option if you want to **configure the attribution to non-controlling interests** and choose the account for adjusting the non-controlling interests in equity. |
| **Adjust non-controlling interest based on** | - **Master data**: The ownership interests defined in the [master data administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md) will be used to calculate the adjustment of non-controlling interests. - **Individual configuration**: An individually configured percentage value or an absolute amount will be used for the adjustment of non-controlling interests. Use the displayed table to specify the share of distribution that will be attributed to non-controlling interests per investment. For all other investments that are not configured in this table, the ownership interests defined in the [master data administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md) will be used. |
### Report
In the **Report** step, enter the consolidation area(s) that a report on the elimination of income from investments is to be created for, if necessary. The report shows the created elimination postings with any differences and the reclassifications to non-controlling interests.
'Report' step
The following options are available on the **Report** step:
| Option | Description |
|---|---|
| **Create report** | Activate the option to create a report on the difference amounts when executing the app. |
| **Consolidation areas included** | Consolidation areas for which the report should be generated.
**Note:** The report can only be created for consolidation areas that were included in the **Settings** step for the app execution. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Elimination of Income from Investments
You can execute the app for the **Elimination of income from investments** either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Elimination of Intercompany Debt"
description: "With the app for elimination of intercompany debt, the receivables and liabilities among the consolidation units of a group are eliminated for consolidated financial statements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-intercompany-debt
language: en
last_updated: 2026-05-01
---
# Creating and Configuring the Elimination of Intercompany Debt
## Overview
With the app for **elimination of intercompany debt**, the receivables and liabilities among the consolidation units of a group are eliminated for consolidated financial statements.
The app eliminates the intercompany transactions for all consolidation units of a consolidation area across all selected accounts based on the given partner information. Any differences from the consolidation are recognized in the second consolidation unit.
In addition, it is possible to generate a **report on differences** that may arise when executing the app. The report shows the differences with the corresponding difference accounts.
## Configuring the Elimination of Intercompany Debt
To configure the app for **elimination of intercompany debt**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In **Settings** step, specify the time and the relevant consolidation areas and/or units for consolidation:
Step 'Settings'
The following options are available on the **Settings** step:
| Option | Description |
|---|---|
| **Create postings** | Time of consolidation. - **Per month**: The app eliminates the intercompany transactions in each month of the consolidation period and creates monthly consolidation postings. - **Accumulated at the end of the period**: The app eliminates the intercompany transactions accumulated in the last month of the consolidation period and creates a consolidation posting only in the last month of the consolidation period.
**Note:** For each consolidation unit that is deconsolidated during the consolidation period, an accumulated consolidation posting is carried out in the last month of inclusion in the consolidation area. |
| **Consolidation area and/or unit** | Consolidation groups and/or units of the selected group for which the consolidation is to be performed. **By default**, **all** consolidation areas and units within the group are included in the consolidation. If you only want to include certain consolidation groups and units in the consolidation, activate the **Individual selection** check box and select one of the following options: - **Individual**: In the table, select individual consolidation areas and/or consolidation units to be considered in the consolidation. - **Exclude**: In the table, select the consolidation areas and/or consolidation units that are to be excluded from consolidation.
**Note:** If you choose **Individual** or **Exclude**, the app will perform no eliminations for intercompany transactions of the excluded consolidation units. |
### Adjustment levels
In the **Adjustment levels** step, sepcify the adjustment levels for consolidation.
Step 'Adjustment levels'
The following options are available on the **Adjustment levels** step:
| Option | Description |
|---|---|
| **Basis** | Adjustment level group that contains all adjustment levels for **data imports** and **adjustment postings** to be considered in the consolidation. Please ensure that the adjustment level for the [proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md) is included in this adjustment level group. |
| **Target** | Adjustment level for consolidation postings to be used for the postings. |
### Elimination
In the **Elimination** step, specify the the required **Accounts** and the **Transaction type** for the elimination of intercompany debt.
‘Elimination’ step
#### Accounts or items with intercompany transactions
Accounts and/or items to be considered for the consolidation
#### Post difference
**Default values**
**Account** and **transaction type** that are to be used by default for postings of differences that arise during consolidation.
The account itself must **not contain** any intercompany transactions to be consolidated.
**Deviating values**
- **Advanced settings**
If you want to define different accounts or transaction types for certain intercompany relationships, activate the option **Advanced settings**.
After that, in the **Intercompany relationship** column, select the two related companies for which you want to define different values and configure a deviating **account** and/or a deviating **transaction type**.
- **Separate account for differences in the period of the deconsolidation**
Activate this option to specify a separate **account** for posting differences in the period of the deconsolidation.
Advanced settings
### Report
In the **Reports** step, you can specify the consolidation area(s) and period for which a report on differences should be generated if any arise when executing the app.
The report shows the differences with the corresponding difference accounts and how the differences arose.
Report step
The following options are available on the **Report** step:
| Option | Description |
|---|---|
| **Generate report** | Activate the option to create a **Report on the difference amounts** when executing the app. |
| **Consolidation areas included** | Consolidation areas for which the report should be generated |
| **Reporting period** | Period for the report. - **Year to date (based on fiscal year of consolidation area)**: The report is created for the period starting from the beginning of the consolidation area's fiscal year and ending with the final period of the current consolidated financial statements. - **Consolidated financial statements**: The report is generated for the period of the current consolidated financial statements. |
> **Note:** The report is created in an executable folder named **Reports for _name of the consolidated financial statements element_** when executing the app and is linked in the detail view of the **Consolidated financial statements** workspace in the **Report** column.
>
> Each created report can be exported in Excel format.
>
> the shows overview table in 'consolidated financial statements' workspace. 'reports' column is selected, showing links to reports generated by apps. icon
> Linked reports in the consolidated financial statements overview
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Elimination of Intercompany Debt
You can execute the app for elimination of intercompany debt either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the difference reports and postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Elimination of Intercompany Income and Expense"
description: "Using the app for elimination of intercompany income and expense, the income and expenses that are the result of business transactions between companies in a given consolidation area are eliminated for consolidated financial statements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-income-and-expense
language: en
last_updated: 2026-05-01
---
# Creating and Configuring the Elimination of Intercompany Income and Expense
## Overview
Using the **app for elimination of intercompany income and expense**, the income and expenses that are the result of business transactions between companies in a given consolidation area are eliminated for consolidated financial statements.
In addition, it is possible to generate a **report on differences** that may arise when executing the app. The report displays the difference amounts with the corresponding difference accounts for each intercompany relationship.
When configuring the app, you can choose from the following options:
- **Elimination of intercompany income and expense over all selected accounts**
With this option, the app will eliminate intercompany transactions between any pair of two consolidation units across all chosen accounts based on the given partner information. Any difference from elimination will be recognized on the second consolidation unit
- **Elimination of intercompany income and expense as elimination between seller and buyer**
With this option, the app will eliminate intercompany transactions posted to seller accounts with the intercompany transactions posted to the respective buyer accounts based on given partner information. Any difference from elimination will be recognized on the buyer side of the intercompany transaction.
> **Note:** IC transactions between two consolidation units that are both posted to the seller accounts (both to the buyer accounts) are not consolidated, but cleared against the difference account. This option can also be used to present a one-sided elimination.
## Configuring the Elimination of Intercompany Income and Expense
To configure the app for **elimination of intercompany income and expense**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the time and the relevant consolidation areas and/or units for consolidation:
Step 'Settings'
The following options are available on the **Settings** step:
| Option | Description |
|---|---|
| **Create postings** | Time of consolidation: - **Per month** — The app eliminates the intercompany transactions in each month of the consolidation period and creates monthly consolidation postings. - **Accumulated at the end of the period** — The app eliminates the intercompany transactions accumulated in the last month of the consolidation period and creates a consolidation posting only in the last month of the consolidation period.
**Note:** For each consolidation unit that is deconsolidated during the consolidation period, an accumulated consolidation posting is carried out in the last month of inclusion in the consolidation area. |
| **Consolidation area and/or consolidation unit** | Consolidation groups and/or units of the selected group for which the consolidation is to be performed. **By default**, **all** consolidation areas and units within the group are included in the consolidation. If you only want to include certain consolidation groups and units in the consolidation, activate the **Individual selection** check box and select one of the following options: - **Individual** — In the table, select individual consolidation areas and/or consolidation units to be considered in the consolidation. - **Exclude** — In the table, select the consolidation areas and/or consolidation units that are to be excluded from consolidation.
**Note:** If you choose **Individual** or **Exclude**, the app will perform no eliminations for intercompany transactions of the excluded consolidation units. |
### Adjustment levels
In the **Adjustment levels** step, sepcify the adjustment levels for consolidation.
Step 'Adjustment levels'
The following options are available on the **Adjustment levels** step:
| Option | Description |
|---|---|
| **Basis** | Adjustment level group containing all adjustment levels for **data imports** and **adjustment postings** which need to be considered during consolidation. Please ensure that this adjustment level group contains the adjustment level for [proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md). |
| **Target** | Adjustment level for consolidation postings to be used for the postings. |
### Elimination
In the **Consolidation** step, specify the **procedure** for the elimination of intercompany income and expense as well as the required **accounts** and the **transaction type**.
‘Elimination’ step
The following options are available on the **Elimination** step:
| Option | Description |
|---|---|
| **Account or items with intercompany transactions** | Accounts for elimination of intercompany income and expense. Choose one of the following options: **Elimination over all selected accounts** — The app will eliminate intercompany transactions between any pair of two consolidation units across all chosen accounts based on the given partner information. Any difference from elimination will be recognized on the second consolidation unit. For this option, select all **accounts and/or items** to be considered for the consolidation. **Elimination between seller and buyer** — The app will eliminate intercompany transactions posted to seller accounts with the intercompany transactions posted to the respective buyer accounts based on given partner information. Any difference from elimination will be recognized on the buyer side of the intercompany transaction. For this option, assign all **accounts and/or items** that are to be included in the consolidation to either the **seller** or the **buyer** by selecting the accounts and/or items in the corresponding area. |
#### Post differences
**Default values**
**Account** and **transaction type** that are to be used by default for postings of differences that arise during consolidation.
The account itself must **not contain** any intercompany transactions to be consolidated.
**Deviating values**
If you want to define different accounts or transaction types for certain intercompany relationships, activate the option **Advanced settings**.
After that, in the **Intercompany relationship** column, select the two related companies for which you want to define different values and configure a deviating **account** and/or a deviating **transaction type**.
Advanced settings
### Report
In the **Reports** step, you can specify the consolidation area(s) and period for which a report on differences should be generated if any arise when executing the app.
The report displays the **difference amounts** with the corresponding **difference accounts** for each intercompany relationship.
‘Report’ step
The following options are available on the **Report** step:
| Option | Description |
|---|---|
| **Generate report** | Activate the option to create a report on the difference amounts when executing the app. |
| **Included consolidation areas** | Consolidation areas for which the report should be generated.
**Note:** The report can only be created for consolidation areas that were included in the **Settings** step for the app execution. |
| **Reporting period** | Period for the report. - **Year to date (based on fiscal year of consolidation area)** — The report is created from the start of the financial year for which the consolidated financial statements are created. - **Consolidated financial statements** — The report is generated for the period of the current consolidated financial statements. |
> **Note:** The report is created in an executable folder named **Reports for _name of the consolidated financial statements element_** when executing the app and is linked in the detail view of the **Consolidated financial statements** workspace in the **Report** column.
>
> Each created report can be exported in Excel format.
>
> the shows overview table in 'consolidated financial statements' workspace. 'reports' column is selected, showing links to reports generated by apps. icon
> Linked reports in the consolidated financial statements overview
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Elimination of Intercompany Income and Expense
You can execute the app for elimination of intercompany income and expense either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the difference reports and postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Elimination of Intercompany Profit or Loss in Current Assets"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/elimination-of-profit-or-loss-in-current-assets
language: en
last_updated: 2026-05-01
---
# Creating and Configuring the Elimination of Intercompany Profit or Loss in Current Assets
## Overview
- You can use the **Elimination of Intercompany Profit or Loss in Current Assets** app to eliminate intercompany profits and losses from sales and services between companies within a group.
- In this process, **intercompany relationships** are formed between the consolidation units within a consolidation group based on previously assigned **partner information** and the **investment relationships** within the company. The values that arise during interim elimination are posted to selected accounts.
- Optionally, the following functions can also be activated:
- Automatic reclassifications in the balance sheet and/or profit or loss statement
- Automatic posting of deferred taxes to the profit adjustment
## Configuring the Elimination of Intercompany Profit or Loss in Current Assets
To configure the app for **elimination of intercompany profit or loss in current assets**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify general settings for consolidation.
Step 'Settings'
#### Create postings
| Option | Description |
|---|---|
| **Per month** | The app eliminates the intercompany transactions in each month of the consolidation period and creates monthly consolidation postings. |
| **Accumulated at the end of the period** | The app eliminates the intercompany transactions accumulated in the last month of the consolidation period and creates a consolidation posting only in the last month of the consolidation period.
**Note:** For each consolidation unit that is deconsolidated during the consolidation period, an accumulated consolidation posting is carried out in the last month of inclusion in the consolidation area. |
#### Elimination options
Additional options for consolidation:
- Select the **Recognize deferred tax** option if deferred taxes arising from the elimination of intercompany profit or loss are to be recognized in current assets. The **Deferred Tax** step will then be displayed.
- Select the **Perform reclassification** option if account balances within the balance sheet and/or profit and loss statement are to be reclassified. The **Reclassifications** step will then be displayed.
#### Consolidation area and/or unit
Consolidation groups and/or units of the selected group for which the consolidation is to be performed. By default, all consolidation areas and units within the group are included in the consolidation.
If you only want to include certain consolidation groups and units in the consolidation, activate the **Individual selection** check box and select one of the following options:
| Option | Description |
|---|---|
| **Individual** | In the table, select individual consolidation areas and/or consolidation units to be considered in the consolidation.
**Note:** If you choose **Individual** or **Exclude**, the app will perform no eliminations for intercompany transactions of the excluded consolidation units. |
| **Exclude** | In the table, select the consolidation areas and/or consolidation units that are to be excluded from consolidation. |
### Adjustment levels
In the **Adjustment levels** step, specify the adjustment levels for consolidation.
Step 'Adjustment levels'
| Option | Description |
|---|---|
| **Basis** | Adjustment level group containing all adjustment levels for **data imports** and **adjustment postings** which need to be considered during consolidation. Please ensure that this adjustment level group contains the adjustment level for [proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md). |
| **Target** | Adjustment level for consolidation postings to be used for the postings. |
### Elimination
In the **Elimination** step, specify the accounts and transaction types for the elimination of intercompany profit or loss.
Step 'Elimination'
#### Balance sheet elimination accounts
- Click **Add row** and select the balance sheet items and/or accounts that contain the intercompany profit or loss in current assets (inventories) from the **Account or item** dropdown list. As part of the elimination process, these amounts are reversed from the selected inventory accounts and eliminated from the service provider’s P&L statement.
- Then, for each account or item, select the **transaction type** to be used for the elimination posting.
#### P&L elimination account
- Select the **account** in the P&L statement from which the intercompany profit or loss is to be eliminated. This account relates to changes in inventory.
- Then select the **transaction type** to be used for the elimination posting.
### Deferred tax
The **Deferred tax** step is displayed as soon as you have activated the **Recognize deferred tax** option in the **Settings** step.
In the **Deferred tax** step, specify the accounts to which any deferral taxes should be posted.
Step 'Deferred tax'
#### Balance sheet
Configure the **accounts** and **transaction** types for posting **deferred tax assets** and **deferred tax liabilities** arising from the elimination of intercompany profit or loss.
The app automatically determines whether to post **deferred tax assets or liabilities** based on the elimination direction (profit vs. loss).
- Deferred tax assets are recognized when the elimination creates a deductible temporary difference.
- Deferred tax liabilities are recognized when the elimination creates a taxable temporary difference.
#### Profit or loss
Configure the **accounts** and **transaction types** for posting **deferred tax income** and **deferred tax expense** in the statement of profit or loss.
These accounts serve as counter-postings to the deferred tax assets and liabilities in the balance sheet.
The app automatically determines whether to post deferred tax income or expense based on the elimination direction (profit vs. loss).
### Reclassifications
The **Reclassifications** step is displayed as soon as you have activated the **Perform reclassification** option in the **Settings** step.
In the **Reclassifications** step, specify the balance sheet and/or P&L accounts to which values should be reclassified and the transaction type to be used for the postings.
Step 'Reclassifications'
#### Balance sheet
Activate the **Perform reclassification within the balance sheet** option to split intercompany inventory balances after elimination and select the account and the transaction type to be used for the recalassification in the balance sheet.
The app automatically reclassifies the base cost portion (100% - profit/loss rate) from the original inventory accounts to the target account you specify here.
#### Profit or loss
Activate the **Perform reclassification within the P&L** option to redistribute eliminated intercompany profit or loss amounts across different P&L accounts.
Then configure **debit and credit accounts** below to split the elimination impact into specific line items.
The reclassification percentage is configured independently in the **Percentages** step.
### Percentages
In the **Percentages** step, specify the percentages to be used when calculating values during the elimination of intercompany profit or loss. Optionally, you can specify different percentages for specific intercompany relationships.
You can configure this step **manually** or **retrieve** percentages from a statistical book.
**Manual Configuration**
If you want to configure the percentages manually, select the **Manual configuration** option. The step will then be displayed as follows:
Step 'Percentages' in manual configuration
Then configure the following options:
#### Default values
Under **Default values**, specify the percentages for:
- The calculation of the IC elimination rate
- The balance sheet reclassification rate
- The P&L reclassification rate
- The calculation of the deferred tax rate
The field balance sheet reclassification rate or the P&L reclassification rate is only displayed if you have enabled **Reclassifications with** in the b **alance Sheet** or **Reclassification wthin the P&L** in the **Reclasifications** step.
#### Additional settings
Select the **Additional settings** option to specify **percentages that differ from the default values** for individual intercompany relationships.
Then configure the **Deviating values** table as follows:
1. Click **Add row** to add a new row.
2. In the **Intercompany relationship** column, first select the **Seller** and then the **Buyer** of the intercompany relationship for which you want to specify different percentages.
3. In the following columns, configure the different values in the same way as the default values.
**Retrieving percentages from a statistical ledger**
If you want to retrieve percentages from a statistical ledger, select the **Retrieve percentages from a statistical ledger** option. The step will then be displayed as follows:
Step 'Percentages' during automatic retrieval
Then select the statistical accounts that contain the percentages used to calculate the eliminations. Depending on the options you selected in the **Settings** and **Reclassifications** steps, the following statistical accounts are required:
- Intercompany elimination rate
- Balance sheet reclassifcation rate
- P&L reclassification Rate
- Deferred tax Rate
The app retrieves the values from these accounts during execution. The accounts must be of the **Percentage** type **with carry over from previous periods**.
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Elimination of Intercompany Profit or Loss in Current Assets
You can execute the app for elimination of intercompany profit or loss in current assets either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the difference reports and postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
Tab 'Created elements'
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Equity Elimination"
description: "Using the App for the equity elimination, the cross-ownerships between group companies are eliminated for the specified period to prepare consolidated financial statements. Values resulting during this process are posted to the accounts that were selected for equity elimination."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination
language: en
last_updated: 2026-05-28
---
# Creating and Configuring the Equity Elimination
## Overview
Using the **App for the equity elimination**, the **cross-ownerships** between group companies are **eliminated** for the specified period to prepare consolidated financial statements. Values resulting during this process are posted to the accounts that were selected for equity elimination.
The app for equity elimination supports the **inclusion of fully and proportionally consolidated subsidiaries** in the consolidated financial statements. In addition to the **elimination of the cross-ownerships** between the group companies, the app can be used to automatically perform a proportional reclassification for the correct recognition of non-controlling interests. Reclassification can be performed either together with the equity elimination or individually.
In addition, the app for equity elimination can be used for the measurement of associated companies using the **equity method**.
The business logic of the app for equity elimination is based on different **consolidation options**. The options may be applied either in accordance with the predefined configuration for the accounting standards **HGB (German Commercial Code), IFRS or US GAAP**, or according to an individual configuration.
> **Note:** **Information regarding range of functions**
>
> The following functions are currently **supported** by the app for equity elimination in the CFO Solution Platform:
>
> - Initial consolidation of fully and proportionately consolidated investments (all available options)
> - Deconsolidation of fully and proportionately consolidated investments in case of full sale of shares
> - Changes in ownership interests for fully consolidated investments without loss of control
> - IC transfers for fully consolidated investments without changes in the effective group share
> - Amortization of goodwill and straight-line reversal of negative consolidation differences
> - Attribution of profit or loss and currency translation differences to non-controlling interests
> - Consolidation of corporate actions for fully and proportionately consolidated investments
> - Measurement of associated companies using the equity method
> - Changes in the consolidation method between full consolidation and the equity method (without IC transfer of shares)
> - Offsetting negative equity carrying amounts when applying the equity method
> - Migration from the legacy app for equity elimination in Lucanet.Financial Client
>
> The following functions are **not supported** by the app for equity elimination in the CFO Solution Platform:
>
> - Deconsolidation of fully and proportionately consolidated investments as well as disposal of associated companies with a remaining interest in the investment
> - Changes in ownership interests for proportionately consolidated investments without loss of control, and for associated companies without loss of significant influence
> - IC transfers for fully consolidated investments with changes in the effective group share
> - IC transfers for proportionately consolidated investments and associated companies
> - Measurement of shares before consolidation using the equity method
> - Consolidation of corporate actions when applying the equity method
> - Changes in the consolidation method between full consolidation and the equity method (with IC transfer of shares)
> - Changes in the consolidation method from and to proportional consolidation
> - Posting comments within the equity elimination postings
>
> Please note that some of the functions which are currently not supported will be introduced gradually in future app versions. We will keep you informed about enhancements to the range of functions in the relevant What’s New communications.
>
> Customers currently using the Financial Client are advised to postpone migration to the next Generation app, until all features relevant to their business needs have been released.
>
> The legacy equity elimination app in Financial Client will be usable until all features are available in the CFO solution platform.
> **Warning:** Only one change of consolidation method per investor-investee relationship can be processed within a given consolidation period. If more than one change occurs during that period, split the consolidated financial statement into multiple ones.
## Configuring the Equity Elimination
To configure the app for **equity elimination**, click the app in the structure view and click **Edit** in the displayed dialog.
Then configure the steps as described below.
### Settings
Specify general configurations for the equity elimination in the **Settings** step:
'Settings’ step
#### Scope of functions
Choose between the full range of functions of the app (**Capital consolidation and reclassification to non-controlling interests**) or whether you only want to **reclassify to non-controlling interests**.
If you select the full range of functions, you can also perform a **measurement according to the equity method**. When this option is activated, the **Equity method** step is shown.
#### Migration from the legacy app
> **Note:** This option is only relevant if you have previously used the **(legacy) equity elimination of Consolidation 2 in Lucanet.Financial Client** and now want to switch to the **equity elimination in the CFO Solution Platform** for the first time.
>
> If this applies, we recommend **automatic migration** to ensure a correct basis for the business logic of the equity elimination in the CFO Solution Platform. Otherwise, you may need to reclassify balances manually. In this case, correct disclosure of the balances of the differences and non-controlling interests in the equity elimination cannot be guaranteed.
>
> If the migration options for the equity elimination app are not activated, historical values for non-controlling interests and goodwill will remain in the previous legacy dimension combinations and the new app cannot use these values as base values. This can lead to erroneous or incomplete postings in the following areas:
>
> - Amortization of goodwill and the straight-line reversal of negative consolidation differences cannot be performed.
> - Deconsolidation and changes in consolidation method from full consolidation to the equity method can lead to incomplete postings because the required base values are missing.
> - IC transfers of investments and changes in ownership interests can also be affected in certain constellations.
If you want to perform the automatic migration to the app for equity elimination on the CFO Solution Platform, the following options are available to you here:
**Reclassify goodwill and negative consolidation differences**
Activate the check box to reclassify the goodwill and negative consolidation differences to the dimension elements and accounts required by the business logic of the equity elimination in the Lucanet CFO Solution Platform.
- This option should always be activated if the legacy app was already used.
- This option is only available if the scope of functions **Equity elimination and reclassification to non-controlling interests** is selected.
> **Note:** In the app for the **equity elimination in the CFO Solution Platform**, the recognition of goodwill and negative consolidation differences at the investor level and the distribution of these values by investors using the partner dimension is no longer supported. This change corresponds to standard GAAP interpretations which stipulate that goodwill must be assigned to certain business units and not on the basis of ownership interests..
**Merge balances of non-controlling interests posted by origin account** If you have presented the non-controlling interests by origin account in the previous version of the app, you need to activate this checkbox to reclassify the balances of the non-controlling interests to the default account for non-controlling interests:.
This option is always available regardless of the selectedscope of functions.
#### Accounting standards
Accounting standard to be applied:
- **IFRS**
- **DRS/HGB (German accounting principles)**
- **US GAAP**
- **Individual** according to user-defined criteria within the scope of the option
> **Note:** This setting affects which app configurations are possible in the following.
#### Consolidation area and/or consolidation unit
Consolidation areasand/or units of the selected group the consolidation is to be performed for
**By default**, **all** consolidation areas and units within the group are included in the consolidation.
If you only want to include certain consolidation groups and units in the consolidation, activate the **Individual selection** check box and select one of the following options:
- **Individual**
In the table, select individual consolidation areas and/or consolidation units to be considered in the consolidation.
- **Exclude**
In the table, select the consolidation areas and/or consolidation units that are to be excluded from consolidation.
> **Note:** If you choose **Individual** or **Exclude**, the app will perform no eliminations for intercompany transactions of the excluded consolidation units.
### Adjustment levels
In the **Adjustment Levels** step, please enter the adjustment levels for the elimination and an account for any rounding differences that may arise.
‘Adjustment levels’ step
The following options are available on the **Adjustment levels** step:
| Option | Description |
|--------|-------------|
| Basis | Adjustment level group containing all adjustment levels for **data imports** and **adjustment postings** which need to be considered during consolidation. Please ensure that this adjustment level group contains the adjustment level for [proportioning](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/data-transfer-and-proportioning.md). |
| Target | Adjustment level for consolidation postings to be used for postings |
| Proportioning | Adjustment level for the proportioning. The adjustment level must be contained in the adjustment level group selected under **Basis**. |
| Consolidated financial statements | Adjustment level group that contains all adjustment levels of the adjustment level group **Basis** and the adjustment level **Target**. |
| Account for rounding differences | Account to which rounding differences are posted |
### Equity elimination
In the **Equity elimination** step, enter the details for the equity elimination.
> **Warning:** Please note that the options available in this step depend on the accounting standard you selected in the **Settings** step. All options that are not relevant are grayed out.
'Equity elimination’ step
| Option | Description |
|--------|-------------|
| Shares and investments | The balance account(s) or item(s) for shares and investments to be included in the equity elimination. All accounts and items must belong to the same transaction type category. |
| Transaction types for historical cost | Transaction types to be used for additions to and disposals from historical costs. These transaction types will be used in the context of IC share acquisitions and equity method measurements. The transaction types selected for historical cost must belong to the same transaction type category as the accounts and/or items selected for **shares and investments**. |
| Equity | Equity accounts or items to be included in the equity elimination. All accounts and items must belong to the same transaction type category. |
| Configure consolidation of corporate actions | Activate the option to include corporate actions in the consolidation process for **fully consolidated subsidiaries**. If you activate the option, additionally choose the **transaction types** for **capital increase and capital reduction** as well as a P&L account to which the **difference from corporate action** is to be posted. The selected transaction types for the corporate actions must belong to the same transaction type category as the selected accounts and/or items for equity.
**Note:** When using the app for **Equity elimination on the CFO Solution Platform**, additional configuration of the corporate actions in the [Master data administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/master-data-administration.md) is not required. |
| Change of ownership interests without loss of control | Under **Recognize differentials**, specify how differences from changes to the ownership interests without loss of control should be recognized. Depending on the underlying accounting standard, you have the following options: - **As goodwill or gain or loss from deconsolidation**: Differentials will be recognized as goodwill or negative goodwill in the event of an increase in ownership interest or as gain or loss from deconsolidation in the event of a reduction in ownership interest. - **In equity**: Differentials are recognized in retained earnings under equity, regardless of whether there is an increase or decrease in ownership interest. When choosing the option **In equity**, please specify an account to which the **Retained earnings** are to be posted. |
| Change of ownership interests with loss of control | Select the profit and loss account for the recognition of the gain or loss from deconsolidation. This account is required during the consolidation process if an investor loses control of a previously fully- or proportionally consolidated subsidiary due to a reduction in the ownership interest.
**Note:** The current version of the app only supports a loss of control for fully consolidated subsidiaries when no shares remain. Partial sale of shares or changes to proportionally consolidated subsidiaries are currently not supported. Please check the postings as adjustments may be required! |
### Differential
In the **Differential** step, enter the details for the equity elimination.
> **Warning:** Please note that the options available in this step depend on the accounting standard you selected in the **Settings** step. All options that are not relevant are grayed out.
‘Differential’ step
| Option | Description |
|--------|-------------|
| Goodwill | Balance sheet item under which accounts for goodwill are to be created. If necessary, activate the option **Amortize goodwill on a straight-line basis**, and also select a **transaction type** that is to be used for the amortization postings. |
| Negative consolidation difference | Specify how negative consolidation differences are to be recognized: - **Recognize in the P&L**: Activate this option to recognize negative consolidation differences in the profit and loss statement and select the corresponding **target account** to be used by the app. - **Recognize in the balance sheet**: Activate this option to recognize negative consolidation differences in the balance sheet and select the **target balance sheet item** under which the account(s) for negative consolidation differences are to be created. - **Reverse negative consolidation difference on a straight-line basis**: When recognition in the balance sheet is chosen, activate this option if negative consolidation differences are to be reversed and select a **transaction type** to be used for the postings.
**Note:** If for a subsidiary included in the scope of execution of the app the **Full Goodwill Method** has been activated, the option **Recognize in the P&L** must be chosen. If a **proportionally consolidated subsidiary** is included in the scope of execution of the app, the option **Recognize in the balance sheet** must be chosen. These restrictions are necessary to ensure that the created equity elimination postings are in accordance with the underlying accounting standards. |
| Currency translation of differential | Specify whether the differential from equity elimination is to be presented in the **currency of the consolidation area** or in the **currency of the consolidation unit**. If the presentation in the **currency of the consolidation unit** is chosen, you should also select the **balance sheet item** under which the technical account(s) for the reclassification of the differentials are to be created or have already been created with the correct attributes. |
| Allocation of indirect differential | Specify whether the differential attributable to indirect non-controlling interests is to be recognized. Specify how differentials relating to indirect non-controlling interests that arise during the initial consolidation of subsidiaries or the consolidation of an increase in shares in subsidiaries is to be recognized. The following options are available depending on the underlying accounting standard: - **As goodwill/negative consolidation difference** from consolidation - **As non-controlling interests in equity**
**Note:** For **full consolidation** using the **full goodwill method** and for **proportionally consolidated** subsidiaries, the differential is **always** recognized as **goodwill/negative consolidation difference** irrespective of the option actually selected for indirect non-controlling interests. |
### Non-controlling interest
In the **Non-controlling interests** step, specify the details for the treatment of the non-controlling interests.
'Non-controlling interest’ step
#### Recognize non-controlling interests
| Option | Description |
|--------|-------------|
| Non-controlling interests | Balance sheet item under which the account or accounts for non-controlling interests are to be created or have already been created with the correct attributes |
| Changes in non-controlling interests | Transaction type to be used for recognizing changes in non-controlling interests following increases or decreases in ownership interests without loss of control |
#### Attribution of income to non-controlling interests
| Option | Description |
|--------|-------------|
| Net income/loss in equity | Balance sheet item or account to be used as the basis for reclassification of the net income/loss to non-controlling interests |
| Transaction type | Transaction type to be used as a basis for the reclassification of the net income/loss to non-controlling interests.
**Note:** This option is only relevant if you have previously used the **(legacy) equity elimination of Consolidation 2 in Lucanet.Financial Client** and now want to switch to the **equity elimination in the CFO Solution Platform** for the first time. If this applies, we recommend **automatic migration** to ensure a correct basis for the business logic of the equity elimination in the CFO Solution Platform. Otherwise, you may need to reclassify balances manually. In this case, correct disclosure of the balances of the differences and non-controlling interests in the equity elimination cannot be guaranteed. |
| Profit or loss attributable to non-controlling interests | Target account in the P&L for posting the reclassification of the net income/loss to non-controlling interests |
#### Attribution of currency translation differences to non-controlling interests
Accounts or items whose values are to be used as a calculation basis for the continuous attribution of the currency translation differences to non-controlling interests
### Equity method
In the **Equity method** step, specify the accounts/items and transaction types to be taken into account when measuring under the equity method.
Note: The **Equity method** step is only visible if you have enabled the option **Measurement under the equity method** in the **Settings** step.
'Equity method' step
**Specify the following for the Recognition and initial measurement according to the equity method:**
| Option | Description |
|--------|-------------|
| Reconciliation between opening and closing carrying amounts of the investment | Select a subledger item with period type **Balance with carry forward from previous period** under which accounts used for the measurement of associates according to the equity method should be created. **Note:** This separate calculation will serve as the basis for the continuous reconciliation between the opening and closing carrying amounts of investments in associates. Please ensure that the account for investments in associates is configured as transfer account for the subledger the selected item belongs to. In addition, the options **Subledger accounts with the same transaction type category as the transfer account use the transaction type of the posting instead of the default transaction type** and **Include partner dimension in the transfer** must be activated within the subledger. |
| Carrying amount increases | Select the transaction type to be used to recognize **increases in carrying amounts** of investments in associates. Please note that the selected transaction type must belong to the same transaction type category as the item chosen for the reconciliation between the opening and carrying amounts. |
| Carrying amount decreases | Select the transaction type to be used to recognize **decreases in carrying amounts** of investments in associates. Please note that the selected transaction type must belong to the same transaction type category as the item chosen for the reconciliation between the opening and carrying amounts. |
| Configure allocation of differential to hidden reserves and liabilities | Activate the option to allocate a difference arising from initial measurement of an associate according to the equity method to the included proportionate hidden reserves and liabilities as well as to the remaining proportionate goodwill or negative consolidation difference. If the option is activated, select the balance sheet item or account used for the disclosure of the **revaluation surplus**. This item or account will serve as the basis for the differential allocation to hidden reserves and liabilities. |
**Specify the following for the Subsequent measurement according to the equity method:**
| Option | Description |
|--------|-------------|
| Net income/loss in equity | Review the selected base account and transaction type within the **Non-controlling interests** step for the continuous attribution of income to non-controlling interests. This account and transaction type will serve as a basis for the subsequent measurement of associates according to the equity method as well. The app will calculate the share of the associate’s profit and loss in each period based on the values found on this combination of account and transaction type. |
| Share of the associate’s income/Share of the associate’s loss | Choose the target P&L account to be used by the app to present the **share of the income or loss from associates** in a separate line item in the consolidated statement of profit or loss. Please note that the differentiation between the share of the associate’s income and loss is solely used to recognize the net result below the correct line item in the profit or loss statement. However, these accounts are not used for a separate disclosure of the associate’s income and losses as this is not required by the legislation. |
| Currency translation differences | Review the selected base accounts and items within the **Non-controlling interests** step for the continuous attribution of currency translation differences to non-controlling interests. These accounts and items will serve as the basis for the subsequent measurement of associates according to the equity method as well. |
| Configure separate recognition of the share of the associate’s other comprehensive income | Activate the option to recognize the share of the associate’s other comprehensive income separately. If this option is activated, select the balance sheet item or account and the transaction type to be used as the basis for calculating the proportionate other comprehensive income within the subsequent measurement of an associate according to the equity method. The app will calculate the share of the associate’s other comprehensive income in each period based on the values found on this combination of account/item and transaction type. Please note that the availability of the option depends on the previously selected accounting standard. |
**Specify the following for the Changes in ownership interests with loss of significant influence:**
> **Warning:** Please note: The current version of the app **only** supports loss of significant influence in associates measured according to the equity method if no shares remain. Partial sales of shares are not supported yet. Please review the postings as adjustments might be needed.
| Option | Description |
|--------|-------------|
| Gain or loss from disposal of associates | Select the account to be used by the app for changes in ownership interests with loss of significant influence to recognize the gain or loss from disposal of associates. |
| Accumulated D&A disposal | Select the transaction type for disposal of accumulated depreciation and amortization on the equity carrying amount. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Equity Elimination
You can execute the app for equity elimination either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Executing the Consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md).
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the app is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Excel-Integration"
description: "Lucanet provides complete Excel integration for planning and reporting purposes. The Lucanet CFP Add-in for Excel 365 enables interactive access from MS Excel to the Lucanet.Financial OLAP Server for data query and editing, and Lucanet.Excel-Reporting enables the creation of standard reports in MS Excel."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration
language: en
last_updated: 2026-05-01
---
# Lucanet Excel Integration
Lucanet provides the complete Excel integration for planning and reporting purposes.
**Lucanet CFP Add-in for Excel 365** enables interactive access from MS Excel to Lucanet.Financial OLAP Server that can be used for data query and data editing from MS Excel.
**Lucanet.Excel-Reporting** enables the creation of standard reports in MS Excel.
You can choose to use **Lucanet CFP Add-in for Excel 365** or **Lucanet.Excel-Reporting** depending on how you want to use MS Excel together with the Lucanet software.
## Comparison
**Area of operations**
| CFP Add-in for Excel 365 | Lucanet.Excel-Reporting |
|---|---|
| Interactive analysis and editing of data | Creating standard reports |
**Advantages**
| CFP Add-in for Excel 365 | Lucanet.Excel-Reporting |
|---|---|
| • The latest values are always available. • Data on Lucanet.Financial OLAP Server can be queried from within MS Excel. • Data on Lucanet.Financial OLAP Server can be edited from within MS Excel. | • No internet access or Lucanet account is required to read the reports. • Lucanet CFP Add-in for Excel 365 does not need to be installed. • An unlimited number of formulas is possible. |
**Disadvantages**
| CFP Add-in for Excel 365 | Lucanet.Excel-Reporting |
|---|---|
| • Internet access and access to the Lucanet CFO Solution Platform are required. • Lucanet CFP Add-in for Excel 365 must be installed. • A Lucanet account is required. • A Lucanet user is required. | • The reports contain the values at the time the report was generated. That means the reports may not necessarily contain the most up-to-date values. • The system only queries values, which cannot be edited. |
**Should be used if...**
| CFP Add-in for Excel 365 | Lucanet.Excel-Reporting |
|---|---|
| The interactive data analysis is necessary, because the latest values should always be available and/or data needs to be edited on Lucanet.Financial OLAP Server from MS Excel. | Standard reports are to be used that are distributed as required and are displayed independently of Lucanet and/or Internet access. |
- [CFP Add-in for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in.md)
- [Lucanet.Excel-Reporting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting.md)
---
---
title: "Executing Multiple Elements Using Workflows"
description: "With workflows, you can map a saved sequence in Consolidation & Financial Planning in which executable elements such as scripts, data imports, or apps, are executed one after another in a defined order."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/executing-elements-using-workflows
language: en
last_updated: 2026-05-01
---
# Executing Multiple Elements Using a Workflow
## Overview
With **workflows**, you can map a saved sequence in Consolidation & Financial Planning in which executable elements such as **scripts**, **data imports**, or **apps**, are executed one after another in a defined order.
Workflows can be created directly in a directory structure, provided that the [element type has been enabled](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) for workflows, and you can:
- Add any executable elements or executable folders from Consolidation & Financial Planning
- Define the behavior in case of errors
- Execute the workflow as a coordinated process
Workflows thereby contribute to the standardization of recurring execution processes and reduce the manual setup effort for repeated runs.
## Creating and Configuring a Workflow
A workflow can be created in any directory structure, provided that the element type **Workflow** has been [enabled](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) for this directory structure.
To create and configure a workflow, proceed as follows:
1. Navigate to the [directory structure](https://support.lucanet.com/en/documentation/glossary.md#directory-structure) in which the workflow is to be created.
2. Select the **root folder** of the directory structure or, if applicable, a **folder** under which you want to create the workflow, and select **Create | Workflow** from the context menu.
The **Create Workflow** dialog is displayed as follows:
Create workflow
3. Enter a **name** for the workflow and click **Save**. The workflow is created in the structure view.
4. In the detail view of the workflow, click **Edit**.
The detail view is displayed as follows, for example:
Detail view of a workflow
5. For each element that you want to execute within the workflow, click **\+ Add row** and then select the element or executable folder that you want to add to the workflow from the drop-down list in the **Element** column.
The elements and/or folders are subsequently executed in the order defined here.
6. Define the **behavior in case of an error or missing read or write permissions**:
- **Continue execution** if the workflow is to be continued even if an error has occurred during execution
- **Cancel execution** if the execution of the workflow is to be stopped when an error occurs while executing an element
Whether you have the permissions required for execution is displayed in the **Permission** column as soon as you have added the element.
7. **Save** the settings.
## Executing Workflow
After you have configured a workflow, you can execute it by clicking **Execute** at the top right of the detail view.
Execute workflow
Once the workflow has been executed, the **Executions** tab displays the **date and time** and **status** of the execution as well as the **user** who executed the workflow.
Following statuses are possible:
- **Not executed**: The workflow has not been executed yet
- **OK**: The workflow was executed successfully.
- **Error**: An error occurred during execution.
- **Canceled**: Execution has been canceled manually by the user.
> **Note:** [Data imports into reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities.md) can only be executed within a workflow if it is an update of an existing import in which the configuration is kept unchanged. If the configuration of a data import is to be adjusted during execution, the data import must be executed as described under [Creating and Executing the Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md).
---
---
title: "Executing the Consolidation"
description: "Different options are available for executing the consolidation and for creating the respective consolidation postings. You can:\n- Execute individual consolidation apps separately\n- Execute multiple consolidation apps jointly in a so-called executable folder\n- Execute entire consolidated financial statements including all child elements"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation
language: en
last_updated: 2026-05-01
---
# Executing the Consolidation
## Overview
Different options are available for executing the consolidation and for creating the respective consolidation postings. You can:
- Execute individual consolidation apps **separately**
- Execute multiple consolidation apps **jointly in a so-called executable folder**
- Execute entire **consolidated financial statements** including all child elements
> **Warning:** **Note for customers who have used apps of the Consolidation 2 or Consolidation 2 Next Generation in Lucanet.Financial Client**
>
> For information on the apps supported in the CFO Solution Platform, please read the [Notes on Migration from Lucanet.Financial Client](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/migration-from-lnfc.md).
## Executing a Consolidation App Separately
Once you have created and configured an app in the **Consolidated financial statements** workspace, you can execute the app. Do one of the following:
- In the upper right corner of the **editing dialog of the app**, click **Execute**:
Executing the app from the detail view
- In the overview table in the **Consolidated financial statements** workspace, click **Execute** in the **Actions** column.:
Executing an app in the overview table
## Combining Consolidation Apps and Executing Them Together
To maintain an overview of a large number of elements, any number of **executable folders** can be created in the **Consolidated financial statements** workspace for better structuring.
In executable folders, several **Consolidated financial statements** elements and/or **consolidation apps** can **be combined and executed**.
Executable folders can be created under the following elements:
- **Consolidated financial statements** root folder
- **Consolidated financial statement** elements
- Executable folder
This is how you group elements in a folder in the **Consolidated financial statements** workspace and execute them:
1. In the **structure view**, select the **element** under which you want to create the executable folder and choose **Create | Folder** from the context menu.
2. Enter a **Name** in the **Create folder** dialog and select a desired **Behavior** if there should be an error during execution of the folder:
- **Continue execution**
- **Cancel execution**
3. **Save** the executable folder.
4. Paste the elements to be summarized into the folder. Do one of the following:
- Add existing elements using the menu commands **Cut** and **Paste**.
- Create new elements in the folder using the **Create** context menu command.
5. Execute the folder and all elements contained in it by clicking **Execute folder** in the **Actions** column in the **overview table**.
Execute folder
## Executing Consolidated Financial Statements
After preparing the consolidated financial statements in the **Consolidated financial statements** workspace, you can execute the entire consolidated financial statements including all contained elements (apps or executable folders).
To do so, click **Execute consolidated financial statements** in the **Actions** column in the **overview table**.
Execute consolidated financial statements
## Viewing the Execution Status
Whether an app, an executable folder or consolidated financial statements have already been executed and whether the execution was successful is shown in:
The upper right corner of the **detail view** of the app:
Execution status in the detail view
In the **overview table** in the **Consolidated financial statements** workspace in the column **Status**:
Execution status
Following statuses are possible:
- **Not executed**: The element has not been executed or all created elements of an already executed app have been deleted.
- **OK**: The element and, if applicable, all child elements were executed successfully.
- **Error**: An error occurred during execution.
- **Canceled**: Execution has been canceled manually by the user.
In the column **Last execution**, you can also see which **user** executed the element for the last **time**.
> **Note:** For a detailed history of past executions, including the process log of each run, open the **Execution log** tab in the app's change log. For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
---
---
title: "Executing the Data Import"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/execute-data-import
language: en
last_updated: 2026-05-01
---
# Executing the Data Import
## Overview
Data can be imported manually into Lucanet.Financial Warehouse from Consolidation & Financial Planning.
## Executing the Data Import
To perform the data import to Lucanet.Financial Warehouse:
1. In the **Import and Journals** folder in the Overview, click the **Importing data into Lucanet.Financial Warehouse** workspace.
2. Select the desired execution settings and click **Execute** in the **detail view** to execute the configuration.
Excecute Import
---
---
title: "Exporting Exchange Rates"
description: "You can export the exchange rates contained in your exchange rate tables to MS Excel at any time."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/export-exchange-rates
language: en
last_updated: 2026-05-01
---
# Exporting Exchange Rates
## Overview
You can export the exchange rates contained in your exchange rate tables to MS Excel at any time.
## Exporting Exchange Rates to MS Excel
To export exchange rates:
1. Right-click the root folder **Exchange rate tables** or an individual exchange rate table.
2. Select **Export | Export exchange rates to MS Excel (XLS or XLSX)** from the context menu **.** The **Export exchange rates to MS Excel** dialog is displayed:
The ‘Export exchange rates to MS Excel’ dialog
3. Speficy the following:
- The **exchange rate tables** from which the exchange rates are to be exported
- The **data levels**
- The **period** for which the exchange rates are to be exported
- The **name** of the export file
4. Click **Export**.
---
---
title: "Exporting values to MS Excel or as a PDF"
description: "For further processing or publication of the data, you have the option of exporting the values displayed in the tree view of ledgers and schedules either as a PDF or as an MS Excel file."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/export-values-excel-pdf
language: en
last_updated: 2026-05-01
---
# Exporting Values to MS Excel or as a PDF
## Overview
For further processing or publication of the data, you have the option of exporting the values displayed in the tree view of ledgers and schedules either as a PDF or as an MS Excel file.
## Exporting values
To export values from ledgers and schedules:
1. In the context menu, click the **settings icon** the settings icon in the header of the first column of a ledger or schedule.
2. Choose **Export** from the context menu.
3. Choose the desired format:
Export values from a balance sheet to MS Excel or as a PDF
---
---
title: "Finalizing a Data Import"
description: "Every data import can be finalized in order to prevent it from being changed or deleted."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/completing-data-import
language: en
last_updated: 2026-05-01
---
# Finalizing a Data Import
## Overview
Every data import can be finalized in order to prevent it from being changed or deleted.
## Finalizing a Data Import
To finalize a data import:
1. In the tree view, right-click the name of the desired data import and choose **Finalize data import** from the context menu.
Finalizing a data import
The following message is displayed:
Confirmation dialog for finalizing an import
2. Click **Yes**.
The data import is finalized and indicated as finalized in the tree view via the finalize data import icon.
> **Note:** Postings created by data imports can be undone using the cancellation postings in Lucanet.Financial Client.
---
---
title: "Fiscal Years"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/fiscal-years
language: en
last_updated: 2026-05-01
---
# Fiscal Years
## Overview
The [Fiscal years](https://support.lucanet.com/en/documentation/glossary.md#fiscal-year) workspace is used to create, administrate, and delete fiscal years in the Lucanet database. The fiscal years created here can be selected for account hierarchies and schedules in the dimension bar when specifying periods.
The fiscal year of a reporting entity is defined independently of the fiscal years defined in the **Fiscal years** workspace and is specified when creating the reporting entity.
---
---
title: "Formatting Numbers and Dates"
description: "Regardless of the selected language, you can configure the date and number format as well as the display of negative numbers in the Lucanet CFO Solution Platform."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/format-numbers-dates
language: en
last_updated: 2026-09-08
---
# Formatting Numbers and Dates
## Overview
Regardless of the selected language, you can configure the date and number format as well as the display of negative numbers in the **Lucanet CFO Solution Platform**. The settings apply to the display of values in ledgers and schedules.
## Opening Formatting Preferences
To open the formatting preferences, click the **user account** area at the bottom of the main menu and select **Formatting preferences** from the **account menu**.
User account area and the account menu
For more information, see [Configuring the Date and Number Format](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#configuring-the-date-and-number-format).
## Configuring Formatting Preferences
In the **Formatting Preferences** dialog, you can configure the formatting for numbers and dates:
'Formatting Preferences' dialog
| Option | Description |
|---|---|
| **Date format** | Defines how the date is displayed |
| **Number format** | Defines how numbers are displayed |
| **Negative numbers** | Defines how negative numbers are displayed |
---
---
title: "Functions"
description: "With functions in tilde formulas, you can query information and data from Lucanet and output them in an Excel report. A function specifies what type of information is retrieved (e.g., numerical values, currencies, exchange rates)."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/functions
language: en
last_updated: 2026-05-01
---
# Functions
## Overview
With functions in tilde formulas, you can query information and data from Lucanet and output them in an Excel report.
A function specifies what type of information is retrieved (e.g., numerical values, currencies, exchange rates).
## Tilde Formula Structure
For functions, the tilde formula must be structured as follows:
**~Function(Parameter 1="_Value_";...;Parameter n="_Value_")**
## Rules for Functions in Tilde Formulas
The following rules apply for functions in tilde formulas:
- One, several or no parameters can be added to the function name.
- The parameters of a function are enclosed in round brackets ( ).
- Several parameters are separated using a semicolon ( ; ).
- The parameters for a function are described with a **keyword** or a **placeholder**.
- A keyword has a **value** that follows an equals sign ( = ) and is enclosed in quotation marks.
- It is also possible to use cell references as values. Quotation marks must not be used for cell references.
## 'Value' Function
The **Value** function can be used to export any value from an account or an item in the Lucanet database.
### Tilde Formula Structure for the 'Value' Function
The tilde formula must be structured as follows:
**~Value(Item="_Name or URL of item/account_";Keyword_1/Placeholder_1;...;Keyword_n/Placeholder_n)**
### Rules for the 'Value' Function
- The basic parameter **item/account** must be specified.
- All other basic parameters are optional.
- For optional parameters, you can use either a placeholder or a keyword.
- A value following an equal sign ( = ) is assigned to a parameter.
- The value of a parameter must be in quotation marks ( " ).
### Basic Parameters for the 'Value' Function
In the **Value** function, you can use the following basic parameters, which match the dimensions in Lucanet:
- Item/account
- Period
- Organization element
- Data level
- Adjustment level/group
- Transaction currency
- Display currency
- Partner
### Optional Parameters for the 'Value' Function
In addition to the basic parameters, the following optional parameters can be used in the **Value** function.
### Abbreviation
The **Abbreviation** parameter is optional and specifies the ledger or schedule to be searched for an item or account. By specifying the ledger or schedule to be searched, you can avoid error messages if the item or account you are searching for exists several times.
If the parameter is omitted, all ledgers and schedules are searched.
> **Note:** **Note**: In schedules, you can only search for items.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~value(Abbreviation="_Abbreviation of ledger_";Pos="_Item/Account_")**
### Currency
By default, values from an account or an item are read into MS Excel in the defined default currency of the reporting entity, consolidation area, or consolidation unit that the specified organization element references. To read in values in other currencies to MS Excel, the parameters **Transaction currency** and **Display currency** can be used.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~value(pos="_item/account_";transaction currency="_transaction currency_";display currency="_display currency_")**
**Keywords**
The currencies defined in Lucanet in the [Currency translation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation.md) workspace can be used as values for **transaction currency** and **display currency**.
**Variants**
The result of a query depends on the keywords used in the Tilde formula. The following variants are available:
- **Without keyword**
The sum of all specified values (in all transaction currencies) converted into the default currency of the organization element
- **Display currency only**
The sum of all specified values (in all transaction currencies) converted into the specified display currency
- **Transaction currency only**
The sum of all values specified in the specified transaction currency converted into the default currency of the organization element
- **Transaction currency and display currency**
The sum of all values specified in the specified transaction currency converted into the specified display currency
> **Note:** To record the values of all transaction currencies, you can use Transaction currency="**All**", if you retain the default name of the element for the value query of all transaction currencies (**All transaction currencies**).
>
> Once you have renamed the element, the tilde formula must also be changed accordingly. In the tilde formula, enter at least the first three letters of the element name as the parameter instead of **All**.
**Example**
In the Excel worksheet, all options for querying the item **Fixed assets** are used. The **Value in** column displays the currency resulting from the tilde formula if the default currency of the selected organization element is **EUR**:
'Currency' parameter
### Transaction type
The **Transaction type** parameter is optional and imports either the values of an account or the values of a transaction type (or transaction type group from the fixed asset schedule) into MS Excel.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Value(Item="_Item/Account_";Transaction type="_Keyword_")**
**Keywords**
The following keywords are available:
- **Start**
Returns the start value of the account on a given date
- **Transaction figures/TF**
Returns the change to the account on a given date
- **Saldo**
Returns the balance of the account on a given date
**Keywords for transaction types or transaction type groups**
When determining the value for a transaction type or for a transaction type group, the **ID** of the transaction type, the **abbreviation** of the transaction type group, or a **link** to a cell must be specified with the corresponding entry:
- Name of a transaction type (e.g. **110 Addition**)
Returns the value **110 Addition**
- **Cost.Start** or **Accumulated depreciation and amortization.Start**
Returns the start value in the transaction type group **Historical cost** or **Accumulated depreciation and amortization**.
- **Cost.TF** or **Accumulated depreciation and amortization.TF**
Returns the change in the transaction type group **Historical cost** or **Accumulated depreciation and amortization**.
- **Cost.Balance** or **Accumulated depreciation and amortization.End of period**
Returns the balance in the transaction type group **Historical cost** or **Accumulated depreciation and amortization**.
The naming of the keywords depends on how naming is entered in the [Dimensions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions.md) under Transaction Types.
**Example**
In the function, the **Transaction type** parameter is used with the keyword **tt** and a cell link (**d11**):
'Transaction type' parameter
### Suppressing error messages
The **No error** parameter is optional and specifies that the system should suppress error messages if the system cannot find the item or account it searched for.
In this case, the return **value** of the Value function is **0**.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Value(Item="_Item/Account_";_no error_)**
### YTD
The **YTD** parameter can be used to query the value of an account or an item for the Year-To-Date period up to the current period.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Value(Item="_Item/Account_";YTD="_Year to date_")**
**Example**
In the following example, the values for the **Wages and salaries** item are queried for the period between July 2017 (= "**YTD 07**") and the period currently specified for the report (e.g. November 2017).
'YTD' optional parameter
### Keywords for the 'Value' Function
For the parameters of the **Value** function, the following keywords are available:
- **Item/account**: Item, Account, ACC
- **Period**: Period
- **Organization element**: Organization element, OE
- **Data level**: Data level, DL
- **Adjustment level**: Adjustment level, BE
- **Transaction currency**: Transaction currency, TC
- **Display currency**: Display currency, Currency, DC
- **Partner**: Partner, P
The following table shows **examples of keywords** with assigned values:
| Example | Description |
|---------|---------|
| Item="Turnover" | Value in quotation marks The system searches for the **Sales** item. |
| Data level=A3 | Absolute cell reference The system searches for the data level whose abbreviation can be found in **cell A3**. |
| Organization element=8 | Reference to row The system searches for the organization element with its abbreviation in **row 8** of the same column. |
| Item=A | Reference to column The system searches for the item whose name is located in **column A** of the same row. |
| Item=A:C | Reference to a cell range The system searches for the item whose name is in the first non-empty column in the same row in **columns A to C**. |
| Period=Period.Comparison | Reference to placeholder The period represented by the **Period.Comparison** placeholder is used. |
| Ledger=heading | Reference to a named cell An adjustment level is being searched whose abbreviation is in the row which was named Row: Heading by means of the row statement (see [Naming Rows/Columns](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/statements.md)). |
### Example for the 'Value' Function
In the Excel worksheet, the **Value** function has parameters for item (**item**), period (**period**), and transaction type (**tt**).
In the tilde formula, references to a cell area (**item=b:c**), a cell (**c12**) and to a row (**15**) are used:
'Value' function
## Additional Functions
The following functions can be used in a tilde formula:
### 'Currency' Function
The **Currency** function enables the **default currency** of elements from the **Reporting entities** or **Organization elements** workspace to be read in to MS Excel.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Currency(Organization element="Name of the element")**
The following elements can be specified as organization element:
- Reference to reporting entity
- Reference to cost center
- Reference to cost center group
- Reference to consolidation area
- Reference to consolidation unit
- Reference to consolidation unit group
- Organization group
The specification of an element is optional. If no element is specified, the user has to choose an element when [creating the report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md).
**Example**
In the Excel worksheet, the **Organization element** parameter of the **Currency** function is specified with a reference to cell **B2**:
'Currency' function
### 'Rate' Function
The **rate** function can be used to read in the **average exchange rate**, the **closing exchange rate**, or the **YTD exchange rate** at which a transaction currency is converted into a display currency, to MS Excel.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~rate(table="name of exchange rate table";data level;exchange rate type;period)**
**Keywords**
The following keywords are available for the parameter Exchange rate type:
- **Closing exchange rate**: Returns the closing exchange rate for a month
- **Average exchange rate**: Returns the average exchange rate for a month
- **YTD exchange rate**: Returns the YTD rate of a month
Only one of the available keywords can be specified at a time.
**Example**
In the Excel worksheet, the **closing exchange rate** and the **average exchange rate** for the table **USD -> EUR** are read in in the **Actual** data level on a monthly basis (**~month**) to MS Excel. In the tilde formula, data level (**B2**), closing exchange rate (**B**) and period (**4**) are used by means of cell references:
'Rate' function
The generated report appears as follows:
Result for function 'rate'
### 'Attribute' Function
You can use the **Attribute** function to query attribute values. The **Attribute** function can also be combined with the tilde formulas **~Fill rows** and **~Fill columns** to import the names of elements into MS Excel in addition to their OIDs.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Attribute(attribute;element)**
**Parameters of the Attribute Function**
The following placeholders must be specified:
- **Attribute**: Key for the attribute whose value is to be read in to MS Excel
- **Element**: The name or URL of the element whose attribute value is to be read in to MS Excel
**Example**
In the Excel worksheet, the **Attribute** function is used to query the English (**Attribute=name**) and the German name (**Attribute=name_ger**) of items and accounts. In column C, a cell reference (b) is used in row 3 and the URL of the account is used directly in row 4:
'Attribute' function
The generated report appears as follows:
Result for function 'attribute'
### 'Document' Function
You can use the **Document** function to access the description for elements.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Document(Element)**
The Element parameter represents the element whose description you want to copy to MS Excel.
**Example**
The tilde formula returns the description of the data level with the URL **ln:goto/LNFC/demo?oid=12907**.
'Document' function
> **Warning:** Currently, descriptions cannot be added to elements in the CFO Solution Platform. Therefore, the **Document** function can only be used to access descriptions that have been added to elements in **Lucanet.Financial Client**.
### 'Comment' Function
The **Comment** function can be used to read in **comments** on items and accounts in MS Excel.
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Comment(Item/Account/Acc="Item/Account";Period="Period";Data level="Data level";Adjustment level="Adjustment level";Organization element="Organization element")**
Specifying a data level, adjustment level, and reporting entity is optional. If no element is specified, the user has to choose one of these elements when creating the report.
**Example**
The tilde formula supplies the comment on the item **Technical equipment and machines** in **November 2017**:
'Comment' function
> **Warning:** Currently, comments cannot be added for items or accounts in the CFO Solution Platform. Therefore, the **Comment** function can only be used to retrieve comments that have been added for items or accounts in **Lucanet.Financial Client**.
---
---
title: "Functions in Ledgers and Schedules"
description: "In Lucanet Consolidation & Financial Planning, numerous functions are available in ledgers and schedules, which can be used to create diagrams or export data, for example."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules
language: en
last_updated: 2026-05-01
---
# Functions in Ledgers and Schedules
## Overview
In the **Lucanet CFO Solution Platform**, the following functions are available in ledgers and schedules:
- [Searching in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/search-ledgers-schedules.md)
- [Creating Postings in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/creating-postings-in-ledgers-schedules.md)
- [Displaying and Configuring Charts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/display-configure-diagrams.md)
- [Drill Down in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drill-down.md)
- [Drilling Down to Original Posting Level](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level.md)
- [Exporting Values to MS Excel or as a PDF](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/export-values-excel-pdf.md)
- [Using Keyboard Shortcuts in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/using-keyboard-shortcuts.md)
---
---
title: "Functions in the Detail View"
description: "This article gives an overview of the general functions that are available in the detail view of Consolidation & Financial Planning."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-in-the-detail-view
language: en
last_updated: 2026-05-01
---
# Functions in the Detail View
## Overview
This article gives an overview of the general functions that are available in the detail view of Consolidation & Financial Planning.
## Highlighting Elements or Formatting Elements Bold
You can use the options **Bold format** and **Highlight** to flag certain elements in the tree view of Consolidation & Financial Planning.
To do so, navigate to the detail view of the desired element, open editing mode, and activate the **Bold format** and/or **Highlight** check box.
Which of these formatting options are available depends on the workspace you work in.
Formatting bold and highlighting
> **Warning:** To format elements in bold or highlight them, you need write permissions for the respective workspaces. You can assign read and write permissions in the **User management** workspace of the Lucanet CFO Solution Platform (see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md)).
## Copying Columns
In Consolidation & Financial Planning, column contents in ledgers and schedules can be copied and reused else where. To do so, navigate to the desired table column and copy the column to the clipboard with a **right click | Copy** or **Copy with headers**.
Context menu for copying column contents
## Copying Values
The **Copy values** context menu command can be used in Consolidation & Financial Planning to copy values to a different point within or outside the Lucanet software. To do so, navigate to the desired table value and copy the value to the clipboard with a **right click | Copy values**. Keep the **CTRL** key pressed to copy several values simultaneously.
To copy all values of a column simultaneously, you can click the column header. This automatically marks all cells and allows them to be copied.
Copying values from an account hierarchy
## Calculating the Total and Minimum, Maximum, and Mean Values
In Consolidation & Financial Planning, you can view the total and the minimum, maximum, and mean values of certain values, such as values from the balance sheet on the status bar or values in the **Show postings** dialog. Select the desired values to display the total on the status bar. Click the three dot icon to display the minimum, maximum and mean values.
Example of displaying totals and other values in the balance sheet
---
---
title: "Functions in the Tree View"
description: "This article gives an overview of the general functions that are available in Consolidation & Financial Planning to change the tree view."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-in-the-tree-view
language: en
last_updated: 2026-05-01
---
# Functions in the Tree View
## Overview
This article gives an overview of the general functions that are available in Consolidation & Financial Planning to change the tree view.
## Creating, Copying, Cutting, Pasting, and Deleting Elements
The functions used to create, copy, cut, paste, and delete elements are available in the tree view for certain elements.
For this purpose, navigate to the desired element in the respective tree view, open the context menu and choose the desired function.
(In the tree view of a view, click the three dots icon and choose the desired function.)
'Copy' menu command in the context menu of an item
## Changing the Order of Elements
In **Consolidation & Financial Planning**, you can change the order of elements in the tree view using the context menu command **Change order** **.** You can sort elements alphabetically in the **Change order** dialog, or use drag-and-drop to sort them manually.
'Change order' dialog
## Copying the OID
The **Copy OID** context menu command can be used to copy the OID of an element to the clipboard and then paste it, for example, in MS Word or MS Excel documents.
## Viewing Element Properties
You can use the **Properties** context menu command to display the respective element properties and edit them, for example accounts and items can be configured (see [Elements in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules.md)).
---
---
title: "Functions Used to Change the Display"
description: "This article gives an overview of the functions that are available in Consolidation & Financial Planning to change the display of elements and to show additional information."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-used-to-change-the-display
language: en
last_updated: 2026-05-28
---
# Functions Used to Change the Display
## Overview
This article gives an overview of the functions that are available in Consolidation & Financial Planning to change the display of elements and to show additional information.
## Showing and Hiding Areas
In the **Consolidation & Financial Planning** solution, you can show or hide certain areas using the pfeil oben icon to make it easier to view elements or items and accounts, e.g. in the balance sheet. The areas you can show or hide include the **Status bar,** the **Dimension bar**, the **treeview** and the **detail** view.
Options for showing and hiding certain areas
> **Warning:** To change the order of **views** in the tree view, mark the desired view, hold the mouse button, and move the view to the desired position.
## Defining an Element as Root
In the tree view of ledgers and schedules, you can define an element as the root and hide all other elements on the same level in the hierarchy at the same time. To do so, open the context menu of the desired element and select the **As root** command.
To show all elements in the hierarchy again, select the Full hierarchy command from the context menu.
Defining an element as root
## Expanding and Collapsing Elements
Subordinate levels of elements can be expanded in the tree view to show more details or collapsed to have a better overview. In the tree view, navigate to a folder and open the context menu.
Context menu for expanding an account hierarchy
> **Warning:** In the tree view of the **Reporting and Analyzing** functional area, you can also use the context menu for items and accounts to define whether you want to expand all levels, all items, or all accounts in each case.
## Changing Column Widths
For a better overview, certain or all column widths in tables can be automatically adjusted or the adjustment of the columns reset. To do this, navigate to the header of the desired column and open the context menu to adjust the desired setting.
Menu of a column header in an account hierarchy
## Limiting the Number of Workspaces
The available workspaces can be limited or extended when selecting elements. To do so, click **Select workspaces**, for example, to create a KPI card in the **Dashboard** workspace:
Select workspace when creating or editing a widget
Choose additional workspaces by activating the check boxes or limiting the selection.
## Displaying Additional Information
A comment iconindicates that additional information is stored in the software for a particular entry, e.g. the exact posting date for the display of values of a posting in the **Journals** workspace:
Comment icon with display of a date in the tooltip
---
---
title: "General Functions"
description: "In Consolidation & Financial Planning, cross-platform functions are available to help you, for example, improve clarity, create or move elements, or navigate between them."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions
language: en
last_updated: 2026-05-28
---
# General Functions
## Overview
In **Consolidation & Financial Planning**, cross-platform functions are available to help you, for example, improve clarity, create or move elements, or navigate between them.
In this section, you will find information on the following topics:
- [Using Keyboard Shortcuts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/using-keyboard-shortcuts.md)
- [Functions for Changing the Display](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-used-to-change-the-display.md)
- [Functions in the Tree View](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-in-the-tree-view.md)
- [Functions in the Detail View](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-in-the-detail-view.md)
- [Adding Additional Information to an Element](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/add-further-information-to-elements.md)
- [Executing Multiple Elements Using Workflows](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/executing-elements-using-workflows.md)
---
---
title: "Generating Excel Reports"
description: "Based on the reporting template available in Lucanet and the tilde formulas it contains, an Excel report with the current data from Lucanet can be generated."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report
language: en
last_updated: 2026-05-01
---
# Generating Excel Reports
## Overview
Based on the reporting template available in Lucanet and the tilde formulas it contains, an Excel report with the current data from Lucanet can be generated.
When a reporting template contains placeholders for **organization element, data level, adjustment level, partner, transaction currency, display currency** and/or **period**, you can configure for each of these placeholders whether a value is fixed for the report or can be selected as required.
## Generating Report
To generate a report:
1. Click the reporting template based on which you want to generate the Excel report.
2. In the detail view under **Template properties**, select the dimensions for which the report should be generated.
Which dimensions are displayed and can be selected depends on the [tilde formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas.md) contained in the Excel file and the [configuration of the placeholders](#config).
Template properties and generate report
3. Click **Generate report**.
The report is saved in Excel format in your download directory.
## Configuring Placeholders in the Reporting Template
When a reporting template contains placeholders for **organization element, data level, adjustment level, partner, transaction currency, display currency** and/or **period**, you can configure for each of these placeholders whether a value is fixed for the report or can be selected as required.
To do this, open the **Placeholders** tab and select the desired placeholder from the drop-down list.
Then configure the displayed options, which differ depending on the selected placeholder:
'Placeholders' tab
The following options are available:
| Option | Description |
|---------|---------|
| Value can be selected | Activate if the value for the placeholder should be configurable before report generation and then enter a **label**. |
| Value has been predefined | Activate if the value should not be selectable. If you choose this option, a report can only be generated for the specified period and/or the default value. |
| The following values can be selected | Only available for data levels. Specifies whether **All data levels** or **Only planning data levels** can be selected for report generation. |
| Periodicity | Only available for periods. Defines whether a month, a quarter, or a year can be selected for report creation. |
| Period count | Only available for periods. Count of periods covered by the report. When generating the report, the user can then specify the report period instead of selecting the report start period. |
---
---
title: "Import and Journals"
description: "A journal is a combination of a data level and a reporting entity or a consolidation area. A journal contains all postings and all underlying posting documents that enable you to understand the details of all postings."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals
language: en
last_updated: 2026-05-01
---
# Import and Journals
In the **Import and Journals** functional area, data can be imported into reporting entities. In addition, you can view postings and data imports created in Lucanet.Financial OLAP Server.
- In the [Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) workspace, you can access postings and data imports.
- In the [Importing data into reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities.md) workspace, you can create and execute data imports into reporting entities.
- In the [Importing Data into Lucanet.Financial Warehouse](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh.md) workspace, the import into Lucanet.Financial Warehouse is configured and executed.
- In the [Period locks](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks.md) workspace, data imports, postings, data transfers from MS Excel, and entries in exchange rate tables can be locked or unlocked.
Functional area 'Import and Journals'
- [Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md)
- [Importing Data into Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities.md)
- [Importing data into Lucanet.Financial Warehouse](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh.md)
- [Configuring Period Locks](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/configure-period-locks.md)
---
---
title: "Importing Data Collection Postings into CFP"
description: "You can pull posting data from a Data Collection process into Consolidation & Financial Planning and import it as postings into reporting entities."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/importing-dc-postings
language: en
last_updated: 2026-10-06
---
# Importing Data Collection Postings into CFP
## Overview
To import postings from Data Collection into Consolidation & Financial Planning (CFP), you set up an integration in the CFP workspace **Importing data into reporting entities**. CFP requests posting data from a Data Collection process and imports the returned postings into the selected reporting entities.
The integration uses the existing workflow for a [data source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md) of type **Provision via script** with a dedicated **Import from DC** script.
> **Note:** Posting data is exported only from **CFP Pivot table** elements in the Data Collection form template (see [Configuring Tables in Form Templates](https://support.lucanet.com/en/documentation/data-collection/basic-configuration-dc/creating-and-configuring-form-templates/configuring-tables-in-form-templates.md#adding-columns-in-data-collection) for more information).
## Prerequisites
Before you can import postings from Data Collection into CFP, the following must be set up:
- A CFP user account with full **Editor** rights configured in **Administration** (see [Defining User Permissions](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md))
- The **Import from DC** script available in your CFP environment. The script is not available by default — contact your Lucanet representative to have it set up.
- An **assignment table** that maps Data Collection dimension codes to the corresponding CFP elements created in CFP (see [Creating Assignment Tables](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-assignment-table.md))
- Both the **Import Data** and **DC-SchedulePostings** [adjustment levels](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-script.md) created in CFP — a CFP dimension that separates values by their origin or purpose, so that the same account in the same period can hold different values on different adjustment levels
- The reporting entities used in the Data Collection process configured in CFP
## Creating and Configuring the Data Source
The data source determines which script CFP executes and which data levels, adjustment levels, dimensions, and reporting entities the import uses. You create and configure it once, before you create any data import that relies on it.
For a description of each field on the data source, see [Provision via script (\#2075)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-script.md). The values below are the ones that apply to Data Collection.
To create and configure the data source:
1. Navigate to **Import and Journals | Importing data into reporting entities | Data sources**.
2. Create a data source of the type **Provision via script** and select it in the structure view (see [Defining the Data Source for the Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).
3. Click **Edit** in the top right corner. The detail view of the script is displayed as follows, for example:
Detail view of the 'Import from DC' data source
4. On the **General** tab, add the **Lucanet Data Collection #3744-DC.REST-JSON.FOS v1.0.0** script to the script list.
5. Still on the **General** tab, configure the following:
- **Data levels**: Add **Actual**. Data Collection collects actual data only; planning data is not supported.
- **Adjustment levels**: Add at least **Import Data** and **DC-SchedulePostings**. **Import Data** is the default for postings generated from Balance Sheet, P&L, and Statistical Ledger tables; **DC-SchedulePostings** always receives postings generated from Schedule tables. If the amount source column carries CFP adjustment level metadata, that adjustment level is used instead and its postings go into a separate posting document.
- **Dimensions**: Activate the dimensions into which the Data Collection postings are imported: **Account**, **Partner**, **Cost center**, and **Transaction type**.
- **Cost centers in the Balance Sheet**: Select **Use specified cost centers** so that the actual cost centers from Data Collection are used.
6. On the **Reporting entities** tab, add the reporting entities whose Data Collection postings you want to import. Only reporting entities added here are available for selection when you execute the import.
7. Click **Save** in the top right corner.
## Creating the Data Import
The data import references the data source you configured and adds the assignment table that translates Data Collection dimension codes into CFP elements.
To create the data import:
1. Navigate to **Import and Journals | Importing data into reporting entities | Data imports.**
2. Optionally, create a dedicated folder for imports from Data Collection by right-clicking the **Data Imports** root folder and choosing **Create | Folder**.
3. Right-click the newly created folder, or the **Data Imports** root folder, and choose **Create | Data Import**. The **New Data Import** dialog is displayed:
'New Data Import' dialog
4. Enter a name for the data import.
5. In the **Data source** field, select the data source that executes the **Import from DC** script.
6. In the **Assignment table** field, select the assignment table that maps Data Collection dimension codes to CFP elements.
7. Click **Save**.
> **Note:** **Configure** next to the **Data source** field reopens the configuration of the selected data source. Any change you make there applies to every data import that uses this data source.
## Importing the Postings
The import is executed form by form — each execution imports the postings from one specific Data Collection form.
To import the postings from a Data Collection form:
1. Open the data import and click **Edit** in the top right corner. The **1. Import** option becomes available.
2. Click **1. Import**. The **Provision via script** dialog is displayed:
'Provision via script' dialog
> **Warning:** Configure the **Lucanet Data Collection #3744-DC.REST-JSON.FOS v1.0.0** tab first. If you make changes on the **Configuration** tab first, the process list does not load correctly.
3. On the **Lucanet Data Collection #3744-DC.REST-JSON.FOS v1.0.0** tab, click **Refresh process list**. The list refreshes with all available Data Collection processes and their corresponding forms.
'Refresh process list' button
4. In the **Process** drop-down list, select the form whose postings you want to import.
5. On the **Configuration** tab, configure the following:
- **Reporting entity(s)**: Select at least one of the reporting entities configured in the data source.
- **Import type**: Select **Balances (cumulated values)** or **Transaction figures**.
- **Fiscal year**: Enter the fiscal year to import.
- **Accounting periods**: Enter the first and last accounting period to import.
6. Click **Save**. CFP retrieves the posting data from Data Collection and imports the returned postings.
7. Click **2. Assign** to assign the imported data to the corresponding elements in the Lucanet database (see [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)).
8. Click **3. Save** to save the data import.
The **Postings** section of the data import displays the postings created during the last execution, with their reporting entity, data level, period, transaction currency, and adjustment level.
## Finalizing the Data Import
Once the imported postings are correct, you can finalize the data import to prevent it from being changed or deleted. To do so, right-click the data import in the tree view and choose **Finalize data import** (see [Finalizing a Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/completing-data-import.md)).
> **Note:** - Posting documents generated from balance sheet and P&L tables must balance per reporting entity.
> - Posting documents generated from statistical ledger tables do not need to balance and are not validated for balance by CFP.
---
---
title: "Importing data into Lucanet.Financial Warehouse"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh
language: en
last_updated: 2026-05-01
---
# Importing Data into Lucanet.Financial Warehouse
## Overview
The import into Lucanet.Financial Warehouse is configured and executed in the workspace **Importing data into Lucanet.Financial Warehouse**.
- The steps that have to be executed in principle to import data into Lucanet.Financial Warehouse are described in [All Steps at a Glance](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/all-steps-data-import-lnfwh-entities.md).
- The procedure for importing data into Lucanet.Financial Warehouse is described in [Data Import Procedure](#Impflow).
You can go here directly to the detailed description of the individual steps:
- [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh.md)
- [Creating Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)
- [Creating and Configuring a Data Transformation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-data-transformation.md)
- [Creating and Configuring Execution Settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-execution-settings.md)
- [Execute import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/execute-data-import.md)
## Importing Data into Lucanet.Financial Warehouse as a Video
The video provides you with the most important information on the topic of **defining a data source, creating execution settings, and executing the data import**:
Video: https://player.vimeo.com/video/1201751079?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** Uploading scripts and configuring data transformations are not covered in the video. For the complete sequence of steps, see [All Steps at a Glance](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/all-steps-data-import-lnfwh-entities.md).
## Data Import Procedure
An **ETL process** (ETL = Extract, Transform, Load) is used to import data from a different system into Lucanet. The data are first extracted from the source system, then transformed, and finally loaded to Lucanet.Financial Warehouse.
When importing data into Lucanet.Financial Warehouse, the data are initially imported into the **temporary** Lucanet.Financial Warehouse. The transformation rules (see [Creating and Configuring Data Transformations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/create-and-configure-data-transformation.md)) are then applied to the data and the data are subsequently written into the persistent Lucanet.Financial Warehouse.
The following figure indicates how the data import into Lucanet.Financial Warehouse is performed:
Process for the Data Import into Lucanet.Financial Warehouse
---
---
title: "Importing Data into Reporting Entities"
description: "In the 'Importing data into reporting entities’ workspace, the import of data from Excel files into the current database on Lucanet.Financial OLAP Server can be configured and executed."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities
language: en
last_updated: 2026-05-01
---
# Importing Data into Reporting Entities
## Overview
In the **Importing data into reporting entities** workspace, the import of data into the current database on **Lucanet.Financial OLAP Server** can be configured and executed. The data can originate from an Excel file, from a script, or from **Lucanet.Financial Warehouse** (see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).
The steps that have to be executed in principle to import data are described in [All Steps at a Glance](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/all-steps-data-import-reporting-entities.md).
You can go here directly to the detailed description of the individual steps:
- [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)
- [Creating an Assignment Table](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-assignment-table.md)
- [Creating and Executing the Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)
- [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)
- [Finalizing Data Import](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/completing-data-import.md)
## Importing Data into Reporting Entities as a Video
The video provides you with the most important information on the topic of **creating an assignment table, defining a data source, executing the data import, and assigning data**:
Video: https://player.vimeo.com/video/1201752011?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video uses **Lucanet.Financial Warehouse** as the origin of the data and continues the import configured under [Importing Data into Lucanet.Financial Warehouse](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh.md), with the same fiscal year and accounting periods.
---
---
title: "Importing Exchange Rates"
description: "Exchange rates for exchange rate tables can either be queried from the European Central Bank or imported from MS Excel."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/import-exchange-rates
language: en
last_updated: 2026-05-01
---
# Importing Exchange Rates
## Overview
Exchange rates for exchange rate tables can either be queried from the European Central Bank or imported from MS Excel.
## Importing Exchange Rates from the ECB
Exchange rates can be queried online from the ECB and imported at the same time into one or more exchange rate tables. All the EURO exchange rates of these currencies, as well as all the exchange rates between these currencies, can be queried.
To call up the exchange rates from the ECB:
1. Right-click the root folder **Exchange rate tables** or an individual exchange rate table.
2. Choose **Import | Import exchange rates from European Central Bank** from the context menu **.** The **Import Exchange Rate From European Central Bank** dialog is displayed:
‘Import Exchange Rate From European Central Bank’ dialog
3. Specify the **exchange rate table**, **data level**, and **period**.
4. Click **Import**.
> **Note:** - All of the exchange rates in the selected data levels and in the selected time period defined in Lucanet are updated on the basis of the exchange rates from the ECB.
> - The most recently available exchange rate of the respective month is used as the closing exchange rate.
> - The average exchange rate is determined in Lucanet by calculating the average using the daily closing exchange rates of the month. This means that the ECB calculation method is used.
## Importing Exchange Rates from MS Excel
To import exchange rates from MS Excel:
1. Right-click the **Exchange rate tables** root folder.
2. Choose **Import | Import exchange rates from MS Excel** from the context menu.
3. Navigate to the desired file and click its name.
4. Click **Import** or press Enter to start the import.
> **Note:** The import can be carried out successfully only if the structure of the Excel file matches the structure of an exchange rate file export file (see [Exporting Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/export-exchange-rates.md)).
---
---
title: "Installing and Updating Lucanet.Script Execution Application"
description: "Lucanet.Script Execution Application (SEA for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script. On this page, you can find out how to install and update SEA."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea
language: en
last_updated: 2026-05-01
---
# Installing and Updating Lucanet.Script Execution Application (SEA)
## Overview
**Lucanet.Script Execution Application** ( **SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the **Lucanet CFO Solution Platform** using an ETL script.
SEA must be installed as a system service in your local environment via **Lucanet.Software Manager** to enable communication with the source system. That means SEA must be installed in the same network as the source system or the source file. The application executes the required scripts locally to extract, transform, and load data from local ERP/financial systems. Subsequently, the data is securely transferred to **Lucanet.Financial OLAP Server** or **Lucanet.Financial Warehouse** in the AWS cloud.
> **Note:** **Lucanet.Software Manager 11** is required for the installation and use of Lucanet SEA.
Before you install SEA, review [Lucanet SEA: System Requirements and Network Configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea/sea-system-requirements.md) so that your IT department can prepare the server and allow the required ports and endpoints in the firewall.
## Installing and Configuring SEA as a Video
The video provides you with the most important information on the topic of **installing and configuring SEA**:
Video: https://player.vimeo.com/video/1201751078?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
The installation and configuration of SEA is carried out in the following steps:
## Creating SEA Instance in the Lucanet CFO Solution Platform
To create an SEA instance in the Lucanet CFO Solution Platform, proceed as follows:
1. If necessary, click **Administration** in the main menu.
2. Click **Platform management | Certificates**. The **Certificates** workspace is displayed as follows, for example:
'Certificates' workspace
3. Click **Generate instance**.
4. Enter the name of the instance in the displayed **Generate instance** dialog.
5. Click **Generate**. The instance is created and displayed in the overview.
6. Click the three-dot icon of the corresponding instance to open the context menu.
7. Click **Download sender** to save the sender certificate locally as a ZIP file.
8. Click **Download receiver** to save the receiver certificate locally as a ZIP file.
> **Note:** More Information about the **Certificates** workspace in the Lucanet CFO Solution Platform can be found under [Generating and Downloading SEA Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md).
## Installing Lucanet.Script Execution App in Lucanet.Software Manager
To install Lucanet.Script Execution Application as a system service in Lucanet.Software Manager:
1. If necessary, update Lucanet.Software Manager to version 11.
2. Start Lucanet.Software Manager.
3. Click the **Install application** tab.
4. Retain the **Retrieve application from Lucanet.Youniverse** presetting and click **Next**.
5. Choose **Lucanet.Script Execution Application** and click **Continue**. Lucanet.Software Manager displays the Settings:
Installing SEA in Lucanet.Software Manager
6. If necessary, change the name in the **Name** input field.
7. Choose the latest version from the **Version** drop-down list.
8. From the drop-down list **Download from**, choose from which download server SEA should be installed. The following options are available:
- Choose **Determine fastest connection automatically** if Lucanet.Software Manager shall determine the download server automatically.
- Choose the desired download server from the drop-down list.
9. After **Configuration file**, upload the ZIP file for the **Receiver** certificate that you downloaded from the CFO Solution Platform in step 1.
10. Define how the service is to be started. Do one of the following:
- Choose **Automatic** if the service is to be started automatically when starting the computer.
- Choose **Manually** if the service is to be started manually.
11. Activate the **Start service after installation** check box if the service is to be started after installation.
12. Click **Install**. The Lucanet.Script Execution Application is installed on your computer as a system service.
13. Click **Finished** when the message **Installation completed** is displayed.
## Creating SEA Applications in the CFO Solution Platform
Before an SEA instance can be used to execute ETL scripts, it must first be created as an application in the **Consolidation & Financial Planning** solution in the CFO Solution Platform. To do so, proceed as follows:
1. Click **Consolidation & Financial Planning** in the main menu to open the solution.
2. Navigate to the **Imports and Journals | Scripts** workspace.
'Scripts' workspace and 'Applications' button
3. Click **Applications**. The **Create new application** dialog is displayed as follows, for example:
'Create New Application' dialog
4. Click **Browse** or use the drag-and-drop function in the **Archive key file** area to upload the ZIP file for the **Sender** certificate that you downloaded from the CFO Solution Platform in step 1.
5. Click **Save**. The SEA application is created and displayed in the Applications list.
> **Warning:** If the ETL script used for data import from the source system into Lucanet.Financial OLAP Server or Lucanet.Financial Warehouse is to be executed via an SEA application, you must assign the SEA application to the script in the configuration of the data sources.
>
> For more information, see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh.md).
## Updating Lucanet.Script Excecution Application
The update of the Lucanet.Script Execution Application is carried out in Lucanet.Software Manager. To do so, proceed as follows:
1. If necessary, open Lucanet.Software Manager.
2. Select the SEA instance for which you want to check for an update on the **My Applications** tab.
3. Click **Check for updates**. The **Check for updates** dialog is displayed, for example, as follows when a new version is available:
Check for available SEA updates
4. Click **Yes**. The SEA instance is being updated.
---
---
title: "Installing the CFP Add-In for Excel 365"
description: "To be able to work with the CFP Add-in for Excel 365, you first need to install the add-in in MS Excel. After having successfully installed the add-in, you can connect the add-in to your Lucanet database."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/installing-cfp-add-in
language: en
last_updated: 2026-05-01
---
# Installing the CFP Add-in for Excel 365
## Overview
To be able to work with the CFP Add-in for Excel 365, you first need to install the add-in in MS Excel. After having successfully installed the add-in, you can connect the add-in to your Lucanet database.
> **Warning:** The Lucanet CFP Add-in for Excel can only be used with the **Consolidation & Financial Planning** solution in the **Lucanet CFO Solution Platform**.
>
> The add-in cannot be used with Lucanet.Financial Client.
## Installing the CFP Add-in for Excel 365 from the Add-Ins Store
To install the CFP Add-In for Excel 365 from the Excel Add-Ins Store:
1. Open MS Excel (in your browser or locally).
2. On the Excel ribbon menu, open the **Home** tab.
3. Open the **Add-ins** drop-down menu and search for the **Lucanet CFP Add-in for Excel 365**.
Searching for the add-in in MS Excel
4. Click **Add** to add the add-in.
After the installation, the add-in is displayed as a new ribbon menu in MS Excel:
CFP Add-in ribbon menu in MS Excel
## Installing the CFP Add-In for Excel 365 via Centralized Deployment
If you do not have access to the Excel Add-In Store due to your company's security settings, you can also install (or have installed) the CFP Add-In for Excel 365 via centralized deployment.
In this case, you can download a current manifest file for the CFP Add-In for Excel 365 [here](https://lnag.sharepoint.com/:u:/s/hubkm/IQCrBWkdkfUESq_76o4tuOGJAYpwT2aquCynVVFyrZAwFXw) and forward it to your IT administration, who can then install the add-in for you.
## Connecting the CFP Add-in for Excel 365 to Lucanet
Proceed as follows to connect the CFP Add-in for Excel 365 to your Lucanet database:
1. Open the **Lucanet CFP Add-in** ribbon menu and click **Log in**.
2. Copy the URL of your Lucanet CFO Solution Platform, for example `example.platform.lucanet.cloud`.
3. In the **Lucanet CFP Add-in** panel on the right-hand side, paste the URL and click **Login**.
CFP Add-in panel to enter database data
---
---
title: "Journals"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale
language: en
last_updated: 2026-06-03
---
# Journals
A **journal** is a combination of a **data level** and a **reporting entity** or a **consolidation area**.
A **journal** contains all postings and all underlying posting documents that enable you to understand the details of all postings.
> **Tip:** The **Journals** workspace corresponds to the **Postings** workspace in Lucanet.Financial Client.
Video: https://player.vimeo.com/video/857844083?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
- [Using Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/use-journals.md)
- [Postings in Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/postings-journals.md)
- [Creating and Configuring Postings in Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/create-configure-posting-reporting-entity.md)
- [Translation with Historical Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/translation-historical-exchange.md)
---
---
title: "LUCANET Formulas"
description: "To allow MS Excel to access Lucanet data, specific, precisely-defined formulas must be entered in the corresponding Excel cells. The formulas are similar to Excel formulas and always consist of a formula name as well as required and optional parameters."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/lucanet-formulas
language: en
last_updated: 2026-05-01
---
# LUCANET Formulas
## Overview
To allow MS Excel to access Lucanet data, specific, precisely-defined formulas must be entered in the corresponding Excel cells. The formulas are similar to Excel formulas and always consist of a formula name as well as required and optional parameters.
## Structure of LUCANET Formulas
The general structure for LUCANET formulas is as follows:
```
=LN.FORMULA NAME("Parameter_1","Parameter_2",...,"Parameter_x")
```
## Rules for LUCANET Formulas
The following rules must be followed in LUCANET formulas:
- Parameter must be specified in quotation marks.
- Parameters are separated by a semicolon.
**Note**: The parameters are separated with the list separator specified under **Regional and Language Options** in the **Windows Control Panel**. If your company uses different language versions of Windows, you must use a semicolon instead of a comma.
- No distinction is made between upper case and lower case.
- Cell links can be used in a LUCANET formula.
- Cell links are separated using a comma.
## Meaning of the Formula Elements
In a LUCANET formula, the formula name specifies the type of information to be queried. The parameters used determine the data or values to be queried. Depending on the structure of the formula this is how different values and information can be queried from Lucanet.
The data that can be queried with LUCANET formulas are:
- Values
- Exchange rates
- Comments
- Attributes
---
---
title: "Lucanet SEA: System Requirements and Network Configuration"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea/sea-system-requirements
language: en
last_updated: 2026-06-15
---
# Lucanet SEA: System Requirements and Network Configuration
## Overview
**Lucanet.Script Execution Application** (**SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script.
This page provides the technical information that your IT department needs to prepare a SEA installation: the system architecture (topology), the system requirements, and the network and firewall configuration (ports and endpoints to allow).
> **Note:** For the step-by-step installation instruction, see [Installing and Updating Lucanet.Script Execution Application](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md). To generate the required certificates, see [Generating and Downloading SEA Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md).
## System Architecture
SEA runs as a system service inside your local network, in the same environment as your source system. It executes ETL scripts locally to extract, transform, and load data from your on-premises ERP/financial systems, and then transfers the results securely to **Lucanet.Financial OLAP Server** or **Lucanet.Financial Warehouse** in Lucanet.Cloud (AWS).
Because Lucanet.Cloud cannot initiate connections into your network, SEA establishes all connections **outbound**: it connects to **AWS IoT Core** to receive its tasks and to **Lucanet.Financial OLAP Server** to exchange data. SEA is in turn the only component that accesses your ERP/source system inside your network.
Depending on whether your source system offers an interface or only export files, one of the following topologies applies.
### Data Access via Interface
If your source system has an interface that allows access to its database or application server, SEA accesses the source system directly, reads the data via an ETL script, and transfers it to **Lucanet.Financial Warehouse**. While doing so, SEA must be connected to **Lucanet.Financial OLAP Server** in **Lucanet.Cloud** via HTTPS (SSL/TLS). SEA should be installed centrally on a single server that can access the source system.
Lucanet SEA: data access via interface
### Using Export Files
If your source system does not offer such an interface, the data must be extracted from the source system using export files. Because export files cannot be stored in **Lucanet.Cloud**, they must be stored locally in your environment. During the ETL process, SEA must be able to access the export files and be connected to **Lucanet.Financial OLAP Server** in **Lucanet.Cloud** via HTTPS (SSL/TLS).
Where you install SEA depends on where the export files are stored.
#### Export Files on a Shared Folder
We recommend storing the export files on a shared folder (network share). SEA then only needs to be installed on a single server that can access the shared folder.
Lucanet SEA: export files on a shared folder
For SEA to read the export files, the account that the SEA service uses to log on must have read permission for the network path where the export files are stored. This account is configured in your operating system, for example in the Windows **Services** console. To change the account:
1. Open the **Services** console (`services.msc`).
2. Right-click the **Lucanet.Script Execution Application** service and select **Properties**.
3. On the **Log On** tab, set the account that the service uses.
The **Log On** tab is displayed as follows, for example:
'Log On' tab of the SEA service
#### Export Files in Local Folders
If the export files are stored in local folders instead, SEA must be installed on each user's computer so that it can access those local folders.
Lucanet SEA: export files in local folders
> **Note:** In all topologies, the connection between SEA and Lucanet.Financial OLAP Server is encrypted with **SSL/TLS (1.2 or higher)**, marked with an asterisk (*) in the diagrams. In addition, SEA connects to AWS IoT Core over **port 8883** (or **port 443** over WebSockets); see the [Network and Firewall Configuration](#network-and-firewall-configuration) section below.
## System Requirements
### Prerequisites
Before you can install SEA, the following prerequisites must be met:
- **Lucanet.Software Manager 11 (2503+4) or higher** must be installed.
- A valid certificate must be generated and downloaded from the Lucanet CFO Solution Platform (see [Generating and Downloading SEA Certificates](https://support.lucanet.com/en/documentation/administration/platform-management/certificates.md)).
### Hardware Requirements
The minimum hardware requirements for each computer running SEA are:
| Component | Minimum requirement |
|---|---|
| CPU | At least 2 CPU cores (4 CPU cores recommended) |
| RAM | At least 8 GB |
| Internal network connection | At least a 1 Gbit connection (10 Gbit recommended) |
| Internet connection | At least a 16 Mbit connection |
| Storage/hard drive | 500 MB or more |
### Operating System
SEA runs on the following operating systems:
- **Microsoft Windows**: all currently supported operating system versions
- **Unix/Linux**: all common maintained distributions, especially CentOS, Debian (version 7 and later), and SUSE
## Network and Firewall Configuration
SEA and Lucanet.Software Manager (which is used to install and update SEA) only establish **outbound** connections. To install and operate SEA, your IT department must allow the following connections through the firewall and through any proxy or endpoint-security software.
### Connections, Ports, and Endpoints
| Connection (outbound) | Target address | Port | Notes |
|---|---|---|---|
| AWS IoT Core (task queue) | Region-specific AWS IoT Core endpoint on amazonaws.com (see note below) | 8883 (or 443) | MQTT over TLS (port 8883), or MQTT over WebSockets with TLS (port 443). Required: SEA registers with AWS IoT Core over port 8883. |
| Lucanet.Financial OLAP Server | platform.lucanet.cloud, lucanet.cloud | 443 | HTTPS (TLS 1.2 or higher). Used during script execution. |
| ERP/source system | Customer-internal address (varies) | Depends on source system | SEA connects directly within your network. |
| Lucanet.Financial Warehouse | Tunneled through Lucanet.Financial OLAP Server | — | Normally no separate firewall rule required. |
| Installation and updates (Lucanet.Software Manager) | youniverse.lucanet.com, cdn.lucanet.com (cdn.lucanet.cn) | 443 | HTTPS (TLS). Used by Lucanet.Software Manager to download and update the SEA program components. Required for installation and updates, not at runtime. |
> **Warning:** The AWS IoT Core endpoint is **not the same for every installation**. It follows this pattern, where `` and `` are placeholders:
>
> `-ats.iot..amazonaws.com`
>
> - `` is unique per AWS account, for example `a1b2c3d4e5f6g7`.
> - `` is the AWS region where your environment is hosted, for example `eu-central-1` for Frankfurt.
>
> For an environment hosted in Frankfurt, the full endpoint is therefore, for example, `a1b2c3d4e5f6g7-ats.iot.eu-central-1.amazonaws.com`. The prefix and region are specific to your installation.
>
> If your firewall cannot allow individual, dynamically generated endpoints, allow the pattern `*-ats.iot..amazonaws.com` instead.
Proxy and PAC (auto-configuration) scripts must not block or rewrite the connections listed above.
### Antivirus and Endpoint-Security Exclusions
To prevent antivirus or endpoint-security software from interfering with SEA, exclude the following directories:
```text
C:\ProgramData\LucaNet
C:\Program Files\LucaNet
```
These are the default Lucanet installation directories.
## Security
- SEA only executes specific, approved tasks.
- A one-time code/session token is used for each ETL script execution.
- All communication is encrypted (to AWS IoT Core and to Lucanet.Financial OLAP Server in the cloud).
- Data processing takes place entirely within your network. Only the aggregated result data is transferred to Lucanet.Financial OLAP Server.
---
---
title: "Lucanet.Excel-Reporting"
description: "Lucanet.Excel-Reporting is used to create standard reports that can be distributed as required and displayed without a Lucanet account or an internet connection. Reports are created and configured directly on the CFO Solution Platform, based on reporting templates saved in Lucanet."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting
language: en
last_updated: 2026-05-01
---
# Lucanet-Excel-Reporting
**Lucanet.Excel-Reporting** is used to create standard reports that can be distributed as required and displayed without a Lucanet account or an internet connection. Reports are created and configured directly on the CFO Solution Platform in a [workspace configured for this purpose](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/configure-workspace-excel-reporting.md).
All reports are created based on [reporting templates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/create-and-edit-reporting-templates.md) that are saved in Lucanet. Excel files can be used as reporting templates.
The data are queried from Lucanet using [tilde formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas.md) that are defined in the reporting templates.
The [generated Excel reports](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md) do not contain specific macros or references to the database and can therefore be forwarded as required.
> **Warning:** The **macros** included in **XLSM files** are not run when creating Excel reports with Lucanet.Excel-Reporting. The macros are, however, retained when XSLM files are uploaded to Lucanet so that macros in the generated report can be run using MS Excel.
## Supported Excel Versions
Lucanet.Excel-Reporting supports **XLS**, **XLSX**, and **XLSM files** from the following Excel versions, depending on the operating system:
| MS Windows | macOS |
|---|---|
| MS Excel 2016 to 2021 | MS Excel 2021 for macOS |
| MS Excel 365 | MS Excel 365 for macOS |
- [Configuring Workspaces](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/configure-workspace-excel-reporting.md)
- [Creating Reporting Templates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/create-and-edit-reporting-templates.md)
- [Working with Tilde Formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas.md)
---
---
title: "Lucanet.Financial Warehouse (#2068)"
description: "After creating a Lucanet.Financial Warehouse (#2068) data source, the settings for importing data from Lucanet.Financial Warehouse are configured in the detail view of the data source."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh
language: en
last_updated: 2026-09-07
---
# Lucanet.Financial Warehouse (\#2068)
## Overview
After creating a **Lucanet.Financial Warehouse (#2068)** data source, the settings for importing data from Lucanet.Financial Warehouse are configured in the detail view of the data source.
## General Properties
The following general properties of the data source can be configured in the upper area of the detail view:
| Option | Description |
|---------|---------|
| Name | Name of the data source |
| Drill down to posting level | Script for drill-down to posting level **Drill down for direct access to Lucanet.Financial Warehouse (#5015)** (optional) |
| Display scanned documents | Script that enables the display of scanned documents (optional) |
| Executed on | Execution location for the script selected in **Display scanned documents**: **Execute on server** or one of the configured **[Script Execution Application (SEA)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md)** instances.
**Note:** This field is only displayed if a script is selected in **Display scanned documents**. It is used as the default execution location when a user opens the original document via the **Show Postings** dialog (see [Drilling Down to Original Posting Level](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level.md)). |
## 'Configuration' Tab
The **Configuration** tab is divided into three subordinate tabs: **General**, **Reporting Entities**, and **Lucanet.Financial Warehouse**.
### 'General' Tab
The **General** tab consists of the following sections:
### Update Lucanet.Financial Warehouse
Updating Lucanet.Financial Warehouse
If necessary, in the **Data Source for Lucanet.Financial Warehouse** column, select the data sources from which Lucanet.Financial Warehouse is to be updated before data import. All data sources from the **Importing Data into Lucanet.Financial Warehouse** workspace can be selected.
### The following data are imported
Options for importing data
Specify which data are to be imported. The following options are available:
| Option | Description |
|---|---|
| **Values** | Values to be imported: - **Posting documents and opening balance sheet values:** Activated by default - **Statistical values:** Optional. If activated, you must enter the code for at least one value category in the displayed **StatisticValueCategoryCode** column. |
| **Import type** | The desired import type: - Transaction figures or balances (selection when importing) - Transaction figures - Balances - Balances - schedules only - Transaction figures incl. automatic contra entry (only planning) - Opening balance sheet values |
| **Data levels** | Data levels into which the data are to be imported.
Enter the name of the data level in the **DataLevelCode** column. |
| **Adjustment levels** | Adjustment levels into which the data are to be imported.
Enter the name of the adjustment level in the **AdjustmentLevelCode** column. |
| **Accounting periods per year** | Number of accounting periods per year (default: 12)
- If you specify a number greater than 12, all periods greater than 12 are imported by default into period 12. You have the option to specify whether the additional periods are to be imported with a suffix into separate adjustment levels. - If you specify a number greater than 12, then it is only possible to import transaction figures. |
### The following dimensions are imported
Selection of dimensions to be imported
Specify which dimensions are to be imported. The **Account** dimension is always activated. If necessary, change the displayed dimension code in the **DimensionCode** column.
**Cost centers in the Balance Sheet**: If the use of the **Cost center** dimension is activated, you can specify whether a drill down by cost centers should be performed in the balance sheet:
- **Use default cost centers always (recommended)**: The default cost center is used
- **Use specified cost centers**: The cost center whose code was specified for the dimension **Cost center** will be used
### Reclassify values
Options for reclassifying values
If necessary, specify whether you want to **reclassify values** during the data import. The following options are available:
| Option | Description |
|---|---|
| **Present intercompany postings on separate accounts** | Accounts and partner for intercompany postings.
If the use of the **Partner** dimension is activated, the corresponding accounts and partners can be specified in the **Accounts to be analyzed** table. |
| **Attach suffix to account name** | Suffix for the account name.
Specify the desired suffix in the displayed **DimensionCode** field. |
| **Reclassify debtors with credit balances and creditors with a debit balance** | Reclassification of debit or credit balances when importing balances or opening balance sheet values.
Specify the desired code in the **DimensionCodefor the ‘Subledger account’ dimension** field. In the **Accounts to be analyzed** area, the account range ( **Account from** and **Account to**) and the balances to be reclassified ( **Credit** or **Debit**) must be specified. |
### The following currencies are imported
Selecting the currency or currencies to be imported
Specify the currencies to be imported.
### 'Reporting Entities' Tab
'Reporting entities' tab
### Specifying Reporting Entities
If necessary, specify the reporting entities that are to be available for selection when importing the data.
The following fields must be specified for each reporting entity:
| Option | Description |
|---------|---------|
| Displayed name | The name displayed to the user during the data import when selecting the reporting entities to be imported |
| Abbreviation in Lucanet | An abbreviation that can be used to derive the complete cost center description (e.g. **Holding** for the cost center **Holding.Personnel Costs**) |
| ID in the data source | The name or technical ID of the reporting entity in the data source |
| First month of the fiscal year | The number of the month in which the company’s fiscal year begins (e.g. **5** for May, **1** for January) |
### Splitting Data Imports During First Execution
Activate the **Split data imports during first execution** check box to split the data import into multiple import files. When the data import is executed for the first time, a separate import file is created for each defined reporting entity. If you do not activate the check box, one import file is created for the entire data import.
> **Tip:** By splitting a data import by reporting entities, subsequent **[updates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/update-data-imports.md)** can in some cases be performed **much faster**, since complete data imports are not updated each time, but rather individual reporting units separately.
The following additional options are available for splitting and/or combining data imports:
| Option | Description |
|---|---|
| **Categorize data imports** | Using **categories**, import data from multiple reporting entities can be combined into one import file.
When activated, the **Category** column is displayed in the reporting entities table. For reporting entities whose import data are to be combined into one import file, the same category must be specified in the **Category** column.
**Note:** Data imports from multiple reporting entities cannot be combined into one import file and split into different folders at the same time using categorization. It is, however, possible to use different categories within a folder. |
| **Use folder** | Using **folders**, generated import files can be distributed to different folders. When activated, the **Folder** column is displayed in the reporting entities table. For reporting entities whose import files are to be stored in the same folder, the same folder name must be specified in the **Folder** column.
The folders including the generated import files are automatically created under **Data Imports** during import. |
| **Adjust name of the month** | A prefix and/or a suffix can be added to the name of the generated import files: - **Use prefix**: Select from the drop-down list (Year, Accounting period, Accounting period and year, Period, Category) - **Use suffix**: Select from the drop-down list (Year, Accounting period, Accounting period and year, Period, Category) |
### 'Lucanet.Financial Warehouse' Tab
Lucanet.Financial Warehouse connection information
The following connection information must be specified on the **Lucanet.Financial Warehouse** tab:
| Option | Description |
|---|---|
| **Database** | The desired database system |
| **Database parameters** | Configuration of the required database parameters and the access data of the technical user ( **User** and **Password**)
The parameters to be specified depend on the chosen database.
**Note:** In the section [Configuring Database Connections](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-lnfwh/defining-data-source-lnfwh/datenbankverbindungen-konfigurieren.md), you can find a table with the default parameters that must be specified, depending on the selected database. |
| **Test connection** | Test whether a connection can be established with the configured database |
| **Analyze database** | Run read-only SQL queries against the configured database, for example to verify that data was imported correctly.
For more information, see [Analyzing Databases](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database.md). |
## 'Uses' Tab
The elements that use the data source are displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column.
'Uses' tab
---
---
title: "Migrating From Integrated Excel.Add.-in to CFP Add-in for Excel 365"
description: "Customers who used the integrated Lucanet.Excel.Add-in (XLAM) can use a migration assistant to convert legacy formulas with the syntax LUCANET(...) to the formula syntax LN.FORMULA NAME (...) used by the Lucanet CFP Add-in for Excel 365.\n\nThe assistant scans all used cells in all worksheets of the current workbook and replaces supported legacy formulas with their LN.* equivalents."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/migrating-from-integrated-to-cfp-add-in
language: en
last_updated: 2026-05-01
---
# Migrating From Integrated Excel.Add-in to CFP Add-in for Excel 365
## Overview
Customers who used the integrated Lucanet.Excel.Add-in (XLAM) can use a **migration assistant** to convert legacy formulas with the syntax **LUCANET(...)** to the formula syntax **LN. _FORMULA NAME_ (...)** used by the **Lucanet CFP Add-in for Excel 365.**
The assistant scans all used cells in all worksheets of the current workbook and replaces supported legacy formulas with their LN.\* equivalents.
> **Warning:** The conversion cannot be undone. We strongly recommend to create a backup copy of the workbook before you start using the migration assistant.
## Using the Migration Assistant
To use the migration assistant for converting LUCANET formulas, proceed as follows:
1. Open the workbook that contains **legacy LUCANET(...) formulas** you would like to convert.
2. Open the **Lucanet CFP Add-in** tab in the Excel ribbon.
3. In the **Other Tools** group, click **Migration assistant**.
Opening the migration assistant
4. The **Migration assistant** opens on the right side of the Excel window with a confirmation message:
Confirmation message of the migration assistant
5. Click **Yes** to start the conversion using the assistant.
6. Proceed as follows, depending on the success of the conversion:
- If the conversion was **successful**, the migration assistant shows a corresponding confirmation message. Click **OK** to complete the migration.
- If the conversion **failed**, the migration assistant lists the cells causing the failure. In this case, go to the listed cell, correct the formula, and run the conversion again using the command **Retry**.
> **Warning:** The conversion cannot be undone. we therefore strongly recommend to create a backup copy of the workbook before you start using the migration assistant.
## Conversion Patterns
The migration assistant applies the following conversions to LUCANET formulas:
| **Legacy formula pattern** | **Converted formula pattern** |
|---------|---------|
| LUCANET("YTD exchange rate", ...) | LN.RATE.YTD(...) |
| LUCANET("Average exchange rate", ...) | LN.RATE.AVERAGE(...) |
| LUCANET("Closing exchange rate", ...) | LN.RATE.CLOSING(...) |
| LUCANET("ATTRIBUTE", ...) | LN.ATTRIBUTE(...) |
| LUCANET("COMMENT", ...) | LN.COMMENT(...) |
| LUCANET(...) | LN.VALUE(...) |
> **Note:** - The migration assistant supports comma and semicolon separators in legacy formulas.
> - During conversion, line breaks in formulas are removed and only lines that start with = are retained.
---
---
title: "MS Excel file (.xls, .xlsx) (#1000)"
description: "After creating an MS Excel File (.xls, .xlsx) (#1000) data source, the settings for importing data from Excel files are configured in the detail view of the data source."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-excel
language: en
last_updated: 2026-05-01
---
# MS Excel file (.xls, .xlsx) (\#1000)
## Overview
After creating an **MS Excel File (.xls, .xlsx) (#1000)** data source, the settings for importing data from Excel files are configured in the detail view of the data source.
## General Properties
The following general properties of the data source can be configured in the upper area of the detail view:
| Option | Description |
|---------|---------|
| Name | Name of the data source |
| Drill down to posting level | Script for drill-down to posting level **Drill-down for Direct Access to MS Excel (Demo) (#5000)** (optional) |
## Choosing the Type of Excel File
Specify the type of Excel files you wish to import on the **Configuration** tab. A description with the structure and the keywords to be used is displayed for each type of Excel file.
Selection of the type of Excel file to be imported
> **Note:** The Excel file to be imported must be structured according to the description displayed.
The following types of Excel files are available:
| Element | Description |
|---|---|
| **Excel file contains keywords (simple)** | For this type, the structure of the Excel file must follow a specific pattern so that the Lucanet Excel parser can process the data. All format details are fixed and cannot be changed.
As soon as you choose this type: - A detailed description of the structure of the Excel file is displayed. - You can download an example file from the description. |
| **Excel file contains keywords (advanced)** | For this type, the structure of the Excel file must follow a specific pattern so that the Lucanet Excel parser can process the data. More keywords can be used than for the simple form.
As soon as you choose this type: - A detailed description of the structure of the Excel file is displayed. - You can download an example file from the description. |
| **Reporting package files** | This type is used to read in Excel reporting packages. Reporting packages are complex Excel files. An example file for the reporting package can be provided upon request by Lucanet.Consulting.
As soon as you choose this type, a detailed description of the structure of the Excel file is displayed. |
| **Freely-definable layout of the Excel file** | This type is used to read in data from Excel files with any layout.
As soon as you choose this type, a detailed description of the structure of the Excel file is displayed. |
> **Note:** Depending on the selected type, further tabs are displayed for configuration specifications. You can find the descriptions of the options on the additional tabs also in the description of the respective Excel type.
## 'Uses' Tab
The elements that use the data source are displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column.
'Uses' tab
---
---
title: "Notes on Migration from Lucanet.Financial Client"
description: "This article is intended for all customers who already use Consolidation 2 in Lucanet.Financial Client. \n\nIt provides information on:\n- Apps that are supported in the CFO Solution Platform\n- Apps that are not supported in the CFO Solution Platform\n- General notes and notes on migration of the app for equity elimination to the Lucanet CFO Solution Platform"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/migration-from-lnfc
language: en
last_updated: 2026-05-01
---
# Notes on Migration from Lucanet.Financial Client
## Overview
This article is intended for all customers who already use Consolidation 2 in Lucanet.Financial Client.
It provides information on:
- Apps that are supported in the CFO Solution Platform
- Apps that are not supported in the CFO Solution Platform
- General notes and notes on migration of the app for **equity elimination** to the Lucanet CFO Solution Platform
- Notes on the app **Adjust and reclassify values in consolidation areas**
## Apps of Consolidation 2
The legacy apps of Consolidation 2 are not supported in the Lucanet CFO Solution Platform. This means:
- You can only create, configure and execute these apps in Lucanet.Financial Client.
- Apps that have already been created in Lucanet.Financial Client are displayed in the CFO Solution Platform (grayed out). However, the apps can neither be clicked nor configured or executed.
Unsupported apps in the consolidated financial statements
> **Note:** There is **no deployment** of these legacy apps planned for the future. We therefore recommend updating to the apps of the Next Generation.
>
> Please note that there is currently no Next Generation version available for the following apps of Consolidation 2:
>
> - Adjust and reclassify values in consolidation areas
> - Status report for the consolidation process
> - Report on investment relationships
> - Report on deconsolidation
## Apps of Consolidation 2 Next Generation
All apps of **Consolidation 2 Next Generation** are fully supported in the Lucanet CFO Solution Platform:
- **Data transfer and proportioning**
- **Debit/credit shifts in consolidation areas**
- **Elimination of income from investments**
- **Elimination of intercompany income and expense**
- **Elimination of intercompany debt**
- **Elimination of intercompany profit or loss in current assets**
- **Reclassification of profit or loss from previous year in consolidation areas**
These apps of Consolidation 2 Next Generation can be used in Lucanet.Financial Client and the Lucanet CFO Solution Platform:
- You can create, configure and execute new apps in both environments.
- You can edit or execute apps already created in Lucanet.Financial Client seamlessly in the CFO Solution Platform. Apps that have been created in the CFO Solution Platform can also be seamlessly edited and executed in Lucanet.Financial Client.
- The reports and postings generated by these apps can be accessed in both environments.
> **Note:** In Lucanet CFO Solution Platform only templates can be used that exclusively contain consolidation apps of the Next Generation.
## App for Equity Elimination
### General Information
The app for equity elimination is available on the Lucanet CFO Solution Platform in a **Next Generation version** for the first time.
For the use of the app for equity elimination, the following applies:
- The app can be created in Lucanet.Financial Client or the CFO Solution Platform.
- Configuration of the app is only possible on the Lucanet CFO Solution Platform.
- Apps configured on the Lucanet CFO Solution Platform can be executed in both environments.
- The postings created by this app can be accessed in both environments.
> **Note:** Please note that the equity elimination Next Generation is currently only available with a limited functional scope. A step-by-step extension of the scope is planned.
>
> Additional information on the functional scope can be found under [Equity Elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md).
>
> Customers who currently use the app for equity elimination in Lucanet.Financial Client, should postpone migration to the app on the Lucanet CFO Solution Platform until all functions relevant to their business requirements are available.
>
> The legacy app for equity elimination in Lucanet.Financial Client can still be used until all functionalities are available on the CFO Solution Platform.
### Notes on Migration
Customers who have already used the app for equity elimination in Lucanet.Financial Client must observe the following when switching to the consolidation on the CFO Solution Platform:
- The business logic of the app for equity elimination was further developed and adapted in certain aspects on the Lucanet CFO Solution Platform: In the app for equity elimination Next Generation, among other things,
- The recognition of goodwill and negative consolidation differences on the level of the investor and the allocation of these values by investors via the partner dimension is no longer supported. This change corresponds to standard GAAP interpretations which stipulate that goodwill must be assigned to certain business units and not based on ownership interests.
- Moreover, when using the Next Generation app for equity elimination, the option for presentation of the non-controlling interests per source account is omitted.
- In order to apply this new business logic correctly when switching to the Lucanet CFO Solution Platform, we urgently recommend performing an automatic migration, as a correct presentation of the balances of the differentials and non-controlling interests cannot be guaranteed with manual postings.
- To perform an automatic migration, you must create the app for equity elimination Next Generation and activate relevant migration options.
- The migration concerns the **reclassification of goodwill and negative consolidation differences** and the **merging of balances of non-controlling interests that were posted per origin account**.
- Additional information on migration can be found in the description under [Equity Elimination](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md) in the _Settings_ section under [Migration from the legacy app](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/equity-elimination.md#migration).
Migration options for equity elimination
## App 'Adjust and Reclassify Values in Consolidation Areas'
The app is available on the CFO Solution Platform in a new and revised version of the next generation.
Customers who used the outdated version of the app **Adjust and Reclassify Values in Consolidation Areas** as part of Consolidation 2 in Lucanet.Financial Client must create and reconfigure the new version of the app when migrating to the CFO Solution Platform.
---
---
title: "Optional Keywords"
description: "Optional keywords can be inserted if you need to import further information in addition to the required content."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/optional-keywords
language: en
last_updated: 2026-05-01
---
# Optional Keywords
## Overview
Optional keywords can be inserted if you need to import further information in addition to the required content. Optional keywords, just like [required keywords](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords.md), are entered in **column A**, while the corresponding parameters are generally entered in **column B**. Exceptions to this are the keywords in the row **Column definition**, whose parameters and posting data must be entered in the corresponding column.
> **Note:** **Note**: If no entry is made for an optional keyword, this cell is skipped during the import.
## Optional Keywords in Column A
The following keywords can be defined in MS Excel in **column A**:
#### Description
Can contain a description of or a comment on the import.
Only one description is allowed per import (see Description and text)
#### Periodicity
Breaks down annual values (**Y**), semester values (**S**), trimester values (**T**) or quarterly values (**Q**) automatically to monthly values (Periodicity)
> **Note:** **Note**: If the abbreviations (**FY**) or (**FQ**) are used, the annual or quarterly values are converted on a straight-line basis into the months of the deviating fiscal year/quarter.
#### Automatic cancellation
When using **Automatic cancellation**, the posting in Lucanet is canceled automatically in the subsequent period after every month.
## Optional Keywords in the Column Definition Row
The following keywords can be defined in the row **Column definition**:
#### Text
Defines the column for posting texts (see Description and text)
#### Item
Specifies the item in Lucanet under which a new account is to be created (see Item)
#### Partner or P
Defines the column for partner information
> **Note:** **Note**: Only partners may be specified.
#### Cost center or CC
Defines the column for the cost center used
> **Note:** **Note**: The keywords **cost center** or **CC** can only be used together with the keyword **reporting entity**.
#### Consolidation unit or CU
Defines the column for the utilized consolidation unit
> **Note:** **Note**: The keywords **consolidation unit** or **CU** can only be used together with the keyword **consolidation area**.
## Optional Keywords with a Different Meaning
The following keywords can be defined both in **column A** and in the column **Column definition**:
| Keyword | Description |
|---------|---------|
| Factor | Defines the factor globally for a row or a column with which the values are multiplied (see Factor) |
| Transaction type or TT | Defines the transaction type for a row or a column |
| Transaction currency or TC | Defines the factor globally for a row or a column with which the values are multiplied (see section Transaction currency) |
## List of Optional Keywords
The following optional keywords are available:
### Description and text
The **LUCANET** Excel workbook can be used to enter posting-specific texts and a description that can be transferred to Lucanet.
#### Keywords and their Position
| Keyword and its position | Position of the content |
|---------|---------|
| Description, in column A | The description is in the same row in column B. |
| Text, in the **Column definition** row | The text is located in the same column after the corresponding posting. |
### Factor
The keyword **Factor** enables conversion of the values during data transfer. The values to be imported are multiplied with the specified **factor**. This makes entries in TEUR possible, for example. The keyword **Factor** can be entered at different positions in the Excel workbook. The values to which the factor is applied depend on the position in the workbook.
#### Validity Range for the Factor
The values to which a factor is applied depend on its position in the Excel workbook:
| Position | Validity range |
|---------|---------|
| Column A, before the row **Column definition** | The entered factor applies for all values of the worksheet. |
| Within the **Column definition** row | The factor applies for all values of the column. |
| Column A, after the **Column definition** row | The factor applies for all values of the row. |
### Periodicity
Entering the keyword **Periodicity** in column A and a period in a value column for the same row informs Lucanet during the import that the values for e.g. are annual or quarterly values. During the import, the value from MS Excel is automatically broken down to month level in Lucanet.
#### Periods
The following periods can be specified:
| Periodicity | Period |
|---------|---------|
| Y | Year |
| Q | Quarter |
| M | Month |
| S | Semester |
| T | Trimester |
| FY | Fiscal year |
| FQ | Fiscal quarter |
| FS | Fiscal semester |
| FT | Fiscal trimester |
### Item
You can use the **Item** keyword to create unavailable accounts in Lucanet. To do this, the keyword **Account** must be entered in the **Column definition** row in front of the keyword **Item** in MS Excel.
### Transaction currency
The keywords **Transaction currency** and **TC** enable postings to accounts in all transaction currencies defined in Lucanet. If no transaction currency is specified, the default currency of the reporting entity or the consolidation areas is used automatically.
#### Validity Range of the Transaction Currency
The values to which the transaction currency is applied depend on the position of the keyword in the Excel workbook:
| Position | Validity range |
|---------|---------|
| Column A, before the row **Column definition** | The transaction currency applies for all values in the worksheet. |
| Within the **Column definition** row | The transaction currency applies for the values in a row. |
| Column A, after the **Column definition** row | The transaction currency applies for all values in a column. |
### Consolidation unit
The keywords **consolidation unit** and **CU** enable posting in the consolidation units of a consolidation area in the **Groups** workspace. If one of these keywords is used, the postings will occur in the default consolidation unit of the consolidation area.
---
---
title: "Organization Elements"
description: "The structure of your enterprise is recreated in the Organization elements workspace. The Organization elements workspace is used for the creation, modification or deletion of references to objects that were previously created in the Reporting entities workspace or in the Groups workspace."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements
language: en
last_updated: 2026-05-01
---
# Organization Elements
## Overview
The structure of your enterprise is recreated in the **Organization elements** workspace. The **Organization elements** workspace is used for the creation, modification or deletion of references to objects that were previously created in the [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) workspace or in the [Groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/defining-group-structure.md) workspace. You can set up not only one but any number of structures, because there is no limit to the number of references that can be created to the objects from the [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) and the [Groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities.md) workspace, nor to the combinations that can be formed from them.
## Elements of the Workspace
The **Organization elements** workspace contains the following elements:
| Option | Description |
|---------|---------|
| Organization groups | Organization groups are used in structures to combine all of the structure elements of the entire structure or of substructures that belong together. For example, all of the structure units of a group can be combined in one organization group and all of the structure units from subgroups can be combined in separate organization groups (see [Creating and Configuring Organization Groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-configure-org-groups.md)). |
| References | References are links to elements that were previously defined in the **Reporting entities** or the **Groups** workspace (see [Creating and Configuring References](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-references.md)). |
| Total lines | Total lines are used for calculating totals or subtotals in structures (see [Creating and Configuring Total Lines](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/create-configure-total-lines.md)). |
| Residual amounts | Residual amounts are created automatically in the **Organization elements** workspace when displaying a group by levels using nested consolidation areas. Residual amounts can correct possible multiple recordings of consolidation units. One residual amount is created per consolidation unit which was recorded several times, containing the reference to consolidation unit and the associated reference to consolidation unit - cancellation (see [Configuring Residual Amounts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/organization-elements/configure-residual-value.md)). |
---
---
title: "Partner"
description: "In Lucanet, partners can be created, managed, and deleted in the dimension of the same name. Partners are used for the consolidation to add partner information to postings and data imports, primarily for consolidation purposes such as identifying intercompany relationships."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/partners
language: en
last_updated: 2026-05-01
---
# Partner
## Overview
In Lucanet, partners can be created, managed, and deleted in the dimension of the same name. Partners are used to add partner information to postings and data imports, primarily for consolidation purposes such as identifying intercompany relationships.
To view the postings – that is, the values – of the individual partners in an aggregated manner, it is possible to pool partners into **partner groups**. In the event of a value query of a partner group, the aggregated value of all partners is displayed.
## Predefined partners
The two predefined partners **000 Default** and **Value of the account** are always present and cannot be deleted.
## 000 Default
If a posting has no partner information, then the value of the posting will automatically be posted to the default partner **000 Default**.
## Value of account
- The partner is the value of an account or of a position and is never displayed in the Account hierarchies in the drill down according to partners.
- The **Value of account** partner is used in the default settings for the display of account values in account hierarchies. If the **Partner** dimension is switched on in the default view for the dimension bar, then the value can also be selected in the **Partner** dimension to be able to display account values independent of partners.
- The partner is used for the value query via the [CFP Add-In for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in.md) to return the value of the account.
---
---
title: "Placeholder"
description: "In tilde formulas, placeholders can be used as substitutes for data levels, adjustment levels, organization elements, periods, time intervals, or as parameters of functions or statements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/placeholders
language: en
last_updated: 2026-05-01
---
# Placeholder
## Overview
A placeholder is a variable that is replaced by actual values.
In tilde formulas, placeholders can be used as substitutes for **data levels, adjustment levels, organization elements, partners, transaction currency, display currency, periods**, and **time intervals**, or as parameters of [functions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/functions.md) or [statements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/statements.md).
When creating a report, the placeholders can be configured individually, i.e., you can configure whether a value for this placeholder is fixed or can be selected as required. For additional information, see [Generating Excel Reports](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md).
## Structure of the Tilde Formula for Placeholders
The tilde formula must be structured as follows:
**~Placeholder**
## Example
In the Excel worksheet, a tilde formula with placeholders is defined for retrieving the **organization element** and **adjustment level** respectively:
Example of placeholders
## Available Placeholders
The following placeholders can be used in a Tilde formula:
#### Data level
Data level
#### Adjustment level
Adjustment level or Adjustment level group
#### Organization element/OE
- Organization group
- Reference to reporting entity
- Reference to cost center
- Reference to cost center group
- Reference to consolidation area
- Reference to consolidation unit
- Reference to consolidation unit group
#### Month/M
First month of the selected period
#### Quarter/Q
Quarter of the first month of the selected period
#### Year/J
Calendar year of the first month of the selected period
#### Display currency/
Currency/
DC
Display currency
#### Transaction currency/ TC
Transaction currency
#### Partner/P
Partner
#### Period
Period
## Types of Placeholders
The following types of placeholders can be used in a tilde formula:
### Placeholders for Parameters
If a parameter in a tilde formula refers to one of the following dimensions, the keyword can be omitted and replaced by the corresponding placeholder:
- Period (can e.g. be replaced by the placeholder ~month)
- Organization element
- Data level
- Adjustment level
- Transaction currency
- Display currency
**Tilde Formula Structure**
The tilde formula must be structured as follows:
**~Function/Statement(Parameter_1="Value";Placeholder_1;...;Placeholder_n)**
**Example**
In the Excel worksheet, **Year** is used as the placeholder for each **period**:
Example for placeholder 'Year'
When [the report is generated](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md), the placeholder in the tilde formula is replaced with the period configured in the detail view:
### Placeholders for Several Elements of the Same Dimension
When you want to choose several elements of the same dimension in an Excel report (e.g. the data levels **Plan** and **Forecast**), you can expand the corresponding placeholder.
Add a full stop to the dimension followed by a description, e.g.:
- **Data level.Plan**
- **Data level.Forecast**
- **Period.Comparison**
**Example**
In the Excel worksheet, two different placeholders ( **data level.plan** and **data level.forecast**) are used for the **Data level** dimension in the tilde formula:
Placeholder for multiple elements
### Placeholders for Periods
In a tilde formula you can use the placeholders **Month, Quarter** and **Year** for the **Period** parameter. All three placeholders can be defined so that further periods are calculated automatically. This makes it easy to represent time series in an Excel worksheet.
**Example 1: Placeholders and additions**
If the period Aug 2017 is selected before the report is generated, the following values are returned depending on the placeholder used:
- ~Month: Aug 2017
- ~Quarter: Q3.2017
- ~Year: 2017
- ~Month+1: Sep 2017
- ~Year+1..year +2: 2018-2019
**Example 2: Forming a time series**
In the tilde formula, the **Month** placeholder is added from column C:
Placeholder for a time series
The following months are calculated based on the month selected during the [creation of the report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md):
Result of placeholders for time series in Excel
### Placeholders for a Time Interval
You can use the **Time interval** placeholder to generate reports that display **comparisons** rather than time series. The user can choose a time interval over a defined periodicity ( **year**, **quarter** or **month**) covering any number of periods.
**Example**
The Excel worksheet contains two tilde formulas for entering **revenue** in two time intervals. **Column D** calculates the difference between the different revenue entries:
Placeholder for time intervals
When [generating the report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/generate-excel-report.md), the time periods to be compared can be selected in the detail view.
---
---
title: "Planning"
description: "The Planning functionalities of our Consolidation & Financial Planning solution can be used to plan on a monthly, quarterly or yearly basis for any planning period and display any scenario based on existing plans."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning
language: en
last_updated: 2026-09-29
---
## Planning
The Planning functionalities of our Consolidation & Financial Planning solution can be used to plan on a monthly, quarterly or yearly basis for any planning period and display any scenario based on existing plans.
The following features are available for Planning:
- [Accounting rules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules.md): Used to define automatic contra entries for integrated balance sheet, profit and loss and cash flow planning.
- [VAT and input VAT configurations](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax.md): Can be taken into account as part of the configuration of accounting rules for accounts and items in general ledgers and subledgers.
- [Sheets:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets.md) Replacing the previously used Forms in Lucanet.Financial Client, Sheets offer enhanced capabilities for performing financial planning calculations — including the ability to create formulas using natural language.
- [Planning wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards.md): With the help of planning wizards, postings can be made automatically using advanced business logic and complex calculations.
- [CFP Add-in for Excel 365:](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-excel-add-in.md) The Lucanet CFP Add-in for Excel 365 can be used to transfer planning, posting records or statistical values, such as employee figures, from MS Excel to Lucanet.
'Accounting rules' workspace
- [Accounting Rules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules.md)
- [VAT/Input Tax Administration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax.md)
- [Planning Using Sheets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets.md)
- [Planning Using Planning Wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards.md)
- [Planning Using CFP Add-in for Excel 365](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-excel-add-in.md)
---
---
title: "Planning Using CFP Add-in for Excel 365"
description: "Lucanet CFP Add-in for Excel 365 can be used to transfer plannings, posting records or statistical values, such as employee figures, from MS Excel to Lucanet. This data must be included in a certain format in the active workbook. This allows, for example, any kind of complex plannings to be created in Excel and imported into Lucanet at the press of a button."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-excel-add-in
language: en
last_updated: 2026-05-01
---
# Planning Using CFP Add-in for Excel 365
## Overview
Lucanet CFP Add-in for Excel 365 can be used to transfer plannings, posting records or statistical values, such as employee figures, from MS Excel to Lucanet. This data must be included in a certain format in the active workbook. This allows, for example, any kind of complex plannings to be created in Excel and imported into Lucanet at the press of a button.
## Structure of the Excel Worksheet
The structure of the worksheet is essential for Lucanet (see [Configuring the Excel worksheet](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet.md#configuring-worksheet)). The import can only be performed if the worksheet has a particular structure.
To import information and values from an Excel table into Lucanet, the data and parameters to be transferred must be defined by keywords on an Excel worksheet of the active workbook.
The keywords show Lucanet which data of an Excel worksheet are to be imported. A distinction is made between **required** and **optional keywords** (see [Required Keywords](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords.md) and [Optional Keywords](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/optional-keywords.md) ).
The required keywords are required in order for Lucanet to recognize that it is an import. Optional keywords can be used to import additional information.
## Transferring Postings
The import can take place after the Excel worksheet has been created in the respective format (see [Transferring Data from MS Excel to Lucanet](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet.md)).
---
---
title: "Planning Using Planning Wizards"
description: "Planning Wizards are functionalities used for more advanced business logic and complex calculations. With the help of the planning wizards, it is possible to carry out postings automatically according to the configuration of the wizard. The planning wizard is only available in planning data levels."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards
language: en
last_updated: 2026-05-01
---
# Planning Using Planning Wizards
## Overview
Planning Wizards are functionalities in Consolidation & Financial Planning used for more advanced business logic and complex calculations. With the help of the planning wizards, it is possible to carry out postings automatically according to the configuration of the wizard. The planning wizard is only available in planning data levels.
> **Tip:** To analyze, review, or share posting data, you can generate a report of all postings, including postings created by planning wizards. For instructions on how to do this, see [Creating a Posting Report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/create-postings-report.md).
## Types of Planning Wizards
The following planning wizards are available:
| Type | Description |
|---------|---------|
| [Loan](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/loan-wizard.md) | Using the loan wizard, it is possible to plan both received and issued loans in Lucanet for reporting entities. |
| [Current account interest](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/current-account-interest.md) | The wizard can be used for reporting entities to plan the automatic interest return of giro accounts and overdraft facilities. |
| [Transfer actual balance to plan](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards/creating-and-configuring-transfer-actual-balance-to-plan-wizards.md) | The wizard can be used to transfer existing account balances from actual to planning periods for reporting entities. |
---
---
title: "Planning Using Sheets"
description: "Sheets offer a flexible way to perform calculations required in the financial planning process. They can be created for all reporting entities for values of ledgers and schedules in planning data levels."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Sheets
## Overview
**Sheets** offer a flexible way to perform calculations required in the financial planning process in Consolidation & Financial Planning. They can be created for all reporting entities for values of ledgers and schedules in planning data levels, either within a **journal** or from a **ledger**.
> **Warning:** **Information for customers who used the planning function in Lucanet.Financial Client**
>
> Sheets are replacing the **forms** used in **Lucanet.Financial Client**. In the CFO Solution Platform, Sheets can be created within the **Import and Journals** workspace.
>
> To ensure transparency and traceability, all the **existing forms** from the Lucanet Financial Client will still be accessible in the Lucanet CFO Solution Platform under **Journals** in **read-only mode**.
## Creating a Sheet Within a Journal
To create a sheet within a journal:
1. Open the **Journals** workspace.
2. In the dimension bar, select the combination of a **planning data level** and **reporting entity** for which a sheet should be created.
3. Right-click the root folder and choose **Create | Sheet**. The **Create Sheet** dialog is displayed:
Creating a sheet
4. Specify the **name** of the element and click **Continue**.
## Creating a Sheet From a Ledger
To create a sheet from a ledger:
1. Open the **Reporting and analyzing** workspace.
2. Select the desired **ledger** (general ledger, sub-ledger or statistical ledger).
3. In the dimension bar, select the combination of **planning data level** and **reporting entity** for which a sheet should be created.
4. Right-click in the row of the ledger hierarchy for which a sheet should be created and choose **Create | Sheet**.
Creating a sheet from a ledger
5. The **Create Sheet** dialog is displayed:
'Create sheet' dialog
6. Specify the **name** of the element and click **Continue**.
## Configuring Sheets
To configure a sheet, click the name of the desired sheet in the tree view, and then click **Edit** in the top right.
Configuration of general properties
### General Properties
The following properties can be edited in the header:
| Option | Description |
|---|---|
| **Element name** | Name of the sheet |
| **Currency** | Currency in which the postings are to be carried out |
| **Adjustment level** | Adjustment level in which the postings are to be carried out |
| **Basis** | Adjustment level (group) used as the planning basis |
#### Configuration
The following menu is displayed when clicking the configuration icon:
Configuration menu
Choosing one of these options will extend the planning area by the corresponding columns.
> **Note:** The selected configuration is not stored at a system level nor shared between different sheets.
#### Change number format
The following menu is displayed when clicking the change number format icon:
'Change number format' menu
Choosing one of these options will adapt the number format accordingly in the planning area.
#### Cost center/ Partner/ Transaction type
Clicking the **Cost center**, **Partner**, or **Transaction type** buttons in the toolbar toggles the visibility of the respective columns in the table.
Hiding these columns does not affect the data stored in them — the system retains the information and uses it when generating the posting.
### Values Tab
Configuration of the 'Values' tab in a sheet
The following options are available on the **Values** tab:
### Toolbar
#### Time period
Used for moving, shortening or extending the planning period. It is possible to change the view to:
- **Month, quarter, trimester, semester,** or **year**
- **Calendar** or **fiscal year**
- **Total period view** – when selected, the system automatically adds columns for all previous years with actual data for the respective reporting entity and displays the actual amounts.
#### Default
Used for restoring the default view of the sheet. In the default view, **Year** is used as the period. The last year of the actual data level and all years of the selected planning data level are displayed.
### Planning Area
The following options are available in the planning area:
#### Account or item
An account or an item for which planning should be undertaken. It is also possible to activate the following options:
**Create independent variable**
If this option is activated:
- The **actual period** column linked to the actual data level is cleared (if previously populated) and locked for editing.
- The **planning period** columns linked to the selected planning data level are cleared and the fields can be edited (numbers and basic mathematical operations are allowed). If a formula has been applied that generates results in the planning period column, the corresponding fields are not editable.
- The **Cost center**, **Partner** and **Transaction Type** columns are locked for editing.
> **Tip:** **Aggregation method**
>
> For indpeendent variables, you can configure how values are aggregated: Right-click an independent variable in the **Account or item** column and select **Aggregation | Sum/No aggregation** from the context menu.
>
> - When **Sum** is selected, entering values at the monthly level and changing the view to quarter, trimester, semester, or year will automatically display the sum of the corresponding months in the period columns. If values are entered on a yearly level, the values are split evenly across all months.
> - When **No aggregation** is selected, enter values only at the monthly level. If you switch to a higher time period view, the period columns will show '...' and a tooltip indicating that values are displayed only on the monthly level because no aggregation is selected.
**Query values from selected account/item**
If this option is activated:
- The columns **Cost center/Partner/Transaction Type**, and **Variable** name are enabled and can be edited.
- The **actual** and **planning period** columns are automatically filled with values from the database by the system. Fields are locked for editing.
- The **Formula** field is locked for editing.
#### Cost center/ partner/ transaction type
Allows selection of a cost center/partner/transaction type from the respective drop-down lists
#### Variable name
Auto-filled with the selected item or account name. You can modify this field with text, numbers, or special characters.
> **Note:** If you add a variable name that already exists within the same sheet, the system will automatically append “(1)” to it. If you add more variables with the same name, the number will increase incrementally.
#### Formula
Used for entering variables and basic mathematical operations (addition, subtraction, multiplication, division and brackets) to perform calculations during the financial planning process.
Key points include:
- It is only possible to enter fixed values with up to two decimals.
- Formulas can be added to planning and independent variable rows, but **not** to querying rows.
- **Time offset:** When a variable is added, a time offset is automatically displayed, with **this month** as the default value. Time offset defines the period from which values are retrieved and used in the calculations of the amount shown in the time period column.
To change it, click the offset value and select one of the available options or click **Custom** to enter a **custom offset**.
Example formula with a variable and time offset
- When using formulas, changes in one calculation can affect other dependent business transactions. The system can recalculate these dependencies automatically or on demand (see [Dependent Business Transactions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets/dependent-business-transactions.md)).
- Formulas that create dependencies between transactions may lead to circular references. The system detects and manages these cases (see [Dependent Business Transactions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets/dependent-business-transactions.md)).
#### Period columns
The **actual period** column, linked with the actual data level, is populated with the amounts retrieved from the database for the selected account or item.
The **planning period** columns linked to the selected planning data level are blank and values can be added using numbers with decimals and basic mathematical operations, unless **Query values from selected account/item** is activated or a formula has been applied that generates results in the planning period column.
> **Note:** To easily distinguish between the different period columns, the **actual period** column is highlighted in gray, whereas the **planning period** columns remain white.
#### Posting text
Used for entering a user-defined posting text to be added to the Sheet posting.
> **Tip:** To analyze, review, or share posting data, you can generate a report of all postings, including postings created by Sheets. For instructions on how to do this, see [Creating a Posting Report](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/create-postings-report.md).
---
---
title: "Postings in Journals"
description: "The Journals workspace contains all postings. In addition to postings and data imports, the workspace also contains elements for (wizard-supported) planning and consolidation."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/postings-journals
language: en
last_updated: 2026-05-01
---
# Postings in Journals
## Overview
The **Journals** workspace contains all postings. In addition to postings and data imports, the workspace also contains elements for (wizard-supported) planning and consolidation.
## Postings in Journals
The following postings are displayed in the **Journals** workspace:
| Posting type | Description |
|---------|---------|
| Posting | In Consolidation & Financial Planning, you can display all postings for reporting entities and consolidation areas for each journal. |
| Posting via MS Excel | As soon as Excel plannings or postings are imported into Lucanet.Financial OLAP Server using **CFP Add-In for Excel 365**, the automatically generated postings are displayed in the **Journals** workspace. |
| Data imports | All data that is imported into reporting entities is transferred to the current Lucanet database using data imports. Data imports are displayed in Consolidation & Financial Planning as a posting in the journal. |
| Translation with historical exchange rates | The Lucanet CFO Solution Platform displays postings of type **Translation with historical exchange rates**. In the **Translation with historical exchange rates** posting, the translation is defined for accounts with historical exchange rates. If translation with historical exchange rates is defined for an account, the value which has been calculated originally using the current exchange rate is cleared and then the value which has been calculated using the historical exchange rate is posted. |
| Postings created by apps | As soon as an app is run as part of Consolidation 2 or within a directory structure, the automatically generated app entries are displayed in the corresponding journal. |
| Sheets | Postings that are automatically created as part of the Sheets configuration (see [Planning Using Sheets](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-sheets.md)). |
| Planning wizard | Postings that are automatically created as part of the Sheets configuration (see [Planning Using Planning Wizards](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/planning-wizards.md)). |
## Show Postings
In journals, you can view postings with the associated posting details at any time. Mark the desired posting in the tree view of a journal.
This is what the detail view of a posting looks like as an example:
Details of a posting
## Detail View of Postings
The following properties are displayed in the detail view of postings:
| Property | Description |
|---------|---------|
| Type | Type of the posting |
| Name | Posting name |
| Reporting entity | Reporting entity in which the posting was created |
| Data level | Data level in which the posting was created |
| Currency | Currency in which the posting values are displayed |
| Adjustment level | Adjustment level in which the posting was created |
| Data import | Name of the data import (only for the **Data imports** posting type) |
| Cancel posting | You can use the **Cancel posting** function to reverse a manually created posting. The cancellation can be cumulative after the last month or after each month. |
> **Warning:** The properties **Currency**, **Adjustment level**, **Data import**, and **Cancel posting** are not displayed in postings of type **Translation with historical exchange rates**.
## Configuring the Posting Mask
On the **Values** tab, you can configure the value display using the posting mask.
Options in a posting mask
The following functions are available in the posting mask:
| Function | Description |
|---------|---------|
| Show cumulated | Activating the **Show cumulated** button displays cumulated values in the posting columns. This displays the total for all posting times. If this button is not activated, all values of the posting entries for a posting or the times for a data import are listed separately. |
| D/C recording | The **D/C recording** button can be used to switch the view from plus and minus recording to the entry of accounting values in debit and credit. |
| Historical exchange rate translation | If a translation with historical exchange rates is defined for a posting value, the value calculated originally using the current exchange rate is balanced and the value calculated using the historical exchange rate is posted. The **Historical exchange rate translation** button can be used to display the historical exchange rate translation for values. |
> **Warning:** The **Historical exchange rate translation** button is only displayed if at least one currency translation has been configured in a reporting entity or consolidation area.
---
---
title: "Provision via script (#2075)"
description: "After creating a Provision via Script (#2075) data source, the settings for importing data via script are configured in the detail view of the data source."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-script
language: en
last_updated: 2026-10-01
---
# Provision via script (\#2075)
## Overview
After creating a **Provision via Script (#2075)** data source, the settings for importing data via a script are configured in the detail view of the data source.
## General Properties
The following general properties of the data source can be configured in the upper area of the detail view:
| Option | Description |
|---------|---------|
| Name | Name of the data source |
| Drill down to posting level | Script to be used for drill-down to posting level (optional) |
| Display scanned documents | Script that enables the display of scanned documents (optional) |
| Executed on | Execution location for the script selected in **Display scanned documents**: **Execute on server** or one of the configured **Script Execution Application (SEA)** instances.
**Note:** This field is only displayed if a script is selected in **Display scanned documents**. It is used as the default execution location when a user opens the original document via **Original Posting** (see [Drilling Down to Original Posting Level](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level.md)). |
## 'Configuration' Tab
The **Configuration** tab consists of the following sections:
### The following scripts are executed during the data import
Adding script
The following options must be configured:
| Option | Description |
|---|---|
| **Script** | Scripts to be executed during data import. All scripts from the **Scripts** workspace can be selected. |
| **Application** | Location where the respective script is to be executed
**Note:** If the script is to be executed on an SEA instance, you must choose the created **application** in the **Application** drop-down list (see [Creating SEA Applications on the CFO Solution Platform](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md#creating-sea-applications-in-the-cfo-solution-platform)).
**Lucanet Script Execution Application** ( **SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script. |
### The following data are imported
Options for data imports
The following options are available:
| Option | Description |
|---|---|
| **Import type** | The desired import type: - Transaction figures or balances (selection when importing) - Transaction figures - Balances - Balances - schedules only - Transaction figures incl. automatic contra entry (only planning) |
| **Data levels** | Data levels into which the data are to be imported.
Enter the name of the data level in the **DataLevelCode** column.
**Note:** This field is only displayed if the corresponding variable is defined in the selected script. |
| **Adjustment levels** | Adjustment levels into which the data are to be imported.
Enter the name of the adjustment level in the **AdjustmentLevelCode** column.
**Note:** This field is only displayed if the corresponding variable is defined in the selected script. |
| **Accounting periods per year** | Number of accounting periods per year (default: 12)
- If you specify a number greater than 12, all periods greater than 12 are imported by default into period 12. You have the option to specify whether the additional periods are to be imported with a suffix into separate adjustment levels. - If you specify a number greater than 12, then it is only possible to import transaction figures. |
### The following dimensions are imported
Selection of dimensions to be imported
Specify which dimensions are to be imported. The **Account** dimension is always activated. If necessary, change the displayed dimension code in the **DimensionCode** column.
**Cost centers in the Balance Sheet**: If the use of the **Cost center** dimension is activated, you can specify whether a drill down by cost centers should be performed in the balance sheet:
- **Use default cost centers always (recommended)**: The default cost center is used
- **Use specified cost centers**: The cost center whose code was specified for the dimension **Cost center** will be used
### Reclassify values
Options for reclassifying values
If necessary, specify whether you want to **reclassify values** during the data import. The following options are available:
| Option | Description |
|---|---|
| **Present intercompany postings on separate accounts** | Accounts and partner for intercompany postings.
If the use of the **Partner** dimension is activated, the corresponding accounts and partners can be specified in the **Accounts to be analyzed** table. |
| **Attach suffix to account name** | Suffix for account name.
Specify the desired suffix in the displayed **DimensionCode** field. |
| **Reclassify debtors with credit balances and creditors with a debit balance** | Reclassification of debit or credit balances when importing balances or opening balance sheet values.
Specify the desired code in the **DimensionCodefor the ‘Subledger account’ dimension** field. In the **Accounts to be analyzed** area, the account range ( **Account from** and **Account to**) and the balances to be reclassified ( **Credit** or **Debit**) must be specified. |
## 'Reporting Entities’ Tab (Conditional)
'Reporting entities' tab
> **Warning:** The **Reporting entities** tab is only displayed if the corresponding variable is defined in the selected script.
The **Reporting entities** tab defines which reporting entities are available for selection when importing the data. The configuration corresponds to the configuration for data sources of type **Lucanet.Financial Warehouse (#2068)**. For the complete description of all options, see [Specifying Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md#specifying-reporting-entities).
In addition, importing data into reporting entities via a script offers the possibility to split data imports into several import files and store them in a predefined folder structure (see [Splitting Data Imports During First Execution](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md#splitting-data-imports-during-first-execution)).
If necessary, contact your Lucanet consultant to find out whether your script can be configured accordingly.
## 'Uses' Tab
The elements that use the data source are displayed on the **Uses** tab.
You can open the respective element by clicking the link in the **Name** column.
'Uses' tab
---
---
title: "Querying Attributes"
description: "You can use querying of attributes from Lucanet, among other things, to export element names in Lucanet via the OID of elements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-attributes
language: en
last_updated: 2026-05-01
---
# Querying Attributes
## Overview
You can use querying of attributes from Lucanet, among other things, to export element names in Lucanet via the **OID** of elements. The OID of an element is always unique while its name does not have to be unique. If an element exists with the same name at several points in Lucanet, a query leads to an error message, while a query with the OID returns the correct result.
## Structure of the LUCANET Formulas
To read in attributes from Lucanet to MS Excel, the formula must be set up as follows:
```
=LN.ATTRIBUTE("Attribute","Object")
```
## Attribute
The parameter **Attribute** specifies either the key of an attribute or the name of an object.
| Attribute | Definition |
|---------|---------|
| Key | Key of the attribute in Lucanet |
| Name | Returns the element name of the specified object |
## Object
The **Object** parameter specifies either the element name or the OID of the object whose attribute is to be read in to MS Excel.
| Object | Definition |
|---------|---------|
| Element name | Returns the attribute of the object with the specified element name |
| lucanet://oid=XXX | Returns the attribute of the object using the URL lucanet://oid=XXX |
---
---
title: "Querying Comments"
description: "You can use LUCANET formulas to query comments in Lucanet (e.g. for values in the general ledger, in subledgers or in schedules) and read them in to MS Excel."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-comments
language: en
last_updated: 2026-05-01
---
# Querying Comments
## Overview
You can use LUCANET formulas to query comments in Lucanet (e.g. for values in the general ledger, in subledgers or in schedules) and read them in to MS Excel.
## Structure of the LUCANET Formulas
To read in comments from Lucanet to MS Excel, the LUCANET formula must be set up as follows:
```
=LN.COMMENT("Abbreviation","Data level","Adjustment level","Organization element",
"Account or Item","Periodicity","StartDate",["EndDate"],["Transaction type"],
["Display currency"],["Transaction currency"],["Partner/partner group"])
```
## Parameters
All parameters must be specified just as described in [Querying Values](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-values.md). The formula can be added with [optional parameters](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-values.md#optpara).
---
---
title: "Querying Data from Lucanet"
description: "You can use CFP Add-In for Excel 365 to selectively read in data from Lucanet to MS Excel. This allows you to populate reports created in MS Excel at the push of a button. As Lucanet saves all data in a central database, all reports are available with the current values from Lucanet at all times."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data
language: en
last_updated: 2026-05-01
---
# Querying Data from Lucanet
## Overview
You can use CFP Add-In for Excel 365 to selectively read in data from Lucanet to MS Excel. This allows you to populate reports created in MS Excel at the push of a button. As Lucanet saves all data in a central database, all reports are available with the current values from Lucanet at all times.
The following can be queried:
- [Values](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-values.md)
- [Exchange Rates](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-exchange-rates.md)
- [Comments](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-comments.md)
- [Attributes](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-attributes.md)
For data to be read in to MS Excel, [LUCANET formulas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/lucanet-formulas.md) must be specified in the Excel workbook. You can use parameters to define which data are to be imported to MS Excel. You can use parameters to define which data are to be read in to MS Excel.
---
---
title: "Querying Exchange Rates"
description: "You can use a LUCANET formula to query exchange rates in Lucanet and read them in to MS Excel."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-exchange-rates
language: en
last_updated: 2026-05-01
---
# Querying Exchange Rates
## Overview
You can use a LUCANET formula to query **exchange rates** in Lucanet and read them in to MS Excel.
## Structure of the LUCANET Formulas
To read in **exchange rates** from Lucanet to MS Excel, the LUCANET formula must be set up as follows:
```
=LN.FORMULA NAME("Name of the exchange rate table","Data level","Date")
```
## Formula Name
The formula name specifies the exchange rate to be read into MS Excel. The following formula names can be entered:
| Formula name | Description |
|---------|---------|
| RATE.CLOSING | Returns the closing exchange rate for a month |
| RATE.AVERAGE | Returns the average exchange rate for a month |
| RATE.YTD | Returns the YTD rate of a month |
| 1/LN.RATE.CLOSING | Returns the reciprocal value of the closing exchange rate for a month |
| 1/LN.RATE.AVERAGE | Returns the reciprocal value of the average exchange rate for a month |
| 1/LN.RATE.YTD | Returns the reciprocal value of the YTD exchange rate for a month |
---
---
title: "Querying Values"
description: "You can use a LUCANET formula to query values from Lucanet and read them in to MS Excel. The formula for querying values must contain certain parameters and can be expanded with optional parameters."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/querying-data/querying-values
language: en
last_updated: 2026-05-01
---
# Quering Values
## Overview
You can use a LUCANET formula to **query values** from Lucanet and read them in to MS Excel. The formula for querying values **must** contain certain parameters and **can** be expanded with optional parameters.
## Querying Values
To read in values from Lucanet into Excel, the formulas must contain the following parameters:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level/Adjustment level group",
“Organization element","Account or Item","Periodicity","StartDate")
```
### Abbreviation
The **abbreviation** defines from where the data to be read in are derived. The following abbreviations are allowed:
| Abbreviation | Meaning |
|---------|---------|
| Abbreviation of a general ledger, abbreviation of a general ledger including subledgers or abbreviation of a schedule | Reading in values from ledgers or schedules with the specified abbreviation |
| fin | **fin** was used in previous versions as keyword for the balance sheet and P&L and can be used as code to read values out of the ledgers to which the balance sheet and P&L of previous versions were transferred. |
| stat | **stat** was used in previous versions as a keyword for statistical ledgers and can be used as code in order to read values out of a statistical ledger to which statistical ledgers of previous versions have been transferred. |
### Data level
The **Data level** parameter specifies in which **data level** the data to be read in are contained. Data can be located in the **actual data level** and in any number of **planning data levels**. To specify data levels:
| Data level | Notation in the Lucanet formula |
|---------|---------|
| Actual data level | "Actual" |
| Planning data level | "Plan 2026-2028" |
### Adjustment level/Adjustment level group
The **adjustment level** or **adjustment level group** parameter specifies the adjustment level or adjustment level group to which the values to be imported are posted and evaluated. The default adjustment level is **Data imports**. To specify adjustment levels or adjustment level groups:
| Adjustment level | Notation in the Lucanet formula |
|---------|---------|
| Data imports | "Data imports" |
| Delta under local GAAP | "Delta under local GAAP" |
### Organization element
The parameter **Organization element** specifies the reference to the reporting entity, cost center, cost center group or organization group from which the values are to be read. Specify organization elements as follows:
| Organization element | Notation in the Lucanet formula |
|---------|---------|
| Holding Inc. | "Holding Inc." |
### Account or item
The parameter **Account** or **Item** specifies the name of the **account and item** whose value you want to export. To specify accounts or items:
| Account/item | Notation in the Lucanet formula |
|---------|---------|
| Technical equipment | "Technical equipment" |
| Turnover | "Turnover" |
### Periodicity
The parameter **Periodicity** specifies the frequency with which the values are read from Lucanet. The following periods are allowed:
| Period | Meaning |
|---------|---------|
| m | Monthly value of the desired period |
| q | Quarterly value of the desired period |
| y | Annual value of the desired period |
| t | Trimester value of the desired period |
| s | Semester value of the desired period |
| fq | Quarterly value for the fiscal year of the desired period |
| fy | Annual value for the fiscal year of the desired period |
**Example**: Export of values for 31/12/2017. The possible periodicities return the following:
| Periodicity | Values |
|---------|---------|
| m | The monthly value for the month of December 2017 |
| q | The value of the last quarter 2017 |
| y | Annual value 2017 |
| fq, fy | The quarterly or annual values for the different fiscal year |
### Start date
The **StartDate** specifies the value for the month, quarter or year in which the date falls. The entry must be made in the format _DD/MM/YYYY_ . This is regardless of the formatting of the view in MS Excel. When entering the date **31/12/2017**, for example, the view format could be **Dec. 2017**.
**Note**: Instead of a specific entry, you can also use MS Excel to apply absolute or relative cell references, such as A2 (relative) or $A$2 (absolute) and references to named cells (see the following examples).
## Optional Parameters
To access more detailed information when querying values, **optional parameters** can be added to the LUCANET formula.
A Lucanet formula with optional parameters is structured as follows:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level","Organization element",
"Account or Item","Periodicity","StartDate",["EndDate"],["Transaction type"],
["Display currency"],["Transaction currency"],["Partner/partner group"],["YTD"])
```
> **Warning:** **Caution**:
>
> - In order to correctly interpret the optional parameters, you **must** stick to the specified sequence!
> - If not all optional parameters are entered for a LUCANET formula, commas need to be set also for those parameters which are not entered.
The following parameters can be used:
### Transaction type
When querying values, the optional parameter **transaction type** can be added to the LUCANET formula. By default, for values from the financial sector, the balance at the end of the period is always exported to MS Excel. When using the optional parameter **Transaction type**, it is also possible to query other values (e.g. the balance at the start of the period).
**Note**: If the parameter **Transaction type** is not specified when querying parameter values, account balances are always exported.
### Structure of the LUCANET Formulas
A Lucanet formula querying the transaction type must be set up as follows:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level",
"Organization element","Account or item","Periodicity",
"StartDate",,"Transaction type")
```
### Parameter
The following parameters for **transaction type** are available:
| Parameter | Description |
|---------|---------|
| Start | Returns the start value of the account on a given date |
| TF | Returns the change to the account on a given date |
| Balance | Returns the balance of the account on a given date |
If fixed asset schedule, provision schedule, loan schedule, and/or statement of changes in equity are set up in Lucanet, you can also query information (in addition to the default parameters) from these categories. The following parameters are available:
| Parameter | Description |
|---------|---------|
| Name of a transaction type (e.g. 110 Addition) | Returns the value of the specified transaction type |
| Cost.Start | Returns the start value of the balance sheet account in the transaction type group **Historical cost**. Alternatively, it is also possible to query the group **Accumulated depreciation/amortization** ("Accumulated depreciation and amortization.Start"). |
| Cost.TF | Returns the change to the balance sheet account in transaction type group **Historical cost**. Alternatively, it is also possible to query the group **Accumulated depreciation and amortization** ("Accumulated depreciation and amortization.TF"). |
| Cost.Balance | Returns the balance of the account in the transaction type group **Historical cost**. Alternatively, it is also possible to query the group **Accumulated depreciation/amortization** ("Accumulated depreciation and amortization.Balance"). |
> **Note:** **Note**: The parameter depends on the name of the transaction types. The parameters must be named just as they are named in the **Dimensions** workspace under **Transaction types**.
### EndDate
When querying values, the optional parameter **EndDate** can be added to the LUCANET formula. You can use this parameter, for example, if you want to read in the cumulated values of a specific period from the P&L to MS Excel. The value read in is then the total of values between the start and end date.
### Structure of the LUCANET Formulas
The LUCANET formula must be set up as follows:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level","Organization element",
"Account or item","Periodicity","StartDate","EndDate")
```
### Partner
When querying values, the optional parameter **Partner** or **Partner group** can be added to the LUCANET formula. You can use these parameters to query partner information.
### Structure of the LUCANET Formulas
The LUCANET formula must be set up as follows to query partner information:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level","Organization element",
"Account or item","Periodicity","Start date",,,,,"Partner/Partner group")
```
> **Note:** **Note**: If no partner is specified, the system returns the value of the account or the item.
### Currency
By default, values from Lucanet are read in to MS Excel in the **default currency**. The **Display currency** and **Transaction currency** parameters can be used to define which values are to be read in to MS Excel and in which currency.
### Structure of the LUCANET Formulas
To query values in a currency other than the default currency, the LUCANET formula must be set up as follows:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level","Organization element",
"Account or item","Periodicity","StartDate",,,"Display currency","Transaction currency")
```
### Variants
The result of a query depends on the parameters used in the Lucanet formula. The following variants are available:
| Parameter | Result |
|---------|---------|
| **Without** keyword | The sum of all business transactions (in all transaction currencies) translated into the specified display currency **Note**: You can also use **Transaction currency**="**All**" to enter the values of all transaction currencies. |
| Display currency **only** | The sum of all business transactions (in all transaction currencies) translated into the specified display currency **Note**: You can also use **Transaction currency**="**All**" to enter the values of all transaction currencies. |
| Transaction currency **and** display currency | The sum of all business transactions in the specified transaction currency translated into the specified display currency |
### YTD
The YTD parameter can be used to query the value of an account or an item from a Year-To-Date period up to a requested period.
### Structure of the LUCANET Formulas
The LUCANET formula must be set up as follows:
```
=LN.VALUE("Abbreviation","Data level","Adjustment level","Organization element",
"Account or item","Periodicity","Start date",,,,,,"YTD XX")
```
```
```
**Explanation**: XX represents a period
**Examples**:
- Periodicity = "m", startDate = "31.07.2025", ytdPeriod = 4 (YTD 04): Queries values from **Apr 2025 to Jul 2025**
- Periodicity = "m", startDate = "31.07.2025", ytdPeriod = 10 (YTD 10): Queries values from **Oct 2024 to Jul 2025**
---
---
title: "Reclassification of Profit or Loss from Previous Periods in Reporting Entities"
description: "You can use the Reclassification of profit or loss from previous periods in reporting entities app to automatically reclassify the period result from the previous year to carry it forward. The following functional topics are covered:\n\nReclassification of the period result from the previous year to carry it forward in local currency\nFixation of the historical exchange rate at foreign currency companies (in different display currencies)"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-in-directory-structures/reclassification-of-profit-or-loss-in-reporting-entities
language: en
last_updated: 2026-05-01
---
# Reclassification of Profit or Loss from Previous Periods in Reporting Entities
## Overview
You can use the **Reclassification of profit or loss from previous periods in reporting entities** app to automatically reclassify the period result from the previous year to carry it forward. The following functional topics are covered:
- Reclassification of the period result from the previous year to carry it forward in local currency
- Fixation of the historical exchange rate at foreign currency companies (in different display currencies)
For reclassification purposes, the following can be configured for the reporting entities:
- Data level
- Adjustment level
- Transaction type
- Cost center (optional)
## Creating an App for Reclassification of Profit or Loss from Previous Periods in Reporting Entities
The app for **Reclassification of profit or loss from previous periods in reporting entities** can be created in any directory structure, provided that the element type **Next Generation App** has been [enabled for](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) this directory structure.
To create the app, proceed as follows:
1. Ensure that the object type **App** has been [enabled](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) in the [workspace configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche.md) for the directory structure under which you want to create the app.
2. Navigate to the directory structure under which you want to create the app.
3. Select the **root folder** of the directory structure or, if applicable, a **folder** under which you want to create the app, and select **Create | App** from the context menu.
The **Create Next Generation App** dialog appears:
Creating an app
4. From the **App type** dropdown list, select the app for **Reclassification of profit or loss from previous periods in reporting entities.**
5. Change the **name of** the app if necessary.
6. Click **Save** to create the app and configure it as described below.
## Configuring an App for Reclassification of Profit or Loss from Previous Periods in Reporting Entities
To configure an app for Reclassification of profit or loss from previous periods in reporting entities, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the posting details and the relevant reporting entities.
Step 'Settings'
#### Postings
**Data level**
Data level at which the reclassification is to be performed.
Closed or archived data levels cannot be selected.
**Period under consideration**
The period under consideration for which the transaction figures are to be read out as the basis for the reclassification.
**Posting month**
Month in which the app transfers the profit or loss from the previous period to the carryforward account.
> **Note:** - For **planning data levels,** the app also takes actual values into account if these fall within the period under consideration.
> - The app automatically selects the month following the period under consideration as the month for performing the reclassification. If the last month of the period under consideration is also the last month of the data level, the reclassification is performed in the last month of the data level.
#### Reporting entities
Reporting entities for which the reclassification is to be performed.
### Adjustment levels
In the **Adjustment levels** step, specify the **adjustment level(s)** for the reclassification of the values.
Step 'Adjustment levels'
> **Note:** The app also carries out postings at adjustment levels that are locked for other postings.
### Reclassification
In the **Reclassification** step, specify the details for the reclassification.
Step 'Reclassification'
The following options must be configured in the **Reclassification** step:
| Option | Description |
|---|---|
| **Net retained earnings** | Account and/or the item(s) containing the transfer accounts of the period result.
The transaction figure of the selected account or item for the **Net retained earnings** is used as the base value for the reclassification within the app. |
| **Reclassification** | - **Reclassification at cost center level** — Activate this option to perform the reclassification at cost center level. If this option is activated, the reclassification is performed separately for each cost center. - **Cancellation of net retained earnings** — The account for the cancellation of the result for the period under consideration. With the exception of transfer accounts, all elements of type **User-defined account** with the period type **Balance with carry forward from previous period** can be selected. - **Carry forward account** — The carry forward account to which the result for the period under consideration is to be reclassified. With the exception of transfer accounts, all elements of type **User-defined account** with the period type **Balance with carry forward from previous period** can be selected. - **Transaction type** — The transaction type that the reclassification is to be performed in. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing an App for Reclassification of Profit or Loss from Previous Periods in Reporting Entities
You can execute the app for **Reclassification of profit or loss from previous periods in reporting entities** either **separately** or together with other apps in an **executable folder**.
### Executing the App Separately
To execute the app separately, click **Execute** at the top right of the **app's editing dialog**:
Executing the app separately
### Combining Apps and Executing Them Together
For better organization, you can create as many folders as you like in a directory structure.
You can group multiple apps together in folders and execute them together. Proceed as follows:
1. Ensure that the object type **Folder** has been [enabled for](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md) the directory structure in the [workspace configuration](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche.md).
2. In the tree view, select the element under which you want to create the executable folder and choose **Create | Folder** from the context menu.
3. Enter a Name in the **Create folder** dialog and select a desired **Behavior** if there should be an error during execution of the folder:
- **Continue execution**
- **Cancel execution**
4. Save the executable folder.
5. Paste the apps to be summarized into the folder. Do one of the following:
- Add existing elements using the menu commands **Cut and Paste**.
- Create new apps in the folder using the **Create** context menu command.
6. Execute the folder and all elements contained in it by clicking **Execute all subordinate elements** in the detail view of the folder.
Executing apps together in a folder
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
> **Note:** For a detailed history of past executions, including the process log of each run, open the **Execution log** tab in the app's change log. For details, see [Viewing the Execution Log and Process Logs](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/change-log.md#viewing-the-execution-log-and-process-logs).
Tab 'Created Elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the Properties of the App
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Reclassification of profit or loss from previous year in consolidation areas"
description: "You can use the Reclassification of profit or loss from previous year in consolidation areas app to automatically reclassify the period result from the previous year to carry it forward."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/configuring-consolidation-apps/reclassification-of-profit-or-loss-in-consolidation-areas
language: en
last_updated: 2026-05-01
---
# Reclassification of Profit or Loss from Previous Year in Consolidation Areas
## Overview
You can use the **Reclassification of profit or loss from previous year in consolidation areas** app to automatically reclassify the period result from the previous year to carry it forward. The following functional topics are covered:
- Reclassification of the period result from the previous year to carry it forward in local currency
- Fixation of the historical exchange rate at foreign currency companies (in different display currencies)
Reclassification is performed for all consolidation units of the group:
- At the selected data level of the group
- For the selected adjustment level(s)
- With the configured transaction type
## Configuring the Reclassification of Profit or Loss from Previous Year in Consolidation Areas
To configure the app for the **reclassification of profit or loss from previous year in consolidation areas**, click the app in the structure view and click **Edit** in the displayed dialog.
Configure the steps as described below.
### Settings
In the **Settings** step, specify the general settings for the configuration:
Step 'Settings'
| Option | Description |
|---|---|
| Postings | The **posting month** for the reclassification.
**Note:** The period of the superordinate Consolidated financial statements element is used for the posting. The app reclassifies the profit or loss for the 12 months before the selected posting month. |
| Consolidation area and/or unit | The consolidation units that the reclassification is to be performed for. **By default all** consolidation units of the group are included. If you only want to include certain consolidation units in the consolidation, activate the **Individual selection** check box and select one of the following options: - **Individual**: In the table, select individual consolidation units to be considered. - **Exclude**: In the table, select the consolidation units that are to be excluded. |
### Adjustment levels
In the **Adjustment levels** step, specify the adjustment levels that should be taken into account when reclassifying the prior year's result.
> **Note:** The app also carries out postings at adjustment levels that are locked for other postings.
Step 'Adjustment levels'
### Reclassification
In the **Reclassification** step, specify the accounts that are to be taken into account when reclassifying the period result from the previous year.
Step 'Reclassification'
| Option | Description |
|---|---|
| Net retained earnings | Account and/or item(s) containing the corresponding transfer accounts of the period result. Only the transaction figures from transfer accounts are read out, even if you choose a superordinate item. |
| Cancellation of net retained earnings | Account for the cancellation of the net retained profits or net accumulated losses. With the exception of transfer accounts, all elements of type **User-defined account** with the period type **Balance with carry forward from previous period** can be selected. |
| Carry forward account | Carry forward account to which the period result from the previous year is to be reclassified. With the exception of transfer accounts and the cancellation account, all elements of type **User-defined account** with the period type **Balance with carry forward from previous period** can be selected. |
| Transaction type | Transaction type that the reclassification is to be performed in. |
> **Tip:** - As long as a step has not been fully configured and/or configuration errors exist, it is displayed with a red exclamation mark the red exclamation icon.
> - Once a step is configured completely and without any errors, it is displayed with a green check mark the green check icon.
> - You can close the configuration dialog by clicking the arrow icon at the top left.
> - To change the name of the app, select the app in the tree view and choose **Properties** from the context menu.
## Executing the Reclassification of Profit or Loss from Previous Year in Consolidation Areas
You can execute the app for the reclassification of profit or loss from previous year in consolidation areas either **separately**, together with other apps in an **executable folder** or as part of **consolidated financial statements**.
How to proceed in each case is described under [Execute consolidation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-2/executing-consolidation.md).
## Displaying and Deleting Created Elements
On the **Created elements** tab, the postings that were created during the app execution are shown.
The table provides the following information:
- **Type** of the element
- **Path** under which the element was created When you click on the link, you are taken directly to the posting in the relevant [journal](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale.md) or to the report.
- Date of the **last execution** that created the element
Tab 'Created elements'
If necessary, you can **delete all elements**.
**Note**: Once all elements have been deleted, the state of the wizard is **Not executed** again.
## Displaying the App Properties
The **App properties** are displayed on the tab of the same name:
'Properties' tab
The following **App properties** are displayed:
- **Type** of the element
- Function of the **App**
- **Version** of the element.
**New available version**
As soon as a new version of the app is available that contains changes to the app configuration and/or the calculation logic of the app, the **Refresh** command is displayed, allowing you to update the app to the latest version.
Information about the changes to each version can be found in the **Release Notes**, which can be accessed via the link of the same name.
> **Warning:** We strongly recommend to update all apps to the new version as soon as possible because it cannot be guaranteed how long an app with an obsolete version can be executed.
---
---
title: "Reporting & Analyzing"
description: "The Reporting and analyzing workspace is, by default, the core workspace in Lucanet Consolidation & Financial Planning, and contains all ledgers, schedules, and directory structures created in the Lucanet database."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze
language: en
last_updated: 2026-05-01
---
# Reporting and Analyzing
The **Reporting and analyzing** workspace is, by default, the core workspace in Lucanet and contains all [ledgers](https://support.lucanet.com/en/documentation/glossary.md#ledger), [schedules](https://support.lucanet.com/en/documentation/glossary.md#schedule), and [directory structures](https://support.lucanet.com/en/documentation/glossary.md#directory-structure) created in the Lucanet database. All parts of the annual financial statements can be found in the **Reporting and analyzing** workspace. This includes the balance sheet, P&L, cash flow statement, fixed asset schedule and disclosures. The respective workspaces can be displayed also according to different accounting standards.
The video provides you with an overview of the most important functions in the **Reporting and analyzing** workspace.
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
Video: https://player.vimeo.com/video/858946719?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** To learn how to use Lucanet for your reporting tasks, the [Reporting with Lucanet](https://learning.lucanet.com/catalog/view/course/id/414) training course is available for you to access in the **Lucanet Learning Space**. During the course, you will ...
>
> - find out how to automate existing reports to replace manual creation as much as possible.
> - obtain valuable tips from our experts, in particular on the report variants most suited to you.
> - discover how simple reporting can be – for example whenever important reports are requested at short notice.
- [Elements in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules.md)
- [Functions in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules.md)
- [Display in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules.md)
- [Views in Ledgers and Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules.md)
---
---
title: "Reporting Entities"
description: "In the Reporting entities workspace, you can create all elements to which postings can be made in Lucanet."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities
language: en
last_updated: 2026-09-29
---
# Reporting Entities
## Overview
In the **Reporting entities** workspace, you can create all elements to which postings can be made in Lucanet. In this workspace, the following elements can be created, managed, and deleted:
- [Reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities.md)
- [Consolidation reporting entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/buchungskreise-fuer-konsolidierungsbuchungen-anlegen-und-konfigu.md)
- [Cost center groups](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-cost-centers.md)
- [Cost centers](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-cost-centers.md)
- [Total lines](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/create-configure-total-lines.md)
---
---
title: "Required Keywords"
description: "Required keywords are needed in order for Lucanet to recognize that it is an import. They are entered in column A or the Column definition row."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords
language: en
last_updated: 2026-05-01
---
# Required Keywords
## Overview
Required keywords are needed in order for Lucanet to recognize that it is an import. They are entered in **column A** or the **Column definition** row.
## Keywords in Column A
The following keywords are **required** and **must** be contained in MS Excel in **column A**.
#### Name
Name of the import
> **Warning:** **Important**: If an Excel import with this name already exists on the data level and in the reporting entity, it will be overwritten!
#### Reporting entity/Consolidation area
Name of the reporting entity or the consolidation area for which the import is to be executed
#### Data level
Name of the [data level](https://support.lucanet.com/en/documentation/glossary.md#data-level) into which the import is to be performed
#### Adjustment level
Name of the **adjustment level** on which the posting is to be performed
#### Column definition
Determines what can be found in each column (see next table)
#### Posting date
Date by which the postings are to be created or the values imported
#### Posting/Auto posting
To enable Lucanet to identify which data are to be imported, one of the two keywords must be specified in column A. It is also possible to specify both keywords together as frequently as desired and in any order.
Together with the **Value** column, the keywords **Posting** and **Auto posting** form a matrix structure whose interfaces define the values to be imported.
#### [Auto posting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords/.md#autoposting)
For postings on a planning data level for which the automatic contra entry is defined in Lucanet.
> **Note:** **Note**: The keyword **Auto posting** can only be used when importing data into reporting entities.
#### [Posting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords/.md#posting)
For postings of one-off or rare business transactions.
> **Note:** **Note**: To ensure an integrated balance sheet, P&L, and cash flow statement at this time, only complete postings can be imported into Lucanet. The following applies for every column containing postings: **Debit = credit**.
### Auto Posting
By entering the **Auto posting** keyword, Lucanet recognizes that the delivered account description is for an account for which a contra entry has been defined in the Lucanet journal. This contra entry is listed automatically.
### Posting
You can use the **Posting** keyword to reflect business transactions with the Excel workbook **LUCANET** in Lucanet. These postings can also be made directly in Lucanet via a manual posting.
## Keywords in the Column Definition Row
The following keywords are required and must be included in the **Column definition** row in MS Excel.
| Keyword | Parameter |
|---------|---------|
| Account | Defines that this column contains the account/item descriptions for the import |
| Value | Defines that the column contains the values to be imported |
| Debit | This keyword can be used instead of the keyword **Value** in order to assign additional information to the corresponding value, indicating that it is a **debit** value. |
| Credit | This keyword can be used instead of the keyword **Value** in order to assign additional information to the corresponding value, indicating that it is a **credit** value. |
[Optional keywords](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/optional-keywords.md) are used to import further information.
---
---
title: "Saving and Sharing Views as Favorites"
description: "In the dimension bar of Consolidation & Financial Planning, you can save custom views of a ledger or schedules as favorites. This allows you to quickly access frequently used views without having to reconfigure the dimension bar.\n\nYou can also share your favorite views with other users."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-views-as-favorites-and-share
language: en
last_updated: 2026-05-28
---
# Saving and Sharing Views as Favorites
## Overview
In the dimension bar of Consolidation & Financial Planning, you can save custom views of a ledger or schedules as favorites. This allows you to quickly access frequently used views without having to reconfigure the dimension bar.
You can also share your favorite views with other users.
## Opening the Favorites Menu
To open the Favorites menu, click the star icon in the dimension bar of a ledger or schedule. The Favorites menu appears as follows, for example:
Favorites menu
## Options in the Favorites Menu
The following options are available in the Favorites menu:
### Add to favorites
Select the **Add to favorites** option to save the currently open view of the ledger or schedule as a favorite under a custom name. The favorite will then appear under **My favorites** in the Favorites menu.
### Manage favorites
Using the **Manage favorites** option, you can rename, reorder, and copy existing favorites to share them with other users. The **Manage favorites** dialog appears as follows, for example:
'Manage Favorites' dialog
The following options are available for managing favorites:
| Option | Description |
|---------|---------|
| Rename a favorite | Select a favorite and click **Edit** to change the name. |
| Copy a favorite to share | Select a favorite and click **Copy to share** to copy the favorite to the clipboard and send it to another user. **Note**: In order for other users to open the view shared via the favorite, they must have the appropriate access permissions for the ledger or schedule in question. |
| Create a new favorite folder | Select the **My favorites** root folder and choose **Create | Folder** from the context menu to create a new folder in the Favorites menu. |
| Move a favorite | Select a favorite and choose **Cut** from the context menu. Then paste the favorite into the desired location in the Favorites menu. |
| Change the order of favorites | Select the **My Favorites** root folder and choose **Change order** from the context menu. In the **Change order** dialog, you can then sort the favorites **alphabetically** or drag them **manually** to the desired position. |
| Delete a favorite | Select a favorite and choose **Delete** from the context menu to delete it. |
---
---
title: "Searching in Ledgers and Schedules"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/search-ledgers-schedules
language: en
last_updated: 2026-08-11
---
# Searching in Ledgers and Schedules
## Overview
The **Search** field in the dimension bar lets you find ledger elements — such as items, accounts, formulas, folders, references, and total lines — directly in ledgers and schedules. It is especially useful for large or deeply nested hierarchies, where the element you are looking for may be several levels down, hidden by a collapsed superordinate element, or excluded by a display setting.
## Searching for an Element in a Ledger or Schedule
To search for an element in a ledger or schedule in Consolidation & Financial Planning, click into the **Search** field in the dimension bar and enter part of the name of the element you are looking for.
Press **Enter** to confirm the search.
All matching elements are highlighted, and any collapsed superordinate elements are automatically expanded as needed to display the first matching element, which is also selected.
A counter next to the search field shows your current position among all matches, for example **3 / 8**. Navigating past the last match leads you back to the first one.
Search field in the dimension bar
> **Note:** - The search is not case-sensitive, and it matches your input anywhere in the element's name — at the beginning, in the middle, or at the end.
> - Use the navigation arrows next to the search field, or the **Up** and **Down** arrow keys, to jump to the previous or next matching element.
> - Click **Clear (×)** next to the search field, or press **Esc**, to clear the search.
> - Your search text is retained after you confirm it, so you can keep working while still seeing the highlighted matches. The search field is cleared automatically when you navigate to another workspace.
## Search Scope
- Search results include all elements in the **by Item** hierarchy — items, accounts, formulas, folders, references, and total lines. Drill-downs other than **by Item** (for example, by organization element or by adjustment level) are not part of the search.
- If none of the ledger elements' names match your search input, the search field displays **No results**.
## Searching While Empty Rows or Columns Are Hidden
If you have activated any option under **Hide empty rows and columns** in the [display settings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-display-settings.md) — for example for the accounts/items dimension — starting a search displays a dialog asking you to **reset hidden rows and columns**. Continuing the search turns off that setting so all results are visible.
---
---
title: "Show Postings"
description: "It is possible to display the underlying postings for each value that is displayed for an account in a ledger or in an schedule. The documents belonging to a posting can be opened from within the Show postings dialog."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/postings
language: en
last_updated: 2026-06-03
---
# Show Postings
## Overview
It is possible to display the underlying postings for each value that is displayed for an account in a ledger or in an schedule using the **Show postings** dialog.
For all data imports that are made using a drill down-capable wizard, also data at posting level and, if necessary, even the scanned original document in the source system can be displayed (see [Drilling Down to Original Posting Level](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level.md)).
The following information on a value is displayed in the **Show postings** dialog:
- The **dimension combination** chosen for each value
- If the document overview is displayed for values whose generation involved a currency translation, the **Show postings** dialog is expanded by options and columns for the **currency translation**.
- All **postings**, the posting date, and the corresponding documents are displayed for each value.
In addition, you have the option to create a new **manual posting** or to **delete** a posting directly from the **Show postings** dialog.
## Showing Postings as a Video
The video provides you with the most important information on the topic of **showing postings**.
Video: https://player.vimeo.com/video/882437217?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
## Opening the 'Show Postings' Dialog
The postings underlying an account value in an account hierarchy are displayed in a separate dialog. Double-click the desired value of an account, for example in the general ledger. The dialog is then displayed as follows, for example:
The 'Show postings' dialog is displayed with the 'Posting filters' area highlighted.
### Posting Filters
In the **Posting filters** area, you can choose the dimension combination for which the posting is to be displayed. The following options are available:
| Option | Description |
|---------|---------|
| Account | Account for which postings and posting documents are to be displayed |
| Adjustment level, data level, organization element, partners | Drop-down lists for the respective dimensions for which postings and posting documents are to be displayed |
| Time period | Time period for which postings and posting documents are to be displayed
**Note**: Click **Total period** to display the overview of documents for the entire period to be displayed in the **Data level** drop-down list.
|
| Transaction currency | Drop-down list with all transaction currencies and the default transaction currency of the configured organization element
**Note**: The available transaction currencies correspond to the currencies defined in the **Currency translation** workspace in Lucanet.Financial Client. The values of all business transactions in the chosen transaction currency or currencies are added up and converted into and displayed in the chosen display currency.
|
| Display currency | Drop-down list with all display currencies and the default display currency of the configured organization element
**Note**: The chosen display currency determines the currency in which values are to be displayed. The available display currencies correspond to the displayed currencies defined in the **Currency translation** workspace in Lucanet.Financial Client. To display values in the display currency, the values of all business transactions are converted from their transaction currency into the chosen display currency and added up.
|
### Postings
The **Postings** area displays the postings whose sum total is the value displayed in the tree view.
'Postings' area in the 'Show postings' dialog
The following **display options** are available in the **Postings** area:
- **View subtotals by**: The interval at which subtotals are to be displayed
- **Exchange rate display**: With posting overviews for values whose generation involved a currency translation: limitation of the number of decimal places for the exchange rate display
The following is displayed in the **table**:
| Column | Description |
|---------|---------|
| Date | Date when the document was created |
| Organization element, adjustment level, partners, transaction type | Display of the selected dimensions |
| Transaction figures | Displayed if the transaction currency and display currency vary |
| Exchange rate, transaction currency | If the posting overview is displayed for values whose generation involved a currency translation, the **Show postings** dialog is expanded by columns for the currency translation.
**Note**: Information on the calculation of the exchange rates will be displayed to you if you use the mouse to move over the comment icon.
|
| Posting | Link to the posting data (see following subheading).
**Note**: The **Posting** table column also displays postings that currently cannot be displayed in the Lucanet CFO Solution Platform. If necessary, switch to Lucanet.Financial Client.
|
| Block | When creating postings in Lucanet.Financial Client, the postings can be divided into several blocks for a better overview. These blocks can then be accessed in the **Block** column. |
| Posting text | For each value and each difference in a ledger, comments can be stored in Lucanet.Financial Client, which are displayed in the **Posting text** column. |
## Displaying Posting Data
You can display the posting data of each posting and each data import for each value. To do so, navigate to the row of the desired posting in the **Posting** column in the dialog used to display the postings and click the link. The window used to display the posting data is displayed, for example, as follows:
Dialog 'Posting filters' with the display of posting data
The following **display options** are available to you:
| Display option | Description |
|---------|---------|
| Show cumulated | Display of the total result across all posting periods |
| D/C recording | Switches the display from plus and minus recording to the entry of accounting values in debit and credit |
| Historical exchange rate translation | Used to display historical exchange rates for accounts or posting values for which a translation with historical exchange rates has been defined. The respective accounts or posting values are then displayed as a link and contain details on the translation. |
### Displaying the Historical Exchange Rate Translation
To display the historical exchange rate translation for a value:
1. Click the button **Historical exchange rate translation**.
2. Click on a value in the table that appears as a link. The dialog expands to display the rates used to calculate the value:
Posting data with activated historical exchange rate translation
## Creating a Manual Posting
You can create a manual posting directly from the **Show postings** dialog. Manual postings can be created for all reporting entities or consolidation areas for periods that are not locked for editing.
Proceed as follows:
1. In the **Show postings** dialog, click **Create posting**.
Creating a posting in the 'Show postings' dialog
2. The **Create Posting** dialog is displayed:
'Create Posting' dialog
3. Specify the **name** of the element.
4. If necessary, change the period for the posting.
5. If necessary, change the **currency** in which the posting is to be made.
6. If necessary, change the **adjustment level**.
7. Click **Continue** and follow the steps described in [Configuring a Posting](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/creating-postings-in-ledgers-schedules.md#configposting) to configure the posting details.
## Deleting a Posting
You can delete one or more postings directly from the **Show Postings** dialog, provided they were not generated by an app or a data import.
To delete a posting in the **Show Postings** dialog, select the row of the desired posting and click **Delete posting**.
Deleting a posting in the 'Show posting' dialog
> **Note:** The user must have write permissions for the ledger or journal containing the posting to be deleted.
---
---
title: "SQL Queries for Lucanet.Financial Warehouse"
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database/sql-queries-fwh
language: en
last_updated: 2026-10-01
---
# SQL Queries for Lucanet.Financial Warehouse
## Overview
With the following SQL queries, you can check the values in Lucanet.Financial Warehouse. Run the queries with the **Analyze database** function (see [Analyzing Databases](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/analyze-database.md)).
The SQL queries for Lucanet.Financial Warehouse help in the following situations:
- Incorrect values are displayed in Lucanet, but the correct values are contained in Lucanet.Financial Warehouse. In this case, the import into the reporting entities must be checked.
- The expected values are not in Lucanet.Financial Warehouse. In this case, a check must be performed to determine whether the import into Lucanet.Financial Warehouse and the script used for the import were configured correctly.
## Notes on Using SQL Queries
The following notes apply when you use the SQL queries for Lucanet.Financial Warehouse:
- The elements listed under [Placeholders in the Queries](#placeholders-in-the-queries) are placeholders and must be replaced accordingly.
- Individual lines can be commented out using `//`, which means the lines are no longer taken into account in the SQL query.
- Texts, and therefore also dimension values, are put in single quotation marks (`'`). Figures, such as the fiscal year and periods, are not.
- You can combine various queries with `UNION` or `UNION ALL` if the number of result columns, their names, and their data types are identical. With `UNION`, data records that occur multiple times are not returned, which only affects duplicates. With `UNION ALL`, all data records are returned.
- For the SQL statements, the following aliases can be used for the tables, if necessary, to make the queries clearer: `B` for `Bundle`, `OB` for `OpeningBalance`, `FP` for `FinancialPosting`, and `FPL` for `FinancialPostingLine`.
The following operators can be used in the SQL queries for Lucanet.Financial Warehouse:
| Operator | Description |
|---|---|
| `=` | Equal to |
| `!=` | Not equal to |
| `<>` | Not equal to |
| `>` | Greater than |
| `<` | Less than |
| `>=` | Greater than or equal to |
| `<=` | Less than or equal to |
| `BETWEEN x AND y` | Is between value x and y, each included |
| `LIKE %%` | Placeholder for character strings |
| `IN ()` | Matches any value in the specified list |
Examples of the `LIKE` and `IN` operators:
- `"Dim_GLAccount" LIKE '%1000'` means accounts that end with 1000.
- `"Dim_GLAccount" LIKE '1000%'` means all accounts that start with 1000.
- `"Dim_GLAccount" IN ('1000', '2000', '3000')` means the accounts 1000, 2000, and 3000.
Conditions can be linked with `AND`, `OR`, or `NOT`, for example `NOT IN (x, y, z)`, and can be encapsulated using brackets.
## Placeholders in the Queries
The SQL queries for Lucanet.Financial Warehouse contain various placeholders that must be replaced before sending the SQL query:
| Placeholder | Description |
|---|---|
| ReportingEntityCode | Name of the reporting entity |
| AdjustmentLevelCode | Name of the adjustment level |
| DataLevelCode | Name of the data level |
| FiscalYear | Fiscal year |
| Period | Posting period |
| Account, and more | Dimension value |
## Available Dimension Codes
The following default dimensions are available in Lucanet.Financial Warehouse, if configured:
| Dimension code | Description |
|---|---|
| GLAccount | Ledger account |
| GroupAccount | Group account |
| SubLedgerAccount | Sub-account of ledger account, for example debtor, creditor, or asset |
| CostCenter | Cost center |
| FunctionArea | Functional area |
| LegalEntityPartner | Partner |
| TransactionType | Transaction type for schedules |
| BusinessUnit | Business unit |
| CostElement | Costs and/or revenue type from cost accounting |
| CostUnit | Cost unit |
| Order | Order |
| OrganizationUnit | Organization unit |
| ProfitCenter | Profit center |
| Project | Project |
| StatisticAccount | Statistical account |
> **Note:** Dimension codes are specified for querying the master data from the `ElementAttribute` table without `Dim_`, for example `GLAccount` instead of `Dim_GLAccount`. For the `ElementCode` of subledger accounts (`SubLedgerAccount`), a prefix is usually used that specifies the account more specifically: `C_` for creditors, `D_` for debtors, and `A_` for assets.
## Example Queries
The following sections contain example queries for Lucanet.Financial Warehouse.
### Determining the BundleCode
Determines the BundleCode for a specific reporting entity and fiscal year. The last executed import comes first.
```sql
SELECT *
FROM "Bundle"
WHERE
"LegalEntityCode" = 'ReportingEntityCode'
AND "FiscalYear" = FiscalYear
ORDER BY
"CreationDateTime"
```
### Determining All Postings
Determines all postings for a specific reporting entity, fiscal year, and period. It is possible to restrict the result to various dimensions.
```sql
SELECT "FPL".*
FROM "FinancialPostingLine" "FPL"
INNER JOIN "Bundle" "B"
ON "FPL"."BundleCode" = "B"."BundleCode"
INNER JOIN "FinancialPosting" "FP"
ON "FPL"."BundleCode" = "FP"."BundleCode"
AND "FPL"."FinancialPostingCode" = "FP"."FinancialPostingCode"
WHERE
"B"."LegalEntityCode" = 'ReportingEntityCode'
AND "B"."FiscalYear" = FiscalYear
AND "FPL"."Period" = Period
AND "FPL"."Dim_GLAccount" = 'Account'
AND "FPL"."Dim_SubLedgerAccount" = 'SubLedger'
AND "FPL"."Dim_LegalEntityPartner" = 'PartnerCode'
AND "FPL"."Dim_CostCenter" = 'CostCenter'
AND "FPL"."Dim_TransactionType" = 'TransactionType'
```
### Determining Opening Balance Sheet Values
Determines the opening balance sheet values for a specific reporting entity and fiscal year. It is possible to restrict the result to various dimensions.
```sql
SELECT "OB".*
FROM "OpeningBalance" "OB"
INNER JOIN "Bundle" "B"
ON "OB"."BundleCode" = "B"."BundleCode"
WHERE
"B"."LegalEntityCode" = 'ReportingEntityCode'
AND "B"."FiscalYear" = FiscalYear
AND "OB"."Dim_GLAccount" = 'Account'
AND "OB"."Dim_SubLedgerAccount" = 'SubLedger'
AND "OB"."Dim_LegalEntityPartner" = 'PartnerCode'
AND "OB"."Dim_CostCenter" = 'CostCenter'
AND "OB"."Dim_TransactionType" = 'TransactionType'
```
### Determining the Balance
Determines the balance for a specific reporting entity and fiscal year. It is possible to restrict the result to the period and to various dimensions.
```sql
SELECT 0 AS "Period", SUM("Debit"-"Credit") AS "Value"
FROM "OpeningBalance" "OB"
INNER JOIN "Bundle" "B"
ON "OB"."BundleCode" = "B"."BundleCode"
WHERE
"B"."LegalEntityCode" = 'ReportingEntityCode'
AND "B"."FiscalYear" = FiscalYear
AND "OB"."Dim_GLAccount" = 'Account'
AND "OB"."Dim_SubLedgerAccount" = 'SubLedger'
AND "OB"."Dim_LegalEntityPartner" = 'PartnerCode'
AND "OB"."Dim_CostCenter" = 'CostCenter'
AND "OB"."Dim_TransactionType" = 'TransactionType'
UNION ALL
SELECT "FPL"."Period", SUM("Debit"-"Credit") AS "Value"
FROM "FinancialPostingLine" "FPL"
INNER JOIN "Bundle" "B"
ON "FPL"."BundleCode" = "B"."BundleCode"
INNER JOIN "FinancialPosting" "FP"
ON "FPL"."BundleCode" = "FP"."BundleCode"
AND "FPL"."FinancialPostingCode" = "FP"."FinancialPostingCode"
WHERE
"B"."LegalEntityCode" = 'ReportingEntityCode'
AND "B"."FiscalYear" = FiscalYear
AND "FPL"."Period" <= Period
AND "FPL"."Dim_GLAccount" = 'Account'
AND "FPL"."Dim_SubLedgerAccount" = 'SubLedger'
AND "FPL"."Dim_LegalEntityPartner" = 'PartnerCode'
AND "FPL"."Dim_CostCenter" = 'CostCenter'
AND "FPL"."Dim_TransactionType" = 'TransactionType'
GROUP BY "FPL"."Period"
```
### Determining Element Master Data
Determines the master data for a specific reporting entity, fiscal year, and element. It is possible to restrict the result to various dimensions.
```sql
SELECT *
FROM "ElementAttribute"
WHERE
"LegalEntityCode" = 'ReportingEntityCode'
AND "FiscalYear" = FiscalYear
AND "DimensionCode" = 'DimensionCode'
AND "ElementCode" = 'ElementCode'
```
---
---
title: "Statements"
description: "Using statements in a tilde formula, you can dynamically insert or name rows and columns in an Excel report with Lucanet.Excel-Reporting."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/statements
language: en
last_updated: 2026-05-01
---
# Statements
## Overview
Using statements in a tilde formula, you can dynamically insert or name rows and columns in an Excel report with Lucanet.Excel-Reporting.
## Tilde Formula Structure for Statements
For statements, the tilde formula must be structured as follows:
**~statement:"Parameter_1";"Parameter_2"**
## Rules for Statements in Tilde Formulas
The following rules apply for statements in tilde formulas:
- Statements always end with a colon ( : ) followed by the parameters of the statement.
- The parameters for a statement must be within inverted commas ( " ).
- Several parameters are separated using semicolons ( ; ).
## Available Statements
The following statements can be used in a tilde formula:
### Naming Rows/Columns
You can use the **Row** and **Column** statements to name the corresponding row or column so that they can be accessed in functions using the name, as well as the row or column number.
The advantage of accessing by name is that functions will retain the correct cell link even after rows and columns are inserted (which can change the numbering of existing rows and columns).
**Structure of the Tilde Formula for Naming Rows and Columns**
The tilde formula must be structured as follows:
**~Row/Column:"Name"**
**Note**: The name of the row or column cannot match a placeholder name.
**Example**
In the following reporting template, **row 5** is named **Period**. In the **Value** function, the name **Period** is used to access the row with the period headings:
Statement for naming a row
The generated report is displayed as follows:
Result of the ‘row’ statement
### Inserting Rows/Columns
The **Fill rows** and **Fill columns** statements can be used to insert further rows or columns dynamically, based on the respective row in an Excel report.
**Structure of the Tilde Formula for Inserting Rows and Columns**
The tilde formula must be structured as follows:
**~Fill rows/Fill columns:Keyword=Item/Organization element/Partner/Transaction type/Adjustment level/Data level;\[Abbreviation\];\[Name/OID\];\[No zero values\];\[Level\]**
The **Abbreviation, Name/OID, No zero values**, and **Level** parameters can be used optionally depending on the parameter.
**Keywords for Items and Organization Elements**
**Items**, **accounts** or **organization elements** can be inserted in the rows or columns of an Excel worksheet. The following keywords are available:
- **Item="Assets”** or **Pos="assets"** All items or accounts directly subordinate to the **Assets** item
- **Item=B7** or **Pos=B7** All items or accounts directly subordinate to the item in cell **B7**
- **Organization element="Group”** or **OE="Group"** All organization elements directly subordinate to the organization element **Group**
- **Organization element=B** or **OE=B** All organization elements directly subordinate to the organization element in column **B**
**Keywords for Dimension Elements**
Elements from the **Partner**, **Data levels**, **Adjustment levels**, and **Transaction types** workspaces can be added to the rows or columns of an Excel worksheet. This means that the partners, data levels, adjustment levels, or transaction types that are attached under folders can be added. For partners, it is also possible to add elements that lie under partner groups.
The following keywords are available:
- **Partner="U.S. subsidiary”** or **P="U.S. subsidiary"**
All partners directly subordinate to the **U.S. subsidiary** partner group
- **Data level=lucanet://db=database&oid=123456** or **DL=lucanet://db=database&oid=123456**
All data levels directly subordinate to the folder with the OID **123456**
- **Adjustment level=lucanet://db=database&oid=234567** or **BE=lucanet://db=database&oid=234567**
All adjustment levels directly subordinate to the folder with the OID **234567**
- **Transaction type=lucanet://db=database&oid=345678** or **TT=lucanet://db=database&oid=345678**
All transaction types directly subordinate to the **345678** folder
> **Note:** - Folders for **data levels**, **adjustment levels**, and **transaction types** cannot be queried by their names. They must be targeted by their OID.
> - Since Lucanet 11 LTS, links to Lucanet elements are created in format ln:goto/LNFC/databasename?oid=XXXXX. The previous format lucanet://db=databasename&oid=XXXXX remains valid, however, and can still be used. This is why the format lucanet://db=databasename&oid=XXXXX is used in some examples for Lucanet.Excel-Reporting.
**Example**
The Excel worksheet contains a tilde formula with the **Fill rows** statement. The formula uses the URL of the item **Other operating expenses**:
'Fill rows' statement
The report created displays all the items contained in **Other operating expenses**. **Row 19** displays the overall total of all items:
Result of a 'Fill rows' statement
**Optional Parameters**
Depending on the parameter, the following optional parameters can be used for the **Fill rows** and **Fill columns** statements:
- With the **Item** parameter: Abbreviation, Level, No zero values, Name/OID
- With the **Organization element** parameter: Abbreviation, Level, No zero values, Name/OID
- With the **Partner** parameter: Level, No zero values, Name/OID
- With the **Data level** parameter: No zero values, Name/OID
- With the **Adjustment level** parameter: No zero values, Name/OID
- With the **Transaction type** parameter: No zero values, Name/OID
### Abbreviation
**Abbreviation** parameter is optional and specifies the **ledger** or **schedule** from which items or accounts are to be inserted. The **Abbreviation** parameter is used if an item or account occurs in several ledgers or schedules.
**Note**: In schedules, you can only search for items.
**Tilde Formula Structure for 'Abbreviation'**
The tilde formula must be structured as follows:
~Fill rows/Fill columns:Abbreviation="_Abbreviation_";Item="_Item_"/Organization element="_Organization element_"
**Keywords**
The keyword defines from where the data to be read in are derived. The following keywords are allowed:
- **Abbreviation of a general ledger, abbreviation of a general ledger including subledgers** or **abbreviation of an schedule**
Reading in values from ledgers or schedules with the specified abbreviation
- **fin**
The keyword fin can still be used to read values from the ledgers to which the balance sheet and P&L from previous versions have been transferred.
- **stat**
The keyword stat can still be used to read values from a statistical ledger to which the values from previous versions have been transferred.
**Example for 'Abbreviation'**
The statement **Fill rows** imports all items below **Assets** from the general ledger for the balance sheet with the abbreviation **B** to MS Excel:
'Fill rows' statement with parameter 'Abbreviation'
### Level
The **Level** parameter is optional and specifies which level under the selected item, account, organization element, or partner group is to be read in to MS Excel. If the parameter is not specified, only the subsequent level is inserted.
**Tilde Formula Structure for 'Level'**
The tilde formula must be structured as follows:
~Fill rows/Fill columns:Keyword=Item/Account/Organization element/Partner group\\Level= **x**
**Values for 'Level'**
The following **level** values are possible:
- **Number, e.g. 2**
Inserts the level defined with the number under the specified item, account, organization element, or partner group. When a level lower than the first level is inserted, the system does not insert all the elements from the intermediate levels but just the elements that are located on the level entered.
- **Account**
Inserts all accounts under the specified account in alphabetical order
- **Item**
Inserts all lowest-level items under the specified item that have no subordinate elements in alphabetical order
**Note**: For partner groups, only the entering of a number (e.g. **Level=2**) is permitted for **Level**. The **account** and **item** parameters are not allowed.
**Example for 'Level'**
The statement specifies that the second level below the item with the URL lucanet://db=demo&oid=2408240 (= Other operating expenses) is to be read in to MS Excel:
'Fill rows' statement with parameter 'Level'
In Lucanet, there are two levels under the **Other operating expenses** item:
Item with multiple levels
The items and values of the second level are displayed in the report:
Result for parameter 'Level'
### No zero values
The **No zero values** parameter is optional and specifies that rows and columns that contain no values in Lucanet are **not** to be displayed in MS Excel.
**Tilde Formula Structure for 'No zero values'**
The tilde formula must be structured as follows:
~Fill rows/Fill columns:Keyword=Item/Account/Organization element/Partner/Data level/Adjustment level/Transaction type; **No zero values**
### Name/OID
The **Name/OID** parameter is optional and specifies whether the queried elements are to be imported into MS Excel with their name or URL.
**Tilde Formula Structure for 'Name/OID'**
The tilde formula must be structured as follows:
~Fill rows/Fill columns: **name/OID**;Keyword=Item/Organization element/Partner/Data level/Adjustment level/Transaction type
**Keywords**
The keyword defines whether the elements to be read in are to be imported into MS Excel with the name or OID. The following keywords are allowed:
- **Name**
The names of the elements are imported into MS Excel.
- **OID**
The URL of the elements is imported into MS Excel.
**Example**
In **~Fill rows** it is specified that the OIDs of the elements below the item with the URI **ln:goto/LNFC/demo_group?oid=12907** are to be read into MS Excel:
'Fill rows' statement with parameter 'OID'
> **Note:** - If the Name/OID parameter is not used, the names of the queried elements are created in MS Excel.
> - If the OID parameter is used, the **Attribute** function can be used to additionally import the names of the queried elements into MS Excel (see section ['Attribute' Function](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/functions.md#attribute)).
---
---
title: "Synchronizing Planning Data Levels"
description: "If a data level has the status 'The planning data level is not synchronized with the actual data level', then it can be synchronized with the actual data level at any time."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/synchronize-planning-data-level
language: en
last_updated: 2026-05-01
---
# Synchronizing Planning Data Levels
## Overview
If a data level has the status **The planning data level is not synchronized with the actual data level**, then it can be synchronized with the actual data level at any time. All planning data levels are synchronized with the actual data level with the help of the respective link. The balances of the general ledger in the last actual period before the start of the planning period are used as initial values for the planning data levels.
## Synchronizing the Current Planning Data Level with the Actual Data Level
To synchronize the current planning data level with the actual data level:
1. Click the name of the data level in the tree view.
2. Click **Edit** at the top right to open the editing mode.
3. On the **Status** tab click **Synchronize planning data level with actual data level**.
> **Warning:** The planning data level is synchronized with the actual data level without the confirmation message.
## Synchronizing All Planning Data Levels Simultaneously with the Actual Data Level
To synchronize all planning data levels with the actual data level at the same time, click **Synchronize all planning data levels** in the workspace taskbar.
> **Warning:** All planning data levels are synchronized with the actual data level without the confirmation message.
---
---
title: "Transaction Types"
description: "The Transaction types workspace is used to create, administrate, and delete transaction type categories and transaction types."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types
language: en
last_updated: 2026-05-01
---
# Transaction Types
## Overview
The [Transaction types](https://support.lucanet.com/en/documentation/glossary.md#transaction-type) workspace is used to create, manage, and delete [transaction type categories](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types/transaction-type-categories.md) and [transaction types](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/transaction-types/transaction-type-types.md).
Transaction types provide information on the reason for changes to an account. As a result, transaction types allow for seamless integration of schedules and cash flow statements in Lucanet at the level of the individual and consolidated financial statements in accordance with HGB, IFRS, US-GAAP or other guidelines simultaneously.
---
---
title: "Transferring Data from MS Excel to Lucanet"
description: "CFP Add-In for Excel 365 can be used to selectively transfer Excel plannings or Excel postings to the Lucanet database."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet
language: en
last_updated: 2026-05-01
---
# Transferring Data from MS Excel to Lucanet
## Overview
CFP Add-In for Excel 365 can be used to selectively **transfer** Excel plannings or Excel postings to the **Lucanet database**. The format and structure of the **LUCANET** workbook are decisive when transferring Excel data to Lucanet. Data can only be transferred successfully from MS Excel to Lucanet if the workbook has a **specific structure** and contains **keywords**.
You can **transfer** the values from MS Excel to Lucanet via menu command or shortcut.
## Configuring the Excel Worksheet
The Excel workbook must contain the following **elements**:
- For Lucanet to recognize the workbook for import, cell A1 must contain the word **LUCANET**.
- [Keywords](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/.md#keywords) that allow Lucanet to identify and import data and information (in the example in blue font).
- **Parameters** that contain information for importing into Lucanet (example with yellow background).
- The **data to be imported**, which contains the corresponding values (with the white background in the example).
Example for transfer of values to Lucanet
Types of formatting, such as the font size, font, frame, and colors of the Excel spreadsheets, have no influence on the import into Lucanet and are freely selectable.
## Keywords
**Keywords** can be used to define which data needs to be imported from an Excel worksheet. A distinction is made between keywords in **column A** and the ones in the **Column definition** row, as well as between [required](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/required-keywords.md) and [optional](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet/optional-keywords.md) keywords.
### Rules for Keywords
The following rules apply for keywords:
- The order of the keywords in **column A** and the **Column definition** row are freely definable.
- The first column may only contain keywords or the cells must be empty.
- Rows without keywords are skipped by Lucanet and not imported.
## Transferring Postings
You can transfer the values from MS Excel to Lucanet via menu command or shortcut. Do one of the following:
- Click **Transfer**
- The following shortcut, depending on the language of MS Excel:
- German: **Ctrl+B**
- Spanish: **Ctrl+W**
- English and all other languages: **Ctrl+E**
If the shortcut does not transfer the values, see [Shortcuts of the CFP Add-in for Excel 365 Do Not Work](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/troubleshooting-cfp-add-in.md#shortcuts-of-the-cfp-addin-for-excel-365-do-not-work).
### Choosing a Worksheet
If several worksheets of the open workbook come into question for the import (i.e. several worksheets contain the keyword **LUCANET** in cell A1), you need to specify the worksheets that are to be imported.
To do so, choose the desired worksheet(s) by activating the checkboxes:
---
---
title: "Translation with Historical Exchange Rates"
description: "In the Translation with historical exchange rates posting, the translation with historical exchange rates is defined for accounts. If translation with historical exchange rates is defined for an account then the value which has been calculated originally using the current exchange rate is cleared and the value which has been calculated using the historical exchange rate is posted."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/translation-historical-exchange
language: en
last_updated: 2026-05-01
---
# Translation with Historical Exchange Rates
## Overview
For every reporting entity and consolidation area for which a currency translation is defined (see [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/reporting-entities/manage-reporting-entities.md) and [Creating and Configuring Consolidation Areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md)), a posting of type **Translation with historical exchange rates** is automatically created in the **Journals** workspace.
In the **Translation with historical exchange rates** posting, the translation with historical exchange rates is defined for accounts. If translation with historical exchange rates is defined for an account then the value which has been calculated originally using the current exchange rate is cleared and the value which has been calculated using the historical exchange rate is posted.
The configuration of the automatically created **Translation with historical exchange rates** postings can be edited in the **CFO Solution Platform**.
> **Note:** To define fixed historical exchange rates **individually at the posting value level**, see [Historical Exchange Rate Translation](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/create-configure-posting-reporting-entity.md#historical-exchange-rate).
## Configuring the Translation with Historical Exchange Rates
To edit the configuration of a **Translation with historical exchange rates** posting, click on the posting, and then click **Edit** in the top right.
### General Properties
General properties of a 'Translation with historical exchange rates' posting
In the header, you can change the **name** of the posting.
### 'Historical Exchange Rates' Tab
The following options are available on the **Historical exchange rates** tab:
'Historical exchange rates' tab
### Overview
In the **Overview** area, you configure and define the view and when the historical exchange rate will apply.
| Option | Description |
|---------|---------|
| Issue | Name of the conversion |
| Period | Period within which the conversion is to be used |
| Adjustment level | Adjustment level in which the historical exchange rate will apply |
| Transaction currency | Transaction currency in which the posting is to be made |
### Details
In the **Details** area, you must specify the accounts to be translated with the historical exchange rate specified in the **Overview** area. The following options are available:
| Option | Description |
|---|---|
| **Account** | Account or item for creating the posting |
| **Cost center/ partner/ transaction type** | Allows selection of a cost center/partner/transaction type from the respective drop-down lists |
| **Transaction currency** | Amount to be translated in the transaction currency
Select **C** for credit for equity and liability accounts, and **D** for debit for asset accounts.
**Note:** When the amount to be translated is entered in the **Transaction currency** column, the system automatically calculates the value in the currency column using the historical exchange rate saved in the **Overview** area. |
---
---
title: "Troubleshooting Guide"
description: "This guide serves as a central resource for resolving issues you are facing with the CFP Add-in for Excel 365 efficiently.\n\nEach entry includes the problem description, root cause, and the steps taken to fix it."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/troubleshooting-cfp-add-in
language: en
last_updated: 2026-05-01
---
# Troubleshooting Guide for CFP Add-in for Excel 365
## Overview
This guide serves as a central resource for resolving issues you are facing with the CFP Add-in for Excel 365 efficiently.
Each entry includes the problem description, root cause, and the steps taken to fix it.
The page will be amended continuously to ensure fast, consistent problem-solving.
## Lucanet Formulas Show the Prefix '\_xldudf\_' (e.g., "\_xldudf_LN_VALUE")
### Error Description
You work with the Lucanet.Excel Add-In and notice that your Lucanet formulas are displayed with the prefix **\_xldudf\_**, e.g. \_ **xldudf_LN_VALUE** instead of their expected format (**LN.VALUE**).
This indicates that Excel cannot recognize or resolve the custom Lucanet functions such as LN.VALUE(), LN.ATTRIBUTE(), and other Lucanet-specific formulas used to retrieve data from Consolidation & Financial Planning (CFP).
### When Does the Error Occur?
The error typically occurs when two or more versions of the Lucanet.Excel-Add-In are installed and active simultaneously:
- **Lucanet COM add-in** \- the legacy Lucanet.Excel-Add-In
- **CFP Add-in for Excel 365** – the modern Office 365-compatible version
Since both add-ins use identical formula names, Excel cannot determine which version to execute, causing the function resolution to fail.
### How to Fix the Error
To fix the error, you must deactivate the legacy Lucanet.Excel-Add-In while keeping the CFP Add-in for Excel 365 active. Proceed as follows:
1. Open Excel and go to **File | Options**.
2. In the **Excel Options** dialog, navigate to **Add-ins** in the left sidebar.
3. From the **Manage** drop-down list, select **COM Add-ins** and click **Go**.
Excel options
4. Deactivate the check box for **Lucanet COM add-in**.
5. Click **OK**.
6. Close and restart Excel.
After restart, Lucanet formulas will display correctly without the \_ **xldudf\_** prefix. The COM add-in remains on your system and can be reactivated if needed.
### What Does This Mean for My Workbooks?
Deactivating the COM add-in does not delete it from your system - it simply prevents it from loading when Excel starts. You can reactivate it later if needed by following the same steps and activating the check box again.
The CFP Add-in for Excel 365 will handle all Lucanet formula calculations going forward.
## Automatic Formula Calculation Disrupts the Workflow
### Error Description
When multiple users edit the same Excel file simultaneously using the CFP Add-In for Excel 365, Excel recalculates the formulas very frequently. This slows down MS Excel and affects workflow.
This behavior depends heavily on the file size, the number of formulas, and the number of users editing the file.
### When Does the Error Occur?
This error typically occurs when:
- Multiple users are working on the same workbook at the same time, and
- MS Excel automatically recalculates the formulas (the default behavior for automatic calculation).
### How to Fix the Error
To fix the error, every user working on the file must disable automatic formula calculation in MS Excel.
To do this, open the **Formulas** tab in the Excel ribbon and select the **Manual** option under **Calculation Options**:
Deactivating automatic formula calculation
You can then manually calculate formulas using the **Refresh** button on the **Lucanet CFP Add-in** tab in the Excel ribbon.
## LN Formulas Show a #NAME? Error After Migrating from the COM Add-In
### Error Description
After migrating from the Lucanet COM Add-In to the CFP Add-in for Excel 365, LN formulas in existing workbooks display a **#NAME?** error when the workbook is opened. The formulas do not return data on the first load.
Once a cell containing an LN formula is activated (for example, by pressing **Enter**) or the formula is re-entered manually, the data refreshes correctly.
### Why Does the Error Occur?
The COM Add-In and the CFP Add-in for Excel 365 are built on fundamentally different technologies. When an LN formula is entered using the Lucanet COM Add-In, Excel stores a hidden reference in the cell pointing specifically to that add-in. When the workbook is subsequently opened with only the CFP Add-in for Excel 365 active, Excel cannot find the original add-in reference and displays **#NAME?**.
### How to Fix the Error
To register all LN formulas in the workbook to the CFP Add-in for Excel 365, use Excel's **Find & Replace** function to force Excel to re-evaluate the formulas:
1. Open the affected workbook with the CFP Add-in active.
2. Press **Ctrl+H** to open the **Find & Replace** dialog.
3. In the **Find what** field, enter **=**.
4. In the **Replace with** field, enter **=**.
5. Click **Replace All**.
Excel re-evaluates all formulas in the workbook and registers them under the CFP Add-in for Excel 365. After this step, LN formulas will work correctly on subsequent opens.
> **Note:** This step is required once per workbook after migrating from the COM Add-In to the CFP Add-in for Excel 365.
## Shortcuts of the CFP Add-in for Excel 365 Do Not Work
### Error Description
You press a shortcut of the CFP Add-in for Excel 365, but the add-in does not execute the action. This can affect the following shortcuts of the CFP Add-in for Excel 365:
- **Ctrl+Q**: refreshes all Lucanet formulas
- **Ctrl+B**, **Ctrl+W**, or **Ctrl+E**: transfers the values from MS Excel to Lucanet. The shortcut depends on the language of MS Excel: **Ctrl+B** for German, **Ctrl+W** for Spanish, and **Ctrl+E** for English and all other languages. For more information, see [Transferring Data from MS Excel to Lucanet](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/cfp-add-in/transferring-data-to-lucanet.md).
### Why Does the Error Occur?
MS Excel uses some shortcuts of the CFP Add-in for Excel 365 for its own features, too. For example, **Ctrl+Q** opens **Quick Analysis** in MS Excel. When you press such a shortcut for the first time, MS Excel displays the dialog **Ctrl+Q is being used for multiple features** and asks which feature the shortcut should execute:
- the MS Excel feature, for example **Quick Analysis**
- the action of the CFP Add-in for Excel 365, for example **Refresh All Formulas (Lucanet CFP Add-in)**
MS Excel saves your choice for the user and the device. If you selected the MS Excel feature, the shortcut no longer executes the action of the CFP Add-in for Excel 365.
### How to Fix the Error
To fix the error, reset the shortcut preferences of the Office add-ins in MS Excel and then assign the shortcut to the CFP Add-in for Excel 365:
1. In MS Excel, click the **Search** box at the top of the window.
2. Enter **Reset Office Add-in Shortcut Preferences** and select the command of the same name.
Resetting the shortcut preferences of the Office add-ins
MS Excel deletes all shortcut preferences of your Office add-ins.
3. Press the shortcut of the CFP Add-in for Excel 365 again, for example **Ctrl+Q**.
4. In the dialog ***Shortcut* is being used for multiple features**, select the action of the CFP Add-in for Excel 365, for example **Refresh All Formulas (Lucanet CFP Add-in)**, and click **OK**.
Assigning the shortcut to the CFP Add-in for Excel 365
The shortcut executes the action of the CFP Add-in for Excel 365 again.
> **Note:** If the command **Reset Office Add-in Shortcut Preferences** is not displayed in the search, add it to the Excel ribbon via **File | Options | Customize Ribbon**.
---
---
title: "Updating Data Imports"
description: "Data imports into reporting entities can be updated manually at any time, either individually or combined in folders."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/update-data-imports
language: en
last_updated: 2026-05-01
---
# Updating Data Imports
## Overview
Data imports into reporting entities can be updated manually at any time, either individually or combined in folders.
## Updating Individual Data Imports
Every data import can be updated manually at any time as follows:
1. Navigate to the respective data import in the **Importing data into reporting entities** workspace.
2. Open the edit mode and click **1\. Import.**
Updating individual data import
3. If necessary, specify configuration values in the displayed dialog.
4. Click **Start**.
## Updating Data Imports Combined in Folders
To maintain an overview when there are many data imports (e.g. for partial imports for every department or branch), folders can be created. Several data imports can be combined in these folders.
All data imports that are combined in a folder can be updated together.
To do so, navigate to the respective folder and click **Update all subordinate data imports**:
Updating all data imports in a folder
---
---
title: "User Interface of Lucanet Consolidation & Financial Planning"
description: "This page contains information about the structure of the user interface and the most important elements in Lucanet Consolidation & Financial Planning. From this page, you can jump easily to the detailed descriptions of the individual areas and functions."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/user-interface-cfp
language: en
last_updated: 2026-05-01
---
# User Interface of Lucanet Consolidation & Financial Planning
## Overview
This page contains information about the structure of the user interface and the most important elements in **Lucanet Consolidation & Financial Planning**. From this page, you can jump easily to the detailed descriptions of the individual areas and functions.
## Structure of the User Interface
After opening the **Consolidation & Financial Planning** solution from the main menu, the application window of Lucanet Consolidation & Financial Planning is displayed. The application window is usually divided into the following sections: **overview**, **tree view**, **dimension bar**, **status bar**, and **detail view**. Which of these elements are displayed depends on the selected function area or workspace.
For example, the general ledger under **Reporting and Analyzing** is displayed as follows:
User interface of the general ledger under 'Reporting and Analyzing'
Depending on which function area or workspace is displayed, the following elements are available in the user interface:
#### Overview
Contains the functional areas and their associated workspaces
#### Dimension bar
Used to configure the dimensions for displaying values, widgets, or journals in **Consolidation & Financial Planning**. The settings made and the chosen dimensions determine the display in the tree view. The dimension bar contains different dimensions, depending on the workspace, see:
- **Dashboards** workspace: [Configuring the Dashboard](https://support.lucanet.com/en/documentation/consolidation-financial-planning/dashboard/display-configure-dashboard.md)
- **Reporting and analyzing** workspace: [Configuring the Dimension Bar](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/display-ledgers-schedules/configure-dimension-bar.md)
- **Journals** workspace: [Using Journals](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/use-journals.md)
#### Tree view
Shows all elements of the respective workspace , e. g. the items and accounts of the balance sheet according to the IFRS.
> **Warning:** The functions available in the tree view are described under [Functions in the Tree View](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-in-the-tree-view.md).
#### Status bar
Shows the total of the values in marked cells, the number of marked cells, and additional values
#### Detail view
Displays the properties of an element or the values of items or accounts from ledgers in a chart. What is displayed in the detail view depends on which workspace has been chosen.
The detail view is only available for the functional areas **Reporting and Analyzing** and **Import and Journals**.
> **Tip:** For more information on showing and hiding the different components, see [Functions Used to Change the Display](https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/functions-used-to-change-the-display.md).
---
---
title: "Using Journals"
description: "In the Journals workspace, you can choose journals and display the details of the associated postings."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/journale/use-journals
language: en
last_updated: 2026-06-04
---
# Using Journals
## Overview
In the **Import and** **Journals** workspace, you can choose journals and display the details of the associated postings.
## Displaying Journals
In the overview, navigate to the **Import and Journals** functional area and click **Journals**. The **Journals** workspace is displayed as follows, for example:
Tree and detail view of a journal
All elements associated with the journal are displayed in the tree view.
The detail view contains detailed information on the journal including all subordinate elements and any additional information.
## Configuring Journals
Different journals are displayed, depending on which [data level](https://support.lucanet.com/en/documentation/glossary.md#data-level) and [reporting entity](https://support.lucanet.com/en/documentation/glossary.md#reporting-entity) or [consolidation area](https://support.lucanet.com/en/documentation/glossary.md#consolidation-area) you choose.
To choose the desired journal:
1. Choose the desired data level in the **Data level** drop-down list.
2. Choose the desired reporting entity or consolidation area in the **Reporting entity or consolidation area** drop-down list.
'Data level' and 'Reporting entity or consolidation area' dropdown lists in the 'Journals ' workspace
---
---
title: "Using Keyboard Shortcuts"
description: "To accelerate operation and navigation, a range of shortcuts is available in ledgers and schedules."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/general-functions/using-keyboard-shortcuts
language: en
last_updated: 2026-05-01
---
# Using Keyboard Shortcuts
## Overview
To accelerate operation and navigation, a range of shortcuts is available for different areas of the software in Consolidation & Financial Planning.
## Available Keyboard Shortcuts for Ledgers and Schedules
The following keyboard shortcuts are available for ledgers and schedules:
| Shortcut | Description |
|---------|---------|
| Ctrl + C or Alt + C | Copy |
| Ctrl + V or Alt + V | Paste |
| Alt + R | Inserting as reference |
| Ctrl + X or Alt + X | Cut |
| Tab | Skip to next cell |
| Shift + Tab | Skip to previous cell |
| ↓ | Navigate down |
| ↑ | Navigate up |
| **←** | Navigate to the left |
| **→** | Navigate to the right |
| Del | Delete |
## Available Keyboard Shortcuts for Tables
The following keyboard shortcuts are available for tables:
| Shortcut | Description |
|---------|---------|
| Ctrl + C | Copy |
| Ctrl + V | Paste |
| Ctrl + X | Cut |
| Alt + S | Save |
| Alt + T | Resolve difference (postings) |
| Tab | Skip to next cell |
| Shift + Tab | Skip to previous cell |
| ↓ | Navigate down (adds a new row when on the last row) |
| ↑ | Navigate up |
| **←** | Navigate to the left |
| **→** | Navigate to the right |
| Del | Delete row |
| Enter | Confirm changes or start editing the cell |
| Esc| Cancel changes |
> **Note:** - Arrow keys move between cells when a cell is not being edited; while editing, they only move the cursor within the cell.
> - Tab and Shift + Tab always move to the next or previous cell, whether or not you are editing.
## Available Keyboard Shortcuts for the Tree View
The following keyboard shortcuts are available for the tree view:
| Shortcut | Description |
|---------|---------|
| Ctrl + C or Alt + C | Copy element |
| Ctrl + V or Alt + V | Paste element |
| Ctrl + X or Alt + X | Cut element |
| Tab | Go to next element |
| Shift + Tab | Go to previous element |
| ↓ | Navigate down |
| ↑ | Navigate up |
| **←** | Collapse element |
| **→** | Expand element |
| Del | Delete |
## Available Keyboard Shortcuts for the Period Window
The following keyboard shortcuts are available for the period window:
| Shortcut | Description |
|---------|---------|
| F9 | Open the period window |
| Space | Change periodicity |
| **←** | Move to the left |
| **→** | Move to the right |
| Enter | Save settings |
## Available Keyboard Shortcuts for Drop-down Menus
The following keyboard shortcuts are available for navigating and selecting elements in drop-down menus::
| Shortcut | Description |
|---------|---------|
| Space | Opens the drop-down menu |
| ↓ | Navigate down |
| ↑ | Navigate up |
| **→** | Expand element |
| **←** | Collapse element |
| Enter | Select element |
## Available Keyboard Shortcuts for Context Menus
The following keyboard shortcuts are available for navigating and selecting elements in context menus::
| Shortcut | Description |
|---------|---------|
| ↓ | Navigate down |
| ↑ | Navigate up |
| **→** | Expand menu option |
| **←** | Collapse menu option |
| Enter | Confirm menu option |
| ESC | Close context menu |
## Available Keyboard Shortcuts for the Detail View
The following keyboard shortcuts are available for the detail view:
| Shortcut | Description |
|---------|---------|
| Alt + S | Save |
| F6 | Start edit mode |
> **Note:** Most of the keyboard shortcuts described in this article also work in the detail view and in dialogs.
---
---
title: "VAT/Input Tax Administration"
description: "For the purposes of planning in Lucanet, it is possible to create VAT and input VAT configurations that can be taken into account as part of the configuration of accounting rules for accounts and items in the general ledger and subledgers."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/vat-input-tax
language: en
last_updated: 2026-05-01
---
# VAT/Input VAT Administration
## Overview
For the purposes of planning in Lucanet, it is possible to create **VAT and input VAT configurations** that can be taken into account as part of the configuration of accounting rules for accounts and items in the general ledger and subledgers.
## Creating VAT Configurations
To create a VAT configuration:
1. Open the **Accounting rules** workspace.
2. In the dimension bar, click the **VAT** button. The VAT configuration dialog is displayed.
3. Right-click a journal folder in the tree view, then select **Create VAT configuration** from the context menu. The **Create New VAT Configuration** dialog is displayed:
'Create new VAT configuration' dialog
4. Enter a name for the VAT tax configuration in the **Element name** field.
5. Click **Save**.
## Configuring VAT Configurations
To configure a VAT configuration:
1. In the dimension bar, click the **VAT** button. The VAT configuration dialog is displayed.
2. Select the combination of **data level** and reporting entity for which you want to edit the VAT configuration.
3. In the tree view, select the desired VAT configuration.
4. Click **Edit** in the top right to open editing mode.
The following configuration options are available:
Configure VAT configuration dialog
#### Configuration
The following options must be configured:
| Option | Description |
|---|---|
| **Percentage** | Tax rate of the VAT/input VAT in percent |
| **Basis** | Periodicity for the tax calculation |
| **Payment to the tax authority** | Indicates when the tax liabilities will be paid (see [Configuring cash flow impact](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules/configure-payment.md#cashflowimpact)) |
| **Disclose VAT/input VAT by** | The time for the disclosure of the VAT/Input VAT.
**Note:** The chosen time for **Disclose VAT/input VAT by** is taken into account only for accounting rules with the **down payment transaction** payment type. |
#### Posting
The following options must be configured:
| Option | Description |
|---|---|
| **Bank account** | An account from which the particular tax should be paid |
| **Sales account/input tax account** | An account for which the liabilities or receivables should be indicated in the balance sheet |
## Applying VAT Configurations to Other Journals
VAT configurations always apply to a journal, i.e. a particular combination of **data level** and **reporting entity**. To avoid creating a new configuration for each journal it applies to, you can either **copy or move** a VAT configuration to individual journals or you can **apply** a VAT configuration to multiple journals at the same time.
To apply a VAT configuration to multiple journals:
1. Open the **Accounting rules** workspace.
2. In the dimension bar, click the **VAT** button.
3. Select the combination of **data level** and **reporting entity** from which you want to apply the VAT configuration to other journals.
4. Click the apply icon button or right-click the VAT configuration and choose **Apply VAT/Input VAT Configuration to Other Journals.** The following dialog is displayed:
'Apply VAT/Input VAT to other journals' dialog
5. Select the **Data levels** and the **Reporting entities** into which the VAT configurations are to be transferred.
6. Click **Save**.
## Copying and Moving VAT Configurations
You can also copy or move a VAT configuration within a journal or to another journal.
To copy or move VAT configurations:
1. Open the **Accounting rules** workspace.
2. In the dimension bar, click the **VAT** button.
3. Select the combination of **data level** and **reporting entity** from which you want to apply the VAT configuration to other journals.
4. Right-click the VAT configuration and choose **Copy** or **Cut**.
5. Select the combination of **data level** and **reporting entity** into which you want to copy or move the VAT configuration.
6. Right-click the **root folder** of the journal and choose **Paste** from the context menu.
---
---
title: "Views in Ledgers and Schedules"
description: "The Lucanet CFO Solution Platform enables you to use templates to simplify and speed up your reporting (e.g. to report on all planning and business development issues that are important to the company). Recurring reports can be configured as views."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules
language: en
last_updated: 2026-09-29
---
# Views in Ledgers and Schedules
## Overview
The **Lucanet CFO Solution Platform** enables you to use templates to simplify and speed up your reporting (e.g. to report on all planning and business development issues that are important to the company). Recurring reports can be configured as **views**.
> **Note:** **Activating views for the Lucanet CFO Solution Platform**
>
> Views from **Lucanet.Financial Client** can be activated for use in the Lucanet CFO Solution Platform (see [Creating and Configuring Views](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views.md)). [User and access permissions](https://support.lucanet.com/en/documentation/administration/user-management.md)
## Views in Ledgers and Schedules as a Video
The video provides you with the most important information on the topic of **views available in ledgers and schedules**:
Video: https://player.vimeo.com/video/862367056?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
## Choosing Views
Choosing a **view** in the tree view of a ledger or schedule displays the associated **dimension bar**. The configuration of the view defines which dimensions can be configured in the dimension bar.
1. If necessary, navigate to the desired ledger or schedule and open the **View** drop-down list in the dimension bar:
Dimension bar in the Lucanet CFO Solution Platform
2. The drop-down list is displayed as follows:
'View' drop-down list
3. Choose the desired view.
**Note**: Views in the **Public** folder are visible and selectable for all users of the database. Views in the **Private** folder are only visible and selectable for the currently logged-in user.
The dimension bar and associated account hierarchy are displayed as follows, for example:
View with associated account hierarchy
## Organizing Views
Views can be copied, moved, or deleted, and the order of views can be changed. To do so, proceed as follows:
1. Click in the dimension bar in the **Reporting and analyzing** workspace the **View** drop-down list and click **Configure views**.
2. Select the desired view in the tree view and choose the desired menu command from the context menu:
Context menu of a view
**Note**: Views that are grayed out cannot be edited because they are not activated for use in the Lucanet CFO Solution Platform. If necessary, activate additional views in **Lucanet.Financial Client** for use in the Lucanet CFO Solution Platform (see [Creating and Configuring Views](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/views-ledgers-schedules/create-configure-views.md)).
3. If necessary, change the order of the views using drag and drop.
---
---
title: "Wizard for Elimination of Intercompany Income and Expense Based on Group-internal Revenue"
description: "Configuring the wizard-assisted elimination of income and expenses between affiliated companies based on intra-group revenue."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-elimination-intercompany-income-expense-group-internal-revenue
language: en
last_updated: 2026-07-20
---
# Wizard for Elimination of Intercompany Income and Expense Based on Group-internal Revenue
## Overview
The **Elimination of intercompany income and expense based on group-internal revenue** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. In this case, (revenue) accounts previously defined in the **Consolidation areas** workspace are offset with one or more expense accounts with allocation of a percentage.
The wizard for **elimination of intercompany income and expense based on group-internal revenue** is displayed as follows, for example:
Wizard for elimination of intercompany income and expense based on group-internal revenue
The following options must be configured in the **Elimination of intercompany income and expense based on group-internal revenue** wizard:
## General
Edit the general properties of the wizard for elimination of intercompany income and expense based on group-internal revenue in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard |
| **Period** | Time period for which the elimination is to be performed
**Note:** After the period has been changed, it is necessary to update the wizard (see the **Updating Wizard** note below). |
Choose whether you want to **perform consolidation for every month of the time period** or **for the entire period in the last month**.
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
The accounts for the elimination of intercompany income and expense based on the group-internal revenue are displayed on the **Values** tab:
The following options are available:
| Option | Description |
|---|---|
| **Refresh** | Refreshes the values in the wizard. |
| **Resolve differences** | Automatically resolves any differences that may have occurred within a posting. Click on a row that contains differences and then click the **Resolve differences** command. |
| **Show only reporting entities containing values** | Hides all reporting entities that do not contain any values. |
| **Partner** | Shows or hides the **Partner** column |
**'Basis' area**: Accounts for related products according to the configuration of the wizard.
**'To post' area**: Displays the postings that the wizard carries out after saving.
The following options are available in the **To post** area:
- Click a displayed difference account to change it if necessary.
- Click **\+ Add Row** to insert a row and select an additional difference account.
- If necessary, change the amounts to be posted to the difference account by clicking the respective amount.
- If necessary, click the trash can icon if you want to delete a difference account.
Options in the 'To post' area
> **Warning:** If you change the **configuration** of a wizard in the [Consolidation areas](https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-and-configure-consolidation-areas.md) workspace and the change should take effect in the posting, the posting must be deleted in the journal and then created again because the **Update wizard** function only updates the values, but not the structure of the wizard-assisted posting.
---
---
title: "Wizard for Inventory Consolidation"
description: "Configuring the wizard-assisted elimination of intercompany profit or loss contained in inventory between affiliated companies."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-inventory-consolidation
language: en
last_updated: 2026-07-20
---
# Wizard for Inventory Consolidation
## Overview
The **Inventory consolidation** wizard enables the wizard-assisted elimination of intercompany profit or loss contained in stock (inventory) between affiliated companies. Intercompany relationships are formed between reporting entities based on settings previously made in the **Consolidation areas** workspace.
The wizard for **inventory consolidation** is displayed as follows, for example:
Wizard for inventory consolidation
The following options must be configured in the **Inventory consolidation** wizard:
## General
Edit the general properties of the wizard for inventory consolidation in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard |
| **Period** | Time period for which the elimination is to be performed
**Note:** After the period has been changed, it is necessary to update the wizard (see section [Updating Wizard](#updating-wizard)). |
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
All **intercompany relationships** for which the assigned balance sheet items contain values are listed on the **Values** tab.
**Area 'Intercompany relationships'**
- **Refresh**: Refreshes the values in the wizard.
- Select the intercompany relationship in the table whose details you want to view or edit.
The following options are available in the table on the right:
| Option | Description |
|---|---|
| **Contained profit or loss portion** | Percentage of the selected intercompany relationship's balance sheet items that contains intercompany profit or loss. |
| **Deferred tax** | Percentage for deferred tax. Only displayed if **Incorporate deferred tax** was activated in the configuration. |
| **Reclassification within the P&L** | Percentage of the amount to be moved. Only displayed if **Reclassifications within P&L** was activated in the configuration. |
| **Reclassification within the balance sheet** | Percentage of the amount to be moved. Only displayed if **Reclassifications within balance sheet** was activated in the configuration. |
| **Transaction types/Partner** | Shows or hides the **Transaction types** column or the **Partner** column. |
Changes only apply to the selected intercompany relationship; other intercompany relationships remain unaffected.
Below the fields, the **To post** area shows the postings the wizard carries out after saving, grouped by category (**Contained profit or loss portion**, **Deferred tax**, **Reclassification within the P&L**, **Reclassification within the balance sheet**), with the applied percentage shown next to each category.
## Updating Wizard
If you change the period in the **General** area, or click **Refresh** in the **Intercompany relationships** area, the **Update wizard** dialog is displayed:
'Update wizard' dialog
1. Choose the desired configuration for the inventory consolidation.
2. Define which elements should be updated. Do one of the following:
- **Update pair combinations**, if only the pair combinations are to be updated.
**Note**: If the **Retain settings for already existing combinations** check box is deactivated, any settings already created might be overwritten by the configuration settings of the wizard.
- **Fully update the wizard** (including cost center, etc.), to update all settings in the wizard.
3. Click **Update**.
---
---
title: "Wizard for Lump Sum Elimination of Intercompany Debt"
description: "Configuring the wizard-assisted, lump-sum elimination of debts and receivables between affiliated companies."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-debt
language: en
last_updated: 2026-07-20
---
# Wizard for Lump Sum Elimination of Intercompany Debt
## Overview
The **Lump sum elimination of intercompany debt** wizard allows you to perform a wizard-assisted elimination of debts and receivables between affiliated companies. This involves offsetting accounts previously defined in the **Consolidation areas** workspace against one another on a lump sum basis.
The wizard for **lump sum elimination of intercompany debt** is displayed as follows, for example:
Wizard for lump sum elimination of intercompany debt
The following options must be configured in the **Lump sum elimination of intercompany debt** wizard:
## General
Edit the general properties of the wizard for lump sum elimination of intercompany debt in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard |
| **Period** | Time period for which the elimination is to be performed |
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
The accounts and values for the lump sum elimination of intercompany debt are displayed on the **Values** tab:
| Option | Description |
|---|---|
| **Refresh** | Refreshes the values in the wizard. |
| **Resolve differences** | Automatically resolves any differences that may have occurred within a posting. Click on a row that contains differences and then click the **Resolve differences** command. |
| **Show only reporting entities containing values** | Hides all reporting entities that do not contain any values. |
| **Threshold for Display** | Differences above the entered value are highlighted in red in the **Balances** area. |
| **Transaction types/Partner** | Shows or hides the **Transaction types** column or the **Partner** column. |
**'Balances' area**: The **Balances** area shows the accounts to be offset against each other according to the configuration of the wizard.
- If the receivables correspond to the liabilities within the combined pair, the value is displayed in green.
- If there is a difference, it is displayed in red or green – according to the definition of the threshold value.
- To obtain detailed information, click the arrow in front of the desired item.
**'To post' area**: The **To post** area displays the postings that the wizard carries out after saving.
The following options are available in the **To post** area:
- Click a displayed difference account to change it.
- Click **\+ Add Row** to insert a row and select an additional difference account.
- Change the amounts to be posted to the difference account by clicking the respective amount.
- Select **Debit** or **Credit** from the displayed drop-down list.
- If necessary, click the trash can icon if you want to delete a difference account.
Options in the 'To post' area
---
---
title: "Wizard for Lump Sum Elimination of Intercompany Income and Expense"
description: "Configuring the wizard-assisted, lump-sum elimination of income and expenses between affiliated companies."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-lump-sum-elimination-intercompany-income-expense
language: en
last_updated: 2026-07-20
---
# Wizard for Lump Sum Elimination of Intercompany Income and Expense
## Overview
The **Lump sum elimination of intercompany income and expense** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. This involves offsetting accounts previously defined in the **Consolidation areas** workspace against one another on a lump sum basis.
The wizard for **lump sum elimination of intercompany income and expense** is displayed as follows, for example:
Wizard for lump sum elimination of intercompany income and expense
The following options must be configured in the **Lump sum elimination of intercompany income and expense** wizard:
## General
Edit the general properties of the wizard for lump sum elimination of intercompany income and expense in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard |
| **Period** | Time period for which the elimination is to be performed |
Choose whether you want to **perform consolidation for every month of the time period** or **for the entire period in the last month**.
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
The accounts for the lump sum elimination of intercompany income and expense are displayed on the **Values** tab:
| Option | Description |
|---|---|
| **Refresh** | Refreshes the values in the wizard. |
| **Resolve differences** | Automatically resolves any differences that may have occurred within a posting. Click on a row that contains differences and then click the **Resolve differences** command. |
| **Show only reporting entities containing values** | Hides all reporting entities that do not contain any values. |
| **Threshold for Display** | Differences above the entered value are highlighted in red in the **Transaction figures** area. |
| **Partner** | Shows or hides the **Partner** column. |
**'Transaction figures' area**: The **Transaction figures** area shows the accounts to be offset against each other according to the **configuration** of the wizard.
- If the income corresponds to the expenses within the combined pair, the value is displayed in green.
- If there is a difference, it is displayed in red or green – according to the definition of the threshold value.
- To obtain detailed information, click the arrow in front of the desired item.
The **To post** area displays the postings that the wizard carries out after saving.
The following options are available in the **To post** area:
- Click a displayed difference account to change it if necessary.
- Click **\+ Add Row** to insert a row and select an additional difference account.
- If necessary, change the amounts to be posted to the difference account by clicking the respective amount.
- If necessary, choose **Debit** or **Credit** in the displayed drop-down list.
- If necessary, click the trash can icon if you want to delete a difference account.
Options in the 'To post' area
---
---
title: "Wizard for Paired Elimination of Intercompany Debt"
description: "Configuring the wizard-assisted, pair-based elimination of debts and receivables between affiliated companies."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-debt
language: en
last_updated: 2026-07-20
---
# Wizard for Paired Elimination of Intercompany Debt
## Overview
The **Paired elimination of intercompany debt** wizard enables the wizard-assisted elimination of debts and receivables between affiliated companies. Pair combinations of accounts are formed between reporting entities or cost centers based on settings previously made in the **Consolidation areas** workspace.
The wizard for **paired elimination of intercompany debt** is displayed as follows, for example:
Wizard for paired elimination of intercompany debt
The following options must be configured in the **Paired elimination of intercompany debt** wizard:
## General
Edit the general properties of the wizard for paired elimination of intercompany debt in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard. |
| **Period** | Time period for which the elimination is to be performed
**Note:** After the period has been changed, it is necessary to update the wizard (see section [Updating Wizard](#updating-wizard)). |
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
All **pair combinations** of reporting entities between which debt relationships exist are listed on the **Values** tab:
- If the receivables correspond to the liabilities within the combined pair, the value is displayed in green.
- If there is a difference, it is displayed in red or green – according to the definition of the threshold value.
- To obtain detailed information, click the arrow in front of the desired pair combination or item.
**Area 'Pair combinations'**
The following options are available in the **Pair combinations** area:
| Option | Description |
|---|---|
| **Refresh** | Refreshes the values in the wizard. |
| **Resolve differences** | Automatically resolves any differences that may have occurred within a posting. Click on a row that contains differences and then click the **Resolve differences** command. |
Select the pair combination in the table whose details you want to view or edit.
The following options are available in the table on the right:
| Option | Description |
|---|---|
| **Threshold for Display** | Differences above the entered value are highlighted in red in the **Pair combinations** area. |
| **Deferred taxes** | Displays the percentage for deferred taxes.
**Note:** You can currently only take deferred taxes into account and enter a tax rate in Lucanet.Financial Client. |
| **Transaction Types** | Shows or hides the **Transaction Types** column. |
## Updating Wizard
If you change the period in the **General** area, the message **Please update the consolidation wizard** is displayed. Proceed as follows in this case:
1. Click **Update wizard** in the **Pair combinations** area. The **Update wizard** dialog is displayed:
'Update wizard' dialog
2. Choose the desired configuration for the paired elimination of intercompany debt.
3. Define which elements should be updated. Do one of the following:
- **Update pair combinations**, if only the pair combinations are to be updated.
**Note**: If the **Retain settings for already existing combinations** check box is deactivated, any settings already created might be overwritten by the configuration settings of the wizard.
- **Fully update the wizard**, to update all settings in the wizard.
4. Click **Update**.
---
---
title: "Wizard for Paired Elimination of Intercompany Income and Expense"
description: "Configuring the wizard-assisted, pair-based elimination of income and expenses between affiliated companies."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/consolidation/consolidation-1/create-configure-consolidation-wizards/wizard-paired-elimination-intercompany-income-expense
language: en
last_updated: 2026-07-20
---
# Wizard for Paired Elimination of Intercompany Income and Expense
## Overview
The **Paired elimination of intercompany income and expense** wizard enables the wizard-assisted elimination of expenses and income between affiliated companies. Pair combinations of accounts between reporting entities or cost centers are formed based on settings previously made in the **Consolidation areas** workspace.
The wizard for **paired elimination of intercompany income and expense** is displayed as follows, for example:
Wizard for paired elimination of intercompany income and expense
The following options must be configured in the **Paired elimination of intercompany income and expense** wizard:
## General
Edit the general properties of the wizard for paired elimination of intercompany income and expense in the top area of the detail view:
| Option | Description |
|---|---|
| **Name** | Name of the wizard |
| **Period** | Time period for which the elimination is to be performed
**Note:** After the period has been changed, it is necessary to update the wizard (see section [Updating Wizard](#updating-wizard)). |
Choose whether you want to **perform consolidation for every month of the time period** or **for the entire period in the last month**.
| Option | Description |
|---|---|
| **Cost center** | Cost center for the postings |
| **Currency** | Currency, in which the consolidation postings are to be made. By default, the transaction currency of the consolidation area is used. |
| **Basis** | Adjustment level with the data for the generation of the consolidation postings |
| **Target** | Adjustment level on which postings are to be made |
## Values
All pair combinations of reporting entities between which income and expense relationships exist are listed on the **Values** tab:
- If the income corresponds to the expenses within the combined pair, the value is displayed in green.
- If there is a difference, it is displayed in red or green – according to the definition of the threshold value.
- To obtain detailed information, click the arrow in front of the desired pair combination or item.
**Area 'Pair combinations'**
The following options are available in the **Pair combinations** area:
| Option | Description |
|---|---|
| **Refresh** | Refreshes the values in the wizard. |
| **Resolve differences** | Automatically resolves any differences that may have occurred within a posting. Click on a row that contains differences and then click the **Resolve differences** command. |
Select the pair combination in the table whose details you want to view or edit.
The following options are available in the table on the right:
| Option | Description |
|---|---|
| **Threshold for Display** | Differences above the entered value are highlighted in red in the **Pair combinations** area. |
- Click the displayed difference account to change it.
- Click **\+ Add Row** to insert a row and select an additional difference account.
- Change the amounts to be posted to the difference account by clicking the respective amount.
- Select **Debit** or **Credit** in the displayed drop-down list.
- If necessary, click the **trash can icon** if you want to delete a difference account.
Options for a pair combination
## Updating Wizard
If you change the period in the **General** area, the message **Please update the consolidation wizard** is displayed. Proceed as follows in this case:
1. Click **Update wizard** in the **Pair combinations** area. The **Update wizard** dialog is displayed:
'Update wizard' dialog
2. Choose the desired configuration for the paired elimination of intercompany income and expense.
3. Define which elements should be updated. Do one of the following:
- **Update pair combinations**, if only the pair combinations are to be updated.
**Note**: If the **Retain settings for already existing combinations** check box is deactivated, any settings already created might be overwritten by the configuration settings of the wizard.
- **Fully update the wizard**, to update all settings in the wizard.
4. Click **Update**.
---
---
title: "Working with Tilde Formulas"
description: "Tilde formulas are used to create Excel reports. A tilde formula defines which data are to be read in from Lucanet to MS Excel. Tilde formulas always start with a tilde (~) and can contain placeholders, functions and statements."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas
language: en
last_updated: 2026-05-01
---
# Working with Tilde Formulas
## Overview
Tilde formulas are used to create Excel reports. A tilde formula defines which data are to be queried from Lucanet and read into MS Excel.
A tilde formula is inserted into each cell of a reporting template where the queried data should be shown in the final report.
Tilde formulas always start with a tilde (~) and can contain **placeholders**, **functions** and **statements**.
**Example**: Instead of manually entering **Revenue: 150,000** into a table in Excel, you write a tilde formula in a cell, and Lucanet automatically inserts the current value of the revenue into the cell.
## Structure of Tilde Formulas
Tilde formulas are structured as follows:
**~Function/Statement(Parameter_1="Value";...;Parameter_n="Value_n")**
## Components of a Tilde Formula
A tilde formula consists of the following components:
| Placeholder | Description |
|---------|---------|
| Function | Specifies what type of information is queried, such as **value** ("I want to retrieve a value from the database”). Unlike placeholders, which only represent values specified by the user, functions retrieve actual data from Lucanet. Functions contain **basic parameters** that further specify the query and can contain **optional parameters**. |
| Parameter | A question or specification in a formula (e.g. **Which account**) |
| Value | The answer to a parameter's question (e.g., **Revenue**) |
| Keyword | A word that is recognized by the tilde (e.g., **Item**) |
| Placeholder | A variable that is replaced by actual values (e.g., **~Month**) In tilde formulas, placeholders can be used as substitutes for data levels, adjustment levels, organization elements, periods, partners, transaction currencies, display currencies, and time intervals, or as parameters of functions or statements. |
| Cell reference | A reference to one or more columns in Excel (e.g., **A2**, **B:D**) |
| Statement | A command that changes the report structure (e.g., **Fill rows**) |
## Rules for Tilde Formulas
- A tilde formula contains either a **function** or a **statement** with parameters (see section [Functions](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/functions.md) and section [Statements](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/functions.md)).
- A value must be assigned to a parameter with an equal sign ( = ).
- Parameters are separated by a semicolon.
- Values for parameters must be specified in inverted commas ( " ).
- It is also possible to use **placeholders** as parameters (see section [Placeholders](https://support.lucanet.com/en/documentation/consolidation-financial-planning/excel-integration/lucanet-excel-reporting/work-with-tilde-formulas/placeholders.md)).
- No distinction is made between upper case and lower case – unless explicitly specified.
- A tilde formula can use spaces, hyphens ( - ) and underscores ( \_ ).
## Example
A tilde formula can be structured as follows, for example:
**~Value(Item="Revenue"; Period=~Month)**
Lucanet processes this tilde formula as follows:
1. Understands that you want a value
2. Identifies item as "**Revenue**"
3. Uses the month selected in the reporting template (e.g., January 2024)
4. Queries the database
5. Returns as a result, e.g. **150,000**(the actual revenue value for January 2024)
---
---
title: "Workspace Configuration"
description: "In the workspace configuration in the CFO Solution Platform, you can create and configure statistical ledgers for the functional area Reporting and Analysis."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche
language: en
last_updated: 2026-05-01
---
# Workspace Configuration
In the **Workspace configuration**, you can display the overview of Consolidation & Financial Planning and customize it flexibly.
All predefined folders and workspaces—depending on your license scope—are displayed here.
In addition, you can:
- Create custom folders and use them to group items
- [Edit the properties of the general ledger](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/edit-general-ledger-details.md)
- Create and configure the following elements:
- [Subledgers](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-subledger.md)
- [Statistical ledgers](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-statistical-ledger.md)
- [Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-schedules.md)
- [Directory structures](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md)
You can find the **Workspace configuration** in the overview at the bottom left.
Workspace configuration in Consolidation & Financial Planning
- [Creating and Configuring Statistical Ledgers](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-statistical-ledger.md)
- [Creating and Configuring Subledgers](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-subledger.md)
- [Creating and Configuring Schedules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-schedules.md)
- [Creating and Configuring Directory Structures](https://support.lucanet.com/en/documentation/consolidation-financial-planning/konfiguration-der-arbeitsbereiche/create-configure-directory-structures.md)
---
## Lease Accounting
Lucanet Lease Accounting offers you a secure and efficient solution for recording, calculating and posting lease contracts in accordance with IFRS 16.
---
title: "All Steps at a Glance"
description: "In this chapter, you will find the individual steps required to account for your lease relationships. The steps must be carried out in the order provided, and performed separately for each lessee (reporting entity)."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/process-description-lease-accounting
language: en
last_updated: 2026-09-18
---
# All Steps at a Glance
## Overview
In this chapter, you will find the **individual steps** required to account for your leases. The steps must be carried out **in the order provided**, and performed separately for **each** lessee (reporting entity).
The step descriptions also contain links to more detailed descriptions.
### Step 1: Configuring the Basic Settings
In the [Settings](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting.md) area, complete the [general configurations](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/general-configurations-la.md),by selecting the **start of fiscal year** and the **transition date.**
Then create the **lessees**, **asset classes**, and **interest rates** to form the foundation for your data collection and posting.
### Step 2: Selecting Lessees
In the [Get started](https://support.lucanet.com/en/documentation/lease-accounting/select-lessee.md) area, select the lessee for whom you want to enter the lease relationships.
### Step 3: Collecting Data
In the [Data collection](https://support.lucanet.com/en/documentation/lease-accounting/data-collection.md) area, create the leases for each lessee by adding the corresponding **lessors**, **lease contracts**,and **components** required for calculations in accordance with IFRS 16.
### Step 4: Categorizing Components
The [Categorization](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md) area automatically categorizes the created **lease components** and identifies the leases that are classified as ‘regular’ in accordance with IFRS 16.
### Step 5: Measuring Data
In the [Measurement](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) area, **preview** the calculations **Lease Accounting** carries out based on the information you have provided and **check** the data. If the data are correct, you can **save** them straight to the Lease Accounting database here.
### Step 6: Saving Postings
View the calculated components in the [Postings](https://support.lucanet.com/en/documentation/lease-accounting/create-postings.md) area and save the **postings** for the components in the Lease Accounting database.
If necessary, you can **reverse** the postings saved in this area.
### Step 7: Exporting Data
Use the [Export](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) area to export the **postings** you have created, so they can be imported into Lucanet.Financial OLAP Server or another system.
You can also use this area to create and export various types of **reports,** providing you with a summary of different lease accounting data.
---
---
title: "Basic Configuration for Lease Accounting"
description: "Before you can start accounting for your leases in Lucanet Lease Accounting, you will need to configure a few basic settings in the ‘Settings’ area. These will form the foundation for your subsequent use of the solution."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting
language: en
last_updated: 2026-10-02
---
# Basic Configuration for Lease Accounting
## Overview
Before you can start accounting for your leases in Lucanet Lease Accounting, you will need to **configure a few basic settings** in the **Settings** area. These will form the foundation for your subsequent use of the solution. These comprise:
- [Creating and configuring reporting entities](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-lessees.md) so they can be selected as lessees
- [Creating and configuring asset classes](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes.md) so they can be used for interest rates and to categorize lease components
- [Creating and configuring interest rates](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-interest-rates.md) so they can be used to calculate lease payments correctly
- [Creating or importing cost centers](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/import-cost-center.md) so they can be linked to your financial data
- Creating [profit centers](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-profit-centers.md), [accounting areas](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-accounting-areas.md), and [business units](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-business-units.md) as optional master data dimensions that you assign to contract components
> **Note:** The first time you open Lease Accounting, a warning icon appears next to **General configurations**, **Reporting entities**, and **Asset classes** in the **Settings** menu until each section is set up. The icon disappears automatically once the section contains data — for example, after you save the general configurations, import or create a reporting entity, or create an asset class.
>
> the warning appear next to sections that still need to be set up. icon
> Warning icons in the 'Settings' menu
---
---
title: "Calculating Data"
description: "The calculation process in Lucanet Lease Accounting assesses the contract components and liabilities in accordance with IFRS 16 and calculates the values accordingly."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/measurement
language: en
last_updated: 2026-05-01
---
# Calculating Data
## Overview
The **calculation** process in Lucanet Lease Accounting assesses the **contract components** and **liabilities** in accordance with IFRS 16 and calculates the values accordingly.
You can generate a **preview** of the contract component assessment to check that all the information and calculations are correct.
Once this is done, you can start the final **calculation** of the contract components. During calculation, the calculated values for the contract components are saved for future postings.
## Generating a Preview of the Calculated Components
Before saving the assessed and calculated values for the contract components and liabilities in Lease Accounting, you can **preview** the calculated data for every contract component that has already been [categorized](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md).
Proceed as follows for **each individual component**:
1. Open the **Preview** workspace:
The ‘Preview’ workspace
2. Select the **Contract number** and **Component number or ID** for the components you want to calculate.
**Note**: The list includes all the contracts and components that have already been [categorized](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md), but whose final values have not yet been calculated and saved in Lease Accounting.
3. Select whether you want to calculate the **Lease Liabilities** or the **Right-of-Use Asset** for the component.
The **calculation preview** contains a summary of the following information:
- The top section shows the **general information** used to **calculate the components** as per your configuration.
- The table provides details on the **calculated values**.
Example of a calculation preview
> **Tip:** **Exporting Calculation Preview**
>
> You can export the calculated values from the calculation preview table as a CSV or Excel file. To do so, right-click any row and choose **Export | CSV export or Excel export.**
## Performing Final Calculations and Saving Components
Once you have used the preview to check the values of all the components, you can perform the **final calculation** for the calculated values and **save** them in the Lease Accounting database.
To do this, open the **Calculate and save** workspace and click **Calculate and save**.
The 'Calculation' workspace
> **Warning:** The **Calculate and save** button saves **all** the components for the selected reporting entities in the database that have been [categorized](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md) but not yet saved.
>
> As such, make sure you check the values for all the components that can be included in the **Preview** workspace before pressing this button.
---
---
title: "Categorizing Components"
description: "The categorization process in Lucanet Lease Accounting checks all new and modified contract components and classifies them in accordance with IFRS 16."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/categorization
language: en
last_updated: 2026-05-01
---
# Categorizing Components
## Overview
The **categorization** process in Lucanet Lease Accounting checks all **new** and **modified** contract components and classifies them in accordance with IFRS 16.
Contract components that are categorized as **regular leases** are included in all the subsequent calculations carried out by Lease Accounting.
Contract components that are classified as **short-term** or **low-value** are not taken into account for the remainder of the process.
In the **Categorization** workspace, you can:
- view components to be categorized
- categorize components
- view the categorization result
## Categorizing Components
To categorize components, proceed as follows:
1. Open the **Components to be categorized** workspace to view all the components that have been added or modified since the last categorization:
The ‘Components to be categorized’ Workspace
2. Click **Categorize** and confirm the query dialog that appears.
3. Lease Accounting will carry out the categorization process automatically.
## Viewing the Categorization Result
Once categorization is completed, you will find an overview of the categorized components in the **Categorization Result** workspace:
The 'Categorization Result' workspace
> **Note:** - The **Lease category** column shows the categories selected by Lease Accounting in accordance with IFRS 16.
> - Only leases categorized as **Regular** are displayed, because leases in the **Low-value** and **Short-term** categories are not included in the accounting process for leases in accordance with IFRS 16.3-4.
> - If you make any changes to a component, you will need to recategorize said component as described in this section so that the details used by **Lease Accounting** in subsequent calculations are up to date.
---
---
title: "Changing the Lessee of Contract Components"
description: "Transfer active, calculated contract components from one lessee to another via file upload, and undo a change of lessee if necessary."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/change-of-lessee
language: en
last_updated: 2026-10-02
---
# Changing the Lessee of Contract Components
## Overview
With a **change of lessee**, you transfer an active, calculated contract component from one lessee to another lessee as of a transfer date — for example, when a lease is taken over by another company of your group. You do not have to enter the component again for the new lessee.
A change of lessee always produces two results:
- The **source component** is terminated in its reporting entity on the transfer date and receives the component event status **Terminated by change of lessee**.
- A **new component** is created in the target reporting entity as a copy of the source component and receives the status **Added due to change of lessee**. The master data dimensions that you specify for the target — cost center, profit center, accounting area, and business unit — are applied to the new component.
At group level, the disposal in the source reporting entity and the addition in the target reporting entity balance each other out.
Because a change of lessee usually affects several components at once, you transfer the components with a **file upload**: download the template, enter one transfer per row, and upload the completed file in the **Change of lessee** workspace.
## Prerequisites
Lucanet Lease Accounting validates each row of the uploaded file individually. A transfer is only performed if all of the following conditions are met; otherwise, the row is rejected with the reason, and no data is changed for that row:
- The source component is a regular lease, is active, and has been calculated.
- The source reporting entity and the target reporting entity are different.
- The target reporting entity, the target contract, and the master data dimensions specified for the target exist.
- The transfer date is the first day of a month and is in the past.
- The transfer date is within the lease term of the component, is not the start date of the component, and — for transition components — is after the transition date.
- No component events exist on or after the transfer date.
- The liability currency of the source component matches the currency of the target contract.
- The exchange rates required for the currency translation are available (see [Exchange Rate Management](https://support.lucanet.com/en/documentation/administration/exchange-rate-management.md)).
## Transferring Components to Another Lessee
To transfer contract components to another lessee:
1. Navigate to **Data collection | Change of lessee**.
The 'Change of lessee' workspace
2. Click **Download template**. The template is downloaded as an XLSX file and contains the **ChangeOfLessee** sheet with a description and an example for each column, as well as an **Instructions** sheet.
3. Enter one transfer per row in the **ChangeOfLessee** sheet. For each transfer, specify the transfer date, the company code, contract number, and component number of the source component, the company code, contract number, and component number of the target, and the cost center, profit center, accounting area, and business unit to be applied to the target component. The business unit must belong to the target reporting entity or be available for all reporting entities.
4. Upload the completed file in the **Change of lessee** workspace using drag and drop, or click **browse** and select the file. Only the XLSX format is supported.
Lucanet Lease Accounting processes the file in the background. Each valid row is transferred; each invalid row is reported with the reason, and the remaining rows are still processed.
## Undoing a Change of Lessee
You can undo a change of lessee. Undoing recovers the source component and archives the component that was created in the target reporting entity.
To undo a change of lessee:
1. Navigate to **Data collection | Undo change of lessee**.
The 'Undo change of lessee' workspace
2. Select the **Contract** and the **Component** that were created by the change of lessee.
3. Click **Undo change of lessee** and confirm the dialog.
---
---
title: "Collecting Data"
description: "You can use the ‘Data collection’ area in Lucanet Lease Accounting to manually collect or import data on each of your lease relationships. These data include the names of the individual lessors, the lease contracts themselves and contract components. You can also reverse contract components whose numbers have already been added to the database."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection
language: en
last_updated: 2026-05-01
---
# Collecting Data
## Overview
You can use the **Data collection** area in Lucanet Lease Accounting to manually collect or import data on each of your lease relationships. These data include the names of the individual **lessors**, the **lease contracts themselves** and **contract components**. You can also **reverse** contract components whose numbers have already been added to the database.
The data are entered separately for each reporting entity, and used later when accounting the lease relationships. The **Data Collection** area contains the following workspaces:
- [Create and Configure Lessors](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-lessor.md)
- [Create and Configure Contracts](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contracts.md)
- [Create and Configure Contract Components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md)
- [Import Data Automatically](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/automatic-data-import.md)
- [View Import History](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/show-import-history.md)
- [Reverse Components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/reverse-components.md)
> **Warning:** Lucanet Lease Accounting can **only** be used for accounting of **regular lease relationships** in accordance with **[IFRS 16.3-4](https://support.lucanet.com/en/documentation/glossary.md#ifrs-16)**. **Short-term** and **low-value** leases are **not** included in the calculation.
>
> As such, we recommend only using this software to record lease relationships that are categorized as **regular** per IFRS 16.3-4.
---
---
title: "Creating Accounting Areas"
description: "Create accounting areas as a master data dimension and assign them to contract components."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-accounting-areas
language: en
last_updated: 2026-09-02
---
# Creating Accounting Areas
## Overview
Accounting areas are a **master data dimension** in Lucanet Lease Accounting. You can assign an accounting area to a [contract component](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md) in the **General information** tab.
An accounting area applies either to a specific reporting entity or to all reporting entities.
> **Note:** - The **Accounting areas** workspace requires the **Full access administrator** or **Settings administrator** role (see [User Roles](https://support.lucanet.com/en/documentation/lease-accounting/user-roles-la.md)).
> - Accounting areas are also available if you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning. Because this dimension does not exist there, accounting areas are not transferred to Consolidation & Financial Planning.
## The 'Accounting areas' Workspace
The **Accounting areas** workspace lists all accounting areas in a table and is displayed as follows, for example:
The 'Accounting areas' workspace
## Creating Accounting Areas
To create an accounting area:
1. Navigate to **Settings | Accounting areas**.
2. Click **Add accounting area**. The **Add Accounting Area** dialog is displayed:
The 'Add Accounting Area' dialog
3. Specify whether the accounting area is related to a reporting entity:
- If **Is the accounting area related to a reporting entity?** is set to **Yes**, select the **Reporting entity** in the drop-down list. By default, the reporting entity you are signed into is selected.
- If you set the toggle to **No**, the accounting area is available for all reporting entities.
4. Enter the **Name of the accounting area**.
5. Click **Save**. The accounting area is displayed in the **Accounting areas** table and can be assigned to contract components of the corresponding reporting entity.
---
---
title: "Creating and Configuring Asset Classes"
description: "An ‘asset class’ is a group of assets that have similar characteristics and are subject to the same accounting treatment. This classification helps to make the structuring and management of lease components more efficient."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes
language: en
last_updated: 2026-09-02
---
# Creating and Configuring Asset Classes
## Overview
An **asset class** is a group of assets that have similar characteristics and are subject to the same accounting treatment. This classification helps to make the **structuring and management of lease components** more efficient. Different asset classes can have different effects on financial indicators. For instance, buildings may have a longer depreciation period than vehicles.
To provide a **basis** for accounting for leases, **asset classes** are created and edited in the workspace of the same name.
> **Note:** Until at least one asset class exists, a warning icon appears next to **Asset classes** in the **Settings** menu. The icon disappears once you create your first asset class.
>
> the a warning appears next to asset classes until at least one asset class exists. icon
> Warning icons in the 'Settings' menu
## The ‘Asset Classes’ Workspace
The **Asset classes** workspace displays all the asset classes that have already been created:
The 'Asset classes' workspace
## Creating an Asset Class
Click **Add new asset class** to create a new asset class.
The **New asset class** dialog is displayed:
The 'New asset class' dialog
## Configuring an Asset Class
When configuring an **asset class**, the following options are available:
> **Note:** Fields marked with a \* are mandatory fields.
| Option | Description |
|---|---|
| Name | Asset class name |
| Asset class type | Type that is going to be assigned to the asset class
**Note:** • The most common asset class types preconfigured in Lease Accounting are available for selection. In addition, the types **Additional asset class type 1** to **Additional asset class type 20** are available. Use these types to classify asset classes for which no preconfigured type exists. • The asset class type is a label used for classification, grouping, and reporting. Depreciation and all other measurement settings are configured on the asset class itself. • You can select the required type in the drop-down list or search for it using the Search box. |
| Minimum depreciation period | Minimum depreciation period that will apply to the asset class, in months |
| Maximum depreciation period | Maximum depreciation period that will apply to the asset class, in months |
| Additional asset details | Specifies whether components of this asset class collect asset-specific details in the component form: • **None** — components of this asset class collect no asset-specific details. • **Car fleet** — the **Car fleet** tab is displayed in the component form to record vehicle details. • **Real estate** — the **Real estate** tab is displayed in the component form to record property details.
For additional information, see [Creating and Configuring Contract Components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md). |
---
---
title: "Creating and Configuring Contract Components"
description: "‘Contract components’ are individual elements of a leasing contract. Each component enables the precise recording and management of different lease terms, conditions and properties of individual underlying assets within the same leasing contract."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components
language: en
last_updated: 2026-10-06
---
# Creating and Configuring Contract Components
## Overview
**Contract components** are individual **elements** of a lease contract. Each component enables the precise recording and management of different lease terms, conditions and properties of **individual underlying assets** within the same lease contract.
This **modular approach** to recording components offers a high degree of **flexibility** in accounting for your leases and takes into account the complexity of modern lease contracts.
You can **create** and **configure** contract components in the **Contract components** workspace. You can also **modify** contract components that have already been calculated.
> **Warning:** Lucanet Lease Accounting can **only** be used for accounting of **regular leases** in accordance with **[IFRS 16.3-4](https://support.lucanet.com/en/documentation/glossary.md#ifrs-16)**. **Short-term** and **low-value** leases are therefore **not** included in the calculation.
>
> As such, we recommend only using this software to record leases that are categorized as **regular** per IFRS 16.3-4.
## 'Contract Components' Workspace
In the **Contract components** workspace, you can display all components that have already been created for a contract.
- Select the corresponding **contract number**. To restrict the selection of contract numbers to one **lessor**, you can first select the corresponding **lessor**.
- Use the **Active** and **Archived** buttons if you only want to see active or archived components:
The 'Contract components' workspace
## Creating Contract Components
To create a new component for a contract, select the **contract number** in the upper area and click **Add component**.
In the displayed **New contract component** dialog, configure the options as described in the next chapter.
## Configuring Contract Components
When configuring a contract component, the following options are available:
> **Note:** - Fields marked with a \* are mandatory fields. The number of mandatory fields on each tab and how many have already been filled in is displayed next to the name of the tab:
> the mandatory fields icon
>
> - Fields that have been grayed out cannot be edited. They are filled in automatically based on the information in Lease Accounting.
### Lease Identification
'Leasing identification' tab
| Option | Description |
|---------|---------|
| Is there an identified asset? | Specify whether the contract component is an asset that is identified in accordance with IFRS 16.3-4. |
| Does the lessee have the right to obtain substantially all of the economic benefits from use of the identified asset throughout the period of use? | Specify whether the lessee derives substantially all of the economic benefit of the asset during its useful life.
**Note:** Economic benefits can be fixed, consumption-independent payments, such as fixed basic rents. |
| Who has the right to direct how and for what purpose the asset is used throughout the period of use? | Specify whether the **lessee (CUSTOMER)**, the **lessor (SUPPLIER)**, or **neither** party **(NEITHER)** makes the decisions about the nature and purpose of the use of the asset.
If you select **NEITHER**, use the additional questions to specify whether: • The lessee has the right to operate the asset throughout the period of use, without the lessor having the right to change those operating instructions. • The lessee designed the asset in a way that predetermines how and for what purpose the asset will be used throughout the period of use?
**Note:** In some cases the relevant decisions about how and for what purpose the asset is used are predetermined. For example, the lessee has the right to direct how and for what purpose the asset is used if he • is able to transform a building originally used for administrative purposes into a production building. • is able to use a vehicle originally used in Germany autonomously in a foreign country. • decides about the produced parts. |
| Lease identification | Based on the information you enter on this tab, this is where the system automatically displays whether the component is identified as a leasing component.
**Note:** If the component is identified here as a **non-lease component**, you can cancel the recording of the components, as the component does not then have to be accounted for in accordance with [IFRS 16](https://support.lucanet.com/en/documentation/glossary.md#ifrs-16). |
### General Information
‘General Information’ Tab
| Option | Description |
|---------|---------|
| External contract number or ID | Displays the number of the contract to which you have assigned the component. |
| Component number or ID | Identification number for the component |
| Cost center | Cost center for the component |
| Profit center | Optional profit center for the component. The drop-down list offers the profit centers that are available for all reporting entities as well as the profit centers of the component's reporting entity, filtered by the selected cost center. |
| Accounting area | Optional accounting area for the component. The drop-down list offers the accounting areas that are available for all reporting entities as well as the accounting areas of the component's reporting entity. |
| Business unit | Optional business unit for the component. The drop-down list offers the business units that are available for all reporting entities as well as the business units of the component's reporting entity. |
| Start date | Start date of utilization of the related component |
| End date | End date of utilization of the related component without considering extension and/or termination options |
| Component currency | Currency in which the component should be calculated. By default, the functional currency of the selected reporting entity (lessee) is displayed. |
| Comments | Optional comments on the details configured on this tab |
### Underlying Asset
'Underlying asset' tab
| Option | Description |
|---------|---------|
| Asset class | Asset class of the component |
| Does the lease agreement contain a purchase option? | Specify whether a purchase option has been agreed for the component.
If **Yes**, configure the details of the purchase option(s) by clicking **Add row** in the table that appears and specifying the following: • **Date of purchase option** • **Value of purchase option** • Whether the exercise of the purchase option is **reasonably certain** |
| Useful life of the underlying asset (in months) | Period during which an asset is available for use by the company |
| Manual entry of interest rates | Enable this option to manually enter a new interest rate in the field **Incremental borrowing rate in percent**, which will override the value defined during the [interest rate creation](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-interest-rates.md), if any interest rates were configured.
**Note:** You can still enable or disable manual entry of interest rates during the [modification of contract components](#contractmodification), specifically for the following **modification parameters**: • Lease term \| Extension option/Termination option (if **reasonably certain** option is activated) • Payments \| Payments • Asset information \| Purchase option (if **reasonably certain** option is activated) • General information \| Base lease term \| Contract term reduction/extension |
| Incremental borrowing rate in percent (e.g. 5.00) | • When **Manual entry of interest rates** is deactivated: This field is automatically populated with the pre-configured interest rate specific to the selected asset class, if an interest rate was set. If no interest rate was set, the field will remain empty or display 0. • When **Manual entry of interest rates** is activated: This field is left empty, and you need to manually enter an interest rate. The manually entered rate will override the interest rate derived from the [interest rate configuration](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-interest-rates.md).
**Note:** The lease liability is measured on initial recognition at the present value of future lease payments. For this, the future lease payments are discounted with the incremental borrowing rate of the reporting entity. The incremental borrowing rate is the interest rate that the reporting entity would have agreed to inception date of the lease, if it had to borrow funds for the same period for the purchase of the leased property. |
| Does the contract contain any asset retirement obligations? | Specify whether the contract contains any asset retirement obligations.
If yes, enter the present value of the amount of the obligation (in component currency). |
| Comments | Optional comments on the details configured on this tab |
### Lease Term
'Lease term' tab
| Option | Description |
|---------|---------|
| Does the contract contain an extension option? | Specify whether an extension option has been agreed for the component.
If **Yes**, configure the details of the extension option(s) by clicking **Add row** in the table that appears and specifying the following: • **Start and end date** of the extension option(s) • Whether the exercise of the extension option is **reasonably certain** • The following **payment details** for each individual extension option that was created by **adding a row**
**Note:** A detailed description of the individual fields that are configured in the **Create payment** dialog can be found in the description of the [Payments](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components/.md#payment) tab. |
| Does the contract contain a termination option? | Specify whether a termination option has been agreed for the component.
If **Yes**, configure the details of the termination option(s) by clicking **Add row** in the table that appears and specifying the following: • **Termination date** • **Is it reasonably certain to exercise the option to terminate the lease?** • **Are there any additional payments of penalties for terminating the lease agreed in the contract?** • **Amount of payments of penalties for terminating the lease (in component currency)** |
| Comments | Optional comments on the details configured on this tab |
### Payments
'Payments' tab
Add the individual payments for the lease component by clicking **Add row** and specifying the following:
**For single payments**
| Option | Description |
|---------|---------|
| Regular payment | Specifies whether the payment is a regular payment or a single payment.
For a single payment, choose **No**. |
| Description | Description for the payment.
**Examples for real estate**: basic rent; prepayment operating expenses; rent for 1st floor, etc. |
| Payment amount in component currency | Amount entered in the contract for the payment (in component currency) |
| Payment date of the single payment | Time agreed for the single payment |
**For regular payments**
| Option | Description |
|---------|---------|
| Regular payment | Specifies whether the payment is a regular payment or a single payment.
For a regular payment, choose **Yes**. |
| Description | Description for the payment.
**Examples for real estate**: basic rent; prepayment operating expenses; rent for 1st floor, etc. |
| Payment amount in component currency | Amount entered in the contract for the payment (in component currency) |
| Type of regular payment | Specifies whether the payment is a **fixed payment** or a **variable payment**. |
| Start and end dates of payments | First and last dates of the payments
**Note:** The start and end dates of the payments define the interval for a series of payments in Lease Accounting in order to represent contract-specific payment terms. The start and end dates of payments may differ from the start and end of the contract. |
| Payment pattern | Choose whether payment is made **yearly**, **half-yearly**, **quarterly**, or **monthly**. |
| Are the payments made in advance? | Specifies whether the payments are in advance, i.e. that the payments must be made at the beginning of the period. |
| Start month of the first complete period of regular payments | Month in which the first full regular payment is made (in format MM-DD)
**Examples:** • Calendar month payments in arrears • Start of component term: 13 March 2022
I.e. the first full payment for a whole calendar month takes place in April. The **start date of the first full period of regular payments is therefore** (MM-TT): **04-01**
**Note:** If terms of payment cause regular payments to be scheduled at dates outside the defined component term, please set up those specific payments as single payments using the respective part of the payment dialog. The Lease Accounting validation will not consider regular payments scheduled for dates outside the defined component term. |
### Residual Value Guarantees
'Residual value guarantees' tab
| Option | Description |
|---------|---------|
| Does the contract contain a residual value guarantee? | Specify whether a residual value guarantee has been agreed for the component.
If **Yes**, configure the details of the residual value guarantee by entering the following in the displayed fields: • **Amount of guaranteed residual value** • **Amount expected to be payable under the residual value guarantee** |
| Comments | Optional comments on the details configured on this tab |
### Additional Payments
'Additional payments' tab
| Option | Description |
|---------|---------|
| Have initial direct costs been incurred? | Specify whether initial direct costs have been incurred.
If **Yes**, also specify the **Total amount of initial direct costs:** (in component currency). |
| Are lease incentives agreed in the contract? | Indicate whether incentive payments by the lessor have been agreed in the contract.
If yes, specify the following: • The **Total amount of lease incentives received (in component currency)** • The **Amount of lease incentives to be received \| lease incentive receivable** • The **Payment date of lease incentives to be received** |
| Comments | Optional comments on the details configured on this tab |
### Car Fleet
The **Car fleet** tab is displayed if the [asset class](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes.md) selected in the **Underlying asset** tab collects car fleet details — that is, if **Additional asset details** is set to **Car fleet** for the asset class. Use this tab to record vehicle details for the component.
'Car fleet' tab
On this tab, you can record details such as the serial number, license plate, mileage, brand and model, the vehicle user, and comments. All fields on this tab are optional. Lucanet Lease Accounting saves the details with the component and includes them when you [copy the component](https://support.lucanet.com/en/documentation/lease-accounting/general-functions-lease-accounting.md).
### Real Estate
The **Real estate** tab is displayed if the asset class selected in the **Underlying asset** tab collects real estate details — that is, if **Additional asset details** is set to **Real estate** for the asset class. Use this tab to record property details for the component.
'Real estate' tab
On this tab, you can record details such as the object number, the address, cadastral details, area sizes, and comments. In the **Reference value** field, you specify which of the recorded values serves as the reference value for the property, for example the total area or the number of workplaces. All fields on this tab are optional. Lucanet Lease Accounting saves the details with the component and includes them when you copy the component.
### Migration
'Migration' tab
| Option | Description |
|---------|---------|
| Is the component a migration component? | Specify whether this is a component that has already been accounted for in accordance with IFRS 16 and is now being migrated to Lucanet Lease Accounting.
If **Yes**, also specify the following details that will change when migrating to Lucanet Lease Accounting: • **Deviating interest rate in percent** • **Deviating start value of the historical cost (in component currency)** • **Deviating start value of the cumulated depreciation (in component currency)** • **Net liability before application of Lease Accounting (in component currency)** • **Migration date** |
| Comments | Optional comments on the details configured on this tab |
### Transition
'Transition' tab
| Option | Description |
|---------|---------|
| Is the component a transition component? | Specify whether this is a transition component, i.e. a component for which **IFRS 16 is being applied for the first time**.
If **Yes**, also differentiate between: • Whether it is an **operating lease** or a **finance lease** • Whether it is a **provision for onerous leases** or an **impairment**
Then configure the fields that are displayed based on the selection made.
**Example configuration — finance lease:** • **Deviating interest rate in percent (e.g. 5.00)** • **Deviating start value of the historical cost (in component currency)** • **Deviating start value of the cumulated depreciation (in component currency)** • **Net liability according to IAS 17 (in component currency)**
**Example configuration — operating lease with provision for onerous leases:** • **Is the right-of-use asset measured at its carrying amount as if the Standard had been applied since the commencement date (IFRS 16 C8(b(i)))?** • **Prepaid payments (in component currency)** • **Accrued payments (in component currency)** • **Provision for onerous leases (in component currency)** |
| Comments | Optional comments on the details configured on this tab |
## Modifying Contract Components
Components that have not yet been calculated can be edited by clicking the pencil icon and editing the tabs as described above under _Configuring Contract Components_.
If components have [already been calculated](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md), the fields of the tabs cannot be edited. Instead, the components must be modified as described below.
To modify a contract component that has already been calculated:
1. In the overview table, click the brush icon in the row of the desired component. The detail view of the components is displayed as follows, for example:
Modify component
2. Open the [modification parameters](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components/.md#modification-parameters) and select the change you want to implement by navigating through the displayed drop-down menu. For example, to add an extension option, select **Lease Term | Extension Option | Add**:
Add extension option
3. Configure the data in the displayed configuration dialog. (A description of the required information can be found in the previous _Configuring Contract Component_ section.)
4. In each configuration dialog, specify the **effective date** from which the modification is to be included in the calculation.
5. Click **Save**.
The last modification made is displayed in the overview table in the **Status** column:
Modified component
6. If applicable, click the modification in the **Status** column to display the **modification history** of the component:
Modification history of a component
> **Warning:** For a modified component to be taken into account in **postings**, you must **calculate and save** the components as described under [Measuring Data](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md).
### Modification Parameters
Components that have been calculated can be modified through modification parameters. The following modification parameters are available:
#### Underlying asset
- Purchase option
- Change to the useful life of the asset
- Proportional scope reduction
- Impairment
- Add/Edit Asset retirement obligation
- Change asset class
- Car fleet modification
- Real estate modification
#### Lease term
- Extension option
- Termination option
#### Payments
- Payments
#### General information
- Base lease term
- Modify master data dimension:
- Change cost center
- Change profit center
- Change accounting area
- Change business unit
In each dialog, the current value is displayed. Select the new value and specify the **Effective date (first month)**. The change creates a new component event: postings from the effective date use the new value, and historical postings remain unchanged. Master data dimension changes are statistical only — they do not affect any calculation, such as the interest rate, the right-of-use asset, or the lease liability.
#### Residual value guarantee
- Reassess or add a residual value guarantee
- Reassess or add an expected payment
---
---
title: "Creating and Configuring Contracts"
description: "A lease contract is a formal agreement between the lessor and the lessee that transfers the right to control the use of an identified asset for a defined period of time in exchange for compensation."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contracts
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Contracts
## Overview
A lease contract is a formal **agreement** between the **lessor** and the **lessee** that transfers the right to control the use of an identified asset for a defined period of time in exchange for compensation.
The contract defines the **conditions** under which the lease is performed, including details of the parties involved and the term of the lease.
**Contracts** are created and configured in the workspace of the same name.
As an alternative to **manual** creation, contracts can also be added by **importing** a CSV file (see [Automatically importing data](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/automatic-data-import.md)).
> **Warning:** Lucanet Lease Accounting can **only** be used for accounting of **regular leases** in accordance with **IFRS 16.3-4**. **Short-term** and **low-value** leases are **not** included in the calculation.
>
> As such, we recommend only using this software to record leases that are categorized as **regular** per IFRS 16.3-4.
## The ‘Contracts’ Workspace
The **Contracts** workspace displays all the contracts that have already been created.
Use the **Active** and **Archived** buttons if you only want to see active or archived contracts:
The 'Contracts' workspace
## Creating a Contract
Click **Add a new contract** to create a new contract.
In the displayed dialog, configure the options for the **New Contract** as described in the next chapter.
## Configuring a Contract
When configuring a contract, the following options are available:
> **Note:** - Fields marked with a \* are mandatory fields. The number of mandatory fields in each tab and how many have already been filled in is shown next to the name of the tab:
> the mandatory fields icon
>
> - Fields that have been grayed out cannot be edited. They are filled in automatically based on the information in Lease Accounting.
### ‘General Information’ Tab
The 'General Information' tab
| Option | Description |
|---------|---------|
| Lessor | Lessor of the contract
**Note:** All [lessors](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-lessor.md) that have been created or imported in Lease Accounting are available for selection. |
| Contract number | The contract number provided by the lessor.
**Note:** If you are the lessee and do not know the lessor’s contract number, enter a contract number of your own ( _company number_\- _individual contract number_; e.g.: 4144 - 9933754). |
| Reporting entity | Reporting entity acting as the lessee for the contract in question |
| Country or region | Shows the lessee’s country or region |
| Contract owner | Contact person or line manager for queries relating to the contract in question |
| Contract file | Allows uploading, viewing, and removing contract files (primarily PDF format) when creating or editing a contract.
In view mode, files can only be downloaded.
After a contract file has been attached to a contract, an attachment icon appears next to the **Contract ID** in the **Contract** overview table. |
### ‘Contract-specific Information’ Tab
The 'Contract specific information' tab
| Option | Description |
|---------|---------|
| Start date of the contract | Start date of the lease contract
**Note:** The start dates of the lease components may differ from the start date of the lease contract itself. |
| End date of the contract | End date of the lease contract, not including and extension and/or termination options.
**Note:** If the contract does not have a fixed term, enter the earliest date on which both parties can terminate the contract without incurring significant termination fees (if in doubt, use the statutory termination date, where applicable). |
### ‘Additional Information’ Tab
The 'Additional Information' tab
Use the **Additional information** tab to add **comments** on the contract in a plain text box.
---
---
title: "Creating and Configuring Interest Rates"
description: "Interest rates are used to calculate the current value of lease payments. They are key to determining lease liability and the right-of-use asset for the balance sheet."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-interest-rates
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Interest Rates
## Overview
**Interest rates** are used to calculate the **current value of lease payments**. They are key to determining lease liability and the right-of-use asset for the balance sheet.
To provide a **basis** for accounting leases, **interest rates** can be managed in the workspace of the same name. New interest rates can either be created **manually** or added by **importing CSV files**.
Interest rates can also be entered manually during the [creation or modification of a contract component](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md), which will override pre-configured interest rates, if any were set.
To allow calculation of country-specific interest rates and rates for different [asset classes](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes.md), each interest rate is always created for a specific combination of **asset class**, **country or region** and **currency**. In addition to this, the interest for each interest rate is split into maturity brackets.
> **Warning:** To ensure that an interest rate can be used for a specific asset class, start by creating the asset class in the [Asset Classes](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes.md) workspace.
## The ‘Interest Rates’ Workspace
The **Interest rates** workspace displays all the Interest rates that have already been created:
The 'Interest rates' workspace
## Creating an Interest Rate
Click **Add a new interest rate** to create a new interest rate.
The **New interest rate** dialog is displayed:
The 'New interest rate' dialog
> **Note:** It is also possible to manually enter an interest rate during the [creation or modification of a contract component](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md). This manual entry will override any interest rate that might have been pre-configured.
## Configuring Interest Rates
When configuring an **interest rate**, the following options are available:
> **Note:** Fields marked with a \* are mandatory fields.
| Option | Description |
|---------|---------|
| Asset class | Asset class to which the interest rate applies
**Note:** Only those asset classes that have already been created in the [Asset classes](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-asset-classes.md) workspace will be available to choose from. |
| Currency | Currency to which the interest rate applies |
| Country or region | Country or region to which the interest rate applies |
| Valid from | Date from which the interest rate will apply |
| Yearly interest | Assignment of interest rates to maturity brackets. To do this, enter the applicable interest rate for each lease term.
The lease terms range from **Up to one year** to **Undefined year (terms > 20 years)**. |
## Importing Interest Rates
As an alternative to manual creation, interest rates can also be imported in the form of CSV files:
Area for importing interest rates
Select the following options in the area above the overview table:
- Click **Browse** and upload the required CSV file.
- Use the **Drag & Drop** method to add the required CSV file.
Once this is done, click **Start import**.
> **Tip:** **CSV Import Templates**
>
> To make automatic imports easier for you, we have provided a template for the CSV file. The structure of this template matches that required for the import.
>
> The CSV file includes instructions on how to add the data.
>
> Use the following link to download the template:
>
> - [Template for Interest Rate Imports](https://lnag.sharepoint.com/:x:/s/hubkm/ETQKqnSQmetAkErnFcX7GU8BdSO-IRUfJkenHlWsy9oRfQ?e=CvasnK)
---
---
title: "Creating and Configuring Lessors"
description: "A lessor is the party the owns the underlying asset and transfers it to another party (the lessee) for a contractually agreed lease term, under certain conditions. Lessors are the contracting parties that provide the basis for lease contracts in Lease Accounting."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-lessor
language: en
last_updated: 2026-05-01
---
# Creating and Configuring Lessors
## Overview
A **lessor** is the party the owns the underlying asset and transfers it to another party (the lessee) for a contractually agreed lease term, under certain conditions. Lessors are the **contracting parties** that provide the basis for lease contracts in Lease Accounting.
**Lessors** are created and configured in the workspace of the same name.
As an alternative to manual creation, lessors can also be added by importing a CSV file (see [Importing Data Automatically](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/automatic-data-import.md)).
## The ‘Lessors’ Workspace
The **Lessors** workspace displays all the lessors that have already been created:
The 'Lessors' workspace
## Creating a Lessor
Click **Add a new lessor** to create a new lessor.
In the displayed dialog, configure the options for the **New lessor** as described in the next chapter.
## Configuring a Lessor
When configuring a lessor, the following options are available:
> **Note:** Fields marked with a \* are mandatory fields. The number of mandatory fields in each tab and how many have already been filled in is shown next to the name of the tab:
>
> the mandatory fields icon
### The ‘General Information’ Tab
The 'General information' tab
| Option | Description |
|---------|---------|
| Name of the lessor | Name of the lessor |
| Lessor ID | Creditor number for the lessor |
| Related reporting entity | The reporting entity to which the lessor can be assigned as the sole contractual partner (lessee)
**Note:** • All reporting entities that have been imported in Lease Accounting are available for selection. • If the lessor is a contractual partner to several different lessees, this field must be left empty. |
| Country or region | Shows the lessor’s country or region
**Note:** You can select the required entry in the drop-down list or search for it using the Search box. |
### The ‘Contact Person’ Tab
The 'Contact person' tab
| Option | Description |
|---------|---------|
| First name | First name of the lessor’s contact person |
| Last name | Surname of the lessor’s contact person |
| E-mail address | The contact person's e-mail address |
| Job position | The contact person’s position |
### The ‘Comments’ Tab
The 'Comments' tab
Use the **Additional information** tab to add **comments** on the lessor in a plain text box.
---
---
title: "Creating Business Units"
description: "Create business units as a master data dimension and assign them to contract components to analyze your lease data by business unit."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-business-units
language: en
last_updated: 2026-10-06
---
# Creating Business Units in Lucanet Lease Accounting
## Overview of Business Units in Lucanet Lease Accounting
Business units are a **master data dimension** in Lucanet Lease Accounting, in addition to cost centers, profit centers, and accounting areas. You can assign a business unit to a [contract component](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md) on the **General information** tab.
A business unit is either related to a specific reporting entity or available for all reporting entities.
> **Note:** - The **Business units** workspace requires the **Full access administrator** or **Settings administrator** role, see [User Roles](https://support.lucanet.com/en/documentation/lease-accounting/user-roles-la.md).
> - Business units are also available if you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning. Consolidation & Financial Planning has no business unit dimension, so the business units that you create in Lease Accounting do not appear in Consolidation & Financial Planning.
## The 'Business units' Workspace in Lucanet Lease Accounting
To display the existing business units in Lucanet Lease Accounting, navigate to **Settings | Business units**. The workspace lists all business units in a table with the columns **Name**, **Reporting entity**, **Creation date**, **Last modified by**, and **Date of last modification**. You can sort and filter the columns.
The 'Business units' workspace
## Creating Business Units in Lucanet Lease Accounting
To create a business unit in Lucanet Lease Accounting:
1. Navigate to **Settings | Business units**.
2. Click **Add business unit**. The **Add Business Unit** dialog is displayed:
The 'Add Business Unit' dialog
3. Specify whether the business unit is related to a reporting entity:
- If **Is the business unit related to a reporting entity?** is set to **Yes**, select the **Reporting entity** in the drop-down list. By default, Lucanet Lease Accounting selects the reporting entity that you are signed into.
- If you set the toggle to **No**, the business unit is available for all reporting entities.
4. Enter the **Name of the business unit**. The name must be unique within the selected reporting entity. A business unit for all reporting entities needs a name that no other business unit for all reporting entities uses.
5. Click **Save**. The business unit is displayed in the **Business units** table, and you can assign the business unit to contract components of the corresponding reporting entity.
## Using Business Units in Lucanet Lease Accounting
After you have created business units, you can use them in the following places in Lucanet Lease Accounting:
- **Contract components:** In the **General information** tab of a component, the **Business unit** drop-down list offers the business units for all reporting entities as well as the business units of the component's reporting entity, see [Creating and Configuring Contract Components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md#general-information).
- **Modifications:** For a calculated component, you can change the business unit with the modification **General information | Modify master data dimension | Change business unit**. The change applies from the effective date and does not affect any calculation.
- **Reports:** You can aggregate the **Account balance** report by business unit, see [Exporting Reports and Postings](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md#report-types).
---
---
title: "Creating or Importing Cost Centers"
description: "Cost centers that have been created for reporting entities in Consolidation & Financial Planning can be imported directly into Lease Accounting. This feature ensures that your financial and lease data are interconnected, allowing for more comprehensive reporting and analysis."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/import-cost-center
language: en
last_updated: 2026-05-01
---
# Creating or Importing Cost Centers
## Overview
**Cost centers** that have been created for reporting entities in **Consolidation & Financial Planning** can be imported directly into Lease Accounting. This feature ensures that your financial and lease data are interconnected, allowing for more comprehensive reporting and analysis.
> **Warning:** Users with a standalone license for **Lucanet Lease Accounting** can create cost centers directly within Lease Accounting, rather than importing them. This process is described in the last section of this article.
## The 'Cost Centers' Workspace
The **Cost Centers** workspace shows all the cost centers that have already been imported from Lucanet Consolidation & Financial Planning:
The 'Cost Centers' Workspace
## Importing Cost Centers
To import cost centers from Lucanet Consolidation & Financial Planning:
1. Click **Import from CFP**. The **Import from CFP** dialog is displayed:
'Import from CFP' dialog
2. Click **Import from CFP** to confirm the message and carry out the import.
Once the cost centers have been imported from Consolidation & Financial Planning, the cost centers will be displayed in the overview table.
> **Warning:** To ensure that cost centers created or updated in Lucanet Consolidation & Financial Planning **at a later date** can be used in Lease Accounting, carry out a **new import** as described above.
>
> When another import run is executed, only those cost centers that have been created or updated since the last import will be added.
## Creating Cost Centers
Users with a standalone license for **Lucanet Lease Accounting** can create cost centers directly within Lease Accounting, rather than importing them.
To create a cost center in Lease Accounting:
1. Navigate to the **Cost Centers** workspace under **Settings** and click **\+ Add cost center.**
Adding a cost center
2. Specify whether the cost center is related to a reporting entity.
If yes, a **Reporting entity** field will appear. Select a reporting entity from the drop-down list.
Cost center related to a reporting entity
3. Enter the **name** of the cost center.
4. Click **Save,** then **Create** in the **Create Record** dialog to add the cost center.
---
---
title: "Creating Profit Centers"
description: "Create profit centers as a master data dimension and assign them to contract components to analyze your lease data by profit center."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-profit-centers
language: en
last_updated: 2026-09-02
---
# Creating Profit Centers
## Overview
Profit centers are a **master data dimension** in Lucanet Lease Accounting. You can assign a profit center to a [contract component](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md) in the **General information** tab and aggregate the [Account balance report](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) by profit center.
A profit center applies either to a specific reporting entity or to all reporting entities. In addition, you can relate a profit center to a [cost center](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/import-cost-center.md).
> **Note:** - The **Profit centers** workspace requires the **Full access administrator** or **Settings administrator** role (see [User Roles](https://support.lucanet.com/en/documentation/lease-accounting/user-roles-la.md)).
> - Profit centers are also available if you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning. Because this dimension does not exist there, profit centers are not transferred to Consolidation & Financial Planning.
## The 'Profit centers' Workspace
The **Profit centers** workspace lists all profit centers in a table and is displayed as follows, for example:
The 'Profit centers' workspace
## Creating Profit Centers
To create a profit center:
1. Navigate to **Settings | Profit centers**.
2. Click **Add profit center**. The **Add Profit Center** dialog is displayed:
The 'Add Profit Center' form
3. Specify whether the profit center is related to a reporting entity:
- If **Is the profit center related to a reporting entity?** is set to **Yes**, select the **Reporting entity** in the drop-down list. By default, the reporting entity you are signed into is selected.
- If you set the toggle to **No**, the profit center is available for all reporting entities.
4. If applicable, select a **Related cost center**. The drop-down list offers the cost centers that are available for all reporting entities as well as the cost centers of the selected reporting entity.
5. Enter the **Name of the profit center**.
6. Click **Save**. The profit center is displayed in the **Profit centers** table and can be assigned to contract components of the corresponding reporting entity.
---
---
title: "Exporting Reports and Postings"
description: "In the ‘Export’ workspace in Lucanet Lease Accounting, you can export existing postings and generate reports for the data that has been recorded in Lease Accounting. This is useful for purposes such as sharing data with other parties, evaluation and comparing data."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/export-data
language: en
last_updated: 2026-10-06
---
# Exporting Reports and Postings
## Overview
In the **Export** workspace, you can:
- Generate **reports** for the data recorded in Lease Accounting. The following reports are available:
- **Balance values for reference date**
- **Contract overview**
- **Disclosures**
- **Asset register**
- **Account balance**
- Export postings that have already been [saved](https://support.lucanet.com/en/documentation/lease-accounting/create-postings.md) so they can be imported into other systems.
All the reports and posting exports can be downloaded separately in the form of an **Excel file**.
> **Note:** If you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning, you can [import](https://support.lucanet.com/en/documentation/lease-accounting/importing-postings-cfp.md) the postings saved in Lease Accounting directly into Consolidation & Financial Planning using a script. In addition, you can export the postings in the **Export postings** workspace. The export and the import are independent of each other, i.e., exporting the postings does not import the postings into Consolidation & Financial Planning. To transfer the postings, execute the import script in Consolidation & Financial Planning.
## Creating Reports
Reports have several uses; for example, they can provide an overview of the contracts in Lease Accounting or be used to compare the figures calculated by the software solution against the data on the balance sheet.
To generate a **report**, proceed as follows:
1. Navigate to **Export | Create reports:**
Create a report
2. In the **Report type** field, select the report type you want to generate from the drop-down list.
> **Note:** The available report types and report-specific additional information are described in the following section.
3. In the **Reporting entities** drop-down list, select the reporting entity or entities for which you want to create the report.
> **Note:** The selection of multiple reporting entities is available for all report types. If you select more than one reporting entity, the data is compiled into one file.
4. (Optional) Activate the **Select report currency** option if you want to generate the report in a specific currency, then select the desired currency from the **Select currency** drop-down list. By default, the currency of the contract component is applied.
> **Note:** **Notes:**
>
> - The **Select report currency** option is available for all report types except **Contract overview**.
> - If the **Select report currency** option is not activated, the contract currencies will be applied (i.e., each contract's values appear in its original currency).
5. Click **Generate report**. The **Report Generation** confirmation dialog is displayed:
The 'Report Generation' confirmation dialog
6. Verify your selection, then click **Generate report** to start generating the report.
### Report Types
The following **report types** are available in Lease Accounting:
| Report type | Description | Required information |
|---------|---------|---------|
| **Balance values for reference date** | Generates subsequent overviews: • Overview of the Balance values for reference date (end of last month) • Overview of the Component events for the reference date (first of a month) | • Reporting entities • The start of reporting period • Reference date • Report currency |
| **Contract overview** | Generates an overview of all the existing contracts | • Reference date |
| **Disclosures** | Generates a detailed breakdown of lease liabilities and assets for the selected reporting entity | • Reporting entities • The start of the reporting period • The end of the reporting period • Report currency |
| **Asset register** | Generates an overview of all assets and asset-related information | • Reporting entities • The end of the reporting period • Report currency |
| **Account balance** | Generates an overview of the balances for each account, aggregated by: • Transaction type • Cost center • Profit center • Accounting area • Business unit and/or • Asset class
This report allows a reconciliation of the balance in the Lease Accounting database with the balance of the accounts in the balance sheet to make sure that both are in line and postings are complete. | • Reporting entities • Posting date from • Posting date to • Aggregate by transaction type/cost center/profit center/accounting area/business unit/asset class • Report currency |
> **Note:** **Notes on creating reports:**
>
> - The report will be created in **XLSX format**, and a download link will be added to the **Reports** section of **Created files**.
> - The **file name** of each report type is structured as follows:
>
> - **Contract overview**: Contract-Overview\_ _ID of the lessee (reporting entity)_\_ _creation date_\_ _creation time_.xlsx
> - **Balance values for reporting date**: Balance-values-for-reference-date\_ _ID of the lessee (reporting entity)_\_ _creation date_\_ _creation time_.xlsx
> - **Disclosures:** Disclosures---in-reporting-currency\_ _name of the lessee (reporting entity)\_creation date_\_ _creation time_.xlsx
> - **Asset register:** Asset-Register\_ _ID of the lessee (reporting entity)\_creation date_creation time_.xlsx
> - **Account balance:** Aggregated-posting-entries-YTD---account-level\_ _ID of the lessee (reporting entity)_\_ _creation date_\_ _creation time_.xlsx
## Exporting Postings
In Lucanet Lease Accounting, you can export the [existing](https://support.lucanet.com/en/documentation/lease-accounting/create-postings.md) **postings** for one, several, or all reporting entities in a single export. The export is available with a standalone license for Lucanet Lease Accounting as well as when you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning.
To export postings, proceed as follows:
1. Open the **Export postings** workspace:
The 'Export postings' workspace
2. In the **Reporting entities** drop-down list, select the reporting entity or entities for which you want to export postings. By default, the reporting entity you are signed in to is preselected.
> **Note:** **Notes:**
>
> - To remove a reporting entity from the selection, click the **X** next to its name.
> - The **Reporting entities** field is mandatory. If you remove all reporting entities, you cannot start the export.
3. Select the **Export date**, i.e. the latest period (**YYYY-MM**) for which you want to export postings.
4. Under **File preferences**, select how you want to generate the posting files:
- **One file for all reporting entities**: You receive one file containing the postings for all selected reporting entities.
- **Individual files per each reporting entity**: You receive a separate file for each selected reporting entity.
If you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning, the **File preferences** options are not available. Lucanet Lease Accounting creates one file per selected reporting entity.
5. Click **Export postings**. The **Export Postings** dialog is displayed:
The 'Export Postings' confirmation dialog
6. Verify your selection, then click **Export postings** to start the export.
> **Note:** **Notes:**
>
> - The export is created in **XLSX format**, and a download link is added to the **Postings** section of the **Created files** workspace.
> - You cannot assign custom file names. The file names are generated automatically as follows:
>
> - **One file for all reporting entities**: _Export date_\_ _Export time_\_ **MultipleRE**\_BookingVoucher\_ _file ID assigned by the Server_.xlsx
> - **Individual files per each reporting entity**: each file name includes the ID of the corresponding reporting entity instead of **MultipleRE**, so that you can identify the postings of each entity.
> - If the export fails for one or more reporting entities, the export continues for the remaining reporting entities. You can still download the files that were exported successfully.
## Viewing and Downloading Created Files
The **Created files** workspace contains **download** links for all the **XLSX files** that have been created as described above. It makes no difference which reporting entity you have selected in the function bar, as this area shows the files created for every reporting entity.
To download a file, proceed as follows:
1. Open the **Created files** workspace:
The ‘Created files’ workspace
2. Select whether you want to view the XLSX files for the **Reports** or for the **Postings**.
> **Note:** For postings, the **Reporting entities** column shows which reporting entities are included in each file. To narrow down the list, select one or more entities in the **Reporting entities** drop-down list above the table.
3. In the row of the file you want to download, click the Download icon .
The file will be saved in your **Downloads folder**.
---
---
title: "General Configurations"
description: "The General Configurations workspace provides essential system-wide settings that establish the foundational parameters for your lease accounting processes."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/general-configurations-la
language: en
last_updated: 2026-05-01
---
# General Configurations
## Overview
The **General Configurations** workspace provides essential system-wide settings that establish the foundational parameters for your lease accounting processes.
> **Warning:** The general configurations must be completed before you can create your first contract components, as they define critical operational parameters that cannot be modified once lease data collection process begins.
> **Note:** Until you save the start of fiscal year and transition date, a warning icon appears next to **General configurations** in the **Settings** menu. The icon disappears once you save these settings.
>
> the a warning appears next to general configurations until it is set up. icon
> Warning icons in the 'Settings' menu
## The ‘General Configurations’ Workspace
The **General configurations** workspace allows you to enter the **start of fiscal year** and **transition date** for your lease accounting setup:
The 'General Configurations' Workspace
## Start of Fiscal Year
The **Start of fiscal year** option defines when your organization's fiscal year begins, which is essential for accurate lease accounting calculations and reporting periods.
## Transition Date
The **Transition date** specifies the month and year when your organization transitions to IFRS 16 lease accounting standards. This is typically the date you first apply the standard, marking the starting point for recognizing lease liabilities and right-of-use assets in your financial statements.
> **Warning:** The **Start of fiscal year** and **Transition date** fields become disabled and cannot be changed once the first component is created.
---
---
title: "General Functions in Lease Accounting"
description: "Lease Accounting provides a number of general functions for actions such as making tables easier to read and switching quickly between reporting entities for which data shall be collected as the lessee."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/general-functions-lease-accounting
language: en
last_updated: 2026-05-01
---
# General Functions in Lease Accounting
## Overview
Lease Accounting provides a number of **general functions** for actions such as making tables **easier to read** and switching quickly between reporting entities for which data shall be collected as the [lessee](https://support.lucanet.com/en/documentation/glossary.md#lessee).
This article describes the functions available.
## Functions in the Function Bar
The function bar is located at the top of the Lease Accounting screen. It provides the following general functions:
General functions in the function bar
| Function | Description |
|---------|---------|
| Select or change reporting entity | In all the workspaces that are used to collect, process, save or export reporting-entity-specific data, you can select or change the reporting entity using the **Reporting entity** drop-down list. |
| Show status and log of tasks | Use the **Active tasks:** button to view a list of the tasks currently running in Lease Accounting and their current execution status. For example, you will be able to see whether the [Categorization](https://support.lucanet.com/en/documentation/lease-accounting/categorization.md), [Calculation](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) and [Export](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) steps are complete. For each task, you can view a **log** that lists the **completed tasks** or any **errors** that may have occurred during execution. |
## Functions in Tables
The following options are available for tables:
#### Edit, view, delete, copy or archive entries
In a table, click the column with the config icon and select one of the following functions:
- the edit icon to edit an entry
- the eye icon to view the details for an entry
- the recycle bin icon to delete an entry
- the archive icon to archive an entry
- the brush icon to modify components
- the copy la icon to copy components (only available for non-calculated components)
> **Note:** Which of the functions listed above is available depends on which workspace you are currently in.
Edit, view, or delete entries
#### Configure columns
To optimize the view of a table, you can configure the columns accordingly. To do this, click the three dot icon in the table header and select one of the following options:
- **Pin column**
- **Autosize this column**
- **Autosize all columns**
- **Reset columns**
- **Reset filters**
Configure columns
#### Filter by entries
To view specific data or results, you can filter each column by specific entries. To do this, go to the three dot icon in the table and click the Filter icon . Once this is done, enter the name of the entry whose table data you wish to see in the Search box:
Filter by entries
#### Show and hide columns
To limit your view to specific columns in a table, go to the three dot icon in the table and click the column sorting icon. Once you have done this, choose one of the following options:
- Enter the name of the column you want to hide or show in the Search box
- Activate or deactivate the check box for the name of the column you want to hide or show.
Search for and show or hide entries
#### Sort data in columns
You can sort the data in table columns **alphabetically (from A-Z or Z-A)** or **in ascending or descending order**. To do this, move the cursor next to the column name in the table header and click the **arrow** icon that appears:
Sort data in columns
---
---
title: "Importing and Configuring Reporting Entities"
description: "A lessee is the party who receives the right to use an asset under the conditions of a lease contract. In Lucanet Lease Accounting, leases are recorded separately for each lessee."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-lessees
language: en
last_updated: 2026-05-01
---
# Importing and Configuring Reporting Entities
## Overview
A lessee is the party who receives the right to use an asset under the conditions of a lease contract. In **Lucanet Lease Accounting**, leases are recorded separately for each lessee.
In your role as lessee, you can select the companies you want to be configured as **reporting entities** in Consolidation & Financial Planning. To ensure that the reporting entities are available in Lease Accounting, the existing reporting entities in Lucanet Consolidation & Financial Planning first need to be **imported** into Lease Accounting.
Importing and the management of reporting entities takes place in the **Reporting entities** workspace.
> **Warning:** Users with a standalone license for **Lucanet Lease Accounting** can create reporting entities directly within Lease Accounting, rather than importing them. This process is described in the last section of this article.
> **Note:** Until at least one reporting entity exists, a warning icon appears next to **Reporting entities** in the **Settings** menu. The icon disappears once you import or create your first reporting entity.
>
> the a warning appears next to reporting entities until at least one reporting entity exists. icon
> Warning icons in the 'Settings' menu
## The ‘Reporting Entities’ Workspace
The **Reporting entities** workspace shows all the reporting entities that have already been imported from Consolidation & Financial Planning:
The 'Reporting entities' workspace
## Importing Reporting Entities
To import reporting entities from Consolidation & Financial Planning:
1. Click **Import reporting entities**.
The following notice will appear:
Reporting entity import notice
2. Click **Import** to confirm the message and carry out the import.
Once they have been imported from Consolidation & Financial Planning, the reporting entities will be displayed in the overview table.
3. Assign a **Country or region** and a **Functional currency** for Lease Accounting to each of the new reporting entities you have imported. You can edit these fields directly in the overview table, or click the pen icon in the row, go to the **General information** tab, and select the required entry from the drop-down list.
> **Note:** - Editing **Country or region** and **Functional currency** fields in the overview table supports bulk updates when many reporting entities are imported from Consolidation & Financial Planning and is especially useful for migrations (e.g. from the IFRS 16 app to the Lucanet CFO Solution Platform).
> - The functional currency can only be changed as long as no components have been calculated for the reporting entity.
4. If necessary, configure any additional details required to use the reporting entity in Lease Accounting (see [Editing Reporting Entities](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-lessees/.md#edit)).
5. Click **Update**.
> **Warning:** To ensure that reporting entities created **at a later date** in Consolidation & Financial Planning can be used in Lease Accounting, carry out a **new import** and add the necessary details as described above.
>
> When another import run is executed, only those reporting entities that have been created since the last import will be added. Any **details** that have already been edited in existing reporting entities will remain unchanged; they **will not be overwritten** when you perform a new import.
## Editing Reporting Entities
To edit the details of an imported reporting entity, go to the reporting entity in question in the overview table and click the pen icon symbol in the corresponding row.
When configuring a reporting entity, the following options are available:
> **Note:** - Fields marked with a \* are mandatory fields. The number of mandatory fields in each tab and how many have already been filled in is displayed next to the name of the tab:
> the mandatory fields icon
>
> - Fields that have been grayed out cannot be edited. They are filled in automatically based on the information in Lucanet.Financial Client.
### ‘General Information’ Tab
The 'General information' tab
| Option | Description |
|---------|---------|
| Technical ID | Shows the technical ID assigned to the company in Lease Accounting |
| Company | Shows the name of the reporting entity |
| OID | Shows the OID of the reporting entity in Lucanet.Financial Client |
| Functional currency | Designated functional currency for the company in Lease Accounting. You can select the currency from the drop-down menu or search for it using the search box.
**Note:** This field can be edited as long as no calculations have been performed for the reporting entity, regardless of whether active components exist. Once calculations are performed, the functional currency can no longer be changed. |
| Default currency of reporting entity | Shows the default currency configured for the company in Lucanet.Financial Client |
| Country or region | Country or region of the reporting entity. Select from the drop-down menu or use the search box to find the required country or region. |
### ‘Contact Person’ Tab
The 'Contact person' tab
| Option | Description |
|---------|---------|
| First name | First name of the company’s contact person |
| Last name | Surname of the company’s contact person |
| E-mail address | E-mail address for the company’s contact person |
| Job position | Position of the company’s contact person |
### ‘Additional Information’ Tab
The 'Additional information' tab
Use the **Additional information** tab to add **comments** on the reporting entity in a plain text box.
## Creating Reporting Entities
> **Tip:** Users with a standalone license for **Lucanet Lease Accounting** can create reporting entities directly within Lease Accounting, rather than importing them.
To create a reporting entity in Lease Accounting, navigate to the **Reporting Entities** workspace under **Settings** and click **\+ Add reporting entity.**
Fill out the following information:
### ‘General Information’ Tab
'General information' tab
| Option | Description |
|---------|---------|
| Company | The name of the reporting entity |
| Business code | Business code of the reporting entity |
| Functional currency | Designated functional currency for the company in Lease Accounting. You can select the currency from the drop-down menu or search for it using the search box.
**Note:** This field can be edited as long as no calculations have been performed for the reporting entity, regardless of whether active components exist. Once calculations are performed, the functional currency can no longer be changed. |
| Country or region | Country or region of the reporting entity. Select from the drop-down menu or use the search box to find the required country or region. |
### ‘Contact Person’ Tab
'Contact person' tab
| Option | Description |
|---------|---------|
| First name | First name of the company’s contact person |
| Last name | Last name of the company’s contact person |
| E-mail address | E-mail address for the company’s contact person |
| Job position | Job position of the company’s contact person |
### ‘Additional Information’ Tab
'Additional information' tab
Use the **Additional information** tab to add **comments** on the reporting entity in a plain text box.
---
---
title: "Importing Data Automatically"
description: "Automatic data imports allow you to import contracts, lessors and contract components automatically. This both simplifies the import process and saves you time."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/automatic-data-import
language: en
last_updated: 2026-05-01
---
# Importing Data Automatically
## Overview
Automatic data imports allow you to import contracts, lessors and contract components automatically. This both simplifies the import process and saves you time.
## The ‘Automatic Data Import’ Workspace
The **Automatic data import** workspace displays all the data import runs that have been executed to date, regardless of which reporting entity is selected:
The 'Automatic data import' workspace
## Importing Data Automatically
To import data, proceed as follows:
1. Open the **Automatic data import** workspace:
Importing data automatically
2. Select the **data to be imported**. The following data types can be imported:
- **Lessors**
- **Contracts**
- **Contract components**
3. Use **drag and drop** to attach the **Excel** or **CSV file** you want to import, or add it via the **Browse** function.
4. Click **Start import**.
> **Tip:** **Excel and CSV Import Templates**
>
> To make automatic imports easier for you, we provide templates for both **Excel** and **CSV** files. The structure of these templates matches that required for the import.
>
> The templates include instructions on how to add the data.
>
> Use the following links to download the templates:
>
> **Excel Templates:**
>
> - [Excel Template for Lessor Imports](https://lnag.sharepoint.com/:x:/s/hubkm/IQCnJUMt8TaHQJhdewJgo_TsAb8JuUOBXODBT6OOEM2_BNY?e=EI71U5)
> - [Excel Template for Contract Imports](https://lnag.sharepoint.com/:x:/s/hubkm/IQApJ5XhiV6pTaHr1SIvRo56ATOX5wTphtJfsPsjSIb94JM?e=gDmxMk)
> - [Excel Template for Contract Component Imports](https://lnag.sharepoint.com/:x:/s/hubkm/IQBHNlo_-CUNTZB_V4fS2xX8AYKjSpJCCaV9FrQRkCjkm18?e=vElVRu): this template uses conditional formatting to help you keep your entries within the allowed length. If you enter more than 250 characters in a cell, that cell turns red. Reduce the number of characters before you start the import.
>
> **CSV Templates:**
>
> - [CSV Template for Lessor Imports](https://lnag.sharepoint.com/:x:/s/hubkm/EW5Dq-ZgJa9ItacvIJe8LWgB-kEQVJs-vIoN65A3YiOHJw?e=eVzXt1)
> - [CSV Template for Contract Imports](https://lnag.sharepoint.com/:x:/s/hubkm/EfIU3mB0GSxCrZIUbohuG-IBgdNaejtTwKjbgTV6v6wirA?e=OuhTOB)
> - [CSV Template for Contract Component Imports](https://lnag.sharepoint.com/:x:/s/hubkm/IQAApa9b5yOHQb6ZNbHXtMILAVA8o5568v-C39ro_efqYhA?e=zXA91A)
## Data Import Details
The following details are displayed in the overview table for each data import:
Overview table in the 'Automatic Data Import' workspace
The table provides the following information:
| Column | Description |
|---------|---------|
| ID | Import ID |
| Date | Date of the import run |
| User name | Name of the user who executed the import |
| Reporting entity OID | OID of the reporting entity (lessee) for whom the import run was executed |
| File name | Name of the imported file |
| File size | Size of the imported file in KB |
| Import mode | The imported file type. This is always CSV. |
| Import type | The data type that was imported. The following options are displayed: • **StandardExternalParter** for importing **lessors** • **LucanetContract** for importing **contracts** • **LucanetComponent** for importing **contract components** |
| Status | Status of the import. The following options are displayed: • **Success** if the import was completed successfully • **Error** if an error occurred during the import run • **Warning** if a warning was issued during the import run • **Info** if the message is only a notice on the import’s execution status • **TBD** if the import run is still ongoing and it is not yet possible to display a status for it
**Note:** • You can view the details of the **individual messages** in the [Import History](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/show-import-history.md). • To jump straight to the history of a specific import, click the eye icon in the configuration column icon column. |
| Number of imported lessors | Number of lessors imported successfully during the import run |
| Number of imported contracts | Number of contracts imported successfully during the import run |
| Number of imported components | Number of contract components imported successfully during the import run |
| Number of issues | Number of issues and warnings output during an import that was not executed successfully
**Note:** • To view the **notes** for imports that were **not executed successfully**, visit the [Import History](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/show-import-history.md). • To jump straight to the history of a specific import, click the eye icon in the configuration column icon column. |
| Configuration column the configuration column icon | To jump straight to the history of a specific import, click the eye icon. |
---
---
title: "Importing Postings into Consolidation & Financial Planning"
source_url: https://support.lucanet.com/en/documentation/lease-accounting/importing-postings-cfp
language: en
last_updated: 2026-09-18
---
# Importing Postings into Consolidation & Financial Planning
## Overview
Postings saved in Lease Accounting can be imported directly into Consolidation & Financial Planning using a script. This integration is available for users with a Consolidation & Financial Planning license.
## Setting up the Import
Before you can import the postings into Consolidation & Financial Planning, you need to perform a one-time setup process, which is described in the following subsections.
### Creating the Import Script
To create the import script:
1. Go to **Import | Scripts**.
2. Right-click your **Lease Accounting folder** (or create a new folder) and select **Create | Script**. The **Create Script** dialog is displayed as follows:
Create script
3. In the **Create Script** dialog, attach the script file provided by:
- Professional Services team during implementation, or
- Customer Support
4. Click **Save.**
5. Click **Edit** in the top right and configure the script with the following information:
- **Name**: Enter a descriptive name for the script.
- **CFO Solution Platform URL**: Enter your platform URL.
- **Reporting entity**: Select the reporting entity (or entities) for which you want to import postings.
- **First month of fiscal year**: Enter the number of the first month (e.g., 1 for January).
6. **Save** the changes.
### Creating the data source
To create the data source:
1. Go to **Import | Importing data into reporting entities**.
2. Right-click your **Lease Accounting folder** (or create a new folder) and select **Create | Data source**. The **Create data source** dialog is displayed as follows:
Create data source
3. Select **Provision via script** as the origin of the data and enter a descriptive **name** for the data source.
4. Click **Save.**
5. Click **Edit** in the top right and configure the data source:
- **Drill down to posting level**: Select the script you created in the previous step.
- **Import type**: Select **Transaction figures**.
- **Data level**: Select the data level where the postings should be imported (e.g., Actual).
- **Adjustment level**: Select the adjustment level for the imported postings. We recommend using a separate adjustment level such as **IFRS 16** to distinguish lease accounting postings from other postings.
- **Dimensions**: Select all dimensions you want to include in your postings.
- **Cost centers**: If you are using specific cost centers in your reporting entity, enable **Use specified cost centers**.
- **Reporting entity**: Add the reporting entity for which you want to import postings.
6. **Save** the changes.
### Creating the Assignment Table
To create the assignment table:
1. Go to **Import |** **Importing data into reporting entities**.
2. Right-click your **Lease Accounting** folder (or create a new folder) and select **Create | Assignment table**. The **Create Element** dialog is displayed as follows:
Create assignment table
3. Enter a descriptive name and click **Save**.
## Importing the Postings
After completing the setup, we recommend that you import the postings **every month** in the following way:
1. Go to the **Import |** **Importing data into reporting entities** workspace.
2. Select your **Lease Accounting data import** (the data source you created during setup) and click **Edit** in the top right.
3. Click **1.Import** and configure the import with the following information:
- **Reporting entity**: Select the reporting entity (or select multiple if needed).
- **Accounting period**: Select the month for which you saved postings (e.g., June 2025).
Configure import
4. Click **Save**. The import typically takes 1-2 minutes to complete.
---
---
title: "Lease Accounting"
description: "Lucanet Lease Accounting offers you a secure and efficient solution for recording, calculating and posting lease contracts in accordance with IFRS 16."
source_url: https://support.lucanet.com/en/documentation/lease-accounting
language: en
last_updated: 2026-09-29
---
# Lease Accounting
### The Solution for IFRS-16-Compliant Accounting
**Lucanet Lease Accounting** offers you a secure and efficient solution for recording, calculating and posting lease contracts in accordance with [IFRS 16](https://support.lucanet.com/en/documentation/glossary.md#ifrs-16).
**Lease accounting** is the process of accounting leases in accordance with IFRS 16 to ensure correct financial reporting and compliance with regulations.
Lease Accounting offers you:
- **Simple and intuitive operation:** When you create a lease contract, the software will actively guide you through the relevant contract dialogs.
- **Contract simulation**: Generate previews of the calculations for your most important lease contracts and check your data.
- **Fast exports**: With just a few clicks, you can export the postings you have saved in Lease Accounting to MS Excel, or generate reports for all the contracts or balances you have created for a set reporting date.
The 'Contracts' workspace in Lucanet Lease Accounting
[Request demo](https://www.lucanet.com/en/request-demo/)
> **Note:** - Do you already use the Lucanet CFO Solution Platform and would like to use Lease Accounting as well? Speak to your Lucanet contact about a Lease Accounting license or get in touch with us via [Contact](https://www.lucanet.com/de/kontakt/).
> - Maybe you’re not a Lucanet customer yet, but you’d like to find out more about our solutions? If so, write to us at [Contact](https://www.lucanet.com/de/kontakt/).
## Your First Steps with Lucanet Lease Accounting
Our instructions will help you get started with Lucanet Lease Accounting in next to no time:
- [Basic Configuration](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting.md)
- [All Steps at a Glance](https://support.lucanet.com/en/documentation/lease-accounting/process-description-lease-accounting.md)
- [FAQs](https://support.lucanet.com/en/documentation/faqs/lucanet-lease-accounting.md)
---
---
title: "Migrating Data"
description: "The Migration workspace lets you move your existing lease portfolio from the IFRS 16 script into Lucanet Lease Accounting. You upload the H2 database file together with the lookup file, run the migration, validate the migrated data, and approve the result."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/migrating-data
language: en
last_updated: 2026-09-02
---
# Migrating Data
## Overview
The **Migration** workspace lets you move your existing lease portfolio from the IFRS 16 script into Lucanet Lease Accounting. You upload the H2 database file together with the lookup file, run the migration, validate the migrated data, and approve the result. Once the migration is approved, Lease Accounting takes over the carrying amounts of your lease portfolio and you can resume calculations, postings, and exports without recalculation gaps.
> **Note:** Preparing the IFRS 16 script in Lucanet.Financial Client and exporting the H2 database file and the lookup file from it is carried out together with your Lucanet Professional Services consultant. This page describes the steps that follow inside Lease Accounting in the CFO Solution Platform.
## Prerequisites
To run the migration from the IFRS 16 script to Lease Accounting, you need one of the following roles:
- Full access administrator
- Settings administrator
- Lease operations administrator
Before you start, prepare the following files from your source IFRS 16 script:
- The **H2 database file** (.mv.db) exported from the IFRS 16 script. This file contains your leasing components, associated payments and options.
- The **lookup file** (XLS or XLSX format) exported from the IFRS 16 script. This file maps source OIDs to their respective transaction currencies and is required so that each migrated component carries the correct component currency.
## Overview of the Migration Flow
The migration from the IFRS 16 script to Lease Accounting consists of the following stages:
1. **Upload** the H2 database file and the lookup file in the **Migration** workspace.
2. **Start the migration** with the migration date that applies to your data.
3. **Check the migration result** in the **Migration result** tab and **download the migration and component validation reports** to identify any data gaps.
4. **Validate** the migrated data in **Lessors**, **Contracts**, and **Contract components** workspaces.
5. **Approve the migration** to unlock calculations, postings, and exports.
## Uploading the Migration Files
To upload the migration files:
1. Navigate to **Settings | Migration**.
2. In the upload area, choose one of the following options to attach the files:
- Drag and drop both files onto the upload area.
- Select **choose a file** and pick both files from your file browser.
The upload area accepts .mv.db database files together with the .XLS and .XLSX lookup files. You must provide both the H2 database file and the lookup file together — the **Upload files** button only becomes active once both files are present and in their expected formats.
3. Click **Upload**.
The files appear as a combined entry in the **Uploaded databases** table with the status **Ready to migrate**.
> **Warning:** **Upload only the latest version of the H2 file and its lookup file.**
>
> Both files are mandatory and must be uploaded together as one package.
>
> If you upload another package after a migration has finished, Lease Accounting adds the new data to the existing migrated data instead of overwriting it.
>
> You can delete an uploaded file until you approve its migration. Deleting an uploaded file does not remove any data that has already been migrated.
## Starting the Migration
To start the migration:
1. In the **Migration date** field in the **Migration** workspace, select the date from which existing carrying amounts for the right-of-use assets are taken over from the IFRS 16 script.
The migration date is used to avoid recalculation gaps or migration differences. Lease Accounting stores the migration date with the uploaded file and shows it later in the **Migration date** column.
Migration date in the 'Migration' workspace
2. In the **Uploaded databases** table, select the **Start migration** icon next to the file you want to migrate. The **Start Migration** dialog is displayed:
'Start Migration' dialog
3. Review the file name and the migration date, then click **Proceed**.
While the migration runs, the **Status** column displays the progress of the migration. When the migration finishes, the status changes to **Migrated** and Lease Accounting displays a confirmation dialog:
Migration confirmation
## Downloading the Migration and Component Validation Reports
After a successful migration, you must validate the migrated data before you can approve the migration and resume calculations, postings, and exports. The data carried over from the IFRS 16 script may contain placeholder values, missing mandatory information, or zero amounts that need your review.
To help you identify these gaps, Lease Accounting provides two on-demand reports — the **Migration report** and the **Component validation report**. Both reports are generated in Excel format and tell you which records need attention, so you know exactly what to correct in the next step.
To download a report:
1. In the **Migration** workspace, select **Migration report** or **Component validation report** above the **Uploaded databases** table.
Uploaded databases table with the Migration report and Component validation report
The reports are generated in the background. Once they are ready, they are automatically displayed in the **Generated reports** table in the same workspace.
2. Click the **Download** icon next to the report to save the Excel file to your computer.
### Migration Report
The **Migration report** lists, for each migrated element (lessors, contracts, contract components, payments, options), whether the element was migrated successfully and, where applicable, the reason for which an element could not be migrated. Use this report to confirm overall data integrity after the migration.
### Component Validation Report
The **Component validation** report lists every component together with its validation findings — the validation rule that triggered, the message returned, and the result (warning, error, or exception).
After a migration, the report shows two additional categories of findings under **Migration from legacy solution:**
- **Dummy values** — flagged whenever a component field still carries placeholder text from the IFRS 16 script. The finding is an error when the placeholder is in the asset class or component currency, and a warning on any other component field.
- **Zero amounts** — flagged as errors whenever an amount field on the component form equals zero, since these usually require review after the migration.
Use this report to find the components that still carry placeholder values from the IFRS 16 script, or that contain zero amounts that may need to be corrected before approval.
## Checking the Migration Result
The **Migration** workspace contains two tabs: the **Migration overview** tab with the upload and migration functions described above, and the **Migration result** tab, which summarizes the outcome of a migration so that you can assess it without opening the Excel reports.
To check the result, open the **Migration result** tab and select the migration in the **Migration execution** drop-down list. By default, the latest migration is selected. The tab displays how many components have been successfully migrated.
If components were not migrated, the **Failed components** table lists every failed component with the columns **Reporting Entity**, **Lease component**, and **Reason for failure**. The components are grouped by reporting entity, and each component displays its failure reasons. Click **Show more** to expand long reason lists.
The 'Migration result' tab
The failed components and reasons match the findings in the **Migration report**.
## Validating the Migrated Data
After you have the report findings, work through them in Lease Accounting. While the migration is pending approval:
- Migrated lessors, contracts, and contract components are available under **Data collection** for review and correction.
- You can save migrated records even when required fields are empty or still hold placeholder values. Normally, Lease Accounting blocks saving until every required field has a valid value, but this rule does not apply to migrated records while the migration is pending approval. This lets you save partial corrections and return to them across multiple sessions. The full check is restored when you approve the migration — every required field must be complete and free of placeholders before you can approve.
- The [Calculation | Preview](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) workspace remains available so you can review potential calculation results at any time. After the migration is approved, use **Calculate and save** to finalize the calculations.
- The [Calculation | Calculations](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) workspace, all workspaces under [Postings](https://support.lucanet.com/en/documentation/lease-accounting/create-postings.md), and [Export | Export postings](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) are hidden until the migration is approved.
To review and correct a migrated record flagged in the reports — a lessor, contract, or contract component — proceed as follows:
1. Navigate to [Data collection | Lessors](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-lessor.md), [Data collection | Contracts](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contracts.md), or [Data collection | Contract components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md).
2. Open the record and review each tab.
3. Replace any placeholder values, complete any missing mandatory information, and select **Save**.
## Approving the Migration
After you have validated all migrated data, approve the migration.
> **Warning:** Select **Approve Migration** only when you are confident that all data has been thoroughly reviewed and validated.
To approve the migration:
1. In the **Migration** workspace, select **Approve migration** in the top right. The **Approve Migration** dialog is displayed:
'Approve Migration' dialog
2. Review the consequences:
- Contract data can no longer be edited.
- Components remain editable until they are calculated.
- Later changes are possible only through standard modifications.
- Further H2 file uploads after approval will follow the migration workspace rules (such as duplicate file rejection by content, not by file name).
3. Click **Proceed**.
When approval succeeds:
- The warning indicators next to **Lessors**, **Contracts**, and **Contract components** are removed.
- The **Calculations**, **Postings**, and **Export postings** workspaces become available.
- The migrated files in the **Uploaded Databases** table receive the status **Approved**.
> **Note:** Approval is only possible if all migrated records pass standard validation. If any record still has missing mandatory fields or other validation errors, Lease Accounting prevents approval and notifies you of the outstanding issues.
## Handling a Failed Migration
If a migration cannot be completed successfully, Lease Accounting displays the status **Failed** for the affected file in the **Uploaded databases** table.
If the migration process fails, try the following steps:
1. **Check the uploaded files** — ensure the H2 file and its corresponding lookup file are valid and not corrupted.
2. **Retry the migration** — you can delete the affected file entry and re-upload the files before starting the migration again.
3. **Contact support** — if the issue persists, please contact your Lucanet administrator or Lucanet Support with the details of this error.
### Missing Reporting Entity
If the H2 file contains records for a reporting entity that does not exist in Lease Accounting, the migration ends with the status **Failed** and the failure reason names the missing OID.
To recover:
1. Import or create the missing reporting entity in Lease Accounting under **Settings | Reporting entities**.
2. In the **Migration** workspace, select the **Re-run** icon next to the failed file.
The re-run skips records that were migrated successfully in the previous run and only processes records that previously failed or were skipped. You do not need to upload the files again.
---
---
title: "Reversing Components"
description: "Reversing components resets them to their “original state”, i.e. how they were before the components’ calculated values were first entered in the database."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/reverse-components
language: en
last_updated: 2026-09-18
---
# Reversing Components
## Overview
**Reversing** components resets them to their **original state**, i.e. how they were before the components’ calculated values were first entered in the database.
> **Warning:** Reversing a component has the following consequences:
>
> - All changes made between when the component was **created** and when **the calculated values were saved in the database for the first time** will **remain in place**.
> - All calculated saved **values** will be **archived**.
> - All recorded component events (e.g. modifications or revaluations) will be **deleted**.
> - All **postings** that have been saved but not yet exported will be **deleted**.
> - A corresponding contra entry with the opposite plus/minus sign will be created for each exported posting. The posting date for this **reversal posting** is the date specified below.
> - Once the reversal is complete, the component is free to be edited as normal again.
> - Reversals **cannot be undone**.
## The ‘Component Reversal’ workspace
The **Component reversal** workspace is displayed as follows:
The 'Component reversal' workspace
## Reversing Components
To reverse a component:
1. Select one of the following options:
- If you want to reverse all reversible components in the selected reporting entity at once, activate the **Reverse all components** option. With the option activated, the **Contract** and **Contract component** drop-down lists are disabled — skip the next two steps and continue with **Perform complete reversal**.
- If you want to reverse individual components, select the **contract** to which the component is assigned and the **contract component** you want to reverse from the respective drop-down lists.
2. Choose the periods the reversal is to be performed for. Do one of the following:
- If you want to reverse all periods, activate the option **Perform complete reversal** and select the **reversal posting date**.
- If you want to reverse only from a specific period onwards, leave the option **Perform complete reversal** deactivated and select the starting month from the **Reverse periods starting from** drop-down list, then select the **reversal posting date**.
3. Click **Perform reversal**. A confirmation dialog is displayed as follows, for example:
'Component Reversal' dialog
4. Click **OK** to confirm component reversal.
> **Warning:** - If you activated the **Reverse all components** option in the first step, Lease Accounting displays an outcome summary after processing with the total number of processed components and how many succeeded or failed. If any components fail, the summary lists the reason so you can take corrective action.
> - Once the reversal is complete, the component is free to be edited as normal again.
> - Reversals cannot be undone.
> - If you switch to another workspace during configuration, any unsaved changes made to your configuration will be lost.
---
---
title: "Reversing Postings"
description: "In Lucanet Lease Accounting, you have the option of reverse postings that have already been created or exported in the 'Reverse postings' workspace."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/reverse-postings
language: en
last_updated: 2026-09-18
---
# Reversing Postings
## Overview
In the **Reverse postings** workspace, you have the option of reversing postings that have already been saved or exported.
> **Warning:** Reversing a posting has the following consequences:
>
> - All postings that have been saved but **not yet exported** will be **archived**.
> - For every **[already exported](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md)** posting, a corresponding contra entry will be created with the selected reversal posting date. Exporting the posting again causes the system to save the contra entry to the data archive.
> - The measurements, modifications and/or reassessments of a contract component are not reset.
> - After the posting has been reversed, contract components can be modified and reassessed and added with an effective date within the reversed periods.
> - The **status** of the affected periods is set to **not posted**. These periods can be posted again after the posting has been reversed.
> - **Existing** reversal postings and reversed postings remain unaffected.
> - The reversal of a posting **cannot be undone**.
## Reversing Postings
To reverse a posting:
1. Open the **Reverse postings** workspace:
The ‘Reverse postings’ workspace
2. Select the **contract** and the **contract component** for which you want to reverse the postings.
3. Select the **period** from which you want to reverse the postings.
4. Select the **reversal posting date**.
5. Click **Reverse postings**.
> **Warning:** **Note on configuration**
>
> - It is only possible to select contracts and contract components that have been created for the selected reporting entity.
> - The period from which the postings are to be reversed must be within the lease term and before the last payment.
> - The reversal posting date must be greater than or equal to the start date of the contract component or the effective date of IFRS 16.
> - The reversal posting date must be greater than or equal to the maximum posting date of the reversed periods.
> - If the contract component is posted again, the new posting date for the reversed periods must be greater than or equal to the last active posting stamp for the relevant contract component.
## Example of a Posting Reversal
The following example illustrates how a posting is reversed:
**Saved postings**
- Accounting period January 2024 | Posting stamp: March 2024
- Accounting period February 2024 | Posting stamp: March 2024
- Accounting period March 2024 | Posting stamp: March 2024
**Input for posting reversal**
Reverse periods starting from: February 2024
**Periods that will be reversed**
February 2024 and March 2024
---
---
title: "Saving Postings"
description: "When you have assessed and calculated the components, you can preview and save the postings for these components. The postings are automatically saved in the Lease Accounting database and can then be exported or imported into Consolidation & Financial Planning."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/create-postings
language: en
last_updated: 2026-10-02
---
# Saving Postings
## Overview
When you have [assessed and calculated](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) the components, you can **save** the **postings** for these components in the Lease Accounting database.
Before you save the postings, you can display the **components to be posted** and preview the pending postings in the **Preview & save postings** workspace.
> **Note:** You can [export](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) the saved postings and import them into other systems. If you use Lucanet Lease Accounting integrated with Consolidation & Financial Planning, you can additionally [import](https://support.lucanet.com/en/documentation/lease-accounting/importing-postings-cfp.md) the postings directly into Consolidation & Financial Planning using a script.
## Displaying Components to be Posted
Before you save the postings for the [previously calculated](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) components, you can display all the **components to be posted** that have not yet been posted up to a selected date.
To do this, open the **Components to be posted** workspace and select the **Accounting period** up to which you want to display the components that have not yet been posted. The components are then displayed in a table:
'Components to be posted' workspace
> **Tip:** The **Status** column indicates whether a component is a **new component (NEW_POSITION)** that is being added for the first time or a **stock component (STOCK_POSITION)** that is being updated by the posting.
## Previewing and Saving Postings
In the **Preview & save postings** workspace, you display the pending postings for the calculated components, check them, and save them in the Lease Accounting database.
To preview and save the postings:
1. Navigate to **Postings | Preview & save postings**.
2. In the **Reporting entities** drop-down list, select one, several, or all reporting entities (default: the reporting entity you are signed into) for which you would like to save the postings.
> **Note:** If you use an integration between Lease Accounting and Consolidation & Financial Planning, you can [import](https://support.lucanet.com/en/documentation/lease-accounting/importing-postings-cfp.md) the saved postings for multiple reporting entities simultaneously using a script.
3. Under **Save postings up to**, select the posting period up to which you would like to save postings.
4. Click **Preview postings**. The table lists every posting that has not yet been saved for the selection, and the number of **Posting lines** and **Contracts** is displayed next to the buttons.
The preview table with pending postings
> **Note:** The preview does not change any data. Click **Export** to export the previewed postings as an XLSX file; the exported file is marked as **Preview only — not a booking voucher**.
5. Click **Save postings**. The **Save Postings** dialog is displayed:
The 'Save Postings' dialog
6. Confirm the **Save Postings** dialog, which displays the selected period and the number of selected reporting entities. The postings are saved automatically in the Lease Accounting database.
> **Tip:** Save the postings after each month to ensure that the postings receive the correct posting date.
> **Note:** Previewing before saving is optional — you can click **Save postings** without displaying the preview first.
## Currency Translation of the Lease Liability
If the component currency differs from the functional currency of the reporting entity, Lucanet Lease Accounting translates the amounts into the functional currency:
- The amounts pertaining to the **right-of-use asset** are translated when the components are [calculated](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) and are therefore already displayed in the functional currency in the preview.
- The **lease liability** and all related values, such as repayments and interest, are translated when the postings are saved, using the closing rate of the posting period.
The difference arising from retranslating the lease liability at the closing rate is posted separately with the posting type **Currency Translation Difference - Lease Liability** and recognized in profit or loss. It is calculated individually for the short-term, mid-term, and long-term portions of the lease liability. In the preview table, these posting lines display only the **Amount in functional currency**; the **Amount in contract currency** and **Exchange rate** columns remain empty.
> **Note:** If an exchange rate is missing for the posting period, the affected postings are not saved, and a message refers you to the [Exchange rate management](https://support.lucanet.com/en/documentation/administration/exchange-rate-management.md) functional area under **Administration**, where you can check your currency combinations and rates.
> **Tip:** Saved postings can be removed from the database by reversing them. For additional information, see [Reversing Postings](https://support.lucanet.com/en/documentation/lease-accounting/reverse-postings.md).
---
---
title: "Selecting a Lessee"
description: "A lessee is the party who receives the right to use an asset under the conditions of a lease contract. In Lucanet Lease Accounting, leases are recorded separately for each lessee."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/select-lessee
language: en
last_updated: 2026-05-01
---
# Selecting a Lessee
## Overview
A **lessee** is the party who receives the right to use an asset under the conditions of a lease contract.
In Lucanet Lease Accounting, leases are recorded **separately for each lessee**.
Before you start recording the lease information, you must first select the **reporting entity** for which you want to enter or edit leases as the lessee.
## Selecting a Lessee
To select a lessee, open the **Get started** workspace and use the drop-down list to select the **Reporting entity** for which you want to record leases:
The 'Get started' workspace
> **Warning:** **Notes**
>
> - To record data in Lease Accounting, a user must be granted access rights to **Lease Accounting** in the **Administration | User Management** area of the **Lucanet CFO Solution Platform** (see [Creating and Editing Users for the CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md)).
> - During a user’s **first login**, all the solution’s workspaces – except for **Settings** – will remain hidden until a reporting entity is selected.
> - If a user needs to enter or edit data for several reporting entities, they must take care to select the correct reporting entity under **Get started**.
> - Users can select any reporting entity from the Lucanet.Financial Client that has already been imported into Lease Accounting using the **Reporting entities** workspace (see [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-lessees.md)).
> - The reporting entities can only be used correctly to calculate lease component if all the mandatory fields have been configured (see [Creating and Configuring Reporting Entities](https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/manage-lessees.md)).
---
---
title: "User Roles in Lease Accounting"
description: "The role-based permission system in Lease Accounting enables administrators to control access to specific functions and data within the solution with the following six predefined roles."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/user-roles-la
language: en
last_updated: 2026-10-06
---
# User Roles in Lease Accounting
## Overview
The role-based permission system in Lease Accounting enables administrators to control access to specific functions and data within the solution with the following six predefined roles:
- **Data collector**
- **Executive reviewer**
- **Lease operations administrator**
- **Auditor**
- **Settings administrator**
- **Full access administrator**
By assigning appropriate roles to users, you can optimize workflows, increase data security, and provide tailored user experiences that align with operational requirements.
## Assigning User Roles
Use the **Administration** section of the **Lucanet CFO Solution Platform** to assign user roles (see [User Management](https://support.lucanet.com/en/documentation/administration/user-management.md)).
## Access to Reporting Entities
In addition to the user role, you can define which reporting entities a user can access. The user then only works with the data of these reporting entities.
By default, a user with a user role for Lease Accounting can access all reporting entities. The reporting entities are assigned in the **Administration** section of the Lucanet CFO Solution Platform (see [Assigning Reporting Entities to Lease Accounting Users](https://support.lucanet.com/en/documentation/administration/user-management/users/assigning-reporting-entities.md)).
If a user can only access some reporting entities, Lucanet Lease Accounting offers only these reporting entities in the reporting entity selection of the function bar and in the **Reporting entities** drop-down lists, for example, when creating reports or exporting postings. The **Created files** workspace displays only the files that the user has full access to. If a file includes several reporting entities, the user must be assigned to all of these reporting entities to see the file.
## Available User Roles
Lucanet Lease Accounting provides six distinct user roles, each with specific permissions across the solution's functional areas:
### Data Collector
The **Data collector** role is designed for users responsible for gathering and entering lease contract information into the system.
Data collector has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | |
| Lessors | Edit |
| Contracts | Edit |
| Components | Edit |
| Component reversal | No permissions |
| **Categorization** | |
| Components to be categorized | Edit |
| **Calculation** | |
| Preview | Read |
| Calculation | No permissions |
| **Postings** | |
| Components to be posted | Read |
| Create postings | No permissions |
| Posting reversal | No permissions |
| **Export** | |
| Create reports | Execute |
| Export postings | No permissions |
| Created files | Read |
| **Settings** | No permissions |
### Executive Reviewer
The **Executive Reviewer** role is intended for users who oversee lease accounting processes, approve critical operations, and perform final steps including posting.
Executive reviewer has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | |
| Lessors | Read |
| Contracts | Read |
| Components | Read |
| Component reversal | Edit |
| **Categorization** | |
| Components to be categorized | Edit |
| **Calculation** | |
| Preview | Execute |
| Calculation | Execute |
| **Postings** | |
| Components to be posted | Execute |
| Create postings | Execute |
| Posting reversal | Execute |
| **Export** | |
| Create reports | Execute |
| Export postings | Execute |
| Created files | Execute |
| **Settings** | No permissions |
### Lease Operations Administrator
The **Lease operations administrator** role is designed for users who manage day-to-day lease accounting operations with extensive functional access, comprising the permissions of both Data collector and Executive reviewer roles.
Lease operations administrator has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | |
| Lessors | Edit |
| Contracts | Edit |
| Components | Edit |
| Component reversal | Edit |
| **Categorization** | |
| Components to be categorized | Edit |
| **Calculation** | |
| Preview | Execute |
| Calculation | Execute |
| **Postings** | |
| Components to be posted | Execute |
| Create postings | Execute |
| Posting reversal | Execute |
| **Export** | |
| Create reports | Execute |
| Export postings | Execute |
| Created files | Execute |
| **Settings** | No permissions |
### Auditor
The **Auditor** role provides comprehensive read access across the system for audit and compliance purposes.
Auditor has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | |
| Lessors | Read |
| Contracts | Read |
| Components | Read |
| Component reversal | Read |
| **Categorization** | |
| Components to be categorized | Read |
| **Calculation** | |
| Preview | Read |
| Calculation | Read |
| **Postings** | |
| Components to be posted | Read |
| Create postings | Read |
| Posting reversal | Read |
| **Export** | |
| Create reports | Execute |
| Export postings | Read |
| Created files | Read |
| **Settings** | |
| Reporting entities | Read |
| Cost centers | Read |
| Asset classes | Read |
| Interest rates | Read |
| General configurations | Read |
### Settings Administrator
The **Settings administrator** role is specialized for users responsible for system configuration and maintenance.
Settings administrator has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | No permissions |
| **Categorization** | No permissions |
| **Calculation** | No permissions |
| **Postings** | No permissions |
| **Export** | No permissions |
| **Settings** | |
| Reporting entities | Edit |
| Cost centers | Edit |
| Asset classes | Edit |
| Interest rates | Edit |
| General configurations | Edit |
### Full Access Administrator
The **Full access administrator** role provides the highest level of system access for comprehensive administration. Full access administrators can create, assign, update, and manage users for the **Lease Accounting** solution from the **Administration** workspace in the platform.
Full Access Administrator has the following permissions:
| Area | Permissions |
|---------|---------|
| **Data collection** | |
| Lessors | Edit |
| Contracts | Edit |
| Components | Edit |
| Component reversal | Edit |
| **Categorization** | |
| Components to be categorized | Edit |
| **Calculation** | |
| Preview | Execute |
| Calculation | Execute |
| **Postings** | |
| Components to be posted | Execute |
| Create postings | Execute |
| Posting reversal | Execute |
| **Export** | |
| Create reports | Execute |
| Export postings | Execute |
| Created files | Execute |
| **Settings** | |
| Reporting entities | Edit |
| Cost centers | Edit |
| Asset classes | Edit |
| Interest rates | Edit |
| General configurations | Edit |
---
---
title: "Viewing Import History"
description: "In Lucanet Lease Accounting, you can visit the ‘Import history’ workspace at any time to access information on all your previous imports across all reporting entities. This allows you to view the properties, status and execution errors for each individual import."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/data-collection/show-import-history
language: en
last_updated: 2026-05-01
---
# Viewing Import History
## Overview
In the **Import history** workspace, you can access information on all your previous imports at any time and across all reporting entities. This allows you to view the **properties**, **status** and execution **errors** for each individual import.
## Viewing Import History
To view the **import history** of an import, select the import in question from the **Import** drop-down list:
Select import from import history
## Details in the Import History
### General
The **General** area displays general information on the execution of the entire **Import run**:
'General' area in the 'Import history' workspace
| Field | Description |
|---------|---------|
| Date | Date of the import run |
| User name | The user who performed the import run |
| Reporting entity OID | OID of the reporting entity (lessee) for whom the import run was executed |
| File name | Name of the imported file |
| Import mode | The file type to be imported. This is always CSV. |
| Import type | The data type that was imported. The following options are displayed: • **StandardExternalParter** for importing **lessors** • **LucanetContract** for importing **contracts** • **LucanetComponent** for importing **contract components** |
| Status | Status of the import. The following options are displayed: • **Success** if the import was completed successfully • **Error** if an error occurred during the import run • **Warning** if a warning was issued during the import run • **Info** if the only message is a notice on the import’s execution status • **TBD** if the import run is still ongoing and it is not yet possible to display a status for it. |
| Number of imported lessors | Number of lessors imported successfully during the import run |
| Number of imported contracts | Number of contracts imported successfully during the import run |
| Number of imported components | Number of contract components imported successfully during the import run |
| Number of issues in the import file | Number of errors and warnings output during an import that was not executed successfully |
### Overview Table
The **Overview table** provides detailed information on every **individual message** output during importing of the CSV file.
Overview table in the 'Import history' workspace
| Column | Description |
|---------|---------|
| ID | Message ID |
| Status | Execution status of the import step to which the message applies |
| Import line | Import line in the CSV file to which the message applies |
| Lessor company ID | Number or ID for the lessor to whom the message applies (only relevant when importing lessors). |
| Contract number or ID | Number or ID for the contract to which the message applies (only relevant when importing contracts). |
| Component number or ID | Number or ID for the component to which the message applies (only relevant when importing contract components). |
| Message | Message output during execution of the import run |
> **Tip:** If the message is cut off, hover the cursor over the message text to read the full message in the form of a tooltip.
---
## Extended Planning & Analysis (xP&A)
Modeling, forecasting, planning - Lucanet xP&A enables your business with a 360° view of planning and analysis data from a single source of truth.
---
title: "Aggregating Dimensions"
description: "The dimension aggregation function determines how the values of different dimension items are combined into one value. This affects the summary value when a variable is collapsed, aggregating the variable in formulas and grouping by other dimensions (see Dimension modifiers)."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions
language: en
last_updated: 2026-05-01
---
# Aggregating Dimensions in Lucanet xP&A
## Overview
The **dimension aggregation** function in Lucanet xP&A (Extended Planning & Analysis) determines how the values of different dimension items are **combined into one value.** This affects the summary value when a variable is collapsed, aggregating the variable in formulas and grouping by other dimensions (see [Dimension modifiers](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md)).
## Configuring the Dimension Aggregation in xP&A
By default, xP&A **sums up** all dimension items when aggregating a variable. To change this, right-click the variable and select a different **Dimension Aggregation**.
For example, if you have split **Employee Benefits** input by **Department**, it might be more appropriate to see the average of the **Departments**, not the total.
Changing the Dimension Aggregation
## Dimension Aggregation Options in xP&A
The available dimension aggregation options in xP&A are:
- **No Aggregation**: can be used when there is no meaningful way to aggregate a variable - it will just show a dash instead of any number.
- **Average**: takes the average value of items in the dimension
- **Min and Max**: takes the minimum or the maximum value of the dimension
- **Median**: takes the median value of all the items within this dimension
> **Note:** **Note**, if the variable has many dimensions, the median value will be calculated over the **lowest level** cells. E.g. if you have **Sales** variable broken down by **Profit Centre A**/ **Profit Centre B** and **Product 1**/ **Product 2**, the total median value for **Sales** will be calculated over four data cells that have both **Profit Centre** and **Product** specified
- **Formula**: uses the variable's formula at the 'aggregate' level, to calculate an aggregation value.
- A good example of this is to think of gross margin across two different centres:
- Profit Centre A - $100K in Net Sales, $90K in Costs - Gross margin is 10%
- Profit Centre B - $1M in Net sales, $500k in Costs - Gross margin is 50%
- By default, xP&A will display the **Gross Margin** variable (**Net Sales-Revenue**)/ **Net Sales** as a **Sum** \- so we would see 60% as our top-level **Gross Margin**.
- A common way around this is to use the **Average** dimension aggregation, which would display a 30% **Gross Margin**. This value is also incorrect, as **Profit Centre B** has much higher net-sales, and its impact to margin should be greater than **Profit Centre A**.
- Logically - the way to do this calculation appropriately would be to add the sales and costs of both profit centres, and then apply the calculation. This is what the **Formula** dimension aggregation helps us achieve, giving us the correct value of 46.4%.
---
---
title: "Aggregation Functions"
description: "Lucanet xP&A has three types of Aggregation Functions that determine how a variable 'rolls up' Categories, Time, and Data respectively."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions
language: en
last_updated: 2026-05-01
---
# Aggregation Functions in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) has three types of aggregation functions that determine how a variable 'rolls up' **Dimensions**, **Time**, and **Data** respectively.
## Aggregation Functions in xP&A
The following aggregation functions are available in xP&A:
| Element | Description |
|---|---|
| **Dimension aggregation** | By default, Lucanet xP&A will take the **Sum** of each dimension item's value to aggregate the variable. However, there are examples where **Sum** does not make sense, e.g. if you have split **Bonus** % by **Department**, it might be more appropriate to see the average of the **Departments**' **Bonus**%, not the **Sum**.
For more information on dimension aggregation, see [Dimension Aggregation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md). |
| **Time aggregation** | In charts and tables, and in roll-up columns in the spreadsheet, Lucanet xP&A automatically rolls up a variable's values across time.
**For example**: If your model is monthly and you have a revenue variable, then xP&A can automatically summarize the total revenue in each year or each quarter. The **time aggregation** function determines how this roll-up happens, and whilst the default is **Sum**, there are examples where you would want other methods (e.g. for balance sheet items like **Cash**, you would want to take the final amount for the 2023 balance, not the sum of all the 2023 balances).
**Note:** The **Time Aggregation** setting of a variable also determines how a variable is 'rolled up' to a model with a higher-level granularity, for example from a weekly model to a monthly model. For more information, see [Different Time Granularities](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/time-granularities.md). |
| **Data aggregation** | The **data aggregation** function on a [variable connected to data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) determines aggregates transactions within each data item linked to a variable. This is usually always going to be **Sum**(which is the default), but there are examples where you might want it to use **Average**, **Median**, **Initial**, **Final**, or **Count** instead.
**Example**: If you have daily cumulative data in your data source, and are pulling that into a weekly or monthly model in xP&A, Sum wouldn't make sense (as that would be adding multiple cumulative numbers together), so you might choose **Final** instead. E.g. 2022-12-20 Cumulative User Count 33 2022-12-21 Cumulative User Count 35
**Sum** would return 68 whereas **Final** would return 35 (the true ending users for the week/month). |
## Aggregation Methods in xP&A
The default method for all three aggregation functions in xP&A ( **Dimensions**, **Time**, **Data**) is **Sum**, but there are other methods available:
- **Average**
- **Min/Max** (not available for Data/Time Aggregation)
- **Final/Initial** (not available for Dimension Aggregation)
- **Median** (not available for Time Aggregation)
- **Formula** (not available for Data Aggregation)
## Using an Aggregation Function in xP&A
The aggregation of a variable can be set via the variable's context menu in xP&A.
1. Click the edit icon to open the context menu.
2. Click **Aggregation**.
Context menu of a variable
3. Click **Aggregation**. The context menu is displayed as follows:
Menu 'Aggregation'
4. Choose the desired **aggregation method**.
And you can find this setting by right-clicking on a **variable in a formula**:
Menu 'Aggregation Function'
---
---
title: "All Steps at a Glance"
description: "In this chapter, you will find the individual steps required to create and use models for the planning and analysis of your data. The step descriptions also contain links to more detailed descriptions."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/process-description-xpa
language: en
last_updated: 2026-05-01
---
# All Steps at a Glance in Lucanet xP&A
## Overview
In this chapter, you will find the individual steps required to create and use models in **Lucanet xP&A** (Extended Planning & Analysis) for the planning and analysis of your data. The step descriptions also contain links to more detailed descriptions.
### Step 1: Creating a New Model
On the start page of Lucanet xP&A, [create](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md) a new model and choose between **Basic New Model** (starting from scratch) or a **template**.
### Step 2: Adding Data and Dimensions
In the **Data** workspace, manage the [data sources](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md) for your Lucanet xP&A model. You can either select an **existing data source** or connect to a **new data source**. Afterwards, you can configure [dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md), if necessary.
### Step 3: Configuring Input Variables
Define [variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md), the key building blocks of your model.
Create new variables in your **model**, then enter **values** manually, **connect data sources**, or use **formulas**.
### Step 4: Calculating Output Variables
Structure your analysis and create calculations.
- **Add sections** to [organize](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/organizing-models.md) your model.
- **Add [formulas](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas.md) and reference inputs** to build all the variables you wish in your model.
### Step 5: Editing the Dashboard
**Visualize** your results using [charts and tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md) in Lucanet xP&A.
On the **Dashboard** tab, you can add charts or tables.
### Step 6: Sharing the Model
Collaborate with your team by [sharing your model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) or dashboard in Lucanet xP&A.
By clicking **Share**, you can give access to colleagues and configure [views](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views.md) to control which parts of the model are shared.
---
---
title: "Basic Concepts and Elements"
description: "The following section describes the most important concepts and elements in Lucanet xP&A. Further details can be found under the links provided."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/basic-concepts-and-Elements
language: en
last_updated: 2026-05-01
---
# Basic Concepts and Elements in Lucanet xP&A
## Overview
The following section describes the most important **concepts** and **elements** in Lucanet xP&A (Extended Planning & Analysis): **Model**, **Scenario**, **Spreadsheet vs. Dashboard**, **Variable**, **Dimension**, and **View**. Further details can be found under the links provided.
## Concepts and elements in Lucanet xP&A
The following concepts and elements are used in Lucanet xP&A:
| Element | Description |
|---|---|
| **Model** | In Lucanet xP&A, a model is a powerful tool for financial planning and analysis. Think of it like a structured spreadsheet where you can input data, build formulas, and run calculations.
You can organize models into folders, share them, clone them, and link them to other models — all within the xP&A interface for seamless navigation and management.
For more information on models, see [Creating a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md) and [Working with Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models.md). |
| **Scenario** | A **scenario** in Lucanet xP&A is a dynamic version of your model where specific variables or values change, but the overall structure — variables, groups, and sections — stays the same.
Scenarios let you test different assumptions, compare outcomes, and make data-driven decisions without altering your core model.
For more information on scenarios, see [Scenarios](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-scenarios.md). |
| **Spreadsheet vs. Dashboard** | In Lucanet xP&A, the **spreadsheet** is where you enter and manage a model's inputs and calculations. It is the core workspace for data entry, applying formulas, and structuring your financial model.
The **dashboard** is where your data comes to life. It is the visual layer that transforms your inputs into charts and insights, helping you analyze trends and make informed decisions.
Easily switch between the spreadsheet (data input and calculations) and the dashboard (visualization and analysis) using the toolbar. |
| **Variable** | **Variables** are the building blocks of your models in Lucanet xP&A. You can define a variable using a [formula](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas.md).
Variables can be one single row, or they can consist of one top row and constituent rows (if the variable is [broken down into dimension items](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md)). |
| **Dimension** | [Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md) in Lucanet xP&A are a way to organize and manage data within a model. They are useful when you have a concept that's broken down.
Examples: • Number of customers (variable) broken down by Geography (dimension) • Revenue (variable) broken down by Product (dimension) • Ad spend (variable) broken down by Marketing Channel (dimension) |
| **View** | **Views** in Lucanet xP&A let you create saved filters on your model, to show only specific variables, dimension items, scenarios, time periods, and charts. |
> **Note:** In Lucanet xP&A, users with the **Viewer** role can create their own private models that are only visible to them.
---
---
title: "Cells and Limits"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cells-and-limits
language: en
last_updated: 2026-05-01
---
# Cells and Limits in Lucanet xP&A
## Overview
A **cell** in Lucanet xP&A (Extended Planning & Analysis) represents a single number in the spreadsheet.
The **model cell count** is the total number of cells when all variables and dimensions are expanded across all scenarios in a model.
Your **organization's cell count** is calculated by adding together the cell counts of each of your models.
When using xP&A, there are **limits** on the number of cells that can be used across your organization.
The default limit is 150 million cells. (If you need more than 150 million cells, then please get in touch with us to increase the limit.)
The more cells you use, the more it affects the **performance of your model**.
In this article, you can find examples on how your cells are counted and information on how proper dimension linking can influence your cell count.
## Example 1: P&L in xP&A
Suppose that you have a P&L model in xP&A:
- Your P&L has 50 line items, represented by **50** variables.
- Your P&L is broken down into **10** departments, represented by a **Department** dimension.
- Your P&L is **monthly**, with 4 years of historical data and 1 year of forecasts ( **5** years total).
The cell count of your P&L would be calculated as follows:
- Variables: **50**
- Dimension items per variable: **10**
- Time steps: 12 x 5 = **60**
**Total = 50 x 10 x 60 = 30,000 cells**
## Example 2: Cohort Model in xP&A
Suppose that you have a SaaS revenue model with monthly cohorts:
- You have **3** different products, represented by a **Product** dimension.
- You have customers in **5** countries, represented by a **Country** dimension.
- You are modelling the customer build (new, churn, expansion, contraction, total) and ARR build, represented by **10** variables in total.
- Your model has 5 years of historicals and 5 years of forecasts ( **10** years total), with **monthly** cohorts.
- You have **3** scenarios with different assumptions: base case, upside, downside.
The cell count of your cohorted revenue model would be calculated as follows:
- Variables: **10**
- Dimension items per variable: 5 x 3 = **15**
- Time steps: 12 x 10 = **120**
- Cohort items per variable: **120**
- Scenarios: **3**
**Total = 10 x 15 x 120 x 120 x 3 = 6,480,000 cells**
## The Importance of Proper Dimension Linking in xP&A
When modeling employee data, it's essential to understand that each employee exists within a specific organizational structure. Every employee is assigned to:
- **One team**
- **One job title**
- **One department**
- **One region**
Because of these one-to-one relationships, dimensions must be properly linked to reflect these real-world constraints.
## Impact of Linked Dimensions on Cell Count and Model Performance in xP&A
**With Proper Dimension Linking**
When dimensions are correctly linked, the model efficiently allocates resources based on the actual organizational structure. For our scenario (1 month, 1 scenario, no additional dimensions), this results in:
- 1,000 cells for 1,000 employees
**Without Proper Dimension Linking**
When dimensions are not linked, xP&A treats each dimension as independent and calculates all possible combinations, resulting in:
- 1,000 employees × 150 job titles × 40 departments × 20 regions × 30 teams
= 3,600,000,000 cells
This dramatic difference—from 1,000 cells to 3.6 billion cells—demonstrates why proper dimension linking is not just a best practice, but a critical requirement for model performance and system stability.
> **Tip:** Always verify your dimension relationships before implementing your model to avoid exponential cell growth and potential system performance issues.
---
---
title: "Cloning a Model"
description: "By cloning a model, you can create an identical copy of the model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cloning-a-model
language: en
last_updated: 2026-05-01
---
# Cloning a Model in Lucanet xP&A
## Overview
By cloning a model in Lucanet xP&A (Extended Planning & Analysis), you can create an identical copy of the model. A cloned model can be useful for the following cases, for example:
- **Template creation**: A cloned model allows you to create templates that can be reused or shared with others.
- **Experimentation**: You can use a cloned model to experiment with changes without affecting the original model.
- **Collaboration**: Cloning a model facilitates collaboration by enabling others to work on a copy of the model without altering the original.
> **Warning:** In order to clone a model you need full access to the model or the model needs to be shared with you with the option **Allow cloning as a template**.
## Cloning a Model in xP&A
To clone a model in xP&A:
1. Navigate to the model on the start page.
2. Click the **three-dot menu** and select **Duplicate:**
'Duplicate' option
If you have other models linked and/or dimensions assigned to the model you want to clone, the **Cloning _Model name_** dialog is displayed as follows, for example:
![Shows the 'Cloning [model name]' dialog in xP&A. Highlighted in red are the 'Linked models' section (with the option to clone linked models or only this model), the 'Dimensions' section (with the option to duplicate or use existing dimensions), and the 'Data sources' section (with the option to duplicate or use existing data sources).](_images/en/cloning-a-model.png)
Dialog when cloning a model
3. Choose if you want to also **Clone _X_ linked models** or if you want to **Only clone this model**.
4. Choose if you want to **Duplicate _X_ dimensions** or if you want to **Use existing dimensions**.
**Note**: If you duplicate the assigned dimensions, you can adjust the duplicated dimensions for planning different scenarios without changing the existing dimensions.
5. Choose if you want to **Duplicate data sources** or if you want to **Use existing data sources** for the cloned model.
6. Click **Clone X models**.
The cloned model(s) will be displayed with the addition **(cloned)** in the model overview of the start page.
## Allowing Others to Clone Your Model in xP&A
You can allow others (who don't have full access) to make a clone of your model. Proceed as follows:
1. Click the **Share** button in the toolbar.
2. On the **Settings** tab, activate the option **Allow cloning as a template**:
Allowing to clone as a template
3. Share the model via public or private link (see [Sharing a model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md)).
All users with whom you shared the model then have the option to click **Use this template** in the top-right, when viewing the model's dashboard.
---
---
title: "Common Formulas"
description: "The following topic give you a taste of common formulas used in Lucanet xP&A, across different themes/use cases."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/common-formulas-
language: en
last_updated: 2026-05-01
---
# Common Formulas in Lucanet xP&A
## Overview
The following article provides an overview of common formulas used in Lucanet xP&A (Extended Planning & Analysis), across different themes and use cases.
### Headcount
### Active Headcount in Lucanet xP&A
This example calculates **Active Headcount** in Lucanet xP&A by comparing each employee's **Start date** and **End date** to the current date.
Active headcount
- Note that both **Start date** and **End date** are broken down by the **Employee** dimension.
- **End date** will have to have [Empty Value](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md) setting of **None**(this is the default for variables formatted as **Dates**).
- The result is a flag, which returns a **1** for each month that the employee that is active with the company, and **0** when they are not.
- The **Total of all Employees** will reflect **Total Headcount** for each month for the company.
### Headcount by Department in Lucanet xP&A
Headcount per Department
As long as your employees are mapped to a **Department**, you can reference any variable broken down by **Employee** and [grouped by](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) **Department**(or any other mappings).
### New Hire in Lucanet xP&A
New hire
Returns a **1** on the employees **start date**, useful for things like New Hire Capex (e.g. Laptops).
### Bonus in Lucanet xP&A
Bonus
- The first part of the formula sets the bonus **month** to **January**(1).
- **Start Date < date - 6** ensures employees have been with the company at least 6 months before receiving a bonus.
- **Annual Salary \* Bonus Target %** results in the bonus amount. Multiplying by **Headcount** will ensure that the bonus is paid only if the employee is active (see **Headcount** formula above)
- Note that the **Bonus Target %** can be set at Department level, seniority, or any other level depending on how you map your dimensions.
### Flat Fee Per Person Costs in Lucanet xP&A
Flat fee per person costs
- Simply set a per employee assumption (can be by department, etc.) as a flat rate
- Multiply that rate by your headcount
### Percentage of Salary Costs in Lucanet xP&A
Percentage of salary costs
- Simply apply a **% rate** to the applicable cost base.
- Like all inputs, they can be split into dimensions for more granular approaches.
### Geography Specific Calculations in Lucanet xP&A
Geography specific calculations
You can create [if then statements based off dimension items](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/if-statements-in-formulas.md), xP&A will automatically apply the correct assumptions to the formula. No need to set any filters!
### Seasonality in Lucanet xP&A
There are many approaches to seasonality in Lucanet xP&A. The following two are the most used, but feel free to take an approach that best fits your needs. Both approaches use the concept of [relative time](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md) so familiarize yourself with it if you have not already.
### Seasonality as a % of Annual Total in Lucanet xP&A
- In this approach you can create a **Seasonality** variable that applies a % of the annual value over 12 months (7 days, 30 days, etc) so that adding Jan-Dec would add up to 1 or 100%.
- Make sure to set up the variable as relative time.
Seasonality as a % of annual total
- Then use another input variable for your **Annual Target**.
- The resulting formula below uses **month - 1** as the [time modifier](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md). The -1 aligns xP&A's [time step index](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md) (which starts at 0), with xP&A's [month index](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) (1-12 for Jan-Dec). Note the **-1** is used because this model starts in **January**, if the model was to start in February, **-2** should be applied and so on for other month start dates.
Seasonality with 'month-1'
### Seasonality as a Variance to the Average in Lucanet xP&A
- The previous approach (% of annual total) divides an annual target throughout the year, whereas this approach adjusts monthly numbers for seasonality.
- The **Seasonality** input in this case, should equal **100%** for “average” months and 120% or **90%** for above or below average months, respectively (and versus adding up to 100% for the year in the previous approach).
Seasonality as a variance to the average
### Cohorts
### What is Cohort Modeling in Lucanet xP&A?
In order to understand your customers at a deeper level, you'll often want to **track** them on a more **granular basis**, using time-based cohorts. This is because customers can behave differently at different points in time, for example:
- **Retention and expansion rates** often follow a pattern depending on how many months they've been a customer.
- **Churn rates** may differ depending on what time of year a customer joined.
- **Spend or engagement** may be higher in initial months after sign-up, then drop off.
- If you have a new **onboarding flow**, more customers might retain in the 2nd month, (vs. when there was no new onboarding flow).
To forecast on this cohort basis, you need to be able to split your customers into different cohorts, so you can apply the correct assumptions (e.g. churn, retention etc) at different points in time.
### Cohorts in Lucanet xP&A
In xP&A, **cohorts act as a dimension that reflects the time period of the model**. For example, if a monthly model goes from **Jan '22** to **Dec '22**, adding cohorts would add **12 items**, one for each month in the model.
Month cohorts
You can access cohorts by explicitly adding the **Cohort** dimension in the **variable** or by referencing cohorts in the **formula**. Below is a simple example of using cohorts:
### Cohort of Leads That Convert Into New Customers in Lucanet xP&A
Cohort of leads that convert into New Customers
**Example Inputs**:
1. New sign-ups is **1,000** for our first month and grows at **5%.**
2. Activation of cohort uses [relative time](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md) so that 1st month is **45%**, 2nd is **25%**, etc.
Activation of cohorts
Simply, this formula is saying "Signups multiplied by activation rate %"
### What is the "cohort" and "t-cohort" doing in Lucanet xP&A?
- By putting cohort as the [time modifier](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) of the **New sign-ups** variable, we are telling xP&A to use the new sign-ups for January in the **Jan** cohort, February in the **Feb** cohort, etc.
- By using **t-cohort** as the time modifier of the **Activations** variable, we are telling xP&A to use the 1st month activation rate (i.e. 45%) for the first month of the cohort (Jan'22 for the Jan'22 cohort), the second activation rate (25%) for the second month of that cohort (Feb'22 for the Jan'22 cohort), and so on.
> **Note:** **Deeper dive on t-cohort:**
>
> Let's consider the Feb '22 cohort, in March '22, in a model that begins in January '22:
>
> - **cohort** is **0** for Jan '22, **1** for Feb '22, etc.
>
> - **t** is **0** for Jan '22, **1** for Feb '22, **2** for Mar '22 etc.
>
> - For our worked example, **t** is **2** and **cohort** is **1**. **t-cohort** will return **1**, so the 2nd month activation rate (**25%**) is applied. This is correct as Mar'22 is the 2nd month of my Feb'22 cohort.
>
> - If the month was instead Feb '22, then **t-cohort** would be **0 (1-1)** corresponding to the 1st month activation rate of **45%**
>
> Note: **t** is a [helper variable](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) (also known as timestep or date).
### Importing Cohort Data in Lucanet xP&A
You can connect your historic cohort data to xP&A via:
- A **spreadsheet**. If you go the spreadsheet route, there are two formats that are compatible with xP&A: **Time-Series** format and **Transactions** format. For both, an example can be found below.
- [Directly from your data warehouse](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md)
The one rule that must be satisfied is that the dates in the **Cohort** column must fall between the range of the **Date** column.
### Time-Series Format in Lucanet xP&A
This is an example of a **Time-series** format spreadsheet for cohorts:
Time series
> **Note:** [Click here to see a Google Sheets template in the time-series format](https://docs.google.com/spreadsheets/d/1mnuElYW-T-3f22q1FEL3kQiXbf5SsWuuSehtEy2R5W4/edit?usp=sharing)
- Each row represents a single variable for a single dimension item.
- The columns can be split into 3 section: **Variable Names**, **Dimensions**, and **Values**
- The **first section** is just the first column:
- It must contain the **Variable Names**.
- In the example above, **column A** contains the variable **Total Billed**. In this case, it was the only variable.
- The **second section** proceeds the first column:
- It contains the **Dimensions.**
- The first row must have the **name of the dimension** and the rows below may have the **name of an item** in that dimension.
- In the example above, **column B** contains the **Cohort** dimension. In this case, it was the only dimension. The cohort names (e.g. **August 2018**) must be formatted as **Dates** to be recognized by xP&A.
- The **third section** follows after all of the columns involved in the second section:
- It contains the **Values.**
- The first row must contain the **dates**, and the rows below are the **values** themselves (must be number format, not text)
- In the example of above, this section ranges from **column C** to **column G.**
### Transactions Format in Lucanet xP&A
Transactions
> **Note:** [Click here to see a Google Sheets template in the transaction format](https://docs.google.com/spreadsheets/d/1VWW6A69o2PjaXOBm2mnFWzLrWfBwQrhJ4-hseIkrc_0/edit#gid=0)
This is an example of a **Transactions** format spreadsheet for cohorts:
- The **first column** must have the name **Date**.
- Simply add a column with the name **Cohort**. As above, the cohort names must be formatted as **Dates** to be recognized by xP&A.
- The other columns can be for additional dimensions and/or data items.
### SaaS Metrics in Lucanet xP&A
Here are some common SaaS metrics you might want to track, and how to build them in xP&A:
### Customer Acquisition Cost (CAC) in Lucanet xP&A
**Customer Acquisition Cost** calculates how much it costs to acquire a **Customer** in the period. Calculated using direct **Marketing Spend** and **Sales/Marketing Staff Costs** in the appropriate period.
For example, let’s say there’s $1m **Marketing Spend** in Jan 22 and then $2m in Feb 22 and Mar 22. **Marketing Spend** takes 2 months to flow down the funnel and convert to **Customers**. In Mar 22, there are 4 new customers, therefore CAC in Mar 22 should be $1m/4 = $250k rather than using the **Marketing Spend** in Mar 22, which would result in $2m/4 = $500k, as this is not the relevant amount which determines the **New Customers** gained in the period.
xP&A’s [Time Modifiers](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) make implementing this logic very easy! If we use the same logic as above in regards to **Payroll Cost** for **Sales** and **Marketing Staff**, we can produce a formula like the image below. The formula takes **Payroll Costs for the Sales and Marketing Department** modified by the amount of **Time** spent in the funnel. This is then divided by the the **New Customers** in the **Period** to arrive at the CAC.
Customer Acquisition Cost (CAC)
### CAC Payback in Lucanet xP&A
**Customer Acquisition Payback** calculates the number of periods required for a **Customer** to produce enough **Gross Profit** to pay back their respective CAC. The shorter the Payback Period the better your business is performing.
Therefore, once you have calculated **CAC**(see above) you can calculate your payback by finding your **ARPU (Average Revenue per Account)** and multiplying this by your **Gross Profit Margin** to find the contribution per **Customer**. Taking CAC and dividing by this **Contribution**, calculates how many periods are required for the customer to payback their CAC.
### ACV/CAC in Lucanet xP&A
**Annual Contract Value/Customer Acquisition Cost** gives indication of profitability on new contracts. After calculating CAC (see above), take the **Annual Contract Value** in the period and divide by **CAC** in the period to produce this metric.
### Magic Number in Lucanet xP&A
The **Magic Number** metric is designed to measure how efficient and effective your **Sales** and **Marketing** spend are in a specific time **period**.
It is calculated by taking **Net New ARR** or **New ARR + Expansion ARR - Churned ARR** and dividing it by **CAC**.
The following general advice is given depending on your Magic Number:
- **Magic Number < 0.5**: A magic number this low indicates that something is wrong with your business model. Whether it be high costs relative to performance or perhaps you have not achieved product-market fit. This is not the time to invest in Sales and Marketing, focus should be elsewhere.
- **0.5 < Magic Number < 0.75**: This is generally considered to be the main threshold for the magic number. If you’re around the 0.75 mark then your sales efficiency is approaching market norms. This is a time to evaluate whether or not to increase Sales and Marketing expense and depends on the specific context of your business.
- **Magic Number > 0.75**: A magic number over 0.75 indicates that this is the time to invest in Sales and Marketing. You likely have a proven product-market fit and solid CAC payback periods and this is the time to take advantage.
### Lifetime Value in Lucanet xP&A
**Lifetime Value** is a metric that measures, you guessed it, the **Lifetime Value** of a cohort of **New Customers**. The higher your LTV the better.
You can calculate LTV by taking **(Average Order Size in the Period \* Average # of Orders in the Period \* Contract Length) / Churn Rate**. This gives LTV for an average customer in the cohort.
### Burn Multiple in Lucanet xP&A
**Burn Multiple** calculates how much **Cash** is being used to generate new business and is used as a guide on sustainability of the current business model. The higher the Burn Multiple, the more the start-up is burning to achieve each unit of growth. The lower the Burn Multiple, the more efficient the growth is.
Calculated by taking **-Net Operating Cashflow** divided by **Net New ARR** or (**New ARR + Expansion ARR - Churned ARR**).
The table below gives some context to how your Burn Multiple shapes up:
Burn multiple
### Net Revenue Retention in Lucanet xP&A
**Net Retention Rate** is a core tracked metric for most SaaS businesses. It gives an indication of the impact of **Customer Retention and Upselling** on the business.
Calculated by taking **(Beginning ARR - Churned ARR + Expansion ARR) / Beginning ARR**.
A solid SaaS company would expect to have a Net Retention Rate of at least 100% with anything above 110% considered exceptional.
### Customer Retention in Lucanet xP&A
**Customer Retention** is a key metric for any business and is measured by how many **Customers** at the Start of the Period **remain** at the **End of the Period**.
It is calculated by taking **(Total Customers at End of Period - New Customers in Period) / Customers at the Beginning of Period**.
Of course you cannot retain more than 100% of your customers, the closer you are to 100% the better your business is performing.
### Balance Sheet and Cashflow
### Current Year Earnings in Lucanet xP&A
Current year earnings
### Retained Earnings in Lucanet xP&A
Retained earnings
### Balance/Check in Lucanet xP&A
Balance/Check
### Indirect Cashflow Statement in Lucanet xP&A
For indirect cashflow statements, make sure every balance sheet item is accounted for in the cashflow statement. As a general rule:
- For **Assets**, cash change is **asset item|previous - asset item|current**
- For **Liability and Equity**, cash change is the opposite **(current - previous)**.
The following items assume a connection to a balance sheet:
### Ending Cashflow in Lucanet xP&A
Ending cashflow
### Change in Working Capital in Lucanet xP&A
Change in working capital
> **Note:** If you are looking for more fulsome templates, you can find them [here](https://www.causal.app/templates).
---
---
title: "Comparing Versions or Scenarios in Charts and Tables"
description: "In xP&A, you can easily compare versions or scenarios of your model on charts and tables."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/comparing-versions-or-scenarios-in-charts-and-tables
language: en
last_updated: 2026-05-01
---
# Comparing Versions or Scenarios in Charts and Tables in Lucanet xP&A
## Overview
You often might want to compare different versions and/or scenarios of your model, for example to:
- Learn how your actual performance compares to your budget or forecast ( **Budget vs. Actuals**, **Forecast vs. Actuals**)
- See how different scenarios affect your numbers (**Scenario A vs. Scenario B**)
- Compare how a new scenario stacks up against your original forecast (**Scenario A vs. Current Forecast**)
In Lucanet xP&A (Extended Planning & Analysis), you can easily compare versions or scenarios of your model on **charts** and **tables**.
> **Tip:** **Special Versions**
>
> xP&A auto-creates a few special versions of your model that you can refer to in tables and charts:
>
> - **Current** takes the current values of your model, i.e. it takes data for the months for which historical data are available, and uses the formulas for forecast months. Whenever you create a chart or table, this is always the default.
> - **Actuals** includes all current values in the model up to and including the [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md). If there is no Last Actual Date set, xP&A will return none.
> - **Rolling Forecast** takes the most recent version of each timestep’s value, where that month was still a “forecast” and not an “actual”, according to the [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) when the version was saved.
> - **Data** includes all current values that come from a [data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md).
## Comparing Versions or Scenarios in Charts in xP&A
To compare model versions or scenarios in a chart in xP&A, you have the following options:
### As a Dimension Breakdown
By default, a chart always shows the values of the variables of the currently active scenario and the **base version** as the current version.
To see or compare the values of other scenarios or versions, you can easily switch to other versions or add them for comparison:
1. Click the edit icon in the top-right corner of a chart visual and go to the **Setup** tab.
2. Navigate to the **Dimensions breakdown** section.
By default, the **Active scenario** and the **Current version** are selected.
3. Choose between one of the following options:
- If you want to see the values of another scenario or version only, hover over the selected scenario, open the drop-down menu using the arrow, and choose the desired scenario or version:
Changing a version
- If you want to see the values of another scenario or version additionally to compare them, click the + icon and add the desired scenario or version:
Adding a version
### As a Filter
You can add the versions or scenarios as a filter to your chart to see one scenario or version at a time and view each as an own page:
1. Click the edit icon in the top-right corner of a chart visual and go to the **Setup** tab.
2. Navigate to the **Filters and controls** section and click the **+** sign.
3. Choose **Scenarios** and/or **Versions**, depending on what you want to set a filter for:
Adding versions or scenarios as a filter
4. The respective filter appears as a drop-down list on the top left of the chart visual:
Filters added to a chart
## Comparing Versions or Scenarios in Tables in xP&A
To compare model versions or scenarios in a table in xP&A, you have the following options:
### As a Row or Column
You can add the versions or scenarios as a row or column to view them side-by-side:
1. Click the edit icon in the top-right corner of a table visual and go to the **Setup** tab.
2. Navigate to the **Columns** or **Rows** section and click the **+** sign.
3. Choose **Scenarios** or **Versions**, depending on what you want to compare:
Adding versions or scenarios as a column
4. Click on the **Scenarios** or **Versions** item that you just added to the **Columns** or **Rows** section. In the menu that is displayed, add the **additional scenario** or **additional version** you want to compare:
Adding the version to be compared
5. Choose if you want to **show the variance** between the compared base and the additional version(s) or scenario(s) in the table.
6. If you show the variance between the compared versions or scenarios, you can additionally decide how you want to show them using the three-dot menu of the additional version or scenario.
You have the following options:
- **Show variance as** a **percentage**, **value** or **both**
- Show variance in a **separate column**
Options for showing variance
### As a Filter
You can add the versions or scenarios as a filter to see one scenario or version at a time and view each as an own page:
1. Click the edit icon in the top-right corner of a table visual and go to the **Setup** tab.
2. Navigate to the **Filters and controls** section and click the **+** sign.
3. Choose **Scenarios** and/or **Versions**, depending on what you want to set a filter for:
Adding versions or scenarios as a filter
4. The respective filter appears as a drop-down list on the top of the table visual:
Filters added to a table
---
---
title: "Comparison: xP&A vs. Excel Performance"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/xpa-vs-excel
language: en
last_updated: 2026-05-01
---
# Comparison: Lucanet xP&A vs. MS Excel Performance
When comparing MS Excel and Lucanet xP&A (Extended Planning & Analysis), **performance differences** become apparent when working with large, complex data models. In an internal test, a large Excel model containing 16,384,000 cells (16,384 columns and 1,000 rows) showed performance constraints under typical usage conditions:
In this test, the Excel file takes approximately 25 seconds to open on high-end hardware (November 2023 Apple M3 Pro with 36 GB RAM). Regular operations within the spreadsheet experience noticeable lag, and saving the file requires about 15 seconds. Additionally, the Excel process consumes approximately 3GB of RAM while in use.
In contrast, Lucanet xP&A is designed to handle significantly larger data volumes efficiently. Lucanet xP&A currently supports hundreds of millions of cells, with future updates expected to expand this capacity further. A **key advantage of Lucanet xP&A** is that calculations are executed on remote servers, making performance largely independent of local machine specifications.
**Note**: These results are based on specific test conditions and may vary depending on the data structure, hardware, and use case.
---
---
title: "Connecting to a BI/Database System"
description: "You can establish a direct data connection to different BI/Database systems to pull in data into xP&A.\n\nThe following applies:\n\nIn order to set up the integration, you must follow individual authentication procedures to link to your system account with xP&A. Detailed set-up instructions are provided for each supported system.\nAll fields (variables and dimensions) that are pulled in need to be defined individually for each BI/Database system using custom queries. For instructions on how to define such queries, see Defining Database Queries.\nFor some systems a connection using an SSH tunnel can be configured."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system
language: en
last_updated: 2026-05-01
---
# Connecting to a BI/Database System in Lucanet xP&A
## Overview
You can establish a direct data connection to different BI/Database systems to pull in data into Lucanet xP&A (Extended Planning & Analysis).
The following applies:
- In order to set up the integration, you must follow individual authentication procedures to link to your system account with xP&A. Detailed set-up instructions are provided for each supported system.
- All fields (variables and dimensions) that are pulled in need to be defined individually for each BI/Database system using custom queries. For instructions on how to define such queries, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- For some systems a connection using an SSH tunnel can be configured.
## Supported BI/Data Warehouse Systems in xP&A
Currently, xP&A supports connections to the following BI/Data Warehouse systems. Click on a system name to open the individual set-up instructions:
- [BigQuery](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-bigquery.md)
- [Databricks](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-databricks.md)
- [Microsoft SQL Server](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mssqlserver.md)
- [MySQL](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mysql.md)
- [Postgres](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-Postgres.md)
- [Redshift](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-redshift.md)
- [Snowflake](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-snowflake.md)
- [Looker](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-looker.md)
---
---
title: "Connecting to a CRM System"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-crm
language: en
last_updated: 2026-05-01
---
# Connecting to a CRM System in Lucanet xP&A
## Overview
You can establish a direct data connection to a CRM system to pull in CRM data into Lucanet xP&A (Extended Planning & Analysis).
The following applies:
- All integrations with CRM systems are established using **Merge**, a third-party platform that enables (API) integrations with different systems.
- In order to set up the integration, you must follow individual authentication procedures to link to your CRM system account with xP&A.
- Independent of the system, there is a set of default fields (variables and dimensions) that are pulled in. In addition, the integration of custom fields can be defined during the configuration of the data connection.
## Supported CRM Systems in xP&A
Currently, Lucanet supports connections with the CRM system **Salesforce.**
A connection to further systems is under development.
## List of Default Fields in xP&A
The following default fields are pulled in from each CRM system that is integrated via **Merge**:
**Variables**
- Activity
- Amount Closed
- Amount Closed Won by Account
- Amount Created
- Opportunities Closed
- Opportunities Created
- Weighted Amount Closed
- Weighted Amount Created
- Weighted Opportunities Closed
- Weighted Opportunities Created
**Dimensions**
- Account
- Activity Type
- Owner
- Owner Role
- Owner Status
- Stage
- Stage Type
> **Note:** You can select additional opportunity filters during the configuration process.
## Prerequisites for the Setup in xP&A
**Necessary Authentications**
You will need to ensure that you set up all necessary **authentications** that are requested in the connection flow.
These authentications differ slightly by CRM system -- [open this link to see a full breakdown](https://help.merge.dev/collections/4202445872-crm) (by our API provider, **Merge**).
## Connecting to a CRM System in xP&A
To connect to a CRM system in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**.
2. In the **Data sources** dialog, open the **CRM** tab and choose the system from which you want to integrate data.
'CRM' tab
3. Choose if you want to:
- Use xP&A's **Sales and Pipeline Report**
- Create the data source **manually** and link the data to your models by yourself (**Advanced**)
4. **Choose a connection** in the **New Data Source** dialog. If you have not configured a connection yet, configure the following steps to set up a connection:
- Choose if you would like to authenticate using **your credentials** or using your **Security Token** **and Organization ID**.
Select the authentication method
- Check the standard fields that can be pulled in with the integration and click **Next** to agree to the [End User Terms](https://www.merge.dev/legal/end-user-terms) of our third-party provider Merge.
Confirm Merge's end user terms
- Select if you want to use your **Production account** or your **Sandbox account**.
Select account type
- **Enter your subdomain** details to connect to the source system and click **Next**.
A detailed description on how to authenticate with each system can be found in [Merge's Help Center](https://help.merge.dev/collections/4202445872-crm).
Enter the subdomain
5. Confirm all following steps to complete the setup of the connection.
6. In the **New Data Source** dialog, select the **opportunity filters** you want to use as breakdowns.
xP&A is pulling your opportunities by owner, stage, and account. If you want to use additional break-downs, you can pick up to three more. Note that a large number of items may result in a slower model.
Select the opportunity filters
---
---
title: "Connecting to a Data Source"
description: "In order to integrate data from a source system into Lucanet xP&A, you need to establish a connection to the respective data source. \n\nThere are two ways of connecting to data sources:\n\nVia the Data workspace\nFrom within a model\n\n\nYou can create various data sources for the same source system integration (e.g. to connect to multiple Google accounts)."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source
language: en
last_updated: 2026-05-01
---
# Connecting to a Data Source in Lucanet xP&A
## Overview
In order to integrate data from a source system into Lucanet xP&A (Extended Planning & Analysis), you need to establish a connection to the respective data source.
xP&A offers integrations with various source systems. The procedures for setting up a connection and to define the data that is pulled in, differ depending on the source system in use. A list of the available source systems and a link to the detailed instructions to connect to them can be found below.
You can create various data sources for the same source system integration (e.g. to connect to multiple Google accounts).
> **Note:** Once a connection to the data source is established, you can:
>
> - [Link variables to integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md)
> - [Drill-down into the underlying details, from any variables connected directly to that data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data.md)
> - [Link dimensions from a data source to dimensions in xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source.md)
> - [Share data sources with other xP&A users](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/sharing-data-connections.md)
>
> How you work with integrated data in variables and formulas, e.g. how to set the currency of integrated data, is described in the sections [Creating and Editing Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md) and [Creating and Editing Formulas.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas.md)
## Available Integrations in xP&A
xP&A offers the following integrations:
| Integration | Available systems |
|---|---|
| **[Spreadsheets](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md)** | • Excel • CSV • Excel Online • Google Sheets |
| **[Accounting Systems](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-accounting-erp.md)** | • Quickbooks • Xero |
| **[BI/Database Systems](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system.md)** | • [BigQuery](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-bigquery.md) • [Databricks](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-databricks.md) • [Microsoft SQL Server](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mssqlserver.md) • [MySQL](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mysql.md) • [Postgres](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-Postgres.md) • [Redshift](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-redshift.md) • [Snowflake](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-snowflake.md) • [Looker](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-looker.md) |
| **[CRM Systems](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-crm.md)** | Salesforce |
| **[HRIS/Payroll Systems](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-payroll-provider.md)** | • Altera Payroll • Bamboo HR • Breathe • Charlie • ChartHop • Deel • Freshteam • Gusto • Hibob • HR Cloud • HR Partner • Humaans • IntelliHR • Justworks • Kallidus • Kallidus (f.k.a. Sapling) • Namely • Nmbrs • Officient • Paychex • Paylocity • PeopleHR • Personio • Proliant • Quickbooks Payroll • SageHR |
| **[Lucanet Consolidation & Financial Planning](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-lucanet-cfp-data-source.md)** | Lucanet CFP Datasource |
| **[Webhook](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-using-webhook.md)** | Webhook |
## Displaying the Data Preview Within a Model in xP&A
Once the data source has been added to the model, it is displayed in the **overview** of the model under **Data**.
You can click the name of the data source to open a section with the **data preview** on the bottom of the model's spreadsheet:
Data preview within a model
## Unlinking or Deleting a Data Source in xP&A
Data sources created by you exist on your xP&A user account. If you unlink a data source from a model, the data source still continues to exist on your account.
**To unlink a data source** from your model, you have the following options:
- In the **spreadsheet** view of a model, go to the **Data** section in the overview, open the three-dot menu of the data source you would like to remove, and click **Remove from model**.
- Go to the **Data** workspace, open the three-dot menu of the data source you would like to remove, and click **Remove**.
Removing a data source from a model
If you want to **permanently delete** a data connection and all its connected data sources from your account, go to the **Data** workspace, open the three-dot menu of the data connection, and click **Delete connection**.
Deleting a data connection
---
---
title: "Connecting to a Lucanet CFP Data Source"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-lucanet-cfp-data-source
language: en
last_updated: 2026-09-17
---
# Connecting to a Lucanet CFP Data Source in Lucanet xP&A
## Overview
You can connect to a Lucanet CFP Data Source to pull in data from Lucanet Consolidation & Financial Planning into Lucanet xP&A (Extended Planning & Analysis).
> **Note:** - A user can only integrate data from CFP if they have a **license** for Consolidation & Financial Planning, and only for the data they have access to in CFP.
> - Access permissions for Consolidation & Financial Planning are configured in the platform administration under user management. To access CFP data, an xP&A user must be assigned the data model role **Editor** or **Observer**. In addition, at least read permissions must be granted for the CFP **workspaces** and **data levels** they should have access to. For more information, see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md) and [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md).
## Connecting to a Lucanet CFP Data Source in xP&A
To connect to a CFP data source in xP&A:
1. Open the **Data** workspace.
2. Choose one of the following options:
- Open the **Data** workspace from the overview on the home page and click **+ New**.
- Open the model you want to integrate data into. In the overview, click the **+** icon next to **Data** and select **New data source**.
3. In the **Data sources** dialog, open the **Accounting** tab and select **Consolidation & Financial Planning**.
The CFP data source is only available to users who have a license for both xP&A and Consolidation & Financial Planning in the CFO Solution Platform.
4. In the **New Lucanet CFP Data Source** dialog, select the **ledger** and the **data level** from Lucanet Consolidation & Financial Planning from which you would like to transfer data, and specify the **display currency** and the **date range** for the data source:
Select ledger
5. Click **Next**. The **Filter data** step is displayed as follows:
Filter data
6. Choose the method for importing organization elements. The following options are available:
- **Single hierarchies**, to import reporting entities and cost centers as a single hierarchical dimension.
This is the **recommended** option to import organization elements.
- **Multiple flat dimensions**, to import reporting entities and cost centers as 2 independent flat dimensions.
This is the **deprecated** option to import organization elements. It still works but won't get any improvements in the future. We strongly recommend the **Single hierarchies** method.
7. Choose the **organization element** and the **adjustment level**, and optionally the **partner(s)** and **transaction type(s)**, which you would like to transfer with this data source from Lucanet Consolidation & Financial Planning.
8. Click **Create data source**.
---
---
title: "Connecting to a Lucanet CFP Data Source"
description: "You can connect to a Lucanet CFP Data Source to pull in data from Lucanet Consolidation & Financial Planning into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/connecting-to-cfp-copy
language: en
last_updated: 2026-09-17
---
# Connecting to a Lucanet CFP Data Source in Lucanet xP&A
## Overview
You can establish a connection to Lucanet Consolidation & Financial Planning (CFP) to pull in data into Lucanet xP&A (Extended Planning & Analysis).
> **Note:** - A user can only integrate data from CFP if they have a **license** for Consolidation & Financial Planning, and only for the data they have access to in CFP.
> - Access permissions for Consolidation & Financial Planning are configured in the platform administration under user management. To access CFP data, an xP&A user must be assigned the data model role **Editor** or **Observer**. In addition, at least read permissions must be granted for the CFP **workspaces** and **data levels** they should have access to. For more information, see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md) and [Defining Permissions for CFP Data Model Roles](https://support.lucanet.com/en/documentation/administration/user-management/users/defining-user-permissions.md).
## Connecting to a Lucanet CFP Data Source in xP&A
To connect to a CFP data source in xP&A:
1. Open the **Data** workspace.
2. Choose one of the following options:
- Open the **Data** workspace from the overview on the home page and click **+ New**.
- Open the model you want to integrate data into. In the overview, click the **+** icon next to **Data** and select **New data source**.
3. In the **Data sources** dialog, open the **Accounting** tab and select **Consolidation & Financial Planning**.
The CFP data source is only available to users who have a license for both xP&A and Consolidation & Financial Planning in the CFO Solution Platform.
4. In the **New Lucanet CFP Data Source** dialog, select the **ledger** and the **data level** from Lucanet Consolidation & Financial Planning from which you would like to transfer data, and specify the **display currency** and the **date range** for the data source:
Select ledger
5. Click **Next**. The **Filter data** step is displayed as follows:
Filter data
6. Choose the method for importing organization elements. The following options are available:
- **Single hierarchies**, to import reporting entities and cost centers as a single hierarchical dimension.
This is the **recommended** option to import organization elements.
- **Multiple flat dimensions**, to import reporting entities and cost centers as 2 independent flat dimensions.
This is the **deprecated** option to import organization elements. It still works but won't get any improvements in the future. We strongly recommend the **Single hierarchies** method.
7. Choose the **organization element** and the **adjustment level**, and optionally the **partner(s)** and **transaction type(s)**, which you would like to transfer with this data source from Lucanet Consolidation & Financial Planning.
8. Click **Create data source**.
---
---
title: "Connecting to a Source System Using a Webhook"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-using-webhook
language: en
last_updated: 2026-05-01
---
# Connecting to a Source System Using a Webhook in Lucanet xP&A
## Overview
This instruction explains how to set up a data source in Lucanet xP&A (Extended Planning & Analysis) to receive data from external source systems using a **webhook**.
A webhook is an automated way for one application to send data to another application in real time. i. e. once new data is available in the source system (e.g. [Looker](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-looker.md)), the webhook automatically delivers that data to xP&A.
Unlike manual data imports where you download and upload files yourself, webhooks work automatically in the background once configured.
Connecting to a data source using a webhook entails the following steps, which are described in the following:
1. Creating a Webhook data source in xP&A
2. Configuring your source system to send data to xP&A
3. Sending or refreshing data
Optionally, you can configure dimension mappings.
## Definitions
The following concepts play a role when using a webhook connection:
| Option | Description |
|---------|---------|
| Webhook | An automated connection that sends data from one system to another when triggered. In this case, the trigger is new data being available. |
| Webhook URL | A unique web address generated by xP&A. External systems send data to this address (using an **HTTP Post** request) and xP&A requests the data from this address as soon as new data is available. Each webhook data source has its own URL. |
| JSON | A standardized data format that systems use to exchange information. You do not need to create JSON files manually—your source system (e.g., Looker) generates them automatically and sends them to the Webhook URL. |
| Key | A label that identifies a specific piece of data (e. g. "Country" or "Customer"). Keys help xP&A understand what each value in your data represents. |
## Prerequisites
Before you begin, make sure you have:
- Access to your xP&A account with permissions to create data sources
- Access to the external system that will send data
- Knowledge of the data structure you want to import (column names, data types)
## Creating a Webhook Data Source in xP&A
To create a webhook data source in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **Other** tab and choose **Webhook.**
Creating a new Webhook data source
3. The **New Data Source** dialog is displayed as follows:
The 'New Data Source' dialog for Webhook
4. Configure the fields as described in the following section.
5. Click **Create webhook data source**.
The created Webhook URL will be displayed in the dialog.
6. Copy the Webhook URL and proceed with the step [Configuring Your Source System to Send Data to xP&A](#configuring-your-source-system-to-send-data-to-xpa).
> **Warning:** Treat the Webhook URL and its token part with caution: Anyone can post updates to the created data source using this token.
### Fields
Configure the following fields in the **New Data Source** dialog for a Webhook. The keys identify the data that are pulled in from the data source.
| Fields | Description |
|--------|-------------|
| Data Source Name | Name of the data source. |
| Data array key | The key under which your data records are stored in the JSON. For Looker, this is always **data**. **Example:** data |
| Date key | The name of the column that contains dates. Values must be strings that can be parsed as dates. Specifies which field in each data entry contains the timestamp for the entire entry. The date key tells xP&A which field in your Webhook JSON represents when the data entry occurred. This date is used to place all the numeric variables from that entry at the correct point in time in your model. **Example:** Posting date |
| Cohort key | The name of the column that contains cohort information. Leave empty if not applicable. Values must be strings that can be parsed as dates. |
| Keys of variables | The names of the columns that contain numeric values. Press **Enter** after each name to add multiple variables. Values must be numbers. Missing keys will be treated as zeros. **Example:** Customers |
| Keys of date variables | Specifies which fields in each entry are date-type variables (the value itself IS a date). Keys of date variables are used when you have variables whose values are dates - not numbers. These become date-formatted variables in your model. |
| Keys of dimensions | The names of the columns that contain dimensions. Press **Enter** after each name to add multiple variables. Values must be strings. **Example:** Country |
## Configuring Your Source System to Send Data to xP&A
After you have copied the Webhook URL from the data source set-up page in xP&A, you need to configure your source system to send the data to the Webhook URL.
The procedure for this set-up depends on your source system. In the following, we describe the set-up steps for the source system **Looker**.
### Example: Configuring Looker
To set-up a Webhook connection in **Looker**, proceed as follows:
1. In Looker, open the **Look** or **Dashboard** you want to send to xP&A.
2. Set up a **scheduled delivery**.
3. Select **Webhook** as the delivery destination.
4. Paste the Webhook URL from xP&A into the destination field.
5. Save and activate the schedule.
For detailed Looker configuration, see [Looker](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-looker.md).
## Sending or Refreshing Data in xP&A
After configuring your source system, trigger a data transmission from your source system (or wait for the scheduled transmission, in case you configured one.)
After that, go to the **Data** workspace in xP&A and [refresh](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md) your **Webhook** data source.
> **Warning:** Each time new data is sent to the Webhook URL, it overwrites the previous data. Therefore, make sure your source system sends complete datasets.
## Configure Dimension Mappings in xP&A
Just like spreadsheet data sources (e.g. [time series with dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md)), you can also use dimension mappings for webhook data sources. For example, if you have an **Employee** dimension and every employee belongs to a **Department**.
For more information, see [Linking Dimensions from a Data Source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source.md#linking-dimensions-from-a-data-source).
## Troubleshooting
### Data does not appear in xP&A
In case data does not appear in xP&A, verify that the Webhook URL is correct in your source system. Check if the data was sent successfully by reviewing the source system's logs.
### Incorrect data structure
In case of incorrect data structure, click **Edit** on your **Webhook** data source, then click **View last uploaded data** to see the raw JSON format. Verify that your keys match the actual data structure.
### Missing values
If values are missing, ensure all required keys (Date key, Variable keys) are configured correctly and match the column names in your source data exactly.
---
---
title: "Connecting to a Spreadsheet"
description: "In xP&A, you can connect to the following spreadsheet file formats: Google Sheets, Excel Online, Excel Upload, CSV Upload\nThe following three data formats for spreadsheet files are supported: Tables, Transactions, Time-series\nEach connected file needs to be formatted in a certain way so that the data can be imported into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet
language: en
last_updated: 2026-05-01
---
# Connecting to a Spreadsheet in Lucanet xP&A
## Overview
In Lucanet xP&A (Extended Planning & Analysis), you can connect to the following spreadsheet **file formats**:
- Google Sheets
- Excel Online
- Excel Upload
- CSV Upload
**Google Sheets** and **Excel Online** are **synchronized**, i.e. you can refresh the data source and the latest data will be imported automatically, whereas data integrated via **CSV Upload** and **Excel Upload** need to be **updated manually**.
The following three **data formats** for spreadsheet files are supported:
- Tables
- Transactions
- Time-series
Each connected file needs to be **formatted** in a certain way so that the data can be imported into xP&A.
We also provide various templates for the different file and data formats, helping you to set up the files much easier.
## Prerequisites
### Formatting a Spreadsheet for Integration
In order to pull in data from a spreadsheet into xP&A, the spreadsheet needs to have a certain format. The format requirements depend on the type of data you want to connect.
### Table
The table format is useful where your values do not vary over time, i.e. it is more of a static database of information.
A table must structured as follows to import its data into xP&A:
- The **first row** represents the **dimension name** or **variable name.**
- **Every subsequent row** (below the top row) represent a single **dimension item.**
- The **first column** must contain the **primary dimension**.
- Additional columns can contain:
- **Mapped dimensions**:
In case of mapped dimensions, the first row must have the name of the dimension being mapped from and the name of the dimension being mapped to, in the following format: \[from dimension\] > \[to dimension\]. Each subsequent row contains the "mapped" dimension
**Note**: (The arrow (">") is important because it is used by xP&A to distinguish between a normal dimension column, and a mapped dimension column! This is equivalent to [linking dimensions in xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source.md), except that you cannot modify the link from within xP&A in this case.)
- **Unmapped dimensions**:
The first row must contain the name of the dimension and all subsequent other row contains a dimension item.
**Note**: It is rare that you will use unmapped or nested dimensions in the table format.
- **Variables**:
The first row must contain the name of the variable and all subsequent rows will contain the values, whether it's a date or a number, for the associated dimension item.
**Note**: You must not include a > in a variable column.
**Example**
Example of a table
### Transactions
The transactions format is useful where your data varies over time, and you track it on a granular basis.
xP&A allows two types of transactions format to be imported:
**Standard format**
The standard format for transaction data allows you to pull in data on a transaction-by-transaction basis into xP&A. This is useful for values that are recorded on a per-day, per-week, or per-event basis, like **Sales by Customer**.
The standard format rules are:
- The **first column** must have the name **Date.**
- **Subsequent columns** can be **values**(such as variables or [Data Items](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md)) or **dimensions**, with a freely-definable name.
**Note**: You can add \[dimension\] or \[variable\] to a column name to ensure that the system recognizes the column correctly.
- You can also add **dimension mappings**. In this case, the column name must have the name of the dimension being mapped from and the name of the dimension being mapped to, in the following format: \[from dimension\] > \[to dimension\].
- You can also add a **Cohort** column to integrate cohorts.
**Example**
Example of transactions (standard format)
**Alternative format**
If your data source has [Data Items](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) coming through in rows rather than columns then you can use the **Alternative format** for data ingestion.
The alternative format rules are:
- The **first column** must have the name **Date**.
- The **second column** must have the name **Type** and contain the [Data Item](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) or variable names.
- The **third column** must have the name **Value** and contain the respective values.
**Example**
Example of transactions (alternative format)
### Time-series
The time-series format is useful where your data varies over time (e.g. by month).
xP&A allows three types of time-series format to be imported:
**Basic time-series**
The basic time-series rules are:
- The **first row** must have **dates** for each value.
- The **first column** must have the **names of each variable.**
- Each subsequent row represents a single variable.
**Example**
Example of basic time-series
**Time-series with dimensions**
With this type, you can include several dimensions.
The rules for time-series with dimensions are:
- Each row represents a single variable, for a single dimension item.
- The columns can be split into four sections:
1. The first column must have the **variables' names**.
2. The next columns represent the **dimensions**:
- The first row of this section must have the name of the dimension.
- The rows below may have the name of an item in that dimension.
3. The last columns represent the **values**:
- The first row of this section must have dates.
- The rows below contain the values themselves — which should be numbers (not text).
> **Tip:** If a variable has more than one dimension, you can create a row for each possible iteration. For example, if Website Revenue was tracked by both Product and Geography, you would have 12 rows for Website Revenue (3 Products x 4 Geographies).
**Example**
Example of time-series with dimensions
**Time-series with linked dimensions**
With this type, you can include dimensions and mappings (i.e. links between dimensions and dimension items). You can include several dimensions and several mappings at the same time.
If you set up the mappings in your [data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md), xP&A will automatically know how to slice and dice your variables.
The rules for time-series with linked dimensions are:
- Each row represents a single variable, for a single dimension item.
- The columns can be split into four sections:
1. The **first column** must have the variables' names.
2. The next columns represent the **dimensions**:
- The first row of this section must have the name of the dimension.
- The rows below may have the name of an item in that dimension.
3. The next columns hold the **dimension mappings**:
- The first row must have the name of the dimension being mapped from and the name of the dimension being mapped to, in the following format: **\[from dimension\] > \[to dimension\]**.
- The rows below may have the name of an item in the dimension being mapped to.
4. The last columns represent the **values**:
- The first row of this section must have **dates**.
- The rows below contain the **values** themselves — which should be numbers (not text).
**Example**
Example of time-series with mapped dimensions
## Connecting to a Spreadsheet in xP&A
To connect to a Spreadsheet in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **Spreadsheets** tab and choose the system from which you want to integrate data.
Spreadsheets tab
3. Configure the steps as described in the following section, depending on the selected source system.
### Excel Upload and CSV Upload
For **Excel Upload and CSV Upload** configure the following steps in the **New Data Source** dialog in xP&A:
| Step | Description |
|---------|---------|
| Upload file | Drag & drop or browse for the file you would like to connect. |
| Headers | **Worksheet**: Select the worksheet you would like to pull the data from. **Headers**: In the file preview on the right, select the row representing the column headers of your dataset. |
| Format | Select the **format** of your data set and click **Apply** to see a preview of the formatted data. |
| Dimensions | Assign the dimensions of your data sources to the dimensions in xP&A in order to use them in xP&A. |
### Excel Online
For **Excel Online** configure the following steps in the **New Data Source** dialog in xP&A:
| Step | Description |
|---------|---------|
| Connection | **Choose a connection**: Authenticate with your Excel Online account or choose an already existing connection with Excel Online. If you encounter issues with the authentication, you need to **Select your file**: Select the file which you would like to connect. **Select a worksheet from your file**: Select the worksheet from which you would like to pull in the data. |
| Headers | **Headers**: In the file preview on the right, select the row representing the column headers of your dataset. You can click **Refresh data** to synchronize the file and get the latest data of your selected file. |
| Format | Select the **format** of your data set and click **Apply** to see a preview of the formatted data. |
| Dimensions | Assign the dimensions of your data sources to the dimensions in xP&A in order to use them in xP&A. |
### Google Sheets
For **Google Sheets** configure the following steps in the **New Data Source** dialog in xP&A:
| Step | Description |
|---------|---------|
| Connection | **Choose a connection**: Authenticate with your Google Sheets account or choose an existing connection with Google Sheets. **Select your file**: Select the sheet which you would like to connect. **Paste URL**: Alternatively, you can paste the URL of the sheet which you would like to connect. **Select a worksheet from your file**: Select the worksheet from which you would like to pull in the data. |
| Headers | **Headers**: In the file preview on the right, select the row representing the column headers of your dataset. You can click **Refresh data** to synchronize the file and get the latest data of your selected file. |
| Format | Select the **format** of your data set and click **Apply** to see a preview of the formatted data. |
| Dimensions | Assign the dimensions of your data sources to the dimensions in xP&A in order to use them in xP&A. |
## Spreadsheet Templates in xP&A
In order to set up your spreadsheets according to the requirements for xP&A more efficiently, you can use the following templates for Google Sheets and/or MS Excel:
| Template/Use case | Link to template and example |
|---------|---------|
| Basic headcount list | [Basic headcount list - Google Sheets Template](https://docs.google.com/spreadsheets/d/1eYetjA87sKSAg7B0z2-Hc48sVRnvnGVTDpUJ3clG1vs/edit?usp=sharing) |
| Payroll actuals by month (time-series) | [Payroll actuals by month (time-series) - Excel Template](https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fstorage.googleapis.com%2Fcausal-public-assets%2Ftemplates%2FTime-series.xlsx&wdOrigin=BROWSELINK) |
| Time-series cohorts | [Time-series cohorts - Google Sheets Template](https://docs.google.com/spreadsheets/d/1mnuElYW-T-3f22q1FEL3kQiXbf5SsWuuSehtEy2R5W4/edit?usp=sharing) |
| Transaction format cohorts | [Transaction format cohorts - Google Sheets Template](https://docs.google.com/spreadsheets/d/1VWW6A69o2PjaXOBm2mnFWzLrWfBwQrhJ4-hseIkrc_0/edit?usp=sharing) [Transaction format - Excel Template](https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fstorage.googleapis.com%2Fcausal-public-assets%2Ftemplates%2FTransaction.xlsx&wdOrigin=BROWSELINK) |
| Basic time-series | [Basic time-serie - Google Sheets Template](https://docs.google.com/spreadsheets/d/1QBnKAbLC__XTLMlspAtOgxw-_PyhY2z0bsLj8rEi_R4/edit?usp=sharing) |
| Time-series with two dimensions | [Time-series with two dimensions - Google Sheets Template](https://docs.google.com/spreadsheets/d/1QBnKAbLC__XTLMlspAtOgxw-_PyhY2z0bsLj8rEi_R4/edit#gid=0) |
## Importing Dimensions From a Spreadsheet in xP&A
When you import a dimension from a spreadsheet (CSV, Excel, or Google Sheets), you can define the hierarchy directly in the cells of the spreadsheet using the **>** separator. xP&A reads the hierarchy path, creates each dimension item at the correct level, and links it to its parent item automatically - there is no need to rebuild the hierarchy by drag-and-drop after the import.
This is the recommended approach when you are setting up a dimension with a large number of dimension items.
**Example**
Dimension hierarchy in the spreadsheet using the **>** separator:
Dimension hierarchy in the spreadsheet
After the import, the dimension appears in the hierarchy in xP&A with the same structure you would get from organizing the dimension items manually:
Dimension hierarchy in xP&A after import
For more information on this topic, see [Creating and Editing Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md#importing-dimensions-from-a-spreadsheet).
## Troubleshooting for Authentication with Excel Online or Google Sheets in xP&A
In case you encounter problems when authenticating to your **Excel Online** or **Google Sheets** account, you first need to grant access permissions to xP&A.
Please note that an **Administrator** role is required for each system to configure the permissions.
**Excel Online**
If you receive the error **Access Denied** or **Need admin approval** when connecting to Excel Online, please send the following troubleshooting guide to your IT Administrator:
1. Sign in to the **Microsoft Entra admin center** as a **Cloud Application Administrator** or **Global Administrator**.
2. Navigate to **Identity** | **Applications** | **Enterprise applications**.
3. In the search box, type **Causal**.
**Note**: The app might also be called **Lucanet xP&A**. If neither name appears in the search results, it means the app has not been “provisioned” yet. Ask one of the xP&A users to attempt to create an Excel Online connection again. When they get the **Need admin approval** error, the app will be created in your directory, and you will be able to find it.
4. Click **Causal** (or **Lucanet xP&A**) in the list to open the application overview.
5. In the left sidebar, under **Security**, select **Permissions**.
6. Click **Grant admin consent for \[ _Your Organization_\]** and accept the permissions ( **files.read.all** and **sites.read.all**) in the displayed dialog.
7. Once granted, the permissions list will show **Granted for \[ _Your Organization_\]** in the status column.
Users can now create Excel Online connections in xP&A.
For more information, you can also consult the Microsoft documentation: [Grant tenant-wide admin consent to an application](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivots=portal).
**Google Sheets**
For Google Sheets, you can find the instructions to configure permissions for xP&A to access data here: [Control which apps access Google Workspace data](https://support.google.com/a/answer/7281227?hl=en#zippy=%2Cinternal-apps).
---
---
title: "Connecting to an Accounting System"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-accounting-erp
language: en
last_updated: 2026-05-01
---
# Connecting to an Accounting System in Lucanet xP&A
## Overview
You can establish a direct data connection to an accounting system to pull in accounting data into Lucanet xP&A (Extended Planning & Analysis).
The following applies:
- All integrations with accounting systems are established using **Merge**, a third-party platform that enables (API) integrations with different systems.
- In order to set up the integration, you must follow individual authentication procedures to link to your accounting system account with xP&A.
- Independent of the system, there is a set of default fields (variables and dimensions) that are pulled in.
## Supported Accounting Systems in xP&A
Currently, xP&A supports connections to the following accounting systems:
- **QuickBooks**
- **Xero**
## List of Default Fields in xP&A
The following default fields are pulled in from each accounting system that is integrated via Merge. They can be selected during the configuration process:
- **Variables**: One variable per GL Account
- **Dimensions**: Two tracking dimensions
## Prerequisites for the Setup in xP&A
**Necessary Authentications**
You will need to ensure that you set up all necessary **authentications** that are requested in the connection flow.
These authentications differ slightly by accounting system -- [open this link to see a full breakdown](https://help.merge.dev/collections/8712682978-accounting-1) (by our API provider, **Merge**).
## Connecting to an Accounting System in xP&A
To connect to an accounting system in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**.
2. In the **Data sources** dialog, open the **Accounting** tab and choose the system from which you want to integrate data.
'Accounting' tab
3. Choose if you want to:
- Use xP&A's **P&L and Runway report**
- Use xP&A's **Full P&L and balance sheet report**
- Create the data source **manually** and link the data to your models by yourself (**Advanced**)
4. Configure the steps of the **New Data Source** dialog as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The **New Data Source** dialog is displayed as follows, for example:
'New Data Source' dialog
1. **Choose a connection**
If you have not configured a connection yet, click **New Connection** and follow the steps in the connection set-up dialog, which depend on the selected system.
A detailed description on how to authenticate with each system can be found in [Merge's Help Center](https://help.merge.dev/collections/8712682978-accounting-1).
2. **Select a dataset**
Select the data set you would like to connect. The following options are available:
- **Profit and Loss**
- **Balance Sheet**
3. **Select an accounting method**
Select the accounting method to be used when generating the report. The following options are available:
- **Accrual**
- **Cash**
4. **Advanced configuration**
Select if you want to **pull classes and/or departments** or if you want to **pull vendors and customers**.
> **Note:** - Pulling in **vendors and customers** allows you to pull in departments, classes, vendors, customers, etc. as dimensions in xP&A, enabling you to model at a more granular level.
> - Even if you do not select this option, you will still be able to [drill down](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data.md) to see actuals at this level of detail.
> - Only select the dimensions you actually need, as refreshing the data source will take significantly longer if you have many tracking dimension items.
---
---
title: "Connecting to an HRIS/Payroll System"
description: "You can establish a direct data connection to various HRIS/Payroll systems to pull in payroll data into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-payroll-provider
language: en
last_updated: 2026-05-01
---
# Connecting to an HRIS/Payroll System in Lucanet xP&A
## Overview
You can establish a direct data connection to various HRIS/Payroll systems to pull in payroll data into Lucanet xP&A (Extended Planning & Analysis).
The following applies:
- All integrations with HRIS/Payroll systems are established using **Merge**, a third-party platform that enables (API) integrations with different systems.
- In order to set up the integration, you must fulfil individual permission requirements and follow authentication procedures to link to your HRIS account with xP&A.
- Independent of the system, there is a set of default fields, i.e. variables and dimensions that are pulled in. Integrating these default field does not require any technical support but can be set up by the customer.
> **Note:** All other fields that you would like to import from your HRIS/Payroll system need to be configured separately. Please reach out to your contact person at Lucanet for further assistance and ensure to have all necessary permissions to access your HRIS/payroll system for this individual setup process.
>
> Please note that we cannot guarantee to be able to pull in all required fields. This will be evaluated during the individual set up process together with our technical experts.
## Supported HRIS/Payroll Systems in xP&A
Currently, xP&A supports integrations with the following HRIS/Payroll systems:
- Altera Payroll
- Bamboo HR
- Breathe
- Charlie
- ChartHop
- Deel
- Freshteam
- Gusto
- Hibob
- HR Cloud
- HR Partner
- Humaans
- IntelliHR
- Justworks
- Kallidus
- Kallidus (f.k.a. Sapling)
- Namely
- Nmbrs
- Officient
- Paychex
- Paylocity
- PeopleHR
- Personio
- Proliant
- Quickbooks Payroll
- SageHR
## List of Default Fields in xP&A
The following default fields are pulled in from each HRIS/Payroll system that is integrated via Merge:
**Variables**
- Start Date
- Start Date (day)
- Latest Annual Salary
- Latest Monthly Salary
- Monthly Salary (timeseries)
- Annual Salary (timeseries)
- Headcount
- End Date
- End Date (day)
**Dimensions**
- Country
- Currency
- Employee
- Employee ID
- Employment Type
- Group
- Location
- Pay Group
- State
- Status
- Team
- Title
> **Note:** **Note on Additional Fields**
>
> Apart from the default fields, every field that you would like to import from your HRIS system needs to be configured separately. Please contact our Support for further assistance and ensure to have all necessary permissions to access your payroll provider.
>
> Please note that we cannot guarantee to pull in all required fields. This will be evaluated during the individually set up process together with our Support.
## Prerequisites for the Setup in xP&A
**Sufficient Permissions**
For setting up the connection, you need to be an **Admin** of your HRIS/payroll system in order to enable xP&A to get the standard information like Salary, Employee Names etc.
If you are not an admin, you can either:
- Enter an admins' credentials in the data connection creation flow in xP&A.
- If your admin has an xP&A account, they can create the data source themselves from scratch, with their own credentials.
**Necessary Authentications**
You will also need to ensure that you set up all necessary **authentications** that are requested in the connection flow.
These authentications differ slightly by HRIS - [open this link to see a full explanation](https://help.merge.dev/en/collections/4258188-hris) (provided by our API provider, Merge).
## Connecting to an HRIS/Payroll System in xP&A
To connect to a payroll provider in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**.
2. In the **Data sources** dialog, open the **Payroll** tab and choose the system from which you want to integrate data.
'Payroll' tab
3. Choose if you want to:
- Connect via xP&A's **Headcount Plan wizard** and get a Headcount model directly connected to your payroll provider.
- Create the data source **manually** and link the data to your models by yourself.
4. Configure the following steps of the **New Data Source** dialog. (As an example, the steps for the source system HiBob are displayed):
- Confirm that you are an admin or copy the displayed URL to share it with your admin and direct them to the next step.
Confirm admin role
- Check the standard fields that can be pulled in with the integration and click **Next** to agree to the [End User Terms](https://www.merge.dev/legal/end-user-terms) of our third-party provider Merge.
Confirm Merge's end user terms
- Enter the authentication details to connect to the source system and click **Next**.
A detailed description on how to authenticate with each system can be found in [Merge's Help Center](https://help.merge.dev/collections/8711975283-hris).
Enter account information
5. Configure all following steps to complete the setup of the connection.
> **Note:** The steps that are required for setting up the connection differ depending on the chosen source system. An instruction for each step is given directly in the set-up dialog.
## Connecting to a Payroll System Using the Headcount Plan Wizard in xP&A
We recommend connecting via xP&A's **Headcount plan wizard** as this way you will get a **headcount model** directly connected to your payroll provider.
To do so, [create a new model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md) and choose the **Headcount plan** wizard in the **Create model** dialog.
## Connecting to Payroll Data via a Google Sheet in xP&A
If you cannot connect directly to your payroll provider, you can also connect xP&A to a Google Sheet with your payroll information.
**Template**
You can use the following template: [Headcount Model Data - Google Sheets](https://docs.google.com/spreadsheets/d/1eYetjA87sKSAg7B0z2-Hc48sVRnvnGVTDpUJ3clG1vs/edit?gid=0#gid=0).
The first tab is a list of your employees and their relevant [dimension mappings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md) (to titles/departments etc), start/end dates, and their latest annual salary. Only use the second tab of the template if you want to include month-by-month payroll actuals by employee.
**Instruction**
For a detailed instruction on how to connect to a Google Sheet, see [Connecting to a Spreadsheet](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md).
---
---
title: "Connecting to BigQuery"
description: "In xP&A, you can connect to the following spreadsheet file formats: Google Sheets, Excel Online, Excel Upload, CSV Upload\nThe following three data formats for spreadsheet files are supported: Tables, Transactions, Time-series\nEach connected file needs to be formatted in a certain way so that the data can be imported into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-bigquery
language: en
last_updated: 2026-05-01
---
# Connecting to BigQuery in Lucanet xP&A
## Overview
You can establish a direct connection to BigQuery to pull in data into Lucanet xP&A (Extended Planning & Analysis).
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Limits for Data Imported from BigQuery in xP&A
In order to prevent the accidental import of large amounts of data, there is a limit on the number of rows (150,000) and the number of items (100) you can have in a dimension when importing data from BigQuery.
Data sources that exceed these limits can negatively affect the performance of your model.
If you would like to remove these limits, please reach out to your Lucanet contact person.
> **Tip:** To reduce the size of your data, aggregate it to the granularity you intend to use in xP&A (day, week, month) using SQL.
## Prerequisites for the Setup in xP&A
### Creating a Google Service Account and Key
Before connecting to BigQuery, you need to create a **Google service account** and an associated **key**.
A service account is a special kind of account for non-human users. For more information, see [Understanding Service Accounts](https://cloud.google.com/iam/docs/understanding-service-accounts). The key is required during the set-up process of the connection in xP&A.
You might need privileged access to your Google infrastructure in order to create a service account. For more information, see [Create service accounts](https://cloud.google.com/iam/docs/service-accounts-create).
To create the service account in Google:
1. Open your **Google Cloud Dashboard**, and go to **Service Accounts** page.
Google Service Accounts
2. Click **\+ Create service account.**
3. Enter a **name** and an **ID** for the service account and click **Create and continue**.
Enter service account name and ID
4. Grant xP&A access to BigQuery by assigning the Role **BigQuery Admin** and click **Continue**.
Assign 'BigQuery Admin' role
5. Go back to the **Service Accounts** page and click on the service account you just created.
6. Open the **Create key** menu and choose **Create new key.**
Create new key
7. In the next dialog, slect **JSON** as **key type** and click Create to **create** and download the key.
Key type 'JSON'
## Connecting to BigQuery in xP&A
To connect to BigQuery in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **BigQuery.**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog for BigQuery
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. **Choose a connection**
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and upload the JSON file you created for the Google service account (as described in [Creating a Google Service Account and Key](#creating-a-google-service-account-and-key))
Uploading the JSON file
2. **Complete the query form**
Enter the following:
- **Data source name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date** **column**, which must be one of BigQuery's date formats
- Names of the columns that contain **variables**(which must have a **numeric** data type.)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to Databricks"
description: "In xP&A, you can connect to the following spreadsheet file formats: Google Sheets, Excel Online, Excel Upload, CSV Upload\nThe following three data formats for spreadsheet files are supported: Tables, Transactions, Time-series\nEach connected file needs to be formatted in a certain way so that the data can be imported into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-databricks
language: en
last_updated: 2026-05-01
---
# Connecting to Databricks in Lucanet xP&A
## Overview
You can establish a direct connection to Databricks to pull in data into Lucanet xP&A (Extended Planning & Analysis).
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
### Whitelist IP Address in Databricks
If your database is behind a firewall, you have to whitelist the static IP address before connecting Databricks with xP&A.
Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
## Connecting to Databricks in xP&A
To connect to Databricks in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **Databricks.**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog for Databricks
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. **Choose a connection**
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New Databricks connection** dialog:
- **Host** name of the Databricks cluster you want to connect
- **Port** of the Databricks cluster you want to connect
- **HTTP path** of the workspace/warehouse you want to connect
- Authentication type to be used when connecting to Databricks. Choose one of the following options:
- **Personal account token**: If you choose this option, copy the personal access token to be used to access Databricks into the **Token** field. (For more information on how to get the access token, see [Authenticate with Databricks personal access tokens](https://docs.databricks.com/aws/en/dev-tools/auth/pat).)
- **Machine-to-Machine OAuth**: If you choose this option, enter the **client ID** and the **Client secret** used in the machine-to-machine authentication workflow with Databricks. (For more information on the client ID and client secret, see [Authenticate access to Databricks using OAuth token federation.)](https://docs.databricks.com/aws/en/dev-tools/auth/oauth-federation)
New Databricks connection
2. **Complete the query form**
Enter the following:
- **Data Source Name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date column**, which must be one of Databricks' date formats
- Names of the columns that contain **variables**(which must have a **numeric** data type)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to Looker"
description: "You can establish a connection to Looker to pull in data into xP&A.\nTo set up the connection, a Webhook data source is required.\nThe following steps are necessary, which are explained in this article:\n- Create a Look containing the data you want to have in your xP&A data source.\n- Create a Webhook data source in xP&A.\n- Set up the scheduled export in Looker."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-looker
language: en
last_updated: 2026-05-01
---
# Connecting to Looker in Lucanet xP&A
## Overview
You can establish a connection to Looker to pull in data into Lucanet xP&A (Extended Planning & Analysis).
To set up the connection, a Webhook data source is required.
The following steps are necessary, which are explained in this article:
1. Create a **Look** containing the data you want to have in your xP&A data source.
2. Create a [Webhook](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-using-webhook.md) data source in xP&A.
3. Set up the scheduled **export** in Looker.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Creating a Look Containing the Data in xP&A
The first step in setting up a connection to Looker is to create a Look containing the data that you would like to have in your data source. The following must be considered for the Look:
- First column must contain the **date** (supported date formats: YYYY-MM-DD and YYYY-MM)
- Second column can contain the **cohort**(optional)
- The following columns can contain the **dimensions**(strings) (optional)
- The following columns must contain at least one **variable**(numbers)
- Make sure missing dates are not filled (expand the **Visualisation** section, click on the gear icon of the date column header, and click **Remove filled in dates**, if necessary)
## Creating a Webhook Data Source for Looker in xP&A
The Looker data is pulled in using a Webhook connection. A detailed instruction on how to set up this connection can be found under [Connecting to a Source System Using a Webhook](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-using-webhook.md).
## Setting Up the Scheduled Export in Looker for xP&A
To pull in the exported data from Looker via the configured Webhook connection, you need to set up the scheduled export in Looker as a last step. Proceed as follows in Looker:
1. Click the gear icon at the top right and select **Schedule**.
Schedule in the Looker settings
2. In the **Where should this data go** section, select **Webhook**.
3. Enter the **Webhook URL of your data source** you created in the previous step.
4. In the **Format data as** section, select **JSON — Simple, Inline**.
5. Configure the trigger, i.e. when the data will be sent to xP&A. Choose one of the following options:
- **Repeating interval**, e.g. once every day
- **Datagroup update**, i.e. every time something in your database changes.
6. Open the **Advanced options** and do the following:
- Select **All results**
- Enable **Apply visualization options**
- Disable **Formatted data values**
Advanced options in Looker
7. Click **Save all.**
> **Warning:** You still have to **manually refresh** the **Webhook** data source in xP&A in order to pull the updated numbers into models that use the data source.
## Troubleshooting
In case the data cannot be pulled in from the data source, you can try the following troubleshooting options:
- Check if the **Look** has the right format (see [Transactions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md#transactions)). For every dimension you need one column in the **Look**.
- Make sure the date format is correct, e.g. 2022-04-20 for April 20th 2022 or 2021-12 for December 2021.
- There might be a nested JSON. In this case, you can try the following:
- Depending on the Look, the values might be nested in the JSON. Go to the **Data** workspace in xP&A, click on the three dots at the top right of the data source card, then click **Edit**. Now click the **View last uploaded data** button at the bottom of the modal to see the received JSON object.
- In the example below, the variables A, B and C are nested in the **Count** field. To access them in the data source, you have to enter the whole path to the object as the variable keys: **Count.A**, **Count.B** and **Count.C**
Example nested variables
---
---
title: "Connecting to Microsoft SQL Server"
description: "You can establish a direct connection to Microsoft SQL Server to pull in data into xP&A.\n\nIt is possible to use an SSH tunnel for the connection."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mssqlserver
language: en
last_updated: 2026-05-01
---
# Connecting to Microsoft SQL Server in Lucanet xP&A
## Overview
You can establish a direct connection to Microsoft SQL Server to pull in data into Lucanet xP&A (Extended Planning & Analysis).
It is possible to use an SSH tunnel for the connection.
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
### Whitelist IP Address in Microsoft SQL Server
If your database is behind a firewall, you have to whitelist the static IP address before connecting Microsoft SQL Server with xP&A.
Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
### Optional: Preparation for Connection via SSH Tunnel
If you want to establish a connection via an SSH tunnel, a user called causal must be created on the remote SSH server and the following public key must be associated with it:
**ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIP9DCR3hBNU/01YU9iK1JMKx2HNsK1+3ChWj3yBqb+Kr causal**
## Connecting to Microsoft SQL Server in xP&A
To connect to Microsoft SQL Server in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **Microsoft SQL Server:**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. **Choose a connection**
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New Microsoft SQL Server connection** dialog:
- Microsoft SQL Server **database host name** without port and database
- Microsoft SQL Server **database port**
- N **ame of the database** to which you want to connect
- **Database user name**
- Database user **password**
- Whether to use **encryption** when connecting to Microsoft SQL Server
If you want to establish a connection via an SSH tunnel, additionally enter:
- Host name of the SSH server used to establish a tunnel connection to the database
- Port of the SSH server used to establish a tunnel connection to the database
> **Tip:** If you configure access to your data warehouse via SSH:
>
> - Make sure to fulfill the prerequisites for the setup.
> - Remember to update the database hostname to be the database's IP internal to your network.
> - If you wish to update an existing connection to use SSH please contact us.
2. **Complete the query form**
Enter the following:
- **Data Source Name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date column**, which must be one of Microsoft SQL Server's date formats
- Names of the columns that contain **variables**(which must have a **numeric** data type.)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to MySQL"
description: "You can establish a direct connection to MySQL to pull in data into xP&A.\n\nIt is possible to use an SSH tunnel for the connection."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-mysql
language: en
last_updated: 2026-05-01
---
# Connecting to MySQL in Lucanet xP&A
## Overview
You can establish a direct connection to MySQL to pull in data into Lucanet xP&A (Extended Planning & Analysis).
It is possible to use an SSH tunnel for the connection.
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
### Whitelist IP Address in MySQL
If your database is behind a firewall, you have to whitelist the static IP address before connecting MySQL with xP&A.
Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
### Optional: Preparation for Connection via SSH Tunnel
If you want to establish a connection via an SSH tunnel, a user called causal must be created on the remote SSH server and the following public key must be associated with it:
**ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIP9DCR3hBNU/01YU9iK1JMKx2HNsK1+3ChWj3yBqb+Kr causal**
## Connecting to MySQL in xP&A
To connect to MySQL in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **MySQL:**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. #### Choose a connection
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New MySQL connection** dialog:
- MySQL **database host name** without port and database
- MySQL **database port**
- **Name of the database** to which you want to connect
- **Database user name**
- Database user **password**
If you want to establish a connection via an SSH tunnel, additionally enter:
- Host name of the SSH server used to establish a tunnel connection to the database
- Port of the SSH server used to establish a tunnel connection to the database
> **Tip:** If you configure access to your data warehouse via SSH:
>
> - Make sure to fulfill the prerequisites for the setup.
> - Remember to update the database hostname to be the database's IP internal to your network.
> - If you wish to update an existing connection to use SSH please contact us.
2. #### Complete the query form
Enter the following **:**
- **Data Source Name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date** column, which must be one of MySQL's date formats
- Names of the columns that contain **variables**(which must have a **numeric** data type.)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to Postgres"
description: "You can establish a direct connection to Postgres to pull in data into xP&A.\n\nIt is possible to use an SSH tunnel for the connection."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-Postgres
language: en
last_updated: 2026-05-01
---
# Connecting to Postgres in Lucanet xP&A
## Overview
You can establish a direct connection to Postgres to pull in data into Lucanet xP&A (Extended Planning & Analysis).
It is possible to use an SSH tunnel for the connection.
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
### Whitelist IP Address in Postgres
If your database is behind a firewall, you have to whitelist the static IP address before connecting Postgres with xP&A.
Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
### Optional: Preparation for Connection via SSH Tunnel
If you want to establish a connection via an SSH tunnel, a user called causal must be created on the remote SSH server and the following public key must be associated with it:
**ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIP9DCR3hBNU/01YU9iK1JMKx2HNsK1+3ChWj3yBqb+Kr causal**
## Connecting to Postgres in xP&A
To connect to Postgres in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **Postgres**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog for Postgres
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. **Choose a connection**
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New Postgres connection** dialog:
- Postgres database host name without port and database
- Postgres database port
- Name of the database to which you want to connect
- Database user name
- Database user password
If you want to establish a connection via an SSH tunnel, additionally enter:
- Host name of the SSH server used to establish a tunnel connection to the database
- Port of the SSH server used to establish a tunnel connection to the database
> **Tip:** If you configure access to your data warehouse via SSH:
>
> - Make sure to fulfill the prerequisites for the setup.
> - Remember to update the database hostname to be the database's IP internal to your network.
> - If you wish to update an existing connection to use SSH please contact us.
2. **Complete the query form**
Enter the following:
- Data Source Name
- Query to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date** column, which must be one of Postgres's date formats
- Names of the columns that contain variables (which must have a **numeric** data type.)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to Redshift"
description: "You can establish a direct connection to Redshift to pull in data into xP&A.\n\nIt is possible to use an SSH tunnel for the connection."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-redshift
language: en
last_updated: 2026-05-01
---
# Connecting to Redshift in Lucanet xP&A
## Overview
You can establish a direct connection to Redshift to pull in data into Lucanet xP&A (Extended Planning & Analysis). It is possible to use an SSH tunnel for the connection.
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
To allow xP&A to connect to your Redshift database, you have to take the following actions upfront:
### Whitelist IP Address in Redshift
If your database is behind a firewall, you have to whitelist the static IP address before connecting Redshift with xP&A.
Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
You also need to make sure that your Redshift database is only accessible with a strong username and password combination when whitelisting these IP addresses. Proceed as follows:
1. Open the **Properties** of your **Redshift Cluster**.
2. Under **Network and security settings**, click the **VPC security group**:
VPC security group settings
3. Open the **Inbound rules** tab and click **Edit inbound rules**:
'Inbound rules' tab
4. As **Type**, select **Redshift**, and enter your external **IP address** under **CIDR blocks** and click **Save rules**.
Enter the IP address
### Make Your Redshift Database Publicly Accessible
To allow xP&A to connect to your Redshift database, you need to make your database publicly accessible. Proceed as follows:
1. Open the **Properties** of your **Redshift Cluster**.
2. Under **Network and security settings**, make sure that the option **Publicly accessible** is activated.
Redshift network and security settings
3. If it is not activated, click **Edit** and activate the option **Turn on Publicly accessible**
Option 'Publicly accessible'
## Connecting to Redshift in xP&A
To connect to Redshift in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **Redshift:**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog for a Redshift connection
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. #### Choose a connection
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New Redshift connection** dialog:
- Redshift **Cluster endpoint host name** without port and database
- Cluster **endpoint port**
- **Name of the database** to which you want to connect
- **Database user name** and **password**
The user credentials are specific to the Redshift cluster and not AWS services. For more information about creating and managing database users in Redshift cluster, see [Redshift documentation](https://docs.aws.amazon.com/redshift/latest/dg/r_Users.html)
If you want to establish a connection via an SSH tunnel, additionally enter:
- Host name of the SSH server used to establish a tunnel connection to the database
- Port of the SSH server used to establish a tunnel connection to the database
> **Tip:** If you configure access to your data warehouse via SSH:
>
> - Make sure to fulfill the prerequisites for the setup.
> - Remember to update the database hostname to be the database's IP internal to your network.
> - If you wish to update an existing connection to use SSH please contact us.
2. #### Complete the query form
Enter the following:
- **Data Source Name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date column**, which must be one of Redshift's date formats
- Names of the columns that contain **variables** (which must have a **numeric** data type.)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Connecting to Snowflake"
description: "In xP&A, you can connect to the following spreadsheet file formats: Google Sheets, Excel Online, Excel Upload, CSV Upload\nThe following three data formats for spreadsheet files are supported: Tables, Transactions, Time-series\nEach connected file needs to be formatted in a certain way so that the data can be imported into xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/connecting-to-snowflake
language: en
last_updated: 2026-05-01
---
# Connecting to Snowflake in Lucanet xP&A
## Overview
You can establish a direct connection to Snowflake to pull in data into Lucanet xP&A (Extended Planning & Analysis).
This article contains a description of the prerequisites and the individual steps of the set-up process.
> **Note:** The fields that are pulled in must be defined during the set-up process using a database query. For a detailed instruction on how to structure such a query, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
## Prerequisites for the Setup in xP&A
### Necessary Permissions
Make sure the account you are using has permission to access the tables you wish to query.
### Whitelist IP Address in Snowflake
Snowflake has the option of implementing a [Network Policy](https://docs.snowflake.net/manuals/user-guide/network-policies.html) in order to restrict access based on IP addresses.
If you are **not using a Network Policy**, your database is publicly accessible and no further actions are necessary.
If you have **enabled a Network Policy**, you have to whitelist the static IP address before connecting Snowflake with xP&A. Which IP address needs to be whitelisted depends on the region where your Lucanet instance is hosted:
| Region | IP address to whitelist |
|--------|------------|
| eu-central-1 | 52.59.129.235 |
| ap-southeast-1 | 13.214.111.217 |
| us-east-1 | 3.223.155.63, 98.87.131.112, 44.219.125.183 |
| eu-central-2 | 51.34.5.247 |
| eu-north-1 | 13.51.154.160 |
> **Tip:** The correct IP address(es) to whitelist matching your region is shown in the **New Data Source** dialog when you create the connection, so please check this information on the user interface.
## Connecting to Snowflake in xP&A
To connect to Snowflake in xP&A:
1. Choose one of the following options:
- Open the **Data** workspace from the overview on the start page and click **\+ New.**
New data source connection from the Data workspace
- Open the model into which you would like to integrate the data, click the **+** sign next to **Data** in the overview, and choose **New data source**:
New data source connection from within a model
2. In the **Data sources** dialog, open the **BI/Database** tab and choose **Snowflake**
'BI/Database' tab
3. The **New Data Source** dialog is displayed as follows:
'New Data Source' dialog for Snowflake
4. Configure the steps as described in the following section.
5. Click **Create data source**.
### Set-up Steps
The following steps are required to set up the data source:
1. **Choose a connection**
Choose an existing connection, or, if you have not configured a connection yet, click **New Connection** and enter the following in the **New Snowflake connection** dialog:
- **Snowflake account identifier** in the format _-_. Please do not use your account name. For more information on Snowflake account IDs, see [Account identifiers](https://docs.snowflake.com/en/user-guide/admin-account-identifier).
- Snowflake **user name**
- **Name of the default warehouse** you want to execute the queries with.
This can be changed by appending the \`USE WAREHOUSE \*;\` statement before the actual [query](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- **Authentication type** to be used when connecting to Snowflake. Choose one of the following options:
- **Key pair**: If you choose this option, copy the displayed key into your clipboard and execute this statement in Snowflake to associate xP&A's public key with the user you have configured.
- **Password**: If you choose this option, enter the password of the user to be used when establishing a connection to Snowflake
Setting up a Snowflake connection
2. **Complete the query form**
Enter the following:
- **Data Source Name**
- **Query** to define the fields which are to be pulled in. For more information, see [Defining Database Queries](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries.md).
- Name of the **Date column**, which must be one of Snowflake's date formats
- Names of the columns that contain **variables**(which must have a **numeric** data type)
> **Tip:** Any remaining columns will be treated as dimensions, and must have a **string** data type.
>
> An exception is the **cohort** dimension, which must be a date, with the column header explicitly labelled **Cohort**.
---
---
title: "Creating a Data Export in xP&A for CFP"
description: "Before data from xP&A can be transferred to Consolidation & Financial Planning, an export containing the desired data needs to be created in xP&A for each model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-data-export-in-xPA-for-CFP
language: en
last_updated: 2026-05-28
---
# Creating a Data Export in xP&A for Transfer to CFP
## Overview
Before data from xP&A can be transferred to Consolidation & Financial Planning, an export containing the desired data needs to be created in xP&A for each model.
## Creating the Data Export in xP&A
To create and configure an export of the data you want to transfer to CFP in xP&A **per model,** proceed as follows:
1. In the model you want to export the data from, click the **Settings** button the settings icon and navigate to the **Export and download** section.
2. Click **+** to create a new export and configure the steps in the **New export** dialog as follows.
3. Configure the **Export definition:**
- Give the export a clear **name** that matches the model (e.g. "Sales forecast").
- Choose the export type **Raw**.
Configuring the export definition
4. Configure the **Target**:
- Under **Export target**, keep the **Download** preselection
- Under **Export output**, choose **Parquet.**
Configuring the export target
5. Configure the **Content**:
- Choose what data you want to export: **All values**, a specific **View**, or a named **Version**.
If you work with specific planning versions (e.g. "Forecast 1+11"), choose **Version** and select the relevant one. This is required when you need to map different versions to different data levels in CFP.
- Under **Additionally exported columns,** select at least the columns **Variable ID** and **Scenario**. You can optionally activate **Cell location** if you want to drill down from CFP to the data in xP&A.
Configuring the export content
6. Click **Create export**.
The export is created and displayed in the **Export and download** section:
New export in the 'Export and download' section
The export can now be accessed by Consolidation & Financial Planning using the script **Lucanet xP&A #3700-xP&A.SQL.FOS**.
7. Repeat the above steps for each model whose output data you want to import into Consolidation & Financial Planning.
---
---
title: "Creating a Model"
description: "A model in Lucanet xP&A refers to a structured representation of data and calculations, similar to a tab in a spreadsheet.\n\nYou can define a model as your \"base\" model representing the default scenario. To compare different scenarios, you can create variants of your \"base\" model in which some variables (or cells of a variable) have different values or formulas."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model
language: en
last_updated: 2026-05-01
---
# Creating a Model in Lucanet xP&A
## Overview
A **model** in Lucanet xP&A (Extended Planning & Analysis) refers to a structured representation of data and calculations, similar to a tab in a spreadsheet.
You can define a model as your "base" model representing the **default scenario**. To compare different scenarios, you can create variants of your "base" model in which some variables (or cells of a variable) have different values or formulas.
The structure of the model — the variables, groups, and sections — doesn't change across scenarios.
In Lucanet xP&A, a new model can be created:
- Manually
- Generated using AI
- Using a wizard
## Creating a New Model in Lucanet xP&A
If you want to create a new model in Lucanet xP&A, click **New model** directly on the **start page** or in the **overview on the start page.** The **Create Model** dialog is displayed as follows:
The 'Create Model' dialog
The following table describes the options for creating a model in Lucanet xP&A:
| Option | Description |
|---|---|
| **Recommended** | You can use the **Generate a model** option to build a new model with the help of our AI-supported **Modeler Agent**, based on a plain-language description. Using the agent, you can avoid repetitive structural setup steps at the start of a project and build a best-practice xP&A structure without writing formulas yourself.
For more information on how to use the agent, see the following section _Creating a New Model with the Modeler Agent in Lucanet xP&A_. |
| **Basic** | You can use the **New model** option to create a new model manually from scratch. |
| **Wizard** | In the wizard area, specific types of models can be created using a wizard **guiding through the setup** process and **using your data** during the setup. The following model types are available: • P&L and Runway • Full P&L and balance sheet report • Headcount plan • Sales and Pipeline Report |
> **Note:** - If you hover over the model type name, a description of the model type is displayed on the right side of the dialog.
> - Once the model is created, you can start editing it and filling it with your data as described in [Modeling your Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data.md).
## Creating a New Model with the Modeler Agent in Lucanet xP&A
The Modeler Agent is an AI agent built into Lucanet xP&A that builds a planning model from a plain-language description. Instead of scaffolding sections, variable groups, variables, timesteps, aggregations, and formulas by hand, you describe the model you want and the agent generates it for you using the xP&A formula language.
To use the Modeler Agent in Lucanet xP&A:
1. On the xP&A start page, click **New model**.
2. In the **Create model** dialog, select the option **Generate a model**. The prompt section of the Modeler Agent is displayed on the right side of the dialog as follows:
Generating a new model with the Modeler Agent
3. In the prompt section, describe the model you want to build, e.g. "Create a SaaS revenue model with ARR, churn, and expansion"
4. The Modeler Agent generates a plan for building the model as follows, for example:
Example for a proposal of the Modeler Agent
5. Review the proposed plan, and, if needed, you can ask the agent questions about the plan or ask to modify the suggestion.
6. Once the plan meets your expectation, click **Build model**.
The model is created based on the suggested plan and you can edit every section, cell, formula, or variable as in any other model.
> **Warning:** **Current restrictions**
>
> At the moment, the following restrictions apply for the Modeler Agent:
>
> - Reports from Consolidation & Financial Planning cannot be included
> - Data source cannot be added
### Modeler Agent as a Video
The following video shows you how to use the **Modeler Agent**:
Video: https://player.vimeo.com/video/1213830783?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
---
---
title: "Creating an Assignment Table"
description: "An assignment table is used to save all elements imported from xP&A (e.g. accounts, reporting entities/cost centers, transaction currency, etc.) and their assignment to elements in CFP.\n\nAssignments are defined during the data import and can then be changed or deleted at any time."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-an-assignment-table-for-import-of-xPA-data
language: en
last_updated: 2026-05-28
---
# Creating an Assignment Table for the xP&A Import into CFP
## Overview
An **assignment table** is used to save all elements imported from xP&A into Consolidation & Financial Planning (CFP) (e.g. accounts, reporting entities/cost centers, transaction currency, etc.) and their assignment to elements in CFP.
Assignments are defined during the data import and can then be changed or deleted at any time.
> **Note:** **Note for customers who still use Lucanet.Financial Client**
>
> You can either perform this step in the Lucanet CFO Solution Platform or in Lucanet.Financial Client. The data source will be visible and editable in both systems, no matter where you created it.
## Creating an Assignment Table for the xP&A Import into CFP
To create an assignment table for the xP&A import into CFP, proceed as follows:
1. In the tree view, right-click the **Assignment tables** folder and choose **Create | Assignment table** from the context menu.
Creating an assignment table
2. The **Create element** dialog is displayed:
Dialog 'Create element'
3. Specify the name of the assignment table in the **Name** field.
4. Click **Save** or press **Enter**.
5. The assignment table is displayed in the tree view and can be selected when creating the data import (see [Creating and Executing the Data Import](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-executing-the-data-import-into-CFP.md) _)_.
---
---
title: "Creating and Configuring the Data Source"
description: "Once you have configured the data transfer script xP&A #3700-xP&A.SQL.FOS, you can create and configure the data source for the import that uses the script and its parameters."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import
language: en
last_updated: 2026-05-28
---
# Creating and Configuring the Data Source for the xP&A Import into CFP
## Overview
Once you have configured the data transfer script **xP&A #3700-xP&A.SQL.FOS**, you can create and configure the data source used to import xP&A data into Consolidation & Financial Planning (CFP). The data source links the script and defines the parameters used for the import.
> **Note:** **Note for customers who still use Lucanet.Financial Client**
>
> You can either perform this step on the CFO Solution Platform or in Lucanet.Financial Client. The data source will be visible and editable in both systems, no matter where you created it.
## Creating and Configuring the Data Source for the xP&A Import into CFP
Proceed as follows to configure the data source necessary for importing data from xP&A into CFP:
1. Open the **Importing data into reporting entities** workspace.
2. Right-click the folder **Data sources** and choose **Create | Data source** from the context menu.
Create a new data source
3. In the **Create data source** dialog, choose **Provision via script**, enter a **name**, and click **Save** to create the data source.
4. Select the data source in the tree view.
5. In the **General** area on top, behind **Drill down to posting level**, select the app **Lucanet xP&A #3700-xP&A.SQL.FOS** which you configured for transferring the desired data.
This enables the drill down from data in CFP to the corresponding data in xP&A.
Select drill-down to posting level
6. Configure the data source parameters as described in the following under _Data Source Parameters_.
7. Click **Save** (or press **Ctrl+S**) to save the data source configuration.
## Data Source Parameters
### 'General' Tab
The **General** tab is displayed as follows, for example:
'General' tab
Configure the following options on the **General** tab:
| Option | Description |
|---|---|
| **Scripts executed during the data import** | **Script:** Select the script **Lucanet xP&A #3700-xP&A.SQL.FOS** (the name may be truncated in the dropdown list). This script is executed during the data import. **Application:** Select where the script is executed, e.g. **Execute on the server**. |
| **Data to be imported** | **Import type:** Select one of the following import types: • **Transaction figures** – imports transaction figures • **Balances** – imports balances • **Transaction figures incl. automatic contra entry** – imports transaction figures with automatic contra entries into planning data levels (not for the actual data level). • **Transaction figures or balances (selection when importing)** – the user chooses transaction figures or balances when executing the import. |
| **Accounting periods per year** | Select the number of periods per fiscal year (e.g. **12**). The app supports 12 periods per fiscal year. |
| **Dimensions to be imported (transaction currency)** | Activate to use a dimension from xP&A as transaction currency for the execution settings and select the **Dimension for transaction currency**. |
| **Dimensions to be imported** | Activate the **Use dimension** checkbox to include the dimension in the import. The **Dimension code** (e.g. **GLAccount** for Account, **CostCenter** for Cost center) is filled in automatically. |
| **Cost centers in the Balance Sheet** | The area **Cost centers in the Balance Sheet** is only visible if you activated the import of the cost center dimension.
Select if you want to **Use default cost centers always (recommended)**, or if you want to **Use specified cost centers** (e.g. from the reporting entities or assignment table). |
| **Reclassify values** | Select if and how values shall be reclassified during the import: • **Attach suffix to account name** • **Present intercompany postings on separate accounts** • **Reclassify debtors with credit balances and creditors with a debit balance** |
### 'Reporting entities' Tab
The **Reporting entities** tab is displayed as follows, for example:
'Reporting entities' tab
Configure the following options on the **Reporting entities** tab:
| Option | Description |
|---|---|
| **Reporting entities that can be selected for import** | Add the reporting entities that can be selected for import and fill in the table columns: • **Displayed name** – name as shown in the UI • **Abbreviation in Lucanet** • **ID in data source** – name of the reporting entity in Lucanet. Must match the exact name in Lucanet, as this is used as the target of the import. • **First month of the fiscal year** – e.g. 1 for January • **Category** – optional category • **Folder** – optional folder |
| **Settings relevant when creating a data import** | • **Split data imports during first execution**: If activated, data imports are split during the first execution. • **Categorize data imports**: If activated, data imports are categorized as specified in the table above. • **Use folders**: If activated, folders are used for organizing data imports as specified in the table above. • **Adjust name of the month**: If activated, the name of the month is adjusted with a specified prefix or suffix. |
### Script-Specific Parameters - 'Model configuration' Tab
The **Model configuration** tab is displayed as follows, for example:
'Model configuration' tab
Configure the following options on the **Model configuration** tab:
| Option | Description |
|---|---|
| **Export IDs** | Table to define the exports created in xP&A that are to be imported into Consolidation & Financial Planning. Specify the following: **Export ID:** ID of the export from xP&A whose values are to be read (selectable options are based on the script configuration). **Do not refresh xP&A export:** If activated, the export from xP&A is not executed again on the next import; previously exported data can be used. If no export has been run yet for this export ID, the export will still be executed. |
| **Import variables** | Option to filter the variables to be imported from xP&A. The following options can be selected: • **Selected variables** – Recommended option allowing you to select an entire **section** or individual variables. Selecting a section is less maintenance-heavy: new variables added to that section in xP&A are automatically included on the next refresh. • **All variables** – All variables from the xP&A export are imported as accounts, except those marked as **Exclude variable** in the **Variables** table. |
| **Variables** | Table to define specific variables to be imported (if you do not want to import **All variables**) or excluded from the import. The table contains the following columns: • **Variable** – variable from xP&A to import as an account (**Refresh** updates the list). • **Multiply value by -1** – if activated, values for that variable are multiplied by -1. xP&A typically stores revenue as positive values, but CFP uses debit/credit logic where revenue (P&L credit) must be imported as negative to display correctly. • **Exclude variable** – if activated, the variable is excluded (when **All variables** is selected). |
| **Multiply all values by -1** | If activated, all values are multiplied by -1. xP&A typically stores revenue as positive values, but CFP uses debit/credit logic where revenue (P&L credit) must be imported as negative to display correctly. You can apply this option per variable, per section, or globally via this checkbox at the bottom. |
> **Tip:** **Tip:** Structure your models with separate sections for revenue and cost outputs, so you can apply the -1 multiplier cleanly at section level.
### Script-Specific Parameters - 'Import configuration' Tab
The **Import configuration** tab is displayed as follows, for example:
'Import configuration' tab
Configure the following options on the **Import configuration** tab:
| Section | Parameters and description |
|---------|---------|
| **Import values** | Option to specify which currency should be used when importing values. Choose between **As specified currency** (uses the currency from xP&A) or **As default currency** (uses the entity's default currency in CFP). |
| **Scenarios** | Scenarios from xP&A whose values are to be imported into CFP. The selection options can be updated by clicking **Refresh**. |
| **Import additional years** | If your model spans more than one year into the future, specify how many extra years to include. |
| **Use prefix** / **Use suffix** | Optionally add a **prefix** or **suffix** to a specific dimension to control how values are mapped (e.g. for sub-ledger account differentiation). |
---
---
title: "Creating and Configuring the Script Lucanet xP&A #3700-xP&A.SQL.FOS"
description: "In order to import an xP&A data export into CFP, you must first create and configure the data transfer script Lucanet xP&A #3700-xP&A.SQL.FOS."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-configuring-the-script-used-for-xPA-import
language: en
last_updated: 2026-05-28
---
# Creating and Configuring the Script Lucanet xP&A \#3700-xP&A.SQL.FOS
## Overview
In order to import an xP&A data export into CFP, you must first create and configure the data transfer script **Lucanet xP&A #3700-xP&A.SQL.FOS**.
> **Note:** **Note for customers who still use Lucanet.Financial Client**
>
> You can either perform this step in the Lucanet CFO Solution Platform or in Lucanet.Financial Client. The script will be visible and editable in both systems, no matter where you created it.
## Creating and Configuring the Script for the xP&A Import into CFP
To create and configure the data transfer script Lucanet **xP&A #3700-xP&A.SQL.FOS** used for importing xP&A data into CFP, proceed as follows:
1. In the overview, click the **Import and Journals** workspace.
2. In the tree view of the workspace, right-click **Scripts** or a folder and select the following from the context menu: **Create | Script**:
Create a new script
3. Choose one of the following options to load the script **xP&A #3700-xP&A.SQL.FOS** into the **Scripts** workspace in the subsequent dialog:
- **Drag and drop** the desired script into the dialog.
- Click **browse** and navigate to the desired script.
4. Create the script.
5. In the detail view of the script, click **Edit** and configure the tabs of the script as described in the following under _Script Parameters_.
6. Click **Save** (or press **Ctrl+S**) to save the script configuration.
## Script Parameters
### 'Connection' Tab
The **Connection tab** is displayed as follows, for example:
'Connection' tab
Configure the following options on the **Connection** tab:
| Parameter | Description |
|---------|---------|
| Export IDs | Select all xP&A exports, i.e. the models that should be imported. All exports are available which have been created in xP&A and for whose model you have access permissions. You can click **Refresh** to update the selection of available exports. |
| Database | Optional: Connection to an SQL database Serves as a temporary storage location for reimporting exports already performed from xP&A and for drill-down without restarting the export from xP&A. Connection information for Lucanet.Financial Warehouse can be used here. |
### 'Dimension configuration' Tab
The **Dimension configuration** tab is displayed as follows, for example:
'Dimension configuration' tab
On the **Dimension configuration** tab, you map xP&A dimensions to CFP dimensions.
The key mapping dimension is **entity** (i.e. how does the entity dimension in your xP&A model translate to cost centers in CFP).
The following options are available on the **Dimension configuration** tab:
| Option | When to use |
|---------|---------|
| Refresh dimensions from xP&A | Click **Refresh dimensions from xP&A** to update the available dimensions from the specified xP&A export(s). |
| Use dimension for reporting entity | Activate if you use a custom dimension in xP&A (not integrated from CFP) and want to map it to reporting entities manually. |
| Use dimension for transaction currency code | This is a **legacy option** and **not needed** in the current xP&A setups. |
| Assign cost centers automatically dependent on OIDs | Activate when you use the **organization element structure** from CFP in xP&A. The OID (unique identifier per cost center) enables automatic matching. |
| Assign cost centers automatically dependent on homonymous names | This is a **fallback option** where matches are based on name. Requires a dedicated assignment table. |
| Dimension mapping | Assign xP&A dimensions to Lucanet.Financial OLAP Server (FOS) dimensions. For user-defined dimensions, you can use the target dimensions **UserdefinedDimension1** to **UserdefinedDimension9**; when configuring the data source, use the corresponding **DimensionsCode** as needed. |
> **Tip:** **Best practice:** Always create a separate [assignment table](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-an-assignment-table-for-import-of-xPA-data.md) for xP&A imports to avoid conflicts with other import processes.
---
---
title: "Creating and Editing Dimensions"
description: "Dimensions are xP&A’s most powerful concept. Dimensions allow you to build your business’ structure directly into your financial models, removing the need for formula duplication and lookups."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions
language: en
last_updated: 2026-05-01
---
# Creating and Editing Dimensions in Lucanet xP&A
## Overview
**Dimensions** are the most powerful concept in Lucanet xP&A (Extended Planning & Analysis). Dimensions allow you to build your business’ structure directly into your financial models, removing the need for formula duplication and lookups.
With dimensions in xP&A, you can:
- Reduce the number of formulas in your models by 100x or more
- Make it much easier to maintain and develop your models over time
- Significantly reduce the chance of human error when working with formulas
- Make it much easier to connect to historical data
- Make it much easier to visualize and pivot data from your models
## Creating a Dimension in xP&A
You have several options for creating a dimension in xP&A:
- Create a new dimension via the **+** icon in the **overview** of the model on the left.
Create a new dimension
- Create a dimension **directly on a variable**:
You can also create a new dimension directly on a variable by clicking on the **Dimensions** button and [adding a dimension breakdown](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md).
Add a dimension to a variable
> **Note:** If dimensions exist in your data sources, these will show up as options when you click the **Dimensions** button on a [variable that is connected to integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md). If you select these dimensions, this will automatically create the dimension in xP&A (if they do not exist in xP&A yet), and add it to your model/variables. See [linking dimensions from data sources](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source.md) for more.
- Create a dimension in the **Dimensions** workspace:
Open the **Dimension** workspace and click **New**.
Create a new dimension in the dimensions workspace
## Editing a Dimension in xP&A
How you edit a dimension in xP&A depends on whether you are editing the dimension in the **spreadsheet** or in the **Dimensions** workspace.
### In a Spreadsheet
To edit a dimension in the **spreadsheet of a model** in xP&A:
1. Click the dimension you want to edit.
Dimensions in a model
2. The dimension is displayed as follows, for example:
Dimension in a model
3. If necessary, edit the **dimension items**. The following functions are available:
- You can **rename**, **duplicate**, or **delete** an item in the item's **three-dot menu**.
- Change the order of the items by moving one or more items using drag and drop.
Edit dimension item
4. If necessary, edit the **dimension** and the **item list** using the functions in the upper right corner of the dimension area.
Edit dimension
The following functions are available:
- Sort, filter or search the dimension
- Rename the dimension
- Change the dimension icon
- Show or hide sparkline columns
- Remove the dimension from the model
- Delete the dimension
### In the 'Dimensions' Workspace
Dimensions can also be edited in the **Dimensions** workspace in xP&A. The **Dimensions** page shows you a list of all of the dimensions on your account, and any dimensions that are used in models that have been shared with you (shared dimensions).
1. If necessary, click **xP&A** in the upper left corner.
2. Navigate to the **Dimensions** workspace.
The **Dimensions** workspace is displayed as follows, for example:
Open the dimension workspace
3. Configure the dimensions as desired (see [Options for Dimensions](#options-for-dimensions)).
4. If you want to edit the dimension items click on an empty space in the dimension line (see [Editing Dimension Items](#editing-dimension-items)).
## Options for Dimensions in xP&A
On the **Dimensions** page in xP&A, you have the following options for dimensions:
| Option | Description |
|---|---|
| **All / Yours / Shared** | Filters the list of dimensions |
| the search icon | Search for a dimension |
| the graph icon | Open a dimension mapping graph |
| the new icon icon | Create a new dimension |
| the category icon | Give dimensions an icon by clicking the icon next to the dimension name |
| **X Models** | Hover to see which models use the dimension; if you have [linked dimensions](#linking-dimensions), the tooltip also shows how they connect to each other |
| the three dot icon | Opens a context menu to inspect or delete the dimension |
| **Edit a dimension item** | Click on an empty space in the desired dimension line (see [Editing Dimension Items](#editing-dimension-items)) |
## Adding a Dimension Item in xP&A
Add new dimension items in xP&A in the bottom row by clicking **New item**.
Add dimension item
> **Warning:** All dimension items for a dimension must be unique, i.e. you cannot have two duplicate dimension items.
## Editing Dimension Items in xP&A
To edit dimension items in xP&A:
1. Click on an empty space in the dimension line.
2. The **Dimension** detail view is displayed as follows, for example:
Product dimension with dimension items
3. Configure the dimension items as desired.
The following functions for dimension items are available in xP&A:
- **Add**/ **delete**/ **rename** dimension items using the **three-dot menu** behind the name of the dimension item.
- **Create** and **update dimension-level links** and **item-level mappings**.
- Set the dimension **icon**.
- **Search**, **sort**, **filter**, or **reorder** dimension items.
- See which **data sources** the dimension is linked to (by hovering over each item).
- Configure a **default currency** for the dimension item by adding the **currency column** using the **+** button. For more information on currency translation and currencies at dimension item level, see [Using Currency and Currency Conversion](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/currency---fx-conversion.md).
> **Tip:** In the **spreadsheet** in xP&A, you can navigate to the dimension to which a dimension item belongs by clicking the **arrow icon**:
>
> the shows 'variable 1' row in xp&a spreadsheet, broken down by dimension items 'sales', 'finance', 'operations', and 'r&d'. highlighted in purple is arrow (tooltip 'open dimension') used to navigate to dimension. icon
> Navigate to dimension
## Structuring Dimensions in Hierarchies in xP&A
If your dimension has an inherent hierarchy, e.g. your dimension is **Group** and contains **Divisions**, **Branches**, and **Shops** that are rolled up, you can build your dimension in xP&A in order to display and aggregate data at the corresponding level.
To create this hierarchy in the **dimension settings**, simply grab a dimension item on the left and drop it under the dimension it belongs. This automatically assigns levels (top items are level 1, their children Level 2, and so on).
In the following example **Division 1** is level 1, **Branch A** is level 2 and **Shop 1, 2 and 3** are level 3:
Hierarchy of a dimension
> **Tip:** In the **spreadsheet** in xP&A, you can group your dimensions by a certain hierarchy level. To do so, click the **Dimensions** button and select the level at which your data is grouped:
>
> the shows dimension breakdown menu in xp&a for 'revenue' variable, with 'levels' selected and level drop down list expanded to 'all levels', '1', and '2'. highlighted in red are dimension icon, level drop down list button, and level options. icon
> Grouping by levels
## Importing Dimensions From a Spreadsheet in xP&A
When you [import a dimension from a spreadsheet](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md) (CSV, MS Excel, or Google Sheets), you can define the hierarchy directly in the cells of the spreadsheet using the **>** separator. xP&A reads the hierarchy path, creates each dimension item at the correct level, and links it to its parent item automatically – there is no need to rebuild the hierarchy by drag-and-drop after the import.
This is the recommended approach when you are setting up a dimension with a large number of dimension items.
**Example**
- In the dimension column of a spreadsheet, write the full path to each item, separating levels with **>**.
- The last segment is the item itself
- Everything before the last segment defines the ancestors
Dimension hierarchy in the spreadsheet
After the import, the dimension appears in the hierarchy in xP&A with the same structure you would get from organizing the dimension items manually:
Dimension hierarchy in xP&A after import
Once the dimension has been imported, you can continue to adjust the hierarchy manually with drag-and-drop in the dimension settings, as described in the previous section.
The two methods can be combined; i.e. first bulk-import the structure from a spreadsheet, then finetune individual items in the dimension details in xP&A.
> **Note:** **Please note**
>
> - **Deduplication:** Items with the same path are treated as the same item. **Revenue > Product Sales** in two different rows resolves to one item **Product Sales** under **Revenue**.
> - **Automatic creation of parents:** You do not need a separate row for every level. If your file only lists leaf items (for example, **Revenue > Product Sales > Licenses**), xP&A creates **Revenue** and **Product Sales** automatically. Auto-created parents have no values of their own; values roll up from their children.
> - **Whitespace:** Spaces around **>** are ignored. **Revenue > Product Sales** and **Revenue>Product Sales** produce the same result.
> - **Maximum depth:** A hierarchy can have up to 128 levels.
> - **Backwards compatibility:** If no cell contains **>**, the import behaves exactly as before and the dimension is created as a flat list.
> - **Invalid path**: xP&A shows a warning if a path is malformed — for example, a trailing >, a leading >, or empty segments between two separators (Revenue > > Licenses). In this case, fix the path in your source file and re-import.
## Adding Types to a Dimension in xP&A
In addition to levels, dimensions in xP&A may also have **types**, which are classifications you can assign to items. Types may align with levels, but don’t have to. For example, you could have a **Shop** type where **Shop 5** and **Shop 6** are grouped under **Shop 4**.
In models, you can group the dimensions either by **types** or **levels**.
To add a type to a dimension in xP&A:
1. Navigate to the detail view of the dimension and click the + sign in the **Types** column on the right-hand side:
Adding a new type to a dimension
2. Enter the name of the type and click **Save**.
3. Add the **Type** column to the dimension table by clicking the **+** sign on top of an empty column and choosing **Show type column**:
Adding the 'Type' column
4. In the **Type** column, assign the types to the relevant dimension items by choosing them from the drop-down list. You can also click **Create new** to create a new type during this assignment step.
Assigning a type to a dimension item
> **Tip:** Once the types have been assigned, you can group your dimensions by type in the **spreadsheet** in xP&A. To do so, click the **Dimensions** button and select the types you want to use for breaking down your dimensions:
>
> the shows dimension breakdown menu in xp&a for 'revenue' variable. highlighted in red are dimension and type list with 'company', 'branch' (selected), and 'shop'. icon
> Grouping by types
## Additional Functions for Dimensions in xP&A
The following additional functions for dimensions in xP&A are available:
### Bringing Existing Dimensions Into Models in xP&A
To include an existing dimension in a model in xP&A, choose one of the following options:
- Navigate to the dimension under the **+** icon in the overview of the model on the left. You can include multiple dimensions at once by clicking multiple dimensions while the picker is open:
Adding a dimension from the overview
- Click the **Dimensions** button on a variable, to add that dimension to the variable (and to the model):
Adding a dimension from a variable
### Indirect Dimension Mappings in xP&A
You can show or hide indirect dimension mappings in xP&A in the data tables, or in the detail view of the dimension in the **Dimension** workspace.
**Example**:
- If each **Employee** has a **Title**, and each **Title** sits within a **Team**, then each **Employee** sits within a **Team** via their **Title**.
- The indirect dimension mapping is from the **Employee** to their **Team**.
- When in the **Employee** dimension, you can reveal the **Team** of each employee by clicking the **>** in the column header.
Show/Hide indirect dimensions
> **Note:** **1-to-1 vs. 1-to-many relationships**
>
> - Linked dimensions have a 1-to-1 relationship, i.e. each dimension item in the primary dimension links to only one dimension item in the linked dimension. Each employee may only have one job title, for instance.
>
> - xP&A's dimensions are not designed for 1-to-many relationships, i.e. one job title cannot sit within multiple departments.
### Linking Dimensions in xP&A
Often, there will be a relationship between dimensions. For example, assigning each **Employee** to a **Job** **Title**, or assigning each **Deal** to a **Sales Representative**.
To link dimensions in xP&A, click the **+** in the far-right column (in the data tables, or in the detail view of the dimension in the **Dimensions** workspace) and select the **Link dimension** option.
Link dimensions
This will create an extra column in the data table, allowing you to map the two dimensions together (e.g. giving each **Employee** a **Location**).
Map dimensions
In **hierarchical** dimensions with **levels**, only the **lowest** dimension items can be linked.
Example: In **Group A** → **Branch 1** → **Shop New**, only **Shop New** can be linked.
> **Warning:** Dimension linking in xP&A can have an impact on your cell count and thus the performance of your model. Always verify your dimension relationships before implementing your model to avoid exponential cell growth and potential system performance issues.
>
> For more information, see [Cells and Limits](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cells-and-limits.md).
### Pasting Dimension Items Into xP&A
To paste data in (e.g. from a spreadsheet), simply copy your data, then select your row(s), and paste (**Ctrl/Cmd + V**). xP&A will "paste over" whatever row(s) you had selected.
If you do not want to paste over what you have already in the data table, then create a **new item** at the bottom of the table (you may have to take off alphabetical sorting if you have that applied), select that new item, and paste over that new item (see [Adding a dimension item](#adding-a-dimension-item)).
---
---
title: "Creating and Editing Formulas"
description: "Formulas are one of the most important concepts in Lucanet xP&A. Formulas let you work with numbers, ranges, and other variables."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas
language: en
last_updated: 2026-05-01
---
# Creating and Editing Formulas in Lucanet xP&A
## Overview
**Formulas** are one of the most important concepts in Lucanet xP&A (Extended Planning & Analysis). Formulas let you work with **numbers**, **ranges**, and other **variables**.
Here are some simple examples:
- `25`: constant value of 25
- `1 to 5`: range from 1 to 5 (technical detail: symmetric [triangle distribution](https://en.wikipedia.org/wiki/Triangular_distribution))
- `(0 to 1) * MyVariable` : the product of a range and another variable
- `if VariableA > 10 then 1 else 0`: Write 1 if variableA is greater than 10, otherwise write 0. You can link multiple conditions with **and** and/or **or**. See [if statements](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/if-statements-in-formulas.md) for more!
- `sample(3, 5)`: either the value 3 or the value 5 (discrete distribution)
## Creating Formulas in Lucanet xP&A
To create or edit a formula in Lucanet xP&A:
1. Make sure that the formula column is displayed. If necessary, click **Formula** in the toolbar.
2. Do one of the following:
- Double-click in the desired cell in the formula column.
- Select the desired cell and press **F2**.
3. Enter the formula (see [Elements in Formulas](#elements-in-formulas-in-lucanet-xpa)).
4. Press **Enter** to save the formula.
> **Note:** If you are getting an error with a variable, you can hover over the formula error or the variable and xP&A will try to explain the cause of the error.
## Elements in Formulas in Lucanet xP&A
The following elements can be used in formulas in Lucanet xP&A:
| Element | Description |
|---|---|
| **Basic operations** | The syntax for basic operations is the same as MS Excel: **\+ \- \\* / ^ \> < =**. |
| **Not equal to** | **<>** or **!=** |
| **Reference variables** | You can reference variables in formulas by typing the variable name and selecting it from the autocomplete drop-down list. You can also [reference variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models.md) in other models if they're linked. |
| **Variable modifiers** | When you reference a variable in a formula, there are two key ways to modify it - using **Dimensions**(if applicable), and **Time**.
For more information, see [Variable Modifiers](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md). |
| **Functions** | Functions that can be used in formulas.
For more information, see [Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/functions.md). |
| **Helper variables** | The following helper variables are available for formulas: • **lastActualDate**: a helper variable that returns the timestep of the [Last Actual Date setting](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), if it is toggled on (see [Helper Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md)) • **blank**: Blank values are treated like 0s in most formulas (e.g. blank + 7 = 0 + 7 = 7), _except_ in instances involving a set of numbers (e.g. avg, min/max/median, count etc) where blanks will be excluded (e.g. avg(5,10,blank) = avg(5,10) = 7.5).
For more information, see [Helper Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md). |
| **If-statements** | If you want a variable to have different values or formulas based on a condition, you can use if-statements. They always have to follow the structure **if condition then X else Y**.
For more information, see [IF Statements](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/if-statements-in-formulas.md). |
> **Note:** You can preview the formula in the top bar:
>
> the shows formula preview bar in lucanet xp&a displaying formula "= sum( revenue this month )" for "p&l with multiple entities and fx (cloned)" row. icon
> Preview a formula
## Adding a Comment to a Formula in Lucanet xP&A
You can add **comments** to your formulas in Lucanet xP&A with a **double slash (//)**. Everything between the double slash and the end of the line will be ignored by xP&A when calculating.
## Distributing Values Using Splashing in a Formula in Lucanet xP&A
When creating a variable that is broken down by dimensions in Lucanet xP&A, you can enter a value at the total level to propagate the values below.
By default, when entering the value, the number is repeated on all the leaf levels (lowest possible dimension item of this dimension). Using the Splashing function, you are able to propagate dimension items with the following distribution types: **Equal split, Pro-Rata, Repeat all leaves** (which is the default), or **Repeat.**
To apply splashing to a formula in Lucanet xP&A:
1. Enter the total value on the total (or branch) item in the formula bar.
The **Select splashing** drop-down list appears:
Splashing options
2. Select the type of splashing you want to apply.
An explanation of the splashing types can be found in the following sub-chapter.
3. Press **Enter** to apply the splashing to the underlying values.
> **Warning:** - If you apply splashing on cells that already contain values, these values will be overwritten by the newly distributed values.
> - Your latest selected splashing type is saved for the next entry. E.g. if you selected **Equal split**, this type of splashing will be used for the next splashing used by this user.
### Available Splashing Types
The following splashing types are available in Lucanet xP&A.
### Equal split
You can use **Equal split** to evenly distribute a value to each level.
The total amount will be equal to the entered number. If you have multiple levels, the value will first be distributed between the higher levels and then proportionally across all the items below.
**Example** after entering **800** on the total level:
Example for 'Equal split'
### Pro-Rata
You can use **Pro-Rata** to distribute values across each level proportionally to their current value.
**Example**:
The following example shows dimension items that already have values:
Example before 'Pro-Rata' is applied
After entering **800** on the total level and applying **Pro-Rata** splashing, the values are distributed as follows:
Example after 'Pro-Rata' is applied
### Repeat all leaves
You can use **Repeat all leaves** to repeat the entered value on each leaf level. **Repeat all leaves** is the default setting for value distribution.
**Example** after entering **800** on the total level:
Example for 'Repeat all leaves"
### Repeat
You can use **Repeat** to repeat the value on the 1st level, and then evenly distribute the value to the nesting levels.
**Example** after entering **800** on the total level:
Example for 'Repeat'
---
---
title: "Creating and Editing Variables"
description: "Variables are the building blocks of your models. If you're a spreadsheet user, you can think of them a bit like spreadsheet cells. If you're a programmer, you can think of them as, well, variables.\nYou can define a variable using a formula. Formulas let you work with numbers, ranges, and other variables."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables
language: en
last_updated: 2026-07-23
---
# Creating and Editing Variables in Lucanet xP&A
## Overview
Variables are the building blocks of your models in Lucanet xP&A (Extended Planning & Analysis). If you're a spreadsheet user, you can think of them a bit like spreadsheet cells. If you're a programmer, you can think of them as, well, variables.
You can define a variable in xP&A using a [formula](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas.md). Formulas let you work with numbers, ranges, and other variables.
This article contains the following chapters on creating and editing variables in xP&A:
- [Aggregation Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md): xP&A has three types of aggregation functions that determine how a variable 'rolls up' Dimensions, Time, and Data respectively.
- [Creating Variables Using AI](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/creating-variables-using-AI.md): xP&A offers different options for AI assistance when creating new variables. AI can be used to suggest new variables to be added to your model.
- [Moving Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/moving-variables.md): You can move variables within a model, as well as between models.
- [Referencing Variables From Linked Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models.md): Instead of a single model with all of your variables and formulas, you can structure your work into separate, smaller models. Once linked, you can reference variables between them.
- [Using Relative Time for Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/relative-time-for-variables.md): Sometimes variables do not refer to specific calendar time steps of your model (Jan 2022, Feb 2022) but refer to relative time (Month 1, Month 2).
- [Using Groups](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-groups.md): Groups are sets of variables within sections. You can also create nested groups simply by creating a group under an existing group.
- [Using Sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md): Variables can be organized into several Sections in the spreadsheet view.
## Creating a Variable in xP&A
To create a variable in xP&A:
1. Click **New Variable** at the end of a section.
Creating a new variable
2. The following drop-down menu is displayed:
Drop-down menu for a new variable
3. Do one of the following:
- **Create a new variable**: If you select this option, enter the name of the new variable in the input field.
- **Create from data**: Creates a new variable from a data item. If you select this option, you can first select the desired data source and then the desired variable. For more information on this topic, see [Linking Variables to Integrated Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md).
- **Import variable**: Reference a variable from a different model. If you select this option, you can first select the desired model and then the desired variable.
4. If you have defined a new variable, you can then specify its [format type](#main-format-types-in-xpa) by clicking on the edit icon or the icon to the left of the variable name:
Choosing a data type for a variable
## Main Format Types in xP&A
There are five main format types for variables in xP&A: **Number**, **Currency**, **Date**, **Percent**, and **Boolean**.
| Option | Description |
|---|---|
| **Number** | For quantities that aren't percentages or currencies.
**Note:** Number formatting (i.e. the decimal and thousands separators) follows your platform-wide formatting preferences which you can define in your user settings at the bottom left of the main menu. (See [Formatting Preferences](https://support.lucanet.com/en/documentation/getting-started/basic-configuration.md#configuring-the-date-and-number-format)).
|
| **Date** | The number will be formatted as a date. You can enter the date as `date(yyyy,mm,dd)` or as `date(yyyy,mm)`. |
| **Currency $** | Choose a specific currency (e.g. USD), or select **Custom** if the currency is not listed (e.g. cryptocurrencies). The currency symbol for common currencies is pre-set from the currency you select (e.g. $ for USD), but you can manually change the prefix/suffix.
**Note:** To learn more about Currency and how xP&A handles FX conversion, see [Using Currency and Currency Translation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/currency---fx-conversion.md). |
| **Percent %** | This expects the variable's value to be a decimal.
**Example**: 0.5 will be displayed as 50%. You can also enter directly as "50%". |
| **Boolean** | A variable that can be True or False (1 or 0), displayed as a checkbox/toggle. |
## Using Advanced Formatting Options in xP&A
In addition to the standard formats, [advanced formats](#advanced-formatting-options-in-xpa) can also be assigned to a variable in xP&A. Proceed as follows to use the advanced formats:
1. Click the edit icon to open the context menu.
2. Click **Format**.
Context menu 'Format'
3. The context menu is displayed as follows:
Advanced format options
4. Choose the desired option (see [Advanced formatting options](#advanced-formatting-options-in-xpa)).
## Advanced Formatting Options in xP&A
The following advanced formatting options are available in the **Format** context menu in xP&A:
| Option | Description |
|---------|---------|
| Human-readable | 1,000 -> 1k, 1,000,000 -> 1m, etc. Human readable is automatically on. |
| Comma separators | Comma separators, i.e. 1000 -> 1,000, 10000 -> 10,000, etc. Comma separators are automatically on. |
| Zero as | Displays cells with 0 values as -, making it easy to spot cells that have non-zero numbers. |
| Negatives | Accounting negatives i.e. ($100,000) not -$100,000 Red negatives i.e. -$100,000 or both ($100,000) |
| Precision | Automatic, or specify the number of decimal places or significant figures. |
| Magnitude | Automatic (as entered), or specify the 'unit' (thousand, lakh, million, crore, billion, trillion) you want to display the value in. For example, if you entered 100 but format the display as 'thousand', this will be 0.1k. |
| Relative time | Activate to use relative time for the variable. For more information, see [Relative Time for Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/relative-time-for-variables.md). |
| Lower is better | Activate if **in comparisons** values of the variable shall be displayed in **green** if they are lower than the values they are compared with. |
## Adding a Custom Prefix and/or Suffix (Custom Units) to a Variable in xP&A
You can set custom unit format for your variables in xP&A, and set whether that unit is displayed before or after the number (prefix vs. suffix).
To add a prefix and/or a suffix in xP&A:
1. Click the edit icon to open the context menu.
2. If necessary, use the drop-down menu to switch to prefix or suffix.
Add suffix and/or prefix to a variable
3. Enter the desired prefix or suffix in the input field.
This gives you ultimate flexibility to visually distinguish the units of variables in your models (e.g. currencies, earnings multiples, ratios, time units etc). Note that custom units are purely visual and do not affect calculations whatsoever.
Examples of prefixes and suffixes
## Types of Variables in xP&A
There are three variable types used in formulas in xP&A, and they are distinguished by their colour.
**Blue variables** are variables that are coming from the existing model.
Variable that is coming from the existing model
**Green variables** are variables that are coming from a [linked model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md). If you hover over the variable you can see which model it is coming from.
Variable that is coming from a linked model
**Purple variables** are xP&A's special [helper variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md), e.g. today, none, date / timestep, cohort.
Helper variable in xP&A
---
---
title: "Creating and Executing the Data Import into CFP"
description: "Once the script, the data source, and the assignment table to be used for the import have been created, you can create and execute the actual import and assignment of data in CFP."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-executing-the-data-import-into-CFP
language: en
last_updated: 2026-05-28
---
# Creating and Executing the Data Import from xP&A into CFP
## Overview
Once the script, the data source, and the assignment table to be used for the import have been created, you can create and execute the actual import and assignment of xP&A data in Consolidation & Financial Planning (CFP).
> **Note:** **Note for customers who still use Lucanet.Financial Client**
>
> You can either perform this step in the Lucanet CFO Solution Platform or in Lucanet.Financial Client. The data import will be visible and editable in both systems, no matter where you created it.
## Creating a Data Import in CFP
To create a data import in CFP:
1. Choose the command **Create | Data import** from the context menu of the **Data imports** root folder or a data import folder.
Creating a data import
2. Enter a name for the data import in the **Create data import** dialog and click **Save**.
The data import is created. The **detail view** of the data import is displayed as follows:
Detail view of a data import
3. Configure the data import (see section [Configuring the Data Import](#configuring-the-data-import)).
4. Import the data (see section [Executing the Data Import](#executing-the-data-import)).
## Configuring the Data Import in CFP
Click **Edit** to configure the data import. The following options are available in the detail view of a data import:
| Option | Description |
|---------|---------|
| Name | Name of the data import |
| Data source | The data source to be used |
| Configure | Opens the dialog with the properties of the data source. Used to check or change the **data source**(see chapter [Creating and Configuring the Data Source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md)). |
| Assignment table | The **assignment table** to be used. |
## Executing the Data Import in CFP
To execute the data import in CFP:
1. Click **1\. Import**. The **Configuration** dialog is displayed:
Dialog for the configuration of the import parameters
2. Choose the following to be used for the import:
- **Import type**
- **Fiscal year**
- **Accounting period**
3. If necessary, you can open the tab with the script name to adjust the [configuration of the data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md) before you execute the import.
Lucanet recommends to make these settings in the data source directly to avoid configuring the settings every time you execute a data import.
4. Click **Save**. If there are any missing assignments, these assignments will be displayed in the detail view of the import:
Detail view with the display of missing assignments
5. Click **2\. Assign**. The **assignments** are displayed, for example as follows:
Assignment table with missing assignments
6. Check the assignments and, if necessary, edit any missing assignments. For a detailed instruction on how to assign data, see [Assigning Data](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)).
7. Save the data import by clicking **3\. Save**.
> **Warning:** Every newly-created data import can only be saved when the import has been successfully performed and all elements have been assigned so that debit = credit is guaranteed in the general ledger (assets side = equity and liabilities side).
> **Note:** As soon as a data import has been successfully saved, the data of the created postings are displayed on the **Postings** tab. You can open the details of each posting by clicking the corresponding link in the **Posting** column.
>
> Furthermore, the **data source** and **assignment table** used for this import can be accessed via a link in the general properties of the data import.
>
> the shows postings tab of an import of xp&a data. highlighted is 'postings' column icon
> Postings created by the import from xP&A
---
---
title: "Creating Variables Using AI"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/creating-variables-using-AI
language: en
last_updated: 2026-05-01
---
# Creating Variables Using AI in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) offers different options for AI assistance when creating new variables. AI can be used to suggest new variables to be added to your model. It comes up with up to 5 suggestions for names and formulas completely on its own, including adding new hardcoded assumptions to then be used in its own calculations.
You can enable the AI assistance in xP&A at model level or when creating new variables.
**How it works**
Based on the variables that you have in your model, AI makes suggestions for your next variable. The suggestions are based on names of the variables and on the formulas you are already using.
## Available AI Options in xP&A
The following options to use AI assistance for creating new variables in xP&A are available:
### Ask AI
With the **Ask AI** menu in xP&A, you can benefit from two different AI functionalities:
**Suggest variables**
With this option, you can ask AI to generate **one-off suggestions** for new variables based on your model.
To use it, click on the **Ask AI** button at the top of the spreadsheet in xP&A and select **Suggest variables**. The AI-suggested variables will appear in the **Inputs** section:
Suggest variables in the 'Ask AI' menu
**Prompt AI**
With this option, you can directly interact with the AI, asking for help with setting up certain calculations and analysis. The AI then suggests the variables typically used for these calculations.
To use it, click on the **Ask AI** button at the top of the spreadsheet in xP&A and select **Prompt AI.** Enter your prompt in the text field and click **Submit**. The AI-suggested variables will appear in the **Inputs** section:
Prompt AI in the 'Ask AI' menu
### Vibe Mode
With this option, you can **automatically generate suggestions** for new variables as you work on a model in xP&A.
To use it, open the model settings and activate the option **Enable Vibe Mode:**
'Enable Vibe Mode' option
## Accepting or Rejecting AI Suggestions in xP&A
Once AI has suggested new variables for your model in xP&A, you can **accept** or **reject** these suggestions.
You can choose to accept or reject them:
- **Individually** right behind the suggested variable name
- **In bulk** at the bottom of the spreadsheet
In addition, you can click **Retry** to have AI suggest other variables.
Accept or reject suggestions
---
---
title: "Defining Database Queries"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system/defining-database-queries
language: en
last_updated: 2026-05-01
---
# Defining Database Queries in Lucanet xP&A
## Overview
Database queries are used to define which data is pulled in from your **BI/Database system** into Lucanet xP&A (Extended Planning & Analysis). They are entered during the set-up process of the integration (see individual set-up instructions for each system) and need to be structured in a certain way.
In this chapter we explain how a database query is defined and what needs to be considered in regards to linked dimensions that are queried.
## Defining a Query in xP&A
**Rules**:
- A query starts with **select**.
- A query must return a **date column.**
- A query must return at least one **value column** for the **variables** (which can be numbers or dates).
- A query can return optional columns for dimensions, dimension mappings, or cohorts.
- Linked dimensions must be included in the following form **_\`from dimension > to dimension\`_** (using backticks)
For more details on linked dimensions, see [Linking dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md#linking-dimensions) and the following chapter _Limitations and Workarounds for Querying Linked Dimensions_.
- A query must contain **from** followed by the _name of the table_ the data is to be extracted from.
**Example query**:
**select** _date, users, country, region as "country > region"_ **from** _users_table_
**Explanation**:
- The data is queried from the **users_table**.
- The first column (**date**) has the dates of the transactions (timestamp or date type).
- The second column (**users**) contains the values of the "users" variable (number type).
- The third column (**country**) is a dimension column, the users are broken down by country (string).
- The fourth column ( _**region as "country > region"**_) is a dimension mapping. The region is not an independent dimension, but the countries are assigned to regions.
**Example query result:**
Example query result
> **Note:** **Querying Constant Values**
>
> If you only want to import constant values (no time series), the date column can be null. For example:
>
> **select** _null as date, price, plan_name_ **from** _price_table_
## Limitations and Workarounds for Querying Linked Dimensions in xP&A
When working with queries, you can only create **one level of linked dimensions (mappings)** per query. This means you can establish multiple direct relationships from a single source dimension, but you cannot create chained relationships within the same query.
**Allowed in one query:**
- A → B
- A → C
- A → D
**Not allowed in one query:**
- A → B and B → C simultaneously
**Workaround Solution**
To handle multi-level relationships, you need to create **two separate queries**:
**Query 1**: Define the initial mapping relationship
**Query 2**: Define the secondary mapping relationship using a fictional value
## Example: Lease Contracts and Vehicle Types
Consider a scenario where:
- Lease contracts are tied to specific vehicles/license plate (A → B)
- Vehicles are linked to vehicle types (B → C)
- The relationship isn't always 1:1 due to vehicles appearing in multiple contracts
The following queries would be used:
**Query 1: Lease Contract to License Plate Mapping**
Query 1
**Query 2: License Plate to Vehicle Type Mapping**
Query 2
**Explanation:**
- The second query uses a **fictional value** (in this case, 1) to satisfy query requirements which will not be used in any model.
- Both queries use **null** as date as a placeholder.
- The mapping syntax uses **>** to indicate the relationship direction.
- This approach maintains data integrity while working within the system's constraints.
---
---
title: "Different Time Granularities"
description: "xP&A allows you to have different time granularities in your models and visuals. Granularity refers to the level of detail in which data of a model are organized. Adjusting granularity affects how detailed the data representation is, with finer granularity providing more detailed information and coarser granularity offering a broader overview."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/time-granularities
language: en
last_updated: 2026-05-01
---
# Different Time Granularities in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) allows you to have different time granularities in your models and visuals. Granularity refers to the **level of detail** in which data of a model are organized. Adjusting granularity affects how detailed the data representation is, with finer granularity providing more detailed information and coarser granularity offering a broader overview.
If you have different time granularities in your models and/or visuals, this article provides information on how xP&A determines how the more granular values are 'rolled up' into the higher-level granularity (e.g. weekly to monthly).
## Rolling Up Lower-Level Granularities to Higher-Level Granularities in xP&A
**Weeks -> months, quarters or years**
By default, in xP&A, a week is rolled up to the month, quarter, or year based off the start date of the week.
**Example**: If I have a week that starts on 30th May, 2022, the full week will count towards the May month, despite 5/7 days of that week being in the month of June.
It is possible to have "custom calendars", i.e. to tell xP&A how you want each week to be rolled up into months. This is useful, for example, if you follow 4/4/5 accounting cycles. At the moment custom calendars are not a user-facing setting, but if you would like to turn one on, please contact us via live-chat in-app.
**Days -> weeks**
By default, in xP&A, days are rolled up into weeks, starting from the start day of the model.
**Example**: If the first day of the model is 1st July, 2022, then week one is the 7 days beginning 1st July, 2022.
**Days -> months**
By default, in xP&A, daily models are rolled up into months based on the month that the day falls into (as you would expect). So 30th May, 2022 rolls up into May.
> **Note:** - The default logic xP&A uses is to sum the values from the lower level granularity (e.g. weekly) to roll-up into the higher-level granularity (e.g. monthly), but you can choose other options in the **Time Aggregation** setting for each variable (e.g. Average, Final). For more information, see [Aggregation Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md).
> - The "roll-up" logic described below applies to:
> - **Visuals** (e.g. how weekly data is rolled up to months or quarters in a table or chart)
> - **Models** of different granularities (e.g. how a weekly model translates to a monthly model).
## Rolling Down Higher-Level Granularities to Lower-Level Granularities in xP&A
Translating higher-level granularities to lower-level granularities in xP&A is done by division. So to get an annual variable of "120" into a monthly model, 120 is divided by 12, to get a monthly value of 120/12 = 10.
**Note**: This is only relevant for bringing variables between different time-granularity models, this transformation is not possible on charts/tables/other visuals.
---
---
title: "Dimensions, Variables, and Formulas"
description: "This article provides step-by-step instructions on how to add, modify, and remove dimension breakdowns from variables in a data model. It further explores the application of formulas across dimensions, offering the ability to override and manage formulas for specific dimension items. Additionally, it covers techniques for sorting and filtering dimension data to enhance the organization and presentation"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas
language: en
last_updated: 2026-05-01
---
# Dimensions, Variables, and Formulas in Lucanet xP&A
## Overview
This article provides step-by-step instructions on how to add, modify, and remove dimension breakdowns from variables in a data model in Lucanet xP&A (Extended Planning & Analysis). It further explores the application of formulas across dimensions, offering the ability to override and manage formulas for specific dimension items. Additionally, it covers techniques for sorting and filtering dimension data to enhance the organization and presentation.
## Breaking Down a Variable by Dimensions in xP&A
To add a dimension breakdown to a variable in xP&A, hover over a variable and click **Dimensions:**
Adding a dimension to a variable
If the variable already has a dimension breakdown in xP&A, it will be coming:
- From its [connected data item(s)](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) (if the dimension exists in the data)
- From its formula (if the formula refers to a variable that has the dimension)
Variable that already has a dimension breakdown
> **Note:** **What if I want to remove the dimension breakdown?**
>
> You can remove the dimension breakdown in xP&A by clicking the **-** next to the dimension after clicking the **Dimensions** button. However, if the dimension is coming from data, or from the formula, follow the steps below:
>
> - If your **variable is connected to data**, and the dimension is coming from data, you can either [aggregate the dimension](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md) in the advanced data options on the variable, or you can **remove the dimension** from the model (from the left sidebar), which will remove the breakdown from all variables that had that dimension.
> - If your **variable is inheriting the dimension from its formula** (e.g. if it refers to a dimensional variable), you can [aggregate the dimension away in the dimension modifier](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md).
You can also create new variables in xP&A when viewing a dimension in the bottom-panel of the spreadsheet (once you open the dimension from the left-hand sidebar).
Click the **+** in the far-right column, and create a new dimensional variable by choosing its format from the drop-down (e.g. Currency, %).
Addin new variable from the bottom panel
## Dimension Breakdowns and Variable Formulas in xP&A
When a variable is broken down by a dimension in xP&A, and you set a formula at the top (aggregate) row, it will be **automatically applied in the same way across all dimension items**. This is powerful as it means you only have to set the formula once.
Formula in the top row
If, however, you wish to set a different formula/value for certain dimension items, simply edit the formula for that particular row/cell. These edits will show up as an **Override**, and you can easily reset the override (back to the default formula), by clicking the reset icon **Reset override** or **Reset row**.
Resetting a row
If you do not have a top (aggregate) row formula or value, then you have no "default", so different formulas or values for dimension item rows or cells are not considered **Overrides**.
> **Note:** **FAQ regarding the Override function**
>
> - **Question**: What if I have 2+ dimensions on a variable (e.g. **Country** and then **Product**), and then override for one of the **Countries**(e.g. **New Zealand**).
>
> **Answer**: All the **Products** under **New Zealand** will now take their formula from the override for **New Zealand** (not the top-level/aggregate row of the variable).
>
> - **Question**: How do I override an entire dimension item row?
>
> **Answer**: Either edit the formula in the formula column (which sets the formula for all months or time steps), or override a cell and then drag/fill-right that formula to all other cells in the row.
> - **Question**: Are different formulas/values in specific time step columns of the top-level/aggregate row of the variable considered overrides?
>
> **Answer**: No, this just serves as a different formula for that time step.
> - **Question**: Can you override data?
>
> **Answer**: No, [data always takes precedence](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md) whenever it is present. It cannot be overridden.
## Re-Ordering Dimensions on a Variable in xP&A
You can easily **drag to reorder** the dimension breakdown on a variable in xP&A.
For example, if you have a variable broken down by **Department** and then **Region**, you can swap the order around so it is **Region** and then **Department** instead. This will not change any calculations, it will just change the dimension ordering that you see when you expand the variable.
Drag to change the order
## Variable Modifiers: Dimensions in xP&A
Dimension modifiers allow you to slice and dice variables within formulas, using the related **dimensions** and **dimension items**. You can:
- Group by linked dimensions
- Filter by dimension items
- Aggregate away dimensions
For a deep-dive, see: [Dimension modifiers](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md#dimension-modifiers-in-lucanet-xpa).
## Referencing Dimension Items Within Formulas in xP&A
You can use your model's dimensions and dimension items in formulas in xP&A as follows:
- You can access the number of dimension items by clicking on the **three dots menu** and selecting **Size**:
Displaying the number of dimension Items
- You can also use dimensions in if-statements (e.g. to dynamically define a variable's dimensional values without requiring a formula for each dimension item).
Dimensions in IF Statements
## Sorting and Filtering Dimensions in the Bottom Panel in xP&A
You can also dynamically filter and sort dimensions in xP&A in the bottom panel (after opening the dimension from the overview on the left).
You can sort either by clicking **Sort Filter**, or from the column header directly. If you sort the dimension items, you have the option to save the order, in which case it is applied to any variables in the models that have that dimension applied.
Sort and Filter dimension items
## Sorting by Dimension Item Value on a Variable in xP&A
You can also sort by dimension item value on a variable in the spreadsheet in xP&A. For instance, if you have **Spend** broken down by **Vendor**, you can quickly sort the **Spend** variable so the breakdown is from biggest to smallest vendor.
Choose to sort based off the values for the [Entire Model Period](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md), or just the [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), and choose **Descending** or **Ascending** order ( **Descending** is the default).
Sort dimension items
Find this setting in the **edit** menu on a variable.
To remove the sort, just click the **x** next to **Entire model period/Last actual date**.
> **Note:** Note that we use the [Time Aggregation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md) setting to determine how values are summed up for the **entire model period**. The default is **Sum**, but if you have set a Time aggregation setting of **Final**, for example, we will sort using only the final value in the entire model period.
---
---
title: "Drilling Down on Integrated Data"
description: "If you have data sources that contain underlying data (e.g. transactions from a source connected source system like Xero, QuickBooks Online, NetSuite, Google Sheets or a CSV import in transaction format), xP&A allows you to drill-down into the underlying detail, from any variables connected directly to that data.\n\nDrill-downs are possible from the dashboard or from the spreadsheet of a model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data
language: en
last_updated: 2026-05-01
---
# Drilling Down on Integrated Data in Lucanet xP&A
## Overview
If you have data sources that contain underlying data (e.g. transactions from a connected source system like **Xero, QuickBooks Online, NetSuite**, **Google Sheets** or a CSV import in transaction format), Lucanet xP&A (Extended Planning & Analysis) allows you to **drill-down into the underlying detail**, from any variables connected directly to that data.
Drill-downs are possible from the **spreadsheet of a model**, from the **'Data' workspace**, or from the **dashboard.**
> **Warning:** The drill-down function:
>
> - Works only on the variables that actually are connected to data items, see [Linking Variables to Integrated Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md)
> - Does not work on [linked model variables, imported variables, or imported tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models.md)
> - Does not work on downstream variables that refer to the [data connected variable](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) in their formula
## Drilling Down From the 'Spreadsheet' in xP&A
To drill-down on integrated data from the spreadsheet:
1. In the **Data** column, click the data icon for the desired data source.
2. Click the **expand arrow icon** behind the data item for which you would like to open the drill-down:
The 'Expand arrow' icon
3. In the **Data** dialog that is displayed, right-click on the value for which you would like to open and choose **Drill-down** from the context menu:
Opening the drill-down dialog
The drill-down is displayed as follows, for example:
The 'Drill-down' dialog
> **Warning:** To drill down on integrated data in the spreadsheet, a user needs [edit or above access](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) permissions to the respective model.
## Drilling Down From the 'Data' Workspace in xP&A
To drill-down on integrated data from the Data workspace: by clicking on the **data icon** in the **Data** column, hovering over a **row with a data icon**, and clicking on the **expand arrows**:
1. Open the desired data source from the **Data** workspace.
2. Navigate to the **Data** tab.
3. Right-click on the cell for which you would like to open the drill-down and choose **Drill-down** from the context menu:
Opening the 'Drill-down' dialog
4. The drill-down is displayed as follows, for example:
The 'Drill-down' dialog
> **Warning:** To drill down on integrated data in the spreadsheet, a user needs [edit or above access](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) permissions to the respective model.
## Drilling Down From the Dashboard in xP&A
You can also enable drill-down in [Tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md) and [Bar charts](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md) on the **Display** tab when editing a chart or table.
Drill-down from the dashboard
> **Warning:** - This function is **deactivated by default** due to the potential sensitivity of underlying data.
> - To drill down on integrated data in the spreadsheet, a user needs [edit or above access](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) permissions to the respective model.
> - Users with [view access](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) to the model will only be able to drill-down on the dashboard if the drill-down option has been enabled on a table.
> - Even if you have enabled the [read-only spreadsheet on the dashboard](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md), drill-down will not be available there.
## Sorting and Filtering the Transaction List in xP&A
Use the **Filters** panel on the right-hand side of the **Drill-down** dialog to filter the list of transactions (e.g. based on transaction memos, GL codes, values, dates).
You can also click the column headers to sort in ascending/descending order.
Filtering transactions
---
---
title: "Editing the Model Settings"
description: "For every model, you can define certain time settings, which include the granularity, the date range, and the last actual date for your model. \nIn addition, you can specify the use of relative dates and fiscal years and how you want to highlight certain time spans in your views."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings
language: en
last_updated: 2026-05-01
---
# Editing the Model Settings in Lucanet xP&A
## Overview
For every model in Lucanet xP&A (Extended Planning & Analysis), you can define certain time settings, which include the **granularity**, the **date range**, and the **last actual date** for your model.
In addition, you can specify the use of **relative dates** and **fiscal years** and how you want to highlight certain time spans in your views.
## Editing the Model Settings in xP&A
To edit the settings for a model in xP&A:
1. Click the gear icon to open the **Model settings**.
2. Adjust the options as necessary.
For a description of the options see the following sections.
3. In the **Apply Changes** dialog that appears, choose if you want to apply the changes **to the current model only** or **to all linked models**.
## Options in xP&A
The following options are available for model settings:
The model settings
| Option | Description |
|---|---|
| **AI features** | Here, you can **enable vibe mode**. Vibe mode turns on automatic AI suggestions for new variables as you build your model, without needing to be manually triggered each time. For more information on this topic, see [Creating Variables Using AI](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/creating-variables-using-AI.md). |
| **Exchange rates** | Here, you can configure the **exchange rates** that are used for **currency translation**. For more information on this topic, see [Using Currency and Currency Translation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/currency---fx-conversion.md). |
| **Time settings** | Here, you can define certain time settings, which include the **granularity**, the **date range**, and the **last actual date** for your model. For more information on this topic, see [Working With Time](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md). |
| **Export and download** | Here, you can export your model(s) out of xP&A into a variety of formats and file types. This is useful, for example, if you want to share your model with people outside of xP&A or to save a local or offline copy of your model and its data. For more information on this topic, see [Exporting a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/exporting-a-model.md). |
| **Model options** | Here, you can define in the model options:
• The **Default Uncertainty Interval** used for your planning throughout xP&A. • If you want to **Hide empty dimension rows**, i.e. the rows that do not contain any data for a particular [dimension item](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md). • The **First cohort name** used for [cohort modeling](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/common-formulas-.md). |
| **Calculation** | Here, you can specify, if you want the data of your model to be **recomputed manually**. Once you activate this option, the data will be recalculated. |
| **Last edited** | Here, you can see **who** last edited the model and **when**. |
| **Audit logs** | Here, you can open the audit logs, which are a **model-by-model running history** of who has made what edits (and when) to a model's variables, dimensions, visuals, or data. For more information on this topic, see [Viewing the Audit Logs of a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/viewing-the-audit-logs.md). |
---
---
title: "Exporting a Model"
description: "You can export your model(s) out of Lucanet xP&A into a variety of formats and file types."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/exporting-a-model
language: en
last_updated: 2026-05-01
---
# Exporting a Model in Lucanet xP&A
## Overview
You can export your model(s) out of Lucanet xP&A (Extended Planning & Analysis) into a variety of formats and file types. This is useful for a variety of situations, for example:
- Sharing your model with people outside of xP&A
- For using the model data or outputs in systems outside of xP&A
- Saving a local or offline copy of your model and its data
## Exporting a Model in xP&A
To export a model in xP&A:
1. Click the **Settings** button the settings icon and navigate to the **Export and download** section.
2. Click **+** to create a new export. The **New export** dialog is displayed.
3. Configure the **Export definition**, **Target**, and **Content** steps as described below. Click **Next** to move from one step to the next.
4. Once all three steps are configured, click **Create export.**
### 'Export Definition' Step
View of the 'Export definition' step in the 'New export' dialog
The following options must be configured in the **Export definition** step:
| Option | Description |
|---|---|
| **Name** | Name of your export |
| **Export definition** | • **Raw** values: This format is useful for inputting into another system (e.g. data warehouse) for further manipulation, or creating pivot tables from. • **Formatted** values: This format is organized like your xP&A model, with time as columns and variables as rows. |
### 'Target' Step
View of the 'Target' step in the 'New export' dialog
The following options must be configured in the **Target** step:
| Option | Description |
|---|---|
| **Download** | Use this option to export a **download file** and choose the **file format**. If you export **formatted values**, the output format is always an **Excel** file. If you export **raw values**, you can choose between **CSV, MS Excel, Google Sheets**, or **Parquet** (a compressed file format designed for fast querying and efficient storage, especially for big data volumes). |
| **External sync** | Use this option if you want the export to be **synced** with an external system and choose the **target system** and the **parameters** for the synchronization. In addition, specify the **export schedule**, i.e. if you want to sync the export one-time only or regularly on a specific day and time.
**Note:** The **External sync** option is only available for **raw** value exports and for the following target systems: **BigQuery, Databricks, MySQL**, **Redshift**, **Postgres** and **Snowflake**. |
### 'Content' Step
View of the 'Content' step in the 'New export' dialog
The following options must be configured in the **Content** step:
| Option | Description |
|---|---|
| **Content** | Choose the **content** to be exported: • **All values**: Export **all values**. • **View**: Filter values via a **view** (you will need to exit the export modal if you need to create a view). • **Version**: Choose a specific **version** to be exported. |
| **Include linked models** | Choose if you want to **include linked models** in the export: • **All**: All linked models are exported. • **Customize**: Choose the linked models you want to export. |
| **Date range** | Choose the **date range** to export: • **Model time dimension**: Will export all dates in the model. • **Model time filter**: Will limit the exported dates to the currently selected time filter. |
| **Skip blank and zero values** | Exclude blank values and values close to zero (smaller than 1E-6) from the export. |
| **Export linked dimensions** | Choose if you want to include the model's linked dimensions in the export.
**Note:** This option is only available for **raw** value exports and is disabled if the model has no linked dimensions to export. |
| **Additionally exported columns** | Additional columns to include in your export. By default, **values**, **variable names**, and **dates** are exported. • **Group Name**: Includes the name of the group the variable belongs to. • **Percentile**: Activate this option if you use **values with uncertainty** (e.g. "10 to 30") in your models and want to see the full distribution for each variable in the export. • **Scenario**: If you disable this column, only values from the default scenario are exported. • **Section Name**: Includes the name of the section the variable belongs to. • **Variable ID**: Represents xP&A's internal ID of the variable. While a variable's name can be changed throughout the lifetime of a model, its variable ID remains constant. • **Cell Location**: Provides URLs linking each exported data point to its origin cell. • **Currency**: Includes the currency ISO code associated with the variable (if the variable is formatted as a currency). |
---
---
title: "Extended Planning & Analysis (xP&A)"
description: "Modeling, forecasting, planning - Lucanet xP&A enables your business with a 360° view of planning and analysis data from a single source of truth."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis
language: en
last_updated: 2026-05-30
---
# xP&A - Extended Planning and Analysis
Modeling, forecasting, planning - Lucanet xP&A enables your business with a 360° view of planning and analysis data from a single source of truth.
The Lucanet xP&A [solution](https://support.lucanet.com/en/documentation/glossary.md#solution) offers you:
- **Single source of truth**: A single, real-time view of financial and operational data keeps everyone aligned and accountable.
- **Smarter planning**: Intuitive modeling and insights help teams move faster, optimize performance, and spot new opportunities.
- **Better collaboration**: Shared access to reliable data improves teamwork, forecasting, and risk management.
Dashboard view in Lucanet xP&A
[Request demo](https://www.lucanet.com/en/request-demo/)
> **Note:** - Do you already use the Lucanet CFO Solution Platform and would like to use xP&A as well? Speak to your Lucanet contact about an xP&A license or get in touch with us via [Contact](https://www.lucanet.com/en/contact/).
> - Maybe you’re not a Lucanet customer yet, but you’d like to find out more about our solutions? If so, write to us at [Contact](https://www.lucanet.com/en/contact).
## Your First Steps with Lucanet xP&A
Our instructions will help you get started with Lucanet xP&A in next to no time:
- [Basic Concepts and Elements](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/basic-concepts-and-Elements.md)
- [All Steps at a Glance](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/process-description-xpa.md)
- [Creating a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md)
---
---
title: "Functions for Formulas"
description: "In the following tables you will find functions that you can use in Lucanet xP&A formulas."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/functions
language: en
last_updated: 2026-05-01
---
# Functions for Formulas in Lucanet xP&A
## Overview
In the following tables you will find functions that you can use in Lucanet xP&A (Extended Planning & Analysis) formulas.
## Available Formulas in Lucanet xP&A
The following functions are available for formulas in Lucanet xP&A:
## Math Functions in Lucanet xP&A
The following math functions are available for formulas in Lucanet xP&A:
| Function | Description |
|---------|---------|
| abs | The absolute value of a number |
| avg | The arithmetic mean (average) of the inputs. Can also be used as **avgif**. **Example**: avg(1, 2, 3) = 2 avg(if Var\[all\] % 2 = 0 then Var\[all\] else none) = avg of all even values |
| first_nonzero_value | The first value that is not zero or empty **Example**: first_nonzero_value(0,none,4,6) = 4 |
| log | Natural logarithm (base e) **Example**: log(e^2) = 2 |
| log10 | Common logarithm (base 10) **Example**: log10(100) = 2 |
| max | The highest of the given values **Example**: max(1, 2, 3) = 3; max(\[1, 2, 3\]) = 3 |
| min | The lowest of the given values **Example**: min(1, 2, 3) = 1; min(\[1, 2, 3\]) = 1 |
| mod | The remainder of a division.You can also use **mod** as "%" **Example**: mod(5, 2) = 1 5 % 2 = 1 recurrence every 4 months: if timeStep % 4 = 0 then 1 else 0 |
| reverse | Reverses the order of an array. **Example**: reverse(\[1, 2\]) = \[2, 1\] |
| round | Rounds the number to the closest integer. Optionally, you can specify the decimal places as the second argument. **Example**: round(2.3) = 2, round(2.5) = 3, round(2.26, 1) = 2.3 |
| rounddown | Rounds the number down, toward 0. Optionally, you can specify the decimal places as the second argument. **Example**: rounddown(2.8) = 2, rounddown(-2.8) = -2, rounddown(2.88, 1) = 2.8 |
| roundup | Rounds the number up, away from 0. Optionally, you can specify the decimal places as the second argument. **Example**: roundup(2.2) = 3, roundup(-2.2) = -3, roundup(2.22, 1) = 2.3 |
| signchange | Timestep on which the first sign change occurs **Example**: signchange(Var\[all\]) |
| spread | Spreads a value over a time period. **Example**: spread(New Customers\[0:t\], Payments\[0:t\]) For a more detailed example, see [Examples for Functions](#examples-for-functions-in-lucanet-xpa). |
| sqrt | Square root of a value **Example**: sqrt(4) = 2 |
| sum | The sum of the inputs. Can also be used as sumif or countif. **Example**: sum(1, 2, 3) = 6. sum(if Var\[all\] % 2 = 0 then Var\[all\] else 0) = sum of all even values |
| sumproduct | Multiplies two or more arrays together and returns the sum of products. **Example**: sumproduct(Var1\[all\], Var2\[all\]) |
| exp | Exponential function **Example**: exp(2) = e^2 |
## Time Functions in Lucanet xP&A
The following time functions are available for formulas in Lucanet xP&A:
| Function | Description |
|---------|---------|
| date | The timestep number of a date. Timesteps start with 0. **Example**: date(2021,12,24) = 11 in a monthly model that starts in Jan 2021 |
| month_from_date | Extracts the month of a date or timestep. **Example**: month_from_date( date(2021,12,24) ) = 12 |
| year_from_date | Extracts the year of a date or timestep. **Example**: year_from_date( date(2021,12,24) ) = 2021 |
## Financial Functions in Lucanet xP&A
The following financial functions are available for formulas in Lucanet xP&A:
| Function | Description |
|---------|---------|
| cumipmt | Cumulative interest paid. **Example**: cumipmt(rate, periods, value, start, end, type) |
| finance.AM | Amortization **Example**: finance.AM(principal, rate, period, yearOrMonth, payAtBeginning) |
| finance.CAGR | Compound annual growth rate **Example**: finance.CAGR(beginning value, ending value, number of periods) |
| finance.CI | Compound interest **Example**: finance.CI(rate, compoundings per period, principal, number of periods) |
| finance.DF | Discount factor (returns an array; must index array to obtain values -- to see all values of array, see working example above). **Example**: finance.DF(rate, number of periods)\[index\] |
| finance.FV | Future value **Example**: finance.FV(rate, nper, pmt, pv, type) |
| finance.IAR | Inflation-adjusted return **Example**: finance.IAR(investment return, inflation rate) |
| finance.irr | Internal rate of return. **Example**: finance.IRR(Cashflows\[all\], \[guess\]) For a more detailed example, see [Examples for Functions](#examples-for-functions-in-lucanet-xpa). |
| finance.LR | Leverage ratio **Example**: finance.LR(total liabilities, total debts, total income) |
| finance.NPV | Net present value **Example**: finance.NPV(rate, initial investment, cash flows\[all\]) For a more detailed example, see [Examples for Functions](#examples-for-functions-in-lucanet-xpa). |
| finance.PI | Profitability index **Example**: finance.PI(rate, initial investment, cash flows\[all\]) |
| finance.PMT | Payment for a loan based on constant payments and a constant interest rate **Example**: finance.PMT(fractional interest rate, number of payments, principal) |
| finance.PP | Payback period **Example**: finance.PP(number of periods, cash flows\[all\]) |
| finance.PV | Present value **Example**: finance.PV(rate, nper, pmt, \[fv\], \[type\]) |
| finance.R72 | Rule of 72 **Example**: finance.R72(rate) |
| finance.roi | Return on investment **Example**: finance.ROI(Cashflows\[all\]) |
| finance.WACC | Weighted average cost of capital **Example**: finance.WACC(market value of equity, market value of debt, cost of equity, cost of debt, tax rate) |
| finance.xirr | Internal rate of return for a schedule of cash flows **Example**: finance.xirr(\[-10,11\], \[0,12\], 12) = 10% For a more detailed example, see [Examples for Functions](#examples-for-functions-in-lucanet-xpa). |
| fv | Future value **Example**: v(rate, nper, pmt, pv, \[type\]) |
| fvifa | Future value interest factor of an annuity **Example**: fvifa(rate, nper) |
| ipmt | Interest portion of a given loan payment **Example**: ipmt(rate, per, nper, pv, \[fv\], \[type\]) |
| pmt | Periodic payment for a loan **Example**: pmt(rate, nper, pv, \[fv\], \[type\]) |
| ppmt | Principal portion of a given loan payment **Example**: ppmt(rate, per, nper, pv, \[fv\], \[type\]) |
| pv | Present value **Example**: pv(rate, nper, pmt, fv, \[type\]) |
| pvif | Present value interest factor **Example**: pvif(rate, nper) |
| rate | Interest rate per period of an annuity **Example**: rate(nper, pmt, pv, \[fv\], \[type\], \[guess\]) |
## Probability Functions in Lucanet xP&A
The following probability functions are available for formulas in Lucanet xP&A:
| Function | Description |
|---------|---------|
| beta | Beta distribution **Example**: beta(alpha, beta) |
| binomial | Binomial distribution **Example**: binomial(n, p) |
| cauchy | Cauchy distribution **Example**: cauchy(local, scale) |
| chisq | Chi-squared distribution **Example**: chisq(k) |
| exponential | Exponential distribution **Example**: exponential(rate) |
| gamma | Gamma distribution **Example**: gamma(shape, scale) |
| invgamma | Inverse-gamma distribution **Example**: invgamma(shape, scale) |
| lognormal | Log-normal distribution **Example**: lognormal(μ, σ^2) |
| lognormal_from | Log-normal distribution **Example**: lognormal_from_interval (from, to, confidence_percent) |
| normal | Normal distribution |
| normal_from | Normal distribution |
| pareto | Pareto distribution **Example**: pareto(min, alpha) |
| poisson | Poisson distribution **Example**: poisson(λ) |
| stdev | The standard deviation of an array **Example**: stdev(Var\[all\]) |
| triangle | Triangle distribution **Example**: triangle(from, to, confidence_percent) |
| uniform | Uniform distribution **Example**: uniform(from, to) |
| variance | The variance of an array **Example**: variance(Var\[all\]) |
## Other Functions in Lucanet xP&A
The following additional functions are available for formulas in Lucanet xP&A:
| Function | Description |
|---|---|
| **error** | Error to assert an invalid state
**Example**: error() |
| **flat_cohort_forecast** | Forecasts cohort data without the cohort dimension.
**Example**: flat_cohort_forecast(oldCohorts\[all\], newCohorts\[all\], retentionRates\[all\], lastDataDate, t, \[additionalChurn\]) |
| **forecast** | Forecasts your future inputs based on historical data using AI.
**Example**: forecast(timestep, past_values, growth_rate), where timestep is t and past_values references the variable with values.
**Notes:** • Make sure you select a time period that has at least 13 inputs for the most accurate results, e.g. 13 months of data. • growth_rate is optional. |
| **gaussian_ramp** | Ramps up a value over a time period in the shape of a gaussian bell curve.
**Example**: gaussian_ramp(timestep, date(2022,10), 2, 100) |
| **if_error** | If the first argument evaluates to an invalid number error, we return the second argument. Otherwise, we return the first argument.
**Example**: if_error(Y/X, Z) - useful where the denominator X is 0, and so the first argument would result in a divided by 0 (invalid number error) |
| **is_data** | Evaluates to 1 if argument is derived from a datasource, and otherwise to 0.
**Example**: is_data(Variable\[all\]) |
| **is_locked** | Evaluates to 1 if argument is a locked dimension item, and otherwise to 0.
**Example**: is_locked(dimensionitem) |
| **last_data_timestep** | Returns the last timestep that is derived from a datasource.
**Example**: last_data_timestep(Var\[all\]) |
| **logistic_ramp** | Ramps up a value over a time period in an S-shape (logistic function).
**Example**: logistic_ramp(timestep, date(2022,1), date(2022,10), 1.8, 100, 200) |
| **quadratic_ramp** | Ramps up a value quadratically over a time period.
**Example**: quadratic_ramp(timestep, date(2022,1), date(2022,10) \[startValue\], \[endValue\]) |
| **ramp** | Ramps up a value linearly over a time period.
**Example**: ramp(timestep, date(2022,1), date(2022,10), 100, 200) |
| **ramp_normalized** | A ramp with the cumulative sum of 1. Useful for distributing a fixed value over a time period.
**Example**: ramp_normalized(timestep, date(2022,1), date(2022,10)) |
## Examples for Functions in Lucanet xP&A
The following table provides some practical examples for selected functions in Lucanet xP&A:
#### Spread values in Lucanet xP&A
**Spread** is a powerful and flexible xP&A function. It allows you to spread a value, or a set of values, over a time period. You can think of it as similar in functionality to **sumproduct** in MS Excel, but more intuitive (and of course, more powerful).
Spread has two arguments:
- x - the value or set of values
- y - the amount you are spreading x by
##### Example:
If all new customers have to pay a $100 sign-up fee in their first month, and from the second month onwards they pay $10 per month for their subscription - you could calculate your monthly revenue using **spread**.
In this instance, your **x** would be your **new customers** each month, and the **y** amount you are spreading it by would be that **payment structure**.
In xP&A, this would look as follows:
Example for 'spread' function
#### Internal Rate of Return (IRR) in Lucanet xP&A
xP&A has lots of finance functions that you might know from MS Excel or Google Sheets - and they work very similar.
##### Example:
If you have a **Cash Flows** variable where the first value is the initial investment and the following values are the returns, you can calculate the IRR like this:
Example for 'finance.irr' function
#### Internal rate of return for a schedule of cash flows (XIRR) in Lucanet xP&A
XIRR is used in Lucanet xP&A when the cash flows are not periodic. That's why XIRR needs three arguments:
- The cashflows
- The time steps at which they occur
- The granularity (how many time steps fit into one year).
##### Example:
If you invest $10 in the first month and have a return of $6 after 10 months and another $6 after 12 months, your formula would look like this:
![Shows a formula in Lucanet xP&A: finance.xirr([-10,6,6], [0,10,12], 12).](_images/en/xirr-example.png)
Example for 'finance.xirr' function
#### Net Present Value (NPV) in Lucanet xP&A
Net Present Value (NPV) compares the money received in the future to an amount of money received today, while accounting for time and interest. The arguments of the function in Lucanet xP&A are:
- Rate in percent
- Cash flows
**Example**:
For a discount rate of 10%, an initial investment of 500 and cashflows of 200, 300 and 200 you can use the function like this: finance.npv(10, -500, 200, 300, 200).
Usually the cashflows are in a time series variable, in this case you can use the variable in the function:
Example for 'finance.npv' function
---
---
title: "Guideline for Exchanging Data Between xP&A and CFP"
description: "Data can be exchanged in both directions between Lucanet Consolidation & Financial Planning (CFP) and Lucanet xP&A (Extended Planning and Analysis). CFP provides actual data for planning in xP&A; modelled planning data can be transferred back from xP&A into CFP. \n\nThis guideline describes the end-to-end process and points to the detailed instructions for each step."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP
language: en
last_updated: 2026-05-28
---
# Guideline for Exchanging Data Between xP&A and Consolidation & Financial Planning
## Overview
Data can be exchanged in both directions between Lucanet Consolidation & Financial Planning (CFP) and Lucanet xP&A (Extended Planning & Analysis). CFP provides actual data for planning in xP&A; modelled planning data can be transferred back from xP&A into CFP.
This guideline describes the end-to-end process of exchanging data between xP&A and CFP, and points to the detailed instructions for each step.
## Prerequisites for Exchanging Data Between xP&A and CFP
Before starting, ensure your xP&A models are built with the following in mind:
| Prerequisite | Description |
|---------|---------|
| **Variables will be mapped to GL accounts** | Think about this upfront: The CFP assignment tables are used to map each output variable to the correct general ledger account. |
| **Entity dimension must be present** | Variables must be split by a dimension that can be mapped to CFP reporting entities or cost centers. Preferably, use the **Organization element** dimensions synced from CFP for a 1:1 match. Alternatively, a custom dimension can be used and mapped manually. |
| **Work with output sections in your model** | Create a dedicated section (e.g. "Sales outputs") containing only the variables you want to transfer back to CFP. This simplifies selection during [data source configuration](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md#scriptspecific-parameters-model-configuration-tab) and reduces maintenance. |
| **Configure accounting rules** | Configure [accounting rules](https://support.lucanet.com/en/documentation/consolidation-financial-planning/planning/accounting-rules.md) since xP&A typically writes a one-sided posting (and debit/credit checks are always applied). You need contra entries to ensure balanced postings. **Note:** If you model out the full debit/credit logic in xP&A (e.g. when it comes to detailed revenue and working capital predictions), you can also work without accounting rules. In order to do so, select a different import type (e.g. transaction figures) during the [data source configuration](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md#general-tab). |
## Process Steps for Exchanging Data Between xP&A and CFP
The process for exchanging data between xP&A and CFP consists of the following basic steps:
### Step 1: Integrating Data from CFP into xP&A
Data from Consolidation & Financial Planning is integrated as a **CFP data source in xP&A**.
How to set up a CFP data source in xP&A is described in [Connecting to a Lucanet CFP Data Source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/connecting-to-cfp-copy.md).
### Step 2: Modeling Data in xP&A
Once the data is available in xP&A, you can model them for your planning and analysis purposes.
Detailed instructions on how to work with data in xP&A can be found in our xP&A documentation. In particular, you can refer to e.g. [All Steps at a Glance for Lucanet xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/process-description-xpa.md), [Working With Integrated Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data.md), or [Modeling Your Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data.md).
### Step 3: Importing Data from xP&A back to CFP for the First Time
Once the planning data is modeled in xP&A, you can then transfer this data back to Consolidation & Financial Planning via import.
The **initial** import process consists of the following steps:
1. [Create an export of the desired data in xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-data-export-in-xPA-for-CFP.md)
2. [Create and configure the import script Lucanet xP&A #3700-xP&A.SQL.FOS](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-configuring-the-script-used-for-xPA-import.md).
3. [Create and configure the data source used for the import into CFP](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md).
4. [Create the assignment table used for the import into CFP.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-an-assignment-table-for-import-of-xPA-data.md)
5. [Create and execute the data import into CFP and assign the imported elements to the elements in CFP.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-executing-the-data-import-into-CFP.md)
All sub-steps necessary for this initial CFP import are described in detail under [Importing Data from xP&A to CFP for the First Time](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp.md).
### Step 4: Updating the Data Import from xP&A to CFP
Once the initial setup is configured, you can then update the import every time you want to transfer updated xP&A data to CFP.
This **recurring** import process consists of the following steps:
1. Create an export of the updated data in xP&A.
2. Update the configuration of the script Lucanet xP&A #3700-xP&A.SQL.FOS to include the new xP&A exports and update the dimension mappings.
3. Execute the data import of updated data into CFP.
All sub-steps necessary for this recurring CFP import are described in a Quick Reference Guide under [Updating the Data Import from xP&A to CFP](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp.md).
---
---
title: "Handling Errors in a Model Using AI"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/handling-errors-in-a-model
language: en
last_updated: 2026-05-28
---
# Handling Errors in a Model Using AI in Lucanet xP&A
## Overview
When a variable contains a calculation error, Lucanet xP&A (Extended Planning & Analysis) displays the error directly in the variable's **warning panel** — accessible, for example, via the indicator shown on the variable in the spreadsheet. To help you understand and resolve errors quickly, xP&A provides two AI-assisted features alongside the standard error message:
- **Explain with AI** helps you interpret what went wrong.
- **Fix with AI** (where available) suggests a correction you can apply directly.
> **Warning:** These AI features are designed to **assist** you — not to replace your judgment. You should always **review** AI-generated explanations and, in particular, any formula suggestion before accepting it.
## Explaining Errors With AI in xP&A
xP&A's AI feature **Explain with AI** generates a plain-language breakdown of the error for the variable you are viewing. To show the error explanation, simply hover over the warning triangle indicating an error and click **Explain with AI**. The explanation typically contains the following information:
- A **short summary** of the issue
- **Why this happened** — context behind the error
- **Impact** — how the error affects the variable or downstream results
- **Common fixes** (when applicable) — practical steps or patterns that often resolve this type of error
A data error explained with AI
> **Note:** - If the analysis is not complete, try to run the **Explain with AI** function again. In some cases, the AI can reuse a recent result without running a full new analysis.
> - You can provide **feedback** using the **Was this helpful?** function so we can improve the AI results over time.
## Fixing Errors With AI in xP&A
xP&A's AI feature **Fix with AI** goes one step further than explaining an error — it proposes a concrete correction, typically an updated formula or expression, based on the error type and your model's context. You can review the suggestion and decide whether to apply it or continue editing manually.
To use **Fix with AI:**
1. Hover over the warning triangle indicating an error and click **Fix with AI**.
Fix with AI
2. Wait for the AI suggestion to load, which is then displayed as follows, for example:
Corrections suggested by AI
3. Review the formula and the comparison between the original value and the proposed fix displayed in the error dialog.
4. Choose one of the following options:
- Click **Accept** to apply the proposed change to your model.
- Click **Dismiss** to discard the proposed change and continue editing your model manually.
> **Note:** - **Fix with AI** proposes a change based on technical error context — it cannot verify whether the formula reflects your intended calculation. Therefore, **always review the AI suggestions** before accepting. Only accept a suggestion if you are confident it matches your business logic.
> - **Fix with AI** may be unavailable if another change workflow is already active (for example, if you are in [proposal mode](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) for model changes). Finish or exit that workflow first, then try again.
> - Sometimes you receive guidance text instead of a formula proposal. This is still useful — read it alongside the output from **Explain with AI**, or use it as a starting point for manual editing.
---
---
title: "Helper Variables"
description: "In this article you will find the available helper variables for formulas in Lucanet xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables
language: en
last_updated: 2026-05-01
---
# Helper Variables in Formulas in Lucanet xP&A
## Overview
In this article you will find the available helper variables for formulas in Lucanet xP&A (Extended Planning & Analysis).
## Available Helper Variables in Lucanet xP&A
The following helper variables are available for formulas in xP&A:
| Helper variable | Description |
|---------|---------|
| cohort | Creates a Cohort Dimension. |
| daysinmonth | Returns the total number of days in the calendar month. |
| fiscalmonth | Fiscal month of the current time step. Must be an integer between 1 and 12. |
| fiscalyear | Fiscal year of the current time step. Must have Fiscal Year toggled on. |
| lastActualDate | Returns the time step index number of the time step of the [Last Actual Date setting](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md). Must have the setting toggled on in the [time settings of a model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md), otherwise none will be returned. See [lastActualDate](#lastactualdate) for more information. |
| month | Indexes the calendar months from 1-12. Jan = 1, Feb = 2 etc. Useful for seasonality, or any variables that occur on a particular month each year: **if month = 4 then X else Y**. |
| blank | Enables you to call **blank** variables in an if statement. E.g. if an employee has no end date: **if End Date = blank then X else Y**. |
| numtimesteps | Returns the total number of time steps in the model. E.g. useful for dividing a value equally over the length of the model: **X / numtimesteps**. |
| quarter | Indexes the quarter from 1-4. Can be used for calculating variables that reoccur in a particular quarter, e.g. **if quarter = 2 then X else Y**. |
| timestep or date | Returns the time step index number of the current time step. E.g. creating a different formula for the first time step of the model: **if timestep = 0 then X else Y**. |
| today | Returns the time step index number corresponding to the current date. E.g. if you want to set a particular value for today, or months beyond today: **if timestep >= today then X else Y**. |
| year | Indexes the calendar year. Useful for setting different values/formulas for different years. E.g. **if year = 2022 then X else Y**. |
## lastActualDate
**lastActualDate** is a helper variable in Lucanet xP&A that returns the timestep of the [Last Actual Date setting](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), if it is toggled on.
This is useful:
- If you want to forecast variables using historical averages e.g. average your new users for the last 3 months of actuals/historicals.
Forecast Variables based on historical average values
- Or for having a different formula for your forecast months vs. your ‘actual’ or historical months. E.g. for a **Churn %** variable, you might want to calculate the actual churn percentage in historical months, but for forecast months this might be an input based off of other variables.
LastActualDate to calculate the churn.
---
---
title: "IF Statements in Formulas"
description: "When you want a variable to have different values or formulas based on a condition, you can use if-statements. They always have to follow the structure if condition then X else Y."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/if-statements-in-formulas
language: en
last_updated: 2026-05-01
---
# If Statements in Formulas in Lucanet xP&A
## Overview
When you want a variable in Lucanet xP&A (Extended Planning & Analysis) to have different values or formulas based on a condition, you can use if statements. They always have to follow the structure **if condition then X else Y**.
## Options in IF Statements in Lucanet xP&A
In Lucanet xP&A, you can link multiple conditions with and and/or or:
- **if condition1 or condition2 then value1 else value2**
- **if condition1 and condition2 then value1 else value2**
In Lucanet xP&A, you can also link conditions with a **list** using the syntax **IN**, for example:
- **if month in \[11, 12, 1, 2\] then 90% else 100%**: means if the month is Nov, Dec, Jan or Feb, return 90% else return 100%.
- You can also use dimensions/dimension items in if-statements, for more information, see [Dimension Items in Formulas](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md).
You can also link conditions with the **exclusion of a list** using the syntax **NOT IN**, for example:
- **if month not in \[11, 12, 1, 2\] then 90% else 100%**: means if the month isn't Nov, Dec, Jan or Feb, return 90%, if it is return 100%.
You can have multiple layers of if statements too, for example:
- **if condition1 then value 1 else if condition2 then value2 else [...]**
> **Warning:** - You can break each of these layers out onto separate lines of your formula editor using **Shift + Enter**.
> - Note that every if statement must have an else, otherwise xP&A will return an error.
## Examples of IF Statements in Lucanet xP&A
The following are examples of IF statements in Lucanet xP&A:
- if timestep > 4 then 1 else 0
- if variable1 > variable2 then 100 else 200
- if timestep > 4 and timestep < 10 then 1 else 0
- if variable1 < 10 then 100 else if variable1 < 20 then 200 else 300
---
---
title: "Importing or Exporting Charts"
description: "This article describes how to import or export charts, e.g. to use a chart as an image outside of Lucanet xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts/importing-exporting-charts
language: en
last_updated: 2026-05-01
---
# Importing or Exporting Charts in Lucanet xP&A
## Overview
This article describes how to **import** or **export** charts, e.g. to use a chart as an image outside of Lucanet xP&A (Extended Planning & Analysis).
## Importing Charts in xP&A
If [models are linked](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md), you can easily import charts from one model into another, just like you can import variables:
1. Click the **+** icon on the bottom left in your dashboard and select **Import chart**.
2. Click the model from which you want to import a chart and select or search for the desired chart.
The imported chart will appear alongside your other charts, the only difference being its title is **Blue**.
> **Warning:** Note that if you are giving people access to **only** the model that imports charts, they will not be able to view the charts properly UNLESS you give them access to the underlying variables and data that the chart leverages. You can do this either by:
>
> - Importing the variables or data that the chart utilizes into the model you are sharing with them
> - Giving them access to the sub-models directly
## Copying or Exporting Charts in xP&A
To copy or download a chart in xP&A as an image:
1. Click the three-dot-icon in the toolbar.
2. Select **Copy** or **Download** from the drop-down menu.
---
---
title: "Initial Data Import from xP&A to CFP"
description: "Once the planning data is modeled in xP&A, you can then transfer this data into Consolidation & Financial Planning. \n\nCFP uses an import script (Lucanet xP&A #3700-xP&A.SQL.FOS) to read in xP&A exports."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp
language: en
last_updated: 2026-05-28
---
# Importing xP&A Data into Consolidation & Financial Planning for the First Time
## Overview
Once the planning data is modeled in xP&A, you can then transfer this data into Consolidation & Financial Planning.
CFP uses an import script (**Lucanet xP&A #3700-xP&A.SQL.FOS**) to read in xP&A exports.
The following sub-steps are necessary for importing data from xP&A to CFP:
1. [Create an export of the desired data in xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-data-export-in-xPA-for-CFP.md) for each model you would like to import into CFP.
2. [Create and configure the script Lucanet xP&A #3700-xP&A.SQL.FOS](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-configuring-the-script-used-for-xPA-import.md). CFP uses this import script to read in the xP&A exports. Configuration is done in the script's settings before you execute an import.
3. [Create and configure the data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-cconfiguring-the-data-source-for_xPA-import.md) used for the import into CFP. In the data source configuration, you link the script and define certain parameters to be used for the import.
4. [Create the assignment table](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-an-assignment-table-for-import-of-xPA-data.md) used for the import into CFP.
This assignment table is the basis for assigning all elements imported from xP&A (e.g. accounts, cost centers, transaction currency, etc.) to elements in CFP.
5. [Create and execute the data import](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-executing-the-data-import-into-CFP.md) into CFP and assign the imported elements to the elements in CFP
The data import uses the data source that is linked to the xP&A script and the assignment table you defined for this purpose.
## Prerequisites for Importing xP&A Data into CFP
Before you configure the import of xP&A data into Consolidation & Financial Planning (CFP), the following prerequisites must be met:
| Prerequisite | Description |
|---------|---------|
| **CFP version** | If you work with Consolidation & Financial Planning in Lucanet.Financial Client, the Lucanet version must be Lucanet 25 or higher. |
| **Script file** | The script **Lucanet xP&A #3700-xP&A.SQL.FOS** is available (e.g. via the partner portal or your Lucanet consultant). |
| **Java library** | The Java library athena-jdbc-3.4.0-with-dependencies.jar is added to the library of the CFP database (typically done by our Cloud Services or SRE team). |
| **Database connection (optional)** | For drill-down support and to avoid re-running the xP&A export on each import, a connection to an SQL database can be used as temporary storage. The connection information for Lucanet.Financial Warehouse can be used for this purpose. |
---
---
title: "Integrating Data"
description: "Data integrations let you connect the variables in your model to different data sources. In most cases, this is used to pull in actual data and to perform forecasts based on historicals."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data
language: en
last_updated: 2026-05-01
---
# Integrating Data in Lucanet xP&A
## Overview
Data integrations in Lucanet xP&A (Extended Planning & Analysis) let you connect the variables in your model to different **data sources**. In most cases, this is used to pull in actual data and to perform forecasts based on historicals.
When a variable is linked to data, it will take its value from the data source if data exists, and will fall back to its formula if data does not exist.
Data integrations can be set up to connect to:
- **Consolidation & Financial Planning** on the **Lucanet CFO Solution Platform**
- Different kinds of systems, such as **CRM**, **Accounting** or **ERP** systems, **Payroll**, or **BI** tools.
A list of the currently available integrations can be found below.
In this section you will find information on the following topics:
- [Connecting to a data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source.md): In order to integrate data from a source system into xP&A, you need to establish a connection to the respective data source.
- [Sharing data connections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/sharing-data-connections.md): By default, data connections and the data sources created from the connections are private to the user who created them. In order to be used by other users, you can share the connection to a data source with them.
- [Working with integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data.md): Once a connection to a source system is established and data is integrated from a data source, you can start working with the data in Lucanet xP&A.
## Available Integrations in xP&A
xP&A currently offers integrations with the following source systems.
Please note that we are extending the list of available source systems constantly. If you are missing a specific source system, please contact us.
| Integration | Available systems |
|---|---|
| **[Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-lucanet-cfp-data-source.md)** | Consolidation & Financial Planning (CFP) |
| **[Accounting](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-accounting-erp.md)** | • Puzzle • QuickBooks • Xero |
| **[HRIS/Payroll](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-payroll-provider.md)** | • Altera Payroll • Bamboo HR • Breathe • Charlie • ChartHop • Deel • Freshteam • Gusto • Hibob • HR Cloud • HR Partner • Humaans • IntelliHR |
| **[Spreadsheet](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-spreadsheet.md)** | • CSV Upload • Google Sheets • Excel Online • Excel Upload |
| **[CRM](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-crm.md)** | Salesforce |
| **[BI/Database](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-bi-data-warehouse-system.md)** | • BigQuery • Databricks • Looker • Microsoft SQL Server • MySQL • Postgres • Redshift • Snowflake |
| **Subscription/Billing** | Stripe |
---
---
title: "Last Actual Date"
description: "The Last actual date is a model-level setting that represents your latest month (or week if in a weekly model) of \"actual\" historic data. It determines the cut-off date for importing data into your model (unless you have the option 'Import data until' set for a data source)."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date
language: en
last_updated: 2026-05-01
---
# Last Actual Date in Lucanet xP&A
## Overview
The **Last actual date** is a model-level setting in Lucanet xP&A (Extended Planning & Analysis) that represents your latest month (or week if in a weekly model) of "actual" historic data. It determines the cut-off date for importing data into your model (unless you have the option 'Import data until' set for a data source).
The following applies to the **Last actual date** in xP&A:
- Whenever there is no data present (usually only beyond the **Last actual date**), xP&A will fall back to the formula to determine the value you see in each month.
- Charts, trend lines, and time step column headers show forecast periods (beyond the **Last actual date**) as dashed. The [actuals version](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model.md) includes only months up to and including the **Last actual date**.
- There is also a [Helper variable](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) available for the last actual date.
## Setting the Last Actual Date for the First Time in xP&A
How the last actual date is set for the first time in xP&A depends on whether you import actual "historic" data via a [data source integration](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md) or if you enter them manually:
- **If you use data integration**, the **Last actual date** is automatically set when you connect data to a model via an integration for the first time (and the date is in the past).
- If you enter data manually, you can determine the Last actual date in the time settings of a model (see [Editing the Model Settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md)).
## Updating (Rolling Forward) the Last Actual Date in xP&A
To update the last actual date in xP&A, i.e. to roll the last actual date forward:
1. In the **Spreadsheet** view, click **Last actual date** in the column header.
2. Select the new month using the calendar:
3. In the dialog that appears, choose:
- Which **data sources** you want to refresh (across the current and linked models)
- For which **linked models** you want to roll the Last actual date forward.
- If you want to save a **version** of the affected models. In this case, the version will be saved as **Latest Oct ‘23** _forecast_ (depending on which month you save it).
4. Click **Apply**.
> **Note:** If you roll the Last actual date back in time, any months of data after the last actual date will be cut off. This is useful for instance if you rolled forward but then realized your books were not closed, or the data was not ready yet.
## FAQ About the Last Actual Date
| Question | Answer |
|---|---|
| **What will happen if I have data beyond the Last actual date in my data sources?** | Even if you have data beyond the **Last actual date** in your data source, they will not be pulled into your model until you roll the **Last actual date** forward. A blue dot will be displayed next to the current **Last actual date** to let you know that there is data beyond the **Last actual date**. |
| **What if I want to bring the forecast months as data from a data source outside of xP&A?** | For more information on this topic, refer to the [Import Data Until Function.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/import-data-until-function.md) |
| **What if some data items within a model have data up to different points in time?** | If you are missing months of data for any data items immediately before (and including) the **Last actual date**, xP&A will fall back to the formula for variables connected to those data items for those months. |
| **Who can change the last actual date?** | Anyone who has full or edit access to the model. |
| **What happens if I refresh data but did not do so via the Last actual date header? (e.g. via auto-refresh, or directly on the data source)** | • If you refreshed and there is now data present beyond the current **Last actual date**, a blue dot will be displayed next to the current **Last actual date** to let you know there is data available. Once you update the **Last actual date**, the new data will be pulled into the model(s). • If you refreshed and data changed for any historic months (up to and including the **Last actual date**), this data will be reflected immediately in the model(s). |
| **What happens if I’ve updated my Last actual date but my data source(s) takes a while to refresh?** | • Most data sources refresh within 1-2 minutes. However, some larger data sources may take longer. In these instances, you may have a new **Last actual date**, but no data being pulled in for it yet. A moving refresh icon will be displayed in the header next to the new **Last actual date** in any model connected to a refreshing data source. • If you know your data sources take a while to refresh, you could instead refresh the data source first, and then update the **Last actual date** once the refresh is finished. |
| **What if I want to restrict months of data, but just for one data source (not all) in a model?** | For more information on this topic, refer to [Import Data Until Function.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/import-data-until-function.md) |
| **What if I don’t use the Last actual date at all?** | Data will flow into the model(s) to which they are connected to as and when they are refreshed, up to whatever months or time steps the data source has data for. Note that there will be no automatic visual distinction between historic months in time step headers or charts, and you will not be able to use the [Last Actual helper variable](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) or [Actuals version](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model.md). |
---
---
title: "Linking Dimensions from a Data Source"
description: "Often, you will import data broken down into dimensions — for example, employee data from your Payroll/HRIS system, or department expenses in Accounting/ERP systems.\n\nWhen you link a data item that has dimensions to a variable, xP&A will not breakdown the variable until you link an xP&A dimension to the dimension in the data source explicitly.\n\nYou can link a dimension either from a model or from a data source."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source
language: en
last_updated: 2026-05-01
---
# Linking Dimensions From Data Sources in Lucanet xP&A
## Overview
Often, you will import data broken down into dimensions — for example, employee data from your Payroll/HRIS system, or department expenses in Accounting/ERP systems.
When you [link a data item](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md) that has dimensions to a variable, Lucanet xP&A (Extended Planning & Analysis) will not breakdown the variable until you link an xP&A dimension to the dimension in the data source explicitly.
You can link a dimension either **from a model** or from a **data source**.
> **Warning:** Once a dimension of a data source is linked to a dimension in xP&A:
>
> - The dimension items will be kept in sync automatically whenever you [refresh your data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md):
>
> - If you add new items in the data source, they will be added to the xP&A dimension as well.
> - If you remove items in the data source, they will not be removed - they will just be unlinked in xP&A.
> - You can also see a full history of your data/dimension synchronization in the [data sync history](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md).
> - Any dimension items coming from your data source are "linked". You can change the name of the dimension item in xP&A, and the link will not be broken.
> - A linked dimension item is displayed with the linked item icon:
>
> the shows a dimension item (' holding ger...') with its linked data highlighted in red. hovering over displays tooltip 'synced with data sources', listing 'balance sheet' as connected data source. icon
> Symbol for linked dimensions
## Linking Dimensions From a Model in xP&A
To link a dimension to a data source from a model:
1. Navigate to the variable in your model for which you want to link the dimensions to the data source. The variable must be [linked to integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md).
2. Click the **Dimensions** button.
3. Select the dimension you want to link.
This will automatically create the dimension in xP&A, and link it to the data source connected to this variable.
Linking a dimension to a data source from a model
## Linking Dimensions from a Data Source in xP&A
To link a dimension of a data source to a dimension in xP&A from a [data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source.md):
1. Open the **Data** workspace and click on the data source for which you want to link the dimensions.
2. Open the **Dimensions** tab.
3. Assign the dimensions of the data source to the dimensions in xP&A. You can switch the dimensions by opening the dropdown menu of the respective dimension field.
Linking a dimension to a dimension in xP&A from a data source
---
---
title: "Linking Models"
description: "Instead of a single model with all of your variables and formulas, you can structure your work into separate, smaller models, and import variables between them."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models
language: en
last_updated: 2026-05-01
---
# Linking Models in Lucanet xP&A
## Overview
Instead of a single model with all of your variables and formulas, you can structure your work in Lucanet xP&A (Extended Planning & Analysis) into separate, smaller models, and import variables between them.
There are a few benefits to working with smaller, linked models:
- There will be less scrolling around and **less potential for confusion** for you as you build out your models.
- It will be **easier** for your team to work with separate models. For example, your HR team can work on your _Headcount Plan_ without worrying about your _Revenue_ model.
- You can have **different permissions** for each model. For example you may want each department head to access the company's P&A model, without being able to see the underlying salary data for each employee (this will live in a separate Headcount model).
- Linked models can have a **different time-granularity**. For example, your _Contracts_ model could be of daily granularity, while your _P&A_ remains monthly.
> **Note:** Once you link models together, you can:
>
> - Reference variables in linked models in your formulas, and you can import variables and visuals from one into another. For more information, see [Referencing Variables From Linked Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models.md).
> - Easily import charts from one model into another, just like you can import variables. For more information, see [Using Tables and Charts](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md).
## Linking Models in xP&A
When in a model, click the **+** in the overview, and link to an existing or a new model:
Linking a model
All **linked models** are displayed in the overview of a model on the left-hand side.
Linked models
> **Warning:** To be able to link models, they have to be in the same folder.
---
---
title: "Linking Variables to Integrated Data"
description: "To use the data you integrated via a connection to a source system in your variables in Lucanet xP&A , you can link the variables to the integrated data. \n\nYou can use this function to perform forecasts based on historicals, for example.\n\nWhen a variable is linked to integarted data, it will take its value from the data if data exists, and will fall back to its formula if data does not exist (usually only beyond the Last actual date).\n\nYou have different options to link variables to integrated data:\n\nYou can link a new variable while creating it.\nYou can link existing variables.\nYou can link a variable from the data preview.\nYou can create a model from a data source in one click.\n\n\nYou can see which data items (from which data sources) are being used at a glance in the Data column:"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data
language: en
last_updated: 2026-05-01
---
# Linking Variables to Integrated Data in Lucanet xP&A
## Overview
To use the data you integrated via a connection to a source system in Lucanet xP&A (Extended Planning & Analysis), you can link the variables to the integrated data.
You can use this function to perform forecasts based on historicals, for example.
When a variable is linked to integrated data, it will take its value from the data if data exists, and will fall back to its formula if data does not exist (usually only beyond the [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md)).
You have different options to link variables to integrated data:
- You can link a new variable while creating it.
- You can link existing variables.
- You can link a variable from the data preview.
- You can create a model from a data source in one click.
You can see which data items (from which data sources) are being used at a glance in the **Data** column and the top bar of spreadsheet:
Linked data shown in the 'Data' column
## Linking a New Variable to Integrated Data in xP&A
To create a new variable linked to integrated data:
1. Click **New Variable** at the end of a section.
Creating a new variable
2. The following drop-down menu is displayed:
Drop-down menu for a new variable
3. Click **Create from data** and select or search for the data source for which you want to integrate data.
4. Select from the drop-down list or search for the **data item** you want to use in the new variable.
The data is integrated into the variable.
5. If necessary, modify the variable's [format type](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md#main-format-types-in-xpa) by clicking on the edit icon or the icon to the left of the variable name.
> **Note:** For more information on variables and how to format and edit them, see [Creating and Editing Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md).
## Linking an Existing Variable to Integrated Data in xP&A
To link an **existing variable** to a **data item**, click in the **Data** column of the variable and choose the data source and data item you would like to connect:
Linking from the data column
## Linking a Variable From the Data Preview in xP&A
To link a variable to the data item of a data source from the data preview:
1. Click the name of the data source in the overview of the model to **open the data preview**.
2. In the row of the desired data item, click the pen icon in the **Linked variables** column.
3. **Choose the variable** you want to link the data item to from the drop-down list that appears. (If the variable does not yet exist, you can [create it](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md) from here by clicking **New variable**.)
Linking from the data preview
## Removing Links From a Variable to Integrated Data in xP&A
To remove a link from a variable to the data item of a data source, choose one of the following options:
- **To remove all links** from all variables to a data source within a model, open the **three-dot menu** behind the name of the data source in the **overview** of the model and choose **Remove from model**:
Removing link from all variables
- **To remove the link from individual variables** to a data source within a model, open the **data preview** of the model, click the pen icon and then on the variable you want to remove:
Removing a link from individual variables
## Creating a Model From a Data Source With One Click in xP&A
If you want to build a model based on underlying integrated data, you can create the model structure in one click. You can use this feature, e.g. to quickly generate a skeleton for a model, such as a P&L model based on a P&L in Xero/QuickBooks.
Each variable is automatically named according to the line items, and is automatically connected to the line item in the data source.
To do so, open the **Data** workspace and choose **Create model from data source** from the three-dot menu of the desired data source:
Creating a model from a data source
## Blanks in Integrated Data in xP&A
If you have **blank values** in integrated data that are used in variables, xP&A will treat them **as 0 by default**, unless you change the data settings to have blanks treated as blanks.
This is useful if you want to exclude the blank values in data from calculations like averages, min/max etc.
**Example**:
**avg(5,10,blank)** with the setting **Treat as blank** will result in **avg(5,10) = 7.5**.
To change the settings how blanks are treated in an integrated data item, click the **data icon** in the **Data** column of a model and choose **Advanced settings**:
Advanced settings of integrated data
Under **Blanks in data**, select if you want to **treat blanks as zero (default)** or if you want to **treat them as blanks**.
'Blanks in data' option
---
---
title: "Lucanet xP&A User Interface"
description: "This page contains information about the structure of the user interface and the most important elements in Lucanet xP&A. From this page, you can jump easily to the detailed descriptions of the individual areas and functions."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/user-interface-xPA
language: en
last_updated: 2026-05-01
---
# User Interface in Lucanet xP&A
## Overview
This page gives you a clear overview of the **Lucanet xP&A (Extended Planning & Analysis) interface** and its **key elements**.
From here, you can quickly navigate to detailed descriptions of each area and function.
## Structure of the Start Page in Lucanet xP&A
When you open the xP&A solution from the main menu, the **Lucanet xP&A start page** loads by default:
Start page of Lucanet xP&A
You can return to the start page at any time by clicking the **xP&A** button in the top left corner of the screen.
### Overview
The following elements are available in the **overview** on the Lucanet xP&A start page:
| Element | Description |
|---|---|
| **Home button** | You can use the home button to navigate back to the **start page** from anywhere in the xP&A solution. |
| **Search field** | You can use the search field to: • Quickly create a new model or data source • Access our product documentation • Navigate to specific elements that are already present in xP&A |
| **Quick creation links** | You can use these links to quickly create a new model or data source. |
| **Workspaces** | You can use this area to navigate to the different **workspaces** of the xP&A solution: • **Models**: Opens the [model overview](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models.md) (which is shown by default on the start page) • **Notifications:** Opens the **notification center** where you are updated on actions regarding your models, data, comments, and organization and teams. • **Data**: Opens the [Data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md) workspace where you can administrate your data integrations, i.e. manage and share your data sources and data connections. • **Dimensions**: Opens the [Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md) workspace where you can manage your dimensions. • **Proposals**: Opens [Proposals](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) workspace where you can manage change proposals. • **Settings**: Opens the **Settings** workspace where you can • Adjust your **notification settings** • Open the **Help** center to access our resources to learn xP&A and get support. |
### Detail View
The following elements are available in the **detail view** on the Lucanet xP&A start page:
| Element | Description |
|---|---|
| **Search field** | You can use the search field to: • Quickly create a [new model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/creating-model.md) or [data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source.md) • Access our product documentation • Navigate to specific elements that are already present in xP&A |
| **Help center** | You can use the Help center to: • Access our resources to learn xP&A and get support. • Submit your ideas to help us improve xP&A |
| **Model overview** | In the **model overview**, you can see all models that you have access to and organize them.
For more information, see [Working with Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models.md) and [Organizing Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/organizing-models.md). |
---
---
title: "Modeling Your Data"
description: "Lucanet xP&A offers various elements to model your data so it can be used in your model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data
language: en
last_updated: 2026-05-01
---
# Modeling Your Data in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) offers various elements to model your data so it can be used in your model. This section contains information on:
- [Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md): Variables are the building blocks of your models in Lucanet xP&A.
- [Formulas](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas.md): Formulas are one of the most important concepts in Lucanet xP&A; they let you work with numbers, ranges, and other variables.
- [Time](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md): Time settings can be applied in Lucanet xP&A at formula level and at model level.
- [Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md): Dimensions are the most powerful concept in Lucanet xP&A.
- [Currency and Currency Translation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/currency---fx-conversion.md): Currency settings and currency translation in Lucanet xP&A allow you to flexibly set up your planning in multiple currencies.
---
---
title: "Moving Variables"
description: "You can move variables within a model, as well as between models."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/moving-variables
language: en
last_updated: 2026-05-01
---
# Moving Variables in Lucanet xP&A
## Overview
You can move variables within a model, as well as between models, in Lucanet xP&A (Extended Planning & Analysis).
## Within a Model in xP&A
Variables can be moved within a model in xP&A by simply dragging/dropping. You can move multiple variables at once by multi-selecting the variables with **Cmd/CTRL + Click**, or **Shift+↑/↓** and dragging/dropping.
## Between Models in xP&A
If models are [linked together](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md), you can easily **move**/ **copy** variables (one or multiple) from one model to another in xP&A by right-clicking, and selecting **Move**/ **Copy variable**, and selecting the destination model. You can think of **Move** like Cut/Paste, and **Copy** like Copy/Paste.
Moving variables between models
---
---
title: "Multi-Player Modeling"
description: "xP&A allows multiple users to work in the spreadsheet of a model at the same time. In this chapter we will explain what needs to be considered for multi-player modeling."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/multi-player-modeling
language: en
last_updated: 2026-05-01
---
# Multi-Player Modeling in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) allows **multiple users** to work in the **spreadsheet** of a model at the same time.
In this chapter we will explain what needs to be considered for multi-player modeling.
> **Tip:** You can see who else is in the model by the initials icon that shows up at the top right (and you can hover over the icon to see their full name).
## Pulling in Changes by Other Users in xP&A
If you are in the same model together with other users and someone makes changes to the model, you will get a pop-up that allows you to pull in their changes by clicking **Pull edits now**.
If you ignore the pop-up and do not pull in the changes, we will combine the changes together automatically.
> **Tip:** The keyboard shortcut to pull in edits is **Ctrl + E (⌘/ctrl + E)**.
## FAQ on Multi-Player Modeling in xP&A
### What happens in case of conflicts?
- If the changes conflict, the **latest change is saved.**
- Examples of this are:
- Editing the name of the same variable at the same time
- Editing a formula of the same variable at the same time ( _unless_ you are editing the formula for different timesteps of a variable, or different dimension items of a variable, in which case the changes do not conflict and xP&A will combine them)
- The only exception to this rule is if someone deletes something (e.g. a variable), then another user tries to rename it, the deletion overrides the rename of the element.
> **Note:** - For charts and tables, xP&A does not combine changes, so if you are editing the same visual at the same time as another user, be aware that the latest change will be saved.
> - If you [reorder dimension items](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md) in the data table, xP&A cannot combine these changes, i.e. if you are editing the order at the same time as another user, the latest change will be saved.
> - For [time settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md) and other advanced [model options](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md), the latest change will be saved.
### Can I deactivate the pop-up?
Yes! You can dismiss the pop-up for your session by clicking the x at the top right (**Don’t show this again**).
This will disable it until you next refresh your browser, or open the model. You will still see the **New edits** button, and you can click on this to pull edits), but you will not see the pop-up.
### What if a team member is in another linked model?
- We only show you who is in the **current model** that you are in.
- When switching to a new tab, i.e. another linked model, xP&A will automatically pull in the latest version of that model, i.e. the other user's edits will be included.
---
---
title: "Organizing Models"
description: "For a better overview, models can be organized in folders and sub-folders. \nIn addition, you can assign a specific icon to identify a model easier, and you can set up favorites for your models."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/organizing-models
language: en
last_updated: 2026-05-01
---
# Organizing Models in Lucanet xP&A
## Overview
For a better overview, models in Lucanet xP&A (Extended Planning & Analysis) can be organized in **folders.**
In addition, you can assign a specific **icon** to identify a model easier, and you can set up **favorites** for your models.
## Organizing Models in Folders in xP&A
Models can be organized into folders in xP&A on the **Models overview page** under **Your models**.
- To create a new folder, click **New folder** and enter a name.
- To **add** a model to a folder, simply **drag & drop** the model into the folder.
- To **remove** a model from a folder, just **drag it onto the arrow** in the top left corner the arrow icon, and hold until it is moved up a folder level.
Models organized in folders
## Changing the Icon of a Model in xP&A
To keep models easily differentiated, you can change the icon by clicking on it and selecting a new one:
Changing an icon
## Marking a Model as Favorite in xP&A
To keep position a model **at the top of a folder or page**, you can mark the model as a favorite by activating the star icon . The model is then displayed under the **Favorites** section on the model overview page:
'Favorite models' section
---
---
title: "Proposing Changes to a Model"
description: "The **Propose Changes** feature allows both Editors and Data Collectors to collaborate on model updates without directly modifying live data.\n\nEditors can now review, approve, or reject suggested updates before they’re applied — ensuring control, traceability, and teamwork."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model
language: en
last_updated: 2026-05-01
---
# Proposing and Approving Changes to a Model in Lucanet xP&A
## Overview
The **Propose changes** feature in Lucanet xP&A (Extended Planning & Analysis) enables collaborative model updates through a structured review workflow.
**Data Collectors** can suggest changes without directly modifying live data, while **Editors** maintain control by reviewing, approving, or rejecting proposed updates before they are applied — ensuring control, traceability, and teamwork.
Change proposals can be made in the spreadsheet or the dashboard of a model and can contain one or several **proposal items**, i.e. individual cell changes.
An overview of all proposals relevant for a user (either as a **Data collector** or **Editor**) can be accessed in the **Proposals** workspace.
> **Note:** In order to be able to participate in the change proposal process, a user must have a certain user role and access to the respective model.
## The 'Proposals' Workspace in xP&A
An overview of all proposals relevant for a user can be accessed in the **Proposals** workspace. Here you can see all proposals you created as a **Data Collector** or for which you are an **Editor**.
In addition, you can:
- Open a proposal in the model view
- Track the status and progress of a proposal
- Filter proposals by **model**, **creator**, or **status**
The workspace is displayed as follows, for example:
'Proposals' workspace
## User Roles and Permissions in xP&A
The user roles involved in the process of change proposals are **Data collectors** and **Editors**. They have the following permissions:
### Data collectors
Data Collectors can contribute changes through the proposal workflow. They cannot edit models directly. Instead they:
- Can create and submit proposals in which they:
- Can propose value changes
- Can add, rename, or delete dimension items
- Can link dimensions
- Cannot add or edit formulas
- Cannot add or delete variables
- Cannot rename variables
- Cannot add data sources
- Can add proposal items to their own proposals as long as the status of the proposal is not **Applied** or **Closed.**
- Can delete their own proposals in the **Draft**, **Submitted**, or **Closed** status (but not after they have been **Applied**) **.**
- Receive notifications when their proposals have been reviewed.
### Editors
Editors have full control over models and proposals. They:
- Edit models directly
- Create proposals for collaborative editing
- Review, approve, or reject proposals from any user
- Apply approved proposals to models
- Delete proposals in **Submitted** or **Closed** status
## Assigning User Roles and Granting Model Permissions in xP&A
In order to be able to participate in the change proposal process, a user must have a certain user role and access to the respective model. The following steps are necessary:
1. The user role **Editor** or **Data Collector** must be assigned in the **Administration** of the Lucanet CFO Solution Platform. For more information, see [User Management](https://support.lucanet.com/en/documentation/administration/user-management.md).
2. To be able to access a model with certain permissions, the **model** or a **view** of the model needs to be shared with a user granting the necessary level of access. For more information, see [Sharing a model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md).
**Data collectors**
- If a user shall be able to propose changes as a **Data collector**, they must be assigned the user role **Data collector** in the **Administration** of the CFO Solution Platform.
- In addition, the **model** or a **view** of the model must be shared with them granting the level of access **Can create change proposals** or **Can create change proposals from the dashboard**.
**Editors**
- If a user shall have **Editor** permissions and the permission to **review** and **approve** changes in a model, they must be assigned the user role **Editor** in the **Administration** of the CFO Solution Platform.
- In addition, the model or a view of the model must be shared with them granting the level of access **Can edit**.
## Statuses of Proposals and Proposal Items in xP&A
Change proposals can consist of one or more proposal items (i.e. individual cell edits) which can have the following statuses during the approval process.
### Statuses of proposals
Proposals can have the following status:
- **Draft**: The proposal is being created before submission. Only visible to the creator.
- **Submitted**: The proposal has been sent for review. Editors are notified and can begin reviewing the proposal items contained in the proposal.
- **Applied**: The proposal has been approved and merged. Approved changes now appear in the model.
- **Closed**: The proposal has been closed without applying any changes.
The current status of a proposal is shown next to the proposal in the proposal mode at the right-hand side of the spreadsheet or dashboard view:
Status of a proposal
### Statuses of proposal items
Proposal items can have the following status:
- **Pending (purple color)**: The proposal item is awaiting review by an editor.
- **Approved (green color)**: The proposal item has been approved by an editor — and will be applied to the model once the editor applies the proposal.
- **Rejected (red color)**: The proposals item has been rejected by an editor — and will not be applied.
The current status of a proposal item is shown:
- At the top right corner of the proposal item
- In the respective comment of the proposal item
Status of a proposal item
## Creating and Submitting a Proposal in xP&A
They way you can create a proposal depends on whether you are a **Data collector** or an **Editor**.
### As a Data Collector
Data Collectors cannot edit models directly, but they can propose changes within a model or a view. To create a proposal as an editor:
1. Edit the content of a cell in a model or view.
The following dialog is displayed:
Creating a new proposal
2. Enter a **name** for the proposal.
3. Click **Create**.
The **proposal mode** is opened and you can see the name of the proposal on top of the model and the proposal details on the right-hand side:
Proposal mode
4. Continue making changes.
Each change is automatically tracked as a proposal item under the proposal you just created.
5. Once all changes are entered, click **Submit** on the top right to submit the proposal to be reviewed by an editor.
The proposal is displayed in the **Proposals** workspace and in the model view and all editors with access to the respective model will be notified of the submitted proposal.
### As an Editor
Editors can both edit models directly (without approval by any other users) or use a proposal to have their changes approved by another editor. To create a proposal as an editor:
1. Go to the model you would like to propose changes for.
2. Open the three-dot menu on the top right and choose **Propose changes**.
'Propose changes' option
3. Enter a name for the proposal and click **Create**.
The **proposal mode** is opened and you can see the name of the proposal on top of the model and the proposal details on the right-hand side:
Proposal mode
4. Continue making changes.
Each change is automatically tracked as a **proposal item** under the proposal you just created.
5. Once all changes are entered, click **Submit** on the top right to submit the proposal to be reviewed by an editor.
The proposal is displayed in the **Proposals** workspace and in the model view and all editors with access to the respective model will be notified of the submitted proposal.
> **Note:** - You can create multiple proposals for the same model.
> - Once you have submitted a proposal, you can start a new proposal for additional changes.
> - As long as in **Draft** and **Submitted** state, a proposal item can be deleted by its creator by hovering over the proposal details and using the **Delete** button (the delete icon).
> - As an **Editor**, you can technically create and apply your own proposal. In practice, when using the change approval flow, you are likely to have your proposals approved by another editor.
> - Proposals in **Draft** and **Submitted** status are live when made by an **Editor**. This means that if you make changes as an editor, they are directly applied and can be traced in the change log in the proposal details when hovering over the cell.
## Opening a Proposal and Proposal Items in xP&A
You can open a proposal from:
- The **Proposals** workspace
- The model view, by clicking on the proposals icon in the top-right.
- The notification, in case you are an editor and have been notified of a submitted proposal.
The proposal details are displayed in the side bar as follows, for example:
Proposal details
You can see the details of the proposal items for each specific variable or dimension by clicking the variable or dimension in the **Changes** section of the proposal details. The proposal item details are displayed as follows, for example:
Proposal item details
You can navigate back to the proposal using the breadcrumbs at the top.
## Approving or Rejecting a Proposal in xP&A
To review and apply or reject proposals, editors have the following options:
**At Cell Level**
Once you opened a proposal, you can see which cells have been edited. Hover over a cell to open the details of the change:
Approving or rejecting directly in a cell
You can then choose to **approve** or **reject** the proposed change using the **arrow** or **X**. If needed, you can enter a reply to the **Data collector** to explain your decision or ask a question.
**At Row Level**
You can also approve or reject a proposal on the entire row level by hovering on the row and making the selection on the left hand.
**At Model Level**
Another option is to approve or reject all changes of the proposal in the model at once. To do so, click the respective buttons in the **Pending changes** section at the bottom of the model view.
If you want to reset the approvals or rejections you already made, you can use the **Reset** button (the reset icon) to bring all proposal items back to the **Pending** state.
Approving or rejecting all changes at model level
## Applying Changes of a Proposal in xP&A
Once an editor has reviewed all proposal items of a proposal, the approved changes can be applied to a model.
To do so, just click **Apply** on the top right.
Data collectors will see the updated status and any comments left by Editors.
## FAQ on Change Proposals in xP&A
### Can I delete a proposal?
- **Data Collectors** can delete their own proposals in **Draft**, **Submitted**, or **Closed** status (but not after it has been **Applied**).
- **Editors** can delete any proposal in **Submitted** or **Closed** status.
### Can I edit a proposal after submission?
Yes. The creator can continue adding new items or editing existing ones until the proposal is **Applied** or **Closed**.
Limitations:
- Proposal items that have already been **approved** or **rejected** cannot be edited.
- Editors reviewing a proposal cannot edit it; they can only approve, reject, or comment.
### Who can see proposals?
This depends on the status of the proposal.
- **Draft**: Proposals are only visible to the creator of the proposal (either an Editor or Data Collector)
- **Submitted**: Proposals are visible to all Editors of that model
Editors can see the number of proposals associated with a model in the top-right corner
### Can multiple people review the same proposal?
Yes.
- Multiple Editors can review and comment on a proposal
- Only one Editor can apply a proposal to the model
- All review activity is tracked in the proposal log
### Can I still view applied or closed proposals?
Yes, you can still see applied or closed proposals and view the following details:
- **Approved** proposal items in **green**
- **Rejected** proposal items in **red**
- **Proposed** values (pending) in **purple**
### Can I re-open a proposal?
- **Closed** proposals can be re-opened by an **Editor** (the proposal reverts to its last status).
- **Applied** proposals **cannot** be re-opened.
### What if all proposal items are rejected?
- The proposal remains in the **Submitted** state.
- It will not auto-close.
- We recommend that Editors **manually close** such proposals.
---
---
title: "Referencing Variables From Linked Models"
description: "Instead of a single model with all of your variables and formulas, you can structure your work into separate, smaller models. Once linked, you can reference variables between them as described in this chapter."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models
language: en
last_updated: 2026-05-01
---
# Referencing Variables From Linked Models in Lucanet xP&A
## Overview
Instead of a single model with all of your variables and formulas, you can structure your work in Lucanet xP&A (Extended Planning & Analysis) into separate, smaller models. Once linked, you can reference variables between them as described in this chapter.
For an instruction on how to link models, see [Linking Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md).
## Referencing Variables in Formulas in xP&A
Once you have linked models in xP&A, you can easily refer to any of the variables in that linked model when you are writing a formula, just by typing its name. The only difference is that it will show up as a **green variable** within a formula (see [variable types](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md#types-of-variables-in-xpa)), and if you hover over the variable you will see which model it is coming from (and **Cmd/Ctrl+Click** will open the model).
Variable from a linked model
> **Note:** If your linked model variable is broken down by a dimension that is not in your current model, and you want to see the breakdown, you will have to link that dimension to the current model. You can do this either via clicking the dimension button on the variable and selecting the dimension, or by adding the dimension in the left-hand-side panel. See [Linking existing dimensions to models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md). If you do not link the dimension to the model, the variable will just display on an aggregated basis (with no dimension items).
> **Note:** If you reference a linked variable whose model has a different start/end date than the model you are in, any missing values will populate with the [empty value setting](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md).
## Referencing Entire Variables in xP&A
If you want to bring in the entire variable from a linked model, within your current model in xP&A, you can import the variable. This will allow you to visually see (but not edit!) the values of the imported variable across time, alongside the rest of the variables in the current model.
To do this in xP&A, click **New Variable** and then select **Import variable**. You can type in the name of the variable or the model that its in (even if it is not linked yet).
Importing a variable from a different model
It will now show up in the spreadsheet in xP&A as a variable, and will be differentiated by its green name.
Variable that is coming from a linked model
Once you have imported a variable, you can broadly use it like any other variable in your model. You can use it in formulas, and you can add it to visuals. The main restriction is that you cannot directly modify an imported variable's attributes, except for its name and description. This variable gets the rest of its attributes from the model in which it "lives".
If you want to make changes to an imported variable, double-click the variable's link icon in the spreadsheet to "zoom in" to its model, and make the changes in the original model.
Open model in which the variable is defined.
---
---
title: "Refreshing a Data Source"
description: "In order to keep your integrated up to date and to reflect the current status of your historical data, your data sources needs to be refreshed. \n\nYou can refresh your data source manually or using an automatic refresh function, and you can view the history of each data refresh at any time."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source
language: en
last_updated: 2026-05-01
---
# Refreshing a Data Source in Lucanet xP&A
## Overview
To keep your data integrated and up to date in Lucanet xP&A (Extended Planning & Analysis), you need to refresh your data sources regularly.
You can refresh them **manually** or set up **automatic refreshes**. Additionally, you can view the history of each data refresh at any time.
> **Note:** Data sources that have been shared with you **by sharing the model** they are used in can only be refreshed if you have **edit access** to this model (see [Sharing a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md)).
## Refreshing a Data Source Manually (Default) in xP&A
By default, you need to manually refresh a data source whenever you want a data sync to happen.
The easiest way to do this is to [roll your Last actual date forward](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) to the new month, which will prompt you to refresh data sources associated with the current model and any linked models:
Rolling the Last actual date forward
If you need to update an existing historical month with the latest data (up to and including the last actual date), you can trigger a refresh through the [data preview](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source.md) inside a model, or using the **Refresh data** button in the **Data** workspace:
Refreshing a data source from the data preview
Refreshing a data source from the 'Data' workspace
In the **Data** workspace, you can also refresh **all** your data sources at the same time:
Refreshing all data sources from the 'Data' workspace
> **Warning:** To be able to refresh a data source, you need to be the **owner** or have **Edit** permission for a model it has been used in (see [Sharing models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md)).
## Refreshing a Data Source Automatically in xP&A
You can also set up an automatic refresh of a data source:
1. Open the **Data** workspace and click on the desired data source.
2. Navigate to the **Overview** tab.
3. Behind **Update interval**, select the interval at which you would like to automatically refresh the data source.
Configuring an auto refresh of a data source
> **Warning:** - We will make a best effort attempt to refresh at your chosen time, but the refresh can be slightly delayed due to server load and other factors.
> - Even if auto-refresh is set up, data will not be pulled beyond the Last actual date of each model (until the Last actual date is rolled forward). For more information, see [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md).
## Viewing the Data Sync History in xP&A
You can view a full history of your data source refreshes. This means you are able to see a list of all previous refreshes, as well as any new data items, dimensions, or dimension items, within each sync.
To view the data source history:
1. Open the **Data** workspace and click the desired data source.
2. Navigate to the **Overview** tab.
3. The data sync history is displayed on the right-hand side of the tab. Click an event in the history to see its details:
The data sync history
---
---
title: "Relative Time for Variables"
description: "Sometimes variables don't refer to specific calendar time steps of your model (Jan 2022, Feb 2022) but refer to relative time (Month 1, Month 2). In this chapter, you get to know how to format a variable as a relative time."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/relative-time-for-variables
language: en
last_updated: 2026-05-01
---
# Using Relative Time for Variables in Lucanet xP&A
## Overview
Sometimes variables in Lucanet xP&A (Extended Planning & Analysis) do not refer to specific calendar time steps of your model (Jan 2022, Feb 2022) but refer to relative time (Month 1, Month 2). In this chapter, you get to know how to format a variable as a relative time.
## How to Change Variables to Relative Time in xP&A
You can format variables as relative time in xP&A by heading to the format menu. Proceed as follows:
1. Click the pencil icon next to the variable name.
2. Click **Format** or use **Cmd/Ctrl+K**.
3. Activate the check box **Relative Time**.
Using relative time for a variable
4. Relative time steps are displayed in the cells (e.g. **Mo 1**, **Mo 2**), as well as in the drop-down list in presentation mode.
> **Note:** **Note**: If you import or reference a relative time variable in a model in xP&A, it will always obey relative time, i.e. it will align with the time step it is associated with, regardless of the model start date.
>
> For example, if you have **Month 1 Retention** of 100% with a model start date of Jan 2021, and then import that variable into a model that starts in Jan 2022, that retention variable will still align with **Month 1** (which is now Jan 2022 in calendar time).
---
---
title: "Sharing a Folder"
description: "As well as sharing models, you can also share entire folders. This is useful when you have various models that you want to organise in a folder structure, and share with a common set of people (similar to Google Drive)."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-folder
language: en
last_updated: 2026-05-01
---
# Sharing a Folder in Lucanet xP&A
## Overview
As well as sharing models in Lucanet xP&A (Extended Planning & Analysis), you can also share entire **folders**. This is useful when you have various models that you want to organize in a folder structure, and share with a common set of people (similar to Google Drive).
## Sharing a Folder in xP&A
1. Navigate to the start page and select the desired folder.
2. Click the three-dot icon and select **Share** from the context menu.
3. Select the desired user(s) or team(s) and specify the access type:
**Can view**: can see the folder and see the [dashboards of the models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md) inside
**Can edit**: can see the folder and its contents, and create/edit the spreadsheets and dashboards of models inside
**Full access**: can see the folder and its contents, create/edit models inside, and change the sharing settings of the folders/models (you can even unshare the folder with the original creator).
4. Click **Invite**.
Dialog to share a folder
### Granting Higher Access to Specific Models or Folders
When you share a folder, it shares everything within that folder too (including models, as well as folders). Anyone you share the folder with will have _at least_ that much access to all of the models or folders within the folder.
You can also grant higher access to specific models or folders within the folder. For example:
- You are the CFO of Company X.
- You create a folder called **Finance**, and share it with your Finance team by giving them **View access**.
- However, you want your VP Strategic Finance to have edit access to the **Revenue model** within the **Finance** folder.
- You can head to the sharing settings of the **Revenue model** and grant that specific user edit access on the model.
## FAQs
### Can I give someone lower access to a model/folder than I have granted them at the parent folder level?
No. If you share a folder with someone, they will have _at least_ that much access to all of the models or folders within the folder.
### Can I grant someone access to a model that doesn't have any access to the parent folder the model is in?
Yes! The model will just show up by itself on their model home page, as opposed to being within the folder. See more on [Sharing models here](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md).
### If someone is a Viewer user type in my Organisation, can I give them edit access to a model?
No - Viewers can only ever view model dashboards, see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md) for more information.
### Who can move models and folders in/out of folders?
Folder admins can move folders, and model admins can move models if the mover has edit access to the folder they are moving from/to.
---
---
title: "Sharing a Model"
description: "Once you have built a model, you will probably want to share it with others. By default, only you have access to your model, so you'll need to specify how you want to share it with others."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model
language: en
last_updated: 2026-05-01
---
# Sharing a Model in Lucanet xP&A
## Overview
Once you have built a model in Lucanet xP&A (Extended Planning & Analysis), you will probably want to share it with others. By default, only you have access to your model, so you'll need to specify how you want to share it with others.
## Inviting Other Users to View, Edit, Or Propose Changes in xP&A
To invite others to view, edit, or propose changes to a model, open the **three-dot menu** on the top right of the spreadsheet view and choose **Share**.
If you only want **certain people** to be able to access your model, enter their e-mail address in the **Invite new users** dialog, and select the level of access you want to grant them. This option requires this group of people to have their own xP&A account.
Dialog to share a model
The following options are available:
- **Full access**: Users can share and edit spreadsheets and dashboards
- **Can edit**: Users can create, edit, and share models (in the spreadsheet and the dashboard) as well as create proposals, and review and accept [proposals](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) made by other users on the model.
- **Can create change proposals:** Users can [suggest](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) changes to spreadsheet values or dimension items
- **Can view**: see the model dashboard only
If your model is **linked** to other models, you will be prompted if you would like to:
- Apply the sharing settings for **all** connected models at once
- Only apply the sharing settings to the **current** model. For example, you might want to only share a summary P&L, but keep sensitive data within the headcount model private (i.e. salaries).
If you regularly share your model/s with the same group of people, you can share directly with your **team**(e.g. Finance Team), or **organization**(e.g. Company X).
> **Note:** **Notes**:
>
> - If a user is a **Viewer**, they will only ever be able to view the model dashboard.
> - If a user is an **Editor**, they will have whatever access you grant them to the specific model or view, see also [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md).
## Sharing Views of a Model in xP&A
If you only want to share **part** of your model, you can create a **view** and share just that view.
**Note**: You need **Full/Admin access** to the model in order to share views.
To share a view:
1. Navigate to the desired view and click **Share**.
Option to share a view
2. On the **Share** tab, start adding the desired users. Choose if the users can view or edit (see following table).
| Option | Description |
|---|---|
| **Can edit** | User can make live edits to anything visible to them in the view. When you share a view with someone else with **edit** access, they are only allowed to make certain edits to the model. In general, they can only update the variables and dimensions that are visible, and they cannot make any structural changes to the model. Here are the changes that are allowed:
**If the view filters by dimension items** If you have a view that filters a certain dimension to only include some items, users you share that view with can only update those items. They can: • Rename the items (e.g. rename "Engineering" to "AI") • Update the formulas for those items (e.g. change Projected Equipment Costs from $100,000 to $200,000 for the Sales department)
These permissions also account for mappings. For example, if you have a dimension called Employees, where each employee is mapped to a Department, and you share a view including the Engineering department, then the person you share with can: • Add Engineering employees • Remove Engineering employees currently mapped to the Engineering department • Rename Engineering employees • Update formulas for Engineering employees (e.g. change Base Salary from $100,000 to $120,000 for a certain employee)
If the person you share with tries to make a change they're not allowed to make, xP&A will block the change and notify them.
**If the view filters by variables** If you have a view that filters a certain dimension to only include some items, users you share that view with can only update those items. They can: • Rename the items (e.g. rename "Engineering" to "AI") • Update the formulas for those items (e.g. change Projected Equipment Costs from $100,000 to $200,000 for the Sales department)
These permissions also account for mappings. For example, if you have a dimension called Employees, where each employee is mapped to a Department, and you share a view including the Engineering department, then the person you share with can: • Add Engineering employees • Remove Engineering employees currently mapped to the Engineering department • Rename Engineering employees • Update formulas for Engineering employees (e.g. change Base Salary from $100,000 to $120,000 for a certain employee)
If the person you share with tries to make a change they're not allowed to make, xP&A will block the change and notify them.
**If the view filters by scenarios** If the view you share filters out certain scenarios, then users will neither be able to see nor update those hidden scenarios.
**Warning:** If a variable does not have any special formula in a scenario, its value will fall back to the default scenario. Make sure you filter out any variables you don't want a user to see, if they are unchanged from the default scenario. |
| **Can view** | User can view [model dashboard](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md) only, edits are not permitted. If someone has access to a model and to a view within that model, they will be able to see both. See [Filter types](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views.md) for the best way of setting up your view to ensure what is visible is exactly as intended. We suggest previewing your view before you share it, if there is sensitive info. |
| **Can create change proposals** | User can [suggest](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) spreadsheet values and dimension items within a view |
| **Can create change proposals from the dashboard** | User can [suggest](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md) spreadsheet values and dimension items within a view via the dashboard |
## Embedding Your Model in xP&A
You can embed your model on your own website, blog, or 3rd party tools like Notion and Medium. To get the embed code of a model:
1. Open the model.
2. Click **Share** at the top right.
3. Share your model via public or private link.
4. Click **Copy code**.
## Publishing via Public or Private Link in xP&A
You can also share models via a **URL**, which is useful if you do not want someone to have to create an account to view your model/dashboard.
Navigate to the **Publish** section in the **Share** dialog and publish your model. Once published, copy the model's link, and send it to people.
People with this link can view the model dashboard only.
> **Note:** **Notes**:
>
> - **Public** links are easy to guess, so unintended viewers may come across your model.
> - **Private** links require a unique token in the URL for added security, so you can be sure that only people you send it to will be able to view the model (unless they decide to send it to other people).
> - **Privately** published **linked** models are not accessible via the same link, unless they share the same token. If you would like all linked models to be accessed from the **same private link**, simply enter the same token when publishing each linked model. You can use the xP&A-generated token, or enter your own one.
> - When sharing via public or private link, you can give viewers the ability to **clone** your model to use themselves. This is useful for things like **templates**.
## Additional Settings in xP&A
On the **Settings** tab, you have the following options:
- **Allow cloning as a template**: When sharing the model with other users, the users can duplicate this model to use it as a template. For more information, see [Cloning a model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cloning-a-model.md).
- **Allow access to spreadsheet (read-only)**: Activate this option if you want to allow other users to view your underlying model spreadsheet, without letting them edit it.
Additional settings when sharing a model
---
---
title: "Sharing a Model or Folder"
description: "After building a model, you have the option to share this model with other users. You can also organize your model into folders and share folders if you want to grant access to multiple models at once."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder
language: en
last_updated: 2026-05-01
---
# Sharing a Model or Folder in Lucanet xP&A
## Overview
After building a **model** in Lucanet xP&A (Extended Planning & Analysis), you have the option to **share** this model with other users. You can also organize your model into **folders** and share folders if you want to grant access to multiple models at once.
This article contains the following chapters on sharing models and folders in xP&A:
- [Sharing a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md): Once you have built a model, you will probably want to share it with others. By default, only you have access to your model, so you'll need to specify how you want to share it with others.
- [Sharing a Folder](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-folder.md): As well as sharing models, you can also share entire folders. This is useful when you have various models that you want to organize in a folder structure, and share with a common set of people.
---
---
title: "Sharing Data Connections"
description: "By default, data connections and the data sources created from the connections are private to the user who created them. In order to be used by other users, you can share the connection to a data source with them.\n\nThere are two ways to do this:\n\nIf a data source in Lucanet xP&A is used in a model, then anyone with edit or higher access rights to that model can access that data source implicitly. \n\nThe second way is to share the data connection directly with others from the Data workspace. A description of this option can be found in this article."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/sharing-data-connections
language: en
last_updated: 2026-05-01
---
# Sharing Data Connections in Lucanet xP&A
## Overview
By default, data connections and the data sources created from the connections in Lucanet xP&A (Extended Planning & Analysis) are private to the user who created them. In order to be used by other users, you can share the connection to a data source with them.
There are two ways to do this:
- If a data source is used in a model, then anyone with edit or higher access rights to that model can access that data source implicitly. For more information, see [Sharing a Model or Folder](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder.md).
- The second way is to share the data connection directly with others from the **Data** workspace. A description of this option can be found in this article.
## Sharing a Data Connection from the 'Data' Workspace in xP&A
To share an existing data connection:
1. Open the **Data** workspace.
2. Navigate to the **connection** you would like to share.
3. Click the **Share** button in the top right corner:
Share button
The **Share** dialog is displayed as follows, for example:
Options to share a connection
4. Choose the **level of access** you want to grant to the people you share the connection with. The following access types are available:
| Option | Description |
|---|---|
| **View access** | Users with this level of access: • Can use the connection to create data sources • Cannot see other users' data sources created with the connection |
| **Edit access** | Users with this level of access: • Can edit and reconnect the connection • Can use the connection to create new data sources from it • Cannot see other users' data sources created with the connection |
| **Full access** | Users with this level of access: • Can access all data sources created with the connection • Can edit, reconnect and/or delete the connection • Can use the connection to create new data sources from it • Can share the connection with other users |
> **Note:** The **Full access** option is useful for sharing connections like **payroll** and **accounting systems** (where you usually want the users to see all data sources associated with the connection), whereas the more restrictive **Edit access** or **View access** options might be more useful for data warehouses where you want to allow others to create queries or data sources, but not see all of your queries or data sources.
## Viewing Shared Data Sources in xP&A
You can display all connections and data sources that have been shared with you in the **Data** workspace on the **Shared** tab.
This tab also shows the data sources that are used in [models that have been shared with you](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md).
'Shared' tab
---
---
title: "Sharing Views"
description: "Users with full or admin access to a model can share a view with other collaborators to give them only this specifically filtered view on this model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views/sharing-views
language: en
last_updated: 2026-05-01
---
# Sharing Views in Lucanet xP&A
## Overview
In Lucanet xP&A (Extended Planning & Analysis), users with full or admin access to a model can share a view with other collaborators to give them only this specifically filtered view on this model.
## Sharing a View in xP&A
To share a view in xP&A:
1. Choose one of the following options:
- Open the **view selection** on the top left of a spreadsheet, open the **three-dot menu** for the view you want to share and click **Share**:
Sharing a view from the view selection
- Open the **three-dot menu** of a spreadsheet on the top right, click **Share** and select the view you want to share:
Sharing a view from the spreadsheet
2. Click the displayed field to show all available **users, teams,** or **organizations**. Alternatively you can type in the e-mail or name to narrow the selection.
3. Select for the user, team, or organization you want to share the view with their level of access (see following subheading).
4. Close the dialog to save your settings.
The view is then displayed with the number of people or groups of people it is shared with:
A shared view
## Levels of Access for a View in xP&A
The following levels of access are available for a view:
| Option | Description |
|---------|---------|
| No access | The user has no access to the view. |
| Can view | The user can only view, edits are not permitted. |
| Can edit | The user can make live edits to anything visible to them in the view. |
> **Note:** - If a user is a **Viewer**,they will only ever be able to view the model dashboard.
> - If a user is an **Editor** or **Administrator**,they will have whatever access you grant them to the specific model or view.
>
> For more information, see [User Roles in Lucanet xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/user-roles-xPA.md).
### What can be viewed?
- If someone has access to only a view, then they can only see that view.
- If someone has access to a model and to a view within that model, they will be able to see both.
See [Filter Options](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views.md) for the best way of setting up your view to ensure what is visible is exactly as intended.
We suggest previewing your view before you share it, if there is sensitive info.
### What can be edited?
When you share a view with someone with the **Can edit** level of access, they are only allowed to make certain edits to the model. In general, they can only update the variables and dimensions that are visible, and they cannot make any structural changes to the model.
The following changes are allowed:
**If the view filters by dimension items:**
If you have a view that filters a certain dimension to only include some items, users you share that view with can only update those items. They can:
- Rename the items (e.g. rename **Engineering** to **AI**)
- Update the formulas for those items (e.g. change **Projected Equipment Costs** from $100,000 to $200,000 for the **Sales** department)
These permissions also account for mappings. For example, if you have a dimension called **Employees**, where each employee is mapped to a **Department**, and you share a view including the **Engineering** department, then the person you share with can:
- Add **Engineering** employees
- Remove **Engineering** employees currently mapped to the **Engineering** department
- Update formulas for **Engineering** employees (e.g. change **Base Salary** from $100,000 to $120,000 for a certain employee)
If the person you share with tries to make a change they are not allowed to make, xP&A will block the change and notify them.
**If the view filters by variables**
If the view you share filters out certain variables, then users will neither be able to see nor update those hidden variables.
**If the view filters by scenarios**
If the view you share filters out certain scenarios, then users will neither be able to see nor update those hidden scenarios.
> **Note:** If a variable does not have any special formula in a scenario, its value will fall back to the default scenario. Make sure you filter out any variables you do not want a user to see, if they are unchanged from the default scenario.
---
---
title: "Troubleshooting"
description: "This topic describes errors that can occur when working with formulas in Lucanet xP&A. A possible solution is described for all errors."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/troubleshooting
language: en
last_updated: 2026-05-01
---
# Troubleshooting Formulas in Lucanet xP&A
## Overview
This topic describes errors that can occur when working with formulas in Lucanet xP&A (Extended Planning & Analysis). A possible solution is described for all errors.
## Errors in Lucanet xP&A Formulas
If you are getting an error with a variable, you can hover over the **Error** or the variable and xP&A will explain the cause of the error:
Displaying an error in a formula
## Common Errors in Lucanet xP&A
The following error messages can be displayed for formulas in xP&A:
| Error Message | Description |
|---------|---------|
| A function has an incorrect number of arguments. | You used too many or too few parameters to call a function. **How do I fix it?** Check the chapter on [Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/functions.md) in our documentation and use the correct number of arguments in your formula. |
| Aggregation set to None. | You use an aggregated variable in your formula, but the variable's dimension aggregation is set to [None](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables.md). **How do I fix it?** Change the variable's [dimension aggregation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md) or do not aggregate the variable in your formula. |
| Dimension error. | There is some inconsistency in the [variable's dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md). |
| Data error. | The data dimensionality does not match the variable dimensionality. This can happen if you explicitly apply a dimension and connect the variable to a data item that is not broken down by that dimension. **How do I fix it?** Make sure the data item and the variable have the same [dimension](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions.md). Either add the dimension to your data source, or remove the dimension from the variable. |
| It is not possible to use date functions for time aggregations. | Currently, calling date to map monthly, quarterly, annual, or exhaustive timespans to an exact date is undefined behaviour. |
| Variable was expected. | You did not provide a variable when you called a function that only works with variables, e.g. **is_data**. **How do I fix it?** Use a variable as the argument when calling the function. |
| Invalid number error. | Your formula results in an invalid number (e.g. division by zero, sqrt(-2)). **How do I fix it?** Correct the formula, or use the **if_error** function to return an alternative value (e.g. ”Z”) instead of an error. |
| Invalid syntax in formula. | You did not use the correct syntax in your formula, e.g. you forgot the "else" in an if-statement. **How do I fix it?** Check the function documentation in the help menu or on the functions page here. |
| Mappings to a dimension are ambiguous. | There is more than one path from one dimension to another dimension. E.g. Dimension A → Dimension B → Dimension C and Dimension A → Dimension D → Dimension C. **How do I fix it?** Remove one of the dimension mappings in the data table. |
| The linked variable does not exist. | This can happen if you import a [variable from a linked model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/referencing-variables-from-linked-models.md), and then delete the original variable in the linked model. **How do I fix it?** Create and import the variable again. |
| There is a cyclical dependency in this formula. | Your variables cyclically depend on each other, e.g. A depends on B and B depends on A. **How do I fix it?** Change the referenced timesteps of the variables. E.g. if A depends on B, then B can depend on the previous value of A. |
| Unknown expression. | You tried to use a function that does not exist in xP&A. **How do I fix it?** Check out the [Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/functions.md) chapter to see the list of supported functions. |
| Unknown variable. | Your formula uses a variable that does not exist in the model. **How do I fix it?** Import the missing variable from a different model or use a different variable in your formula. |
| You need to aggregate a span using min(), avg(), ... | A span is an array of values, e.g. Variable\[all\] or Variable\[0:t\]. The result of your formula has to be a single number and cannot be a span. **How do I fix it?** Aggregate the span into a single number using an [aggregation function](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md) like sum(Variable\[all\]) or min(Variable\[0:t\]). |
---
---
title: "Troubleshooting for Slow or Large Models"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/troubleshooting-slow-large-models
language: en
last_updated: 2026-05-01
---
# Troubleshooting for Slow or Large Models in Lucanet xP&A
## Overview
The performance of a model in Lucanet xP&A (Extended Planning & Analysis), i.e. the speed of loading or calculating it, depends on various factors:
- Model size (cell count mainly depends on number of time steps, number of dimension items, number of variables, number of scenarios)
- Complexity of the formulas (e.g. a **sumif** formula is slower than a simple addition)
- Complexity of the visuals (charts and tables)
In this chapter, we provide some ideas how slow model performance can be tackled.
## Using the Model Inspector in xP&A
To investigate a model's size (and which linked models, and variables within models, are the biggest culprits), you can use the Model Inspector.
To open the **Model Inspector**, simply press **i** on your keyboard when you are in a model (with no variables selected) and the following dialog will be shown:
The Model Inspector
## Storage Limit in xP&A
If you see the below error message, you have breached the storage limit allowed for the model. Please follow the steps above to go to the Model Inspector and pay particular attention to the **Variable Size Analysis** section.
This will show the largest variables in the model so you know which variables to target in reducing size.
Model size warning
## Other Possible Solutions in xP&A
If the speed and/or performance of your models slow, consider the following options:
- Turn on **Manual recompute.** This means you can make multiple edits to the model, recompute to evaluate them all at once, and save to persist your changes.
To do so, open the [model settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md), and activate **Recompute and save manually** under **Calculation**.
- Hide the visuals pane (top-right of spreadsheet), and/or consider deleting unused visuals, or moving them to a separate model.
- Consider reducing the model granularity and/or the length of your model, in the [time settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md).
- If you are using dimensions (including cohorts):
- Consider if you need the dimension on every variable in your model(s), or just some variables. You can [aggregate away the](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) dimension for the variables you don’t require the breakdown on.
- Consider if you can reduce the number of dimension items in the dimension (e.g. grouping all smaller dimension items into "other" instead of having them each as separate items).
- If you have variables that have a specific value/formula for each dimension item (or multiple overrides within the variable), this will make the model larger as xP&A needs more storage space. Consider if you need this, or could use one aggregate formula instead, or use a [dimension item in an if-statement](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/if-statements-in-formulas.md) (allowing you to dynamically define a variable's dimensional values/formulas without requiring a separate formula for each dimension item).
- With if-statements, consider if you really need a nested if-statement (i.e. if X then Y else if A then B else \[...\]), or if you can use multiple if statements in the same formula (i.e. if X then Y else 0 + if A then B else 0 + \[...\]). The latter is a lot simpler and quicker to compute as the if-statements are separate.
- If you have one big model, consider splitting it up into smaller sub-models. You can [move variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/moving-variables.md) to make these changes easily.
- Consider removing scenarios that are no longer in use.
- If your model is connected to a data source, and the data source is large (either because of its granularity, its dimensionality, etc), then consider aggregating data **in the data source** instead of in xP&A.
---
---
title: "Updating the Data Import from xP&A to CFP"
description: "After the initial import into Consolidation & Financial Planning has been configured and executed for the first time, you then only need to update the CFP import every time you want to transfer updated xP&A data to CFP. \n\nThe steps of this recurring update process are described in this Quick Reference Guide."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/updating-the-data-import-from-xPA-to-CFP
language: en
last_updated: 2026-05-28
---
# Updating the Data Import from xP&A into Consolidation & Financial Planning
## Overview
After the initial import into Consolidation & Financial Planning (CFP) has been configured and executed for the first time, you then only need to update the CFP import every time you want to transfer updated xP&A data to CFP.
The steps of this recurring update process are described in this Quick Reference Guide.
## Creating an Updated Export in xP&A
If you want to transfer updated data from xP&A to CFP, you first need to create an export of the updated data **per model**. Proceed as follows:
1. In the model you want to export the data from, click the **Settings** button the settings icon and navigate to the **Export and download** section.
2. Click **+** to create a new export and configure the steps in the **New export** dialog as follows.
3. Configure the **Export definition:**
- Give the export a clear **name** that matches the model (e.g. "Sales forecast").
- Choose the export type **Raw**.
Configuring the export definition
4. Configure the **Target**:
- Under **Export target**, keep the **Download** preselection
- Under **Export output**, choose **Parquet.**
Configuring the export target
5. Configure the **Content**:
- Choose what data you want to export: **All values**, a specific **View**, or a named **Version**.
If you work with specific planning versions (e.g. "Forecast 1+11"), choose **Version** and select the relevant one. This is required when you need to map different versions to different data levels in CFP.
- Under **Additionally exported columns,** select at least the columns **Variable ID** and **Scenario**. You can optionally activate **Cell location** if you want to drill down from CFP to the data in xP&A.
Configuring the export content
6. Click **Create export**.
The export is created and displayed in the **Export and download** section:
New export in the 'Export and download' section
The export can now be accessed by Consolidation & Financial Planning using the script **Lucanet xP&A #3700-xP&A.SQL.FOS**.
7. Repeat the above steps for each model whose output data you want to import into Consolidation & Financial Planning.
## Updating the Configuration of the Import Script in CFP
To import updated xP&A data into CFP, you need to update the configuration of the import script **Lucanet xP&A #3700-xP&A.SQL.FOS** that is used, to include the new xP&A exports and update the dimension mappings. Proceed as follows:
1. Navigate to the script in the **Scripts** workspace and click **Edit** in the detail view of the script.
Edit the import script
2. On the **Connection** tab, select all the **Export IDs** of all xP&A exports (models) that are to be imported.
Selecting the export IDs
3. Open the **Dimension configuration** tab. The tab is displayed as follows, for example:
'Dimension configuration' tab
4. Click **Refresh dimensions from xP&A** to update the available dimensions from the specified xP&A export(s).
5. Choose how the entity dimension in your xP&A model translates to dimensions in CFP. The following options are available:
- **Use dimension for reporting entity**: Choose this option, when you use a custom dimension in xP&A (not synced from CFP) and want to map it to entities manually.
- **Use dimension for transaction currency code**: This is a legacy option and not needed in current xP&A setups
- **Assign cost centers automatically dependent on OIDs**: Choose this option when you use the **Organization element** structure from CFP in xP&A. The OID (unique identifier per cost center) enables automatic matching.
- **Assign cost centers automatically dependent on homonymous names**: This is a fallback option for matches based on name. Requires a dedicated assignment table.
6. Behind **Dimension mappings**, assign the dimensions from your xP&A exports to the corresponding dimensions in CFP.
7. **Save** the configuration.
> **Tip:** **Best practice:** Always create a separate [assignment table](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-an-assignment-table-for-import-of-xPA-data.md) for xP&A imports to avoid conflicts with other import processes.
## Executing the Import of Updated Data in CFP
Once you created the exports of the updated xP&A data and updated the import script to include these new exports, you can execute the data import into CFP.
Please note that it is not necessary to configure the data source and assignment table again, as these already have been defined during the initial import and will be re-used during every recurring import.
Proceed as follows:
1. Navigate to the **data import** element in the **Importing data into reporting entities** workspace and click **Edit** in the detail view of the script.
Data import element
2. In the detail view, click **Import**. The **Provision via script** dialog is displayed as follows, for example:
Configuration of the data import
Specify the following:
- **Reporting entity(ies)**: Select the reporting entity(ies) in CFP to import into
- **Import type**: Choose **Transaction figures incl. automatic contra entry (only planning)**.
- **Fiscal year and accounting periods**: Set the time range matching your planning horizon.
3. Switch to the tab with the **script name** and go to the **Model configuration** tab. The tab is displayed as follows, for example:
'Model configuration' tab
Configure the following options on the **Model configuration** tab:
- **Export IDs**: ID of the export from xP&A whose values are to be read (selectable options are based on the script configuration).
- **Import variables**: Choose **Selected variables** (recommended) and select individual variables or sections to be imported or choose **All variables**.
- **Multiply value by -1**: xP&A typically stores revenue as positive values, but CFP uses debit/credit logic where revenue (P&L credit) must be imported as negative to display correctly. You can apply this option per variable or per section in the table, or globally via the checkbox at the bottom.
> **Tip:** Structure your models with separate sections for revenue and cost outputs, so you can apply the -1 multiplier cleanly at section level.
4. Switch to the **Import configuration** tab. The tab is displayed as follows, for example:
'Import configuration' tab
Configure the following options on the **Import configuration** tab:
- **Import values**: Choose between **As specified currency** (uses the currency from xP&A) or **As default currency** (uses the entity's default currency in CFP).
- **Scenarios**: Select one or more scenarios to import.
- **Import additional years**: If your model spans more than one year into the future, specify how many extra years to include.
- **Prefix/Suffix**: Optionally add a prefix or suffix to a specific dimension to control how values are mapped (e.g. for sub-ledger account differentiation).
5. Click **Start** to execute the import.
6. After the import has been finished, go to the [assignment table](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/guideline-data-exchange-xPA-CFP/importing-data-from-xpa-to-cfp/creating-and-executing-the-data-import-into-CFP.md) to map any unrecognized values to the correct GL accounts.
---
---
title: "User Roles in Lucanet xP&A"
description: "There are three distinct types of permissioning in xP&A. Each type defines which what a user can see and do in Lucanet xP&A."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/user-roles-xPA
language: en
last_updated: 2026-05-01
---
# User Roles and Permissions in Lucanet xP&A
## Overview
In Lucanet xP&A (Extended Planning & Analysis), users can control user access and permissions at three levels:
- Organization-level permissions (i.e. user roles, teams)
- Model-level access
- Folder-level access
## Organization-Level Permissions and User Roles in Lucanet xP&A
At the **organization** level in Lucanet xP&A, there are three user roles with different types of permissions:
- **Administrators:** Administrators can:
- Create, edit, and share models.
- Add and remove people to and from the organization
- Create teams, e.g. **Finance Team** or **Marketing** Team.
- **Editors**: Editors can:
- Create, edit, and share models
- Create proposals and accept proposals on the model
- **Data collectors**: Data collectors can propose edits to models with some other actions allowed. They **can:**
- Write comments
- Annotate charts
- Propose changes to variables and dimension items
- Propose to add, rename, delete or link dimension items
But they **cannot:**
- Add, delete, or update visuals, variables, groups, and sections
- Add, delete, or update models, folders, or data sources
- **Viewers**:
- **Can** view dashboards shared with the organization but **cannot** access underlying models to make changes.
- **Can** create their own models, but **cannot** share models with the organization.
The user roles are assigned in the **Administration** section of the **Lucanet CFO Solution Platform** (see [User Management](https://support.lucanet.com/en/documentation/administration/user-management.md)).
## Model-Level and Folder-Level Permissions in Lucanet xP&A
The permissions a user has for actions on a model depend on the level the model (or the folder the model is contained in) is shared with the user.
In Lucanet xP&A, sharing options for an entire model are:
- Full access
- Can edit
- Can create change proposals
- Can view
In addition, a model can be shared **via public or private link** or only a limited view of the model can be shared.
For more information, see [Sharing a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder/sharing-model.md) and [Using Views](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views.md).
---
---
title: "Using Charts"
description: "Charts can be used to visualize your data, either within the Spreadsheet workspace or the Dashboard workspace."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts
language: en
last_updated: 2026-05-01
---
# Using Charts in Lucanet xP&A
## Overview
**Charts** in Lucanet xP&A (Extended Planning & Analysis) can be used to visualize your data, either within the **Spreadsheet** workspace or the **Dashboard** workspace. Charts are useful if you want to visualize several variables.
The most commonly used chart types are **bar** or **line** charts, or a **combination** of both. An instruction on how to use and edit them is described below.
But there are also other chart types available, depending on the purpose of the chart.
For better collaboration with others, you can **import** charts from other models, and **copy** or **export** them as an image.
## Creating a Chart in xP&A
To create a **chart** in xP&A:
- In the **spreadsheet** workspace:
- Right-click a variable and choose **Create chart.**
- Click the **Charts** icon in the top-right corner the charts icon to open the **Charts** side panel and choose **New chart.**
- In the **Dashboard** workspace, click the **+** icon at the bottom left.
Choose the desired **chart type** from the list of available visualization options:
Visualization options
> **Note:** To add the variables you want to visualize, drag & drop them onto an existing chart from the **Spreadsheet** workspace (when you have the charts side panel open).
## Editing a Chart in xP&A
You can edit a chart
- In the toolbar of the **Spreadsheet** workspace, by clicking the **Charts** icon
- In the **Dashboard** workspace
The options to edit a chart can be found in the toolbar at the top right of the chart visual:
Table settings toolbar
## Options for Bar and Line Charts in xP&A
The following options are available for charts of type **Bar** and **Line**:
### General Options
| Option | Description |
|---|---|
| **Three-dot menu** | You can use the three-dot menu to: • **Copy** the chart as an image • **Download** the chart as an image • **Clear annotations and highlights** from the chart • Add a **description** • **Delete** the chart |
| **Time aggregation** | You can use the roll-up/drill-down column drop-down list to determine how variables are displayed across time (e.g. quarterly, yearly), and toggle between them easily.
**Tip:** See section _Time Aggregation_ in [Aggregation Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md) if you want to change how a variable aggregates into quarters or years (the default setting is **sum**). |
### Setup Options
To open the setup options, click the edit icon in the top-right corner of a chart visual and go to the **Setup** tab:
Chart setup options
The following setup options are available:
| Option | Description |
|---|---|
| **Series** | You can easily add, rename, reorder (by drag&drop), and delete variables in the **Series** section. You can also choose, instead of adding variables one-by-one to a chart, to add the entire group or section to the chart. The chart always stays in sync with the spreadsheet when variables get added or removed from a group or section.
**Variable's Setup Details**
By double-clicking on a variable in this section, you can: • Change the **color** of the bar or line for this variable • Plot variables on the **left or right axis** • Plot one variable as a **line**, and another as a **bar** • Remove the **dimensions breakdown** (see below explanation on Dimensions breakdown) • Add **scenarios** and **versions** for the variable • Display the variable's **value** and/or **growth rate** as a **label** • Open the **advanced** setting options |
| **Targets and events** | You can use this section to display certain data points in the chart and assign a color to them: • **Targets** • **Events** • Vertical **Today** line • [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) line |
| **Date range** | By default, the chart will display the entire model date range. If you would like to shorten the date range, you can select a custom start and/or end date for the chart here. |
| **Dimensions breakdown** | If a variable is broken down by a **Dimension**, then by default, xP&A will keep the breakdown. If you wish to 'aggregate away' the underlying dimension items, you can do so by clicking the **variable** and clicking the minus icon in the **Dimensions breakdown** section. |
| **Filters and controls** | In this section you can add filters to the table, e.g. a **time** filter or a filter to arrange different versions and/or scenarios next to each other. |
### Display Options
To open the display options, click the edit icon in the top-right corner of a chart visual and go to the **Display** tab:
Chart display options
The following display options are available:
| Option | Description |
|---|---|
| **Enable drill-down** | You can use this option to enable a [drill down on underlying integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data.md) (transactions).
Anyone viewing the dashboard will be able to view these underlying details. Note that this information may be sensitive. |
| **Show stacked bars** | You can use this option to switch between visualization as stacked bars or separated bars. |
| **Display as** | You can use this option to switch between visualization as stacked **bars** or **lines**. |
| **Axes** | You can use this option to plot variables on the left or right axis. |
| **Labels** | You can use this option to display the variable's **value** and/or **growth rate** as a **label**. |
### Advanced Options
To open the advanced setting options, click the edit icon in the top-right corner of a chart visual and go to the **Advanced** tab. The following advanced options are available:
Advanced chart options
## Other Chart Types in xP&A
Apart from **Bar** and **Line** charts, there are other chart types available that can be used depending on the purpose of the data visualization:
| Chart type | Description |
|---|---|
| **Text** | **Text** is useful for **providing context** alongside your models and dashboards (e.g. variance analysis, model reforecast reasoning etc).
When you choose this option, a text field is displayed. In this text field you can: • Type and format text like you normally would in any other text editor • Add hyperlinks and ordered lists • Reference live variable values by typing `/` (e.g. /Revenue), then choose which time step you want to reference (last actual date, today, and final). **Note:** [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) will be the default option when a Last Actual Date exists in the model. This means that when you refresh your data (and have a new Last Actual Date), your variable references within a text on dashboards will auto-update, too. • Mention people in text by typing. **Note:** This does not notify them via email, rather it is a way to name others within commentary where relevant. • Add headings using the following shortcuts: `#` Heading (big heading), `##` Heading (medium heading), `###` Heading (small heading) |
| **KPI** | A **KPI chart** lets you see a big number for the value of a variable, or set of variables. Use it to draw attention to important outputs of your model. |
| **Distribution** | **Distribution charts** are useful to plot variables that have uncertainty. Create a chart, then go to the chart settings, and click **static**, then choose **Distribution**. |
| **Listogram** | The **Listogram chart** is useful for visualizing things like: Revenue by Geography, Opex spend by Team/Vendor, Payroll spend by Department/Country etc.
With a listogram, you can: • Sort a variable by its dimension items, and easily discern which items are the largest/smallest, and their relative proportion to the whole. • Show the breakdown as a percentage or a value, and you can also limit the number of items shown (e.g. if you only want to see the top 10). |
| **Pie** | **Pie charts** are best used when you want to show parts of a whole in a simple, instantly digestible way, e.g. a breakdown of revenue by dimension, where a pie chart makes it easy to observe which dimension represents the highest proportion, or to compare two variables. |
| **Static Bar** | A **Static bar chart** shows a snapshot comparison of categories at a single point in time. It is designed for variable comparisons, not trends, e.g. to compare different revenue in the same time period. |
| **Waterfall** | A **Waterfall chart** is a powerful visualization tool that allows you to drill into the differences between variables, versions, or scenarios, making it an excellent choice for storytelling and analysis, such as the difference between starting ARR and ending ARR, budget vs. actuals, or default vs. aggressive scenarios.
Waterfall charts consist of a starting bar, an ending bar, and intermediate bars that break down the difference between them.
This chart type supports multi-bridge or multi-step waterfalls, where the ending bar of one bridge becomes the starting bar of the next. |
### Setting Up a Waterfall Chart
To set up a waterfall chart, go to the **Setup tab** and configure the following:
1. Select the time **granularity** of the data you would like to visualize.
2. In the **Bars** section:
- Set the **start value** by selecting the desired variable (e.g., Total Revenue) and adjust the **time period** if needed (e.g., total revenue for 2025).
- Set the **end value** by selecting the target variable (e.g., Net Profit). The **time period** will default to match the start value.
- Add **intermediate values** as needed (e.g., Cost of Goods Sold, Operating Expenses) to show the breakdown of changes.
- If you recorded values as positive values but want to visualize them as negative values (and vice versa), click on the value and activate the option **Invert value**.
3. Optionally, customize the **labels** for each bar.
Example of a waterfall chart
## Importing Charts in xP&A
If [models are linked](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md), you can easily import charts from one model into another, just like you can import variables. For step-by-step instructions, see [Importing or Exporting Charts](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts/importing-exporting-charts.md).
---
---
title: "Using Comments and Descriptions"
description: "There are two main areas for commenting in Lucanet xP&A: In the spreadsheet, to collaborate with fellow model builders and editors. On the dashboard, to collaborate with your end-users, e.g. your business partners, investors etc"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/using-comments-and-descriptions
language: en
last_updated: 2026-05-01
---
# Using Comments and Descriptions in Lucanet xP&A
## Overview
There are two main areas for commenting in Lucanet xP&A (Extended Planning & Analysis):
- In the **spreadsheet**, to collaborate with fellow model builders and editors
- On the **dashboard**, to collaborate with your end-users, e.g. your business partners, investors etc
Descriptions, by contrast, are more permanent explanations of a variable/formula — an ongoing guide for anyone looking at the model. This article tells you everything you need to know about comments and descriptions in Lucanet xP&A.
## Adding a Comment on Variables and Cells in Lucanet xP&A
Start a comment thread on a variable in Lucanet xP&A by using **Shift+C** on your keyboard, or right-clicking and using the command **Add comment**. You can either comment on the variable as a whole, or comment on a specific cell within the variable (e.g. specific month or dimension item).
Create comment for a variable
If a comment exists, a yellow triangle is displayed in the cell:
Display of an existing comment
## Adding a Description to Variables and Formulas in Lucanet xP&A
Descriptions in Lucanet xP&A are meant to be more permanent explanations of a variable/formula. You can think of them as an ongoing guide for anyone looking at the model. Add a description by right-clicking and using the command **Add Description**.
Adding a description to a variable
You can edit an existing description by double-clicking on it.
> **Note:** If you create a description for a variable in the Inputs section, it also appears on the [Dashboard](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md).
## Adding an In-Line Formula Comment in Lucanet xP&A
You can also add comments within your formulas with a double slash **//**. Everything between the double slash and the end of the line will be ignored by xP&A when calculating.
## Comment Permissions in Lucanet xP&A
There are two main areas for comments in Lucanet xP&A: in the spreadsheet, and on the dashboard.
- Those with **Edit (and above) access** to a model can see and interact with _all_ comments across the spreadsheet and the dashboard.
- Those with **View access** only can see/interact with comments on the dashboard.
- If you only have access to the dashboard via a public/private link, you cannot see/reply to existing threads or create new.
- Comments on the spreadsheet are not shown in a read-only spreadsheet on dashboard.
Comment threads in Lucanet xP&A only show up in the views and/or scenarios they were created in, and only for those who have access to those views and/or scenarios. For example, if you create a comment in the High Spend scenario, only those who have access to the High Spend scenario will be able to see/reply to the thread.
---
---
title: "Using Currency and Currency Translation"
description: "Variables, if set to Currency format, have a Currency drop-down where you can explicitly choose the Currency (e.g. USD, JPY, GBP), which will set the currency prefix symbol (e.g. $ ¥ £) or wording (e.g. AUD)."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/currency---fx-conversion
language: en
last_updated: 2026-05-01
---
# Currency and Currency Translation in Lucanet xP&A
## Overview
Currency settings and currency translation in Lucanet xP&A (Extended Planning & Analysis) allow you to flexibly set up your planning in multiple currencies.
As a first step, currency translation in Lucanet xP&A must be set at **organization level**.
If you wish to use different currency translation behaviors in Lucanet xP&A at model, variable, or dimension level, you can adjust the settings for these levels individually.
- Currency settings at **model level** can be used to either display the data in the local currency or in the display currency.
- Currency settings at **variable level** can be used to edit the local currency and exchange rate for individual variables or dimensions.
- Currency settings at **dimension item level** can be used to define a default currency for the dimension items used in variables. If needed, the default can be changed for certain dimension items in variables.
- In addition, you can set a **currency on data sources** for the data to be pulled in.
> **Note:** The translation of the different currencies is always based on the configured exchange rates.
>
> - Users who are also working with **Lucanet Consolidation & Financial Planning** (CFP) automatically use the exchange rates configured in CFP.
> - For users who do not work with CFP, currency translation is based on **Auto rates** from an external provider.
## Setting the Currency at Organization Level in Lucanet xP&A
As a first step for automatically translating currencies between different variables and data sources in xP&A, you have to set the currency for your organization. Proceed as follows:
1. Open the **Settings** workspace and navigate to the **Currency** organization settings. Currency translation is enabled by default.
Enabling currency translation at organization level
2. Based on whether you use the Lucanet solution **Consolidation & Financial Planning** (CFP) or not, the source of the exchange rates used for currency translation will be set by default:
- **Auto rates** if you do not have CFP enabled as a solution - this uses live rates from the external provider **Open Exchange Rates**.
- **CFP rates**, if you have CFP enabled as a solution - this uses exchange rates configured in **Consolidation & Financial Planning**.
To change this pre-setting, please contact our Customer Support.
> **Warning:** Please note that these organizational settings apply for all models, variables, and dimensions and cannot be changed at a lower, individual level. I.e., if you choose **CFP rates** for your organization, you cannot select **Auto rates** for a model, a variable or a dimension, but CFP rates will always apply.
>
> **Important**
>
> Switching between **Auto rates** and **CFP rates** after you have set up currencies in your model may result in loss of information. If the system is not able to map a currency when changing the type of exchange rates, the affected variables will be converted to plain numbers and lose their currency formatting.
>
> **Example:** If you created a custom currency called "ZZZ" while using CFP rates, switching to Auto rates will convert any variables using "ZZZ" to numerical variables (without currency settings), since "ZZZ" is not a recognized currency code in Auto rates and can therefore not be mapped.
3. Choose the **default currency** of your organization.
This default currency will be used for all newly created models and can be adjusted individually in the [currency settings at model level](#setting-the-currency-at-model-level-in-lucanet-xpa).
4. If you use **CFP rates** for currency translation, configure the additionally displayed **Exchange rates** section by choosing for each currency relation the **data level** in CFP to be applied to the exchange rate table in xP&A.
Selecting the exchange rates from CFP
5. Click **Apply**.
## Setting the Currency at Model Level in Lucanet xP&A
By default, each new model in Lucanet xP&A will use the currency translation settings configured at organization level.
If you want to use different currency translation behavior in a model, you can adjust it in the [model settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md). These model-level settings determine how the model interprets and translates values throughout all variables (unless you configure individual translation behavior [at variable level](#setting-the-currency-at-variable-level-in-lucanet-xpa).)
1. Click the gear icon to open the **Model Settings:**
Currency options in the model settings
2. Under **Exchange rates**, assign for each exchange rate relation the exchange rates from CFP to be used.
All exchange rates for which an [exchange rate table](https://support.lucanet.com/en/documentation/consolidation-financial-planning/platform-dimensions/currency-translation/create-configure-exchangerate-table.md) has been defined in **Consolidation & Financial Planning** are available for selection.
If necessary, you can update the selection using the **sync button** or edit the available exchange rates in **Consolidation & Financial Planning** using the link **Edit in CFP**.
3. Select the **Default currency** for the model.
4. Select the **Default exchange aggregation type:**
- **Average exchange rate**
- **Closing exchange rate**
5. Click **Apply changes**.
## Setting the Currency at Variable Level in Lucanet xP&A
By default, a variable in Lucanet xP&A uses the same default currency and currency translation settings as the model it is used in.
However, you can change the currency settings for each variable, e.g., to set a variable to USD even if the model is EUR.
To individually set the currency of a variable:
1. Click the edit icon or the icon to the left of the variable name.
2. Click the currency icon to set the **Currency** data type for the variable.
3. Choose the **currency** and the **exchange rate aggregation type** from the drop-down lists:
Currency settings for a variable
The variable is then displayed with the **Currency** data type icon and all values of the variable are displayed in the set currency and with the corresponding currency symbol:
Variables with a set currency
> **Warning:** The following constraints apply when setting the currency for a variable in Lucanet xP&A:
>
> - Only those currencies for which an exchange rate table has been defined in the [model settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md) are available for selection.
> - If a variable in EUR uses a variable in USD, **automatic conversion** occurs using the model’s currency settings.
## Setting the Currency at Dimension Item Level in Lucanet xP&A
For variables with dimensions (e.g., **Region**, **Entity**, **Country**) in Lucanet xP&A, different currencies can be assigned per dimension item.
**Example**:
- Revenue \[US\] uses USD
- Revenue \[France\] uses EUR
- Revenue \[UK\] uses GBP
Totals always use values converted into the variable’s currency before aggregating.
You can set a **default currency** for each dimension item in the [Dimension Settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md). This saves time when you have many variables using the same dimension item, as the variables by default use this currency then.
If needed, you can also specify individually for each variable, if the dimension items used therein use a different currency.
### Setting a Default Currency at Dimension Item Level in Lucanet xP&A
You can set a default currency at the dimension item level in the [Dimension Settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md) which will be used by every variable using this dimension item as default.
1. Open the dimension details by clicking the dimension name.
2. Click the **+** icon in the column header and choose **Show currency column**.
Show currency column
3. In the currency column, click the currency cell and select the default currency. Choose one of the following options:
- Choose the **default currency** from the list of available currencies.
- Choose **Unset** if no default currency is needed.
Choosing the default currency
> **Note:** Keep the following in mind after setting a default currency for a dimension item in Lucanet xP&A:
>
> - Once a default has been set, new currency variables using this dimension will automatically use the set currency as default.
> - Existing variables are not automatically changed but they keep their current settings.
### Setting a Currency for a Dimension Item in a Variable Individually in Lucanet xP&A
If you want a certain dimension item in a variable to use a different currency than the default currency set in the dimension settings, you can assign an individual currency in the model:
1. Open the **Spreadsheet** view of the model.
2. Navigate to the desired variable and expand the list of dimension items under a dimension.
3. Click the **currency icon** on the right of the dimension item name and choose one of the following options from the menu:
- **Parent default**, if the dimension shall use the variable's default currency or the parent dimension's currency
- **Default currency**, if the dimension item shall use the default currency set for this dimension item in the dimension setting (only available if a default is set as described in the previous sub-heading).
- Choose a **specific currency** and the **exchange rate aggregation type** from the drop-down lists.
Currency options for a dimension item in a variable
4. The variable using this dimension item is then displayed with the corresponding currency symbol.
> **Tip:** **Understanding Currency Inheritance**
>
> The system uses the following hierarchy in Lucanet xP&A to determine which currency applies to a dimension item (from highest to lowest priority):
>
> 1. Explicit currency set on dimension item in the model (variable-level override)
>
> 2. Dimension default currency (from dimension settings)
>
> 3. Parent dimension's currency (if a variable has multiple dimensions)
>
> 4. Variable's default currency (the currency set on the variable itself)
>
> **Example scenario:**
>
> Variable **Revenue** has **USD** as its default currency
>
> Dimension **Region** has **EUR** set as default for **France**
>
> - If you select **Dimension default** for **Revenue \[France\],** the dimension item will use **EUR**
> - If you select **Parent default** for **Revenue \[France\]**, the dimension item will use **USD**(the variable's default)
> - If you select **GBP** individually, the dimension item will use **GBP** regardless of any defaults
### Important Behaviors When Changing the Currency Settings for Dimension Items in Lucanet xP&A
The following behaviors apply in Lucanet xP&A when you change currency settings for dimension items:
**Non-Currency Variables**
- If a variable is **not** a currency type (e.g., count, percentage), dimension item currency settings are ignored
- Currency settings only apply to variables with a currency unit type
**Changing Defaults**
- If you update a default currency in the dimension settings, only dimension items set to **Dimension default** will be affected
- Dimension items with explicit currency selections remain unchanged
**Removing the Default Currency**
- If you remove a default currency from the dimension settings, all dimension items using **Dimension default** will fall back to **Parent default** (the variable's currency)
- A confirmation warning will appear before this change is applied
### Example Workflow for Currencies at Dimension Item Level in Lucanet xP&A
**Scenario:** You have a **Revenue** variable broken down by **Country**(**US, UK, France, Germany**).
1. Set up the default currency in the dimension settings:
- US → USD
- UK → GBP
- France → EUR
- Germany → EUR
2. Create your revenue variable and set its unit to Currency with USD as the variable default.
3. **In the model**, each country row will automatically use the **Dimension default**:
- Revenue \[US\] shows in USD
- Revenue \[UK\] shows in GBP
- Revenue \[France\] shows in EUR
- Revenue \[Germany\] shows in EUR
4. The **Total** row converts all values to USD (the variable's default) before summing.
5. To override a specific **dimension item**, click the currency icon and select a different currency or **Parent default** to use the variable's currency instead.
## Setting the Display Currency of a Model in Lucanet xP&A
By default, a model in Lucanet xP&A displays all currencies in the **local currency** that has been configured for them.
You can change this setting so that the variables and dimensions are displayed in another display currency, converting all the currencies based on the configured exchange rates.
To do so, open the currency options in the top ribbon of a model and choose, if you want to display the local currency or any other currency for which an exchange rate has been defined:
Options to change the display currency of a model
> **Note:** Please note that the editing of values occurs in the local currency that is set on the variable or dimension.
## Currency Translation of Connected Data in Lucanet xP&A
You can set a currency for every data source used to [integrate data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md) into Lucanet xP&A from a source system.
**General Behavior**
When connected data that has a currency set is connected to a variable in a different currency, xP&A will automatically convert all values pulled in from a data source to the currency set for the variable:
- e.g. if your variable is in AUD, but you connect data that is in USD, xP&A will convert the USD data values to AUD
- e.g. if your data is in USD but you want to see how that converts to EUR, set the variable to EUR and xP&A will convert USD to EUR
**Behavior With Multiple Data Sources**
If more than one data source is connected to the same variable, **all data sources** are automatically converted into **one target currency**.
By default, the first added data source’s currency becomes the initial target currency.
You can override this behavior in the [variable’s currency settings](#setting-the-currency-at-variable-level-in-lucanet-xpa). All other data sources connected to this variable will be converted into that variable's target currency.
### Setting the Currency for a Data Source in Lucanet xP&A
How you set the currency for a data source in Lucanet xP&A depends on the type of data source.
**For CFP data sources**
For CFP data sources, the currency is assigned during the [set-up process](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/connecting-to-a-data-source/connecting-to-a-lucanet-cfp-data-source.md) in the **Select ledger** step under display currency:
Currency settings of a CFP data source
**For all other data sources**
For all other data sources, the currency is set after the data source has been created. To do so, go to the **Overview** tab of the data source and choose the **currency** and if you want to use the **average exchange rate** or **closing exchange rate** for conversion.
Currency settings for a data source
> **Note:** Keep the following in mind about currency settings for data sources in Lucanet xP&A:
>
> - Only the user that created the data source can update the currency settings.
> - For common data sources, currency settings are automatically detected and set by xP&A.
> - For other data sources where xP&A cannot auto-detect the currency (e.g. Google Sheets), currency can be manually set (but currency settings are completely off by default).
## FAQ on Currency Translation in Lucanet xP&A
This section answers frequently asked questions about currency translation in Lucanet xP&A.
### Where can I see the exchange rates used? Where does xP&A source the exchange rates from? Can I adjust the exchange rates used?
You can see the exchange rates for each period used by drilling-down into the cells of the converted variable.
### Does xP&A calculate currencies over two exchange rate tables?
**Example**:
From **MXN** to **EUR** through **MXN** to **CHF** and from **CHF** to **EUR**(if there is no exchange rate table for MXN to EUR)?
**Answer**
**No**, xP&A does not perform currency triangulation across multiple exchange rate tables. If a direct **MXN–EUR** rate is missing, the system will only use the inverse of an existing rate. E.g. if you have **MXN** to **CHF** configured, xP&A will know the rate from **CHF** to **MXN** but not to other currencies.
### Why don't Payroll / HRIS data sources have currency auto-set in Lucanet xP&A?
In Lucanet xP&A, Payroll/HRIS data sources do not have currency set because often different employees are paid in different currencies. Our Headcount wizard shows how to translate all employees into one common currency using a **Currency** dimension, and a user-populated exchange rate variable. We do not recommend setting a data-source level currency for this data source, unless every employee is paid in the same currency.
### What happens when I have "future" data that goes beyond what xP&A has exchange rates for?
For any periods where xP&A cannot access an historical exchange rate, xP&A will carry the latest historic rate forward, and convert "future" data values at that rate. For example, in a monthly model, if there are historical exchange rates until November 2023, but you have data available and connected for December 2023, xP&A will convert the December 2023 value using the latest rate from November 2023 (depending on whether data source is set to **Average** or **Closing exchange rate**).
### What is the "Custom" currency option in Lucanet xP&A?
If you use a currency that is not on our list (e.g. a certain cryptocurrency), you can select **Custom** (at the very bottom of the list) and set your own prefix/suffix to reflect the currency.
Working with custom currencies
> **Note:** If you have a **Custom** currency set, xP&A will not be able to do any auto-translation.
### What if I don't want to use xP&A's currency translation?
If you don't want to use currency translation, you can switch off the feature on your organization level (see [Configuring Currency Translation at Organization Level](#setting-the-currency-at-organization-level-in-lucanet-xpa)).
### What if there is data present for the current period (e.g. month in a monthly model), but the period is not yet finished?
For any data items that are constant (i.e. non-time-varying), xP&A will convert these at the latest completed period's rate. For example, in a monthly model, if there are historic FX rates until November 2023, but the current date is 15th December 2023, xP&A will convert the constant value using the latest rate from November 2023 (depending on whether data source is set to **Average** or **Closing exchange rate**).
Lucanet xP&A uses the same logic for data connected to [models without a time dimension (i.e. granularity of None).](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md)
## Different Ways to Set Up Your Consolidation Models in Lucanet xP&A
There are many ways you can set up your consolidation in Lucanet xP&A.
You can either have no entity breakdown (in which case you would drill-down to see detail at the entity level), or you can use dimensions to break down by entity (see below) which means you can easily visualise historics by entity, and forecast by entity, too.
'Marketing' is broken down by Entity (UK, US), and data is connected at the entity level
To set up entity-level breakdown in Lucanet xP&A:
- [Create a dimension called 'Entity'](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md), and add a dimension item for each entity.
- [Breakdown the variables by this 'Entity' dimension](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md), and connect data items from each entity to the relevant entity row.
> **Note:** You can also have **separate models** **for each entity**, and then have a linked consolidation model that combines them together.
>
> Note, however, that we do not recommend this, as (1) you will not be able to take advantage of our automatic currency translation (unless you also connect the consolidated model to data from each entity), (2) adding extra entities would be manual (building an extra model, vs. simply adding an extra dimension item in the **Entity** dimension as per above).
---
---
title: "Using Dashboards"
description: "Dashboards are a nice way for others to view and interact with your model. It shows your model's input variables at the top, with its charts underneath. You also have the option to show them a read-only spreadsheet view, too."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards
language: en
last_updated: 2026-05-01
---
# Using Dashboards in Lucanet xP&A
## Overview
Dashboards in Lucanet xP&A (Extended Planning & Analysis) are a nice way for others to view and interact with your **model**. It shows your model's input **variables** at the top, with its **charts** underneath. You also have the option to show them a read-only **spreadsheet** view, too.
Dashboards can be useful in various contexts:
- For sharing with current or potential investors
- For collaborating with non-finance team members
- For model-builders that want to zoom out from the detail of the spreadsheet
## Adjusting the Input in xP&A
Dashboard viewers can adjust the value of the input variables to see what happens in different situations. These changes aren't saved to your model, unless they have edit access, in which case they'll see a **Save changes** button.
Each variable in the **Inputs** section of your model will appear as an adjustable input at the top of the **Dashboard**, see also _Input Section_ under [Using Sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md).
The adjustable inputs section of the **Dashboard** is split up into **tabs** if variables are grouped. This makes it easy to navigate when there are lots of input variables.
If you don't want a variable to appear as an adjustable input, move it out of your model's **Inputs** section.
## Adding Commentaries or Descriptions in xP&A
You can add **text** on your dashboard and add **comments** alongside your visuals or metrics.
To create a comment, click the **comment** icon in the toolbar of the element that you want to comment on:
Comment option for charts
To add a **description**, click the **settings** icon on the top right of the dashboard and add a description in the **Dashboard settings**.
---
---
title: "Using Dimensions"
description: "Dimensions are Lucanet xP&A’s most powerful concept. This topic conceptually explains dimensions so that you can use them in your models."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions
language: en
last_updated: 2026-05-01
---
# Using Dimensions in Lucanet xP&A
## Overview
Dimensions are the most powerful concept in Lucanet xP&A (Extended Planning & Analysis). This topic conceptually explains dimensions so that you can use them in your models.
This section also contains the following chapters on using dimensions in xP&A:
- [Creating and Editing Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md): Dimensions allow you to build your business' structure directly into your financial models, removing the need for formula duplication and lookups.
- [Aggregating Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md): The dimension aggregation function determines how the values of different dimension items are combined into one value.
- [Dimensions, Variables, and Formulas](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md): Step-by-step instructions on how to add, modify, and remove dimension breakdowns from variables in a data model, and how to apply formulas across dimensions.
## A Dimension is Basically a List in xP&A
Suppose you are building a financial model for your online coffee business. You sell 10 different products (**SKU**), each with a different price.
In xP&A, you can create a dimension called **SKU** with each product as its own item:
Dimension 'SKU' with dimension items
## Dimensions Let You Break Your Variables Down in xP&A
In a spreadsheet you would create a row for each **product**, and a column for **Price**:
Products with prices in a spreadsheet
In xP&A, you can create a single **Price** variable, broken down by your **SKU** dimension:
Variable 'Price' with dimension 'SKU'
## Dimensions Flow Through Your Formulas in xP&A
Suppose that you have to pay 20% in taxes on each sale, and you want to calculate your post-tax revenue for each product.
In a spreadsheet, you would have to create 10 new rows and do a separate calculation for each product.
In xP&A, you can simply do the calculation once, and xP&A will automatically calculate it for each dimension item separately.
Calculated dimension items
## Dimensions Can be Modified On-The-Fly in xP&A
Suppose that you add a new product to your offering.
In a spreadsheet you would have to find every instance of your product list in your model, insert a new row in the right place, and then fill in the correct formula for it.
In xP&A, you can simply add your new product to your **SKU** dimension, and xP&A will automatically include it wherever the SKU dimension is used.
## Dimensions Can Have Hierarchies (Levels) in xP&A
If your dimension has an inherent hierarchy, e.g. your dimension is **Group** and contains **Divisions**, **Branches**, and **Shops** that are rolled up, you can build your dimension in xP&A in order to display and aggregate data at the corresponding level.
To create this hierarchy in the **dimension settings**, simply grab a dimension item on the left and drop it under the dimension it belongs. This automatically assigns levels (top items are level 1, their children level 2, and so on). For more information, see [Creating and Editing Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md).
In the following example, **Division 1** is level 1, **Branch A** is level 2 and **Shop 1, 2 and 3** are level 3:
Hierarchy of a dimension
## Dimensions Can Have Attributed Types in xP&A
In addition to levels, dimensions in xP&A may also have **types**, which are classifications you can assign to items.
Types may align with levels, but don’t have to.
For example, you could have a **Shop** type where **Shop 5** and **Shop 6** are grouped under **Shop 4**.
In models, you can group the dimensions either by **types** or **levels**. For more information, see [Creating and Editing Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md).
Group by types
## Dimensions Can be Linked to Each Other in xP&A
You think about your products falling into two different groups: **Coffee beans** and **Coffee equipment**.
In xP&A, you can create a dimension called **Product Group**, link it to the **SKU** dimension, and then assign each **SKU** to a **Product Group.** (For more information, see [Creating and Editing Dimensions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md).)
Linked dimension
## Dimensions Facilitate “Lookup” Operations in xP&A
In xP&A, dimension breakdowns can replace the VLOOKUP-style formulas you would otherwise need in a spreadsheet. Suppose that your taxes are not just 20% across all products, but that there is a different tax payable on food (e.g. coffee beans) versus coffee equipment.
In a spreadsheet, you would do the following:
1. Set up a lookup table between **SKU** and **Product Group**
2. Break your tax assumption out into separate values for each **Product Group**
3. Replace your tax calculation formulas with VLOOKUPs (or similar) to use the correct tax amount for each product
In xP&A, you can simply apply the **Product Group** breakdown to your **Tax** variable, and xP&A will automatically use the correct tax amount for each product in your downstream calculations.
Applying the 'Product Group' breakdown to the tax variable
**Price** is broken down by **Product** while **Tax percentage** is broken down by **Product Group**, but xP&A lets you multiply them directly without any manual lookups.
## Dimensions Let You Slice and Dice Easily in Charts and Tables in xP&A
Suppose that you have your monthly revenue broken down by **SKU** and want to create a stacked bar chart showing your monthly revenue broken down by **Product Group**.
In a spreadsheet, you would have to first “pivot” your data (using formulas and copy&pasting) and then chart the pivoted version of the data.
In xP&A, you can simply create a chart of your **Revenue** variable, and then pivot the data directly on the chart without any setup.
Chart to the variable 'Revenue'
## Dimension Values Can be Overridden in xP&A
Every business is messy, and sometimes you will need to hardcode certain values or set different formulas for different periods.
You can override any dimension value in xP&A by simply clicking and typing into the relevant cell. This is a useful 'escape hatch', but should be used sparingly!
---
---
title: "Using Groups"
description: "Groups are sets of variables within sections. You can also create nested groups simply by creating a group under an existing group."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-groups
language: en
last_updated: 2026-05-01
---
# Using Groups in Lucanet xP&A
## Overview
Groups are sets of variables within sections in Lucanet xP&A (Extended Planning & Analysis). You can also create nested groups simply by creating a group under an existing group.
## Creating a Group in xP&A
Groups can be created in xP&A as follows:
1. Hold down the **CTRL** key and select the elements to be included in the new group.
2. Press **CTRL+G** or choose **Group Variables** in the context menu.
Grouping variables
3. Enter a name for the new group.
Aside from visual organisation in the spreadsheet, groups in xP&A can also be used for:
## Easily Adding Totals in the Spreadsheet and on Tables in xP&A
You can easily add totals for a group in xP&A's spreadsheet and tables:
- These totals will automatically stay up to date as new variables are added, or existing variables are removed, from the group/section.
- **In the spreadsheet**: hit the sum icon at the top of the group/section row (see [Using Sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md)).
- **On tables**: add a group/section as a series to add its variables as well as a total row (see [Using Sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md)).
## Using Groups in Functions (Within Formulas) in xP&A
Easily sum (or avg/min/max...) the variables within the group. Just type `sum(Group Name)` and xP&A will sum all the variables within that group. When variables are added to (or removed from) the group, the function (e.g. sum) will auto-update.
## Keeping Variables on Tables in Sync With the Spreadsheet in xP&A
If you add a Group to a table (as opposed to the individual variables), then the table in xP&A will automatically stay up to date as variables are added/removed from the group in the spreadsheet (see [Using Sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md)).
## Table Headers in xP&A
Organise variables under Group name headers on tables in xP&A. You can toggle this setting off under **Display | Show group headers**.
Display settings for table headers
---
---
title: "Using Keyboard Shortcuts"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/user-interface-xPA/keyboard-shortcuts
language: en
last_updated: 2026-05-01
---
# Using Keyboard Shortcuts in Lucanet xP&A
## Overview
Keyboard shortcuts are crucial to your efficiency when building or navigating models in Lucanet xP&A (Extended Planning & Analysis).
Below is a list of the shortcuts currently available in xP&A, split by Windows and Mac.
> **Tip:** The **Command bar** is the biggest shortcut of them all. It allows you to perform a variety of actions at your fingertips with only one shortcut: **Ctrl+K (⌘K on Mac)**
>
> In the command bar you can do things like:
>
> - Change variable(s) unit and formatting (precision, magnitude)
> - Switch between models, views, workspaces, dashboard, or scenarios
> - Add variables to views, add scenarios, dimensions, or visuals
## Keyboard Shortcuts for Windows in xP&A
The following shortcuts are available for Windows:
List of shortcuts for Windows
## Keyboard Shortcuts for Mac in xP&A
The following shortcuts are available for Mac:
List of shortcuts for Mac
---
---
title: "Using Scenarios"
description: "A scenario is a live variant of your model in which some variables (or cells of a variable) have different values or formulas. The structure of the model — the variables, groups, and sections — doesn't change across scenarios."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-scenarios
language: en
last_updated: 2026-05-01
---
# Using Scenarios in Lucanet xP&A
## Overview
A scenario in Lucanet xP&A (Extended Planning & Analysis) is a live variant of your model in which some variables (or cells of a variable) have different values or formulas. The structure of the model — the variables, groups, and sections — does not change across scenarios.
This is useful when comparing different discrete options. For example, you might be trying to decide whether to hire 5 people or 10 people this year.
## Creating a Scenario in xP&A
Do one of the following to create a new scenario in xP&A:
- Right-click on a variable and click **New Scenario**.
- Click **Scenarios** in the toolbar, and then click **+**.
Creating a new scenario
> **Note:** **Rules when changing formulas and/or values in scenarios**
>
> - If you change (override) the formula and/or value of a cell, that cell will no longer be linked to the default scenario (but the rest of the variable will).
> - If you change (override) the entire variable's formula, then the entire variable will no longer be linked to the default scenario.
> - Any variables and cells you do not change or override, will still be linked to the default scenario (so any formula and/or value updates in the base model will flow through).
> - If you want to remove the override in the scenario, hit **Reset row** or **Reset override**. This will revert the formula to match the default scenario, and reinstate the link (so that any future updates to the base model will flow through).
> - Variables and/or cells that have been changed in a scenario will have a **pink** background.
> **Note:** If you have a set of [linked models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md) \- the scenario will automatically apply across all models. If you subsequently create a new linked model they will be automatically pulled across.
## Editing a Scenario in xP&A
Selecting a scenario under **Scenarios** in the toolbar, will take you into **Scenario** mode. In this mode, you will be able to change the value of any variable and/or cell, and this change will only be applied in the **active** scenario.
## Additional Functions for Scenarios in xP&A
You also have the following functions available via the three-dots menu the three dot menu icon of a scenario:
Additional functions for scenarios
> **Note:** **Overriding the default scenario**
>
> If other scenarios exist after overriding the default model with another, all unchanged values for variables in the other scenarios will all revert to the values of the new, default model.
>
> In other words, if you have a base model and two additional scenarios: **Scenario A** and **Scenario B**, and the base model is overridden by **Scenario A** to be the default model, then all of the variables in **Scenario B** that were unchanged from the original, default scenario, those variables will now take on the values of the new, default scenario.
## Comparing Scenarios in Charts and Tables in xP&A
You can visualize multiple scenarios together in charts and tables, to easily compare them. For a comprehensive overview of this functionality, see [Comparing Versions or Scenarios in Charts and Tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/comparing-versions-or-scenarios-in-charts-and-tables.md).
---
---
title: "Using Sections"
description: "Variables can be organized into several Sections in the spreadsheet view."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections
language: en
last_updated: 2026-05-01
---
# Using Sections in Lucanet xP&A
## Overview
Variables can be organized into several **Sections** in the spreadsheet view in Lucanet xP&A (Extended Planning & Analysis).
## Input Section in xP&A
The first section in xP&A is always the **Inputs** section, this is not able to be renamed or deleted. Any variables that are in this section will show up in the [Dashboard](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md), and are able to be played with (i.e. adjusted) by viewers. If you do not want a variable to appear as an adjustable input, move it out of your model's **Inputs** section.
> **Note:** Model inputs can be in any section of a model!
Input section in the spreadsheet view
## Other Sections in xP&A
By default, there is one more section auto-created when you start a new model in xP&A, named **Calculations**. However, you can delete or rename that section, add more sections, colour your sections, and reorder sections as you wish.
Add a new section
## Automatic Totals in Spreadsheet and Tables in xP&A
Easily add totals for a section in xP&A, which will automatically stay up to date as new variables are added, or existing variables are removed, from the section.
- **In the spreadsheet**: hit the sum icon at the top of the group/section row.
- **On tables**: add a group/section as a series to add its variables as well as a total row. (Hit the sum icon once added to see the total only, or variables only).
Automatic totals
## Sections in Functions in xP&A
Easily sum (or avg/min/max...) the variables within a section. Just type `sum(Section Name)` and xP&A will sum all the variables within that section. When variables are added to (or removed from) the section, the function (e.g. sum) will auto-update.
## Keeping Variables on Tables in Sync With Spreadsheet in xP&A
If you add a section to a table (as opposed to the individual variables), then the table in xP&A will automatically stay up to date as variables are added/removed from the section in the spreadsheet.
Sync Table with spreadsheet
## Table Headers in xP&A
Organise variables under their Section Name headers on tables in xP&A (within the **Display** settings).
Display settings for table headers
---
---
title: "Using Tables"
description: "Tables can be used to visualize your data, either within the Spreadsheet workspace or the Dashboard workspace."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables
language: en
last_updated: 2026-05-01
---
# Using Tables in Lucanet xP&A
## Overview
**Tables** can be used in Lucanet xP&A (Extended Planning & Analysis) to visualize your data in a pivot table, either within the **Spreadsheet** workspace or the **Dashboard** workspace.
Tables are helpful if, for example, you want to drill down and see the details on one variable.
## Creating a Table in xP&A
To create a **table** in xP&A, choose one of the following options:
- In the **spreadsheet** workspace, right-click a variable and choose **Create chart | Table:**
Creating a table from a variable
- In the **spreadsheet** workspace, click the **Charts** icon in the top-right corner the charts icon to open the **Charts** side panel and choose **New chart | Table.**
- In the **Dashboard** workspace, click the **+** icon at the bottom left and select **Table** from the displayed list:
Creating a table from the side panel or using the + icon
> **Note:** - To add the variables you want to visualize, drag & drop them onto an existing table from the spreadsheet workspace (when you have the charts side panel open).
> - By right-clicking on a table, you can duplicate it (or delete it).
## Editing a Table in xP&A
You can edit a table
- In the toolbar of the **Spreadsheet** workspace, by clicking the **Charts** icon
- In the **Dashboard** workspace
The options to edit a table can be found in the toolbar on the top right of the table visual:
Table settings toolbar
## Options for Tables in xP&A
The following options are available for a table:
### General Options
The following general options are available for tables in xP&A:
| Option | Description |
|---|---|
| **Commenting a cell** | You can add a comment to each cell of a table. Simply hover over the cell you want to comment on and click the yellow comment icon that appears. You can enter your comment in the comment field and save it using **Enter** or the purple arrow icon.
Comments on a cell are highlighted with a yellow triangle at the top left of the cell. Hover over the yellow triangle to show the comment, all the replies and their authors. |
| **Three-dot menu** | You can use the three-dot menu to: • **Copy** the table as an image • **Download** the table as an image • **Clear annotations and highlights** from the table • Add a **description** • **Delete** the table |
| **Time aggregation** | You can use the roll-up/drill-down column drop-down list to determine how variables are displayed and summed across time (e.g. quarterly, yearly), and toggle between them easily.
**Tip:** See section _Time Aggregation_ in [Aggregation Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md) if you want to change how a variable aggregates into quarters or years (the default setting is **sum**). |
| **Year-to-date roll-up** | The **Year-to-date** roll-up option allows you to see how you are tracking in the year to date.
• The **Year** can either track the calendar year (i.e. starting in January), or the fiscal year (starting with your [fiscal start month](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md), if set). • The **to Date** can either be to your [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), or to **today**'s date. If you use **Last actual date**, this means that your table will auto-update when you update your **Last actual date** after a [data refresh](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md).
**Note:** **Year-to-date** also works across versions and scenarios, for example, you can compare your actual YTD performance with how you thought you would be doing so far from your Budget version. |
| **Relative comparison** | You can use this option to compare the value of a variable across relative time periods (e.g. the prior month, the prior year).
In addition, you can choose if you want to show the **variance** as **percentage**, **value**, or **both**. |
| **Adjust column widths** | xP&A has a default column width, but if you have a longer column name (and don't want to hover to see it), you can adjust column widths by dragging the header. Useful shortcuts: • **Hold Shift** to adjust multiple similar columns at once • **Double-click** to reset to default width • **Hold shift while double-clicking** to reset multiple similar columns at once |
### Setup Options
To open the setup options, click the edit icon in the top-right corner of a table visual and go to the **Setup** tab:
Table setup options
The following setup options are available:
| Option | Description |
|---|---|
| **Series** | You can easily add, rename, reorder (by drag&drop), and delete variables in the **Series** section. You can also choose, instead of adding variables one-by-one to a table, to add the entire **group** or **section** to the table. The table always stays in sync with the spreadsheet when variables get added or removed from a group or section.
By clicking on a variable in this section, you can: • Change the **font style** • Define if the **values** of this variable are **editable** • Open the **advanced** setting options |
| **Series axis** | Use this section to set whether your variables are displayed as **rows** or as **columns**. |
| **Date range** | By default, the table will display the entire model date range. If you would like to shorten the date range, you can select a custom start and/or end date for the table here. |
| **Columns/Rows** | In this section, you can define which dimensions (e.g. dimensions, scenarios, versions) to include as the rows and columns of the table. By default, **Time** is included as a column dimension. If your model has its own **custom dimensions**, you can choose to include those. When including a custom dimension, you can automatically include **dimension totals** by hovering over the dimension and clicking the **Total** button. |
| **Notes column** | If you click on the **+** button in the **Columns** section, you can add a **Notes** column to your table. The **Notes** column can be used to add in-line context to your tables, e.g. providing variance analysis for Budget vs. Actuals, or explaining key differences between scenarios. |
| **Filters and controls** | In this section you can add filters to the table, e.g. a **time** filter or a filter to arrange different versions and/or scenarios next to each other. |
### Display Options
To open the display options, click the edit icon in the top-right corner of a table visual and go to the **Display** tab:
Table display options
The following display options are available:
| Option | Description |
|---|---|
| **Enable drill-down** | You can use this option to enable a [drill down on underlying integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data.md) (transactions).
Anyone viewing the dashboard will be able to view these underlying details. Note that this information may be sensitive. |
| **Show group headers** | If [variables are grouped](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-groups.md) in the **Spreadsheet** workspace, then the table will automatically display these variables under a group heading.
You can use this option to toggle the group headers on or off. |
| **Show section headers** | You can also show [sections](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/using-sections.md) as table headers. This is useful if you have a structured table you need to organize. |
| **Hide empty rows** | You can use this option to hide rows where the value is 0 or empty. |
### Advanced Options
To open the advanced setting options, click the edit icon in the top-right corner of a table visual and go to the **Advanced** tab. The following advanced options are available:
Advanced table options
For a detailed description of the advanced option **Editable values** see the following chapter _Editable Tables_.
## Editable Tables in xP&A
**Editable tables** are a special type of table that users can add to their dashboards to:
- Make edits without the need of editing info in a spreadsheet.
- Allow other users to make edits to dimension items and their [associated links and variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md).
They are especially useful when you need end-users, often unfamiliar with spreadsheets, to easily provide their inputs towards a budget (e.g. a department head adding their projected new hires for the upcoming year).
To create an editable table, click the edit icon in the top-right corner of a table visual, go to the **Advanced** tab and activate the option **Editable values**.
---
---
title: "Using the 'Import Data Until' Function"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/import-data-until-function
language: en
last_updated: 2026-05-01
---
# Using the 'Import Data Until' Function in Lucanet xP&A
## Overview
By default, Lucanet xP&A (Extended Planning & Analysis) imports data from data sources for all periods (e.g. months) where data is available, up until the [Last actual date.](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md)
The **Import data until** setting lets you control how far back or forward data is imported for specific data sources in a model.
Normally, xP&A pulls all available data up to the [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) for every data source. However, sometimes you might want to override this for specific data sources. That’s where **Import data until** comes in.
**Why would you use it?**
- To exclude certain months from a specific data source:
Suppose most of your data sources are reliable up to the [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), but one data source contains incorrect or incomplete recent data.
You can use **Import data until** to stop pulling data from that source earlier (e.g., one month before the [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md)) while still importing full data for the others.
- To include forecast data for a specific data source:
If a data source contains forecasted values beyond the Last actual date (e.g., if you're forecasting revenue in an external tool), you can extend "Import data until" for that source only.
This allows you to combine real historical data with external forecasted data in the same model.
Instead of applying the Last actual date to every data source equally, the **Import data until** function gives you flexibility, allowing certain data sources to stop earlier or continue further than the default Last actual date.
> **Note:** If you have turned **Import data until** on for a data source, that will take **precedence over the Last actual date** in that model, for that data source only.
>
> If you want to import **new data** for that data source (or cut off data earlier for that data source), you need to do so **manually** (via [refreshing the data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md), and/or **updating** the **Import data until** date as described below).
## Example
The following examples shows how the settings of the **Last actual date** and **Import data until** affect the data imported from a data source:
If:
- Your **Snowflake user data** in your **Revenue** model has an **Import data until** of **December 2024**.
- Your **QBO P&L data** also used in your **Revenue** model has **no Import data until** set.
- Your **Last actual date** is **December 2024**, but you drag it forward to **January 2025**.
Then:
- **Snowflake user data** will stay cut off at **December 2024**.
- **QBO P&L data** will be pulled into the model up until **January 2025** (if present).
## Configuring the 'Import Data Until' Function in xP&A
To configure the 'Import Data Until' function:
1. Open the model for which you like to configure the **Import data until** function.
2. Open the **data preview** of a data source by clicking on the data source in the overview.
3. Open the **three-dot menu** on the top right of the data preview.
4. Activate the option **Import data until**.
5. Set the **date** up until which you want to import data from this data source into the selected model.
Configuring the 'Import data until' function
## FAQs
| Question | Answer |
|---|---|
| **What if my 'forecast' data is used in a model that has no other data sources? Do I still need to use the 'Import data until' function?** | No. In this case, you can just turn the [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) setting off in that model. Data will flow in as and when it is [refreshed](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md), up to whatever months the data source has data for.
If the model is [linked to other models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md), and you update the **Last actual date** in those other models, the forecast model/data source will not be affected. |
| **What if my historic data source that has less months of useable data than my other historic data sources is used in a model with no other data sources? Do I still need to use the 'Import data until' function?** | No. In this case, you can just set an earlier [Last actual date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md) in this model (and have the other models use the latest **Last actual date**). |
| **Can I set different 'Import data until' dates for the same data source in different models?** | Yes. The setting is unique to each data source, with each model that it is used in. |
---
---
title: "Using Time Aggregation and Relative Comparisons"
description: "xP&A offers different functionalities to compare or aggregate your data in order to gain deeper insights, identify trends, and support strategic decision-making across planning and analysis workflows."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/time-aggregation-and-relative-comparisons
language: en
last_updated: 2026-05-01
---
# Using Time Aggregation and Relative Comparisons in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) offers different functionalities to compare or aggregate your data in order to gain deeper insights, identify trends, and support strategic decision-making across planning and analysis workflows.
## Time Aggregation in xP&A
In [charts](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md) and [tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables.md), and in the roll-up columns in a spreadsheet, xP&A can automatically aggregate a variable's values across time.
**Example**: If your model is monthly and you have a **Revenue** variable, then xP&A can automatically summarize the total revenue in each year.
The **time aggregation** function lets you choose how this summary is calculated. The following options are available:
- **Sum**
Sums up the individual values, e.g. anything that represents a discrete quantity which can accumulate, e.g. "Revenue"
- **Average**
Calculates the mean of the individual values, e.g. generally anything that's a percentage, like "Growth rate"
- **Final**
Takes the final value in the set of individual values, e.g. anything representing an accumulation, like "Total users" or "Cash in bank", or a percentage that you expect to move roughly monotonically
- **Initial**
Takes the first value in the set of individual values
- **Formula**
Uses the variable's formula to calculate an aggregation value, e.g. if you have a variable for the _margin_ with the formula _profit / revenue_, the formula aggregation will take the total profit and divide it by the total revenue of the aggregated period.
You can set up the time aggregation as follows:
**In charts and tables**
Right-click a variable and choose **Aggregation | Time Aggregation** and then the desired aggregation methods from the context menu:
Time aggregation menu on a variable
**In roll-up columns**
If you have roll-up columns toggled on, you can click a rollup cell to easily edit the **Time aggregation** setting for each variable:
Time aggregation menu on a roll-up column
> **Tip:** - Note that the time aggregation setting of a variable also determines [how a variable is 'rolled up' to a model with a higher-level granularity](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/time-granularities.md).
>
> For example, when a model with lower granularity (such as Monthly) pulls data from a model with higher granularity (such as Weekly), the time aggregation setting determines if it should pull the sum, the average, the final etc.
> - For more information on aggregation functions for data and dimensions, see [Aggregation Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/aggregation-functions.md).
## Relative Comparisons in xP&A
You can easily compare the value of a variable across relative time periods (e.g. the prior month, the prior year). The comparison is shown on a time aggregated basis too, if relevant.
For example, if your model is **monthly** and you have set your table to **yearly** time aggregation with the showing the variance as a relative comparison, a Year-over-Year Comparison (YoY) will show for 2025 vs. 2026, as well as each month (e.g. Jan 2025 vs. Jan 2026).
Comparisons in charts
---
---
title: "Using Views"
description: "Views let you create saved filters on your model, to show only specific variables, category items, scenarios, time periods, and charts. This can be useful if you as the model builder want to filter the model for a specific subset of things, or if you want to share only a View of your model with your collaborators, as opposed to the whole thing."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views
language: en
last_updated: 2026-05-01
---
# Using Views in Lucanet xP&A
## Overview
In Lucanet xP&A (Extended Planning & Analysis), views let you create saved filters on your model, to show only specific variables, dimension items, scenarios, time periods, and charts.
This can be useful if you as the model builder want to filter the model for a specific subset of data, or if you want to [share only a view](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views/sharing-views.md) of your model with your collaborators, instead of the whole model content.
## Creating and Configuring a View in xP&A
To create and configure a view in xP&A:
1. Click the **Views** button in the top left of the spreadsheet.
2. In the **Views** dialog, click **New** or **Create a view** and start adding filters (see subheading below).
## Filter Options in xP&A
The **Filters** section is displayed as follows:
Filter options to configure a view
The following filters are available:
### Variable filters
| Filter | Description |
|---------|---------|
| is none of | Filters out the specific variable(s) you select |
| is one of | Filters for only the specific variable(s) you select |
| contains | Filters for variable names that contain your searched term |
| has dimension | Filters for only the variables that have the selected dimension applied |
| does not have dimension | Filters out the variables that have the selected dimension applied |
### Chart filters
| Filter | Description |
|---------|---------|
| is one of | Filters out the selected visual(s) |
| is none of | Filters for only the selected visual(s) |
> **Note:** Note that if you share a view with a **chart filter**, the variables in the spreadsheet will still be visible, unless you explicitly filter them out. In this situation, a [dashboard](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md) may be more appropriate.
### Time filters
The time filter is simple - just enter the time range you would like to see. Note that this affects both the spreadsheet, as well as the time range shown in any visuals.
### Dimension filters
The dimension **is one of** filters by dimension item(s) within a **dimension**(on all the variables where that dimension exists), as well as any dimensions mapped to it.
**Example**:
If **Employee** is linked to **Title** which is linked to **Department**, and your view filters for the **Engineering Department**, xP&A will do the following across the spreadsheet and charts:
- Filter for **Engineering** on the variables that have the **Department** dimension
- Filter for the **Titles** that sit within **Engineering** on any variables that have the **Title** dimension
- Filter for **Employees** within **Engineering**(linked via their **Title**), on any variables that have the **Employees** dimension
- Filter the [aggregates](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md) of the above relevant variables for only the **Engineering Department**
- If you want to show others the unfiltered aggregates within a view, you can do this by creating another variable that [aggregates the dimension away](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) (e.g. create a **Monthly Payroll** with the **Department** dimension aggregated away).
> **Warning:** Please note:
>
> - Dimensions that are not effectively linked to the filter dimension will not be filtered.
> - Consider the modified version of the example above: If in your data it is possible to have the same **Title** belonging to different departments, you cannot establish **Title**-\> **Department** mappings; you could only have **Employee**-\> **Title** and **Employee**-\> **Department**. If you then create a view that filters by department, the **Employee** items will be filtered, but your users still could access all the items of the **Title** dimension, e.g. via [Editable Tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables.md#editable-tables). This might not be desirable if the names of **Title** items are sensitive.
> - As a workaround, for some data sources it is possible to replace **Title** with synthetic column like **Title & Department**, which can directly be mapped to **Department**, thus allowing the filter rules to work.
> - This **will not** filter out variables that **do not have the dimension on them**. If you wish to do that, you could combine the filters **Variable has dimension** and **Dimension is one of.**
### Scenario filters
| Filter | Description |
|---------|---------|
| is one of | Filters for only the specific scenario(s) you select |
> **Note:** When a view with a **scenario** filter is active, you will only be able to see the **selected** scenarios.
## Examples for Views in xP&A
### Model Navigation
Models can get large and complex. Views let you easily slice and dice your model for just the portion you are wanting to see at a point in time. For example, if I just want to dig into the inputs for **Model 3** for **2025**, I could set up the view below to easily select.
Example for model view
### Budgeting Processes
For example - if your **Expenses model** is broken down by **Department**, you can create separate views to share with each department head, where they will only be shown the parts of the model that are relevant to them.
### Tailored Dashboards
You might need to share your model with different groups of stakeholders — the management team, the rest of the company, investors, board, etc.
Instead of creating separate models to slice the same information in different ways, you can create multiple views on the same model. Each view will limit which charts, tables, and variables are shown, so that each group of stakeholders can see a dashboard that is tailored to them.
---
---
title: "Values with Uncertainty"
description: "This article explains how ranges and Monte Carlo simulations as well as different distribution shapes are used in xP&A to model uncertainty in formulas, enabling more realistic and probabilistic forecasting."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/values-with-uncertainty
language: en
last_updated: 2026-05-01
---
# Values With Uncertainty in Lucanet xP&A
## Overview
This article explains how **ranges** and **Monte Carlo simulations** as well as **different distribution shapes** are used in Lucanet xP&A (Extended Planning & Analysis) to model uncertainty in formulas, enabling more realistic and probabilistic forecasting.
## Ranges and the Monte Carlo Method in Lucanet xP&A
When variables in Lucanet xP&A are in the format of a range (e.g. 0 to 100, uniform(0,100), a **Monte Carlo simulation** is run to estimate the possible outcomes of an uncertain event. Monte Carlo will randomly pick a value from the distribution and compute the whole model as if it were that random constant value. This process is repeated multiple times to generate distributions for the output variables.
The use of the simulation allows xP&A to perform computations using values with uncertainty that are not possible without it. Due to this method of handling uncertainty, you may notice that the range of the cell and the value are not the numbers you input or would expect, but only by a trivial amount.
Range with Monte Carlo method
## Distribution Shapes in Lucanet xP&A
There are many different types of distribution shapes for values with uncertainty. Here are three examples of distributions that xP&A supports:
## Triangular Distribution in Lucanet xP&A
In Lucanet xP&A, values in the format of '# to #' produce a triangle distribution where the center value is the most likely value, while the edges of the range are the least likely:
Chart with a Triangular Distribution
## Uniform Distribution in Lucanet xP&A
In Lucanet xP&A, using the function **uniform(from, to)**, a uniform distribution can be produced:
Chart with a Uniform Distribution
## Poisson Distribution in Lucanet xP&A
In Lucanet xP&A, using the function **poisson(lambda)**, a poisson distribution will be produced:
Chart with a Poisson Distribution
## Sample in Lucanet xP&A
The **sample** function in Lucanet xP&A takes a random sample from the provided numbers. For example, **sample(1,2,3)** may return 1, 2 or 3 with equal probability.
Chart with Sample function
---
---
title: "Variable Modifiers"
description: "When you reference a variable in a formula, there are two key ways to modify it - using Categories (if applicable), and Time."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers
language: en
last_updated: 2026-05-01
---
# Variable Modifiers in Formulas in Lucanet xP&A
## Overview
When you reference a variable in a formula in Lucanet xP&A (Extended Planning & Analysis), there are two key ways to modify it - using **Dimensions**(if applicable), and **Time**.
## Time Modifiers in Lucanet xP&A
Time modifiers in Lucanet xP&A allow you to reference various different time instances of a variable.
Time Modifier
## Types of Time Modifiers in Lucanet xP&A
The following types of time modifiers are available in Lucanet xP&A:
### Relative
**This 'month'**: returns the current value of that variable
**Previous 'month'**: returns the previous value of that variable, relative to the time step in which the formula is being applied.
**Example**: In June, **Customers\[previous\]** corresponds to the value of **Customers** in May.
> **Note:** By default, when you reference another variable, xP&A will return the current value of that variable. When you reference the variable itself, xP&A will return the previous value of that variable.
**Look-back** and **look-forward**: returns the value of that variable x days/weeks/months/years in the past or future, from "t" (the current time step).
**Example**: if you want xP&A to return the value 12 months ago, your time modifier would be **t-12**. Conversely, if you wanted to return the value three months in the future, your time modifier would be **t+3**.
Looking back 6 month ago
> **Note:** In a look-back or look-forward, you may reference dates that are _before_ the start, or _after_ the end of a model's date range. These cells will evaluate to the empty value of the variable (ie., either 0, or the **none** value).
### Fixed
**Final**: returns the value of the final timestep of the model for that variable. Note that if you extend your [model time settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md), any variables referencing the final time step will auto-update.
**Absolute**: returns the value of a single, particular timestep for that variable. e.g. 1 refers to the 2nd timestep of the model, 0 refers to the 1st timestep of the model etc. You can also just type in **date(YYYY,MM)** instead of the timestep index number.
### Spans
Spans are a sequence of time steps, e.g. past six months in a monthly model would be **t-6:t-1**.
> **Note:** Spans always need to be aggregated, e.g. wrapped in a **sum** or **avg** function.
**All**: returns the sum of all time steps for a variable.
Using 'All' in a formula
**Span with a custom start/end-point**
- E.g. first 6 days/weeks/months/years of your model: 0:5 (absolute)
Using a span ('first 6 months') in a formula
- Past three days/weeks/months/years (relative, useful for rolling averages)
Using 'last 3 months' in a formula
## Dimension Modifiers in Lucanet xP&A
Dimension modifiers in Lucanet xP&A allow you to slice and dice referenced variables within formulas, using the related dimensions and dimension items.
You can use the following dimension modifiers in Lucanet xP&A to modify referenced variables within formulas:
### Grouping by Linked Dimensions in Lucanet xP&A
Once you have [linked dimensions together](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/create-edit-dimensions.md) in Lucanet xP&A, you can then easily slice variables along different dimensions.
**Example**: We have an **Employee** dimension, which is linked to a **Team** dimension. By default, we've worked out **Salaries** by **Employee**, and now we're interested in seeing **Salaries** by **Team**.
Click on the **Dimension** icon in the referenced variable in the formula, and then select the desired dimension and click **Group by**.
Using 'Group by'
> **Note:** If you want to "Group by" **multiple dimensions** at one time just hold down **Shift** and click each of the dimensions you want to select. e.g. if you want to group by **Team** and then **Role**. This displays as multiple layers of nesting.
### Filtering by Dimension Items in Lucanet xP&A
Sometimes you'll want to select a single item from a dimension and use it in a formula in Lucanet xP&A.
Click the **Dimension** icon in the referenced variable in the formula, select the desired dimension, and then click the individual item you want to filter by.
**Example**: If you want to do a calculation only based on the **Engineering** Team's salaries, you would select **Engineering** under **Department**.
Filtering by category item
> **Note:** If you want to filter for multiple dimension items, just hold down **Shift** and click each of the dimension items you want to select.
### Aggregating Away a Dimension in Lucanet xP&A
Sometimes you might want to aggregate away a dimension in Lucanet xP&A, if you no longer care to see that level of granularity.
**Example**: If you have filtered **Salary** by **Employee** for just the **Engineering** team, but no longer care to see the **Employee** breakdown, you can aggregate the **Employee** dimension.
Use the two commands **Aggregate** **(Sums across dimension)** and **All (Keep dimension intact)** to remove or re-add the breakdown of a dimension. To do this, click on the variable in the top bar:
Aggregating away a category
### Other Ways of Using Dimensions in Lucanet xP&A
There are a few other ways that you can use or manipulate dimensions and dimension items within variables and formulas in Lucanet xP&A, that are not variable modifiers in formulas.
### Aggregating at the Variable Level in Lucanet xP&A
Sometimes you might want to change how a variable aggregates its dimension items. xP&A's default is to sum the dimension items, but see [Dimension aggregation](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/aggregating-dimensions.md) for more options.
### Dimension Items in Formulas in Lucanet xP&A
[You can also reference dimension items within formulas](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/using-dimensions/dimensions-variables-and-formulas.md).
---
---
title: "Versioning a Model"
description: "Lucanet xP&A automatically takes snapshots of your model (or set of linked models) at regular intervals, and you can also manually save a named version of a model."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model
language: en
last_updated: 2026-05-01
---
# Versioning a Model in Lucanet xP&A
## Overview
Lucanet xP&A (Extended Planning & Analysis) automatically takes snapshots of your model (or set of linked models) at regular intervals, and you can also manually save a named version of a model.
Versions and snapshots are useful for:
- Comparing different versions of the model(s) against one another
- Rolling back to older versions if you want to revert a set of changes
## Opening the Version History in xP&A
To navigate to the version history of a model, click the **Versions** button in the top right corner in the **Spreadsheet** view:
Opening the version history of a model
The version history is displayed as follows, for example:
Version history of a model
On the right side of the table header, you can choose to **Show named versions only** or to **Show all versions**, i.e. also those automatically created by the system.
## Manually Adding a Named Version in xP&A
In addition to the snapshots that are automatically created by the system, you can manually save **named versions** of your model (or set of [linked models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md)).
For example, if you finalize a budget, you can save a version called "Budget 2025" and refer back to it later or use it in charts and tables as a comparison against actuals.
You can also view named versions but will not be able to edit anything in it, unless you roll-back.
To save a named version:
1. Open the **version history** of the model.
2. Enter a **name** for the **New version**.
3. Click **Create**.
Creating a named version
> **Warning:** - All linked models must have the same [fiscal year settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time.md) in order to save a version.
> - If you change the [granularity of a model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/time-granularities.md), you will no longer be able to compare with prior versions.
> - If you have a model that is [linked to a data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md), each version will use the values from the data source that existed when the version was saved. Versions will not be re-evaluated, e.g. if values in the data source change.
>
> However if **you roll the model back** to that version, it will be **re-evaluated with updated values** from the data source.
## Options for a Named Version in xP&A
If you hover over the row of an existing named version, you can:
- **Edit** the name
- **Delete** the version, using the trash bin icon
- **View** the version in read-only mode.
- **Roll-back** to the version to be able to edit it
Options for a named version
> **Warning:** If you have a model that is [linked to a data source](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data.md), each version will use the values from the data source that existed when the version was saved. Versions will not be re-evaluated, e.g. if values in the data source change.
>
> However, if you **roll the model back** to that version, it will be **re-evaluated with updated values** from the data source.
---
---
title: "Viewing and Visualizing Data"
description: "Once you have set up your spreadsheets, you have multiple options to create certain views of your data or visualize your data, e.g. for presentation purposes or if you want to share your data with other users."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data
language: en
last_updated: 2026-05-01
---
# Viewing and Visualizing Data in Lucanet xP&A
## Overview
Once you have set up your spreadsheets in Lucanet xP&A (Extended Planning & Analysis), you have multiple options to create certain **views** of your data or **visualize** your data, e.g. for presentation purposes or if you want to share your data with other users.
This article contains the following chapters on viewing and visualizing data in xP&A:
- [Using Dashboards](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-dashboards.md): Dashboards are a nice way for others to view and interact with your model. It shows your model's input variables at the top, with its charts underneath. You also have the option to show them a read-only spreadsheet view, too.
- [Using Charts](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables-charts.md): Charts can be used to visualize your data, either within the Spreadsheet workspace or the Dashboard workspace. Charts are useful if you want to visualize several variables.
- [Using Tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-tables.md): Tables can be used in xP&A to visualize your data in a pivot table, either within the Spreadsheet workspace or the Dashboard workspace.
- [Using Scenarios](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-scenarios.md): A scenario is a live variant of your model in which some variables (or cells of a variable) have different values or formulas. The structure of the model — the variables, groups, and sections — does not change across scenarios.
- [Using Views](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/using-views.md): Views let you create saved filters on your model, to show only specific variables, dimension items, scenarios, time periods, and charts.
Furthermore, xP&A allows you to compare or aggregate your data using the following functionalities:
- [Comparing Versions or Scenarios in Charts and Tables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/comparing-versions-or-scenarios-in-charts-and-tables.md): You often might want to compare different versions and/or scenarios of your model, for example to learn how your actual performance compares to your budget or forecast, see how different scenarios affect your numbers, or compare how a new scenario stacks up against your original forecast.
- [Using Time Aggregation and Relative Comparisons](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/viewing-and-visualizing-data/time-aggregation-and-relative-comparisons.md): xP&A offers different functionalities to compare or aggregate your data in order to gain deeper insights, identify trends, and support strategic decision-making across planning and analysis workflows.
---
---
title: "Viewing the Audit Logs of a Model"
description: "Audit logs are a model-by-model running history of who has made what edits (and when) to a model's variables, categories, visuals, or data."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/viewing-the-audit-logs
language: en
last_updated: 2026-05-01
---
# Viewing the Audit Logs of a Model in Lucanet xP&A
## Overview
In Lucanet xP&A (Extended Planning & Analysis), audit logs are a model-by-model running **history of who has made what edits (and when)** to a model's variables, dimensions, visuals, or data.
They give **model admins** oversight when sharing edit access to the model with other team members, and comfort in knowing they are always in the loop with recent changes that have been made by others.
> **Warning:** To view the audit logs of a model, a user needs to have [edit or full access](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder.md) to the model.
## Opening the Audit Logs of a Model in xP&A
To open the audit log of a model, click the gear icon in the top right corner of a spreadsheet to open the [Model settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md) and click **Audit logs** at the bottom. The audit log is displayed as follows, for example:
Audit logs
> **Warning:** Audit Logs **do not include** any actions related to:
>
> - Data item transformation on a variable
>
> - Formatting of variables
>
> - [Sharing or permissions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder.md)
>
> - Viewing models or dashboards
>
> - Commenting (these are covered in the comment history)
>
> - Versions (these can be seen in the [version history](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model.md))
>
> - Undoing actions
---
---
title: "Working With Integrated Data"
description: "Once a connection to a source system is established and data is integrated from a data source, you can start working with the data in Lucanet xP&A.\n\nIn this section, you will find out how you can:\n\nUse integrated data in variables\nLink dimensions from the data source to dimensions in xP&A\nRefresh data sources\nUse the function 'Import data until'\nManage your data sources"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data
language: en
last_updated: 2026-05-01
---
# Working With Integrated Data in Lucanet xP&A
## Overview
Once a connection to a source system is established and data is integrated from a data source, you can start working with the data in Lucanet xP&A (Extended Planning & Analysis).
In this section, you will find out how you can:
- [Use integrated data in variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-variables-to-integrated-data.md): To use the data you integrated via a connection to a source system in your variables, you can link the variables to the integrated data.
- [Link dimensions from the data source to dimensions in xP&A](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/linking-dimensions-to-data-source.md): Often, you will import data broken down into dimensions — for example, employee data from your Payroll/HRIS system, or department expenses in Accounting/ERP systems.
- [Refresh data sources](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/refreshing-a-data-source.md): To keep your data integrated and up to date, you need to refresh your data sources regularly.
- [Use the function 'Import data until'](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/import-data-until-function.md): By default, xP&A imports data from data sources for all periods (e.g. months) where data is available, up until the Last actual date.
- [Drill-down on integrated data](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/integrating-data/working-with-integrated-data/drill-down-on-integrated-data.md): If you have data sources that contain underlying data (e.g. transactions from a connected source system like Xero, QuickBooks Online, NetSuite, Google Sheets or a CSV import in transaction format), xP&A allows you to drill-down into the underlying detail, from any variables connected directly to that data.
---
---
title: "Working with Models"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models
language: en
last_updated: 2026-05-01
---
# Working with Models in Lucanet xP&A
## Overview
A model in Lucanet xP&A (Extended Planning & Analysis) refers to a structured representation of data and calculations, similar to a tab in a spreadsheet.
Models in xP&A can be:
- **Organized** into folders, **cloned**, and **linked** with other models
- **Shared** in parts through views or as a whole to collaborate with others within the xP&A solution
- **Exported** to be used and to collaborate with others outside the xP&A solution
This article contains the following chapters on working with models in xP&A:
- [Organizing Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/organizing-models.md): For a better overview, models can be organized in folders. You can also assign a specific icon to identify a model easier, and set up favorites for your models.
- [Linking Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/linking-models.md): Instead of a single model with all of your variables and formulas, you can structure your work into separate, smaller models, and import variables between them.
- [Cloning a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cloning-a-model.md): By cloning a model, you can create an identical copy of the model.
- [Exporting a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/exporting-a-model.md): You can export your model(s) out of xP&A into a variety of formats and file types.
- [Sharing a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/sharing-a-model-folder.md): After building a model, you have the option to share this model with other users. You can also organize your model into folders and share folders if you want to grant access to multiple models at once.
- [Versioning a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model.md): xP&A automatically takes snapshots of your model (or set of linked models) at regular intervals, and you can also manually save a named version of a model.
- [Viewing the Audit Log of a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/viewing-the-audit-logs.md): Audit logs are a model-by-model running history of who has made what edits (and when) to a model's variables, dimensions, visuals, or data.
- [Cells and Limits](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/cells-and-limits.md): A cell in xP&A represents a single number in the spreadsheet, and there are limits on the number of cells that can be used across your organization.
- [Editing the Model Settings](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/editing-model-settings.md): For every model, you can define certain time settings, which include the granularity, the date range, and the last actual date for your model.
- [Handling Errors in a Model Using AI](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/handling-errors-in-a-model.md): When a variable contains a calculation error, xP&A displays the error directly in the variable's warning panel and provides two AI-assisted features to help you understand and resolve it: Explain with AI and Fix with AI.
- [Multi-Player Modeling](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/multi-player-modeling.md): xP&A allows multiple users to work in the spreadsheet of a model at the same time.
- [Proposing and Approving Changes to a Model](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/propose-changes-to-model.md): The Propose changes feature enables collaborative model updates through a structured review workflow. Data Collectors can suggest changes without directly modifying live data, while Editors review, approve, or reject proposed updates before they are applied.
- [Troubleshooting for Slow or Large Models](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/troubleshooting-slow-large-models.md): The performance of a model in xP&A, i.e. the speed of loading or calculating it, depends on various factors such as model size, formula complexity, and visual complexity.
---
---
title: "Working with Time"
description: "The key concept to understand about working with time in Lucanet xP&A is the timestep index system that can be applied in variables in formulas."
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time
language: en
last_updated: 2026-05-01
---
# Working With Time in Lucanet xP&A
## Overview
There are two ways that time settings can be applied in Lucanet xP&A (Extended Planning & Analysis):
**At Formula Level**
The key concept to understand about working with time in xP&A is the **timestep index system** that can be applied in variables in **formulas**.
**At Model Level**
Besides this, you can define certain time settings for each model in xP&A, which include:
- **Granularity**
- **Date range**
- **Last actual date**
- **Relative dates**
- **Fiscal year settings**
> **Note:** In addition to the time settings affecting the calculations of your data in xP&A, you have the option to use a **time filter** in the **spreadsheet** or **dashboard** view to merely define the time period you want to look at.
## Time Settings at Formula Level in xP&A
### Timestep Index in Variable Modifiers in xP&A
The time step index in xP&A allows you to modify variables in formulas, e.g. refer to the value of a variable in three months. This is done using [Time modifiers](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/variable-modifiers.md) in formulas.
> **Note:** The time step index always starts at 0, not 1. So 0 corresponds to the first time step of the model (e.g. Jan'22), 3 corresponds to the fourth time step (Apr'22), and so on.
Timestep in a formula
### Date Function in xP&A
The **Date** function in xP&A converts an input in **Date** format to the appropriate **timestep** in a model to allow further calculations. For more information on the functions for **Time**, see [Functions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/functions.md).
Date function
### Time-Dependent Helper Variables in xP&A
In addition, xP&A also has various in-built [helper variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) (like **date**, **month**, **year**, or **lastActualDate**) that make it easy to work with time.
Helper variable for time
## Time Settings at Model Level in xP&A
You can also adjust your time settings at the level of each model in xP&A. Proceed as follows:
1. Click the gear icon to open the **Model settings**.
2. Adjust the options as necessary.
For a description of the options see the following sections.
3. Click **Apply changes**.
4. In the **Apply changes** dialog, choose if you want to apply the changes **to the current model only** or **to all linked models**.
### Options in xP&A
The following options are available for time settings in xP&A:
Time settings for a model
| Option | Description |
|---|---|
| **Granularity** | Granularity refers to the level of detail in which data of a model are organized. The following granularity levels exist:
For more information on this topic, see [Different Time Granularities](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/time-granularities.md).
**Warning:** If you change the granularity of a model, you will no longer be able to compare with prior [versions](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/working-with-models/versioning-a-model.md). |
| **Model date range** | The date range for which the model is calculated. |
| **Last actual date** | The **last actual date** is a model-level setting that represents your latest month (or week if in a weekly model) of "actual" historic data.
To determine your **Last actual date**, activate this option and select the desired month to be used as last actual date.
**Note:** • There is also a [Helper variable](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-andedit-formulas/helper-variables.md) available for the **last actual date**. • For more information on the last actual date in xP&A, see [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md).
**Warning:** • Use this option in a model's time settings only if you enter your actual "historic" data **manually**. • If you import your actual data using a data integration, this option described here is not used. In this case, the last actual date is set using the integration via a data source. |
| **Use relative dates** | Activate this option, if you want to use relative dates for your model.
Relative dates refer to time periods that are not tied to specific calendar dates but are instead defined in relation to a current or reference point. For example, **Year 1** instead of 2020.
Relative dates allow for comparisons across time periods, such as comparing data from the current month to the previous month or year.
**Examples**: • **Retention rate**: You probably will not use January, February and March for a retention rate, but rather use a customer's first, second, and third month. • **Sales person** (or other productivity driven role) ramp time: When you add a new sales person you probably don't want to assume that they will be 100% productive in their first month but rather that they ramp up at some percentage over time.
For more information on relative dates, see [Relative Time for Variables](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/create-edit-variables/relative-time-for-variables.md). |
| **Start relative dates from "0" / Start from "0"** | Activate if the first period to be considered is **Period 0**. |
| **Use fiscal years** | Activate this option if you also want to use a fiscal year for your model and select the **Start month** and if you want to have your fiscal year label be based on the **end of year** or start of year.
Your fiscal year settings will affect the column headers in the spreadsheet, as well as any quarterly and yearly roll-up columns.
**Example:** If your fiscal year runs from **April 1** to **March 31**, then you would set your start month to be **April**. If you chose the label to be based on the end of the year, i.e. the fiscal year from **April 1, 2024** to **March 31, 2025** would be labelled **"FY24"**. |
| **Highlight today in spreadsheet** | Activate this option to highlight the current timestep in the **spreadsheet** view. |
## Using the Time Filter in a Spreadsheet or Dashboard in xP&A
In xP&A, you can easily adjust the time period you are looking at across the spreadsheet and dashboard by adjusting the time filter in the top-right corner:
Time filter in the spreadsheet
You can choose between the following options for adjusting the time filter in xP&A:
- Enter a **custom** time filter using the calendar:
Custom time filter
- Select a dynamic **suggested** option (e.g. **Last 6 months of actuals, Last actual month, Current year, Next year**), which will automatically update the visible time range based on changes to either the [Last Actual Date](https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/modeling-your-data/working-with-time/last-actual-date.md), or calendar time.
**Example**: if your time filter is set to **Last 6 months of actuals**, and you roll forward your model's **Last actual date**, the filter will automatically adjust for the latest 6 months of actuals.
Suggested time filter
> **Warning:** - The time filter setting does not change the model time settings or underlying calculations, it simply filters for the time range you have selected.
> - Dashboard viewers (who do not have edit access to the underlying model) can easily toggle the period they are looking at by themselves (although the default period will be set by model editors).
---
---
title: "xP&A Video Tutorials"
source_url: https://support.lucanet.com/en/documentation/xp-a---extended-planning-and-analysis/x-pa-video-tutorials
language: en
last_updated: 2026-05-01
---
# Video Tutorials in Lucanet xP&A
## Overview
In this section you will find **video tutorials** that will help you to learn and use our Lucanet xP&A (Extended Planning & Analysis) solution.
> **Note:** Please note that currently the videos still show the user interface of the former product Causal and that some functionalities may slightly differ between Causal and Lucanet xP&A.
>
> One difference is, for example, the renaming from **Categories in Causal** to **Dimensions in xP&A.**
> **Note:** The videos also offer **Spanish subtitles**. To enable Spanish subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español**.
## xP&A 101
The best way to learn xP&A. This series will take you through the interface, the structure, and more.
### The Spreadsheet
Video: https://player.vimeo.com/video/1060082452?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Formulas and Scenarios
Video: https://player.vimeo.com/video/1060082317?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Charts and Tables
Video: https://player.vimeo.com/video/1060082544?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Connecting to Data
Video: https://player.vimeo.com/video/1060082289?muted=false&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
## xP&A for Finance
Learn how to use xP&A to understand and forecast your business.
### Setting Up Your P&L
Video: https://player.vimeo.com/video/1060082395?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Building a Headcount Plan
Video: https://player.vimeo.com/video/1060082485?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Building a Revenue Forecast
Video: https://player.vimeo.com/video/1060082518?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Setting Up Your Budget
Video: https://player.vimeo.com/video/1060082368?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
### Sharing With Stakeholders
Video: https://player.vimeo.com/video/1060082433?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
---
## ESG Reporting
Lucanet ESG Reporting meets all the requirements in the ESG report process, because it covers all non-financial risks and opportunities that can arise in connection with the daily activities of an enterprise. ESG Reporting complies with the ESRS provisions, the EU taxonomy, and the GHG protocol, and provides decentralized data collection with customized questionnaires. It can also be used to calculate GHG emissions.
---
title: "Adding Custom Questions"
description: "As an ESG Administrator, you can extend the ESRS, ESRS 2.0, or VSME questionnaire with your own custom questions to collect company-specific metrics, voluntary disclosures, or internal KPIs within the same data collection workflow."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions
language: en
last_updated: 2026-09-28
---
# Adding Custom Questions
## Overview
As an **ESG Administrator**, you can extend the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire with your own **custom questions**. Custom questions let you collect company-specific metrics, voluntary disclosures, or internal KPIs that go beyond the standard framework content, within the same governed data collection workflow.
You add custom questions in the **Questionnaire builder**, directly under the **disclosure requirement** they belong to. This page describes how to add, reorder, and delete them.
> **Note:** Custom questions can only be added by an **ESG Administrator** and only while the questionnaire is **editable**, i.e., while you are working on a draft (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)). ESG Data Collectors and reviewers cannot add custom questions.
## Question Types
When you add a custom question, you first choose its type. The following types are available:
| Type | Description |
|---|---|
| **Text input** | Free text field. |
| **Numeric input** | Numeric field, optionally with a unit and with 0 or 2 decimal places. |
| **Monetary** | Amount of money, formatted in the report currency with 2 decimal places. |
| **Yes/No** | Yes/no question. |
| **Static table** | A table with fixed rows and fixed columns. |
| **Dynamic table** | A table with fixed columns and flexible rows, where the ESG Data Collector adds the rows during data collection. |
In addition, the **Custom information** section of the dialog offers one entry that is not answered by an ESG Data Collector:
| Type | Description |
|---|---|
| **Formula-based KPI** | A calculated value. It is calculated from the answers to other questions of the questionnaire and is read-only during data collection (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)). |
## Adding a Custom Question
1. In the **Questionnaire builder**, click **Edit** to start a draft.
2. Expand the questionnaire down to the **disclosure requirement** to which you want to add a custom question.
3. On the disclosure requirement, click **+ Add custom question**.
'+ Add custom question' button on a disclosure requirement
4. In the **Add custom question** dialog, select the type of question you want to add, then click **Next**.
Choosing the type of custom question
5. Enter the question details and complete the question (see *Single Questions* or *Table Questions* below).
When you add a custom question, the following applies:
- The question is inserted at the **top** of the existing questions within the disclosure requirement.
- The question is marked with a **Custom** badge in the questionnaire builder (see *Displaying the 'Custom' Badge* below).
- The question is assigned to **all reporting entities** by default. You can change the assignment in the same way as for standard questions (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
- If the parent disclosure requirement is hidden, the custom question is hidden as well.
> **Note:** Custom questions are part of the questionnaire draft. Click **Apply changes** in the questionnaire builder to save them. Click **Discard** to remove all changes made in the draft.
### Single Questions
For **Text input**, **Numeric input**, **Monetary**, and **Yes/No** questions, you go straight to the question details after selecting the type.
Complete the following fields, then click **Add**:
| Field | Description |
|---|---|
| **Question number** | An identifier of your choice, e.g., `CQ-1`. It is not renumbered automatically when you reorder questions. |
| **Question text** | The question shown to the ESG Data Collector. |
| **Unit** | Optional. The unit of measurement displayed to the ESG Data Collector next to the answer field, for example `tCO2e`, `MWh`, or `FTE`.
**Note:** Only available for **Numeric input** questions.
|
| **Decimal places** | Optional. A drop-down list with the options **0** and **2**, set to **0** by default. The setting controls how the entry of the ESG Data Collector is formatted: with **0** decimal places, an entry of `1234.56` is displayed as `1,234`.
**Note:** Only available for **Numeric input** questions.
|
| **Guideline text** | Reference text for the question, comparable to the guideline text of standard questions. |
| **Additional guidance** | Company-specific instructions, examples, or internal references. |
Entering the details of a single custom question
### Table Questions
For **Static table** and **Dynamic table** questions, you first enter the same question details as for a single question, then click **Next** to define the table structure.
The dialog for adding a table appears as follows, for example:
Defining the table structure for a static table
On the **Define the table structure** screen:
1. Click **+ Add column** for each column you need. Enter a column label and select the column type: **Text**, **Numeric**, or **Monetary**.
For **Numeric** columns, a second drop-down list appears in which you select **0 decimal** or **2 decimals**. The default is **2 decimals**.
2. Add the rows. The available row types depend on the table type:
- For a **static table**, click **+ Add row** and choose the row type:
- **Add empty value row** — a row for the ESG Data Collector to fill in.
- **Add total row** — a row that automatically sums the numeric and monetary columns during data collection.
Enter a label for each row.
- For a **dynamic table**, only **+ Add total row** is available, because the value rows are added by the ESG Data Collector during data collection. The table structure displays the note **The rows will be added by the data collector**, and the total row is labelled **Total value**.
3. Click **Add** to create the custom question.
> **Warning:** When you delete a column or row from a table question that already contains collected data, a warning appears before the data is removed. Deleting the column or row also deletes the data that has been collected for it.
## Displaying the 'Custom' Badge
Custom questions are marked with a **Custom** badge so that you can distinguish them from standard framework questions. The badge is shown:
- In the **Questionnaire builder**.
- In the **aggregated report** (see [Generating ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md)).
The badge is **not** shown to ESG Data Collectors in the data collection interface or to reviewers in the review interface, so that custom questions look and behave like standard questions during data collection.
Custom question with the 'Custom' badge
## Editing a Custom Question
You can change the details of a custom question as long as the questionnaire is editable, i.e., while you are working on a draft.
1. Click the three-dot icon next to the custom question and select **Edit**.
2. Change the details in the **Edit custom question** dialog.
**Note**: The question type cannot be changed.
3. Click **Save**.
4. Click **Apply changes** in the questionnaire builder to save your changes.
> **Warning:** If you change the **Unit** of a custom question for which responses have already been collected, these responses are deleted. Before the change is applied, the dialog **Change Unit** appears.
> Click **Change Unit** to delete the responses and apply the new unit, or **Cancel** to keep the current unit. If no responses have been collected yet, the unit is changed without a confirmation.
## Reordering Custom Questions
You can change the order of custom questions within a disclosure requirement:
1. Navigate to the custom question you want to reorder.
2. Drag the question to its new position within the **same** disclosure requirement. You cannot move a custom question into a different disclosure requirement.
3. Click **Apply changes** to save the new order and data.
The question number does not change when you reorder questions.
Option for reordering a custom question
## Deleting a Custom Question
To delete a custom question, click the three-dot icon next to it and select **Delete**. Remember to click **Apply changes** to save your changes.
> **Warning:** Before you delete a question or a table column, check whether the formula of a [formula-based KPI](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md) refers to it. If a value used in a formula is no longer part of the questionnaire, the KPI can no longer be calculated and the formula has to be corrected. Use the **Preview** option of a KPI to see what its formula refers to.
Once your questionnaire is complete, continue with [Starting Data Collection](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/starting-data-collection.md). For how custom questions are filled out, see [Filling Out Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data.md).
---
---
title: "Adding Formula-Based KPIs"
description: "As an ESG Administrator, you can extend the questionnaire with formula-based KPIs. A KPI calculates its value automatically from the answers to other questions in the questionnaire and is displayed as read-only during data collection."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis
language: en
last_updated: 2026-09-25
---
# Adding Formula-Based KPIs
## Overview
As an **ESG Administrator**, you can add **formula-based KPIs** to the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire. A formula-based KPI is a **calculated value**: instead of being answered by an ESG Data Collector, it is calculated from the answers to other questions in the same questionnaire.
This keeps derived metrics, for example ratios, shares, or totals, in the Lucanet CFO Solution Platform, and the derivation is transparent for everyone who works with the report. A manual calculation after data collection is no longer needed.
You add formula-based KPIs in the **Questionnaire builder**, in the same place as custom questions, that is, in the **disclosure requirement** they belong to.
> **Note:** As an **ESG Administrator**, you can only add formula-based KPIs while the questionnaire is **editable**, that is, while you are working on a draft (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
## Formula Elements
A formula combines **operands** with **operators**.
**Operands**
An **operand** is a value from the questionnaire that is used in the formula calculation. ESG Reporting provides an **operand catalog** with all operands that produce a number in the questionnaire:
| Operand | Description |
|---|---|
| **Numeric and monetary questions** | The answer to a question of the type **Numeric input** or **Monetary**. |
| **Static table cells** | A single cell of a static table, identified by its row and column. A table question therefore provides as many operands as it has cells. |
| **Dynamic table column totals** | The total of a dynamic table column across all rows the ESG Data Collector enters. |
| **Other formula-based KPIs** | A KPI that is already defined in the same questionnaire. |
| **Fixed numbers** | A number entered directly in the formula, for example for a conversion or constant factor. |
Questions that do not produce a number, that is, **Text input**, **Yes/No**, and **Date**, are not offered in the catalog and cannot be used in a formula.
**Operators**
The formula editor provides a toolbar with the following operators:
| Operator | Meaning |
|---|---|
| **+** | Addition |
| **−** | Subtraction |
| **×** | Multiplication |
| **÷** | Division |
| **%** | Expresses the result as a percentage |
| **(** and **)** | Parentheses, to control the order of calculation |
> **Note:** You never type formula syntax yourself. Each operand is inserted as a separate element that you can remove individually, and it keeps pointing at the right question even if that question is later renamed.
## Adding a Formula-Based KPI
Proceed as follows:
1. In the **Questionnaire builder**, click **Edit** to start a draft.
2. Expand the questionnaire down to the **disclosure requirement** to which you want to add the KPI.
3. On the disclosure requirement, click **+ Add custom question**.
'+ Add custom question' button on a disclosure requirement
4. In the **Add custom question** dialog, select the **Formula-based KPI** option in the **Custom information** section and click **Next**. The dialog is then displayed as follows:
Entering the details of a formula-based KPI
5. Enter the KPI details:
- **KPI number**: The number under which the KPI appears in the questionnaire, for example `BP-1.99`.
- **KPI name**: The name displayed to the ESG Data Collectors.
- **Unit**: The unit of the calculated value, for example `tCO2e`, `MWh`, `FTE`, or `%`.
- **Decimal places**: Select **0** or **2** from the drop-down list. The default is **2**.
6. In the **KPI / Calculated field** area, build the formula. You have the following options:
- **Insert operands**: Click **@** or type `@` in the formula field. The operand catalog opens and displays the structure of the questionnaire. Use the search to find an operand by its question number or its text. Click the operand you want to use to insert it into the formula.
- **Insert operators**: In the toolbar, click the operator you want to use.
Searching for an operand in the operand catalog
Repeat until the formula is complete. To remove an operand, click the **x** next to it.
A completed formula for a percentage KPI
7. Click **Add**.
When you add a formula-based KPI, the following applies:
- The KPI is inserted at the **top** within the disclosure requirement and is marked with a formula icon.
- The KPI has **no reporting entity assignment of its own**. A KPI is displayed to a reporting entity only if that reporting entity is assigned to all the questions used in its formula (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
- If the parent disclosure requirement is hidden, the KPI is hidden as well.
A formula-based KPI in the questionnaire builder
> **Note:** Like custom questions, formula-based KPIs are part of the questionnaire draft. Click **Apply changes** to save them, or **Discard** to remove all changes made in the draft.
## Checking a KPI Before Data Collection
To see how a KPI will appear to the ESG Data Collectors, click the three-dot icon next to it and select **Preview**. The preview displays the KPI number, the KPI name, the formula in full, and the read-only value field with its unit.
Preview of a formula-based KPI
In the formula, each operand is displayed with its complete path — question number, question text, and, for table cells, the row and column — so you can check that the formula refers to the values you intended.
## Editing and Deleting a Formula-Based KPI
Using the three-dot icon next to the KPI, you can [edit](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md#editing-a-custom-question) or [delete](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md#deleting-a-custom-question) the KPI in the same way as a custom question. When you edit a KPI, you change both its details and its formula.
## Displaying the Formula-Based KPI During Data Collection
Once data collection has started, the KPI is calculated from the answers of each reporting entity and is displayed as read-only — see [Filling Out Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data.md). In the aggregated report, a group value is calculated in addition to the per-entity values — see [Generating ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md).
---
---
title: "All Steps at a Glance – ESG Reporting"
description: "In this chapter, you will find the individual steps required to create an ESG report. These steps must be carried out in the order indicated by either the ESG Administrator or the ESG Data Collector. The step descriptions also contain links to more detailed descriptions."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/process-description-esgrep
language: en
last_updated: 2026-09-28
---
# All Steps at a Glance – ESG Reporting
## Overview
In this chapter, you will find the individual steps required to create an ESG report. These steps must be carried out in the order indicated by either the ESG Administrator or the ESG Data Collector. The step descriptions also contain links to more detailed descriptions.
### Step 1: Creating a Report and Entering the Master Data
The ESG Administrator creates a new ESG report and enters the master data for it, e.g. the period and the reporting entities. The ESG Administrator also selects the report guideline, i.e. [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme), and can initiate the double materiality assessment as well as the option to collect EU Taxonomy data.
For more information, see [Creating an ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md).
### Step 2: Mapping of Double Materiality Assessment Results
In case the ESG Administrator has selected the ESRS report guideline, the mapping of a previously executed double materiality assessment can be carried out to help determine the scope of the ESRS questionnaire for each reporting entity.
For more information, see [Mapping Double Materiality Assessment Results](https://support.lucanet.com/en/documentation/esg-reporting/perform-dma.md).
### Step 3: Configuring the Report Questionnaire
Before data collection begins, the ESG Administrator defines the scope of the ESRS, ESRS 2.0, or VSME questionnaire, and can extend the questionnaire with custom questions and formula-based KPIs.
For more information, see [Configuring the Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md).
### Step 4: Collecting Data
**Editors** can collect the following:
- **ESG data** in the ESRS or VSME questionnaire and the Emissions Module. **Reviewers** then review the collected data.
- **EU Taxonomy data** in the **Reports and Activities** workspace.
During data collection, the collected data is already **aggregated**, and the ESG Administrator can access the aggregated data.
For more information, see [Collecting Data for ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep.md).
### Step 5: Checking Data
The ESG Administrator checks the submitted data and can then either approve the data or reject them and send them back.
For more information, see [Checking Data](https://support.lucanet.com/en/documentation/esg-reporting/check-data-esgrep.md).
### Step 6: Generating ESG Report and Preparing Data for Disclosure Management
Once all data have been approved, the ESG Administrator can generate an ESG report at the touch of a button and prepare it automatically for [Lucanet Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md). There, the data can be made available via a data import and used in reports.
The ESG Administrator can also view a report of the aggregated data.
For more information, see [Aggregating Data](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md).
### Step 7: Optional Actions:
If required, the ESG Administrator can create custom emission factors for the emission module, see [Creating Custom Emission Factors](https://support.lucanet.com/en/documentation/esg-reporting/creating-custom-emission-factors.md).
If required, the ESG Administrator can download the ESG report as a CSV file, and the EU Taxonomy report as an Excel file.
For more information, see [Exporting Data](https://support.lucanet.com/en/documentation/esg-reporting/export-data-esgrep.md).
If required, the ESG Administrator can reopen the aggregated ESG report to collect updated values from the assigned reporting entities.
For more information, see [Reopening an Aggregated ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/reopening-aggregated-esg-reports.md).
---
---
title: "Assessing Minimum Safeguards"
description: "In the Minimum Safeguards workspace, you can fill out a questionnaire for your reporting entity assessing whether your reporting entity meets the minimum safeguards criteria, i.e. essential international guidelines, focusing on four core standards: \nOECD Guidelines for Multinational Enterprises\nUN Guiding Principles on Business and Human Rights\nILO Fundamental Conventions\nThe International Bill of Human Rights."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/minimum-safeguards
language: en
last_updated: 2026-05-01
---
# Assessing Minimum Safeguards
## Overview
In the **Minimum Safeguards** workspace, you can fill out a questionnaire for your reporting entity assessing whether your reporting entity meets the minimum safeguards criteria, i.e. essential international guidelines, focusing on four core standards:
- **OECD Guidelines for Multinational Enterprises**
- **UN Guiding Principles on Business and Human Rights**
- **ILO Fundamental Conventions**
- **The International Bill of Human Rights**.
Confirming your reporting entity's alignment with these standards is an essential step to ensure the **alignment with the EU Taxonomy** for any business activity related to your reporting entity.
## Completing the Minimum Safeguards Questionnaire
Proceed as follows to assess whether your reporting entity meets the minimum safeguards criteria:
1. Navigate to the **Minimum Safeguards** workspace.
2. Navigate to the desired ESG report and click your reporting entity. The questionnaire is displayed as follows:
Minimum safeguards questionnaire
3. Answer all questions and provide an explanation, if necessary.
## Impact of Questionnaire
After having completed the questionnaire, the ESG Reporting solution automatically assesses whether the minimum safeguards criteria have been met. The following options are possible:
| Option | Description |
|---------|---------|
| All questions have been answered with **Yes** | The minimum safeguards criteria **have been met** for this reporting entity. |
| At least one question has been answered with **No** | The minimum safeguards criteria **have not been met** for this reporting entity. |
| Questions have been answered **partially** or not yet | The assessment of the minimum safeguards for this reporting entity **is in progress**. |
> **Note:** The status of the minimum safeguards assessment is automatically updated and displayed:
>
> - On the **Minimum Safeguards** overview page
> - On the business activity overview page of your reporting entity in the **Reports and Activities** workspace
>
> the status message on minimum safeguards assessment in business activity overview icon
> Status message on minimum safeguards assessment in business activity overview
---
---
title: "Assigning Users as Editors or Reviewers"
description: "When configuring the ESRS or VSME questionnaire, you as an ESG Administrator can assign reporting entities along with its designated ESG Data Collectors that were defined in the master data administration to certain parts of the questionnaire. These ESG Data Collectors then are assigned as editors to the entire questionnaire or parts of it (see Using the Questionnaire Builder)."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/defining-access-esgrep
language: en
last_updated: 2026-05-01
---
# Assigning Users as Editors or Reviewers
## Overview
When configuring the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire, you as an **ESG Administrator** can assign reporting entities along with its designated ESG Data Collectors that were defined in the master data administration to certain parts of the questionnaire. These ESG Data Collectors then are assigned as **editors** to the entire questionnaire or parts of it (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
Additionally, you can make sure that either the entire questionnaire data or certain parts are **edited** or **reviewed** by **subject matter experts**, depending on the categories or questions. To do so, you can assign further users to the questionnaire or parts of it even if the users have not been assigned to a reporting entity in the master data administration.
## Prerequisites
To assign a user as **editor** or **reviewer** to parts of the questionnaire, please ensure that:
- The required user is licensed for the user role **ESG Data Collector** or **ESG Administrator** (see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md)).
- The ESG report has progressed to step **3 Data collection** or higher.
## Assigning Users as Editors or Reviewers
To define the accessible scope of the questionnaire for an individual user and assign them as editor or reviewer, do the following:
1. Navigate to the data collection page of the reporting entity for which you want to define the access.
2. On the data collection page, navigate to the required elements, e.g. categories, standards, or questions, and click the users icon .
3. Activate or deactivate the check box in the **Reviewer** or **Editor** column for the required users. You can use the search box to quickly find and assign users.
4. Click **Apply**.
Assigning users to 'Basis for preparation'
> **Note:** Please note:
>
> - Users **cannot** be assigned as editors and reviewers simultaneously.
> - The assignment **cannot** be changed for users that have been defined as ESG Data Collectors in the master data administration, i.e. these users are automatically assigned to the whole questionnaire.
> - If you change the assignment for an element that is a category, standard, section, or disclosure requirement, you automatically change the assignment for all subordinate elements as well.\
> \
> **Example**: If you assign a user as editor to the section **Basis for Preparation**, you will also assign this user as editor to the subordinate disclosure requirements and questions, such as **BP-1 General basis for preparation of sustainability statements**.
---
---
title: "Canceling an ESG Report"
description: "As an ESG Administrator, you can cancel ESG reports. This is useful if errors are discovered, for example. You can cancel any ESG report that has not yet reached “Data aggregation” status."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/cancel-report-esgrep
language: en
last_updated: 2026-05-01
---
# Canceling an ESG Report
## Overview
As an **ESG Administrator**, you can cancel ESG reports. This is useful if errors are discovered, for example. You can cancel any ESG report that has not yet reached **Data aggregation** status. Canceled reports are listed separately.
## Canceling an ESG Report
To cancel an ESG report, go to **ESG Reports**. Navigate first to the Report overview, then to the ESG report you wish to cancel. In the **Status** column, click the three dots icon. In the displayed context menu, select the **Cancel** command. In the displayed dialog, click **Cancel report**.
Context menu to cancel an ESG report
## Viewing Canceled ESG Reports
You can access canceled ESG reports at any time. To do this, navigate to **ESG Reports** or **Data Collection** and open the **Canceled Reports** tab:
Example for 'Cancelled reports' tab under 'Data Collection'
---
---
title: "Checking Data"
description: "Once the ESG Data Collectors have collected and submitted all the data for both the ESRS or VSME questionnaire and the Emissions Module, as an ESG Administrator, you can check the submitted data and approve them – or reject them, if necessary."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/check-data-esgrep
language: en
last_updated: 2026-05-01
---
# Checking Data
## Overview
Once the ESG Data Collectors have collected and submitted all the data for both the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire and the Emissions Module, as an **ESG Administrator**, you can check the submitted data and approve them – or reject them, if necessary.
## Checking Data
Once the ESG Data Collectors have collected and submitted all the data for both the questionnaire and the Emissions Module, as an ESG Administrator, you can check the data. To do this, navigate to the desired ESG report in the **ESG Reports** or **Data Collection** workspace and click the reporting entity whose data you want to check. The data collection page is displayed as follows, for example:
Options to check submitted data of a reporting entity
Use the panel on the right-hand side to navigate between categories, or click **Show notes** to display any notes left by the ESG Data Collector when submitting their data. You can also click the attachment icon to check if the ESG Data Collector has attached files to provide background information regarding their answer.
## Adding or Editing Additional Guidance
In case you need the reporting entities to submit or change report data, you can use the **Additional guidance** option in the report (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)) to add additional guidance or edit existing notes.
> **Warning:** Note that **changing or deleting additional guidance** for a question for which data have already been collected **resets** the status of that question for the assigned reporting entities.
## Approving or Rejecting Data
Once you have checked the data, you have two options:
- If the data are correct, click **Approve**.
- If you find any problems in the data, click **Reject**. If you reject the data, the ESG data collectors must review the information they submitted.
You can approve or reject data by selecting the desired option directly on the data collection page of a reporting entity.
Options to reject or approve report data
You can also approve or reject data in the **ESG Reports** or **Data Collection** workspace (see [General Functions in ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting/general-functions-esg.md)).
---
---
title: "Collecting and Reviewing ESG Data"
description: "Once the ESRS, ESRS 2.0, or VSME questionnaire has been configured and the data collection process has started, the ESG data can be collected and reviewed by all users assigned as editors or reviewers. \nDuring data collection, ESG Administrators can add users and assign individual users to be editors or reviewers and display the aggregated responses that have been collected at a given time.\nAfter all data have been collected and reviewed, the questionnaire can be submitted."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep
language: en
last_updated: 2026-05-01
---
# Collecting and Reviewing ESG Data
## Overview
Once the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire has been configured and the data collection process has started, the ESG data can be collected and reviewed by all users assigned as **editors** or **reviewers**.
During data collection, **ESG Administrators** can add users and assign individual users to be editors or reviewers and display the aggregated responses that have been collected at a given time.
After all data have been **collected** and **reviewed**, the questionnaire can be **submitted**.
## Administration and Monitoring by ESG Administrators
During data collection, you as an **ESG Administrator** can administrate and monitor the data collection as follows:
- You can assign individual users as editors or reviewers to certain parts of the questionnaire (see [Assigning Users as Editors or Reviewers](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/defining-access-esgrep.md)).
- You can make changes to the scope of the questionnaire (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
- You can display the aggregated responses that have been collected so far at any time (see [Displaying Aggregated Responses During Data Collection](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/enhancements-for-aggregated-esg-reports.md)).
## Data Collection Process
In general, the process for data **collection** and **review** is as follows:
| Step | Description |
|---------|---------|
| Navigating to the ESG report | Users can access the data collection page by navigating to the ESG Reporting solution and clicking the required reporting entity: the data collection esgrep data collection icon View of the 'Data Collection' workspace for ESG Data Collectors In the subsequently displayed data collection page, users can switch between the tabs for **ESRS**, **ESRS 2.0**, or **VSME** and the **Emissions Module** tab via the tab view at the top. |
| Collecting data | If a user has been assigned by an ESG Administrator as an **editor**, they fill out the questionnaire and the Emissions Module entirely or only the questionnaire parts that have been assigned to them. After entering data for a question, the editors activate the **Mark as completed** check box to indicate that the question is **ready for review** (see [Filling Out Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data.md) and [Filling Out the Emissions Module](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/fill-out-emission-module.md)). |
| Reviewing data | If a user has been assigned by an ESG Administrator as a **reviewer** to the entire questionnaire or parts of the questionnaire, they can start reviewing the data as soon as the data has been collected (see [Reviewing Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/reviewing-data.md)). |
| Submitting data | Once all the data have been collected for both the questionnaire and the Emissions Module, **editors** or **reviewers** can click **Submit**, and leave a note, if necessary. The data will then be checked by the ESG Administrator. |
> **Note:** If any of the required data is missing, has not been marked as complete, or has not been reviewed, the users will **not** be able to submit the data. To submit the data, all questions must be marked as **Completed**, and all questions with an assigned reviewer must be marked as **Reviewed**. The questions with missing data or statuses will be automatically marked with a validation message to make them easier to identify.
---
---
title: "Collecting Data for ESG Report"
description: "Once the ESRS, ESRS 2.0, or VSME questionnaire has been configured and the data collection process has started, ESG users can start with collecting the following data:\nESG data can be collected and reviewed in the ESRS, ESRS 2.0, or VSME questionnaires, and the Emissions module by all users assigned as editors or reviewers, see Collecting and Reviewing ESG Data. \nEU Taxonomy data can be collected in the functional area EU Taxonomy by users who were assigned for this task in the master data administration, see Collecting EU Taxonomy Data."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep
language: en
last_updated: 2026-05-01
---
# Collecting Data for ESG Report
## Overview
Once the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire has been configured and the data collection process has started, ESG users can start with collecting the following data:
- **ESG data** can be collected and reviewed in the ESRS, ESRS 2.0, or VSME questionnaire, and the Emissions module by all users assigned as **editors** or **reviewers**, see [Collecting and Reviewing ESG Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep.md).
- **EU Taxonomy data** can be collected in the functional area **EU Taxonomy** by users who were assigned for this task in the **master data administration**, see [Collecting EU Taxonomy Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data.md).
---
---
title: "Collecting EU Taxonomy Data"
description: "The EU Taxonomy is a classification system established by the European Union to define which economic activities can be considered environmentally sustainable.\nIn the EU Taxonomy functional area, users can create business activities, such as using solar energy panels, and assess if these business activities are eligible for the EU Taxonomy."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data
language: en
last_updated: 2026-05-01
---
# Collecting EU Taxonomy Data
## Overview
The [EU Taxonomy](https://support.lucanet.com/en/documentation/glossary.md#eu-taxonomy) is a classification system established by the European Union to define which economic activities can be considered environmentally sustainable.
In the **EU Taxonomy** functional area, users can:
- Create **business activities**, such as using solar energy panels, and assess if these business activities are **eligible** for the EU Taxonomy (see [Creating a Business Activity and Performing the Eligibility Assessment](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/create-ba-perform-eligibility.md)).
- Perform the **alignment assessment**, i.e.:
- Perform the **minimum safeguards assessment** (see [Performing Minimum Safeguards Assessment](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/minimum-safeguards.md)) for a reporting entity.
- Cover the SCC and DNSH questionnaires for every business activity (see [Performing Alignment Assessment](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/alignment-assessment.md)).
- Provide an oversight of their reporting entity's financial status (see [Collecting Financial Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/collect-financial-data.md))
- **Export** the aggregated EU Taxonomy data in standardized Excel format for regulatory compliance and integration with Lucanet Disclosure Management (see [Exporting Data](https://support.lucanet.com/en/documentation/esg-reporting/export-data-esgrep.md)).
## Prerequisites for Collecting EU Taxonomy Data
To be able to start with the data collection for the EU Taxonomy report, you first need to complete the setup of the questionnaire builder (needs to be done by an **ESG Administrator**, see also [Configuring the ESRS or VSME Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md)). Otherwise, you cannot access your report in the **Reports and Activities** workspace.
## Recommended Step Sequence
To create an EU Taxonomy report, we recommend the following step sequence:
1. Create any number of business activities and perform the taxonomy eligibility.
2. Fill out the minimum safeguards questionnaire.
3. Assess the taxonomy alignment for the business activity.
4. Enter the financial data for the business activity.
> **Tip:** You can export collected EU Taxonomy report data in an Excel file, see [Exporting Data](https://support.lucanet.com/en/documentation/esg-reporting/export-data-esgrep.md).
---
---
title: "Collecting Financial Data"
description: "In the Financial Data workspace, users can collect and manage financial data required for EU Taxonomy reporting, i.e. baseline values and business activity values."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/collect-financial-data
language: en
last_updated: 2026-05-01
---
# Collecting Financial Data
## Overview
In the **Financial Data** workspace, users can collect and manage financial data required for [EU Taxonomy](https://support.lucanet.com/en/documentation/glossary.md#eu-taxonomy) reporting, i.e.:
- **Baseline values**, i.e. revenue, capital expenditure (CapEx), and operational expenditure (OpEx) **of the reporting entity**
- **Business activity values**, i.e. revenue, capital expenditure (CapEx), and operational expenditure (OpEx) **of each business activity**
Based on this information, investors and external stakeholders will get deeper insights on how sustainable a company is.
In the **Financial Data** workspace, users can access the financial data overview to see all EU Taxonomy reports and their assigned reporting entities.
**ESG Data Collectors** can navigate to the individual pages of **reporting entity financial data** to collect and manage financial data, and collect baseline values and account information for each reporting entity and for eligible business activities based on eligibility and alignment assessments
**ESG Administrators** can monitor the status of financial data collection in read-only mode.
## Navigation
The **Financial Data** workspace is part of the **EU Taxonomy** folder and provides an overview of the data collection status for each reporting entity. The individual data collection page for the financial data is displayed as follows, for example:
Page for collecting financial data for a reporting entity
## Collecting Baseline Values
**Baseline values** represent the foundational financial data (turnover, CapEx, OpEx) that must be collected for each reporting entity before business activity values can be completed. To collect baseline values, do the following:
1. Specify the turnover, CapEx, and OpEx in the currency specified in the master data.
2. Specify the accounts that were taken into account to determine the baseline value.
3. Activate the check box in the top right section to mark the baseline values section as completed.
> **Note:** To **change** or **delete** values after having marked the section as complete, you can deactivate the checkbox and make your changes. Please keep in mind that this might affect related business activities and set their status back to **In Progress**.
## Collecting Business Activity Values
**Business activity values** are collected separately for each eligible business activity and environmental goal combination. These sections only appear for business activities that have successfully passed the eligibility assessment. To collect business activity values, do the following:
1. For each business activity, specify the turnover, CapEx, and OpEx in the currency specified in the master data in each row.
2. Activate the check box in the top right section to mark the business activity section as completed.
> **Note:** To access **details** on the **eligibility assessment** or **alignment assessment** of a specific business activity, you can click the three-dot menu on the right-hand side and select **Open Eligibility assessment** or **Open Alignment assessment** from the context menu.
## Statuses for Financial Data Collection
After having specified financial data, the ESG Reporting solution automatically assesses the completion status and displays the corresponding icon next to the title of the reporting entity. The following statuses are possible:
| Option | Description |
|---------|---------|
| the eligible aligned icon | **Completed**, i.e. baseline values and all business activity sections are marked as **Completed**. |
| the in progress icon | **In progress**, i.e. one or more sections have not been completed yet. |
---
---
title: "Configuring the Report Questionnaire"
description: "Once you have created an ESG report as an ESG Administrator and entered the master data, you can continue by configuring the ESRS, ESRS 2.0, or VSME questionnaire, depending on the report guideline chosen in the master data.\nThe ESRS questionnaire is based on the ESRS requirements, whereas the VSME questionnaire is based on EFRAG. Both questionnaire versions can be configured individually."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep
language: en
last_updated: 2026-05-01
---
# Configuring the Report Questionnaire
## Overview
Once you have created an ESG report as an **ESG Administrator** and entered the master data, you can continue by configuring the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire, depending on the report guideline chosen in the master data.
The ESRS questionnaires are based on the ESRS requirements, whereas the VSME questionnaire is based on EFRAG. Both questionnaire versions can be configured individually.
- Refer to [Structure of the Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/structure-questionnaire.md) to learn more about the questionnaire's structure, general functions, and the impact of having mapped the results of a [double materiality assessment](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment) on the structure.
- Refer to [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md) to learn about how to define the questionnaire scope and to assign reporting entities.
- Refer to [Adding Custom Questions](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md) to learn about how to extend the questionnaire with your own company-specific questions.
- Refer to [Starting Data Collection](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/starting-data-collection.md) to learn about the next step.
---
---
title: "Covering SCC and DNSH Questionnaires"
description: "If your business activity is eligible for the EU Taxonomy, you can proceed to the Alignment assessment page. In this page, you specify for each of the environmental goals associated with your business activity whether your business activity is compliant with the following criteria:\nSubstantial Contribution Criteria (SCC) \nDo Not Significant Harm (DNSH)"
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/alignment-assessment
language: en
last_updated: 2026-05-01
---
# Covering SCC and DNSH Questionnaires
## Overview
If your business activity is **eligible** for the EU Taxonomy, you can proceed to the **Alignment assessment** page. In this page, you specify for each of the environmental goals associated with your business activity whether your business activity is compliant with the following criteria:
- Substantial Contribution Criteria (**SCC**)
- Do Not Significant Harm (**DNSH**)
Your business activity is considered as aligned with the EU Taxonomy if:
- The compliance with the SCC and DNSH criteria is achieved **and**
- Your reporting entity fulfils the [minimum safeguard](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/minimum-safeguards.md) criteria.
## Covering the SCC and DNSH Questionnaire
Proceed as follows to assess if your business activity is aligned with the EU Taxonomy:
1. On the **Eligibility assessment** page, click **Alignment assessment**. The **Alignment assessment** page is displayed as follows:
Example for 'Alignment assessment' page
2. If necessary, deactivate the toggle buttons for the environmental goals that are not applicable on the **Substantial Contribution Criteria (SCC)** tab. The criteria on the **Do No Significant Harm Criteria (DNSH)** tab will be adjusted accordingly (see information box below).
3. For each question of the displayed environmental goals on the **SCC** and **DNSH** tabs, indicate whether your business is **compliant** or not **compliant**, or choose **Not applicable** if the question does not apply to your business activity.
4. If necessary, enter a comment.
> **Note:** **Notes**:
>
> - If you activate **more than one** environmental goal on the **SCC** tab, all six criteria on the **DNSH** tab will be activated.
> - if you activate **only one** environmental goal on the **SCC** tab:
> - The other five criteria on the **DNSH** tab for the other environmental goals are activated.
> - The environmental goal activated on the **SCC** tab will be deactivated on the **DNSH** tab.
> - In case you change responses for the environment goals on the **Eligibility Assessment** page after starting the alignment assessment, resulting in qualifying or disqualifying environmental goals, the **display of qualified environmental goals** on the **Alignment assessment** page will change accordingly.
> - To navigate to the overview of the business activities of your reporting entity and their statuses, click **Activities overview** on the top right of the page.
---
---
title: "Creating a Business Activity and Performing the Eligibility Assessment"
description: "The EU Taxonomy is a classification system established by the European Union to define which economic activities can be considered environmentally sustainable.\nIn the EU Taxonomy functional area, users can create business activities, such as using solar energy panels, and assess if these business activities are eligible for the EU Taxonomy."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/create-ba-perform-eligibility
language: en
last_updated: 2026-05-01
---
# Creating a Business Activity and Assessing the Taxonomy Eligibility
## Overview
In the **Reports and Activities** workspace, users can create **business activities**, such as using solar energy panels, and assess if these business activities are **eligible** for the EU Taxonomy.
## Creating a Business Activity
To create a new business activity:
1. Open the **Reports and Activities** workspace and click the reporting entity for which you want to create business activities.
The overview of already created business activities is displayed as follows, for example:
Display of status of assessment for taxonomy eligibility and eligibility goals for business activities
2. In the top right corner, click **\+ Business activity**.
3. Specify the data for your business activity and perform the eligibility assessment (see following subheadline).
### Specifying Business Activity and Performing Eligibility Assessment
Specify the data for your business activity and perform the eligibility assessment as follows:
### General data
| Field | Description |
|---------|---------|
| Business activity name | Name of your business activity |
| EU Taxonomy sector | EU Taxonomy sector that corresponds to your business activity, e.g. the EU Taxonomy sector **Energy** corresponds to the business activity named **Geothermal District Heating Systems**. |
| EU Taxonomy activity | EU Taxonomy activity that falls under the chosen EU Taxonomy sector and that best describes your business activity, e.g. if you are generating energy from a photovoltaic plant, the suitable activity would be **Electricity generation using solar photovoltaic technology**. |
| NACE code | NACE code(s) that correspond(s) to your business activity. The selection of NACE codes has no effect on the eligibility, but it helps you to easier align your business activity with the EU Taxonomy. |
| None of the NACE codes apply | See tooltip for more information. |
### Financial figures
| Option | Description |
|---------|---------|
| Do you have financial figures (turnover, CapEx, OpEx) for the selected business activity in the current reporting period? | Indicate whether you can deliver financial figures for your selected business activity. |
### Environmental goals
Depending on the EU Taxonomy activity chosen above, the environmental goals are automatically displayed. For each of the environmental goals listed below, indicate whether your business activity can be associated with the EU Taxonomy activity or NACE code that is mentioned in the description in the blue information box:
1. Choose **Yes** or **No** for each environmental goal.
2. Provide an explanation as to why you chose **Yes** or **No**.
> **Note:** Please note:
>
> - The descriptions are derived directly from the taxonomy activities descriptions in the delegated regulations.
> - The following applies to the descriptions:
> - In case there is **more than one** environmental goal applicable, the descriptions might be **the same** for two or more goals. In that case, your answer for one of the goals is **automatically applied** to the other goals with the same descriptions.
> - If the descriptions are **different** for the environment goals, you have to answer for each goal individually.
> - On the right-hand side, you can find the following:
> - The **status of the assessment** for every individual goal
> - An **E** or **T** indicating the **contribution type**, i.e. the business activity is classified as a transitional or enabling business activity; please note that this does not apply for all business activities.
> - A **three-dot menu** with the option to display information on the **Substantial Contribution Criteria (SCC)** that are relevant for the environmental goal. The SCC information can help you determine whether your business activity is eligible for the EU Taxonomy regarding a specific environmental goal.
Example for business activity
## Statuses for Eligibility Assessment
After having configured your business activity, the ESG Reporting solution automatically assesses the taxonomy eligibility. The following statuses are possible:
| Icon | Description |
|---------|---------|
| the eligible aligned icon | **Eligible**: One or more environmental goals have been confirmed with **Yes**, and the question related to financial figures was answered **positively**. |
| the not eligible not aligned icon | **Not eligible**: **No** was chosen for **all** environmental goals, or the question related to financial figures was answered **negatively**. |
| the in progress icon | **In progress**: One or more environmental goals have not been confirmed with **Yes** or **No**, or the question regarding the financial figures has not been answered yet. |
> **Note:** If your business activity has the status **Eligible**, you can continue with the [alignment assessment](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/alignment-assessment.md).
---
---
title: "Creating Custom Emission Factors"
description: "In addition to standard emission factors from our database, you can use custom emission factors to include missing or organization-specific data, ensuring that your results better reflect your organization's activities or specific supplier data."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/creating-custom-emission-factors
language: en
last_updated: 2026-09-28
---
# Creating Custom Emission Factors
## Overview
In addition to standard [emission factors](https://support.lucanet.com/en/documentation/glossary.md#emission-factor) from our database, you can use custom emission factors to include missing or organization-specific data, ensuring that your results better reflect your organization's activities or specific supplier data.
Custom emission factors must first be created in the **Custom Emission Factors** workspace by an **ESG Administrator** before they can be used.
## Creating a Custom Emission Factor
To create a custom emission factor:
1. Navigate to the **Custom Emission Factors** workspace and click **Add custom factor**.
2. In the **Create Custom Emission Factor** dialog, enter the required data.
3. Click **Create** to save.
The new custom emission factor will be displayed in the table as follows, for example:
'Custom Emission Factors' workspace
> **Note:** **Decimal Precision of the Emission Factor Value**
>
> You can enter the **Total of kgCO2e** value with up to **6 decimal places** (e.g. `0.123456`), so that you can maintain more precise data. Values with fewer decimals and existing custom emission factors remain valid and are displayed as before — no adjustment is required. The value is displayed with the same precision in the **Custom Emission Factors** overview table.
## Defining the GHG Scope and Category
In the **Create Custom Emission Factor** and **Edit Custom Emission Factor** dialogs, you can use the optional **GHG Scope & Category** field to define where the custom emission factor is available when creating footprints in the Emissions Module.
'GHG Scope & Category' field in the 'Create Custom Emission Factor' dialog
The drop-down list offers the following options:
- **Scope 1**
- **Scope 2**
- **Scope 3 – All categories**
- The individual **Scope 3** categories 1 to 13.
A custom emission factor can carry several values (e.g. Scope 1 and Scope 3, Category 2). **Scope 3 – All categories** and the individual Scope 3 categories are mutually exclusive.
The field determines where the custom emission factor appears:
- **Left empty**: The custom emission factor is available for **every footprint**, regardless of its scope or category. This is the default and the state of all existing custom emission factors.
- **Containing a value**: The custom emission factor is available **only** for footprints whose scope — and, for Scope 3, category — matches one of the selected values.
> **Note:** **Notes**:
>
> - The **GHG Scope & Category** field is **optional** and never blocks creating or saving a custom emission factor.
> - You can configure the field when creating the custom emission factor and change it later — but only while the custom emission factor is **Not used** (see [Status of Custom Emission Factors](https://support.lucanet.com/en/documentation/esg-reporting/creating-custom-emission-factors/.md#status-of-custom-emission-factors)).
> - Existing custom emission factors are not changed. They remain available for every footprint until you edit them and define a scope and category.
## Status of Custom Emission Factors
Custom emission factors can have two statuses: **In use** (actively used in the calculation of a footprint) and **Not used** (not currently referenced). The status is displayed in the custom emission factors overview as follows, for example:
Status of custom emission factors
Custom emission factors with the status **Not used** can be edited or deleted as needed. If you leave the **Edit Custom Emission Factor** dialog with unsaved entries, the **Unsaved Changes** dialog is displayed.
## Exporting Custom Emission Factors
There are two options for exporting custom emission factors, including all their attributes, to a CSV file:
- Use the context menu opened by the three-dot icon next to each factor to download a single emission factor.
- Click **Export all** above the overview table to download all custom emission factors at once.
---
---
title: "Creating Report"
description: "As an ESG Administrator, your first responsibility within the ESG reporting process is to enter the master data for each ESG report, e.g. the period, the reporting entities to report, the users to report within these reporting entities, and the location of these reporting entities. This provides the basis for the ESG report and the subsequent steps."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep
language: en
last_updated: 2026-08-28
---
# Creating an ESG Report
## Overview
As an **ESG Administrator**, you do the first step of the ESG reporting process by creating an ESG report. When creating, you enter the master data, such as:
- The period, group currency, and the reporting entities to report
- The report guideline, i.e. [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme)
You also determine whether you want the report to be created based on the EU Taxonomy, and, in case of choosing ESRS as the report guideline, whether the reporting entities need to carry out a mapping of the [double materiality assessment](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment) results.
## Creating a Report and Entering Master Data
To create a report and enter the master data:
1. Navigate to the **ESG Reports** workspace and click **Create new report**.
The **Master Data** step is displayed as follows:
Master data user interface
2. Enter the following:
- **Name** of the ESG report
- **Period** to be taken into account when generating the report
- **Group currency** to use when entering numbers in the ESG report
3. Choose whether you want your ESG report to be based on **ESRS**, **ESRS 2.0**, or **VSME** requirements.
4. Activate the **EU taxonomy (Beta)** option if you want to assign users to create reports based on the EU taxonomy (see [Managing Reporting entities](#managing-reporting-entities)).
5. **Define reporting entities** that should be involved in the data collection process and assign users to provide data for the ESRS data collection and/or the EU taxonomy report (see [Managing Reporting entities](#managing-reporting-entities)).
6. If you want to perform a mapping of the **double materiality assessment** results before configuring the ESRS questionnaire: Retain the presetting for the **Double Materiality Assessments** option and click **Start materiality assessments** (see [Mapping Double Materiality Assessment Results](https://support.lucanet.com/en/documentation/esg-reporting/perform-dma.md) for subsequent steps). If you do not want to do a mapping of the double materiality assessment results, deactivate the option accordingly.
> **Warning:** **Notes**:
>
> - The **Double Materiality Assessments** option is only available if you choose **ESRS** as report guideline.
> - You can only perform the mapping of the double materiality assessment results if you have purchased the **Advanced** or **Professional** license package.
> - Once you start with the mapping of the double materiality assessment results, you can **no longer change** the report guideline.
> - In case you have deactivated the **Double Materiality Assessments** option and have started building the questionnaire, you can still return to the master data page and activate this option (see [Configuring the ESRS Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md)).
### Managing Reporting Entities
In the **Reporting entities assignment** area, you manage the reporting entities that are involved in the data collection process and **assign** users per reporting entity to provide data for the **ESRS data collection** and/or the **EU taxonomy**. The procedure depends on whether you have licensed Lucanet.Financial OLAP Server or whether you do not work with Lucanet.Financial OLAP Server:
### Procedure for users with access to Lucanet.Financial OLAP Server
If you have licensed Lucanet.Financial OLAP Server, you can access the reporting entities that were created in Lucanet.Financial OLAP Server for the assignment. Proceed as follows:
1. Click **Add first reporting entities**.
2. In the **Manage Reporting Entities** dialog, activate the check boxes in the **Assigned to ESG Reporting** column for the reporting entities that need to submit data for the ESG report. You can also use the **search box** to quickly find and assign specific reporting entities.
Options in the 'Manage Reporting Entities' dialog for users who use Lucanet.Financial OLAP Server
Click **Apply**.
3. In the **Reporting entities assignment** area, select the following for each reporting entity:
- One or more responsible **users** who will provide the data for the **ESRS data collection** and/or the **EU taxonomy** report.
- The **location** of the reporting entities. This information is required in order to collect data on [GHG emissions](https://support.lucanet.com/en/documentation/glossary.md#ghg-emissions).
> **Warning:** **Note**: You can only enter the location if you have purchased the **Advanced** or **Professional** license package.
### Procedure for users without access to Lucanet.Financial OLAP Server
If you have **not** licensed Lucanet.Financial OLAP Server, create the reporting entities in the master data administration as follows:
1. Click **Add first reporting entities**.
2. In the **Manage Reporting Entities** dialog, you have the following options:
- Enter the desired reporting entities by clicking **Add reporting entity** and entering the name in the **Reporting entity** column.
- **Search** for specific reporting entities in the table.
- Activate the check boxes in the **Assigned to ESG Reporting** column for reporting entities that are used in other ESG reports and automatically appear in the table. You can also activate the check box in the column header to activate all reporting entities that are listed.
- Edit or delete reporting entities.
Options in the 'Manage Reporting Entities' dialog for users who do not use Lucanet.Financial OLAP Server
Click **Apply**.
3. In the **Reporting entities assignment** area, select the following for each reporting entity:
- One or more responsible users who will provide the data for the **ESRS data collection** and/or the **EU taxonomy** report.
- The **location** of the reporting entities. This information is required to collect data on [GHG emissions](https://support.lucanet.com/en/documentation/glossary.md#ghg-emissions).
> **Warning:** **Note**: You can only enter the location if you have purchased the **Advanced** or **Professional** license package.
## Proceeding with the Next Step
After having entered all master data and managed the reporting entities, you can click **Go to questionnaire builder** to configure a customized ESRS, ESRS 2.0, or VSME questionnaire for your ESG Data Collectors (see [Configuring the ESRS or VSME Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md)).
> **Note:** **Note**: If you have activated the **Double Materiality Assessments** option, you can only proceed after all assigned reporting entities have submitted their double materiality assessment report. Subsequently, the master data page will be displayed as follows:
>
> the master data page with 'materiality assessments completed' status highlighted; report guideline and 'double materiality assessments' fields are greyed out and 'go to questionnaire builder' is enabled icon
> View of the master data page after DMA process has been completed
---
---
title: "Displaying Aggregated Responses During Data Collection"
description: "Once the data collection phase of an ESG report has started, you as an ESG Administrator are able to monitor the aggregated responses of all assigned reporting entities while the ESG report is collecting data."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/enhancements-for-aggregated-esg-reports
language: en
last_updated: 2026-09-25
---
# Displaying Aggregated Responses During Data Collection
## Overview
During the data collection phase of an ESG report, you as an **ESG Administrator** are able to monitor the aggregated responses of all assigned reporting entities.
## Navigating to Aggregated Responses
To open the aggregated data for a given ESG report, navigate to the **Report overview** tab in the **ESG Reports** workspace. Open the desired ESG report.
Opening an ESG report in the data collection phase
On the subsequent overview, click **Show aggregated responses**.
Showing aggregated data in the data collection phase
## Status Icons in Aggregated Responses
When viewing the aggregated responses for an ESG report during the data collection phase, **status icons** indicate the **completion status of each question** across all reporting entities:
| Status | Description |
|---------|---------|
| the eligible aligned icon | **Completed by all reporting entities**, i.e. all reporting entities have activated the **Mark as completed** check box for the question. |
| the in progress icon | **In progress**, i.e. one or more reporting entities have **not** activated the **Mark as completed** check box for the question. |
> **Note:** **Note**: **Formula-based KPIs** are displayed in this preview as well, with their formula, the values of the individual reporting entities, and the group value. They behave exactly as in the final aggregated report (see [Generating ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md)).
---
---
title: "ESG Reporting"
description: "Lucanet ESG Reporting meets all the requirements in the ESG report process, because it covers all non-financial risks and opportunities that can arise in connection with the daily activities of an enterprise. ESG Reporting complies with the ESRS provisions, the EU taxonomy, and the GHG protocol, and provides decentralized data collection with customized questionnaires. It can also be used to calculate GHG emissions."
source_url: https://support.lucanet.com/en/documentation/esg-reporting
language: en
last_updated: 2026-09-29
---
## ESG Reporting
With Lucanet ESG Reporting, you have a modern tool at your disposal to collect, analyze, and report your ESG relevant data.
- Trust in efficient and reliable data management as well as information analysis and reports in real time.
- Benefit from automated processes to minimize the time required to collect ESG data.
- Rely on templates that comply with the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), and [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) requirements and the [GHG Protocol](https://support.lucanet.com/en/documentation/glossary.md#ghg-protocol), and provide decentralized data collection with customized questionnaires as well as the possibility to collect and calculate [GHG emissions](https://support.lucanet.com/en/documentation/glossary.md#ghg-emissions).
User interface for Lucanet ESG Reporting
[Request demo](https://www.lucanet.com/en/request-demo/)
> **Note:** - You already use the Lucanet CFO Solution Platform and would like to use ESG Reporting as well? Get in touch with your Lucanet contact or get in touch with us via [Contact](https://www.lucanet.com/en/contact/).
> - You are not a Lucanet customer yet and would like more information on our solutions? Simply get in touch with us via [Contact](https://www.lucanet.com/en/contact/).
> **Tip:** Links for more information:
>
> - [Lucanet's software for integrated ESG reporting](https://www.lucanet.com/en/solutions/esg-sustainability-reporting-software/) [LucaNet's software for integrated ESG reporting](https://www.lucanet.com/de/cpm-software/esg-reporting-software/ "LucaNet's software for integrated ESG reporting")
> - [Spelling It Out: Your Ultimate Guide to ESG Reporting](https://www.lucanet.com/en/esg-reporting/)
## First Steps With ESG Reporting
Our instructions will help you get started with Lucanet ESG Reporting in next to no time:
- [All Steps at a Glance](https://support.lucanet.com/en/documentation/esg-reporting/process-description-esgrep.md)
- [Creating an ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md)
- [FAQs](https://support.lucanet.com/en/documentation/faqs/lucanet-esg-reporting.md)
---
---
title: "Exporting Data"
description: "As an ESG Administrator you can export data from your ESG reports in different formats: aggregated ESRS and VSME data as a CSV file, and EU Taxonomy data in Excel using standardized EU Annex II templates."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/export-data-esgrep
language: en
last_updated: 2026-09-28
---
# Exporting Data
## Overview
As an **ESG Administrator**, you have the option of exporting data from your ESG reports in different formats depending on the report type:
- **ESRS/VSME reports**: Export the aggregated **questionnaire data** as a CSV file and the aggregated **emission data** as an Excel file
- **EU Taxonomy reports**: Export aggregated data in Excel format using standardized EU Annex II templates
## Exporting ESRS or VSME Report Data
As an ESG Administrator, you can export the aggregated data of your ESRS or VSME report from the **Aggregated report** page. Two exports are available:
- **Export questionnaire data**: downloads all aggregated responses from your reporting entities as a **CSV file**.
- **Export emission data**: downloads the aggregated GHG footprint (emission) data as an **Excel (.xlsx) file**. This option is only available to **ESG Administrators**.
To export ESRS or VSME data:
1. Navigate to the **Aggregated report** page.
2. Click **Export** at the top right, then select **Export questionnaire data** or **Export emission data**.
'Export' menu on the 'Aggregated report' page
The file is generated and downloaded to your computer automatically.
> **Warning:** When the window narrows, the **Reopen for editing** button and the **Export** button merge into the **Actions** button. If necessary, click **Actions** to continue.
**Formula-Based KPIs in the CSV File**
If the questionnaire contains **formula-based KPIs** (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)), they are exported together with the answers. Each KPI is written as its own row — once per reporting entity and once for the aggregated value — and contains:
- The **calculated value** and the **unit** of the KPI, in the same columns as the answers to the other questions
- The **formula** in readable form, including the complete path of each input value
- The **state** of the KPI, which shows whether the value could be calculated
The existing columns of the CSV file are unchanged, so existing imports and evaluations of this file continue to work.
## Exporting EU Taxonomy Report Data
For **EU Taxonomy reports**, you can export data in a standardized **Excel format** that complies with EU Annex II reporting templates. This export includes:
- **Template I**: Summarized KPIs for Turnover, CapEx, and OpEx
- **Template II**: Detailed activity breakdowns for each KPI with environmental objectives
The exported Excel file is structured according to official EU regulations and is ready for import into **Lucanet Disclosure Management** for further processing and publication.
To export EU Taxonomy data:
1. Navigate to the **Reports and Activities** workspace in the **EU Taxonomy** functional area.
2. In the **Report overview**, navigate to the report to be exported.
3. Click the **Export** button on the right.
Button to export EU Taxonomy data
The export file is generated and downloaded to your computer automatically.
### Setup of the EU Taxonomy Export
The export of an EU Taxonomy report generates a single Excel file containing **four worksheets** based on the official EU Annex II templates:
The **Summary** worksheet, based on Template I, provides an overview of your organization's business activities that are aligned with the EU Taxonomy across all three key performance indicators **Turnover, CapEx, and OpEx** (see also [Collecting Financial Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/collect-financial-data.md)).
For each KPI, the template shows:
- **Total amounts** in your reporting currency
- Percentage of business activities that are **eligible for the EU Taxonomy**
- Percentage of business activities that are **aligned with the EU Taxonomy**
- Breakdown by the six environmental objectives, i.e., **Climate Change Mitigation**, **Climate Change Adaptation**, **Water**, **Circular Economy**, **Pollution Prevention**, **Biodiversity**
- Proportion of contribution types, i.e., **enabling** and **transitional** business activities
The **Turnover**, **CapEx**, and **OpEx** worksheets, based on Template II, each provide a detailed breakdown of individual business activities for the respective KPI:
- Business activity name and EU Taxonomy code
- Percentages of **taxonomy eligibility** and **taxonomy alignment**
- Contribution to each **environmental objective**
- Contribution type, i.e., **enabling** or **transitional** business activity
- Proportion of taxonomy-aligned business activities within taxonomy-eligible business activities
---
---
title: "Filling Out Report Questionnaire"
description: "The users that have been assigned as editors fill out the ESRS or VSME questionnaire and the Emissions Module entirely or only the parts that have been assigned to them. The data from the Emissions Module will be automatically copied into the ESRS or VSME questionnaire."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data
language: en
last_updated: 2026-09-28
---
# Filling Out Report Questionnaire
## Overview
The users that have been assigned as **editors** fill out the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire entirely or only the parts that have been assigned to them. For the data collection, users can attach files, and mark questions as completed to indicate the questions as ready for final review.
## Collecting Data in the ESRS, ESRS 2.0, or VSME Questionnaire
The [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), ESRS 2.0, or VSME questionnaire is split into four sections respectively and is displayed as follows, for example:
User interface of the ESRS questionnaire
> **Note:** **Note for editors with the user role 'ESG Data Collector'**:
>
> The scope of the categories or questions **visible** to you as an ESG Data Collector depends on two aspects:
>
> - The ESG Administrator can configure the questionnaire for the **reporting entity** to which you are assigned, i.e. assign this reporting entity to the whole questionnaire or to certain parts of it (see [Using the Questionnaire Builder](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder.md)).
> - During data collection, the ESG Administrator can assign **you to certain parts** of the questionnaire as editor or reviewer (see [Assigning Users as Editors or Reviewers](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/defining-access-esgrep.md)).
>
> For those reasons, you may not see the whole questionnaire, but only **parts** of it.
>
> **Note for editors with the user role 'ESG Administrator':**
>
> The status at the top of the data collection page indicates your access to the questionnaire:
>
> - **Read-only** — you have not been assigned as editor to any part of the questionnaire. All answer fields are disabled.
> - **Partially editable** — you have been assigned as editor to certain parts of the questionnaire. Only the questions assigned to you can be edited; the remaining questions are displayed as read-only.
### Providing Answers for Questionnaire
In the questionnaire, enter the data required for your reporting entity. While doing this, please note the following information:
- All the data you enter will be saved automatically.
- The ESG Administrator may have added additional guidance to support data collection, e.g. company-specific instructions, examples, or internal references. The additional guidance icon indicates that additional guidance has been added for a question (see *Viewing Guidance and Notes* below).
- You can use the side panel on the right of the screen to navigate between the individual categories and the questions relating to them (see *Navigating with the Side Panel* below).
- The questions in the questionnaire are available in English, French, and German and will be displayed in the selected user language accordingly. If you select any other language, the questions will be displayed in English.
- To get an overview about all users assigned to specific categories or other parts of the questionnaire as **editors** or **reviewers**, click the users icon .
- If you have marked a question as **Completed**, the question is displayed as read-only. If a reviewer is assigned, the question becomes available for the reviewer to review. If the reviewer has marked the question as **Reviewed**, you cannot provide answers for this element anymore (see also [Marking Questions as Completed](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data/.md#marking-questions-as-completed)).
- You can attach files or download attached files (see below).
> **Note:** **Note**: Besides the standard framework questions, the ESG Administrator may have added **custom questions** to a disclosure requirement (see [Adding Custom Questions](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md)). Custom questions appear inline together with the standard questions and are answered in the same way, depending on their question type.
### Working with Calculated KPIs
The ESG Administrator may also have added **formula-based KPIs** to the questionnaire (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)). A KPI is a **calculated value**: you do not answer it. It is calculated from the answers to other questions of the questionnaire and is updated automatically as soon as you save an answer that the formula uses.
You recognize a KPI by the formula icon next to its number and by the **KPI** badge. Below the number and the name, the formula is displayed in full, and below it the calculated value together with its unit:
A calculated KPI with its inputs displayed
For a KPI, note the following:
- The value field is **read-only**. Nobody can enter or overwrite a KPI value — neither an ESG Data Collector nor a reviewer nor the ESG Administrator.
- A KPI has no **Mark as completed** check box, and it is not reviewed separately. It follows the answers it is calculated from.
- Each input in the displayed formula is a **link**. Click it to jump directly to the question that provides that input.
- Click **Show responses** to open a table of all inputs with their current values and the resulting KPI value, so you can see how the value is calculated. Click **Hide responses** to close the table again.
- As long as an input is still missing, no value is calculated. Instead, the KPI indicates that it is still waiting for inputs, and names the questions concerned, so that a partially calculated and therefore misleading figure is never displayed.
- You only see a KPI if you have access to **all** the questions used in its formula.
### Viewing Guidance and Notes
For each question, you can open the guidance provided for it by the reporting framework and by your ESG Administrator.
1. Click the three-dot icon next to the question.
2. Select **Guidance and notes**.
The **Guidance and notes** panel opens on the right of the screen.
The 'Guidance and notes' panel of a question
3. Select the tab you need:
- **Guideline text**: The guideline text of the reporting framework or, for a custom question, the guideline text entered by the ESG Administrator
- **Additional guidance**: The company-specific instructions, examples, or internal references added by the ESG Administrator
4. Click the **Close** icon to close the panel.
> **Note:** **Note**: The panel is **read-only** for editors and reviewers. Only the ESG Administrator can change the additional guidance, in the questionnaire builder.
>
> If no additional guidance has been added for a question, the **Additional guidance** tab displays the following text:
>
> > Additional guidance has not been added to this element yet.
### Navigating with the Side Panel
The side panel on the right of the screen contains a **Search** box and the structure of the questionnaire, so that you can navigate to any category or question directly.
By default, the side panel is collapsed to a narrow bar. Click it to expand it. In the header of the expanded panel, the following options are available:
- **Keep side panel expanded** — pins the side panel so that it remains expanded while you work. The pinned state is remembered: when you reload the page or switch between the **ESRS** and **Emissions Module** tabs, the side panel is still expanded.
- **Collapse side panel** — collapses the side panel back to the narrow bar.
### Attaching Files
You can **attach files** to certain answers in the questionnaire. Uploading documents can provide supporting information and evidence for prior data input.
1. Navigate to the desired question, click the three-dot icon next to it and select **Attachments**.
The attachment area opens below the question.
2. Attach a file by **drag and drop** into the attachment area, or click **browse** and select the file.
Attaching a file to a question
Each attached file is displayed below the drop zone as a tile showing the **file name**, the **file size**, and the **date** on which it was attached.
When a question has one or more attachments, the question header displays an **attachment indicator** (e.g. **One attachment**). This lets you identify documented questions at a glance, without opening each one — which is especially helpful for review and audit tasks in larger reports.
Attachment indicator marking a question that has an attached file
### Downloading and Deleting Attached Files
After a file is attached, you can **download** it to your local device **at any time**, or delete it from the question.
1. Click the three-dot icon next to the question and select **Attachments**.
2. Hover over the tile of the file you need.
Two icons appear on the tile:
- The **download icon** the download icon — downloads the file to your local device.
- The **delete icon** the recycle bin icon — removes the file from the question.
> **Note:** **Note**: As a **reviewer**, you can only access the files attached to questions that are assigned to you.
### Marking Questions as Completed
After having provided an answer for a question, you can explicitly indicate that a question is ready for final review by activating the **Mark as completed** check box. The **Mark as completed** check box is displayed for each question in the questionnaire. The behavior of this check box depends on whether a **reviewer** has been assigned to the question:
- Question **without** an assigned reviewer: The question is displayed as read-only for the data collector.
- Question **with** an assigned reviewer: The question is displayed as read-only for the data collector and becomes available for the **reviewer** to review.
Proceed as follows to mark a question as completed:
1. Ensure that the question contains at least a partial answer.
2. Activate the **Mark as completed** check box for the question.
Once a question is completed, you can hover over its **Completed** icon to see who completed it and when. The tooltip displays **Completed by *user name*** and the **date and time**.
Tooltip on the 'Completed' icon showing who completed the question and when
> **Note:** **Notes**:
>
> - The **Mark as completed** check box is disabled if no answer has been provided yet. Its tooltip then reads *Content is required to mark answer as complete*.
> - If you need to change the answer to a question that has already been marked as completed, deactivate the **Mark as completed** check box for the question. If a reviewer has been assigned to the question, the question will no longer be available for review until you mark it as completed again.
> - When a question in the questionnaire displays data that is automatically copied from the **Emissions Module** and you mark this question as completed, the corresponding footprints in the Emissions Module become **read-only**. You cannot create or edit the related footprints until you deactivate the **Mark as completed** check box for the question.
> - The **Mark as completed** check box is only available in ESG reports that are created as of December 8, 2025.
> - **Formula-based KPIs** have no **Mark as completed** check box. They are calculated automatically and follow the answers they are based on (see *Working with Calculated KPIs* above).
---
---
title: "Filling Out the Emissions Module"
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/fill-out-emission-module
language: en
last_updated: 2026-09-29
---
# Filling Out the Emissions Module
## Overview
In addition to filling out the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire, the users that have been assigned as **editors** fill out the **Emissions Module** entirely or only the parts that have been assigned to them. To fill out the Emissions Module, the users **create footprints**, either manually or by importing consumption data created in MS Excel with the ESG Emission Agent.
The data from the Emissions Module will be automatically copied into the ESRS, ESRS 2.0, or VSME questionnaire.
> **Warning:** The Emissions Module is only available with the **Advanced** or **Professional** license package.
## Setup of the Emissions Module
Like the Greenhouse Gas Protocol ([GHG Protocol](https://support.lucanet.com/en/documentation/glossary.md#ghg-protocol)), the Emissions Module is split into three scopes: 1, 2, and 3. The three scopes represent the following three categories:
- **Scope 1**: all direct [GHG emissions](https://support.lucanet.com/en/documentation/glossary.md#ghg-emissions), e.g. natural gas or gasoline
- **Scope 2 - location-based**: all indirect GHG emissions resulting from the generation of power, e.g., electricity or district heating, based on the **average emissions intensity** of the grids where energy consumption occurs.
- **Scope 2 - market-based**: all indirect GHG emissions resulting from the generation of power, e.g., electricity or district heating, considering the **specific energy purchases** made by an organization.
- **Scope 3**: all indirect GHG emissions arising from consumption, e.g., waste disposal
The Emissions Module is displayed as follows, for example:
User interface of the Emissions Module
To enter emissions, you will need to create footprints for each emission (see next subheading).
## Import of Footprints from MS Excel Using ESG Emission Agent
You have two options to create footprints in the Emissions Module:
- The ESG Emission Agent allows you to **upload your existing emission activity data from MS Excel** and have Lucanet's ESG Emission Agent automatically convert each row into a structured GHG footprint entry — complete with the correct emission factor, scope classification, and CO₂ equivalent values. You can then review, edit, and approve the footprint suggestions before the footprints are committed to your Emissions Module.
- You can **create [single footprints manually](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/fill-out-emission-module/.md#manually-creating-a-footprint)** in the Emissions Module.
> **Tip:** For more information on how the ESG Emission Agent processes your data and generates footprint suggestions, see [Overview of the AI-Supported Import Process Using the ESG Emission Agent](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/ete-process-overview.md).
### Importing Footprint Data from MS Excel
#### Prerequisites for Using the ESG Emission Agent
To use the ESG Emission Agent, both of the following are required, in any order:
- A user with the **License Manager** role has activated the AI features of the Lucanet CFO Solution Platform in the **Lucanet licenses** workspace. For more information, see [Managing Lucanet Licenses | Activating and Deactivating the AI Features](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md#activating-and-deactivating-the-ai-features).
- You have requested access to the ESG Emission Agent by e-mailing [esg@lucanet.com](mailto:esg@lucanet.com).
> **Warning:** Before you start an import, please make sure to keep the Excel files **small**, **aggregate** where possible, and **split entries** across Excel worksheets.
#### Instructions
Proceed as follows to upload previously created consumption data and review the footprint suggestions to be added to the **Emissions Module**:
1. If necessary, navigate to the **Emissions Module** tab.
2. Click **Import data (Beta)** at the top right of the page.
Button to import consumption data from MS Excel
3. In the file selection dialog of your operating system, select your Excel file and confirm your selection. The import starts immediately.
> **Note:** - ESG Reporting will automatically start processing the Excel data and generate suggestions for footprints using the ESG Emission Agent for your review (see following subheading). This process may take some minutes.
> - While the file is being processed, the **Import data (Beta)** button is replaced by a **Cancel import** button. Click it to stop the import before any suggestions are generated.
> - Only XLS and XLSX files are accepted.
> **Tip:** You can also start the import directly from [Lucanet Lume](https://support.lucanet.com/en/documentation/lume.md). To do so, use the [ESG Emission Agent](https://support.lucanet.com/en/documentation/lume/agents.md) in Lume: Ask the ESG Emission Agent to upload your emissions and select the relevant report and reporting entity. The agent then takes you straight to the import in the **Emissions Module**, with the report and the reporting entity already selected. From there, you upload your Excel file as described above.
### Reviewing Suggested Footprints
> **Warning:** Disclaimer
>
> AI can make mistakes. Always review suggestions carefully to ensure accuracy.
After your Excel file has been processed, you can access an overview of the footprint suggestions generated by the ESG Emission Agent for your review. Click **Review imported footprints** to start your review.
Button to access footprint suggestions generated by the ESG Emission Agent
In the subsequently displayed dialog **Imported Footprints**, you can review each suggestion and decide whether to **accept, edit, or not accept** it.
If necessary, use the **filter** and/or **sort options** in the **Footprint**, **Scope assignment**, and **AI confidence score** columns to facilitate your review.
'Imported Footprints' dialog
The following actions are available:
**Accepting suggestions**
If a suggestion for a footprint has been correctly imported and mapped by the ESG Emission Agent, you can quickly accept it. Do one of the following:
- **Accept individual suggestions**: Activate the **Accept** check box for the footprint.
- **Accept all suggestions**: Activate the check box in the column header **Accept**.
Click **Confirm and create** to transform the accepted suggestions into footprints. The footprints will appear in the appropriate scope category and will be included in your ESG report.
> **Warning:** **Please note**: Only the suggestions whose **Accept** check box is activated are created. All remaining suggestions are discarded without further notice when you click **Confirm and create**. Make sure you have reviewed every suggestion before you confirm.
**Interrupting and resuming your review**
If you cannot complete your review in one go, click **Save as draft and close window** at the bottom left of the dialog. Your accepted suggestions and your edits are saved.
To resume, click **Review imported footprints** again. The dialog opens with your previously accepted suggestions still selected.
> **Note:** As soon as you activate the **Accept** check box for a suggestion, its **Scope assignment** and its pencil icon become read-only. Deactivate the check box again if you need to edit the suggestion.
**Editing suggestions**
If a suggestion needs adjustments, you can edit it before accepting. The following options are possible:
- In the **Footprints** column, you can click the pencil icon next to the suggestion to open the **detail view** and modify the footprint data, e.g. name, sector, or sub-sector.
- In the **Scope assignment** column, you can adjust the scope.
**Rejecting suggestions**
If a suggestion is irrelevant, incorrect, or a duplicate, you can reject it by deactivating the **Accept** check box. Rejected suggestions will not be created as footprints and will be discarded after clicking **Confirm and create**.
> **Note:** **Notes**:
>
> - Each suggested footprint displays the name and the row of the Excel sheet that contain the **original data** that the ESG Emission Agent used to create the suggested footprint.
> - The column **AI confidence score** displays the **expected accuracy** of the suggestions generated by the ESG Emission Agent as a percentage.
>
> The **overall confidence score** is calculated from **four weighted factors**:
>
> - Semantic match quality (40%)
> - Region match (30%)
> - Year match (15%)
> - Emission factor specificity (15%)
>
> Even with a high confidence score, always review the footprints generated by the ESG Emission Agent carefully. For more information on how the confidence score is calculated, see [Overview of the AI-Supported Import Process Using the ESG Emission Agent](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/ete-process-overview.md).
>
> - You can only have **one review in progress at a time**. You have to complete or cancel your current review before you can start a new Excel import.
> - You can **cancel the review** once the suggestions have been generated: Click **Cancel** in the **Imported Footprints** dialog and confirm with **Leave without saving**. Click **Continue reviewing** to return to your review instead.
> **Warning:** **Cancelling the review discards the entire import**: If you confirm with **Leave without saving**, all suggestions of the current import are discarded — including the ones you have already accepted and saved with **Save as draft and close window**. A saved draft is not a safeguard against cancelling.
>
> Footprints that you already created with **Confirm and create** in an earlier import are **not** affected and remain in the Emissions Module.
### Example of a Footprint Generated by the ESG Emission Agent
After having accepted and created footprints based on the suggestions generated by the ESG Emission Agent, you can display the footprints by navigating to the corresponding scope, e.g.:
Example of a footprint generated by the ESG Emission Agent
The ai generated icon is displayed next to each of the footprints generated by the ESG Emission Agent. To facilitate finding the **source information** that the footprint is based on, the row at the bottom of each footprint displays the Excel file and sheet that the footprint is based on.
## Manually Creating a Footprint
Proceed as follows to manually create a footprint in the **Emissions Module**:
1. If necessary, navigate to the **Emissions Module** tab.
2. Select the scope you require on the right-hand side of the screen.
3. Click **Create footprint**.
4. Enter a name for the footprint in the **Emission name** field.
5. If necessary, use any combination of the filters **Sector**, **Sub-sector**, **Source**, **Location**, **Year**, and **Unit type** to narrow down the emission factors shown in the **Activity type** table. To show only standard or custom emission factors, select the corresponding option in the **Emission factors** section.
Create footprint dialog
> **Note:** The filters **Sector**, **Sub-sector**, **Source**, **Location**, **Year**, and **Unit type** are all optional. The choice of whether to filter for **all** emission factors or only **standard or custom emission factors** is also optional. You can apply them in **any order**, and each filter shows only the options that still return at least one emission factor. You can change or remove any filter, and the **Activity type** table and the remaining filters update accordingly, without you having to re-enter the others.
6. Select the desired emission factor from the **Activity type** table.
The **Activity type** table shows emission factors that are relevant for the footprint you are creating (see the following info box). If necessary, use the **Search** field to find specific emission factors by entering relevant keywords (e.g., "Motorbike" or "R-170"). The table updates to show factors matching your keyword search and any filters you have applied.
7. Click **Create**.
> **Note:** **Scope- and Category-Aware Emission Factors**
>
> The **Activity type** table is automatically limited to the emission factors that are valid for the footprint you are creating:
>
> - For **Scope 1** and **Scope 2** footprints, the table shows all emission factors for that scope.
> - For **Scope 3** footprints, the table shows only the emission factors for the footprint's specific GHG Protocol category.
>
> You do not select the scope or category manually — the context is taken from the footprint you are working on. This also applies to the custom emission factors that carry a GHG scope and category definition (see [Creating Custom Emission Factors](https://support.lucanet.com/en/documentation/esg-reporting/creating-custom-emission-factors.md)).
>
> **Note:** **Decimal Precision of Emission Values**
>
> You can enter emission values with up to **4 decimal places** in the footprint input fields. When you leave a field, the value is formatted to exactly four decimal places (e.g. `1.5` becomes `1.5000`).
>
> Emission values displayed in the **summary panel** on the right and in the questionnaire tables that are populated from the **Emissions Module** are displayed with **2 decimal places**, in line with ESRS reporting requirements. The full precision is retained in the background.
> **Tip:** Tip for Keyword Search
>
> Use the keyword search to find specific emission factors that may not appear in the initial list. The keyword search helps you access emission factors beyond the first 500 results, making it easier to find specialized factors for your calculations.
> **Tip:** Tip for Using Custom Emission Factors
>
> If there are custom emission factors available, the custom emission factors will be displayed in the drop-down list **Activity type** as follows, for example:
>
> the custom factors example icon
> Example of a custom emission factor displayed when creating a footprint
>
> For more information, see [Creating Custom Emission Factors](https://support.lucanet.com/en/documentation/esg-reporting/creating-custom-emission-factors.md).
> **Note:** Once you have entered all the data for the Emissions Module, the data will be automatically copied into the **Environmental** section of the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) or VSME questionnaire, under **Metrics and Targets**.
> **Note:** When creating a footprint, the system automatically uses the latest data version of the [emission factor](https://support.lucanet.com/en/documentation/glossary.md#emission-factor) for GHG calculation. The data version used is stored and displayed for every footprint, so you can track at all times on which emission factor the calculation of the footprint is based:
>
> the a footprint is displayed. data version is highlighted in red. icon
> Data version displayed on a footprint
---
---
title: "General Functions in ESG Reporting"
description: "Depending on your user role, there are several general functions available to you in ESG Reporting, e.g. canceling ESG reports or displaying notes on a specific ESG report. This article describes the available functions depending on the user role."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/general-functions-esg
language: en
last_updated: 2026-05-01
---
# General Functions in ESG Reporting
## Overview
Depending on your user role, there are several general functions available to you in ESG Reporting, e.g. canceling ESG reports or displaying notes on a specific ESG report. This article describes the available functions depending on the user role.
## Functions for ESG Administrators
As an ESG Administrator, you can access the **ESG Reports** and **Data Collection** workspaces and do the following:
#### Create ESG report
In the **ESG Reports** workspace, you can create new ESG reports (see also [Creating an ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md)).
#### Access ESG reports and approve or reject submitted data for ESG reports
You can **access** the data submitted by the reporting entities for an ESG report by
- Clicking the desired ESG report in the **ESG Reports** workspace and then clicking the reporting entity to view the individual data
- Navigating to the desired ESG report in the **Data Collection** workspace and clicking the reporting entity to view the individual data
You can **approve** or **reject** the data submitted by the reporting entities for an ESG report by
- Selecting the desired option directly in the data collection page of a reporting entity
- Navigating to the desired ESG report in the **ESG Reports** or **Data Collection** workspace and clicking the three-dot icon on the right side of the table to select the desired option from the context menu
Options to access, approve, or reject an ESG report in the 'ESG Reports' workspace
#### Filter ESG reports and [Double Materiality Assessment](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment) reports
You can **filter** the list of ESG reports or double materiality assessment reports. Click the filter icon in the respective columns to facilitate the search as follows:
- In the **ESG Reports** workspace, you can filter by name and status, in the **ESRS Data Collection** workspace you can filter by name only.
- In the **Double Materiality Assessments** workspace, you can filter by name and date of modification.
Filter options in the 'ESG Reports' workspace
#### Cancel ESG reports
You can **cancel** ESG reports, i.e. any ESG report that has not yet reached **Data aggregation** status. This is useful if errors are discovered, for example. Canceled reports are listed separately.
To cancel an ESG report, navigate to the ESG report in the **ESG Reports** overview that you want to cancel, click the three-dot icon, and select **Cancel** from the context menu.
Canceling an ESG Report
#### Reopen aggregated ESG reports
You can can **reopen** an aggregated ESG report to collect updated values from the assigned reporting entities (see [Reopening an Aggregated ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/reopening-aggregated-esg-reports.md)).
#### Restore canceled ESG reports
You can **restore** canceled ESG reports, allowing you to resume work from the point at which the ESG report was canceled.
To restore a canceled ESG report, navigate to the **ESG Reports** or **Data Collection** workspace and open the **Canceled reports** tab. Click the three-dot icon and select **Restore** from the context menu.
Restoring a canceled ESG report
#### Open canceled ESG reports
You can **open** canceled ESG reports at the last status of the report at any time.
To open a canceled ESG report, navigate to the **ESG Reports** or **Data Collection** workspace and open the **Canceled Reports** tab. Open any given ESG report by clicking the report name.
Opening a canceled ESG report
#### Display notes
You can display notes on an ESG report that were created when data for an ESG report were submitted, approved, or rejected. You have two options to display notes:
- Click **Show notes** on the data collection page of a reporting entity.
- Navigate to the desired ESG report in the **ESG Reports** or **Data Collection** workspace and click the three-dot icon on the right side of the table to select **Show notes** from the context menu.
Displaying notes in the 'ESG Reports' workspace
#### Duplicate ESG reports
As an **ESG Administrator**, you can **duplicate** a report, allowing you to work with existing data from the original ESG report in a separate ESG report (see also [Working with Duplicated ESG Reports](https://support.lucanet.com/en/documentation/esg-reporting/duplicate-report.md) to learn more about how to duplicate an ESG report and work with duplicated ESG reports).
Duplicating an ESG Report
## Functions for ESG Data Collectors
As an ESG Data Collector, you can access the **Data Collection** and **[Double Materiality Assessments](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment)** workspaces and do the following:
#### Access ESG report or double materiality assessment report
You can access the ESG report (see [Editing Data](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data.md)) and the double materiality assessment report (see [Performing Double Materiality Assessment](https://support.lucanet.com/en/documentation/esg-reporting/perform-dma.md)) to enter data for your assigned reporting entity.
#### Open canceled ESG reports
You can open canceled ESG reports at the last status of the report at any time.
To open a canceled ESG report, navigate to the **Canceled Reports** tab in the **ESRS Data Collection** workspace. Open any given ESG report by clicking the report name.
Opening canceled ESG report as Data Collector
#### Display notes
You can display notes on an ESG report that were created when data for an ESG report were submitted, approved, or rejected. Do one of the following:
- Click **Show notes** on the data collection page of your assigned reporting entity
- Navigate to the desired ESG report in the **ESRS Data Collection** workspace and click the three-dot icon on the right side of the table to select **Show notes** from the context menu.
Displaying notes in the 'Data Collection' workspace
---
---
title: "Generating ESG Report"
description: "As an ESG Administrator, once you have approved the data submitted by all your reporting entities for an ESG report, you can generate the ESG report containing the individual reporting data for the assigned reporting entities and the aggregated numerical data. The aggregated data are also prepared for the import into the Lucanet Disclosure Management solution for further processing."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep
language: en
last_updated: 2026-09-24
---
# Generating ESG Report
## Overview
As an **ESG Administrator**, once you have approved the data submitted by all your reporting entities for an ESG report, you can generate the ESG report containing the individual reporting data for the assigned reporting entities and the aggregated numerical data. The aggregated data are also prepared for the import into the [**Lucanet Disclosure Management**](https://support.lucanet.com/en/documentation/disclosure-management.md) solution for further processing _._
## Generating ESG Report
To generate the ESG report, navigate to the **Data Collection** page of your report and click **Next**.
Option to generate ESG report
The aggregated data are prepared for import into **Lucanet Disclosure Management**.
You can now also view the aggregated ESG report.
### Viewing Responses Depending on Element Type
Depending on the element type, you have the following options to view detailed responses:
**In general**, you can use **Show responses** to view which reporting entity has provided which response for every question in the questionnaire:
Option to show responses for each reporting entity
For responses in the form of **radio buttons**, you can click **Show explanation** to access the explanation of the data collectors for their answer.
For responses provided in the form of **data in tables**, a table with the aggregated data is directly displayed. By double-clicking a cell with aggregated values, you can drill down to the individual values entered by each reporting entity:
Aggregated responses displayed in a table
Drill-down to data entered by individual reporting entities
> **Note:** Any **custom questions** that the ESG Administrator added to the questionnaire (see [Adding Custom Questions](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md)) are marked with a **Custom** badge in the aggregated report. You can show and drill down into their responses in the same way as for standard questions.
### Viewing Formula-Based KPIs
**Formula-based KPIs** (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)) are marked with **KPI** in the aggregated report and are displayed with their complete formula. As KPIs are calculated, they are read-only.
Click **Show responses** to see how the KPI is composed. The table lists every reporting entity with its own KPI value, followed by the **Group KPI** row:
KPI values per reporting entity and the group value
The group value is **not** the sum or the average of the individual KPI values. Instead, the input values are first aggregated across all reporting entities, and the formula is then applied to these aggregated values.
> **Note:** You are able to view and access aggregated responses while the data collection phase is still ongoing. For a detailed information, see [Displaying Aggregated Responses During Data Collection](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/enhancements-for-aggregated-esg-reports.md)
---
---
title: "Mapping Double Materiality Assessment Results"
description: "Double materiality assessments (DMA) provide a foundational analysis of your organization's impact on sustainability and consist of impact materiality and financial materiality. By combining these two factors, it is possible to assess which sustainability risks and opportunities are material for your organization and, thus, should be included in your ESG report.\n\nAs an ESG Data Collector, you can specify in the DMA report which sustainability topics are relevant for your reporting entity and submit the report. This information will be used to determine the part of the ESRS questionnaire that your organization has to report on."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/perform-dma
language: en
last_updated: 2026-05-01
---
# Mapping Double Materiality Assessment Results
## Overview
[Double materiality assessments](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment) (**DMA**) provide a foundational analysis of your organization's impact on sustainability and consist of [impact materiality](https://support.lucanet.com/en/documentation/glossary.md#impact-materiality) and [financial materiality](https://support.lucanet.com/en/documentation/glossary.md#financial-materiality). By combining these two factors, it is possible to assess which sustainability risks and opportunities are material for your organization and, thus, should be included in your ESG report.
As an **ESG Data Collector**, you can map the results of your DMA to the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) questionnaire by specifying in a DMA report which sustainability topics are **relevant** for your reporting entity, and submit the report. This information will be used to determine the part of the ESRS questionnaire that your organization has to report on.
## Prerequisites
To specify your DMA results in **ESG Reporting** in a DMA report, please ensure the following:
- You have purchased the **Advanced** or **Professional** license package.
- The users that will configure the DMA report are licensed for the user role **ESG Data Collector** or **ESG Administrator** (see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md)) and are assigned in the master data (see [Creating an ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md)).
## Navigating to the DMA Report
To start the DMA report for your reporting entity, navigate to the **Double Materiality Assessments** workspace and click the reporting entity that you have been assigned to:
View of the 'Double Materiality Assessment' workspace for ESG Administrators
## Configuring the DMA Report
The DMA report for a reporting entity is a list of sustainability topics containing various **standards**, **sections**, and **disclosure requirements** from the ESRS questionnaire. In the DMA report, these elements correspond to **topics**, **sub-topics**, and **sub-sub-topics**. A DMA report is displayed as follows, for example:
Structure of a DMA report
Activate the check boxes in the columns **Impact** and **Financial** to specify whether one or more sustainability topics have an impact materiality, a financial materiality, or both, as per your DMA.
The following icons are used:
| Icon | Description |
|---------|---------|
| the fully assigned icon | **In the case of a topic:** The topic including its sub-topics and sub-sub-topics has an impact materiality or financial materiality. **In the case of a sub-topic:** The sub-topic including its sub-sub-topic has an impact materiality or financial materiality. **In the case of a sub-sub-topic:** The sub-sub-topic has an impact materiality or financial materiality. |
| the partially assigned icon | **In the case of a topic:** The topic has at least one sub-topic or sub-sub-topic with an impact materiality or financial materiality and at least one sub-topic or sub-sub-topic without an impact materiality or financial materiality. **In the case of a sub-topic:** The sub-topic has at least one sub-sub-topic with an impact materiality or financial materiality and at least one sub-sub-topic without an impact materiality or financial materiality. |
| the not assigned icon | The topic, sub-topic, or sub-sub-topic does not have an impact materiality or financial materiality. |
## Submitting the DMA Report
Once you have completed the DMA report for your reporting entity, click the **Submit** button on the top right-hand side of the DMA report page.
You can also navigate to the DMA report in the **Double Materiality Assessments** workspace and select **Submit** from the context menu:
Submit DMA report in the Double Materiality Assessment workspace
> **Note:** After the DMA reports have been submitted by **all assigned reporting entities**, the ESRS questionnaire can be configured. The scope of the ESRS questionnaire and the assignment of reporting entities to specific questionnaire parts will **automatically be adapted** according to the information obtained from the DMA reports (see [Configuring the ESRS or VSME Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md)).
## Working with DMA on Duplicate Reports
When duplicating an existing ESG report, the setting for the **Double Materiality Assessments** option in the master data as well as existing data for a DMA result mapping are retained and copied into the duplicate. You can choose to activate or deactivate the **Double Materiality Assessments** option.
In case the original report already contained data on DMA result mappings, you can continue working with the same data in the duplicate report. Submitted DMA reports will affect the ESRS questionnaire in the duplicate report accordingly.
---
---
title: "Overview of the AI-Supported Import Process Using the ESG Emission Agent"
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/ete-process-overview
language: en
last_updated: 2026-09-29
---
# Overview of the AI-Supported Import Process Using the ESG Emission Agent
## Overview
With the AI-supported import of consumption data, you can upload your existing emission activity data from MS Excel and have Lucanet's ESG Emission Agent automatically convert each row into a structured GHG footprint suggestion — complete with the correct emission factor, scope classification, and CO₂ equivalent values (see also [Filling Out the Emissions Module](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/fill-out-emission-module.md)).
The following sections provide an overview of the **process**, how the ESG Emission Agent **determines certain values** to be included in the footprint suggestions, and an explanation of the **AI confidence levels** displayed.
> **Note:** To use the ESG Emission Agent, both of the following are required, in any order:
>
> - A user with the **License Manager** role has activated the AI features of the Lucanet CFO Solution Platform in the **Lucanet licenses** workspace. For more information, see [Managing Lucanet Licenses | Activating and Deactivating the AI Features](https://support.lucanet.com/en/documentation/administration/platform-management/licenses.md#activating-and-deactivating-the-ai-features).
> - You have requested access to the ESG Emission Agent by e-mailing [esg@lucanet.com](mailto:esg@lucanet.com).
## Process Overview
You upload one MS Excel file at a time. The ESG Emission Agent processes the file and presents you with a set of suggested footprints for review. You then review, adjust where necessary, and accept the footprint suggestions from the current file before you can upload the next one. This ensures data quality and gives you full control over every footprint before it is included in your GHG dataset. The ESG Emission Agent processes all relevant Excel sheets within a single uploaded file. It reads each Excel sheet independently and skips rows that represent totals or aggregated summaries.
## Traceability
Every suggested footprint is linked back to its exact origin in your Excel file, i.e., you can see both the **sheet name** and the **original row number** from your MS Excel file. This makes it straightforward to cross-reference the ESG Emission Agent's output with your source data, verify the numbers, and trace any footprint back to where it came from.
## Individual Steps of the Process Using the ESG Emission Agent
When you upload your Excel file, the ESG Emission Agent works through a structured, multi-step process to transform each activity into a footprint suggestion.
1. **Retrieve valid unit types** Before doing anything else, the ESG Emission Agent fetches the complete list of valid unit types from the emission factor database (e.g., **Volume**, **Distance**, **Weight**, **Money**, **Energy**). This is a prerequisite step that ensures every subsequent search uses only valid, recognized measurement categories.
2. **Read and interpret the file content** The ESG Emission Agent reads each row across all relevant Excel sheets. For each activity it identifies:
- The **activity type** (e.g., fuel combustion, electricity, freight, business travel)
- The **geographic location** (country or region)
- The **unit of measurement** (liters, km, kWh, EUR, etc.)
- The **quantity**, interpreted in the locale-specific number format of the source data
- The **reporting year** — detected from the file content or sheet context
- The **original Excel row number**, which is appended to every row in the processed data for full traceability
The ESG Emission Agent also **automatically detects the report year and default region** from the file. This data is used as a reference for all subsequent emission factor searches: The **reporting year** determines which factor vintages are valid, and the **detected region** anchors the geographic search.
3. **Search for emission factors using a 4-phase strategy** For each activity, the ESG Emission Agent conducts a structured search within our offered databases and your custom emission factors:
- **Phase 1 — Discovery:** A broad search with minimal constraints (activity keywords and unit type, no region filter) to understand what data is available and learn the naming patterns, available regions, and data sources in the database.
- **Phase 2 — Region grouping:** Based on the detected country, the ESG Emission Agent builds geographic tiers — for example, for a German activity: exact Germany → German-speaking cluster (DE, AT, CH) → Central Europe → EU-wide → Global.
- **Phase 3 — Multi-region search:** The ESG Emission Agent searches across a geographic cluster in a single query, which is more efficient and automatically provides built-in geographic fallbacks.
- **Phase 4 — Progressive refinement:** If results are insufficient, the ESG Emission Agent iterates through broader tiers until suitable candidates are found. If too many results are returned (more than 200), the ESG Emission Agent adds more specific keywords or switches to a single-region search to reduce ambiguity.
4. **Select the best-matching emission factor** When multiple potential factors are found, the ESG Emission Agent applies a clear priority order:
1. **Correct unit type** — Must match the activity's measurement category
2. **Activity match** — The emission factor description must align with the activity
3. **Geographic match** — Exact country preferred, then geographic cluster, then continent, then global
4. **Most recent year** — The most up-to-date factor is preferred, but the factor year must not be newer than the reporting year (future data is methodologically invalid for historical reporting)
5. **Specific unit** — The exact unit (e.g., liters vs. cubic meters) must match
5. **Map and structure the footprint** The selected emission factor is mapped to:
- The correct **GHG scope** (Scope 1, 2, or 3)
- The appropriate **category** (e.g., **Mobile Combustion**, **Business Travel**, **Electricity**, **Purchase of Goods and Services**)
- The correct **parameter structure** — including handling of compound unit types (e.g., weight over distance for freight, passengers over distance for flights). For compound types where both values must be present and cannot be assumed, the ESG Emission Agent flags the row as incomplete rather than inventing a missing value.
## AI Confidence Levels
For every suggested footprint, the ESG Emission Agent calculates a **confidence score** that tells you how certain it is about its generated data. This helps you focus your review on the entries that need the most attention. The overall confidence score is calculated from four weighted factors:
#### Semantic match quality
- Weighted with **40%**
- Measures how closely your source text matches the emission factor's activity description:
- **90–100%** — Exact keyword match (e.g., **diesel** maps directly to a diesel emission factor)
- **70–85%** — Synonym or related term match (e.g., **fuel oil** mapped to **diesel**)
- **50–70%** — Category-level match only (e.g., **vehicle fuel** mapped to **diesel**)
- **30–50%** — Inferred from context (e.g., **fleet costs** used to infer **diesel**)
- **0–30%** — No clear match; a fallback factor was used
#### Region match
- Weighted with **30%**
- Measures how precisely the emission factor's geography matches your data's location
- **100%** — Exact country match (e.g., a German office matched to a German emission factor)
- **80–90%** — Country within a broader region (e.g., Germany matched to a DACH factor), or no region detected but your default region was used
- **70–80%** — Continent-level match (e.g., Germany matched to an EU/Europe factor)
- **50–70%** — No regional overlap; a global factor was used as the best available match
- **20–40%** — No region detected at all; a global average was applied
- **0–20%** — Geographic mismatch (e.g., a German activity matched to an Australian factor)
#### Year match
- Weighted with **15%**
- Measures how current the emission factor data is relative to your reporting year
- **100%** — The emission factor year matches your reporting year exactly
- **80–90%** — The emission factor is 1–5 years older than your reporting year
- **60–80%** — The emission factor is 6–20 years older
- **0%** — The emission factor is newer than your reporting year (methodologically invalid; future data cannot be used for historical reporting)
#### Emission factor specificity
- Weighted with **15%**
- Measures how many potential factors the ESG Emission Agent had to choose from (fewer = more confident)
- **100%** — Only 1 matching factor found (unambiguous)
- **70%** — 2–10 matching factors (reasonable disambiguation)
- **50%** — More than 10 matching factors (high ambiguity)
> **Note:** **Formula:** confidence = (semantic × 0.40) + (region × 0.30) + (year × 0.15) + (specificity × 0.15)
### Confidence Tiers
The combined score is displayed as a color-coded indicator for each suggested footprint:
#### Green
- High confidence
- Score ≥ 80%
#### Yellow
- Review recommended
- Score = 50–79%
#### Red
- Needs attention
- Score < 50%
> **Warning:** **Important Notes**
>
> - For compound activity types (e.g., freight measured in weight over distance), the ESG Emission Agent requires both values to be available in your source data. If data is incomplete, the ESG Emission Agent will flag the row rather than invent a missing value.
>
> - Total (aggregated) rows in your Excel file are automatically excluded from processing.
>
> - Only one file can be processed at a time. The next upload only becomes available once the current file's proposals have been reviewed and accepted.
---
---
title: "Reopening an ESG Report"
description: "Even after the Data aggregation step has been finalized, an ESG Administrator can reopen the aggregated ESG report. This might be necessary to collect updated values from the assigned reporting entities."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/reopening-aggregated-esg-reports
language: en
last_updated: 2026-05-01
---
# Reopening an ESG Report
## Overview
Even after the **Data collection** or **Data aggregation** step has been finalized, an **ESG Administrator** can reopen the aggregated ESG report. This might be necessary to collect updated values from the assigned reporting entities.
## Reopening the ESG Report for Individual Reporting Entities
After having approved the report data of the assigned reporting entities of an ESG report, an **ESG Administrator** can reopen the data collection page for **specific reporting entities**. The users assigned as ESG Data Collectors can then adjust or add further data for their reporting entity.
To reopen the data collection page for a **single reporting entity**:
1. Navigate to the required ESG report and to the **Data Collection** page of the reporting entity which is to be given access again to their data collection page.
2. Click the three-dot menu at the right.
3. Select **Reopen** from the context menu.
Button to reopen the data collection for a single reporting entity
## Reopening the Whole ESG Report
After the **Data aggregation** step has been finalized, an **ESG Administrator** can reopen the whole ESG report to collect updated values from the assigned reporting entities.
An aggregated report can be reopened from:
- The **Aggregated report** page
Reopening an aggregated report from the 'Aggregated report' page
- The report overview in the **ESG Reports** workspace
Reopening an aggregated report from the 'ESG Reports' workspace
- The **Data Collection** page
Reopening an aggregated report from the 'Data Collection' page
> **Warning:** When the window for the **Aggregated report** page narrows, the **Reopen for editing** button and the Download icon merge into the **Actions** button. If necessary, click **Actions** to continue.
When an approved or aggregated ESG report is reopened, its status, as well as the report statuses of the individual reporting entities, will be set to **In Progress**. ESG Data Collectors can then edit the values in the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire and resubmit the ESG report.
In a reopened ESG report, the ESG Administrator can also edit the **additional guidance** for questions in the Questionnaire Builder again.
---
---
title: "Reviewing Data"
description: "The users that have been assigned as reviewers to an ESG report can start reviewing data as soon as data have been collected."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/reviewing-data
language: en
last_updated: 2026-09-21
---
# Reviewing Data
## Overview
The users that have been assigned as **reviewers** to an ESG report can start reviewing data as soon as data have been collected.
## Access to ESG Report
The type of access to the ESG report depends on your user role and whether you have been assigned as an editor and/or a reviewer. A status message at the top of the data collection page indicates the type of access:
Status 'Partially editable' in the header
### Access for ESG Administrators
If you, as an ESG Administrator, have been assigned as a reviewer and/or an editor to certain parts of the questionnaire, one of the following status messages will be displayed:
| Status message | Description |
|---------|---------|
| Read-only | The user is exclusively assigned as a reviewer and has read access to the whole questionnaire. |
| Partially editable | The user is partially assigned as a reviewer and partially assigned as an editor, i.e. they can only edit the parts of the questionnaire to which they have been assigned as editor, but have read access to the rest. |
### Access for ESG Data Collectors
After the questionnaire has been configured, the ESG Administrator can assign you as an ESG Data Collector to certain parts of the questionnaire as editor/and or reviewer (see [Assigning Users as Editors or Reviewers](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/defining-access-esgrep.md)). For this reason, you may not see the whole questionnaire, but only parts of it. A status message at the top of the data collection page indicates the type of access:
| Status message | Description |
|---------|---------|
| Read-only | The user is exclusively assigned as a reviewer to a part of the questionnaire and only has read access to the part that they have been assigned to. |
| Partially editable | The user is partially assigned as a reviewer and partially assigned as an editor. The user only has read access to the parts for which they are assigned as reviewer and has write access to the part that they have to edit. |
## Prerequisites for Reviewing
Before you can review a question, the ESG Data Collector must have activated the **Mark as completed** check box for the question.
> **Note:** **Note**: If the ESG Data Collector deactivates the **Mark as completed** check box after you have started the review, the question is no longer available for review until the ESG Data Collector marks it as completed again.
## Reviewing an Element of the Questionnaire
As soon as an answer has been provided for a standard, section, disclosure requirement, or question, and the data collector has **marked the question as completed**, you can review the data. To mark the element as reviewed, activate the **Reviewed** check box at the top right side of the element:
Mark an answer of a question as reviewed
If necessary, deactivate the check box to revoke the review.
> **Note:** **Note**: The ESG Administrator may have added **additional guidance** to support data collection, e.g. company-specific instructions, examples, or internal references. The additional guidance icon indicates that additional guidance has been added for a question.
>
> When the ESG Administrator **adds, changes, or deletes** additional guidance for a question, the status of that question is reset for the assigned reporting entities — including questions that have **not yet been answered**. This ensures that:
>
> - unanswered questions are presented with the updated guidance from the start, and
> - previously answered questions need to be edited and reviewed again so that the answer can be reconfirmed against the updated guidance.
> **Note:** **Note**: **Formula-based KPIs** are visible in the review context as well, but they are not reviewed separately. A KPI is calculated from the answers it refers to and stays read-only; it has no review action of its own (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)).
---
---
title: "Setting Up CFP Permissions for ESG Administrators"
source_url: https://support.lucanet.com/en/documentation/esg-reporting/user-roles-esgrep/setting-up-cfp-read-rights-esg-admins
language: en
last_updated: 2026-09-01
---
# Setting Up CFP Permissions for ESG Administrators
## Overview
This guide explains how to configure the rights of an ESG user with the **Administrator** user role who also needs access to data in the **Consolidation & Financial Planning (CFP)** solution. ESG Administrators need read permissions on CFP master data so that the organization elements defined in CFP are visible in the ESG master data.
## Setup
Configure the user or users with the **ESG Administrator** user role as follows:
1. Open Lucanet.Financial Client and navigate to the **Users** workspace.
2. Assign the [Observer role for CFP](#assigning-the-observer-role-for-cfp) to the user.
3. Set the required [read and access permissions](#setting-read-and-access-permissions).
4. **Save** the configuration.
### Assigning the Observer Role for CFP
1. In the tree view, click the relevant user.
2. In the **General** section, activate the **User has access to the data model** check box, if necessary.
3. In the drop-down list, select the **Observer** role. The selected role is displayed as follows:
Selecting the 'Observer' role for data model access
### Setting Read and Access Permissions
1. In the **Permissions** tab, navigate to the **Data access** folder and open the **Organization elements** subfolder.
2. Enable the **Read** permission for **Organization elements**. The enabled permission is displayed as follows:
Enabling the 'Read' permission for organization elements in the 'Data access' folder
3. Switch to the **Access** tab and activate the **Lucanet.Financial Client and Lucanet.Excel Add-In** check box. The activated access rights are displayed as follows:
Enabling access via Lucanet.Financial Client and Lucanet.Excel Add-In
## Result
After the setup, CFP appears as an enabled solution in the main menu. The ESG Administrator sees only the relevant master data; financial figures are not visible.
---
---
title: "Starting Data Collection"
description: "Once you have configured the ESRS, ESRS 2.0, or VSME questionnaire, you can release the ESG report for data collection."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/starting-data-collection
language: en
last_updated: 2026-05-01
---
# Starting Data Collection
## Overview
Once you have configured the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire, you can release the ESG report for data collection.
Click **Start data collection** in the questionnaire builder to begin this process.
Start data collection
---
---
title: "Status Update per Reporting Entity"
description: "For each reporting entity, the Reports and Activities workspace provides a page with an assessment overview of:\nMinimum safeguards\nTaxonomy eligibility\nTaxonomy alignment\nFinancial data status for every business activity\nIn case the assessment of the minimum safeguard criteria is still in progress, you can directly access the corresponding questionnaire via link."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/status-update
language: en
last_updated: 2026-05-01
---
# Status Update per Reporting Entity
## Overview
For each reporting entity, the **Reports and Activities** workspace provides a page with an assessment overview of:
- Minimum safeguards
- Taxonomy eligibility
- Taxonomy alignment
- Financial data status for every business activity
In case the assessment of the minimum safeguard criteria is still in progress, you can directly access the corresponding questionnaire via link.
## Status Overview
After clicking the desired reporting entity in the **Reports and Activities** workspace, the status overview is displayed as follows, for example:
Status information on reporting entity
| No. | Description |
|---------|---------|
| 1 | Assessment of **minimum safeguards** |
| 2 | Option to display the minimum safeguards questionnaire for this reporting entity |
| 3 | Status of assessment for taxonomy eligibility |
| 4 | Applicable environmental goals for taxonomy eligibility. Their color indicates the status: **Green**: The business activity is **eligible** for this environmental goal. **Gray**: The business activity is **not eligible** for this environmental goal. **Yellow**: The assessment is still **in progress**. Hover over an abbreviation to see the full name of the environmental goal. |
| 5 | Status of assessment for taxonomy alignment: **Aligned**: Minimum safeguards have been met, and the activated goals in the SCC and DNSH questionnaire all have the status **Compliant** or **Not applicable**. **Not aligned**: Minimum safeguards have not been met, or at least one of the activated goals in the SCC and DNSH questionnaires have the status **Not compliant**. **In progress**: Assessment of the minimum safeguards criteria has not yet begun or is still in progress, or at least one of the activated goals in the SCC and DNSH questionnaires has the status **In progress**. |
| 6 | Applicable environmental goals for taxonomy alignment. Their color indicates the status: **Green**: The business activity is **aligned** for this environmental goal. **Gray**: The business activity is **not aligned** for this environmental goal. **Yellow**: The assessment is still **in progress**. Hover over an abbreviation to see the full name of the environmental goal. |
| 7 | Status of collection of financial data: **In progress**: the collection of financial data is ongoing. **Completed**: the baseline values for the reporting entity and the financial data for the business activity have been collected. **-**: there is no financial data, e.g. because the business activity is not eligible for the EU Taxonomy. |
| 8 | Three-dot menu with options to **Delete** the business activity or use **Go to financial data** to directly navigate to the detailed financial data page of the corresponding reporting entity. |
---
---
title: "Structure of the Report Questionnaire"
description: "The ESRS, ESRS 2.0, or VSME questionnaire consists of several elements that are displayed in a tree structure and offers you various functionalities."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/structure-questionnaire
language: en
last_updated: 2026-05-01
---
# Structure of the Report Questionnaire
## Overview
The [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire consists of several elements that are displayed in a tree structure and offers you various functionalities. Before starting to configure your questionnaire, familiarize yourself with the setup and general functions and, in case of working with an ESRS questionnaire, with the possible impact of mapping the results of a [double materiality assessment](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment) (DMA) on the ESRS questionnaire structure.
## General Structure
The ESRS, ESRS 2.0, or VSME questionnaire is displayed in a tree structure to make it easier to recognize which elements belong to which superordinate element and the current position of the user in the hierarchy. The questionnaire consists of the following hierarchy elements: categories, standards, sections, disclosure requirements, and questions:
Hierarchy of the ESRS questionnaire
The questionnaires include the following:
- The **ESRS** questionnaire includes the categories **General Disclosures**, **Environmental**, **Social**, and **Governance** and can be displayed in English, German, or French.
- The **ESRS 2.0** questionnaire provides the same questionnaire structure as the standard ESRS hierarchy, i.e., **General Disclosures**, **Environmental**, **Social**, and **Governance**. However, compared to ESRS, the ESRS 2.0 structure is shorter and less complex.
- The **VSME** questionnaire includes the categories **General Information**, **Environmental Metrics**, **Social Metrics**, and **Governance Metrics** and can be displayed in English, German, French, Italian, Spanish, Polish, or Dutch.
Each category provides access to the corresponding ESRS or VSME **standards** and the **sections**, **disclosure requirements**, and **questions** the standard contains.
## General Functions
Using the context menu or information icons on the right-hand side, you can do the following:
- For **categories**: Click the three-dot icon to show or hide all subordinate elements.
- For **disclosure requirements**: Click the information icon to view the original text of the guideline the disclosure requirement is based on.
- For **questions**: Click the three-dot icon to display a preview of how the question will be displayed to the ESG Data Collector(s) or to view the original text of the guideline the question is based on.
Guideline text for a question from the ESRS questionnaire
## Impact of Mapping DMA Results on Structure
If you, as an ESG Administrator, have chosen **ESRS** as report guideline and activated the option **Double materiality assessment** when creating the ESG report, you will automatically have access to a pre-configured ESRS questionnaire, i.e. as soon as all reporting entities assigned to the ESG report have submitted their DMA reports, the ESG solution will automatically apply this information to the relevant parts of the ESRS questionnaire. The following applies:
- If a reporting entity **marked** a topic, sub-topic, or sub-sub-topic as having either [financial](https://support.lucanet.com/en/documentation/glossary.md#financial-materiality) or [impact materiality](https://support.lucanet.com/en/documentation/glossary.md#impact-materiality), this reporting entity is **assigned** to the respective element in the ESRS questionnaire.
- If a reporting entity did **not** mark a topic, sub-topic, or sub-sub-topic as having either financial or impact materiality, this reporting entity is **not assigned** to the respective element in the ESRS questionnaire.
- If **none** of the reporting entities marked a topic, sub-topic, or sub-sub-topic as having either financial or impact materiality, then the respective element is automatically **excluded** from the ESRS questionnaire.
- **All other parts** of the ESRS questionnaire that are not mapped in the DMA report are **included** in the ESRS questionnaire and **assigned** to all reporting entities.
> **Tip:** Keep in mind: You can change this presetting by configuring the ESRS questionnaire according to your needs (see [Configuring the Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep.md)).
---
---
title: "User Roles and User Interface in ESG Reporting"
description: "There are two available user roles for Lucanet ESG Reporting: ESG Administrator and ESG Data Collector. The options available to you will differ depending on which role you have been assigned. You will also see a different ESG Reporting interface depending on your role."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/user-roles-esgrep
language: en
last_updated: 2026-09-15
---
# User Roles and User Interface
## Overview
There are two available user roles for Lucanet ESG Reporting: **ESG Administrator** and **ESG Data Collector**. The options available to you will differ depending on which role you have been assigned. You will also see a different ESG Reporting interface depending on your role.
## Assigning User Roles
Use the **Administration** section of the **Lucanet CFO Solution Platform** to assign user roles (see [User Management](https://support.lucanet.com/en/documentation/administration/user-management.md)).
## ESG Administrator
Users with the **ESG Administrator** user role have full access to the ESG solution. The **ESG Administrator** user role is designed to monitor and control ESG reports. ESG Administrators can perform various tasks, such as:
- Creating new ESG reports and administrating master data
- Configuring the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs) or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire
- Checking, approving and rejecting submitted ESG reports
- Canceling and restoring ESG reports
## User Interface for ESG Administrators
ESG Administrators can access the following workspaces:
### ESG Reports
In the **ESG Reports** workspace, ESG Administrators can access an overview of all the ESG reports that have been created and view their current statuses. ESG Administrators can also:
- Create new reports or cancel existing reports
- Access existing reports and approve or reject data submitted by ESG Data Collectors
- Access and restore canceled reports
- Reopen aggregated reports
- Display notes on reports
Display of 'ESG Reports' workspace for ESG Administrators
### ESG Data Collection
In the **ESG Data Collection** workspace, ESG Administrators can view information on the status of the data collection for reports that have already been assigned to the reporting entities. ESG Administrators can also:
- Access existing reports and approve or reject data submitted by ESG Data Collectors
- Display notes on reports
Example for available functionalities for ESG Administrator in the 'Data Collection' workspace
### Double Materiality Assessments
In the **[Double Materiality Assessments](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment)** (DMA) workspace, ESG Administrators can access a list of all DMA reports and their respective status, as well as open a DMA report to gather more detailed information. It is also possible to view a list of canceled ESG reports whose DMA process was in progress or finalized at the time of cancelation.
View of the 'Double Materiality Assessments' workspace for ESG Administrators
### Custom Emission Factors
In the **Custom Emission Factors** workspace, the ESG Administrator can create and manage custom emission factors. These factors can then be selected in the **Activity type** drop-down list when creating a footprint for the emissions module.
'Custom Emission Factors' workspace
### EU Taxonomy
Under **EU Taxonomy**, ESG Administrators can access the following workspaces:
The **Reports and Activities** workspace provides an overview of current and canceled EU Taxonomy reports, their status, and their assigned reporting entities. It is possible to access the individual business activities per reporting entity and check their status on taxonomy eligibility or taxonomy alignment.
Display of the 'Reports and Activities' workspace for ESG Administrators
The **Minimum Safeguards** workspace provides a status overview of the [minimum safeguard questionnaires](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/collect-eut-data/minimum-safeguards.md) for each reporting entity and the option to display each minimum safeguard questionnaire.
Display of the 'Minimum Safeguards' workspace for ESG Administrators
> **Note:** ESG Administrators have **view** access only. To be able to **edit** an EU Taxonomy report, the user with ESG Administrator user role has to be assigned as data collector to an EU Taxonomy report in the master data administration.
> **Note:** For more information on the available functionalities for ESG Administrators, please refer to [General Functions](https://support.lucanet.com/en/documentation/esg-reporting/general-functions-esg.md).
## ESG Data Collector
Users with the **ESG Data Collector** user role have limited functionalities and are designed to enter and submit ESG-relevant data for their reporting entity. ESG Data Collectors can access the **ESG Data Collection** and **[Double Materiality Assessments](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment)** (DMA) workspaces and can perform various tasks, such as:
- Entering data in the ESG report or DMA report to which the Data Collector has been assigned
- Submitting data and adding notes to their data
## User Interface for ESG Data Collectors
ESG Data Collectors can access the following workspaces:
### ESG Data Collection
In the **ESG Data Collection** workspace, ESG Data collectors can view the status and access their assigned ESG reports for data collection. ESG Data Collectors can also display canceled ESG reports.
Display of 'ESG Data Collection' workspace for ESG Data Collectors
### Double Materiality Assessments
In the **Double Materiality Assessments** workspace, ESG Data Collectors can view the status of their assigned DMA reports and access the DMA reports to classify the respective sustainability topics, if necessary, and submit the DMA report. It is also possible to view a list of all canceled ESG reports whose DMA process was in progress or finalized at the time of cancelation and to which the ESG Data Collector was assigned as editor or reviewer.
Display of the 'Double Materiality Assessments' workspace for ESG Data Collectors
### EU Taxonomy
Under **EU Taxonomy**, ESG Data Collectors can access the **Reports and Activities** workspace to all EU Taxonomy reports to which they are assigned and access the list of canceled EU Taxonomy reports.
> **Note:** For more information on the available functionalities for ESG Data Collectors, please refer to [General Functions](https://support.lucanet.com/en/documentation/esg-reporting/general-functions-esg.md).
---
---
title: "Using the Questionnaire Builder"
description: "After having familiarized yourself with the structure and general functions of the questionnaire builder, you can start configuring the ESRS, ESRS 2.0, or VSME questionnaire, i.e., you can define the scope of the questions that you want to include in the questionnaire, and define which reporting entity has access to certain parts of the questionnaire."
source_url: https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/using-questionnaire-builder
language: en
last_updated: 2026-09-28
---
# Using the Questionnaire Builder
## Overview
After having familiarized yourself with the structure and general functions of the questionnaire builder, you can start configuring the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), [ESRS 2.0](https://support.lucanet.com/en/documentation/glossary.md#esrs-20), or [VSME](https://support.lucanet.com/en/documentation/glossary.md#vsme) questionnaire, i.e., you can define the scope of the questions that you want to include in the questionnaire, and define which reporting entity has access to certain parts of the questionnaire.
Proceed as follows:
### Defining the Questionnaire Scope
When configuring a new questionnaire, all elements are **included by default**. You can include or exclude questions from the questionnaire by activating or deactivating the respective check box. Proceed as follows:
1. Click **Edit** to start defining the scope. A draft of the original questionnaire is automatically created.
2. Deactivate the check boxes of the elements that you want to exclude from the questionnaire.
3. Click **Apply changes** to save your draft.
> **Note:** Further information on the **scope definition** :
>
> - If you include a superordinate element, all of its child elements will also be included.
> - If you exclude a child element, the check box of all its superordinate elements will be changed to the not all included icon to visualize that there is at least one question under the superordinate element that has been excluded from the questionnaire.
> - Content that has been excluded is grayed out.
>
> Further information on the **questionnaire drafts** :
>
> - You can make multiple changes to the scope of the questionnaire when defining the questionnaire, but also **after** the [data collection](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep.md) has started, i.e. until the data for the ESG report are [aggregated](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md).
> - Any element that is **excluded** due to a change to the questionnaire scope will be **hidden** from the questionnaire along with any answers, attached files, additional user assignments, or reviews that may have already been created.
> - Any element that was previously excluded and is **included again** in a later draft will be **visible** again along with any answers, attached files, additional user assignments, or reviews that may have already been created in the past.
Options for including or excluding questions
> **Warning:** Before you exclude a question or a table column, check whether the formula of a [formula-based KPI](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md) refers to it. An excluded question no longer provides a value, so the KPI can no longer be calculated. Include the question again, or correct the formula of the KPI. Use the **Preview** option of a KPI to see what its formula refers to.
> **Note:** Optional: map results of double materiality assessment
>
> In case you have chosen **ESRS** as report guideline and as long as you have not completed the configuration of the **ESRS questionnaire**, you still have the option to map the results of a [double materiality assessment](https://support.lucanet.com/en/documentation/glossary.md#double-materiality-assessment), even if you have deactivated the **Double Materiality Assessments** option in the master data page.
>
> To do so, return to the master data page and activate the respective option (see [Creating an ESG Report](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md)). Please keep in mind that this action will **undo** all configurations that you have made so far to the ESRS questionnaire.
### Assigning Reporting Entities to Specific Questionnaire Parts
All reporting entities that have been defined in the **master data administration** as data collectors are automatically assigned to the **whole** ESRS, ESRS 2.0, or VSME questionnaire. However, you can assign the reporting entities to **certain parts** of the questionnaire to create customized questionnaires and collect data specifically assigned to a reporting entity.
Questionnaire builder with assignment state per element
**Assigning or Unassigning Reporting Entities**
To assign certain reporting entities to a part of the questionnaire or remove this assignment, click the button of the element for which you want to change the assignments.
Button with assignment state for 'General Disclosures'
In the subsequently displayed dialog, you can assign or unassign the required reporting entities.
Assigning reporting entities to the 'General Disclosures' category
**Icons for Assignment States**
The following icons are used to display an assignment state:
| Icon | Description |
|---------|---------|
| the fully assigned icon | **In the case of an organization element:** All of the reporting entities that are part of this organization element are fully assigned to this element (only relevant for users who use Lucanet.Financial OLAP Server). **In the case of a reporting entity:** The reporting entity is assigned to this element and to all of the subordinate questionnaire elements. |
| the partially assigned icon | **In the case of an organization element:** The organization element contains at least one assigned and at least one unassigned reporting entity (only true for users who use Lucanet.Financial OLAP Server). **In the case of a reporting entity:** The reporting entity is assigned to at least one of the subordinate elements but not to all of the subordinate elements. |
| the not assigned icon | **In the case of an organization element:** None of the reporting entities of the organization element are assigned (only true for users who use Lucanet.Financial OLAP Server). **In the case of a reporting entity:** The reporting entity is not assigned to this element or to any of its subordinate elements. |
> **Note:** **Note**: To assign reporting entities to the **whole** ESRS, ESRS 2.0, or VSME questionnaire or **remove** this assignment **completely**, return to the [master data administration](https://support.lucanet.com/en/documentation/esg-reporting/master-data-esgrep.md) and manage the reporting entities accordingly.
> **Note:** **Note**: A **formula-based KPI** has no assignment of its own. It is visible for a reporting entity only if that entity is assigned to **all** the questions used in its formula. If you later unassign one of these questions, the KPI is no longer displayed for that reporting entity (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)).
**Example of a Configuration**
In the following example for an ESRS questionnaire builder, 11 reporting entities have been assigned to the **General Disclosures** category in total. 9 of the reporting entities are only partially assigned, i.e. in this example, 2 reporting entities cannot access **1\. Basis for Preparation**.
Assignment status for the 'General Disclosures' category and its subordinate elements
The tooltip that appears when hovering over the organigram icon reflects this accordingly:
Tooltip with information of assigned reporting entities
### Adding Additional Guidance for ESG Data Collectors
As an **ESG Administrator**, you can add **additional guidance** to individual **questions** in the questionnaire. You can use additional guidance to supplement the original text of the guideline the question that is based on by providing ESG Data Collectors with company-specific instructions, examples, or internal references directly for each question.
To add additional guidance to a question, proceed as follows:
1. Navigate to the question to which you want to add additional guidance.
2. Click the three-dot icon and select **Additional guidance** from the drop-down list.
'Additional guidance' option for a question
3. In the subsequently displayed panel **Additional guidance**, enter your text.
4. Click **Save**.
The additional guidance is now visible to all ESG Data Collectors assigned to this question (see [Filling Out Report Questionnaire](https://support.lucanet.com/en/documentation/esg-reporting/collect-data-esgrep/esg-data-collection-esgrep/editing-data.md)).
### Adding Custom Questions
Besides configuring the standard questions, you can extend the questionnaire with your own **custom questions** to collect company-specific metrics, voluntary disclosures, or internal KPIs. For details, see [Adding Custom Questions](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-custom-questions.md).
### Adding Formula-Based KPIs
You can also add **formula-based KPIs** — calculated values that are derived from the answers to other questions of the questionnaire. For details, see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md).
---
---
title: "Working with Duplicated ESG Reports"
source_url: https://support.lucanet.com/en/documentation/esg-reporting/duplicate-report
language: en
last_updated: 2026-09-25
---
# Working with Duplicated ESG Reports
## Overview
When duplicating an ESG report, Lucanet ESG Reporting automatically copies key data and configurations from the source report, helping you save time and maintain consistency across reporting periods. This article explains what information is duplicated, how to work with duplicated content, and how to modify the report structure on duplicate reports.
## Duplicating ESG Reports
As an ESG Administrator, you can duplicate a report with the pre-set configurations in the master data and ESRS or VSME questionnaire. The parameters of the duplicated report can be adjusted.
To duplicate an ESG report, proceed as follows:
1. Navigate to the ESG report on the **Report overview** tab and click the **Duplicate report** icon.
Duplicate icon for ESG report
> **Warning:** The duplicated report is automatically displayed in the **Master Data** step, regardless of the source report's status.
2. For the duplicated report:
- Enter the **name** and the **period**.
- The **currency**, **report guideline**, configurations for **Double materiality assessment**, **EU Taxonomy**, the **reporting entities assignment**, and any **additional guidance** added to questions in the source questionnaire are automatically copied from the source report, but you can change the configurations for the duplicate as needed.
3. Continue configuring the duplicate report (see following sections).
## Working with Duplicate Reports
### Duplication Indicators
Data that has been duplicated from the source report displays a **duplication indicator** showing the name of the source report. These indicators appear in:
- **Emissions Module**: Next to duplicated footprints in each scope and category
- **ESRS or VSME Questionnaire**: Next to duplicated questionnaire answers
The indicator is displayed as follows, for example:
Indicator for duplicated data
> **Note:** The duplication indicator is **removed** when:
>
> - You modify any data in a duplicated emissions footprint
> - You change any part of a duplicated questionnaire answer
> - You edit values, selections, or text in duplicated content
### Working with Duplicated Data
The following data are **automatically copied** when you duplicate a report.
#### User assignments
**User assignments** configured in the source report's **Data Collection** step are copied to the duplicate report, i.e. users assigned as **editors** or **reviewers** for specific sections and questions. The assignments are copied **per reporting entity** and **per questionnaire element**.
> **Note:** The duplicate report displays these assignments in **edit mode by default**, allowing you to:
>
> - Review and adjust assignments as needed
> - Add new users or remove existing ones
#### Double Materiality Assessment responses
If the source report includes a Double Materiality Assessment, the **DMA responses from reporting entities are copied** to the duplicate report.
#### Footprints in the Emissions Module
All **footprints** created in the source report's Emissions Module are copied to the duplicate report, including all original data, such as activity type and emission factor.
#### Answers in the ESRS or VSME questionnaire
**Questionnaire answers** from the source report are copied to the duplicate report **only when both reports use the same guideline**, i.e. if the original report is based on ESRS, but the duplicated report is based on the VSME guideline, the answers are not copied into the duplicated report.
If the guideline is not changed, the answers, such as text inputs or numerical values are copied into the duplicated report.
### Handling Changes to Questionnaire Structure
If the questionnaire structure has changed between the source report and the duplicate report, e.g. because the template has been updated or the Questionnaire Builder has been modified, the data in the duplicated report are affected as follows:
- **New questions** in the source report: The questions contain no copied answers.
- **Deleted questions** in the source report: Deleted questions are not displayed anymore in the duplicate report. If a deleted question is added again later, the original input will reappear.
- **Modified questions** in the source report: Modified questions contain no copied answers if the question type or question text has changed.
- **Formula-based KPIs**: KPIs and their formulas are copied together with the questionnaire. If a value used in a formula no longer exists in the duplicate report, for example because the duplicate is based on a newer guideline version, the KPI can no longer be calculated. The ESG Administrator has to correct the formula in the questionnaire builder (see [Adding Formula-Based KPIs](https://support.lucanet.com/en/documentation/esg-reporting/questionnaire-builder-esgrep/adding-formula-based-kpis.md)).
## Excluded Data in Duplicated Reports
When duplicating an ESG report, certain data are **not copied** to ensure data integrity and allow for a fresh start in the new reporting period. The following table explains what is excluded to plan your data collection process effectively:
#### Review and mark as completed statuses
- The **review status** of questions or sections marked as **Reviewed** by reviewers are reset in the duplicated report.
- The **mark as completed statuses** of questions marked as completed by data collectors are also reset.
#### EU Taxonomy data
**EU Taxonomy** data from the source report is **not** copied to the duplicate report, such as business activities and their configurations, or eligibility assessments or alignment assessments.
#### Notes and comments
**Notes** and **comments** created during the data collection and review process are **not** copied, e.g when submitting a report, or when approving or rejecting data.
#### Attachments
**Attachments** uploaded to questionnaire questions are **not** copied to the duplicated report.
---
## Disclosure Management
The Lucanet Disclosure Management solution enables you to cover the entire process from data collection and evaluation to transmission and reporting. Its automated data flow and integrated XBRL tagging system allow you to combine your financial and ESG reporting processes.
---
source_url: https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/layout-check
language: en
last_updated: 2026-08-03
---
# Layout Check
## Overview
In Lucanet **Disclosure Management**, the **Layout Check** automatically monitors the text and formatting consistency of a Word chapter. As soon as a chapter is checked out or updated in Word, the Layout Check checks the content for deviations from the stored text and formatting rules – without requiring any additional work step. The Layout Check also runs automatically when a result document is created.
Violations found are shown on the **Layout violations** tab of the Messages window in Word (see [Reviewing Layout Check Violations](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md)).
On the **Layout check** tab in the **Configure document** workspace, you define which rules are monitored.
> **Warning:** The **Layout check** tab and all related functions require an **Advanced** license or higher. Without a sufficient license, the tab is displayed but disabled.
## Opening the 'Layout Check' Tab
To open the **Layout check** tab, proceed as follows:
1. Open a document and click **Configure document**.
2. Open the **Layout check** tab. It is displayed as follows, for example:
The 'Layout check' tab in the 'Configure document' workspace
## Enabling and Disabling Text Rules
The Layout Check rules are divided into two groups in the **Text rules** area: **Characters** and **Formatting**.
Each rule has its own toggle switch that lets you enable or disable the rule individually.
Some rules depend on each other:
- **'Spacing' font-size adjustment** can only be enabled if **Custom font size** is active.
- **'Spacing' color highlight** can only be enabled if **Highlight** is active.
Disabling the parent rule also disables the dependent rule.
The header of **Text rules**, as well as of each of the two groups, shows the number of active rules, for example **15 of 15 active**.
> **Note:** The Layout Check settings apply document-wide, regardless of the document language – unlike the [Typography Rules](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/manage-typography-rules.md), which are managed per document language.
The following rules are available:
**Characters**
| Rule | Description |
|---|---|
| Duplicate punctuation | Flags identical punctuation marks that appear immediately next to each other. |
| Missing punctuation at end of paragraph | Flags body-text paragraphs that do not end with a sentence-closing punctuation mark: period, question mark, exclamation mark, colon, semicolon, or ellipsis. Checked in body text only, not headings, lists, or table-of-contents entries. |
| Duplicate quotation marks | Flags duplicated quotation marks. |
| Missing or misordered brackets | Flags missing brackets or mismatched bracket pairs (for example, round, square, or curly brackets). |
| Duplicate whitespace | Flags spaces that appear immediately next to each other. |
| Repeated words | Flags words that are immediately repeated. |
**Formatting**
| Rule | Description |
|---|---|
| Custom font size | Flags characters with a manually set font size (not inherited from the style). |
| 'Spacing' font-size adjustment | Checks whether font size adjustments were made through the configuration on the 'Spacing' tab, and flags them as separate layout violations. Checked on protected spaces only. |
| Custom font | Flags characters with a manually set font. |
| Custom font color | Flags characters with a manually set font color. |
| Custom shading | Flags manually set shading. |
| Highlight | Flags manually set highlighting. |
| 'Spacing' color highlight | Checks whether highlight color adjustments were made through the configuration on the 'Spacing' tab, and flags them as separate layout violations. Checked on protected spaces only. |
| Changed values | Flags text passages with highlighted, changed values. Checked in table cells and inline variables only, not in regular body text. |
| Unlisted style | Flags styles that are not stored in the [Style Guide](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md). |
> **Note:** Graphics are not monitored by the Layout Check. Table content is currently covered by the **Changed values** and **Unlisted style** rules. Headers, footers, and footnotes are not checked by any rule.
## Impact on Existing Chapters
When the Layout Check is activated for a document for the first time, all existing violations of the active rules appear at once the next time a Word chapter is checked out. How many there are depends on the respective chapter.
You can mark intentional deviations as **Approved** directly on the **Layout violations** tab with a single click (see [Reviewing Layout Check Violations](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md)) – this is a one-time but necessary effort. After that, these spots are no longer flagged as an active violation.
---
---
title: "All Steps at a Glance"
description: "In this chapter, you will find the individual steps required to generate a report using Lucanet Disclosure Management. The presented sequence of steps is our recommendation for configuring and creating a business report in the most effective way possible."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/process-description-disclmgmt
language: en
last_updated: 2026-05-01
---
# All Steps at a Glance – Disclosure Management
## Overview
In this chapter, you will find the individual steps required to generate a report using **Disclosure Management**. The presented sequence of steps is our recommendation for configuring and creating a result document in the most effective way possible.
You do not have to follow the recommended sequence in detail. If necessary, individual steps can also be carried out at a different time. For greater clarity, we have focused on the main steps and have not described optional detailed steps.
### Step 1: Creating a Document
In the **Dashboard**, new documents are created and all the documents that have been created in Disclosure Management are displayed.
- Create a new document in the [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md).
### Step 2: Creating a Chapter Structure
For a document managed by Disclosure Management, you can create as many chapters and chapter levels as you need to structure the document.
- Create the structure of the document in the [Manage Chapters](https://support.lucanet.com/en/documentation/disclosure-management/chapter-mgmt-disclmgmt.md) workspace.
### Step 3: Creating Periods
A **period** is a time frame for which report data are imported and saved. For a document, you can create and manage as many periods as you need, e.g. **current year** or **previous year**.
- Create the required periods in the [Manage Periods](https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt.md) workspace.
### Step 4: Defining Data Sources
**Data sources** form the basis of a data import from a source system and/or a source file into Disclosure Management.
- In the [Import Management](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt.md) area, configure the data source(s) to import the desired data into Disclosure Management.
### Step 5: Configuring and Executing a Data Import
During a **data import**, data are imported into Disclosure Management from the source systems used.
- In the [Import Data](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md) workspace, configure the data import and import the data from the source system into Disclosure Management.
### Step 6: Creating and Programming Excel Files
Excel files form the main basis for using report data from a source system. Data from Excel files are embedded in Word files in such a way that the values in the report are updated automatically if the Excel data are updated, e.g. as a result of an additional data import. Carry out the following individual steps:
- In the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md), create Excel files for the chapters to include the report values from the source system.
- Insert [Name Columns, Value Columns, and Programming Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md) in the Excel tables.
- Carry over report values to the Excel file using the [Programming Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-values.md).
- Insert [Outreas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md) in the Excel tables.
### Step 7: Creating and Configuring Word Files
Word files play a key role in Disclosure Management when it comes to creating a business report. The final result document is built using Word files. Carry out the following individual steps:
- In the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md), create Word files for the chapters of the document.
- Insert [Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-outarea-in-worddocument.md) from the Excel files in the Word files where report values are to be displayed.
- If necessary, insert [Text Values](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word-use-variables.md).
- If necessary, assign a [Layout](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_insert_layout.md) to outareas.
- If necessary, tag text blocks in the Word document using [XBRL Tags](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags.md).
### Step 8: Creating and Configuring Validations
[Validations](https://support.lucanet.com/en/documentation/glossary.md#validation) check and ensure the consistency of values within a document.
- Create and configure the necessary validations in the [Manage Validations](https://support.lucanet.com/en/documentation/disclosure-management/validation-mgmt-disclmgmt.md) workspace.
### Step 9: Checking and Adjusting Report Values
Report values imported from a source system can be manually checked, updated, and modified in the **data view**. The values must be checked, for example, to avoid and correct errors when rounding or validating the report values.
- Open the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) for all programmed Excel files and check the displayed values.
- If necessary, adjust any incorrect report values.
### Step 10: Configuring and Creating the Result Document
The **result document** is the final report created by Disclosure Management.
- Configure and generate the result document in the [Creation](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md) workspace.
---
---
title: "Assigning Document Roles for Disclosure Management"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt
language: en
last_updated: 2026-09-10
---
# Assigning Document Roles for Disclosure Management
## Overview
Document-specific roles can be used to assign permissions at the document level, e.g. read and write permissions for documents, chapters, periods and validations, or the permission to import data or change the status of individual process steps.
In the **Document roles** workspace of Role Management, you can use predefined roles to assign the following permissions:
- **Document-level permissions**, e.g. read and write permissions for individual documents, chapters, periods and validations
- **Workflow-based permissions** for changing the status of individual process steps within a workflow
## 'Document roles' workspace
The **Document roles** workspace is displayed as follows:
The workspace 'Document roles'
## Permissions at the Document Level and Workflow-Based Permissions
The permissions that can be assigned using predefined roles at the document level are listed in the **Document roles** area, in the right-hand column, under **_Role_ Permissions**.
You can also view an overview of the permissions a user with the corresponding role has for changing a status within a predefined workflow. To do this, click the Info icon in the **Workflow-based permissions** area.
**Note**: User-defined workflows will only become available with a later version of Lucanet.
The following permissions can be assigned with the available document roles:
### Document Administrator
#### Document-level permissions
- **ReadAllChapters**: Read all chapters
- **EditAllChapters**: Edit all chapters
- **DeleteAllChapters**: Delete all chapters
- **ReadAllExcelFiles**: Read all Excel files
- **EditAllExcelFiles**: Edit all Excel files
- **DeleteAllExcelFiles**: Delete all Excel files
- **EditAllReportData**: Edit all report data
- **ReadAllReportData**: Read all report data
- **CommentReportData**: Delete all report data
- **ReadAllWordFiles**: Read all Word files
- **EditAllWordFiles**: Edit all Word files
- **DeleteAllWordFiles**: Delete all Word files
- **ReadAllDocumentVariables**: Read all document variables
- **EditAllDocumentVariables**: Edit all document variables
- **DeleteAllDocumentVariables**: Delete all document variables
- **ChapterUnlocking**: Unlock chapter
- **LayoutAction**: Perform layout action
- **ReadPeriods**: Read periods
- **EditPeriods**: Edit periods
- **DeletePeriods**: Delete periods
- **ReadAllLanguages**: Read all languages
- **EditAllLanguages**: Edit all languages
- **DeleteAllLanguages**: Delete all languages
- **ReadAllValidations**: Read all validations
- **EditAllValidations**: Edit all validations
- **DeleteAllValidations**: Delete all validations
- **StatusChangesFrom**: Make status changes
- **StatusChangesTo**: Make status changes
- **CopyDocuments**: Copy documents
- **EditDocumentSettings**: Edit document settings
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ImportData**: Import data
- **EditXBRLMapping**: Create XBRL mapping
- **ReadDocument**: Read a document activated for the user
- **EditDocument**: Edit a document activated for the user
- **DeleteDocument**: Delete a document activated for the user
- **ReadAttachments**: Read Attachments
- **EditAttachments**: Edit Attachments
- **DeleteAttachments**: Delete Attachments
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Document Administrator** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Document Administrator role
### Document Editor
#### Document-level permissions
- **EditAllLanguages**: Edit all languages
- **ReadAllValidations**: Read all validations
- **EditAllValidations**: Edit all validations
- **DeleteAllValidations**: Delete all validations
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **EditDocument**: Edit a document activated for the user
- **ReadPeriods**: Read periods
- **EditXBRLMapping**: Create XBRL mapping
- **ReadAttachments**: Read Attachments
- **EditAttachments**: Edit Attachments
- **DeleteAttachments**: Delete Attachments
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **EditAllDocumentVariables**: Edit all document variables
- **EditPeriods**: Edit periods
- **DeletePeriods**: Delete periods
- **ReadAllLanguages**: Read all languages
- **CopyDocuments**: Copy documents
- **ImportData**: Import data
- **ReadDocument**: Read a document activated for the user
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Document Editor** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Document Data Importer role
### Document Quality Manager
#### Document-level permissions
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ReadDocument**: Read a document activated for the user
- **ReadPeriods**: Read periods
- **EditXBRLMapping**: Create XBRL mapping
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Document Quality Manager** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Document Quality Manager role
### Document Reader
#### Document-level permissions
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ReadDocument**: Read a document activated for the user
- **ReadPeriods**: Read periods
- **ReadAttachments**: Read Attachments
- **ReadAllReportData**: Read all report data
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Document Reader** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Document Reader role
### Chapter Reader
#### Chapter-level permissions
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadDocument**: Read a document activated for the user
- **ReadPeriods**: Read periods
- **ReadAttachments**: Read Attachments
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Chapter Reader** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Chapter Reader role
### Chapter Editor
#### Chapter-level permissions
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadDocument**: Read a document activated for the user
- **ReadPeriods**: Read periods
- **ReadAttachments**: Read Attachments
- **EditAttachments**: Edit Attachments
- **DeleteAttachments**: Delete Attachments
#### Workflow-based permissions
The graphic below shows the permissions that are assigned to users with the **Chapter Editor** role, depending on the current status of the document in the workflow:
Workflow-based permissions for the Chapter Editor role
## Inheriting Chapter Roles to Sub-Chapters
By default, a chapter role applies only to the exact chapter it is assigned to. If a document has the **Inherit chapter roles to sub-chapters** option enabled in its document settings, the **Chapter Reader** and **Chapter Editor** roles assigned on a parent chapter also apply to all sub-chapters below it, across all levels — including sub-chapters that are created later.
Inherited and explicitly assigned roles accumulate: a user can hold an inherited role and an additional role assigned directly on the sub-chapter at the same time. Assignments that were made directly on a sub-chapter remain active when inheritance is enabled.
For more information about the option, see [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md#chapter-roles).
## Assigning Document Roles to Users
To assign a document role to a user:
1. If necessary, open the **Role Management**.
2. In the **Document roles** column, select the user role you want to assign to a new user.
3. In the **Assigned users** area, click +.
4. In the displayed dialog, select the following items:
- The **User**
- The **Document year** for which you want to assign the role, where applicable.
- If necessary, the **Document name**.
5. In the document list, select the documents or in the chapter list the chapters to which the role for the selected user is to be assigned.
6. **Save** the settings.
---
---
title: "Assigning Global Roles for Disclosure Management"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt
language: en
last_updated: 2026-07-31
---
# Assigning Global Roles for Disclosure Management
## Overview
Global roles can be used to assign solution-wide, cross-document permissions, e.g. administrator rights for documents, import functions, system settings, and role assignment within Disclosure Management.
## 'Global roles'workspace
The **Global roles** workspace is displayed as follows:
The 'Global roles' workspace
> **Warning:** Before a user can be assigned a role in Disclosure Management, they need to be activated for Disclosure Management in the **User Management section of the Lucanet CFO Solution Platform**.
>
> - If a user is assigned the role of **Administrator** for Disclosure Management in the User Management section of the Lucanet CFO Solution Platform, this user will automatically receive the **Global Administrator** role within the Disclosure Management solution, together with all the associated solution-wide, cross-document administrator rights. At least one user with the **Administrator** role for Disclosure Management must be created.
> - If a user is assigned the role of **Editor** for Disclosure Management in the User Management section of the Lucanet CFO Solution Platform, this user will automatically be assigned the role of **Global Editor** within the Disclosure Management solution.
> - If a user is assigned the role of **Reviewer** for Disclosure Management in the User Management section of the Lucanet CFO Solution Platform, this user will automatically be assigned the role of **Global Reviewer** within the Disclosure Management solution.
> - If a user is assigned the role of **Reader** for Disclosure Management in the User Management section of the Lucanet CFO Solution Platform, this user will automatically be assigned the role of **Global Reader** within the Disclosure Management solution.
> - If a user is assigned the role of **No specific role** for Disclosure Management in the User Management section of the Lucanet CFO Solution Platform, this user will not receive any kind of special role at first within the Disclosure Management solution. Different permissions can only be assigned to a user if they are first assigned a user role by a **Global Administrator**.
## Permissions for Global Roles
The permissions that can be assigned with a global role are listed on the right-hand column in the **_Role_ Permissions** area.
The following permissions can be assigned with the available global roles:
### Global Administrator
- **ReadAllDocuments**: Read all documents
- **EditAllDocuments**: Edit all documents
- **DeleteAllDocuments**: Delete all documents
- **ReadRoles**: View roles
- **SettingsGlobal**: Edit global settings
- **AssignGlobalRoles**: Assign global roles
- **ImportAdministration**: Manage data imports
- **AssignDocumentRoles**: Assign document roles
- **ReadAllChapters**: Read all chapters
- **EditAllChapters**: Edit all chapters
- **DeleteAllChapters**: Delete all chapters
- **ReadAllExcelFiles**: Read all Excel files
- **EditAllExcelFiles**: Edit all Excel files
- **DeleteAllExcelFiles**: Delete all Excel files
- **EditAllReportData**: Edit all report data
- **ReadAllReportData**: Read all report data
- **CommentReportData**: Delete all report data
- **ReadAllWordFiles**: Read all Word files
- **EditAllWordFiles**: Edit all Word files
- **DeleteAllWordFiles**: Delete all Word files
- **ReadAllDocumentVariables**: Read all document variables
- **DeleteAllDocumentVariables**: Delete all document variables
- **ChapterUnlocking**: Unlock chapter
- **LayoutAction**: Perform layout action
- **DeletePeriods**: Delete periods
- **ReadAllLanguages**: Read all languages
- **ReadAllValidations**: Read all validations
- **ReadAttachments**: Read Attachments
- **DeleteAllLanguages**: Delete all languages
- **ReadAllValidations**: Read all validations
- **StatusChangesFrom**: Make status changes
- **StatusChangesTo**: Make status changes
- **EditDocumentSettings**: Edit document settings
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **EditXBRLMapping**: Create XBRL mapping
- **CopyDocuments**: Copy documents
- **ReadAllResultDocuments**: Read all result documents
- **ResultDocumentsHistory**: Open result document history
- **ReadPeriods**: Read periods
- **EditAllDocumentVariables**: Edit all document variables
- **EditPeriods**: Edit periods
- **EditAllLanguages**: Edit all languages
- **EditAllValidations**: Edit all validations
- **DeleteAllValidations**: Delete all validations
- **EditAllResultDocuments**: Edit all result documents
- **ImportData**: Import data
- **EditAttachments**: Edit Attachments
- **DeleteAttachments**: Delete Attachments
### Global Editor
- **ReadAllDocuments**: Read all documents
- **EditAllDocuments**: Edit all documents
- **ReadAllDocumentVariables**: Read all document variables
- **EditAllDocumentVariables**: Edit all document variables
- **ReadAllLanguages**: Read all languages
- **EditAllLanguages**: Edit all languages
- **ReadAllValidations**: Read all validations
- **DeleteAllValidations**: Delete all validations
- **CopyDocuments**: Copy documents
- **ReadAllResultDocuments**: Read all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ReadAttachments**: Read Attachments
- **EditAttachments**: Edit Attachments
- **DeleteAttachments**: Delete Attachments
- **ReadPeriods**: Read periods
- **EditXBRLMapping**: Create XBRL mapping
- **ReadAllChapters**: Read all chapters
- **EditPeriods**: Edit periods
- **DeletePeriods**: Delete periods
- **DeleteAllValidations**: Delete all validations
- **EditAllResultDocuments**: Edit all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ImportData**: Import data
### Global Reviewer
- **ReadAllDocuments**: Read all documents
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ReadPeriods**: Read periods
- **EditXBRLMapping**: Create XBRL mapping
### Global Reader
- **ReadAttachments**: Read Attachments
- **ReadAllDocuments**: Read all documents
- **ReadAllChapters**: Read all chapters
- **ReadAllDocumentVariables**: Read all document variables
- **ReadAllLanguages**: Read all languages
- **ReadAllResultDocuments**: Read all result documents
- **EditAllResultDocuments**: Edit all result documents
- **DeleteAllResultDocuments**: Delete all result documents
- **ResultDocumentsFromOtherUser**: Open other users’ result documents
- **ResultDocumentsHistory**: Open result document history
- **ReadPeriods**: Read periods
## Assigning Users a Global Role
To assign a global role to a user:
1. In the **Global roles** column, select the user role you want to assign to a new user.
2. In the **Assigned users** area, click **+**.
3. In the displayed dialog, select the user you want to assign to the role.
4. **Save** the settings.
---
---
title: "Attachments"
description: "Additional information in the form of attachments can be added to all chapters of a Disclosure Management document. This functionality allows you to link important supplementary documents directly with your reports, thereby collecting all relevant information in one place. A document's attachments are managed centrally in a dedicated area."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/attachments
language: en
last_updated: 2026-05-01
---
# Adding Attachments to Documents
## Overview
Additional information in the form of **attachments** can be added to all chapters of a Disclosure Management document. This functionality allows you to link important supplementary documents directly with your reports, thereby collecting all relevant information in one place.
A document's attachments are managed centrally in a dedicated area.
> **Tip:** You can upload PDF, DOCX, XLSX files and images (e.g., PNG, JPEG) up to 5 MB each as an attachment to a chapter.
## Uploading Attachments
To add an attachment to a chapter:
1. If necessary, open the document to which you want to add attachments.
2. In the **Cockpit**, click the desired link in the **Attachments** column. The **Attachments** area will be displayed:
The attachments for all chapters can be managed centrally in the ‘Attachments’ area
3. Select the desired chapter from the **Select chapter** drop-down list.
4. Add the desired attachment via Drag & Drop or click **Browse** and select the desired attachment.
## Displaying Preview
A preview can be displayed for some file types. To activate a preview:
1. Hover your mouse over the desired entry in the **Attached Files** list. If a preview can be displayed for the file type, a preview icon will be displayed:
Opening the preview
2. Click the icon to display the preview.
---
---
title: "Basic Configuration"
description: "Before you can start creating an annual report in Lucanet Disclosure Management, you need to configure a few basic settings."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt
language: en
last_updated: 2026-05-01
---
# Basic Configuration for Disclosure Management
## Overview
Before you can start creating a report in Lucanet Disclosure Management, you need to configure a few basic settings. These comprise:
- **Installing the MS Office Components**\
\
The **[Dispatcher](https://support.lucanet.com/en/documentation/glossary.md#dispatcher)** is a program that must be installed on every computer on which you want to use the Lucanet Disclosure Management solution.\
\
**Ribbons** are menu ribbons that you will need to install if you want to use Disclosure Management with MS Word and MS Excel.\
\
For more information, see [Installing and Updating the MS Office Components](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/install-disp-andribbon.md).
- **Assigning User Roles for Disclosure Management**\
\
You can use user roles to help you define the permissions each user has for specific areas in Disclosure Management. For example, you can use **global roles** to assign system-wide permissions, or simply assign specific **document roles**.\
\
For more information, see [Managing User Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt.md).
- **Configuring System-Wide Settings**\
\
A user with the neccessary permissions can configure preferences that will apply system-wide for the display of certain areas of Disclosure Management for all users.\
\
More information on this can be found in [Disclosure Management Settings](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/discl-mgmt-settings-disclmgmt.md).
---
---
title: "Cockpit"
description: "This is the central work interface in Lucanet Disclosure Management, and shows the editing state of a document at a glance."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt
language: en
last_updated: 2026-05-01
---
# Cockpit
## Overview
The **Cockpit** is the central work interface of the **Disclosure Management** solution, and shows the editing state of a document managed by **Disclosure Management** at a glance.
In the Cockpit, **Rows** reflect the chapters and sub-chapters of documents that have been created in the [Manage chapters](https://support.lucanet.com/en/documentation/disclosure-management/chapter-mgmt-disclmgmt.md) workspace. The **Columns** display detailed information on the individual chapters.
The Cockpit offers a number of options, including:
- Creating and editing Excel files, Word files, and Word references for the chapters and sub-chapters of a document
- Opening Excel and Word files
- Selecting the document language
- Changing and tracking the status of chapters and sub-chapters
- Assigning structures
- Opening the detail view
- Opening the data view
- Showing attachments to a chapter
## Opening the Cockpit
You can open the Cockpit in any of the following ways:
- In the [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md), click on the document you want to open in the Cockpit.
- In the overview, click **Cockpit**.
- Click **Cockpit** on the function bar.
The Cockpit is displayed as follows, for example:
Disclosure Management 'Cockpit’
> **Warning:** If all the other workspaces in the **overview** are grayed out when you open the **Cockpit** and cannot be opened, you do not have the access permissions for these workspaces. If necessary, edit the permissions in [Role Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt.md) or contact your system administrator.
## Configuring the Chapter List
Above the chapter list, you will see the editing bar. You can use this to carry out a number of tasks, including:
- Browsing the chapter list
- Defining which columns to display
- Selecting the display language
- Selecting the required structure,
- Configuring the display and sorting of the chapters
- Extracting the chapter structure of the document into an Excel file
The edit bar is displayed as follows, for example:
Edit bar for the chapter list in the cockpit
The edit bar offers the following options for the chapter list:
#### Find chapter
In the **Chapter search** drop-down list, you can enter your desired search criterion. You can reuse the most recent search criteria, so you don’t have to re-enter them manually when repeating the same search.
> **Note:** If a structure other than the default structure is active in the Cockpit, the chapter search **only** searches the chapters that are visible in that structure. If you switch the structure while a search criteria is active, the search is automatically re-applied.
#### Configure columns
You can adjust the chapter list to suit your needs by showing or hiding individual columns.
#### Select language
If more than one language is stored for a document in Disclosure Management, you can use the **Select language** drop-down list to select the language you wish to use.
#### Select structure
**Structures** are a named selection and arrangement of chapters, including section breaks, used to generate a specific report version from a document.
A single source document can contain multiple **structures**, for example default structure, short report, Management Report, attachment, etc., from which different Word result documents can be generated.
> **Warning:** The drop-down list currently only contains the structures that were carried over from SmartNotes during the migration to Disclosure Management.
>
> Creating, deleting, or renaming structures is not yet possible in Disclosure Management and will be implemented in a later version.
| Option | Description |
|---------|---------|
| the 'expand or collapse chapter' icon | **Expand or collapse chapter**: Switches between displaying all sub-chapters for the document and only displaying the top-level chapters. |
| the 'display chapters as tree structure or flat list' icon | **Display chapters as tree structure or flat list**: Switches between displaying the defined chapter structure for the document and a simple list of all chapters. |
| the 'select/deselect all chapters' icon | **Select/deselect all chapters**: Selects all the chapters or removes the current selection. |
| the 'extract chapter structure' icon | **Extract chapter structure**: Exports the chapter structure of the document to an Excel file. |
## Editing a Chapter
> **Warning:** Read and write permissions can be defined for chapters. You can only edit chapters for which you have editing permissions. For more information, see [Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md).
On the edit bar for each chapter, you can open a context menu by clicking the three dots icon :
The following commands are available:
| Command | Description |
|---------|---------|
| Data view | Manually edit report values using the [Data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md), for example to correct rounding or validation errors. |
| MS Excel | Add a new or a locally saved (external) Excel file to a chapter. |
| MS Word | Add a new Word file, an external Word file, or a Word reference to a chapter. |
| Change status | Assign a new status to a chapter. |
| Assign structures | Assign any chapter to a **structure**. |
| Delete chapter | Deletes the chapter from the document. |
| Open attachments | Opens the [Attachments](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/attachments.md) section, where you can manage attachments for the current chapter. |
| Create partial result document | Uses the selected chapters to create a partial document (see [Creating a Partial Result Document](#pd)). |
### Details for individual commands
#### Data view
During the data import, report values are written based on the Excel programming in the Excel worksheets, and can be manually edited using the [Data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md). This is useful if you need to correct rounding or validation errors, for example.
> **Note:** The **Data view** is **only available for programmed Excel files**.
>
> - An Excel file is classed as “programmed” if it has a Name column, at least one Values column, and at least one Programming column, and at least one cell is programmed into the Programming column.
> - If the Programming column is empty, the Excel file is not classed as programmed.
#### MS Excel
If no Excel file has been assigned to a chapter yet, the following commands are displayed:
- **Add Excel file**: Launches MS Excel with a new file and adds said Excel file to the chapter
- **Add external Excel file**: Adds a locally saved Excel file to the chapter
#### MS Word
If no Word file has been assigned to a chapter yet, the following commands are displayed:
- **Add Word file**: Launches MS Word with the saved template for a new Word document, and adds said Word file to the chapter
- **Add external Word file**: Adds a locally saved Word file to the chapter
- **Add Word reference**: Adds a chapter from another report to this chapter (see [Working with Word References](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/use-word-references.md)).
#### Change status
You can use the **Change status** context menu command to assign a new status to a chapter.
Context menu 'Change status'
## Opening Detail View
Click the info icon to open the [Detail View of a Chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md). The detail view of the chapter displays a variety of information, including the history and details of the assigned MS Office files.
## Creating Partial Result Document
You can create a partial result document at any time, using any chapters of your document. Proceed as follows:
1. Press and hold down the **CTRL** key.
2. In the Cockpit, use the left mouse button to select the chapters you want to include in the partial result document.
3. Click the three dot icon for a chapter and select **Create partial result document**:
Creating Partial Result Document
---
---
title: "Configuring a Document"
description: "In Lucanet Disclosure Management, you can configure individual specifications for each document in the 'Configure document' workspace."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt
language: en
last_updated: 2026-09-10
---
# Configuring a Document
## Overview
In the **Configure document** workspace, individual specifications can be configured for each document. These include:
- Localization
- Separator
- Prefix and suffix
- MS Office settings
- Word template used
- Behavior when updating tables
- Document languages
- Typography rules (Spaces)
- Style guide specifications
- Rules monitored by the Layout Check
> **Warning:** - The settings valid for all documents can be overwritten in the [Advanced Settings](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/excel-file-settings.md) of an Excel file.
> - In addition, document-wide specifications can be configured, for example the display of user names or specifications for import purposes. More information on this can be found in [Disclosure Management Settings](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/discl-mgmt-settings-disclmgmt.md).
## Opening a Workspace
In the overview of a document, click **Configure document** to open the workspace.
Workspace 'Configure Document'
## Options on the 'General Settings' Tab
You can set the following options on the **General Settings** tab in the **Configure document** workspace. Each option is explained in more detail in the user interface.
#### MS Office
Settings for MS Office documents:
Document settings for MS Office
#### Chapter roles
Settings for passing chapter role assignments down to sub-chapters:
Document settings for chapter roles
The **Inherit chapter roles to sub-chapters** option controls whether a chapter role that is assigned on a parent chapter also applies to the sub-chapters below it. The setting applies to the whole document and behaves as follows:
- When the option is **enabled**, a user who holds a chapter role on a parent chapter automatically holds the same role on every sub-chapter below it, across all levels. Sub-chapters that are created later inherit the role as well, without any further assignment.
- Inherited and explicitly assigned rights **accumulate**. A user who holds the **Chapter Editor** role through inheritance and the **Chapter Reader** role explicitly on a sub-chapter holds both roles on that sub-chapter. If the same role is assigned on both the parent chapter and the sub-chapter, it counts as a single assignment.
- When the option is **disabled**, only the roles that are explicitly assigned to a chapter apply. Assignments that already exist on sub-chapters are kept and remain active.
> **Note:** Enabling or disabling the option does not change any existing role assignments. It only changes how the assignments are evaluated when a user opens a chapter.
For more information about chapter roles, see [Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md).
#### MS Word
Settings for MS Word documents:
Document settings for MS Word
> **Note:** The **Highlight changed values on refresh** option is only available when the **Update values within table** insert mode is selected. With the other insert modes, the option is greyed out. If you disable the option, existing table highlights are removed on the next refresh.
> **Note:** **Replacing negative zero values in Word tables**
>
> Rounding can turn a small negative value into `-0`, which is usually not the representation you want in a published report. Use the **Replace -0 with** setting to define the text that Disclosure Management writes instead. The setting applies to the whole document and behaves as follows:
>
> - It is applied to **all tables**, regardless of whether a layout template is assigned to them.
> - It takes effect both when an individual Word file is opened and when a result document is generated. You do not have to open or edit the individual Word files beforehand.
> - It recognizes the different minus characters (for example, hyphen-minus and en dash) as well as values with decimal places, such as `-0.0` or `-0.00`, taking the decimal separator in use into account.
> - Cells that contain `0`, a negative value other than zero, or text that merely contains `-0` remain unchanged.
> - The layout and formatting of the table cell are preserved.
>
> If you change the replacement text, the affected tables are re-inserted the next time the Word file is opened. Word files that have already been stored do not have to be edited manually.
#### MS Excel
Settings for the format template and number formatting in MS Excel:
Document settings for MS Excel (part 1)
Settings for the display and programming of values in MS Excel:
Document settings for MS Excel (part 2)
For more information about MS Excel files in Disclosure Management, see [Creating and Editing Excel Files](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt.md).
#### Data view
Settings for the data view:
Document settings for the data view
For more information about the data view, see [Using the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md).
#### Layout robot
Selecting the [layout robot](https://support.lucanet.com/en/documentation/glossary.md#layout-robot):
Document settings for the layout robot
For more information about the layout robot and its tasks, see [Using Layouts in MS Excel](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/assign-layout-toexcel.md) and [Using Layout Actions in MS Word](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_insert_layout.md).
#### XBRL
Selecting the desired **XBRL taxonomy** for XBRL tagging.
Document settings for XBRL
For more information about the XBRL tagger, see [Editing Documents in the XBRL Tagger](https://support.lucanet.com/en/documentation/disclosure-management/transfer-document-to-XBRL-tagger.md).
## Further Tabs in the 'Configure document' Workspace
In addition to **General Settings**, the **Configure document** workspace provides the following tabs:
| Tab | Purpose |
|---------|---------|
| [Language Settings](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/language-settings.md) | Manage the document languages, including the primary language (Default Language) and language-specific format templates for MS Word. |
| [Spaces](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/manage-typography-rules.md) | Manage the typography rules that are applied automatically when a Word file is checked out (for example, non-breaking spaces between a number and a unit). |
| [Style Guide](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md) | Define which Word styles are available for headings and body text, so that all authors work with the same formatting specifications. |
| [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/layout-check.md) | Choose which text and formatting rules are monitored while a report is edited in Word. |
---
---
title: "Configuring an Excel File"
description: "In the Advanced settings of an Excel file, you can overwrite the Output format and Number formatting settings that are valid for all documents."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/excel-file-settings
language: en
last_updated: 2026-05-01
---
# Configuring an Excel File
## Overview
In the **Advanced settings** of an Excel file, you can overwrite the **Output format** and **Number formatting** settings that are valid for all documents.
> **Warning:** The advanced settings in an Excel file overwrite the settings defined in the [Configure Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) workspace.
## Opening Advanced Settings
How you open the advanced settings depends on the Office variant you use. In **Office for the Web** and **Office Native**, the user guidance and interface are identical.
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, proceed as follows to open and configure the advanced settings:
1. Click **Maintain properties** in the Excel ribbon.
The **Advanced Settings** open as a task pane on the right.
Advanced settings as a task pane in Office for the Web and Office Native
2. Configure the desired settings (see [Configuring Advanced Settings](#eS)) and then click **Apply**.
> **Note:** Changes to the advanced settings only take effect after the Excel file is next checked in.
### Office for Desktop
In Office for Desktop too, the advanced settings of an Excel file can be opened and configured from the **Excel ribbon**. Proceed as follows:
1. Click **Maintain properties** in the Excel ribbon.
Opening advanced settings from the Excel ribbon
2. The **Advanced Settings** dialog is displayed in MS Excel:
Advanced settings of an Excel file
3. Configure the desired settings (see [Configuring Advanced Settings](#eS)) and then click **Apply**.
## Configuring Advanced Settings
The following options are available in the advanced settings:
| Option | Description |
|---|---|
| Overwrite output format | The output format of the Excel file can be set in the drop-down list (e.g. **Million**). |
| Overwrite number formatting | Defines the formatting for values in the file and the number of decimal places used by Disclosure Management in its calculations.
When you activate the **Overwrite number formatting** check box, the option **Decimal places** in the **Number formatting** area will be unlocked and can be edited.
The **preview** will be adjusted as soon as you change the settings in the **Number formatting** area. |
#### Overwrite row assignment
Disclosure Management recognizes the connection between periods and their values based on the set row assignment ( **revenue from the current year** and **revenue from the previous year**, for example).
The **Row assignment** is responsible for ensuring that periods (such as periods in the current year and the corresponding periods in the previous year) are displayed correctly in the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md).
The following row assignments are available:
- **Programming**: When the **Programming** row assignment is selected, Disclosure Management searches for identical programming, e.g. same accounts in the current and previous year. This type of row assignment properly matches the current to the previous year, especially when programming schedules in which the current period and the period being used for comparison are located in different rows.
Overwriting the row assignment using the 'Programming' method
- **Row position**: Disclosure Management identifies the report values that belong together based on their **Row position**. If several values are located in the same row, they are regarded as belonging together. This type of assignment is used in tables in which the values of the current period and the comparison period are located in adjacent columns, regardless of the selected programming, for example. If two report values are located in the same row and have different programming, e.g. **#s6** and **#m6**, Disclosure Management recognizes them as belonging together with the **Row position** row assignment.
Overwriting the row assignment using the 'Row position' method
- **Row label**: Disclosure Management identifies the report values based on their **Row label** (= name_ column). If several values have the exact same label, they are regarded as belonging together. This type of assignment is very rare.
> **Note:** By default, the **Programming** row assignment is preset.
---
---
title: "Configuring and Executing a Data Import"
description: "When you have defined the data source(s) and the connections to these data sources as the basis for the import in the Import Management area, you can configure and execute the data import. Both are carried out in the Lucanet Import Data workspace at individual document level."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt
language: en
last_updated: 2026-05-01
---
# Configuring and Executing a Data Import
## Overview
When you have defined the data source(s) and the connections to these data sources as the basis for the import in the **Import Management** area, you can configure and execute the data import. Both are carried out in the **Import data** workspace at individual document level.
> **Warning:** The **Import data** workspace is only activated for users who have been assigned the **Document Administrator** or **Document Data Importer** role at document level in Disclosure Management role management. (For additional information about user roles in Disclosure Management, see [Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md).)
## Required Sequence of Steps
To configure and execute a data import:
1. In the overview of a document, click **Import data** to open the workspace.
2. Select the data source to be used for the import (see section [Selecting a Data Source](#SelDataSource)).
3. Choose the parameters for the data import at document level (see section [Parameterizing Data](#paramData)).
4. If necessary, display a preview of the import and check the data (see section [Displaying a Preview and Checking Data](#Preview)).
5. Start the data import (see section [Starting the Data Import](#startimp)).
## Selecting a Data Source
When you open the **Import data** workspace at document level, the **Data sources** area is displayed by default:
‘Data sources' area
This area contains all the data sources you defined in **Import Management** (see section [Defining a Data Source](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt.md)). You can sort the data sources by **name**, **connection type**, **description** or **last execution date**.
Select the data source(s) to be imported by activating the corresponding check box(es) and click **Go to parameterization**.
## Parameterizing Data
In the **Parameterization** area, select the parameters for importing the selected data source(s) at document level. The area is displayed as follows, for example:
‘Parameterization' area
The area contains the following elements:
| Option | Description |
|---|---|
| Connection to the data source | Displays the connection of the selected data source and serves as the top root folder for parameterizing the data source. The element can be expanded and collapsed using the arrow icon. A separate root folder for parameterization is displayed for each data source selected in the **Data sources** area. |
| Data source | Displays the selected data source. The element can be expanded and collapsed using the arrow icon so that further parameters can be assigned for this data source, if necessary. |
| Mapping | Displays the mapping that has been defined within a data source. The element can be expanded and collapsed using the arrow icon. For each mapping defined within a data source, a separate folder is displayed that can be expanded and collapsed. For additional information on defining mappings see section [Defining a Data Source](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt.md). |
When you have selected all parameters for all displayed data sources, you have the following options:
- You can use the **Open preview** button to display a preview of the imported data in order to check the data again before the actual import. For additional information on this, see chapter [Displaying a Preview and Checking Data](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt/.md#Vorschau%2520anzeigen%2520und%2520Daten%2520pr%25C3%25BCfen).
- You can use the **Start data import button** button to import the data immediately without a preview. For additional information on this, see section [Starting the Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt/.md#Datenimport%2520starten).
- You can navigate back to the **Data sources** area to make any necessary adjustments to the selection of data sources.
## Displaying Preview and Checking Data
When you have configured all parameters for all selected data sources, you can use the **Open preview** button to display a preview of the imported data in order to check the data again before the actual import.
The preview is displayed as follows, for example:
‘Preview' area
The following elements are displayed in the preview in the top section:
| Option | Description |
|---|---|
| Name | Name of the data source(s) to be imported |
| Connection type | Connection type of the data source: **Client FlatFile Import** (client-side import of an Excel or CSV file); **Server FlatFile Import** (server-side import of an Excel or CSV file); **Lucanet Rest API Import** (import from a Lucanet database); **S3 ESG Import** (import from Lucanet ESG Reporting) |
| Description | Description stored in the definition of the connection to the data source |
| Last execution | Date of the last execution of an import of this data source |
The following elements are displayed in the preview in the table:
| Element | Description |
|---------|---------|
| Programming | Content of the column that was defined as a programming column in the imported data source |
| Name | Content of the column that was defined as a name column in the imported data source |
| New value | New value after the current import |
| Old value | Old value before the import |
| Difference | Difference between new and old value |
When you have checked the import in the preview, you have the following options:
- You can import the data using the **Start data import** button. For additional information on this, see section [Starting the Data Import](#startimpt).
- You can make changes to the configuration of the import and reopen the preview. Changes are possible in the following areas:
- In the previous steps **Data sources** or **Parameterization**.
- In the **Import Management** in the connection to the data source or the data source itself.
## Starting the Data Import
To start a data import, click **Start data import** either in the **Parameterization** area or in the **Preview** area.
The task of executing the data import is then transferred to the [job monitor](https://support.lucanet.com/en/documentation/glossary.md#job-monitor) and you can display the status of the task by clicking on the bell icon at the top right-hand corner. Successful execution of an import is displayed as follows, for example:
Notification of successful import
---
---
title: "Configuring the Data View"
description: "Various display options can be configured in the data view. For example, it can be defined from which columns and for which periods values are to be displayed.\n\nFurthermore, rows can be configured in such a manner that they are hidden in the Outarea of the Word and/or Excel file."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/data-view/open-and-configure-data-view
language: en
last_updated: 2026-05-01
---
# Configuring the Data View
## Overview
Various display options can be configured in the data view. For example, it can be defined from which columns and for which periods values are to be displayed.
Furthermore, rows can be configured in such a manner that they are hidden in the Outarea of the Word and/or Excel file.
## Options
You can configure what is displayed in the data view in the upper area of the view.
The following options are available:
### Values to Be Displayed
Activate the check boxes of the value columns whose values you wish to review.
### Periods to Be Displayed
Activate the check boxes of the periods whose values you wish to review.
### Output Format
Number format (e. g. thousands, millions, and billions) for the values to be used in the **data view**. This can only be modified by changing the output format in MS Excel.
The output format displayed here is adopted from the [document settings](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) or – if the output format of the Excel file is overwritten in the [advanced settings](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/excel-file-settings.md) of MS Excel – from the Excel file.
> **Note:** The output format serves as the basis for reporting, validating, and checking data, which is why it cannot be changed in the **data view**.
### Displaying Exact Values
Activate the **Show exact value** check box to display the exact report data based on the items from the source system, i. e. without rounding to thousands or millions.
The **exact value** will then be displayed on a new row under the rounded value.
### Hiding Rows
Using the data view, rows can be configured so that they are hidden in MS Word and MS Excel.
> **Note:** Hiding rows affects the Outarea and view in MS Word and MS Excel. When rows are hidden in the data view, they are also hidden in MS Excel and MS Word. They remain visible in the data view, however.
>
> The settings of the data view are always of higher priority than the settings in MS Excel.
There are two ways to hide rows:
- **Hiding all rows:**\
\
You can configure how all rows are to be displayed by activating the **Apply condition to hide for all** check box and choosing one of the settings described below.
- **Hiding individual rows:**\
\
You can configure how each individual row is to be displayed by choosing one of the following settings in the last column under **Condition to hide**:
| Setting | Description |
|---|---|
| According to Excel | Rows will be displayed in MS Word just as they have been configured in MS Excel. In other words, if rows are hidden in MS Excel, they will not be displayed in MS Word. They will always remain visible in the data view, however. |
| When a value is rounded down to zero | A row will be automatically hidden if all the values overwritten by the user or the rounded values at hand are equal to zero. |
| When exact values are equal to zero | A row will be automatically hidden if all the exact values it contains (prior to rounding) are equal to zero, or automatically displayed if the values are greater or less than zero. |
| Hide always | The row will always be hidden. |
| Always show | The row will always be displayed. |
---
---
title: "Creating and Editing Chapters"
description: "For a document managed by Lucanet Disclosure Management, you can create as many chapters and chapter levels as you need in the 'Cockpit' to structure the document hierarchically."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/chapter-mgmt-disclmgmt
language: en
last_updated: 2026-05-01
---
# Creating and Editing Chapters
## Overview
For a document managed by **Disclosure Management**, you can create as many chapters and chapter levels as you need to structure the document hierarchically.
Each individual chapter will be displayed in its own row in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md). One Excel document and one Word document can be stored for each chapter.
### Creating Chapters
To create a new chapter:
1. In the overview of a document, click **Manage chapters** to open the workspace:
Detail view of chapter management
2. Click **Add chapter** to create a new chapter. The editing mode of the **Clipboard** area will be activated automatically.
3. Enter the chapter name in the **Clipboard** and then click an empty area in the **Clipboard**.
> **Note:** You can change the chapter name at a later time by clicking the pencil icon .
### Arranging Chapters
You have the following options for arranging chapters:
- **Moving chapters to the chapter structure**: Select the chapter you want to move, and move the chapter from the **Clipboard** to the **Chapter structure** while keeping the right mouse button pressed.
- **Creating subchapters**: To create subchapters, move the desired chapter directly below the superordinate chapter while keeping the right mouse button pressed. A gray dotted box will help you navigate:
Example: moving chapter 5 below chapter 4.2
- **Changing the order of chapters**: By default, once subchapters have been created, only the order of the subchapters can be changed. To also change the order of chapters at the upper level, activate the **Sort chapter** option:
Option for changing the order of chapters
### Deleting Chapters
To delete a chapter, click the recycle bin icon.
> **Note:** **Notes**:
>
> - To delete chapters at the highest level, the **Sort chapter** option must be activated.
> - Chapters for which subchapters have been assigned **cannot** be deleted.
> **Warning:** - Read and write permissions can be defined for chapters. You can only edit chapters for which you have editing permissions. For more information, see chapter [Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md).
> - For information on editing chapters, see [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md) in the section [Edit chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md#editChapter).
---
---
title: "Creating and Editing Columns"
description: "An MS Excel file for Lucanet Disclosure Management must always contain the following three column types to ensure that values are imported in the MS Excel file or existing values are updated."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns
language: en
last_updated: 2026-05-01
---
# Creating and Editing Columns
## Overview
An Excel file for **Disclosure Management** must always contain the following three column types to ensure that values are inserted in the Excel file or existing values are updated:
- **Name columns**
- **Value columns**
- **Programming columns**
A **footnote column** can also be defined. Values written in this column are then added to the Word documents in the Outareas of Excel files.
This section explains what the individual column types mean and how to create them. You will also learn what entries can be used for the programming column.
> **Note:** Instead of creating columns manually, you can also have them detected automatically using AI. See [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md).
> **Warning:** To detect and define outareas and columns using AI, you need at least the **Advanced** license.
## Definitions
The following table shows the various column types and their meaning:
#### Name column (obligatory)
Name columns contain the row labels, i.e. the names of the individual report values, such as the names of items and accounts.
A name column has the following Properties:
- The name of a name column begins with **name\_**.
- The name of a name column is given a **sequential number**.
- The name of a name column can optionally be supplemented with a language abbreviation (e.g., name_1\_en).
> **Note:** Notation for a Name Column
>
> In general, name columns follow the notation below:
>
> name __sequential number\[\_language\]_
>
> **Example**: name_1, name_1\_en
#### Value column
(obligatory)
**Value columns** contain the report values of the current document. In columns that are defined as value columns, values are added and updated after each data import and whenever the Excel file is updated.
A value column has the following properties:
- The name of a value column begins with **value\_**.
- The name of a value column is given a **sequential number** and a **PeriodID**.
- The name of a value column can optionally be supplemented with a language abbreviation (e.g., name_1\_en).
> **Note:** Notation for a Value Column
>
> In general, value columns follow the notation below:
>
> value\_ _sequential number\[\_suffix\]_
>
> **Example**: value_1\_PAJ06, value_1\_PAJ06_de
#### Programming column
(obligatory)
The **programming column** is responsible for programming the contents of the **value\_** column. It contains information such as item numbers or account numbers from the source system and other details for calculating values in value columns.
A programming column has the following properties:
- The name of a programming column begins with **prog\_**.
- The name of a programming column is given a **sequential number** and a **PeriodID**.
> **Note:** Notation of a programming column
>
> In general, programming columns follow the notation below:
>
> prog\_ _sequential number_Suffix_
>
> **Example**: prog_2\_PAJ
> **Warning:** Additional information on the entries permitted in programming columns can be found in [Entries Permitted in the Programming Column](#progcol).
#### Footnote column
(optional)
The **footnote column** can be used to add footnotes to values in the Outareas of Excel files in the Word documents. Footnotes defined for a value in Excel are also displayed in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view.md) and can be edited there.
A footnote column has the following properties:
- The name of a footnote column begins with **footnote\_**.
- The name of a footnote column is assigned a **sequential number** and a **period ID**.
- The name of a footnote column can optionally be supplemented with a language abbreviation (e.g., name_1\_en).
> **Note:** Notation for a footnote column
>
> In general, footnote columns follow the notation below:
>
> footnote\_ _sequential number_period ID_
>
> **Example**: footnote_1\_AJ, footnote_1\_AJ_en
>
> - **1** stands for the value column to which the **footnote column is to apply.**
> - The **value column 1 (value_1)** for a specific period must be assigned **footnote column 1** for the same period **(footnote_1)**.
> - The **value column 2** for the same period **(value_2)** is then assigned the **footnote column 2 (footnote_2)** etc.
> **Tip:** - The desired footnote number is then written in the footnote column behind the value configured before it in the Excel file.
> - The footnote number and the text for the footnote can then be written manually in the Word file under the relevant table.
> - To delete a footnote, the number can be simply deleted in the cell.
## Creating Columns
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, you create columns using the **Mark Area** task pane. You create name columns on the **Name column** tab and value and programming columns on the **Period columns** tab.
#### Creating a Name Column
To create a name column:
1. In MS Excel, select the column that contains the row labels.
2. In the Excel ribbon, click **Mark Area** and open the **Name column** tab in the task pane.
3. Click **+ Add name column**.
The **New Name Column** dialog is displayed. Enter a name and click **Save**.
'New Name Column' dialog
#### Inserting Programming and Value Columns
To insert programming and value columns, use the **Period columns** tab.
1. In MS Excel, select the desired column.
2. In the Excel ribbon, click **Mark Area** and open the **Period columns** tab in the task pane.
3. Click **+ Add period column**.
The context menu of the **+ Add period column** button provides menu items for the periods that have been created in the [Manage Periods](https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt.md) workspace. For each period, a **value column** (**value\_**) and a **programming column** (**prog\_**) are available.
'+ Add period column' context menu with entries for each period
4. From the menu, select the desired programming or value column.
### Office for Desktop
You can create all columns using the Excel ribbon and the buttons shown in the following figure:
Buttons in the Excel ribbon for inserting columns
To create columns:
#### Creating a Name Column
To create a name column:
1. Select the desired column in MS Excel.
2. Click **Name** in the Excel ribbon.
3. Click the desired entry in the menu displayed:
'Name' button with menu on the Excel ribbon
#### Creating a Value Column
To create a value column in an Excel file:
1. Select the desired column in MS Excel.
2. Click **Value** in the Excel ribbon. In the Excel ribbon, menu items are available for the periods that have been created in the [Manage Periods](https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt.md) workspace.
3. Click the desired entry in the menu displayed:
Value' button with menu on the Excel ribbon
> **Note:** To display a **column name** instead of the period ID in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view.md), a column name can be additionally assigned **to each configured value column** in Excel.
>
> To do so, click the cell that contains the column name and do one of the following:
>
> - Choose **Disclosure Management | Insert column name _x_** from the context menu of the cell.
> - Click **Insert** on the Excel ribbon and choose the menu item **Insert column name** _x_.
>
> the "insert column name" command is displayed, which appears if you click 'insert' on excel ribbon icon
> Inserting a column name by means of the ribbon
#### Creating a Programming Column
To create a programming column:
1. Select the desired column in MS Excel.
2. Click **Prog** in the Excel ribbon. In the menu, menu entries are available for all the [Periods](https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt.md) that have been created.
3. Choose the desired entry:
'Prog' button on the Excel ribbon
#### Creating a Footnote Column
To create a footnote column:
1. Select the desired column in MS Excel.
2. Click **Other** on the Excel ribbon. In the menu, menu entries are available for all the [Periods](https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt.md) that have been created.
3. Choose the desired entry:
'Other' button on the Excel ribbon
> **Note:** Alternatively, the footnote column can also be created as follows:
>
> - Using the context menu of a column in Excel
> - In the detail view of a value in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view.md).
## Index of Value and Programming Columns
> **Note:** The indexes (= sequential number) of value and programming columns are interdependent. The **prog_1** column contains the instructions for filling the **value_1** column (e.g. by specifying the corresponding item numbers); **prog_2** contains the instructions for **value_2**, and so on.
>
> For that reason, there must always be the same amount of programming columns as there are value columns.
## Entries Permitted in the Programming Column
The following table lists the entries permitted in the programming column. Other entries are not permitted in the programming columns because every entry could be interpreted as a "fill instruction" for the value column(s) and could therefore overwrite contents.
| Entry | Description |
|---|---|
| #s\[name\] or sequential number | Selection as an **Excel sum formula** (only addition, subtraction, multiplication, and division as well as the Excel sum formula **=SUM()**), e.g. **#s1, #s2, #s\[EBIT\]**. |
| #sf\[name\] or sequential number | **Excel sum formula** with a freely definable number of decimal places. **Note:** Sums that have been programmed using **#sf** are not rounded to the number of decimal places that were specified when checking in the Excel file. Instead, exactly the number of decimal places calculated as the result is applied. |
| #m\[name\] or sequential number | Selection as a manual report value, e.g. **#m1, #m2, #m\[numberemployees\]**. |
| #mf\[name\] or sequential number | Manual report value with a freely definable number of decimal places. **Note:** Numbers that have been programmed using **#mf** are not rounded to the number of decimal places that were specified when checking in the Excel file. Instead, exactly the number of decimal places that the user has entered is applied. |
| #mt\[name\] or sequential number | Manual text value. **Note:** Contents that have been programmed using **#mt** are saved as text and are not available for further calculation. |
| #l and sequential number | Selection as a blank row, e.g. **#l1, #l2**. Disclosure Management does not expect a value here and leaves the row blank in the rounding view. This is mainly used before headings in tables (e.g. assets). |
| #r\[sequential number\] | Reference to another report data record |
| #rf\[sequential number\] | Reference with a freely definable number of decimal places. **Note:** Numbers that have been programmed using **#rf** are not rounded to the number of decimal places that were specified when checking in the Excel file. Instead, exactly the number of decimal places that the reference source contains is applied. |
| 30768000 | Value of account number **30768000**. |
| -30768000 | Inversion of the sign for the value of account number **30768000**. **Note:** Depending on the formatting of the cell, MS Excel may not accept a leading minus sign. You can solve this by starting with an apostrophe, e.g. **'-30768000**. |
| 30768000;30769000 | Sum of the values from accounts **30768000** and **30769000** |
| ; (semicolon) | Separates item/account numbers |
| 30768000;-30769000 | **30768000** minus **30769000** |
| 30111000#9999#CC-EV, 53290000#SEK1 | Subitems/transaction types/exchange rates, etc. are entered using **#** after item numbers. |
> **Warning:** Subsequent changes to designations in **#m** or **#s** programming can lead to problems with validations and references. Validations and references refer to the unique **#m** or **#s** programming. For example, if the sequential index referred to by a reference is changed from **#m6** to **#m7**, the value of the cell in which the **#m6** programming is stored will remain assigned to the reference.
## Example of a Programming Column
An example for programming the **prog\_** column is shown in the following figure:
Example of a P&L table
### Explanations for the Example
The following list contains explanations of the entries in the example table:
#### 5
The entry **30100000** in **row 5** of the **prog\_** column means that the cell \[the report value\] of the **value\_** columns in **row 5** is filled with the value recorded at account/item number **30100000** in the source system.
The minus sign in front of the item number inverts the sign in the table view.
In the example, the entry **-30100000** denotes the sum of revenue recorded as **-59,882 units \[here € million\]** in the source system and presented as **€59,882 million** in **cell G5** for the current year.
#### 12
The entry **#s12** in cell **K12** indicates that the corresponding report values of the **value\_** columns \[so cells **G12** and **I12**\] are calculated using a sum formula.
The formula to be calculated – in this case **=SUM(G7:G11)** and **=SUM(I7:I11)** – is entered in cells **G12** and **I12** of the **value\_** columns.
> **Warning:** The **#s** programming is the only possible entry in the **prog\_** column that requires an additional entry (input in the value cell) for calculation in the **value\_** column.
#### 13
The entry **-31010000;-31020000** in **cell K13** instructs Disclosure Management to invert the sign of the values of accounts **31010000** and **31020000** to a minus sign in the corresponding cells of the **value\_** columns ( **G13** and **I13**), to add them together (separation of item numbers using **;**), and to then present the sum as a rounded figure in accordance with standard commercial practice if necessary. In this way, as many item numbers as required can be added together or subtracted from each other to then present the resulting amount in the **value\_** column.
The account numbers to be added together are always separated by a semicolon.
If only a certain transaction type or the value of a subaccount is to be presented instead of the total amount of an account, this is done by specifying the desired limitation. The limitation \[e.g. **transaction type 300**\] is entered behind the item number using the **#** symbol as a separator, e.g. **30200000#300**\].
> **Warning:** The transaction type must have been imported with the corresponding designation and stored in the Disclosure Management database.
#### 25
The entry **#m25** in cell **K25** defines the entries in cells **G25** and **I25** as numbers to be entered manually by the user. This means that these report values will stay at **0** until a user defines and saves the value for the report values in the [Rounding View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) or in Excel.
#### 31, 32
The rows of the Excel table will only be displayed in the rounding form if a programming instruction has been entered in their **prog\_** column. If the rounding form is to include a **heading** or **blank row** in which no report value is generated or manually entered, this can be done using the entry **#l**. In this case too, the instructions must be given a sequential number like in the **#s** and **#m** programming instructions.
In the example presented, a special calculation operation is performed in rows **31** and **32**, which is not to be recorded and managed by Disclosure Management. For that reason, the entries **#l31** and **#l32** are used in the programming column for these two rows. All entries in the corresponding rows of the **value\_** columns of the Excel table will not be displayed or evaluated in the [Rounding View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) (e.g. not included in sums).
> **Warning:** Sums programmed using **#s** cannot be read in via **#l** programming. In this case, Disclosure Management generates an error message because the values cannot be calculated as a result of the blank row.
---
---
title: "Creating and Editing Excel Files"
description: "MS Excel files form the main basis for using report data from the source system. For report generation purposes, data from the MS Excel files can be embedded in MS Word files in such a way that the values in the report are updated automatically if the MS Excel data are updated, e.g. as a result of an additional data import. To that end, an MS Excel file can be assigned to every chapter of a Disclosure Management document in the Cockpit."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt
language: en
last_updated: 2026-05-01
---
# Creating and Editing Excel Files
## Overview
Excel files form the main basis for using report data from the source system. For report generation purposes, data from the Excel files can be embedded in Word files in such a way that the values in the report are updated automatically if the Excel data are updated, e.g. as a result of an additional data import. To that end, an Excel file can be assigned to every chapter of a Disclosure Management document in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
## Creating Excel Files
Excel files can be created in the **Cockpit** or in the detail view of a chapter. Alternatively, existing files located in the local file directory can be assigned to a chapter to create a new Excel file.
To create an Excel file for a chapter:
1. Click **Cockpit** in the overview or click **Document** in the function bar.
Opening a document in Disclosure Management
2. Click the **three dots icon** the three dots icon at the end of the desired chapter row.
3. Choose **MS Excel | Add Excel file** or **MS Excel | Add external Excel file** from the context menu.
Creating a new Excel file
4. MS Excel will open with a new workbook. As soon as you **Check In** the file, it will be displayed in the **MS Excel** column of the Cockpit.
## Opening Excel Files
Excel files assigned to a chapter can be opened from the **Cockpit** for editing purposes.
To open an Excel file for a chapter:
1. Click **Cockpit** in the overview or click **Document** in the function bar.
Opening a document in Disclosure Management
2. You have two options for opening the file:
- Click the desired file.
- Click the **three dots icon** the three dots icon at the end of the desired chapter row and choose **MS Excel | Open Excel file** from the context menu:
Opening an Excel file from the Cockpit
3. The file will open in MS Excel and can be edited using the **Excel ribbon**.
## Editing Excel Files
Excel files can be edited using the **Excel ribbon**. The Excel ribbon provides specific functions tailored to Disclosure Management:
Excel ribbon for Disclosure Management
> **Note:** The [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md) chapter provides an overview of all the functions available in the Excel ribbon.
> **Warning:** Have you not installed the ribbons yet? Then go to the [Toolbox](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/install-disp-andribbon.md) of Disclosure Management and first install the **Excel ribbon**, the **Word ribbon**, and the **[Dispatcher](https://support.lucanet.com/en/documentation/glossary.md#dispatcher)**. The Dispatcher is responsible for communication between Disclosure Management and the MS Office files.
---
---
title: "Creating and Editing Periods"
description: "For a document managed by Lucanet Disclosure Management, you can create as many periods as you need, e.g. current year or previous year. A period is a time frame for which report data are imported and saved and in which data are aggregated by time."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/period-mgmt-disclmgmt
language: en
last_updated: 2026-05-01
---
# Creating and Editing Periods
## Overview
For a document managed by **Disclosure Management**, you can create as many periods as you need, e.g. current year or previous year. A period is a time frame for which report data are imported and saved and in which data are aggregated by time.
Periods are needed in the following contexts:
- During a data import, the report data are always imported into a specific period.
- The programming in an Excel file is always configured for a specific period.
- When programming an Excel file using the Programming Assistant, the report data for the relevant period are always displayed.
## Creating Periods
To create a new period:
1. In the overview of a document, click **Manage periods** to open the workspace.
2. In the detail view, click **Add period** to create a new period.
Creating a new period
## Configuring Periods
You have the following options for configuring periods:
| Option | Description |
|---------|---------|
| Designation | Period name |
| Start date and end date | Dates on which the period starts and ends |
| Previous period | If applicable, the previous period from which the data are to be carried over when updating the document |
| Description | Optional description of the period |
| Default period | Check box for defining this period as the default period |
> **Note:** **Note regarding a previous period**: If you assign a **Previous period** to a period, this previous period will be indented:
>
> the displays period management workspace. previous period for 'current year' is highlighted in red. icon
> Example of a previous period displayed in the period management workspace
## Editing Periods
To edit or delete a period, navigate to the desired period in the **Manage periods** workspace and click the pencil icon or the trash can icon in the relevant row.
---
---
title: "Creating and Editing Validations"
description: "In Lucanet Disclosure Management, validations are used to check and ensure consistency within a document and the associated calculations. Validations record deviations from the same values within a document at a glance. For this purpose, two values are compared (e.g. assets and liabilities)."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/validation-mgmt-disclmgmt
language: en
last_updated: 2026-05-01
---
# Creating and Editing Validations
## Overview
In **Disclosure Management**, **validations** are used to check and ensure consistency within a document and the associated calculations. **Validations** record deviations from values within a document at a glance. For this purpose, two values are compared (e.g. **assets** and **liabilities**).
For example, the value of an item number from the **Disclosure Management** database can be validated against the total of the reporting values that make up this item number.
Validations can be created across tables from all the reporting data within a document.
## Opening Workspace
In the overview of a document, click **Manage validations** to open the workspace.
Managing validations in Disclosure Management
## Options in the Validation List
You can use the **three-dot icon** menu to edit, copy or delete existing validations:
Functions for created validations
## Creating Validation
To create a new validation:
1. If necessary, open the **Manage validations** workspace.
2. Click the add icon to create a new validation. The **Add validation** area is displayed:
Configure a new validation
3. Specify the details of the validation (see section [Configuring Validation](#configVal)).
4. Click **Add** to create the new validation.
## Configuring Validation
When configuring a validation, the following options are available:
| Option | Description |
|---------|---------|
| Left validation side | **Chapter** Chapter to be validated. The drop-down list includes all chapters of the current document. **Column** Value column containing the value to be validated **Period** Period from which the value is to be validated The drop-down list includes all periods from the specified **column**. **Value** Value to be validated. The drop-down list includes all values contained in the specified **column** and for the specified **period**. |
| Right validation side | **Chapter** Chapter to be validated. The drop-down list includes all chapters of the current document. **Column** Value column containing the value to be validated **Period** Period from which the value is to be validated The drop-down list includes all periods belonging to the specified **column**. **Value** Value to be validated. The drop-down list includes all values contained in the specified **column** and for the specified **period**. |
| Create validation for all available periods | Automatically creates validations for all related periods in the table based on the specified validation details (e.g. the validations **current year** against **current year** and **previous year** against **previous year**). As soon as this check box is activated, the **Period** drop-down list is deactivated. |
| Number of decimal places | Number of decimal places to be taken into account during validation. When the value **Automatic** is selected, the setting from the associated Excel spreadsheet is used for validation. |
> **Note:** Validations can also be tracked in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md) and in the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) as soon as the **Validations** column is displayed there. Validations are always displayed in the chapter that was selected as the **left validation side** during configuration of the validation:
>
> the displays a section of with columns 'chapter name', 'status', 'validations'. displays two validations, one shows a warning. both validations are outlined in red. icon
> Display of a validation in the Cockpit
## Troubleshooting
The list of validations shows the validations created with the **left validation side** and **right validation side** and the respective **value**. If the values differ, an error is indicated by the warning icon.
> **Warning:** If incorrect validations are displayed, this means there is a deviation between the two compared values. Incorrect validations can be corrected as follows, for example:
>
> - Check the validation for plausibility. Were the correct values compared?
> - Edit the corresponding values in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md). Values may need to be adjust or rounded because values have been compared with different number formats.
> - Check the [Programming](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-values.md) of the Excel table. Were the correct values and arithmetical operations used for calculated values?
---
---
title: "Creating and Editing Word Files"
description: "Word documents play a key role in Lucanet Disclosure Management when it comes to creating a business report. The final result document is built using them. Word documents can be used to make the corporate design and texts available for the desired result document. In Word documents, the Excel tables maintained in Disclosure Management are also published. A Word file can be stored for each chapter of a Disclosure Management document. Word files contain the Word ribbon, which provides specific functions for editing files."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file
language: en
last_updated: 2026-05-01
---
# Creating and Editing Word Files
## Overview
Word documents play a key role in **Disclosure Management** when it comes to creating a business report. The final result document is built using them. Word documents can be used to make the corporate design and texts available for the desired result document. In Word documents, the Excel tables maintained in Disclosure Management are also published.
A Word file can be stored for each chapter of a Disclosure Management document.
Word files contain the **Word ribbon**, which provides specific functions for editing files.
## Creating Word Files
Word files can be created in the **Cockpit** or in the detail view of a chapter. Alternatively, existing files located in the local file directory can be assigned to a chapter to create a new Word file.
To create a Word file for a chapter:
1. Click **Cockpit** in the **overview** or click **Document** in the function bar:
Open a document in Disclosure Management
2. Click the **three dots icon** the three dots icon at the end of the desired chapter row.
3. Choose **MS Word | Add Word file** or **MS Word | Add external Word file** from the context menu.
Create a Word file in the Cockpit
4. MS Word will open with a new file. As soon as you **Check In** the file, it will be displayed in the **MS Word** column of the Cockpit.
## Opening Word Files
Word files assigned to a chapter can be opened from the **Cockpit** for editing purposes.
To open a Word file for a chapter:
1. Click **Cockpit** in the overview or click **Document** in the function bar.
Opening a document in Disclosure Management
2. You have two options for opening a **Word file** in the Cockpit:
- Click the desired Word file in the **MS Word** column.
- Click the **three dots icon** the three dots icon at the end of the desired chapter row and choose **MS Word | Open Word file** from the context menu.\
\
Opening a Word file from the Cockpit
\
\
The file will open in MS Word and can be edited using the **Word ribbon**.
> **Note:** Word files can also be opened from the [Detail View of a Chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md).
## Editing Word Files
Word files can be edited using the **Word ribbon**. The Word ribbon provides specific functions tailored to Disclosure Management:
Word ribbon for Disclosure Management
- Among other functions, the Word ribbon contains a function for inserting any desired Excel tables in a Word document.
- In addition to Excel tables, [Text Values](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word-use-variables.md), [Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md), [XBRL Tags](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags.md), and more can be inserted in a Word document easily and conveniently using the Word ribbon.
> **Note:** The [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md) chapter provides an overview of all the functions available in the Word ribbon.
> **Note:** A specific Word template can be stored for each document in Lucanet Disclosure Management.
>
> To assign a Word template to a document, you must open the **Configure document** workspace and add a Word template in the **MS Word** section (see also [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md)).
>
> This is also where you can use the download icon to save an already assigned Word template locally (e.g. to use it in another document).
>
> the shows 'configure document' workspace. 'ms word' area is displayed. options for format template are outlined in red. icon
> Assign, save, or delete format template for MS Word
---
---
title: "Creating and Inserting Document Variables"
description: "For frequently used texts or formulations in Disclosure Management documents, document variables can be used, which can be retrieved and inserted in every MS Excel or MS Word file via the MS Word or MS Excel ribbon."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable
language: en
last_updated: 2026-09-07
---
# Creating and Inserting Document Variables
## Overview
For frequently used texts or formulations in Disclosure Management documents, **document variables** can be used, which can be retrieved and inserted in every Excel or Word file via the **Word** or **Excel ribbon**.
In Disclosure Management, predefined document variables are available for the **year**, **previous year**, and **reporting date**. Additional custom variables can be created in the **Variables** workspace.
> **Note:** The date format of date variables (such as **reporting date**) can be configured in the [document settings](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) — with a leading zero (for example, `30.06.`) or without (for example, `30.6.`).
> **Tip:** Document variables can also be used in the text parameters of an import processing, for example to filter on a reporting period that changes when the report is rolled forward. For more information, see [Using Document Variables in Text Parameters](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt.md#using-document-variables-in-text-parameters).
## Creating Document Variables
Document variables are created in the **Variables** workspace. The **Variables** workspace is displayed as follows, for example:
Workspace 'Variables'
To create a new variable:
1. Click **Add new variable**.
2. Enter the **Name**, **Description** (optional), and **Value** of the variable.
3. Click **Create**.
The new variable is created and can be inserted into a Word document (see following section).
## Inserting Document Variable
How you insert a document variable depends on the Office variant you use. In **Office for the Web** and **Office Native**, the user guidance and interface are identical.
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, proceed as follows to insert a document variable:
1. Click the **Document Variables** button.
'Document Variables' button in the ribbon
2. The **Document Variables** task pane opens on the right. The **List of variable(s)** section lists all available document variables with their **Name**, **Value**, and **Description**. Initially, it contains document variables for the **current year**, **previous year**, and **reporting date**.
'Document Variables' task pane
3. In the Excel worksheet, select the cell where you want to insert the document variable.
The selected cell is shown in the **Selection** area.
4. For the desired document variable, click **Assign**.
The document variable is inserted into the selected cell and its status changes to **Assigned**. A document variable can be assigned to only one cell at a time.
> **Note:** To remove a document variable's assignment, select the cell containing the document variable and click **Detach** in the **Selection** area. The document variable is removed from the cell and can then be assigned to another cell.
>
> the removing a document variable's assignment via 'detach' icon
> Removing a document variable's assignment
> **Note:** In **Office for the Web** and **Office Native**, you can highlight inserted document variables in a Word document: on the **DM-Content** tab, click **Set** and select the **Document Variables** entry. Use **Remove | Document Variables** to remove the highlight again (see [Ribbons for MS Office for the Web](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web.md#highlight)).
### Office for Desktop
In **Office for Desktop**, insert a document variable into Excel or Word documents as follows:
1. Select a cell in an Excel file or place the cursor at the desired position in a Word file.
2. Click **Insert Document Variable** in the Excel or Word ribbon.
Inserting a document variable via the Word ribbon
The **Insert Document Variable** dialog will be displayed. The dialog lists all the document variables that have already been created, along with their **Name**, **Value**, and **Description**. Initially, this will contain document variables for the **current year**, **previous year**, and **reporting date**:
'Insert Document Variable' in MS Word
3. Select the desired document variable.
4. Click **Insert document variable**.
> **Note:** When you insert document variables in MS Excel, corresponding names are created automatically for the relevant cells (see [Names and Name Extensions in MS Excel](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/setup-excel-file.md)).
---
---
title: "Creating Result Document"
description: "A complete or partial result document can be generated at any time in Lucanet Disclosure Management. A result document contains the current status of an annual report stored in Disclosure Management."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document
language: en
last_updated: 2026-05-01
---
# Creating Result Documents
## Overview
A complete or partial result document can be generated at any time in Disclosure Management. A **result document** contains the current status of a document stored in Disclosure Management.
## Creating a Result Document
To create a result document:
1. In the overview of a document, click on the **Creation** workspace.
The **Creation** workspace is displayed:
Creating result document
2. Configure the result document (see section [Configuring Result Document](#resdoc)).
3. Click **Create result document**.
## Configuring a Result Document
The following options are available for the result document:
| Option | Description |
|---|---|
| Result document name | Name of the result document. |
| Language | Language of the result document. All languages defined in the [Configuring Documents](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) workspace are offered. |
| Structure variant | Version of the result document
**Note:** **Structures** are a named selection and arrangement of chapters, including their own section breaks, which is used to generate a specific report version from a document. A single source document can contain several **structures**, e.g. standard structure, short report, management report, notes, etc., from which different Word result documents can be generated. |
| General | **Control report (add file name)**: The combined elements of the result document are labeled with the name of their chapter of origin. This allows you to quickly see from which chapter and therefore from which Word or Excel file a particular element of the result document originates.
**Write user name in the header**: The name of the creator and the time of creation are written in the header of the result document.
**Remove values**: All values under the control of Disclosure Management are replaced by a zero. |
| Word functions | **Accept all changes and stop tracking**: All tracked changes in the Word files are accepted and change tracking is then ended.
**Remove hidden text**: The hidden texts contained in the Word files are not included in the result document.
**Remove comments**: The comments contained in the Word files are not included in the result document.
**Remove content controls**: All content controls are removed from the generated result document. The content within them (text, values, and so on) is preserved—only the control wrapper is removed. This option applies to Word result documents only and does not affect the source documents. |
| XBRL | **Add XBRL mapping**: Adds XBRL mapping to the created result document. The Word file can then be loaded into the XBRL tagger.
If this check box is not activated, no XBRL tags are transferred to the result document. |
| Typography | **Apply typographic correction**: Applies typographic corrections to the result document, for example correcting quotation marks and dashes.
**Highlight typographic changes**: The typographic corrections made are highlighted in the result document. |
| Content groups | Defines which [content groups](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md#content-groups) the result document is created for. Select the check box of a content group so that all sections assigned to that content group are included in the result document. A section is included in the result document as soon as it is assigned to at least one of the selected content groups.
**Highlight with group color**: Displayed when a content group is selected. Highlights the sections assigned to that content group in the result document using its color.
**Note:** If no content group is selected, all sections are included in the result document regardless of their content group assignment. Sections that are not assigned to any content group are always included.
|
| Translation document | **Generate as translation document**: The result document contains the content in the language defined above, while the out-areas for tables and charts are switched to the selected target language. This makes the document suitable for external translation; afterward, the translated document can be reimported into the target language via the history. |
| Output area language | Target language for the output areas (tables and charts) in the translation document. This drop-down list is displayed when **Generate as translation document** is selected. |
> **Note:** Creating a result document automatically also runs the Layout Check for the included Word chapters. No separate option is required for this.
>
> For more information about the Layout Check, see [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/layout-check.md) and [Reviewing Layout Check Violations](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md).
## Creating a Partial Result Document
You can generate a partial result document from any chapter of a document at any time. To do this, you must switch to the **cockpit** and follow the [steps described here](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md#pd).
---
---
title: "Dashboard"
description: "The dashboard is the opening screen in Lucanet Disclosure Management. From the dashboard, you can create new documents and view all the documents that have been created in Disclosure Management. You can also open documents from the dashboard."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt
language: en
last_updated: 2026-05-01
---
# Dashboard
## Overview
The **dashboard** is the opening screen in Disclosure Management. From the dashboard, you can create new documents and view all the documents that have been created in Disclosure Management. You can also open documents from the dashboard.
## Options in the Dashboard
The dashboard is displayed as follows:
Structure of the dashboard and available options
The following options are available in the dashboard:
| Options | Description |
| --- | --- |
| Filter or search for documents | Options for filtering documents by year or searching for specific documents |
| Import document extracts | Option for importing previously extracted documents with the **SNE** file extension |
| Create documents | Option for creating a new document. Enter the **document name** and define the **reporting date** by which the document needs to be completed. Go to **Workflow** and apply the **Default Workflow**, then click **Save**. The document will now be displayed in the **Document overview**. |
| Open documents | To open and configure the required document, click it in the document overview. For more information, see [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) |
| Sort documents | Option to sort documents by document name, reporting date or creation date, in either ascending or descending order |
| Edit or delete documents | Option for changing the document name or reporting date, or deleting the document |
> **Note:** Disclosure Management enables you to create extracts of documents so you can send them to Amana Consulting for auditing or inspection, for example. For more information, see [Rolling Forward or Copying a Document](https://support.lucanet.com/en/documentation/disclosure-management/perpetuate-copy-doc-disclmgmt.md).
## Extracting Multiple Documents into One File
> **Warning:** To extract multiple documents into one file, you must have one of the following roles:
>
> - Global Administrator
> - Document Administrator (for the documents you have permissions for)
>
> Without one of the mentioned roles, the **Extract documents to file** button is deactivated. A tooltip with a message about the missing permission is displayed.
To extract multiple documents into one file:
1. Hold down the **CTRL** key and select the documents you want to extract into a file.
2. Do one of the following:
- Right-click the three-dot icon and select **Extract**.
- Click the **Extract documents to file** button.
Extracting multiple documents into a single file
3. Once the extraction is complete, a new message will be displayed in the [notification window](https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt/notifications.md), from which you can download the extracted report.
---
---
title: "Defining a Data Source"
description: "Data sources are the basis for importing data from a source system or a source file into Lucanet Disclosure Management. To import the desired data into Disclosure Management and use it in reports, the data source must be configured accordingly in the Import Management area."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt
language: en
last_updated: 2026-09-08
---
# Defining a Data Source
## Overview
Data sources are the basis for importing data from a source system or a source file into Disclosure Management. To import the desired data into Disclosure Management and use it in reports, the data source must be configured accordingly in the **Import Management** area.
The following is defined during configuration of the data source:
- Which data from the data source should be taken into account for the import (**Parameterization**)
- Which columns contain which data (**Mapping**)
- Whether and how certain data should be converted or enriched during the import (**Transformation**)
- Whether and how certain data should be summarized during the import (**Aggregation**)
The configuration of the data source depends on the type of data source (i.e. whether you obtain data from a **file**, from a **Lucanet database** or from **Lucanet ESG reporting**).
> **Warning:** The **Import Management** functional area is only activated for users who have been assigned the **global administrator** role in Disclosure Management role management, as only this user role is authorized to manage imports (**ImportData**). (For additional information about user roles in Disclosure Management, see [Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md))
## Prerequisites
To create a data source, you must first define a connection for this data source in the **Connections** workspace. For additional information, see [Defining a Connection to a Data Source](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-source-connection-disclmgmt.md). Several data sources can be created with the same connection.
## Creating a Data Source
Data sources are created and configured in the Disclosure Management **Import Management** area:
Creating a data source
To create a data source:
1. Click in the function bar on **Import Management** and then in the overview on **Data sources** to open the workspace.
2. Click **Create new data source**.
3. Configure the data source as described in the following sections.
4. Save the data source.
> **Tip:** An overview of all data sources already created is displayed on the left-hand side of the detail view. From here, you can:
>
> - Create a new data source
> - Select and edit existing data sources
>
> By default, a data source for **importing from Lucanet ESG Reporting** is already created in the overview, which is preconfigured and can be used by all users who have licensed Lucanet ESG Reporting. For additional information on this data source see section [Default Data Source for Importing from Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt/.md#defaultds).
## Configuring a Data Source
To configure a data source, you have to open the edit mode by clicking **Edit** in the data source's detail view.
### General Settings
General settings of a data source
| Option | Description |
|---|---|
| Name | Name of the data source |
| Connection | Selection of the connection to the data source that was previously configured in the **Connections** workspace. |
| Description | Optional description for the connection |
| Import parameters | Area for defining the import parameters (see section [Defining Import Parameters](#Imptparam)). |
| Create | Creates the data source or saves the changes made. |
> **Note:** - Several data sources can be created with the same connection.
> - When importing an Excel file, a separate data source must be created for each worksheet.
> - As soon as the connection has been selected, further configuration fields and commands are displayed.
## Detail view of a data source
The detail view of a data source is displayed as follows, for example:
Detail view of a data source
The following functions are available in the detailed view:
- Click **Preview** to display a preview of the imported data before and after applying the configuration created under Mappings (see section [Displaying a Preview of the Imported Data](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt/.md#Preview)).
- Click **Edit** in the **General settings** area if you want to edit the general properties and/or the [Import parameters](#Imptparam).
- Click **Edit** in the **Mappings** section if you want to create new mappings or edit or delete existing mappings.\
\
The area **Mappings** is used to create one or more mappings for the data source, i.e. Specifications on how the imported data should be assigned within Disclosure Management.\
\
**Transformations** and **aggregations** of the data to be imported can also be configured via the configuration of the mappings (see section [Defining Mapping](#mappings)).
- You can also delete the data source, save it, and cancel editing of the details.
### Defining Import Parameters
You can use import parameters to specify which data should be imported from a data source. The required parameters for this depend on the type of data source (i.e. whether you obtain data from a **file**, from a **Lucanet database** or from **Lucanet ESG reporting**).
In the data source interface, click **Import parameters** to open the configuration of the import parameters.
An explanation of the parameters that you must or can define for an import is provided on the user interface.
### Defining Parameters for Importing from a File
> **Note:** When importing data from an **XLSX file**:
>
> - The parameters **Worksheet** and **Header** are required.
> - All other parameters are **optional**. If you do not specify anything, all rows and columns containing data on the specified worksheet are imported.
>
> - When importing an XLSX file, a separate data source must be created **for each worksheet** to be imported.
Parameters for Importing from an Excel File
> **Warning:** No additional parameters are required when **importing a CSV file**.
### Defining Parameters for Importing from a Lucanet Database
> **Note:** When **importing from a Lucanet database**:
>
> - You can select all elements available in the Lucanet database from which you want to import.
> - If multiple selection is possible, check boxes for selecting the individual elements are displayed in the drop-down lists.
> - Select the **Can be overwritten** check box if the parameters you specify here can be overwritten by parameters you specify when performing the import. For additional information on parameterization when performing the import, see [Configuring and Executing a Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt.md).
> **Note:** All import parameters are described in the user interface.
### Required Parameters
Mandatory parameters for importing from a Lucanet database
### Optional Parameters
Optional parameters for importing from a Lucanet database
### Parameters for Importing from ESG Reporting
Import parameters for importing from Lucanet ESG Reporting
**Description**
**Report name**
Select the ESG report from which data is to be imported.
> **Note:** - All reports that have been created in the **Lucanet ESG Reporting** solution and for which the data has already been aggregated are available for selection.\
> \
> For further information on data aggregation of an ESG report can be found in [Aggregating Data](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md) chapter of the Lucanet ESG Reporting solution documentation.
> - The predefined default data source **ESG Reporting Datasource** is available in the overview of data sources and can be used by all users who have licensed Lucanet ESG Reporting (see section [Default Data Source for Importing from Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt/.md#defaultds))
### Defining Mapping
**Mappings** are required for subsequent use of the imported data in Disclosure Management.
Mappings are used to define which columns of an imported Excel file contain which values. The columns are stored when programming an Excel file that is used in a report so that the correct data is inserted in the report. For additional information on programming the reporting data in an Excel file, see [Inserting Report Values in MS Excel](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-values.md).
In addition, one or more **transformations** and/or **aggregations** can optionally be defined for each mapping (i.e. whether the data should be converted, enriched and/or summarized before import).
Several mappings can be defined for a data source and selected during the import process. For example, a mapping can be created for different periods or periodicities.
All existing mappings are shown in the **Mappings** area. By clicking **Edit**, you can create, edit or delete new mappings:
Edit Mappings
### Creating and Configuring Mappings
To create a mapping, proceed as follows:
1. In the detail view of the desired data source, click **Edit** in the **Mappings** area.
2. In the following view, click **Add mapping**. The following dialog is displayed:
Edit mapping
3. Then configure the fields for the mapping as follows:
| Option | Description |
|---|---|
| Name | Name of the mapping. |
| Description | Optional description for the mapping |
| Name column | Select the range in the data source that contains the names to be inserted in the name column of the programmed Excel file used in the report (e.g. the names of the accounts and/or items or the page of the balance sheet). |
| Value column | Select the range in the data source that contains the values to be inserted into the value column of the programmed Excel file used in the report (e.g. values in a specific reporting year). |
| Programming column | Select the range in the data source that contains unique identifiers to be inserted into programming column of the programmed Excel file used in the report (e.g. account numbers). |
| Importing texts | Activate this option if cells with text are to be included in the import. |
| Import zero values | Activate this option if cells with zero values are to be taken into account during the import. |
### Configuring Transformations (Optional)
You can use transformations to specify whether source data should be converted or enriched before import. Transformations always create a new column in the imported data.
To create a transformation within a mapping:
1. In the detail view of the desired data source, click **Edit**.
2. In the following view, click **Add mapping** or select **Edit** in the context menu of the **three-dot icon** the three dot icon of an existing mapping.
Adding or editing a mapping
3. Edit the displayed fields.
An explanation of the fields is provided on the user interface.
In a text parameter, you can enter a document variable instead of a fixed value (see [Using Document Variables in Text Parameters](#using-document-variables-in-text-parameters)).
4. Click the **Preview** button and check the **Imported items** tab in the displayed window to determine whether the transformation provides the desired result.
The following transformation types are currently available:
#### Suffix
The **Suffix** transformation is used to append a definable text to a value and write it to a new column.
Instead of a fixed value, the **Suffix** parameter can take its value from a document variable (see [Using Document Variables in Text Parameters](#using-document-variables-in-text-parameters)).
Configuration of the 'Suffix' transformation
**Example**
**New column name**: Item name_Group
**Source column**: Item name
**Suffix**: \_Group
**Column before transformation**:
Column in Excel before transformation 'Suffix'
**New column after transformation**:
Column in Excel after transformation 'Suffix'
#### Join
The transformation type **Join** is used to connect the values of two selectable columns and write them to a new column.
Configuration of the 'Join' transformation
**Example**
**New column name**: Account_with_Transaction_type
**First source column**: Account number
**Second source column**: Transaction type
**Separator**: #
**Columns before transformation**:
Columns in Excel before transformation 'Join'
**New column after transformation**:
Column in Excel after transformation 'Join'
#### Replace
The transformation type **Replace** is used to replace text in a source column and write the result to a new column. All occurrences of the text entered in **Remove text** (mandatory) are replaced by the text entered in **Insert text** (optional). If you leave **Insert text** empty, the matched text is removed without replacement. You can use this, for example, to generate clean programming values from a raw source column.
Instead of a fixed value, the **Remove text** and **Insert text** parameters can take their values from a document variable (see [Using Document Variables in Text Parameters](#using-document-variables-in-text-parameters)).
Configuration of the 'Replace' transformation
**Example**
**New column name**: SN-Nummer
**Source column**: Column1
**Remove text**: Programmierung\_
**Insert text**: SN-
**Source data before transformation**:
Source data before transformation 'Replace'
**New column after transformation**:
Processed data after transformation 'Replace'
#### Multiply
The transformation type **Multiply** is used to multiply each numeric value of a source column by a defined **Factor** and write the result to a new column. For example, you can use the factor `1000` to convert values reported in thousands into single units, or the factor `-1` to flip the sign of a column. Non-numeric values are skipped (left empty in the result column) and empty cells remain empty. The result is formatted according to the same decimal and grouping rules as the **Sum** aggregation.
Configuration of the 'Multiply' transformation
**Example**
**New column name**: Wert x -1
**Source column**: Column5
**Factor**: -1
**Source data before transformation**:
Source data before transformation 'Multiply'
**New column after transformation**:
Processed data after transformation 'Multiply'
#### Substring
The transformation type **Substring** is used to extract a defined portion of a text value from a source column and write it to a new column. The extraction begins at the position entered in **Start** (1-based, so the first character is position 1) and returns the number of characters entered in **Amount of characters**. If the requested number of characters exceeds the remaining length of the value, the entire remaining text is returned. If the start position is beyond the length of the value, the result is empty. Both fields accept whole numbers greater than 0.
Configuration of the 'Substring' transformation
**Example**
**New column name**: Laufende Nummer
**Source column**: Column1
**Start**: 16
**Amount of characters**: 5
**Source data before transformation**:
Source data before transformation 'Substring'
**New column after transformation**:
Processed data after transformation 'Substring'
#### Split
The transformation type **Split** is used to split a text value in a source column into parts using a defined separator and write the part at a specified index into a new column. Use this transformation to extract a specific segment from a composite key or delimited value – for example, to read the country code out of a value such as "Berlin;DE;10115".
After selecting **Split** as the transformation type, the following additional fields are displayed:
| Field | Description |
|---|---|
| Delimiter | The character or string that separates the parts of the source value (for example ";", "-", "\|"). Accepts any non-empty string, including special characters and whitespace. |
| Section | Which part of the split value is written into the new column (1-based: first part = 1). Accepts only integers greater than 0. |
> **Note:** - Each **Split** transformation produces exactly one new column. To extract multiple parts from the same source value, add multiple Split transformations.
> - If the source value does not contain the separator, the entire value is treated as part 1; Section 2 or higher returns an empty string.
> - If the Section index exceeds the number of parts, the new column receives an empty string – no error is raised.
> - Leading and trailing whitespace within split parts is preserved as-is.
Configuration of the 'Split' transformation
**Example**
**New column name**: Country code
**Source column**: Location
**Separator**: ;
**Section**: 2
**Source data before transformation**:
Source data before transformation 'Split'
**New column after transformation**:
Processed data after transformation 'Split'
#### Take over
The transformation type **Take over** processes a source column row by row, top to bottom, and writes a value into a new column for every row:
- If the source cell in the current row is **non-empty**, that value is copied unchanged into the new column.
- If the source cell in the current row is **empty**, the new column receives the value from the most recent non-empty source cell above.
Use this transformation to flatten grouped or header-style source data – for example, when a parent account name appears only once at the top of a group and the rows below are left blank.
> **Note:** - If the first rows have no non-empty source value above them, the new column remains empty for those rows.
> - A value counts as empty when it is null, an empty string, or contains only whitespace.
> - The source column itself is not modified; the filled values are written exclusively into the new column.
> - The fill value updates every time a non-empty source cell is encountered. The row order at the time of execution depends on any preceding sort or filter processings.
Configuration of the 'Take over' transformation
**Example**
**New column name**: Account group
**Source column**: Group header
**Source data before transformation**:
Source data before transformation 'Take over'
**New column after transformation**:
Processed data after transformation 'Take over'
### Configuring Aggregations (Optional)
You can use **aggregations** to specify whether source data should be aggregated (i.e. summarized) before import.
To create an aggregation within a mapping:
1. In the detail view of the desired data source, click **Edit**.
2. In the following view, click **Add mapping** or select **Edit** in the context menu of the **three-dot icon** the three dot icon of an existing mapping.
Adding or editing a mapping
3. Edit the displayed fields.
An explanation of the fields is provided on the user interface.
In a text parameter, you can enter a document variable instead of a fixed value (see [Using Document Variables in Text Parameters](#using-document-variables-in-text-parameters)).
4. Click the **Preview** button and check the **Imported items** tab in the displayed window to determine whether the aggregation provides the desired result.
The following aggregation types are currently available:
#### Sum
You can use the **Sum** aggregation to total all numerical values in the value column – grouped according to the source column to which the total function is applied.
Configuration of the aggregation of type 'Sum'
**Example**
**Source column**: Column2
**Columns before aggregation**:
Column in Excel before aggregation 'Sum'
**Columns after aggregation**:
Column in Excel after aggregation 'Sum'
#### Filter
You can use the **Filter** aggregation type to import only values that match the defined filter condition.
Instead of a fixed value, the **Filter** parameter can take its value from a document variable (see [Using Document Variables in Text Parameters](#using-document-variables-in-text-parameters)).
The condition must be entered manually into the **Filter** field. The filter value or text must be placed in double inverted commas.
The following arithmetical and logical operators are available for defining the filter condition:
**Arithmetical operators for text filters**:
- '**=**' imports all rows that match the specified filter text exactly.
- **<** imports all rows whose text comes after the specified filter text in their relative position in the alphabetical sort order.
- **<=** imports all rows whose text in their relative position in the alphabetical sort order is in the same position or after the specified filter text.
- **>** imports all rows whose text comes before the specified filter text in their relative position in the alphabetical sort order.
- **>=** imports all rows whose text in their relative position in the alphabetical sort order is in the same position or before the specified filter text.
- **<>** displays all rows that do not match the specified filter text exactly.
- **contains** displays all rows that contain the specified filter text at any location.
- **notContains** displays all rows that do not contain the specified filter text.
**Arithmetical operators for number filters:**
- **<** displays all rows with a value greater than the specified number. If the value in a row is a text, it is not taken into account.
- **<=** displays all rows with a value greater than or equal to the specified number. If the value in a row is a text, it is not taken into account.
- **>** displays all rows with a value that is less than the specified number. If the value in a row is a text, it is not taken into account.
- **>=** displays all rows with a value less than or equal to the specified number. If the value in a row is a text, it is not taken into account.
- **<>** displays all rows that do not match the specified filter text exactly
- **contains** displays all rows that contain the specified filter value at any location
- **notContains** displays all rows that do not contain the specified filter value
**Logical operators:**
Filter conditions can be linked with **and** and **or**.
Configuration of the aggregation of type 'Filter'
**Example**
**Source column**: Transaction type
**Filter expression:** contains "110"
**Column before aggregation**:
Column in Excel before aggregation 'Filter'
**Column after aggregation**:
Column in Excel after aggregation 'Filter'
#### Filter not empty
The **Filter not empty** aggregation type removes every row whose value in the selected source column is empty. A value counts as empty when it is null, an empty string, or contains only whitespace (spaces, tabs). Rows with a non-whitespace value in the source column are kept unchanged. Other columns are not modified.
> **Note:** **Filter not empty** does not create a new column – the **New column name** field is not displayed for this aggregation type.
Configuration of the aggregation 'Filter not empty'
**Example**
**Aggregation name**: Remove empty keys
**Source column**: Programming key
**Rows before aggregation**:
Source data before aggregation 'Filter not empty'
**Rows after aggregation**:
Processed data after aggregation 'Filter not empty'
#### Filter numeric
The **Filter numeric** aggregation type keeps only rows whose value in the selected source column is numeric. A value counts as numeric when it can be parsed as a decimal number according to the connector's number format settings (consistent with the **Sum** aggregation). Negative values and decimal values count as numeric. Empty cells, text values, and values containing non-numeric characters are not counted as numeric and the corresponding rows are removed. Other columns are not modified.
> **Note:** **Filter numeric** does not create a new column – the **New column name** field is not displayed for this aggregation type.
Configuration of the aggregation of type 'Filter numeric'
**Example**
**Aggregation name**: Keep numeric amounts only
**Source column**: Amount
**Rows before aggregation**:
Source data before aggregation 'Filter numeric'
**Rows after aggregation**:
Processed data after aggregation 'Filter numeric'
## Using Document Variables in Text Parameters
Instead of entering a fixed value, you can have a text parameter take its value from a **document variable**. This is useful when a report is rolled forward: you change the document variable once, instead of editing the value in every affected mapping.
Document variables are supported in the text parameters of the following processing types:
| Processing type | Parameter |
|---|---|
| Filter | **Filter** |
| Prefix | **Prefix** |
| Suffix | **Suffix** |
| Replace | **Remove text**, **Insert text** |
To insert a document variable, write its name between two percent signs — for example `%quarter%`. To write a literal percent sign, use two percent signs (`%%`).
A variable can appear anywhere within a parameter, and a parameter can contain more than one. For a document variable `year` with the value `2025`, the filter expression `contains "FY%year%"` matches rows containing `FY2025`.
The field shows a hint explaining the syntax, and an unclosed reference such as `="%quarter` is reported as a syntax error before you can save.
> **Note:** The stored configuration always keeps the variable, not the value it resolved to. If the document variable `quarter` changes from `Q3` to `Q4`, the next import filters on `Q4` without any change to the mapping.
> **Warning:** The value of a document variable is always compared as a single piece of text. It is never interpreted as part of the filter expression.
>
> This matters when a value contains the words **and** or **or**, which are otherwise logical operators (see section [Filter](#filter)). A document variable holding `Research and Development` matches rows whose value is exactly `Research and Development` — the **and** is not treated as an operator.
The following also applies:
- The document variable must exist in the document that the import runs in. If it cannot be resolved, the import fails and names the variable concerned.
- A document variable with an empty value resolves to an empty text, so the parameter is applied to empty values.
- In the **Import management** area, the preview shows the variable as written, for example `%quarter%`. Import management is not tied to a single document, so no document variables are available there. In a document — in the mapping preview and during the actual import — the variable is resolved as usual.
For information on creating document variables, see [Creating and Inserting Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md).
## Displaying Preview of the Imported Data
To check whether the configured mapping(s) are configured correctly and deliver the desired result, you can display a preview of the imported data in a separate window.
To do this, click **Open preview in new window** in the data source interface.
The preview of the imported data is displayed as follows, for example:
Preview of the data import
The following elements are displayed in the import preview:
| Element | Description |
|---------|---------|
| Import preview for | Name of the data source |
| Mapping for the preview | Selection of the mapping for which a preview of the import is to be displayed. All mappings defined in the data source can be selected. |
| 'Source data' tab | Source data that serves as the basis for the import |
| 'Processed data' tab | Preview of the data after applying transformations and/or aggregations that may have been configured. If no aggregations and/or transformations have been configured, the same data are displayed on this tab as on the **Source data** tab. |
| 'Imported data' tab | Preview of the data that will be imported at the end. |
| Last updated | Time of the last update of the import preview |
| Update | Click this button if you want to execute the import preview again. |
## Default Data Source for Importing from Lucanet ESG Reporting
To avoid additional configuration effort, a predefined default data source is already available for importing report data from Lucanet ESG Reporting.
The following data is imported from an ESG report using this data source:
- The **question** from the ESG questionnaire in text form (**Name** column)
- The **unique ID** of the entry that is required for programming the Excel file in which the value is to be displayed. (The ID is made up of the number of the question from the ESG questionnaire with the row and column index of the CSV file that is generated in the background when the ESG reporting data is aggregated)
- The **value** that is stored in the report for this entry
In the Import preview, the imported data is displayed as follows, for example:
Example of an import preview with the ESG reporting data source
To use the default data source:
1. Click on the data source **ESG Reporting Datasource** in the **Data sources** area.
2. In the **Import parameters** area, select the ESG report from which you want to import the data from the drop-down list.
3. If necessary, display a preview of the imported data (see Displaying a Preview of the Imported Data).
> **Warning:** - This default data source can be used by all users who have licensed Lucanet ESG Reporting. For all users without a license for Lucanet ESG Reporting, the data source is displayed but cannot be loaded.
> - All reports that have been created in the **Lucanet ESG Reporting** solution and for which the data has already been **aggregated** are available for selection. For further information on data aggregation of an ESG report can be found in [Aggregating Data](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md) chapter of the Lucanet ESG Reporting solution documentation.
> - This default data source **cannot be edited any further**. To import the above-mentioned data, it already contains a predefined mapping and two predefined transformations.
> - If you want to import data other than the above from an ESG report, you can create a custom data source and define mapping(s) and, if necessary, transformations and/or aggregations as described in the previous sections.
---
---
title: "Defining Connection to a Data Source"
description: "To create a data source as the basis for importing data from a source system or a source file into Lucanet Disclosure Management, a connection to the data source must first be defined in the Import Management area."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-source-connection-disclmgmt
language: en
last_updated: 2026-05-01
---
# Defining Connection to a Data Source
## Overview
To create a data source as the basis for importing data from a source system or a source file into Disclosure Management, a connection to the data source must first be defined in the **Import Management** area.
The following connection types are available:
- Connection for **importing from a file** (in CSV or XLSX format)
- Connection for **importing from a Lucanet database**
- Connection for **importing from Lucanet ESG reporting**
> **Warning:** The **Import Management** functional area is only activated for users who have been assigned the **Global Administrator** role in Disclosure Management role management, as only this user role is authorized to manage imports (**ImportData**). For additional information about roles in Disclosure Management, see [Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md).
## Creating Connection to a Data Source
Connections to data sources are created and configured in Disclosure Management **Import Management**:
Create a connection to the data source
To create a new connection:
1. Click in the **function bar** on **Import Management** and then in the **overview** on **Connections** to open the workspace.
2. Click **Create New Connection**.
3. Configure the connection (see [Configuring Connection to a Data Source](#config_connection)).
> **Warning:** An overview of all connections already created is displayed under **Connections**. You can use the three dots icon to:
>
> - Select and edit existing connections
> - Delete connections
>
> By default, a connection for the import from Lucanet **ESG Reporting** is already created in the overview, which cannot be configured further and which can be used by all users who have licensed Lucanet ESG Reporting.
## Configuring Connection to a Data Source
### General Settings
General settings for a data source connection
| Option | Description |
|---|---|
| Name | Name of the connection |
| Connection | Select the connection type: **Import from file** (used to import data from an Excel and/or CSV file); **Import from Lucanet database** (used to import data from a Lucanet database). |
| Description | Optional description for the connection |
> **Warning:** No connection type is available for **Import from Lucanet ESG Reporting**. A **default connection** has already been created for the connection to this Lucanet solution, which cannot be configured separately, and which can be used by all users who have licensed Lucanet ESG Reporting.
### Connection Settings
The connection-specific settings depend on which connection type you have selected in the general settings.
### Import From File
### Import From an CSV File
Specific settings for a CSV file connection
| Option | Description |
|---|---|
| File type | The file type to be imported. Select **CSV** and configure the displayed fields. |
| Decimal separator | Separator used in the CSV file to indicate decimal values. |
| Has header row | Activate this check box if the first row of the CSV file is a header row. |
| Thousands separator | Separator used in the CSV file to indicate thousand values. |
| Separator for values | Separator used in the CSV file to separate values. |
| Sample file | Used to upload a sample file. The data in the sample file is not saved; it is only used as an aid when configuring the data source. The structure of the sample file must match the structure of the file actually imported. |
### Import From an XLSX File
Specific settings for an XLSX file connection
| Option | Description |
|---|---|
| File type | The file type to be imported. Choose **XLS**. |
| Sample file | Used to upload a sample file. The data in the sample file is not saved – the file is only used as an aid when configuring the data source. The structure of the sample file must match the structure of the file actually imported. |
### Import from Lucanet Database
Specific settings for a Lucanet database connection
| Option | Description |
|---|---|
| Host | Host of the Lucanet database to which the connection is to be established. |
| Database | Name of the Lucanet database to which the connection is to be established. |
| User and password | Access data of the user for accessing the Lucanet database. |
| Remember password | Activate this check box if you want the system to save the entered access data. |
| Decimal separator | Separator used in the Lucanet database to indicate decimal values. |
| Thousands separator | Separator used in the Lucanet database file to indicate thousand values. |
### Import from Lucanet ESG Reporting
Default connection 'ESG-Reporting'
### Description
No connection type is available for import from Lucanet ESG Reporting. A default connection **ESG Reporting** has already been created for the connection to this Lucanet solution, which cannot be configured separately, and which can be used by all users who have licensed Lucanet ESG Reporting.
## Editing Connection
An existing connection can be edited via the context menu of the three dots icon or via the **Edit** button:
Edit an existing connection
---
---
title: "Defining Outareas"
description: "Outareas provide the database for the tables in result documents and define the cell areas of an MS Excel table that can be used for exporting into an MS Word file. An MS Excel file can contain multiple Outareas."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas
language: en
last_updated: 2026-05-01
---
# Defining Outareas
## Overview
**Outareas** provide the database for the tables in result documents and define the cell areas of an Excel table that can be used for exporting into a Word file. An Excel file can contain multiple Outareas.
> **Note:** Instead of creating outareas manually, you can also have them detected automatically using AI. See [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md).
> **Warning:** To detect and define outareas and columns using AI, you need at least the **Advanced** license.
## Notation of Outareas in MS Excel
> **Tip:** - The name of **outareas** always begins with **outarea**.
> - Outareas **can** be extended by a name and a language addition. Name and language extensions are always preceded by an underscore (**\_**), for example **outarea_P&L_en**.
> - All names that begin with **outarea** are interpreted as an outarea and can be inserted in MS Word.
## Office for the Web and Office Native
In **Office for the Web** and **Office Native**, you create, move, and manage Outareas using the **Mark Area** task pane.
### Creating an Outarea
To create an Outarea:
1. In MS Excel, select the cells that are to define the new Outarea.
2. In the Excel ribbon, click **Mark Area**.
The **Mark Area** task pane opens on the right and the **Outarea** tab is displayed. The selected cell range is shown in the **Selection** area.
'Outarea' tab in the 'Mark Area' task pane
3. On the **Outarea** tab, click **+ Add Outarea**.
A dialog is displayed. If applicable, enter a name extension in the **outarea\_** input field and, for multilingual documents, select a language code from the drop-down list. Then click **Save**.
Defining the name extension and language for the Outarea
### Moving an Outarea
To move an Outarea:
1. Select the cells where an existing Outarea is to be moved to.
2. In the Excel ribbon, click **Mark Area**.
The **Mark Area** task pane opens on the right and the **Outarea** tab is displayed.
3. On the **Outarea** tab, next to the desired Outarea, click **Move to selection**.
The Outarea is moved to the selected cell range.
### Renaming or Deleting an Outarea
To rename or delete an Outarea:
1. In the Excel ribbon, click **Mark Area**.
The **Mark Area** task pane opens on the right and the **Outarea** tab is displayed.
2. On the **Outarea** tab, click the Outarea that you want to rename or delete.
3. Click
- the **pencil icon** to rename the Outarea.
- the **trash icon** to delete the Outarea.
Renaming or deleting an Outarea
> **Warning:** After inserting a table from MS Excel in MS Word, the two files will be linked. If an Outarea is renamed or deleted, this link will no longer exist. Data from MS Excel will then **no longer be displayed in the Word file**.
## Office for Desktop
### Creating an Outarea
To create an Outarea in an Excel file:
1. In MS Excel, select the cells that are to define the new Outarea.
2. You have two options for inserting an Outarea:
- In the Excel ribbon, click **Insert** and choose **Insert Outarea** from the menu.\
\
Inserting an Outarea via the Excel ribbon
- Open the context menu by right-clicking it and choose **Disclosure Management | Insert Outarea**.
Inserting an Outarea via the context menu
3. If you're editing a monolingual document, the new Outarea will be inserted. If you're editing a multilingual document, the **New Outarea** wizard will be displayed:
'New Outarea' dialog
4. If applicable, enter a name extension for the Outarea in the **outarea\_** input field.
5. If necessary, select a language code from the drop-down list. The drop-down list displays the language codes for the document languages created so far.
6. Click **Save**.
> **Note:** If an Outarea already exists in an Excel file, the **Insert Additional Outarea** menu command will be displayed in the context menu of the **Insert** button and in the **Disclosure Management** context menu.
>
> the displays menu of 'insert' button. displays 'insert additional output range | insert output range' menu command. 'insert' and menu command are highlighted in a red border. icon
> Creating an additional Outarea using the 'Insert' button
### Moving an Outarea
To move an Outarea:
1. Select the cells where an existing Outarea is to be moved to.
2. Open the **Disclosure Management** context menu by right-clicking it.
3. In the context menu, choose **Disclosure Management | Move Outarea**.
Moving an Outarea
### Renaming or Deleting an Outarea
The easiest way to delete and rename an Outarea is by using the Excel Name Manager. To do so, click **Name Manager** in the **Excel ribbon**.
Opening the Name Manager from the Excel ribbon
In the Name Manager, you can edit the name of an Outarea or delete an Outarea. You can find out more about working with the Excel Name Manager in [Creating and Editing Names and Name Extensions in Excel](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/setup-excel-file.md).
> **Warning:** After inserting a table from MS Excel in MS Word, the two files will be linked. If the name of the Outarea is changed via the Name Manager or the Outarea is deleted, the link will no longer exist. Data from MS Excel will then **no longer be displayed in the Word file**.
>
> When checking in an Excel file, you will be notified if this is the case. You can then cancel the check-in process and undo the change.
---
---
title: "Detail View of a Chapter"
description: "The detail view of a chapter in Lucanet Disclosure Management shows the most important information on the chapter and the MS Office files defined for it, and provides context-specific functions."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view
language: en
last_updated: 2026-05-01
---
# Detail View of a Chapter
## Overview
The detail view of a chapter in shows the most important information on the chapter and the MS Office files defined for it, and provides context-specific functions. The most important Information and options in the detail view of a chapter are:
- Rename or delete **Chapter**
- Change the **Status** of a chapter
- Open, edit or delete **MS Office files**
- Show **History** for MS Office files
- Show **Previous versions** of MS Office files
- Add **Section break** to Word files
- Show the **Mode** of Excel files
- Open **Data view** for Excel files
## Opening the Detail View of a Chapter
To open the detail view of a chapter:
1. Go to the **overview** and click **Cockpit**. Alternatively, go to the **function bar** and click **Document**.
Opening the detail view of a chapter
2. Click the info icon to open the detail view of a chapter. The detail view of a chapter is displayed as follows, for example:
Detail view of a chapter
## Options in the Detail View of a Chapter
The following options and information are available in the detail view of a chapter:
### Options for Chapters
Options in the detail view of a chapter
### Description
The following options are available in the detail view of a chapter:
| Option | Description |
|---------|---------|
| Rename chapter | Click the **Edit** icon to rename the chapter. |
| Delete chapter | Click the **Recycle bin** icon to delete the chapter. |
| Status | In the **Status** drop-down list, you can change the status of the document. The status change will not be shown in the history until the detail view of the chapter is re-opened. |
### General Options for MS Office Files
### Description
The menu under the three dot icon contains the following functions for all MS Office files:
- Open and edit
- Download
- Delete
Options for Word files in the detailed view of a chapter
The following information is displayed for all MS Office files:
**Last saved**
Date on which the MS Office file was last saved. This option also shows whether or not the file is locked. If the locked icon is displayed, the file is locked.
> **Note:** Locked files can be unlocked in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
**Last data change**
Date of the last data change. A data change is displayed if a new data import that resulted in changes to the data has been carried out.
### History of Office files
**Description**
The **History** list shows the changes that have been made in the selected chapter. The following changes are displayed:
- Check-ins for MS Office files
- Changes to the chapter’s status
- Data changes in the MS Office files
- Deletions of MS Office files
- Creating, deleting, and updating a [Word reference](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/use-word-references.md)
- Ignoring an available update of a Word reference
History of Office files in the chapter detail view
> **Note:** To filter the changes shown in the history, click the filter icon button.
**Open previous version**
You can open any of the versions shown in the history at any time. To do this, click the **Word** or **Excel icon** for the selected file in the **History**.
Then **check in** the file **again** to update the values changed since saving the restored version (for example by re-importing the data) if necessary.
### Special Options for Word Files
### Description
You can use **Section breaks** to define different areas for different layouts or formats within the Word file for a chapter.
Add Section change to a Word file
The following section breaks are available in the **Section break** drop-down list for Word documents:
| Section break | Description |
|---------|---------|
| Continuous | You can use the **Continuous** section break if you want to use multiple different formats on one page, for example (e.g. different number of columns). |
| Next page | The section break **Next page** can be used, for example, to reconfigure headers and footers on the following page. |
| Odd side | The new section will start on an odd-numbered page. You can use the **Odd side** section break if you want new chapters to automatically start on an odd-numbered page, for example. |
| Even side | The new section will start on an **even-numbered** page. You can use the **Even side** section break if you want new chapters to automatically start on an even-numbered page, for example. |
> **Note:** The selected section break will be indicated by an icon in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md) for the document in question.
### Special Options for Excel Files
Options for Excel files in the detailed view of a chapter
### Description
| Option | Description |
|---|---|
| Value insertion | Displays the mode used to add values to the Excel file.
The [Mode of an Excel File](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/excel-file-mode.md) indicates what procedures will be used to import and update report values. |
| Data view | Opens the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md). You can use the data view to correct rounding or [Validation Errors](https://support.lucanet.com/en/documentation/disclosure-management/validation-mgmt-disclmgmt.md). |
---
---
title: "Disclosure Management"
description: "The Lucanet Disclosure Management solution enables you to cover the entire process from data collection and evaluation to transmission and reporting. Its automated data flow and integrated XBRL tagging system allow you to combine your financial and ESG reporting processes."
source_url: https://support.lucanet.com/en/documentation/disclosure-management
language: en
last_updated: 2026-09-29
---
## Disclosure Management: An End-to-End Process up to the Completed ESEF and ESG Annual Report
You can use the Lucanet **Disclosure Management** solution to create [ESEF](https://support.lucanet.com/en/documentation/glossary.md#esef)-compliant annual reports. Disclosure Management enables you to cover the entire process from data collection and evaluation to data transmission and reporting. The automated data flow and integrated [XBRL](https://support.lucanet.com/en/documentation/glossary.md#xbrl) tagging enable combined financial and ESG reporting.
Lucanet Disclosure Management supports both the increased tagging requirements of ESEF reporting and the implementation of consistent [CSRD](https://support.lucanet.com/en/documentation/glossary.md#csrd)-compliant ESG reporting, which has been mandatory for many companies since 2024.
Lucanet Disclosure Management offers you:
- **Quick and easy reporting**: With automated data flow and integrated XBRL tagging, you can create combined financial and ESG reports quickly and easily.
- **Ready to print**: You work with Lucanet Disclosure Management from the first data import to the publication of the annual report in a ready-to print layout with no media discontinuity.
- **XBRL engine**: Lucanet Disclosure Management not only meets the new requirements of the European Single Electronic Format (**[ESEF](https://support.lucanet.com/en/documentation/glossary.md#esef)**), but you can also easily generate **SEC filings** or **local GAAP** reports in XBRL format (e.g. **UK GAAP**).
Disclosure Management 'Cockpit'
[Request demo](https://www.lucanet.com/en/request-demo/)
> **Note:** - Are you already using the Lucanet CFO Solution Platform and would also like to use Disclosure Management? Contact your Lucanet contact person for the licensing of Disclosure Management or contact us at [Contact](https://www.lucanet.com/en/contact/).
> - Not yet a Lucanet customer and would like to know more about our solutions? Then write to us at [Contact](https://www.lucanet.com/en/contact/).
## Getting Started with Disclosure Management
Our instructions help you get started with Lucanet Disclosure Management in next to no time:
- [Basic Configuration](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt.md)
- [All Steps at a Glance](https://support.lucanet.com/en/documentation/disclosure-management/process-description-disclmgmt.md)
- [FAQs](https://support.lucanet.com/en/documentation/faqs/lucanet-disclosure-management.md)
---
---
title: "Disclosure Management Settings"
description: "In the Lucanet Disclosure Management settings, each user can configure their own individual preferences for how certain areas of Lucanet Disclosure Management are displayed. These will apply across all documents."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/discl-mgmt-settings-disclmgmt
language: en
last_updated: 2026-05-01
---
# Disclosure Management Settings
## Overview
In the **Disclosure-Management Settings** you can configure individual preferences for how certain areas of Disclosure Management are displayed. These will apply across the whole system:
- General display
- Data import display
- Display in MS Excel
> **Warning:** The **Disclosure Management Settings** functional area is only available to users who have been assigned the roles of **Global Administrator** or **Global Settings Administrator** in the Role Management area of Disclosure Management, because these roles are the only ones with permission to manage system-wide settings (**global settings**). For more information on roles in Disclosure Management, see [Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md).
## Opening the Disclosure Management Settings
To open the Disclosure Management settings, go to the Disclosure Management function bar:
Disclosure Management menu bar
## Options
In the **Disclosure Management Settings**, you can configure the following options. Each option is explained in more detail in the user interface.
the discl mgmt settings general icon General settings
---
---
title: "Displaying History of a Result Document"
description: "In the history of a result document, you can quickly see when a version was created, who created it and with which options it was created."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document/document-history
language: en
last_updated: 2026-05-01
---
# History of a Result Document
## Overview
In the **history** of a result document, you can quickly see when a version was created, who created it and with which options it was created.
## Opening the History
In the overview of a document, click **History** to open the history of a result document:
Open the history of a result document
The following options are available in the history:
| Option | Description |
|---------|---------|
| Search | Searches for the specified character string in the list of documents. |
| Word, Excel, [iXBRL](https://support.lucanet.com/en/documentation/glossary.md#ixbrl), HTML | The system only displays documents of the file types whose check boxes are activated. |
| Show documents from other users | Result documents created by other users are also displayed in the list of result documents. |
| List of result documents | **Name** The name of the result document **Created on** Creation date of the result document **Created by** Creator of the result document **Language** Language of the result document **Error** If he result document contains errors, they are displayed here. Possible errors might be, for example, defective Outareas, key figures in continuous text or document variables. |
| the info button.png "scale:2.5" icon | Opens the detail view of the history for a result document. |
| the download button.png "scale:2.5" icon | Downloads the result document. |
| the recycle bin button.png "scale:2.5" icon | Deletes the result document from the history. |
> **Note:** **Open Version**
>
> You can open any of the versions shown in the history at any time. To do this, click the icon or the name for the selected file in the History.
## Comparing Documents
To track changes easily, you can compare two result documents at any time.
To compare result documents:
1. If necessary, open the **History**.
2. Activate the check boxes of the documents you want to compare.
3. Click **Compare documents**.
Comparing two versions of a document
## Opening the Detail View
For each version of a result document in the history, you can open a detailed view in which you can obtain detailed information relating to the version.
In the history of a document, click the info icon in the row of the desired version of the result document:
Open the detail view of a history
The detail view of a history is displayed as follows, for example:
Detail View of a History
The detail view shows the settings that were used when the selected version was created:
| Option | Description |
|---------|---------|
| Created on, Created by | Creator of the result document and the date and time at which the result document was created. |
| Language | Language in which the result document is created. |
| Structure | Name of the structure used to generate the result document (e.g. standard structure, summary report, management report) |
| General | **Control report (add file name)** The combined elements of the result document were labeled with the name of their chapter of origin. This allows you to quickly see from which chapter and therefore from which Word or Excel file a particular element of the result document originates. **Write user name in the header** The name of the creator and the time of creation were written in the header of the result document. **Remove values** All values under the control of Disclosure Management have been replaced by a zero. |
| Word functions | **Disable tracking of changes** The change tracking mode in the Word file has been deactivated. **Remove hidden text** The hidden texts contained in the Word files were not included in the result document. **Remove comments** The comments contained in the Word files were not included in the result document. |
| XBRL | **Add XBRL mapping** The XBRL mapping was added to the result document. The Word file can be loaded into the XBRL tagger. |
| Messages | List of errors that may have occurred when creating the document with chapter name and time at which the error occurred. The last column shows the MS Office file associated with the chapter. You can open any MS Office file directly from the column by clicking the corresponding MS Office icon. |
## Exporting the Detail View of a History to MS Excel
The detail view of the history can be exported to an Excel document at any time. Proceed as follows:
1. If necessary, open the **History**.
2. In the list of result documents, click the info icon in the desired row.
3. Click **Export to MS Excel**.
Exporting history to MS Excel
---
---
title: "Editing Documents in the XBRL Tagger"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/transfer-document-to-XBRL-tagger
language: en
last_updated: 2026-05-01
---
# Editing Documents in the XBRL Tagger
## Overview
The Lucanet [XBRL Tagger](https://support.lucanet.com/en/documentation/xbrl-tagger.md) is an ideal complement to Disclosure Management. You can seamlessly transfer result documents from [Lucanet Disclosure Management](https://support.lucanet.com/en/documentation/glossary.md#disclosure-management) to the XBRL Tagger and process the documents further. The XBRL Tagger has the following key features:
- The XBRL Tagger automatically validates the tagging in a document.
- The XBRL Tagger provides effective support for creating reports in iXBRL format, including ESEF.
- With the XBRL Tagger, you can tag your financial report immediately and convert it to [iXBRL](https://support.lucanet.com/en/documentation/glossary.md#ixbrl) without an implementation project and without IT expertise.
## Prerequisites
The following prerequisites must be fulfilled so that a document from Disclosure Management can be transferred to the XBRL Tagger and processed further:
- The XBRL Tagger must be licensed.
- In the settings of the Disclosure Management document, the desired taxonomy must be assigned (see [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md)).
- When creating the result document, the **Add XBRL Mapping** check box must be activated (see [Creating Result Documents](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md)).
- A result document must be created in Disclosure Management (see [Creating Result Documents](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md)).
## Transferring a Document to the XBRL Tagger
To transfer a document from Disclosure Management to the XBRL Tagger:
1. Open the **Document overview** workspace in the **XBRL Tagger** solution.
2. Click **Create new tagging file** and select the **From Lucanet Disclosure Management** command.
Transferring document from Disclosure Management to the XBRL Tagger.
3. A dialog displays all available result documents. Select the desired document.
---
---
title: "Editing Values"
description: "The data view can be used to import values from a source system, check them, and, if necessary, manually adjust them."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view
language: en
last_updated: 2026-09-29
---
# Editing Values
## Overview
The data view can be used to import values from a source system, check them, and, if necessary, manually adjust them. The values are edited in the following areas:
- Some values can be edited directly in the **data view** itself. You can find additional information in [Editing Values in the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view/.md#Data).
- The history of a value or text, for example, can be displayed in the **detail view**, which can be opened for each value or text value from the data view. You can use the history to decide whether and which actions are to be performed, such as changing or restoring a value. You can find additional information in [Editing Values in the Detail View](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view/.md#Detail).
- You can go from the data view for values for which a **validation** has been configured in a different document or that have been **referenced** from a different document directly into the respective underlying document and edit values there. You can find additional information in [Editing Values in Linked Documents](https://support.lucanet.com/en/documentation/disclosure-management/data-view/edit-values-in-data-view/.md#Links).
## Editing Values in the Data View
**Values in cells without highlighting** and values in cells highlighted in **blue** or **yellow** (see [Colors and Icons in the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md#FarbenSymbole)) can be edited directly in the data view as follows:
Click the desired cell in the data view and adjust the value. Click **Save** to save your entries.
Editing values in the data view
## Editing Values in the Detail View
The data view is supplemented by the **detail view**. The **history** of a given value or text, for example, is displayed in the **detail view**. Based on the **history**, you can determine what actions need to be taken (if any). In the **detail view**, you can also re-enter user-defined values or restore values that have been entered in the past.
Values in cells **without highlighting** and values in cells **highlighted in blue** or **yellow** (see [Colors and Icons in the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md#FarbenSymbole)) can be edited directly in the **detail view** as follows:
1. In the **data view**, click the **info icon** the info icon of the desired cell to open the **detail page**.
2. The **detail view** of a value or cell is displayed, for example, as follows:
Detail page of a value or cell
3. Click **Edit**.
4. Configure the details of the cell (see the section on the [options in the detail view of a cell](#detailview)).
5. Click **Save** to save your entries.
When you save, the changes you have made to values will be applied to the respective MS Excel file.
6. If you wish, you can then click **Close** to exit the **detail view**.
> **Note:** Once you have saved your entries and exited the **detail view**, the settings you have configured and/or the changes you have made will be indicated in colors in the **data view**:
>
> - If an imported value (previously not highlighted in color) is **manually overwritten** and saved in the detail view, it will be highlighted in **blue** in the data view.
> - If an imported value is **restored** in the detail view by means of the history, the highlighting of the cell will be **reset** in the data view.
> - Cells for which you have entered a **comment** in the detail view are marked with a **blue** triangle in the data view.
>
> (See also [Colors and Symbols in the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md#FarbenSymbole))
### Options in a Cell’s Detail View
The following options are available in the **detail view** of a cell:
| Option | Description |
|---|---|
| Cell programming | Programming of a cell in the [programming column](https://support.lucanet.com/en/documentation/glossary.md#programming-column) of the corresponding MS Excel file. The value in this cell can also be an account number, an ID, or another unique identifier.
**Note:** For more information on changing the programming of an MS Excel file, please refer to the chapter on [Defining Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md#progcol). |
| Validated with | If a [validation](https://support.lucanet.com/en/documentation/disclosure-management/validation-mgmt-disclmgmt.md) of the value has been configured, the Excel document used to perform the validation is displayed.
Click the name of the document to open its data view and make any adjustments if necessary. |
| Referenced from | If the value is referenced from a different Excel document, the Excel document from which the value comes will be displayed here.
Click the name of the document to open its data view and make any adjustments if necessary. |
| Output format | Number format (thousands, millions, billions, etc.) for values used in the **data view**. The **output format** can be changed in MS Excel and in the document settings.
**Note:** If you wish to change the **output format** of the **data view**, please refer to the chapter on [Configuring Documents](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md#roundview). |
| Footnote | **Footnote** added to this value. The footnote will appear next to the value within the table in the Word document that contains the [Outarea](https://support.lucanet.com/en/documentation/glossary.md#outarea) and in the [result document](https://support.lucanet.com/en/documentation/glossary.md#result-document).
If a footnote has already been added to an Excel document (see [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md)), the footnote is displayed here and can be edited if necessary. |
| New user-defined value | **Value**: Rounding values can be defined or updated here. **Comment**: This field enables the user to enter a **comment**. **Comments** must be saved in order for them to appear in the **history**. |
| History | History of the changes made to the value. The following columns will appear:
**Modified on**: The **date** on which a value was changed and/or a **comment** was entered. **Overwritten value**: The original value before it was changed. The value is transferred to the **New user-defined value** field by clicking the paste value icon. This function enables you to restore values whenever you wish. **Exact value**: The exact value as it was stored on the specified **date**. The warning triangle the triangle icon indicates that an imported, manually edited value has been overwritten by an import. **Modified by**: The user who changed the value or entered a comment into the system on the date indicated. **Comment**: A **comment** entered for the value in question. |
## Editing Values in Linked Documents
If the **validation** of a value has been configured in a different Excel document or the value **referenced** from a different Excel document, this is indicated accordingly in the data view (see [Colors and Icons in the Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md#FarbenSymbole)):
Marking for validated and referenced values
1. Move the cursor over the respective icon.
The underlying documents are displayed in a **tooltip**:
Tooltip with link to reference document
2. Do one of the following to open the data view of a linked document:
- Click the link icon (for one linked document)
- Click the document name in the tooltip (for several linked documents)
3. If necessary, edit the value and save the data view.
The value edited in this way is transferred to all documents in which it is referenced.
---
---
title: "Importing Data"
description: "The data import is used to load item numbers, item names and values from a source system and/or a source data file into the Lucanet Disclosure Management database and make them available for the creation of an annual report."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt
language: en
last_updated: 2026-05-01
---
# Importing Data
## Overview
The data import is used to load item numbers, item names and values from a source system and/or a source data file into the Disclosure Management database and make them available for report creation.
It is possible to address several source systems or source files simultaneously and import data from them.
Before a data import can be carried out, the **data sources** including any data transformations and aggregations as well as the **connections** to these data sources must first be defined in the **Import Management** area.
The **data import** itself is then configured and executed at **document level**.
> **Warning:** The **Import Management** and **Import data** areas are only activated for users who have the corresponding permissions to configure and/or execute a data import. These areas are grayed out for all other users.
## Required Sequence of Steps
To import data into Disclosure Management:
1. A user with the **Global Administrator** role creates a connection to the data source and configures it. For additional information, see [Defining Connection to a Data Source](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-source-connection-disclmgmt.md).
2. A user with the **Global Administrator** role creates one or more data sources and configures them. The configuration includes the **mapping** of the data within Disclosure Management and, if necessary, the **transformation** and/or **aggregation** of the data to be imported. For additional information, see [Defining a Data Source](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/define-data-srouce-disclmgmt.md).
3. A user with the **Global Administrator**, **Document Administrator** or **Document Data Importer** role configures the data import based on the data source and executes it at individual document level. For additional information, see [Configuring and Executing a Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt.md).
> **Note:** For additional information on user roles and permissions, see [Managing User Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt.md).
---
---
title: "Inserting Outareas into a Word Document"
description: "MS Excel tables and the Outareas defined in them provide the data for the tables in the result documents. The Outareas created in MS Excel can be transferred to a Word document using the Word ribbon."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-outarea-in-worddocument
language: en
last_updated: 2026-05-01
---
# Inserting Tables with Outareas into MS Word
## Overview
Excel tables and the **Outareas** defined in them provide the data for the tables in the result documents. The **Outareas** created in MS Excel can be transferred to a Word document using the **Word ribbon**.
> **Warning:** To transfer tables from Excel spreadsheets to Word documents, they must be part of an **Outarea** defined in the Excel file (see [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md)).
## Inserting Tables
How you insert the **Outarea** of an Excel table into a Word document depends on the selected MS Office variant.
### Office for the Web and Office Native
To insert a table in **Office for the Web** and **Office Native**:
1. Open the desired Word file from the [cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
2. Place the cursor at the desired position in the Word document.
3. On the **DM-Content** tab of the Word ribbon, click **Insert table/chart**.
The **Insert table** task pane is displayed on the right:
'Insert table' task pane in Office for the Web and Office Native
4. Configure the options (see the following table) and then click **Insert**.
The **Insert table** task pane offers the following options in Office for the Web and Office Native:
| Option | Description |
|---|---|
| Document | The **document** that contains the desired table. |
| Chapter | The **chapter** from which an Outarea is to be inserted into the Word document. |
| Outarea | The **Outarea** to be inserted into the Word document. |
| Use Excel number format | Applies the number format stored in the Excel file to the inserted table. |
| Insert | Inserts the selected Outarea into the Word document. |
> **Note:** All further functions available in **Office for Desktop** will soon also be available in **Office for the Web** and **Office Native**.
> **Note:** In **Office for the Web** and **Office Native**, you can highlight the tables inserted into the Word document: on the **DM-Content** tab, click **Set** and select the **Disclosure-Management-Tabellen** or **Nicht-Disclosure-Management-Tabellen** entry. Use the **Remove** button to remove the highlight again (see [Ribbons for MS Office for the Web](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web.md#highlight)).
### Office for Desktop
To insert a table in **Office for Desktop**:
1. Open the [cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
2. Click the desired Word document in the cockpit or choose **MS Word | Open Word file** in the menu of the **three dots icon**:
Opening a Word file from the Cockpit
3. Place the cursor at the desired position in the Word document.
4. In the Word ribbon, click **Insert Table**:
Inserting tables and/or diagrams using the Word ribbon
The **Table configuration** dialog is displayed:
'Table configuration’ dialog
5. Configure the dialog (see following sections) and click **Save**.
## Options in the 'Table configuration' Dialog
The following options are available in **Office for Desktop** in the **Table configuration** dialog.
### Options in the ‘Table overview’ section
The following options are available in the **Table configuration** dialog in the **Table overview** area:
| Name | Description |
|---------|---------|
| Document | The **document** that contains the desired table. The corresponding reference year is displayed in front of the name of the individual documents. |
| Chapter | The **Chapter**, from which an Outarea is to be inserted into a Word document. All chapters of the selected document to which an Excel file is assigned are displayed. |
| Outarea | **Outarea** to be inserted into the Word document. As soon as a chapter is selected, the **Outareas** available in the Excel file are listed in the **Outarea** drop-down list. |
| Insert table | Inserts the selected Outarea into the Word document. |
### Options in the ‘Layout Configuration’ section
The following options are available in the Table configuration dialog in the **Layout configuration** area:
| Option | Description |
|---|---|
| No template | Default setting. No template is used for the table to be inserted. |
| Use template | Loads the values of the selected template and uses them for the current table. |
| Start from scratch | **Table width**: The absolute width of the table in cm, e.g. 15.5. Equivalent to the **Preferred width** table property in MS Word. **Table indent**: The indent the table in cm, e.g. 2. Equivalent to the **Indent from left table** property in MS Word. **Double tab position**: Moves the number in the table by the specified factor in order to ensure the numbers wrap around existing footnotes or brackets, for example. This value is specified in cm, e.g. - 0.2 would move the numbers 2 mm to the left. In the example below, negative numbers are written in brackets in MS Excel. This has resulted in the numbers no longer being positioned below one another (left-hand column). Entering a double tab in MS Excel will realign the numbers so they are below one another again (right-hand column). |
| Column width | **Generic column widths**: Combination of fixed and calculated column widths. For example, you can enter the widths for number columns and layout columns (in cm). The width of the name column is then calculated automatically. **Number column width**: Width of number column in cm; **Layout column width**: Width of layout column in cm. **Fixed column width**: Fixed column width in cm |
| Table alignment | Sets the alignment of the table. |
| Text wrapping relative to the table | Determines whether the surrounding text is wrapped around or placed as a new paragraph. |
| Cell margins | Opens the **Padding options** dialog, where you define the cell margins and the spacing between cells for all cells of the table (see section **Options in the ‘Cell margins’ dialog**). |
| Add as a template | Saves the current settings as a template. |
| Reset to default | Resets all settings to their default values. |
### Options in the ‘Cell margins’ dialog
Use the **Cell margins** button in the **Layout configuration** area to open a dialog where you define the cell margins and cell spacing for all cells of a template’s table. The values are saved at template level. The dialog contains the following options:
| Option | Description |
|---|---|
| Default cell margins | Sets the inner spacing of the cells in centimetres (cm) – for **Top**, **Bottom**, **Left** and **Right** respectively. The default value is 0 cm in each case. |
| Allow spacing between cells | Enables the spacing between cells. Only when the checkbox is activated can a value for the **spacing** (in cm) be entered in the field below it. The option is deactivated by default. |
> **Note:** - Negative values cannot be entered in the input fields.
> - All values are saved in centimetres (cm) with up to two decimal places.
> - Click **OK** to apply the entered values, or **Cancel** to discard the changes.
> **Warning:** - The report values in the table are updated each time the Word document is used (e.g. when checking out or creating a result document).
> - You can also update the values using the **Update** button in the Word ribbon.
> - Report values cannot be changed in the Word file itself, but must be adjusted in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) or in the corresponding Excel file.
---
---
title: "Inserting Report Values in MS Excel"
description: "Lucanet Disclosure Management provides the Programming Wizard for inserting report values in MS Excel files. This allows previously imported report values to be inserted in an MS Excel table easily and conveniently."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-values
language: en
last_updated: 2026-05-01
---
# Inserting Report Values in MS Excel
## Overview
Disclosure Management provides the **Programming Assistant** for inserting report values in Excel files. This allows previously imported report values to be inserted in an Excel table easily and conveniently.
> **Warning:** Data to be used from an **ESG report** created with [Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting.md) are inserted into an Excel file using a separate function in the **Excel ribbon**. How to do this is described in the chapter [Inserting Tables From ESG Reports](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-data-from-esg-reports.md).
## Inserting Report Values
How you insert report values depends on the Office variant you use. In **Office for the Web** and **Office Native**, the user guidance and interface are identical.
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, proceed as follows to insert report values from a [Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md):
1. In the Excel ribbon, click **Programming Assistant**.
The **Programming Assistant** opens as a task pane on the right and is displayed as follows, for example:
Programming Assistant as a task pane in Office for the Web and Office Native
2. Configure the **Selected Column** and **Data Source** drop-down lists.
3. If necessary, enter a character string in the **Search** input field to filter the list of report values.
4. In the list of report values, activate the check box of the value that you want to carry over to the Excel file.
5. Click **Adopt**.
6. In the Excel ribbon, click **Check In** to apply the changes in Disclosure Management.
### Office for Desktop
To insert report values from a [Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md) in MS Excel:
1. Double-click a cell in a **value column** or **programming column**. The **Programming Assistant** will then be displayed in MS Excel:
'Auto Programming' tab in the Programming Wizard in MS Excel
2. Configure the **Selected Column** and **Data Source** drop-down lists.
3. If necessary, enter a character string in the **Filter** input field to filter the list of report values.
4. In the **Alias** column of the list of report values, activate the check box of the value that you want to carry over to the Excel file.
5. Click **Adopt**.
6. In the Excel ribbon, click **Check In** to apply the changes in Disclosure Management.
> **Warning:** You should be aware that the **programming columns** in the Excel file might be on top of each other for the current year and previous year. When using the programming column, it is therefore important to ensure that the desired column is set in the **Selected Column** drop-down list before inserting report values.
## Using the Programming Assistant
On the **Auto Programming** tab, the imported values are assigned to cells in the Excel file in Disclosure Management.
The following options are available on the **Auto Programming** tab:
| Option | Description |
|---|---|
| Selected Column | Depending on whether you have opened the Programming Assistant via a value column or programming column, the value columns or programming columns available in the Excel file will be shown to you for selection in the **Selected Column** drop-down list. |
| Filter | Filter value for the report data. The specified filter will be applied across all four columns, meaning you can also search for texts, names, or even individual values. |
| Data Source | Data source from which report values are to be carried over. |
| List of report values | Once all the settings have been configured, a list will be displayed with all the report values that can be inserted in the Excel file. **Alias:** The **Alias** column displays the account numbers or item numbers from the data source or [Data Import](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt/configure-and-define-data-import-disclmgmt.md). Activate the check box of the value(s) that you want to carry over to the Excel file. |
| Preview | The selected report values are displayed here as a **preview** along with their name (account/item numbers from the alias column), their value, and the programming in the programming column. |
| Clear | Clears the preview and, after clicking **Adopt**, also clears the value and programming in MS Excel. |
| Adopt | Adopts new/changed programming in the Excel file. After clicking **Adopt**, a semicolon followed by the selected alias (e.g. **;10100230**) will be entered in the programming column. The value of the selected alias will be entered in the value column. With immediate effect, the current report value of this account/item number will always be displayed in the corresponding value column. |
> **Warning:** To apply the changes in Disclosure Management, the Excel file must be subsequently checked in.
## Unknown Item Numbers
If an item number that does not exist in the current data import is addressed in the programming column, this will be highlighted in red and labeled as **Unknown** in the Programming Assistant.
An unknown item number is displayed in the Programming Assistant.
If this item number is present again in a later data import, the corresponding report value will be displayed as normal. For example, this may be the case when zero values are not imported.
As soon as the report value of the item number is no longer zero in a later import, it will be displayed in the Programming Assistant along with its name, value, and data source.
---
---
title: "Inserting Tables From ESG Reports"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-data-from-esg-reports
language: en
last_updated: 2026-05-01
---
# Inserting Tables From ESG Reports
## Overview
In order to use data collected with [Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting.md) in Disclosure Management reports, a separate option is provided in the **Excel ribbon**. This allows **tables** from previously imported ESG reports to be inserted in an Excel file easily and conveniently.
In order to use ESG data in Disclosure Management documents, the **columns** of the Excel file must be configured and the **output area** for display in MS Word must be defined accordingly.
Optionally and if necessary, the values can be adjusted in the [data view](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md) .
## Inserting an ESG Table
To insert an ESG table from an [imported ESG Report](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md) into MS Excel:
1. Click **Insert ESG table** in the Excel ribbon.
The 'Insert ESG table' command in the Excel ribbon
2. The **Insert ESG table** dialog is displayed in MS Excel:
The 'Insert ESG table' dialog
3. From the drop-down list that appears, select the **Table from ESG Reporting** that you want to insert into the Excel file.
4. If necessary, activate the **Automatically assign Disclosure Management Columns** check box.
You can use this option to define whether name columns and programming and value columns should be assigned automatically. As soon as you activate automatic row assignment, you can also assign **periods** to the columns in the table. The result of this option is as follows:
- The first column is defined as the **[name column](https://support.lucanet.com/en/documentation/glossary.md#name-column)**.
- The columns in the table are defined as **[value columns](https://support.lucanet.com/en/documentation/glossary.md#value-column)** for the specified period.
- The **[programming columns](https://support.lucanet.com/en/documentation/glossary.md#programming-column)** are inserted into the table on the right.
5. If necessary, activate the **Automatically extend dynamic tables** check box. With this option, the table is automatically extended by the specified number of rows. You can use this option, for example, to have placeholders for additional data in the Excel table so that you do not have to manually expand the table later.
6. Click **Insert**.
The table is inserted. Depending on the activated options, column types are automatically defined (see **step 4**) and/or additional rows are inserted (see **step 5**).
> **Note:** - The questions of the ESG reports that were [imported](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md) for the opened document are available for selection.
> - For each question in an ESG report, a **separate** Excel file must be created.
> - As soon as you click **Insert**, all data that may have been present in the Excel file will be overwritten.
> - The **Table Type** indicates whether it is a static or a dynamic table from ESG Reporting.
> - This function is used to insert **values** from ESG tables. To insert **text-only responses** from a questionnaire into a report in Disclosure Management, the **Insert ESG text value** function is available in the **Word ribbon** . For more information on inserting text values from ESG reports, see [Inserting Texts from ESG Reports](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-texts-from-esg-reports.md).
## Defining Columns
If you have not activated the **Automatically assign Disclosure Management Columns** option when inserting an Excel table (see [step 4 in the Inserting an ESG Table section](#AutoColums)), you must then define the columns of the Excel table (i.e. the **name column**, the **value column(s)**, the **programming column(s)**, and optionally the **footnote columns**). To do this, proceed as described in the section [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md).
The columns of an Excel file into which data from an ESG table has been inserted are structured as follows:
Columns of an Excel file after inserting an ESG table
## Defining Outareas
In order to display the values that have been inserted from an ESG report in a Word file, you must define the cell ranges as an Outarea. Proceed as described in [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md).
---
---
title: "Inserting Texts From ESG Reports"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-texts-from-esg-reports
language: en
last_updated: 2026-05-01
---
# Inserting Texts From ESG Reports
## Overview
In order to use responses collected in **text form** with [Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting.md) also in Disclosure Management, a separate option is provided in the **Word ribbon**. This makes it easy and convenient to insert text responses from [aggregated ESG reports](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md) into a Word file.
> **Note:** This function is not yet available for **MS Office for the Web** and **MS Office Native**. For a comparison of the functions in the individual variants, see [Comparison: MS Office for the Web, MS Office Native, and MS Office for Desktop](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md#comparison-ms-office-for-the-web-ms-office-native-and-ms-office-for-desktop).
## Inserting ESG Text Values
To insert text answers from [aggregated ESG reports](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md) into MS Word.
1. Navigate to the position in the Word document where you want to insert the text and click on **Insert ESG text value** in the Word ribbon.
The 'Insert ESG text value' command in the Word ribbon
2. The **Insert ESG text value** dialog is displayed in MS Word
Dialog 'Insert ESG text value'
3. From the **Report file** drop-down list, select the aggregated ESG report from which you want to insert the response.
4. From the **Question from ESG reporting** drop-down list, select the question for which you want to insert the answer.
5. From the **Reporting entity** drop-down list, select the company whose answer you want to insert.
6. Click **Insert**.
> **Note:** - The questions of all ESG reports that have been [aggregated](https://support.lucanet.com/en/documentation/esg-reporting/aggregate-data-esgrep.md) in ESG Reporting are available for selection.
> - You can insert several answers into a Word document.
> - This function is used to insert text responses to an ESG report. To insert tables from an ESG report into a document in Disclosure Management, the **Insert ESG tables** function is available in the **Excel ribbon** . For more information on inserting tables from ESG reports, see [Inserting Tables From ESG Reports](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-data-from-esg-reports.md).
---
---
title: "Inserting XBRL Tags"
description: "When working with Lucanet Disclosure Management, XBRL tags of a chosen taxonomy or placeholders for XBRL tags can be inserted in MS Word documents in Lucanet software using the Word ribbon. The inserted placeholders can simply be replaced with specific XBRL tags in a subsequent tagging step using the XBRL Tagger."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags
language: en
last_updated: 2026-05-01
---
# Inserting XBRL Tags in Word Documents
## Overview
Using the **Word ribbon**, [XBRL](https://support.lucanet.com/en/documentation/glossary.md#xbrl) tags of a chosen taxonomy or placeholders for XBRL tags can be inserted in Word documents. The inserted placeholders can simply be replaced with specific XBRL tags in a subsequent tagging step using the XBRL Tagger.
> **Note:** This function is not yet available for **MS Office for the Web** and **MS Office Native**. For a comparison of the functions in the individual variants, see [Comparison: MS Office for the Web, MS Office Native, and MS Office for Desktop](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md#comparison-ms-office-for-the-web-ms-office-native-and-ms-office-for-desktop).
## XBRL Functions in MS Word
The XBRL functions for a Word document can be opened from the **Word ribbon**:
XBRL functions in the Word ribbon
The following XBRL functions are available in MS Word:
### Inserting an XBRL Text Block
'XBRL Lite Textblocks' window in MS Word
### Description
The following options are available in the **XBRL Lite Textblocks** window:
**Add**
The **Add** button has two functions:
- It can be used to insert **XBRL tags** from the selected taxonomy.
- It can be used to insert **placeholders** for XBRL tags. The inserted placeholders can be replaced with specific tags in a subsequent document tagging step using the [XBRL Tagger](https://support.lucanet.com/en/documentation/disclosure-management/xbrl-window.md).
To insert an **XBRL tag**:
1. Select the text you want to tag in the Word document.
2. Select the tag you want to insert from the taxonomy list of available tags.
3. Click **Add**. The selected tag will be inserted.
To insert a **placeholder**:
1. Ensure that no tag is selected in the taxonomy list of available tags.
2. Click **Add**. The **Placeholder** tag will be inserted.
**Update Tag**
Changes an existing tag. To change a tag:
1. Select the tag you want to change in the **Content Controls** list.
2. Select the new tag in the taxonomy list of available tags.
3. Click **Update Tag**).
**Delete**
Deletes the tag selected in the **Content Controls** list from the Word document.
**Toggle Design Mode**
Displays or hides the XBRL tags defined in the document.
**Extend Selection to Paragraph**
Extends the tag area selected in the document to the end of the paragraph.
**Taxonomy**
- **Input field**: Searches the list of text block tags for the search term entered.
- **Table**: Contains all the text block tags available in the selected taxonomy.
**Content Controls**
List of all the XBRL tags used in the Word document. By highlighting a tag in the list, the corresponding area will be displayed in the Word document.
### Inserting an XBRL Tag
To insert an **XBRL tag**:
1. Select the text you want to tag in the Word document.
2. Select the tag you want to insert from the taxonomy list of available tags.
3. Click **Add**. The selected tag will be inserted.
### Inserting a Placeholder
To insert a **placeholder**:
1. Ensure that no tag is selected in the taxonomy list of available tags.
2. Click **Add**. The **Placeholder** tag will be inserted.
### Inserting an XBRL Footnote Tag
'XBRL Lite Footnotes' window in MS Word
The following options are available in the **XBRL Lite Footnotes** window:
| Option | Description |
|---|---|
| Add | Assigns an **XBRL footnote tag** to the text selected in the Word document. |
| Delete | Deletes the XBRL footnote tag selected in the **Content Controls** list from the Word document. |
| Toggle Design Mode | Displays or hides the XBRL tags defined in the document. |
| Content Controls | List of all the footnote tags used in the Word document. By highlighting a tag in the list, the corresponding area will be displayed in the Word document. |
### Highlighting XBRL Text Blocks
Word document with highlighted XBRL text blocks
### Description
The **Highlight XBRL Text Blocks** function highlights all the tagged text blocks in a Word document.
MS Word displays a comment field for all highlighted XBRL text blocks for the user to enter notes regarding the tag.
---
---
title: "Installing and Updating the MS Office Components"
description: "The Dispatcher is a program that must be installed on each computer on which you wish to use the Lucanet Disclosure Management solution. Special ribbons are provided to allow you to use Lucanet Disclosure Management with MS Word and MS Excel. These ribbons will provide you with effective assistance when working with Lucanet Disclosure Management."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/install-disp-andribbon
language: en
last_updated: 2026-09-07
---
# Installing and Updating the MS Office Components
## Overview
Lucanet Disclosure Management works with MS Word and MS Excel in three variants: **MS Office for the Web**, **MS Office Native**, and **MS Office for Desktop**. Which components you need to install on your computer depends on the variant you choose.
In principle, you need to perform the following steps:
1. **Choose a variant:** First decide which MS Office variant you want to use. You will find the differences between the variants in the [MS Office variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
2. **Install the components:** Then install the components required for your variant. All components are provided in the **Toolbox** of Disclosure Management.
The following table shows which components are required for each variant:
| Variant | Required components |
|---|---|
| **MS Office for the Web** | Office Online Manifest |
| **MS Office Native** | Manifest files that provide the ribbons as an add-in |
| **MS Office for Desktop** | Dispatcher plus the MS Word ribbon and the MS Excel ribbon |
> **Warning:** For **MS Office for the Web** and **MS Office Native**, there are two ways to configure the variant:
>
> - The IT department configures the variant centrally for the entire company in **Office Management**.
> - Each user configures the variant locally.
>
> Before installing locally, clarify whether a company-wide installation is planned and/or feasible.
Jump directly to the right instructions for your variant and installation type:
- [MS Office for the Web: central](#ms-office-for-the-web-installing-centrally)
- [MS Office for the Web: local](#ms-office-for-the-web-installing-locally)
- [MS Office Native: central](#ms-office-native-installing-centrally)
- [MS Office Native: local](#ms-office-native-installing-locally)
- [MS Office for Desktop](#ms-office-for-desktop-installing-the-dispatcher-and-ribbons)
> **Note:** The installed components are updated regularly. Whenever an update is available, you will be informed automatically once you open an MS Office document in Lucanet Disclosure Management. For more information, see the [Updating the components](#updating-the-components) section.
## MS Office for the Web: Installing the Office Online Manifest
For the **MS Office for the Web** variant, you activate the Disclosure Management ribbons in the browser via the **Office Online Manifest**. The manifest is provided in the **Toolbox** and can be set up either centrally by the IT department for the entire company, or locally by each user.
### MS Office for the Web: Installing Centrally
The IT department can roll out the **Office Online Manifest** centrally for the entire company via the **Microsoft 365 Admin Center**. The entire process typically takes 10–20 minutes. Proceed as follows:
1. **Open the Microsoft 365 Admin Center:** Open [https://admin.microsoft.com](https://admin.microsoft.com) and sign in with your Microsoft 365 administrator account. Then go to **Settings | Integrated Apps** in the left navigation bar.
The Integrated apps page in the Microsoft 365 Admin Center
> **Tip:** If the **Integrated Apps** option is not displayed, click **Show all** at the bottom of the navigation list to display all menu items.
2. **Deploy the add-in:** On the **Integrated Apps** page, click the **Add-Ins** link near the top and then click **Deploy Add-in**. Click **Next** in the wizard.
3. **Upload the manifest:** In the wizard, select **Upload Custom App** and the app type **Office Add-In**. Choose **Upload manifest file (.xml) from device**, click **Choose File**, and select the **Office Online Manifest** from the **Toolbox**.
4. **Define the target audience:** On the next page of the wizard, select who should receive the add-in and click **Next**:
- **Everyone** – deploy to the entire organization.
- **Specific users/groups** – phased rollout, for example starting with a pilot group.
- **Just me** – for initial testing by the administrator.
> **Note:** It may take up to 24 hours until the add-in is rolled out and appears in MS Word and MS Excel on the user side.
### MS Office for the Web: Installing Locally
Each user can upload the **Office Online Manifest** locally in MS Word. You first download the manifest from the **Toolbox** and then upload it in the browser. Proceed as follows:
1. **Download the manifest:** Click **Toolbox** in the function bar of Disclosure Management and open the **Manifest files** area. Download the manifest file there under **Office Online Manifest**.
2. **Open MS Word:** Open a Word file from a document for which the **Office for the Web** variant was selected under **Configure document**. The file opens in the browser.
3. **Open Add-ins:** On the ribbon, click **Add-ins** and then **More Add-ins**.
Add-ins pane in Word for the Web
4. **Switch to the admin-managed catalog:** The **Office Add-ins** dialog opens on the **Store** tab, which is usually disabled. Click the **Admin Managed** tab.
The Admin Managed tab in the Office Add-ins dialog
5. **Start the upload:** In the top right, click **Upload My Add-in**.
The 'Upload My Add-in' link in the Office Add-ins dialog
6. **Select and upload the manifest:** In the **Upload Add-in** dialog, click **Browse**, select the manifest file you downloaded earlier, and click **Upload**.
The Upload Add-in dialog
After the installation, the Disclosure Management ribbons are available in MS Word and MS Excel, see [After the installation](#after-the-installation).
## MS Office Native: Adding the Ribbons as an Add-in
> **Note:** This section applies to the **MS Office Native** variant. Here, the ribbons are not provided via the Dispatcher and the MSI ribbons, but as an **add-in** via manifest files in the locally installed Office application. For more information, see the [MS Office variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
For **MS Office Native**, Disclosure Management provides two manifest files in the **Toolbox**: the **Word and Excel Desktop Content Manifest** and the **Word Desktop Layout Manifest**. These manifest files provide the ribbons as an add-in in MS Word and MS Excel – either centrally by the IT department for the entire company, or locally by each user.
### MS Office Native: Installing Centrally
The IT department can roll out the add-ins centrally for the entire company via the **Microsoft 365 Admin Center**. The entire process typically takes 10–20 minutes. Proceed as follows:
1. **Open the Microsoft 365 Admin Center:** Open [https://admin.microsoft.com](https://admin.microsoft.com) and sign in with your Microsoft 365 administrator account. Then go to **Settings | Integrated Apps** in the left navigation bar.
The Integrated apps page in the Microsoft 365 Admin Center
> **Tip:** If the **Integrated Apps** option is not displayed, click **Show all** at the bottom of the navigation list to display all menu items.
2. **Deploy the add-in:** On the **Integrated Apps** page, click the **Add-Ins** link near the top and then click **Deploy Add-in**. Click **Next** in the wizard.
3. **Upload the manifest:** In the wizard, select **Upload Custom App** and the app type **Office Add-In**. Choose **Upload manifest file (.xml) from device**, click **Choose File**, and select the manifest file from the **Toolbox**. Repeat this step for both manifest files (Content and Layout).
4. **Define the target audience:** On the next page of the wizard, select who should receive the add-in and click **Next**:
- **Everyone** – deploy to the entire organization.
- **Specific users/groups** – phased rollout, for example starting with a pilot group.
- **Just me** – for initial testing by the administrator.
> **Note:** It may take up to 24 hours until the add-in is rolled out and appears in MS Word and MS Excel on the user side.
### MS Office Native: Installing Locally
To use the ribbons as an add-in in MS Word and MS Excel locally, you must make the two manifest files available as a trusted add-in catalog via a shared folder. Proceed as follows:
1. **Prepare a manifest folder:** Download the two manifest files from the **Toolbox** and place them in a local folder.
2. **Create a network share:**
1. Right-click the manifest folder and select **Properties**.
2. Go to **Sharing | Advanced Sharing**.
3. Enable **Share this folder** for your user.
4. Copy the resulting network share path, for example `\\YOUR-PC\OfficeAddinManifests`.
3. **Configure the trusted add-in catalog in MS Word:**
1. Open **MS Word**.
2. Go to **File | Options**.
3. Select **Trust Center**.
4. Click **Trust Center Settings**.
5. Go to **Trusted Add-in Catalogs**.
6. Paste the network share path into the **Catalog URL** field and click **Add Catalog**.
7. In the **Trusted Catalogs** table, enable the **Show in Menu** checkbox and click **OK**.
8. Restart MS Office.
Trusted Add-in Catalogs in the MS Word Trust Center
4. **Load the add-in from the catalog:** Open **MS Word** and go to **Home | Add-ins | Advanced**. In the **Office Add-ins** dialog, the **Shared Folder** tab now shows the provided manifest files. Select both add-ins one after another.
The Shared Folder tab in the Office Add-ins dialog
For **MS Excel**, proceed in the same way. The **Prepare a manifest folder** and **Create a network share** steps apply to both programs and only need to be performed once. Because the trusted add-in catalog is configured per application in MS Office, you only repeat the last two steps in **MS Excel**:
- Add the shared folder under **File | Options | Trust Center | Trust Center Settings | Trusted Add-in Catalogs**.
- Then load the add-in via **Home | Add-ins**.
> **Note:** If a manifest file contains errors, MS Office ignores it and does not show it under **Shared Folder**.
## After the Installation
After the installation for **MS Office for the Web** or **MS Office Native**, the Disclosure Management ribbons are available in MS Word and MS Excel.
In MS Word, two ribbons are displayed, the **DM-Content** ribbon and the **DM-Layout** ribbon:
Content ribbon for Disclosure Management
Layout ribbon for Disclosure Management
In MS Excel, the Disclosure Management ribbon is displayed as follows:
Disclosure Management ribbon in MS Excel
## MS Office for Desktop: Installing the Dispatcher and Ribbons
For the **MS Office for Desktop** variant, you install the **[Dispatcher](https://support.lucanet.com/en/documentation/glossary.md#dispatcher)** as well as the **ribbons** for MS Word and MS Excel.
The **Dispatcher** is a program that must be installed on each computer on which you wish to use MS Office for Desktop. This variant does not work without the Dispatcher. The Dispatcher handles the communication between Disclosure Management in the browser and the locally installed MS Office programs.
### Installing the Dispatcher
> **Warning:** To install the Dispatcher on your computer, the following is required:
>
> - **Windows 64-bit version**
> - **Microsoft dotNet 10.0.0**
To install the **Dispatcher** for Disclosure Management:
1. Click **Toolbox** in the function bar of Disclosure Management and click **Dispatcher** in the overview. The detail view is displayed as follows, for example:
Detail view of the Dispatcher area
2. Download the MSI file for the Dispatcher and navigate to your **Downloads** folder.
3. Double-click the MSI file to execute it.
MSI file in Windows Explorer
4. The Dispatcher is installed automatically and can then be found on your computer under **Disclosure Management Office File Dispatcher**:
Dispatcher in Windows start menu
> **Note:** The Dispatcher will launch automatically whenever you create a file in Disclosure Management or open an existing file.
### Dispatcher in the MS Windows system tray
After installation, the Dispatcher is displayed as an icon in the MS Windows system tray. You will receive a message as soon as the Dispatcher is running and as soon as you open an MS Office file. You can stop the Dispatcher and view the log via the context menu of the icon in the system tray:
Context menu of the Dispatcher in the MS Windows context menu
### Installing the Ribbons
To install the **Office ribbons** for Disclosure Management:
1. In Lucanet Disclosure Management, navigate to the **Toolbox** tab and click **Ribbons** in the tree view. The detail view is displayed as follows, for example:
Detail view of the ribbon area
2. Click **Download** to download the MSI file for the **MS Word ribbon** or the **MS Excel ribbon** and then navigate to your download folder.
3. Double-click the MSI file to execute it.
WordInstaller in Windows Explorer
The ribbon is installed automatically and is displayed in MS Word or MS Excel as follows as soon as you open a Word document or Excel document from Lucanet Disclosure Management:
- In MS Word:
Ribbon in MS Word
- In MS Excel:
Ribbon in MS Excel
> **Note:** Depending on your security settings, you may have to confirm the installation again as soon as you open MS Word or MS Excel for the first time after installing the ribbons. In the displayed message, click **Install**.
>
> the displays confirmation message regarding word ribbon in microsoft office. icon
> Confirmation message in Microsoft Office
>
> If you currently have installed Ribbons with the version 25.08 or older, you have to uninstall the Ribbons in **Programs & Apps** and delete the two installation directories under **C:\\Users\\{username}\\AppData\\Roaming\\DisclosureManagementExcelAddIn** and **C:\\Users\\{username}\\AppData\\Roaming\\DisclosureManagementWordAddIn**, first.
>
> After completing these steps, you can reinstall the Ribbons with the latest version.
## Updating the components
**Office for Desktop:** [Opening an **MS Office** document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file.md#openMSDoc) from **Disclosure Management** automatically performs a software check for the latest version of the installed components, such as the **Dispatcher** and **Ribbons**. If a later version is available, the system displays a corresponding note and a link to the page where the latest version can be downloaded.
---
---
title: "Language Settings"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/language-settings
language: en
last_updated: 2026-06-18
---
# Language Settings
## Overview
On the **Language Settings** tab in the **Configure document** workspace, you manage the document languages of a Disclosure Management document. For each language, you can assign a separate format template for MS Word.
One of the configured languages serves as the document's primary language (**Default Language**).
## Opening the 'Language Settings' tab
To open the **Language Settings** tab, proceed as follows:
1. Open a document and click **Configure document**.
2. Open the **Language Settings** tab. It is displayed, for example, as follows:
The 'Language Settings' tab in the 'Configure document' workspace
3. Configure the language settings if required (see the following section).
## The document's primary language
One of the configured languages is the document's primary language (referred to as **Default Language** in the user interface). It has the following functions:
- It is the default language for new content when no other language is selected.
- It appears as a separate **Default Language** entry in the language list on the [Spaces](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/manage-typography-rules.md) tab. Click **Default Language** there to open the typography rules for the primary language.
## Adding a language
To add a new language, proceed as follows:
1. Open a document and click **Configure document**.
2. On the **Language Settings** tab, click **Add Language**.
3. The **Add New Language** dialog appears:
Configuring the settings for a new document language
4. Configure the new language (see the following section).
5. Click **Create** to add the language.
The added language then appears in the language list on the **Language Settings** tab.
## Options on the 'Language Settings' tab
The following options are available on the **Language Settings** tab:
- **Add Language**: Adds a document language. Clicking **Add Language** opens the **Add New Language** dialog (see the section [Adding a language](#adding-a-language)).
- **Edit**: Opens edit mode for the settings of the respective language.
- **Format template**: Adds or removes format templates for MS Word. The maximum file size for a format template is 5 MB.
## Editing or deleting a language
To change the basic settings of an existing language or to delete a language, proceed as follows:
- **Edit a language**: Select the desired language in the list. Click **Edit**. The **Edit Language** dialog opens.
- **Delete a language**: Click the trash can icon to delete the selected language. A dialog appears in which you can confirm or cancel the deletion of the language.
---
---
title: "Managing Typography Rules"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/manage-typography-rules
language: en
last_updated: 2026-06-18
---
# Managing Typography Rules
## Overview
The **Spaces** tab in the **Configure document** workspace provides a central overview of the **typography rules**. Typography rules define how certain expressions are treated typographically when a Word file is opened (checked out) – for example, by inserting a non-breaking space between a number and a unit or by suppressing a space between a currency symbol and an amount.
Typography rules are managed per document language and are divided into two areas:
- **Default rules**: predefined rules provided by Lucanet e.g. for German and English.
- **Custom rules**: company- or project-specific rules that you create yourself.
> **Warning:** The **Spaces** tab and all associated functions require an **Advanced license** or higher and are available exclusively to **Global Admins** and **Document Admins**.
## Opening the 'Spaces' tab
To open the **Spaces** tab, proceed as follows:
1. Open a document and click **Configure document**.
2. Open the **Spaces** tab. It is displayed, for example, as follows:
The 'Spaces' tab in the 'Configure document' workspace
3. In the **Language-specific rules** list on the left, select the language whose rules you want to manage. The **Default Language** entry refers to the primary language defined under **Language Settings**.
4. The rule editor on the right shows the rules for the selected language. The upper area displays the default rules for the selected language, and the lower area displays the custom rules.
## Activating and deactivating default rules
The following options are available for activating or deactivating default rules:
- **Activate or deactivate default rules globally**: Located in the upper-right area of the rule editor (**Activate default rules**). Activates or deactivates **all** default rules of the selected language at once. When the global toggle is off, the entire **Default rules** area is hidden.
- **Activate or deactivate specific default rules**: Each default rule has its own toggle on the right-hand side of the rule row. Use it to deactivate individual rules that do not match your company's internal requirements.
> **Note:** When the **global** toggle is switched back on after a deactivation, all individual toggles are reset to **on**. The system then automatically checks whether there are any conflicts with existing custom rules and automatically deactivates conflicting default rules.
> **Warning:** For languages **without predefined default rules** (for example, French), the global toggle is disabled and grayed out. The tooltip reads: **Default rules are not available for this language** _._
## Creating custom rules
To create a custom rule, proceed as follows:
1. In the **Custom rules** area, click **Add custom rule**. The **Add custom rule** dialog appears:
The 'Add custom rule' dialog
2. Enter the left (**Left**) and right (**Right**) term of the expression for which you want to create a rule.
- Use the **0-9** button to insert a \[0-9\] placeholder for any digit.
- Use the **a-z** button to insert the \[a-z\] placeholder for any letter.
- Purely numeric entries (for example, 5 or 100) are automatically converted to \[0-9\] when you leave the field.
3. Under **Rule**, select a **rule type**. The following rule types are available:
| Rule type | Effect | Example |
|---------|---------|---------|
| Coupled | Inserts a normal non-breaking space between Left and Right. | 251 million euros. |
| Tightly coupled | Inserts a non-breaking narrow space between Left and Right. | 100 %. |
| Suppress distance | Removes any space between Left and Right. Especially useful when different rules apply to different languages. | A space that appears between a digit and the percent sign in German should be suppressed in English. |
> **Tip:** For **Coupled** and **Tightly coupled** rules, the corresponding character is inserted even if there is no space between the two terms.
4. Click **Save**.
If, when you save a custom rule, a default rule with an identical Left/Right combination already exists, a dialog appears in which you can decide how to proceed.
## Editing or deleting custom rules
To edit or delete custom rules, proceed as follows:
- **Edit a rule**: In the three-dot menu of a custom rule, click **Edit**:
Editing custom rules
The **Edit rule** dialog opens with the existing values. Edit the rule configuration as required.
- **Delete a specific rule**: In the three-dot menu of a custom rule, click **Delete**. Confirm the deletion in the dialog that appears. If this custom rule previously deactivated a default rule with an identical Left/Right combination, the following note appears: **One or more default rules are currently deactivated and may now be reactivated manually.**
- **Delete all rules**: To remove all custom rules of the selected language at once, click **Remove all rules** in the **Custom rules** area. The button appears as soon as at least one custom rule exists.\
\
In the confirmation dialog, click **Delete** to permanently delete all custom rules of the selected language. If there are deactivated default rules with an identical Left/Right combination, the dialog includes a note that these default rules can be reactivated manually after the deletion.
## Applying typography rules
Active typography rules are applied automatically when a Word file is checked out. For more information about the behavior during check-out and about removing the markings in Word, see [Creating and Editing Word Files](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file.md) and [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
---
---
title: "Managing User Roles for Disclosure Management"
description: "Different user roles can be assigned for Lucanet Disclosure Management in the Lucanet CFO Solution Platform for each user who is activated for the solution."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt
language: en
last_updated: 2026-05-01
---
# Managing User Roles for Disclosure Management
## Overview
Different **user roles** can be assigned for Disclosure Management in the Lucanet CFO Solution Platform for each user who is activated for the solution. User roles define what permissions a user has for certain areas in Disclosure Management. For example, they allow you to assign **role assignment permissions** and **read and write permissions** for individual documents, or the permission to change the **status of individual process steps**.
Disclosure Management distinguishes between two types of user role:
- **Global roles** which can be used to assign solution-wide, cross-document permissions, e.g. administrator rights for documents, import functions, system settings, and role assignment within Disclosure Management.
- **Document roles** which can be used to assign permissions at the document level, e.g. read and write permissions for documents, chapters, periods and validations, or the permission to import data or change the status of individual process steps.
## Opening Role Management for Disclosure Management
Disclosure Management's **Role Management** can be opened via the function bar, and is displayed as follows:
The 'Role Management' area
Role management is split into three areas: **Users**, **Global roles** and **Document roles**.
### Users
The **Users** area shows the users that have been activated for Disclosure Management in the User Management area of the **Lucanet CFO Solution Platform** (see [Creating and Editing Users for the Lucanet CFO Solution Platform](https://support.lucanet.com/en/documentation/administration/user-management.md)), together with the roles they have been assigned for Disclosure Management. The area is displayed as follows:
This area serves as an overview, and cannot be edited. Users are assigned their individual roles in the **Global roles** and **Document roles** areas, described in the following sections.
### Global Roles
In the **Global roles** area, you can use predefined roles to assign solution-wide, cross-document permissions. The workspace is displayed as follows:
The 'Global roles' workspace
For a full list of the available global roles and their permissions, and how to assign them to users, see [Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md).
### Document Roles
In the **Document roles** area, you can use predefined roles to assign permissions at the document level. The workspace is displayed as follows:
The workspace 'Document roles'
For a full list of the available document roles and their permissions, and how to assign them to users, see [Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md).
## In This Section
In this section, you will find information on the following user role topics for Disclosure Management:
- **[Assigning Global Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md)**\
\
Learn what global roles are used for, which permissions each predefined global role grants, and how to assign a global role to a user.
- **[Assigning Document Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-document-roles-disclmgmt.md)**\
\
Learn what document roles are used for, which permissions each predefined document role grants, and how to assign a document role to a user.
- **[Transferring User Roles to Another User with Lucanet Lume](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/transfer-user-roles-lume-disclmgmt.md)**\
\
Use Lucanet Lume to transfer a user's document- and chapter-level roles to another user in one step, instead of assigning them manually.
---
---
title: "Mode of Excel Files"
description: "The stored MS Excel files in Lucanet Disclosure Management can generally be differentiated between in terms of whether and how they are programmed. The method for inserting and updating the values determines their mode."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/excel-file-mode
language: en
last_updated: 2026-05-01
---
# Mode of Excel Files
## Overview
The stored Excel files can generally be differentiated between in terms of whether and how they are programmed. The method for inserting and updating the values determines their **mode**.
## Modes for Excel Files
The **mode** defines how report values from the Disclosure Management database are inserted and updated in the Excel tables for the chapters of a document.
The mode depends on whether and how the file or table is programmed. The mode of an Excel file tells you how report values are **imported** and **updated**.
The mode is assigned automatically by Disclosure Management.
The following modes exist for Excel files:
- In **Automatic** mode, the Excel table is programmed so that Disclosure Management automatically inserts report values. The report values match the source system's items or accounts imported into Disclosure Management or are made up of calculation operations of multiple items. Manual changes to individual report values can only be made in the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md).
- In **Semi-automatic** mode, the Excel table is programmed so that at least one report value is recorded manually in the data view or in the Excel table. The manually maintained report values should ideally be entered and edited in the [Data View](https://support.lucanet.com/en/documentation/disclosure-management/data-view.md). In addition, report values are automatically inserted and updated by Disclosure Management via items from the database.
- In **Manual** mode, the Excel table is programmed so that all report values of the Excel document have to be maintained manually in the data view or in the Excel table. No report values are automatically inserted or updated.
- If an Excel table is not programmed, it has no mode. Such tables are purely manual tables and are only edited in MS Excel itself and not managed by Disclosure Management. That means they cannot be edited via the data view and no history is maintained for the existing values.
## Displaying the Mode
The mode of an Excel file is displayed in the [Chapter Detail View](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md) for the chapter to which the Excel file is assigned.
The chapter detail view can be opened from the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md) by clicking the info icon.
Opening the detail view of a chapter
The mode is displayed as follows:
Mode of an Excel file
---
---
title: "MS Office Variants"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants
language: en
last_updated: 2026-09-10
---
# MS Office Variants
## Overview
In Lucanet Disclosure Management, three different variants are available for working with MS Word and MS Excel: **MS Office for the Web**, **MS Office for Desktop**, and **MS Office Native**. The selected variant determines **where** MS Office documents are opened and edited – in the browser or in the version of MS Office installed locally on the computer – and which ribbons you work with in MS Word or MS Excel.
You set the variant per document under **Configuring a Document** in the **General Settings** area, using the **MS Office Variant** selection. For more information on the settings, see [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md).
Selecting the MS Office variant under **Configuring a Document | General Settings**
## The three variants compared
The following table shows how the three variants differ in terms of the MS Word and MS Excel version used:
| Variant | MS Word opens … | MS Excel opens … |
|---|---|---|
| [**MS Office for the Web**](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web.md) | in the browser | in the browser |
| [**MS Office for Desktop**](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-desktop.md) | in the locally installed Office version | in the locally installed Office version |
| [**MS Office Native**](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-native.md) | in the locally installed Office version (as an add-in) | in the locally installed Office version (as an add-in) |
## Variant details
### MS Office for the Web
When **MS Office for the Web** is selected:
- **MS Word documents** open in the browser (Office for the Web).
- **MS Excel documents** open in the browser (Office for the Web).
This lets authors edit Word and Excel files directly in the browser without a local Office installation.
### MS Office for Desktop
When **MS Office for Desktop** is selected, **all** MS Office documents – Word and Excel – open in the version of MS Office installed locally on the computer.
### MS Office Native
With **MS Office Native**, you use the Office for the Web ribbons together with the locally installed Office programs (MS Word and MS Excel). In this variant, Disclosure Management runs directly in the locally installed Word desktop application as an add-in – in contrast to Office for the Web, which runs in the browser.
## Which variant is right for me?
### Advantages and disadvantages of the MS Office variants
| Variant | Advantages | Disadvantages | Installation |
|---|---|---|---|
| **MS Office for the Web** | Collaborative work by several authors directly in the browser; no local Office installation required; always up to date | Limited by the Microsoft web platform: no custom fonts, no multi-column layout, no advanced typography; some Disclosure Management functions are not yet available | Only upload the **Office Online Manifest** – no Dispatcher |
| **MS Office Native** | Work in the locally installed Office application with the full range of MS Word/Excel functions (custom fonts, multi-column layout, typography); modern ribbons (**DM-Content**/**DM-Layout**); **no Dispatcher required**; successor to MS Office for Desktop | Local Office installation required; individual functions from Office for Desktop are being added gradually (currently only minor differences) | Two **manifest files** (Content + Layout) – no Dispatcher |
| **MS Office for Desktop** | Work in the locally installed Office application; currently the largest range of functions (e.g. XBRL, ESG text value, advanced table and layout configuration) | **Phase-out model**; complex installation (Dispatcher + Word ribbon + Excel ribbon); the Dispatcher and ribbons have to be updated frequently | **Dispatcher** + **Word ribbon** + **Excel ribbon** |
### Recommendation by use case
| Your use case | Recommended variant |
|---|---|
| Several people are to work on a document together/collaboratively, without a local Office installation | **MS Office for the Web** |
| Local work with the full range of MS Word/Excel functions (custom fonts, multi-column layout, typography) – in the modern variant without a Dispatcher | **MS Office Native** |
| You need functions that are currently only available in MS Office for Desktop (e.g. XBRL, ESG text value, advanced table/layout configuration) | **MS Office for Desktop** (interim solution) |
> **Note:** **MS Office Native** is the recommended variant for local work and is the successor to **MS Office for Desktop**. The function differences that currently still exist between **MS Office for the Web**/**MS Office Native** and **MS Office for Desktop** will be aligned soon – after that, there will be no reason to keep using MS Office for Desktop. For a detailed comparison of the functions, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md#comparison-ms-office-for-the-web-ms-office-native-and-ms-office-for-desktop).
## Required installation per variant
Disclosure Management provides the components needed for each variant in the **Toolbox** – in the **Dispatcher**, **Ribbons**, and **Manifest files** areas:
- **MS Office for the Web**: Download the **Office Online Manifest** and upload it to Office for the Web to activate the Disclosure Management ribbon in the browser.
- **MS Office for Desktop**: Install the **Dispatcher** and the **Ribbons** (MS Word ribbon and MS Excel ribbon).
> **Note:** **Only in Office for the Web**: The **Dispatcher** is the basic prerequisite for using MS Office for Desktop on a computer: without it, MS Office for Desktop does not work. The Dispatcher handles the communication between Disclosure Management in the browser and the locally installed MS Office programs.
>
> For detailed installation instructions for the Dispatcher and ribbons, see [Installing and Updating the MS Office Components](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/install-disp-andribbon.md).
- **MS Office Native**: Add the two desktop **manifest files** as add-ins – the **Word und Excel Desktop Content Manifest** and the **Word Desktop Layout Manifest**.
> **Note:** For MS Office Native, two separate manifest files – one for **Content** and one for **Layout** – are available in the **Toolbox**. For more information on the ribbons, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
## Activating the MS Office variant
To activate the MS Office variant you want:
1. Open **Configuring a Document** and switch to **General Settings**.
2. In the **MS Office Variant** area, select the entry you want.
3. Save the setting.
---
---
title: "Names and Name Extensions in MS Excel"
description: "To enable automatic insertion and updating of values in MS Excel files and interaction between MS Office files, names and/or name suffixes must be assigned to certain columns, cells and cell ranges in MS Excel. Names and name suffixes are used to link MS Word with MS Excel spreadsheets. You can easily insert and edit names and name suffixes for Lucanet Disclosure Management using the Excel ribbon."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/setup-excel-file
language: en
last_updated: 2026-05-01
---
# Names and Name Extensions in MS Excel
## Overview
To enable automatic insertion and updating of values in Excel files and interaction between MS Office files, **names** and/or **name suffixes** must be assigned to specific columns, cells and cell ranges in MS Excel. Names and name suffixes are used to link MS Word with Excel spreadsheets.
You can easily insert and edit names and name suffixes for Disclosure Management using the [Excel ribbon](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
In this chapter, we demonstrate the importance of names in Excel files and how to insert and edit names.
## Use Names and Name Suffixes
The following table shows the names that must or may be present in an Excel file so that the corresponding values and information are automatically inserted and/or updated in the Excel file:
| Name | Description |
|---|---|
| outarea | **Outarea** for the export to Word. Outareas represent the data basis for the tables in result documents. |
| name_1 | Defines a **name column**. The name column is a mandatory column. It contains the row labeling (i.e. the names of the individual report values). |
| value\_ _sequential number_period ID_ | Defines a **value column**. A value column contains the report values of the current document. In columns that are defined as value columns, the values are inserted or updated **after each data import** and **when the Excel file is updated**. |
| prog\_ _sequential number_PeriodID_ | Defines a **programming column**. The programming column is responsible for programming the contents of the column **value\_**. For example, it contains item numbers from the source system and other information for calculating the corresponding value columns. |
| footnote\_ _sequential number_period ID_ | Defines a **footnote column**. The footnote column can be used to add footnotes to values of Excel files, which are then displayed in the Outareas in Word documents. |
| sn_duedate | **Due date** of the document. You can find additional information on variables under [Inserting Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md). |
| sn_year | **Reference year** of the document, e.g. **2024**. You can find additional information on variables under [Inserting Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md). |
| sn_prevyear | **Previous year** of the document, e.g. **2023**. You can find additional information on variables under [Inserting Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md). |
## Conditions for Names and Name Suffixes
The following conditions for names and name suffixes must be observed when programming in MS Excel:
- In MS Excel, different cells, cell ranges and columns must be assigned unique names.
- When using names in MS Excel, you must observe the distinction between upper and lower case letters.
- Disclosure Management uses sequential numbers when assigning names, as MS Excel does not allow identical names. This is particularly important when names are entered manually by the user in Excel.
- Cells and columns can be assigned several names simultaneously in Excel (e.g. a column defined as **value_1\_CURRENTYEAR01** and as **value_1\_PREVIOUSYEAR01**). However, only one name is displayed when the column is selected in alphabetical order.
> **Tip:** While it is possible to program on multiple worksheets, we recommend minimizing the number of worksheets for performance reasons.
## Office for the Web and Office Native
### Creating Names
In **Office for the Web** and **Office Native**, you create names using the **Mark Area** task pane. The task pane contains a tab each for **Outarea**, **Name column**, and **Period columns**.
> **Note:** Instead of creating outareas and columns manually, you can also have them detected automatically using AI. See [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md).
> **Warning:** To detect and define outareas and columns using AI, you need at least the **Advanced** license.
Task pane for creating and editing outareas and columns
> **Note:** You can find detailed instructions for the individual tabs in [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md) (**Outarea** tab) and in [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md) (**Name column** and **Period columns** tabs).
### Editing Names
> **Warning:** Changes to names have a direct impact on programming or links in MS Word. If, for example, the name of the Outarea (**outarea**) is changed, the Outarea must be reinserted in MS Word.
In **Office for the Web** and **Office Native**, you edit or delete a name using the **Mark Area** task pane:
1. In the Excel ribbon, click **Mark Area** and open the relevant tab (e.g. **Outarea**).
2. Click the desired entry and then
- the **pencil icon** to edit the name.
- the **trash icon** to delete the name.
Editing names in the 'Mark Area' task pane
## Office for Desktop
### Creating Names
You have several options for creating names in MS Excel:
#### Using the Excel Ribbon
The simplest option for assigning a name is the **Excelribbon** for Disclosure Management. Proceed as follows:
1. In MS Excel, select the cell, cell range or column for which you want to assign a new name. Depending on which cell, row or column you have selected, the available buttons are enabled in the Excel ribbon based on the context.
The 'Name' button in the Excel ribbon
2. Click the desired button in the Excel ribbon.
#### Using the Context Menu
You can also use the Disclosure Management context menu to assign names. Proceed as follows:
1. Select the desired cell, row or column.
2. Right-click to open the context menu.
3. The **Disclosure Management** menu contains the functions provided by Disclosure Management based on the context:
'Disclosure Management' context menu in MS Excel
#### Using the Name Manager
You can also use the MS Excel name manager to create names. Proceed as follows:
1. Select the cell or column for which you want to assign a name.
2. In the Excel ribbon, click in the **Name Management** area on **Name manager**.
Open the name manager from the Excel ribbon
3. In the name manager, click **Create**.
4. The **Create Name** dialog is displayed:
Creating a new name in MS Excel
5. Specify the new **name** and click **OK**.
> **Warning:** We recommend that you always use the **Excel ribbon** or the **Disclosure Management** context menu to insert names, as this avoids errors due to incorrect spelling.
### Editing Names
> **Warning:** Changes to names have a direct impact on programming or links in MS Word. If, for example, the name of the Outarea (**outarea**) is changed, the Outarea must be reinserted in MS Word.
All existing names can be filtered, sorted, edited and deleted using the MS Excel **name manager**.
To edit a name via the Excel name manager:
1. In the Excel ribbon, click in the **Name Management** area on **Name manager**.
Open the name manager from the Excel ribbon
2. In the name manager, select the name you want to edit.
Name manager in MS Excel
3. Click **Edit**. The **Edit Name** dialog is displayed:
Edit name in MS Excel
4. Edit the **name** and click **OK**.
---
---
title: "Notifications"
description: "The notifications in the Lucanet Disclosure Management notification window ensure that you are always well informed. You receive status and result messages for the actions you perform."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt/notifications
language: en
last_updated: 2026-05-01
---
# Notifications
## Overview
The **Disclosure Management** notification window issues messages as soon as you perform certain actions. These messages include:
- Whether it was possible to execute an action
- When and by whom an action was executed
- That a triggered action is in the queue (i.e. It could not be executed yet because other actions must be completed first)
- A button for downloading an **extract**
- A button for opening a **result document**
## Opening the Notification Window
To open a notification window:
1. Click the **bell** icon in the **function bar** at the top right of the application window to open the notification window.
Opening the notification window
2. The notification window is displayed as follows, for example:
Notification window in Disclosure Management
## Options in Notification Window
The notification window includes the following options:
#### Mark all as read
Marks all messages in the notification window as read
#### Mark as read
Marks the corresponding message as read.
#### Cancel
Cancels the current process. After clicking **Cancel**, a confirmation prompt appears. You can then confirm or cancel the process cancellation.
The following processes can be canceled:
- Create extract
- Import extract
- Create copy
- Create update
#### Download extract
Downloads the extract created in the [Roll forward/copy](https://support.lucanet.com/en/documentation/disclosure-management/perpetuate-copy-doc-disclmgmt.md) workspace.
#### Open result document
Opens the result document created in the [Creation](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md) workspace.
## Notification Types
There are five notification types:
#### Successful
The action was completed successfully.
**Example**:
The result document has been created successfully
#### Failed
The action has failed.
**Example**:
The action has failed
#### In process
The action is being processed.
Action that is currently being executed
#### Wait for other processes
Indicates the place in the queue.
**Example**:
##### 'Document name' - Data import is waiting for other processes
Position in the queue: 3
Your position in the queue has been reserved.
The data import will automatically start as soon as the previous processes have been completed.
#### Warning
The action was completed with warnings.
**Example**:
##### 'Document name' - Data import completed with warnings
Started on:: 'Date' | 'Time'
Started by: 'User name'
Data source: 'Name of data source'
Completed on: 'Date' | 'Time'
The following warnings appeared during the data import:
- Warning 1
- Warning 2
- ...
---
---
title: "Programming References"
description: "Some report values, for example the numbers in a key figures table, are repeated in multiple places in reports. So that these only have to be updated in one place and are rounded immediately if applicable, references can be set. If a report value is also used elsewhere, only a reference to the Source value is set for this. The target value of the reference then no longer needs to be updated separately because changes to the source value will be transferred automatically to the target value by means of the reference."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/prog-references
language: en
last_updated: 2026-05-01
---
# Programming References
## Overview
Some report values, for example the numbers in a key figures table, are repeated in multiple places in reports. So that these only have to be updated in one place and are rounded immediately if applicable, **References** can be set. The use of references is recommended in the following cases, for example:
- If a report value is also used elsewhere, only a reference to the **Source value** is set for this. The **Target value** of the reference then no longer needs to be updated separately because changes to the source value will be transferred automatically to the target value by means of the reference.
- References can also be set for report values of other documents managed by Disclosure Management. Among other things, this can be used for quarterly reporting to link comparative periods in the balance sheet with figures already published in annual financial statements.
Disclosure Management provides the **Programming Assistant** for inserting report values in Excel files.
## Inserting References
How you insert references depends on the Office variant you use. In **Office for the Web** and **Office Native**, the user guidance and interface are identical.
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, proceed as follows to insert a reference:
1. Select a cell in the value column where you want the target value to be displayed.
2. In the Excel ribbon, click **Programming Assistant**.
The **Programming Assistant** opens as a task pane on the right.
3. Open the **Reference Programming** tab.
'Reference Programming' tab of the Programming Assistant as a task pane
4. Configure the **Document**, **Chapter**, **Column**, and **Period** drop-down lists.
5. If necessary, enter a character string in the **Search** input field to filter the list of report values.
6. In the **Name** column of the list of report values, activate the check box of the value that you want to carry over to the Excel file as a reference.
7. Click **Adopt**.
8. In the Excel ribbon, click **Check In** to apply the changes in Disclosure Management.
### Office for Desktop
References can be inserted in Excel files using the **Excel ribbon**. To create a reference, select a cell in the value column where you want the target value to be displayed. The reference can then be inserted using the **Programming Assistant**. Proceed as follows:
1. Double-click a cell in a value column or programming column. The **Programming Assistant** will then be displayed in MS Excel.
2. Open the **Reference Programming** tab:
'References Programming' tab of the Programming Assistant in MS Excel
3. Configure the **Document**, **Chapter**, **Column**, and **Period** drop-down lists.
4. If necessary, enter a character string in the **Filter** input field to filter the list of report values.
5. In the **Name** column of the list of report values, activate the check box of the value that you want to carry over to the Excel file as a reference.
6. Click **Adopt**.
7. In the Excel ribbon, click **Check In** to apply the changes in Disclosure Management.
> **Note:** References must be programmed separately for each cell. Even with programming columns that are on top of each other, the **#r\[name\]** entry in the programming column only ever applies to the cell that was selected when the assistant was called up.
## Options for reference programming
The **Reference Programming** tab contains the various possible settings for selecting a source value. Detailed information for a reference, such as the name of the source value, the value, and the programming, is displayed in the **Preview** in the bottom area of the assistant.
The following options are available in the **Reference Programming** tab of the Programming Assistant:
| Option | Description |
|---|---|
| Document | Document where the report value (source value) for the reference is located |
| Chapter | Chapter in the source document where the report value for the reference is located |
| Column | Column in the source document where the report value for the reference is located |
| Period | Period in the source document where the report value for the reference is located |
| Filter | Filter value for the report data displayed in the list of report values |
| Use extended decimals #rf | The abbreviation **DP** stands for decimal places. Activate the check box if the decimal places of the report values are not to be truncated. In this case, the source format of the report values will be used as the reference instead of the target format of the table. |
| List of report values | Once all the settings have been configured, a list will be displayed with all the report values that can be used as reference values. **Name:** The **Name** column displays the content of the name column linked to the displayed report value. In the **Name** column, activate the check box of the value that you want to carry over to the Excel file as a reference. |
| Preview | The selected report values are displayed here as a **preview** along with their Name (account/item numbers from the alias column), their Value, and the Programming in the programming column. |
| Clear | Clears the preview and, after clicking **Adopt**, clears the value and programming from the Excel file. |
| Adopt | Saves the new reference. By adopting the reference, the reference programming in the form **#r\[row number\]** is inserted in the corresponding cell of the programming column. |
> **Warning:** To apply the changes in Disclosure Management, the Excel file must be subsequently checked in.
---
---
title: "Reimporting a Result Document"
description: "In Disclosure Management, you can reimport externally edited Word result documents back into the existing report structure. The system automatically maps the content to the original chapters and saves each section as a new version."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document/reimport-result-document
language: en
last_updated: 2026-07-15
---
# Reimporting a Result Document
## Overview
In Disclosure Management, you can reimport externally edited Word result documents back into the existing report structure. Disclosure Management automatically maps recognized content to the original chapters. Recognized chapters that are not skipped and not locked are saved as new versions — for example, after an external audit review or after a translation.
> **Note:** Reimport is also available for **partial result documents**. This applies only to partial result documents generated after this feature was introduced; for partial result documents generated earlier, the **Re-import result document** option remains disabled.
For a partial result document, reimport only considers the chapters that were part of the original partial result document. All other chapters in the report remain unchanged — they are not checked for conflicts, not versioned, and not recorded in the audit history.
Reimport requires the **Edit all result documents** permission and is available at the Basic license level.
## Translation Workflow
The **Reimport** and **Generate as translation document** options work together as an end-to-end translation workflow:
### Step 1: Generate a translation document
In the **Creation** workspace, enable **Generate as translation document** and select the target language.
Option 'Generate as translation document' in the 'Create result document' dialog
Click **Create result document**. The generated Word document contains the content in the default language, but uses the target-language out-areas for tables and charts.
### Step 2: Edit externally
Share the Word document with the external translator. They edit the content directly in the file.
### Step 3: Reimport
Open the document's **History** in Disclosure Management and reimport the translated file into the target language (see the following section).
## Reimporting a Document
To re-import a results document, follow these steps:
1. In the document overview, open the **History** workspace.
2. On the desired result document row, open the three-dot menu and select **Re-import result document**.
Command 'Re-import result document' in the three-dot menu of the History
3. The following dialog is displayed.
Dialog 'Re-import result document'
4. Upload the externally edited Word file in DOCX format. The file must not exceed 100 MB and must have been generated from the selected result document. Do not remove or modify the embedded chapter markers — they are required to map the content back to the original chapters.
5. If the document has multiple languages configured, in the **Target language** drop-down list, select the language under which the new chapter versions should be saved. The language of the original result document is selected by default.
> **Note:** Reimport does not perform automatic translation or recalculation of report data. Derived data such as variables, table contents, or XBRL information is updated only the next time the chapter is checked out and back in.
6. Review the summary. It shows the number of recognized chapters and missing chapter markers. Unrecognized and locked chapters are then listed in the conflict list.
- If all chapters were recognized, proceed to the next step.
- If the dialog lists conflicts, resolve them before confirming (see [Resolving Conflicts](#resolving-conflicts)).
'Review changes' step with conflict list and 'Confirm re-import' button
7. Click **Confirm re-import**. The reimport runs in the background. You can track progress in the dialog or close it. You will receive a notification once it is complete. Recognized chapters that are not skipped and not locked are saved as new versions in the selected language.
## Resolving Conflicts
If the dialog lists unrecognized or locked chapters, each row must be resolved before the **Confirm re-import** button becomes active.
| Row type | Available options |
|---|---|
| **Unrecognized chapter** (chapter marker missing or unreadable) | **Append to previous chapter** — adds the content to the previous chapter's Word document **Skip** — leaves the chapter unchanged; you can update it manually afterward |
| **Locked chapter** (currently locked by another user or the workflow) | **Skip — I will add changes manually** — leaves the chapter unchanged **Cancel re-import** — aborts the entire reimport; no changes are saved |
To apply an option to multiple rows at once, use the bulk actions in the conflict list header:
- **Append each to previous chapter** — appends the unassigned content for every conflict with a missing chapter marker to its respective previous chapter; locked chapters remain unaffected
- **Skip all** — sets "Skip" for all rows
- **Clear** — removes all conflict resolutions selected so far; the uploaded file, target language, and analysis result remain unchanged
## After Reimport
- Each reimported chapter is saved as a new version; previous versions are retained in the version history.
- The history row displays a **Reimported** badge. Hovering over the badge shows the timestamp of the most recent reimport.
- An audit entry is created for each affected chapter, capturing user, timestamp, chapter, and language.
---
---
title: "Reviewing Layout Check Violations"
description: "View layout violations on the Messages tab in Word, jump to the affected location in the document, and approve or revoke approval of intentional deviations."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations
language: en
last_updated: 2026-08-03
---
# Reviewing Layout Check Violations
## Overview
When you check out or update a Word chapter in Lucanet Disclosure Management, or when you create a result document, the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/layout-check.md) automatically checks the content for text and formatting deviations. Violations found (**layout violations**) are shown to you directly in Word in the events report, so you can review them without interrupting your workflow.
This feature is only available in Office Native and Office for the Web.
## Viewing Layout Violations
Open the Messages window using the **Event Reports** button in the Word ribbon (see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md)). The **Layout violations** tab is divided into three areas:
- **Layout violations**: Shows the active layout violations in the order they occur in the document.
- **Approved**: Contains the violations you have approved (see [Approving Violations](#approving-violations)).
- **Information**: Contains notices about changed values, styles from the **System styles** group, and detected firesys content (see [Migrating firesys Content to Content Groups](#migrating-firesys-content-to-content-groups)). These entries are navigable but do not count as layout violations and cannot be approved.
The 'Layout violations' tab in the event reports
> **Note:** - If no violations were found, the tab shows the notice: **No layout violations were found.**
> - Hovering the mouse over an entry (tooltip) shows a description of the rule and a suggested resolution.
> - Clicking an entry's navigation icon jumps directly to the corresponding spot in the Word document.
## Approving Violations
If a reported violation is intentional (for example, a deliberately different formatting), you can approve it. This requires permission to edit the document settings. Proceed as follows:
1. On the **Layout violations** tab, click the **Approve** checkmark icon at the relevant entry.
2. The entry is removed from the active list and shown in the **Approved** area. The approval applies only to that specific occurrence in the current chapter. The underlying rule remains active and continues to flag other occurrences. If you change the content at that spot, the approval no longer applies. If the deviation still exists, the spot is flagged as a violation again the next time the Layout Check runs.
## Revoking an Approval
To revoke an approval, proceed as follows:
1. On the **Layout violations** tab, expand the **Approved** area.
2. Click the **Revoke** arrow icon at the relevant entry.
The entry is removed from the **Approved** area. If the deviation still exists, the spot is flagged as an active violation again the next time the document is checked out or updated.
## Migrating firesys Content to Content Groups
When you open the **Layout violations** tab in the event reports, Disclosure Management checks the document for the five fixed firesys colors for dynamic content: blue, turquoise, red, green, and orange. It detects text passages with the corresponding firesys font shading as well as table cells with the matching diagonal firesys marker. Other, individually formatted text passages are not detected as firesys content.
You can access detected occurrences in the **Information** area. Detected occurrences do not count as layout violations and therefore cannot be approved. Each entry shows the detected firesys color and the number of occurrences. For migration, the following options are available to you:
- If the color is already assigned to a content group in the [Style Guide](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md#assigning-a-firesys-color), you can migrate every occurrence of that color in the document to the assigned content group in one step. You can navigate to text occurrences via the entry. Navigation is not available for markers detected only in tables.
- If the color is not yet assigned to a content group, the entry is flagged accordingly and migration is disabled. In the Style Guide, first assign the corresponding firesys color to a new or existing content group.
> **Warning:** The migration is applied immediately to every occurrence of the selected color. It permanently removes the original firesys markers and cannot be undone. This also removes the original firesys behavior for keeping or deleting content at the chapter level. After the migration, you can still include or exclude the affected content groups when creating a result document.
## When the Layout Check Runs
The Layout Check runs automatically:
- when a Word chapter is checked out,
- when a Word chapter is updated using the **Update** button,
- and when a [result document is created](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md).
Which rules are monitored is defined on the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/layout-check.md) tab in the **Configure document** workspace.
---
---
title: "Ribbons for Disclosure Management"
description: "Overview of the ribbons for MS Word and MS Excel in Disclosure Management and a comparison of the functions across the MS Office variants."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt
language: en
last_updated: 2026-09-10
---
# Ribbons for Disclosure Management
## Overview
When working with MS Office documents, you use functions in specific [ribbons](https://support.lucanet.com/en/documentation/glossary.md#ribbon) for MS Word and MS Excel. The functions provided are adapted for use in conjunction with **Lucanet Disclosure Management**:
- The **Word ribbon** helps you when structuring and formatting Word content.
- The **Excel ribbon** helps you program an MS Excel file for Disclosure Management.
Which ribbons are available to you depends on the selected MS Office variant. A description of the respective functions can be found in the following chapters:
- [Ribbons for MS Office for Desktop](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-desktop.md) – Functions in the ribbons for MS Word and MS Excel in the MS Office for Desktop variant.
- [Ribbons for MS Office Native](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-native.md) – Functions in the DM-Content and DM-Layout tabs of the Word ribbon in the MS Office Native variant.
- [Ribbons for MS Office for the Web](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web.md) – Ribbons in the MS Office for the Web variant.
> **Note:** - For an overview of the variants themselves, see the [MS Office Variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
> - For an overview of the functional differences, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
> - The **Event Reports** button in the Word ribbon also shows the results of the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md).
## Comparison: MS Office for the Web, MS Office Native, and MS Office for Desktop
The following tables compare the functions of the ribbons across the three variants **MS Office for the Web**, **MS Office Native**, and **MS Office for Desktop**.
Legend: ✅ = available · ❌ = not available.
### Word Ribbon
| Function | MS Office for the Web | MS Office Native | MS Office for Desktop |
|---|---|---|---|
| Check In | ✅ | ✅ | ✅ |
| Update | ✅ | ✅ | ✅ |
| Help | ✅ | ✅ | ❌ |
| Event Reports | ✅ | ✅ | ✅ |
| Set/remove highlight (Set/Remove) | ✅ | ✅ | ❌ |
| Highlight tables / highlight body text number | ❌ | ❌ | ✅ |
| Insert table/chart | ✅ | ✅ | ✅ |
| Insert body text number | ✅ | ✅ | ✅ |
| Insert document variable | ✅ | ✅ | ✅ |
| Assign Layout Actions | ✅ | ✅ | ✅ |
| Insert ESG text value | ❌ | ❌ | ✅ |
| Remove locking of content controls | ❌ | ❌ | ✅ |
| Style Guide | ✅ | ✅ | ❌ |
| Special Characters | ✅ | ✅ | ❌ |
| Reset manual formatting | ✅ | ✅ | ❌ |
| Hanging Indent | ✅ | ✅ | ❌ |
| Page Break | ✅ | ✅ | ❌ |
| Character spacing | ❌ | ✅ | ❌ |
| Word spacing | ❌ | ✅ | ❌ |
| Report on violations acc. to layout check | ✅ | ✅ | ❌ |
| Save File Locally | ❌ | ❌ | ✅ |
| Open Local File | ❌ | ❌ | ✅ |
| Recover Version | ❌ | ❌ | ✅ |
| Compare with Local Document | ❌ | ❌ | ✅ |
| Insert XBRL tags / highlight text blocks | ❌ | ❌ | ✅ |
| Copilot (text adjustment, text draft) | ✅ | ✅ | ✅ |
### Excel Ribbon
| Function | MS Office for the Web | MS Office Native | MS Office for Desktop |
|---|---|---|---|
| Publish / Check In | ✅ | ✅ | ✅ |
| Update | ✅ | ✅ | ✅ |
| Help | ✅ | ✅ | ❌ |
| Event Reports | ✅ | ✅ | ✅ |
| Insert document variable | ✅ | ✅ | ✅ |
| Properties | ✅ | ✅ | ✅ |
| Create/edit outareas and columns | ✅ | ✅ | ✅ |
| Programming assistant | ✅ | ✅ | ❌ |
| Area and column assistant | ✅ | ✅ | ❌ |
| Add area highlights/Add layout area | ✅ | ✅ | ✅ |
| Name Manager (manage and delete names) | ❌ | ❌ | ✅ |
| Insert ESG table | ❌ | ❌ | ✅ |
| Save File Locally | ❌ | ❌ | ✅ |
| Open Local File | ❌ | ❌ | ✅ |
| Recover Version | ❌ | ❌ | ✅ |
---
---
title: "Ribbons for MS Office for Desktop"
description: "Functions in the ribbons for MS Word and MS Excel in the MS Office for Desktop variant."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-desktop
language: en
last_updated: 2026-06-10
---
# Ribbons for MS Office for Desktop
## Overview
In the **MS Office for Desktop** variant, you use functions in specific [ribbons](https://support.lucanet.com/en/documentation/glossary.md#ribbon) for MS Word and MS Excel. The functions provided are adapted for use in conjunction with **Lucanet Disclosure Management**:
- The [**Word ribbon**](#special-functions-in-the-word-ribbon) helps you when structuring and formatting Word content.
- The [**Excel ribbon**](#special-functions-in-the-excel-ribbon) helps you program an MS Excel file for Disclosure Management.
> **Note:** - For a general overview of the available variants and their installation, see the [MS Office Variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
> - For an overview of the functional differences, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-desktop/...md).
## General Functions in the Ribbons
Some functions are available in both ribbons, while others are specific to MS Word or MS Excel. The following figures highlight the general functions in the ribbons for MS Word and MS Excel:
Word ribbon (Office for Desktop) containing the general functions for Disclosure Management
Excel ribbon (Office for Desktop) containing the general functions for Disclosure Management
Description of the general functions:
### Server
| Option | Description |
|---|---|
| Check In | The current file is saved in the database. **Comments** can be stored during the check-in process and are displayed in the document's history. |
| Update | Changes made are shown as a preview without having to check in the file. The file view is refreshed according to the current settings. |
### Files
| Option | Description |
|---|---|
| Event Reports | Opens the internal error logging system that flags invalid references, etc. (**Show Log**). In Word files, the **Layout Check** tab additionally shows the text and formatting deviations found by the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md). |
| Save File Locally | Saves the file in the local file directory. |
| Open Local File | Opens a file from the local file directory. |
| Recover Version | Opens or recovers a previous version of the document that is currently open. |
### Document Variables
| Option | Description |
|---|---|
| Document Variables | Inserts a document variable. Document variables are text building blocks that can be created in the document variable management tool and then easily inserted in every Word and Excel file of the current document. For more information, see the [Using Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md) chapter. |
## Special Functions in the Word Ribbon
The following specific functions are available in the Word ribbon:
### File
**Compare with Local Document** opens the local directory structure where a file can be selected for comparison.
### Integration
| Option | Description |
|---|---|
| Insert Table | Opens a dialog where a table can be selected from an Excel file to carry it over to the Word document. For more information, see [Inserting Tables in a Word Document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-outarea-in-worddocument.md). |
| Insert ESG text value | Opens a window that lets you insert text responses from an aggregated ESG report into the Word document. For more information, see [Inserting Texts From ESG Reports](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-texts-from-esg-reports.md). |
| Highlight tables | Highlights the tables contained in the Word document. Use the drop-down menu to choose which type of tables is highlighted. |
| Highlight body text number | Highlights the body text numbers and document variables contained in the Word document. For more information, see [Using Text Values in MS Word](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word-use-variables.md). |
| Remove locking of content controls | Removes the locking of the content controls contained in the Word document so that they can be edited again. |
### [XBRL](https://support.lucanet.com/en/documentation/glossary.md#xbrl)
| Option | Description |
|---|---|
| Insert XBRL Text Block Tag | Opens a window in MS Word where you can assign an XBRL text block tag to a selected area in the Word document. |
| Insert XBRL Footnote Tag | Opens a window in MS Word where you can assign an XBRL footnote tag to a selected area in the Word document. |
| Highlight XBRL Text Blocks | Highlights all XBRL text blocks in the current Word file and displays a comment field for all highlighted text blocks. |
More information on inserting XBRL tags can be found in [Inserting XBRL Tags](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags.md).
### Copilot
| Option | Description |
|---|---|
| Text adjustment | Opens a window in MS Word that allows you to optimize a selected text in the Word document with AI support. |
| Text draft | Opens a window in MS Word that enables you to create a taxonomy-compliant text with AI support. |
For more information on using the Copilot in Disclosure Management, see [Using Copilot for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/copilot-for-disclosure-mgmt.md).
## Special Functions in the Excel Ribbon
The following specific functions are available in the Excel ribbon:
### Name Manager
| Option | Description |
|---|---|
| Name Manager | Opens MS Excel's standard Name Manager. |
| Delete Names | Deletes a selected name from the Excel file. |
| Delete All Names | Deletes all names from the Excel file. |
### Cells
| Option | Description |
|---|---|
| Insert | Adds a new outarea. |
| Move | Shifts an outarea. |
| Insert Document Variable | Insertion of a document variable; document variables are text building blocks that can be created in the document variable management tool and then easily inserted in every Excel and Word file of the current document. |
| Insert ESG Table | Opens a dialog for inserting tables from an imported ESG report that was created with [Lucanet ESG Reporting](https://support.lucanet.com/en/documentation/esg-reporting.md). For more information, see [Inserting Tables From ESG Reports](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/insert-data-from-esg-reports.md). |
### Columns
| Option | Description |
|---|---|
| Name | Button for creating a name column |
| Value | Button for creating a value column |
| Prog | Button for creating a programming column |
| Other | Button for creating other columns, e. g. footnote columns |
For more information on inserting columns, see [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md).
### Settings
**Edit Properties** opens a dialog where the general properties of the Excel file can be configured.
### Layout
**Add Layout Area** defines an area where a specific layout from the **Layout Robot** is to be applied (see [Configuring Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md)). By doing so, you ensure that a table layout defined using the Layout Robot is implemented in the Word document.
---
---
title: "Ribbons for MS Office for the Web"
description: "Ribbons for MS Word and MS Excel in the MS Office for the Web variant."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web
language: en
last_updated: 2026-09-10
---
# Ribbons for MS Office for the Web
## Overview
In the **MS Office for the Web** variant, you work with the Disclosure Management ribbons directly in the browser.
The **Word ribbon** is split into two tabs:
- The [**DM-Content**](#dmcontent-tab) tab contains the content-related functions.
- The [**DM-Layout**](#dmlayout-tab) tab contains the layout functions.
The **[Excel ribbon](#excel-ribbon)** helps you program an MS Excel file for Disclosure Management.
> **Note:** - For a general overview of the available variants and their installation, see the [MS Office Variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
> - For an overview of the functional differences, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-for-web/...md).
## General Functions
The **Server** and **Lucanet** areas are available on both tabs.
### Server
| Option | Description |
|---|---|
| Check In | The current file is saved in the database. Comments can be stored during the check-in process and are displayed in the document's history. |
| Update | Changes made are shown as a preview without having to check in the file. The file view is refreshed according to the current settings. |
### Lucanet
| Option | Description |
|---|---|
| Help | Opens the help for Disclosure Management. |
## 'DM-Content' Tab
'DM-Content' tab of the Word ribbon in MS Office for the Web
### Highlight
| Option | Description |
|---|---|
| Set | Highlights the selected type of element with color. The drop-down offers the available highlight types (see below). |
| Remove | Removes highlights that have been set. The drop-down offers the highlight types to be removed (see below). |
Use the **Set** drop-down to choose which elements are highlighted:
| Option | Description |
|---|---|
| Disclosure-Management tables | Highlights the tables managed by Disclosure Management. |
| Non-Disclosure-Management tables | Highlights the tables that are not managed by Disclosure Management. |
| Document Variables | Highlights the document variables contained in the document. |
| Text Values | Highlights the body text numbers in the document. |
Use the **Remove** drop-down to remove the respective highlights:
| Option | Description |
|---|---|
| Disclosure-Management tables | Removes the highlight of the tables managed by Disclosure Management. |
| Non-Disclosure-Management tables | Removes the highlight of the tables not managed by Disclosure Management. |
| Document Variables | Removes the highlight of the document variables. |
| Text Values | Removes the highlight of the body text numbers. |
| Remove Coupler Highlights | Removes the highlights of the couplings. |
| Remove Data-Change Highlights | Removes the highlights of data changes. |
### Integration
| Option | Description |
|---|---|
| Insert table/chart | Opens a dialog where a table or chart can be selected from an Excel file to carry it over to the Word document. For more information, see [Inserting Tables in a Word Document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-outarea-in-worddocument.md). |
| Insert text values | Inserts a body text number from the document's data at the cursor position. |
| Document Variables | Inserts a document variable into the Word document. For more information, see the [Using Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md) chapter. |
| Assign Layout Actions | Assigns layout actions from the Layout Robot to the selected area so that a defined layout is applied in the result document. |
### File
| Option | Description |
|---|---|
| Event reports | Opens the internal error logging system that flags invalid references, etc. The **Layout Check** tab additionally shows the text and formatting deviations found by the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md). |
### Copilot
| Option | Description |
|---|---|
| Copilot | Opens the **Copilot** task pane, which lets you generate new text (**Writer** mode) or edit selected text (**Enhancer** mode) with AI support. The task pane switches between the two modes automatically, depending on whether text is selected. |
For more information on using the Copilot in Disclosure Management, see [Using Copilot for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/copilot-for-disclosure-mgmt.md).
## 'DM-Layout' Tab
'DM-Layout' tab of the Word ribbon in MS Office for the Web
### Text
| Option | Description |
|---|---|
| Style Guide | Opens the Style Guide pane, which displays the formats and content groups configured in the [Style Guide Manager](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md#configuring-the-style-guide-manager). |
| Special Characters | Opens a drop-down menu for inserting typographic special characters (see below). |
| Reset manual formatting | Resets manual formatting at the paragraph and character level so that the original styles are restored. |
Use the **Special Characters** drop-down to insert the following special characters:
| Option | Description |
|---|---|
| Em Dash | Inserts an em dash (—). |
| Non-Breaking Hyphen | Inserts a non-breaking hyphen that is not broken at the end of a line. |
| Soft Hyphen | Inserts a soft hyphen (an optional hyphenation point). |
| Non-Breaking Space | Inserts a non-breaking space that is not broken across lines. |
| Soft Line Break | Inserts a soft line break without starting a new paragraph. |
### Hanging Indent
| Option | Description |
|---|---|
| From Cursor Position | Creates a hanging indent from the current cursor position. |
| Expand | Increases the hanging indent. |
| Reduce | Decreases the hanging indent. |
| Reset | Resets the hanging indent. |
### Page Break
| Option | Description |
|---|---|
| Page Break | Inserts a page break at the cursor position. |
## Excel Ribbon
The Excel ribbon helps you program an MS Excel file for Disclosure Management. It provides the following functions:
Excel ribbon of Disclosure Management in MS Office for the Web
### Server
| Option | Description |
|---|---|
| Publish | Publishes the current Excel file and saves it in the database. |
| Update | Changes made are shown as a preview without having to publish the file. The file view is refreshed according to the current settings. |
### File
| Option | Description |
|---|---|
| Event reports | Opens the internal error logging system that flags invalid references, etc. |
| Mark Area | Marks an outarea in the Excel file. For more information, see [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md). |
| Document Variables | Inserts a document variable into the Excel file. For more information, see the [Using Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md) chapter. |
| Programming Assistant | Opens the programming assistant, which helps you program value and programming columns. For more information, see [Programming References](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/prog-references.md). |
### Copilot
| Option | Description |
|---|---|
| Area and column assistant | Opens the **Area and column assistant** task pane, which lets you detect outareas and their name, value, and programming columns automatically using AI. For more information, see [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md). |
### Layout
| Option | Description |
|---|---|
| Add Area Highlights | Highlights the defined outareas in the Excel file with color. |
### Settings
| Option | Description |
|---|---|
| Properties | Opens a dialog where the general properties of the Excel file can be configured. |
### Help
| Option | Description |
|---|---|
| Help | Opens the help for Disclosure Management. |
---
---
title: "Ribbons for MS Office Native"
description: "Functions in the DM-Content and DM-Layout tabs of the Word ribbon in the MS Office Native variant."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-native
language: en
last_updated: 2026-09-10
---
# Ribbons for MS Office Native
## Overview
In the **MS Office Native** variant, you use the ribbons from Office for the Web together with the locally installed Office programs (MS Word and MS Excel). Disclosure Management runs directly as an add-in in the locally installed Word desktop application.
In this variant, the **[Word ribbon](#word-ribbon)** is split into two tabs:
- The [**DM-Content**](#dmcontent-tab) tab contains the content-related functions.
- The [**DM-Layout**](#dmlayout-tab) tab contains the layout functions.
The **[Excel ribbon](#excel-ribbon)** helps you program an MS Excel file for Disclosure Management.
> **Note:** - For a general overview of the available variants and their installation, see the [MS Office Variants](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ms-office-variants.md) chapter.
> - For an overview of the functional differences, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-native/...md).
## Word Ribbon
The Word ribbon is split into the two tabs **DM-Content** and **DM-Layout**. The **Server** and **Lucanet** areas are available on both tabs.
### General Functions
The **Server** and **Lucanet** areas are available on both tabs.
#### Server
| Option | Description |
|---|---|
| Check In | The current file is saved in the database. Comments can be stored during the check-in process and are displayed in the document's history. |
| Update | Changes made are shown as a preview without having to check in the file. The file view is refreshed according to the current settings. |
#### Lucanet
| Option | Description |
|---|---|
| Help | Opens the help for Disclosure Management. |
### 'DM-Content' Tab
'DM-Content' tab of the Word ribbon in MS Office Native
#### Highlight
| Option | Description |
|---|---|
| Set | Highlights the selected type of element with color. The drop-down offers the available highlight types (see below). |
| Remove | Removes highlights that have been set. The drop-down offers the highlight types to be removed (see below). |
Use the **Set** drop-down to choose which elements are highlighted:
| Option | Description |
|---|---|
| Disclosure-Management tables | Highlights the tables managed by Disclosure Management. |
| Non-Disclosure-Management tables | Highlights the tables that are not managed by Disclosure Management. |
| Document Variables | Highlights the document variables contained in the document. |
| Text Values | Highlights the body text numbers in the document. |
Use the **Remove** drop-down to remove the respective highlights:
| Option | Description |
|---|---|
| Disclosure-Management tables | Removes the highlight of the tables managed by Disclosure Management. |
| Non-Disclosure-Management tables | Removes the highlight of the tables not managed by Disclosure Management. |
| Document Variables | Removes the highlight of the document variables. |
| Text Values | Removes the highlight of the body text numbers. |
| Remove Coupler Highlights | Removes the highlights of the couplings. |
| Remove Data-Change Highlights | Removes the highlights of data changes. |
#### Integration
| Option | Description |
|---|---|
| Insert table/chart | Opens a dialog where a table or chart can be selected from an Excel file to carry it over to the Word document. For more information, see [Inserting Tables in a Word Document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/insert-outarea-in-worddocument.md). |
| Insert text values | Inserts a body text number from the document's data at the cursor position. |
| Document Variables | Inserts a document variable into the Word document. For more information, see the [Using Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md) chapter. |
| Assign Layout Actions | Assigns layout actions from the Layout Robot to the selected area so that a defined layout is applied in the result document. |
#### File
| Option | Description |
|---|---|
| Event reports | Opens the internal error logging system that flags invalid references, etc. The **Layout Check** tab additionally shows the text and formatting deviations found by the [Layout Check](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md). |
#### Copilot
| Option | Description |
|---|---|
| Copilot | Opens the **Copilot** task pane, which lets you generate new text (**Writer** mode) or edit selected text (**Enhancer** mode) with AI support. The task pane switches between the two modes automatically, depending on whether text is selected. |
For more information on using the Copilot in Disclosure Management, see [Using Copilot for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/copilot-for-disclosure-mgmt.md).
### 'DM-Layout' Tab
'DM-Layout' tab of the Word ribbon in MS Office Native
#### Text
| Option | Description |
|---|---|
| Style Guide | Opens the Style Guide pane, which displays the formats and content groups configured in the [Style Guide Manager](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide.md#configuring-the-style-guide-manager). |
| Special Characters | Opens a drop-down menu for inserting typographic special characters (see below). |
| Reset manual formatting | Resets manual formatting at the paragraph and character level so that the original styles are restored. |
Use the **Special Characters** drop-down to insert the following special characters:
| Option | Description |
|---|---|
| Em Dash | Inserts an em dash (—). |
| Non-Breaking Hyphen | Inserts a non-breaking hyphen that is not broken at the end of a line. |
| Soft Hyphen | Inserts a soft hyphen (an optional hyphenation point). |
| Non-Breaking Space | Inserts a non-breaking space that is not broken across lines. |
| Soft Line Break | Inserts a soft line break without starting a new paragraph. |
#### Hanging Indent
| Option | Description |
|---|---|
| From Cursor Position | Creates a hanging indent from the current cursor position. |
| Reset | Resets the hanging indent. |
| Expand | Increases the hanging indent. |
| Reduce | Decreases the hanging indent. |
#### Page Break
| Option | Description |
|---|---|
| Page Break | Inserts a page break at the cursor position. |
#### Typography
| Option | Description |
|---|---|
| Reset Spacing | Resets the character spacing of the selected text to the default value. |
| Expand Spacing | Increases the character spacing of the selected text. |
| Reduce Spacing | Decreases the character spacing of the selected text. |
| Expand Word Spacing | Increases the spacing between words in the selected text. |
| Reduce Word Spacing | Decreases the spacing between words in the selected text. |
## Excel Ribbon
The Excel ribbon helps you program an MS Excel file for Disclosure Management. It provides the following functions:
Excel ribbon of Disclosure Management in MS Office Native
### Server
| Option | Description |
|---|---|
| Publish | Publishes the current Excel file and saves it in the database. |
| Update | Changes made are shown as a preview without having to publish the file. The file view is refreshed according to the current settings. |
### File
| Option | Description |
|---|---|
| Event reports | Opens the internal error logging system that flags invalid references, etc. |
| Mark Area | Provides functions for creating and editing outareas and columns of the Excel file. For more information, see [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md) and [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md). |
| Document Variables | Inserts a document variable into the Excel file. For more information, see the [Using Document Variables](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/use-document-variable.md) chapter. |
| Programming Assistant | Opens the programming assistant, which helps you program value and programming columns. For more information, see [Programming References](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/prog-references.md). |
### Copilot
| Option | Description |
|---|---|
| Area and column assistant | Opens the **Area and column assistant** task pane, which lets you detect outareas and their name, value, and programming columns automatically using AI. For more information, see [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md). |
### Layout
| Option | Description |
|---|---|
| Add Area Highlights | Highlights the defined outareas in the Excel file with color. |
### Settings
| Option | Description |
|---|---|
| Properties | Opens a dialog where the general properties of the Excel file can be configured. |
### Help
| Option | Description |
|---|---|
| Help | Opens the help for Disclosure Management. |
For a comparison of the functions in the **MS Office for the Web**, **MS Office Native**, and **MS Office for Desktop** variants, see the [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt/ribbons-office-native/...md) chapter.
---
---
title: "Rolling Forward or Copying a Document"
description: "The ‘Roll forward/copy’ workspace in Lucanet Disclosure Management provides an easy way of creating a successor document."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/perpetuate-copy-doc-disclmgmt
language: en
last_updated: 2026-05-01
---
# Rolling Forward or Copying a Document
## Overview
The **Roll forward/copy** workspace in Lucanet Disclosure Management provides an easy way of creating a successor document.
## Opening the Workspace
In the overview of a document, click **Roll forward/copy** to open the workspace. The workspace is displayed as follows, for example:
Copy or roll forward a document
## Defining the Target Document Type
First, select whether you want to create a **Copy** or a **Roll forward**. The processes of rolling forward and copying a document differ in the following ways:
> **Tip:** - When **rolling a document forward**, all the document’s periods are rolled forward based on their hierarchy, and the current period is used as the previous period in the new document. Unlike when copying a document, this process does not create an exact copy; instead, the periods in the document are moved forward in time.
> - When **copying** a document, the whole document is copied, with the option to include all the created Office files and all the defined validations associated with it.
Proceed as follows:
| Option | Description |
|---|---|
| **As copy** | Click this option to create a copy. |
| **As roll forward** | Click this option to roll the document forward. |
The options that are subsequently displayed will vary depending on your selection.
## Configuring a Copy or Roll Forward
The following options are available:
| Option | Description |
|---|---|
| Source document | Name of the document for which you wish to create a copy or roll forward, and the source document reporting date. |
| Target document | Name of the target document you want to create; this is set by default to the name of the current document with the prefix **Copy of**. Also shows the target document reporting date. |
| Default status | The initial status you want to set for the copy or roll over of your document. |
| Copy document structure only | All MS Office files will be excluded from the copying process. The copy you create will only contain the document structure of the source document. If this check box is activated, the period table will be hidden. |
| Remove attachments | The attachments in the source document will not be included in the copied or rolled-over document. |
| Color MS Word texts | All the texts from the Word files will be highlighted in your copied and rolled-over documents. The **Color MS Word texts** option is useful if you want to highlight the parts of the text that still need to be revised or checked, for example. |
| Period table | **Source period**: The **Source period** column shows all the periods in the source document. **Copy period**: Periods whose **Copy period** check box is activated will be copied from the source document into the target document. **Target period**: Period in the target document to which the source period in question will be added. **Copy comments**: Comments whose **Copy comments** check box is activated will be copied from the source document into the target document. |
| Extract document to file | Disclosure Management allows you to create extracts of documents so you can send them to Lucanet Amana Consulting for auditing or inspection, for example. Once creation of the extract is complete, a message will appear in the [Notification window](https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt/notifications.md). You can use this dialog to download your extracted report. |
| Create copy | Creates the copy of the source document using the selected options. Once creation of the copy is complete, a corresponding message will appear in the [Notification window](https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt/notifications.md). The new document will appear in the [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md) under the name you have given it. You can now open it from there. |
> **Note:** If the original document contains Word references, they initially still point to the old source document in the copied or rolled-forward document. For information on how to re-point these Word references, see [Re-Pointing Word References with Lucanet Lume to a New Source Document](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/use-word-references.md#re-pointing-word-references-with-lucanet-lume-to-a-new-source-document).
---
---
title: "Style Guide"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt/style-guide
language: en
last_updated: 2026-05-01
---
# Style Guide
## Overview
In Lucanet **Disclosure Management**, the **Style Guide** gives you a central tool for binding the design of your reports to your corporate design in a consistent way.
> **Warning:** The Style Guide is only available in **Office Native** and **Office for the Web**.
With the Style Guide, you store your company's formatting rules as an XML file centrally in Disclosure Management. As a result, all authors work with the same specifications for fonts, headings, body text, and other text elements. This prevents visual inconsistencies between chapters or contributors from the outset and reduces the effort required for the final layout alignment.
The Style Guide Manager is also where you manage **Content Groups**, which let you dynamically show or hide sections of your result documents for different audiences (see the [Content Groups](#content-groups) section).
> **Note:** The functions described here require an **Advanced** license or higher.
## How the Style Guide Manager works
On the Style Guide tab in the **Configure document** work area, you manage the **Style Guide Manager** per document language. In the **Style Guide Manager**, you define which formats are available in Word documents for your reports. The styles defined in a Word template (Word styles) can be structured into groups, and you can control which styles are available for the respective content section of a report. The Style Guide Manager is displayed in the **Configure document** work area as follows, for example:
Groups displayed in the Style Guide Manager
The Style Guide Manager configuration has the following effect: In Word documents, the **Style Guide** button is available in the **DM-Layout** [Disclosure Management ribbon](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md). Use it to show a pane in MS Word that displays the formats configured in the Style Guide Manager:
'DM-Layout' Disclosure Management ribbon
As a user, you therefore do not need to distinguish between permitted and non-permitted styles, because all permitted formats are displayed and provided in a structured way in MS Word.
## Opening the Style Guide Manager
To open the Style Guide, proceed as follows:
1. Open a document and click **Configure document**.
2. Open the **Style Guide** tab. The **Style Guide** tab is displayed as follows, for example:
The 'Style Guide' tab in the 'Configure document' work area
On the left, the **Style Guide Manager** shows the **style groups** and the **content groups**; on the right, it shows the available **styles**.
## Configuring the Style Guide Manager
To configure the Style Guide Manager, you generally perform the following steps:
- You can import a **firesys** Word template (see the **Importing a Style Guide** section).
- You can assign styles to the predefined default style groups (**Headings** and **Text**) by dragging and dropping them from the list of available formats.
- You can create your own style groups and assign styles to them by dragging and dropping them from the list of available formats.
### Predefined style groups
The following style groups are predefined and cannot be deleted or renamed:
| Style group | Purpose |
|---------|---------|
| Headings | Word styles for headings (for example, Heading 1 to Heading 9, Title, Subtitle). |
| Text | Word styles for body text (for example, Body Text, Normal, Quote). |
| System styles | Styles that Disclosure Management uses on a regular basis (for example, for comments and callouts) and that cannot be changed or reassigned here. |
Click the style group's name to expand or collapse the section. Next to the name, the number of styles currently assigned to the style group is displayed (for example, **"Headings 1"**).
### Creating a Style Group
In addition to the predefined style groups, you can create your own style groups. To create a style group, proceed as follows:
1. In the **Style Guide Manager**, click **\+ Add Style Group**.
2. In the **Group name** field, enter a name for the style group. Click **Save**.
3. The new style group then appears in the **Style Guide Manager**.
### Further Actions for Style Groups
The following additional functions are available for your own style groups:
- **Change name**: In the style group's row, click the **edit icon** and adjust the **name** as required in the dialog that follows.
- **Delete style group**: In the style group's row, click the **delete icon** and confirm the security prompt.
- **Change order**: Each style group is preceded by an icon for dragging the style group: the change order icon. Use it to drag a style group to the desired position.
## Word Styles
After creating the style groups, you assign them the Word styles from the imported Word template.
### Assigning Word Styles
The **Available Styles** area on the right lists all Word styles imported from the Word template, sorted by style group assignment. Above the section, you find:
- The **Import** button for importing a Style Guide configuration (see below).
- The **Search styles...** field for filtering the styles by name.
By default, the **Unassigned** section is expanded and contains all styles that are not yet assigned to a group. The number of unassigned styles is shown in the heading (for example, **Unassigned · 91 styles**).
### Assigning a Style to a Style Group
To assign a style to a style group, proceed as follows:
1. Find the desired style in the Available Styles area (using the search field if necessary).
2. On the left in the Style Guide Manager, expand the desired target style group so that the **Drop Styles here** field is visible:
The **Drop Styles here** field of the expanded target style group.
3. Click the change order icon and drag the style into the **Drop Styles here** field of the desired style group on the left.
4. Drop the style. The status of the style changes from **Unassigned** to the name of the target style group.
5. In the **Available Styles** area, all assigned styles are displayed in the **Assigned** section.
## Assigning Styles in the Word Document
Once the styles are configured in the Style Guide Manager, you assign them to a text passage in the Word document via the **Style Guide** task pane.
> **Warning:** The Style Guide is only available in **Office Native** and **Office for the Web**.
To assign a style to a text passage, proceed as follows:
1. Open the desired document.
2. Click **Style Guide** on the Word ribbon (**DM-Layout** tab, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md)).
The Word window **Style Guide** is displayed:
'Style Guide' window in MS Word
3. Select the desired text passage in the Word document.
4. In the **Style Guide** Word window, click the desired style.
The style is applied to the selected text passage. If a style is already assigned to the current cursor position, the corresponding entry in the task pane shows a checkmark. For most style categories (for example, alignment), only one style can be assigned at a time; clicking another style in the same category replaces the previous assignment.
> **Note:** Assigning content groups follow the same operating principle: select a text passage, then choose the desired content group (see the [Assigning Content Groups in the Word Document](#assigning-content-groups-in-the-word-document) section).
## Content Groups
With **Content Groups**, you can assign sections of your Word documents to one or more audiences, for example **Intern**, **Stakeholder**, or **Management**.
When creating a result document, you select the content groups whose content should be included. Content without an assigned content group is always included. Content assigned to one or more content groups is included as soon as at least one of these content groups is selected; otherwise, it is removed. This lets you generate multiple audience-specific report versions from a single source document, without maintaining the content multiple times.
> **Note:** For information on how to assign a content group to a text passage in the Word document, see the [Assigning Content Groups in the Word Document](#assigning-content-groups-in-the-word-document) section.
In the **Style Guide Manager**, content groups are managed in the **Content Groups** area, separate from the style groups for styles:
The 'Content Groups' area in the Style Guide Manager
### Creating a Content Group
To create a new content group, proceed as follows:
1. In the **Content Groups** area, click **+ Add Content Group**.
The **Add Content Group** dialog is displayed as follows, for example:
The 'Add Content Group' dialog
2. In the **Name** field, enter a name for the content group.
3. In the **Color** field, select a color from the list of available colors. The color identifies the content group in the Style Guide Manager and when creating a result document.
4. Optional: Expand the **Advanced** area and assign the content group a firesys source color in the **firesys color** field (see the [Assigning a firesys Color](#assigning-a-firesys-color) section).
5. Click **Save**.
### Assigning Content Groups in the Word Document
You assign a content group to a text passage in the Word document the same way as any other style, via the **Style Guide** task pane (see [Assigning Styles in the Word Document](#assigning-styles-in-the-word-document)).
To assign a content group to a text passage, proceed as follows:
1. Open the desired document.
2. Click **Style Guide** on the Word ribbon (**DM-Layout** tab, see [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md)).
The **Style Guide** task pane is displayed.
3. Select the desired text passage in the Word document.
4. In the **Style Guide** task pane, in the **Content Groups** area, click the desired content group.
The content group is assigned to the selected text passage.
If a text passage has a content group assigned, MS Word indicates this as follows:
- Clicking into the text passage shows the tag of the assigned content group.
Tag of an assigned content group after clicking into the text passage
- Hovering the mouse over the text passage shows the color of the assigned content group, if a color is defined for the group.
Color of an assigned content group when hovering the mouse over it
### Further Actions for Content Groups
The following functions are available for existing content groups:
- **Edit**: In the content group's row, click the **edit icon** to change the name or firesys color. The color can only be changed as long as the content group is not yet assigned to any text passage in a chapter.
- **Delete**: In the content group's row, click the **delete icon** and confirm the security prompt. A content group can only be deleted once it is no longer assigned to any text passage.
- **Change order**: Drag a content group by its preceding icon to the desired position.
### Assigning and Reviewing Content Groups in the Word Document
In the **Content Groups** area of the **Style Guide** Word task pane, you can assign content groups to the current selection, remove assignments, and review text passages that already have a content group assigned. You manage the content groups themselves in the Style Guide Manager under **Configure document > Style Guide**.
'Content Groups' area in the 'Style Guide' window
The following functions for content groups are available in the **Style Guide** Word window:
- **Assigning and removing**: A checkmark next to a content group indicates that it is assigned to the currently selected text passage (see [Assigning Styles in the Word Document](#assigning-styles-in-the-word-document)). Unlike other style categories, a text passage can have more than one content group assigned at the same time. Clicking an already assigned content group removes only that assignment, without removing any other content groups assigned to the same text passage.
- **Counting and browsing occurrences** (Office for the Web only): The number next to the group name shows the number of occurrences assigned in the document. The arrow icons let you jump directly to the previous or next occurrence, relative to the current cursor position; from the last occurrence, navigation jumps back to the first, and vice versa. If a content group has no assigned occurrences, the row shows the count **0** and both arrow icons are disabled.
- **Highlighting assigned text passages**: The eye icon shows the Word highlighting for all text passages that have the content group assigned. This does not use a Word highlighter color.
Use the **Reset** button below the list to remove the highlighting for all content groups at once, instead of hiding each group individually via its eye icon. The button only removes the visual highlighting, not the assignments themselves.
> **Note:** Navigation via the arrow icons does not change the document – no highlighting is applied, so your own manual highlights are preserved.
### Assigning a firesys Color
If you previously worked with **firesys**, you can optionally assign a content group a **firesys color** in the **Advanced** area. This assignment supports a later migration of firesys documents with color-coded text passages to the matching content group. By default, no firesys color is assigned (**None**).
> **Note:** The automated migration of existing firesys documents based on this assignment is performed via the **Information** area of the event reports in MS Word. For more information, see [Migrating firesys Content to Content Groups](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/reviewing-layout-check-violations.md#migrating-firesys-content-to-content-groups).
Which content groups are taken into account when creating a result document is defined in the [Creation](https://support.lucanet.com/en/documentation/disclosure-management/create-resulting-document.md#configuring-a-result-document) workspace.
## Importing a Style Guide
Using the **Import** button above the **Available Styles** list, you can import an existing Style Guide configuration from firesys. Proceed as follows:
1. Click **Import**. The **Style Guide Import** dialog is displayed.
2. Drag and drop the import file into the upload area, or click **Browse** to select the file.
3. Click **Import**.
---
---
title: "The Lucanet Disclosure Management User Interface"
description: "This page contains information about the structure of the user interface and the most important elements in Lucanet Disclosure Management. From this page, you can jump easily to the detailed descriptions of the individual areas and functions."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt
language: en
last_updated: 2026-05-01
---
# The Lucanet Disclosure Management User Interface
## Overview
This page contains information about the structure of the user interface and the most important elements in **Lucanet Disclosure Management**. From this page, you can jump easily to the detailed descriptions of the individual areas and functions.
## Structure of the User Interface
When you first open the Disclosure Management solution from your main menu, you will see the **Lucanet Disclosure Management** **application window**. By default, the **Dashboard** functional area opens first.
The **application window** is usually divided into two areas: the **function bar** and the **detail view**. For some functional areas, you will also see an **overview** displaying the main **workspaces** for the functional area in question.
Disclosure Management user interface
The following elements are available in the user interface:
#### Function bar
This is used to navigate between the individual functional areas in Disclosure Management. The following areas are available:
- **Dashboard**: Displays an overview of all the documents that have been created, and provides the ability to filter the documents according to certain criteria. You can also use this area to create new documents. For more information, see [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md).
- **Document**: Opens the **Cockpit** for the document that is selected in the dashboard. You can use the cockpit to manage documents. For more information, see [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
- **Toolbox**: Provides the [Dispatcher](https://support.lucanet.com/en/documentation/glossary.md#dispatcher) and the Office ribbons you will need to use Lucanet Disclosure Management. For more information, see [Installing and Updating the MS Office Components](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/install-disp-andribbon.md).
- **Import Management**: Allows you to configure connections and data sources for importing data to edit in Disclosure Management. For more information, see [Importing Data](https://support.lucanet.com/en/documentation/disclosure-management/import-data-disclmgmt.md).
- **Role Management**: Provides an overview of the user roles and the associated solution-wide and document-specific permissions, and allows you to assign these roles and permissions. For more information, see [Managing User Roles for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt.md).
- **Disclosure Management Settings**: Allows you to configure individual preferences for how certain areas in Disclosure Management will be displayed. These preferences apply to all documents. For more information, see [Disclosure Management Settings](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/discl-mgmt-settings-disclmgmt.md).
- **Notifications**: Provides information on the status of various process steps in Disclosure management, such as the creation of result documents and the importing of data. You can open documents or copies thereof that have been created successfully directly by clicking the corresponding notification. For more information, see [Notifications](https://support.lucanet.com/en/documentation/disclosure-management/user-interface-disclmgmt/notifications.md).
#### Overview
This is used to navigate between the **workspaces** of the individual functional areas in Disclosure Management.
It is not possible to display an overview for the [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md) or [Disclosure Management Settings](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/discl-mgmt-settings-disclmgmt.md) functional areas.
#### Detail view
Here, you can view and edit the details of the individual workspaces. What is displayed in the detail view depends on which workspace has been chosen.
---
---
title: "Transferring User Roles to Another User with Lucanet Lume"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/transfer-user-roles-lume-disclmgmt
language: en
last_updated: 2026-07-31
---
# Transferring User Roles to Another User with Lucanet Lume
## Overview
With Lucanet Lume, you can transfer a user's document- and chapter-level roles to another user directly via a chat command, instead of working through Role Management manually for every document and chapter.
Lucanet Lume reads all of the source user's document- and chapter-level roles and assigns them to the target user in addition to their existing roles. Existing role assignments of the target user are kept, and roles the target user already has are skipped. No roles are removed.
[Global roles](https://support.lucanet.com/en/documentation/disclosure-management/basic-configuration-disclmgmt/role-mgmt-disclmgmt/assign-global-roles-disclmgmt.md) are not part of this transfer; existing global roles of both users remain unchanged. The source user's roles are not changed by the transfer.
## Prerequisites
- You need the **Administrator** role for Disclosure Management, at the **Professional** license level.
- The source and target users must be two different users who are activated for Disclosure Management in the User Management area of the Lucanet CFO Solution Platform.
## Instructions
To transfer the roles of one user to another user with Lucanet Lume:
1. Open Lucanet Lume and describe, in natural language, which user roles should be transferred, for example:
"Transfer the permissions of [name of the source user] to [name of the target user]."
Transferring user roles with Lucanet Lume
2. Lucanet Lume resolves both users and shows a preview of the planned changes, split into two sections:
- Roles to be added to the target user
- Roles the target user already has, which remain unchanged
Each entry shows the role name, the scope (document or chapter), and the title of the affected document or chapter. Global roles of both users are listed in a separate, informational-only section and are excluded from the transfer. No permissions are changed yet.
3. Review the preview and confirm the transfer in Lucanet Lume.
4. After confirmation, Lucanet Lume applies the changes: the missing document- and chapter-level roles are added to the target user. Lucanet Lume then returns a summary of the roles added.
## Canceling the Transfer
If you cancel or close the conversation with Lucanet Lume before confirming, no permissions are changed and no audit log entry is created.
---
---
title: "Using Copilot for Disclosure Management"
description: "All Word documents can be optimized with AI assistance using Copilot for Disclosure Management. You can adjust your texts quickly and easily or generate completely new drafts. The Writer function helps you efficiently and accurately create taxonomy-compliant reports by generating text for any disclosure label that meets IFRS or ESRS requirements. With the Enhancer function, you can optimize your texts:"
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/copilot-for-disclosure-mgmt
language: en
last_updated: 2026-09-10
---
# Using Copilot for Disclosure Management
## Overview
All Word documents can be optimized with AI assistance using **Copilot for Disclosure Management** – in **Office for the Web**, **Office Native**, and **Office for Desktop**. You can adjust your texts quickly and easily or generate completely new drafts.
- The **Writer** function helps you efficiently and accurately create taxonomy-compliant reports by generating text for any disclosure label that meets **IFRS** or **ESRS** requirements.
- With the **Enhancer** function, you can optimize your texts using the following features:
- Change the tone of the text (positive, neutral, negative)
- Shorten a text
- Make a text more detailed
- Create a bulleted list
- Create a headline
- Using the **Insert ESG text values** function (**Office for Desktop** only), you can create a report at group level from the disclosures of the subsidiaries. The function significantly simplifies and automates the process of preparing group disclosures.
The Excel ribbon provides the **Area and column assistant** in the same **Copilot** area, which lets you detect outareas and their name, value, and programming columns in MS Excel automatically using AI. For more information, see [Using the Area and Column Assistant](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant.md).
> **Warning:** To use Copilot, you need at least the **Advanced** license.
For a comparison of the functions in the individual variants, see [Comparison: MS Office for the Web, MS Office Native, and MS Office for Desktop](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md#comparison-ms-office-for-the-web-ms-office-native-and-ms-office-for-desktop).
## Office for the Web and Office Native
### Starting Copilot
In **Office for the Web** and **Office Native**, you start Copilot using the **Copilot** button on the **DM-Content** tab of the Word ribbon (**Copilot** area). This opens the **Copilot** task pane.
'Copilot' button on the Word ribbon
The task pane automatically switches between the **Writer** and **Enhancer** modes, depending on whether text is selected in the document:
- If **no text is selected**, the **Writer** mode is active.
- If **text is selected**, the task pane automatically switches to the **Enhancer** mode.
There is no manual toggle between the two modes. An info icon ⓘ next to the **Copilot** heading shows a tooltip explaining the two modes when you hover over it.
### Drafting Text
If no text is selected in the document, Copilot opens in **Writer** mode with the description **Generate a new narrative based on the parameters selected below.**
To generate a new text:
1. Click **Copilot** on the **DM-Content** tab of the Word ribbon.
The **Copilot** task pane is displayed in **Writer** mode:
Copilot in Writer mode in Office for the Web
2. In the **Taxonomy** drop-down list, choose the desired taxonomy.
3. In the **Disclosure label** drop-down list, choose the desired disclosure label.
4. Optionally, in the **Tone** drop-down list, choose the desired tone.
5. Optionally, enter company-specific information in the **Additional information** text field that is relevant to the selected disclosure label.
6. Click **Generate**.
The generated text is displayed under the heading **Report** in the task pane.
7. Click **Apply** to insert the text into the document, **Discard** to delete it, or **Copy** to copy it to the clipboard. If necessary, change the selection and click **Generate** again if the result is not satisfactory.
### Adjusting Text
If you select text in the document, Copilot automatically switches to **Enhancer** mode with the description **Edit or review selected text in the document.**
To adjust selected text:
1. Select the text that you want to improve.
The **Copilot** task pane automatically switches to **Enhancer** mode:
Copilot in Enhancer mode in Office for the Web
2. In the **Edit or review selection** drop-down list, choose the desired option (see section **Options for Text Enhancement**).
3. Optionally, in the **Tone** drop-down list, choose the desired tone.
4. Optionally, enter additional information in the **Additional information** text field.
5. Click **Generate**.
The edited text is displayed under the heading **Report** in the task pane.
6. Click **Apply** to replace the text in the document, **Discard** to delete the result, or **Copy** to copy it to the clipboard. If necessary, change the selection and click **Generate** again if the result is not satisfactory.
## Office for Desktop
### Starting Copilot
You can start Copilot for Word documents in Disclosure Management directly from the Word ribbon:
Start Copilot for Disclosure Management from the Word ribbon
### Drafting Text
With the **Writer** function, you can create and insert new text for Word documents. To do this, select a label for which the AI should generate text. Additionally, you can provide company-specific information in a text field.
The function then automatically generates taxonomy-compliant text sections for the specified label and incorporates any additional company-specific information provided into the generated text. The two taxonomies, **IFRS** and **ESRS** are taken into account.
To create a text for a label:
1. Click **Writer** on the Word ribbon.
The **Copilot - Writer** window will appear in the Word document:
Draft text using Copilot for Word documents in Disclosure Management
2. Choose either **IFRS** or **ESRS** under Taxonomy.
3. Choose a disclosure label from the **Disclosure Label** drop-down list.
4. Optionally, enter company-specific information in the **Additional information** text field that is relevant to the selected disclosure label.
5. Click **Generate**.
6. Click **Accept** to insert the result into the document. If necessary, change the settings and click **Generate** again if the result is not satisfactory.
### Adjusting Text
With the **Enhancer** function, you can tailor an existing text in a Word document according to your needs.
To adjust text:
1. Select the text that you want to improve.
2. Click **Enhancer on the Word ribbon.** The **Copilot - Enhancer** window will appear in the Word document:
Adjust text using Copilot for Word documents in Disclosure Management
3. Configure the Copilot as required (see section **Options for Text Enhancement**).
4. Click **Generate**.
5. Click **Accept** to insert the result into the document. If necessary, change the settings and click **Generate** again if the result is not satisfactory.
### Inserting ESG Text Values
With the help of the function **Insert ESG text values**, reports at group level can be created based on the disclosures of the subsidiaries using the Copilot. The function significantly simplifies and automates the creation process for group disclosures.
- The function is capable of automatically generating the final ESRS-compliant sustainability report at group level based on the disclosures from the subsidiaries.
- As a user, you can choose a question from the ESG questionnaire and view the different answers of the subsidiaries.
- You can add additional information.
- You can discard the result at any time and create the report again.
- If the result matches your requirements, you can add it to your document by clicking it.
To use the **Insert ESG text value** function:
1. Click **ESG text value** on the Word ribbon.
The **Insert ESG text value** window will appear in the Word document:
Draft text using Copilot for Word documents in Disclosure Management
2. In the **Report file** drop-down list, choose the report from which the ESG data are to be read from.
3. In the drop-down list **Question from ESG Reporting**, choose the desired question.
4. In the list **Choose a reporting entity**, activate the checkboxes of the reporting entities whose data is to be included in the overall report.
5. Optionally, enter additional information in the **Additional information** text field that is to be added to the report.
6. In the **Tone** drop-down list, choose the desired tone for the report.
7. Click **Generate**.
8. Click **Accept** if you want to insert the result into the document. If necessary, change the settings and click **Generate** again if the result is not satisfactory.
## Options for Text Enhancement
The following AI options are available for enhancing texts in a Word document in Disclosure Management:
| Option | Description |
|---------|---------|
| Change tone | Changes the tone of the selected text. |
| Rephrase | Rephrases the selected text. |
| Elaborate | Formulates the selected text in more detail and adds context information if necessary. |
| Shorten | Shortens the selected text. |
| Create bullet list | Creates a list of bullet points from the selected text. |
| Create numbered list | Creates a numbered list from the selected text. |
| Create headline | Creates a heading for the selected text. |
> **Note:** For the **Change tone**, **Rephrase**, **Elaborate**, and **Shorten** options, the inserted text keeps the paragraph style the selected text already had, instead of being reset to Word's "Standard" style.
---
---
title: "Using Layout Actions in MS Word"
description: "With the help of layout actions, you can apply a layout you have defined in Lucanet Disclosure Management’s layout robot to an Excel worksheet that you want to insert in Word."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_insert_layout
language: en
last_updated: 2026-09-10
---
# Using Layout Actions in MS Word
## Overview
With the help of **layout actions**, you can apply a layout you have defined in Lucanet Disclosure Management’s **layout robot** to an Excel worksheet that you want to insert in Word.
> **Note:** By saving a **layout robot**, you can use **layout actions** in MS Excel and MS Word to give your tables a uniform design. Use the [Configure document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) option to assign a layout robot to a document.
## Opening the Layout Actions Assistant
How you open layout actions depends on the selected MS Office variant. The subsequent configuration of the layout action is identical in all variants (see section [Configuring Layout Actions](#configuring-layout-actions)).
### Office for the Web and Office Native
To use layout actions in **Office for the Web** and **Office Native**:
1. In the Word document, position your cursor in the table to which you want to apply layout actions.
2. On the **DM-Content** tab of the Word ribbon, click the **Layout Actions zuweisen** button.
The **Layout Actions zuweisen** task pane is displayed on the right:
'Layout Actions zuweisen' task pane in Office for the Web and Office Native
3. Configure the layout action (see [Configuring Layout Actions](#configuring-layout-actions)), then click **Save**.
### Office for Desktop
To use layout actions in **Office for Desktop**:
1. In the Word document, position your cursor in the table to which you want to apply layout actions.
2. Go to the **Word ribbon** and click the **Insert layout actions** button.
Open the ‘Layout Action’ dialog from the Word ribbon
3. The **Layout Action** dialog is displayed in MS Word:
'Layout Action’ dialog
4. Configure the layout action (see [Configuring Layout Actions](#configuring-layout-actions)), then click **Apply**.
After a document update, the table that was selected beforehand is selected again, so you stay where you were working.
## Working Through Several Tables in Sequence
In **Office for Desktop**, the Layout Actions Assistant can apply a layout action and move straight on to the next table, so that you do not have to scroll through the document to find it. This is useful in chapters that contain several tables.
The assistant offers the following options in addition to **Apply**:
| Option | Description |
|---|---|
| Previous | Applies the current layout action to the selected table without running a document update, then selects the previous Disclosure Management table in the document.
**Note:** The option is not available while the first Disclosure Management table in the document is selected.
|
| Next | Applies the current layout action to the selected table without running a document update, then selects the next Disclosure Management table in the document.
**Note:** The option is not available while the last Disclosure Management table in the document is selected.
|
Only Disclosure Management tables are taken into account. Plain Word tables in the same document are skipped.
After each jump, the assistant displays the layout action of the newly selected table, so you can adjust it before moving on.
> **Note:** **Previous** and **Next** deliberately do not run a document update. Use **Apply** when you want the document to be updated as well.
## Configuring Layout Actions
Unless stated otherwise, the following configuration options apply to all MS Office variants – **Office for the Web**, **Office Native**, and **Office for Desktop**. The example screenshots in this section are taken from **Office for Desktop**.
The following options are available in the **Layout Action** dialog:
### General
'General' area in the 'Layout Action' dialog
In the **General** section of the **Layout Action** dialog, you can select and configure the table layouts defined in the layout robot.
| Option | Description |
|---|---|
| Layout Action | Click the corresponding table in the Word document and select the required layout from the drop-down list. **Note:** If there are no entries in the **Layout Action** drop-down list, you will first need to assign a layout robot to your document under [Configure document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md). |
| Table scaling | Available in **Office Native** only. In the drop-down list, select the scaling percentage to be applied to the table. Table width, spacing, and font size are adjusted proportionally, so that a table that is otherwise too large fits on one page. |
### Parameter
'Parameter' area in the 'Layout Action' dialog
### Description
In the **Parameter** section of the **Layout Action** dialog, you can edit the properties of the table. The following options are available:
| Option | Description |
|---|---|
| Table width | The absolute width of the table in cm, e.g. **15.5**. Equivalent to the **Preferred width** table property in MS Word. |
| Double tab position | Moves the number in the table by the specified factor in order to ensure the numbers wrap around existing footnotes or brackets, for example. This value is specified in cm, e.g. **\- 0.2** would move the numbers **2 mm** to the left. You can find an example at the bottom of the table. |
| Table indent | The indent of the table in cm, e.g. **2**. Equivalent to the **Indent from left** table property in MS Word. |
| First layout column | Numerical value indicating which column should be treated as the first layout column. Layout columns are empty columns created between value columns in MS Excel.
Layout columns are used purely for aesthetic reasons.
If a column does not contain any content and its width is <= 0.5 px, the layout robot will register it as a layout column. |
| First double tab column | Numerical value indicating which column should be the first to include a double tab. |
| Do not separate paragraphs | Prevents paragraph breaks in the table, ensuring it stays together as intended. |
| Invert zebra | Inverts the pattern of alternating colors used in a table (e.g. each white column is followed by a gray one, etc.). |
| Do not apply double tab to percentage values | The position of the double tab entered under the **Double Tab position** option is not applied to percent values. |
Example for the **Double tab position** option: In the example below, negative numbers are written in brackets in MS Excel. This has resulted in the numbers no longer being positioned below one another (left-hand column). Entering a double tab in MS Excel will realign the numbers so they are below one another again (right-hand column):
Using a DoubleTab to align numbers one below the other in MS Word
### Columns
'Use generic column widths' in the 'Layout Action' dialog
'Use fixed column widths' in the 'Layout Action' dialog
In the **Columns** section of the **Layout Action** dialog, you can edit the column widths of the selected table. The following options are available:
| Option | Description |
|---|---|
| Use generic column widths | Combination of fixed and calculated column widths. For example, you can enter the widths for **number columns** and **layout columns** (in **cm**). The width of the name column is then calculated automatically. This value is specified in **cm**. Alternatively, you can use an **Auto** column; the column width will then be calculated automatically based on the value you enter in the other column. **Note:** You can use **generic column widths** if your table regularly alternates between column types, e.g. Name column, **Layout** column, **Value** column, **Layout** column, **Value** column, etc. |
| Use fixed column widths | Use this option to define fixed column widths. When using fixed column widths, you will need to enter the width of each column in turn, in cm. Each width should be separated with a hash (#), e.g. **0.3#1.2#2.0#3#4.1**. Instead of a specific size value, you can also use **Auto**, e.g.: **auto#2.5#1.3**. The column width will then be calculated automatically based on the values you have entered for the other columns. **Note:** You can use **fixed column widths** if you don’t want your columns to alternate regularly, e.g. if you want several Name columns next to each other. |
> **Note:** A separate layout robot can be stored for each document in Lucanet Disclosure Management.
>
> To assign a layout robot to a document, you must open the Configure document workspace and add a layout robot in the Layout Robot settings area (see also [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md)).
>
> This is also where you can use the icon to save an already assigned layout robot locally, e.g. to use it in another document.
>
> the shows 'configure document' workspace. 'layout robot settings' area is displayed. options for layout robot are outlined in red. icon
> Assign, save, or delete layout robots
---
---
title: "Using Layouts in MS Excel"
description: "The layouts defined in a Layout Robot in Lucanet Disclosure Management can be applied in an MS Excel table. The applied layouts will be adopted automatically when the table is inserted in a MS Word document."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/assign-layout-toexcel
language: en
last_updated: 2026-05-01
---
# Using Layouts in MS Excel
## Overview
The layouts defined in a [Layout Robot](https://support.lucanet.com/en/documentation/glossary.md#layout-robot) can be applied in an Excel table. The applied layouts will be adopted automatically when the table is inserted in a Word document.
## Applying a Layout
### Office for the Web and Office Native
In **Office for the Web** and **Office Native**, you apply layouts using the **Add Area Highlights** task pane. Proceed as follows:
1. Select the table cells for which you want to apply a layout.
2. In the Excel ribbon, click **Add Area Highlights**.
The **Add Area Highlights** task pane opens on the right and the **Insert** tab is displayed. The selected cell range is shown in the **Selection** area.
3. On the **Insert** tab, select the desired layout from the **Columns** or **Rows** sections.
'Insert' tab in the 'Add Area Highlights' task pane
4. If necessary, repeat the process for other cells in the table.
5. Click **Check In** in the Excel ribbon.
> **Note:** The **List** tab lists the area highlights that have already been applied. Using **Move to selection** next to an entry, you can move the layout to the cell range currently selected in the Excel worksheet.
>
> the 'list' tab in 'add area highlights' task pane with applied area highlights. icon
> 'List' tab with applied area highlights
### Office for Desktop
To apply a layout defined in a Layout Robot to an Excel table:
1. Select the table cells for which you want to apply a layout.
2. Click **Add Layout Range** in the Excel ribbon. The menu containing the layouts available in the selected **Layout Robot** will be displayed:
'Add Layout Range' button in the Excel ribbon
3. Select the desired layout from the menu.
4. If necessary, repeat the process for other cells in the table.
5. Click **Check In** in the Excel ribbon.
> **Warning:** - If the outarea defined in the Excel file has already been applied in a Word document, the layout changes will only become visible when the Excel file is checked in.
> - If you checked out both documents at the same time, you can make the changed layout visible by clicking the **Update** button in the [Word Ribbon](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
> **Note:** A separate layout robot can be stored for each document in Lucanet Disclosure Management.
>
> To assign a layout robot to a document, you must open the Configure document workspace and add a layout robot in the Layout Robot settings area (see also [Configuring a Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md)).
>
> This is also where you can use the icon to save an already assigned layout robot locally, e.g. to use it in another document.
>
> the shows 'configure document' workspace. 'layout robot settings' area is displayed. options for layout robot are outlined in red. icon
> Assign, save, or delete layout robots
---
---
title: "Using Text Values in MS Word"
description: "Lucanet Disclosure Management allows you to insert individual report values from the MS Excel files of the currently open document into the body text of MS Word files. So-called text values are inserted into the MS Word document."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word-use-variables
language: en
last_updated: 2026-05-01
---
# Using Text Values in MS Word
## Overview
**Disclosure Management** allows you to insert individual report values from the MS Excel files of the currently open document into the body text of MS Word files. So-called **text values** are inserted into the Word document.
Text values are references to the actual report values. If values in the Excel documents are changed, e.g. by manual rounding or by importing data, the corresponding text values are updated automatically. It is not necessary to check or adjust the text values manually.
## Inserting Text Values
How you insert a text value depends on the selected MS Office variant. The subsequent configuration of the text values is identical in all variants (see section [Configuring Text Values](#configuring-text-values)).
### Office for the Web and Office Native
To insert a text value in **Office for the Web** and **Office Native**:
1. Open the desired Word file from the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md).
2. Place the cursor at the position in the Word document where the text value is to be inserted.
3. On the **DM-Content** tab of the Word ribbon, click **Insert text values**.
The **Insert text values** task pane is displayed on the right:
'Insert text values' task pane in Office for the Web and Office Native
4. Configure the text values to be inserted as required (see section [Configuring Text Values](#configuring-text-values)) and then click **Insert**.
### Office for Desktop
To insert a text value in **Office for Desktop**:
1. Click the three-dot icon in the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md) and select **Edit Word file** from the context menu or click the desired Word file in the **MS Word** column.
Opening a Word file
2. The selected Word file is opened.
3. Place the cursor at the position in the Word document where the text value is to be inserted.
4. Click **Insert text values** in the Word ribbon.
Inserting a text value using the Word ribbon
The **Insert text values** window is displayed:
'Insert text values' dialog
5. Configure the text values to be inserted as required (see section [Configuring Text Values](#configuring-text-values)) and then click **Insert**.
## Configuring Text Values
The following configuration options apply to all MS Office variants – **Office for the Web**, **Office Native**, and **Office for Desktop**. The example screenshots in this section are taken from **Office for Desktop**.
> **Note:** In **Office for the Web** and **Office Native**, some labels differ from the Office for Desktop screenshots shown below, even though the functionality is identical:
>
> - The **Source** section is called **Value Source** there.
> - The **Insert** section is called **Settings** there.
You have the following options for configuring text values:
### Source
'Insert text values' area in the 'Insert text values' dialog
The source of the text value is set in the upper part of the **Insert text values** dialog. The following options are available:
| Option | Description |
|---|---|
| Document | When the wizard is opened, the Excel file of the corresponding chapter is automatically preset. If no Excel file with a value column is stored for the corresponding chapter, Disclosure Management searches for the closest Excel document in the structure and enters it. |
| Chapter | Chapter in which the desired text value is defined |
| Column | Value column in which the desired text value is defined |
| Period | Period in which the desired text value is defined |
| Found Values | The available values with their designation and the current value. The designation is derived from the corresponding [name column](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md) of the Excel document. |
In the **Office for the Web** and **Office Native** task pane, **Found Values** is a separate, collapsible section with a count indicator (e.g. "Found Values (12)"), not just a row within **Source**.
### Insert
Area for inserting values and deviations in the 'Insert text values' dialog
You have the following options for formatting values:
| Option | Description |
|---|---|
| Unit | Unit of the text value. In addition to the scaling units (1 / 1,000 / 1,000,000 / 1,000,000,000), **%** is available: the stored raw value is multiplied by 100, so for example 0.42 displays as 42 %.
**Note:** The scaling units offered in the **Unit** drop-down list depend on the table inserted in the Word document. It is not possible to insert the text values in a lower scaling unit than the one stored in the table. |
| Value | Inserts the selected text value at the selected position. |
| Percentage variation | Percentage change in the value compared to the previous period. Inserts the deviation value with a percentage sign. |
| Absolute variation | Absolute change in the value compared to the previous period. Inserts the deviation value with the currently set unit. |
| Number formatting string | Display of the text value, such as separators or the number of decimal places. In addition to formats with a regular hyphen, formats are available that display negative values with a long minus (en dash) – optionally with or without a thin space between the minus and the number. The preview in the drop-down list depends on the document culture (for an English document, for example, 1,234.56 | –1,234.56). **Use absolute value**: Specifies that the report value is used regardless of the sign. **Use exact imported value**: Specifies that the exact value of the report value is used for the calculation, even if a rounded number is displayed in the text value. **Note:** The two options **Percentage variation** and **Absolute variation** are only displayed if a previous period exists for the selected period. |
| Insert | Inserts the text value at the current position. Under **Value preview**, the text value is displayed as it will be inserted with the current settings. |
### Condition
The 'Prefix’ and ‘Postfix’ areas in the 'Insert text values' dialog
### Description
Text values can be provided with **prefixes** and **postfixes (suffixes)** and thus dynamically stored, for example **loss** or **profit** or a currency unit such as **EUR**. The following options are available for prefixes and postfixes (suffixes):
| Option | Description |
|---|---|
| Condition | Choose the desired condition from the drop-down list. The defined conditions are checked from top to bottom. The configuration for prefixes and postfixes whose condition is fulfilled first is then executed. |
| Prefix | Text that is written before a text value when it is inserted. **Overwrite prefix**: Enables the input field below to enter a prefix that overwrites the existing one. **Insert whitespace after prefix**: Inserts a protected space after the text entered in the **Prefix** input field. |
| Postfix (suffix) | Text that is written after a text value when it is inserted. **Overwrite Postfix**: Enables the input field below to enter a postfix that overwrites the existing one. **Insert whitespace before postfix**: Inserts a protected space before the text entered in the **Postfix (suffix)** input field. |
| Other setting | **Do not show value**: The value is not displayed in the **prefix** and/or **postfix (suffix)** input fields as soon as the condition is met. **Switch displayed Sign (+/-)**: Changes the sign of the value of the inserted text value. |
**Further options in the 'Conditions' area**
- Click the plus sign **(+**) to create another restriction.
- The buttons in the menu bar of a condition can be used to change the order or delete the condition.
Menu bar of a condition
- Click the collapse icon to expand or collapse the configuration of a restriction. When collapsed, restrictions are displayed as follows:
Folded conditions
## Highlighting Text Values
The Word ribbon can be used to highlight inserted document variables and text values in the Word document using the **Highlight text values** button.
Highlight text values with the Word ribbon
Inserted variables and references to report values are provided with a comment in the Word document and highlighted in color. The comment contains a description of the type of report value and its source.
> **Note:** In **Office for the Web** and **Office Native**, this function has a different name: on the **DM-Content** tab, click the **Set** button and select the **Text Values** entry. Use the **Remove** button and the **Text Values** entry to remove the highlight again.
---
---
title: "Using the Area and Column Assistant"
description: "The Area and column assistant uses AI to automatically detect outareas and their name, value, and programming columns in MS Excel files, as an alternative to configuring them manually."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/area-column-assistant
language: en
last_updated: 2026-08-11
---
# Using the Area and Column Assistant
## Overview
The **Area and column assistant** uses AI to automatically detect outareas in MS Excel files, as well as their name, value, and programming columns, as an alternative to configuring them manually via the [Mark Area](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/setup-excel-file.md#office-for-the-web-and-office-native) task pane.
The Area and column assistant is available in **Office for the Web** and **Office Native**.
> **Warning:** To use the Area and column assistant, you need at least the **Advanced** license.
Use the **Area and column assistant** button on the Excel ribbon to open the **Area and column assistant** task pane with the **Outarea** and **Values** tabs:
- On the **Outarea** tab, the assistant detects table areas in the Excel spreadsheet.
- On the **Values** tab, the assistant detects name, value, and programming columns within a selected outarea.
## Starting the Area and Column Assistant
You start the Area and column assistant directly from the Excel ribbon:
'Area and column assistant' button on the Excel ribbon
## Detecting Outareas
On the **Outarea** tab, you can have outareas in the active worksheet detected automatically.
1. Click **Area and column assistant** on the Excel ribbon.
The **Area and column assistant** task pane is displayed with the **Outarea** tab open.
'Outarea' tab in the 'Area and column assistant' task pane
2. Optionally, in the **Padding** section, define a margin for detection (**Top**, **Left**, **Right**, **Bottom** fields; default value 0 for each).
3. Click **Detect outareas**.
The detected outareas are displayed in the **Adjust outareas** section.
4. Activate the checkboxes of the outareas that you want to keep. If necessary, adjust the cell range of a detected outarea (see **Adjusting Detected Outareas**).
5. Save the assignment.
### Adjusting Detected Outareas
The following buttons are available for each detected outarea in the **Adjust outareas** section:
| Button | Description |
|---|---|
| Edit outarea | Opens a dialog for renaming the outarea (prefix, name, language code). Saving also sets the outarea to the cell range currently selected in the worksheet. |
| Highlight the area in the worksheet | Highlights the outarea's cell range in the Excel worksheet without changing it. |
| Move to selection | After a confirmation prompt, moves the outarea to the cell range currently selected in the worksheet. |
## Detecting Columns
On the **Values** tab, you can have the name, value, and programming columns for an outarea detected automatically.
1. In the **Area and column assistant** task pane, switch to the **Values** tab.
2. In the **Outarea** drop-down list, select the desired outarea.
3. Optionally, select the **current period** and the **previous period**.
4. Select the desired AI engine and start column detection.
The detected columns are displayed in the results list.
5. Save the assignment.
> **Note:** Saving is only possible once the results list contains at least one name, one value, and one programming column. If one of the three column types is missing, the assignment is not saved.
For more information on the column types, see [Creating and Editing Columns](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md) and [Defining Outareas](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-outareas.md).
---
---
title: "Using the Data View"
description: "In Lucanet Disclosure Management, the data view is used to review report values (including details like history, comments, and validation) that have been imported from a source system and to update and/or modify them when necessary."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/data-view
language: en
last_updated: 2026-05-01
---
# Using the Data View
## Overview
In Lucanet Disclosure Management, the **data view** is used to review report values (including details like **history**, **comments**, and **validation**) that have been imported from a source system and adjust them when necessary.
Discrepancies can occur when report values are imported in **cents** and results are displayed in **thousands**, for example. In such cases, cent values (which are rounded to the nearest thousand) differ from the original values. The **data view** makes it possible to correct these deviations manually.
> **Note:** The **Data view** function is only available for [programmed Excel files](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt.md).
>
> - An MS Excel file is classed as **programmed** if it has a Name column, at least one Values column, and at least one Programming column, and at least one cell is programmed into the Programming column.
> - If the Programming column is empty, the MS Excel file is not classed as programmed.
## Video: Using the Data View
In the following video, you can see how to use the data view and adjust values:
Video: https://player.vimeo.com/video/1020582227?muted=true&autoplay=false&loop=false&playsinline=true&controls=true&portrait=false&byline=false&title=false
> **Note:** The video also offers **Spanish and German subtitles**. To enable subtitles, click the **CC** button in the bottom-right corner, then use the **gear icon (Settings)** to select **Español** or **Deutsch**.
## Opening the Data View
To open the **data view**, proceed as follows:
1. In the [Dashboard](https://support.lucanet.com/en/documentation/disclosure-management/dashboard-disclmgmt.md), click the document that you wish to check.
Opening a document from the Dashboard
2. To open the **data view** for a chapter, select one of the following options:
- Click the **three dots icon** the three dot icon of a chapter with a programmed MS Excel file and choose **Data view**:
Opening the data view from the cockpit
- Click the info icon to open the [detail view for a chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md) and then click **data view**.
3. The **data view** will display all the cells with report values from the MS Excel file associated with the chapter. The **data view** will be displayed as follows (for example):
Data view in Disclosure Management
> **Note:** - The data view always displays all the rows programmed in the programming column of the MS Excel file in question.
> - To display a value column in the data view with its column name from MS Excel, the cell that contains the **column name** must be configured accordingly (see [Creating a Value Column](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt/define-columns.md#columnname)).
## Colors and Symbols in the Data View
The cell colors and icons used in the **data view** indicate the type of values in a given report. The basic value types are:
- **Automatic values**: values imported from the source system
- **Manually entered values**: values entered manually by the user
Explanations of the colors and icons used can be opened by clicking the **Legend** button:
Data view legend
---
---
title: "Using the XBRL Tagger"
description: "Thanks to the integrated XBRL Tagger, you can easily create XBRL-based, electronic company reports using Lucanet Disclosure Management by assigning the report data to an XBRL taxonomy (XBRL tagging/XBRL mapping). A range of XBRL taxonomies are available for this purpose."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/xbrl-window
language: en
last_updated: 2026-05-01
---
# Using the XBRL Tagger
## Overview
The **XBRL standard** is an internationally recognized standard for creating and transmitting electronic financial data to authorities, investors, and other recipients. For example, financial reports have to be created in XBRL format by law in many countries.
XBRL stands for **eXtensible Business Reporting Language** and is an XML-based language for creating electronic documents as part of financial reporting.
The structure of electronic company data is usually based on a specific accounting standard and is referred to as an **XBRL taxonomy**. Examples of this include the HGB, IFRS, and US-GAAP taxonomies.
Thanks to the integrated XBRL Tagger, you can easily create XBRL-based, electronic company reports using Lucanet Disclosure Management by assigning the report data to an XBRL taxonomy (XBRL tagging/XBRL mapping). A range of XBRL taxonomies are available for this purpose.
## Opening the XBRL Tagger
To open the **XBRL Tagger**:
1. In the **Overview** of a document, click **XBRL** to open the workspace.
2. Click the **Open XBRL window** button. The XBRL Tagger will open in a separate window:
Window of the XBRL Tagger
## Using the XBRL Tagger
Separate documentation provided by the Lucanet company AMANA explains how to use the XBRL Tagger.
The XBRL Tagger documentation can be accessed via the following link: [XBRL Tagger Documentation from AMANA (a Lucanet Company)](https://amana.atlassian.net/wiki/spaces/SND/pages/6235756/CloudSN-ESEF+Module)
> **Warning:** Because the XBRL Tagger has been optimized for use in the Lucanet Disclosure Management solution, there are a few slight differences not described in the external documentation for the XBRL Tagger:
>
> - Different design
> - The procedure for storing an XBRL taxonomy differs. In Disclosure Management on the Lucanet CFO Solution Platform, you store the desired taxonomy in the [Configure Document](https://support.lucanet.com/en/documentation/disclosure-management/configure-document-disclmgmt.md) workspace.
> - In Disclosure Management on the Lucanet CFO Solution Platform, the following is also possible in MS Word:
> - Text block tagging with placeholders; in other words, placeholders can be set in MS Word and then tagged in the assignment window of the XBRL Tagger.
> - Tagging of XBRL footnotes
>
> Further information on these two functions can be found in [Inserting XBRL Tags in Word Documents](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags.md).
---
---
title: "Versioning and Recovery of MS Office Files"
description: "In the Lucanet Disclosure Management, MS Excel and MS Word files are saved using the 'Check In' function. When a file is checked in, a new version of the file is created automatically. All versions of a file can be recovered at any time."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/file-versioning-restore
language: en
last_updated: 2026-05-01
---
# Versioning and Recovery of Files
## Overview
In Disclosure Management, Excel and Word files are saved using the **Check In** function. When a file is checked in, a new version of the file is created automatically. All versions of a file can be recovered at any time.
## Office for the Web and Office Native
In **Office for the Web** and **Office Native**, checking in and updating work in a similar way to **Office for Desktop**. The two relevant buttons are located in the Word ribbon on the **DM-Content** tab:
Buttons for checking in and updating in the Word ribbon ('DM-Content' tab)
### Checking In a File
To check in a file:
1. In the Word ribbon, on the **DM-Content** tab, click **Check In**.
The **Check-In** task pane opens on the right.
'Check-In' task pane
2. Enter a comment in the **Check-in message** field.
3. Click **Check in**.
Disclosure Management creates a new version of the file. When you check in a Word chapter, an entry is created in the document **History**, from which the version can be recovered.
### Recovering a Version
When you check in a Word chapter, an entry is created in the document **History**, from which you can recover a previous version. To open the history of a document:
1. Click the info icon to open the [Detail View of a Chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md).
2. In the detail view, open the document **History** and recover the desired version (see [Detail View of a Chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md)).
## Office for Desktop
### Checking In a File
To check in a file:
1. Click **Check In** in the Word or Excel ribbon:
'Check In' button in the Word ribbon
2. The **Check In** dialog will be displayed:
Dialog for checking in an Office file
3. You have the following options for entering a comment:
- Enter a comment in the input field.
- If helpful, click **Recent Comments** to reuse one of the 20 most recently used comments.
4. By default, an Excel or Word file that contains errors cannot be checked in. If you want to check in a defective file despite this, activate the **Force Check In** check box.
5. Click **Check In**.
Disclosure Management will then create a new version of the file. In the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md), the time of the change will be displayed in the **Word** column.
### Recovering a Version
You can open a previous version of the current file at any time.
To recover a version:
1. Click **Recover Version** in the ribbon.
'Recover Version' button in the Word ribbon
2. The **Version History** window will be displayed:
'Version History' Word window
3. Select the desired version in the drop-down list.
4. If necessary, click **Compare** to compare the selected version of the document with the current version.
5. Click **Open**.
6. **Check in** the file **again** to update the values changed since saving the restored version (for example by re-importing the data) if necessary.
> **Note:** Versions can also be opened from the **History** in the [Detail View of a Chapter](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt/chapter-detail-view.md).
---
---
title: "Working with MS Office Files"
description: "In Lucanet Disclosure Management, Word and Excel files play a key role, firstly for importing data and secondly for creating a business report."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice
language: en
last_updated: 2026-05-01
---
# Working with MS Office Files
## Overview
In Disclosure Management, Word and Excel files play a key role, firstly for importing data and secondly for creating a business report:
- **Excel files** form the main basis for using report data from the source system. For report generation purposes, data from the Excel files can be embedded in Word files in such a way that the values in the report are updated automatically if the Excel data are updated, e.g. as a result of an additional data import.\
\
More information on this can be found in [Creating and Editing Excel Files](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/excel-files-disclmgmt.md).
- **Word files** play a key role in Disclosure Management when it comes to creating a business report. The final result document is built using them. In Word documents, the Excel tables maintained in Disclosure Management are published with their report values. Word documents are also used to make the corporate design and texts available for the desired result document.\
\
More information on this can be found in [Creating and Editing Word Files](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file.md).
In the [Cockpit](https://support.lucanet.com/en/documentation/disclosure-management/cockpit-disclmgmt.md), an Excel file and/or Word file can be assigned to each chapter of a Disclosure Management document. In addition to standalone Word files, content can be reused across reports via Word references.
When working with MS Office documents, you can use functions in specific **ribbons** for MS Excel and MS Word. The functions provided in the ribbons are perfectly adapted for use in conjunction with Lucanet Disclosure Management. More information on this can be found in [Ribbons for Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/ribbons-disclosure-mgmt.md).
---
---
title: "Working with Word References"
description: "With Word references in Disclosure Management, you can reuse the content of a chapter from one report in a chapter of another report."
source_url: https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/use-word-references
language: en
last_updated: 2026-05-01
---
# Working with Word References
## Overview
With **Word references** in **Disclosure Management**, you can reuse the content of a chapter from one report in a chapter of another report.
## Creating Word references
You can create a Word reference in the Cockpit via the **three-dot icon** of an empty chapter.
To create a Word reference for a chapter:
1. Open the target document.
2. In the **Cockpit**, at the end of the row of an empty chapter, click the **three-dot icon**.
Creating Word references in the Cockpit
3. In the menu, choose **MS Word | Add Word reference**. The following dialog is displayed:
'Add Word reference' dialog
> **Note:** The **Add Word reference** command is not available in the following cases:
>
> - You do not have editor permission for the chapter.
> - There are no referenceable documents available.
> - The chapter already contains a reference.
> - The chapter already contains a chapter.
4. Configure the Word reference. The following information must be specified:
| Option | Description |
|---------|---------|
| Source report | Report that contains the chapter you want to reference |
| Chapter | Chapter you want to reference |
| Language | Drop-down list with all available languages |
5. Click **Apply and open**.
6. The following actions are performed:
- MS Word opens automatically with the source content in the selected language.
- After opening, a check-in is automatically performed in the background.
- The reference is created in the target chapter, and the source content is inserted as a chapter at the selected position.
- In the **Cockpit**, an additional icon for a reference is displayed in the MS Word column:
Display of a reference in the Cockpit
> **Note:** Changes you make in the Word reference are not transferred to the original chapter.
## Updating a Word Reference in 'Track Changes' Mode
When the source chapter of a Word reference is updated, the **Cockpit** highlights the reference icon in the MS Word column. In addition, a tooltip on Status displays the **Update available** note:
Display of an update of the source chapter
To check and apply updates of a Word reference:
1. Click the icon of the Word reference. The Word editor opens with **Track Changes** mode enabled. Changes from the source chapter are highlighted in the Word document.
2. Use the native Track Changes functions in MS Word to review the differences:
- Accept changes you want to apply.
- Reject changes you do not want to apply.
3. Click **Check in** to save the result. The following actions are then performed:
- The highlighting of the reference icon in the Cockpit is removed.
- The reference metadata is updated with the new check-in timestamp of the source chapter.
- A new entry is created in the chapter's history.
## Ignoring an Update of a Word Reference
When the source chapter of a Word reference is updated, the **Cockpit** highlights the reference icon and shows the **Update available** note. If you do not want to review the update, you can dismiss it directly from the three-dot menu instead of opening **Track Changes** mode.
To ignore an update of a Word reference:
1. In the **Cockpit**, at the end of the row of the reference chapter, click the **three-dot icon**.
Three-dot menu of a Word reference with the 'Ignore update' command
2. Under the menu item **MS Word**, choose the command **Ignore update**.
> **Note:** The **Ignore update** command is only available while an update is shown for the reference icon. References without an available update do not show this command.
3. The update is dismissed immediately, without a confirmation dialog. The following actions are performed:
- The update highlighting is removed from the reference icon in the Cockpit.
- A new entry is added to the chapter's history that records the ignored update, including the source document, the chapter, the timestamp, and the author. The reference icon is shown next to the entry.
- The reference's status and check-in timestamp remain unchanged.
> **Note:** Ignoring an update applies only to the current version of the source chapter. The reference continues to track the source: if the source chapter is updated again, the reference icon is highlighted again so that you can review or ignore the new update.
## Discarding Manual Changes
You can discard changes you have made in a Word reference at any time.
Proceed as follows:
1. In the **Cockpit**, at the end of the row of an empty chapter, click the **three-dot icon**.
Discarding manual changes
2. Under the menu item **MS Word**, choose the command **Discard manual changes**.
3. The document matches the state of the original chapter again.
## Unlinking a Reference
You can unlink a Word reference from the original chapter at any time. Proceed as follows:
1. In the **Cockpit**, at the end of the row of an empty chapter, click the **three-dot icon**.
Unlink reference
2. Under the menu item **MS Word**, choose the command **Unlink reference**.
3. The link to the original chapter is removed, and the current state of the Word reference is added as a chapter to the current document. The icon indicating a reference is removed.
## Re-Pointing Word References with Lucanet Lume to a New Source Document
When you roll forward a document that contains Word references, the references in the new, rolled-forward document initially still point to the old source document. Rolling forward a document does not automatically adjust existing Word references to a new referenced source document.
With Lucanet Lume, you can re-point all affected Word references of a document to a new source document in one step, instead of removing and re-creating each reference individually.
### Prerequisites
- Both the document containing the Word references and the referenced source document have already been rolled forward or copied individually (see [Rolling Forward or Copying a Document](https://support.lucanet.com/en/documentation/disclosure-management/perpetuate-copy-doc-disclmgmt.md)).
- The source and target documents must match structurally, because Lucanet Lume matches Word references based on their structure, not their content. This is therefore only possible between a document and a 1:1 copy or roll-forward of that document, not between documents with different content.
- The feature is currently available for Word references only.
### Instructions
To re-point Word references with Lucanet Lume to a new source document:
1. Roll forward or copy both the document that contains the Word references and the referenced source document individually ([Rolling Forward or Copying a Document](https://support.lucanet.com/en/documentation/disclosure-management/perpetuate-copy-doc-disclmgmt.md)). This creates two new documents for the new period. The old documents remain unchanged.
2. Open Lucanet Lume and describe, in natural language, which references should be re-pointed, for example:
"In the report [name of the target document], all Word references currently pointing to [name of the old source document] should point to [name of the new source document]."
Re-pointing Word references with Lucanet Lume
3. Lucanet Lume then guides you step by step through the process and asks for the required information, including:
- The exact name of the target document (as stored in the Dashboard)
- The exact name of the old source document
- The exact name of the new source document
4. Confirm the action when Lucanet Lume shows the planned change and asks whether it should be carried out.
5. After confirmation, Lucanet Lume re-points all matching Word references in the target document to the new source document in one step. References for which no matching counterpart is found in the new source document remain unchanged, pointing to the old document.
> **Note:** Lucanet Lume does not check the textual content of the referenced chapters; it matches references based on their structure. Therefore, check in the Cockpit whether all the desired references were re-pointed correctly.
### Behavior When No Counterpart Is Found
If Lucanet Lume cannot find a chapter with the same structure or ID in the new source document as in the old source document, the affected Word reference cannot be re-pointed. Lucanet Lume reports this case as a missing counterpart (**NO_COUNTERPART**) and leaves the reference unchanged, pointing to the old source document.
Message from Lucanet Lume when no counterpart is found
In this case, Lucanet Lume offers two options:
- You can ask Lume for the affected target chapter and further details about the missing counterpart.
- You can adjust the chapter structure in the new source document so that a matching chapter exists, and then trigger the re-pointing of the reference again.
---
## XBRL Tagger
You can use the Lucanet XBRL Tagger to immediately tag your business report without an implementation project or any IT knowledge and convert it into iXBRL. The time required to create the report is reduced considerably by processing all taxonomies and creating them correctly according to the latest standard.
---
title: "Adding KVK Filing Information"
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/kvk-filing-information
language: en
last_updated: 2026-06-12
---
# Adding KVK Filing Information
The **KVK Filing Information** panel in the **XBRL Tagger** lets you review and complete the mandatory filing information required for a KVK (Kamer van Koophandel) submission to the **Dutch authorities**. The panel displays all mandatory fields defined in RTS Annex II, point 3, and shows how many of them are complete.
The panel is only visible when a document using a **KVK taxonomy** is open.
## Opening the KVK Filing Information Panel
To open the **KVK Filing Information** panel, open a document using the KVK taxonomy and click the **KVK Filing Information** button in the toolbar on the right.
KVK Filing Information panel in the XBRL Tagger
## KVK Mandatory Fields
The **KVK Mandatory Fields** section displays all 11 required fields from RTS Annex II, point 3. A progress bar at the top shows how many fields are complete (for example, **11 / 11**).
Use the tabs above the fields to filter by status:
- **All** — all 11 fields
- **Missing** — fields that have not yet been filled in
- **Auto** — fields automatically extracted from tagged values in the document
- **Manual** — fields entered manually
The following fields are available:
| Field | Description |
|---|---|
| **Chamber of Commerce Registration Number** | Registration number of the legal entity. Automatically extracted from the `bw2-titel9:ChamberOfCommerceRegistrationNumber` tag.
**Note:** The number must consist of 8 consecutive digits, and the first two digits must not be **00**. If the format is invalid, the message "The registration number must have a valid format (8 consecutive digits, of which the first two digits must not be 00)." is displayed directly in the field.
|
| **Legal Entity Name** | Legal name of the entity. Automatically extracted from the `bw2-titel9:LegalEntityName` tag. |
| **Legal Entity Legal Form** | Legal form of the entity (for example, *Besloten vennootschap*). Automatically extracted from the `bw2-titel9:LegalEntityLegalForm` tag. |
| **Registered Office** | Registered office of the entity. Automatically extracted from the `bw2-titel9:LegalEntityRegisteredOffice` tag. |
| **Legal Entity Size** | Size classification of the entity. Select one of the following: **Micro legal entity**, **Small legal entity**, **Medium-sized legal entity**, or **Large legal entity**. Maps to the `kvk:LegalEntitySize` tag. |
| **Financial Reporting Period End Date** | End date of the financial reporting period. Automatically extracted from the `bw2-titel9:FinancialReportingPeriodEndDate` tag. |
| **Financial Reporting Period** | Reporting year. Automatically extracted from the `bw2-titel9:FinancialReportingPeriod` tag. |
| **Financial Statements Consolidated** | Indicates whether the financial statements are consolidated. Automatically extracted from the `rj:FinancialStatementsConsolidated` tag. |
| **Auditor's Report Present** | Indicates whether an auditor's report on the financial statements is present. Automatically extracted from the `kvk:AuditorsReportFinancialStatementsPresent` tag. |
| **Document Adoption Status** | Indicates whether the annual financial statements have been formally adopted. Automatically extracted from the `bw2-titel9:DocumentAdoptionStatus` tag. |
| **Document Adoption Date** | Date on which the financial statements were adopted. Only displayed when **Document Adoption Status** is true. Automatically extracted from the `bw2-titel9:DocumentAdoptionDate` tag. |
## Exemption Flags
The **Exemption Flags** section lists three conditional legal exemptions. Select the checkbox next to each exemption that applies to the filing entity.
| Flag | XBRL Tag |
|---|---|
| **Article 2:396 BW (small company)** | `kvk:Article396ExemptionApplied` |
| **Article 2:403 BW (group exemption)** | `kvk:Article403ExemptionApplied` |
| **Audit exemption (2:396 para. 7)** | `kvk:AuditExemptionApplied` |
## Field Status
Each field in the panel shows one of the following status indicators:
| Status | Description |
|---|---|
| **Auto** | The value was automatically extracted from a tagged element in the document. The field is read-only. |
| **Manual** | The value was entered manually and can be edited. |
| **Conditional** | The field is only displayed under specific conditions. |
## Actions in the Panel
| Action | Description |
|---|---|
| **Re-extract from tags** (refresh icon, bottom-right of the panel) | Re-reads the tagged values in the document and updates the automatically extracted fields. If an auto-extracted value differs from a previously entered manual value, a conflict notification is shown — click the update button in the notification to apply the extracted value. |
| **Export readiness** | The status line at the bottom of the panel shows **Ready for export** when all mandatory fields are complete. The XBRL package export is possible at any time, however the package is not valid without all mandatory fields being complete. |
> **Note:** Save the document before using the re-extract function. The extraction reads from the last saved version of the document.
---
---
title: "All Steps at a Glance"
description: "In this chapter, you can find the individual steps required to tag a document with the Lucanet XBRL Tagger. The presented sequence of steps is our recommendation for editing a document as effectively as possible."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/process-xbrl-tagger
language: en
last_updated: 2026-05-01
---
# All Steps at a Glance – XBRL Tagger
## Overview
In this chapter, you can find the individual steps required to tag a document with the **Lucanet XBRL Tagger.**
The presented sequence of steps is our recommendation for a procedure that is as effective as possible. You do not have to follow the recommended sequence in detail. If necessary, individual steps can also be carried out at a different time. For greater clarity, we have focused on the main steps and have not described optional detailed steps.
### Step 1: Preparing a Word Document
To tag a Word document correctly, certain prerequisites must be fulfilled.
Check your document for all items in the list at [Preparing a Word File](https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/prepare-word-file.md).
### Step 2: Adding a Word Document
Editing a document is always started by loading the document into the XBRL Tagger.
Add the document to the list of documents in the [document overview](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md).
### Step 3: Opening a Word Document
Open the desired document from the [document overview](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md). The open document is displayed in the **XBRL document** workspace.
### Step 4: Configuring the Document Settings
In the XBRL Tagger settings, various specifications can be made for the document currently open, for example for the taxonomy, tagging, and the result document.
Configure the default settings for the document in the [Settings](https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/configure-xbrltagger.md) workspace.
### Step 5: Tagging the Document
Documents are tagged in the **XBRL document** workspace.
Switch to the **XBRL document** workspace and [tag](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md) the document.
### Step 6: Generating an XBRL Report
When creating the finished iXBRL document, a report package is generated that contains the result document and various reports.
[Create](https://support.lucanet.com/en/documentation/xbrl-tagger/generate-ixbrl.md) the report.
### Step 7: Checking the XBRL Document
Before downloading the report package, you can subject the tagged document to a final check.
- Open the document to be checked from the [Result documents](https://support.lucanet.com/en/documentation/xbrl-tagger/ergebnisdokumente.md) workspace.
- The document is displayed in the [iXBRL-Viewer](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-viewer.md) workspace, where it can be checked.
---
---
title: "Analyzing XBRL Data with Lucanet XBRL Vision"
description: "Lucanet XBRL Vision is a free, web-based tool for professional analysis of XBRL data that enables instant validation and visualization without uploading data or installing software. It is designed for finance professionals, auditors, and regulators, and ensures full data privacy by processing directly in the browser."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-daten-analysieren
language: en
last_updated: 2026-05-01
---
# Analyzing XBRL Data with Lucanet XBRL Vision
## Overview
**Lucanet XBRL Vision** is a free, web-based tool for professional analysis of XBRL data that enables instant validation and visualization without uploading data or installing software. It is designed for finance professionals, auditors, and regulators, and ensures full data privacy by processing directly in the browser. The main features of Lucanet XBRL Vision are:
- **Data privacy**: The tool requires no registration or installation and processes all data locally in the browser, fully protecting users’ privacy.
- **Ease of use:** Navigate your inline XBRL reports with an intuitive, professional user interface. Tagged elements, their relationships, and hierarchies are clearly visualized.
- **Extensive analysis functions**: Lucanet XBRL Vision provides interactive visualization of inline XBRL reports, technical and business validation according to XBRL 2.1, and supports standards such as ESEF and ESRS.
- **AI-friendly data preparation**: The tool converts XBRL data into structured JSON formats optimized for large language models and modern data pipelines, enabling advanced analysis and integration.
## Opening Lucanet XBRL Vision
Do one of the following to open Lucanet XBRL Vision:
- Click the following URL to open Lucanet XBRL Vision:\
\
[https://vision.platform.lucanet.cloud/vision](https://play.goconsensus.com/b83e6cb3b)
- Copy the URL to the clipboard and paste it into your web browser’s address bar.
The start page of Lucanet XBRL Vision is displayed as follows:
Start page of Lucanet XBRL Vision
## Analyzing XBRL Data
To analyze XBRL data:
1. Use drag and drop or click **Browse** to have a ZIP or XBRL file validated.
2. The document is validated automatically after being added.
3. Do one of the following:
- **View iXBRL report**: For visualization and manual review of inline XBRL content and information, the document is displayed in the iXBRL **Inline Viewer**. The stored XBRL information can be displayed and highlighted.
- **Download validation report**: Creates an Excel file with any validation errors and their severity and downloads the file.
- **Convert inline XBRL reports to XBRL-JSON**: Creates an XBRL‑JSON file and saves it to the local computer.
---
---
title: "Basic Configuration"
description: "To begin tagging a document, you must configure the document settings and the Word document."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger
language: en
last_updated: 2026-05-01
---
# Basic Configuration for the XBRL Tagger
## Overview
To begin tagging a document, you must carry out the following steps:
- **Configuring the document settings**: You can configure report-specific settings for the XBRL Tagger for each document in the **Settings** workspace. You can find the respective details in the chapter [Configuring Document Settings](https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/configure-xbrltagger.md).
- **Configuring the Word document**: MS Word documents must meet specific requirements to be tagged correctly. You can find the respective details in the chapter [Preparing a Word File](https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/prepare-word-file.md).
---
---
title: "Calculation View"
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/calculation-view
language: en
last_updated: 2026-05-01
---
# Using the Calculation View
## Overview
XBRL calculation linkbases define mathematical relationships between financial statement elements (e.g. total assets = current assets + non-current assets). These relationships must be correct for the report to pass regulatory validation (e.g. ESEF).
XBRL Tagger provides a dedicated side panel, the **calculation view**, to:
- Display and edit calculations
- Display details
- Add and remove summands
- Identify summands that are also used in other tables and navigate directly to them
## Opening the Calculation View
Open the calculation view by clicking the calculator icon in the sidebar:
Opening the calculation view
The calculation view is displayed as follows:
Calculation view in XBRL Tagger
> **Warning:** The **calculation view** only contains values after you have selected a cell with a calculated value in a table in the current document.
>
> If the calculation view does not display any values, select a calculated value first.
## Editing Calculations
To edit calculations:
1. Activate the **Edit enabled** option.
Calculation view in edit mode
2. If necessary, use the drop-down list under **Calculated value** to change the sign (e.g. whether a summand is added to or subtracted from the total). The following options are available in the drop-down list:
| Option | Description |
|---------|---------|
| None | Value has no sign |
| As Reported | Sign remains as reported |
| Reverse | Value has the opposite sign |
| Always positive | Value always has a positive sign |
| Always negative | Value always has a negative sign |
3. If necessary, change the **Weight** option. **Weight** can be set to **1** or **-1** and is an additional option to change the sign.
'Weight' in the calculation view
> **Tip:** The **Weight** option is only available when either the element or the total element has the balance type **Unknown**.
>
> For debit values, Weight is always **-1**; for credit values it is **1**. Because **Unknown** can be either, you can set the balance type yourself.
## Displaying Details
In the calculation view, you can activate **Full details** to display additional technical information for each summand.
Full details help you check that values were parsed correctly and the correct taxonomy elements were applied, for example when taxonomy labels are ambiguous. The following additional information is displayed:
- The parsed value read from the source document, without applying **weight** or **sign logic**.
- The technical name (the XBRL taxonomy element identifier).
Calculation view with details
## Cross-Table Tag Navigation in the Calculation View
In the **Calculation** linkbase, XBRL Tagger shows which summands are used in other tables of the same report: summands that are used in more than one table are highlighted with a **light red background** and a red **information icon**.
Display of a summand that is used in several tables
Click the information icon to navigate directly to the corresponding table and cell. This lets you check cross-table tag relationships at a glance and spot tagging inconsistencies quickly.
## Adding Values to a Calculation
You can add more values from tables to a calculation. Proceed as follows:
1. Select the value or values in the table that the calculation belongs to.
2. In the calculation view, click **Add selection**.
Adding a selection
3. The values selected in the table are added to the calculation.
## Deleting a Calculation or Value
You can remove individual values from a calculation or delete the entire calculation. To do this, click the calculation view delete icon.
---
---
title: "Configuring Document Settings"
description: "Individual specifications can be configured for each document in the 'Settings' workspace"
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/configure-xbrltagger
language: en
last_updated: 2026-05-01
---
# Configuring Document Settings
## Overview
Individual specifications can be configured for each document in the **Settings** workspace, such as:
- The taxonomy to be used
- Settings for using specific Word elements, e. g. footnotes and tables
- Settings for the report to be created, such as the language and currency
- Settings for the report package
- Settings for tagging a document
## Opening the Workspace
To open the **Settings** workspace:
1. Make sure you have opened the desired document.
2. Click the settings icon in the function bar to open the workspace.
3. Configure the settings (see [Configuring Settings](#config_set))
4. Save the settings.
Open the 'Settings' workspace
## Configuring Settings
You can configure the following options in the **Document settings**. You can find an explanation of the options directly at the respective setting on the user interface.
> **Note:** To restore the **default settings**, scroll to the end of the settings and click **Reset to default**.
#### Taxonomy
Selection of the taxonomy to be used:
> **Note:** The primary taxonomy is automatically determined according to the selected **reporting requirements** and cannot be changed.
Selection of the taxonomy
#### MS Word
Settings for elements in Word documents:
Default settings for Word elements
#### Report
Settings for the report to be created:
Default settings for the report to be created
> **Note:** Opening the settings automatically derives **Extension prefix** and **Target namespace** from the **Company name** field, as long as these fields are still empty — existing values are never overwritten, and the settings are not considered changed by this. If you edit **Company name** afterwards, Extension prefix and Target namespace are automatically recalculated and overwritten. If no company name is set, both fields stay empty and must be filled in manually.
#### Package settings
Settings for the report package to be created:
#### Tagging
Tagging settings:
Default settings for tagging a document
---
---
title: "Creating a Taxonomy Extension"
description: "Companyspecific disclosures not available in the standard taxonomy must be reported as 'taxonomy extensions'. Furthermore, what are referred to as 'anchors' must be used to specify the present taxonomy items to which the extension is semantically connected."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrltagger-extend-taxonomy
language: en
last_updated: 2026-05-01
---
# Creating a Taxonomy Extension
## Overview
Companyspecific disclosures not available in the standard taxonomy must be reported as **taxonomy extensions** (extension elements). Furthermore, what are referred to as **anchors** must be used to specify the present taxonomy items to which the extension is semantically connected.
> **Warning:** A taxonomy extension is permitted only if the taxonomy does not contain a suitable element and the core element of the taxonomy would result in misrepresentation.
## Creating an Extension
To create an extension:
1. Select the cells that belong to the extension.
2. Click **Add Extension** in the header of the document:
'Add Extension' button
3. Edit the properties of the extension in the **Fact Properties** area:
Properties of an extension
4. Create and configure an anchor (see [Adding and Configuring an Anchor](#anchoring)).
> **Warning:** The created extension must be linked to the core taxonomy. What are referred to as **anchors** are created for this purpose. There are two different types of anchors:
>
> - **Narrow anchor**: element of the core taxonomy with a narrower accounting meaning than the extension element. Any number of narrow anchors may exist.
> - **Wide anchor**: element of the core taxonomy with a broader accounting meaning than the extension element. Only one wide anchor may exist at a time.
## Adding and Configuring an Anchor
To perform the anchoring, the respective tags must be inserted and configured under **Properties**. To anchor an extension:
1. Select the extension you want to anchor.
2. Scroll to the very bottom of the **Properties** area.
3. Drag the respective tag from the taxonomy and drop it onto the **Drop anchor element here** field.
Field used to set an 'anchor'
4. Configure the anchor by defining whether it is a **narrow** or **wide** anchor. Bring the respective slider into the corresponding position for this purpose.
Wide and narrow anchor
> **Note:** An extension may always only have **one wide**, but **several narrow** anchors.
---
---
title: "Custom Hierarchies"
description: "In the XBRL Tagger, the Custom hierarchies dialog allows you to adjust the order and structure of dimension elements and abstract elements. This way, you can reflect your internal report structure and meet your auditors' requirements without editing taxonomy files manually."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/userdefined-hierarchies
language: en
last_updated: 2026-07-28
---
# Custom Hierarchies
## Overview
In the **XBRL Tagger**, the **Custom hierarchies** dialog allows you to adjust the order and structure of **dimension elements** and **abstract elements**. This way, you can reflect your internal report structure and meet your auditors' requirements without editing taxonomy files manually.
By default, the XBRL Tagger derives the hierarchies for abstracts and dimensions automatically from the selected taxonomy. You only need to adjust hierarchies manually if the default structure does not reflect your reporting requirements – typically at an auditor's request or to align with internal reporting logic.
The XBRL Tagger includes a saved hierarchy in the generated extension taxonomy files and in the iXBRL report. A **saved dimension hierarchy** affects both the **Presentation Linkbase** and the **Definition Linkbase**. A **saved abstract hierarchy** affects the **Presentation Linkbase**.
## Opening the 'Custom Hierarchies' Dialog
To open the **Custom hierarchies** dialog, click **Custom hierarchies** in the function bar of a document:
Opening the 'Custom hierarchies' Dialog
> **Note:** **PDF documents**: For PDF documents, open the dialog instead via the **Custom hierarchies** button in the **Table actions** toolbar of the respective table (see [Detecting Tables Manually (PDF Documents)](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md#detecting-tables-manually-pdf-documents)). The dialog then opens directly for that table.
The **Custom hierarchies** dialog is displayed, for example, as follows:
'Custom hierarchies' dialog
The **Custom hierarchies** dialog contains two tabs with different purposes:
- **Dimensional hierarchy**: Shows the hierarchy of the dimension elements of a table and the axes they belong to. You can rearrange dimension members by drag-and-drop, change superordinate elements, or add more dimension elements from the taxonomy view.
The **Dimensional hierarchy** tab is only available if the reporting requirement allows taxonomy extensions.
- **Abstract hierarchy**: Groups tagged elements of a role and thereby structures the Presentation Linkbase. Abstract elements are used only for grouping – they cannot be used to tag actual values.
The **Abstract hierarchy** tab is only available if the reporting requirement allows taxonomy extensions.
## Prerequisites
The two tabs have different prerequisites:
- **Dimensional hierarchy**: At least one table and its table cells must be tagged in the document. Otherwise, the tab shows the message **No tagged tables available**.
- **Abstract hierarchy**: The **Allow taxonomy extension** setting must be activated for the document. Otherwise, the tab shows the message **Abstract Hierarchy Not Available**.
To check whether taxonomy extensions are allowed for your selected reporting requirement:
1. On the XBRL Tagger **dashboard**, open the information window of the desired document. Either click the document's row, or use the **Show document information and result set** command in the context menu of the three-dot icon.
Context menu command ‘Show document information and result set’
2. Switch to the **Information** tab.
3. Check whether the **Allow taxonomy extension** option is activated.
## Displaying the Dimensional Hierarchy
On the **Dimensional hierarchy** tab, you can adjust dimension elements and their axes for each table.
To display a dimension hierarchy:
1. Open the **Table** drop-down list and select a table.
2. Open the **Taxonomy role** drop-down list and select the desired taxonomy role.
> **Note:** **PDF documents**: If you opened the dialog via the **Table actions** toolbar of a PDF table, the first step does not apply: the **Dimensional hierarchy** tab already shows the hierarchy of that table directly, without having to additionally select it from the **Table** drop-down list.
## Displaying the Abstract Hierarchy
On the **Abstract hierarchy** tab, you can group tagged elements of a role and thereby structure the Presentation Linkbase. Abstract elements cannot themselves be used to tag actual values in the report – they only serve as parent grouping elements.
To display an abstract hierarchy:
1. Open the **Role** drop-down list and select a role.
2. Open the **Taxonomy role** drop-down list and select the desired taxonomy role.
> **Warning:** If you have made unsaved changes and select a different role, the XBRL Tagger displays the **Overwrite hierarchy** confirmation dialog with the question **Overwrite existing hierarchy?** Click **Overwrite** to switch roles and discard your changes, or click **Cancel** to stay in the current role.
#### Adjusting Hierarchies
In both tabs, you can rearrange elements at all levels of the hierarchy by drag-and-drop. The following actions are possible:
- Move an element **before** or **after** another element on the same level.
- Move an element so that it becomes a **subordinated element** of another element.
- Move an element to a higher or lower level of the hierarchy tree.
To rearrange an element:
1. Click the desired element in the hierarchy tree and hold down the mouse button.
2. Drag the element to the desired position.
3. Release the mouse button.
## Adding an Element
You can add elements to the hierarchy that are not yet used in any tag.
To add an element:
1. Find the desired element in the **Taxonomy** area.
2. Drag and drop the element to the desired position in the hierarchy tree.
## Deleting an Element
You can only delete an element if no facts are tagged with it, directly or indirectly. If deletion is allowed, a **trash bin icon** is displayed next to the element.
To delete an element:
1. Hover over the desired element in the hierarchy tree.
2. Click the trash bin icon.
3. The element is removed from the hierarchy. The XBRL Tagger automatically reassigns subordinate elements to the superordinate element of the deleted element, so no orphaned elements remain.
> **Note:** If an element cannot be deleted, no trash bin icon is displayed. In this case, first remove the tags from the affected facts.
## Saving or Resetting Changes
Changes to the hierarchies are not applied automatically. The buttons at the bottom of the dialog control whether your changes take effect or not.
The following options are available:
- Click **Save changes**: The XBRL Tagger applies the custom hierarchy for the selected table or role. After saving, a success message confirms that the hierarchy has been updated (e.g., **Dimension Hierarchy Updated** or **Abstract Hierarchy Updated**).
- Click **Reset to default**: The XBRL Tagger restores the default hierarchy of the base taxonomy. On the **Dimensional hierarchy** tab, the reset is performed immediately.\
\
On the **Abstract hierarchy** tab, the XBRL Tagger displays the **Overwrite hierarchy** confirmation dialog if there are unsaved changes. Click **Overwrite** to discard your changes, or click **Cancel**.
- Click **Cancel**: The changes are not applied.
## Effects on the iXBRL Export
A saved custom hierarchy affects the following areas:
- The generated **extension taxonomy files** reflect the adjusted structure.
- The **iXBRL report** is generated with the adjusted hierarchy.
- A saved **dimension hierarchy** is translated into the corresponding tree in both the **Presentation Linkbase** and the **Definition Linkbase** when the report is generated.
- A saved **abstract hierarchy** is translated into a representation for the **Presentation Linkbase**.
- The hierarchy is saved per table (on the **Dimensional hierarchy** tab) or per role (on the **Abstract hierarchy** tab). Other tables or roles are not affected.
---
---
title: "Dashboard"
description: "The document overview is the starting point in the Lucanet XBRL Tagger. All documents to be tagged are loaded into the document overview."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger
language: en
last_updated: 2026-09-04
---
# Dashboard
## Overview
The **Dashboard** is the starting point in the **XBRL Tagger**. All documents to be tagged are loaded into the Dashboard. The XBRL Tagger supports both Word documents (DOCX) and PDF files (PDF).
## Opening the Dashboard
When you open the XBRL Tagger, the **Dashboard** is always displayed. If you want to navigate to the **Dashboard** from another workspace, click Dashboard in the upper left corner of the **breadcrumb navigation**.
The Dashboard is displayed as follows, for example:
Dashboard in the XBRL Tagger
## Adding a Document
To add a document:
1. Click **Create new tagging file** and do one of the following:
- From Lucanet Disclosure Management
- From your computer
2. Either the **Create tagging file from Disclosure Management** or **Add New Document** dialog is opened, depending on your choice (see **Options When Adding Documents**).
## Options When Adding Documents
### Creating Tagging File from Disclosure Management
As soon as you choose the **From Lucanet Disclosure Management** command, the following dialog is displayed:
Add document from Lucanet Disclosure Management
### Description
The following options are available in the dialog:
**Report name**
Files created in Lucanet Disclosure Management. Select the desired file.
**Create**
Creates the chosen file in the XBRL Tagger.
### Adding New Document
As soon as you choose the **From your computer** command, the following dialog is displayed:
'Add a new document' dialog
### Description
The following options are available in the dialog:
| Option | Description |
|---------|---------|
| **Upload document** | Click the download icon to choose a document or drag and drop the desired file into the dialog. Both Word documents (DOCX) and PDF files (PDF) are supported. |
| **Optional mapping file** | When uploading a PDF, you can optionally upload a PDF mapping file (PDF.MAPPING) together with the document to apply pre-defined XBRL mappings. **Note**: The mapping file must have the same base name as the PDF. |
| **Tagging file name** | Optional document name. If you do not specify any name, the name of the chosen document will be used. |
| **Reporting requirement** | Automatically determined specifications defined by regulatory authorities are activated for the document by choosing the reporting requirement. The system automatically searches for the matching reporting requirement. If the automatically selected entry does not fit, you can adjust it manually. |
| **Create** | The document is created. |
## Displaying Document Information
As soon as you click on a row in the dashboard, a window appears on the right-hand side. The **Information** tab displays the settings that were automatically created when the document was created. The configuration depends on the selected **report request** (see [Adding a document](#adddocument)).
Alternatively, you can use the **Show document information and result set** command in the context menu of the three-dot icon to open the information window:
Open the window with document information and the result set
You can change the reporting requirement for a document by choosing the desired **reporting requirement** from the drop-down list and then clicking **Save**.
Display information about a document
## View sets of results documents
After generating an iXBRL document, the results of the generation are displayed to the right of the table on the **Result documents sets** tab. On this tab, you can download the result documents or the results report, among other things. For more information, see the section [View Result Documents](https://support.lucanet.com/en/documentation/xbrl-tagger/ergebnisdokumente.md).
Alternatively, you can use the **Show document information and result set** command in the context menu of the three-dot icon to open the information window:
Open the window with document information and the result set
## Other Options in the Dashboard
The following options are available in the Dashboard:
| Option | Description |
|---------|---------|
| **Search** | Searches the list of documents for the entered search term — not only in the tagging file name and the originally imported file's name, but also in the name of the assigned **Reporting Requirement**, in the short name of its taxonomy (e.g. "ESEF", "KVK"), and in that taxonomy's technical entry point address — this is also where terms like "IFRS" or "EFRAG" find matches, since those terms are part of that address. If a Reporting Requirement bundles several taxonomies, the document is found via any of them, but appears only once in the results. You can additionally filter the search results by activating a filter from the drop-down list. |
| **Favorites** (the favourites xbrltag deactivated icon the favourites xbrltag activated icon) | Shows whether a document is marked as a favorite or not. A filled star indicates that the document is a favorite. All documents marked as favorites are displayed in the document overview on the Favorites tab. |
| **"(Pending review)" indicator** | Appears directly after a tagging file's name whenever the document has an outstanding review — whether triggered by importing a new file version or by AI tagging. The indicator disappears automatically once the review is completed or discarded, and updates live without needing to reload the dashboard. |
Search options in the dashboard
### Options in the three-dot menu
The following options are available in the three-dot menu of documents:
| Option | Description |
|---------|---------|
| **Open** | Opens the document in the **XBRL document** workspace, where it can be tagged. |
| **Rename** | Opens a dialog for renaming the document. |
| **Import new file version** | Imports a new version of the document. Existing text block tags from the previous version are automatically applied to the new version of the document. This option is available for both Word documents (DOCX) and PDF documents (PDF). The dialog only accepts the same file type as the original document; if the file extension does not match, the message **Invalid file extension** is displayed.
**Note:** If a [Tag Update Preview](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-update-preview.md) is already open for the document, an information window opens instead. You can use it to open the ongoing preview or cancel the import; a new import is only possible after the preview has been applied or discarded.
**Note (PDF documents only):** If not a single tag could be carried over during the roll-forward of a PDF document, no Tag Update Preview opens. Instead, the message "Document Not Rolled Forward – No tags could be carried forward onto the new PDF. The existing document is unchanged." appears, and the document remains unchanged in its previous version.
|
| **Continue review** | Reopens the [Tag Update Preview](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-update-preview.md) if an open preview still exists for the document.
**Note:** This option is only visible if a Tag Update Preview has already been opened for the document.
|
| **Delete pending review (change set)** | Discards the document's open Tag Update Preview without applying the changes it contains.
**Note:** This option is only visible if a Tag Update Preview has already been opened for the document.
|
| **Delete document** | Deletes the document from the list of documents. **Caution:** You can delete only documents you have loaded into the dashboard yourself. |
| **Duplicate document** | Creates a duplicate of the document. You can use duplicates, for example, for checking or testing purposes. |
| **Download document** | Downloads the document. |
| **Show document information and result set** | Opens a window displaying document information and the results of the generation process. |
| **Update Tagging document from Disclosure Document** | Updates the document from [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md). All tags from the current version of the document are transferred to the new version of the document. **Note:** The button is only available if the document has been imported from [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md) into the XBRL Tagger. |
## Status Display with Icons
The following icons appear when a document is locked:
| Option | Description |
|---------|---------|
| the locked icon | Shows that the document is being used by a user and is therefore locked and cannot be opened. |
| the status icon | You can unlock the document by clicking the icon. |
---
---
title: "Displaying and Editing Properties of Tags"
description: "The properties of an XBRL tag can be displayed and edited in the XBRL document workspace in Lucanet XBRL Tagger."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/edit-tag-properties
language: en
last_updated: 2026-05-01
---
# Displaying and Editing Properties of Tags
## Overview
The properties of an XBRL tag can be displayed and edited in the **XBRL document** workspace.
## Displaying Properties
The properties of a tag can be checked and edited if necessary by clicking on a tagged element in the **Fact Properties** area.
To change the properties of a tag:
1. Select a tagged element in the **Tagging** document.
2. If necessary, use the **sidebar** to open the **Taxonomy**.
3. Edit the desired setting under **Fact Properties**.
Display and edit properties of a tag
> **Warning:** As soon as you have chosen several values simultaneously in the **document**, some properties may show the entry **Several values are selected** in gray. This means the entry cannot be edited. Only the properties that are the same for all selected elements can be edited.
## Editing Properties
The properties of tags are divided into four areas ( **General**, **Monetary**, **Tags**, and **Extension**).
> **Note:** - The **Monetary** area is displayed only for values.
> - The **Extension** area is displayed only for extensions (see [Creating a Taxonomy Extension](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrltagger-extend-taxonomy.md)).
The following properties for tags can be displayed and, if necessary, edited:
### 'General' Area
| Property | Description |
|---------|---------|
| **Period type** | Default period for the selected value. - **Instant date**: determines the time, e. g. beginning or end of a period. - **Duration**: a period for which the value for the start to end date is specified. As soon as the chosen tag specifies **Duration**, a start and end date can be entered in the input fields then displayed under **Period**. **Note:** By default, an attempt is made to read out a date from the header of the table for the time or period. If, for example, 2021 is entered there, 31.12.2021 will be inserted as the instant date and 31.12.2020 to 31.12.2021 (i. e. for the entire year 2021) for the duration. If the header of the table does not contain the year, the current year will be used by default. |
| **Period** | Start and, if necessary, end date. A start and end date are displayed only for the **Duration** period type. |
| **Preferred Label Role** | Label used as preferred name. Preferred names are used for the precise specification of items. **Example:** Specification of a balance at the beginning and end of a period: The concept is assigned a **period start name** and **period end name** and marked as preferred name at the respective points in the **presentation tree**. The default name for the concept is **Property, plant, and equipment**. - Property, plant, and equipment at the beginning of the period (**period start label**) - Increase (decrease) of the property, plant, and equipment – Additions, property, plant, and equipment – Depreciations, property, plant, and equipment – Decrease, property, plant, and equipment - Property, plant, and equipment at the end of the period (**period end label**) |
| **Label** | The item name from the table row to which the tagged value belongs. The name is automatically transferred from the Word document into the properties. |
| **Status** | Status of the selected tags. |
| **Tagged by AI** | Indicates whether this tag was created using the AI tagging function. For more information, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md). |
| **Documentation** | Supplementary information on the tag can be entered here. |
### 'Monetary' Area
| Property | Description |
|---------|---------|
| **Report as nil** | Specifies what is to be interpreted as **value 0** (e. g. a line in a value cell). |
| **Decimals** | Number of decimal places for the accuracy of the reported number. For example, **-3** means accuracy in thousands, **2** means accuracy of two decimal places. |
| **Scale** | Defines the unit of the reported value. E. g.: - 6 for millions - 3 for thousands - -2 for percent **Example:** If values are entered in millions, with a scale of **6**, **450** would be displayed as **450 000 000**. |
| **Format** | Defines which character is to be interpreted as decimal separator. The other character is then interpreted as thousands separator. **Examples:** 1,000.0 and 1.000,0 |
| **Sign Logic** | Specifies the sign logic. In some cases, the sign logic used in the report will vary from the requirements of the regulatory authority. Like IFRS taxonomies, XBRL taxonomies require in general that certain items, such as **Cost of Sales** (**ifrs-full: Cost Of Sales**), are reported as positive numbers. If the item is disclosed as a negative number on the balance sheet, it may be necessary to reverse the value in the XBRL report, but still disclose it as "negative." In some accounting systems (like SAP) all credit notes in the report have a negative sign, whereas the regulatory authority expects these values to be reported with a positive sign. It is possible to change the sign logic for an individual cell. The following settings are available: - **None**: No specific sign logic is applied. - **As reported**: The value is added always with the same sign as in the report for the iXBRL document. - **Reverse**: The sign is reversed. Negative values are reported as positive values in the iXBRL document and reversed. - **Always positive**: The value is entered always with a positive sign. - **Always negative**: The value is entered always with a negative sign. |
| **Unit** | Specifies the currency of the selected values. |
| **Unit denominator** | Used to specify the unit of the denominator of a fraction. **Example:** euros/m². As soon as the **Unit denominator** check box is activated, the unit **m²** can be chosen from the displayed dropdown list. |
### 'Tags' Area
| Property | Description |
|---------|---------|
| **Line item** | Line items tags are the basic tags of the taxonomy. They are used to mark numeric accounting information and qualitative (non-numeric) specifications. Every tag always only has one **line item**. A tag can be deleted by deleting the line item. **Line items** can be extended by **dimensions** and **abstracts**. |
| **Dimension** | Displays the **dimensions** contained in the tag. With the [ESEF](https://support.lucanet.com/en/documentation/glossary.md#esef), there is usually no more than one dimension. However, with the [ESRS](https://support.lucanet.com/en/documentation/glossary.md#esrs), there is often more than one dimension. Dimensions are qualifying features required for the unambiguous identification of an issue. For example, a dimension could be used to specify that an issue applies to a specific geographic region. In the XBRL taxonomy, dimensions are provided as a pre-defined list of elements (also referred to as **dimension members**), such as **country**, **gender**, **type of greenhouse gas**. There are also dimensions that are specific to certain units and must be reported in this context, such as **geographic region**, **strategies**, **objectives**, **business segments**. |
| **Abstract** | If the tag is a table tag, an **abstract** is always displayed in the properties of the tag. **Example:** A table that displays a cash flow statement is tagged with the tag **ifrs-full:StatementofCashFlowsAbstract**. |
### 'Extension' Area
| Property | Description |
|---------|---------|
| **Balance type** | Specifies whether the values are **debit** or **credit** values. |
| **Name** | Technical name of the element. |
| **Item type** | Technical data type of the extension element. |
| **Anchors** | Extensions must be linked to the base taxonomy. What are referred to as **anchors** are created for this purpose (see [Creating a Taxonomy Extension](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrltagger-extend-taxonomy.md)). |
| **Label** | The item name from the table row to which the tagged value belongs. The name is automatically transferred from the Word document into the **properties** and can be changed user specifically. |
| **Reason for extension** | You can enter here optional reasons for why no standard taxonomy concept can be used. |
| **Period type** | Default period for the selected value. - **Instant date**: determines the time, e. g. beginning or end of a period - **Duration**: a period for which the value for the start to end date is specified. As soon as the chosen tag specifies **Duration,** a start and end date can be entered in the input fields then displayed under **Period**. **Note:** By default, an attempt is made to read out a date from the header of the table for the time or period. If, for example, 2021 is entered there, 31.12.2021 will be inserted as the exact time and 31.12.2020 to 31.12.2021 (i. e. for the entire year 2021) for the duration. If the header of the table does not contain the year, the current year will be used by default. |
> **Note:** **In-tool validations**: In addition to the properties of tags, the results of **in-tool validations**–validations performed while editing a document – are displayed in the **Properties** area. This feature allows you to respond and correct any tagging errors immediately.
>
> More information can be found under [Validations](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/validation_xbrltagger.md).
---
---
title: "Displaying and Editing the Status of Tags"
description: "To obtain a better overview of the tagging process, the status of tagged elements can be defined in Lucanet XBRL tagger."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-status
language: en
last_updated: 2026-05-01
---
# Displaying and Editing the Status of Tags
## Overview
The **status** of tagged elements can be defined to obtain a better overview of the tagging process.
## Available Statuses
The following statuses are available for tagged cells and text blocks:
| Color | Status |
|---------|---------|
| the tagstatus inprogress icon | **Tag in progress**: The tagging has not yet been completed. The properties of the tag may have to be re-edited, or a reviewer has reset the status because the tag is not correct or has not been configured correctly. |
| the tagstatus review icon | **Tag must be checked**: The tag must be checked. Areas, for example, that are tagged in the **Lucanet Disclosure Management** are displayed in yellow. |
| the tagstatus final icon | **Tag completed**: The tag has been checked and accepted. |
## Changing the Status of an Individual Tag
You can change the status of a tag at any time. Proceed as follows:
1. Right-click a tagged element and choose **Change status | Status** from the context menu.
'Set status' context menu
2. Choose the desired status.
## Changing the Status of Several Tags
You can change the status of several tagged cells or text blocks also simultaneously. Proceed as follows:
1. Choose the desired cells. Two options are available:
- Mark the desired cells while pressing the left mouse button.
- Use the arrow keys on your keyboard while holding down the **SHIFT** key to choose several cells.
- **Select non-adjacent cells**: Hold down the **CTRL** key and left click on each cell to be included in the selection.
- **Select adjacent cells**: Select the first cell to be included in the selection and then hold down the **SHIFT** key. While holding down the **SHIFT** key, click the last cell to be included in the selection.
2. Right-click the chosen cells and choose the **Change status** context menu command.
3. Choose the desired status.
**Note**: You can change the status of a tag also under **Properties** (see [Displaying and Editing Properties of Tags](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/edit-tag-properties.md)).
## Status Presettings
You can define the following presettings for the status of tags in the [Settings](https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/configure-xbrltagger.md) workspace:
- Which status is to be initially assigned to **newly created tags**.
- Which status is to be assigned to **extension tags**.
- Which status is to be assigned to tags **automatically added** to the document. Tags are automatically added, for example, if a Word document contains what are referred to as **content controls**, which may have been added to the Word document in the [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md).
Presettings for the status of tags
---
---
title: "Displaying Result Documents"
description: "After generating an iXBRL document, the results of the generation are displayed in the document overview in the right-hand panel on the 'Result document sets' tab."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/ergebnisdokumente
language: en
last_updated: 2026-05-01
---
# Displaying Result Documents
## Overview
After generating an XBRL report, the results of the generation are displayed in the **Dashboard** in the right-hand panel on the **Result document sets** tab.
## Displaying the ‘Result Document Sets’ Tab
For all documents for which a result document has already been generated at least once, information about the generation is displayed in the right-hand panel on the **Result document sets** tab. Additional functions are available on the tab (see [Functions for Result Documents](#funcs)).
To display the **Result document sets** tab, select in the document overview a document for which a report has already been generated. The **Result document sets** tab is displayed as follows, for example:
Result document sets
## Functions for Result Documents
The validation results and the generated files are displayed on the **Result document sets** tab. The following functions are available:
| Option | Description |
|---------|---------|
| the three dot menu icon | Opens a menu with the following menu commands: - Download result document set - Download result report - Rename this version - Delete |
| the download icon | Downloads the respective document, or the entire result document set (as a ZIP file). |
| **Open preview** | Opens the preview in the **iXBRL Viewer** workspace (see [iXBRL Viewer](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-viewer.md)). |
---
---
title: "Displaying the Preview"
description: "A preview can be displayed in the 'iXBRL Viewer' workspace to visualize and manually check the InlineXBRL content and information. The saved XBRL information can be displayed and highlighted in the iXBRL viewer."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-viewer
language: en
last_updated: 2026-05-01
---
# Displaying the Preview: iXBRL Viewer
## Overview
A preview can be displayed in **iXBRL Viewer** workspace to visualize and manually check the InlineXBRL content and information. The saved XBRL information can be displayed and highlighted in the iXBRL viewer.
## Opening the Preview
To create a preview:
1. Open the **Result documents** workspace.
2. Open the desired document by clicking **Open preview**.
3. The document is opened in the **iXBRL Viewer** workspace.
Tagged document in the iXBRL viewer
## Options in the iXBRL Viewer
The following options are available in the **iXBRL Viewer** workspace:
Source includes [iXBRL Viewer - XBRL - Confluence (atlassian.net)](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/1348859/iXBRL+Viewer)
| Option | Description |
|---------|---------|
| Highlight XBRL Elements | Select the tagged elements in the document, which are either tagged with a tag from the taxonomy or as an extension. As soon as the check box has been activated, tags from the taxonomy are displayed in **green** and extension tags in **violet**. |
| the ixbrlviewer configure icon | Changes the language of the user interface of the iXBRL Viewer. |
| the ixbrlviewer outline icon | Shows the table of contents for the document, if present. |
| the ixbrlviewer search icon | With the search, you can perform a full text search throughout the entire report. The search text must consist of at least three characters. As soon as you activate the button, the list of tags is displayed. You can display the details on each tag by clicking the respective button: the show tag details icon Show details of a tag |
| the ixbrlviewer stepper icon | Switches to the next or previous tag in the document. |
| the ixbrlviewer filter icon | Opens or closes the search filter options. |
---
---
title: "Generating an iXBRL Report"
description: "The iXBRL document, including all documents and folders prescribed by the regulatory authorities, can be generated in the 'XBRL document' workspace."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/generate-ixbrl
language: en
last_updated: 2026-05-01
---
# Generating an XBRL Report Package
## Overview
The iXBRL document, including all documents and folders prescribed by the regulatory authorities, can be generated in the **XBRL document** workspace.
In addition to the actual report, the XBRL Tagger creates Excel files that contain additional information on the document. Validations documented in an Excel file, for example, are performed during the generation process.
All results of the generation are displayed in the **Dashboard** and can be downloaded from there.
## Creating an iXBRL Document
To create a valid iXBRL document with all tagged data:
1. Go to the [XBRL document](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document.md) workspace.
2. Click **Generate XBRL Report** in the function bar.
Generating an iXBRL report package
3. The report is created together with four Excel files as a **set of result documents**.
4. Switch to the **[Dashboard](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md)** using the breadcrumb **navigation** at the top left to download the report package or the files you have created.
## Files in the Report Package
Even though the iXBRL file is an individual XHTML file, it is not enough to publish or submit only this file. A complete report package must be published instead.
The folder structure and the documents that must be published as an ESEF report package, with _Company_ used as placeholder for the short name of the reporting unit, are described in the following table in the figure.
#### _company.date.language.zip_
The generated ZIP file meets the requirements for the **report package specification** and contains the actual report and additional folders:
> **Warning:** The complete ZIP file must be submitted to the responsible authority! All other generated files are intended only for internal purposes.
> **Note:** The other files of the report package are described in the following section.
Contents of the generated ZIP file
## Additional Files
In addition to the actual report, the following Excel files are created, which contain additional information on the created iXBRL report:
#### Calculation report
The **calculation report** provides an overview of all calculations in the report and indicates whether they are valid or not. Invalid calculations may occur, for example, in the following cases:
- In the event of **rounding errors**. In this case, the values must be adjusted in the document.
- If the **incorrect sign** was used or configured. You can change the sign of a value in the **XBRL document** workspace in the properties of the assigned tag under **Format | Sign Logic**.
#### Mapping report
The **mapping report** contains a detailed overview of all tags or mappings and their properties that are applied to a document.
It may also contain all non-tagged cells with table mapping and their determined values.
#### Text block report
The **text block report** shows which text block tags exist in the report, their properties and, if necessary, which mandatory text block tags are still missing.
#### Validation report
The **validation report** contains, among other things, the following information:
- Overview of all information on the report
- Statistical information
- Results of the validations performed
- Any existing warnings
- Overview of all tables that have been tagged
- All linkbases created
---
---
title: "Introduction to iXBRL"
description: "The reports created by the Lucanet XBRL Tagger are based on the standard iXBRL. You can find the corresponding basic information in this chapter."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/ixbrl-introduction
language: en
last_updated: 2026-05-01
---
# Introduction to iXBRL and the XBRL Tagger
## Overview
The reports created by the **Lucanet XBRL Tagger** are based on the standard **iXBRL**. You can find the corresponding basic information in this chapter.
## Definition
> **Note:** **iXBRL (Inline eXtensible Business Reporting Language)** is a standard derived from the standard **XBRL**. XBRL allows financial data to be displayed in a format that can be read by human beings and machines. This dual function increases the transparency and user friendliness of financial reports and ensures that they are easy to access and analyze by a wide range of stakeholders, including supervisory authorities, investors, and analysts.
## Reports and Taxonomies
The **ESEF taxonomy** is based on the IFRS taxonomy. In the figure above, the XBRL report on the left side refers to the taxonomy items for every tagged number. As a result, additional information from the taxonomy is available for this concept, such as the **label** and the calculations to which this concept belongs.
A **taxonomy extension** must be created for company-specific items.
The format referred to as **inline XBRL (also iXBRL)** is XBRL embedded in HTML. The advantage of this format is that an iXBRL report can be opened in any web browser to be read by a human.
> **Tip:** Further information
>
> - You can find additional supplementary and detailed information on taxonomies and reports under [Further Guidance - XBRL](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/32215005/Further+Guidance) (English) and the underlying topics, including in:
>
> - [Packaging and Publishing of ESEF iXBRL Reports](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/32215022/Packaging+and+Publishing+of+ESEF+iXBRL+Reports)
> - [Presentation Linkbase, Preferred Labels and Periods](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/32215081/Presentation+Linkbase+Preferred+Labels+and+Periods)
> - [Understanding Taxonomies and Reports](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/32215123/Understanding+Taxonomies+and+Reports)
> - [ESEF Reporting Manual](https://amana.atlassian.net/wiki/spaces/XBRLD/pages/32215248/ESEF+Reporting+Manual)
> - You can find numerous definitions and explanations for concepts and terms concerning (i)XBRL in the (external) [XBRL Glossary](https://www.xbrl.org/guidance/xbrl-glossary).
## Properties of the XBRL Tagger
### Loading the XBRL Taxonomy
The XBRL Tagger makes the selection of taxonomies particularly easy, as these are already set up in pre-configured **Reporting requirements**. The taxonomies are typically represented using the **Presentation**, **Calculation** and **Definition Linkbase**. Translations of taxonomy elements in the form of labels are displayed in all languages that are supplied with the taxonomy.
### Tagging Word Files with XBRL Taxonomy Elements
Word documents can be opened, analyzed, and displayed in the XBRL Tagger. The tagging itself is performed by **drag & drop**. The XBRL Tagger supports the user with **consistency checks**. Tables with multiple columns can be assigned using dimension elements from the taxonomy. All metadata required, such as the reporting period and currency, are automatically identified if possible. A **status-based workflow** can be implemented by using different colors for the tagging elements. The mapping itself can be exported and imported – The XBRL Tagger restores the tags even if numbers and texts are changed.
### Taxonomy Extensions
The Tagger has a function for **taxonomy extensions**, which can be used to add elements that cannot be represented by the taxonomy. This function includes an **anchoring function** described by the [ESMA](https://www.esma.europa.eu/) **(European Securities and Market Authority)**.
### XHTML Converter and iXBRL Generation
The XBRL Tagger converts Word documents into valid **XHTML**, which is required for inline XBRL (**iXBRL**). The formatting and layout of the original documents are maintained as far as possible. An iXBRL report is saved after applying the XBRL tags according to the assignment.
### Validations
When creating an iXBRL report, a complete XBRL validation is conducted, covering the following specifications:
- XBRL Specification 2.1
- XBRL Dimensions 1.0
- XBRL Formula 1.0
- Table Linkbase 1.0
- Extensible Enumerations 1.0 and 2.0
- Inline XBRL 1.1 incl. XHTML and Transformation Registries 1-4
- Unit Registry
- Additionally, a so-called filing rule validation is performed. For example, an ESEF report is checked against the [ESEF Reporting Manual](https://www.esma.europa.eu/sites/default/files/library/esma32-60-254_esef_reporting_manual.pdf) and the rules it contains.
---
---
title: "Managing Continuation Chains"
description: "The Continuation administration allows you to view, reorder, and manage all continuation items belonging to a selected tag in one place."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/continuation-administration
language: en
last_updated: 2026-05-28
---
# Managing Continuation Chains
## Overview
A tagged text block in **Lucanet XBRL Tagger** can span multiple sections of a document.
When a single XBRL tag covers text that is distributed across different pages or chapters, the individual text sections are linked in a **continuation chain**. Each section in the chain is referred to as a **continuation item**.
The **Continuation administration** allows you to view, reorder, and manage all continuation items belonging to a selected tag in one place.
## Opening the 'Continuation Administration' Dialog
You have the following options for opening the **Continuation administration** dialog:
- Via the **context menu**: Right-click a tagged text block in the **Tagging** area and select **Continuation administration** from the context menu:
Opening Continuation administration from the document
> **Note:** The menu item is disabled (grayed out) if the selected tag has no continuation chain, i.e., if it is a stand-alone tag without continuations.
- Via the **command bar**: Click the search icon in the top bar of the **XBRL document** workspace or press **CTRL + SHIFT + P** to open the command bar. Search for **Continuation administration** and select the command.
- **Properties** area: When you select a tagged text block in the **Tagging** area that is part of a continuation chain, the **Continuation** section is displayed in the **Properties** area:
'Properties' area with continuation item
## Structure of the 'Continuation Administration' Dialog
The **Continuation administration** dialog is displayed, for example, as follows:
Dialog 'Continuation Administration'
The following information is displayed in the **Continuation administration** dialog:
- **Tag name**: The human-readable name of the XBRL tag the continuation chain belongs to. All items in the chain share the same tag name.
- **Tag technical name**: The technical XBRL identifier of the tag (for example, ifrs-full:DisclosureOfBorrowingsExplanatory).
The table lists all continuation items in the continuation chain. The following columns are displayed for each item:
| Column | Description |
|---------|---------|
| **Order #** | The current position of the item in the continuation chain. |
| **Content** | A short preview of the text content (up to 120 characters). Click the double arrow to display the full text. |
| **Chapter** | The chapter in the source document that contains the current continuation item. |
| **Doc. #** | The position of the item in the source document (document position). Use this column to compare the custom order with the original document structure. |
## Functions in the 'Continuation Administration' Dialog
The following functions are available in the **Continuation administration** dialog:
| Column | Description |
|---------|---------|
| the change order cont icon **Change order** | Move rows by drag-and-drop to change the order. |
| the showfullcontent cont icon **Show content** | Click the double arrow to display the full text. |
| ** the navigate to element cont icon ** **Navigate to item in document** | The document scrolls to the item and selects it in the **Tagging** area. |
| ** the delete cont icon ** **Delete item** | Removes the item from the continuation chain. **Note**: The **Delete** button is disabled when only one item remains in the chain. The last remaining item contains the primary XBRL tag and cannot be deleted. |
| **Reset to document position** | The position of the item in the source document (document position). Use this column to compare the custom order with the original document structure. |
| **Save changes** | Applies the changes. |
## 'Continuation' Area in the Properties
When you select a tagged text block in the **Tagging** area that is part of a continuation chain, the **Continuation** section is displayed in the **Properties** area. This section gives you a quick overview of the item's position in the chain, without having to open the full administration dialog.
Actions for a continuation item in the 'Properties' area
The following information is displayed for a continuation item in the **Properties** area:
| Property | Description |
|---------|---------|
| **Tag name** | The human-readable name of the XBRL tag. |
| **Tag technical name** | The technical XBRL identifier of the tag. |
| **Member** | The dimension member assigned to the item, if any. |
| **Position in chain** | The current position of the item within the continuation chain. |
| **Document position** | The position of the item in the source document. |
The following navigation and actions are also available in the **Properties** area:
- **Actions** menu:
- **Edit**: Opens the **Continuation administration** dialog for the entire chain.
- **Delete continuation chain**: Removes all continuation links in the chain after your confirm. Click **Yes, delete** to confirm the operation.
- **Next item / Previous item**: Navigates to the next or previous item of the chain in the document.
---
---
title: "Preparing a Word File"
description: "MS Word documents must meet specific requirements to allow then to be tagged correctly. In this chapter, you can find the most important requirements that Word documents must meet to be tagged."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/basic-configuration-xbrltagger/prepare-word-file
language: en
last_updated: 2026-05-01
---
# Preparing a Word File
## Overview
MS Word documents must meet specific **requirements** to allow them to be **tagged correctly**. In this chapter, you can find the most important requirements that Word documents must meet to be tagged.
## Requirements for Word Documents
To allow MS Word documents to be tagged correctly, the following prerequisites must be fulfilled:
- For MS Word documents, it is necessary to use styles ( **Heading 1**, **Heading 2** etc.) to structure the documents. To change the structure level of styles, right-click the paragraph and choose **Paragraph** and then **Outline Level**.
- All tables provided with tags must be normal Word tables (no embedded Excel tables etc.).
- It is not possible to tag values of a table included as an image in a document.
- Shapes and images anchored before or after a text are positioned at the anchor position. This can result in a different layout when converting to XHTML.
- Images and shapes inserted as embedded Office objects (e. g. diagrams from MS PowerPoint or MS Excel) cannot be converted into XHTML. Such images must be converted into images, e. g. by creating and inserting a screenshot.
- The conversion of two-column text layouts from MS Word into XHTML is not supported.
---
---
title: "Reviewing AI Tagging Suggestions"
description: "After an AI tagging run, you can apply the suggested tags directly or first approve or reject them individually in the review window."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging-review
language: en
last_updated: 2026-09-04
---
# Reviewing AI Tagging Suggestions
After AI tagging on a **Word document**, you decide how to proceed with the suggested tags: apply them directly right away, or first approve or reject them individually in the **review window** before they are applied to the document.
## Overview
Once AI tagging finishes — triggered via **Auto-tag page with AI** (text tagging) or **Auto-tag table with AI** (table tagging) — a dialog opens letting you choose between applying the proposals directly and reviewing them in the review window.
Dialog shown after AI tagging completes
> **Note:** The dialog appears identically for text tagging and table tagging. For more on AI-assisted tagging itself, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
> **Note:** This choice is only available for **Word documents**. For **PDF documents**, AI tagging suggestions continue to be applied directly; no dialog and no review window appear.
## Dialog After AI Tagging Completes
The **AI Tagging Complete** dialog shows the number of prepared tags and offers the following options:
| Element | Description |
|---|---|
| **Apply directly** | Applies all prepared tags to the document immediately — as before, without further review. |
| **Open review window** | Opens the review window, where you can approve or reject each suggested tag individually (see [Using the Review Window](#using-the-review-window) below). |
| **×** (close icon) | Closes the dialog without applying the tags or opening the review window. The prepared tags remain as a pending review. |
## Using the Review Window
The review window you reach via **Open review window** is the same screen shown after a roll-forward — documented in full under [Using the Tag Update Preview](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-update-preview.md). The core interaction (change list, document view, Fact Properties panel, legend) is identical; this section covers only the controls relevant to AI tagging suggestions.
> **Note:** Because the same review window is shared by roll-forward and AI tagging, some text still uses roll-forward-specific wording — for example, the header still reads **Tag update preview**, and the discard confirmation dialog refers to **roll-forward changes**, even when you opened the window from AI tagging. The workflow itself (approve, reject, apply, discard) works identically regardless of entry point.
### Overview Bar
The overview bar shows the number of tags by status — **pending**, **approved**, **removed** — along with the **review progress** as a percentage progress bar.
### Tag List
The tag list shows all tags suggested by AI tagging. Use the checkboxes to select one or more entries, or **Select all** to mark the entire list. The following actions are available for the selection:
| Action | Description |
|---|---|
| **Approve** | Sets the selected tags to **approved**. |
| **Reject** | Sets the selected tags to **removed**; they are not applied to the document. |
| **Pending** | Resets the selected tags back to **pending**. |
Use the **Search** field to find a tag by name or element ID.
### Fact Properties
When you select a tag in the list or in the document view, the **Fact Properties** panel shows its details, including the assigned element and the current review status.
## Applying or Discarding Changes
The following actions are available in the header of the review window:
- **Discard changes:** Discards all suggested tags from the run without applying them.
- **Close:** Leaves the review window without completing the review. Your decisions so far are kept, and you can continue the review later.
- **Apply to the document:** Applies all tags marked **approved** to the document. The button is disabled while any tags are still **pending**; a tooltip explains: "Review in progress. All suggestions must be approved or rejected."
> **Note:** Your decisions (approved, rejected, pending) are saved automatically as soon as you make them — no separate save step is needed, and no confirmation message appears. You can leave the review window at any time via **Close** and continue the review later without losing decisions you've already made. Tags are only applied to the document once you click **Apply to the document**. If saving a decision fails, the message "Failed to save the review decision. Please try again." appears, and the affected decision is reset to its previous status.
---
---
title: "Tagging a Document Manually"
description: "Lucanet's XBRL Tagger allows individual words or sentences, values, and entire chapters and tables of a document to be tagged."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document
language: en
last_updated: 2026-07-28
---
# Tagging a Document Manually
## Overview
**Lucanet's XBRL Tagger** allows individual words or sentences, values, and entire chapters and tables of a document to be tagged.
## Tagging a Document Manually
The XBRL Tagger allows the following elements of a document to be tagged:
- Texts
- Tables
- Values in tables
Elements can be tagged **manually** by drag and drop, or **with AI assistance** using the Tagger Agent. For more information on AI-assisted tagging, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
To tag elements manually:
1. Select the element you want to tag in the **Document** area.
2. Search for the desired tag in the **taxonomy**.
3. Drag and drop the tag onto the chosen element.
4. If necessary, edit the **properties** of the tag (see [Displaying and Editing Properties of a Tag](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/edit-tag-properties.md)).
Tagging a text block
> **Note:** **KVK taxonomy only:** Certain elements that come from an "-all" taxonomy (e.g. `kvk-all.xsd`) can't be tagged by drag-and-drop or double-click. These elements are shown dimmed in the taxonomy tree and in search results; a tooltip explains why, for example: *"kvk-i:Assets refers to an '-all' taxonomy. This element must not be used because it would include the complete taxonomy in the final report."*
After successfully tagging, the tagged element is highlighted in color (see [Status of Tags](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-status.md)).
> **Note:** **In-tool validations**: In addition to the properties of tags, the results of **in-tool validations**–validations performed while editing a document – are displayed in the **Properties** area. This feature allows you to respond and correct any tagging errors immediately.
>
> More information can be found under [Validations](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/validation_xbrltagger.md).
> **Note:** **Tags and placeholders for tags** that you have created in the [Lucanet Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md) solution are transferred to the XBRL Tagger and can be further edited there. You can find information on tagging Word documents in our Disclosure Management solution in [Using the XBRL Tagger](https://support.lucanet.com/en/documentation/disclosure-management/xbrl-window.md).
## Linkbases
The three tabs in the [Search options](#search) area contain what are referred to as **linkbases**. Linkbases contain all tags defined in the chosen taxonomy and show, in particular, the relationships between the tags.
Linkbases in the 'Taxonomy' area
Which linkbases are displayed depends on the chosen taxonomy. The following linkbases, for example, are displayed in the ESEF taxonomy:
- **Presentation**: contains the structure of the elements of the chosen taxonomy that you can use to tag the document currently loaded.
- **Calculation**: shows how the elements of the taxonomy are calculated. Summands used in other tables of the report are highlighted and can be opened directly (see the following section _Cross-Table Tag Navigation in the Calculation View_).
- **Definition**: contains the logical relationships between elements of the taxonomy.
## Cross-Table Tag Navigation in the Calculation View
When you open a calculation in the **Calculation** linkbase, the XBRL Tagger shows which summands are also used in other tables of the same report. This makes cross-table tag relationships visible at a glance and helps you spot potential tagging errors or inconsistencies quickly.
### Visual Highlighting
Summands that are used in another table of the report are highlighted with a light red background and a red info icon next to the label. Summands that are used only in the current table are not highlighted.
> **Note:** The highlighting applies **only to summands**. Superordinate calculation items and totals are not highlighted, even if they are used in other tables.
### Navigating to Another Table
Click the info icon or the highlighted summand label to navigate directly to the first other table where the same tag is used. The following steps are performed:
- The calculation view of the target table is opened.
- The corresponding cell is selected.
- If the **Properties** area is open, it shows the properties of the selected cell.
### Tagging Texts and Text Blocks
> **Note:** Tagging text and text blocks is done in the text content layer. Before tagging text and text blocks, switch to the **Text Tagging** tab at the top of the document area. For more information, see [Working with Layers](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md).
>
> the open text tagging layer icon
> Open the text tagging layer
**Taxonomies (e. g. IFRS, ESEF)** may require the marking of individual words or sentences (referred to as **text** in the following) (e. g. headquarters of the company = **DomicileOfEntity**) and the marking of text blocks (e. g. specification of liabilities \[text block\] = **DisclosureOfBorrowingsExplanatory**). The tags are of different types: **text** and **text block**. Whether words or sentences are tagged as text or text block is predefined by the taxonomy. These tags have different icons in the XBRL Tagger:
| Element | Description |
|---------|---------|
| Text | Text tags (strings) are used to tag **brief information**, for example something like **Country of Incorporation** or **Name of Reporting Entity**. |
| Text block | Text block tags are used to mark **large quantities of information**, such as notes and accounting guidelines including tables. Text blocks are intended for paragraphs or areas that cover several pages. |
> **Note:** - To tag texts or text blocks from [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md), they must be defined as so-called **content controls**. You can define content controls in MS Word on the **Developer tab**.
> - If the **Developer** tab is not displayed in MS Word, you need to activate the tab. In MS Word, select **File | Options | Customize Ribbon**, and activate the checkbox of the **Developer** tab under **Main Tabs**.
To tag text or text blocks, you have to mark the desired content control in the Word document and then drag the desired tag from the taxonomy and drop it onto the selected part.
In all other documents – including **PDF documents**, which cannot contain content controls in principle – select the desired text section directly in the document and then drag and drop the desired tag from the taxonomy onto the selected area.
> **Tip:** **AI alternative**: You can also tag individual text areas using the context menu — right-click a text area and select **Tag with AI** or **Suggest tags for selection**. To AI-tag all narratives on the current page at once, use the **Tag page with AI** button in the function bar. For more information, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
AI options in the context menu
### Continuation Chain
A text block tag can span several sections of a document. If the tagged text is distributed across different pages or chapters, the individual sections are linked in what is referred to as a **continuation chain**. Each section in the chain is a **continuation element**. Continuation elements are managed in a dedicated dialog (see [Managing Continuation Chains](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/continuation-administration.md)).
### Tagging All Text Content
You can tag all text content in the entire document in a single step, without having to select each text block individually.
To tag all text content in the document:
1. Open the document in the **XBRL Document** workspace and switch to the **Text tagging** tab.
2. Click **Tag all text content** in the function bar.
All text content in the document is tagged automatically.
### Tagging Tables
> **Note:** Tables are tagged at the table level. Before tagging tables, switch to the **Table Tagging** tab at the top of the document area. For more information, see [Working with Layers](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md).
>
> the open table tagging layer icon
> Open the table tagging layer
Tables are tagged by dragging the desired tag onto the placeholder for the table tag. In all tables, the placeholder can be found in the top, right corner and shows the entry **Drag and Drop here**:
Placeholder for the table tag
> **Note:** **PDF documents**: For PDF documents, a table must first be detected using **Auto select** before it can be tagged (see [Detecting Tables Manually (PDF Documents)](#detecting-tables-manually-pdf-documents) below). There, the placeholder for the table tag also shows the entry **No taxonomy element assigned** instead of **Drag and Drop here**.
Tables are tagged with what is referred to as an **abstract**.
> **Tip:** **AI alternative**: Numerical cells in a table can also be tagged with AI assistance. Select a cell in the table and click **Auto-tag table with AI** in the function bar. For more information, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
**Example**: A table that displays the cash flow statement is tagged with the tag **ifrs-full:StatementofCashFlowsAbstract**.
Table with the cash flow statement and the corresponding tag
**Changing the Row Order of a Table**
You can adjust the order of the table rows as follows:
1. Click the **Row Order** button above the document. The following dialog is displayed:
Dialog 'Table Row Order'
2. In the **Select Table** drop-down list, select the table in which you want to change the row order.
3. Change the row order in the **Table Row Order** dialog using drag and drop.
4. Click **Save**.
> **Note:** **PDF documents**: For PDF documents, open the dialog instead via the **Row order** button in the **Table actions** toolbar of the respective table (see [Detecting Tables Manually (PDF Documents)](#detecting-tables-manually-pdf-documents)). The dialog then opens directly for that table, without having to additionally select it from the **Select Table** drop-down list. The table must already contain at least one tagged cell — no row order is available for a table that has only been detected using **Auto select** but not yet tagged.
> **Tip:** You can also reset the row order to the base taxonomy by clicking the button **Use Row Order of the Base Taxonomy**.
> **Warning:** To apply the changes to the row order when generating a document, please make sure to save the document by clicking **Save document** before generating.
### Copying a Table with Tags to Another Layer
If you need an already tagged table with identical content on another layer — for example, to run additional calculations on the same cells — you can copy the table together with all its existing tags to another layer instead of tagging every cell manually again.
1. Right-click the table tag of the already tagged table.
> **Note:** This option is only available for already tagged tables and only for Word documents.
2. Select **Copy to layer** from the context menu.
A submenu shows the available target layers.
Context menu of a tagged table with the option 'Copy to layer'
3. Select the desired target layer.
The table structure and all existing tags are copied to the selected layer. The source layer remains unchanged.
> **Note:** Layers that already contain a tagged copy of this table are shown greyed out in the submenu and cannot be selected. Hovering over such a layer shows a tooltip indicating that it already contains a mapping for this table.
> **Tip:** If the target layer already contains an untagged copy of the table structure — for example, on the import layer right after the document was uploaded — that copy is populated with the source table's tags instead of creating another structure.
After copying, you receive a confirmation that all tags were copied to the target layer. If the operation fails, you are also notified.
### Detecting Tables Manually (PDF Documents)
Unlike Word documents, where the table structure comes directly from the document format, the XBRL Tagger does **not** detect tables in PDF documents automatically. A table must first be detected using the **Auto select** function before it can be tagged. Detection always applies only to the page currently displayed: once a page contains at least one detected table, **Auto select** is no longer available for that page, and the function must be run again on every further page that contains tables.
To detect and tag a table in a PDF document:
1. Open the PDF document in the **XBRL Document** workspace and switch to the **Table tagging** tab.
2. Navigate to the page containing the table to be detected.
3. Click the **Auto select** button at the top right of the function bar.
The Tagger Agent analyses the current page and detects the table areas it contains. Progress is shown in the **AI background tasks** panel under the **Detect tables** task.
The 'Auto select' button in the function bar
4. Once a table has been detected, the **Table actions** toolbar appears above it. The table itself still shows the placeholder **No taxonomy element assigned** until it has been tagged.
5. Tag the detected table in one of the following ways:
- Drag the desired tag from the taxonomy and drop it onto the **No taxonomy element assigned** placeholder in the **Table actions** toolbar, as described in [Tagging Tables](#tagging-tables), or
- Click **Tag table with AI** in the **Table actions** toolbar to have the table tagged with AI assistance (see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md)).
> **Note:** This function is only available for PDF documents. **Auto select** attempts to detect all table areas on the current page in a single pass. The **Auto select** button is always displayed in English, regardless of the selected language.
**Adjusting the Boundaries of a Table (PDF Documents)**
> **Note:** This function is only available for PDF documents.
After a table has been detected using **Auto select**, you can adjust its boundaries afterwards.
1. Select the table whose boundaries you want to adjust.
The floating table toolbar is displayed above the table.
2. Click **Edit** in the table toolbar.
The 'Edit' button in the floating table toolbar
Edit mode is activated: the table is displayed as a selection with drag handles at its boundaries, and an **Edit mode** notice is shown.
3. Drag the selection pins to adjust the boundaries of the table.
4. Click **Accept** to apply the change, or **Cancel** to discard it.
Alternatively, press Enter to accept or Escape to cancel.
> **Warning:** If the adjusted table overlaps another already tagged element, the change cannot be applied. Adjust the pins so the areas no longer overlap, or cancel the edit.
> **Note:** If existing cell tags cannot be fully transferred to the new table shape, you are asked whether the affected tags should be placed on the clipboard instead.
> **Tip:** An applied boundary change can be undone with Ctrl+Z. While edit mode is active, undo is not available.
### Tagging Values in Tables
A value or several values in a table can be tagged also simply by means of drag-and-drop. As soon as a tag from the XBRL taxonomy has been identified that is suitable for the table cell or table cells chosen in the document, the tag can be dragged from the **Taxonomy** area and dropped onto the value selected in the table.
Tagging a value
The cells are marked in green as soon as the tagging was successful.
The tagging details of values can be checked and/or changed by clicking a cell in the Properties area (see [Displaying and Editing Properties of Tags](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/edit-tag-properties.md)).
> **Tip:** **Tip**: In tables, you can define properties for all values at once by selecting the table completely and defining the desired configuration under **Properties**. The configuration of the properties will then apply to all values of the table.
### Member Tagging
Tables for which the items are broken down into columns and rows require both **line item tags** to tag the row and **tags for columns** (= member tags). Member tags are displayed in the ESEF taxonomy by a special icon and contain the label in the suffix **\[Member\]**.
Proceed as follows:
1. **Specifying a line-item element**: First select the **rows**, choose the desired element from the XBRL taxonomy, and drag it into the selected column.
2. **Specifying member elements**: Then select the **column** to be tagged, choose the desired element from the XBRL taxonomy and drag it into the selected column.
> **Note:** You can tag a single cell in a table or several cells at the same time. The following options are available for tagging several cells in a document at the same time:
>
> - Select the desired cells while **holding down the left mouse button**.
> - Use the arrow keys on your keyboard while holding down the **SHIFT** key to choose several cells.
> - **Select non-adjacent cells**: Hold down the **CTRL** key and left click on each cell to be included in the selection.
> - **Select adjacent cells**: Select the first cell to be included in the selection and then hold down the **SHIFT** key. While holding down the **SHIFT** key, click the last cell to be included in the selection.
With the [ESEF](https://support.lucanet.com/en/documentation/glossary.md#esef), the only use case for member tagging is the tagging of the table **Statement of changes in equity**. After successfully tagging, the element receives two tags (one **line item tag** and one **dimension tag**).
Line item tag and dimension tag for a value in the statement of changes in equity
In contrast, tables in which the column headers contain a period (e. g. **2022** and **2024**) are each tagged with the same tag, which then varies only in terms of the period.
### Tagging as Addition in Parentheses
Facts that belong to a table, but are not physically part of it, (e. g. if a number that belongs to a table is used in continuous text) can be marked as what are referred to as **additions in parentheses**, i. e. as additional information appended to the table. This information must also be disclosed.
To tag an element (e. g. a value) as an addition in parentheses:
1. Select the desired value with a **content control element** when preparing the Word document before loading it to the XBRL Tagger.
2. Select the desired value in the document.
3. Tag the value by means of drag-and-drop with the desired tag.
4. The tagged element must then also be tagged to the table to which it belongs. To do so, tag the value with the table tag, i. e. with the **Abstract** tag of the table to which the value belongs.
> **Note:** **PDF documents**: Since PDF documents cannot contain content control elements, the first step does not apply to them. Select the desired value directly in the PDF document (step 2) and continue with tagging (steps 3–4).
> **Warning:** - You can insert content control elements either directly in MS Word or alternatively in the [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md) solution (see [Inserting XBRL Tags](https://support.lucanet.com/en/documentation/disclosure-management/work-with-msoffice/configure-word-file/word_add_xbrltags.md)).
> - You can find information on content control elements in MS Word also here: [About content controls - Microsoft Support](https://support.microsoft.com/en-us/office/about-content-controls-283b1e29-0b77-4781-b236-2d02c1cce1c2?ns=WINWORD&version=90)
## Copying and Pasting Tags
Tags can be copied in the document and inserted else where. Proceed as follows:
1. Select a tagged element in the document.
2. Open the context menu of the element and choose the **Copy** command.
Copying a tag
3. Select an element and choose **Insert** from the context menu. The tag is inserted together with all properties and the current status.
## Additional Functions
The following additional functions are available for the taxonomy and the elements it contains:
### Filtering the Taxonomy
To quickly find the suitable tag, the taxonomy can be filtered by certain criteria. Click the open search options icon, to open the search options:
Search options for taxonomy
The following filters are available:
- **Exact match**: filters tags that match the exact term entered under **Search** and contain only it, for example the search term **Assets** finds only **ifrs-full:assets**.
- **Abstracts only**: shows **abstracts** that contain the search term.
- **Item types**: filters the search results by the chosen **element types**. As soon as you activate the option, you can select the desired element types in the displayed list.
### Displaying References
As soon as you select an element in the taxonomy, the references of the selected tag are displayed in the **Properties** area:
Display references of a taxonomy element
### Displaying Tagged Items
To quickly find out if and where a tag has been used in the document, you can open the **Tagged items** drop-down list in the **Properties** area and identify the locations of the tag's usage in the document.
Display tagged items
---
---
title: "Tagging a Document with AI"
description: "The Tagger Agent uses AI to automate XBRL tagging of financial reports (Word and PDF): it proposes text blocks, tables, and calculation relationships for you to review and approve."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging
language: en
last_updated: 2026-09-04
---
# Tagging a Document with AI
The **Tagger Agent** is an AI-powered agent that automates IFRS taxonomy tagging of financial reports, reducing the process from days to hours. It identifies text blocks and tables, suggests matching XBRL elements, and prepares calculation relationships — so you can review and approve tags instead of creating them manually from scratch.
## Overview
The Tagger Agent supports both **Word documents** (DOCX) and **PDF documents** (PDF) with the same feature set for both document types.
The Tagger Agent processes two types of content:
- **Text blocks** – headings, paragraphs, and disclosure notes
- **Tables and calculations** – financial tables, including multi-page tables and calculation relationships between rows
> **Note:** All AI-assisted tagging functions require a valid AI licence.
## The 'AI Background Tasks' Panel
The **AI background tasks** panel shows the progress of all AI actions the Tagger Agent runs in the background — including **Detect document profile** (runs automatically when a document is opened), **Detect tables** (triggered via **Auto select** for PDF documents), and **Auto-tag table** (triggered via **Auto-tag table with AI**/**Tag table with AI**).
The 'AI background tasks' panel with a running task and two completed tasks
The panel is divided into two sections:
- **Active**: Shows all currently running tasks with a step-by-step progress display (e.g. **Prepare document**, **Extract structure**, **Tag cells**, **Apply sign logic**, **Validate and finalize**) and a progress bar in percent. Click **Cancel** to stop a running task at any time.
- **Recent**: Shows the most recently completed or cancelled tasks with their result (e.g. "12 cells tagged" or "Cancelled by user"), a task ID and timestamp, and a link to jump directly to the affected place in the document (**Open in viewer**) or to the report settings (**Open document settings**). Click **Clear** to remove the entire history; click the **×** next to an individual task to dismiss only that one.
## Using the Tagger Agent for Text Block Tagging
The Tagger Agent analyses the text content of the document and identifies text sections — for example, accounting policy disclosures, notes, and explanatory paragraphs — that can be tagged as XBRL text blocks.
For each identified text region, the agent performs the following steps:
- It detects the boundaries of the text block within the page.
- It suggests a matching XBRL taxonomy element (type Text or Text Block).
- It positions the tag at the exact coordinates of the content.
To start AI-assisted text block tagging:
1. Open the document in the **XBRL Document** workspace.
2. Switch to the **Text tagging** tab at the top of the document area.
3. Click **Auto-tag page with AI** in the function bar.
The "Auto-tag page with AI" button in the function bar
The agent proposes tags for the detected text blocks on the current page. The **AI Tagging Complete** dialog then opens.
4. In the dialog, choose how to proceed with the suggested tags: **Apply directly** to apply them immediately, or **Open review window** to approve or reject them individually beforehand (see [Reviewing AI Tagging Suggestions](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging-review.md)).
5. If you chose **Apply directly**: Review each applied proposal in the **Properties** panel and modify or remove it as needed.
> **Note:** This choice is only available for **Word documents**. For **PDF documents**, AI tagging suggestions continue to be applied directly. For more on the review window, see [Reviewing AI Tagging Suggestions](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging-review.md).
### Tagging an Individual Text Area Using AI Options
For a quick AI-assisted tag suggestion for a single text area, the available AI commands depend on the tagging status of that text area:
**Not-yet-tagged text area:** Select the desired text area. A **AI options** menu with the following commands is displayed:
| Option | Description |
|--------|-------------|
| **Tag with AI** | Automatically tags the selected text area with AI. |
| **Suggest tags for selection** | Retrieves AI recommendations for the selected text area without tagging it immediately. |
The 'AI options' menu for a selected, not-yet-tagged text area
**Already tagged text area:** The **Re-tag with AI** command is instead available in the tag's regular context menu, alongside the other commands for that element (see [Context Menu Commands in the Document View](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md#context-menu-commands-in-the-document-view)).
Proceed as follows:
1. On the **Text tagging** tab, navigate to the desired text area in the document.
2. Select the text area you want to tag.
3. Choose the desired option: for a not-yet-tagged text area, **Tag with AI** or **Suggest tags for selection**; for an already tagged text area, **Re-tag with AI** from the regular context menu.
## Using the Tagger Agent for Table and Calculation Tagging
The Tagger Agent also processes financial tables in Word and PDF documents. It detects table areas, extracts their content, and creates XBRL tagging proposals for numerical values and calculation relationships.
Table tagging by the agent includes:
- **Table detection** – identifies table areas on each page, including multi-page tables
- **Value tagging** – proposes XBRL element assignments for numerical cells in the table
- **Calculation tagging** – proposes calculation relationships between rows (summands and totals)
- **Flagging incomplete tables** – tables that cannot be reliably extracted are flagged for manual review
> **Note:** For PDF documents, table areas must first be detected using **Auto select** before they can be tagged (see [Automatically Detecting Tables in PDF Documents](#automatically-detecting-tables-in-pdf-documents-auto-select) below). For Word documents, the table structure is available directly from the document format.
### Tagging an Entire Table with AI
To start AI-assisted table tagging:
1. Open the document in the **XBRL Document** workspace.
2. Switch to the **Table tagging** tab at the top of the document area.
3. Select a cell inside the table you want to tag.
4. Click **Auto-tag table with AI** in the function bar.
The "Auto-tag table with AI" button in the function bar
The agent proposes XBRL element assignments for the numerical cells in the table. If the table is already partially tagged, only the untagged cells are completed. The **AI Tagging Complete** dialog then opens.
5. In the dialog, choose how to proceed with the suggested tags: **Apply directly** to apply them immediately, or **Open review window** to approve or reject them individually beforehand (see [Reviewing AI Tagging Suggestions](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging-review.md)).
Dialog shown after AI tagging completes — identical for text tagging and table tagging
6. If you chose **Apply directly**: Review each applied proposal and accept, modify, or reject it.
7. For tables flagged as incomplete, manually correct the table structure before accepting the agent's proposals.
8. To generate calculation linkbase relationships (summands and totals) for the table, click **Generate calculation** in the function bar.
The agent derives calculation linkbase relationships from the table structure and proposes summands and totals.
### Tagging an Individual Cell Using the Context Menu
Instead of tagging the entire table, you can also have a single, not-yet-tagged cell tagged directly with AI:
1. Right-click the not-yet-tagged cell.
2. Select **Tag this cell with AI** from the context menu.
Context menu of a not-yet-tagged table cell
The AI automatically suggests a matching XBRL element for the cell.
> **Note:** For a complete overview of all context menu commands for table cells and text elements — including the differences between Word and PDF documents — see [Working with Layers](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md#context-menu-commands-in-the-document-view).
### Automatically Detecting Tables in PDF Documents ('Auto select')
Unlike Word documents, where the table structure comes directly from the document format, the Tagger Agent detects tables in PDF documents using AI. A table must be detected before it can be tagged.
1. Switch to the **Table tagging** tab.
2. Click **Auto select** at the top right of the function bar.
The agent analyses the current page and detects the table areas it contains. Progress is shown in the **AI background tasks** panel under the **Detect tables** task.
3. Once a table has been detected, a **Table actions** toolbar appears above it.
It offers the same actions available for Word documents via the function bar: **Row order**, **Custom hierarchies**, **Tag table with AI**, **Generate calculation**, **Expand**, **Edit**, and **Delete table**.
4. Click **Tag table with AI** in the toolbar to tag the detected table with AI.
Tagging a table in a PDF document with AI
> **Note:** As long as no table has been detected, no context menu for tables is available in PDF documents. The **Table actions** toolbar only appears after detection via **Auto select** (see also [Context Menu Commands in the Document View](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md#context-menu-commands-in-the-document-view)).
> **Note:** Unlike Word documents, PDF documents allow several detected tables to be tagged with AI at the same time. While a table is being tagged, the document view is locked for that operation.
> **Note:** **Generate calculation for PDF documents**: Like **Row order** and **Custom hierarchies**, **Generate calculation** also requires the table to already contain at least one tagged cell. Unlike those two functions, however, this is not checked upfront: the action always starts as the **Calculate table** AI background task, but fails for a not-yet-tagged table with the message **"Table has no tagged cells. Tag at least one cell before running AI calculations."** in the **AI background tasks** panel.
## Retrieving an AI Explanation for a Tag
For any tag — whether created manually or by the Tagger Agent — you can retrieve an AI-generated explanation for the current tag proposal.
The **Advisor** tab is available in the **Properties** panel for all tag types. To retrieve the explanation:
1. Select the tag in the document for which you want to retrieve an explanation.
2. Open the **Advisor** tab in the **Properties** panel.
Advisor tab in the Properties panel
3. Click **Get AI explanation**.
The AI generates an explanation for the current tag proposal and displays it on the tab.
> **Note:** If you change tag properties after the explanation has been displayed, a notice appears indicating that the explanation is based on settings that have since been changed.
## The "Tagged by AI" Property
The **General** tab of the tag properties shows the **Tagged by AI** field, which indicates whether a tag was created by the Tagger Agent or manually. The **Last modified by** field shows the user who initiated the AI tagging.
---
---
title: "User Interface of the Lucanet XBRL Tagger"
description: "On this page, you can find information on the structure of the user interface and the main elements in the Lucanet XBRL Tagger. From this page, you can jump easily to the detailed descriptions of the individual areas and functions."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/user-interface-xbrltagger
language: en
last_updated: 2026-05-01
---
# User Interface of the Lucanet XBRL Tagger
## Overview
On this page, you can find information on the structure of the user interface and the main elements in the **XBRL Tagger**. From this page, you can go easily to the detailed descriptions of the individual workspaces of the XBRL tagger.
## Structure of the User Interface
After opening the XBRL Tagger from the main menu, the **application window** of the **Lucanet XBRL Tagger** is displayed.
> **Note:** The user interface differs slightly depending on whether you open a Word document or a PDF document. However, the basic structure of the user interface is the same in both cases.
The **application window** consists of the following elements:
XBRL Tagger user interface
The following elements are available in the user interface:
#### Navigation
You can use the breadcrumb **navigation** to switch between the different workspaces in XBRL Tagger. For example, you can use it to open the [Dashboard](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md), which displays all documents that have been loaded into XBRL Tagger.
#### Function bar
The **function bar** contains all functions for the currently open document.
#### Document view
Area in which a document is tagged (see chapter [XBRL document](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document.md)).
When a PDF document is open, the document is displayed as a rendered PDF with tagging overlays. You can switch between the **Text tagging** and **Table tagging** layers at the top of the document area to work with text blocks or tables. For more information, see [Tagging a Document](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md) and [Working with Layers](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md).
#### Panel
The **panel** contains buttons for showing and hiding additional and detailed information about the currently open document. The following can be displayed:
- Taxonomy
- Property
- Calculation
- Clipboard
- Footnote
- KVK filing information
- Document outline
- Version history
> **Note:** For PDF documents, only the **Taxonomy** and **Property** panels are available. They are displayed automatically as soon as an element is selected in the document. The other panels (Calculation, Clipboard, Footnote, KVK filing information, Document outline, Version history) are not available for PDF documents.
The panel also has its own bar at the bottom with the following functions: validation, generate XBRL report, AI background tasks.
#### Detail view
The **detail view** displays additional and detailed information about the current document. You can switch between the various details using the **panel**.
---
---
title: "Using Hidden Elements"
description: "In the XBRL Tagger, you can use the Hidden elements view to manually add and tag XBRL values that do not exist as visible elements in the source document. These values are referred to as hidden elements (hidden facts)."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/use-hidden-facts
language: en
last_updated: 2026-05-28
---
# Using Hidden Elements
## Overview
In the **XBRL Tagger**, you can use the **Hidden elements** view to manually add and tag XBRL values that do not exist as visible elements in the source document. These values are referred to as **hidden elements (hidden facts)**.
> **Note:** - According to ESEF guidelines, hidden elements are generally not recommended. In certain regulatory scenarios, however, hidden elements may be required.
> - Hidden elements are part of the document validation and the iXBRL export: they are taken into account during XBRL validation and included in the iXBRL report package.
> **Warning:** **Hidden elements** are only available if the **Use hidden elements** option is activated in the document settings.
## Activating Hidden Elements
To activate hidden elements for an XBRL document:
1. In the function bar, click the settings icon to open the **Document settings**.
2. In the **Tagging presets** area, activate the **Use hidden elements** option.
Enabling use of hidden elements
3. Save the settings.
4. The **Hidden elements** tab is now also displayed in the document.
Display of the 'Hidden elements' tab
## Adding Hidden Elements
To add hidden elements:
1. Open the **Hidden elements** tab:
'Hidden elements' tab
If hidden elements have already been saved in the document, they are automatically displayed in the table when you open the **Hidden elements** tab.
2. Click **Add** in the table.
3. A new row is added to the table.
4. In the new row, click the **Value** column and enter the value.
5. Click **Save**.
## Tagging Hidden Elements
To tag hidden elements:
1. In the **Taxonomy** area, search for the desired taxonomy element.
2. Drag and drop the taxonomy element onto the desired row in the table.
3. After tagging is successful, the table displays the information of the assigned taxonomy element in the **Label** and **Technical name** columns.
Table with hidden elements
4. Click **Save**.
## Editing Hidden Elements
To edit the value of an existing hidden element:
1. In the table, click the **Value** column of the desired hidden element.
2. Change the value and confirm your change by clicking **Save**.
## Deleting a Hidden Element
To delete a hidden element:
1. Click the **recycle bin icon**. The hidden element is removed from the table.
Deleting a hidden element
---
---
title: "Using the Document Outline"
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/document-outline
language: en
last_updated: 2026-07-23
---
# Using the Document Outline
The **Document Outline** panel displays all elements tagged in the document in a structured overview that follows the document hierarchy. It lists all tagged text and table elements at a glance and shows the assigned taxonomy concept as well as the technical element for each one.
It also serves as a navigation aid, letting you jump directly to a tagged element without having to search through the document manually.
> **Note:** The **Document Outline** panel is only available for Word documents (DOCX). It is not available for PDF documents.
The panel is available in both **Text tagging** and **Table tagging**:
- On the **Text tagging** tab, all tagged text blocks are listed, grouped by the document's headings.
- On the **Table tagging** tab, all tagged table elements are listed accordingly.
> **Note:** Continuous text blocks that span multiple continuation sections are marked in the outline as **Part 2/3**, **Part 3/3**, and so on.
## Opening the Document Outline
1. Open the document in the **XBRL document** workspace.
2. Click the **Document outline** icon in the sidebar (see screenshot).
The panel opens and shows all elements already tagged on the currently selected tab (**Text tagging** or **Table tagging**).
Document outline panel in the XBRL Tagger
## Navigating to a Tagged Element
Click an entry in the outline to jump directly to the corresponding location in the document.
Use the search field at the top of the panel to search for a specific element, for example by searching for "Balance Sheet" to jump directly to the corresponding balance sheet item.
> **Note:** Switch between the **Text tagging** and **Table tagging** tabs to display the matching outline for text blocks or table elements.
## Extension Elements in the Outline
Elements tagged with a concept from your **taxonomy extension** are shown in the outline just like elements from the **base taxonomy** — on both the **Text tagging** and **Table tagging** tabs. Extension elements are marked with their own icon and the technical name of the element, so you can find these tags directly in the outline too and use the outline to navigate to the corresponding location in the document.
> **Tip:** For more information on creating extension elements, see [Creating a Taxonomy Extension](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrltagger-extend-taxonomy.md).
---
---
title: "Using the Tag Update Preview"
description: "After a roll-forward, the Tag Update Preview lets you review which tags were automatically carried over from the previous file version before the changes are applied."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-update-preview
language: en
last_updated: 2026-09-04
---
# Using the Tag Update Preview
When you upload a new version of an already tagged Word or PDF document via [Import new file version](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md), the XBRL Tagger automatically carries the existing tags over to the new document version (**roll-forward**). Before these changes are permanently applied to the document, the **Tag Update Preview** opens automatically. There you can review all the tags that were carried over and decide whether to apply the changes, edit them individually, or discard them.
> **Note:** If not a single tag could be carried over during the roll-forward of a PDF document, the Tag Update Preview does not open. Instead, the message "Document Not Rolled Forward – No tags could be carried forward onto the new PDF. The existing document is unchanged." appears. In this case, the document remains unchanged in its previous version.
> **Note:** Only one Tag Update Preview can be open for a document at a time. As long as a preview has not yet been completed, opening the document takes you back to the Tag Update Preview automatically, and no further new file version can be imported for this document.
## Structure and Functions of the Tag Update Preview
The following sections describe the structure and functions of the Tag Update Preview.
### Header
The header of the Tag Update Preview contains the following areas:
- The **status bar**, which shows which document the tags come from and which document they are being migrated to: "Tags from **[source document]** will be migrated to **[target document]**".
- The **toolbar** with buttons for cancelling, saving, and applying the changes.
- The **progress display** with the number of tags still pending, already approved, and removed, plus a progress bar showing the overall review progress as a percentage.
Header of the Tag Update Preview
### Adjusting the View
Use the following functions to adjust the Tag Update Preview to your needs:
- The **Text tagging** and **Table tagging** tabs determine whether the change list and the document view show changes to text content or to tables.
- In the **Current Document**/**Updated Document**/**Mixed View** group, you choose which version of the document is shown in the document view:
- **Current Document:** shows the previous document version.
- **Updated Document:** shows the new document version with the changes that were carried over.
- **Mixed View:** shows the previous and the new version of a changed section directly one below the other for comparison.
Functions for displaying the desired version of the document
- The checkboxes under **Show** let you show or hide the **Document view** and **Fact properties** areas individually.
> **Note:** The **Tags** checkbox is enabled by default and is available in addition to these; the change list itself remains visible regardless of it.
### Change List
The change list on the left shows all tags that were carried over from the previous document version during the roll-forward. Each entry in the change list shows:
- The affected text passage or table element.
- The assigned taxonomy concept and the technical element.
- An indicator of the type of change (e.g. **Modification** for a content change, or **Removal** if an element is no longer present in the new document version).
Change list in the Tag Update Preview
Use the checkboxes to the left of the entries to select one or more entries, or **Select all** to mark the entire list.
Use the drop-down list to the right of an entry to set whether that tag should be approved, rejected, or set to pending.
The following actions are available:
| Action | Description |
|---|---|
| **Approve** | Sets the selected entries to **approved**. |
| **Reject** | Sets the selected entries to **removed**. |
| **Pending** | Resets the selected entries back to **pending**. |
Use the search field above the list to search specifically for a tag name or an element ID.
### Legend
Click the **Legend** button in the top-right corner to open a window that explains the colour coding of the highlights in the document view.
Legend button of the Tag Update Preview
The colours have the following meaning:
| Colour | Meaning |
|---|---|
| Green | The change has been approved. |
| Yellow | The content was shortened or extended and still needs to be reviewed. |
| Red | The element is no longer present in the new document version. |
### Document View
The document view in the middle shows the document as read-only, in the version you selected in the **Current Document**/**Updated Document**/**Mixed View** group (see [Adjusting the View](#adjusting-the-view)).
Changed text passages and tables are highlighted in colour and marked with the **Changed** label as well as the tag's current review status (e.g. "Pending"). Use the zoom controls in the top-right corner of the document view to zoom in or out.
Highlighted change in the document view
> **Note:** The document view is a reduced, read-only variant of the document viewer and is also used in the review window to review AI tagging suggestions (see [Reviewing AI Tagging Suggestions](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging-review.md)).
## Viewing Details of a Change
When you click an entry in the change list or the entry in the document view, the **Fact properties** panel opens on the right with detailed information about this tag. The following properties are displayed:
- **XBRL Element:** the full taxonomy URL of the assigned concept
- **Change Type:** the type of change (e.g. "Modification")
- **Review Status:** the tag's current review status (e.g. "Pending Review")
- **Old Value** and **New Value:** the previous and the new value of the element, if available
Fact properties for a change
## Applying or Discarding Changes
The following buttons are available in the header to edit and complete the Tag Update Preview:
- **Discard Changes:** Deletes the entire Tag Update Preview. Since this action cannot be undone, a confirmation dialog appears beforehand, noting that the roll-forward changes will be discarded and the document remains unchanged.
- **Close:** Takes you back to the dashboard without completing the Tag Update Preview. A separate save step isn't necessary: every approve, reject, or reset-to-pending decision in the change list is applied automatically as soon as you click it, with no confirmation message. If saving a decision fails, the message "Failed to save the review decision. Please try again." appears, and the affected decision is reset to its previous status. The Tag Update Preview remains open, and the document stays locked until you apply or discard the changes.
- **Apply to the document:** Transfers all entries with the status "approved" to the document and completes the Tag Update Preview.
> **Note:** The **Apply to the document** button is disabled while any entries are still **pending**; a tooltip explains: "Review in progress. All suggestions must be approved or rejected." First set all entries to **approved** or **removed** (see [Change List](#change-list)) to enable the button.
Buttons of the Tag Update Preview
---
---
title: "Using XBRL Blueprint"
description: "XBRL blueprint lets you inspect the structure of your extension taxonomy live in the XBRL Tagger — in the Presentation, Calculation, and Definition linkbase trees, without generating a report package first."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-blueprint
language: en
last_updated: 2026-07-27
---
# Using XBRL Blueprint
**XBRL blueprint** lets you inspect the structure of your extension taxonomy directly in the XBRL Tagger — live, and without generating a report package first. The function shows all tagged elements in the three linkbase trees **Presentation**, **Calculation**, and **Definition**, and updates automatically with every tagging change.
## Opening XBRL Blueprint
Click **XBRL blueprint** in the document toolbar to open the panel below the document view.
> **Note:** The **XBRL blueprint** button is only enabled when the active reporting requirement includes an extension taxonomy and at least one element in the document has already been tagged with an extension element. If no extension taxonomy is present, the button remains disabled.
XBRL blueprint in the XBRL Tagger
## Structure of the Panel
Use the three tabs **Presentation**, **Calculation**, and **Definition** to switch between the three linkbase views of the extension taxonomy. Each tree shows the full hierarchy — both the extension elements and the referenced elements from the base taxonomy. Extension elements are visually distinguished from base taxonomy elements, among other things by a dedicated icon and the company's namespace prefix (e.g. `company:...`) instead of the base taxonomy's prefix (e.g. `ifrs-full:...`).
The following search and filter options are available above the tree:
- A search field (**Search...**) to search specifically for an element.
- The **by technical name** and **by exact match** checkboxes, to narrow the search to the technical name or to exact matches.
- The **Show exact value** checkbox.
- Four drop-down lists to restrict the display: **Select period**, a drop-down list to filter by balance, **Select data type**, and **Select namespace**.
Each element in the tree shows its **taxonomy tag** and its **technical ID**, as well as — if available — the tagged values, grouped by reporting period and unit (e.g. EUR, EUR/xbrli:shares).
## Live Synchronization
The panel is generated directly from the document's current tagging state, without requiring a report package to be generated first. Every tagging change in the document is reflected in the tree immediately; no manual refresh is needed.
---
---
title: "Validations in XBRL Documents"
description: "A document can be checked for errors, validity and completeness by means of validations. Lucanet XBRL Tagger has two validation types."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/validation_xbrltagger
language: en
last_updated: 2026-05-01
---
# Validations
## Overview
A document can be checked for errors, validity and completeness by means of **validations**. The XBRL Tagger has two types of validation:
- Validations executed while editing the document, referred to as **in-tool validations**. The currently tagged areas are checked for inconsistencies and errors.
- Validations that are automatically carried out when creating an iXBRL document.
## Display In-Tool validations
The results of the In-Tool validations performed while editing a report are displayed in a separate view. To view the validations, proceed as follows:
1. Click on the open validation view icon in the right sidebar to display the validations.
2. The results of the validations are displayed as follows, for example:
Display of validation results
## Validation Result Types
The validation results are divided into the following types:
| Type | Description |
|---------|---------|
| Validation error | Shows errors detected during the validation process. The listed errors must be rectified. |
| Validation warning | Shows warnings that may have to be edited. The listed warnings should be checked. |
| Validation information | Shows general information, for example on non-tagged values in a table. |
| Validation success | Shows the validation areas in which no errors were found. |
## Options for Validation Results
The following options are available for validation results:
| Option | Description |
|---------|---------|
| the info pink icon | Click the icon to show details on the message. |
| the navigateto mapping icon | Click the icon to display the tag and its properties. |
| Filter results | Shows options for filtering the validation results: |
| Re-validate | Carries out all validation processes again. |
## Validations When Creating an iXBRL Report
When creating an iXBRL report, a complete XBRL validation is conducted, covering the following specifications:
- XBRL Specification 2.1
- XBRL Dimensions 1.0
- XBRL Formula 1.0
- Table Linkbase 1.0
- Extensible Enumerations 1.0 and 2.0
- Inline XBRL 1.1 incl. XHTML and Transformation Registries 1-4
- Unit Registry
- Additionally, a so-called filing rule validation is performed. For example, an ESEF report is checked against the [ESEF Reporting Manual](https://www.esma.europa.eu/sites/default/files/library/esma32-60-254_esef_reporting_manual.pdf) and the rules it contains.
> **Note:** An iXBRL report is created in the [XBRL document](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document.md) workspace by clicking **Generate iXBRL report package**.
---
---
title: "Working with Footnotes"
description: "In the XBRL Tagger, you can use tagged text blocks as footnotes. To do so, link the tagged text block to one or more cells of a table."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/footnote-tagging
language: en
last_updated: 2026-05-28
---
# Working with Footnotes
## Overview
In the **XBRL Tagger**, you can use tagged text blocks as **footnotes**. To do so, link the tagged text block to one or more cells of a table.
## Creating Footnotes
To create a new footnote:
1. If necessary, open the desired document and switch to the **Text tagging** tab.
Opening the 'Text tagging' tab
2. Select a tagged text block in the document.
> **Note:** If you want to use a text block as a footnote that is not yet tagged, drag the desired tag from the taxonomy onto the selected text block (see [Tagging a Document Manually](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md)).
3. In the side bar, click the **Footnote** panel.
The panel shows the footnote connections of the currently selected text block, if any. If the selected text block is not yet linked to a cell in a table, the **Footnote** panel is displayed as follows:
Footnote panel at start, with no cell selected in a table
4. Switch to the **Table tagging** tab.
5. In the desired table, select the cell(s) to which the selected text block should be assigned as a footnote:
The selected cell is assigned to a table cell in the Table tagging view
6. Click **Attach to footnote**.
Footnote panel before any footnote is created
7. The assigned footnotes are then displayed in the panel, for example, as follows:
Footnote assigned to three cells of a table
## Values of the Footnote
When you select a text block linked to a footnote, the **Footnote** panel shows the **Values of footnote** area with the following columns:
- **Table**: Name of the table the cell comes from.
- **Column**: Column header of the linked cell.
- **Tag**: Tag name of the linked cell.
- **Value**: Value of the linked cell.
## Functions in the Footnote Panel
The following functions are available for a footnote connection:
| Function | Description |
|---------|---------|
| **Navigate to cell** | Navigates from the **Footnote** panel to the linked cell in the document |
| **Delete** | Removes the link from the footnote. |
---
---
title: "Working with Layers"
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer
language: en
last_updated: 2026-05-01
---
# Working with Layers
## Overview
In **XBRL Tagger**, **layers** allow you to apply different tags to the same text block more than once. Because tags within one layer must not overlap, you can add another layer for overlapping tagging ranges. This is useful when, for example, a paragraph has to be tagged with two different taxonomy elements.
Each document in XBRL Tagger has two predefined layers by default: a default layer for text and a default layer for tables.
In the editor, only the tags of the active layer are displayed. You can create and manage additional layers in the **Layer Manager**.
## Default Layers in XBRL Tagger
In the **XBRL Document** workspace, two **tabs** at the top of the document area allow you switch between layers for text tagging and table tagging:
- **Text tagging**: Activates the layer for text tagging. Table tags are hidden and only text tags are displayed.
- **Table tagging**: Activates the layer for table tagging. Text tags are hidden and only table tags are displayed.
'Text tagging' and 'Table tagging' tabs in XBRL Tagger
## Creating and Editing Layers
In the **Layers** drop-down list, you can add, edit, or delete layers. To add a layer:
1. Open the drop-down list **Layers** and click **Add new text layer**.
Saving a new layer
2. Enter a name for the new layer, then click **Save layer**.
Add new layer
## Switching Layers
To switch to a different level, follow these steps:
1. Open the **Layers** drop-down list.
2. Click on the desired layer.
Switching to layer 1
3. The selected layer is displayed in the editor.
## Additional Options in the 'Layers' Dialog
Additionally, the following options are available in the **Layers** dialog:
| Option | Description |
|---------|---------|
| the for deleting a layer icon | Deletes the layer.
**Note:** - If the layer already contains tags, a warning appears that all associated tags will also be deleted. - The default layers cannot be removed. |
| the for editing a layer icon | Opens editing mode for the selected layer. Change the name and click **Save** to change the layer name.
**Note:** The default layers **Text import** and **Table import** cannot be renamed; the edit and delete icons are disabled for these two layers.
|
## Moving a Tagged Element to Another Layer
Both tagged text sections and tagged tables can be moved to a different layer afterwards, without having to re-create the tag.
> **Note:** **Move to another layer** is only available for Word documents. For PDF documents, the context menu does not contain this command (see [Context Menu Commands in the Document View](#context-menu-commands-in-the-document-view)).
### Moving a Text Element
1. Right-click the tagged text section.
2. Select **Move to another layer** from the context menu.
A submenu shows the available target layers.
Context menu of a tagged text section with the option 'Move to another layer'
3. Select the desired target layer.
The tag is moved to the selected layer. A placeholder appears at its original position on the source layer, indicating which layer the element is now on.
### Moving a Table
1. Right-click the table tag above the tagged table.
2. Select **Move to another layer** from the context menu.
Context menu of a tagged table with the options 'Move to another layer' and 'Copy to layer'
3. Select the desired target layer.
The entire table structure with all tags is moved to the selected layer.
> **Note:** To copy a tagged table to another layer instead of moving it — leaving the source layer unchanged — use the **Copy to layer** option (see [Tagging a Document Manually](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md)).
## Context Menu Commands in the Document View
Right-clicking in the document view opens a context menu. Which commands are available depends on whether you click a text element or a table element, whether it is already tagged, and whether the document is a **Word** or a **PDF document**.
> **Warning:** For PDF documents, right-clicking the table tag above a tagged table does **not** open a context menu. The corresponding table actions are instead available via the table toolbar that appears when the table is selected.
### Context Menu for Text Elements ('Text tagging' Tab)
| Command | Description | Word Document | PDF Document |
|---|---|---|---|
| **Set status** | Opens a submenu to set the tag's review status (**In progress**, **Pending review**, **Final**). | Available | Not available |
| **Continuation administration** | Opens the **Continuation administration** dialog if the tag is part of a continuation chain (see [Managing Continuation Chains](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/continuation-administration.md)). | Available if the tag has continuation elements | Not available |
| **Move to another layer** | Opens a submenu with the available target layers and moves the element there. | Available | Not available |
| **Cut** | Cuts the element to the clipboard. | Available | Available |
| **Copy** | Copies the element to the clipboard. | Available | Available |
| **Paste** | Pastes the clipboard content. Only active if something was previously cut or copied. | Available | Available |
| **Edit** | Opens the tag for editing. Only appears if the element consists of several linked text anchors. | Available | Available |
| **Tag with AI** | Appears for a selected, not-yet-tagged text area and tags it automatically with AI. | Available | Not available |
| **Suggest tags for selection** | Retrieves AI recommendations for the selected, not-yet-tagged text area without tagging it immediately. | Available | Not available |
| **Re-tag with AI** | Re-tags the element with AI. | Available | Not available |
| **Delete** | Removes the tag from the element. | Available | Available |
For a selected, not-yet-tagged text area, the AI-specific commands are shown in their own **AI options** context menu:
Context menu 'AI options' for a selected, not-yet-tagged text area
For more details on AI-assisted tagging, see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
### Context Menu for Table Elements ('Table tagging' Tab)
For tables, a distinction is made between the context menu of the **table tag** (right-click the tag label above the table) and the context menu of an **individual cell** (right-click a cell inside the table).
**Table tag (entire table):**
| Command | Description | Word Document | PDF Document |
|---|---|---|---|
| **Move to another layer** | Moves the entire table structure with all tags to another layer. | Available | No context menu available (see note above) |
| **Copy to layer** | Copies the table structure with all tags to another layer; the source layer remains unchanged. Only available if the table is already tagged. | Available | No context menu available |
| **View table properties** | Opens the properties of the table. | Available | No context menu available |
| **Delete** | Removes all tags of the table. | Available | No context menu available |
**Individual cell:**
For a not-yet-tagged value cell, the context menu shows only a few commands:
| Command | Description | Word Document | PDF Document |
|---|---|---|---|
| **Copy** | Copies the cell content to the clipboard. | Available | Available |
| **Paste** | Pastes the clipboard content. Only active if something was previously copied. | Available | Available |
| **Tag this cell with AI** | Suggests a tag for the cell automatically using AI. Requires an AI license. | Available | Not available |
| **Delete** | Removes the cell's content. | Available | Available |
Context menu of a not-yet-tagged table cell
The same commands as for text elements apply to an already tagged cell (see table above: Set status, Continuation administration, Move to another layer, Cut, Copy, Paste, Edit, Re-tag with AI, Delete). In addition, the following table-specific AI command is available:
| Command | Description | Word Document | PDF Document |
|---|---|---|---|
| **Validate this cell's tag** | Appears for an already tagged cell and lets AI check the existing tag. | Available | Not available |
> **Note:** If several elements are selected at the same time, **Move to another layer** acts on the entire selection.
---
---
title: "XBRL Document"
description: "The 'XBRL document' workspace is the main workspace in the Lucanet XBRL Tagger. The documents from the document overview are tagged in the 'XBRL document' workspace."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document
language: en
last_updated: 2026-07-27
---
# XBRL Document
## Overview
The **XBRL document** workspace is the main workspace in the **XBRL Tagger**. The documents from the **Dashboard** are tagged in the XBRL document workspace.
## XBRL Document Workspace
The **XBRL document** is divided principally into three areas:
Document view with a Word document
> **Note:** The document view of PDF documents is structured similarly and differs only slightly from the document view of a Word document.
The following elements are displayed as soon as you open a document from the [Dashboard](https://support.lucanet.com/en/documentation/xbrl-tagger/dashboard-xbrltagger.md):
- **Document**: shows the document currently open. In the document:
- The [status of the tags](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/tag-status.md) is displayed in color. Areas marked in green, for example, have already been tagged, checked, and accepted and have therefore been assigned the **Final** state.
- Elements provided with a **content control element** are marked in yellow. The areas marked in yellow in a document must be tagged. As soon as you mark the area of a content control element, the area is displayed in blue. This allows you to easily identify what exactly belongs to the content control element.
> **Note:** **Content control elements** are Word elements that can be created, for example, in the [Disclosure Management](https://support.lucanet.com/en/documentation/disclosure-management.md) solution or in a Word document outside the CFO Solution Platform.
- A **red triangle** may be displayed in the top, left corner of **value cells**. The red triangle indicates that there is a validation message for this value. Move the cursor onto the red triangle to display the reason for the validation message in a tool tip.
- **Detailed and additional information**: Depending on the view selected in the **toolbar** on the right, additional and detailed information about the currently open document is displayed.
> **Note:** For more information on tagging text and tables, see [Tagging a Document Manually](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrl-tag-document.md) and [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md).
The following views are available in the toolbar:
| View | Description |
|---|---|
| **Multi-panel** | Enables the simultaneous display of multiple views side by side. |
| **Taxonomy** | The **taxonomy** used in the document. |
| **Properties** | Displays the properties of a selected tag or taxonomy element (see [Displaying and Editing Properties of Tags](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/edit-tag-properties.md)). |
| **Calculation** | Mathematical relationships between elements of the annual financial statements (e.g., total assets = current assets + fixed assets) (see [Using the Calculation View](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/calculation-view.md)). |
| **Clipboard** | Displays mappings in the clipboard. |
| **Footnote** | Enables the management of footnotes in the document (see [Working with Footnotes](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/footnote-tagging.md)). |
| **KVK filing Information** | Displays filing information for the KVK. Only displayed if KVK was selected as the taxonomy. |
| **Document outline** | Enables navigation via an outline of the text and table elements tagged in the document (see [Using the Document Outline](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/document-outline.md)). |
| **Version history** | Displays the version history of the document. **Note:** The version history supports up to 50 saved versions. Once this limit is reached, older versions are replaced, with the exception of versions marked as favorites, which are retained. |
| **Validation** | Checks of the document for errors, validity, and completeness (see [Validations](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/validation_xbrltagger.md)). |
| **Generate XBRL report** | Generates the iXBRL report (see [Generating an XBRL Report Package](https://support.lucanet.com/en/documentation/xbrl-tagger/generate-ixbrl.md)). |
| **AI background tasks** | Shows the progress of the Tagger Agent's AI actions running in the background (see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md)). |
## General Functions When Editing a Word Document
In addition to special functions, the following general functions are available in the top bar:
| Option | Description |
|---------|---------|
| **Add Extension** | Function used to create an extension, see [Taxonomy Extensions](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/xbrltagger-extend-taxonomy.md). |
| **Download document** | Loads the file with all mapping information into a desired directory. All settings, the selected taxonomy, the tags with properties and status, and all metadata are part of the file and stored in it. |
| **Save document** | Saves the current status of the document on the server. |
| **Save as version** | Saves the current status of the document as a named version. The version history of a document can be accessed via the toolbar on the right. |
| **Generate iXBRL report package** | Generates the iXBRL report including all documents and folders prescribed by the regulatory authorities in what is referred to as an iXBRL report package. Excel files, which display additional information on the document, are created in addition to the actual report. You can read the respective details in [Generating an iXBRL Report Package](https://support.lucanet.com/en/documentation/xbrl-tagger/generate-ixbrl.md). The finished document and all reports are displayed in the [Result Document](https://support.lucanet.com/en/documentation/xbrl-tagger/ergebnisdokumente.md) workspace and can be loaded from there. |
| the function search icon | Opens an input field, in which you can search for functions provided by the XBRL Tagger. It is an intelligent search, which provides you with the functions most suitable to the entered search term. **Note:** The input field can also be opened by pressing **CTRL + SHIFT + P**. |
## General Functions When Editing a PDF Document
Word and PDF documents generally offer the same tagging functionality. However, for PDF documents some of the general functions and views described above differ:
Editing a PDF document
### Functions in the Toolbar of a PDF Document
The following table shows which functions are available in the toolbar when editing a PDF document:
| Function | Description |
|---|---|
| **Layers** | Shows the active layer and allows you to switch between layers (see [Working with Layers](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/using-layer.md)). |
| **Cut** / **Copy** / **Paste** | Cuts, copies, or pastes the content of the clipboard for a selected element. Only active if an element is selected or the clipboard contains content. |
| **Undo** / **Redo** | Undoes the last action or restores it. |
| **Taxonomy** | Opens the **Taxonomy** panel (see [The following views are available in the toolbar](#xbrl-document-workspace) above). |
| **Clipboard** | Opens the **Clipboard** panel (see table above). |
| **Validation** | Opens the **Validation** panel (see table above and [Validations](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/validation_xbrltagger.md)). |
| **AI background tasks** | Opens the **AI background tasks** panel (see table above and [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md)). |
| **Auto select** | Additional function in table tagging that is not available for Word documents: automatically detects table areas on the current PDF page using AI before they can be tagged (see [Automatically Detecting Tables in PDF Documents](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md#automatically-detecting-tables-in-pdf-documents-auto-select)). |
### Functions for PDF Documents in Table Tagging
Once a table has been selected — or, for PDF documents, detected via **Auto select** — a toolbar appears above it:
Tagging a table in a PDF document with AI
The following functions are available in the toolbar:
| Function | Description |
|---|---|
| **Row order** | Allows you to change the order of table rows. |
| **Custom hierarchies** | Opens the management of custom hierarchies for the table (see [Custom Hierarchies](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/userdefined-hierarchies.md)). |
| **Tag table with AI** | Tags the table using AI (see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md)). |
| **Generate calculation** | Generates calculation relationships (summands and totals) for the table (see [Tagging a Document with AI](https://support.lucanet.com/en/documentation/xbrl-tagger/xbrl-document/ai-tagging.md)). |
| **Expand** | Opens a submenu with other available table layers. |
| **Edit** | Opens the table for editing. |
| **Delete table** | Removes the table and all associated tags. |
---
---
title: "XBRL Tagger"
description: "You can use the Lucanet XBRL Tagger to immediately tag your business report without an implementation project or any IT knowledge and convert it into iXBRL. The time required to create the report is reduced considerably by processing all taxonomies and creating them correctly according to the latest standard."
source_url: https://support.lucanet.com/en/documentation/xbrl-tagger
language: en
last_updated: 2026-05-01
---
# XBRL Tagger
With the **European Single Electronic Format** ([ESEF](https://support.lucanet.com/en/documentation/glossary.md#esef)) published by the **ESMA (European Securities and Market Authority)**, all listed companies in the EU are obliged to store their annual financial statements in [XBRL](https://support.lucanet.com/en/documentation/glossary.md#xbrl) from 2020. **Lucanet XBRL Tagger** helps you to do so.
The XBRL tagger can do this for you:
- The XBRL Tagger makes the selection of taxonomies particularly easy, as these are already set up in pre-configured **Reporting requirements**. Thanks to the certified and generic implementation, additional reporting requirements can be easily added to the LucaNet XBRL Tagger. The XBRL Tagger supports users in creating reports in iXBRL format, including ESEF.
- You can use our XBRL Tagger to immediately tag your business report without an implementation project or any IT knowledge and convert it into [iXBRL](https://support.lucanet.com/en/documentation/glossary.md#ixbrl). The time required to create the report is reduced considerably by processing all taxonomies and creating them correctly according to the latest standard.
- Once it has been created, the mapping can be transferred simply to the following year.
- Our solution ensures reliable ESEF reporting according to the current requirements. We rely on the unique approach of our integrated XBRL Engine, which enables the implementation of technical marking, i.e. tagging.
- The XBRL Tagger is an ideal supplement to the Disclosure Management. You can transfer documents from the [Lucanet Disclosure Management](https://support.lucanet.com/en/documentation/glossary.md#disclosure-management) smoothly into the XBRL Tagger and further process them there.
XBRL Tagger on the Lucanet CFO Solution Platform
[Request demo](https://www.lucanet.com/en/request-demo/)
> **Note:** - Are you already using the Lucanet CFO Solution Platform and, for example, the Lucanet Disclosure Management? In this case our XBRL Tagger will be an ideal supplement. Get in touch with your Lucanet contact for licensing the XBRL Tagger or write to us at [Contact](https://www.lucanet.com/en/contact/).
> - You are not yet a Lucanet customer and would like to know more about our solutions? Then write to us at [Contact](https://www.lucanet.com/en/contact/).
---
## Tax Compliance & Reporting
---
title: "'My Forms' Workspace"
description: "The 'My Forms' workspace is the central place for managing tax reports and is divided into the 'Drafts', 'Forms', and 'Transmitted' tabs."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-services/overview-forms
language: en
last_updated: 2026-05-01
---
# 'My Forms' Workspace
## Overview
The **My forms** workspace is the central place for managing tax reports in Tax Services. Here, you can create, edit, and transmit tax forms to German tax authorities.
The workspace is divided into three tabs:
- Drafts
- Forms
- Transmitted
To open a form from one of these overview tabs, click the form.
### Drafts
The **Drafts** tab shows all forms of the selected unit that are in progress and have not yet been transmitted.
'Drafts' tab
The **Drafts** tab contains the following information:
- Current processing step
- Editor
- Date of the last change
- Form package version
- Data type version
Drafts can be opened with a click and then edited. The system automatically locks the forms during editing. Locked forms are highlighted with gray hatching in the overview.
In addition, drafts can be copied or deleted via the tab's three-dot menu:
Three-dot menu of the 'Drafts' tab
### Forms
The **Forms** tab shows available form templates from which you create new forms.
'Forms' tab
The following form templates are available:
- Änderung der Bankverbindung (change of bank details)
- Änderung der Adresse (change of address)
- Belegnachreichungen zur Steuererklärung (subsequent submission of documents for the tax return)
How to create a new form is described in [Creating a Form](https://support.lucanet.com/en/documentation/income-taxes/tax-services/create-form.md).
### Transmitted
The **Transmitted** tab shows all reports that have already been successfully transmitted to the tax authority in read-only mode.
'Transmitted' tab
> **Note:** - Transmitted forms can no longer be edited. This overview supports the documentation and traceability of your tax reports.
>
> - You can check the transmission results and the tax authority's confirmation in the form overview.
>
> - You can still copy transmitted forms.
>
> - Completed forms are subject to a statutory retention obligation of 10 years. You can only delete a form after this period has expired.
---
---
title: "(Special) Investment Income"
description: "The ‘(Spezial-) Investmenterträge’ ((Special) Investment Income) workspace is used to enter issues pursuant to section 20 (1.3 and 1.3a) of the Income Tax Act (EStG)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/special-investment-returns
language: en
last_updated: 2026-05-28
---
# (Special) Investment Income
## Overview
In the **(Spezial-) Investmenterträge (Special Investment Income)** workspace, income from (special) investment funds can be entered centrally. The entered data is forwarded, for example, to **schedules SPIF, SPIFA, AESt, KAP**, and to **assessment forms for partnerships**.
## Navigation
You can access the **(Spezial-) Investmenterträge** workspace under **Company | Current Taxes | (Spezial-) Investmenterträge**. The **(Spezial-) Investmenterträge** workspace is displayed as follows, for example:
Investmenterträge' (Special Investment Income) workspace")'(Spezial-) Investmenterträge' (Special Investment Income) workspace
## Options
The following options are available in the **(Spezial-) Investmenterträge** workspace:
| Option | Description | Company | Select the desired Company in the drop-down list.
Own: Only the issues relating to (special) investment income of the individual company currently edited are displayed.
Group internal: All issues relating to (special) investment income created in the (sub-)group are displayed.
Tax group: All issues relating to (special) investment income created in the tax group are displayed. |
|---------|---------|---------|---------|
| Company | Select the desired **Company** in the drop-down list. - **Own**: Only the issues relating to (special) investment income of the individual company currently edited are displayed. - **Group internal**: All issues relating to (special) investment income created in the (sub-)group are displayed. - **Tax group**: All issues relating to (special) investment income created in the tax group are displayed. |
| Create | Opens a workspace where you can enter details on a (special) investment fund. |
| Import | Opens a workspace where you can configure an import: | The following options are available: **Import**: imports the data from the file chosen under **File path**. **Vorlage Investmentfonds** (Investment fund template): loads the existing Excel import template to the local hard drive. **Vorlage Spezialfonds inkl. Anlage SPIF** (Special investment fund template incl. SPIF attachment): loads the existing Excel import template for (special) investment income, including the option to enter information for the SPIF attachment, to the local hard drive. **Destination**: Define here the import destination: Choose either Investmenterträgen (Investment income) or **Spezial-Investmenterträgen incl. Anlage SPIF**. **Delete existing imports**: Activate this check box if an existing import is to be deleted before the next import process. **File path**: file from which data are to be imported. the special invest return import icon Import configuration of (Special) investment income |
| Report | Generates an Excel file containing all entries of the list |
---
---
title: "(Sub-) Group"
description: "The data of the individual companies are aggregated in the (Sub-)Group functional area."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group
language: en
last_updated: 2026-09-29
---
# (Sub-) Group
## Overview
The data of the individual companies are aggregated in the **(Sub-)Group** functional area.
## Workspaces in the (Sub-)Group Area
The following workspaces are available in the **(Sub-)Group** functional area, depending on the selected company and the configuration:
- [Status](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/milestone-status-subgroup.md)
- [Deferred Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/deferred-taxes-subgroup.md)
- [TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/trr.md)
- [Validation](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/validation-sub-group.md)
- [Reports](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Reports-company-workspace.md)
- [Report DT](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/reports-sub-group/report-ls.md)
- [Report DT Pos](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/reports-sub-group/report-ls-pos.md)
- [Report DT (LCF)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/reports-sub-group/report-vv.md)
- [Report TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/reports-sub-group/report-trr.md)
- [Import](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/bulk-import.md)
> **Note:** With the exception of the **Status** workspace, the workspaces are available only for companies for which the **(Sub-)Group** check box has been activated in the **Companies** workspace (see [Companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) master data area).
---
---
title: "§ 15a EStG"
description: "You can use the §15a EStG workspace to enter or display losses with limited liability."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/15A-EStG
language: en
last_updated: 2026-05-28
---
# § 15a EStG
## Overview
In the **§ 15a EStG** work area, you can enter all relevant information on loss offsetting for limited partners and comparable shareholders.
> **Note:** The **§ 15a EStG** workspace is available only to partnership companies.
## Navigation
You can access the workspace **§ 15a EStG** under **Company | Current Taxes | § 15a EStG**.
The **§ 15a EStG** workspace is displayed as follows, for example:
'§ 15a EStG' Workspace
---
---
title: "§ 8b KStG"
description: "Both what is referred to as the net method (tax exemption of issues pursuant to section 8b of the Corporate Tax Act at the level of the receiving company) and the gross method can be applied in Income Taxes (applies to partnership companies and tax group members). The § 8b KStG workspace is available to enter these issues to enable differentiated treatment and automated calculation."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/s-8b-kstg---beteiligungen-an-anderen-koerperschaften-und-persone
language: en
last_updated: 2026-05-28
---
# § 8b KStG – Investments in Other Corporations and Associations
## Overview
Both what is referred to as the **net method** (tax exemption of issues pursuant to **section 8b of the Corporate Tax Act** at the level of the receiving company) and the **gross method** can be applied in Income Taxes (applies to partnership companies and tax group members).
The **§ 8b KStG** workspace is available to enter these issues to enable differentiated treatment and automated calculation.
## Navigation
You can access the **§ 8b KStG** workspace under **Company | Current Taxes | § 8b KStG**.
The **§ 8b KStG** workspace is displayed as follows, for example:
'§ 8b KStG' workspace
## Options
The following options are available in the **§ 8b KStG** workspace:
| Option | Description | Company | Select the desired company in the drop-down list. The following options are available:
Own: only the issues of the individual company chosen for editing
Group internal: all entered issues according to section 8b of the Corporate Tax Act of the entire group.
Tax group: issues within the tax group |
|---------|---------|---------|---------|
| Company | Select the desired company in the drop-down list. The following options are available: - **Own**: only the issues of the individual company chosen for editing - **Group internal**: all entered issues according to section 8b of the Corporate Tax Act of the entire group. - **Tax group**: issues within the tax group |
| Create | Opens a dialog where the details of an issue according to section 8b can be entered. The relevant data and the legal basis are entered here. Depending on the selection made under **Issue**, the relevant fields for this issue must then be completed.
To display the issue correctly in the **BEG attachment**, the **partner ID** must be entered.
|
| Import | Opens the **§ 8b KStG - Import** area: | The following options are available in **§ 8b KStG - Import**: - **Import**: imports the data from the file currently loaded under **File path**. - **Import template**: loads the template to the local hard drive. - **Delete existing § 8b KStG imports**: Activate this check box if existing imports are to be deleted when new data are imported. - **File path**: Click **Select File** to load the file from which data are to be imported. the 8b kstg import icon '§ 8b KStG - Import' workspace |
| Dialogue §8b KStG | Generates the current data into an Excel file. |
---
---
title: "Administrating Master Data"
description: "Under Master Data, you can create, import, and manage globally valid data for Tax Balance."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance
language: en
last_updated: 2026-05-28
---
# Administrating Master Data
## Overview
Under **Master Data**, you can create, import, and manage globally valid data for Tax Balance.
This includes:
- Creating [companies](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-company.md) for which you can prepare tax balance sheets and transmit them to the tax office
- Creating [tax balance sheets](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-tax-balance-sheet.md) and assigning them to the companies for which the tax balance sheets are to be used
- Creating [adjustment levels](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-adjustment-level.md) to assign tax deviations for different levels of knowledge (such as tax return, annual financial statements, tax audit)
- Configuring [interfaces](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-interface.md) for the data import
- Importing [GCD master data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/import-master-data-from-income-taxes.md) from the **Income Taxes** module
- Performing [mass imports](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/execute-mass-import.md) for several years and/or companies
- Adding [re](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-transformations.md) [organizations](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-transformations.md)
- Transferring [balance sheet structures](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/import-balance-sheet-structure.md) to transfer tax adjustments to Income Taxes, if necessary.
- [Importing E-Balance data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/import-e-bilanz-from-other-systems.md) from other systems, like Lucanet.E-Bilanz or Smart Tax Balance
---
---
title: "Administration"
description: "In the Administration workspace, you can view and maintain basic system settings of Income Taxes."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/administration
language: en
last_updated: 2026-05-28
---
# Administration
## Overview
In the **Administration** workspace, you can view and maintain basic system settings of Income Taxes.
> **Warning:** The settings in the **Administration** workspace are generally defined once by Lucanet as part of the product’s implementation. If changes are necessary, we recommend either having them executed directly by Lucanet, or consulting with Lucanet first.
## Navigation
The **Administration** workspace can be found under **Master Data | Administration**.
The **Administration** workspace is displayed as follows, for example:
Master data workspace 'Administration'
## Options in the 'Administration' Workspace
The following options are available in the **Administration** workspace:
| Option | Description |
|---------|---------|
| Activation | Opens an area in which Income Taxes can be activated or deactivated: |
| Log-Level change | Opens an area where you can adjust the log levels of individual loggers. For example, it is possible to set individual loggers to the DEBUG level in order to obtain more information in the event of a problem. |
| Stop all reports | Cancels all ongoing reports in Report Engine. |
| Web service | Opens an overview with all supported SOAP web service interfaces. |
## 'System Settings' Tab
On the **System settings** tab, you can view the current **system settings** and specify **file types** that are allowed and not allowed.
## 'Server' Tab
On the **Server** tab, the server's **configuration files** are displayed. The configuration files can also be downloaded.
## 'Connection Parameters' Tab
On the **Connection parameters** tab, you can specify the parameters for interfaces to external systems. The following interfaces are available:
| Category | Description |
|---------|---------|
| SAP RFC (flexible) | Here, data from an SAP system can be imported using a flexible RFC module. The structure is variable. |
| REST service | This connection parameter integrates external systems via REST interfaces. This includes, for example, the transmission of data to tax authorities as well as imports into Income Taxes. |
| REST keystore | Encrypted data transmissions of REST services (interfaces over TLS or with client authentication) are configured here. Both the truststore and the keystore are configured in this way. |
## 'Miscellaneous' Tab
On the **Miscellaneous** tab, language-specific revaluation surpluses, **LCF (Losses carried forward)**, and **reporting dimensions** can be created. In addition, elements that have already been created are displayed with their respective IDs.
## 'Administration Hint' Tab
On the **Administration hint** tab, you can specify the text to be displayed on the **starting page (Home)** of Income Taxes.
## 'Third-Party Software' Tab
On the **Third-party software** tab, it is possible to download the third-party JavaScript software used.
---
---
title: "All Steps at a Glance"
description: "In this chapter, you will find the individual steps for creating and sending your VAT returns in VAT, each with links to detailed descriptions."
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/all-steps-at-a-glance
language: en
last_updated: 2026-09-30
---
# All Steps in Lucanet VAT at a Glance
## Overview of All Steps in VAT
In this chapter, you will find the individual steps for creating and sending your VAT returns in Lucanet VAT (Value Added Tax). Each step description contains links to detailed descriptions.
You usually perform the first two steps once at the start of the project; if something changes later, for example in the company structure, you adjust the configuration. You repeat the remaining steps in every reporting period. Not every step applies to every company: which steps VAT displays depends on the company type, the kind of period, and the configuration.
### Step 1: Configure the Settings in VAT
At the start of the project, configure the technical basis of VAT. You access the settings via the gear icon in the top right corner. The settings in VAT include:
- the **Interface configuration** for importing the ERP reports, for example via the REST interface or a network drive
- the **Connection parameter** for connecting the ERP systems and for electronic transmission
- the **Countries** settings, for example for the review steps and the **Paid** status
- the **users and roles**
### Step 2: Maintain the Master Data in VAT
In the **Master data** functional area in VAT, store all VAT-relevant data of the companies. This includes the periods, the companies with their due dates, the company codes, and the tax codes with their mapping to the fields of the declaration form. You also specify which reconciliations are performed for the companies.
The master data is usually entered at the start of the project and can be adjusted for specific periods if something changes.
### Step 3: Create and Send the Preliminary VAT Return in VAT
Create, review, and send the preliminary VAT returns of your companies in the [Value Added Tax](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax.md) functional area. The reporting process for the preliminary VAT return in VAT comprises the following steps:
- **Import data**: for a single company in the [Import](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/import-single-company.md) workspace, or for several companies at once in the [Mass Data Import](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/import-multiple-companies.md) workspace. Not applicable if the declaration is created manually and in special prepayment periods.
- **Review and edit the declaration**: in the [Declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/declaration-edit-finalise.md) workspace – manual adjustments and offsetting entries are optional.
- **Perform reconciliations**: in the [Reconciliations](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/performing-reconciliations.md) workspace, if reconciliations are configured for the company.
- **Finalize the declaration**: in the [Declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/declaration-edit-finalise.md) workspace.
- **Review and finalize the VAT group return**: in the [VAT Group Return](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/vat-group-return.md) workspace – only for representative VAT group members and consolidated VAT group members.
- **Perform the review before transfer**: if activated in the country settings. For more information, see the [Month Overview](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/monthly-overview.md) page.
- **Send the declaration**: in the [Send declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/send-declaration.md) workspace – only for standalone companies and representative VAT group members.
- **Perform the review after transmission** and **document the payment**: if activated in the country settings.
You can track the current processing status of all steps at any time in the [Status](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/tax-sales-status.md) workspace.
### Step 4: Create and Send the European Sales List in VAT
Create and send the European Sales List (ESL) for your intra-Community transactions in the [European Sales List](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list.md) functional area in VAT. The reporting process corresponds to that of the preliminary VAT return: you import the ESL data in the [Import](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/import-data-summary.md) workspace, make manual adjustments in the [Declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/create-declaration-report.md) workspace if necessary, perform the [reconciliations](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/reconciliation-report.md), finalize the declaration, and transmit it in the [Send declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/send-declaration-report.md) workspace to the German Federal Central Tax Office (Bundeszentralamt für Steuern).
The functional area is only visible if the **Submits ESL** check box is activated in the master data of the company, and it is only available in preliminary return periods. If possible, finalize the ESL before you perform the reconciliations of the preliminary VAT return – the reconciliation with the ESL compares the values of both declarations.
### Step 5: Optional: Use Overviews and Create Corrections in VAT
The following workspaces of the **Value Added Tax** functional area in VAT are not assigned to a fixed process step. You use them in parallel to the reporting process as required. The [Month Overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/monthly-overview-report.md) and the [Year Overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/yearly-overview-report.md) of the **European Sales List** functional area work in the same way:
| Workspace | When you use it |
|---------|---------|
| [Status](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/tax-sales-status.md) | Track the processing status of all steps of the chosen company at any time, including logs and file attachments. |
| [Month overview](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/monthly-overview.md) | Check the reporting progress of all companies in a period, for example before a due date. Here you can also open or finalize several declarations at once. |
| [Year overview](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/yearly-overview.md) | Check the reporting progress of all companies over the entire calendar year. |
| [Declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/declaration-edit-finalise.md) and [Month overview](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/monthly-overview.md) | Create a correction after transmission if you need to correct the declaration. In the month overview and the year overview, you create a correction by clicking the **Sent** status. |
| [Comparison view of corrections](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/comparison-corrections.md) | After creating a correction, compare the original declaration with the correction versions. |
| [Reports](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/create-download-reports.md) | Create Excel reports for analyzing the VAT data, for example after finalizing the declaration. |
---
---
title: "Angaben für MU (Information for Partners)"
description: "Relevant information is displayed in the Angaben für MU (Information for Partners) workspace for the following attachments: - AESt attachment - SPIF attachment - SPIFA attachment"
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/information-for-mu
language: en
last_updated: 2026-05-28
---
# Angaben für MU (Information for Shareholders)
## Overview
The **Angaben für MU** (Information for Shareholders) workspace displays data taken from the **(Spezial-) Investmenterträge**((Special) Investment Income) workspace and makes these data available for further editing. Specifically, you can use the **Angaben für MU** (Information for Shareholders) workspace to edit data (where relevant) for:
- Anlage AESt
- Anlage SPIF
- Anlage SPIFA
> **Note:** The **Angaben für MU** (Information for Shareholders) workspace is available only to **partnership companies**.
## Navigation
You can access the workspace **Angaben für MU** under **Company | Current Taxes | Angaben für MU**.
The **Anlage SPIF** form is displayed, for example, as follows:
'Anlage SPIFA' form
## Functions
You can view the distribution of the entered data across the shareholders (co-entrepreneurs) in total and for each country or (special) investment fund in the **AESt attachment** and **SPIF attachment**.
You can transfer data from subordinate companies from the SPIF and/or SPIFA attachment with the **Take over issues** button in the **SPIFA attachment**.
---
---
title: "Anlage Bekanntgabe (Notification Attachment)"
description: "Consent to the electronic notification of trade tax assessment notices by the municipalities entitled to levy the tax is given in the Anlage Bekanntgabe workspace."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/add-announcement
language: en
last_updated: 2026-05-28
---
# Anlage Bekanntgabe (Notification Attachment)
## Overview
The **Anlage Bekanntgabe (Notification attachment)** can be used to consent to the digital delivery of the trade tax assessment notice by the municipalities entitled to levy the tax. In the federal states that levy trade tax themselves (Berlin, Bremen, and Hamburg), the respective tax office is responsible for the tax assessment notice. No consent to the digital delivery of the trade tax assessment notice via the **Anlage Bekanntgabe** is therefore required in these cases.
If consent is given to receive the digital trade tax assessment notice, the tax authorities will transmit the company data obtained with the **Anlage Bekanntgabe** to the municipalities. The municipalities use this information to issue the trade tax assessment notice digitally.
> **Note:** You should use the **Anlage Bekanntgabe** only if your company meets the technical requirements to receive tax assessment notices electronically. A prerequisite is that a business account has been set up by the enterprise. Detailed information on the digital trade tax assessment notice and the business account can be found, for example, on the web site of the Hessian Ministry of Finance at [https://www.digitaler-gewerbesteuerbescheid.de/unternehmen](https://www.digitaler-gewerbesteuerbescheid.de/unternehmen).
## Navigation
The **Anlage Bekanntgabe** form is available in two workspaces under **Company | Current Taxes**:
- **Decomposition** workspace: The form is automatically activated here and cannot be deactivated. However, the **Bekanntgabe attachment** will be transmitted electronically to the tax office only if the form contains data.
- **Local tax** workspace: If **Anlage Bekanntgabe** is activated in the form configuration, the Bekanntgabe attachment is visible in the **Local tax** workspace and data can be entered.
The **Anlage Bekanntgabe** workspace is displayed, for example, as follows:
workspace")'Anlage Bekanntgabe' (Notification attachment) workspace
## Activating 'Anlage Bekanntgabe' in the 'Local tax' Workspace
To activate the **Anlage Bekanntgabe** form in the **Local tax** workspace:
1. Go to **Company | Basic data** in the overview.
2. Click **Form configuration**.
3. Activate the check box **Anlage Bekanntgabe - Einwilligung in die elektronische Bekanntgabe des Gewerbesteuerbescheides durch die hebeberechtigte Gemeinde** (Notification Attachment - Consent to the electronic notification of the trade tax assessment notice by the municipality entitled to levy the tax) on the **Local tax** tab.
Activating 'Anlage Bekanntgabe' in the 'Local tax' Workspace
## Options
The following options are available in the **Anlage Bekanntgabe** workspace:
| Option | Description |
|---------|---------|
| Save | Saves your entries. |
| Comments | Opens a dialog where you can create a new comment or transfer an existing comment. |
---
---
title: "API Tokens"
description: "In the API-Tokens area of your profile, you generate and manage API tokens that external systems use to authenticate their requests to the Tax Data Hub, for example when importing data via an interface."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-administration/api-tokens
language: en
last_updated: 2026-06-24
---
# API Tokens
## Overview
In the **API-Tokens** area of your profile, you generate and manage API tokens. An external system uses an API token to authenticate its requests to the **Tax Data Hub**, for example when importing data via an interface.
> **Note:** The **My Profile** page is provided by **Tax Administration** for all **Tax Compliance & Reporting** modules. You can use the same token for several interfaces.
## Generate an API token
1. Open the **Tax Administration** module.
2. Navigate to **My Profile**:
Profile menu with the 'My profile' entry
3. Go to the **API-Tokens** area and proceed as described in the [Configuring the 'API-Tokens' area](#configuring-the-apitokens-area) section.
4. Click **Save**. The **Validity** column indicates whether the token is valid.
5. In the **Copy API token** column, click the **copy symbol** to copy the token to the clipboard.
### Configuring the 'API-Tokens' area
In the **API-Tokens** area, click the **plus symbol** on the right to add a new row, and fill in the displayed input fields:
The 'API-Tokens' area with the input fields
| Field | Description |
|---|---|
| **Name** | A short name for the token |
| **Description** | Optional description text. Can be left empty. |
| **Expiration date** | Optional expiry date. If the field is left empty, the token is valid indefinitely. |
> **Warning:** - Keep the token secure and do not share it with others.
> - If you do not set an expiration date, the token remains valid indefinitely.
> - You can create several tokens for different external systems.
---
---
title: "Aufteilungsquoten (Allocation Quotas)"
description: "How tax bases are allocated is shown in the Aufteilungsquoten (Allocation Quotas) workspace. The Allocation Quotas workspace is relevant whenever investment relationships change during the year, e. g. when a shareholder changes. Entries on the allocation quotas in Anlage FB are required for this purpose."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/allocation-quotas
language: en
last_updated: 2026-05-28
---
# Aufteilungsquoten (Allocation Quotas)
## Overview
How tax bases are allocated is shown in the **Aufteilungsquoten (Allocation Quotas)** workspace. The **Allocation Quotas** workspace is relevant whenever investment relationships change during the year, e. g. when a shareholder changes. Entries on the allocation quotas in **Anlage FB** are required for this purpose.
The chosen allocation quota is used in other workspaces and forms, e. g. in the [Revenue](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/income.md) workspace, transfer workspaces, and assessment forms.
## Technical Background
When investment relationships change during the year, the quotas can be calculated for the following types of time-apportioned tax base allocations:
- Keine zeitanteilige Aufteilung (No time-apportioned allocation)
- Halbjährliche Aufteilung (Semi-annual allocation)
- Vierteljährliche Aufteilung (Quarterly allocation)
- Zweimonatliche Aufteilung (Two-monthly allocation)
- Monatliche Aufteilung (Monthly allocation)
- Tagesgenaue Aufteilung (Monate mit 30 Tagen) (Allocation by day (months with 30 days))
- Tagesgenaue Aufteilung (Monate mit tatsächlichen Tagen) (Allocation by day (months with actual days))
## Navigation
The **Aufteilungsquoten** (Allocation Quotas) workspace is opened under **Company | Basic data | Aufteilungsquoten**. The **Aufteilungsquoten** (Allocation Quotas) workspace is displayed as follows, for example:
'") Workspace 'Aufteilungsquoten (Allocation Quotas)'
> **Note:** The **Aufteilungsquoten** workspace is only available for **partnership companies**.
Allocation quotas are determined based on the entries made in **Anlage FB**. The time-apportionment allocation entries on the **main form ESt 1 B** **(Hauptvordruck ESt 1 B)** are not taken into account.
If no time-apportioned allocation is chosen, the allocation will be based on the quotas from the master data.
With the allocation types **no time-based allocation** to **monthly allocation**, the allocation quotas are calculated based on the ownership interests at the end of each time period, regardless of the actual date of entry or exit. With **allocation by day** (months with 30 days), the date entry on the 31st day of a month is treated as the 30th day of the same month.
## Changing an Allocation Quota
To change the allocation quotas:
1. Activate the desired option (e.g. **Vierteljährliche Aufteilung (quarterly allocation)**).
2. Click **Calculate quotas** to update the allocation quotas.
---
---
title: "Ausländische Zwischengesellschaften (Foreign Intermediate Companies)"
description: "The ‘Ausländische Zwischengesellschaften (Foreign Intermediate Companies)’ workspace contains the investments in foreign intermediate companies in accordance with section 7 of the Foreign Tax Act."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/international-intermediate-companies
language: en
last_updated: 2026-05-28
---
# Ausländische Zwischengesellschaften (Foreign Intermediate Companies)
## Overview
Investments in foreign intermediate companies in accordance with **section 7 of the Foreign Tax Act (AStG)** are entered in the **Ausländische Zwischengesellschaften** workspace. The entered data are included in the workspace **Company | Current Taxes | Corporate Income Tax** for further processing, where they are provided on the **Anlage ZwiG** (ZwiG Attachment) form.
## Navigation
You can access the **Ausländische Zwischengesellschaften** workspace under **Company | Basic data | Ausländische Zwischengesellschaften**. The **Ausländische Zwischengesellschaften** workspace is displayed as follows, for example:
workspace")'Ausländische Zwischengesellschaften' (Foreign Intermediate Companies) workspace
## Columns in the 'Ausländische Zwischengesellschaften' workspace
The following columns are displayed in the **Ausländische Zwischengesellschaften** workspace:
| Column | Description |
|---------|---------|
| Sachverhalts-ID (Issue ID) | Unique identification number of the issue for internal administration and referencing |
| Bezeichnung der Zwischengesellschaft (Name of intermediate company) | Name of the foreign intermediate company in which an investment is held |
| Steuernummer der Zwischengesellschaft (Tax number of intermediate company) | Tax identification number of the foreign intermediate company in the respective country |
| Beschreibung des Sachverhaltes (Description of issue) | Free text description of the controlled foreign company taxation issue for better identification and documentation |
## Creating an Intermediate Company
To create new foreign intermediate companies:
1. Click **Create**. The following area is displayed:
Creating an issue for investments in foreign intermediate companies
2. Enter the **Issue ID**, the master data of the intermediate company ( **name** and **tax number**), and the **issue**.
3. Click **Update tax calculation** in the **Ausländische Zwischengesellschaften** workspace.
> **Warning:** Please note:
>
> - The **Update tax calculation** button takes effect only if the **Anlage ZwiG** form is activated under **Basic data | Form configuration**.
> - Additional information on tax bases from foreign intermediate companies can be entered only if you activate the **Anlage ZwiG** form on the **Corporate Income Tax** tab under **Company | Basis data | Form configuration**.
> - If the **ZwiG** attachment is activated after creating the foreign intermediate company, the tax must be calculated again with the **Update tax calculation** button.
---
---
title: "B/S Comparison"
description: "Besides the \"Loss carried forward\" workspace, the \"B/S Comparison\" workspace is the central workspace for determining deferred taxes."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison
language: en
last_updated: 2026-05-28
---
# B/S Comparison
## Overview
Besides the **Loss carried forward** workspace, the **B/S Comparison** workspace is the central workspace for determining deferred taxes.
The B/S Comparison consists of several tabs. The structure of the balance sheet corresponds to the structure stored in the master data for the selected period. The structure of the tabs in the B/S Comparison is identical.
## Navigation
The **B/S Comparison** folder is displayed under **Company | Deferred Taxes | B/S Comparison**. The **Local GAAP - Tax Balance** workspace is displayed as follows, for example:
B/S Comparison, Local GAAP - Tax Balance
## Workspaces in the 'B/S Comparison' Workspace
The following workspaces are available in the **B/S Comparison** folder:
- [Local GAAP - Tax Balance](#hgb-stb)
- [IFRS - Local GAAP](#ifrs-hgb)
- [Total: IFRS - Tax Balance](#totalifrsstb)
- [Other Deferred Taxes](#otherdeftaxes)
For companies configured as partnerships in the master data and assigned to the German tax law, the [Supplementary tax balance sheet](#supbalsheet) workspace is additionally displayed.
For companies not assigned to German tax law in the master data (foreign companies), the [Additional tax](#addtax) workspace can be additionally activated in the [Companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) master data workspace.
The workspaces are described in detail in the following sections:
### 'Local GAAP - Tax Balance' Workspace
The **Local GAAP - Tax Balance** workspace is displayed as follows, for example:
B/S Comparison, Local GAAP - Tax Balance
The following columns are displayed in the **Local GAAP - Tax Balance** workspace:
- **Local GAAP**: representation of the local balance sheet (for German companies: balance sheet in accordance with commercial law).
- **Tax balance (EUR)**:shows the result from the **Local balance** and **Correction to tax balance sheet** columns. Tax balance values always result from the two preceding columns and cannot be entered directly.
- **Correction to tax balance sheet**: contains, in the case of German companies, the deviations in accordance with **Section 60 (2) EStDV**.
- **Import**: shows the balance sheet values imported via the interface – these values cannot be edited.
- **Manually**: column for manual entries by the user. This allows, for example, reclassifications or adjustments to the imported values.
> **Note:** The use of the **Manually** column must be activated in the master data in the [Company](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) workspace for each company.
>
> This setting is activated by default and the balance sheet comparison can be edited manually.
- **Total**:Calculates the totals of the previous columns, which are relevant for determining the balance sheet differences ( **Relevant gross difference** column).
- **Relevant gross difference**: The **Relevant gross difference** column is calculated automatically and shows the differences between the local balance (or local balance sheet) and the tax balance. These differences must be assigned to the corresponding **Thereof** columns in the next step and serve as the basis for calculating the deferred taxes.
### 'IFRS - Local GAAP' Workspace
In the **IFRS - Local GAAP** workspace, the IFRS balance is compared with the local GAAP \[or local balance sheet\]. The **IFRS - Local GAAP** workspace is displayed as follows, for example:
IFRS - Local GAAP
The following columns are displayed in the **IFRS - Local GAAP** workspace:
- **Local GAAP**: Taken from the **Local GAAP - Tax Balance** workspace.
- **IFRS**: The IFRS balance sheet is represented here.
- **Import**: Shows the balance sheet values imported via the interface – These values cannot be edited.
- **Manually**: column for manual entries by the user. This allows, for example, reclassifications or adjustments to the imported values.
> **Note:** The use of the **Manually** column must be activated in the **Company** master data dialog for each company.
>
> This setting is activated by default and the balance sheet comparison can be edited manually.
- **Total**: Calculates the totals of the previous columns, which are relevant for determining the balance sheet differences ( **Relevant gross difference** column).
- **Relevant gross difference**: The **Relevant gross difference** column is calculated automatically and shows the differences between the Local GAAP (or local balance sheet) and the tax balance. These differences must be assigned to the corresponding **Thereof** columns in the next step and serve as the basis for calculating the deferred taxes.
### 'Supplementary Tax Balance Sheet’ Workspace
The **Supplementary tax balance sheet** workspace is displayed only in the B/S Comparison for German partnership companies. The entries are optional and apply to partner-specific corrections of the tax balance sheet values of assets or liabilities of the partnership company.
Complementary tax balance sheet
The supplementary tax balance sheet is maintained for each partner or shareholder. The shareholders are managed in the master data under **Company** and displayed in the selection list.
You can enter the tax balance sheet value corrections in the **Supplementary tax balance sheet** column. The **Gross difference, Supplementary tax balance sheet** column is calculated automatically.
These differences must be assigned to the corresponding **Thereof** columns in the next step and serve as the basis for calculating the deferred taxes.
Only temporary and permanent P/L effects are available for the **Thereof** columns. An allocation to **OCI** is not possible.
### 'Additional Tax' Workspace
The **Additional Tax** workspace is available only for companies to which German tax law does not apply. The display of the workspace also depends on whether the display is activated in the **Additional Tax** field in the company master data.
The purpose of the **Additional Tax** workspace is to take into account deviating assessment bases for a second type of income tax.
B/S Comparision - 'Additional Tax'
The **Correction to tax balance sheet II** column can be edited by the user. All other balance sheet columns are linked to the corresponding workspaces (e. g. the IFRS balance sheet to the **IFRS - Local GAAP** workspace).
Using the workspace also requires that columns are created for the purpose of dividing the differences by means of the **Maintain columns** function. The balance sheet differences are determined between the **Correction to tax balance sheet II** and **IFRS balance** columns.
> **Note:** Using the **Additional Tax** workspace must be activated in the [Company](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) master data workspace for each company.
>
> You can select **Additional Tax** under **Application parameter - Tax calculation**. The following options are available here:
>
> - No additional Tax (default)
> - Based on Tax base
> - Based on Local GAAP
### 'Total' Workspace
The **Total** workspace provides an overall view of all assets and liabilities across the IFRS balance sheet, Local GAAP, and tax balance. The balance sheets are taken from the individual workspaces and cannot be edited here. The **Relevant gross difference** column is based on the comparison between the IFRS balance and the tax balance ( **tax balance value** minus **IFRS balance** value).
'Total' workspace
The values in the **Total** workspace are linked to the following workspaces:
- Local GAAP - Tax Balance
- IFRS - Local GAAP
The following workspaces of the balance sheet comparison are not included in **Total**. However, they are used for the calculation of deferred taxes and displayed in the [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md) workspace:
- Supplementary tax balance sheet
- Additional tax
- Other Deferred Taxes
### 'Other Deferred Taxes’ Workspace
The **Other Deferred Taxes** workspace allows deferred taxes to be entered directly for each balance position (e. g. adjustments from audit issues) and is displayed, for example, as follows:
B/S Comparison - Other Deferred Taxes
The **Other Deferred Taxes** workspace works without balance sheet differences.
The deferred taxes to be entered can be entered either in the **affecting P&L** or **affecting OCI** column. The classification of deferred taxes with regard to maturity is based on the settings in the [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md) master data workspace _._
## Options in the B/S Comparison Workspaces
The following table describes the functions in the B/S Comparison workspaces. Note that some functions are not available in all workspaces.
#### Save
All inputs must be saved after entry. This applies also if the values are only imported and no manual adjustments are made.
#### Import
Opens the workspace for importing values into the balance sheet comparison and, if necessary, into the detailed tax workspaces.
#### Comments
Comments can be added here to specific balance sheet positions, and Excel files uploaded and their values imported.
#### Split differences
The **Split differences** function is available in the **Local GAAP - Tax Balance** and **IFRS - Local GAAP** workspaces.
The **Split differences** function depends on the settings made in the [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md) master data workspace for dividing the calculated balance sheet differences.
Whether any balance sheet differences that occur at the selected balance sheet position are temporary or permanent is predefined for automation in the master data. Furthermore, it must be defined whether the value movement is to be treated through profit or loss (P/L) or through OCI.
The **Split differences** function uses this information for automatic allocation of the balance sheet differences to the **thereof columns**:
- P/L differences (calculation of deferred taxes, through profit or loss)
- OCI differences (calculation of deferred taxes, through OCI)
- Permanent P/L differences (no calculation of deferred taxes, TRR effect)
- Permanent OCI differences (no calculation of deferred taxes)
The **thereof columns** preset based on the master data are displayed with a black border for each balance sheet position. This allows the user to identify the individual target columns before executing the function. Manual adjustment is possible at any time afterwards.
Manual entry or reallocation of the differences is possible at any time. This allows special to be processed first by manual input and then the **Split differences** function used to automatically split the remaining differences.
#### Calculate Local GAAP
The **Calculate Local GAAP** function is available in the **Local GAAP - Tax Balance** workspace.
This function copies the IFRS balance sheet completely into the Local GAAP in the **Local GAAP - Tax Balance** workspace.
#### Reset values
The **Reset values** function is available in all subordinate workspaces of the B/S Comparison folder except in the **Total** workspace.
Allows the contents of selected columns to be reset to the value **zero**.
> **Warning:** **Caution**: It is not possible to restore the reset data.
#### Maintain columns
After clicking **Maintain columns**, the **Tax Rate Maintenance** dialog is displayed.
The **Maintain columns** function is used, among other things, to display national specifics in the calculation of deferred taxes. In some countries, certain balance sheet differences must be assessed with a different tax rate – for example if capital gains from real estate are subject to a special tax rate. **Maintain columns** can be used to specifically take such different tax effects into account.
For more information, see [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md).
#### Expand/collapse balance sheet positions
Balance sheet positions can be expanded and collapsed either selectively (per position) or completely (for the entire balance sheet tree).
#### Export as Excel/Export as PDF
Exports the balance sheet comparison to MS Excel or to a PDF document.
#### the incometaxes zero values icon
Show/hide all cells without values
Hides or shows all rows in the balance sheet structure that do not contain any values and are not total positions. This is helpful for large balance sheet structures if only the balance sheet positions with values are to be displayed.
> **Tip:** **Signs of Balance Sheet Values**
>
> The balance sheet comparison follows SAP logic with regard to signs. Therefore, all assets must be entered with a positive sign. Liabilities are entered with a negative sign.
## Validations in the 'B/S Comparison' workspace
A number of **validations** are implemented in the **B/S Comparison**. Error messages are displayed in the event of any discrepancies. It is not possible to close the **Deferred Taxes** milestone if validation errors exist.
The validation rules are carried out for each workspace, i. e. for all subordinate workspaces in which data can be entered (with exception of the **Total** workspace). The following messages can be displayed:
- **The balance sheet has not been saved.**\
\
The balance sheet is saved, as throughout income taxes, by clicking the **Save** button.
- **The balance sheet is not balanced.**\
\
An unbalanced balance sheet (total of **assets** not equal to total of **liabilities**) leads to an error message. Furthermore, an exclamation mark is displayed in the top row of the balance sheet comparison.
The values in the top row of the balance sheet must equal zero (corresponds to a balanced balance sheet). An exception to this is the **Relevant gross difference** column. Values other than zero can also be displayed here in the top balance sheet row without resulting in a validation error.
- **Allocation of difference incomplete**\
\
Caculated balance sheet differences must be allocated to the various **thereof columns**. The **Allocation of difference incomplete** validation rule checks this requirement. The row with the relevant balance sheet position is highlighted in red in the event of unallocated differences.
## Technical Notes on B/S Comparison
In principle, four scenarios that lead to temporary differences or deferred taxes are conceivable:
Asset side of the balance sheet:
1. **IFRS value > Tax value** \[taxable temporary difference or deferred tax liability\]
2. **IFRS value < Tax value** \[deductible temporary difference or deferred tax asset\]
Liability side of the balance sheet:
1. **IFRS value < Tax value** \[taxable temporary difference or deferred tax liability\]
2. **IFRS value > Tax value** \[deductible temporary difference or deferred tax asset\]
Values on the asset side are entered with a positive sign in Income Taxes. Values on the liability side of the balance sheet have a negative sign. Based on the **Relevant gross difference** column, this results in the following scenarios:
| Balance sheet side | Sign of the 'Relevant gross difference' column |
|---------|---------|
| Assets | \[-\] deferred tax liability \[DTL\] |
| Assets | \[+\] deferred tax asset \[DTA\] |
| Equity and liabilities | \[-\] deferred tax liability \[DTL\] |
| Equity and liabilities | \[+\] deferred tax asset \[DTA\] |
A positive sign in the **Relevant gross difference** column results in deferred tax assets, a negative sign in deferred tax liabilities.
---
---
title: "Basic Data"
description: "In the \"Basis data\" workspace, corporations can select the assessment rate used (for trade tax purposes) and assign foreign branches. For partnership companies, this workspace also allows you to manage partners."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data
language: en
last_updated: 2026-09-29
---
# Basic Data
## Overview
The assessment rate used (for trade tax purposes) can be selected and foreign branches assigned for corporations in the **Basis data** workspace. For partnership companies, this workspace also allows you to manage partners.
> **Note:** You can activate or deactivate all tax return forms in the **Basis data** workspace (see [Form configuration](#form-configuration) section).
## Navigation
The **Basic data** workspace is opened under **Company | Basic data**.
The **Basis data** workspace is displayed as follows, for example:
'Basic data' workspace
## Tabs in the 'Basic Data' workspace
Various tabs are displayed in the **Basis data** workspace, depending on the selected company and the configured country. They are described in the following section.
The following tabs can be displayed in the **Basis data** workspace:
### Calculation
The following options are available on the **Calculation** tab:
**Copy from**: The basis data can also be copied from another period - provided the company in question was also created as a record in the source period.
Select the desired period from the **Copy from** drop-down list and then click **+** to copy the basic data from the set period.
**Used assessment rate**:
The following options are available:
- From master data ( **Company** master data dialog)
- From apportionment of local tax base ( **GewSt 1D** form dialog)
- Manual input (in the **Basic data** workspace)
**Calculation type**: The **calculation type** relates to the distribution of revenue. The participation deduction information (in %) is used as basis in the case of **allocation by quota**. Alternatively, an **allocation not by quota** can also be selected.
> **Warning:** The **Calculation type** option is only available for partnership companies.
### Form configuration
All tax return forms can be activated or deactivated on the **Form configuration** tab. The tab is displayed as soon as the workflow for processing the tax return (see [Milestones & Status](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/status.md)) has been started. The default settings of the form configuration are based on the legal form, type of tax payer, and tax liability of the company. Based on this information, the forms that typically need to be transmitted to the tax office in this configuration are preselected.
The tax return forms that are to be transmitted electronically on a regular basis for the company's income tax returns are preselected on the basis of this information.
The **Form configuration** tab is displayed for all periods from assessment period 2018 onwards. Exception: The unit is a special investment fund.
### Company data
You can enter all master data of the company, such as the legal form key on the **Company data** tab. The tax rates are displayed among other things. If you want to specify different tax rates, select the **Unit-specific tax rates** check box and then edit the desired input fields.
### ESt 1 B main form
Various settings and master data relating to the assessment return for partnership companies are entered on the **ESt 1 B** tab.
### Additional information ERiC-Transfer
If necessary, enter additional information on the [ERiC transfer](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer.md) here. The information is organized into the following tabs:
- Municiple trade tax
- Corporate income tax
- Local tax decomposition
- CIT decomposition
- KapEStA
- Revenue
### Management address
You can enter the following information on the **Management address** tab:
- Management address
- Mailbox address
- Contact information
- Determination of tax residency (Place of domicile and management in the assessment period)
- Only for property communities: place of administration
- Address of the permanent establishment for the purposes of business tax return
### Tax Consultancy/Participation
Specify who participated in the preparation of the return on the **Tax Consultancy / Participation** tab.
> **Warning:** The information is transmitted only if the **Send contact details of tax consultancy** option is selected under **Additional information ERiC transfer**.
### Bank account
The company's account information can be entered and edited on the **Bank account** tab.
### Registrations
The **Registration** drop-down list is used to specify whether a registration exists or not. If you select **Yes**, you can then specify the additional properties of the registration.
### Legal guardian
You must enter the entrepreneur, legal guardian, or managing director here. This information is relevant only for the purposes of the municiple trade tax return or the local tax segmentation up to and including assessment period 2020.
### Receiving agent
If necessary, enter the details of a common **receiving agent** appointed by all parties involved here.
### Annex FB (Anlage FB)
You can enter and edit information about shareholders of partnership companies on the **Annex FB tab**. Additional information can be entered after creating a partner.
### Shareholding structure
If not all partners have already been entered in the master data under **Company**, they can be subsequently entered in the **Basis data** workspace. Subsequent entries are necessary, for example, for the purposes of the electronic tax return.
> **Tip:** For partnership companies, the parters created in the master data are displayed.
## Sub-workspaces in the 'Basic data' workspace
Up to four sub-workspaces are displayed in the **Basis data** workspace depending on the selected company, its legal form, and the current assessment time of the period:
- [Notifications of tax arrangements](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/Notification-of-tax-arrangements.md)
- [Allocation quotas](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/allocation-quotas.md)
- [Foreign intermediate companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/international-intermediate-companies.md)
- [Foreign branches/Fonds](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data/foreign-businesses-funds.md)
---
---
title: "Business Activities"
description: "In the Business Activities workspace, you can select the main business activities of a CE."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/business-activities-cbcr
language: en
last_updated: 2026-07-28
---
# Business Activities
## Overview
In the **Business Activities** workspace, you can select the main business activities of a CE.
## Navigation
The **Business Activities** workspace can be found under **Country-by-Country-Reporting | Entity Data Collection | Business Activities** and is displayed as follows, for example:
'Business Activities' workspace
## Selecting Business Activities
To report a business activity for the selected CE, activate the check box in the row of the corresponding activity, **CbC-2.1** to **CbC-2.13**.
> **Note:** If you activate the check box **CbC-2.13** for **Other**, you have to describe that activity in line **CbC-2.14**, **Other Entity Information**.
> **Warning:** The text entered in **CbC-2.14** is excluded from **Section 3** of both the EU and Australian public CbC reports. Only the check marks for **CbC-2.1** to **CbC-2.13** appear in the public report.
## Showing IDs
The **Show IDs** button displays the technical identifiers of each business activity, which map the activity to its data interface for imports and troubleshooting.
To show the IDs:
1. At the top of the workspace, click **Show IDs**. Each business activity displays the **Mapping ID** and the **TQ ID** below its name.
'Business Activities' workspace with the IDs displayed
2. To return to the normal view, click **Business Activities** in the menu again.
---
---
title: "C0 – Safe Harbour Check"
description: "The Safe Harbour Check workspace includes the three transitional safe harbour tests:\n- Simplified ETR test \n- De minimis test \n- Routine profits tests"
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c1
language: en
last_updated: 2026-05-01
---
# C0– Safe Harbour Check
## Overview
The **Safe Harbour Check** workspace includes the three transitional safe harbour tests:
- Simplified ETR test
- De minimis test
- Routine profits tests
These tests are followed by information on the applicability of the transitional safe harbour.
For the safe harbour check, entity data is aggregated on a jurisdictional level based on the **reporting dimension type** selected for the **CbCR-Safe Harbour Blending**.
## Navigation
The **C0 – Safe Harbour Check** workspace can be found at **Pillar 2 | Calculation | C0 – Safe Harbour Check**. The workspace is displayed as follows, for example:
'C1 - Safe Harbour Check' workspace
## Performing Safe Harbour Check
Specify the following per section:
### Simplified ETR Test
#### 1.1
**Qualified CbCR Profit (Loss) before Income Tax**
Displays the aggregate of the **CbCR-2** values for the jurisdiction or subgroup.
#### 1.3
Income Tax Expense (including uncertain tax positions)
Displays the aggregate of the **CbCR-3.1** values for the jurisdiction or subgroup.
#### 1.4
Income Tax Expense related to uncertain tax positions
Displays the aggregate of the **CbCR-3.2** values for the jurisdiction or subgroup.
#### 1.5
**Income Tax Expense (after eliminating uncertain tax positions)**
Displays the aggregate income tax expense after eliminating uncertain tax positions, based on the following calculation: {1.3} - {1.4}.
#### 1.6
**Simplified ETR**
Displays the aggregate simplified ETR by dividing the income tax by the qualified CbCR profit or loss before income tax: {1.5} / {1.1} \* 100.
#### 1.7
Transition Rate
Displays the transition rate of 15%.
#### 1.8
Simplified ETR Test successful?
Indicates whether or not the simplified ETR test is successful.
### De Minimis Test
#### 2.1
**Qualified CbCR Revenue**
Displays the aggregate of the **CbCR-1** values for the jurisdiction or subgroup.
#### 2.3
**Average GloBE Revenue threshold**
Displays the GloBE revenue threshold (€ 10,000,000).
#### 2.4
**Qualified CbCR Profit (Loss) before Income Tax**
Displays the aggregate of the **CbCR-2** values for the jurisdiction or subgroup.
#### 2.6
**Average GloBE Income threshold**
Displays the fixed GloBE income threshold (€ 1,000,000).
#### 2.7
**De Minimis Test successful?**
Indicates if the de minimis test is successful.
### Routine Profits Test
#### 3.1
**Qualified CbCR Profit (Loss) before Income Tax**
Displays the aggregate of the **CbCR-2** values for the jurisdiction or subgroup.
#### 3.2
**Relevant Eligible Payroll Costs of Eligible Employees performing activities in the jurisdiction**
Displays the aggregate of the **CO-1.1** values for the jurisdiction or subgroup.
#### 3.A1
**Allocations of Eligible Payroll Costs in case of Permanent Establishments or Flow-Through Entities**
Displays the payroll cost allocations applicable to permanent establishments or flow-through entities in the jurisdiction.
#### 3.3
**Application of relevant mark-up percentage for the Reporting Fiscal Year**
Displays the relevant mark-up percentage for the reporting year, e.g. 9.8% for 2024.
#### 3.4
**Payroll Carve-Out Amount**
Displays the aggregate amount of eligible payroll costs for the jurisdiction or subgroup multiplied by the relevant mark-up percentage.
#### 3.5a
**Value of relevant Eligible Tangible Assets located in the jurisdiction at the beginning of the reporting year**
Displays the aggregate of the **CO-2.1** values for the jurisdiction or subgroup.
#### 3.5b
**Value of relevant Eligible Tangible Assets located in the jurisdiction at the end of the reporting year**
Displays the aggregate of the **CO-2.2** values for the jurisdiction or subgroup.
#### 3.A2
**Allocations of Eligible Tangible Assets in case of Permanent Establishments or Flow-Through Entities**
Displays the tangible asset allocations applicable to permanent establishments or flow-through entities in the jurisdiction.
#### 3.5
**Carrying value of relevant Eligible Tangible Assets located in the jurisdiction**
Displays the arithmetic mean of the values in lines 3.5 and 3.5b above.
#### 3.6
**Application of relevant mark-up percentage for the Reporting Fiscal Year**
Displays the relevant mark-up percentage for the reporting year, e.g. 7.8% for 2024.
#### 3.7
**Tangible Assets Carve-Out Amount**
Displays the carrying value of relevant eligible tangible assets multiplied by the relevant mark-up percentage.
#### 3.8
**Total amount of the Substance-Based Income Exclusion**
Displays the sum of the payroll carve-out amount and the tangible assets carve-out amount.
#### 3.9
**Routine Profits Test successful?**
Indicates whether or not the routine profits test is successful.
### Applicability
| Option | Description |
|---------|---------|
| 4 | **Is the Transitional CbCR safe harbour generally available for the Reporting Fiscal Year?** |
| 5 | **Was the election to use the Transitional CbCR safe harbour exercised in the previous Reporting Fiscal Year?** |
| 6 | **Which Safe Harbour Election is exercised for the jurisdiction or joint venture group?** |
| 7 | **Is the elected Safe Harbour successful?** |
| 8 | **Result: Will the Transitional CbCR safe harbour be applied for the Reporting Fiscal Year?** |
---
---
title: "C1 – NMCE Safe Harbour"
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c1-nmce-safe-harbour
language: en
last_updated: 2026-05-01
---
# C1 – NMCE Safe Harbour
## Overview
The **NMCE Safe Harbour** workspace provides a simplified compliance option for **Non-Material Constituent Entities (NMCEs)**. This safe harbour allows qualifying constituent entities (CEs) to be excluded from the full-scope Pillar 2 calculations ( **C2 – CE Calculations**, **C4 – Jurisdictional Blending**, and **C5 – Top-up Tax Allocation**) while still being included in the initial safe harbour assessments.
The **NMCE Safe Harbour** includes three alternative tests that CEs can use to demonstrate they meet materiality thresholds:
- Simplified ETR Test
- De Minimis Test
- Routine Profits Test
If at least one of these tests is successful, the CE may elect to use the NMCE Safe Harbour through the **Entity Election EE-1** in the **Entity Election and General Information** workspace.
> **Note:** **Notes**:
>
> - Only CEs that have been marked as **non-material** in the master data can use the NMCE Safe Harbour. You can verify this setting by navigating to **Master Data | Companies** and selecting your CE to access the detail view. On the **International Tax** tab, check whether **AMAE50** is activated.
> - **Stateless CEs** are **not eligible** for the NMCE Safe Harbour and are excluded from these calculations. You can verify this setting by navigating to **Master Data | Companies** and selecting your CE to access the detail view. On the **International Tax** tab, check whether **AMAE52** is activated.
> - For the NMCE Safe Harbour, CE data is aggregated on a jurisdictional level based on the **reporting dimension type** selected for blending.
## Navigation
The **C1 – NMCE Safe Harbour** workspace can be found at **Pillar 2 | Calculation | C1 – NMCE Safe Harbour** and is displayed as follows:
C1 - NMCE Safe Harbour workspace
To access this workspace and display the desired values:
1. Select a snapshot in the **Home** workspace.
2. Navigate to **C1 – NMCE Safe Harbour**.
3. Select the jurisdiction or subgroup you want to review from the **Jurisdiction** drop-down list.
## Performing the NMCE Safe Harbour Check
The NMCE Safe Harbour check aggregates data from all constituent entities within a jurisdiction that are marked as **non-material** and are **not stateless entities** (see also _Overview_).
NMCE Safe Harbour displays the results of three tests. If any of the tests is successful, the NMCE Safe Harbour is **available** for that jurisdiction or subgroup.
### Simplified ETR Test
The **Simplified ETR Test** compares the effective tax rate against the minimum rate of 15%.
| Option | Description |
|---------|---------|
| NM-1.1 Qualified CbCR Revenue | Displays the aggregate of qualified CbCR revenue for all non-material entities in the jurisdiction or subgroup. This value is based on **CbCR-1** from the **CbCR Safe Harbour** workspace in the **Entity Data Collection**. |
| NM-1.2 Income Tax Expense accrued | Displays the aggregate of income tax expense accrued for all non-material entities in the jurisdiction or subgroup. This value is based on **CbCR-4** from the **CbCR Safe Harbour** workspace (see [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md)). |
| NM-1.3 Simplified ETR | Displays the simplified effective tax rate calculated as: {NM-1.2} / {NM-1.1} × 100. |
| NM-1.4 Transition Rate | Displays the minimum transition rate of 15%. |
| NM-1.5 Simplified ETR Test successful? | Indicates whether the Simplified ETR Test is successful. The test is successful if the **Simplified ETR**(NM-1.3) is equal to or greater than the **Transition Rate**(NM-1.4). |
### De Minimis Test
The **De Minimis Test** verifies whether GloBE Revenue stays below specified thresholds across multiple fiscal years.
#### NM-2.1 GloBE Revenue - Reporting Fiscal Year
Displays the **aggregate GloBE Revenue** for the reporting fiscal year for all non-material entities in the jurisdiction or subgroup.
#### NM-2.2 GloBE Revenue - 1st preceding Fiscal Year (if applicable)
Displays the **GloBE Revenue from the first preceding fiscal year**, if available. This value is retrieved from the prior period snapshot.
#### NM-2.3 GloBE Revenue - 2nd preceding Fiscal Year (if applicable)
Displays the **GloBE Revenue from the second preceding fiscal year**, if available. This value is retrieved from snapshots from two periods prior.
#### NM-2.4 FY not available
Indicates **which fiscal years are not available** for the calculation (e.g., if this is the first or second year of reporting, prior fiscal year data may not exist).
#### NM-2.5 GloBE Revenue - Average of the available Fiscal Years
Displays the **average GloBE Revenue calculated across all available fiscal years**. The calculation considers only the fiscal years for which data is available.
#### NM-2.6 Average GloBE Revenue threshold
Displays the **threshold for average GloBE Revenue**. The standard threshold is € 10,000,000.
#### NM-2.7 De Minimis Test successful?
Indicates whether the De Minimis Test is successful. The test is successful if the average GloBE Revenue (NM-2.5) is below the threshold (NM-2.6) and the average GloBE Income is below € 1,000,000.
A checkbox is displayed if the test is successful.
### Routine Profits Test
The **Routine Profits Test** calculates the **Substance-Based Income Exclusion** by evaluating payroll costs and tangible assets, applying the relevant carve-out percentages.
#### NM-3.1 Qualified CbCR Revenue
Displays the **aggregate of qualified CbCR revenue for all non-material entities** in the jurisdiction or subgroup. This value is based on **CbCR-1** from the **CbCR Safe Harbour** workspace in the **OECD-Standard** folder.
#### NM-3.2 Relevant Eligible Payroll Costs of Eligible Employees performing activities in the jurisdiction
Displays the **aggregate of eligible payroll costs for employees** performing activities in the jurisdiction for all non-material entities. This value is based on **CO-1.1** from the **Substance-based Income Exclusion** workspace in the **OECD-Standard** folder.
#### NM-3.3 Allocations of Eligible Payroll Costs in case of Permanent Establishments or Flow-Through Entities
Displays the **aggregate of payroll cost allocations for permanent establishments or flow-through entities** for all non-material entities. These allocations are made in the **FTE & PE Allocations** workspace.
#### NM-3.4 Application of relevant mark-up percentage for the Reporting Fiscal Year
Displays the relevant **mark-up percentage for payroll costs for the reporting fiscal year**.
#### NM-3.5 Payroll Carve-Out Amount
Displays the **payroll carve-out amount** calculated by multiplying the sum of eligible payroll costs and allocations by the relevant mark-up percentage: ({NM-3.2} + {NM-3.3}) × {NM-3.4}.
#### NM-3.6 Value of relevant Eligible Tangible Assets located in the jurisdiction at the beginning of the reporting year
Displays the **aggregate value of eligible tangible assets at the beginning of the reporting year** for all non-material entities. This value is based on **CO-2.1** from the **Substance-based Income Exclusion** workspace in the **OECD-Standard** folder.
> **Note:** **Note**: This value uses the exchange rates from the prior period.
#### NM-3.7 Value of relevant Eligible Tangible Assets located in the jurisdiction at the end of the reporting year
Displays the **aggregate value of eligible tangible assets at the end of the reporting year** for all non-material entities. This value is based on **CO-2.2** from the **Substance-based Income Exclusion** workspace in the **OECD-Standard** folder.
#### NM-3.8 Carrying value of relevant Eligible Tangible Assets located in the jurisdiction
Displays the **arithmetic mean of the tangible asset values** at the beginning and end of the reporting year: ({NM-3.6} + {NM-3.7}) / 2.
#### NM-3.9 Allocations of Eligible Tangible Assets in case of Permanent Establishments or Flow-Through Entities
Displays the **aggregate of tangible asset allocations for permanent establishments or flow-through entities** for all non-material entities. These allocations are made in the **FTE & PE Allocations** workspace.
#### NM-3.10 Application of relevant mark-up percentage for the Reporting Fiscal Year
Displays the **relevant mark-up percentage for tangible assets for the reporting fiscal year**.
#### NM-3.11 Tangible Assets Carve-Out Amount
Displays the **tangible assets carve-out amount** calculated by multiplying the sum of the carrying value of tangible assets and allocations by the relevant mark-up percentage: ({NM-3.8} + {NM-3.9}) × {NM-3.10}.
#### NM-3.12 Total amount of the Substance Based Income Exclusion
Displays the **total substance-based income exclusion**, calculated as the sum of the payroll carve-out amount and the tangible assets carve-out amount: {NM-3.5} + {NM-3.11}.
#### NM-3.13 Routine Profits Test successful?
Indicates **whether the Routine Profits Test is successful**. The test is successful based on comparing the **substance-based income exclusion (NM-3.12)** against the **qualified CbCR revenue and relevant income thresholds**.
A checkbox is displayed if the test is successful.
### Result
NM-4 displays whether at least one of the three tests (Simplified ETR, De Minimis, or Routine Profits) is successful.
If this field displays a positive result, i.e. the checkbox is activated, the constituent entities in this jurisdiction or subgroup are **eligible to elect the NMCE Safe Harbour** (see also **EE-1** in the **Entity Election and General Information** workspace of the [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md) folder).
## Relationship to Entity Elections
The NMCE Safe Harbour check determines **eligibility** for the NMCE safe harbour, but it does not automatically exclude CEs from the full-scope calculations. To actually **apply** the NMCE Safe Harbour, do the following:
1. Check that at least one test in **C1 – NMCE Safe Harbour** is successful, i.e. **NM-4** displays positive result.
2. Activate the **EE-1** checkbox under **Entity Data Collection | OECD-Standard | Entity Election and General Information** workspace for each constituent entity.
3. Create a new snapshot to apply the following exclusion from:
- C2 – CE Calculations
- C4 – Jurisdictional Blending (for most values)
- C5 – Top-up Tax Allocation
> **Note:** If **EE-1** is activated but none of the tests were successful in the corresponding jurisdiction or subgroup in **C1 – NMCE Safe Harbour**, the NMCE Safe Harbour is **not** applicable for the CE.
---
---
title: "C2 – CE Calculations"
description: "The C2 - CE Calculations workspace contains a list of the data points used in the Pillar 2 calculations, including entity elections as well as jurisdictional elections, to the extent that they impact individual CEs."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c2
language: en
last_updated: 2026-05-01
---
# C2 – CE Calculations
## Overview
In the **Tax Compliance & Reporting** solution, the **C2 - CE Calculations** workspace contains a list of the data points used in the Pillar 2 calculations, including entity elections as well as jurisdictional elections, to the extent that they impact individual CEs.
Values in this workspace might differ from the respective values in the entity data collection for any of the following reasons:
- As in all parts of the **Calculation** section, values are displayed in the **snapshot currency**.
- The entity data collection allows importing multiple values into the same field and making further adjustments in that line. The calculations use and display the **Total** value for each line item.
- Activating the **AMAE20** to **AMAE26** checkboxes confers **Excluded Entity** status, effectively setting most values to zero. However, activating the checkbox for **EE-4** strips an entity of that status.
- Certain other elections also are included in the Pillar 2 calculations. Those elections are highlighted in the description of the linked item.
> **Warning:** If a CE qualifies for the **NMCE Safe Harbour**, i.e. the [NMCE Safe Harbour Check](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c1.md) was successful and **EE-1** has been activated for the CE (see **Entity Election and General Information** workspace in the [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md) folder), the CE is **excluded** from the workspace.
## Navigation
The **C2 – CE Calculations** workspace can be found at **Pillar 2 | Calculation | C2 – CE Calculations** and is displayed as follows:
'C2 – CE Calculations' workspace
The workspace contains two tabs:
- **C2 - CE Calculations**: Displays the calculated values for each data point.
- **Additions / Reductions**: Displays additions and reductions applied to the calculation.
To access this workspace and display the desired values:
1. Select a snapshot in the **Home** workspace.
2. Navigate to **C2 – CE Calculations**.
3. Select the jurisdiction or subgroup you want to review from the **Jurisdiction** drop-down list.
## Notes on the Individual Sections
### Determination of Net GloBE Income (Loss)
- INC-1 and all following fields of this section: Excluded entity status sets this value to zero.
- INC-2.11: Not selecting **EE-2** sets this value to zero.
- INC-2.12: Not selecting **JE-31** sets this value to zero.
- INC-2.13: This value reflects the sum of the relevant **cross-border adjustments**.
- INC-2.15: Not selecting **JE-32** sets this value to zero.
- INC-2.16: Not selecting **JE-10** sets this value to zero.
- INC-2.17: This value reflects the sum of the relevant **cross-border adjustments**.
- INC-2.18: Not selecting **JE-33** sets this value to zero.
- INC-2.24: Not selecting **EE-8** sets this value to zero.
- INC-2.25 represents the **International Shipping Income Exclusion** and equals the sum of **SHIP-1** (International Shipping Income) and **SHIP-2** (Qualified Ancillary International Shipping Income) from the **International Shipping** workspace (see also [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md)). If the CE has no international shipping activities, this value will be zero.
- INC-2 is the **sum of adjustments**: {INC-2.1}-{INC-2.2}-{INC-2.3}+{INC-2.4}-{INC-2.5}-{INC-2.6}+{INC-2.7}-{INC-2.8}-{INC-2.9}+{INC-2.10}-{INC-2.11}+{INC-2.12}-{INC-2.13}+{INC-2.14}+{INC-2.15}+{INC-2.16}+{INC-2.17}-{INC-2.18}-{INC-2.19}+{INC-2.20}-{INC-2.21}-{INC-2.22}-{INC-2.23}+{INC-2.24}-{INC-2.25}+{INC-2.26}
- INC-3 is the **Net GloBE Income (Loss)**: {INC-1}+{INC-2}
### Determination of Covered Current Taxes
- All fields except CT-2 and CT-3: Excluded entity status sets this value to zero.
- CT-2.6 includes covered taxes on income that is **excluded from GloBE income**, including taxes attributable to **international shipping income** (see **SHIP-4** from the **International Shipping** workspace in the [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md) folder). These covered taxes are subtracted from the current tax expense to maintain consistency between the income exclusion and the related tax treatment.
- CT-2.12: Not selecting **JE-10** sets this value to zero.
- CT-2.16: Not selecting **EE-8** sets this value to zero.
- CT-2 is the **sum of adjustments:**{CT-2.1}+{CT-2.2}+{CT-2.3}+{CT-2.4}+{CT-2.5}-{CT-2.6}-{CT-2.7}-{CT-2.8}-{CT-2.9}-{CT-2.10}-{CT-2.11}-{CT-2.12}-{CT-2.13}-{CT-2.14}+{CT-2.15}+{CT-2.16}
- CT-3 is **current taxes after adjustments:**{CT-1}+{CT-2}
### Determination of Covered Deferred Taxes
- fields DT-1 to DT-16 and DT-4:
- Excluded entity status sets this value to zero.
- Selecting **JE-50** sets this value to zero.
- DT-1 is the **Total Deferred Tax Expense** calculated as: {DT-1.1} - {DT-1.2} + {DT-1.3}
- DT-2 is the **sum of adjustments**: -{DT-2.1}-{DT-2.2}-{DT-2.3}-{DT-2.4}-{DT-2.5}-{DT-2.6}+{DT-2.7}+{DT-2.8}+{DT-2.9}-{DT-2.10}-{DT-2.11}-{DT-2.12}+{DT-2.13}-{DT-2.14}-{DT-2.15}+{DT-2.16}
- DT-3 is the **total deferred tax adjustment amount**: {DT-1}+{DT-2}
- DT-5 is the **total deferred tax adjustment amount (recasted)**: {DT-3}-{DT-4}
- ACT-1 are the **Adjusted Covered Taxes**: {CT-3}+{CT-4}+{DT-5}
### Determination of Substance-based Income Exclusion Amount
- fields CO-1, CO-1.1, CO-2, CO-2.2:
- Excluded entity status sets this value to zero.
- Selecting **JE-12** sets this value to zero.
- CO-1.1: States for each entity the **Total** value of eligible payroll costs from the entity data collection.
- CO-1B: equals **SHIP-3.1** from the **International Shipping** and represents the payroll costs related to employees engaged in international shipping activities. Because the related income is excluded from GloBE income (via **INC-2.25**), these payroll costs must also be excluded from the substance-based carve-out calculation to maintain consistency. This amount is subtracted from the eligible payroll costs before applying the carve-out percentage.
- CO-1.2 shows the mark-up percentage relevant for eligible payroll costs according to the date in GEN-1.2.
- CO-1 is the **Payroll Carve-Out Amount**: (({CO-1.1}+{CO-1A}-{CO-1B})\*{CO-1.2})/100
- CO-2.1:
- States for each entity the **Total** value of the entity data collection in CO-2.1.
- Is set to zero if the entity is an excluded entity, that did not elect not to be treated as an Excluded Entity (EE-4).
- Is set to zero if the Entity elected not to apply the Substance-based Income Exclusion (JE-12)
- CO-2B: equals **SHIP-3.2** from the **International Shipping** workspace and represents the carrying value of tangible assets (e.g., ships, equipment) used in international shipping operations. Because the related income is excluded from GloBE income (via **INC-2.25**), these tangible assets must also be excluded from the substance-based carve-out calculation to maintain consistency. This amount is subtracted from the eligible tangible assets before applying the carve-out percentage.
- CO-2.4 shows the mark-up percentage relevant for eligible tangible assets according to the date in GEN-1.2.
- CO-2 is the **Tangible Assets Carve-Out Amount**: (({CO-2.3}+{CO-2A}-{CO-2B}) \* {CO-2.4})/100
- CO-3 is the **Substance-based Income Exclusion**: {CO-1}+{CO-2}
> **Note:** **Note**: The subtraction of **CO-1B** and **CO-2B** ensures that the substance-based income exclusion (carve-out) is calculated only on the payroll costs and tangible assets that relate to income that is **included** in the GloBE income calculation. This **prevents double-counting of benefits** when international shipping income is excluded.
### Information for the Top-Up Tax Calculation and Information
- fields TT-2.3, I-3:
- Excluded entity status sets this value to zero.
- **I-3** is independent of the aggregate asset gain election (**JE-10**).
### De Minimis Information
| Option | Description |
|---------|---------|
| FYALL | Shows the number of fiscal years during the two preceding reporting periods during which the CE was not part of the calculation. |
| DM-4.1 | Average of the revenue of the reporting fiscal year and the two preceding years if those are available. If fiscal years from earlier periods are not available, the value is calculated by dividing the cumulative revenue by the number of fiscal years available. |
| DM-4.2 | Average of the GloBE revenue of the reporting fiscal year and the two preceding years if those are available. If fiscal years from earlier periods are not available, the value is calculated by dividing the cumulative GloBE revenue by the number of fiscal years available. |
| DM-4.3 | Average of the financial accounting net income (or loss) of the reporting fiscal year and the two preceding years if those are available. If fiscal years from earlier periods are not available, the value is calculated by dividing the cumulative GloBE revenue by the number of fiscal years available. |
| DM-4.4 | Average of the GloBE income (or loss) of the reporting fiscal year and the two preceding years if those are available. If fiscal years from earlier periods are not available, the value is calculated by dividing the cumulative GloBE income or loss by the number of fiscal years available. |
### International Shipping Income Exclusion
| Option | Description |
|---------|---------|
| SHIP-1.x | **SHIP-1.1**: Displays the categories selected in the entity data collection for international shipping activities pursuant to Article 3.3.2. **SHIP-1.2**: The total revenue from international shipping activities, as entered in the entity data collection. **SHIP-1.3**: The costs attributable to international shipping activities, as entered in the entity data collection. SHIP-1: International Shipping Income, automatically calculated as the net income from international shipping activities ({SHIP-1.2} - {SHIP-1.3}). This amount contributes to the exclusion in **INC-2.25**. |
| SHIP-2.x | **SHIP-2.1**: Displays the categories selected in the entity data collection for qualified ancillary international shipping activities pursuant to Article 3.3.3. **SHIP-2.2**: The total revenue from qualified ancillary international shipping activities, as entered in the entity data collection. **SHIP-2.3**: The costs attributable to qualified ancillary international shipping activities, as entered in the entity data collection. **SHIP-2**: **Qualified Ancillary International Shipping Income**, automatically calculated as the net income from qualified ancillary activities ({SHIP-2.2} - {SHIP-2.3}). This amount contributes to the exclusion in **INC-2.25**. |
| SHIP-3.x | Adjustments to maintain consistency with income exclusion **SHIP-3.1**: Displays the payroll costs related to international shipping activities, as entered in the entity data collection. This amount is subtracted in **CO-1B** when calculating the payroll carve-out amount (**CO-1**). **SHIP-3.2**: Displays the carrying value of tangible assets used in international shipping operations, as entered in the entity data collection. This amount is subtracted in **CO-2B** when calculating the tangible assets carve-out amount (**CO-2**). **Covered Taxes**: Taxes on excluded shipping income |
| SHIP-4 | Displays the covered taxes related to the international shipping income that is being excluded, as entered in the entity data collection. This amount is included in **CT-2.6** (Current tax expense on income excluded from GloBE Income or Loss) to ensure that taxes on excluded income are also removed from the covered taxes calculation. |
---
---
title: "C3 – De Minimis Check"
description: "The De Minimis Check workspace contains the permanent safe harbour test. This test is successful if the GloBE revenue and the GloBE Income are below the respective GloBE thresholds."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c3
language: en
last_updated: 2026-05-01
---
# C3 – De Minimis Check
## Overview
In the **Tax Compliance & Reporting** solution, the **De Minimis Check** workspace contains the permanent safe harbour test. This test is successful if the GloBE revenue and the GloBE Income are below the respective GloBE thresholds.
The average GloBE revenue and the average GloBE income are calculated on a CE basis as part of the CE Calculations. The de minimis check aggregates these values on a jurisdictional or subgroup level, based on the **reporting dimension type** selected for the **CbCR-Safe Harbour blending**, and compares them to the relevant threshold.
## Navigation
The **C3 – De Minimis Check** workspace can be found at **Pillar 2 | Calculation | C3 – De Minimis Check** and is displayed as follows:
'C3 – De Minimis Check' workspace
To access this workspace and display the desired values:
1. Select a snapshot in the **Home** workspace.
2. Navigate to **C3 – De Minimis Check**.
3. Select the jurisdiction or subgroup you want to review from the **Jurisdiction** drop-down list.
## De Minimis Information
This section displays the underlying revenue and income data for the reporting fiscal year and the two preceding fiscal years, as well as the calculated averages.
### Reporting Fiscal Year
| Field | Description |
|---------|---------|
| DM-1.1 | Revenue (Financial Accounts) for the reporting fiscal year. |
| DM-1.2 | GloBE Revenue for the reporting fiscal year. |
| DM-1.3 | Financial Accounting Net Income (or Loss) for the reporting fiscal year. |
| DM-1.4 | GloBE Income (or Loss) for the reporting fiscal year. |
### 1st Preceding Fiscal Year
| Field | Description |
|---------|---------|
| DM-2.1 | Revenue (Financial Accounts) for the 1st preceding fiscal year (if applicable). |
| DM-2.2 | GloBE Revenue for the 1st preceding fiscal year (if applicable). |
| DM-2.3 | Financial Accounting Net Income (or Loss) for the 1st preceding fiscal year (if applicable). |
| DM-2.4 | GloBE Income (or Loss) for the 1st preceding fiscal year (if applicable). |
### 2nd Preceding Fiscal Year
| Field | Description |
|---------|---------|
| DM-3.1 | Revenue (Financial Accounts) for the 2nd preceding fiscal year (if applicable). |
| DM-3.2 | GloBE Revenue for the 2nd preceding fiscal year (if applicable). |
| DM-3.3 | Financial Accounting Net Income (or Loss) for the 2nd preceding fiscal year (if applicable). |
| DM-3.4 | GloBE Income (or Loss) for the 2nd preceding fiscal year (if applicable). |
### Fiscal Year Availability and Averages
| Field | Description |
|---------|---------|
| FYALL | Shows the number of fiscal years during the two preceding reporting periods during which the CE was not part of the calculation. |
| DM-4.1 | Shows the aggregate amount of the average revenue (Financial Accounts) for the reporting dimension. |
| DM-4.2 | Shows the aggregate amount of the average GloBE revenue for the reporting dimension. |
| DM-4.3 | Shows the aggregate amount of the average financial accounting net income (or loss) for the reporting dimension. |
| DM-4.4 | Shows the aggregate amount of the average GloBE income (or loss) for the reporting dimension. |
## De Minimis Test
This section contains the test values and the result of the de minimis check.
| Field | Description |
|---------|---------|
| DM-5.1 | GloBE Revenue – Average of the three fiscal years. This is the same value that is used in line **DM-4.2** above. |
| DM-5.2 | Average GloBE Revenue threshold (EUR 10,000,000). |
| DM-5.3 | GloBE Income (or Loss) – Average of the available fiscal years. This is equal to the **DM-4.4** value above. |
| DM-5.4 | Average GloBE Income threshold (EUR 1,000,000). |
| DM-6 | The de minimis test is successful if the aggregated average GloBE revenue (**DM-4.2**) is below the average GloBE revenue threshold (**DM-5.2**); and the average GloBE income (**DM-4.4**) is below the average GloBE income threshold (**DM-5.4**). |
| DM-7 | Indicates the basis on which the de minimis test was performed. |
---
---
title: "C4 – Jurisdictional Blending"
description: "The jurisdictional blending aggregates CE data based on the reporting dimension type selected for the top-up tax blending."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c4
language: en
last_updated: 2026-05-01
---
# C4 – Jurisdictional Blending
## Overview
In the **Tax Compliance & Reporting** solution, the workspace **C4 – Jurisdictional Blending** can be found. The jurisdictional blending aggregates CE data based on the **reporting dimension type** selected for the **top-up tax blending**.
Unless otherwise indicated, the fields in this dialog aggregate the respective values for a jurisdiction or subgroup. For example, INC-1 aggregates the INC-1 values of the individual CEs in a given jurisdiction.
> **Warning:** If a CE qualifies for the **NMCE Safe Harbour**, i.e. the [NMCE Safe Harbour Check](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c1.md) was successful and **EE-1** has been activated for the CE (see **Entity Election and General Information** workspace in the [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md) folder), the CE is **excluded** from the workspace.
## Navigation
The **C4 – Jurisdictional Blending** workspace can be found at **Pillar 2 | Calculation | C4 – Jurisdictional Blending** and is displayed as follows:
'C4 – Jurisdictional Blending' workspace
To access this workspace and display the desired values:
1. Select a snapshot in the **Home** workspace.
2. Navigate to **C4 – Jurisdictional Blending**.
3. Select the jurisdiction or subgroup you want to review from the **Jurisdiction** drop-down list.
## Notes on the Section 'Determination of Covered Deferred Taxes'
- **DT-1.1, DT-1.2, DT-1.3**: These fields aggregate the respective values from the [C2 - CE Calculations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c2.md) workspace for each jurisdiction.
- **DT-1**: The aggregated total deferred tax expense for the jurisdiction, calculated as the aggregate of the DT-1 values from all constituent entities in the jurisdiction.
- **TCF-1.1**: The excess negative tax expense amount is calculated only in case of negative adjusted covered taxes that exceed the expected adjusted covered taxes.\
\
In the case of an overall GloBE loss, the excess negative tax expense amount is the positive difference between the expected negative tax expense and the negative tax expense.\
\
In the case of an overall GloBE income, the excess negative tax expense amount is the positive value of the negative tax expense.
- **TCF-1.2**: The excess negative tax expense carry-forward lowers the adjusted covered taxes if there is a remaining balance of the excess negative tax expense carry-forward from prior years (I-1.1) and the GloBE income and the adjusted covered taxes are positive. The negative expense carry-forward is decreased by the lower of the remaining balance of excess negative tax expense carry-forward and the adjusted covered taxes of the current period.
- **ACT-1**: Adjusted Covered Taxes ={CT-2.2}+{CT-3}+{CT-4}+{DT-5}+{TCF-1.1}-{TCF-1.2}
---
---
title: "C5 – Top-up Tax Allocation"
description: "This workspace displays the top-up tax payable by low-taxed CEs and members of joint venture groups."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c5
language: en
last_updated: 2026-05-01
---
# C5 – Top-up Tax Allocation
## Overview
In the **Tax Compliance & Reporting** solution, the **C5 – Top-up Tax Allocation** workspace displays the **top-up tax payable** by low-taxed CEs and members of joint venture groups.
The tax is calculated by distributing the top-up tax amount per jurisdiction or subgroup to the low-taxed CEs with a positive GloBE income based on their share of the total GloBE income in that jurisdiction or subgroup.
> **Warning:** If a CE qualifies for the **NMCE Safe Harbour**, i.e. the [NMCE Safe Harbour Check](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/c1.md) was successful and **EE-1** has been activated for the CE (see **Entity Election and General Information** workspace in the [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md) folder), the CE is **excluded** from the workspace.
## Navigation
The **C5 – Top-up Tax Allocation** workspace can be found at **Pillar 2 | Calculation | C5 – Top-up Tax Allocation** and is displayed as follows:
'C5 – Top-up Tax Allocation' workspace
To access this workspace and display the desired values:
1. Select a snapshot in the **Home** workspace.
2. Navigate to **C5 – Top-up Tax Allocation**.
3. Select the jurisdiction or subgroup you want to review from the **Jurisdiction** drop-down list.
## Notes on the Individual Sections
### Low-taxed CE Allocated Top-Up Tax
| Field | Description |
|---------|---------|
| TA-1 | ISO code of the **jurisdiction or subgroup**. |
| TA-2.1 | **Positive GloBE income of the low-taxed CE or member of Joint Venture Group.** |
| TA-2.2 | **Total GloBE Income of the Jurisdiction or Subgroup**. Equal to **INC-3** of the entire jurisdiction or subgroup. |
| TA-2 | **Relevant Percentage of the Net GloBE Income**: {TA-2.1} / {TA-2.2} \* 100. |
| TA-3.1 | **Total Top-Up Tax Amount of the Jurisdiction or Subgroup**. Equal to **TT-3**. |
| TA-3 | **Top-Up Tax Amount of the low-taxed CE or member of Joint Venture Group**: {TA-2} \* {TA-3.1} / 100. |
### Income Inclusion Rule
| Field | Description |
|---------|---------|
| TA-4.1 | **Inclusion of Top-up Tax Expense of subsidiaries**. Equal to the **Total** amount in **IR-1**. |
| TA-4.2 | **Income Inclusion Rule Offset**: {TA-3} \* {TA-4.1} / 100. |
| TA-5 | **Allocation of Top-up Tax Amount to local CE under a QDMTT**. |
### Additional Current Top-up Tax
| Field | Description |
|---------|---------|
| TA-6.1 | **Total Amount of Additional Current Top-up Tax of the Jurisdiction or Subgroup**. |
| TA-6.2 | **Allocation Basis**. |
| TA-6.3 | **Allocation Rate**. |
| **TA-6** | **Additional Current Top-up Tax allocated to CE or member of Joint Venture Group**. |
| TA-7 | **Additional Current Top-up Tax Expense of CE or member of Joint Venture Group**. |
---
---
title: "Calculation"
description: "At Country-by-Country Reporting | Calculation | Home, users can create new snapshots, manage existing snapshots, and select a snapshot that will be presented in the other workspaces under Calculation."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr
language: en
last_updated: 2026-07-28
---
# Calculation
## Overview
In the **Country-by-Country-Reporting** sub-module, the calculation process creates a snapshot that reflects the data exactly as it was in the moment of its creation. Snapshots do not change as new data is added to the sub-module or when jurisdictional or entity elections are changed. Instead, after entering new data or to evaluate the impact of an election, you have to create new snapshots.
In the **Home** workspace, users can create new snapshots or select an existing snapshot. The other workspaces display the information from that snapshot.
## Navigation
The **Calculation** folder can be found at **Country-by-Country-Reporting | Calculation**.
## Workspaces in the 'Calculation' folder
The **Calculation** folder contains the following workspaces:
| Workspace | Description |
|---------|---------|
| [Home](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/home.md) | Lets you create, manage, and select snapshots. The other **Calculation** workspaces display the data from the selected snapshot. |
| [Group Data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/group-data.md) | Displays the group data from the **Group Data Collection** workspace as it was when the snapshot was created — a required part of the Country-by-Country report. |
| [Table 1](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/tables-cbcr.md#table-1) | Shows the country-by-country data at jurisdiction level: the aggregate values for all CEs in a jurisdiction, converted into the snapshot currency. |
| [Table 2](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/tables-cbcr.md#table-2) | Shows the country-by-country data at entity level, for all CEs resident in the selected jurisdictions, in the snapshot currency. |
| [Table 3](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/tables-cbcr.md#table-3) | Shows the additional information entered in the **Group Data Collection** workspace. |
| [Public Report (EU)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/public-report-eu.md) | Shows the EU public Country-by-Country report. |
| [Public Report (Australia)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/calculation-cbcr/public-report-aus.md) | Shows the Australian public Country-by-Country report. |
> **Note:** The **Public Report (EU)** and **Public Report (Australia)** workspaces appear only after you select a snapshot that includes the matching public-reporting scope — **Public CbCR (EU)** or **Public CbCR (Australia)** — chosen when you perform the calculation.
---
---
title: "Calculation"
description: "In the context of tax management and reporting, the term calculation refers to a data-driven process that produces specific results in compliances with the relevant laws and guidelines. These calculations are essential for deriving key financial indicators such as tax liabilities, income adjustments, and safe harbors."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation
language: en
last_updated: 2026-05-01
---
# Calculation
## Overview
In the context of tax management and reporting, the term **calculation** refers to a data-driven process that produces specific results in compliances with the relevant laws and guidelines. These calculations are essential for deriving key financial indicators such as **tax liabilities**, **income adjustments**, and **safe harbors**.
In the Pillar 2 module, the calculation process creates a **snapshot** that reflects the data exactly as it was in the moment of its creation. Snapshots do not change as new data is added to the module or when jurisdictional or entity elections are changed. Instead, after entering new data or to evaluate the impact of an election, you have to create new snapshots.
In the **Home** workspace, users can create new snapshots or select an existing snapshot. The other workspaces display the information from that snapshot.
---
---
title: "Capital Gains Tax on Dividends"
description: "How to enter the entire dividend issue is described in this chapter. The entry is made in §8b KStG, including the entry of the capital gains tax and the indication of the posting method (affecting or not affecting P&L)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2/tax-on-dividends
language: en
last_updated: 2026-05-28
---
# Capital Gains Tax on Dividends
## Overview
How to enter the entire dividend issue is described in this chapter. The entry is made in **§8b KStG**, including the entry of the capital gains tax and the indication of the posting method (affecting or not affecting P&L).
## Capital Gains Tax on Dividends Pursuant to Section 8b (1) of the Corporate Tax Act (KStG)
The capital gains tax is entered on the [§8b KStG](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/s-8b-kstg---beteiligungen-an-anderen-koerperschaften-und-persone.md) form. If no entry is made in **therefrom posted**, the issue is considered not affecting P&L. If the issue is corrected or deleted, the entered capital gains tax is also deleted.
Formular §8b KStG
The posting affecting P&L is usually made only for tax group parents and standalone companies. Tax group members and intermediate tax group parents usually post without affecting P&L.
If an entry is made in **therefrom posted**, it is automatically included in the WA and GK attachment:
Anlage WA - Weitere Angaben / Anträge
Anlage WA – Zeilen 82.5 und 82.5
Anlage WA – Zeilen 83.1 und 83.2
From assessment year 2014 onwards, the capital gains tax of the tax group member is no longer disclosed cumulatively at the respective tax group parent. The WA attachment is always to be completed only with the tax group parent's own values.
Addition of the posted tax affecting P&L to the result after taxes for reconciliation to the result before taxes under **Current Taxes | Current Taxes**:
Gewinn(+)/Verlust (-) lt. G+V nach Steuern
Consideration of the tax when calculating the commercial profit transfer of a tax group member under **Current Taxes | Current Taxes**:
Berücksichtigung der Steuer bei der Berechnung der handelsrechtlichen Gewinnabführung
Disclosure of creditable taxes for crediting against the tax expense / calculation of the tax provision under **Current Taxes | Current Taxes**:
Steuer bei der Berechnung der handelsrechtlichen Gewinnabführung einer Organgesellschaft
## Other Capital Gains Tax
The disclosure of the creditable gains yield tax is entered in the WA attachment for the respective company (if necessary with disclosure of **davon erfolgswirksam gebucht** (thereof posted affecting P&L).
Anlage WA – Anrechnung von Abzugssteuern
From assessment year 2014 onwards, the capital gains tax of the tax group member is no longer disclosed cumulatively at the respective tax group parent. The WA attachment is always to be completed only with the tax group parent's own values.
If an entry is made in **thereof P&L**, it is automatically included in the WA and GK attachments.
The posting affecting P&L is usually made only for tax group parents and standalone companies. Tax group members and intermediate tax group parents usually post without affecting P&L.
Addition of the posted tax affecting P&L to the result after taxes for reconciliation to the result before taxes:
/Verlust (-) lt. G+V nach Steuern") Gewinn (+)/Verlust (-) lt. G+V nach Steuern
Consideration of the tax when calculating the profit transfer according to commercial law of a tax group member:
Berechnung der handelsrechtlichen Gewinnabführung einer Organgesellschaft
Disclosure of creditable taxes for crediting against the tax expense / calculation of the tax provision:
Ausweis der anrechenbaren Steuern
---
---
title: "CE Information"
description: "The CE Information workspace contains the fields where you enter information on an individual CE, including its address and tax identification number (TIN)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/ce-information-cbcr
language: en
last_updated: 2026-07-28
---
# CE Information
## Overview
The **CE Information** workspace contains the fields where you enter information on an individual CE, including its address and tax identification number (TIN).
## Navigation
The **CE Information** workspace can be found under **Country-by-Country-Reporting | Entity Data Collection | CE Information** and is displayed as follows, for example:
'CE Information' workspace
## Entering the Address
Under **Place of Incorporation, Registration or Management**, enter the address and type of address of the selected CE in the fields **CbC-3.1** to **CbC-3.10**. **City** (**CbC-3.8**) and **Address type** (**CbC-3.10**) are mandatory.
In **CbC-3.0**, **Financial Statement Basis (Currency Conversion)**, select the basis used for the currency conversion from the drop-down list.
## Entering the Tax Identification Details
In the **Identification Numbers** section, enter the tax identification details of the CE:
- In **CbC-3.11**, enter the **Tax identification number (TIN)**, and in **CbC-3.12** select who the TIN was issued by.
- If the CE does not have a TIN, activate the check box **CbC-3.13**, **The CE does not have a TIN**.
- To add a further identification number, activate the check box **CbC-3.14**, **Add identification number**, and complete the fields **CbC-3.14a** to **CbC-3.14c**. To add a second identification number, activate the check box **CbC-3.15**, **Add second identification number**, and complete the fields **CbC-3.15a** to **CbC-3.15c**.
## Confirming the Data
In the **Confirmation** section, a user with the necessary rights activates the check box **CbC-3.16**, **Hereby I confirm that the data stated above has been updated and verified**, to confirm that the data in this workspace has been updated and verified.
## Showing IDs
The **Show IDs** button displays the technical identifiers of each field, which map the field to its data interface for imports and troubleshooting.
To show the IDs:
1. At the top of the workspace, click **Show IDs**. Each field displays the **Mapping ID** and the **TQ ID** below its name.
'CE Information' workspace with the IDs displayed
2. To return to the normal view, click **CE Information** in the menu again.
---
---
title: "Certificates"
description: "In the Certificates work space, you can centrally record, maintain, and assign Elster and ELMA certificates to users."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-administration/certificates
language: en
last_updated: 2026-05-01
---
# Certificates
## Overview
In the **Certificates** work space, you can centrally record, maintain, and assign Elster and ELMA certificates to users.
## Creating and Configuring Certificates
Proceed as follows:
1. Click **Create**.
2. In the input mask that is then shown, select the type of the certificate and, if applicable, enter a description and comment.
Depending on the selected certificate type, additional areas are displayed (see the following subheadings).
Input mask for ELMA certificate
### ELMA Certificate
Specify the following in the **User allocation** and **ELMA** areas:
| Option | Description |
|---------|---------|
| User allocation | In the **User allocation** area, you can assign the certificate to multiple users. You can assign only one certificate of one type to each user. For example, if you have created two ELMA certificates, you can assign only one of the two ELMA certificates to user A. |
| Certificate file | Select a certificate file of the PEM file type. |
| Password | Please enter the password associated with the certificate. |
| BZSt-Number | BZST number with format \[BZ\] or \[BX\]\[9 digits\] |
| Account-Id | 10-digit numeric user account ID |
### ELSTER Certificate
Specify the following in the **User allocation** and **ELSTER** areas:
| Option | Description |
|---------|---------|
| User allocation | In the **User allocation** area, you can assign the certificate to multiple users. You can assign only one certificate of one type to each user. For example, if you have created two ELSTER certificates, you can assign only one of the two ELSTER certificates to user A. |
| Certificate file | Select a certificate file of the PFX file type. |
| Password | Please enter the password associated with the certificate. |
### DIP Certificate
Please specify the following in the **User allocation** and **DIP** areas:
| Option | Description |
|---------|---------|
| User allocation | In the **User allocation** area, you can assign the certificate to multiple users. You can assign only one certificate of one type to each user. For example, if you have created two DIP certificates, you can assign only one of the two DIP certificates to user A. |
| Client ID | Enter the client ID corresponding to the certificate. |
| Certificate file | Select a certificate file of the PEM file type. |
| Key File | Select a key file in PEM format that matches the certificate. |
---
---
title: "CoA Company"
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coacompany
language: en
last_updated: 2026-05-28
---
# CoA Company
## Overview
The balance sheet structure maintained in the [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md) area essentially serves as the basis for the B/S comparison of all created companies. In the **CoA Company** workspace, this structure can be individually extended for single companies:
- In the **CoA Company** workspace, the structure from the **CoA Group** workspace is displayed.
- It is not possible to delete or edit existing balance sheet positions. However, it is possible to extend each lowest balance sheet position by adding a single-level breakdown. These new, **unit-specific** balance sheet positions must always be assigned to a superior group balance sheet position.
## Navigation
The **CoA Company** workspace belongs to the function area **Master Data** and is, for example, displayed as follows:
'CoA Company' workspace
## Creating and Administrating Balance Sheet Positions
Click **Create** to add a new balance sheet position. The input mask is then displayed as follows:
Creating balance sheet position
These details must be stored for each balance sheet position that represents an **input position**. Input positions are subordinate to superior account positions. For example, technical plants and machinery are entered as input positions under the superior account position **Property plant and equipment**.
With the exception of **Account ID** and **Superior account position**, enter the Information in the input mask as described in [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md) in the section _Creating and Maintaining Balance Sheet Position_. Please specify the following for **Account ID** and **Superior account position**:
| Option | Description |
|---------|---------|
| Account ID | An individual account ID must be assigned for each balance sheet position. The account ID can no longer be edited afterwards and is also no longer available after the balance sheet position is deleted. The name of the balance sheet position is not entered in this field. This only takes place after the creation in a subsequently displayed table area on the right side. |
| Superior account position | Only the lowest hierarchy level of the balance sheet structure from the **CoA Group** workspace can be selected as a superior account position; in other words, adjustments are limited to a single-level breakdown. The selection list contains only balance sheet positions that meet this criterion. |
## Mapping
If balance sheet positions that were created in the prior period are deleted in the current period, a **mapping** can be used to ensure that the correct change in deferred tax is determined for each balance sheet position for reporting purposes. For this purpose, non existing balance sheet items from the previous period are assigned to a current balance sheet item.
To do this, click on Mapping in the Balance Sheet Company workspace. For more information about the general range of functions, see [CoA Group](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups.md) in the _Additional Functions_ section. In the mapping function in the **CoA Company** workspace, you can also assign company-specific accounts that were included in the previous period and have been deleted in the current period to a current balance sheet item.
---
---
title: "CoA Group"
description: "The balance sheet structure stored in the CoA Group workspace provides the common, binding framework for all companies and serves as the basis for the B/S Comparison workspace in the Company functional area."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups
language: en
last_updated: 2026-09-29
---
# CoA Group
## Overview
The balance sheet structure stored in the **CoA Group** workspace provides the common, binding framework for all companies and serves as the basis for the [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md) workspace in the **Company** functional area _._ An exception to this is the use of the [CoA Company](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coacompany.md) workspace – here, the balance sheet structure can be **extended in a unit-specific manner**.
Due to the balance-sheet-oriented approach to the determination of deferred taxes according to IFRS, US-GAAP, and local GAAP(the so-called temporary concept), entering a **balance sheet structure** is essential. Adjustments to the balance sheet structure in the **CoA Group** workspace only affect the selected period – other periods created in TCR are not impacted by this.
## Navigation
The **CoA Group** workspace belongs to the function area **Master Data** and is, for example, shown as follows:
'CoA Group' workspace
## Creating and Administrating Balance Sheet Positions
Click **Create** to add a new balance sheet position. The input mask is then displayed as follows:
") Creating a new balance sheet position (excerpt)
These details must be specified for each balance sheet position that represents an **input position**. Input positions are subordinate to superior account positions. For example, technical plants and machinery are entered as input positions under the superior account position **Property plant and equipment**. Specify the following:
#### Copy based on
Creates a copy based on an existing balance sheet position.
#### Account ID
An individual account ID must be assigned for each balance sheet position. The account ID can no longer be edited afterward and is also no longer available after deleting the balance sheet position.
The name of the balance sheet position is not entered in this field. This only takes place after creation in a subsequently displayed table area (see [Names of Balance Sheet Positions in Multiple Languages](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coagroups/.md#mula)) _._
#### Reporting Dimension
During administration of the group balance sheet, the standard reporting dimension \[---\] is always assigned and cannot be edited. This attribute can only be changed for specific companies in the [CoA Company](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/coacompany.md) workspace.
#### Superior account position
The structure of the balance sheet is defined by specifying the superior account position. The superior account position is always the sum of the respective subordinate positions. In the **B/S Comparison** workspace, the structure is indented by leading periods and displayed below the respective superior account position:
Display of balance sheet positions
#### Relevant for current taxes
This specification determines that the balance sheet position affects the tax balance profit. For German companies, this refers to balance-sheet-internal tax differences pursuant to § 60 (2) EStDV. Consequently, only deviations between the local balance (local GAAP) and the tax balance are taken into account.
The P/L-effective change in the tax balance surplus/deficit (this change represents the tax balance surplus/deficit result of the respective fiscal year) is automatically calculated by Income Taxes and displayed as a proposed value for the purpose of calculating actual taxes (for example) in the folder [Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes.md).
#### Account is relevant for deferred tax
Certain balance sheet positions, such as equity or tax positions, are **excluded** from the determination of deferred taxes. For such positions, deactivate the check box **Account is relevant for deferred tax**. Income Taxes does **not** take possible balance sheet differences into account for these items.
Positions that are relevant for the calculation of deferred taxes or for tax rate reconciliation ([TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/trr.md)) must be classified as temporary or permanent. Activate the check box **Account is relevant for deferred tax** accordingly. Activating it makes these rows of the B/S comparison editable for input regarding the allocation of the gross balance sheet differences to “thereof” columns.
“Thereof” columns provide standard allocation options for purposes related to dividing balance sheet differences. The definition of the following attributes offers the option of automatic division in the **B/S Comparison** dialog:
- P/L differences
- OCI differences
- Differences in permanent P/L
- Differences in permanent OCI
Permanent balance sheet differences, such as shares in affiliated companies under German tax law (§ 8b KStG), do not result in deferred taxes. Nevertheless, activate the check box **Account is relevant for deferred tax**, as this may result in effects for tax rate reconciliation (TRR).
#### Relevant for True Up
The check box **Relevant for True Up** is automatically activated. Deactivate the check box if a position should not be included in the calculation of proposed True Up values.
#### Temporary
Balance sheet positions for which the **Temporary** check box is activated will trigger the calculation of deferred taxes in the event of any balance sheet differences in the tool. Therefore, activate the check box for all balance sheet positions where taxable (deferred tax liabilities - DTL) or deductible (deferred tax assets - DTA) temporary differences may arise. In this case, also activate the check box **Account is relevant for deferred tax**.
Conversely, this means that balance sheet positions that are not classified as temporary are considered **permanent**. Permanent differences **do not** lead to the calculation of deferred taxes, but may be relevant for purposes of tax rate reconciliation (TRR).
#### Temporary difference affecting equity
Balance sheet positions for which the check box **Temporary difference affecting equity** is activated do not trigger a P/L effect when calculating deferred taxes, but are instead reflected in the OCI (other comprehensive income), which does not affect the corresponding result. Adjustments involving temporary differences affecting equity occur in the area of IFRS, such as with financial instruments (IAS 39) or pensions (IAS 19). Deferred taxes that are associated with these changes in amount must also be accounted for in a manner that does not affect the corresponding result. The OCI effect of deferred taxes is reflected in the [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md) workspace.
Balance sheet positions for which the check box **Temporary difference affecting equity** is **not** activated (= **affecting P&L**) trigger a P/L effect when calculating deferred taxes. The P/L effect of deferred taxes is reflected in the **Summary** and **TRR** workspaces, for example.
Choose between **affecting P&L** and **affecting OCI**. The effect on taxable income of the adjustment of deferred taxes generally depends on the underlying accounting circumstances at hand. If the change in a balance position (e.g. depreciation) is accounted for via P/L, the deferred taxes attributable to this must also be considered as affecting P.L.
#### OCI category
Adjustments affecting OCI can be assigned to a specific OCI issue, for example, AFS securities. The individual issues are maintained in the master data under [Administration](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/administration.md) in the area _Revaluation surplus_.
Income statement-related presentation of OCI issues:
Preselection in B/S comparisons is controlled via the **Affecting P&L** setting. If differences are split automatically, the difference will be allocated to the **P/L** column in the “thereof” column when the **Affecting P&L** setting is activated. However, it may be necessary to display additional differences affecting OCI for this position in a different “thereof” column. In order for this difference to be assigned to a specific OCI issue, all OCI issues available for selection are displayed, even when the setting **Affecting P&L** is activated.
#### Short term temporary difference
This option defines the maturity of a balance sheet position. TCR makes it possible to divide deferred taxes into short-dated and long-dated positions. If the check box **Short term temporary difference** is activated, deferred taxes attributable to this balance sheet position will also be classified as short-dated.
Mapping the maturity structure affects the positions netted of deferred taxes within the tools: Short-dated deferred tax assets are netted with short-dated deferred tax liabilities, and long-dated deferred tax assets with long-dated deferred tax liabilities. The division of balance sheet positions into short-dated and long-dated positions is not mandatory.
#### Disclosed major class of deferred tax
For balance sheet positions that are to be evaluated for the disclosed major class of deferred tax, activate the **Disclosed major class of deferred tax** check box. These balance sheet positions are displayed aggregated in the **Company** folder in the **Report DT** workspace. Either the upper or the lower level in the disclosed major class of deferred tax can be indicated for each position. This prevents balance sheet positions from being accounted for twice.
It makes sense to have the resulting (shortened) balance sheet structure match the balance sheet structure of the company's annual report. This ensures that the notes on deferred taxes for each balance sheet position can be taken directly from Income Taxes.
#### Split differences automatically
The identified balance sheet differences in the **B/S Comparison** workspace must be split into the following columns:
- P/L differences
- OCI differences
- Permanent P/L differences
- Permanent OCI differences
If the **Split differences automatically** check box is activated, these differences will be split automatically. Otherwise, the gross differences must be divided across the columns manually. This can be useful, for example, when part of the gross difference is to be classified as **temporary** and part as **permanent**. The automatic splitting of differences is carried out in the **B/S Comparison** workspace using the separate **Split differences** button.
#### Residual position
A balance sheet should ultimately always be balanced. To have the balancing item (such as a profit position) calculated automatically, you can designate an item in the balance sheet structure as a residual position. If values are then imported or entered manually, the system will check in the balance sheet comparison during saving whether a validation difference would occur. If this is the case, the calculated difference is posted to the residual position.
The balancing item can be set separately for IFRS, HGB, and HB/StB differences.
> **Tip:** The **residual position** option is an additional feature that is not included in the standard product. If you are interested, please contact your Lucanet representative or use the [contact form](https://www.lucanet.com/en/contact/).
## Further Actions
### Names of Balance Sheet Positions in Multiple Languages
The language is generally set under **My Profile**. To ensure that user-created records can also be displayed in the respective local language, you must set up the language accordingly. If no text is defined for a language, the record can only be identified by the account ID after selecting the language. Proceed as follows:
1. After creating a balance sheet position, navigate to the overview table and click the pencil icon next to the desired balance sheet position.
2. Select the desired language from the drop-down list in the **Language** section in the input screen that then appears.
**Examples**:
Language - Account Name (= output value)
Deutsch - Bilanz
English - Balance Sheet
Francais - Bilan
3. Enter the designation in the selected language and click **Create**.
Language settings for group account
### Maintaining Columns
By default, the following columns are predefined in Income Taxes and are used to allocate balance sheet differences in the **B/S Comparison** workspace _:_
- P/L differences
- OCI differences
- Differences in permanent P/L
- Differences in permanent OCI
The differences are multiplied for the calculation of deferred taxes by the tax rate stored in the **Countries** workspace, i.e. the average tax rate for deferred taxes. This applies to all the above-mentioned standard columns, meaning also to any permanent differences that must be taken into account in tax rate reconciliation ([TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Tax-reconciliation-statement.md)).
In the **CoA Group** workspace, click **Maintain columns** to create additional columns for B/S comparisons. The **Tax Rate Maintenance** dialog is displayed as follows:
> **Tip:** This function was introduced because in some countries, deferred taxes for selected balance sheet differences must be calculated using a **different tax rate**. Earnings from the sale of real estate may be subject to a special tax rate. The **Maintain columns** function can take such deviating tax effects into account accordingly.
'Tax Rate Maintenance' dialog
Specify the following:
#### Dialog
The columns must be assigned to either the **IFRS - Local GAAP** or the **Local GAAP - Tax Balance** workspace. The display of the inserted columns is therefore only displayed in the selected area of the B/S comparison.
#### Applicable tax rate
Tax rate by which the balance sheet differences recorded in this column are to be multiplied. The regulations for the purposes of deferred tax rates apply here, i.e. the future (deferred) tax rate does not necessarily have to correspond to the currently valid tax rate.
#### Affecting P&L / affecting OCI
For each newly added , you must specify whether the (temporary) effects should result in deferred taxes that **affect P&L** or **affect OCI**. This reporting obligation also applies when the **Permanent** setting is activated for the column.
#### Description
The description appears as a column description in the **B/S Comparison** workspace _._
#### Permanent
If the balance sheet differences processed in this column are of a permanent nature, you must activate the **Permanent** check box. The differences do not lead to deferred taxes, but are instead appropriately taken into account in tax rate reconciliation ([TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Tax-reconciliation-statement.md)).
In addition to creating columns manually, you can use the corresponding optional predefined columns via the **plus icon**. These columns include **Thereof other changes affecting P&L**, for example.
The division of balance sheet differences among manually created columns cannot be performed automatically. This requires manual adjustment of the B/S comparison.
#### Mapping ID
To import difference amounts into this “thereof” column, you must assign a unique **mapping ID**. The mapping ID can be any text up to 20 characters long; using special characters or spaces is not recommended.
The mapping ID is also used to export values from Income Taxes.
### Mapping
If balance sheet positions are deleted in the current period that were present in the prior period, you can use the **Mapping** function to ensure that the correct change in deferred taxes is determined for each balance sheet position for reporting purposes. To this end, non existing balance sheet positions from the previous period are assigned to a current balance sheet position.
The settings apply to all units within the group.
Mapping functionality
---
---
title: "Cockpit"
description: "The Cockpit folder offers the option to monitor and change milestones and execute imports from various sources."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/cockpit-cbcr
language: en
last_updated: 2026-07-28
---
# Cockpit
## Overview
The **Cockpit** folder of the **Country-by-Country-Reporting (CbCR)** sub-module is your central place to track the progress of CbCR data collection per Constituent Entity (CE) and to load data into the sub-module.
## Navigation
The **Cockpit** folder can be found at **Country-by-Country-Reporting | Cockpit**. The folder and its corresponding workspaces are displayed as follows, for example:
'Income Taxes' workspace in 'Import' folder
## Workspaces in the 'Cockpit' folder
The **Cockpit** folder contains one workspace and one sub-folder:
| Workspace | Description |
|---------|---------|
| [Status Monitoring](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/cockpit-cbcr/status-monitoring.md) | Lets you track and update the CbCR milestone status of each Constituent Entity for the selected period. You can filter CEs by jurisdiction, search the table, and change milestone statuses individually or in bulk. |
| [Import](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/cockpit-cbcr/import.md) | Lets you load CbCR data from one of four sources. The sub-folder contains a separate workspace for each source: • **Income Taxes:** copy values from the Income Taxes module • **Questionnaire Value Transfer:** transfer field values from a CbCR Questionnaire • **External:** import from an external file • **Period copy:** copy all CbCR data from another period You can import data for an individual Constituent Entity or run the import for all CEs at once. |
---
---
title: "Cockpit"
description: "The Cockpit folder offers the option to monitor and change milestones, and execute imports from various sources."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/cockpit
language: en
last_updated: 2026-05-01
---
# Cockpit
## Overview
The **Cockpit** folder offers the option to monitor and change milestones, and execute imports from various sources.
To do so, the **Cockpit** provides the following workspaces:
- [Status Monitoring](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/cockpit/status-monitoring.md)
- [Import](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/cockpit/import.md)
---
---
title: "Comments"
description: "Comments in Income Taxes are additional explanations of individual rows, workspaces, or forms. Comments can contain text or file attachments. Furthermore, in many cases it is optionally possible to transfer data to the tax calculation using the Comments function."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/comments
language: en
last_updated: 2026-05-28
---
# Comments
## Overview
**Comments** in Income Taxes are additional explanations of individual rows, workspaces, or forms. Comments can contain text or file attachments. Furthermore, in many cases it is optionally possible to transfer data to the tax calculation using the **Comments** function.
## Navigation
The **Comments** workspace is opened under **Company | Comments**.
The **Comments** workspace is displayed, for example, as follows:
'Comments' workspace
> **Note:** For quicker administration, comments can be edited also directly in the relevant areas.
>
> When working with a specific **form**, you will find the **Comments** button directly on the form. You can view all form-related comments, create new comments, and administer existing comments there. The same functionality is available also in workspaces.
>
> New comments must be created always in the workspace or form that contains the target field for the data transfer.
>
> After creating a comment, a comment icon appears next to the target field. The information stored in the comment is displayed by clicking the icon. Once a comment has been created, it is displayed in the central **Company | Comments** workspace, where it can be administered there.
## Options
The following options are available in the **Comments** workspace:
| Option | Description |
|---------|---------|
| Create comment | Opens a dialog in which a new comment can be created (see section [Creating Comments](#createcomment)). |
| Show prior periods | With **Show prior periods**, you can also display comments from previous periods in the context of the current company. Comments from other periods can only be viewed, not edited. |
| Show elster protocols | With **Show elster protocols**, all file attachments generated as part of the electronic submission are also displayed. These types of comments can be deleted only if they do not need to be retained for compliance reasons. If you still attempt to delete such a file attachment, you will receive a corresponding error message. |
## Creating comments
When you click **Create comment**, the **Comments and attachments** dialog is displayed:
'Comments and attachments' dialog
When creating a comment, file attachments (e. g. a PDF file) can also be stored in addition to specifying an amount and a free-text field for remarks. The individual fields are described in the following table:
#### Category
The current workspace is entered here automatically. **Other comments** is displayed here if the record is created in the **Comments** workspace.
#### Subcategory
The relevant row from the current workspace is chosen here.
This property is a free text field in the **Comments** workspace.
#### Context/column
The assignment is made here if a workspace consists of several columns (e.g. partners, sectors).
#### Amount
Optionally, an amount can be entered that is to be explained with this comment.
#### Amount from excel-attachment
The value is to be determined from the stored Excel file and imported if this selection field is activated. For details, see below.
#### Comments
A brief explanation (maximum 255 characters) can be entered here.
#### Attachments
In some cases, the documentation may be in a separate document. Click the gray-shaded field to upload a file.
To upload a value from the document into Income Taxes, you must upload an Excel file.
Otherwise, the allowed file types will be specified by the Income Taxes administration.
#### Get Data
The amount is transferred directly to the tax calculation row if this field is activated.
> **Warning:** The **Get Data** check box is visible only if a comment is created in a workspace or form that also contains a target field.
> **Note:** **Take over all data**
>
> You can find the **Take over all data** button in the **Kommentare und Anhänge (Comments and Attachments)** dialog of the respective workspace or form. This button allows you to transfer all available comment data at once to the workspace or form currently open.
---
---
title: "Companies"
description: "In the Companies workspace, the companies created in the selected period are displayed."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies
language: en
last_updated: 2026-09-29
---
# Companies
## Overview
In the **Companies** workspace, the companies created in the selected period are displayed.
> **Tip:** The key attributes of a company, such as the assigned country, legal owner, or legal form, are displayed directly in the company overview. If you would like to view all information about the companies, go to **Reporting / Tax Reports** and run the **Companies** report there.
## Navigation
The **Companies** workspace can be opened under **Master Data | Companies**. The **Companies** workspace is displayed as follows, for example:
Workspace 'Companies'
## Creating a Company
To create a new company, click **Create** in the **Companies** workspace and configure the tabs displayed (see the following subheadings).
> **Note:** Please note:
>
> **Required fields** are indicated by a **red** asterisk. Information required for **tax declarations** is indicated by a **blue** asterisk. This also applies to master data collected for the transmission of e-balance sheets. This data can be copied into the **Tax Balance** module via a web service interface.
>
> Essential master data must be stored on the **Company data** tab. The other tabs are mainly intended for electronic tax declarations and **electronic reporting to German tax authority**, which is why they will not be discussed in detail below.
## 'Company Data' Tab
The tab is displayed as follows, for example:
'Company Data' tab
**Copy based on**: This field only appears when creating a new company; it supports the transfer of data from companies already entered in Income Taxes.
Select the desired source period and company from the drop-down lists and then click **Copy now** to transfer the master data into the new company to be created.
Please note that the following master data will not be copied, so you will need to complete it:
- Assignment ownership to parent company
- Assignment of companies to be converted
- Reporting dimensions
- Allocation of position mapping
- Allocation of the connection information
- Interfaces
### General Information
#### ID *
The ID uniquely identifies a company. Up to 20 characters can be used (letters and numbers). The ID can only be assigned once and cannot be changed afterwards (applies across periods). The Unit-ID should match other relevant accounting systems (e.g. SAP) to ensure the functionality of any potential interfaces.
#### Name *
The name of the company should include the legal form. This is required when submitting tax declarations with Income Taxes.
#### Shortname
Entering a short name is optional. Keeping things consistent with other relevant accounting systems is also advisable here. The use of short names (e.g. SAP company abbreviations) can be useful for evaluation purposes or reports.
#### Legal form type *
The legal form can be selected from a list.
The tax calculation dialogs displayed in the **Company** function area are, in some cases, dependent on the selected legal form. For example, dialogs for determining tax bases are displayed only for partnerships.
#### Additional company codes
Additional company code IDs can be listed here if they are relevant for importing transaction data.
#### Country *
For “Country (Nation)”, select the country in which the company is headquartered or its management is based. Data sets from the master data dialog **Countries** are available for selection. The tax rates and exchange rates of the selected country are used for tax calculation and to convert the currencies of reports into the reporting currency of the company in question.
#### Materiality
This field indicates the materiality of the company and can, for example, affect the scope of questions in Tax Questionnaire or the degree of automation when performing bulk imports for tax calculation.
Materiality is also factored into the configuration of the workflow bot for single companies.
#### Tax number
A tax number is required for German companies if tax declarations are also to be sent electronically with Income Taxes.
The unified federal schema consists of:
**FFFF**: four-digit tax office number
**0**: 0 (by definition)
**BBB**: three-digit district number (NRW: four digits)
**UUUU**: four-digit distinction number (NRW: three digits)
**P**: single check digit
**Example:** FFFF0BBBUUUUP - 9198058870707
#### Local tax office
The specification of a local tax office is required for German companies if tax declarations are to be sent electronically with TCR.
The tax authority responsible is automatically determined based on the tax number (the first four digits).
The tax office numbers (F)FF are extended to four digits for the Elster tax number format.
##### Tax Office Numbers
- Baden-Württemberg 28F
- Bayern 9FFF
- Berlin 11FF
- Brandenburg 3FFF
- Bremen 24FF
- Hamburg 22FF
- Hessen 26FF
- Mecklenburg-Vorpommern 4FFF
- Niedersachsen 23FF
- Nordrhein-Westfalen 5FFF
- Rheinland-Pfalz 27FF
- Saarland 1FFF
- Sachsen 3FFF
- Sachsen-Anhalt 3FFF
- Schleswig-Holstein 21FF
- Thüringen 4FFF
#### Business tax ID number
A business tax ID number uniquely identifies your company with tax authorities and other government agencies. It facilitates communication with the authorities and can help simplify and automate tax processes in the future. Business tax ID numbers are assigned by Germany's Federal Central Tax Office.
#### Tax number of the Federal Central Tax Office (BZSt)
A tax number from the Federal Central Tax Office (BZSt) is required for tax declarations and the reporting of withholding tax.
#### Business activity / Business area
This entry is optional and serves as an extension of possible filter options within the Reports and Excel views. For example, the view in the **Company** workspace can also be sorted by business area. This attribute should not be confused with reporting dimensions.
In addition, the information is used in tax declarations.
#### Local tax/local tax rate
Here, a distinction is made between companies that are coded to the country **Germany** and companies that are coded to **foreign countries**.
This value is used solely for the calculation of current taxes and does not apply to the calculation of deferred taxes.
**Germany:**
In this field, the local tax rate (e.g. 250%, 400%) is entered, which, together with the state tax rate (this is entered in the **Countries** area), leads to the effective tax rate.
Alternatively, in the **Company** function area within the **Basis data** workspace, a different local tax rate can also be specified. By default, the tax rate from the master data is used and applied for the calculation of local tax (group tax relief).
**Outside of Germany:**
For foreign companies, the local income tax rate must be entered.
This value is used as the proposed value for the second foreign income tax (local tax). To account for local tax rates that vary by region, a different tax rate can also be specified under **Current Taxes |** **Local Tax (Gewerbesteuer)**.
In principle, for the calculation of profit tax expenses at companies in foreign countries, the option **Local tax column in Toolbox** must be activated for the respective company in the **Company** workspace.
#### Additional information
Here, you can enter further information about the company in a free text field.
This field is also displayed under **Company | Basis data** so that the notes are directly available to the user.
#### Comment (internal)
This field is for entering further information that should only be accessible to authorized users in the **Master Data** functional area.
### Tax Office Numbers
- Baden-Württemberg 28F
- Bayern 9FFF
- Berlin 11FF
- Brandenburg 3FFF
- Bremen 24FF
- Hamburg 22FF
- Hessen 26FF
- Mecklenburg-Vorpommern 4FFF
- Niedersachsen 23FF
- Nordrhein-Westfalen 5FFF
- Rheinland-Pfalz 27FF
- Saarland 1FFF
- Sachsen 3FFF
- Sachsen-Anhalt 3FFF
- Schleswig-Holstein 21FF
- Thüringen 4FFF
### Fiscal Year
These fields only need to be maintained if two fiscal years end within a calendar year (please note that this scenario cannot be accounted for properly in Income Taxes). In all other cases, no entry is necessary here.
An automatic connection to the main form ESt 1 B (as of 2024: row 41) for partnerships does not exist, as the fields are not identical in content. A non-calendric fiscal year must always be entered in form ESt 1 B if, in the case of a partnership, the fiscal year does not correspond to the calendar year.
### Current Tax Charge – Group Data
The tax group structure stored in Income Taxes applies for both corporate income tax and business tax purposes. In addition, information regarding the tax group is also relevant for electronic tax declarations. Depending on the settings, different tax forms are enabled in some cases (e.g. the **OG enclosure** for members and the **Tax Payer of Group enclosure** for parent companies).
#### Type of tax payer *
This feature stores the current tax charge structure in the master data.
#### Tax payer of group *
If a company is defined as a member or intermediate parent, the tax payer of the group must be specified in this row.
The selection list contains companies for which the type of tax payer has been set as **Tax payer of group** or **Interm. parent**. For a tax payer of a group or a standalone company, the entry **(---)** should be selected.
#### Neutral recognition of the balancing item for tax group
If this function is activated, no neutralization of expense/income arising from the reversal or creation of balancing items as defined in § 14, para. 4 KStG and considered in the earnings determination will be made on the part of the tax payer of the group. This is because the tax payer of the group does not take the change in the balancing item into account in the correction (pursuant to § 60, para. 2(1) EStDV) to adjust the local balance to the tax balance. By default, this check box is not activated (recommended).
#### Company
Description
#### German company
- The values determined for the local taxes of tax group companies as part of a tax calculation are allocated to the (interim) group parent in order to calculate tax for the consolidated group. The allocated values are displayed under **Actual Taxes | TB Transfer** for each group member.
- If the **Deliver deferred taxes** function is activated for members, deferred taxes are forwarded to the tax payer of the group (the “formal approach”). The respective deferred taxes received and transferred are displayed under **Deferred Taxes | Summary**.
- The closing of the milestones **Current Taxes** and **Deferred Taxes** is only possible for (interim) tax payers of groups if all direct subsidiaries have completed their processing, i.e. the milestone is set to the status **Completed** or **Audited**.
#### Foreign company
- The values determined for tax group companies as part of a tax calculation are allocated to the tax payer of the group for the group's tax calculation. The allocated values are displayed in the Tax Group dialog for each member.
- In the actual tax calculation, additional rows are displayed to record the allocations received from tax group members from the **Tax Group** dialog and to determine the tax expenses for the overall tax group, or to make it possible to utilize/increase losses of the overall tax group.
- Closing the milestones **Current Taxes** and **Deferred Taxes** is only possible for the tax payer of the group if all direct members have completed their processing, i.e. the milestone is set to the status **Closed** or **Audited**.
> **Note:** The **Tax Group** workspace is only displayed for foreign tax payers of groups.
The characteristic **Tax payer of group**(or **Interm. parent**– ZOT) has the following effects (among others):
### Application Parameter
The **Application parameter** blocks include various settings of the company in question that directly influence the calculation of tax. Depending on the setting selected here, calculations in the area of the company will be performed differently.
**Application parameter** area:
#### (Sub-) Group
This check box controls whether the company is a (sub-)group in which the values of the dependent single companies (and, if applicable, further sub-groups) are aggregated. The determined values can be extended by consolidation measures.
Additionally, the company also has access to the **(Sub-)Group** functional area. In this area, the work progress of the dependent or subordinate companies can be monitored based on the milestones. The aggregation of company data for the purposes of TRR and other notes is also performed in this area. The characteristic **(Sub-)Group** is also a selection criterion for reports.
When you activate this check box, two more options will be displayed:
- including balancing (Accounting standard: IFRS)
- including balancing (Accounting standard: Commercial Law)
#### Local tax is deductible for corporate tax
- This field has not been relevant for German companies since 2008.
- The setting has a corresponding effect on foreign tax calculation (Toolbox).
- In Swiss tax calculations, the setting affects the calculation of row 74 in the workspace **Net Profit**.
> **Note:** The **Net Profit** workspace is only displayed if Swiss tax law is activated and **Swiss tax law** has been set in the [Countries](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries.md) master data for the company. To **activate** Swiss Tax law, please get in touch with your Lucanet contact person or use the [contact form](https://www.lucanet.com/en/contact/).
#### Balance type Local/IFRS (optional)
By default, the setting **(---)** should be chosen here. In order for the partial workspace **Local GAAP/Tax Balance** to be available at the company level, the balance type Local GAAP must be selected for German companies. This master data characteristic is not relevant for foreign companies (the setting has no impact).
The dialog **Local GAAP/Tax Balance** can be used if the tax balance surplus/deficit is to be determined in a balance sheet structure that deviates from the regular folder **B/S Comparison**. The use of this functionality requires separate maintenance of the local GAAP balance sheet structure within the master data.
> **Warning:** The setting is only available when working with the **Local balance sheets** function in Income Taxes.
#### Tax Allocation Calculation
Selection of the calculation of tax assessments (current taxes) for the calculation of tax in the current period (not late adjustments).
This option applies to both German and foreign companies. The function does not refer to deferred taxes (for this, the **Deliver deferred taxes** function is available). By default, tax allocation calculation is deactivated.
Tax allocation calculation must be considered in connection with the income tax group. Tax assessments are only applicable in these cases. Therefore, the following comments must be observed:
##### Type of Tax Payer: Standalone (Germany)
Allocations are not calculated for German companies that are subject to independent taxation. The activation has no impact on the tax calculation under **Current Taxes**.
##### Type of Tax Payer: Standalone (Foreign Countries)
For independently taxable foreign companies, activation leads to the determination of a tax assessment. This is why allocation must not be activated.
In exceptional cases, an allocation may also be necessary for independently taxed companies, e.g. if a negative external tax is to be calculated. However, a manual reclassification via the partial workspace **Current Taxes** must then be made to the external tax expense.
##### Type of Tax Payer: Member / Interm. Parent (Germany and Foreign Countries)
If tax allocation calculation is activated, an allocation is calculated for both the first tax type (Local Tax) and the second tax type (Corporate Income Tax), and the tax is attributed to the tax payer of the grup.
By default, both business tax and corporate income tax are deactivated (see figure above). If an allocation is to be calculated for only one tax type, **Deactivated** must be selected and only the check box for the tax for which no allocation should be determined should be checked.
If an allocation is activated, the tax expense/income will be displayed under the allocations in the summary of tax expenses in the partial workspace **Current Taxes**.
##### Type of Tax Payer: Tax Payer of Group (Germany)
Allocations are not calculated for tax payers of groups. Activation has no effect on tax calculation in the partial workspace **Current Taxes**.
##### Type of Tax Payer: Tax Payer of Group (Foreign Countries)
Tax allocation calculation must be activated for the tax payer of the group. This results in the tax payer of the group determining a negative tax in the case of a negative result. On this basis, it can be determined whether an LCF exists after the tax expense of the tax group is offset. The current tax charge is displayed as a third-party tax and not as an allocation.
#### Discont. Operation
This attribute should be selected if the requirements for an outgoing business segment are met (e.g. in accordance with IFRS 5). This field does not affect calculations in Income Taxes, but it can be used as a selection criterion for reporting purposes.
#### Deliver deferred taxes
This attribute controls whether members deliver deferred taxes to the tax payer of the group (the **“formal approach”**). Ensure that the company is assigned a tax payer of the group or an intermediate parent. The transfer and receipt of deferred taxes are displayed under [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md).
**Partnership:**
In addition, the function also serves to transfer deferred taxes from a partnership to the partners. If the attribute is set for a partnership, the portion of deferred taxes attributable to corporate income tax is passed on proportionally to the partners.
#### Netting of deferred taxes (Accounting standard: IFRS)
In IFRS periods, the following options for the offsetting of deferred taxes are available:
- Without Netting
- Netting (maturity)
- Netting (types of taxes without maturity)
#### Netting of deferred taxes (Accounting standard: Commercial Law)
According to local GAAP, companies have the option to offset for the purposes of deferred taxes.
If the check box is activated, the option to offset under commercial law is applied so that deferred taxes are netted in the **Summary** workspace. In addition, the exercise of the option is displayed.
> **Warning:** This setting is only available in cases involving a commercial law period.
#### Option
Description
#### Edit Balance Sheet Comparison manually
Data in [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md) can be specified both automatically (via interface) and manually.
If this check box is activated, the balance sheet comparison can be edited manually. This applies to both the data input and any possible reclassifications of automatically imported balance sheet values. By default, the option is activated, allowing you to edit B/S comparisons.
#### No local Balance
Here, foreign companies have the option to hide the columns for local GAAP balance sheets in the **B/S Comparison** workspace. This is useful when the local GAAP balance sheet is always identical to the IFRS balance sheet for the company in question.
> **Warning:** This setting is only available in cases involving an IFRS period.
#### Additional tax
This drop-down list is available exclusively to foreign companies. This option also refers to the **B/S Comparison** workspace and enables the display of an additional table sheet.
This is appropriate for companies that, deviating from the average tax rate, must recognize deferred taxes based on an additional assessment base.
#### Asset/property management or trust company
This function is only relevant for German partnerships. The attribute makes it possible to map the tax calculation of a partnership transparently for the partner (shareholder) in question. All local tax additions and deductions are allocated directly to the partner. Calculation of the interest capping rule is also not active. Interest and depreciation are reported solely to the partner.
For non-affected companies, select **Standard**.
For the partner, an additional column appears in the **GewSt1A** showing the local tax modifications of the subordinate asset/property management company or trust company as an addition to their own value **.**
> **Warning:** Please note that this function is currently only available in periods using the 2017 form set.
#### Column for local tax in Toolbox
This function is only relevant for foreign companies.
Activate it to display a column for **local tax** (or local income tax) in the [Actual Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes.md) workspace along with the calculation of corporate income tax.
The use of this function is appropriate when the two profit tax expenses use a different assessment basis. Using the new column **Local tax**, the tax base can be developed starting from profit before tax in accordance with local GAAP and evaluated using the local tax rate stored in the master data.
#### Limited taxable
Starting from the 2016 assessment period, it is possible for corporations with limited tax liability to submit a tax declaration.
#### Change of currency
If a company changes its functional FX code, this can be selected with this check box. The company will then be treated as a new company without prior period values.
#### Current tax liabilities and assets
This check box enables use in the **Tax liabilities** workspace.
#### Applicability of “Konzernklausel” (§ 4h, para. 2(1)(b) EStG)
This option is only relevant for German companies for purposes related to **calculation of the interest capping rule**.
#### Applicability of “Escapeklausel” (§ 4h, para. 2(1)(c) EStG)
This option is only relevant for German companies. If it is activated, the exception clause (or “escape clause”) found in § 4h, para. 2(1)(c) of the EStG will be taken into account when determining non-deductible interest expenses in the **Company** functional area under **Attachment A**.
#### Option to capitalise (active deferred taxes)
This option only applies to periods for which **commercial law** has been selected as the accounting standard. According to § 274 of the local GAAP, there is an option to capitalize for excess deferred tax assets. The check box is used to control whether the respective company exercises the option to capitalize in such a way that deferred tax assets are recognized (when the check box is activated). If the option is activated, an active surplus is displayed in the [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md) workspace and in **Report DT**.
The exercise of commercial law options is displayed in local GAAP periods in the upper area under **Summary** and **Report DT**.
> **Warning:** This setting is only available in cases involving a commercial law period.
**Application parameter – Tax calculation (Closing v3)** area:
**Application parameter – Income tax return (Closing v3)** and **Application parameter (commercial law)** areas:
### Type of Tax Payer: Standalone (Germany)
Allocations are not calculated for German companies that are subject to independent taxation. The activation has no impact on the tax calculation under **Current Taxes**.
### Type of Tax Payer: Standalone (Foreign Countries)
For independently taxable foreign companies, activation leads to the determination of a tax assessment. This is why allocation must not be activated.
In exceptional cases, an allocation may also be necessary for independently taxed companies, e.g. if a negative external tax is to be calculated. However, a manual reclassification via the partial workspace **Current Taxes** must then be made to the external tax expense.
### Type of Tax Payer: Member / Interm. Parent (Germany and Foreign Countries)
If tax allocation calculation is activated, an allocation is calculated for both the first tax type (Local Tax) and the second tax type (Corporate Income Tax), and the tax is attributed to the tax payer of the grup.
By default, both business tax and corporate income tax are deactivated (see figure above). If an allocation is to be calculated for only one tax type, **Deactivated** must be selected and only the check box for the tax for which no allocation should be determined should be checked.
If an allocation is activated, the tax expense/income will be displayed under the allocations in the summary of tax expenses in the partial workspace **Current Taxes**.
### Type of Tax Payer: Tax Payer of Group (Germany)
Allocations are not calculated for tax payers of groups. Activation has no effect on tax calculation in the partial workspace **Current Taxes**.
### Type of Tax Payer: Tax Payer of Group (Foreign Countries)
Tax allocation calculation must be activated for the tax payer of the group. This results in the tax payer of the group determining a negative tax in the case of a negative result. On this basis, it can be determined whether an LCF exists after the tax expense of the tax group is offset. The current tax charge is displayed as a third-party tax and not as an allocation.
### Employee Data
The provision of employee data is optional and serves information purposes only. No company-specific authorizations are associated with this.
This information is useful given the fact that balance sheet data (accounting) and tax data (tax department) are often edited by different individuals. In addition, this information can also be helpful to foreign companies when using **Income Taxes**. If employee data is to be entered, a selection list with the users created in Income Taxes is displayed. These are administered separately in the master data in the **User** workspace.
### FX Code
By default, the exchange rates from the country settings are used for currency conversion in reporting. If these rates are **not** to be used for a company, they can be overwritten here with unit-specific settings. This could be applied in a case involving highly seasonal business, for example.
To use this option, activate the **Unit-specific currency** check box. Then specify the following:
- FX rate (cut-off date, RC to LC)
- Avg FX rate (RC to LC)
The proposed values show the entries from the master data for countries. The **FX code** itself is also displayed here, but cannot be changed.
### Tax Rates
By default, the tax rates from the country settings are used for calculations in Income Taxes. If these tax rates are **not** to be used for a company, you can overwrite them here with unit-specific settings.
To use this option, activate the **Unit-specific tax rates** check box. You can then specify the following:
- Corporate income tax
- Local/State tax rate
- Combined current income tax rate
- Combined deferred tax rate
- thereof, deferred tax rate local tax
- Additional tax rate
> **Note:** Please note:
>
> It is only possible to switch the tax rates to **unit-specific** in their entirety. Therefore, the tax rates that should not deviate from the country settings must also be maintained again.
### Assignment Ownership to Parent Company
The assignment of ownership to a parent company is required for purposes related to preparing consolidated financial statements, but also for calculating current taxes.
In Income Taxes, the process of merging companies within a group is based on full consolidation.
### Explanation of Unit Superiors
| Designation | Explanation |
|---------|---------|
| Legal owner | The legal owner is determined from a selection list. The list contains the companies maintained in Income Taxes for the selected period. When using Income Taxes for the first time, the highest group companies must therefore be created first. These can then be assigned to the subsidiaries as the legal owner. |
| Civil law quota (%) | For the legal form type **Partnership** _:_ Entering the civil law quota is not relevant for the purposes of tax calculation. The civil law quota is used exclusively for selected reports. |
| Basis for the distribution of taxable amounts (%) | The quota must be entered as a percentage value (a number without the percent sign). Among other things, this data is used for the graphical presentation of the group structure. The specification of investments determines the forwarding of the assessment bases of German partnerships to the partners (or shareholders), as well as the selection menu of the partner area **SupBal** (supplementary tax balance sheet) in the [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md) workspace. |
| Partner number (form sheet FB) | This information is required for the purposes of electronic tax declarations and the exporting of master data to SmartTaxBalance (number of partner from assessment declaration – form sheet FB). This information is only relevant for German partnerships. |
| Kind of partnership | The kind of partnership is to be indicated exclusively for German partnerships. This specification controls the display of the partner (e.g. a limited partner) in the § 15a EStG dialog for purposes related to the tax accounting of losses. In addition, this information is required for the purposes of electronic assessment declarations (in particular enclosure FB) and exporting master data to Tax Balance. |
| Specials of partnership | This information is only relevant for German partnerships. It must be specified whether the partner subject to the assessment is a natural person, a partnership, or a corporate enterprise. This information is required for the purposes of electronic assessment declarations (in particular enclosure FB) and exporting master data to Tax Balance. |
| Private assets | The investment is part of private assets (enclosure FB). |
| Consolidation | Activate this check box to ensure consolidation of the created/edited company within the group financial statement. The field can only be activated for a single legal owner. Companies for which the field is not activated are displayed in brackets in the graphical group view. |
### Other Information on the 'Company Data' Tab
- **Reporting dimensions**: For (optional) allocation to a reporting dimension (or dimension value), you must first create dimension values in the [Reporting Dimensions](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/reporting-dimensions.md) workspace. After creation (within the same period), the data sets will be available in the selection list.
- **Allocation of position mapping**: The unit-specific mapping for interfaces can be allocated via this area.
- **Allocation of connection information**: Connection information of the Administration page is inserted here. This can pertain to third-party FTP servers or similar that are required for the import interface.
- **Interfaces**: Interface configurations that have not been defined as the default interface can be inserted here on a unit-specific basis.
## Others Tabs
In addition to the company data described previously, other unit-specific master data can be stored on further tabs within the **Company** workspace.
- Management address
- Tax Consultancy / Participation
- Bank account
- Registrations
- Legal guardian
- Receiving agent
- Shareholder (only for corporations)
- Shareholding structure
With this information, a tax database for master data can be established. The data is only relevant for German companies. For the purposes of electronic tax declaration, some information is mandatory; these are marked with a **blue asterisk**.
## Bulk Edit
This function allows certain data sets to be changed simultaneously for a selection of companies (e.g., the local tax rate or settings regarding tax assessment).
- The companies to be changed can be chosen from a selection list. The selection list contains all companies in the period under consideration.
- In the **Change** column, the attributes to be adjusted must be marked, and in the **Values** column, the new value to be set must be specified.
- Bulk editing is then carried out using the **Execute modifications** button.
## Presentation Options
In the upper area of the **Company** workspace, you can select one of three display options:
### List
By default, the companies are displayed in a tabular list format when the dialog is opened.
### Group Structure
This display option presents master data based on the information in the **Assignment of parent companies** area. Companies for which **(Sub-)Group** is activated are highlighted in color. Companies are displayed in brackets when they have a holding relationship with a superior company, but are consolidated under a different legal owner.
Display of group structure
### Tax Group Structure
This display option presents master data based on the information in the **Current Tax Charge – Group data** area. Tax payers of groups, intermediate parent companies, and fiscal units are distinguished by their color. Companies that are not included in an income tax group are displayed on a gray background. A checkmark after the company name indicates that the option **Deliver deferred taxes** is activated for the respective company.
Display of the tax group structure
---
---
title: "Company"
description: "In the Company functional area, the calculation of current (actual) and deferred taxes for annual and monthly financial statements is carried out. The electronic tax return is also edited in this area and submitted to the tax authority."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company
language: en
last_updated: 2026-05-28
---
# Company
## Overview
In the **Company** functional area, the calculation of current (actual) and deferred taxes for annual and monthly financial statements is carried out. The electronic tax return is also edited in this area and submitted to the tax authority.
Annual and monthly financial statements are edited in **annual closing periods**, while tax returns are edited in **tax return periods**.
## Workspaces in the 'Company' Functional Area
The following workspaces are available in the **Company** functional area:
- [Status](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/status.md)
- [Basis Data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data.md)
- [Import](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/import.md)
- [Import Suite](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/import-suite.md)
- [Deferred Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes.md)
- [Audit Issues](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/bp-sachverhalte.md)
- [Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2.md)
- [KapEStA](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/kapesta.md)
- [Electronic Transmission](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer.md) (only available in tax return periods)
- [Data Transfer](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/data-transfer.md)
- [Data Export](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/data-export.md)
- [Validation](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/validation.md)
- [Comments](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/comments.md)
- [Snapshots](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/snapshots.md)
---
---
title: "Comparison View of Corrections"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/comparison-corrections
language: en
last_updated: 2026-09-28
---
# Comparison View of Corrections in Lucanet VAT
## Overview of the 'Comparison View of Corrections' Workspace in VAT
The **Comparison view of corrections** workspace in Lucanet VAT (Value Added Tax) shows two correction versions of a declaration side by side and displays the difference between the two versions. This lets you see at a glance which fields have changed between the chosen correction versions. The view is available for both the **Declaration** and the **VAT Group Return**.
## Navigation to the 'Comparison View of Corrections' Workspace in VAT
The **Comparison view of corrections** workspace can be found under **VAT | Value Added Tax | Comparison view of corrections** and is displayed as follows, for example:
'Comparison view of corrections' workspace
## Structure of the Overview in VAT
In the upper area of the **Comparison view of corrections** workspace in VAT, you choose the correction versions that you want to compare via two drop-down lists:
- **First drop-down list**: Choose the reference correction. The original declaration is not available here, because at least one correction is required as a reference.
- **Second drop-down list**: Choose the correction that you want to compare with. Only corrections with a lower number than the reference correction are available. Correction 0 corresponds to the original declaration.
> **Note:** The **Declaration type:** drop-down list is only visible for representative VAT group members and consolidated VAT group members. There you switch between the comparison view for the **Declaration** and the **VAT Group return**.
The comparison view only contains values once at least one correction has been created for the chosen company and period.
The comparison view of corrections in VAT shows the following columns:
| Column | Description |
|---------|---------|
| Row | Row number of the declaration field |
| Name | Name of the declaration field |
| Correction (reference) | Field value from the correction chosen in the first drop-down list |
| Correction (comparison) | Field value from the correction chosen in the second drop-down list |
| Difference | Difference between the values of the two corrections |
## Further Functions in the 'Comparison View of Corrections' Workspace in VAT
In addition to the [general functions](https://support.lucanet.com/en/documentation/income-taxes/vat/user-interface-general-functions.md), the following functions are available in the context menu of the three-dot icon (⋮) in the top right corner of the **Comparison view of corrections** workspace in VAT:
| Function | Description |
|---------|---------|
| Form language: DE/Form language: EN | Switches the language of the declaration form between **DE** (German), **EN** (English), or, if stored, the national language of the form. |
| Show all values/Show Only differences values | Switches between the complete view of all field values and a filtered view that only shows fields with differences between the correction versions. |
---
---
title: "Configuration"
description: "In the Configuration workspace, you can choose interfaces to be used for a period-independent, automated export."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-configuration
language: en
last_updated: 2026-05-28
---
# Configuration
## Overview
In the **Configuration** workspace, you can choose interfaces to be used for a period-independent, **automated export**.
You specify whether and at what event an automated export is to be created in the **[Structure](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-structures.md)** workspace under **[Precondition for export](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-structures.md#trigger)** .
> **Warning:** - An automated export is available only for interfaces with the **Export** direction and the **Custom Report** interface type.
> - The **Configuration** workspace is required only for this use case. In all other cases, interfaces are defined on a period-dependent basis in the **[Structure](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-structures.md)** workspace.
## Choosing an Interface for Automated Export
The **Configuration** workspace is displayed, for example, as follows:
General configuration of an interface
To configure an interface for automated export, specify the following:
| Option | Description |
|---------|---------|
| **Period** | Tax return period for which the automated export is to be created |
| **Export-Templates** | This entry is not required and can be left empty. |
| **Export Interfaces** | Selection of the export interface to be used for the automated export of a report. Only interfaces with the **Export** direction and of type **Custom Export** are available for selection, for which [preconditions for export](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-structures.md#trigger) have been defined in the **Structure** workspace. |
> **Warning:** All other fields in the **Configuration** workspace are not relevant and do not need to be configured.
---
---
title: "Configuring Appropriation of Net Income"
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-profit-appropriation
language: en
last_updated: 2026-07-27
---
# Configuring Appropriation of Net Income
## Overview
Under German commercial law, the annual financial statements of a corporation or of a (commercial) partnership as defined in Section 264a HGB (German Commercial Code) allow two variants for presenting the net income for the year in equity.
- **Variant 1** – Balance sheet before appropriation of the net income for the year
- **Variant 2** – Balance sheet with partial or full appropriation of the net income for the year (Section 268 (1) HGB)
In the context of the e-balance sheet (E-Bilanz), both presentations are relevant, because they lead to different requirements for the taxonomy items used. If the balance sheet is prepared with partial or full appropriation of the net income (**Variant 2**), you must configure and enter the **Appropriation of net income** report element in **Tax Balance**. This chapter describes how to proceed.
## Variants for Presenting the Net Income for the Year
Two variants are available for presenting the net income for the year in equity, each of which requires different taxonomy items:
- **Variant 1** – Balance sheet before appropriation of the net income for the year
- **Variant 2** – Balance sheet with partial or full appropriation of the net income for the year (Section 268 (1) HGB)
| Variant | Legal form | Balance sheet item in equity |
|---|---|---|
| Variant 1 | Corporation (KapG) | Net income/net loss for the year (`bs.eqLiab.equity.netIncome`) |
| Variant 1 | (Commercial) partnership (PersG) | Net income/net loss for the year (`bs.eqLiab.equity.netIncomePartnershipsHGBs264c`) |
| Variant 2 | Corporation (KapG) | Net retained profits/net accumulated loss (`bs.eqLiab.equity.profitLoss`) |
| Variant 2 | (Commercial) partnership (PersG) | Net retained profits/net accumulated loss (`bs.eqLiab.equity.profitLossPartnershipsHGBs264c`) |
> **Note:** The **Appropriation of net income** report element (`incomeUse`) is mandatory if the core and supplementary taxonomy is used (see the BMF (German Federal Ministry of Finance) letter of September 28, 2011, annex to margin no. 11) – even if the e-balance sheet is submitted as a pure tax balance sheet.
According to the prevailing opinion, the equity items **net income/net loss for the year** and **net retained profits/net accumulated loss** must not be changed for tax purposes, because they are items under commercial law. The tax surplus/deficit (Section 60 (2) EStDV) is therefore reported in the balance sheet item **Equity, tax adjustment item** (`bs.eqLiab.equity.netIncome.taxBalanceGenerally`), irrespective of the legal form and irrespective of how the net income for the year is presented. In **Tax Balance**, this procedure is preset in the [Tax Balance Sheet Settings](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-tax-balance-settings.md) workspace.
The following sections describe the settings to be taken into account if the balance sheet is prepared with appropriation of the net income for the year (**Variant 2**). They assume that a commercial balance sheet with a tax reconciliation is submitted.
## Configuring GCD Master Data
In the GCD master data, you specify whether the balance sheet reports the net retained profits/net accumulated loss and whether the appropriation of net income is submitted as a separate report element.
To do this, open the [tax balance sheet](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/open-tax-balance.md) you want to edit and, under **GCD Master Data** | **Report Elements**, set the **Income statement ends with net retained profits / accumulated loss** option (`genInfo.report.id.incomeStatementendswithBalProfit`) to **Yes**.
If you use the core and supplementary taxonomy, also set the **Appropriation of net income** entry (`genInfo.report.id.reportElement.reportElements.EV`) to **Yes**. If the balance sheet was prepared in accordance with Section 268 (1) HGB, the tax authorities require a statement of appropriation of net income.
> **Warning:** If you use special taxonomies (for example taxonomies for banks or insurance companies), the **Appropriation of net income** entry must not be set to **Yes**. Instead, enter the corresponding P&L items as described in the section [Special Procedure for Special Taxonomies](#special-procedure-for-special-taxonomies).
Configuring the appropriation of net income in the GCD master data
All other report elements of the **GCD Master Data** are described in the article [Managing GCD Master Data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/gcd-master-data.md).
## Configuring Taxonomy Items
In the **Company** | **Tax Balance Sheet Settings** | **Taxonomy items** workspace, you specify how the net retained profits/net accumulated loss are transferred between the report elements and which taxonomy items are used for this. If you use the **core and supplementary taxonomy**, the following options are relevant for the appropriation of net income:
| Option | Description |
|---|---|
| **Activate automatic transfer between income statement and balance sheet** | Controls whether the net retained profits/net accumulated loss are transferred automatically from the **Appropriation of net income** report element to the **Balance sheet** report element.
With **Yes**, the transfer is automatic.
With **No**, the net retained profits/net accumulated loss must be assigned manually as an account under **Company** \| **Mappings** to the corresponding taxonomy item (`bs.eqLiab.equity.profitLoss` or `bs.eqLiab.equity.profitLossPartnershipsHGBs264c`). If no suitable account exists, create a manual account and then assign it. |
| **Net income recognized in equity** | If the net income is appropriated, the taxonomy item for the net income for the year must be changed to **net retained profits/net accumulated loss**. Depending on the legal form, select the item **Equity, net retained profits/net accumulated loss(balance sheet)** (`bs.eqLiab.equity.profitLoss`) or **Equity, net retained profits / net accumulated loss for the financial year (balance sheet) of partnerships** (`bs.eqLiab.equity.profitLossPartnershipsHGBs264c`). |
| **Activate automatic transfer for the appropriation of profit** | Controls whether the net income/net loss for the year is transferred automatically from the **Income statement** report element to the **Appropriation of net income** report element as the starting figure.
With **Yes**, the transfer is automatic.
With **No**, the net income/net loss for the year must be assigned manually to the statement of appropriation of net income under **Company** \| **Mappings**. If no suitable account exists, create a manual account and then assign it. |
| **Net income/net loss for the year in the appropriation of net income** | Is set automatically. No adjustment is required. |
| **Net retained profits/net accumulated loss in the appropriation of net income** | Is set automatically. No adjustment is required. |
Options for the appropriation of net income in the tax balance sheet settings
>
> **Note:** **Notes on configuration**
>
> - To select a taxonomy item, click **Actions** | **Choose item** in the relevant field and then navigate to the item you want in the tree structure.
>
> the shows actions > 'choose item' command in a field in taxonomy items section icon
> Selecting a taxonomy item with the 'Choose item' command
>
> - You do not have to configure the tax balance sheet settings again for every tax balance sheet. In the **More actions** menu in the top right corner of the **Tax Balance Sheet Settings** workspace, you can apply the settings from the previous year with the **Apply from the previous year** command.
> - All other options of the **Tax Balance Sheet Settings** are described in the article [Configuring Tax Balance Sheet Settings](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-tax-balance-settings.md).
## Configuring the Balance Sheet and the Statement of Changes in Capital Accounts
If the **Income statement ends with net retained profits / accumulated loss** option (`genInfo.report.id.incomeStatementendswithBalProfit`) is set to **Yes** in the GCD master data, the following conditions apply to the **Balance sheet** and **Statement of changes in capital accounts** report elements (see the technical guide to the e-balance sheet, section B.9.1.1):
#### Balance sheet
In the **Balance sheet** report element, the following items must not be reported with a value or submitted as part of the e-balance sheet:
- **Equity, net retained profits / net accumulated loss for the financial year (balance sheet) of partnerships** (`bs.eqLiab.equity.netIncomePartnershipsHGBs264c`)
- **Equity, net income/net loss for the financial year (balance sheet), corporations** (`bs.eqLiab.equity.netIncome`)
- **Equity, retained profits/accumulated loss (balance sheet) brought forward of (commercial) partnerships** (`bs.eqLiab.equity.retainedEarningsPartnershipsHGBs264c`)
- **Equity, retained profits/accumulated loss brought forward of corporations** (`bs.eqLiab.equity.retainedEarnings`)
- **Equity, surplus of unappropriated funds** (`bs.eqLiab.equity.SurplusOfUnspentFunds`)
#### Statement of changes in capital accounts
In the **Statement of changes in capital accounts** report element (`kke`), for the combination of dimension values **Tax reconciliation** (`dim_taxTrans`) = **Tax base** (`dim_taxBal`), values may only be reported for the following characteristics of the **Kinds of capital accounts** dimension (`dim_kindsOfEquityAccounts`) if the partner or co-entrepreneur concerned has an **Opening balance capital account** (`table.kke.sumEquityAccounts.sumYearEnd.begin`) other than 0:
- **Net income/net loss for the financial year (balance sheet) of (commercial) partnerships** for general partners (`table.kke.allKindsOfEquityAccounts.unlimitedPartners.netIncomeLoss`)
- **Net income/net loss for the financial year (balance sheet) of partnerships** for limited partners (`table.kke.allKindsOfEquityAccounts.limitedPartners.netIncomeLoss`)
- **Retained profits / accumulated loss brought forward (balance sheet) of (commercial) partnerships** for general partners (`table.kke.allKindsOfEquityAccounts.unlimitedPartners.retainedProfitLoss`)
- **Retained profits/accumulated loss (balance sheet) brought forward of partnerships** for limited partners (`table.kke.allKindsOfEquityAccounts.limitedPartners.retainedProfitLoss`)
Otherwise, the **Closing balance of equity capital account** (`table.kke.sumEquityAccounts.sumYearEnd`) must be 0 for the respective combination.
> **Note:** As a rule, the account types **net income/net loss for the year** and **retained profits/accumulated loss brought forward** should not be submitted with a value either for limited partners (Kommanditisten, Teilhafter) or for general partners (Komplementäre, Vollhafter). An exception applies only if the opening balance of these account types is other than 0.
## Mapping Accounts for the Appropriation of Net Income
The **Appropriation of net income** report element (`incomeUse`) starts with the **net income/net loss for the year** (`incomeUse.gainLoss.netIncome`) as the starting figure and leads via several arithmetically linked sub-items to the **net retained profits/net accumulated loss** (`incomeUse.gainLoss`).
> **Tip:** The taxonomy visualization provided by the tax authorities at [www.taxonomie.hessen.de](https://www.taxonomie.hessen.de) helps to distinguish arithmetically linked items from purely explanatory disclosures. In addition, some items are only relevant for certain legal forms, for example **Capital contributions in reporting period** (`incomeUse.deposits`) and **Capital withdrawals in reporting period** (`incomeUse.withdrawals`) for a KGaA and for entities other than corporations.
>
> For example, the arithmetic link of the item **Bilanzgewinn / Bilanzverlust** (net retained profits / net accumulated loss) in the appropriation of net income is presented as follows:
>
> the shows arithmetic link of item bilanzgewinn / bilanzverlust (net retained profits / net accumulated loss) on www.taxonomie.hessen.de icon
> Visualization of the taxonomy item 'Bilanzgewinn / Bilanzverlust'
In practice, the statement of appropriation of net income can only rarely be entered exclusively on the basis of the accounts imported from the trial balance (Summen- und Saldenliste). Therefore, under **Company** | **GAAP Reports** | **Accounts**, create manual accounts if required and then assign them to the taxonomy items of the appropriation of net income. You can choose the account number and description freely.
Creating a manual account for the appropriation of net income
How to create and assign accounts manually is described under [Maintaining GAAP Reports](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/maintain-gaap-reports.md).
## Special Procedure for Special Taxonomies
If you use special taxonomies (for example taxonomies for banks or insurance companies), the **Appropriation of net income** report element (`incomeUse`) must not be announced.
If the item **Income statement ends with net retained profits / accumulated loss** (`genInfo.report.id.incomeStatementendswithBalProfit`) is set to **Yes**, the corresponding P&L item for the net retained profits/net accumulated loss must be reported with a value instead (see the technical guide to the e-balance sheet, section B.9.1.1):
| Taxonomy type | P&L item | Taxonomy item |
|---|---|---|
| Taxonomy for banks | 34. Net retained profits/net accumulated losses | `isBanks.gainLoss` |
| Taxonomy for insurance companies | 21. / 18. / 22. Net retained profits/net accumulated losses (P&L) / 18. Adjustment item | `isIns.gainLoss` |
## ERiC Validations When Submitting the E-Balance Sheet
If the item **Income statement ends with net retained profits / accumulated loss** (`genInfo.report.id.incomeStatementendswithBalProfit`) is set to **Yes** in the GCD master data, ERiC performs the following checks when the e-balance sheet is submitted (see the technical guide to the e-balance sheet, section B.14.3.2.3.4.2):
**Check 1**
Balance sheet → Equity, net retained profits/net accumulated loss (balance sheet) for corporations (`bs.eqLiab.equity.profitLoss`) or for partnerships (`bs.eqLiab.equity.profitLossPartnershipsHGBs264c`)\
**=** Appropriation of net income → Net retained profits/net accumulated loss (P&L) (`incomeUse.gainLoss`)
This check ensures that the net retained profits/net accumulated loss submitted in the statement of appropriation of net income (`incomeUse.gainLoss`) match the balance sheet item of the same name, **net retained profits/net accumulated loss** (`bs.eqLiab.equity.profitLoss` for a KapG, `bs.eqLiab.equity.profitLossPartnershipsHGBs264c` for a PersG).
**Check 2**
Appropriation of net income → Net retained profits/net accumulated loss (P&L); Net income/net loss for the financial year, appropriation of net profit (`incomeUse.gainLoss.netIncome`) **+** Balance sheet → Equity, tax adjustment item, reconciliation difference tax accounts to financial statements in current year (`bs.eqLiab.equity.netIncome.taxBalanceGenerally.transferDiffTaxAccounts`)\
**=** Income statement → Net income/net loss for the financial year (`is.netIncome` or `ismi.netIncome`)
This check ensures that the sum of the net income/net loss for the year from the statement of appropriation of net income (`incomeUse.gainLoss.netIncome`) and the tax surplus/deficit from the balance sheet (`bs.eqLiab.equity.netIncome.taxBalanceGenerally.transferDiffTaxAccounts`) matches the net income/net loss for the year in the income statement (`is.netIncome`) after the tax reconciliation has been processed.
---
---
title: "Configuring Functions"
description: "In the Functions workspace, important tax tools are provided to correctly reflect complex issues, such as tax groups, partnerships, special business assets, and reorganizations in the system, and make automatic calculations and adjustments."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions
language: en
last_updated: 2026-05-28
---
# Configuring Functions
## Overview
In the **Functions** workspace, important **tax tools** are provided to correctly reflect complex issues such as tax groups, partnerships, special business assets, and reorganizations in the system and make automatic calculations and adjustments.
These include the following functions:
- **Documents**: You can use these functions to upload, link, or manage relevant documents, such as tax documents, working documents, or external certificates.
- **Tax Group Function**: This function provides support in determining the surplus or deficit within and prior to the tax group. It enables the automatic generation of tax adjustments for the investment book values of the tax group in the tax balance sheet of the tax group parent.
- **Trust Model**: Using this function, you can create or update tax adjustments based on the tax balance sheet data of a trust company. During the configuration, you can select the trust company's tax balance sheet and target adjustment level, and choose the relevant Balance Sheet and Income Statement positions. The corresponding tax adjustments are then created or updated.
- **Mirror image method**: The function enables the automatic generation of tax adjustments for the valuation of investments in partnerships according to the so-called mirror image method.
- **Transfer to special business assets**: This function enables the creation and updating of special balance sheet issues based on tax adjustments in the balance sheet of the affected shareholder.
- **Reorganizations**: This function assists you with the tax accounting adjustments required for the entities involved in the reorganization. In this process, the assets and liabilities of the transmitting entity are automatically reflected in the balance sheet of the receiving entity. Detailed information on configuring reorganizations can be found in [Configuring Reorganizations](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions/configure-transformations.md).
---
---
title: "Configuring Reorganizations"
description: "The Reorganization function helps you make the necessary balance sheet adjustments for the entities involved in the reorganization. In this process, the assets and liabilities of the transmitting entity are automatically reflected in the balance sheet of the receiving entity."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions/configure-transformations
language: en
last_updated: 2026-09-29
---
# Configuring Reorganizations
## Overview
The **Reorganization** function helps you make the necessary balance sheet adjustments for the entities involved in the reorganization. In this process, the assets and liabilities of the transmitting entity are automatically reflected in the balance sheet of the receiving entity.
After you have [created](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-transformations.md) the individual reorganization issues in the master data, you can now configure the details of the reorganizations here.
Configuring a reorganization comprises the following steps, which are described in this chapter:
1. [Configuring details for the transmitting entity](#sender)
Define the items and values to be transferred at the transmitting entity in this step
2. [Configuring details for the receiving entity](#receiver)
\- Define the target levels for the receiving entity in this step
3. Automatic generation of tax adjustment issues
After completing the second step, the tax adjustment issues are automatically created for the receiving entity.
## Navigation
The **Reorganizations** workspace is opened under **Company| Functions | Reorganizations**.
The workspace displays an overview of all **reorganizations** already created in the master data and their status, for example as follows:
Overview of created reorganizations
## Technical Prerequisites
The following technical requirements must be observed when creating and configuring reorganizations:
**Taxonomy type**
For successful execution, both entities must use the same taxonomy type (e.g. core taxonomy) and the same taxonomy version (e.g. version 6.7). If the taxonomies are different, the reorganization is aborted by the program before the tax adjustments are created at the receiving entity. The user then has the option to adjust the taxonomy of the receiving entity and subsequently continue the reorganization.
**Required permissions**
The permission concept for the reorganization function is designed in such a way that the reorganization can be carried out by different users for the transmitting and receiving entities.
Each user must have the required permissions to <54>edit tax adjustments for the respective entity as well as the <57>Execute reorganizations permission.
The following permissions are also required for managing the reorganization: <60>Read reorganizations, <63>Edit reorganizations and <66>Reset reorganization status.
## Editing State of a Reorganization
The current **editing state** of a reorganization is displayed both in the overview of all reorganizations created and in the detail view of the respective configuration process (referred to as reorganization dialog).
The state of the reorganization changes automatically each time a step is completed. The following states are passed through during the configuration:
1. Not Started
2. Transmitting entity in progress
3. Transmitting Entity finished
4. Receiving entity in progress
5. Receiving entity finished
The reorganization is considered complete only when the state is **Transmitting Entity finished**.
> **Note:** The editing status can be reset at any time to make changes to the reorganization. How to proceed is described in [Correcting Information](#correcting-information).
## Configuring Details for the Transmitting Entity
Editing the reorganization begins at the transmitting entity. Define the items and values to be transferred in this step. Proceed as follows:
1. Open the desired reorganization under **Company | Functions | Reorganizations** and click **Start reorganization**.
Starting reorganization
2. The state of the reorganization is set to **Transmitting entity in progress** and the balance sheet tree is displayed only with commercial balance sheet values.
The structure of the balance sheet tree is based on the taxonomy schema of the current tax balance sheet.
3. Click **Select adjustment levels.** The balance sheet tree is recalculated in consideration of the tax adjustment issues.
Selecting adjustment levels
4. Choose the balance sheet item whose values and deviations are to be transmitted during the reorganization. Choose one of the following options:
- Activate the **check box** in front of each balance sheet item separately.
- Click **More actions | Transfer calculated values** to select all balance sheet items at the lowest level including equity and tax adjustment issues for transfer at once.
The **commercial balance sheet values** and **deviations** are then transferred to the respective **Thereof transferred** column.
Selected items and their transferred values and deviations
> **Note:** You can find notes on the columns of the balance sheet tree and the transfer logic of the values under [Columns of the Balance Sheet Tree](#columns).
5. Click **Save** to save the current editing status.
6. Click **Finish reorganization** to complete the editing of the transmitting entity and allow you to start editing the receiving entity.
The status of the reorganization is set to **Transmitting Entity finished**.
The composition and values of the transferring assets and liabilities are fixed and can no longer be influenced by subsequent changes in the Balance Sheet report element.
> **Warning:** The editing status of the transmitting entity can be **saved** at any time to continue editing at a later time.
>
> If changes are made to the balance sheet of the transmitting entity in the mean time, e. g. by re-importing commercial balance sheet values or correcting tax adjustments, the **Local Gaap** and **Deviation** columns are automatically updated in the reorganization dialog. Values already saved in the **Thereof transferred** and **Intermediate value / fair market value** columns are retained and must be adjusted manually if necessary.
>
> If individual balance sheet items or tax adjustment issues are no longer in the balance sheet tree due to changes to the Balance Sheet report element, they will also be removed from the reorganization dialog provided the reorganization has not yet been completed at the transmitting entity.
>
> When editing is re-opened, deleted items are listed in an info box.
## Columns of the Balance Sheet Tree
The balance sheet tree has the following column structure:
#### Balance sheet item
This column displays the items that correspond to the items in the **Balance sheet of the transmitting entity** report element under **GAAP Reports | Balance Sheet**.
Tax adjustment issues are also displayed.
Each item at the lowest balance sheet level and each tax adjustment issue is provided with a check box. As soon as you activate a check box, the commercial balance sheet values or deviations are transferred to the **Thereof transferred** column.
> **Note:** Please check whether and, if necessary, which equity items are to be chosen for transfer.
#### Local Gaap
Displays the commercial balance sheet values of the items and the commercial balance sheet approach of the tax adjustment issues.
The values cannot be edited and are not changed by selecting individual items for transfer.
#### Thereof transferred
(Local Gaap)
Contains commercial balance sheet values of the transferring assets and liabilities.
The value from the **Local Gaap** column is initially transferred to this column as soon as the item's check box is activated.
This value can be changed manually, for example, if not all assets and liabilities of the item are transferred to the receiving entity.
If the selection of the item is cleared, the entered values will be lost.
The values in this column follow the calculation logic of the balance sheet tree: The total items are automatically calculated based on the chosen items at the lowest level.
#### Deviation
Displays the totaled tax deviations of the chosen adjustment levels.
These values cannot be edited and are automatically updated when the selection of adjustment levels changes.
#### Thereof transferred
(Deviations)
Contains the tax deviations of the tax adjustments chosen for transfer.
The value from the **Deviation** column is initially transferred as soon as the check box of the tax adjustment issue is activated.
The values cannot be edited and follow the calculation logic of the balance sheet tree.
#### Intermediate value / fair market value
Top-up amounts can be entered manually here if the reorganization takes place at a higher value than the book value.
Entries are possible only for balance sheet items at the lowest level.
If the item is deselected, any entries already made will be lost.
#### Tax balance sheet
Displays the final values of the transferring assets and liabilities.
The values result from the sum of the two columns **Thereof transferred** (Local Gaap and Deviations) and **Intermediate value / fair market value**.
These values form the basis for the tax adjustment issues in the balance sheet of the receiving entity.
> **Warning:** Currently, no tax adjustments are automatically created **at the transmitting entity**. Any top-up amounts for the assets and liabilities must therefore be entered manually in its closing balance sheet.
## Configuring Details for the Receiving Entity
In this step, choose the target adjustment levels to which the tax balance sheet values of the transferring assets and liabilities are to be transferred.
For the transferred commercial balance sheet values, top-up amounts to the intermediate or fair market value and tax adjustment issues, you can choose either a common target level or a separate target level in each case.
1. Open the desired reorganization under **Company | Functions | Reorganizations** and click **Start reorganization**.
2. The state of the reorganization is set to **receiving entity in progress**.
3. Choose the adjustment levels to which the values are to be transferred at the receiving entity:
Selecting the target adjustment levels
> **Note:** For better traceability of the results, it is recommended to create **at least one separate, company-specific adjustment level** at the receiving entity level to reflect the reorganization process.
4. Click **Save** to save the current editing status.
5. Click **Finish reorganization** to complete the editing of the receiving entity.
The state of the reorganization is set to **Transmitting Entity finished**.
At the same time, corresponding tax adjustment issues are **automatically** created at the receiving entity level.
A separate tax adjustment issue is created for each transferred commercial balance sheet value, tax deviation value, and top-up amount for the intermediate or fair market value.
## Correcting Information
To correct information in configuration steps that have already been completed for a reorganization:
1. First, reset the state of the reorganization by opening the reorganization under **Master Data | Reorganizations** and clicking **Reset**.
Reset status
2. The status of the reorganization is reset to **Not started**.
3. Navigate to the **Company | Functions | Reorganizations** area and open the desired reorganization.
4. Make the necessary changes as described in the individual configuration steps above.
> **Warning:** **Note before you automatically generate the adjustments again**
>
> The tax adjustments that have already been generated automatically at the receiving entity remain unchanged when the state is reset.
>
> Since new tax adjustment issues are created each time the reorganization is carried out automatically, the **existing tax adjustments must be deleted manually beforehand**.
>
> To do this, go to the **Company | GAAP reports | Adjustments** area. Both the text filter (according to the suffix in the case description) and the column filter for the **Reorganization** adjustment type can be used for the targeted selection of the affected tax adjustment issues:
>
> the shows adjustments workspace below gaap reports folder. workspace and column header for filtering type are marked in red. icon
> Filtering by adjustment types
---
---
title: "Configuring Tax Balance Sheet Settings"
description: "General settings for the display and taxonomy items are configured in the Tax Balance Sheet Settings workspace."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-tax-balance-settings
language: en
last_updated: 2026-05-28
---
# Configuring Tax Balance Sheet Settings
## Overview
General settings for the display and taxonomy items are configured in the **Tax Balance Sheet Settings** workspace.
These comprise:
- **SAP sign logic**
- **Taxonomy items** for the disclosure of specific values
- The option to **activate automatic application for the determination of taxable profit** and **in declaratory procedures** for partnerships
- Settings for **capital account development** as well as for **tax groups** or the **mirror image method**
You can [automatically determine](#auto) and populate the tax balance sheet settings.
## Navigation
The **Tax Balance Sheet Settings** workspace is displayed as soon as you open a tax balance sheet under **Company**:
'Tax Balance Sheet Settings' workspace
## Automatically Determining Tax Balance Sheet Settings
You can automatically determine and populate the tax balance sheet settings.
To do this, open the **More actions** menu and select one of the following options:
- **Determine default values** to automatically populate the settings based on the chosen taxonomy and legal form
- **Apply from the previous year** to automatically apply the settings from the previous year
Determining values automatically
The suggested values are automatically inserted and the values changed in this way are indicated accordingly.
Check and change the suggested values if necessary and click **Save**.
All options can also be edited manually.
## Options
The following options are available depending on the chosen [taxonomy version](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-tax-balance-sheet/notes-taxonomies.md):
#### SAP sign logic
Select whether the **SAP sign logic** should be applied to all report elements.
#### Taxonomy items
Specify the following:
- Whether the tax adjustment item of the last reporting date is to be included in the P&L of the bank taxonomy
- Taxonomy items for:
- Recognizing the balance of the tax adjustment item at the end of the previous year in the income statement of the banking taxonomy
- The tax adjustment item of the last reporting date in equity
- The tax surplus/deficit in equity for the current year
- Adjustments recognized directly in equity in the current year
- Whether the net income for the year (or: retained earnings) should be automatically transferred from the income statement (or: appropriation of earnings) to the balance sheet
- Taxonomy item for the net profit/loss for the year in equity (or in the case of appropriation of profit/loss: net profit/accumulated loss in equity)
**Notes**:
- If the net profit/accumulated loss rather than the net profit/loss for the year is recognized in equity in the balance sheet, the taxonomy item must be adjusted. In this case, the net profit/loss for the year must not be stored as a taxonomy item, but the taxonomy item retained earnings/accumulated deficit.
- The taxonomy item **net retained profits/accumulated losses** is managed separately for **corporations** and **commercial partnerships**.
- If the net profit/loss for the year from the income statement is automatically transferred to the "Appropriation of profit" section of the report (or to the income statement for insurance taxonomies) as the starting figure for determining the retained earnings/accumulated deficit.
#### Partnership
Specify the following:
- Whether the net profit/loss for the year should be automatically transferred from the **income statement** report to the **determination of taxable profit** report
- Whether the taxable profit/loss should be automatically transferred from the **determination of taxable profit** report to the **determination of taxable profit in declaratory procedure** report
#### Capital account development
Specify the equity accounts for the crediting of the following values:
- **Net income/loss for the year - General partner**
- **Net income/loss for the year - Limited partner**
- **Tax surplus/deficit - General partner**
- **Taxable surplus/deficit - Limited partner**
#### Tax group
Specify the taxonomy item for the adjustment of the carrying amount of the investment for tax purposes in the event of a deficit transfer prior to the tax group.
#### Mirror image method
Specify the taxonomy item for the tax adjustment of the carrying amount of the investment.
> **Note:** Further information and explanations regarding the required details can be obtained, if necessary, by clicking the corresponding input field:
>
> the further information icon
> Further information
---
---
title: "Corporate Income Tax"
description: "The corporate income tax return is prepared in the Corporate Income Tax functional area. You can find the attachments that must be completed for electronic tax return purposes in the Corporate Income Tax functional area. The individual attachments correspond to the forms of the tax authority."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/corporate-tax
language: en
last_updated: 2026-05-28
---
# Corporate Income Tax
## Overview
The corporate income tax return is prepared in the **Corporate Income Tax** functional area.
You can find the **forms** that must be completed for electronic tax return purposes in the **Corporate Income Tax** functional area. Forms that are not visible by default can be activated individually. The individual forms correspond to the forms of the tax authority.
The [Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes.md) workspace can be used alternatively for annual financial statements and reporting purposes.
## Navigation
The **Corporate Income Tax** functional area contains several **forms** that you can open via **Company | Current Taxes | Corporate Income Tax**.
> **Tip:** You can define which forms are to be displayed in the **Corporate Income Tax** functional area on the **Corporate Income Tax** tab via **Company | Basic data | Form configuration**.
>
> the configuration of forms to be displayed in 'corporate income tax' functional area icon
> Configuration of the forms to be displayed in the 'Corporate Income Tax' functional area
For example, the **Anlage ZVE** (ZVE Attachment) form is displayed as follows:
") Functional area ‘Corporate income tax’ - 'Anlage ZVE' (ZVE Attachment)
## Decomposition
You can find a description of the corporate income tax allocation and the **KSt-Zerlegung** (CIT Allocation) form in the chapter [Allocation (Trade Tax Allocation and Corporate Income Tax Allocation)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/decomposition-gewst-kst.md).
## Forms
The following forms are available for the **Corporate Income Tax** functional area (as of **assessment period 2024**):
#### Anlage ZVE
The taxable income is determined in the **ZVE attachment**, which leads directly to the tax assessment. It collects all tax-relevant data required for the tax assessment. If the tax bases are determined in other attachments, the result of this assessment will be included in the ZVE attachment.
#### Anlage GK
The income from commercial operations is determined in the **GK attachment**. The income determined in the GK attachment is transferred to the ZVE attachment.
#### Anlage OT
In the event of a tax group, the **OT attachment** must be completed by the tax group parent. The tax bases of the individual tax group members, determined for the tax group parent, are entered in this attachment. A separate OT attachment is required for each tax group member.
> **Warning:** The tax bases of all tax group members attributable to the tax group parent are displayed in the **Current Taxes | TB Transfer** workspace, where they can be transferred automatically to the OT attachments to the tax group parent's tax return.
#### Anlage OG
In the event of a tax group, the **OG attachment** must be completed by the tax group member. The tax bases relevant to the tax group parent are entered in this attachment.
> **Warning:** The tax bases for the tax group parent are displayed in the **Current Taxes | Transfer zum OT** (Transfer to Tax Group Parent) workspace, where they can be transferred automatically to the OT attachment to the tax group parent's tax return.
#### Anlage SPIF
The **SPIF attachment** must be completed if the tax payer has invested in a special investment fund (see also [(Special) Investment Income](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/special-investment-returns.md)). The corresponding amounts are transferred to the GK attachment, where they are included in the calculation of income from commercial operations.
#### Anlage Zinsschranke
The interest capping rule limits the interest expenses a company may deduct for tax purposes. The data required to determine the interest and EBITDA carried forward are entered in the **Interest Capping Rule attachment**. The deductible interest expenses, interest carried forward, and EBITDA carried forward are determined in accordance with section 8a of the Corporate Tax Act and section 4h of the Income Tax Act.
For tax groups, only the tax group parent, not the tax group member, must complete the Interest Capping Rule attachment. However, pre-tax group interest carried forward may need to be considered for the tax group member.
For companies with interest expenses below € 3 million, the attachment is normally not required unless an interest carried forward exists.
#### AESt Attachment
This is where the information required for the consideration of foreign tax is entered. The attachment covers the following case groups:
- Foreign taxes that are creditable pursuant to **section 26 (1)** in conjunction with **section 34c 2, 3 of the Income Tax Act**;
- Foreign taxes that are deductible from the assessment basis pursuant to **section 26 (1)** in conjunction with **section 34c (1) of the Income Tax Act (EStG)**.
#### AEV Attachment
This is where the information required to assess the tax exemption of negative foreign income related to third countries in accordance with **section 2a of the Income Tax Act** is entered.
The results from the AEV attachment are included in the corporate income tax return.
#### Anlage SPIFA
This is where income from special investment funds that is achieved indirectly via a partnership company or tax group member is entered.
The **SPIFA attachment** supplements the SPIF attachment with the information required to credit or deduct foreign taxes for investment income if the investment is held via a partnership company or tax group member.
#### Anlage SAN
The **SAN attachment** is a form used to calculate the tax-exempt recapitalization gains pursuant to section 3a of the Income Tax Act.
#### Anlage Verluste
The remaining loss carried forward is determined for the assessment of losses in the **Losses attachment**.
The deductible loss for the current assessment period determined in the Losses attachment is transferred to the ZVE attachment.
#### Anlage Invest-Verluste
The uncompensated negative income for investment funds is determined in the **Anlage Invest-Verluste** (Investment Losses attachment). The form must be completed only by investment funds, not by their investors, as an attachment to the corporate income tax return and loss assessment.
#### Anlage ZwiG
This is where information relevant to the taxation of foreign intermediate companies pursuant to section 7 of the Foreign Tax Act must be entered (referred to as controlled foreign company taxation).
The data for the controlled foreign company taxation pursuant to **sections 7, 8 of the Foreign Tax Act** are entered in the ZwiG attachment. These data are transferred if a notice of assessment is already available (standard case). If no assessment has (yet) been made, the information for the ZwiG attachment must be determined separately.
#### Anlage WA
Additional information for the corporate income tax return is compiled in the **WA (Additional Information) attachment**. It includes the following content:
- Crediting of withholding taxes pursuant to **section 36 (2.2)** in conjunction with **section 36a of the Income Tax Act** (rows 2–7);
- Crediting of tax deductions pursuant to **section 50a of the Income Tax Act** for tax payers subject to limited tax liability (rows 8 and 9);
- Crediting of foreign taxes pursuant to **section 50d (10.5) of the Income Tax Act** in conjunction with **section 26 (1) of the Corporate Tax Act** (rows 10 and 11);
- Information on harmful acquisition of ownership pursuant to **section 8c of the Corporate Tax Act** (rows 11a–11g);
- Information on loss and/or interest carried forward subject to continuation requirements pursuant to **section 8d of the Corporate Tax Act** (rows 12–14);
- Contractual agreements with investors and related persons (rows 15–19);
- Supervisory board compensation to tax payers subject to unlimited tax liability (rows 20–20g);
- Country-related report of multinational enterprise groups pursuant to **section 138a AO** (rows 27–29);
- Compensation in accordance with **section 50a (1.1** to **4)** and **(7) of the Income Tax Act** to tax payers subject to limited tax liability (rows 30–37);
- COVID-19 emergency aid, bridging aid, and comparable grants (row 40);
- Research allowance (rows 41–44).
#### Anlage WA – Aufsichtsratvergütungen (Zeile 20) (Supervisory Board Compensation (Row 20))
You can enter information on all supervisory board compensation paid in the assessment year centrally here.
#### WA attachment – Vergütung nach § 50 a EstG / § 10 StAbwG (Zeile 30) (Remuneration pursuant to section 50a of the Income Tax Act / section 10 of the Tax Haven Defense Act (row 30))
You can enter the information on compensation to tax payers subject to limited tax liability (e. g. supervisory board compensation, license fees) centrally here.
#### Anlage ÖHK
The **ÖHK attachment** is used to divide corporations in which legal persons under public law hold the majority of voting rights into individual sectors.
The division of sectors ensures that losses can be accounted for only within specific business segments. This enables the correct documentation of the compensation and deduction of losses in accordance with section 8 (9) of the Corporate Tax Act.
The form consists of four parts:
- A detailed description of the sectors
- Allocation of the income
- Assessment of the deductible loss
- Development of the loss carried forward
A separate attachment must be completed for each sector to ensure appropriate loss offsetting.
#### Anlage Kassen
The **Kassen (Funds) attachment** is a supplementary form to the corporate income tax return, which must be submitted by legally responsible pension, death, health, and relief funds if they are exempt from corporate income tax pursuant to section 5 (1.3) of the Corporate Tax Act.
The ZVE and GK attachments must also be submitted in the event of full or partial tax liability.
The form is divided into ten sections and collects information such as:
- General details
- Fund provider
- Investment of fund assets
- Type of benefits granted
- Beneficiaries
- Use of funds
- Amount of benefits
- Calculation of the endowment
#### Anlage Gem
The **Gem attachment** is a form used for the corporate income tax return, which the tax authorities use to verify whether tax-privileged corporations (section 5 (1.9) of the Corporate Tax Act) meet the requirements for tax exemption.
The Gem attachment must be submitted regularly every three years unless extensive economic activities of the tax-exempt corporation require an annual declaration.
In addition, documents such as the balance sheet and profit and loss statement, must be submitted electronically for the entire audit period to allow the tax exemption or partial tax liability to be verified.
#### Anlage Ber
The **Ber attachment** is a supplement to the corporate income tax return. which must be completed by professional associations not under public law, including trade unions, to verify the tax exemption pursuant to section 5 (1.5) of the Corporate Tax Act. These associations are exempt from corporate income tax and trade tax unless they operate an economic business that exceeds the tax exemption threshold or supports political parties.
Tax returns are required regularly every three years unless there are relevant economic activities or political support that require an annual declaration. Supplementary documents, such as balance sheets and activity reports, must be submitted for each year of the audit period.
#### Anlage STG
You can enter information on cross-border tax arrangements here.
#### Anlage KSt 1 F
The **KSt 1 F attachment** must be completed by corporations subject to unlimited tax liability (in particular capital companies, cooperatives, mutual insurance associations, economic associations, and enterprises of commercial nature with their own legal personality). It is used to determine and update the tax contribution account and what is referred to as special disclosure pursuant to sections 27 and 28 of the Corporate Tax Act.
The tax contribution account is required to distinguish between taxable dividend distributions and tax-neutral returns of capital contribution when making distributions to investors. The attachment must be submitted for each fiscal year.
In addition, the KSt 1 F attachment provides information on the dividend distributions and services made during the fiscal year to ensure correct tax treatment and monitoring of the capital gains tax deduction.
---
---
title: "Countries"
description: "In the Countries workspace, the countries maintained in the selected period are displayed."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries
language: en
last_updated: 2026-05-28
---
# Countries
## Overview
In the **Countries** workspace, the countries maintained in the selected period are displayed. Creating countries is necessary in order to create **companies**. Each company is **assigned** to a country and uses the tax rates stored for this country for the **calculation of current and deferred taxes**.
The chapter describes:
- The creation and configuration of countries, along with an overview of the main attributes of a country, such as tax rates and exchange rates (see [Creating and Configuring the Element Type “Country”](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries/create-configure-country.md))
- The importing of exchange rates, including the structure of corresponding CSV files (see [Importing Exchange Rates](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries/import-exchange-rates.md)).
> **Note:** Name of a country in multiple languages
>
> The language for Income Taxes is set in the **Home** workspace. In order for data sets created by the user to be displayed in the **respective country language**, corresponding language entries must be created in the detail view **Country**. Examples:
>
> Country name (= output value)
>
> German (= Deutschland)
>
> English (= Germany)
>
> Francais (= Allemagne)
---
---
title: "Country-by-Country Reporting"
description: "The Country-by-Country Reporting (CbCR) sub-module enables the automated collection, validation, and reporting of country-specific data in accordance with OECD guidelines and local regulations."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting
language: en
last_updated: 2026-07-28
---
# Country-by-Country Reporting: Collection and Reporting of Country-Specific Data
The **Country-by-Country Reporting (CbCR)** sub-module enables the automated **collection, validation, and reporting of country-specific data** in accordance with **OECD guidelines** and local regulations. The CbCR sub-module includes features for data integration and audit workflows and provides ready-to-use reports. This allows for a comprehensive overview of global tax obligations, improved compliance, reduced manual effort, and increased audit readiness.
'Group Data Collection' workspace
## Key Benefits
CbCR offers the following benefits:
- **Overview of jurisdictions and entities with CbCR-relevant key figures**: Table 1 provides detailed insights at the jurisdiction level, while Table 2 offers a clear breakdown by constituent entities (CEs).
- **Adding additional information**: Users can add customer-specific supplementary information for each jurisdiction — or combination of jurisdictions — for any item in the CbC report. Comments can be provided in multiple languages to ensure clear communication in key languages. All additional information is seamlessly integrated and displayed as Table 3 in the CbC report, providing the tax authorities with a more complete and transparent overview.
- **Public CbCR reporting**: In addition to the regular non-public CbC report filed with tax authorities, the sub-module supports public Country-by-Country reporting under **EU Directive 2021/2101** (submitted to the German Federal Gazette in iXBRL format) and the **Australian public CbCR** schema. Both public reports can be generated from a single snapshot and include mechanisms for omitting sensitive information and explaining material discrepancies.
- **Excel reports**: It is possible to create Excel files containing all the information from the Tables 1, 2 and 3.
- **Integration of [Pillar 2](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two.md) and CbCR for the Pillar 2 Safe Harbour Check**: The integration between the CbCR and Pillar 2 sub-modules simplifies the process by enabling the data required for the Safe Harbour Check to be imported directly from the CbCR sub-module into the **Pillar 2** sub-module.
- **Reporting**: CbCR simplifies country-by-country reporting by providing a direct DIP interface (DIP = digital inbox) to the Federal Central Tax Office (BZSt).
- **XML validations and creation of XML reports**: CbCR ensures the accuracy and reliability of your CbC reports through comprehensive validations at every stage. From input data to calculation results to the final XML output, the sub-module performs rigorous checks to identify inconsistencies and errors early in the process. Users can create a complete XML report and have it validated as well as download an XML source file with all metadata.
---
---
title: "Create and Download Reports"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/create-download-reports
language: en
last_updated: 2026-09-28
---
# Creating and Downloading Reports in Lucanet VAT
## Overview of the 'Reports' Workspace in VAT
In the **Reports** workspace in Lucanet VAT (Value Added Tax), various Excel reports for analyzing the VAT data are available. Which reports VAT displays depends on the chosen company type and the kind of period – preliminary return, annual return, or special prepayment.
You can also import your own Excel reports as templates and then create them like the supplied reports.
## Navigation to the 'Reports' Workspace in VAT
The **Reports** workspace can be found under **VAT | Value Added Tax | Reports** and is displayed as follows, for example:
'Reports' workspace
## Structure of the 'Reports' Workspace in VAT
The **Reports** workspace in VAT shows a table with all available reports. Use the **Search** field to filter the table. The table contains the following columns:
| Column | Description |
|---------|---------|
| Name | Name of the report |
| Data origin | Data source that the report is based on |
| Explanation | Short description of the report content |
## Creating and Downloading Reports in VAT
To create a report in VAT, click anywhere in the row of the required report. The notifications side panel is displayed and shows the progress of the report creation. While the report is being created, you can continue working in VAT and create further reports. You can also open the side panel at any time via the bell icon in the header.
As soon as the report is finished, the file name is displayed in the side panel. Click the file name to download the report. To cancel the creation of a report, click **X**. To delete a finished report that you no longer need, click the trash can icon.
Side panel with report creation
## Importing a Custom Excel Report in VAT
You can import your own Excel template to make additional reports available in VAT. The imported report is then displayed in the table of the workspace and can be created there like the supplied reports.
> **Note:** The **Import** function is only visible if your role allows you to import report templates.
Proceed as follows to import a custom Excel report in VAT:
1. In the context menu of the three-dot icon (**⋮**) in the top right corner, click **Import**. The **Import Excel template** dialog is displayed:
'Import Excel template' dialog
2. Check the **Type** drop-down list. For importing your own report, the type **Custom Report Template** is preselected; only system administrators can choose a different type.
3. In the **Name of Report** field, enter the name under which the report is to be displayed in the table.
4. In the **Explanation** field, enter a short description of the report content.
5. In the **Data origin** field, enter the data source that the report is based on. The entries from the **Explanation** and **Data origin** fields are displayed in the columns of the same name in the table.
6. Click **Choose File** and choose the Excel file in XLSX format.
7. Click **Import**. The button is only active once you have chosen a file. VAT adds the report to the table.
---
---
title: "Creating a Company"
description: "In the Companies workspace, you can manage the companies for which you want to prepare tax balance sheets and transmit them to the tax office."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-company
language: en
last_updated: 2026-05-28
---
# Creating and Configuring a Company
## Overview
In the **Companies** workspace, you can manage the companies for which you want to prepare tax balance sheets and transmit them to the tax office.
## Navigation
The **Companies** workspace can be opened under **Master Data | Companies**.
This workspace provides an overview of all **companies** that have already been created and is displayed, for example, as follows:
'Companies' workspace
## Creating a Company
To create a company:
1. In the **Companies** workspace, click **Add.**
2. Enter a unique **company ID**.
As a rule, the value from the ERP system should be used as the company ID.
3. Enter a **name** for the company.
4. Click **Save**.
## Deleting a Company
To delete a company, open the entry for the company in the overview table with a click and then click **Delete**.
> **Warning:** Deleted companies are not archived, but permanently deleted, and cannot be restored.
---
---
title: "Creating a Form"
description: "This chapter describes how to create a new form instance for a unit and a reference date as the basis for entering, validating, and transmitting a tax report."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-services/create-form
language: en
last_updated: 2026-05-01
---
# Creating a Form
## Overview
For each unit and each reference date, you can create a separate form instance in Tax Services. This forms the basis for entering, validating, and transmitting the tax report.
## Creating a Form
To create a new form:
1. On the start page, select the desired **Reference Date** and **Unit**.
'Tax Services' start page
2. Click **Show forms**.
3. Open the **Forms** tab and click the desired form type.
'Forms' tab
4. The system automatically creates a new form instance and opens it in the overview:
Overview page for 'Belegnachreichung zur Steuererklärung' (subsequent submission of documents for the tax return)
5. Configure the form instance according to your requirements (see [Form Processing Procedures](https://support.lucanet.com/en/documentation/income-taxes/tax-services/form-processing-procedures.md)).
---
---
title: "Creating a Tax Balance Sheet for an Individual Company"
description: "After you have defined the master data for Tax Balance, you can create the tax balance sheet(s) at the individual company level."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance
language: en
last_updated: 2026-05-28
---
# Creating a Tax Balance Sheet for an Individual Company
## Overview
After you have defined the master data for Tax Balance, you can create the tax balance sheet(s) at the individual company level.
The following steps are required to create a tax balance sheet for an individual company:
- [Opening the desired tax balance sheet](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/open-tax-balance.md)
- [Managing GCD master data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/gcd-master-data.md)
- [Defining settings for the tax balance sheet](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-tax-balance-settings.md)
- [Importing data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/import-data.md)
- [Creating GAAP reports](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/maintain-gaap-reports.md)
- [Creating and Configuring Adjustments](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/maintain-gaap-reports/creating-and-configuring-adjustments.md)
- [Configuring functions](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions.md)
- If applicable, [Configuring Reorganizations](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions/configure-transformations.md)
## Navigation
A tax balance sheet at the company level is created in the **Company** area.
The area is displayed as follows, for example:
'Company' area
---
---
title: "Creating an Adjustment Level"
description: "To reflect different levels of knowledge (such as tax return, annual financial statements, tax audit), tax deviations based on commercial law values can be assigned to adjustment levels. The level of transparency is increased by using adjustment levels."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-adjustment-level
language: en
last_updated: 2026-05-28
---
# Creating and Configuring Adjustment Levels
## Overview
To reflect different **levels of knowledge** (such as tax return, annual financial statements, tax audit), **tax deviations** based on commercial law values can be assigned to adjustment levels. The level of transparency is increased by using adjustment levels.
In the **Adjustment Levels** workspace, you can create, name, and configure global adjustment levels.
The adjustments themselves are then entered at the individual company level on the adjustment levels created here (see [Creating GAAP Reports](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/maintain-gaap-reports.md)).
> **Note:** It is possible to configure special adjustment levels that are used for only one company at the [individual company level](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance.md).
>
> Changing the order only affects companies created subsequently. The order of adjustment levels for existing companies can only be changed at the individual company level.
## Navigation
The **Adjustment Levels** workspace can be opened under **Master Data | Adjustment Levels**.
The workspace displays an overview of all global **adjustment levels** that have already been created in the **master data** and is displayed as follows, for example:
'Adjustment Levels' workspace
## Creating an Adjustment Level
To create an adjustment level, click **Add** in the **Adjustment Levels** workspace, enter a **name** for the adjustment level, and **save** your entries.
> **Note:** When creating the adjustment level, a technical name is automatically assigned. The technical name is required if you want to import an Excel adjustment. To import into an adjustment level, the named area must be called "Level_TECHNICAL_NAME". This value is read-only and cannot be changed.
## Migrating an Adjustment Level
You can use the **Migrate** function to migrate adjustment levels that were created at the individual company level to a global adjustment level.
> **Warning:** This function is relevant only to existing customers who have already used **Tax Balance** prior to its release on the Lucanet CFO Solution Platform.
---
---
title: "Creating and Configuring Adjustments"
description: "You can enter tax deviations based on commercial-law values at adjustment levels and create the company-specific adjustment levels that may be required for this purpose in the Adjustments workspace.\nIn addition to company-specific adjustment levels, you can also use global adjustment levels that you have created in the master data. You can also update or import existing adjustments."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/maintain-gaap-reports/creating-and-configuring-adjustments
language: en
last_updated: 2026-05-28
---
# Creating and Configuring Adjustments
## Overview
You can enter tax deviations based on commercial-law values at adjustment levels and create the company-specific adjustment levels that may be required for this purpose in the **Adjustments** workspace.
In addition to company-specific adjustment levels, you can also use global adjustment levels that you have created in the [master data](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-adjustment-level.md). You can also update or import existing adjustments.
## Creating a Company-Specific Adjustment Level
To create a company-specific adjustment level:
1. In the introduction text of the **Adjustments** workspace, click the **Adjustment levels** link.
Link to create an adjustment level
2. On the **Adjustment levels** page, click **Add**.
3. Specify the following in the displayed **New level** dialog:
- **Name** of the adjustment level.\
\
The name of an adjustment level is displayed, for example, in the **GAAP reports** view under **Balance sheet/P&L**. Adjustment levels and their names cannot be transferred with the E-Balance.
- Whether the adjustment level is a **sum level\
\
** If this option is activated, the value for this adjustment level is determined from the sum of the values of the preceding adjustment levels. You cannot enter or import a value for this adjustment level. Use this option, for example, to get an overview of adjustment levels from multiple transformation processes.
- Whether the adjustment level is a **simulation level**.\
\
Simulation levels are not transferred to the tax authorities.
Creating a company-specific adjustment level
## Creating an Adjustment
To add a new adjustment:
1. In the **Adjustments** workspace, click **Add**.
Adding an adjustment
2. As the **type** of the tax adjustment, select **Standard form** for manual entry of values.
**Note:** The option **Standard form with Excel integration** is no longer supported in Tax Balance. You can convert existing adjustments of this type to **Standard form** using the migration function described under **Value development**.
3. Enter the **name** of the tax adjustment. The name is transmitted as the title of a footnote when the E-Balance is submitted.
4. Enter the **balance sheet item** or the **P&L item** of the adjustment.
5. Choose the **type of reconciliation**.
6. Enter the **explanation** to the tax office to be transmitted as a footnote when transmitting the e-balance sheet.
7. Click **Save**.
8. Then configure the properties of the adjustment as described in the following section.
## Configuring an Adjustment
You can configure the adjustment either directly when creating it, or later by clicking the adjustment in the overview.
The following details can be edited in workspaces specifically displayed for this purpose:
### Value Development
Under **Value development**, you can record the values for the tax **deviation**. Choose one of the following options:
- Enter the value in the **commercial balance sheet**, then enter the tax **deviation** in the column of the corresponding **adjustment level**.
- Enter the value in the **commercial balance sheet** and the value in the **tax balance sheet**.
The table then displays the resulting values, i.e., either the deviation or the value in the **tax balance sheet,** along with the **Difference in assets**, the **Difference in profit**, and whether the adjustment is **not recognized in profit or loss**.
Value development of an adjustment
The following options are also available via the **More actions** menu:
- You can **update** adjustments to the next year.
If you choose this option, specify the following in the displayed dialogs:
- source tax balance sheet
- which header data and elements should be updated
- whether the application should be additive or overwriting
- You can **apply values from a depreciation series**, provided that a depreciation series has been created for the adjustment.
If you choose this option, specify the following in the displayed dialog:
- the adjustment level to which the values of the depreciation series should be written
- whether the values in other adjustment levels should be deleted
- whether the values of previous years should be recalculated
- whether the values of the depreciation series should be rounded, and if so, how
- You can **apply values from existing account value calculations**.
If you choose this option, specify the following in the displayed dialog:
- the adjustment level to which the values of the account value calculations should be written
- whether the values in other adjustment levels should be deleted
- For adjustments of the type **Standard form with Excel integration**, the **Migrate to standard form** option is also available. With this function, you can migrate adjustments stored in an Excel file into a **Standard form** adjustment. The values from the Excel file are migrated directly to Tax Balance, and the Excel file is added to the **Documents** workspace for documentation purposes.
### Header Data
Under **Header data**, you can edit general information for each adjustment.
Header data of an adjustment
This includes:
- **Name** of the adjustment, which is transmitted as the title of a footnote
- **Status** of the adjustment. You can choose between **Not Started**, **In Progress**, **Done**, and **Checked**. The status has no effect on the workflow. It is used only for internal documentation of the processing progress and is not transmitted with the E-balance.
- **Balance sheet item**
- **P&L item**
- **Type of reconciliation**
- **Explanation** for the adjustment, which is transmitted as the text of a footnote
- **Internal explanation**, which is not transmitted
- **Import identification feature**, used to uniquely identify the adjustment during an import. It is recommended not to change this value after the initial definition, as this change must be reflected in the exports of third-party systems in order to be able to assign the adjustment. Please therefore only make changes to this field with caution.
- **Target item no.**, used to transmit the tax values maintained in the **Tax Balance** module to the [Income Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes.md) module.
- **Tax group**. (Applies only to tax groups and intermediate tax group parents.)
- Partnership in whose **special business assets** the tax adjustment is to be transferred.
**Notes**:
- Tax deviations that reflect assets of a special business asset can be transferred to the corresponding special balance sheet of the shareholder.
- To enable the link to the corresponding special balance sheet, you must enter the master data of the corresponding shareholder in the **master data** of the partnership under **Shareholder**. In the **Company** field, link the shareholder to this company.
- The **type** of adjustment is determined at the time of creation. This value is read-only and cannot be changed.
**Updating Adjustments**
In the **Header data** section, you can also update adjustments to the next year using the **Update** option. Only the adjustment itself is updated, not the values.
If you choose this option, specify the **following** in the displayed dialogs:
- source tax balance sheet
- which header data and elements should be updated
- whether the application should be additive or overwriting
### Account Assignments
Under **Account assignments**, you can select the accounts of the balance sheet item chosen in **Header data** on which the adjustment is to be displayed in the balance sheet in Tax Balance.
Account assignments of an adjustment
To do this, click **Edit**, select one or more accounts you want to assign in the displayed dialog, and click **Save**.
**Updating Adjustments**
In the **Account assignments** section, you can also update adjustments to the next year using the **Update** option. Only the adjustment itself is updated, not the values.
If you choose this option, specify the following in the displayed dialogs:
- source tax balance sheet
- which header data and elements should be updated
- whether the application should be additive or overwriting
### Account Value Calculations
Under **Account value calculation**, you can specify how the values on the specified accounts should be calculated for tax purposes, if necessary. You can also define whether a **factor** in percent or an **adjustment value** as an amount should be used for the calculation.
To create an account value calculation, click **Add** and specify the following in the **New account value calculation** dialog:
- the **account number or numbers** for which the account value calculation should be defined
- how the calculation should be performed. Choose one of the following options:
- Select **Calculation with factor**, then enter the factor for calculating the local value and the tax base.
- Select **Calculation with adjustment value**, then enter an **adjustment value for the local value** and an **adjustment value for the tax base**.
Creating an account value calculation
**Updating Adjustments**
In the **Account value calculation** section, you can also update adjustments to the next year using the **Update** option. Only the adjustment itself is updated, not the values.
If you choose this option, specify the following in the displayed dialogs:
- source tax balance sheet
- which header data and elements should be updated
- whether the application should be additive or overwriting
### Depreciation Series
Under **Depreciation series**, you can define depreciation series for depreciable values in the commercial balance sheet and the tax balance sheet.
To do this, open the **Depreciation series** workspace and first specify whether you want to depreciate the commercial balance sheet or tax balance sheet values of the depreciation series using the **straight-line** or **declining-balance** method. This setting cannot be changed subsequently.
Then specify the following:
- Start of amortisation
- **Assessment base** and **amortisation period** for the **commercial balance sheet approach**
- **Assessment base** and **amortisation period** for the **tax balance sheet approach**
Click **Create depreciation series** to create the depreciation series.
Depreciation series for an adjustment
### Documents
Under **Documents**, you can add supporting documents for each adjustment, such as receipts, proofs, or internal reports.
To do this, click **Add** and specify the following:
- the **file** you want to upload as a document
- whether it is a document according to **GoBD**
- whether the document should be **assigned** to the **current tax balance sheet** or the **current company**. This setting cannot be changed subsequently.
- a **comment**(optional)
Adding a document
## Displaying Adjustments in the Balance Sheet
Once an adjustment has been created and configured, you can display it in the **balance sheet** in the **GAAP reports** functional area.
To do this, use the drop-down list at the top left to show the corresponding adjustment level or levels. Adjustments are displayed with a violet background:
Adjustment in the balance sheet
---
---
title: "Creating and Configuring an Interface"
description: "To import your financial data from source systems, you must first define the interfaces used to import them from these systems. Interfaces are used to define specific settings for the import behavior and import parameters."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-interface
language: en
last_updated: 2026-05-28
---
# Creating and Configuring an Interface
## Overview
To import your financial data from source systems, you must first define the interfaces used to import them from these systems.
Interfaces are used to define specific settings for the import behavior and import parameters.
## Navigation
The **Interfaces** workspace can be opened under **Master Data | Interfaces**.
The workspace displays an overview of all **interfaces** that have already been created and is displayed as follows, for example:
'Interfaces' workspace
## Creating an Interface
To create a new interface:
1. In the **Interfaces** workspace, click **Add.**
2. Choose the **type** of interface, i. e. which data you want to import or from which source system you want to import data. The following options are available for selection:
- **Statement of changes in fixed assets**
- **Reporting Entities**
- **Equity accounts**
- **Debt Capital accounts**
- Import of data from the **Income Taxes** module
- **Accounts and adjustments**
- **Accounts and adjustments** (as **mass import** for multiple companies)
- **Determination of taxable profit for special cases**
3. Enter a **name** for the interface.
4. Click **Save**.
5. Configure the options available for the respective interface type.
### Configuration Example
For an interface used to import a fixed asset schedule, the following options are configured, for example:
## Editing an Interface
To edit an interface, click the desired interface in the overview table.
You can then edit and save the displayed details.
## Copying an Interface
To use data from an interface already configured in another interface, you can create a copy of the interface. To do this, click the **More actions** menu in the overview table and choose the **Copy** command.
Copying an interface
A copy of the interface is automatically created with the name suffix **(copy)** and you can edit and save the details.
---
---
title: "Creating and Configuring Periods"
description: "This article describes how to create and configure periods and provides two examples for the configuration of an annual report and a tax declaration for a True Up period."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/periods/create-period
language: en
last_updated: 2026-09-29
---
# Creating and Configuring Periods
## Overview
This article describes how to create and configure periods and provides two examples for the configuration of an annual report and a tax declaration for a True Up period.
## Creating Periods
Periods can be created in normal mode or expert mode. To create a period, proceed as follows:
1. Navigate to the workspace **Periods**.
2. Click **Create** or **Create (expert)** and enter the required data in the dialog that appears.
3. Click **Create**.
> **Note:** **Note:** The dialog fields are explained in the following table:
Creating period
#### ID
The ID is a number automatically assigned by Income Taxes to uniquely identify the respective period.
#### Name
The name of the period can be freely selected. The use of a uniform nomenclature for period names is recommended (e.g., IFRS Reporting 2024-12-31) to ensure a good overview even when dealing with a large number of periods.
The entry is limited to 255 characters.
#### End of period / due date
This refers to the cut-off date of the corresponding period (specified in the format YYYY-MM-DD, e.g. 2025-12-31).
If the Risk Management module is activated in the period, this attribute is called **Due date**.
#### Tax Form
Using the **Tax Form** attribute, the corresponding tax forms for the respective assessment time of the period can be selected. Choose from the following:
- For assessment times **before 2015**
- From the assessment time (VZ) 2015, the corresponding year applies (VZ 2018 => Tax Form 2018).
> **Note:** If an **annual report** is to be represented with the period, select **Tax Form 2017**. The tax forms for subsequent years can currently only be used for tax declaration purposes.
#### Prior period
The specified prior period can also be changed after creating the period. Since Income Taxes calculates the movement of deferred taxes (i.e. the P/L effect) based on this information (for example), providing the prior period is absolutely necessary for the correct presentation of the change.
At various points during tax calculation, Income Taxes also calculates carry-forward amounts (e.g. LCF) that refer to the prior period.
When using Income Taxes for the first time, select (---) as the prior period.
#### Period to compare
This attribute must be unlocked via customizing.
In a small number of instances, the period selected here is used as a comparison. This logic is used, for example, in Swiss tax forms for the calculation of certain proposed values. In another case, the period to compare is used during the validation of deferred taxes in the dialog **Others**.
#### Related period
The related period is specified in a new version of a period.
Typically, an annual report (for example) has no related period. A tax declaration period has the annual report of the same year as its related period.
Provide this information if a True Up is to be performed for an existing period; otherwise, select (---).
#### Summary Period
Summary periods are an additional function that is not available in the standard product. To acquire a license, please get in touch with your Lucanet contact or use the [contact form](https://www.lucanet.com/en/contact/) on our website.
This makes it possible to assign a summary period to an entry or adjustment period. Through this assignment, the entry, adjustment, and summary periods are related to each other, which enables the subsequent calculation of the sum of all assigned periods in the summary period.
If the companies in the entry, adjustment, and summary periods are managed in different currencies, a currency conversion is performed for the presentation in the summary period.
If a summary period is selected here, an additional check box with the name **Adjustment level** will be displayed. If this check box is not activated, it is an entry period; otherwise, it is an adjustment period.
#### Kind of period
Regarding the type of period, a distinction is generally made between **closing** and **planning**.
Due to their differing objectives, planning periods feature a different dialog structure (reduced dialog for P/L-based calculation of current and deferred taxes). Your objective is to determine a future tax quota. Planning periods are not part of the standard module and must be activated via customizing.
In contrast, the closing periods for the calculation of deferred and current taxes are relevant in the context of annual reports and tax declarations.
#### Master data / Tax calculation Copy based on
An existing period can be used as a template when creating a new period.
After selecting the period to be copied, you can specify whether the transaction data of the selected period should also be copied by activating the **Tax calculation with transaction data** check box. If you do, you can also specify whether the milestone status values from the source period should also be transferred by clicking the check box **with milestone status**. If the check box is not activated, all previously achieved milestones will be reset to the status **In process** in the new period.
> **Warning:** In principle, when creating a closing period, the master data of an existing period is used. Any changes in tax rates or other master data must then be updated without fail in the newly created period.
Specifying a period as template
#### Questionnaire Copy based on
When using the Questionnaire module, master data and transaction data from an existing period can also be specified to create a new period. The data sets that are considered transaction data or master data are defined individually for each customer during the conception of Questionnaire.
#### Calculation base
The values in the attributes **Calculation base** and **Active patches** provide important information regarding the existing Income Taxes configuration for the respective period. If, for example, there are changes in tax laws over time, these changes are stored in a new calculation base (Calc. base). The same applies if new functions are added within Income Taxes or if calculation procedures and automated calculations are changed. This ensures that already created periods use the applicable "prior" calculation bases (i.e. the legal status that was valid at the time) and newly created periods use the most current calculation base.
Newly created periods are therefore always (automatically) created with the most current calculation base. An exception applies to periods in which the transaction data of an existing period is copied in addition to the master data. Here, the calculation bases of the copied period are carried over – therefore, the most current calculation base is not automatically used. In this case, however, the calculation base can subsequently be changed by the user.
If, for example, a new period "Closing 2024-12-31" is created and a copy of the master data and transaction data from the preceding period "Closing 2023-12-31" is requested, the calculation base from the period "Closing 2023-12-31" will also be copied. If the latest calculation base is then to be used, the user must configure this setting manually in the period's edit mode after the period has been created.
#### active patches
These can be used to activate or deactivate individual calculation bases. In this case, a single calculation base is referred to as a patch.
For further information on importing and updating calculation bases and patches, see [Updating Calculation Bases and Patches](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/periods/update-calc-logic-patches.md).
#### Period type,
Calculation logic,
Rounding
The period type distinguishes between the options **Annual report** and **Tax return**.
A period of type **Tax return** always uses the calculation logic **Gross**, and **Rounding** is also automatically activated in this case. If the submodule **Tax Return** is enabled, electronic transfer is also possible for these periods (see [ERiC-Transfer](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer.md)).
#### Accounting standards
Here, the options **IFRS** and **Commercial Law** are available. This choice is particularly relevant for the [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md) workspace. While three balance sheet columns are displayed in IFRS periods (IFRS balance, local balance, tax balance), only the local balance and tax balance are displayed in local GAAP periods. This difference also affects the presentation of the workspace [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md).
When using the Income Taxes module for US-GAAP purposes, IFRS must be selected as the accounting standard. The same applies if a group financial statement in line with local GAAP is to be prepared in Income Taxes. Three balance sheet columns are also required here: German GAAP Consolidated (adapted to group accounting standards), Local balance, and Tax balance.
This setting can only be made when creating a new period. Subsequent changes are not possible.
#### Automation current taxes
If this setting is activated, the workspaces for current taxes (Corporate Income Tax 1A, Appendix A, etc.) are automatically synchronized with the **Current Taxes** workspace and proposed values are automatically applied. To use this setting, select **Closing v3** as the type of period and set the tax form to **Before 2015**.
If **2015 or newer** is selected for the tax form, the synchronization of **Current Taxes** is performed automatically without the need for any additional configuration, which is why this attribute is not displayed when creating the period.
## Example Configurations for Periods
Here are two example configurations of periods:
### Annual Report 2019
In this example, an annual report for 2019 is configured as follows:
Example configuration for the 2019 annual report
The following information was provided for the annual report:
| Dialog field | Description |
|---------|---------|
| Tax Form | 2017 |
| Previous period | Annual Report 2018 (not a tax declaration for 2018!) |
| Related period | \-\-\- |
| Kind of period | Closing v3 |
| Master data / Tax calculation Copy based on | If master data is continuously maintained in the standard period (---), this can also be used as a template when creating the new period “Annual Report 2019”. If Annual Report 2018 is to be used as a copy template, the master data must first be updated in the newly created period Annual Report 2019 (e.g. tax rates, holding quotas). |
| Period type, calculation logic | For annual report periods, usually **Annual report (net)**. |
### Tax Return 2019 (=> True Up period)
In this example, the tax return for a True Up period is configured as follows for 2019:
Example configuration for tax return with true-up period 2019
The following information has been specified for the tax return:
| Dialog field | Description |
|---------|---------|
| Tax Form | 2019 |
| Prior period | Tax return 2019 (not an annual report for 2018!) |
| Related period | Annual Report 2019 (period for which a True Up is being conducted) |
| Kind of period | Closing v3 |
| Master data / Tax calculation Copy based on | **Annual Report 2019** incl. **tax calculation with transaction data**, **without** milestone status: For this reason, the tax values already recorded in Annual Report 2019 only need to be updated. |
| Period type, calculation logic | For tax declaration periods, always **Tax return**( **Gross** and **Rounding**). |
---
---
title: "Creating and Configuring the Element Type Country"
description: "This article describes how to create and configure countries and also includes an overview of the corresponding key attributes, such as tax rates and exchange rates."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries/create-configure-country
language: en
last_updated: 2026-09-29
---
# Creating and Configuring the Element Type Country
## Overview
This article describes how to create and configure **countries** and also includes an overview of the corresponding key attributes, such as tax rates and exchange rates. The creation of countries is necessary in order to create **companies**.
## Creating an Element of Type 'Country'
To create a new element of type **Country**:
1. In the **Countries** workspace, click **Create**:
Creating country
2. Enter the required information (see the following subheading).
## Configuring Element of Type 'Country'
To configure an element of the **Country** type, proceed as follows:
### General Information
The **General Information** area is displayed as follows:
Configuring general information of the 'Country' element
Specify the following:
#### ID
Clearly identifies a country. Up to three places can be used. The ID can only be assigned once. It is not possible to change it later on.
For country IDs, it is advisable to use abbreviations according to ISO 3166-1-ALPHA-2 (two letters, e.g. DE, GB, FR). Regions or specific requirements for tax rates can, for example, be represented by US1, US2, US3, (…).
#### Country region
Specifies the region to which the country belongs and restricts the selection options for the **ISO code** field.
> **Note:** Furthermore, the country region can be used for evaluations by region in **Own reports**.
#### ISO Code
Establishes a unique assignment to a country. This is particularly important because the ID of the country can be assigned freely.
> **Note:** The ISO code should always be set, especially when the **Questionnaire** or **Compliance** module is used. These modules use the ISO code internally and can only be used to a limited extent if no entry is provided.
>
> Furthermore, the ISO code can be used for country-specific analyses in **Own reports**.
#### Tax Template
Defines the structure of the forms for determining current taxes in the **Company** function area.
If a tax calculation for a country is to be defined in the master data dialog **Toolbox**, select the tax template **(---)** (preset as standard by default). You can then access **Current Taxes**.
> **Note:** If the tax template **Germany** is selected, the tax detail dialogs are enabled to determine current taxes.
### Tax Rates (Enacted)
The **Tax Rates (Enacted)** area is displayed as follows:
Configuring tax rates of the 'Country' element
Specify the following:
#### Corporate income tax (CIT) rate
The tax rate used to determine the German corporate income tax or the initial foreign income tax (corporate tax).
> **Note:** - This entry is relevant for all countries set up in Income Taxes.
> - The value is used only for the calculation of current taxes. It does **not** apply to the determination of deferred taxes.
#### Local/State tax rate
Indicates the local tax or basic tax rate.
> **Note:** For this entry, a distinction must be made between Germany and other countries. For foreign countries, the value of zero may also be entered if no local income tax is levied or if it should be disregarded in **Income Taxes**.
**Germany**
Enter the basic tax rate of 3.5% (§ 11 (2) GewStG).
The basic tax rate is used for multiplication with the taxable income calculated in Income Taxes. The resulting base tax amount is multiplied by the local tax of the commune(s) in which the company is located. The local tax is therefore administered individually for each company (in the master data dialog **Company**).
**Foreign Countries**
This amount is used for the second foreign income tax (local tax) for foreign companies. In the **Current taxes** dialog, it is also possible to specify a different tax rate in the **Business tax (Gewerbesteuer)** column (or local tax) in order to account for local tax rates that differ at the regional level.
If a local tax or local tax rate is specified in the master data dialog **Company**, this will be prioritized as the proposed value displayed.
#### Combined current income tax rate
Indicates the average real tax rate for the current year. This tax rate corresponds to the sum of the two tax types **Corporate income tax** and **Local tax**.
> **Note:** This tax rate is key in determining the TRR row **Expected income tax expenses/earnings**. The difference between the tax rate of the country of the holding company and the company tax rate, multiplied by the profit before tax, represents a TRR transition item.
#### Combined deferred tax rate
Indicates the tax rate used for the calculation of deferred taxes. This tax rate generally corresponds to the combined current income tax rate for the current year or the sum of the two income tax types (corporation tax and trade income tax).
> **Note:** A deviation between the combined current tax rate for deferred taxes and the combined current income tax rate may arise if the (future) tax rate of the country in question changes. The liability method underlying IAS 12 is based on the future tax rate.
#### thereof, deferred tax rate local tax
Here, you must specify the portion of the combined tax rate for deferred taxes that is attributable to **local tax** (or local income tax). The difference between the two tax rates is attributable to the **corporate income tax**(incl. solidarity surplus for the country “Germany”).
> **Note:** This entry is particularly relevant for German **partnership companies**. It ensures, for example, that the share of deferred taxes for corporate income tax that is attributable to external partners is not displayed in the group. The local tax portion of the latent tax rate is also used as the proposed value for the calculation of deferred taxes on export loss relief in the **[LCF](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/loss-carry-forward.md)** workspace.
#### Additional tax rate
Indicates additional taxes:
- For Germany: Enter the valid solidarity surplus (group tax relief) for Germany (5.5%).
- For countries to which the tax template of Germany does not apply: entering data in this field does not trigger any calculations.
### FX Code
The **FX Code** area is displayed as follows:
Configuring currency information of the 'Country' element
**EUR** is set by default as the FX code. Specify the following:
#### FX Code
Indicates the foreign currency associated with the corresponding currency code. The currency code should be three characters long (recommendation: ISO 4217, e.g. EUR, USD), but no more than 10 characters.
> **Note:** - **Exchange rates** must match the consolidation system. Otherwise, there may be differences between Income Taxes and the external system. It is therefore advisable to import the exchange rates from upstream systems (this is also possible via Excel CSV files).
> - Exchange rates can be specified in the indirect quotation (e.g. for USD, entering 1.32814 indicates the price in USD for one euro).
#### Avg FX rate (RC to LC)
The average exchange rate is required for the conversion of the P/L effects of deferred taxes.
#### FX rate (cut-off date, RC to LC)
Indicates the closing exchange rate. This closing exchange rate is required for the **conversion of balance sheet stocks**. The difference from currency conversion is charged or credited to the currency difference of equity in the group financial statements. Exchange rates are also required for the use of reports. The difference from currency conversion is charged or credited to the currency difference of equity in the group financial statements. Exchange rates are also required for the use of reports.
#### Currency with decimal places
Activate if the values of the companies assigned to the country in question are to be displayed with decimal places in the different areas of Income Taxes. This option is activated by default.
---
---
title: "Creating and Finalizing the Declaration"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/create-declaration-report
language: en
last_updated: 2026-10-05
---
# Creating and Finalizing the European Sales List in Lucanet VAT
## Overview of the 'Declaration' Workspace of the European Sales List in VAT
The **Declaration** workspace in the **European Sales List** (ESL) functional area in Lucanet VAT (Value Added Tax) displays the European Sales List of the selected company and period. The European Sales List contains the intra-Community supplies, services, and triangulations that must be transmitted to the Federal Central Tax Office. VAT fills the entries of the declaration automatically via the import of the ERP report **RFASLM00**; in addition, you can add entries manually via **Add**.
The [European Sales List](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list.md) page describes the prerequisites under which the **European Sales List** functional area is displayed.
## Navigation to the 'Declaration' Workspace of the European Sales List in VAT
The **Declaration** workspace can be found under **VAT | European Sales List | Declaration** and is displayed as follows, for example:
The 'Declaration' workspace
## Structure of the 'Declaration' Workspace of the European Sales List in VAT
Above the declaration table, VAT displays the following totals of the European Sales List:
| Total | Description |
|---------|---------|
| Total amount of supplies | Total amount of all intra-Community supplies with type of transaction **0** in EUR |
| Total amount of services | Total amount of all services with type of transaction **1** in EUR |
| Total amount of intra-Community triangulations | Total amount of all intra-Community triangulations with type of transaction **2** in EUR |
| Total amount | Total amount of all entries of the European Sales List in EUR |
**Columns of the declaration table**
The declaration table of the European Sales List in VAT contains the following columns:
| Column | Description |
|---------|---------|
| ser. no. | Consecutive number of the entry. The number is assigned automatically. |
| Country code | Two-digit ISO country code of the EU member state in which the purchaser is established, e.g. **AT**, **FR**, or **NL**. Exception: For Greece, **EL** is used instead of **GR**. |
| VAT ID | VAT identification number of the purchaser or company in another EU member state. Length and format can vary by country. |
| Sum (in EUR) | Consolidated net amount of the tax base per type of transaction and purchaser in full euros without decimal places. Up to three rows can exist for one business partner if intra-Community supplies, services, and triangulations are carried out with this partner. |
| Type of transaction | Type of transaction: **0** = intra-Community supplies, **1** = services, **2** = intra-Community triangulations |
| VAT ID valid | Result of the check of the VAT identification number, if a check was executed |
> **Note:** The values of the European Sales List are transmitted in full euros without decimal places.
## Adding an Entry Manually to the European Sales List in VAT
To add an entry manually to the European Sales List in VAT:
1. In the **Declaration** workspace, click **Add** the plus icon. The **Add** view is displayed:
Adding an entry manually in the European Sales List
2. Fill in the following mandatory fields:
- **Country code**: Two-digit ISO country code in capital letters, e.g. **AT** or **FR**
- **VAT ID**: VAT identification number of the purchaser – a company within the EU. Length and format can vary by country.
- **Tax bases total**: Consolidated net amount per type of transaction and purchaser in full euros without decimal places
- **Type of transaction**: Type of transaction. Possible values: **0 - Supplies**, **1 - Services**, **2 - Intra-Community triangulations**
3. Click **Save** to transfer the entry into the declaration.
If you enter the same country code and the same VAT identification number as for an existing entry, VAT sums up the amounts per type of transaction.
> **Note:** Check whether the serial numbers are consecutive. Missing numbers can indicate faulty rows in the import file that VAT did not import.
## Creating the European Sales List via the Import in VAT
If you have imported and saved the ERP report **RFASLM00** in the [Import](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/import-data-summary.md) workspace, VAT transfers the data into the declaration table of the European Sales List automatically. In addition to the imported entries, you can add further entries manually via **Add** (see section [Adding an Entry Manually to the European Sales List in VAT](#adding-an-entry-manually-to-the-european-sales-list-in-vat)).
## Data Transfer from Company Members into the European Sales List in VAT
For superordinate companies with company members, VAT transfers the ESL data of the company members automatically when you open the **Declaration** workspace. The workspace displays the time of the last transfer under **Last data transfer from company members**.
The following also applies to superordinate companies with company members:
- The **Add** button is not available – the entries originate exclusively from the company members.
- You can only finalize the declaration once all associated company members have finalized their declaration.
## Finalizing the European Sales List in VAT
To finalize the European Sales List in VAT, click **Finalise** in the top right corner.
Depending on the configuration, the button can be deactivated if certain prerequisites are not yet fulfilled – e.g. if the reconciliations have not been executed yet or contain errors.
After finalizing, you transmit the declaration to the Federal Central Tax Office via the [Send declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/send-declaration-report.md) workspace.
> **Note:** Use the **Open ESL** button in the top right corner to reopen a finalized declaration. Alternatively, reopen the declaration via the [Month overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/monthly-overview-report.md) or the [Year overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/yearly-overview-report.md).
## Managing Corrections of the European Sales List in VAT
In VAT, you create a correction of the European Sales List via the [Year overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/yearly-overview-report.md). In a correction, you only enter the correction items – VAT does not display the entries of the previously sent declaration again. For each correction, specify the VAT identification number, the country code, and the correction amount.
Via a drop-down list in the header area of the **Declaration** workspace, you switch between the original declaration and the corrections and view previous declarations.
> **Note:** Do not create corrections for company members in the individual company member, but always via the Year overview in the overall declaration.
## Further Functions in the 'Declaration' Workspace of the European Sales List in VAT
In addition to the [general functions](https://support.lucanet.com/en/documentation/income-taxes/vat/user-interface-general-functions.md), the following functions are available in the context menu of the three-dot icon (⋮) in the top right corner of the **Declaration** workspace of the European Sales List in VAT:
| Function | Description |
|---------|---------|
| Check VAT IDs - VIES | Checks the VAT identification numbers contained in the declaration via the VIES system – the VAT Information Exchange System of the European Commission. The **VAT ID valid** column displays the result. |
| Check VAT IDs - BZSt | Checks the VAT identification numbers contained in the declaration via the Federal Central Tax Office. Only available if the declaration contains German VAT identification numbers. |
---
---
title: "Creating Reorganizations"
description: "In the Reorganizations workspace, you can configure tax accounting adjustments for the entities involved in reorganizations."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-transformations
language: en
last_updated: 2026-05-28
---
# Creating Reorganizations
## Overview
You can create reorganizations and the entities involved in them in the **Reorganizations** workspace.
The details of the individual reorganizations, such as the transferred items and values or the target levels for the receiving entity, are then configured in the **Functions** workspace. How to proceed is described in [Configuring Reorganizations](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions/configure-transformations.md).
## Navigation
The **Reorganizations** workspace is opened under **Master Data | Reorganizations**.
The workspace displays an overview of all **reorganizations** that have already been created and their status, and is displayed as follows, for example:
'Reorganizations' workspace
> **Note:** Reorganizations with the configuration status **Transmitting Entity finished** are hidden in the reorganizations overview. To display these reorganizations, you must activate the **Show all reorganizations** option.
## Technical Prerequisites
The following technical prerequisites must be observed when creating and configuring conversions:
**Taxonomy Type**
For successful execution, the same taxonomy type (e. g. core taxonomy) and the same taxonomy version (e. g. version 6.7) must be used for both entities. If the taxonomies are different, the reorganization is automatically stopped by the system before the adjustment issues are created for the receiving entity. The user then has the option to adjust the taxonomy of the receiving entity and subsequently continue the reorganization.
**Required Permissions**
The permission concept for the reorganization function is designed so that the reorganization can be carried out by different users for the transmitting and receiving entities.
Each user must have the permissions required to **edit tax adjustments**, and the **Execute reorganizations** permission, for the respective entity.
In addition, the following permissions are required to manage the reorganization: **Read reorganizations**, **Edit reorganizations**, and **Reset reorganization status.**
## Creating a Reorganization
To create a reorganization:
1. In the **Reorganizations** workspace, click **Add.**
2. Specify the following in the **New reorganization** dialog:
- Tax balance sheet of the **transmitting entity**
- Tax balance sheet of the **receiving entity**
- An **issue** for the reorganization. The issue serves to document the reorganization process, e. g. to specify the type of reorganization (merger, spin-off, change of legal form, etc.).
- A **comment** on the reorganization (optional)
3. Click **Save**.
The reorganization is displayed in the overview of the **Reorganizations** workspace and can be configured as described in [Configuring Functions](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-single-entity-tax-balance/configure-functions.md).
> **Note:** The selection of the tax balance sheets cannot be subsequently changed. In the case of a faulty selection, the reorganization must be deleted and created again.
---
---
title: "Creating Reports"
description: "You can generate reports of the data entered in Tax Balance in the Reports workspace. In addition, you can create an instance report of the tax balance sheet, which exports the XML-based version transmitted to the tax office into a human-readable and printable format."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/create-reports-
language: en
last_updated: 2026-05-28
---
# Creating Reports
## Overview
Two areas are available for creating reports:
In the **Reporting** functional area, you can create the following reports:
- **Instance report of the tax balance sheet**\
\
You can use this report to export the XML-based version of the tax balance sheet into a human-readable and printable XLS format. You can generate the XML file, which is the basis of the instance report, in the [Transmit E-Balance Sheet](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/transmit-the-tax-balance.md#xml) workspace.
- **Development of taxable and deductible differences**\
\
This report tracks the development of tax adjustments over several years and displays key information, such as balance sheet items, adjustment issues, asset differences, and annual changes. The report can be created for several companies.
You can generate reports of the data entered in **Tax Balance** for a company in the **Reports** workspace of the company.
The following reports are available:
- Value development for current tax balance sheet
- Balance sheet overview with tax adjustments
- Balance sheet overview with tax adjustments - for tax group
- Balance sheet overview with tax adjustments - for tax group (§ 14 KStG (German Corporate Income Tax Act) old version)
- Development of proprietary differences
- Development of proprietary differences by tax adjustment level
- Development of proprietary differences by tax adjustments
- Mapping
- Special balance sheets
- Statement of changes in capital accounts
- Statement of changes in fixed assets
- Supplementary balance sheets
- Tax adjustment overview
## Creating Reports in the 'Reporting' Functional Area
The **Reporting** functional area is opened via the overview and is displayed as follows:
'Reporting' functional area
### Creating an Instance Report
The XML file of the instance report can be generated in the [Transmit E-Balance Sheet](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/transmit-the-tax-balance.md#xml) workspace.
Then proceed as follows to create an **instance report** in the **Reporting** functional area:
1. In the overview, click **Instance report**.
2. Upload the **file** of the instance from which an instance report is to be created.
3. Specify the **encoding** of the instance file.
The encoding of the instance can be read in the first row of the document. The following usually applies:
- Instances originating from Tax Balance have the encoding UTF-16.
- Instances created in Smart Tax Balance and downloaded via Tax Balance have the encoding UTF-8.
- Instances originating from Smart Tax Balance have had the UTF-16 encoding since version 20 and higher.
- Instances from previous versions of Smart Tax Balance have the encoding ISO-8859-15.
4. Click **Create report**.
The report is generated in XLSX format and can be downloaded via the **job monitor** by clicking the bell icon at the top right edge (the bell tb icon).
### Creating a Report on the Development of Taxable and Deductible Differences
To create a **report on the development of taxable and deductible differences** in the **Reporting** functional area:
1. In the overview, click **Development of taxable and deductible differences**.
2. Select the **tax balance sheet group** you want to create the report for.
Only the tax balance sheet groups for which you have the required permissions are available for selection.
3. Click **Continue**.
4. Select the **companies** for which you want to create the report.
5. Click **Create report**.
The report is generated in XLSX format and can be downloaded via the **job monitor** by clicking the bell icon at the top right edge (the bell tb icon).
## Creating Reports in the 'Reports' Workspace
The **Reports** workspace is displayed in the overview as soon as you open a tax balance sheet under **Company**:
'Reports' workspace
To create a report in the **Reports** workspace, click the desired report.
The report is generated automatically after clicking it.
## Downloading Generated Files
After you have created the report, you can download the generated file.
To do this, click the bell icon to open the **job monitor**. The state of the task is then displayed below the task:
Job monitor
The export file is downloaded and saved to your download directory by clicking the corresponding task.
---
---
title: "Creating Tax Balance Sheets"
description: "In the Tax Balance Sheets workspace, you can create your tax balance sheets and assign them to the companies for which the tax balance sheet is to be used."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-tax-balance-sheet
language: en
last_updated: 2026-05-28
---
# Creating and Configuring Tax Balance Sheets
## Overview
In the **Tax Balance Sheets** workspace, you can create your tax balance sheets and assign them to the **companies** for which the tax balance sheet is to be used.
Furthermore, in this step you choose the **taxonomy type** and **taxonomy version** to be used for the tax balance sheet.
## Navigation
The **Tax Balance Sheets** workspace can be opened under **Master Data | Tax Balance Sheets**.
The workspace displays an overview of all tax balance sheets that have already been created and is displayed as follows, for example:
'Tax Balance Sheets' workspace
The overview table contains the following information:
- **Name** of the tax balance sheet
- **Start** and **reporting date** of the tax balance sheet
- **Taxonomy** that has been assigned to the tax balance sheet
- **Number of companies** that have been assigned to the tax balance sheet
## Creating a Tax Balance Sheet
To create a tax balance sheet, click **Add** in the **Tax Balance Sheets** workspace and then configure the steps of the **Create Tax Balance Sheets** dialog as follows:
Step 1 in the 'Create Tax Balance Sheets' dialog
#### 1
Selection of the **previous year** to be used as the basis for the new tax balance sheet
Do one of the following:
- Choose **no previous year** if the tax balance sheet is not to be based on any tax balance sheet from a previous year.
- Choose an **existing tax balance sheet** to be included for the previous year.\
\
The profit difference ([section 60 (2) of the Income Tax Ordinance (EStDV)](https://www.gesetze-im-internet.de/estdv_1955/__60.html)) is calculated in the current tax balance sheet, taking into account the (tax) asset differences from the previous year.
#### 2
- **Balance sheet start**\- is transferred to the e-balance sheet
- **Balance sheet date** \- is transmitted to the e-balance sheet and determines which taxonomy version may be used
- Indication of whether the tax balance sheet should be marked as an **interim financial statement**. As a result, the tax balance sheet is displayed in a special way in some views.
#### 3
**Name** of the tax balance sheet
#### 4
Selection of the **taxonomy type** and **taxonomy version**
> **Tip:** Please refer to the [Notes on Taxonomies](https://support.lucanet.com/en/documentation/income-taxes/tax-balance/master-data-tax-balance/create-tax-balance-sheet/notes-taxonomies.md) for further information.
#### 5
Selection of the **companies** for which the tax balance sheet is to be created
## Editing a Tax Balance Sheet
To edit a tax balance sheet, click the desired tax balance sheet in the overview table.
You can then edit and save the displayed details.
> **Note:** All changes made in this way are applied to all companies assigned to this tax balance sheet.
---
---
title: "Cross-border Adjustments"
description: "While allocations and adjustments are legally distinct concepts, from a technical perspective, cross-border adjustments work similar to tax allocations and FTE & PE allocations."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/cross-border-adjustments
language: en
last_updated: 2026-05-01
---
# Cross-border Adjustments
## Overview
While allocations and adjustments are legally distinct concepts, from a technical perspective, cross-border adjustments work similar to [tax allocations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/tax-allocations.md) and [FTE & PE allocations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/fte-pe-allocations.md).
Cross-border adjustments can be imported as part of the [allocations import](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/cockpit/import.md), but the adjustments can also be manually created. The **Cross-border Adjustments** workspace is used to create cross-border adjustments between the **CE that is subject to the adjustment** and the **CE or member of a Joint Venture (JV) group**. The transferred values affect the CE calculation in the fields **INC-2.13** and **CT-2.17**.
> **Note:** In this article, the **CE that is subject to the adjustment** is called **source CE**, and the **CE or member of a JV group** is called the **target CE**.
## Navigation
The **Cross-border Adjustments** workspace can be found at **Pillar 2 | Entity Data Collection | Cross-border Adjustments**. The workspace is displayed as follows, for example:
'Cross-border Adjustments' workspace
> **Note:** **Notes**:
>
> - Adjustments use the local currency of the source CE.
> - The **Incoming allocations** tab is purely informational. Entering new adjustments or editing existing adjustments must be done outgoing from the source CE.
## Creating Adjustments
In addition to the option to import adjustments, you can also manually create new adjustments in the Pillar 2 module. To create a new cross-border adjustment:
1. In the **Cross-border Adjustments** workspace, select a **period** from the **Applies to period** drop-down menu.
2. Select the **source CE** from the **Company** drop-down menu.
3. Click **Create**.
4. In the subsequently displayed **Allocation Detail** dialog, select the following for your new adjustment:
- A **target CE** from the dropdown list **Other CE or member of JV Group involved in the adjustment**.
- An **adjustment type**:
- Arm’s length adjustments
- Intragroup financing arrangements
5. Enter an amount for the **reduction of the GloBE income of the CE that created this adjustment**.
6. Click **Save**.
> **Note:** **Notes**:
>
> - Optionally, you can upload supporting documents as an **attachment** to the adjustment or add a **description**, e.g. a comment that explains divergences from prior years.
> - After you selected the adjustment type, the value for the **Basis for the adjustment** field is automatically entered.
## Editing Adjustments
In addition to the option to import adjustments, you can also manually create new adjustments in the Pillar 2 module. To create a new cross-border adjustment:
1. In the **Cross-border Adjustments** workspace, select a **period** from the **Applies to period** drop-down menu.
2. Select the **source CE** from the **Company** drop-down menu.
3. Click **Edit**.
4. Select an **adjustment type**:
- Arm’s length adjustments
- Intragroup financing arrangements
5. Update the **reduction of the GloBE income of the CE that created this adjustment** in the local currency of the source CE.
6. Click **Save**.
> **Note:** **Note**: Optionally, you can upload supporting documents as an **attachment** to the adjustment or add a **description**, e.g. a comment that explains divergences from prior years.
---
---
title: "Current Taxes"
description: "For foreign companies, the tax is calculated in the Current Taxes workspace. Unlike German companies, the income assessment is made without using tax workspaces. The structure of the Current Taxes workspace is configured for each country within the master data (Toolbox workspace)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes
language: en
last_updated: 2026-05-28
---
# Current Taxes
## Overview
In the **Current Taxes** functional area, you can calculate the tax for the annual financial statements and prepare the German tax returns. The tax forms are provided as workspaces. In addition, there are special form-independent workspaces, such as **§ 8b KStG**, **TB transfer**, **(Spezial-) Investmenterträge** ((Special) Investment Income), where you can enter the corresponding issues centrally.
In addition to German companies, the tax calculation can also be displayed for foreign companies. You can configure the tax calculation for foreign companies for all countries except Switzerland in the [Master Data | Toolbox](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/toolbox.md) functional area. Unlike German companies, with the exception of Switzerland, the income assessment is made without using tax workspaces.
A separate functional area is available for Switzerland, but with fewer workspaces.
## Prerequisites
Before you can begin editing the tax return, the relevant company must first be created in the [Master Data | Companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) functional area. Then activate the **Current Taxes** milestone in the [Company | Status](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/status.md) functional area to start editing.
You can enter or activate all other master data required for the tax return and the forms required under [Company | Basic data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/basic-data.md) on the tabs displayed there.
## Navigation
You can access the **Current Taxes** functional area under **Company | Current Taxes**. The **Current Taxes** functional area contains several workspaces (see section [Workspaces in the 'Current Taxes' Area](#pworkspace)) and is displayed, for example, as follows:
'Current Taxes' functional area
## Workspaces in the 'Current Taxes' Functional Area
The following **workspaces** are available in the **Current Taxes** functional area — depending on the chosen company and configuration:
- [Tax Liabilities](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/change-of-tax-items.md)
- [Tax Groups](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/tax-groups.md)
- [Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2.md)
- [Gewerbesteuer (Local Tax)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/local-business-tax.md)
- [Corporate Income Tax](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/corporate-tax.md)
- [Reduced Tax Calculation](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2.md)
- [Decomposition](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/decomposition-gewst-kst.md)
- [§ 8b KStG](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/s-8b-kstg---beteiligungen-an-anderen-koerperschaften-und-persone.md)
- [TB Transfer](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/bmg-transfer.md)
- [Zuwendungen (Grants)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/donations.md)
- [Transfer zum OT (Transfer to Tax Group Parent)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/transfer-to-ot.md)
- [Report Tax Balance Based Profit](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/report-stb-profit.md)
- [(Spezial-) Investmenterträge ((Special) Investment Income)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/special-investment-returns.md)
- [Interest Capping Rule](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/interest-capping-rule.md)
- [Transfer zum Anteilseigner (Transfer to Shareholder)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/transfer-to-shareholder.md)
- [Revenue](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/income.md)
- [§ 15a EStG](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/15A-EStG.md)
- [Angaben für MU (Information for Partners)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/information-for-mu.md)
- [Feststellung (Determination)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/feststellung.md)
- [Rollforward LCF](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/rollforward-lcf.md)
---
---
title: "Current Taxes"
description: "In the 'Current Taxes' workspace, you can enter country-specific tax data for foreign companies to calculate taxes. These data are required above all to create the tax rate reconciliation (TRR)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2
language: en
last_updated: 2026-05-28
---
# Current Taxes
## Overview
In the **Current Taxes** workspace, you can enter country-specific tax data for foreign companies to calculate taxes. These data are required above all to create the tax rate reconciliation [(TRR)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Tax-reconciliation-statement.md).
The structure of the **Current Taxes** workspace is configured for each country within the master data in the [Master Data | Toolbox](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/toolbox.md) workspace. After configuration, the corresponding country-specific data can be entered in the **Current Taxes** workspace.
> **Note:** The **Current Taxes** workspace is displayed by default in **condensed** view. All rows with the value 0.00 are hidden in all columns. They can be displayed again with the **Show all lines** button.
> **Warning:** The **Current Taxes** workspace is only available in annual closing periods.
## Navigation
The **Current Taxes** workspace is part of the **Current Taxes** functional area and is displayed, for example, as follows:
'Current Taxes' workspace
## Options in the 'Current Taxes' Workspace
The following special options are available in the **Current Taxes** workspace:
| Option | Description |
|---------|---------|
| Back to tax payer of group | Switches to the superior tax group parent and opens the **Company | Status** workspace. |
| Data lineage by import | Downloads an Excel file with the data imported into Income Taxes. |
| Show all lines | Show also rows with the value 0.00. |
## Details on Selected Aspects
The following sections provide detailed coverage of specific aspects in the context of current taxes:
### Current Tax Calculation – Foreign Countries
By default, the income assessment takes only corporate tax into account.
If the **Local tax column in Toolbox** check box is activated for the chosen company in the [master data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md), it can also be taken into account in a separate column for the income assessment. This allows different assessment bases to be drawn on for the two tax types:
Income assessment taking into account local tax and corporate income tax
It is also possible to enter a comment for each row.
**Starting Value: Profit Before Tax**
The income assessment starts with the **profit before taxes** determined according to local commercial law (not with the result before taxes according to IFRS). Balance sheet and off-balance sheet adjustments are subsequently taken into account.
**Balance Sheet Adjustments (Surplus/Deficit)**
In row 2 ff., the tax surplus/deficit is taken into account and differentiated into a temporary and permanent portion:
Balance sheet adjustments
The proposed values are derived from the **B&S Comparison** functional area ( **Local GAAP - Tax Balance** workspace). Based on the prior period (which is defined when creating the period), Income Taxes determines the change in differences between the local balance sheet and tax balance sheet. The distinction between temporary and permanent differences made in the balance sheet comparison is also taken into account.
The proposed values (thereof temporary differences, thereof permanent differences) can be traced for each balance sheet item on the basis of the balance development using the **Local gaap - tax comparison** report.
### Off-Balance-Sheet Adjustments
All off-balance sheet adjustments are entered by the user (there is also the option of automated import from, for example, Excel tax calculation sheets). The rows available within the dialog are defined in the Toolbox configuration.
Deferred taxes and any tax losses carried forward can also be taken into account in addition to the off-balance-sheet adjustments. Both topics are subsequently covered in separate chapters.
### Tax Rates Used
For corporate income tax purposes, the taxable income is multiplied by the tax rate stored in the master data. The local tax rate is used to calculate the local tax.
Tax rates for local tax and corporate income tax stored in the country master data
For TRR purposes: The individual off-balance-sheet adjustments in the **Corporate income tax (CIT) rate** column are taken into account in the TRR on an issue-specific basis (e. g. tax-free dividends or non-deductible expenses). Off-balance-sheet adjustments for local income tax purposes are processed in total in the TRR row **Local tax (only foreign countries)**.
### Special Issues
Further issues, such as withholding taxes or current taxes entered in the OCI and equity can be entered at the end of the workspace.
## Utilization of and Addition to Losses Carried Forward
Tax losses carried forward are utilized and added in the toolbox in rows 12 and 13 and are linked to the [LCF](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/loss-carry-forward.md) workspace for the purpose of determining deferred taxes.
**Scenario: Addition to Losses Carried Forward**
If the income assessment results in a tax loss, row 13 (Steuerpflichtiges Einkommen für Körperschafts-/Lokale Steuer (Taxable Income for Corporate/Local Tax)) is decisive for the addition to the loss carried forward:
Addition to losses carried forward
The calculated loss carried forward is linked to the **Rollforward LCF** sub-workspace in the **LCF** workspace:
**Scenario: Utilization of Losses Carry Forward**
If the income assessment results in a taxable profit and usable tax losses carried forward are available at the same time, they must be entered in row 12.1 (Nutzung des steuerlichen Verlustvortrags (Utilization of tax loss carried forward)). The loss utilization is also automatically taken into account in the **LCF** workspace.
**Consideration of Corporate Tax and Local Tax**
If the column used to calculate the local income tax (local tax in Toolbox) is activated in the master data, the respective addition and utilization of the loss carried forward with regard to local income tax is taken into account (in the **LCF** workspace: Tax losses carry forward local tax).
### (Pre-)Tax Group Excess and Deficit Transfers
Asset differences between commercial and tax balance sheets at the level of the tax group member mean that the profit transferred to the tax group parent falls short of (deficit transfers) or exceeds (excess transfers) the tax balance sheet profit of the tax group member.
A distinction must be made here between pre-tax group excess and deficit transfers (section 14 (3) of the Corporate Tax Act) and tax group excess and deficit transfers (section 14 (4) of the Corporate Tax Act).
The tax group and pre-tax group asset differences of the tax group member calculated outside of Income Taxes (e. g. in Tax Balance) must be included in Income Taxes for the preparation of the tax return.
### Pre-Tax Group Excess and Deficit Transfers
Therefore, according to section 14 (3) of the Corporate Tax Act, an active or passive balancing item must be created at the level of the tax group parent.
The rows are used further according to their name. Here is a brief explanation:
- **N-4.0:** total of all pre-tax group excess transfers (total of N-4.1 to N-4.3).
- **N-4.1:** You can enter pre-tax group excess transfers in accordance with section 14 (3.1) of the Corporate Tax Act here, provided they do not come from the tax contribution account. If data are imported from Tax Balance, the corresponding import value is inserted as a proposed value in this row.\
\
A different assessment will be necessary if the excess transfer is taken from the tax contribution account or no issue according to section 8b of the Corporate Tax Act is to be created. In these cases, the proposed value is entered in rows N-4.2 or N-4.3 according to the tax treatment. The value in row N-4.1 must be adjusted accordingly.\
\
Values in row N-4.1 are transferred to the **OG attachment** and the **KSt1F** form of the respective tax group member for the preparation of the tax return. Furthermore, an automatically generated issue in accordance with section 8b (1) of the Corporate Tax Act with the corresponding capital gains tax will be triggered at the tax group parent by saving the assessment basis transfer.
- **N-4.2:** Pre-tax group excess transfers from the tax contribution account are entered here. The data entered here are further processed accordingly for the tax group member on the **KSt1F** form and in the **OG attachment**. No issue according to section 8b of the Corporate Tax Act is created in this case.
- **N-4.3:** Pre-tax group excess transfers that do not come from the tax contribution account are entered here. The entry is further processed accordingly in **KSt1F** and the **OG attachment**. In contrast to row N-4.1, no issue in accordance with section 8b (1) of the Corporate Tax Act with the corresponding capital gains tax is transferred for the tax group parent. If it is a tax-free distribution, a corresponding issue must be created manually in the **§8b KStG** (Corporate Tax Act, section 8b) workspace for the tax group parent (pre-tax group excess transfer without capital gains tax withholding).
**Note for the Tax Return:**
If it is a tax-free distribution, enter it in the tax return of the tax group member in row D11.2.5 of the **GK attachment** "Davon vororganschaftliche Mehrabführungen (ohne Einlagekonto; Anlage eines Sachverhaltes im Sinne d. § 8b Absatz 1 KStG auf Ebene des (Z)OT ohne KapESt und SolZ)“ ("Of which pre-tax group excess transfers (without contribution account; creation of an issue in accordance with section 8b (1) of the Corporate Tax Act at the level of the (I)TP without capital gains tax and solidarity surcharge)"). In this case, an issue according to section 8b of the Corporate Tax Act is automatically created for the tax group parent.
- **N-5.1**: Pre-tax group deficit transfers in accordance with section 14 (3.2) of the Corporate Tax Act must be entered here. They are processed accordingly on **KSt1F** and in the **OG attachment** for the respective tax group member.
- **N-6:** Tax group excess transfers in accordance with section 14 (4.1) of the Corporate Tax Act must be entered here. The values are included in the OG attachment and made available to the tax group parent by means of the TB transfer for processing in the **OT attachment** and on **KSt1A**.
- **N-7**: Tax group deficit transfers in accordance with section 14 (4.1) of the Corporate Tax Act must be entered here. The values are included in the **OG attachment** and made available to the tax group parent by means of the TB transfer for processing in the **OT attachment** and on **KSt1A**.
- **MM_CHECK**: The tax group and pre-tax group excess and deficit transfers are entered in detail in rows N-4.0 to N-7. The deviations between the commercial balance sheet and tax balance sheet (section 60 (2) of the Income Tax Ordinance), which were entered when determining the tax balance sheet profit, are validated with the values in rows N-4.0 to N-7 in the MM_CHECK row. The control value should be € 0.00. This validation is only for reconciliation purposes and does not affect any milestones or other value transfers.
### Tax Group Excess and Deficit Transfers
**Legal status for fiscal years ending after December 31, 2021**:
- According to section 14 (4) of the Corporate Tax Act, an active or passive balancing item for tax group relationships must be consequently created at the level of the tax group parent.
- The tax group balancing items are developed for each tax group member and entered in the **Current Taxes** workspace in Income Taxes.
- As part of the system change to contribution solution, the tax group balancing items had to be dissolved and transferred to the investment account.
**Legal status for fiscal years beginning after December 31, 2021**:
- During the tax group period, deficit transfers are to be treated as contributions and excess transfers as return of contributions, which increases or decreases the investment book value of the tax group member at the tax group parent accordingly.
- Tax group excess and deficit transfers are entered as follows:
- GK attachment, row D11.2.1: Mehrabführungen (Excess transfers)
- GK attachment, row D11.2.2: Minderabführungen (Deficit transfers)
---
---
title: "Current Taxes in Switzerland"
description: "There is a three-tier taxation system of federal government, cantons, and communes in Switzerland, with each level having the right to levy its own taxes. The tax calculation differs across the 26 cantons. To apply the Swiss tax calculation specifically in Income Taxes, you can activate the Swiss Tax Law function in the country master data. Individual flags must be activated for this purpose."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2/currency-taxes-switzerland
language: en
last_updated: 2026-05-28
---
# Current Taxes in Switzerland
## Overview
There is a three-tier taxation system of federal government, cantons, and communes in Switzerland, with each level having the right to levy its own taxes. The tax calculation differs across the 26 cantons.
To apply the Swiss tax calculation specifically in **Income Taxes**, you can activate the **Swiss Tax Law** function in the [country master data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/countries.md). Individual flags must be activated for this purpose.
We can provide you with an Excel template, which you can use to maintain and import cantonal and municipal tax rates. We do not provide continuous updates of the tax rates.
> **Warning:** The Swiss tax calculation is an optional function that must be activated individually. If you would like to use the Swiss tax calculation, please contact us at [gtc-support@lucanet.com](https://platform.openai.com/chat/edit?models=gpt-4o).
---
---
title: "Data Export"
description: "The flexible export currently supports the creation of a CSV file with data from the trade tax allocation (GewStZ) and the generation of CSV and PDF files based on custom reports."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/data-export
language: en
last_updated: 2026-05-28
---
# Data Export
## Overview
The flexible export currently supports the creation of a CSV file with data from the trade tax allocation (**GewStZ**) and the generation of CSV and PDF files based on **custom reports**.
## Navigation
The **Data Export** workspace can be found under **Company | Data Export** or under **Reporting | Data Export**.
The **Data Export** workspace is displayed, for example, as follows:
Workspace 'Data export'
## Requirement for the Data Export
To export data, an interface structure must be created under **Master Data | Interface | Structure**.
Creating an interface structure in the master data
> **Note:** You can find details on creating interface structures in [Structure](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces/interfaces-structures.md).
## GewStZ Export (Trade Tax Allocation Export)
To export trade tax allocation data, you must configure the following settings with a name of your choice:
Exporting trade tax allocation Data
## Export with Custom Reports
The prerequisite for this case is that you have previously created a custom report of type **Export** under **Reporting | Reporting Engine**.
> **Note:** To create a custom report of type **Export** under **Reports | Reporting Engine**, you must have the **System Administrator – Edit** permission.
On this basis, a data export can now be configured. When the export is executed, the custom report is generated and the data from one worksheet of this Excel file are read out and exported in CSV format. The following settings must be made in the **interface structure**:
Configuring data export
The following details are particularly important:
- The **Custom Report** entry,
- The Excel sheet from which the data are taken
- The row of the Excel sheet in which the export should start (skip header rows)
- The target that specifies whether the export is made available as a download, exported to the specified file path, or exported to a database table
> **Warning:** When exporting to a **database table**, the **Excel sheet name** must match the table name from the database. In addition, the column names in the report must match the column names in the database table.
Optionally, specify a restriction in the **Milestone** drop-down list. This means that the export may be performed only when a specific milestone has been reached.
Selecting the milestone that must be in a specific state before export
## Specifying the Complete File Path
In the **Absolute file path** field, the name of the export file must be entered with a complete and valid path of the web server, e. g.:
C:\\temp\\Exportdatei.csv
The path must exist on the web server, which means Income Taxes does not explicitly establish an FTP connection or similar connection.
Placeholders (in curly brackets) can be used for specific values (e. g. the current date) both in the path and in the file name. These placeholders are replaced by the current values when the export file is generated. To include the ID of the current company in the name, you must, for example, use the **UNITID** placeholder:
`C:\temp\Export_{UNITID}.csv`
The following placeholders are currently available:
- {YYYY}: year of the current period
- MM}: month of the current period
- {DD}: day of the current period
- {year}: year of the date
- {mon}: month of the date
- {day}: day of the date
- {hour}: hour of the date
- {min}: minute of the date
- {sec}: second of the date
- {PERIODID} ID of the current period
- {UNITID}: ID of the current unit
- {USERID}: ID of the current user
- {USERNAME}: name of the current user
- {BUKRS}: reporting entities of the current company according to **Master Data | Company | Additional company codes**
The placeholders can also be used in the path to store files in different directories, for example by the year and month:
`C:\temp\{year}\{mon}\Export_{UNITID}.csv`
## Automatic Export
In the interfaces, the **Trigger export automatically upon** option is also displayed if the **Export** and **Custom Report (csv)** options have been chosen:
Configuring automatic export
> **Warning:** Please note the following when using the automatic export: The **{UNITID}** (see [Specifying the Complete File Path](#filepath)) must always be specified in the absolute file path of the automatic export.
A standard interface configured in this way is displayed in the **Interface** drop-down list in the **Data Export** workspace, where it can be chosen:
Configuring the interface in the ‘Data Export’ workspace
An interface chosen here checks within the period whether the milestone chosen in the interface has been closed, and then performs the export. The **Absolute file path** field needs to be filled for this type of export.
In contrast, **export interfaces** can also be assigned to a company. If export interfaces are assigned to a company, only the exports assigned to that company are performed.
These exports can be triggered either by manually closing the milestone or by import in the subgroup area.
## Export Procedure
To start the data export:
1. Open the **Data Export** workspace.
Workspace 'Data export'
2. Select the required **Interface**.
3. Click **Export** to start the export.
4. If no absolute file path was specified, the file is downloaded directly from the browser. If a path was defined as described above, the file is stored under the name specified there. If an additional PDF export is optionally required, it is stored under the same name as the CSV file (with the extension .PDF).
---
---
title: "Data Transfer"
description: "The Data Transfer workspace is used to store, display, and adjust imported values that are required for reports, posting documents, and validation, but do not flow directly into the balance sheet comparison. Typical cases of use are account information and account balances from source systems that are supplied with the import and are to be used in calculations or exports at a later point of time."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/data-transfer
language: en
last_updated: 2026-05-28
---
# Data Transfer
## Overview
The **Data Transfer** workspace is used to store, display, and adjust imported values that are required for reports, posting documents, and validation, but do not flow directly into the balance sheet comparison. Typical cases of use are **account information** and **account balances from source systems** that are supplied with the import and are to be used in calculations or exports at a later point of time.
Entries in the **Data Transfer** workspace cannot be created manually. They are created exclusively by means of the import (e.g. by file import, RFC, or REST service – at both the individual company and mass import level). However, existing entries can be corrected manually in the **Manual adjustment** column.
> **Warning:** - A prerequisite for displaying the **Data Transfer** workspace is the corresponding permission (see [Permissions](https://support.lucanet.com/en/documentation/income-taxes/tax-administration/roles.md)).
> - The workspace is not available in planning periods and periods for which the tax calculation is deactivated.
## Navigation
The **Data Transfer** workspace is opened under **Company | Data Transfer**. The **Data Transfer** workspace is displayed, for example, as follows:
'Data Transfer' workspace
## Workspace Structure
The **Data Transfer** workspace consists of a table with the following columns:
| Column | Description |
|---------|---------|
| Account ID | The technical identifier (key) of the imported position |
| Business Unit | The identifier of the corresponding reporting entity |
| Import value | The value imported from the source system. This field cannot be edited manually. |
| Manual adjustment | A correction value that you can enter manually (positive or negative) |
| Info | A tooltip icon that shows when and by whom the manual adjustment was last changed |
| Total | The automatically calculated total of **Import value** and **Manual adjustment** |
> **Note:** The date and name of the last import are displayed below the company and period selection.
The table can be exported as an Excel or PDF file using the integrated export function. In addition, the values can be used by means of technical IDs in reports and validations (see [Technical Export](#te)).
## Adjusting Values Manually
You can enter or change the values in the **Manual adjustment** column manually, provided the period is not closed and you have the **Edit** permission. To adjust a value manually:
1. Navigate to the **Data Transfer** workspace.
2. Enter the desired correction value in the **Manual adjustment** column. Positive and negative values are permitted.
3. The **Total** column is automatically calculated and updated from **Import value** and **Manual adjustment**.
4. Click **Save**.
> **Note:** Each change to the manual adjustment is logged with the date, time, and name of the user. This information is available via the tooltip icon in the **Info** column.
## Importing into the 'Data Transfer' Workspace
Values are imported into the **Data Transfer** workspace by the import (e.g. by file import, RFC, or REST service – at both the individual company and mass import level). Import into the data transfer is supported by both mapping variants:
- **Default mapping**: In the mapping table, TAX.TIMPORT. is entered as the target item. Each mapping row maps a source item to exactly one item ID in the data transfer.
- **Extended mapping**: The TIMPORT target dialog is used with a freely definable item identifier (Target Line) as mapping target. It can also be composed dynamically from several source columns.
## Behavior with Existing Data
By default, existing entries are not automatically removed by the import. If a key already exists, the imported value is overwritten by the newly imported value. Any keys that are not included in the current import remain unchanged. An import with the value 0.00 does not delete the entry, but sets the import value to 0.00.
This default behavior can be adjusted in the interface configuration. The **Importwert zurücksetzen (Reset import value)** and **Manuelle Anpassung zurücksetzen (Reset manual adjustment)** settings can be used to control whether the existing imported values and/or manual adjustments are to be reset before the import. If both options are activated, all existing entries for the company and period are deleted completely before the import – after the import, the data transfer contains only the newly imported entries.
### Behavior with Closed Milestones
The **Data Transfer** workspace itself is not linked to a milestone. The editability of the dialog depends solely on whether the period is closed.
There is one special aspect for the import: even when milestones such as **Current taxes** or **Deferred taxes** are closed, values can still be imported into the **Data Transfer** workspace. In this case, only the data transfer values are imported. Values for other workspaces/dialogs such as the **B/S Comparison** are not imported.
## Technical Export
The values from the **Data Transfer** workspace can be exported by means of technical IDs. This allows the values to be used in validations and standard reports.
The following technical IDs are available for the export:
| Technical ID | Description |
|---------|---------|
| `DataTransfer_ERP_[_]` | Import value |
| `DataTransfer_CORR_[_]` | Manual adjustment |
| `DataTransfer_SUM_[_]` | Total of import value and manual adjustment |
The **** placeholder corresponds to the item no. and **** to the optional business unit identifier. The business unit identifier is omitted if only one standard reporting entity exists.
The data transfer values are available by means of the technical IDs in all areas that use the central export mechanism. They include, among others, standard reports, posting documents, flexible validation (validation type = 4), and the value transfer to the **Pillar 2** and **CbCR** sub-modules.
## Period Copy and Transaction Data Copy
### Period Copy
When you create a new period with a transaction data copy, the contents of the **Data Transfer** workspace are automatically transferred to the new period. No data transfer values are copied in summary periods.
### Transaction Data Copy
To transfer data transfer values using the transaction data copy:
1. Open the **Company | Status** workspace.
2. Open the **Copy transaction data** dialog.
3. Activate the **Data Transfer** check box.
4. Start the copy process.
The copied values appear at the same place in the target period as in the source period.
**Behavior with existing data in the target period:** The transaction data copy does not delete existing entries in the target period. A merge behavior applies instead:
- Entries that exist in both the source period and target period (same key) are **completely overwritten** – including the import value, manual adjustment, total value, and adjustment date and user.
- Entries that exist only in the source period are **added** to the target period.
- Entries that exist only in the target period remain **unchanged**.
> **Warning:** Since the manual adjustments from the source period are also transferred when keys match, any existing manual adjustments in the target period may be lost.
### Period Transfer (Import/Export)
In the period transfer (import and export of a period), the values of the **Data Transfer** workspace are also transferred.
## Permissions
The **Data Transfer** workspace has its own **DataTransfer** permission object with the following configurations:
| Configuration | Description |
|---------|---------|
| Read | Displays the **Data Transfer** workspace. The values are visible but cannot be changed. This permission is a prerequisite for accessing the workspace. |
| Edit | Edits the manual adjustments in the **Data Transfer** workspace. This permission requires **Read** permission – the Edit permission alone is not sufficient to open the workspace. |
> **Warning:** The **Data Transfer** workspace cannot be accessed without **Read** permission. For full use (viewing and editing), both permissions are required.
## Write Protection
The **Data Transfer** workspace is write-protected when one of the following conditions applies:
- The period is closed.
- You only have the **Read** permission.
In write-protected mode, all input fields in the **Manual adjustment** column are deactivated. The values can still be viewed, but not changed.
> **Note:** Permissions can be granted and changed by authorized users in the [Tax Administration](https://support.lucanet.com/en/documentation/income-taxes/tax-administration.md) module.
---
---
title: "Data Transmission"
description: "The Data transmission workspace is used for the electronic transfer of the tax return. In this workspace, you can perform a test run including transmission before the final transmission."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/data-transfer
language: en
last_updated: 2026-05-28
---
# Data Transmission
## Overview
The **Data transmission** workspace is used for the electronic transfer of the tax return. In this workspace, you can perform a test run including transmission before the final transmission.
## Navigation
The **Data transmission** workspace is opened under **Company | Electronic Transmission | Data transmission**. The **Data transmission** workspace is displayed, for example, as follows:
'Data transmission' workspace
The table shows all transmission processes created for tax returns of the chosen period and their processing status.
> **Note:** Any live transmission that have been carried out can no longer be deleted from Income Taxes. They are permanently stored in the **Electronic Transmission | Data transmission** workspace.
## Tax Return Transmission Process
To transmit a tax return, the following process must be completed:
1. In the [Validation](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/validation-electronic-transmission.md) workspace, check the entries currently made in the workspaces (forms).
2. Click the **Start transmission** button. The Dialog **Preparing for transmission – Step 1** is displayed:
Preparing for transmission - Step 1
3. Choose one of the following options:
- Choose the tax type for which the transmission process is to be started from the **Type of tax** drop-down list.
- Choose the snapshot you want to use from the **Snapshot** drop-down list or specify whether a new snapshot is to be created.
- In the **Version of the mapping** drop-down list, select the mapping version. The latest mapping version is usually chosen here.
> **Warning:** **Snapshots in transmission**
>
> Data transmissions always use a snapshot. Therefore, subject the tax calculation to a validation process before creating the snapshot. At least one valid snapshot is required for the electronic test transmission and the live transmission.
4. Once all data have been entered, click the **Continue** button to execute the second process step.
Preparing for transmission - Step 2
The following options are available in the **Preparing for transmission – Step 2** dialog:
Option
Description
Datum zur Unterschrift (Signature date)
Enter the date
Ort zur Unterschrift (Place of signature)
Enter the place here
Über die Angaben in der Steuererklärung hinaus sind weitere oder abweichende Angaben oder Sachverhalte zu berücksichtigen (Any additional or deviating information or issues that go beyond the tax return are to be taken into account)
Activate the check box if you want to provide additional or deviating information beyond the tax return. The data entered in the **Ergänzende Angaben zur Steuererklärung** (Supplementary information for the tax return) free text field is transmitted to the tax office if this check box is activated.
Hints
The displayed notes must be confirmed with the check boxes to generate a snapshot.
5. Click the **Start now** button to initiate the data transmission process. The transmission process is displayed, for example, as follows:
Transmission process: Click the triangle to the left of a process step to show more information about each step.
### Preparation
The following information is displayed in the **Preparation** section:
- **Zusammenfassungsbericht (Summary report)**: The data ready for transmission are displayed here in summarized form. No adjustments by the user are necessary. The forms to be transmitted in the next step are indicated by a green check mark.
- **Anreicherung (Enrichment)**: A (technical) file (**Steuerfall.xml**) is _generated_ during each transmission process. This is visible in the **Enrichment** step.
- **Validation results**:
- ERiC error messages from the tax authority that prevent transmission
- Confirmations of successful validations
- **Test dispatch**: If the **validation** was successful, the protocol is displayed here as a PDF file.
### Review
The following information is displayed in the **Review** section:
- **More actions**: This function allows you to attach files to the Submission step. They are not transmitted and are used only to document your decision. Only PDF files are allowed.
- **Reject**: Clicking the **Reject** button opens a window with a free-text field. You can enter the reason for rejection and confirm the rejection here. The data transmission is stopped and the rejection is automatically documented in the workflow. To transmit the data successfully, start a new transmission process afterwards.
- **Accept**: Clicking the **Accept** button opens a window with a free-text field. Here you can enter a comment for the review and confirm the review. The data are then transmitted to the responsible authority.
## Perform the next steps in the process
Once you have checked for any validation errors in the **Transmission** dialogue or carried out other actions, the corresponding next step will be activated. You can also start the individual process steps directly from the table by clicking on one of the icons in the Status column:
- Steps that have already been completed are highlighted in green and marked with a check mark.
- The next step due to be taken is outlined in green.
- Steps that cannot yet be executed are outlined in grey.
Status mit Buttons für Prozessschritte
## Sending Corrections
You can transmit corrections by re-running the transmission process. Proceed as follows:
1. Open the **Company | Electronic Transmission | Data transmission** workspace.
2. Click the **Start transmission** button and carry out the transmission process, as described before, in the same way as for the initial transmission of the tax return.
> **Warning:** Income Taxes assigns correction ID **0** to the initial data transmission. Each additional successful live transmission increments the correction transmission counter by 1.
>
> All transmissions can be viewed in the overview table under **Company | Electronic Transmission | Data transmission** workspace. You can track the number of corrections there in the **Korrekturnummer (Correction number)** column.
## Fast Entry
Additional values for the purpose of the tax return can be entered in the [Fast Entry](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/fast-entry.md) workspace based on what are referred to as ERiC IDs. This ensures that all rows of the forms can be transmitted – including those that may not yet be available in Income Taxes.
---
---
title: "Decomposition"
description: "This section describes the trade tax allocation and corporate income tax allocation."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/decomposition-gewst-kst
language: en
last_updated: 2026-05-28
---
# Allocation (Trade Tax Allocation and Corporate Income Tax Allocation)
## Overview
This section describes the **trade tax allocation** and **corporate income tax allocation**.
## Allocation Modes
The **trade tax allocation** and **corporate income tax allocation** can be used in different modes, depending on the respective customer-specific configuration:
#### Trade Tax Allocation
- Allocation based on the payroll (standard case)
- Allocation with several allocation scales
- Allocation with several allocation scales and upper-level allocation
In the latter two cases, the allocation details are defined by the tax group parent.
#### Corporate Income Tax Allocation
- Allocation based on the payroll (standard case)
- Allocation with several segmentation scales
In the latter case, the allocation details are defined by the tax group parent.
## Navigation
You can access the **Decomposition** functional area under **Company | Current Taxes | Decomposition**. The **Decomposition** functional area contains up to three forms, depending on the chosen period and company.
The **Local Tax Segmentation** form is displayed, for example, as follows:
'Decomposition' workspace
## Forms in the 'Decomposition' Functional Area
The following forms are available for the **Decomposition** functional area:
| Option | Description |
|---------|---------|
| KSt-Zerlegung (Corporate Income Tax Allocation) | If the corporate income tax amounts to at least an absolute value, i. e. a positive or negative amount of € 500,000, the corporate tax must be allocated. You can enter the branches and the allocation scale in the **KSt-Zerlegung** workspace. Data already entered in the **Local Tax Segmentation** workspace can be included in the corporate income tax allocation. For investments in partnership companies, data may need to be supplemented. The entered data are transmitted to the tax office in the **Erklärung für die Zerlegung der Körperschaftsteuer (Declaration for the Allocation of Corporate Income Tax)** together with a **Branch attachment** for each affected municipality and, if necessary, the **Beteiligung (Investment) attachment**. |
| Local Tax Segmentation | If a commercial enterprise has branches in several municipalities, the trade tax is levied proportionally according to the tax assessment amount in each municipality. This amount must be divided among the affected municipalities. You can enter the branches and the allocation scale in the **Local Tax Segmentation** workspace. The entered data are transmitted to the tax office for each affected municipality in the **Erklärung für die Zerlegung des Gewerbesteuermessbetrags (Declaration for the Allocation of the Trade Tax Assessment Amount)** together with a **Branch attachment**. |
| Anlage Bekanntgabe (Notification Attachment) | The **Anlage Bekanntgabe** form can be used to give consent to the digital receipt of the notice of trade tax allocation. **Note**: This option should be selected only if the enterprise meets the technical requirements for receiving tax assessment notices electronically. A business account must be set up for this purpose. If the delivery is made to a tax consultant, they too must be technically able to receive digital deliveries. Detailed information on this topic and the business account can be found, for example, on the web site of the Hessian Ministry of Finance at [Der digitale Gewerbesteuerbescheid für Unternehmen und Steuerberatende | digitaler Gewerbesteuerbescheid (The Digital Trade Tax Assessment Notice for Enterprises and Tax Consultants | Digital Trade Tax Assessment Notice)](https://www.digitaler-gewerbesteuerbescheid.de/unternehmen). |
## Tabs on the Local Tax Segmentation and KSt-Zerlegung Forms
The tabs
- [Tax payer of group](#organ)
- [Selection of cities](#gemeinde)
- [Company](#company)
are included in both forms and are described in the following sections.
### 'Tax payer of group' Tab
The **Tax payer of group** tab displays an overview of the entries of all tax group members. By default, the display is aggregated by municipalities and sorted by values in descending order. When using several allocation scales, the values are aggregated according to the allocation defined by the tax group parent. Alternatively, the display can also be aggregated by companies.
### 'Selection of cities’ Tab
You can compile the municipalities required for your entries on the **Selection of cities** tab. Proceed as follows:
1. Choose one of the municipalities present in the Income Taxes database together with its master data in the **Multiplier selection** area by clicking **+**.
Compiling municipalities using the list
2. If a municipality is missing, you can add a municipality together with its community key in the **Multiplier input** area.
3. The list of all municipalities compiled for the current company is then displayed in the upper area of the **Selection of cities** tab:
List of all municipalities compiled for the current company
4. If necessary, add the post code, tax number, and local tax rate details.
5. If necessary, mark a municipality as the location of the management.
> **Note:** The post code, tax number, local tax rate, and management details are required for the Elster transmission.
### 'Company’ Tab
You must enter the values for the payroll (or other and additional allocation scales) for each municipality on the **Company** tab.
'Company' tab
> **Warning:** The **Company** tab is not displayed if the company is a tax group member or an interim tax group parent.
**Cities from GewStZ**
The **Cities from GewStZ** function is additionally available on the **Company** tab on the **KSt-Zerlegung** form.
'Cities from GewStZ' function on the 'KSt-Zerlegung' form
**Cities from GewStZ** is used to transfer all municipalities and the corresponding values (e. g. payroll, etc.) from the trade tax allocation. Municipalities that have already been set up in the corporate income tax allocation are not deleted, but, if necessary, are overwritten with the current data from the trade tax allocation.
### 'Zerlegung des Gewerbesteuermessbetrages' (Allocation of Trade Tax Assessment Amount) Tab
The **Zerlegung des Gewerbesteuermessbetrages** tab is also displayed on the **Local Tax Allocation** form **.**
The allocation of the local tax assessment amount is required whenever an enterprise has branches in several municipalities. The uniformly determined trade tax assessment amount must then be allocated to the various municipalities to allow each municipality to levy its share of the local tax.
## Importing Data
As an alternative to manual entry, the data of a company can be imported also via the flexible interface. The tax group parent can import the data for several companies across the tax group. A CSV file can be uploaded here, provided the interface structures have been pre-defined in the [Master Data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces.md) area.
> **Note:** **Please note**:
>
> - Numbers in the CSV file to be imported must be displayed without thousands separators.
> - A period must be used as the decimal symbol in the CSV file to be imported.
To import a CSV file:
1. Click **Import** on the **Company** tab.
2. Specify the CSV file to be imported in the subsequent dialog.
3. The data for a company are updated or newly created according to the import file (see **Import Results** in the following for further information).
### Import Results
A data import generates the following results:
- Any existing entries for a municipality at a company are deleted if no corresponding data are present in the import file.
- The import can be performed also if no municipalities have yet been assigned to the company. In this case, the existing municipalities in the import file are stored for this company and provided with the values from the import file.
- Data for a company can be **added iteratively**. Assuming two interface structures have been defined:
- The first interface structure contains the company code, the information on the municipality, and the values of the first allocation scale.
- The second interface structure contains the company code, the community key, and the values of the second allocation scale and the upper-level allocation.
If an interface structure has been defined in this way, the values can be imported sequentially by means of two files. They are merged on the Income Taxes side. It should be noted that both files include the same company code and community key. In this case, the value **0** may need to be imported to ensure this prerequisite is fulfilled.
---
---
title: "Deferred Taxes"
description: "The Deferred Taxes functional area contains a number of workspaces in which deferred tax assets and liabilities are calculated. Which workspaces are displayed depends on the company currently selected and the master data configuration."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes
language: en
last_updated: 2026-05-28
---
# Deferred Taxes
## Overview
The **Deferred Taxes** functional area contains a number of workspaces in which deferred taxes can be calculated for tax reporting in accordance with IAS 12 and Section 274 HGB, and corresponding note disclosures can be generated.
Which workspaces are displayed depends on the company currently selected and the master data configuration.
## Navigation
The **Deferred Taxes** function area is displayed under **Company | Deferred Taxes**.
**B/S Comparison | Total** is a workspace within **Deferred Taxes** and is displayed as follows, for example:
'Deferred Taxes' section
## Workspaces in the 'Deferred Taxes' Section
The following workspaces are available in the **Deferred Taxes** section — depending on the selected company and the configuration:
- [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md)
- MVB (only optionally available)
- [LCF (Loss carried forward)](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/loss-carry-forward.md)
- [OBD](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/obd.md) (only optionally available)
- [Others](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/other-def-taxes-ind-company.md)
- [Summary](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/result-sheet.md)
- [TRR](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Tax-reconciliation-statement.md)
- [Reports](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/Reports-company-workspace.md)
---
---
title: "Deferred Taxes of (Sub-)Group"
description: "The workspace Deferred Taxes in the (Sub-) Group area aggregates the deferred tax assets and deferred tax liabilities calculated in the Company workspace."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/sub-group/deferred-taxes-subgroup
language: en
last_updated: 2026-05-28
---
# Deferred Taxes of (Sub-)Group
## Overview
The workspace **Deferred Taxes** in the **(Sub-) Group** are aggregates the deferred tax assets and deferred tax liabilities calculated in the **Company** workspace. The view is divided into several table areas:
- Display of current deferred taxes per company
- Recording of consolidation adjustments
- Addition/disposal of companies
- Deferred taxes summary
## Navigation
The **Deferred Taxes** workspace is displayed under **(Sub-) Group | Deferred Taxes** for example as follows:
group")'Deferred taxes' workspace for a (sub-) group
## Display of Current Deferred Taxes per Company
The first table area displays the current balances of deferred taxes and the corresponding P&L or OCI effects. The view begins with the tax group members and intermediate tax group parents. In the event that the option **Deliver deferred taxes** is activated in the master data ([Companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) workspace), the deferred taxes are consolidated at the level of the tax group parent:
Deferred taxes at the tax group parent level
In the event that the option **Deliver deferred taxes** is not activated, the deferred taxes are consolidated per tax group member. The total after offsetting is the same in both variants.
The other dependent companies are listed under the tax group members. The offsetting of deferred taxes is carried out in accordance with IAS 12 only at the level of the respective individual company.
Offsetting deferred taxes
In the upper area, the list can be used to restrict the countries displayed. For example, only German companies can be filtered in the view.
In addition to displaying the current deferred tax assets and deferred tax liabilities, there is the table sub-area **Change**:
| Column | Description |
|---------|---------|
| Deferred Taxes | Aggregated change in deferred tax balance |
| Expense (Profit) | Change in deferred taxes affecting P&L |
| Other Comprehensive Income | Change in deferred taxes affecting OCI |
| Currency Exchange | Foreign currency translation is explained in a separate [chapter](https://amana.atlassian.net/wiki/spaces/GTCD23/pages/81239409/W+hrungsumrechnung). |
| Addition/Disposal | These columns identify companies that, according to the master data ([Companies](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/companies.md) workspace), have been added or disposed of compared to the prior period. In addition, a separate display of these companies is provided further down in the workspace. |
The display of maturities for deferred tax balances is related to the setting **Including balancing (Accounting standard: IFRS)** from the company master data. If this is activated, short-term and long-term deferred taxes are displayed.
## Recording of Consolidation Adjustments
For purposes of the consolidated financial statements, in addition to the deferred taxes at the reporting data level (= area **Company**), the deferred taxes attributable to consolidation postings must also be taken into account.
Consolidation postings are recorded in the **Adjustment** area:
Group | Deferred Taxes’ workspace") Consolidation adjustments in the ‘(Sub-)Group | Deferred Taxes’ workspace
Several preset consolidation types are available for recording in the workspace described here. A new record is created via the plus symbol. The corresponding deferred taxes can then be recorded.
## Deferred Taxes Summary
At the end of the workspace **Deferred Taxes** for a subgroup is the **Deferred taxes summary** table area. This area aggregates the deferred taxes at the company level (or reporting data level) and the group postings (if recorded):
Deferred taxes summary
The column **Current Period** can be reconciled with the values from the table area **Display of current deferred taxes per company**(columns **Deferred tax assets** and **Deferred tax liabilities**). The column **Adjustment** or **Adjustment (corr.)** corresponds with the indication of changes per company.
### Validation
A validation is performed below the table. The value must equal zero. If a non-zero amount is displayed there, this is an indication of an incorrect validation of the summary. The change in deferred taxes (sub-group level) compared to the prior period is validated.
---
---
title: "Detail Results"
description: "The Allocations workspace displays a table with different information about allocations between a source CE and a target CE. It is possible to export the assignment as an Excel file or as a pdf."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation/allocations
language: en
last_updated: 2026-05-01
---
# Detail Results
## Overview
The **Detail Results** workspace provides detailed information about the Pillar 2 calculation results. It is possible to export the results as an Excel file or as a pdf.
The workspace contains the following tabs:
- **Allocations** — Displays allocations between constituent entities (CEs), including arm's length adjustments and intragroup financing arrangements.
- **Deferred Taxes Transition** — Displays deferred tax transition details between disposing and acquiring CEs.
## 'Allocations' Tab
The **Allocations** tab displays a table with allocation details between a **source CE** and a **target CE**. In addition to allocations _in sensu stricto_, the table also contains information on adjustments for arm's length adjustments and adjustments for intragroup financing arrangements.
Example of allocations
## 'Deferred Taxes Transition' Tab
The **Deferred Taxes Transition** tab displays a table with deferred tax transition details. The data is grouped by the **Entity's Jurisdiction** by default.
'Deferred Taxes Transition' tab
---
---
title: "Differences"
description: "In the workspace Differences, a user-configurable evaluation of deferred taxes is possible."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/reporting/differences
language: en
last_updated: 2026-05-28
---
# Differences
## Overview
In the **Differences** workspace, users can configure an evaluation of deferred taxes. The report is based on the **B/S Comparison** workspace from the Income Taxes area **Company** and can be transferred to an Excel view. In addition to deferred taxes, the corresponding gross differences are also displayed.
## Navigation
The workspace **Differences** is opened via **Reporting | Differences**.
The **Differences** workspace is displayed as follows, for example:
'Differences' workspace
## Report Configuration
The **Differences** report is based on the selected options. The individual settings are described in the following table. The following options are available:
| Option | Description |
|---------|---------|
| Applies to period | A reporting period must be specified, it defines the period to be analyzed |
| Company | The company must be specified. Depending on the selected parameter **Structure**, the tax group or sub-group is evaluated based on this, for example. |
| Balance type | The balance sheet type defines the level of the balance sheet differences under consideration. E.g. it can be specified whether the level **IFRS - Tax balance** or **Local GAAP - Tax balance** should be included in the analysis. |
| CoA Company | By selecting a CoA Company, the differences under consideration can be (optionally) restricted. |
| Show as from | In this input field, you can set a limit for the **differences** to be displayed. Balance sheet items for which the balance sheet difference falls below the limit are not displayed in the report. If the field is left blank, all differences other than 0.00 are displayed. |
| Reporting Dimension | A reporting dimension can be selected (optionally). The selection list is based on the **Reporting Dimension** workspace of the period chosen above. |
| Country | A country can be selected (optionally). The selection list is based on the **Countries** workspace of the period selected above. |
| Period to compare | The list of periods to compare contains all periods created in Income Taxes. Specifying a comparison period is optional. |
| Structure | Five display options are available. This parameter applies only to companies for which the user is authorized. **Company**: Only the selected company is displayed. **List**:All companies recorded in the master data are displayed. The list is based on the selected period. **Group structure**: Available for companies that are defined as (sub-)group in the master data. If you select this option, you must select the corresponding company. **Tax group structure**: Available for companies that are defined as tax group parent in the master data. If you select this option, you must select the corresponding company. **Tax group structure** **\+ Partnership companies**: See description of tax group structure. |
| Calculation with quota | Specifies whether calculations are to have a quota. |
| Show CoA company sum/Show unit sum | Specifies whether the sum is to be calculated for each CoA company item or per unit. |
| Details | Allows further restrictions in the report. |
## Displaying Report
Click **Show** to start displaying the report based on the selected criteria.
---
---
title: "Displaying an Einheits-GmbH & Co. KG"
description: "An Einheits-GmbH & Co. KG is a special form of GmbH & Co. KG in which the limited partnership (KG) and its general partner GmbH form an economic unit. In this case, the KG is often the sole shareholder of the general partner GmbH. This means that the KG both controls its general partner and conducts the business. How to set up an Einheits-GmbH & Co. KG is described in detail in this chapter."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2/structure-gmbh-co-kg
language: en
last_updated: 2026-05-28
---
# Displaying an Einheits-GmbH & Co. KG
## Overview
An **Einheits-GmbH & Co. KG** is a special form of GmbH & Co. KG in which the limited partnership (KG) and its general partner GmbH form an economic unit. In this case, the KG is often the sole shareholder of the general partner GmbH. This means that the KG both controls its general partner and conducts the business.
Due to the circular investment structure, it is not possible to display the structure of an Einheits-GmbH & Co. KG using master data alone. The general partner share of 0% is maintained at the individual company level by means of the basic data in the **FB attachment**. You can enter the remaining ownership relationships by means of the master data.
How to set up an Einheits-GmbH & Co. KG is described in detail in this chapter.
## Examples of an Einheits-GmbH & Co. KG
The following figure shows an example of an Einheits-GmbH & Co. KG:
Example: Structure of an Einheits-GmbH & Co. KG
## Creating an Einheits-GmbH & Co. KG
To create an Einheits-GmbH & Co. KG:
1. Create the limited partner under **Master Data | Companies** and, if necessary, assign the legal owner.
Creating limited partner under 'Master Data | Companies'
2. Create the GmbH & Co. KG under **Master Data | Companies**. Assign the limited partner as the legal owner. The general partner should not be entered at this point.
Creating Einheits-GmbH & Co. KG in the master data
Assigning limited partner as legal owner
3. Create the general partner GmbH under **Master Data | Companies**. Enter the Einheits-GmbH & Co. KG as the legal owner.
Creating general partner GmbH
Assignment ownership to parent company
4. Enter the general partner under **Company | Basic data | Anlage FB** as follows:
Enter the **Unit-ID** from the master data.
In the row for the complementary company, activate the checkbox for **Komplementär Einheits-GmbH & Co. KG**.
") Recording general partner in the FB attachment (Anlage FB)
5. Enter the **Unit-ID** from the master data.
6. In the row for the complementary company, activate the checkbox for **Komplementär Einheits-GmbH & Co. KG**.
After all entries have been completed, the circular investment structure is displayed in the master data of the GmbH & Co. KG. The general partner share is displayed by means of the basic data in the master data. It is important to maintain the company ID correctly in the master data.
---
---
title: "E-mail Configuration"
description: "In the workspace E-mail configuration, you can configure e-mail servers that are used to send e-mail templates."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-administration/e-mail-configuration
language: en
last_updated: 2026-05-01
---
# E-mail Configuration
## Overview
In the workspace **E-mail configuration**, you can configure e-mail servers that are used to send e-mail templates.
## Heading
The **E-mail configuration** workspace can be found under **Tax Administration | E-mail configuration**.
The **E-mail configuration** workspace is displayed as follows (for example):
'E-mail configuration' workspace
All configured e-mail servers are displayed in the table. The columns of the table contain the following information:
- **ID**: Technical ID of the configuration
- **Intention**: Intention for which the server configuration was created
- **Host**: Host of the e-mail server
- **User name**: User name for authorization and authentication on the e-mail server
- **Port**: Port of the e-mail server
- **Archived**: E-mail server configuration is active or archived
The table displays the e-mail templates that have already been created.
## Options
The following options are available:
| Option | Description |
|---------|---------|
| the edit icon | Opens the configuration in edit mode |
| the details icon | Opens the configuration in read-only mode |
| the recycle bin icon | Archives the configuration |
| the restore icon | Restores an archived configuration, provided that no other active configuration with the same intention exists |
## Creating an E-mail Configuration
To create a new e-mail configuration:
1. Click **Create** to create a new e-mail server configuration.
**Note**: If the **Create** button is not displayed, you have created a configuration for all available **intentions**. In this case, you can archive or edit an active configuration.
2. The configuration options are displayed as follows:
Options for an e-mail configuration
3. Choose the desired **intention** from the drop-down list.
4. Configure the additional fields (see following section).
## Setting Up an E-Mail Configuration
The following options are available for e-mail configurations:
| Option | Description |
|---------|---------|
| Host | Host name of the SMTP server |
| User name | User name for the SMTP server. The user name is used as the sender e-mail address. If the user name is not a valid e-mail address, a sender e-mail address must be specified. |
| Sender's e-mail address | As an alternative to the user name, a sender e-mail address can be specified in this field. If the user name is not a valid e-mail address, specifying the sender e-mail address is mandatory. |
| Password | User's password for the SMTP server |
| Port | Port of the SMTP server |
| Authentication using 'AUTH' command | Authenticate users with the **AUTH command** |
| Connection using SSL | Use SSL for the connection |
| Trust all hosts | If an SSL connection is used, all hosts will be trusted. |
| TLS-protected connection | **STARTTLS** command is used to switch the connection to a TLS-protected connection |
| Send 'RSET' command instead of 'NOOP' command | Use **RSET** command instead of **NOOP** command |
| Success message of 'NOOP' command only with response code 250 | Success message of **NOOP** command will only be recognized with response code 250 |
## Testing Connection
After the e-mail configuration has been successfully saved, you can test the connection to the e-mail server. To do this, click **Test connection**. If the connection is established successfully, a success message is displayed; otherwise, an error message is shown.
## Sending Test E-Mail
To test whether the system can actually send e-mails correctly, you can send a test e-mail. To do so, proceed as follows:
1. In the **Test e-mail address** field, enter an e-mail address that you can access.
2. Click **Send test e-mail**.
3. Then check the appropriate inbox. If an e-mail with the subject **Portal Mail configuration test. Do not reply** and **Testmail from Lucanet Tax Administration** in the body has been received, the test was successful.
4. Otherwise, check the e-mail server configuration and send another test e-mail.
---
---
title: "E-Mail Templates"
description: "The E-mail templatesworkspace allows you to create templates for e-mails for specific intentions. These templates are triggered by events, expanded/enriched with appropriate content, and sent to users of Income Taxes."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-administration/email-templates
language: en
last_updated: 2026-05-01
---
# E-Mail Templates
## Overview
The **E-mail templates** workspace allows you to create templates for e-mails for specific intentions. These templates are triggered by events, expanded/enriched with appropriate content, and sent to users of Income Taxes.
## Navigation
The **E-mail templates** workspace can be found under **Tax Administration | E-mail templates**.
The **E-mail templates** workspace is displayed as follows, for example:
'E-mail templates' workspace
## Options
The table displays the e-mail templates that have already been created. The following options are available:
- Click the recycle bin icon to delete an e-mail template.
- Click the edit icon to edit an e-mail template.
- Click on a row in the table to display a preview of the template on the right side of the workspace. You will find the language-specific templates on the respective tabs – provided they have been defined.
## Creating and Configuring an E-Mail Template
To create a new e-mail template:
1. In the **E-mail template** workspace, click **Create**.
**Note**: If the **Create** button is not displayed, you have already created a template for all available **template intentions**. In this case, you can only edit or delete an existing template. The following area is displayed:
Create E-mail template
2. Select the desired **template intention** from the drop-down list.
3. Enter an appropriate e-mail subject for this **template intention** in the **Subject** field.
4. Format the e-mail in the text editor using the available text formatting tools.
5. If necessary, use the tabs **German** _,_ **English** and **French** to create additional language-specific templates.
---
---
title: "Edit and Finalize Declaration"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/declaration-edit-finalise
language: en
last_updated: 2026-09-28
---
# Editing and Finalizing the Declaration in Lucanet VAT
## Overview of the 'Declaration' Workspace in VAT
The **Declaration** workspace in Lucanet VAT (Value Added Tax) shows the preliminary VAT return of the chosen company. The declaration form contains all relevant fields of the declaration. VAT automatically enters the field values based on the imported ERP reports and the configured tax code mapping. You can also adjust values manually, create offsetting entries, and create corrections.
Depending on the configuration of the company in the master data, there are two basic ways of creating the declaration in VAT:
- **With tax code mapping (ERP import or manual):** VAT enters the values of the declaration based on a configured tax code mapping. You do not enter values directly in the fields, but add them via entries with tax codes. This procedure is described in the sections [Displaying Field Entries](#displaying-field-entries-in-vat) and [Adding an Entry](#adding-an-entry-in-vat).
- **Without tax code mapping:** You enter the declaration values directly in the form fields. For more information, see the section [Declaration Without Tax Code Mapping](#declaration-without-tax-code-mapping-in-vat).
> **Note:** Some fields in the form are sum fields that VAT calculates automatically. You cannot edit these fields directly.
## Navigation to the 'Declaration' Workspace in VAT
The **Declaration** workspace can be found under **VAT | Value Added Tax | Declaration** and is displayed as follows, for example:
'Declaration' workspace
## Structure of the Overview in VAT
The declaration form in VAT shows the preliminary VAT return with the following columns:
| Column | Description |
|---------|---------|
| Kind of transactions | Row number and name of the declaration field according to the official form |
| Basis of assessment EURO | Input field for the base of the respective VAT matter |
| VAT/GST/Turnover tax EURO | Input field for the related tax amount |
Rows without input fields are section headings or sum rows that are calculated automatically.
The small triangle icon in front of a field indicates that at least one tax code is mapped to this field.
If a field was changed in the current correction, it is highlighted in blue. Fields with a value other than **0,00 €** get a thick border when the declaration is opened again.
## Displaying Field Entries in VAT
In the declaration form in VAT, click the **plus icon** next to a field value to expand the individual entries and see which values with which tax codes flowed into the field.
Expanded field view after clicking the plus icon
The expanded view in VAT shows a table with all entries that contribute to the current field value:
| Column | Description |
|---------|---------|
| Identifier | Made up of the tax code, the tax code form, and a sequential number. The number **0** indicates a value from the imported report. |
| CC | Company code to which the entry is assigned. |
| Value | Amount of the base or the tax amount. Negative amounts are displayed with a minus sign. |
| Comment | Explanation of the origin of the entry. Automatic entries get, for example, the comment **Import Report V00**. |
The following actions are available next to each entry in the expanded field view in VAT:
| Icon | Action |
|---------|---------|
| X | Create an offsetting entry (see section below). Only available while the declaration is open. |
| Paper clip | Opens the **Save attachment and comment** dialog. There you can enter a **Comment** (max. 250 characters) and upload a file via **Choose File**. Attachments that have already been saved are displayed in a table with comment, file name, user, and change date. |
| Information icon | Display the compliance stamp: shows who made the entry when and in which correction. |
## Adding an Entry in VAT
Proceed as follows to add a manual entry to a field in VAT:
1. Click the **plus icon** next to the required field to expand it. The **Change** area is displayed below the field.
2. In the **Change** area, choose the tax code from the drop-down list.
3. Enter the amount.
4. In the **Comment** field, enter a meaningful text with at least five characters.
5. Click the **plus icon** to the right of the value field to add the entry.
The new entry is displayed in the table, and VAT updates the field value automatically. You can add as many entries to a field as you like. You cannot delete entries – use an offsetting entry instead.
> **Note:** You can only add an entry if a tax code is mapped to the required field. If a tax code is mapped to several fields, VAT automatically transfers the entry to all linked fields – depending on the country configuration.
## Creating an Offsetting Entry in VAT
An offsetting entry corrects or reverses an existing entry in the declaration in VAT.
Proceed as follows to create an offsetting entry in VAT:
1. Click the **plus icon** next to the field to expand the individual entries.
2. Click the X icon next to the entry that you want to offset. The confirmation dialog is displayed.
3. In the confirmation dialog, check the listed affected fields and offsetting entries.
4. Enter a comment.
5. Click **OK**.
## Managing Corrections in VAT
The **Declaration** workspace in VAT always shows only one correction of the declaration – by default the most recent one when you open it. Use a drop-down list to switch between the different corrections.
To compare two corrections directly with each other, switch to the [Comparison view of corrections](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/comparison-corrections.md) workspace. There you choose two corrections via drop-down lists and can optionally display only the fields with differences.
## Finalizing the Declaration in VAT
Click **Finalise** in the top right corner to close the declaration in VAT.
Depending on the configuration, the button can be grayed out if certain prerequisites are not yet met – for example, if the reconciliations have not yet been performed or if mandatory reconciliations have errors. In this case, VAT displays the reason above the declaration form.
> **Note:** You can reopen a closed declaration in the **Declaration** workspace as long as the parent declaration has not been finalized yet. For standalone companies, reopening is always possible. Alternatively, reopen the declaration via the [Month overview](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/monthly-overview.md).
## Declaration Without Tax Code Mapping in VAT
If a company in VAT is configured without tax code mapping, you enter the declaration values directly in the input fields of the form. In this case, the plus icon next to the fields is not present.
If there is a direct relationship between a base field and a tax field and a clear tax rate applies, VAT calculates the corresponding field automatically. For adjustments, you overwrite the existing values in the fields.
Via the paper clip icon, you can also add a file with a comment to a field in this mode.
## Non-Monthly Declarations in VAT
Not every company submits its declaration monthly. Depending on the country and sales, companies can also report quarterly or annually. For these companies, the following applies in VAT:
- The data is still imported monthly and accumulated in the reporting month.
- As soon as the previous months are closed, VAT automatically transfers their values to the reporting period. Each transferred entry gets the comment **Data transfer from previous period: *name of the period***.
- In the reporting month, VAT takes into account the values transferred from the previous months together with the values of the current month.
> **Note:** For parent companies of company subdivisions, VAT does not transfer any values from the previous months, because the company subdivisions already perform this transfer.
## Further Functions in the 'Declaration' Workspace in VAT
In addition to the [general functions](https://support.lucanet.com/en/documentation/income-taxes/vat/user-interface-general-functions.md), the following functions are available in the context menu of the three-dot icon (⋮) in the top right corner of the **Declaration** workspace in VAT:
| Function | Description |
|---------|---------|
| Import SPP value to declaration | Transfers the deduction amount of the special prepayment (SPP) to the current preliminary VAT return. This function is only available for Germany and is only displayed for standalone companies and representative VAT group members in monthly periods if a corresponding SPP period exists. |
| Info view | Shows technical details for each field, for example the field type, the mapping ID, and the calculation formula |
| Recalculation of sum values | Recalculates all sum values of the open declaration. Useful, for example, after changes to the rounding logic in the settings. |
| Declaration export (Pdf) | Exports the declaration as a PDF file |
| Declaration export (Excel) | Exports the declaration as an Excel file |
| Form language: DE/Form language: EN | Switches the display language of the declaration form, independently of the system language |
---
---
title: "Editing Reconciliations 1 to 14"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/performing-reconciliations/editing-reconciliations-1-to-14
language: en
last_updated: 2026-09-29
---
# Editing Reconciliation Results 1 to 14 in Lucanet VAT
## Overview of Reconciliations 1 to 14 in VAT
This page describes the individual reconciliations that Lucanet VAT (Value Added Tax) performs for a company. For each reconciliation, you learn what is checked, how a difference arises, and how to edit an incorrect item.
For information on how to start the reconciliations and how to read the reconciliation result and the processing status, see [Performing Reconciliations](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/performing-reconciliations.md).
## Reconciliation 1: Plausibility of VAT Amounts in VAT Report V00 in VAT
Reconciliation 1 in VAT checks whether the VAT shown in the RFUMSV00 report matches the amount that results from multiplying the base by the tax rate of the respective tax code. Differences are often caused by rounding differences.
### Editing an Incorrect Item
If a reconciliation item of reconciliation 1 in VAT has an error, proceed as follows:
1. Activate the check box in the **Edit** column for the affected item.
2. Below the table, enter a correction value and a comment with at least five characters.
3. Click **Save** to transfer the change to the declaration.
You can view all changes made in the change log. There you can also upload a file attachment for each change.
> **Note:** In the master data, you can configure a limit for automatic adjustments for the company. VAT automatically corrects differences below this limit and marks them with an exclamation mark as the reconciliation result. In this case, no manual editing is required.
## Reconciliation 2: Comparison of G/L Account with VAT Return in VAT
Reconciliation 2 in VAT compares the VAT payable calculated in the VAT form with the balance of the tax payable account from the imported trial balance (RFBILA).
**Prerequisite:** A separate account for the posted VAT payable or refund must exist in SAP.
Common causes of differences in reconciliation 2 in VAT:
- The account clearing of the tax payable account is not exact to the month.
- Residual amounts remain on the account.
- The account clearing is shifted by a permanent extension of the filing deadline.
### Editing a Difference
To resolve a reconciliation difference in reconciliation 2, adjust the relevant tax payable account via **Change RFBILA**. Observe the sign specified by VAT, and then perform the reconciliations again.
Alternatively, you can make the change directly in the declaration form by adjusting the respective tax code in the corresponding field position, and then perform the reconciliations again.
> **Note:** Enter a meaningful comment in the comment field. You can also upload attachments in the change log of the reconciliation.
## Reconciliation 3: Checking Differences Between VAT Reports V00 and V10 in VAT
Reconciliation 3 in VAT compares the bases from the RFUMSV00 and RFUMSV10 reports per tax code. VAT shows any differences in an overview table.
Possible causes of differences are intended or incorrect settings in the ERP system or a modification of the standard reports. This reconciliation is also the basis for reconciliations 4 to 8.
### Editing an Error
To edit an error in reconciliation 3 in VAT, choose one of the following adjustment options depending on the situation:
- **Change RFUMSV10**: Adjusts the RFUMSV10 to the RFUMSV00 (standard case). This adjustment has no effect on the declaration form.
- **Change RFUMSV00**: Adjusts the RFUMSV00 to the RFUMSV10 (special case). The adjusted value is entered in the declaration in the field to which the affected tax code is mapped.
> **Note:** In the first months, it is recommended to collect the differences per company and to send the incorrect tax codes to the responsible ERP department using the Excel view, so that you can look for the cause together.
## Reconciliations 4–6: Completeness Check of Income, Expense, and Asset and Liability Accounts in VAT
Reconciliations 4, 5, and 6 in VAT check the completeness of the tax postings for different account categories. For each configured account number, VAT compares the account balance from the RFBILA00 with the aggregated tax base from the RFUMSV10. Differences indicate that there are postings without a tax code or that incorrect reversal postings were made.
**Prerequisite:** Both RFBILA00 and RFUMSV10 must be imported. If one of the reports is missing, VAT performs the reconciliation with an error.
Reconciliations 4 to 6 in VAT check the following accounts:
| Reconciliation | Checked accounts |
|---------|---------|
| 4\. Completeness check of revenue accounts | Income accounts |
| 5\. Completeness check of expense accounts | Expense accounts |
| 6\. Completeness check of asset and liability accounts | Asset and liability accounts |
Possible differences in reconciliations 4 to 6 in VAT and their meaning:
| Difference | Indication |
|---------|---------|
| Value RFBILA > value RFUMSV10 | Postings without a tax code exist |
| Value RFUMSV10 > value RFBILA | Possibly incorrect reversal posting |
### Editing an Error
For each incorrect item of reconciliations 4 to 6 in VAT, decide whether the difference is relevant for reporting:
- **Not relevant for reporting**: Activate the check box in the **Not subject to reporting** column. The item is set directly to **Done**.
- **Relevant for reporting**: Choose the tax code that should have been used for the posting. Enter the correction value and a comment, and click **Save**. The adjustment is taken into account in the declaration.
> **Note:** **Note on signs:** During the import, VAT processes the signs differently depending on the tax code form and the account type. Therefore, some differences in these reconciliations may not be actual errors.
## Reconciliations 7–8: Plausibility Check of Tax Codes in VAT
Reconciliations 7 and 8 in VAT check whether postings with certain tax codes were posted to the expected account groups.
| Reconciliation | Check |
|---------|---------|
| 7\. Plausibility check input tax code | Checks that accounts with input tax codes (VST, ESE) were not posted to income accounts. |
| 8\. Plausibility check output tax code | Checks that accounts with output tax codes (MWS, ESA) were not posted to expense accounts. |
Possible causes of reconciliation errors in reconciliations 7 and 8 in VAT:
- An account was classified incorrectly in the master data.
- An amount was posted to the wrong account – usually not relevant for reporting.
- An amount was posted with a wrong tax code.
### Correcting a Wrong Tax Code
If an amount was posted with the wrong tax code, proceed as follows in VAT:
1. Activate the check box in the **Edit** column for the affected item.
2. Below the table, choose the correct tax code.
3. Enter the correction value and a comment.
4. Click **Save**.
VAT automatically creates two adjustments in the declaration: an offsetting entry on the original, wrong tax code and a posting on the correct tax code.
> **Note:** Also correct the corresponding posting in the ERP system. Since this is usually a posting in the subsequent period, VAT creates resubmissions so that the adjustments can be deducted again in the corresponding subsequent period.
## Reconciliation 9: Reconciliation with ESL in VAT
Reconciliation 9 in VAT checks whether the values reported in the European Sales List match the values of the preliminary VAT return.
VAT compares the following matters in reconciliation 9:
| Matter | Source of information in the preliminary VAT return – example Germany | Source of information in the ESL |
|---------|---------|---------|
| Intra-Community supplies | Field 41 + field 77 | All entries with type of service "0" – supplies |
| Intra-Community other services | Field 21 | All entries with type of service "1" – other services |
| Intra-Community triangular transactions | Field 42 | All entries with type of service "2" – triangular transaction |
Differences often arise because the amounts in the European Sales List do not contain cents – decimal places are truncated, not rounded. For extensive European Sales Lists, this can result in high rounding differences.
In the master data, you can configure a tolerance limit – absolute or as a percentage. If the difference is within this limit, VAT displays the item with a yellow exclamation mark.
> **Note:** In the master data, you specify whether VAT performs the reconciliation when creating the preliminary VAT return, when creating the European Sales List, or in both declarations.
## Reconciliation 10: Deviation from the Mean of the Last 12 Months in VAT
Reconciliation 10 in VAT calculates the deviation between the specified field value of the current month and the average value of this field over the last 12 months.
You configure the reconciliation in the master data – including the field to be checked and the tolerance limit, absolute or as a percentage. If both variants are configured, the percentage tolerance limit applies.
For a more detailed analysis, use the report **Deviation between current month and average of 12 previous months**.
> **Note:** This reconciliation only makes sense for a company with relatively constant sales.
## Reconciliations 12–13: Plausibility Check for Reverse Charge and Intra-Community Acquisitions in VAT
> **Note:** These reconciliations only make sense if the company is entitled to full input tax deduction.
Reconciliations 12 and 13 in VAT comprise the following checks:
| Reconciliation | Check |
|---------|---------|
| 12\. Plausibility check for reverse charge | Checks whether the tax value of the reverse-charge transactions matches the input tax value claimed. |
| 13\. Plausibility check intra-community acquisitions / Inputtax | Checks whether the tax value of the intra-Community acquisitions matches the corresponding input tax value. |
Differences can be caused by rounding differences or can indicate that certain tax codes do not entitle to full input tax deduction.
If materiality thresholds have been configured, VAT either treats minor differences as negligible – the so-called de minimis threshold – or automatically adds them to the resubmissions so that they can be checked at a later date.
## Reconciliation 14: Zero Balance Validation of G/L Accounts in VAT
Reconciliation 14 in VAT checks whether the stored G/L accounts have a zero balance, for example for automatic reclassifications at period-end closing.
You configure the G/L accounts for this reconciliation under **Master data | Reconciliations**. There, assign each account to the **Zero balance G/L account** group if it is to be taken into account in reconciliation 14.
If a difference is not an actual error, you can record this in the detail view to close the item.
---
---
title: "Einkünfte (Revenue)"
description: "The tax for partnership companies is calculated in the Revenue workspace.\nThe workspace must always be used for partnership companies and is linked to the workspace Current Taxes Current Taxes in annual financial statement periods."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/income
language: en
last_updated: 2026-05-28
---
# Einkünfte (Revenue)
## Overview
The tax for partnership companies is calculated in the **Einkünfte (Revenue)** workspace. The workspace must always be used for partnership companies and is linked to the workspace **Current Taxes** | **[Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/current-taxes-2.md)** in annual financial statement periods.
In **tax return periods**, the **Revenue** workspace is linked to the workspaces **Current Taxes | [Transfer zum Anteilseigner](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/transfer-to-shareholder.md) (Transfer to Shareholder)** and **Current Taxes [Feststellung](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/feststellung.md) (Determination)**. Data entered in the **Revenue** workspace are automatically transferred to the linked workspaces.
## Navigation
The **Einkünfte (Revenue)** workspace can be found under **Company | Current Taxes | Einkünfte**.
The **Revenue** workspace is displayed, for example, as follows:
' workspace")'Einkünfte (Revenue)' workspace
> **Note:** The **Revenue** workspace is available only to **partnership companies**.
The tax bases in the **Revenue** workspace are split into columns, depending on the number of partners set up.
## Technical Information
The surplus/deficit result from deviations between the local balance sheet and the tax balance sheet (aggregate local balance sheet) is determined directly from the balance sheet comparison (workspace **Deferred Taxes | [B/S Comparison](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/deferred-taxes/balance-sheet-comparison.md)**). In addition, the surplus/deficit result from any supplementary balance sheets is displayed.
The calculated values are displayed as proposed values in the **Revenue** workspace. Corrections from true-up effects are determined only for the aggregate balance sheet.
---
---
title: "Electronic Transmission"
description: "In addition to its reporting functions, Income Taxes can also be used to submit the electronic tax return."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer
language: en
last_updated: 2026-05-28
---
# Electronic Transmission
## Overview
In addition to its reporting functions, Income Taxes can also be used to submit the electronic tax return.
The e-balance sheet, which is submitted as an attachment to the tax return, is sent to the tax authorities from the **Tax Balance** module.
The **Electronic Transmission** workspace contains the following workspaces for the submission of the electronic tax return:
- [Validation](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/validation-electronic-transmission.md)
- [Data Transmission](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/data-transfer.md)
- [Fast Entry](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/fast-entry.md)
## Tax Return Preparation Process (Example)
An example of the process used to prepare the (income) tax return is illustrated in the following figure:
tax return") Example process for creating the (income tax) tax return
Transaction data and, if necessary, master data are imported from the ERP system into Income Taxes. In the **Current Taxes** workspace, you can supplement the imported data with all the information required for the annual tax return. In addition, data for the capital gains tax return can be entered in the **KapEStA** workspace. Once all tax-relevant information has been entered, the tax return (or pre-payment) is electronically submitted to the tax authority via the **Tax Transfer Hub (TTH)** in the Elektronische Übermittlung (Electronic transmission) workspace.
> **Note:** - The **Tax Transfer Hub (TTH)** is a technical component implemented in Income Taxes, which is not visible to the user.
> - Within Income Taxes, it must be observed that a **tax return period** must be created for tax return purposes. This activity is described in the following section.
> - Furthermore, a valid **ELSTER certificate** must be stored in the master data for the user.
## Distinguishing Between Annual Financial Statement Periods and Tax Return Periods
In the annual financial statements, the tax calculation needs to be entered in Income Taxes above all for the purpose of the provisions calculation and the **Tax Rate Reconciliation (TRR)**. The form dialogs do not have to be used for this purpose – A reduced tax calculation is available: the **Current Taxes** workspace (form set 2017).
The values are synchronized automatically between forms and the **Current Taxes** workspace. For example, non-deductible expenses entered in the reduced tax calculation are automatically transferred to **Anlage GK**.
A special feature of **annual financial statement periods** is the processing of issues in accordance with section 8b of the Corporate Income Tax Act. They are exempted already at the level of the entering tax group member, not at the level of the tax group parent (known as the **net method**). This also allows a "stand-alone TRR" to be created for each tax group member. However, what is referred to as the **gross method** applies to tax return periods. The tax exemption for section 8b corporate tax issues applies only at the level of the tax group parent, section 15 (1.2) (the same applies to partnership companies: here too the exemption only applies to the last shareholder in the ownership chain).
The gross method is implemented by the tax authority on the tax forms. The distinction between the gross method and net method is reflected in the [Periods](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/periods.md) master data workspace:
Options for creating a period in master data
- When a period is created for **tax return purposes**, it is automatically created as a gross period and the **Rounding** option is activated.
- When the period is created as an **annual financial statement period**, the **Calculation logic** parameter can be chosen freely from the drop-down list as follows:
- **Net**: The tax exemption for section 8b Corporate Income Tax Act (KStG) issues applies at the level of the tax group member (**net method**).
- **Gross**: The **Rounding** check box can be activated.\
\
The tax exemption for section 8b Corporate Income Tax Act (KStG) issues applies only at the level of the tax group parent (**gross method**).
## Creating a Tax Return Period in Income Taxes
To submit the tax return electronically, a separate period must be created in Income Taxes. As a general rule, the tax return is filed during the year (usually a few months after the annual financial statements). Data that have already been entered in the annual financial statements can be reused when creating the periods and only need to be updated (referred to as [true-up](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/true-up.md)). The process can be illustrated as follows:
Process from annual financial statements to submission
Transaction data are copied when the tax return period is created, regardless of whether the detailed tax dialogs (forms) or the reduced tax calculation ([Current Taxes](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes.md) workspace) are used in the annual financial statements.
The milestone status is not applied. It would otherwise be necessary to reset the milestones for companies with a closed status ( **finished** or **checked** milestone status).
The period is then created and completed in Income Taxes.
In the case of multiple periods, the individual parameters used to create the periods are configured as follows:
") Configuration of the parameters for periods (AFCP = Annual Financial statements Period, TRP = Tax Return Period)
---
---
title: "Entity Data Collection"
description: "The Entity Data Collection folder stores information on individual constituent entities (CEs). This information then forms the basis for the Country-by-Country report."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr
language: en
last_updated: 2026-07-28
---
# Entity Data Collection
## Overview
The **Entity Data Collection** folder stores information on individual constituent entities (CEs). This information then forms the basis for the Country-by-Country report.
## Navigation
The **Entity Data Collection** folder can be found at **Country-by-Country-Reporting | Entity Data Collection.** The folder and its corresponding workspaces are displayed as follows, for example:
'Home' workspace in 'Entity Data Collection' folder
## Workspaces in the 'Entity Data Collection' folder
The **Entity Data Collection** folder contains the following workspaces:
| Workspace | Description |
|---------|---------|
| [Home](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/cbcr-home.md) | Shows the milestone status of each CE in the period and is the entry point for the data collection workflow. |
| [Financial Data](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/financial-data.md) | Holds the financial values that each CE reports for CbCR — for example revenues, profit or loss before tax, income tax paid, income tax accrued, stated capital, accumulated earnings, number of employees, and tangible assets. |
| [Business Activities](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/business-activities-cbcr.md) | Records the nature of each CE's main business activities. |
| [CE Information](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/entity-data-collection-cbcr/ce-information-cbcr.md) | Contains identification and master data of each CE, such as tax identification number, incorporation jurisdiction, and address. |
> **Note:** Entries in the **Entity Data Collection workspaces** are in the local currency of each CE. The conversion to the CbCR reporting currency takes place when you run the calculation.
---
---
title: "Entity Data Collection"
description: "The Entity Data Collection folder stores information on individual constituent entities (CEs). This information then forms the basis for the Pillar 2 calculations. This article explains which data is stored in the entity data collection and how to enter that data."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection
language: en
last_updated: 2026-05-01
---
# Entity Data Collection
## Overview
The **Entity Data Collection** folder stores information on individual constituent entities (CEs). This information then forms the basis for the Pillar 2 [calculations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/calculation.md). This article explains which data is stored in the entity data collection and how to enter that data.
## Navigation and Layout
The **Entity Data Collection** folder can be found at **Pillar 2 | Entity Data Collection** and contains the following workspaces:
- [Home](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/pillar-two-home.md)
- [OECD-Standard](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/oecd-standard.md)
- **Individual Calculations** (This workspace shows individual calculations added by users or their implementation partners. By default, the workspace is without function and will not be described in detail.)
- [Tax Allocations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/tax-allocations.md)
- [FTE & PE Allocations](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/fte-pe-allocations.md)
- [Cross-border Adjustments](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/pillar-two/entity-data-collection/cross-border-adjustments.md)
'Tax Allocations' workspace
There are three types of data stored in the Pillar 2 module:
- **Checkboxes**
- **Numerical data**
- **Alphanumerical information**
All three types use **blue borders** to highlight values that have been imported from another Lucanet Software GmbH module, **green borders** for imports from external sources, and **no border** for manual entries.
---
---
title: "European Sales List"
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list
language: en
last_updated: 2026-10-05
---
# European Sales List in Lucanet VAT
## Overview of the 'European Sales List' Functional Area in VAT
The **European Sales List** (ESL) in Lucanet VAT (Value Added Tax) is used to monitor intra-Community supplies and services within the European single market. VAT transmits the European Sales List to the **Federal Central Tax Office** (BZSt). The European Sales List covers the following types of transactions:
- **Intra-Community supplies** (type of transaction: 0)
- **Services** in accordance with sec. 18b sent. 1 no. 2 of the German VAT Act (type of transaction: 1)
- **Intra-Community triangulations** in accordance with sec. 25b para. 2 of the German VAT Act (type of transaction: 2)
In the **European Sales List** functional area in VAT, you import, check, create, and send the ESL. The workspaces are arranged in the order in which you typically work through the steps of the reporting process.
For an overview of all steps of the reporting process, see the [All Steps at a Glance](https://support.lucanet.com/en/documentation/income-taxes/vat/all-steps-at-a-glance.md) page. The [User Interface and General Functions in VAT](https://support.lucanet.com/en/documentation/income-taxes/vat/user-interface-general-functions.md) page describes the functions that are available in all workspaces.
## Prerequisites for the European Sales List in VAT
The **European Sales List** functional area in VAT is only displayed if the following prerequisites are fulfilled:
- The **Submits ESL** check box is activated in the master data of the selected company.
- The selected period is a **preliminary VAT return period**. You cannot create a European Sales List in annual VAT return or special prepayment periods.
## Navigation to the 'European Sales List' Functional Area in VAT
The **European Sales List** functional area can be found under **VAT | European Sales List** and is displayed as follows, for example:
The 'Status' workspace in the 'European Sales List' functional area
## Reporting Periods of the European Sales List in VAT
As a rule, the European Sales List must be submitted **monthly** by the 25th day of the following month. Depending on the amount of the transactions and the types of services, different deadlines apply. The following table describes the reporting periods of the European Sales List:
| Reporting period | Prerequisite | Deadline |
|---------|---------|---------|
| Monthly | Standard case for intra-Community supplies and triangulations | By the 25th day of the following month |
| Quarterly | The total tax bases for intra-Community supplies and triangulations did not exceed EUR 50,000 in any of the four preceding quarters and do not exceed this threshold in the current quarter. | By the 25th day after the end of the quarter |
| Yearly | No obligation to submit preliminary VAT returns, that is, a previous year's turnover below EUR 1,000, and additional thresholds, including supplies and services below EUR 200,000 and intra-Community supplies below EUR 15,000 | By January 25 of the following year |
If the transactions exceed the threshold of EUR 50,000 within a quarter, the European Sales List must again be submitted monthly from that point on – for all months of the current quarter.
If a company does not carry out any reportable transactions in a month or quarter, no European Sales List needs to be submitted. A nil declaration is not required.
You configure the reporting frequency in the master data of VAT under **Companies**.
## Workspaces in the 'European Sales List' Functional Area in VAT
The **European Sales List** functional area in VAT contains the following workspaces:
| Workspace | Description |
|---------|---------|
| [Status](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/esl-status.md) | Provides a tabular overview of the current processing status of the reporting process for the selected company. Displays all steps with their respective status and log. |
| [Import](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/import-data-summary.md) | Enables you to import the ESL data, e.g. the ERP report RFASLM00. VAT imports the data automatically from a network drive, or you import the data manually. |
| [Reconciliations](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/reconciliation-report.md) | Enables you to reconcile the European Sales List with the preliminary VAT return, that is, reconciliation 9. |
| [Declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/create-declaration-report.md) | Displays the European Sales List with its entries: VAT ID, country code, amount, and type of transaction. You can transfer entries via the import or add them manually, and finalize the declaration. |
| [Month overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/monthly-overview-report.md) | Displays the reporting progress of all companies in a period. Enables mass actions such as finalizing or reopening several declarations. |
| [Year overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/yearly-overview-report.md) | Displays the reporting progress of all companies over an entire calendar year. This is also where you create corrections to sent declarations. |
| [Send declaration](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/send-declaration-report.md) | Transmits the European Sales List electronically to the Federal Central Tax Office – via the ELMA5 procedure or the ELSTER procedure, depending on the volume. Available for standalone companies and representative VAT group members. |
## Company Members in the European Sales List in VAT
Via company members, VAT merges the data of several company codes into the European Sales List of the superordinate company. As soon as all associated company members have finalized their declaration, VAT transfers the ESL data of the company members into the declaration of the superordinate company automatically.
You do not create corrections in an individual company member, but via the [Year overview](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/yearly-overview-report.md) in the overall declaration.
## Relationship Between the European Sales List and the Preliminary VAT Return in VAT
The transactions reported in the European Sales List must also be declared in the **preliminary VAT return** – in fields 41, 21, and 42 in accordance with sec. 18b of the German VAT Act. In VAT, you reconcile the two declarations via the configurable **reconciliation 9** in the [Reconciliations](https://support.lucanet.com/en/documentation/income-taxes/vat/european-sales-list/reconciliation-report.md) workspace.
---
---
title: "Exporting Data"
description: "Using the export function, you can export a CSV file with the balance sheet and account data of the tax balance sheet. This file can then be imported into the Income Taxes module."
source_url: https://support.lucanet.com/en/documentation/income-taxes/tax-balance/export-data
language: en
last_updated: 2026-05-28
---
# Exporting Data
## Overview
You can use the **export function** to export a CSV file with the following data:
- Balance sheet and account data from the tax balance sheet
- Four calculated special items for tax groups:
- Surplus transfers prior to the tax group (key: tax-balance-special-position-pre-tax-group-remittance-surplus)
- Deficit transfers prior to the tax group (key: tax-balance-special-position-pre-tax-group-remittance-shortfall)
- Surplus transfers within the tax group (key: tax-balance-special-position-tax-group-remittance-surplus)
- Deficit transfers within the tax group (key: tax-balance-special-position-tax-group-remittance-shortfall)
This file can then be imported into the **Income Taxes** module.
> **Tip:** You can also initiate the **import of Tax Balance data** directly in the **Income Taxes** module of the **Tax Compliance & Reporting** solution. For detailed instructions, see [Import Suite](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/import-suite.md).
## Navigation
The **Export** workspace is displayed in the tree view as soon as you open a tax balance sheet under **Company**:
'Export' workspace
## Exporting Data
To Create a CSV Export:
1. Navigate to the **Export** | **Income Taxes** workspace.
2. Choose how the exported values are to be broken down. The following options are available for selection:
- By **balance sheet item**
- By **target item no.**
3. Choose the **adjustment levels** you want to export from the drop-down list or remove the adjustment levels that are not to be transferred by clicking the **x**.
4. Click **Export** to generate the export file.
## Downloading Generated Files
After you have created the export, you can download the generated file.
To do this, click the bell icon to open the **job monitor**. The status of the export task is then displayed below the task:
Job monitor
The export file is downloaded and saved in your download directory by clicking the corresponding task.
---
---
title: "Exporting Periods"
description: "The period export function provides the option to export either all or part of a period’s data."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/periods/export-periods
language: en
last_updated: 2026-05-28
---
# Exporting Periods
## Overview
The period export function provides the option to export either all or part of a period’s data.
## Prerequisites
To be able to initiate a period export, you need the authorization **Master Data: Period export – Execute**. You will then find the corresponding workspace under **Master Data | Periods | Period Export**.
## Exporting Periods
Periods can be exported in the **Period Export** workspace. Proceed as follows:
1. Click **Start export**.
2. Configure the **Export parameters** area (see the following table).
3. Click **Start export**.
Configuring export of a period
The following options are available:
#### Source period
Periods to be exported
#### Type of data
- **Master data only**: data from the **Master data** functional area
- **Master data and transaction data**:\
\
data from the functional areas **Master data** and **Company**
> **Warning:** Please note:
>
> At present, the functional area **(Sub-)Group** cannot be exported completely. There is currently only the option to export information on consolidations.
>
> The **B/S comparison** is part of the master data. It is exported along with the values it contains. Whether these are taken into account or not is further specified in the corresponding period import.
#### Apply position mapping
Activated whenever an export mapping for (balance sheet) positions is stored. This mapping is applied during the period export.
> **Note:** **Export mapping**
>
> The export mapping for (balance sheet) positions is stored in the **Position mapping** workspace. Ensure that the balance type **IFRS / Local GAAP** and the mapping type **IFRS => External** are stored in the workspace.
#### Company selection
Selection of the companies to be be exported:
- **All units**
- **Selected companies**:Displays another selection field, **Single companies**, which supports multiple selection.
- **By reporting dimension**: Displays another selection field, **Reporting dimensions**, which supports multiple selection.
- **By tax group**: Displays another selection field, **Tax groups**, which supports multiple selection.
#### Shareholding structure
Activate if allocation information regarding the unit superiors, type of tax payer, and tax payer of the group should be exported.
#### Consolidation data
Activate if information regarding consolidations from the functional area **(Sub-)Group** should be exported.
> **Note:** This parameter is only displayed if you have selected the **Company selection** option **All units**.
#### Active records only
Activate if only **active** data sets should be exported. Otherwise, **active and archived** data sets will be exported.
> **Note:** **Notes**:
>
> - This parameter is only displayed if you have selected the **Company selection** option **All units**.
> - In this context, **data sets** include all master data that distinguishes between the statuses **Active** and **Archived**. The following data sets can currently be archived: countries, companies, reporting dimensions, CoA Company.
#### Encrypt export
Activate if the export package should be encrypted. In the **Password** input field displayed, enter a password to secure the export file. The password must comply with the configured password policy.
> **Note:** **Notes**
>
> - Under certain circumstances, an export may take a longer time. Log information is written to the PERIODENTRANSFER log file throughout the process. However, an additional log file that is readable for the user is also generated.
> - Once the export is finished, the result is displayed in a short summary.
> - You can continue working in other periods in Income Taxes or log out during an export. The export will continue in the background. You can log in again at a later point in time and, depending on the export progress, the current status bar or the results page will be displayed.
## Additional Actions
After an export, you have the following options:
- You can download the exported data as a "\*.gpt" file and the detailed log information as a "\*.txt" file
- You can open the log file (e.g. in Excel)
- You can perform a new export by clicking the **Restart export** button. The current status of the executed export will be deleted.
## Locking Mechanisms
To ensure that the data in export files reflects a consistent state, an export can only be initiated if the following conditions are met at that time:
- **No user is accessing the data of the source period**: As soon as a user opens a workspace, a lock entry is created in the system. When a period export is initiated, the system checks whether a lock entry exists for this period.
- **No additional period export or import is being executed in parallel**: To ensure the second condition is met, a lock is placed on the period currently in use during the period transfer. In the case of a period export, this is the source period. On the one hand, this lock entry prevents any further period export or import from being carried out. On the other, users are not able to make any changes during a period that is locked due to the transfer.
After the period transfer is completed, the lock entry for the period is automatically **reset**, regardless of whether the export was successful or an error occurred.
---
---
title: "External"
description: "The External workspace loads CbCR data from outside the platform — either from a file you upload (CSV, TXT, XLS, or XLSX) or from a server-side path or third-party connection that an administrator has configured as an interface."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/cbc-reporting/cockpit-cbcr/import/external
language: en
last_updated: 2026-07-28
---
# External
## Overview
The **External** workspace loads CbCR data from outside the platform — either from a file you upload (CSV, TXT, XLS, or XLSX) or from a server-side path or third-party connection that an administrator has configured as an interface.
## Navigation
The **External** workspace can be found at **Country-by-Country-Reporting | Cockpit | Import | External**. The workspace is displayed as follows, for example:
'External' workspace in 'Import' folder
## Importing External Data
To import data from an external source:
1. Navigate to **Country-by-Country-Reporting | Cockpit | Import | External**.
2. In the **Applies to period** drop-down list, select the target CbCR period.
3. In the **Company** drop-down list, select the CE.
> **Note:** To execute the import for all CEs at once instead, activate the **Run import for all Constituent Entities** check box in the table below. If you do not see the check box, your role does not allow bulk imports — ask your system administrator to enable it.
4. In the **Interface** drop-down list in the table below, choose the interface that matches your file format and source system. If no interfaces appear, you need to set up and configure a new interface first. For instructions, see [Interfaces](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/master-data-income-taxes/interfaces.md).
5. Depending on the interface type:
- For a file-upload interface, click **Choose File** next to **File path** and select an import file (CSV, TXT, XLS, or XLSX).
- For a server-side or SAP RFC interface, the configuration sets the file path or connection, so no further input is needed.
6. Click **Import**. The system parses the data and shows the result and any error or warning messages on screen.
7. Review the result. Then do one of the following:
- Click **Save** to commit the data. A progress bar tracks the save, which can take a while for large files.
- Click **Cancel** to discard the parsed data.
---
---
title: "Fast Entry"
description: "Additional values for the purpose of the tax return can be entered in the Fast entry workspace, based on what are referred to as ERiC IDs. This ensures that all rows of the forms can be submitted – including those that may not yet be available in Income Taxes."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/eric-transfer/fast-entry
language: en
last_updated: 2026-05-28
---
# Fast Entry
## Overview
Additional values for the purpose of the tax return can be entered in the **Fast entry** workspace, based on what are referred to as ERiC IDs. This ensures that all rows of the forms can be submitted – including those that may not yet be available in Income Taxes.
## Navigation
The **Fast entry** workspace is opened under **Company | Electronic Transmission | Fast entry**. The **Fast entry** workspace is displayed, for example, as follows:
'Fast entry' workspace
## Options
The following options are available:
#### Create
Opens the following workspace, where you can configure the fast entry:
---
---
title: "Feststellung (Determination)"
description: "The declaration for the separate and uniform determination of income of a partnership is performed in the functional area Feststellung (Determination)."
source_url: https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/feststellung
language: en
last_updated: 2026-05-28
---
# Feststellung (Determination)
## Overview
In the **Feststellung (Determination)** functional area, you can enter all the data required for the **declaration for the separate and uniform determination of tax bases**.
The individual Anlagen forms under **Feststellung (Determination)** correspond to the official forms of the tax authority and must be completed for the purpose of the electronic tax return.
Only the [Revenue](https://support.lucanet.com/en/documentation/income-taxes/income-taxes/company/current-taxes/income.md) workspace is used in the annual financial statements or reporting.
> **Note:** The following income types are supported: **commercial enterprise**, **rental** and **leasing**, **investment income**, and **other types of income**.
>
> The following types are not supported:
>
> - Self-employment
> - Agriculture and forestry
## Navigation
The **Feststellung** (Determination) functional area is opened under **Company | Current Taxes | Feststellung**. The functional area contains – depending on the configuration – various forms:
'Feststellung' (Determination) workspace with 'Anlage FE 1 – VuV'
> **Tip:** The forms displayed in the **Feststellung (Determination)** functional area can be specified via **Company | Basic data | Form configuration** on the **Feststellung** tab:
>
> the configuring forms displayed in 'feststellung' (determination) functional area icon
> Configuring the forms displayed in the 'Feststellung' (Determination) functional area
The following forms can be activated for the **Feststellung (Determination)** functional area:
## Forms in Assessment Period 2024
| Form | Description |
|---|---|
| Anlage FE 1 | Must be completed for co-partnerships (e.g. partnership companies). The total income is determined first and then distributed among the parties involved. Available for: commercial enterprise (FE 1 -G); rental and leasing (FE 1 – VuV). |
| Anlage FE 2 | Covers capital gains, other income subject to preferential tax rates, and other types of income; this income is then distributed among the parties involved. Available for: commercial enterprise (FE 2 -G); rental and leasing (FE 2 – VuV); other types of income (FE 2 – SO). |
| Anlage FE 3 | Covers special expenses and information on de minimis aid and special depreciation for new residential rental construction pursuant to section 7b of the Income Tax Act (EStG), laboratory associations and cost/auxiliary associations, as well as information on section 3a of the Income Tax Act; the amounts are then distributed among the parties involved. |
| Anlage FE 4 | Information on the tax relief for retained profits (section 34a of the Income Tax Act (EStG)) and on determining the non-deductible loan interest pursuant to section 4 (4a) of the Income Tax Act; the amounts are then distributed among the parties involved. Available for: commercial enterprise. |
| Anlage FE 5 | Information on non-deductible loan interest (section 4 (4a) of the Income Tax Act (EStG)), losses with limited liability (section 15a of EStG), losses in connection with tax deferral models (section 15b of EStG), and tax relief for retained profits (section 34a of EStG); the amounts are then distributed among the parties involved. Available for: commercial enterprise (FE 5 -G); rental and leasing (FE 5 – VuV). |
| Anlage FE VM | Covers the tax bases for each party involved in connection with losses with limited liability (section 15a of EStG) and losses in connection with tax deferral models (section 15b of EStG). Available for: commercial enterprise (FE VM -G); rental and leasing (FE VM – VuV). |
| Anlage FE-K | Must be completed if the partnership or community generates income for which the tax exemption or taxation depends on the legal form and corporations are involved. Covers the tax bases both for the partnership and proportionally for the corporations involved. The form is divided into two parts: the tax bases of the company and the shares of the corporations involved. |
| Anlage FE-K-Bet | To be completed by partnerships whose shareholders include corporate income tax entities if the partnership received distributions in the assessment period that may result in tax-free income from shares in corporations. Covers profit distributions to determine their tax liability specifically and supplements the entries made in Anlage FE-K; to be completed separately for each investment and distribution. |
| Anlage FE-AUS 1 and Anlage FE-AUS 2 | Required for tax bases with a foreign reference. FE-AUS 1 covers the foreign taxes attributed to parties involved (an entry is made only if the standard income tax rate applies; with investment income, only if not already settled by the tax deduction); FE-AUS 2 determines tax-exempt but progression-relevant foreign income and add-back amounts. Available for: commercial enterprise (FE AUS - G); rental and leasing (FE AUS – VuV); other types of income (FE AUS – SO). |
| Anlage FE-KAP | Covers the income from investment assets jointly generated by the co-partnership (e.g. partnership) and the corresponding recoverable taxes such as capital gains tax and foreign taxes. Distinguishes between gains with and without domestic tax deduction and those subject to the standard income tax rate; also covers gains taxed at a reduced rate, various tax reduction amounts, limited-creditable capital gains taxes, and family foundations; the amounts are then distributed among the parties involved. |
| Anlage FE-KAP-INV | Determination of the tax bases for investment income not subject to domestic tax deduction; to be completed separately for each investment fund. |
| Anlage FE-OT | Must be completed by partnerships that are the tax group parent of a tax group member. Covers the tax bases of the tax group member attributed to the partnership; these are then allocated to the shareholders by the separate income determination. |
| Anlage Zinsschranke | Limits how much interest expense a company may deduct for tax purposes. Covers the data required to determine the interest and EBITDA carried forward; the deductible interest expenses, interest carried forward, and EBITDA carried forward are determined in accordance with section 8a of the Corporate Tax Act (KStG) and section 4h of the Income Tax Act (EStG). For tax groups, only the tax group parent completes the form (for the tax group member, pre-tax group interest carried forward may need to be considered). For companies with interest expenses below € 3 million, the form is normally not required unless an interest carried forward exists. |
| Anlage Corona-Hilfen | Covers whether the co-partnership (e.g. partnership) received COVID-19 emergency aid, bridging grants, and comparable grants. |
## Forms in Assessment Period 2025
For the 2025 assessment period, the structure of the Anlagen forms for the **declaration for the separate and uniform determination of tax bases** was fundamentally reorganized. The previous collective forms FE 1 to FE 6, as well as FE-AUS, FE-AUS 2, and FE-VM, were dissolved and replaced by individual forms specific to each income type. Income from commercial enterprise, rental and leasing, and other types of income is now entered in its own form (FE-G, FE-V, FE-SO). You can find the corresponding foreign information in the respective **-AUS** forms.
Anlage Corona-Hilfen has been discontinued and no longer applies for the 2025 assessment period. Information pursuant to sections 15a and 15b of the Income Tax Act (EStG), which previously had to be declared in Anlage FE-VM, is now integrated directly into the respective income-type-specific forms.
| Form | Description |
|---|---|
| ESt 1 B | Main form for the declaration for the separate and uniform determination of the bases for income taxation. Contains general information about the company/community, type of distribution, termination of the company, special investment units, deviating financial year, and information about supporting documents. Mandatory form. |
| Anlage FB | Information about the parties involved in the determination. Mandatory form. For each party involved, a separate entry with the tax identification or business identification number, responsible tax office, and participation ratio must be added. |
| Anlage FE-G | Information about the income from commercial enterprise to be determined. The following are entered: Current income; capital gain on the sale/discontinuation of the entire business, a part of the business, or a co-entrepreneur share; income subject to preferential tax rates/further information; information on the tax relief for retained profits pursuant to section 34a of the Income Tax Act (EStG); subsequent taxation/transfer of the amount subject to subsequent taxation pursuant to section 34a of EStG. |
| Anlage FE-V | Information about the income from rental and leasing to be determined. |
| Anlage FE-SO | Information about the other types of income to be determined: Recurring income; benefits within the meaning of section 22 (3) of the Income Tax Act (EStG) (crypto assets, other benefits); private sale transactions (real property, rights, crypto assets, other assets) incl. individual information on real property and rights equivalent to real property (rows 16-24); death benefit payments; income from recurring income subject to preferential tax rates. |
| Anlage FE-Sonstiges | Distribution of special expenses, information on de minimis aid, special depreciation for new residential rental construction pursuant to section 7b of the Income Tax Act (EStG), laboratory associations, cost/auxiliary associations, information on section 3a of EStG, construction withholding tax, and family foundations pursuant to section 15 of the Foreign Tax Act (AStG). Also contains the Creditable taxes section and the limitation of the creditability of capital gains tax pursuant to section 36a of EStG/section 31 (3) of the Investment Tax Act (InvStG). |
| Anlage FE-KAP | Distribution of investment assets/crediting of taxes. Covers investment income with/without domestic tax deduction, income subject to the standard income tax rate, reduced taxation pursuant to section 34 (1) of the Income Tax Act (EStG), creditable taxes, family foundations pursuant to section 15 of the Foreign Tax Act (AStG), and income that is tax-exempt under a double taxation agreement (DTA)/progression proviso. |
| Anlage FE-KAP-INV | Determination of the tax bases for investment income not subject to domestic tax deduction. |
| Anlage FE-K | Distribution of tax bases when corporations are involved. Required if corporations are directly or indirectly involved in a partnership. |
| Anlage FE-K Bet | Additional information when corporations are involved: Distribution of current income pursuant to section 20 (1) nos. 1, 2, 9, and 10 letter a of the Income Tax Act (EStG). |
| Anlage FE-G-AUS | Distribution of foreign income and taxes for income from commercial enterprise: Foreign income taxed in the source state/notional foreign taxes under a double taxation agreement (DTA); permanent establishment income that is tax-exempt under a DTA; add-back taxation pursuant to sections 7–13 of the Foreign Tax Act (AStG); income that is tax-exempt under a DTA/progression proviso. |
| Anlage FE-V-AUS | Distribution of foreign income and taxes for income from rental and leasing. Subdivided into the total tax bases of the company/community and the distribution among the parties involved in the determination. |
| Anlage FE-SO-AUS | Distribution of foreign income and taxes for other types of income. Subdivided into the tax bases of the company/community and those of the parties involved. |
| Anlage FE-OT | Additional information for partnerships (co-partnerships) to which the tax bases of tax group members are attributed. |
| Anlage FE-Zinsschranke | Deduction of business expenses for interest expenses (section 4h of the Income Tax Act (EStG)). Only to be completed if net interest expenses are ≥ € 3 million, an interest carried forward has been determined, and/or to determine an EBITDA carried forward. |
---
---
title: "File Import via SFTP"
description: "With the file import via SFTP, you upload report files to the storage area of your Lucanet environment, from which VAT imports the files. The guide describes the SFTP access, file rules, automation, and troubleshooting."
source_url: https://support.lucanet.com/en/documentation/income-taxes/vat/platform-interfaces/file-import-sftp
language: en
last_updated: 2026-10-06
---
# File Import via SFTP for Lucanet VAT
## Overview of the File Import via SFTP in VAT
With the file import via SFTP, you upload the report files of your ERP system to a dedicated storage area of your Lucanet environment, from which Lucanet VAT (Value Added Tax) imports the files. On the Lucanet CFO Solution Platform, the file import via SFTP replaces the classic network drive because the platform does not provide UNC or SMB shares.
You upload the files to the `Share/` folder. During the import, VAT reads the `Share/` folder, checks every file name against the configured filename pattern, imports the matching files, and then moves them to the `Archive/` folder. The upload alone does not trigger an import: A file remains in `Share/` until you start an import in VAT.
The following guide is intended for customer IT teams who administer the uploading machine. The guide describes the setup of the SFTP access, the rules for the files, the automation of the upload, and troubleshooting.
> **Note:** If your customer system can send HTTP requests, you can alternatively transmit the data without an export file via the [REST import API](https://support.lucanet.com/en/documentation/income-taxes/vat/platform-interfaces/rest-import-api.md).
The following diagram shows the infrastructure and the path of a file from the customer network to VAT:
Infrastructure and data flow of the file import via SFTP in VAT
A file reaches VAT via SFTP as follows:
1. You upload the file via SFTP to the `Share/` folder.
2. The SFTP endpoint stores the file in the encrypted storage area of your Lucanet environment.
3. The import in VAT reads the `Share/` folder and checks every file name against the filename pattern.
4. VAT moves processed files to the `Archive/` folder. As a result, the files disappear from `Share/`.
5. VAT stores the data in the Pre-Import. From there, the data goes into regular processing.
The platform never opens a connection into your network. You upload the files, and VAT collects them.
## Characteristics of the File Import via SFTP in VAT
The following table summarizes the characteristics of the file import via SFTP in VAT:
| Characteristic | Description |
|---|---|
| **Transport** | You upload the files via SFTP to the storage area of your Lucanet environment. |
| **Direction** | VAT reads the files from the storage area. |
| **Authentication** | The sign-in to the SFTP endpoint uses an SSH key pair of the ed25519 type. |
| **Trigger** | The import in VAT triggers the processing, not the upload. |
| **Metadata** | VAT recognizes the company, report, and period from the file name. |
| **Interface type in VAT** | VAT uses the **Network drive** interface type. |
| **Typical use** | The file import suits existing file export routes and companies that previously imported via a network drive. |
The file import via SFTP applies to the import of the VAT reports. The file import via SFTP is not available for VAT Audit.
## Prerequisites for the File Import via SFTP in VAT
Make sure that the following prerequisites are met in your company before you transfer files to VAT via SFTP:
- **Machine**: A machine in your network contains the export folder and uploads the files. For the setup, you usually need administrator rights on this machine.
- **Network**: Firewall and proxy allow outbound SFTP connections via TCP 22 to the regional SFTP endpoint.
- **SFTP client**: An SFTP client such as WinSCP, FileZilla, Cyberduck, or OpenSSH `sftp` is installed. For automated operation, you additionally need a sync tool.
- **Password manager**: A password manager holds the backup of the private key.
You receive the following information and files from Lucanet:
- the onboarding kit **lucanet-sftp-keygen-*version*.zip** with generators for Linux, macOS, and Windows
- the host of the SFTP endpoint in the region in which the data of your Lucanet environment is stored
- your user name for the SFTP endpoint
- the `Share/` target folder and a sample file name according to which you name your export files
## Setup Process for the File Import via SFTP in VAT
Lucanet and your IT team share the setup of the file import via SFTP in VAT. The following table shows the steps and the role that executes each step:
| Step | Role | Content |
|---|---|---|
| 1 | Lucanet | Lucanet sets up the storage area and the SFTP user for your Lucanet environment. |
| 2 | Lucanet | Lucanet creates an interface of the **Network drive** type in VAT, maintains the filename pattern, and executes the connection test. |
| 3 | Lucanet | Lucanet provides you with the onboarding kit, the host, the user name, and the sample file name. |
| 4 | Customer | You generate an SSH key pair. |
| 5 | Customer | You send only the public key to Lucanet. |
| 6 | Lucanet | Lucanet registers your public key, compares the fingerprint with you, and confirms the host and user name. |
| 7 | Customer | You allow the connection in the firewall, check the host key, and test the connection. |
| 8 | Customer | You upload a test file to the `Share/` folder. |
| 9 | Customer | You execute the import in VAT and check the result. |
| 10 | Customer | You automate the upload and monitor it. |
Between step 5 and step 7, you wait for Lucanet. As long as Lucanet has not registered your public key and confirmed the host and user name, every sign-in fails. The failed sign-in is not a misconfiguration on your side, but the handover point in the process.
## Configuring the Interface for the File Import via SFTP in VAT
For VAT to find the uploaded files, an interface of the **Network drive** type exists in VAT. Lucanet creates the interface at the start of the project in the **Interface configuration** workspace. You access the workspace via the gear icon in the top right corner.
On the Lucanet CFO Solution Platform, VAT hides the **Path to netdrive** and **Path to archive directory** fields because VAT automatically uses the `Share/` and `Archive/` folders of your storage area. In the interface, you maintain the **Filename pattern**, for example:
```text
----.
```
The page for creating an interface of the **Network drive** type is displayed in VAT as follows, for example:
The 'Interface configuration: Network drive' page
The **Connection test** checks reading and writing in one step: VAT reads the `Share/` folder and creates an empty test file in `Archive/`, which VAT then deletes again. Lucanet executes the connection test before you upload for the first time. This way, Lucanet can reliably distinguish permission errors from upload problems.
Lucanet defines the specific filename pattern with you during the project. You receive a sample file name based on the pattern, according to which you name your export files, as described in the [File Names for the File Import via SFTP in VAT](#file-names-for-the-file-import-via-sftp-in-vat) section.
## Generating an SSH Key Pair for the File Import via SFTP in VAT
The sign-in to the SFTP endpoint for VAT uses an SSH key pair of the ed25519 type. You generate the key pair on the machine that will upload the files later. The onboarding kit from Lucanet contains generators for all platforms. Any OpenSSH installation generates the key pair just as well.
To generate the SSH key pair for the file import via SFTP in VAT:
### Linux and macOS
Unzip the onboarding kit and execute the generator:
```bash
unzip lucanet-sftp-keygen-.zip
cd lucanet-sftp-keygen-
./generate-key.sh # writes ./lucanet-sftp and ./lucanet-sftp.pub
```
Without the onboarding kit, generate the key pair with OpenSSH:
```bash
ssh-keygen -t ed25519 -C lucanet-sftp -f ./lucanet-sftp
```
### Windows
Unzip the onboarding kit in PowerShell, unblock the scripts, and execute the generator:
```powershell
Expand-Archive lucanet-sftp-keygen-.zip
cd lucanet-sftp-keygen-
# The kit comes from the internet; otherwise Windows blocks the scripts (Mark-of-the-Web):
Get-ChildItem -Recurse -Path . | Unblock-File
.\generate-key.ps1 # writes .\lucanet-sftp and .\lucanet-sftp.pub
```
> **Warning:** Leave the passphrase empty if the upload is to execute unattended, because a service cannot respond to an input request. In this case, the file permissions protect the private key: mode `0600` on Linux and macOS, a restricted ACL on Windows. The generator of the onboarding kit already sets these permissions.
## Sending the Public Key for the File Import via SFTP in VAT to Lucanet
For the registration at the SFTP endpoint for VAT, Lucanet needs only the public key. Send the **lucanet-sftp.pub** file to Lucanet via the agreed secure channel.
The private key never leaves the machine. Store a backup of the private key in the password manager. If the private key is lost, generate a new key pair and send the new public key to Lucanet.
Lucanet checks the public key before the registration. A public key is a single line that starts with `ssh-ed25519`, `ssh-rsa`, or `ecdsa-sha2-`. If the file sent starts with `-----BEGIN ... PRIVATE KEY-----`, it is the private key: Lucanet then does not import the file, deletes it, and requests a new key pair.
After the registration, Lucanet compares the fingerprint of the public key with you and confirms the host and user name.
> **Warning:** To replace the key without downtime, send the new public key to Lucanet, switch to the new private key after the confirmation, and only then ask Lucanet to delete the old public key. The deletion takes effect immediately, and you cannot undo it.
## Checking the Firewall and the Host Key for the File Import via SFTP in VAT
Before you upload the first file for VAT, allow the connection and check the identity of the SFTP endpoint. To do so, allow outbound connections via TCP 22 to the host of your region in the firewall and proxy.
To record the host key of the SFTP endpoint for VAT and display its fingerprint, for example for the Frankfurt region:
```bash
ssh-keyscan -p 22 eu-central-1.sftp.platform.lucanet.cloud > known_hosts
ssh-keygen -lf known_hosts
```
Compare the displayed fingerprint with the fingerprint of your region. The following table shows the hosts and fingerprints of the SFTP endpoints:
| Region | Host | Fingerprint |
|---|---|---|
| eu-central-1, Frankfurt | `eu-central-1.sftp.platform.lucanet.cloud` | `SHA256:JV+0dVOFVOMOA8Zn5gRhpSVQZALjsoY7OD+fPfJiqLM` |
| eu-north-1, Stockholm | `eu-north-1.sftp.platform.lucanet.cloud` | `SHA256:ROlNNvtVe5BCAeIYJOrBfiXKhLua6Upml3k427EG3WQ` |
Each region has its own endpoint and therefore its own fingerprint. Compare the line for the host that Lucanet gave you. Both host keys are 4096-bit RSA keys; `ssh-keygen -lf` reports them as `4096 SHA256:… (RSA)`.
> **Warning:** If the fingerprint differs, stop and contact Lucanet. Do not simply read in the host key again. `ssh-keyscan` trusts the server that answers at that moment. If the connection were intercepted, you would store the attacker's key, and every later check would confirm it. Only the comparison with the published fingerprint closes this gap. The same rule applies later: A host key error in an active route is a reason to stop and ask, not a reason to delete `known_hosts`.
Then test the connection. Replace *user-name* with the user name that Lucanet confirmed to you:
```bash
sftp -i ./lucanet-sftp @eu-central-1.sftp.platform.lucanet.cloud
```
## Uploading a Test File via SFTP for VAT
For the first upload to the storage area for VAT, use a test file without real data.
To upload the test file for VAT with OpenSSH `sftp`:
```bash
sftp -i ./lucanet-sftp @eu-central-1.sftp.platform.lucanet.cloud
sftp> cd Share
sftp> put test.csv
sftp> ls
```
In a graphical SFTP client, enter the host, port 22, and the user name, select the **lucanet-sftp** file as the identity file, and drag the file to the `Share/` folder.
> **Warning:** Always upload the files to the `Share/` folder. The import in VAT does not find a file in the root directory of the storage area.
## Executing and Checking the Import in VAT
After the upload, start the import in VAT. For a single company, click **Import from network drive** in the [Import](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/import-single-company.md) workspace. For several companies, click **Update import data** in the [Mass Data Import](https://support.lucanet.com/en/documentation/income-taxes/vat/value-added-tax/import-multiple-companies.md) workspace.
The import reads the `Share/` folder including all subfolders and checks every file name against the filename pattern. VAT stores processed files under `Archive//#