When you import SEPA payments via MT940 format, IBAN and BIC will be transferred to the transaction details of the payment.
When SEPA payments are matched to an order or an invoice, the BIC and IBAN will be transferred to the order/invoice details in pixi* Customer Service. pixi* supports import of IBAN and BIC from the following positions in the SEPA payment file: ?30, ?31, ?20, ?21, ?22+?23. The following combinations are possible:
?30?31 – Example: ?30ABCD1234?31DE123456789000000000
?20?21 – Example: ?20ABCD1234?21DE123456789000000000
-
If „BIC“/„BIC:“ or „IBAN“/“IBAN:“ is written in the file, pixi* also recognizes the following combinations:
?21IBAN DE123456789000000000?22BIC ABCD1234?23(leer)
?21BIC: ABCD1234?22(leer)?23IBAN: DE123456789000000000
?30IBAN: DE123456789000000000?31BIC: ABCD1234
To improve compatibility with changes for SEPA 2014, import of payment data has been enhanced for LOU Update 19 and ELI Update 11. SEPA allows one unstructured reference of 140 characters (SVWZ - SEPA-Verwendungszweck). In MT940, each field can have max. 27 characters - this means that the 140 characters of the SEPA reference need to be distributed to the MT940 fields. Based on the keyword ‘SVWZ’ which refers to the reference text of a payment, all necessary fields from the MT940 bank file that contain the reference text are imported to ‘Text data – 01’ in Transaction properties > General tab.
When using MT940 files to import SEPA payments, the reference fields (?20-29) are used for information that is specific for SEPA format:
MREF - Mandate reference (Mandatsreferenz)
EREF - End-to-end reference (Ende-zu-Ende-Referenz)
KREF - customer reference (Kundenreferenz)
CRED - creditor ID or DEBT - Debitor ID
SVWZ - SEPA unstructured reference (max. 140 characters) (SEPA-Verwendungszweck)
ABWA - Different payment initiator (Abweichender Auftraggeber)
ABWE - Different payment receiver (Abweichender Empfänger)
Transaction signature (PIXIX…) which is transferred within the SEPA XML for direct debits in the end-to-end reference (EREF) to the bank, is imported from bank file (MT940 format) to field ‘Text data – 02’ in transaction properties > General tab. This assures proper automatic matching and moving SEPA/DTAUS records from “Sent to Bank” to “Completed” folder.
If keywords SVWZ or EREF are not included, everything stays as it is - we import fields:
text1 = field ?20
text2 = field ?21
-
text3 = fields ?22+?23
Note: From pixi* LOU Update 30 and AVA Update 6 ‘Text data – 03’ contains the complete text from fields ?20 to ?29 to assure that all information from the payment file is available for payment matching.
bank code/BIC = field ?30
account nr/IBAN = field ?31
customer name = fields ?32+?33