Financials > Matching > Automatic matching 

Use this function to manage automatic matching, which pairs accounting entries to facilitate the analysis of an account balance on any given date.
Example: associating an invoice with a payment

The transactions recorded in the A/P-A/R Accounting module on customer and supplier accounts are the object of an automatic matching. The payments are posted directly to the invoices or journals to which they are linked.

The matching function in the Financials module is used for matching GL accounts. 

The principle of automatic matching consists of generating a selection process and the automatic reconciliation of postings as a function of previously defined criteria. It can be generated for an account from the manual matching function or for a group of accounts from the dedicated function.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

The automatic matching processing of accounts can be generated globally from the dedicated function, which makes it possible to select all the accounts to be matched.

As a function of the selection criteria used, the accounts are matched by:

  • All the companies in the folder or the selected company.
  • If a specific company has been defined, the selection can also correspond to a specific site.
  • It can also include all the accounts or certain accounts falling within a number range, and even some auxiliary accounts when the GL account defined is a collective account.
  • You can restrict the selection to a date range.
  • Any errors are detailed in a log file displays when the process is complete.

Matched entries: 

These are marked with an uppercase letter code.

An automatic line in the journal entry is generated that displays the calculated currency variance when the invoice currency is different from the payment currency.

Unmatched, or partially matched entries:

These are or those entries having been subjected to a partial matching, marked by a lowercase letter code, are displayed.

An automatic line in the journal entry showing the calculated currency variance is not generated. However, if you set the LOWMTCGEN – Exch rate var / low matching parameter (CPT chapter, MTC group) to Yes, the currency variance is calculated and automatically generates a line in the journal entry. This only applies to partial matches after changing the parameter setting. So could have a situation where partial payments before the parameter change do not have a corresponding currency variance and those posted after the parameter change would have a corresponding line in the journal entry for the currency conversion calculation.

Close

 

Fields

The following fields are present on this tab :

Header

 

  • Ledger (field LEDTYP)

 

Grid Details

 

Selection

Specify the accounts to be matched.
Matching can be performed for one or all the companies, for one or all the sites.
It is possible to specify:

  • a start and end account,
  • for a control account:
    • a start and end BP
    • a period.

 

 

 

 

  • Start date (field DATDEB)

 

  • End date (field DATFIN)

 

  • Define the criteria (field CRIT)

Specify the accounts to be matched.
Matching can be performed for one or all the companies, for one or all the sites.
It is possible to specify:

  • a start and end account,
  • for a control account:
    • a start and end BP
    • a period.

Close

 

Batch task

This function can be run in batch mode, but no dedicated standard task is delivered to run it.

Specific Buttons

This button is used to define the matching methods to be used and their hierarchy.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Too many entry lines to be matched

This error message is displayed when the number of lines to match exceeds the maximum number of lines as defined in the Number of matching lines - MTC activity code.

Tables used

SEEREFERTTO Refer to documentation Implementation