Dedicated format transformation mappings > CFONB

CFONB add-on Map-Brokers

Available add-on Map-Brokers

The FEX Map-Brokers listed in the following table transform CFONB messages into SEPA messages.

Map-Broker name	CFONB input format	SEPA output format	Handling constraints
CFONB_160_VIRT_to_SEPACustBnkCrdtTrsfr	CFONB (160_VIRT)	Customer to Bank Credit Transfer (pain.001.001.03)	None
CFONB_320_VETR_to_SEPACustBnkCrdtTrsfr	CFONB (320_VETR)	Customer to Bank Credit Transfer (pain.001.001.03)	See CFONB (320_VETR) input information and constraints

Message handling information and constraints

General considerations

Error handling

During message handling in Integrator the rejection of a file could be global or partial. For example with a file containing multiple remittances, each remittance containing multiple operations:

In partial reject mode, only the correct remittances are transformed to SEPA format. The remittances in error (because of an incorrect header or footer, or because of an incorrect operation) are not transformed to SEPA.
In global reject mode, if one or more remittances are in error, all remittances (including the correct remittances) are rejected in error.

Transformation mapping functions

Initiating party identification: <GrpHdr><InitgPty><Nm>xxxxxxx</Nm></InitgPty></GrpHdr>.
This information can be initialized using a configuration variable.
Message ID to be supplied by the map conversion: <MsgId>xxxxxxx</MsgId>.
It is suggested that you use an ID syntax such as "FEXloggerId/FEXHostName/TCPCommandPort". The number of characters must be less than or equal to 35.
Payment information ID to be supplied by the map conversion if not present in the CFONB input file: <PmtInf><PmtInfId>xxxxxxx</PmtInfId></PmtInf>.
It is suggested that you use an ID syntax such as: "XIBloggerId/Remittancenumber/XIBHostName/TCPCommandPort". The number of characters must be less than or equal to 35.
Set the Category Purpose field (<PmtInf><CtgyPurp>xxxxxx</CtgyPurp></PmtInf> and <PmtInf><CdtTrfTxInf><Purp><CD>xxxxxx</CD></Purp></CdtTrfTxInf></PmtInf>), based on fields from the input file. For the moment, there are no rules which clearly define how to set this field (the values depends on input file properties).

CFONB (320_VETR) input information and constraints

Currency

All payment transactions must use the Euro currency.

If field 03/19 = 1 or 3, then field 03/16 must be "EUR"
If field 03/19 = 2 or 4 then ALL 04/25 fields must be "EUR"

Creditor account

The creditor account value is not mandatory. However, for CFONB to SEPA mapping, the creditor account field (04/5) has to be set in each payment transaction of an 320_VETR remittance. If not, the remittance must be rejected.

IBAN processing

For the debtor account field (03/11), IBAN and RIB are authorized (the 03/10 field gives information on the 03/11 field format: "1"=IBAN, "2"=RIB). Converting RIB to IBAN consists of adding "FR" plus the IBAN key.
For the creditor account field (04/5), BBAN national identifier and IBAN are allowed:
- If (04/4 = "1") then 04/5 is in IBAN format
- If (04/4 = "2") then 04/5 is in BBAN format
- If (04/4 = "0") then the remittance must be rejected
If the BBAN is provided:
- If 05/06 (BIC CODE) is present, it includes the country code. To convert the BBAN account number into IBAN, add the country code plus the IBAN key at the beginning of the BBAN.
- If 05/6 is not present, then field 05/7 (beneficiary bank country code) is mandatory. To convert from the BBAN account number to IBAN, add the country code plus the IBAN key at the beginning of the BBAN.

Adding a BIC

For the debtor account, either:
- The BIC code may be available in the 03/09 field
- If the 03/09 field does not contain a value, the BIC is deduced from the IBAN account debtor
For the creditor account
- The BIC code may be available in the 05/06 field
- If the 05/06 field does not contain a value, the BIC is deduced from the IBAN account creditor

Chargebearer account

For the chargebearer account fields (04/20, 04/21 and 04/22), the present release of the SEPA Map-Broker does not map the fields to pain001. If fields 04/20, 04/21 and 04/22 are present in the 320_VETR input file, they must be ignored.

Execution date handling

Attention: For the execution date for payment transactions, in 320_VETR, the execution date is provided at the payment transaction level, whereas in SEPA the execution date is provided at the remittance level. For Map-Broker handling, if the 320_VETR remittance is in multi-date format, the 320_VETR remittance will be split into multiple SEPA remittances.