Analytical accounting
Introduction into analytical accounting
“Analytical accounting” corresponds to cost accounting in AOS.
Analytical accounting is a genuine management and steering tool for companies. With the analytical accounting, the data is processed to explain financial results and provide the information needed for decision-making. It is based on, but is not limited to, general financial accounting.
Analytical accounting is not compulsory, although it is recommended.
Analytical accounting has a number of objectives:
-
To identify the costs of a company's various functions ;
-
Calculate profit or loss by product ;
-
Inventory management ;
-
Explain the results ;
-
Provide management with detailed financial information for decision-making.
Analytical entry
An analytical entry in AOS is an operation, consisting of recording a commercial transaction (Purchase/Sales Order, Purchase/Sales Invoice, Contracts, etc.), or a financial transaction (Purchase/Sales Invoice) by means of a distribution on analytical axes and on each of these axes by a distribution into analytical accounts.
An entry corresponds to a “move” in AOS.
Analytical entries are :
- Recorded in one or more journals (for categorisation if necessary);
-Of a forecast type (Order, Contract, Invoice) or an actual type (Accounting);
-
Represent an amount via a distribution percentage applicable to the related transaction (order line, invoice line, accounting entry line);
-
Dated (the date is identical to the date of the related transaction).
Analytical journals
Access: Accounting → Configuration → Analytics → Analytic journals
Journals can be configured via the Accounting menu.
The analytical journal is an extra-accounting document (it’s not mandatory) which records all the analytical entries that have been generated.
In Axelor, even if it is possible to generate several analytical journals, it is necessary at the very least to create an Analytical journal that will record all the entries that have been created.
Analytical axes
Access: Accounting → Configuration → Analytics → Analytic axes
Analytical axes are values. These values are used to categorise analytical entries so that they can be tracked and analysed on different models, such as Sales Orders, Purchases, Invoices and Accounting Entries. An example of an analytical axis is a project or department from which originated the accounting entry.
Analytical axes are attached to a company or can be shared between companies (in the case of a multi-company). To be shared, the Company field must not be filled in on the analytical axis.
An axis is characterised by a Code and a Name. Bear in mind that the Code must be unique for each company. The distribution on each analytical axis must always be equal to 100% to ensure that the data is perfectly consistent.
The analytical axis also has 2 additional options:
-
Manage parent accounts: this option allows you to authorise the management of tree structures (on several levels) on analytical accounts.
-
Number of analytical groupings: analytical groupings are used to add depth of analysis with another dimension to group data across axes or potentially on the same axis. For each analytical grouping, you can define grouping values, which can be selected directly on the analytical account.
Analytical accounts
Access: Accounting → Configuration → Analytics → Analytic accounts
The analytical accounts or analytical items or analytical sections are the detail elements which are attached to an analytical axis and which enable financial transactions to be allocated via one or more distribution keys.
Analytical accounts are attached to a company or can be shared between companies in the case of a multi-company system. If the company field is empty, the account is shared.
If, for example, the Analytical Axis is a Department axis, then the analytical accounts are the departments and they will allocate the analytical entries to these items.
The analytical accounts have levels, the lowest and main level being level 1.
If the analytical axis allows parent accounts, the Parent field will be displayed, enabling you to manage a tree structure.
Here is an example for an organisation by department: the Trade department, which would be a Level 1, could have two sub-levels. These two sub-levels are : 1 B2B analytical account and 1 B2C analytical account. The analytical account related to a level 1 account must necessarily be level 2.
For example: Axis 2 (on the right side) authorises the use of parent codes, unlike Axis 1. If the grouping criteria is activated, it is possible to define the corresponding grouping values.