The EBR app uses a specific “Data Exchange Definition”, already prepared and included in the tools of the App, which can be quickly imported.
It is possible to manage the CBI reasons that qualify the reporting movements to facilitate the reconciliation and posting operations. Through “Create Reason Codes” you can automatically create the current CBI reasons.
To each CBI reason it is possible to associate a counterpart (G/L account, Bank Account, Customer, Vendor) which will be used automatically in the posting of the accounting transaction.
The counterpart can be generic or specific for each current account.
The balance source type can be a G/L account, but it is possible to choose also Bank Account.
In particular, the possibility of using the Bank Account Type allows you to manage transfer transactions, transit bank accounts, bank accounts for cash pooling operations.
For each reason it is possible to define the “CBI Reasons – Posted Reconc. Ledger Entry Doc. Type” which will be used in the accounting posting. The options provided are:
Default | enables the standard BC behavior which only provides the document type "Payment" or "Refund" depending on the sign of the transaction. |
Blank | it is possible to use the "blank" document type for posting financial charges / income, transfers and, in general, movements that are not receipts \ payments, |
Through “Account Mapping " it is possible to view the general mapping settings:
On “Bank Acc. Reconciliation Setup (EBR)” you can set:
On the Bank Account card you need to enter:
On each bank account card, you can set the tolerance parameters used by the payment link function. The “Payment Matching” section is never used.
The “EBR” App uses in the “Payment Reconciliation Journals” and the standard automatic linking functions. Previously, therefore, it is necessary to check the settings proposed by the system in relation to:
The “Payment Application Settings” page allows you to define general linking criteria. The main parameters are as follows:
Name | Description |
---|---|
Related Party Name Matching | defines whether to carry out the recognition on customer \ vendor \ banks \ employees ledger entries for * Whole string (Exact Match with Permutations) * Partial match (String Nearness) * No match (Disabled) |
Enable Customer Ledger Entries Matching | defines whether to carry out the recognition of customer entries |
Enable Vendor Ledger Entries Matching | defines whether to carry out the recognition of vendor entries |
Enable Bank Ledger Entries Matching | defines whether to carry out the recognition of bank entries |
On Payment Application Rules page you can change the automatic linking policies used by the system.
These connections are based on the following parameters:
Which are compared with the fields present on the transaction:
The recording of bank statements has a specific source code defined in the “Source Code Setup” page (it is proposed automatically by the system)
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.