Counterpart extraction
This function is used to define the counterpart extraction rules.
It is used to:
- define te journals involved in the extraction (all the journals impacting a list of accounts),
- aggregate the amounts mentioned on these journals in the ledger keeping currency onto total lines that can be set up.
The following postings, because of their nature, are not a part of the extraction:
- entry templates,
- inactive simulations,
- Carry-forward or closing entries.
The extract function has been originally designed to calculate the funds flow statements (extraction of those journals having an impact on the financial accounts, and total of their counterparts, to enable the analysis of the cash flows by origin (customer cash receipt, supplier cash disbursement, bank expenses, etc.). it can also be used for any other type of analysis based on this principle.
Prerequisite
Refer to documentation Implementation
Screen management
This function is used to define a counterpart extraction rule.
It is composed of:
- a header defining the rule, as well as the accounts to be analyzed,
- a grid, available to set up the aggregation rules of the counterpart amounts.
Entry screen
Identification
Extraction code (field CODANY) | ||||||||||||||||
This code identifies the extraction rule. |
||||||||||||||||
Active (field ENAFLG) | ||||||||||||||||
This box is used to specify if the tax determination rule must be activated or not:
|
||||||||||||||||
Description (field DESTRA) | ||||||||||||||||
Common title of the current record. |
||||||||||||||||
Movement type (field TYPMNT) | ||||||||||||||||
Enter the type of movement you wish to export. You can, for instance, export movements only or both movements and carry-forwards. |
||||||||||||||||
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.
|
||||||||||||||||
Accounts to be analyzed (field FRM) | ||||||||||||||||
This field will store the accounts that represent cash or bank deposits. The calculation will only be done for entry journals including such accounts. The setup principles are the following:
|
Option
Include rate deviations (field RATDEVFLG) |
This field will give the user the possibility of diferenciating the booking of the rate deviations or not. So, the behaviour is as follows:
The rate deviations accounts are triggered from the chart of accounts associated to the core model and ledger defined previously. |
Grid Setup
Original account (field ORIFRM) | ||||||||||||||||
This 250-character field is used to define the accounts to be processed. The setup principles are the following:
|
||||||||||||||||
Code (field COD1) | ||||||||||||||||
The amounts are aggregated onto lines that can be set up. The code and sub-code define each line in a unique manner. Descriptions and a formula are associated with it. |
||||||||||||||||
Subcode (field COD2) | ||||||||||||||||
Description (field LIBEL) | ||||||||||||||||
Enter the description of the relevant record. This long description is used as a title in screens and reports. |