Automatic remittance creation - Implementation
Prerequisite
Activity codes
The following activity codes (sorted by type) may have an impact on the way the function operates :
Functional
LEG :
Multi-legislation management
Sizing
REM :
Number of discount note lines
Sequence numbers
The sequence numbers used to number the documents managed by this function are :
PY5 : Payments-Deposit Slips
The sequence number assignment function defines the sequence number which is used
Authorizations
An authorization can be granted for this function to limit the processes to a company or a site.
The following options can be activated or deactivated for each user :
Access by user
Other prerequisites
Tables to be completed
The following tables are used by the function. Their content must be updated if necessary :
|
Table |
Table description |
|---|---|
|
BANK [BAN] |
|
|
TABPAYTYP [TPY] |
|
|
TABCUR [TCU] |
|
|
FACILITY [FCY] |
|
|
COMPANY [CPY] |
|
|
GACCOUNT [GAC] |
|
|
TABCHANGE [TCH] |
Currency rate table |
|
BPARTNER [BPR] |
Payment transactions
The payment transaction parameters are used to define if the payment must be put on a bank remittance. The creation of a remittance is mandatory if the payment transaction authorizes an intermediate posting phase.
Payment
A bank must therefore be associated with the payment in order that it can be recorded on a remittance.
Banks
In bank parameters (see the documentation Bank accounts), the 'O/L check remit.' field, if checked, is used to automatically generate separate remittances based on the type of check (local menu 654).