Generally speaking, the matching consists of pairing journal postings unsing a matching code in order to facilitate the analysis of an account balance on a given date.
For instance: associate an invoice with its payment.
Based on criteria defined beforehand, the matching can be:
In any case, a wrong matching can be cancelled:
Refer to documentation Implementation
Presentation
The account unmatching processing can be generated globally from the dedicated function, which defines the unmatching criteria.
Based on the selection criteria used, the matchings to be cancelled will be searched for:
It is possible to limit cancellations to the partial or closed matching groups and to certain matching codes.
The selection of the entries to be unmatched is necessarily limited by a start date and an end date. It can concern all the periods or the open periods only.
Close
Fields
The following fields are present on this tab :
Header
|
  |
|
Select the ledger where the matching and unmatching operations will be carried out. |
Grid Details
|
  |
Selection
|
It is possible to define the ranges of accounts to be unmatched. If only one account is selected, it is possible to specify ranges on the match letters to be unmatched. |
|
  |
|
  |
|
  |
|
  |
|
  |
|
  |
|
If this box is checked, no control will be performed on the period status. |
|
It is possible to define the ranges of accounts to be unmatched. If only one account is selected, it is possible to specify ranges on the match letters to be unmatched. |
|
  |
|
  |
Close
This function can be run in batch mode. The standard task ACCUNMTC is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
The selected site does not belong to the previously selected company. Use the selection function to find another site.
The date ranges are not consistent. For instance, this message can be displayed if the range end date entered is earlier than the range start date.