Belgian bank statement

• Statement no. (field RBKNUM)

Belgian bank statement number, generated automatically during the creation or import of the CODA file.
For this statement number to be generated automatically, the BERBK counter must be set up and assigned.

• Bank (field BAN)

Bank of the Belgian bank statement.
In Import, the bank is determined automatically based on the Bank ID number or IBAN code, defined in the CODA file.

• Sequence (field EXTNUM)

• Date created (field CREDAT)

Date at which the Belgian bank statement has been entered or imported.

• Company (field CPY)

Company of the bank entered or determined based on the bank ID number or IBAN code, transmitted to the CODA file on recording 1.

• Currency (field CUR)

Currency of the bank entered or determined based on the bank ID number or IBAN code, transmitted to the CODA file on recording 1.

• Site (field FCY)

Site determined based on the site set up for the bank.
Otherwise: main site of the company set up for the bank.

• Calculated balance (field WNEWAMT)

• File format (field FILTYP)

Field that cannot be entered, determined according to the creation mode of the CODA statement.

• If the statement is entered, the format is "Manual".
• If the statement is imported, the format is "CODA".

• File name (field FILNAM)

Field loaded only in import, corresponding to the file name of the imported CODA statement.

• Date (field OLDDAT)

Corresponds to the date of the old balance of the Belgian bank statement.

• This field can be entered when no previous statement exists for the Bank/Financial site pair.
• If a previous balance exists, this field cannot be entered and is loaded automatically based on the date of the new balance of the previous statement.

• Amount (field OLDAMT)

Corresponds to the amount of the old balance of the Belgian bank statement.

• This field can be entered when no previous statement exists for the Bank/Financial site pair.
• If a previous balance exists, this field cannot be entered and is loaded automatically based on the amount of the new balance of the previous statement.

• Sign (field OLDSNS)

Corresponds to the sign of the old balance of the Belgian bank statement.

• This field can be entered when no previous statement exists for the Bank/Financial site pair.
• If a previous balance exists, this field cannot be entered and is loaded automatically based on the sign of the new balance of the previous statement.

• Date (field NEWDAT)

Corresponds to the date of the new balance of the Belgian bank statement.
The date of the new balance is controlled and cannot be prior to the date of the old balance.

• Amount (field NEWAMT)

Corresponds to the amount of the new balance of the Belgian bank statement.

• Sign (field NEWSNS)

Corresponds to the sign of the new balance of the Belgian bank statement.

• Debit (field AMTDEB)

Corresponds to the total of the debt movements of the Belgian bank statement (i.e. the total of lines with the "Revenue" sign).

• Credit (field AMTCDT)

Corresponds to the total of credit movements of the Belgian bank statement (i.e. the total of lines with the "Expense" sign).

• To validate (field VALFLG)

Field that can be accessed f the line status is "to validate".
To mass validate the statement, use right-click / Column upd.

• Site (field FCYLIN)

Management in Entry/Import

• In Entry, the site of the line is, by default, self-loaded by the site in the statement header.
• In Import, if no remittance is assigned, the rule applied is the same as in Entry.
• In Import, if a remittance slip is assigned, the site corresponds to the site of this slip, and cannot be modified.
• The site can no longer be modified once the statement line has been validated or a remittance slip is assigned in table 1, in the current statement line.
  

• Slip no. (field FRMNUM)

Management in Entry

This field can be entered manually or loaded by picking, provided the site is entered and the following conditions are met:

• The line must not be validated.
• The account field must be blank.
• The BP field must be blank.
• The BELRBK - Belgian Bank Statement parameter value must be set to "Yes" for the company of the statement.

Control in Entry

• Only slips with the same company as the one of the statement can be entered.
• Only slips for which the intermediate posting has been performed can be entered.
• If the bank posting has already been performed for the slip, this slip cannot be entered.
• Only slips that have not been allocated to another statement line can be entered.

A tunnel provides direct access to the Remittances function.

Management in Import

For the remittance to be automatically assigned in import, the sequence number of Belgian payments must not exceed 13 characters so that the internal reference can be interpreted. (this field being broken down into 2 blocks of 13 characters in the CODA file).
The slip number will be assigned once an internal reference has been transmitted to the CODA statement and controls are valid (i.e. controls in entry).
As soon as a slip is assigned to the current line of table 1 in the statement, the "Amount" and "Internal reference" fields of table 2 are loaded with respect to the amounts and references of the payments associated with the remittance slip.

• BP (field BPRNUM)

Management in Entry

Field that can be entered and modified by the user, provided that:

• the current statement line has not been validated,
• there is no account defined on the current statement line of table 1,
• no open item has been allocated in table 2.
• no remittance slip is loaded in the current statement line of table 1.

Management in Import

• The BP is determined based on the bank ID number or IBAN code, transmitted to the CODA file on recording 23.
• If several BPs share the same bank ID number / IBAN code, the BP field is not loaded.

• Company name (field BPRNAM)

Corresponds to the BP company name, when this BP is defined.

• Accounting date (field ACCDAT)

Field defining the accounting date that will be used during the payment or remittance posting.
When the statement line of table 1 has not been completely entered and an open item or slip is entered by picking, the accounting date is loaded by default by the date of the current day.

• Value date (field VALDAT)

Field defining the value date that will be used during the payment or remittance posting.
The date is loaded by default by the accounting date.

• Sign (field SNS)

Management in Entry

Field specifying the movement sign.
This field can take three different values:

• Revenue (affects the debtor balance of the statement),
• Expense (affects the creditor balance of the statement),
• Unspecified (in this case, the debtor/creditor balances of the statement are not affected).

If a remittance slip is defined, the field cannot be entered and the sign corresponds to the sign of the payment transaction associated with the slip.
If no remittance slip is defined, the sign determines the sign of the payment transaction which will be used to generate the payment.

Management in Import

If the sign of recording 21 in the CODA statement is equal to 0, the movement sign is creditor.  
The sign of the statement line takes the value "Expense".

If the sign of recording 21 in the CODA statement is equal to 1, the movement sign is debtor.
The sign of the statement line is thus "Revenue".

• Amount (field AMTCUR)

Management in Entry

• If a remittance is defined, the field cannot be entered and corresponds to the total amount of the slip.
• If no remittance is defined, the amount can be entered and corresponds to the total amount of the payment to be generated.
• The amount is in bank currency.

Management in Import

Field specifying the movement amount

• If the import of Belgian bank statements has been performed with the "Import of detail lines" flag unchecked, the amount will correspond to the global amount of the current recording 21.
• If the import of Belgian bank statements has been performed with the "Import of detail lines" flag checked, the amounts will correspond to the total of lines contained in the current recording 21.
  The total of all lines of table 2 is always equal to the amount of the current statement line of table 1.

• Bank account (field ACCBAN)

Bank account defined based on the bank journal setup for the bank.

• Account (field ACCTMP)

When an account is defined, the generated Debtor/Creditor payment is of the 'charge' type.
This field is used to enter the charge or product account for the payment of charges.

This field can be entered and modified if:

• the current statement line has not been validated,
• no open item or remittance has been assigned to the current statement line,
• no BP has been entered in the current statement line.
  

• Payment transaction (field PAYTYP)

If a remittance is defined, the field cannot be entered and corresponds to the payment transaction linked to the note.
If no remittance is defined, the payment transaction defined will be used during the payment generation. By default, the loaded transaction is the one set up the parameter value BELTRSDEF - Payment transaction.

Control in entry

The controls performed are the same as those applied to the parameter value BELTRSDEF - Payment transaction.

• Payment no. (field PYHNUM)

Corresponds to the payment number generated when no remittance has been assigned to the validated bank statement line.

• Status (field STATUT)

This field is calculated and can take the following values:

• "suspended": not all fields required for the validation of a statement line are entered,
• "to validate": the statement line can be validated.

   Condition so that the status is "To validate": case of a payment

• The site set in the payment line must not be blank.
• The payment transaction must not be blank.
• The accounting destination must not be blank.
• The amount must not be equal to 0.
• The accounting date must not be blank.
• The total of the amounts of table 2 lines must correspond to the amount of the statement line linked to table 1.
• No remittance is entered on the current line.
• The sign is not unspecified.

   Conditions so that the status is "To validate": case of a remittance

• The site set in the payment line must not be blank.
• The slip number must be entered.
  
  
• "validated": the statement line has been validated. This will result in either the bank validation of a remittance, or the generation and posting of a payment.

• Destination (field DENCOD)

Management in Entry

This field can be entered if:

• non remittance slip is loaded in the current statement line of table 1,
• the statement line has not been validated.
  
  The accounting destination is defined by default according to the sign of the statement line of table 1.
• If the sign is "Expenses", the accounting destination loaded by default is the one defined in the parameter value:
  DENSPG-Accounting destination Expense.
  
• If the sign is "Revenue", the accounting destination loaded by default is the one defined in the parameter value:
  DENTAK-Accounting destination Revenue.

Management in Import

• If the import of Belgian bank statements is performed with the field "Import of detail lines" unchecked: Global Mode.

• Regardless of the allocation type of the section defined in recording 21 the accounting destination is defined according to the movement sign.
  
• If the movement sign is credit, then the accounting destination is taken from the parameter value:
  DENSPG-Accounting destination Expense
• If the movement sign is debit, then the accounting destination is taken from the parameter value:
  DENTAK-Accounting destination Revenue
• Regardless of the allocation type of the CODA section, defined in recording 21, the account field of the detail line is always blank.
  
  
• If the import of Belgian bank statements is performed with the field "Import of detail lines" checked: Detail Mode.
  
  
• If recording 21 only contains a detail number with the same sequence number, then the accounting destination is defined in the exact same way as the "import in global mode" and the account field of the detail line is blank.
• If recording 21 contains several detail numbers with the same sequence number, then the accounting destination and the account are loaded as follows:
   
• If the CODA section defined in recording 21 is set up in the setup function of CODA sections, and the allocation type is "1- None", then the accounting destination is defined according to the payment sign (via the DENSPG / DENTAK parameter values) and the account field of the detail line is blank.
• If the CODA section defined in recording 21 is set up in the setup function of CODA sections, and the allocation type is "2- Account", then the accounting destination is defined according to the BELDENDEF - Accounting destination parameter value by default, and the account is taken from the one set up in the CODA section.
• If the section defined in recording 21 is not set up in X3, the default section defined in the BELRUBDEF - Default section parameter value is taken instead.

• Account (field ACC)

In entry

The account field can be entered, depending on the setup of the accounting destination.

In import

The account field is self-loaded depending on the accounting destination and on the CODA section.

• Type (field VCRTYP)

Management in Entry

Corresponds to the entry type of the open item selected by picking or manual entry.
When an account is defined in table 1, this field cannot be entered.

Management in Import

Corresponds to the entry type of the open item found automatically using the VCS number, when the communication type of record 21 is 101.

• Entry (field VCRNUM)

Management in Entry

Corresponds to the entry number of the open item selected by picking or manual entry.
When an account is defined in table 1, this field cannot be entered.

Management in Import

Corresponds to the entry number of the open item (Sales Invoice / Customer BP invoice) found automatically using the VCS number, when the communication type of record 21 is 101.

• Amount (field AMTLIN)

Management in Entry

• Field loaded automatically by the amount entered in table 1 in the statement line.
• If an open item is entered or selected by picking, the self-loaded amount is replaced by the available balance of the open item.

If a remittance slip is assigned in table 1, in the current statement line, the amounts of each table 2 lines will match the amounts of each payments of the remittance respectively. In this case, the amount cannot be modified.

Management in Import

• If the import of Belgian bank statements is performed with the field "Import of detail lines" unchecked: Global Mode.
• The amount corresponds to the global amount of the current recording 21. It is equal to the amount of the current statement line in table 1.
  
  
• If the import of Belgian bank statements is performed with the field "Import of detail lines" checked: Detail Mode.
  
  
• The amounts of each table 2 line will match each detail line of the CODA file current movement.
• The total of the amounts of table 2 lines, is equal to the amount of the current statement line of table 1.
• The amounts can either correspond to the amount of payments associated with the assigned remittance, or to the amounts of open items recovered using the VCS number, or else to a simple amount (no open item linked).
  

Case of currency open items

• When the open item is in a currency different from the bank currency, the amount in open item currency is converted into bank currency.
• If the bank currency is equal to the main ledger currency.
  
  
• If the payment transaction is set to "Without invoice rate application", the open item amount is converted into the accounting date of the current statement line.
• If the payment transaction is set "With invoice rate application", the open item amount is converted into the accounting date of the invoice.
  
  
• If the bank currency different from the main ledger currency, the open item amount is always converted into accounting date of the current statement line and the invoice rate application is not applied, regardless of the type of setup used for the payment transaction.
  Note: in this case, if the reverse rate is applied, the open item will not necessarily be closed in transaction currency.

• VAT code (field VATLIN)

This field can be entered if the accounting destination and account assigned to the accounting destination are subject to VAT.
The VAT code is loaded by default by the code set up on the account.

• Internal reference (field REFINT)

Management in Entry

When a remittance slip is entered, the field contains the payment number associated with the slip.

Management in Import

When the internal reference is loaded in the CODA file in recording 22, the field is used to automatically determine the slip number with payment references corresponding to the number of the transmitted internal references.

Note: the internal reference is composed of two blocks of 13 positions: therefore, the sequence numbers of Belgian payments must not exceed 13 digits.

• VCS number (field BELVCS)

Field loaded only in import.
It contains the transfer number with structured communication.
When this field is entered, the program automatically assigns the sales or customer BP invoice, linked to the same VCS number, provided this invoice has not already been closed.
The VCS number is transferred when the communication type of recording 21 is 101.

• Account no. (field BIDNUM)

Field loaded only in import.
It corresponds to the bank account number or IBAN code of the BP.
It makes it possible to automatically assign the BP field, provided that multiple BPs are not set up with the same Bank account number or IBAN code.

• BIC code (field BICCOD)

Field loaded only in import.
It corresponds to the BIC code of the BP.

• Counterpart name (field OFFACCNAM)

• Sequence number (field NUMSEQ)

Field composed of 8 digits loaded only in Import.

• The first 4 digits correspond to the sequence number of the permanent recording.
  The sequence number starts with 0001 and is increased by 1 for each "movement" product related to another movement of the statement.
• The last 4 digits correspond to the detail number.
  The detail number starts with 0000 and is increased by 1 for each "movement" product with the same permanent sequence number.
  

• Type (field TYP)

The type characterizes the communicated amount (total, sub-total, details).

• Operation code (field CODOP)

Field loaded only in import.
Each operation is assigned a unique code in the CODA statement. This coding always contains 8 positions.

• 1st = type.
• 2nd and 3rd = group: specifies the category the operation belongs to.
  For example: transfer, card, paying bank...
• 4th and 5th = operation: identifies the operation of a group.
  For each group code, a series of operation codes are linked to debit and credit movements.
• 6th + 7th + 8th = section.

The type and section are displayed in their respective fields, this field therefore displays the group + operation.

Examples of Groups:

Example of Groups / Operations:
 Example: Group 01 - Local/International transfers - SEPA Credit Transfer - Debit Operation

 Example: Group 01 - Local/International transfers - SEPA Credit Transfer - Credit Operation

To obtain the complete list of group codes by operation, refer to the documentation on CODA of the Febelfin website:

• In French: http://febelfin.be/sites/default/files/Payments/Standard-CODA-23-FR.pdf
• In English:  http://febelfin.be/sites/default/files/Payments/Standard-CODA-23-EN.pdf

• Heading (field RUB)

Field loaded only in Import.
The "heading" provides the details of commission charges or discounts.

The section affects the determination of the accounting destination and of the account allocated to this destination.

For further information, refer to the documentation help of CODA sections.

• Communication type (field TYPCOM)

Field loaded only in import.

In the CODA file, communications can be displayed.
When the communication is structured, a code of 3 positions indicates the type of communication followed by the communication.

For further information, refer to the documentation help of Communication types.

When the communication is entered, it is possible to view the communication detail by right-clicking / structured communication view.

• Recipient name (field DESTNAM)

Field loaded only in import.

• Bank BIC code (field BICCODBAN)

Field loaded only in import.
It corresponds to the BIC code of the bank.

• Account no. (field BIDNUMBAN)

Field loaded only in import.
Bank account number or IBAN code of the bank.

• Identification no. (field IDENTNUM)

Field loaded only in Import.
Identification number of the account holder settled in Belgium.

• Holder name (field ACCNAM)

Field loaded only in import
Name of the account holder

• Account description (field ACCDES)

Field loaded only in import.

• field WFRETXT

Field loaded only in import.
Additional information transferred to record 4 of the CODA file.