Setup >  A/P-A/R accounting >  Files >  Bank file definitions  

Display all Hide all

This table describes the created bank file formats:

  • targeting banks,
  • by the banks or the factors, and to be integrated into the software.

The format (either fixed or variable) can be customized for each bank, but it must be modified with caution. In particular, it can be interesting to modify these formats when some banks demand specific information and/or a different order in the transmitted data. As a matter of fact, a bank file is defined by a code that identifies it (this code is the one which is specified by the payment transactions setup), and by an optional bank code.

When an interface bank file is created for a particular bank, the system checks if there is a setup for the correct code and the corresponding bank. If there is none, the default setup defined for the empty bank code is used.

As the standard, the following formats are available to manage standard payment modes, in conformity with the French Committee for Banking Organization and Standards (CFONB). The formats are all delivered with an empty bank code, but it is possible to copy these records by specifying a particular bank code, and even to create new formats with other codes).

Code

Title

LCR (electronic bill of exchange)

LCR deposit

PRELEVE

BP debit

VIREMENT

Bank transfer

VIRINTER

International bank transfer

The following formats are also available in standard for managing bank files not related to bank payments, to be integrated or extracted:

Code

Title

RELBAN

Bank statement to be integrated

RELLCRBOR

Paying bank files of the bank to integrate

REPLCRBOR

Answer to the LCR or BOR statement (to be extracted)

QUITTANCE

Factoring receipt for the factor

 

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

For each file format, the file design of the various records that compose it is defined.
It usually includes header, detail, sub-total and total records, but there are also some specific cases:

  • For those files defining the factoring receipts: two additional levels exist (called sub-total and detail 2).
  • In the case of bank statements: an additional level is provided.
  • In some case (i.e. international transfers): there can be two detail levels (identified by an order number that will be equal to 1, then 2, this information remaining set to 0 in the other cases).

Close

 

Fields

The following fields are present on this tab :

Block number 1

  • Bank file (field COD)

No help linked to this field.

This field is optional. It is used to customize the structure of a file for a given bank. The record with the empty bank field will be used for banks with no specific record.

Non-compulsory field containing the legislation code (miscellaneous table 909).

The entered value is used upon creation and validation of the folder and upon addition of data during legislation copy.

The data concerning the requested legislations and the common data (legislation code empty) on folder creation.

Only the records concerning the folder legislations are retrieved on folder validation.

The Legislation field is also used as a filter and checked upon movement selection and entry (entry of invoices, payments, journals etc.).

If the field is empty, the current record can be used whatever the legislation of the company concerned by the movement.
  • Record type (field RECTYP)

No help linked to this field.

  • Detail order number (field ORDNUM)

This order number is used to break down and sort the 'Detail' type records.

Block number 5

  • Description (field DESTRA)

 
  • Short description (field SHOTRA)

 
  • Format type (field FMT)

The format of the bank file can be of the Fixed or Variable type.

Fixed

This format is used to exchange fixed-format files with the bank, such as bank statements and bills of exchange.

When you select the type Fixed, a data file is generated (the data correspond to to the results of the formula entered in the field Formula).The position and length of data are set in this file.

Variable

This format is used to exchange XML files with the bank, such as SEPA and non SEPA transfers and direct debit.

When you select the type Variable, a data file is generated (the data correspond to to the results of the formula entered in the field Formula). These data are surrounded by tags, entered in the fields Start separator and End separator. Selecting this format type leads to displaying the Mandatory and Condition columns required in the setup.

For bank files subject to the SEPA standard (Variable type and bank file group SCT 'SEPA bank transfer' or SDD 'SEPA direct debit'), only the following characters are authorized:
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
- ? : (  ) . , "  and / (only inside a zone)
Space character
A control on characters is performed when generating the file.
- If a prohibited character is included in a chain of characters, it will be automatically replaced by a blank space.
- If a prohibited character is placed at the start or end of a chain, it is automatically deleted.
For example :
          <Nm>/COMPANY FATHER&SONS/</Nm>
After a new processing in Sage X3:
          <Nm>COMPANY FATHER SONS</Nm> (deletion of start and end '/' characters in the tag and '&' character replaced by a blank space).

The Length, Formula and Title columns are common to both format types.
  • File prefix (field FILREF)

This sequence will be used as a prefix in the names of the files generated by this descriptor.
  • File extension (field FILEXO)

Enter the extension of the file names that will be generated for the magnetic transfers. They can contain up to four characters.

  • Condition (field FORCND)

This field is used to enter a formula conditioning the entry of the current record.

This field is specified at detail order no. level.

Grid Records

  • No. (field NUM)

Invoice number.
This number is used to identify the invoice in a unique way. It is entered upon each creation or automatically generated depending on the counter associated with the invoice type.
  • Field type (field FLDTYP)

No help linked to this field.

  • Position (field POS)

 
  • Length (field LNG)

No help linked to this field.

  • Start separator (field STRSEP)

Enter the start separator. A control is performed between the start and end tags to make sure that the tags are consistent with each other.

You can add a value inside an attribute in the XML tag:

  • In the tag, use the code $1$ as a value.
  • In the XML file, this code $1$ is then replaced by the result of the formula entered in the field Formula.

For example:

  • The start separator is <InstdAmt Ccy="$1$">.
  • The formula in the field Formula is [F:PYH]CUR.
  • In the generated XML file, $1$ is then replaced by the currency. For instance: <InstdAmt Ccy= "EUR">1000</InstdAmt>


If the start separator contains the code $1$, the first occurrence of $1$ is replaced by the result of the evaluated formula (the other occurrences of $1$ are not modified).

If the start separator does not contain that $1$ code, the result of the formula is displayed in the XML file after the tag.
  • Formula (field FRM)

For bank files whose format is of the 'Variable' type, specify the variables used for the XML file.

Examples:

[L]MSGID : this variable contains the value of the sequence number used. This sequence number is defined in the function Sequence number assignment.

[L]NBPYH : this variable contains the number of payments included in the file.

[L]TOTCUR : this variable contains the sum of all the payments included in the file, without taking currencies into account, that is to say, without conversions.
  • Mandatory (field OBY)

This column is displayed only for formats of the 'Variable' type.

It can be entered when the Formula column contains a value.

If the values are mandatory and if the conditions are not fulfilled (in the field Condition) on generating the XML bank file, the bank file is generated but an error is displayed in the log file for information purposes.

  • End separator (field ENDSEP)

Enter the start separator. A control is performed between the start and end tags to make sure that the tags are consistent with each other. For example, the following warning message can be displayed in case of an error: "The end separator should be </XX>. Do you want to modify it? ".
  • Condition (field CND)

This field is used to enter a formula conditioning the entry of the current record.

The XML management rules require that the start and end tags are not generated if there is no value between the two tags.

In the event of XML element groups with optional values, this field, if it is not populated, prevents the creation of the record.

Entering a condition is not necessary for the tags with optional values (when the field Mandatory is set to 'No') if these tags are not directly included in an XML element group.

 
  • Description (field DESLIN)

No help linked to this field.

Generation

  • Total length (field TOTLNG)

 

Block number 4

  • Multicurrency (field CURMULT)

This flag is used to check that the remittance file is in a single currency when the multi-currency mode is forbidden by the file format.
  • Bank file group (field NATPAY)

The nature of the payment makes it possible to associate the bank file with a payment transaction. Several file formats can correspond to the same payment nature: according to the bank institution or the national/international character of the payment, the file format is different.

Currency

  • Currency control (field CURCTL)

 

Table number 2

 

Close

 

Specific Buttons

The following fields are included on the window opened through this button :

Block number 1

  • field OBJET

 
  • field CLES

 

Block number 2

  • From folder (field DOSORG)

Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.
  • All folders (field TOUDOS)

Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).
  • To folder (field DOSDES)

Use this field to define the folder to which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

Close

This button is used to copy the record definition from or to another folder.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Incorrect expression (followed by an additional message)

The syntax of the entered calculation formula is not correct (for example: "A closing bracket is missing.").

Tables used

SEEREFERTTO Refer to documentation Implementation