Account
- Title
- Account
- 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.
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.
Audit trails are used to log and monitor 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. These posting releases are controlled in LucaNet.Financial Client in the Posting and planning workspace using audit trails.
Audit trails are used to log and monitor 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. These posting releases are controlled in LucaNet.Financial Client in the Posting and planning workspace using Audit trails.
Consolidation areas are the elements that contain all consolidation units that are to be consolidated together.
D/C recording switches the view from plus and minus recording to the entry of accounting values in debit and credit.
In LucaNet, data are stored in data levels. A distinction is made between the actual data level and the planning data levels:
Debit/credit shifts are configured 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 ledgers and schedules, 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 used to combine elements.
A fiscal year is a period of 12 months used by a company or organization for financial and economic purposes. The fiscal year does not necessarily have to correspond to the calendar year, but can begin and end at any time.
Controlling indicators such as the absolute liquidity ratio, the equity ratio, and the return on sales can be created in LucaNet 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.
The general ledger is used to store and display accounts and items in LucaNet. 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.
In a posting of type Posting, you can define individual historical exchange rate translations in LucaNet.Financial Client for each posting value. All currency translations configured for the reporting entity or consolidation area are taken into account.
Items are used in LucaNet 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.
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.
Ledgers are used 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.
Numerical object identifier for elements. The OID ensures that the corresponding element (= object) to be queried or executed can be identified by the LucaNet software.
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.
A posting is used to record a financial transaction or event in a financial accounting system. All postings in LucaNet are made to accounts.
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.
Reporting entities are the elements to which postings can be made in LucaNet. Generally, reporting entities are equivalent to the companies of an enterprise. To enable granular postings, cost centers can be created for reporting entities.
Schedules are used for summary presentation of changes with respect to a particular area, e.g. assets, provisions, credits or equity.
In a cumulated display, the sum of a value is displayed in posting columns across all posting entries.
Statistical ledgers can be used 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).
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 (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.
The transaction currency specifies which values are used in calculating the display currency. Each posting in LucaNet must contain information about the transaction currency in which they are to be performed. You can define any number of transaction currencies in LucaNet.
Transaction types 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 types 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 LucaNet.Web Client: 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 LucaNet.Financial Client.
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 LucaNet.Web Client 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.