Use this function to automatically generate bank remittances for the various payment transactions defined with the posting phase (see the documentation for Payment transactions).

The generation of bank remittances does not constitute in itself a payment posting phase. It makes it possible to generate a remittance that can be:

  • Printed to physically accompany a bank deposit
  • Associated with a bank file for transmission to the bank


Creating a remittance is mandatory if the payment transaction authorizes an intermediate posting phase. 

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Selection criteria of the payments to be recorded on the remittance

Company & Site

The remittance is single-company or single-site, depending on the parameters of the sequence number counter.

  • if no particular company is selected, there is at least one remittance per company.
  • if the site is not specified, the payments for all the sites of the same company are recorded on the same remittance
     (provided this is compatible with other criteria).

It is thus possible to reduce the selection of the payments to be processed in bank remittance generation to one company and one site.

If a company is specified, but not the site, it is necessary to enter the 'Grouping site' field that is used as the header site on the remittance.

Payment transaction

The remittance is payment single-type. Thus, if no payment transaction has been specified, a remittance is generated by transaction.

It is possible to reduce the selection of those payments to be placed on a remittance to one payment transaction on which they are recorded.

Bank

It is the bank to which the bank remittance is sent. The remittance is thus single-bank.

It is possible to reduce the selection of those payments to be placed on a remittance to one allocated bank.

The company, payment transaction and bank are the minimum criteria to regroup the open items on the same remittance.

Other criteria can limit the selection of the payments to be processed: the entry batch number, the user, the currency, an open item due date range and their amount.

Generation options of the bank remittances

Grouping/reference

This payment grouping based on a common reference is only used for payment transactions where the 'Remittance reference' field has been set up in entry mode (see Payment transactions documentation).

Remittance type

The 'Remittance type' field is forced to 'Cash receipt' if all the payment transactions selected and concerned by the bank remittances are checks (Printing code=CHE or CHR). The bank remittances are thus generated by check type with the deposit type assigned to 'Cash receipt'.

This field cannot be entered and is left empty if all the payment transactions selected and concerned by the bank remittances are set up with entry of the remittance type. The remittances are then generated by remittance type.

Except for these two particular cases, the field must be specified because the other payment transactions (set up without entry of the remittance type) are generated in common bank remittances, where the assigned remittance type is applied to the entered remittance type.

Block number 1

All companies (field ALLCPY)

To select the payments regardless of the related companies, check the "All companies" field.
To select the payments for company XXX, uncheck the "All companies" field and mention XXX in the "Company" field.

Company (field CPY)
Legislation (field LEG)
All sites (field ALLFCY)

To select the payments regardless of the related sites, check the "All sites" field.
To select the payments for site XXX, uncheck the "All sites" field and mention XXX in the "Site" field.

Site (field FCY)

Selection

All transactions (field ALLTYP)

To select the payments regardless of the related transaction, check the "All transactions" field.
To select the payments for transaction XXX, uncheck the "All transactions" field and mention XXX in the "transaction" field.

SEPA payment entry transactions are submitted to the following groupings when the checkbox All transactions is checked :

  • same order giver,
  • same account to be debited,
  • same currency (reminder: all payment transaction that can be submitted to SEPA must be in EUR),
  • same due date.
Transaction (field TYP)

To select the payments regardless of the related transaction, check the "All transactions" field.
To select the payments for transaction XXX, uncheck the "All transactions" field and mention XXX in the "transaction" field.

All entry batches (field ALLLOT)

To select the payments regardless of their related entry batch, check the "All entry batches" field.
To select the payments for the entry batch XXX, uncheck the "All entry batches" field and mention XXX in the "Entry batch" field. Caution, this filter on entry batches can only be applied to the "payments", which excludes payments on slips or paying banks.

Approved payments only (field PAYAPP)

This check box is selected by default. You can clear this check box to include nonapproved payments.

This check box is not available when authorization is not required.
Entry batch (field LOT)

To select the payments regardless of their related entry batch, check the "All entry batches" field.
To select the payments for the entry batch XXX, uncheck the "All entry batches" field and mention XXX in the "Entry batch" field. Caution, this filter on entry batches can only be applied to the "payments", which excludes payments on slips or paying banks.

All banks (field ALLBAN)

To select the payments regardless of the related bank or cash desk, check the "All banks" field.
To select the payments for bank or cash desk XXX, uncheck the "All banks" field and mention XXX in the "Bank" field.

Bank (field BAN)
All users (field ALLUSR)

To select the payments regardless of which user has carried out the last entry, check the "All users" field.
To select the payments whose last entry has been carried out by user XXX, uncheck the "All users" field and mention XXX in the "Users" field.
The user having completed the last entry for a payment is the author of the last modification of said payment or by default his creator.

User (field USR)
All currencies (field ALLCUR)

To select the payments regardless of the related currency, check the "All currencies" field.
To select the payments for a single currency XXX, uncheck the "All currencies" field and mention XXX in the "Currency" field.
To select the payments displaying a currency among the ones defined by the currency group YYY, uncheck the "All currencies" field and mention YYY in the "Currency group" field.

Currency (field CUR)
Currency group (field GRPCUR)
Items until (field DATECHMAX)

If a date is entered, only the payments where the due date is entered and is earlier or equal to the entry date will be taken into account for the generation of the remittance notes.
Minimum payment (field MINAMTPAY)

Only the payments where the amount is greater than or equal to the minimum amount entered and less than or equal to the maximum amount entered will be considered for the generation of the remittance notes.
field CURMINAMT
Maximum payment (field MAXAMTPAY)

Only the payments where the amount is greater than or equal to the minimum amount entered and less than or equal to the maximum amount entered will be considered for the generation of the remittance notes.
field CURMAXAMT1
Max. remittance amt. (field MAXAMTVCR)

Fore the payment transactions having a determined sense (Revenue or Expense), it is possible to indicate a maximum amount for the remittance notes generated. In this case, once this amount is reached, another remittance note is generated.

This amount must be greater than or equal to the maximum amount for the payment.
field CURMAXAMT2
Reference group (field REF)

If this field is ticked, for payment transactions having the Remittance reference field enterable, the remittance notes are created by grouping the payments on the same remittance reference.
Remittance site (field FRMFCY)

A remittance note is single company, but may be multi-site.
Indicate the site to be assigned to the remittance notes that are generated. If the payments for a single site are selected, the site for the remittance notes must be the same. If no site has been selected, the site for the receipt notes generated is that of the first payment.

Discount type (field FRMTYP)

For payment transaction associated with checks (i.e. those for which the Process zone of the printing code is CHR or CHE), the discount type is forced into Cash receipt (first choice of the local menu).
For payment transactions defined with the entry of Discount type (Cash receipt, discount and so on), the receipt notes are constituted via the grouping of payments that have the same discount type.
In the other cases, indicate the discount type to be assigned to the receipt notes generated.

Execution date (field EXEDAT)

Execution date for the transfer to be carried out on the notes.

Batch task

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

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation