Glossary

All postings in Consolidation & Financial Planning are made to accounts. Accounts are only changed by postings and therefore behave the same way as accounts in conventional financial accounting systems.

In Lease Accounting, an accounting area is a master data dimension that you can assign to a contract component on the General information tab. An accounting area applies either to a specific reporting entity or to all reporting entities. Accounting areas are statistical only and do not affect the calculation.

Adjustment levels are used in Consolidation & Financial Planning to determine the accounting or valuation basis under which a value was posted and measured, independently of the data level. There is always at least one adjustment level in which data imports are saved by default; separate adjustment levels are typically reserved for standard-specific adjustment postings (e.g., HGB, IFRS, US-GAAP, or corporate valuation). Several adjustment levels can be combined into an adjustment level group to display a combined result, such as an IFRS-compliant consolidated statement.

Anchoring links a company-specific extension element to semantically related elements of the base taxonomy. Anchoring helps clarify the meaning of the extension element. The following two types of anchors are distinguished:

The rules of the respective taxonomy and reporting standard determine which anchors are required or permitted and which requirements apply.

For more information, see Creating a Taxonomy Extension.

In Data Collection, an approver is a user who is assigned to a reporting entity in a reporting package to review the forms submitted by its collectors. Users with the Data Collector role or the Administrator role can be approvers. Approvers approve a form or send it back to the collector with a comment. Each reporting entity needs at least one approver before it can take part in a data collection process.

In Lease Accounting, an asset class groups underlying assets that share the same characteristics and the same accounting treatment, for example buildings or vehicles. Each asset class has an asset class type and a minimum and maximum depreciation period. Asset classes are required for interest rates and for categorizing contract components.

Assignment tables are used in Consolidation & Financial Planning to save the elements imported from a source system (e.g., accounts, reporting entities, cost centers, partners, transaction currencies, transaction types, data levels, and adjustment levels) and their assignment to the corresponding elements in the Lucanet database. Assignments are defined during a data import and can be changed or deleted at any time.

Attributes are used in Consolidation & Financial Planning to define multilingual descriptions or customer-specific information for Lucanet elements. An attribute must be created and activated for the dimension of an element before its value can be defined in that element's properties.

In Lease Accounting, a business unit is a master data dimension that you can assign to a contract component on the General information tab. A business unit applies either to a specific reporting entity or to all reporting entities. Business units are statistical only and do not affect the calculation.

In Data Collection, a CFP pivot table is a form template element whose rows are taken over from a Consolidation & Financial Planning workspace, such as the general ledger, a subledger, a statistical ledger, or a schedule. The rows keep their hierarchy, can be synchronized with CFP later, and their currency columns can be marked as used for postings so that the collected values can be imported into CFP.

In Lease Accounting, a change of lessee transfers an active, calculated contract component from one reporting entity to another as of a transfer date. The source component is terminated in its reporting entity, and a copy is created in the target reporting entity. Changes of lessee are uploaded as an XLSX file and can be undone.

CO₂ equivalent (CO₂e) expresses the climate impact of different greenhouse gases as the amount of carbon dioxide with an equivalent warming effect. This makes emissions from different greenhouse gases comparable and allows them to be added together. Values can be expressed in kilograms or metric tons of CO₂e.

In Lucanet ESG Reporting, emission factors can be expressed in kgCO2e per activity unit, such as a kilowatt-hour of electricity. These factors are used to calculate the emissions of a footprint.

The Cockpit is the central work interface in Lucanet Disclosure Management. It provides an overview of all the documents managed in Disclosure Management and their editing state at a glance.

In Data Collection, a collector is a user with the Data Collector role who is assigned to a reporting entity in a reporting package to enter or import the data of its forms, execute the validation rules, and submit the forms for approval. Each reporting entity needs at least one collector before it can take part in a data collection process.

Consolidation areas are the elements in Consolidation & Financial Planning that contain all consolidation units that are to be consolidated together.

Consolidation units are used in Consolidation & Financial Planning to represent the consolidation dimension elements in consolidation areas. A default consolidation unit must 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. To simplify administration, consolidation units can be grouped into consolidation unit groups.

With a Content Group, you assign sections of a Word document in Lucanet Disclosure Management to one or more audiences (for example, Internal, External, or Management). When creating a result document, you select the content groups whose content should be included; sections without an assigned content group are always included, and sections with an assigned content group are included only if at least one of these content groups is selected. Content groups are managed in the Style Guide Manager.

In Lease Accounting, a contract component is the unit that is categorized, calculated, and posted. A lease contract consists of one or more contract components, for example one component per leased vehicle. Each component has an underlying asset, a lease term, and payments, and can optionally be assigned master data dimensions such as a cost center.

Cost centers are used in Consolidation & Financial Planning to describe in detail where costs were incurred within a reporting entity. Cost centers can be grouped into cost center groups. When cost centers are used, a default cost center is always required, to which all values without cost center information are posted.

In Lease Accounting, cost centers are a master data dimension that you can assign to contract components. If you use Lease Accounting together with Consolidation & Financial Planning, you import the cost centers from Consolidation & Financial Planning. With a standalone license, you create them directly in Lease Accounting.

The CSRD (Corporate Sustainability Reporting Directive) is a directive proposed by the European Union to enhance and standardize sustainability reporting by companies.

In Consolidation & Financial Planning, D/C recording switches the view from plus and minus recording to the entry of accounting values in debit and credit.

A dashboard is a configurable view that visualizes financial data using widgets. Dashboards are created and managed in the Dashboards section of the main menu, and can be shared with other users, duplicated, and exported.

In Data Collection, a data collection process is one execution of a reporting package for a specific reporting period. When an administrator starts the process, Data Collection creates the forms of each reporting entity from all form templates assigned to it, sets a deadline per form template, and notifies the assigned users. The process is finalized when all its forms are approved.

Data Hub is the central data-integration function of the Lucanet CFO Solution Platform and is opened from the main menu. Through connections and source datasets, Data Hub imports data from external source systems, such as SAP S/4HANA, Microsoft Dynamics 365, or an SQL database accessed through JDBC. The imported data is then available to the Lucanet solutions.

The Lucanet Data Lake is the central cloud storage layer for financial and operational data in the Lucanet CFO Solution Platform. The Data Lake stores the data in standardized formats, from the raw data of a source system to reporting-ready datasets. Lucanet.Financial Warehouse is provided within the Lucanet Data Lake.

In Consolidation & Financial Planning, data are stored in data levels. A distinction is made between the actual data level and the planning data levels:

In the Data view in Disclosure Management, you can manually check, update and modify report values that have been imported from a source system.

Debit/credit shifts are configured in Consolidation & Financial Planning so that negative postings do not have to be disclosed as negative numbers in general ledgers. Instead, negative values are posted as positive values to a contra account via the debit/credit shift. The amount is disclosed or not on the contra account in the general ledger, depending on whether the balance is positive or negative.

In xP&A, a dimension is a way of breaking down a variable's data into multiple items — for example, splitting a Revenue variable by Region or Product. Dimensions can be linked to one another (e.g. Employee → Title → Department) so that filtering or aggregating by one dimension correctly follows through to the others.

In ledgers and schedules in Consolidation & Financial Planning, the dimension bar is displayed in the upper area of the application window. In the dimension bar, the dimensions Time period, Adjustment level, Data level, Organization element, Transaction currency, Display currency, and Partner are selected and configured for display in the tree view.

Directory structures are workspaces used in Consolidation & Financial Planning to administer elements such as connections, Lucanet.Excel-Reporting files, Next Generation Apps, scripts, workflows, and folders.

Disclosure Management is the solution for creating reports and managing publication. It is designed to help you organize and optimize the "final furlong" of your reporting process. It was developed to manage fiscal content in all types of report that handle large volumes of numerical information that needs to be synchronized between multiple data sources and consumers.

The main purpose of this software is to eliminate most of the manual steps that are required when transferring data from their systems to the necessary output format. At the same time, it is designed to keep the information consistent in different parts of a single report, across multiple reports, and across different output formats.

Disclosure Management covers your entire process, from data collection to evaluation, transfer and reporting. Its automated data flow and integrated XBRL tagging system allow you to combine your financial and ESG reporting processes.

The Dispatcher is a program that must be installed on every computer on which Lucanet Disclosure Management is to be used. The Dispatcher is required to establish a connection between the local Office installation and the CFO Solution Platform. The Disclosure Management files are downloaded to the local MS Office by the Dispatcher and then uploaded back to the CFO Solution Platform.

The display currency defines the currency in which values are displayed. In Consolidation & Financial Planning, any desired display currencies can be defined. To display values, exchange rate tables are used to convert all values from the transaction currency to the display currency. Period locks (Audit trails in Lucanet.Financial Client) can be used to define the periods within which exchange rate tables may be created or changed.

Double materiality assessments (DMA) provide a foundational analysis of an organization's impact on sustainability. According to the CSRD, the DMA consists of two types of materiality that organizations need to consider:

By combining these two factors, it is possible to assess which sustainability risks and opportunities are material for a specific company and, thus, should be included in their reporting.

In Data Collection, a drill down lets collectors break the value of a pivot table row or column down by the elements of a dimension: local account, cost center, partner, transaction type, or adjustment level. Administrators configure the drill down in the form template with up to one level per dimension, and can require transaction currency details per partner.

In Data Collection, a dynamic table is a form template element in which collectors can add, duplicate, and remove rows themselves during data collection, up to a configured maximum number of rows. Administrators configure only the columns and the maximum number of rows of a dynamic table.

An emission factor converts activity data, such as energy consumption or distance traveled, into an estimate of greenhouse gas emissions. A factor can express emissions in CO₂ equivalents per activity unit, such as kgCO2e per kilowatt-hour.

In Lucanet ESG Reporting, you select an emission factor when creating a footprint in the Emissions Module. Standard emission factors are provided in the database. ESG Administrators can create custom emission factors for missing activities or organization-specific data, such as supplier data.

The ESEF (European Single Electronic Format) is a regulatory framework mandated by the European Securities and Markets Authority (ESMA) for the digital reporting of annual financial reports by issuers listed on EU-regulated markets.

The Lucanet ESG Reporting ( ESG = E nvironmental, S ocial, and G overnance) solution covers all your needs in the ESG reporting process. 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 requirements and the GHG Protocol, and provides decentralized data collection with customized questionnaires. It can also be used to calculate GHG emissions.

The ESRS (European Sustainability Reporting Standards) are a set of standards developed by the EFRAG (European Financial Reporting Advisory Group) under the mandate of the CSRD (Corporate Sustainability Reporting Directive). These standards aim to enhance and harmonize the sustainability reporting of companies within the European Union by providing clear and detailed guidelines on what and how to report on ESG (Environmental, Social, and Governance) issues.

ESRS 2.0 is a report guideline available in Lucanet ESG Reporting as a third option alongside ESRS and VSME. The ESRS 2.0 questionnaire uses the same pillar structure as ESRS: General Disclosures, Environmental, Social, and Governance, however with a shorter and less complex structure.

The EU Taxonomy is a classification system established by the European Union to provide clarity on which economic activities can be considered environmentally sustainable. This involves defining detailed technical screening criteria for each environmental objective, which are established through delegated acts.

Exchange rate tables are used in Consolidation & Financial Planning to define the exchange rates between transaction currencies and display currencies, including average exchange rates, closing exchange rates, and year-to-date exchange rates. Any number of exchange rate tables can be created, for example to model variants of the same exchange rate relationships with different rates.

In Consolidation & Financial Planning, the Execution log is a tab in the change log of an app, script, data import, or execution setting. It lists each time the element was executed, with date/time, user, and status, and links to the detailed process log of that run. Execution log entries are only available for a rolling retention period of 30 days; older runs remain visible as an Executed entry in the general change log.

Financial materiality, or "outside-in perspective", is a term used to classify a sustainability matter in the double materiality assessment. Financial materiality refers to the importance of ESG factors that have a direct or indirect impact on an organization's financial performance or condition, and it focuses on how environmental and social issues, as well as governance practices, might influence the financial outcome.

A fiscal year is a period of 12 months used by a company or organization for financial and economic purposes. In Consolidation & Financial Planning, the fiscal year does not necessarily have to correspond to the calendar year, but can begin with any month.

In Lucanet ESG Reporting, a footprint is an individual emissions record in the Emissions Module. A footprint combines activity data, such as energy consumption or distance traveled, with an emission factor to calculate greenhouse gas emissions. Each footprint belongs to a scope.

In Data Collection, a form template defines the structure of the data to be collected: sections with elements such as CFP pivot tables, pivot tables, dynamic tables, and text, numeric, financial, date, Boolean, and selection fields. Validation rules and reporting packages can only use published form templates. When an administrator starts a data collection process, Data Collection creates a form from the form template for each reporting entity to which the form template is assigned.

Controlling indicators such as the absolute liquidity ratio, the equity ratio, and the return on sales can be created in Consolidation & Financial Planning using formulas. A formula is a calculated item. The formula used to calculate the value can be specified by the user. Each variable in the formula must refer to an item or an account in the Lucanet database.

In xP&A, a formula is an expression that defines a variable's value, written in xP&A's own formula language. Formulas can reference numbers, other variables, and dimensions, and support functions such as sum, if_error, and if...then...else for aggregation and conditional logic.

In Lease Accounting, the functional currency is the currency of a reporting entity in which the values of all its contract components are calculated and posted. Components in a different component currency are translated into the functional currency. The functional currency can only be changed as long as no components have been calculated for the reporting entity.

The general ledger is used in Consolidation & Financial Planning to store and display ledger elements, primarily accounts and items. The account structure of a balance sheet (generally in accordance with the country-specific accounting standard, e.g. the German Commercial Code (HGB)) is stored in the general ledger. In the general ledger, the original accounts from the financial accounting source systems are created, assigned and managed, and manually created accounts and items are administrated.

GHG is an acronym for greenhouse gases. These are gases that trap heat in the Earth's atmosphere, contributing to the greenhouse effect and global warming. GHG emissions refer to the release of these gases into the atmosphere, mainly through human activities.

The GHG Protocol (Greenhouse Gas Protocol) is an internationally recognized standard for calculating and reporting greenhouse gas emissions. The GHG Protocol provides companies and governments with a standardized method to quantify and manage their emissions.

In xP&A, a group is a set of variables within a section. Groups can be nested by creating a group under an existing group, and a group's total can be displayed automatically in the spreadsheet or on a table.

In a posting of type Posting in Consolidation & Financial Planning, you can define individual historical exchange rate translations for each posting value. All currency translations configured for the reporting entity or consolidation area are taken into account.

IFRS 16 regulates the recognition, measurement, presentation, and disclosure requirements for leases in the financial statements of companies that prepare their accounts in accordance with IFRS.

Impact materiality, or "inside-out perspective", is a term used to classify a sustainability matter in the double materiality assessment. Impact materiality refers to the significance of an organization's effects on the environment and on people, and how these effects influence the organization's capacity to create value over time.

In Lease Accounting, the incremental borrowing rate is the interest rate used to discount the lease payments of a contract component. Lease Accounting determines the rate from the interest rates configured for the combination of asset class, country or region, currency, and lease term, unless a rate is entered manually for the component.

In Data Collection, intercompany validation compares the values that two reporting entities report against each other, for example receivables and payables, in group currency or in transaction currency and optionally within tolerance thresholds. Like regular rules, intercompany validation rules are either Blocking or Warning. Collectors execute the intercompany validation per reporting entity from the Data collection workspace.

Items are used in Consolidation & Financial Planning for a better overview and better structuring of ledgers. Hierarchies are created by means of items. The value at the item level is always the total of all subordinate items and accounts.

iXBRL stands for Inline eXtensible Business Reporting Language. iXBRL is a standard derived from the XBRL standard.

It's a standard that allows financial data and other business reports to be presented in a format that is both human- and machine-readable. This dual capability enhances the transparency and usability of reports, ensuring that they can be easily accessed and analyzed by a wide range of stakeholders, including regulators, investors, and analysts.

In Disclosure Management, the processing of actions initiated by the user is managed by the so-called Job Monitor. Depending on the process and status, the Job Monitor issues a message in the Disclosure Management notification window.

In Consolidation & Financial Planning, a journal contains all postings and data imports of the respective combination of data level and reporting entity or consolidation area and all the documents underlying the individual postings.

A key figure that measures the performance of an organization against a defined objective. In ESG Reporting, KPIs can be added to the questionnaire as formula-based KPIs: calculated values that are derived from the answers to other questions of the questionnaire instead of being answered by an ESG Data Collector.

The Last actual date is a model-level setting in xP&A representing the latest month (or week) of actual historic data. It determines the cut-off before which xP&A uses imported data, and after which it falls back to formulas to produce forecast values.

The Layout Check automatically monitors the text and formatting consistency of a Word chapter in Lucanet Disclosure Management, for example duplicate punctuation marks or font formatting that does not match the company's style guide. It runs when a Word chapter is checked out or updated, and when a result document is created. Which rules are monitored is defined on the Layout Check tab in the Configure document workspace.

With the help of the layout robot, you can use “layout actions” in MS Excel and MS Word to give your tables a uniform design. The layout robot is saved in the Document Settings.

In Lease Accounting, the lease liability is the present value of the lease payments that a lessee owes for a contract component, discounted with the incremental borrowing rate. Lease Accounting calculates the lease liability per period, together with the repayments and interest, and posts it in accordance with IFRS 16.

Ledgers are used in Consolidation & Financial Planning for summarizing accounts and items for recreating a particular presentation (e.g. balance sheet or profit and loss statement). A distinction is made between general ledgers, subledgers, and statistical ledgers.

A lessee is a party in a leasing agreement who receives the right to use an asset owned by the lessor in exchange for lease payments.

A lessor refers to a party that leases out an asset to another party under a lease agreement.

The License Manager is a user role in the Lucanet CFO Solution Platform. Users with this role act as authorized representatives with contractual authority and can request license upgrades via the platform with binding effect. All actions performed are legally binding.

A linkbase is a component of an XBRL taxonomy that describes the relationships between the taxonomy elements. The Lucanet XBRL Tagger displays taxonomies using the following three linkbases:

For more information, see Tagging a Document Manually.

In xP&A, linked models are separate, smaller models that reference each other's variables and visuals instead of combining everything into a single model. Linking models lets teams work on separate parts of a plan (e.g. headcount and revenue) with their own permissions and even a different time granularity per model.

The Lucanet data model is the data objects available in Lucanet and the connection between them.

In Lease Accounting, a migration component is a contract component that has already been accounted for in accordance with IFRS 16 in another tool and is transferred to Lease Accounting as of a migration date. On the Migration tab of the component, you enter the values as of the migration date, such as the deviating interest rate and the start values of the historical cost and the cumulated depreciation.

In xP&A, a model is the container for the sections, variable groups, variables, dimensions, and formulas that make up a plan, forecast, or analysis. Models can be linked to one another, cloned, versioned, and shared or embedded in dashboards.

The Modeler Agent is an AI agent available in xP&A (and via Lucanet Lume) that builds a planning model from a plain-language description, generating the sections, variables, timesteps, aggregations, and formulas so the user does not have to create them manually.

In Lease Accounting, a modification is a change to a contract component that has already been calculated, for example an extension option, a changed payment, or a change of the asset class. Each modification has an effective date from which it is included in the calculation. The modifications of a component are listed in its modification history.

In Disclosure Management, Name columns contain the row designations – or names – for the individual report values, such as the names of items and accounts.

A name column has the following Properties:

Notation for a Name Column

Generally speaking, name columns follow the notation below:

name _sequential number

Example: name_1

Numerical object identifier for elements in Consolidation & Financial Planning. The OID ensures that the corresponding element (= object) to be queried or executed can be identified by the Lucanet software.

OIDC (OpenID Connect) is an authentication method that builds on the OAuth 2.0 protocol and adds an additional identity layer. It enables the secure verification of user identity and supports Single Sign-On (SSO), allowing users to access various applications seamlessly and securely.

In Consolidation & Financial Planning, an organization element is a specific component based upon which an organization is structured, and that serves to define the structure and hierarchy within the organization.

Excel tables and the Outareas defined in them provide the data for the tables in the result documents. To ensure that Lucanet Disclosure Management can use tables from Excel documents contained within Word document, these tables must be part of an Outarea defined in the Excel file. The Outareas created in MS Excel can be transferred to a Word document using the Word Ribbon.

Partners are used in Consolidation & Financial Planning to add partner information to postings and data imports, primarily for consolidation purposes such as mapping intercompany relationships. To view the values of individual partners in aggregate, partners can be grouped into partner groups.

Period locks are used in Consolidation & Financial Planning to lock or unlock postings, data imports, data transfers from MS Excel, and entries in exchange rate tables for a given combination of data level, adjustment level, time, and reporting entity or consolidation area. There are two types: period locks for postings, and period locks for exchange rates. Changes to postings, exchange rates, or lock status are logged on the Audit trail tab of a period lock. Period locks correspond to Audit trails in Lucanet.Financial Client.

A posting is used to record a financial transaction or event in a financial accounting system. All postings in Consolidation & Financial Planning are made to accounts.

In Lease Accounting, a profit center is a master data dimension that you can assign to a contract component on the General information tab. A profit center applies either to a specific reporting entity or to all reporting entities and can be related to a cost center. Profit centers are statistical only and do not affect the calculation.

In Disclosure Management, the Programming column is responsible for programming the content of value columns ( value_ columns). It contains data such as item and account numbers from the source system, plus other information for calculating values in values columns.

A programming column has the following properties:

Notation for a Programming Column

Generally speaking, programming columns follow the notation below:

prog_ sequential number_Suffix

Example: prog_2_PCURRENTYEAR

A process log is the detailed record generated when an app, script, data import, or execution setting is executed in Consolidation & Financial Planning. It lists the individual steps of the run in a hierarchical tree, with their timing, duration, and progress, and can be downloaded as a text or Excel file. Process logs are opened from the Execution log.

In Consolidation & Financial Planning, references are links that refer to items or accounts in general ledgers, subledgers and statistical ledgers. References can be used to create derived structures (e.g. a derived IFRS balance sheet). A distinction is made between direct and indirect references.

A report package is a standardized file package based on the ZIP format for distributing XBRL reports together with their associated files. The Report Packages 1.0 specification published by XBRL International defines its structure. For an iXBRL report, the package contains one or more related XHTML documents and, where applicable, a report-specific extension taxonomy and associated resources such as images or style sheets. The package also contains metadata that describes the package. The Lucanet XBRL Tagger creates the report package when it generates the report. The requirements of the respective filing authority determine which package format and additional contents are required for submission.

For more information, see Generating an XBRL Report Package.

Reporting entities are the elements in Consolidation & Financial Planning to which postings can be made. Generally, reporting entities are equivalent to the companies of an enterprise. To enable granular postings, cost centers can be created for reporting entities.

Data Collection imports reporting entities from Consolidation & Financial Planning, and administrators assign collectors and approvers to them. Every form in a data collection process belongs to exactly one reporting entity.

In Lease Accounting, a reporting entity is a company that records leases as the lessee. Each reporting entity has a country or region and a functional currency, and all workspaces except Settings display the data of the reporting entity selected in the Get started workspace.

In Lucanet ESG Reporting, a reporting entity is an organizational unit for which ESG data is collected in a report. ESG Administrators select the participating reporting entities in the report's master data and assign users to provide their data. Reporting entities can be taken from Lucanet.Financial OLAP Server or created directly in the ESG report's master data if Lucanet.Financial OLAP Server is not used.

In Data Collection, a reporting package bundles the published form templates, the participating reporting entities with their collectors and approvers, the collection frequency, and the group currency for a data collection process. An administrator can only start a data collection process from a published reporting package. Administrators can change a reporting package later. The changes apply only to data collection processes that start afterwards.

In the Lucanet XBRL Tagger, a reporting requirement is a predefined specification that bundles the requirements a regulatory authority sets for a document, for example for ESEF reporting. Among other things, the reporting requirement determines the primary taxonomy of a document. When you add a document, the XBRL Tagger automatically searches for the suitable reporting requirement; you can change it manually if necessary.

For more information, see Dashboard.

A result document is the final report or business report created in Lucanet Disclosure Management, often in the form of a Word file. Microsoft Word is the most important output medium for fiscal reports of all types. Disclosure Management can generate a ready-to-print layout at the Microsoft Word level itself. This is achieved using a “layout robot”, which can create tables that match the specified corporate design at the push of a button.

Ribbons are multi-functional bars for applications. In Lucanet Disclosure Management, you can use special functions in ribbons for MS Excel and MS Word when working with MS Office documents:

In Lease Accounting, the right-of-use asset is the asset that a lessee recognizes for the right to use the underlying asset of a contract component during the lease term. It is measured on the basis of the lease liability and depreciated over the lease term or the useful life of the underlying asset.

SAML (Security Assertion Markup Language) is an XML-based framework for the distribution of authentication and authorization information between different parties, particularly between an Identity Provider (IdP) and a Service Provider (SP). It enables Single Sign-On (SSO) by securely transmitting authentication data over the Internet, allowing users to access multiple applications and services with a single set of login credentials.

In xP&A, a scenario is a named variant of a model's data (e.g. Base Case, Upside, Downside) that lets you compare different sets of assumptions or outcomes side by side without duplicating the whole model. Each additional scenario increases a model's total cell count.

Schedules are used in Consolidation & Financial Planning for summary presentation of changes with respect to a particular area, e.g. assets, provisions, credits or equity.

A scope is one of the three categories that the GHG Protocol uses to classify greenhouse gas emissions. In Lucanet ESG Reporting, footprints in the Emissions Module are organized by these scopes:

For Scope 2 emissions, Lucanet ESG Reporting follows the GHG Protocol's distinction between location-based calculations using average grid emissions intensity and market-based calculations reflecting the organization's specific energy purchases.

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 Consolidation & Financial Planning 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.

In xP&A, a section organizes variables within the spreadsheet view. Every model has an Inputs section by default, whose variables appear as adjustable inputs on the model's dashboard.

Separators are empty items that can be created in Lucanet.Financial Client for better clarity of ledgers and schedules.

Sheets are used in Consolidation & Financial Planning as a flexible way to perform the calculations required in the financial planning process. Sheets can be created for reporting entities or for values of ledgers and schedules in planning data levels. They can be created either from within a journal or directly from a ledger. They replace the planning forms used in Lucanet.Financial Client.

In a cumulated display in Consolidation & Financial Planning, the sum of a value is displayed in posting columns across all posting entries.

A Software Bill of Materials (SBOM) is a comprehensive list of all components, including open-source and third-party elements, that are contained in a software application. An SBOM typically includes information on component names, versions, licenses, and dependencies. In the Lucanet CFO Solution Platform, SBOMs are available for download in JSON format.

Solution is the word Lucanet uses for applications that can run on the Lucanet CFO Solution Platform. Examples of solutions include Consolidation & Financial Planning, ESG Reporting and Disclosure Management. The solutions you have licensed are displayed in the main menu of the Lucanet CFO Solution Platform. For licensing, customers should contact their Lucanet contact person or use the contact form↗ on the Lucanet website.

A source dataset specifies which data Data Hub imports from a source system, and how to configure the import. Each source dataset belongs to a connection. Importing a source dataset makes its data available to the Lucanet solutions.

A source system is a data source that the data in Lucanet are imported from, for example an ERP system such as SAP S/4HANA or Microsoft Dynamics 365, a spreadsheet, or another external system. Various Lucanet solutions import data from source systems.

Statistical ledgers can be used in Consolidation & Financial Planning to create account hierarchies that need not be subject to the rules of double-entry accounting (e.g. derived profit and loss structures and balance sheet structures, indirect cash flow statements, and direct liquidity planning or statistical workspaces).

In Lucanet Disclosure Management, a structure refers to a named selection and arrangement of a document’s chapters. Structures are used to generate different report versions from a single source document (e.g., summary report, detailed report, management report).

The Default structure always contains all chapters of the document.

Subledgers are used in Consolidation & Financial Planning 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 (generally in accordance with the country-specific accounting standard, e.g. the German Commercial Code (HGB)). 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 Lucanet XBRL Tagger, tagging refers to assigning values and text sections of a report to elements of an XBRL taxonomy. The result is a tag that marks the value or text in a machine-readable way. In the XBRL Tagger, you tag by drag and drop or with AI support using the Tagger Agent.

For more information, see Tagging a Document Manually and Tagging a Document with AI.

A taxonomy, also called an XBRL taxonomy, is a structured collection of elements that describes the items and disclosures of a reporting mandate in a machine-readable way, for example the ESEF taxonomy, which is based on the IFRS taxonomy. Additional information is available for each taxonomy element, such as labels in several languages and the calculations to which the element belongs. In the Lucanet XBRL Tagger, the selected reporting requirement determines the taxonomy.

For more information, see Introduction to iXBRL and the XBRL Tagger.

Taxonomy alignment means that an economic activity meets the requirements for environmental sustainability under the EU Taxonomy. An activity must contribute substantially to at least one environmental objective, do no significant harm to the other objectives, comply with minimum safeguards, and meet the applicable technical screening criteria.

Taxonomy eligibility means that an economic activity is covered by an activity description in the delegated acts of the EU Taxonomy, regardless of whether it meets the associated technical screening criteria. An eligible activity is therefore not automatically taxonomy-aligned.

A taxonomy extension, also called an extension element, is a company-specific element that you create in the Lucanet XBRL Tagger if the standard taxonomy does not contain a suitable element. A taxonomy extension is only permitted if the core element of the taxonomy would lead to a misrepresentation. You must link each taxonomy extension to the core taxonomy by anchoring.

For more information, see Creating a Taxonomy Extension.

Time series are elements in Lucanet.Financial Client that partially have predefined values, such as work days per year, but can also represent customizable values.

A timestep in xP&A is a single period of time (e.g. one month or one week) in a model's timeline, determined by the model's time granularity. Formulas can reference values from other timesteps (e.g. the previous month).

Total lines or subtotal lines are elements in Consolidation & Financial Planning whose values are based on the total of all elements of the same level above the total line.

TOTP stands for Time-based One-Time Password. The authenticator app and the server derive the same six-digit code from a key that is shared when the app is set up and from the current time. The code changes every 30 seconds and is generated without an internet connection. In the Lucanet CFO Solution Platform, TOTP is used for the TOTP MFA (authenticator app code) authentication method.

The transaction currency defines the currency in which a financial transaction (e.g., a posting) is performed in Consolidation & Financial Planning. Each posting must contain information about its transaction currency. Exchange rate tables are used to convert values from the transaction currency to the display currency. You can define any number of transaction currencies.

In Lease Accounting, the transaction plan defines to which accounts and transaction types Lease Accounting posts the values of each asset class type. Lease Accounting provides a default transaction plan, and you can upload your own transaction plan as an Excel file in the Posting configurations workspace. The transaction plan applies to all postings saved after the upload.

Transaction types are used in Consolidation & Financial Planning to provide information about the reason for changes to an account within a given period. This information is used to display schedules (fixed asset schedules, provision schedules, statements of changes in equity, loan schedules) and the indirect cash flow statement.

Transaction type categories summarize all transaction types for a schedule. The following transaction type categories are predefined in Consolidation & Financial Planning: fixed asset schedules, provision schedules, loan schedules, and statements of changes in equity. There are predefined transaction types in all categories. In addition, any number of other transaction type categories and transaction types can be created in Consolidation & Financial Planning.

In Lease Accounting, a transition component is a contract component for which IFRS 16 is applied for the first time as of the transition date that you define on the General configuration tab of the Posting configurations workspace. On the Transition tab of the component, you specify whether the component was an operating lease or a finance lease under IAS 17 and enter the values required for the transition.

In Disclosure Management, validations provide a way of checking and ensuring consistency within a document and its associated calculation. Validations summarize any deviations between values that should be the same within a document. They do this by comparing two values.

In Data Collection, validation means executing the validation rules of a form or the intercompany validation of a reporting entity. Collectors can only submit a form after they have executed its validation rules and no blocking rule has failed.

In Data Collection, a validation rule checks the collected data before a collector submits a form. Regular rules validate relationships within one form or between the forms of the same reporting entity and are either Blocking, which prevents submission until the rule passes, or Warning. Intercompany validation rules compare values between two reporting entities and are also either Blocking or Warning. Data Collection only applies published validation rules to new data collection processes.

In Disclosure Management, Value columns contain the report values for 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:

Notation for a Value Column

Generally speaking, value columns follow the notation below:

value_ sequential number[_suffix]

Example: value_1_PAJ06

Vibe Mode is an AI option in xP&A that automatically generates suggestions for new variables as a user builds out a model, without the user needing to explicitly ask for them — unlike Ask AI, which generates suggestions on request.

The dimensions displayed in the Dimension bar in ledgers and schedules depend on the configuration of the corresponding View to which the dimension bar belongs. Lucanet.Financial Client and Consolidation & Financial Planning provide the option of configuring different views with any desired columns. In addition to the default view for the presentation of time series, reporting entities and adjustment levels, any number of comparison views can also be configured.

In xP&A, a view is a saved filter on a model — by variable, dimension item, scenario, or time period — used to display only a relevant subset of the model's content. Views can optionally be shared with specific collaborators at a chosen access level, e.g. Can view or Can edit.

VSME stands for Voluntary Sustainability Reporting Standard and is designed for small and medium enterprises (SMEs). It is a European voluntary reporting framework developed to provide a simplified, proportional alternative to the mandatory ESRS (European Sustainability Reporting Standards). VSME has been developed by the EFRAG (European Financial Reporting Advisory Group) for SMEs excluded from the CSRD, enabling these companies to report on ESG issues without using ESRS, which have a broader scope, to fulfill business partner data requests and secure green financing.

A widget is a single element on a dashboard that displays data or text. Widgets are placed and resized on the dashboard grid and configured individually with the data they display. The available widget types are KPI, Bar, Line, Static bar, Waterfall, Pie, Listogram, and Text box.

A workspace is an area in which thematically related objects are grouped together — for example, Reporting entities or Currency translation in Consolidation & Financial Planning, or Form templates in Data Collection. Workspaces exist across all Lucanet solutions on the Lucanet CFO Solution Platform.

XBRL stands for eXtensible Business Reporting Language. It is an XML-based language used to create electronic documents in the field of financial reporting.

The XBRL standard is an internationally recognized standard for creating and transferring digital financial data to authorities, investors and other recipients. In fact, using the XBRL format for financial reports is a legal requirement in many countries.

The structure of the company’s electronic data is generally based on a particular accounting standard. This is referred to as the XBRL taxonomy. Examples of this include the HGB, IFRS, and US-GAAP taxonomies.