Account Structures
The account structures, designed to simplify the entry of journals of a recurring nature, are used to automatically initialize accounting (general account, tax code) and analytical (natures, allocation structures and dimensions) information of the entries associated with it.
They are accessible in the parameters of the entry transactions, when entering journals or invoices (customer or supplier) of the A/P - A/R Accounting module.
The combination of an account structure and an entry transaction is used to optimize the entry of postings by only displaying on the screen the fields necessary for the entry and by defining their default value.
When entering a BP invoice, by default, once the tax-excl amount of the invoice has been entered, it is suggested to apply the account structure defined at the level of the customer or supplier record (see the documentations Customers and Suppliers)
When the account structure contains VAT accounts, they are not taken into account on invoice entry.
Based on the module, the purpose of a structure is different:
- an account structure designed to be used in the A/P - A/R Accounting module corresponds to a single-entry entry structure since the offset is ensured with respect to the document header (BP and tax-incl amount),
- an account structure designed to be used in connection with an entry transaction corresponds to a double-entry entry structure since the structure contains all the entry lines of the journal.
Prerequisite
Refer to documentation Implementation
Screen management
Entry screen
Header
Structure (field DIA) |
This code (1 to 10 alphanumerical characters) is used as the sole identifier of the account structure. A structure can be used in invoice entry mode of the A/P-A/R Accounting mode and/or in the parameterization of the journal entry transactions. In an invoice of the A/P-A/R Accounting module, the structure can be used on the invoice line using the "Structure" button. |
field DESTRA |
Common title of the current record. |
Identification
Short description (field SHOTRA) |
The short description replaces the standard description when display or print constraints require it. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language. The connection language must be defined as a default language for thefolder. |
Group (field GFY) |
The 'group' field is used to assign an account structure to the companies and sites contained in the entered group. It is possible to set up a group from the setup of of the account structure. |
Accessibility
Access code (field ACS) |
When it has been entered, the access code makes it possible to limit the operational rights on the account structures based on the user profiles.
|
Validity start date (field VLYSTR) |
These dates define the period during which the structure can be used. |
Validity end date (field VLYEND) |
Grid Chart of accounts code
Chart of accounts (field COA) |
This field is mandatory (at least a chart of accounts must be entered) and is used to specify a chart of accounts for the accounts which will be used in the current account structure. The number of charts of accounts is limited to nine for each account structure. |
Grid Dimension code
Dimension type (field DIE) |
This field is used to specify a dimension view for the accounts whic will be used in the current account structure. This fields is optional. When there is no dimension view entered, the information is copied by default from the setup of the accounts. The number of dimension views is limited to twenty for each account structure. |
Grid Description
No. (field NUMLIG) |
Account (field ACC1) |
This field can accommodate accounts of "normal" or "collective" type. When an account structure is used in BP invoice entry, the accounts parameterized as "VAT account" or "VAT/EU account" will be ignored and the journal line will not be created. |
Account (field ACC2) |
Account (field ACC3) |
Account (field ACC4) |
Account (field ACC5) |
Account (field ACC6) |
Account (field ACC7) |
Account (field ACC8) |
Account (field ACC9) |
BPs (field BPR) |
Accessible field if the account on the line is a "collective" type account, but not mandatory. If the BP field of one of the structure lines is empty, when the latter is preloaded, the operation mode will differ depending on the original function:
|
Coefficient (field COE) |
Specify here the weighting coefficient assigned to this structure line. The coefficient calculation and application method varies depending whether or not the structure is called from the journal entry or the BP invoice entry. In BPinvoiceentry, the coefficients are used to calculate the amount associated with each line as follows: In accountjournalentry, the coefficients are used to calculate the amount associated with each line and determine its sense (Debit/Credit). |
Tax (field VAT) |
This field is used to specify a tax code. |
Description (field LIGDES) |
Setup field used to initialize the content of the journal line or the BP invoice line. |
Distribution (field DSP) |
The analytical distribution codes are used to automatically distribute the amount of an accounting posting line over several analytical lines according to weighting factors and this, via a single entry. |
field CCE1 |
Specify here the analytical allocations of each account structure line dimension view by dimension view. |
field CCE2 |
field CCE3 |
field CCE4 |
field CCE5 |
field CCE6 |
field CCE7 |
field CCE8 |
field CCE9 |
field CCE10 |
field CCE11 |
field CCE12 |
field CCE13 |
field CCE14 |
field CCE15 |
field CCE16 |
field CCE17 |
field CCE18 |
field CCE19 |
field CCE20 |
Pre-loading dimensions |
This functionality is used to retrieve the dimension types set up for the ledgers based on the account structures. |
Reports
By default, the following reports are associated with this function :
LISSCHCPT : Account structures
This can be changed using a different setup.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Incorrect date
This message can be displayed for instance if the validity end date entered is earlier than the validity start date.
You do not have access to this code.
The entered access code does not exist in the table or the user creating the account does not have access to this code. The selection function should be used to find out an existing or authorized code.
Screen incompatible with the nature
The syntax of the entered filter is not consistent with the default nature associated with the account. The nature filter must authorize the use of the account default nature. The default nature or the nature filter have to be modified.