Bank Posting - Implementation
Prerequisite
Activity codes
The following activity codes (sorted by type) may have an impact on the way the function operates :
Dependent activity codes
These codes are never entered in folder management, because their value is calculated :
REGBC (Bank/Cash register).
Functional
LEG :
Multi-legislation management
General parameters
Sequence numbers
No sequence number is used by this function.
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 :
Generation
Access by user
Other prerequisites
Payment types
The payment type is a grouping key of the payments based on the sense of these payments and their payment mode (miscellaneous table no. 3: Checks, Drafts, Transfers, etc.).
The setup of these payment types (see documentation Payment transactions) is used to define the posting and regrouping stages. For instance, the regrouping code is mentioned at this level for the bank deposit (deposit by payment, slips, due date) and the automatic payment journal enabling the generation of the accounting entry is also defined at the same level.
Automatic payment journals
(see documentation Automatic payment journal)
The characteristics (document type, journal, description etc.) of the journal generated further to the payment bank deposit are defined in the automatic payment journal.
The journal type (Cash receipt, disbursement etc.) à is defined in "hard code". It is important to check that it matches the journals to be generated.
Bank account
During the setup of the bank accounts, it is possible to define if the following is managed:
-
off/on-site checks
-
deposits by due date
-
paying bank notices by due date
It is important to check the consistency of this setup with the regrouping codes defined in the payment transaction.