The Credit Transfer/SEPA functionality is used in the A/P payment proposal routine in order to create payment orders for electronic transfer to financial institutions in the XML format outlined in the standard or local guidelines according to the following UNIFI ISO 20022 Payments Messages:
- CustomerCreditTransferInitiationV02 (Msg ID pain.001.001.02), which is found in the ISO MDR (Message Definition Report) 2006.
- CustomerCreditTransferInitiationV03 (Msg ID pain.001.001.03), which is found in the ISO MDR (Message Definition Report) 2009.
The CRETFR function control automatically activates the ISO MDR 2009. If you need the ISO MDR 2006 as well, then you also set the Character value (position 1) to Y in the Function control file. Otherwise, set the value to N.
See About Credit Transfer and SEPA for more information.
Basic data
The following outlines the complete setup procedure in the basic tables and files.
Tables/Files | To do | Additional information | Role | Preload in appl. |
---|---|---|---|---|
Work with function controls | Activate the CRETFR function control. This will automatically activate the ISO MDR 2009 (Msg ID pain.001.001.03).
If you need the ISO MDR 2006 (Msg ID pain.001.001.02) as well, then you also set the Character value (position 1) to Y. Otherwise, set the value to N. By activating the ISO MDR 2006 some of fields will be open for input. Otherwise, they are protected. |
Activation makes the panels for the Credit Transfer/SEPA functionality available. |
|
FIN |
Work with DI mapping definitions | Activate the DI mapping definition *ASWXML2/CRETFR/2. If you need the ISO MDR 2006, then activate *ASWXML2/CRETFR/1. |
The DI mapping definition *ASWXML2/CRETFR/1 and connected details is used to map the DC1 files for payment orders, created in the A/P payment proposal routine, to an XML file according to the ISO MDR 2006.
The DI mapping definition ASWXML2/CRETFR/2 and connected details is used to map the DC1 files for payment orders, created in the A/P payment proposal routine, to an XML file according to the ISO MDR 2009. Note: See more information in section Work with IFS communicator types below. |
|
GEN |
Work with DI methods | Activate ACCEFAX and/or ACCEMAIL to send a DI document by fax or e-mail. | Only applicable if the A/P remittance advice should be sent to a supplier by fax or e-mail. Note: See more information in section BP file maintenance/DI methods below. |
|
GEN |
Work with document output formats | Specify for program FLR455, A/P remittance advice, if portrait or Adobe format should be used. | The program FLR455 prints the A/P remittance advice for selected suppliers in the A/P payment proposal routine. |
|
FIN |
Work with currencies | Define the currency EUR for a SEPA payment. | Either set the currency code or the ISO currency code to EUR. |
|
|
Work with ISO 20022 external code lists | The preloaded elements are marked with an asterisk (*). Each element is connected to the applicable codes. All preloaded elements and codes are activated. Activation/Inactivation can be performed on both element and code level. Note: The elements *GRP and *PAYMTD must be active.
For preloaded codes and other codes, see the UNIFI ISO 20022 Payments Message documents (see above), or the ISO 20022 external code lists for the applicable element. |
|
FIN | |
Work with Credit Transfer schemes | Activate the applicable Credit Transfer scheme for your country.
Enter Credit Transfer data for the company. |
Credit Transfer schemes (CT) define the format of the transferred information.
The pre-defined scheme *STD creates the base standard XML scheme UNIFI ISO 20022 Payments Message CustomerCreditTransferInitiationV02 (Msg ID pain.001.001.02), which is found in the ISO MDR 2006. The pre-defined scheme *S09 creates the base standard XML scheme UNIFI ISO 20022 Payments Message CustomerCreditTransferInitiationV03 (Msg ID pain.001.001.03), which is found in the ISO MDR 2009. Whether the created XML scheme should be a CT (Credit Transfer) or an SCT (SEPA Credit Transfer) is defined by the A/P payment mode, Credit Transfer definition. Certain local Credit Transfer schemes are also preloaded to support local exceptions from the standard schemes above. Technical consultant info. To activate, e.g. the BE scheme for Msg ID pain.001.001.03, you select a Scheme ID and set the Scheme short name field to BE09. The scheme short name will be used as a suffix to the standard format program for the creation of payment order files. Example: First the system calls the standard format program, FLR440, and then calls the local format program, FLR440BE09, to update the local exceptions. When a new scheme short name is added into the table to be used in the A/P payment proposal routine, you might need to create a new local format program FLR440xxxx to execute the exceptions. The new program FLR440xxxx will automatically be called from the main format program, FLC440, which is retrieved from Work with A/P payment modes. SEPA Credit Transfer schemes (SCT) are used for SEPA payments. See About Credit Transfer and SEPA for more information. |
Initiating party, Debtor |
FIN |
Work with IFS communicator types | Enter an IFS communicator type to transfer a file from/to the IFS. | The IFS communicator type is used in different routines to connect to the Integrated File System (IFS). Define the Description, Folder name, File name, Company prefix and Backup. Set the Send field to YES. Other fields are not applicable.
For the A/P payment proposal routine you define the IFS communicator in Work with A/P payment modes below. If the A/P payment mode needs different IFS communicators, then you can override the IFS communicator in Work with transfer types. If the selected DI mapping definition *ASWXML2/CRETFR/1 or *ASWXML2/CRETFR/2 is active in Work with DI mapping definitions, then the DI tool maps the A/P payment orders for Credit Transfer to an XML file and then transfers the XML file to the IFS. |
|
|
Assign client via Work with DC1 user profiles | Activate the applicable client types (*FAX, *PHONE, MAIL) for the selected user profile and specify the fax number, phone number and/or e-mail address. | The contact person, the DC1 user, is responsible for the supplier’s account in the company.
You can define a contact person and specify if an A/P remittance advice should be printed on A/P payment mode level or on Business partner file/A/P payment mode level. The contact data is printed on the remittance advice. You can also define a contact person in Work with Credit Transfer schemes. That contact data is included in the XML file for Msg ID pain.001.001.03. If no contact person exists or contact data is missing, then the data is defaulted from Work with companies. |
|
|
Work with A/P payment modes | Define data for the payment modes CRETFR and SEPA. |
|
|
FIN |
Work with A/P payment modes, Credit Transfer data | Define data for the payment modes CRETFR and SEPA. | Some of the entered data can be overridden on supplier level in the Business partner file maintenance on the A/P payment modes panel or on document level.
Exception: If the Grouping code is GRPD, then the Credit Transfer data, Payment means, Payment type info, Charge bearer, Check instructions and Delivery method are retrieved from Work with A/P payment modes and not from supplier level or from the document level. The limit exists due to the Message block constructions in the standard XML schemes UNIFI ISO 20022 Payments Messages CustomerCreditTransferInitiationV02 (Msg ID pain.001.001.02) and CustomerCreditTransferInitiationV03 (Msg ID pain.001.001.03). |
|
FIN |
Work with A/P payment modes/Payment types | Define data for the payment modes CRETFR and SEPA. |
|
|
|
Work with banks | Enter Credit Transfer data for your bank. | Note: The Batch booking field must be set to YES or NO for the selected bank’s (banks’) payment mode(s) in Work with A/P payment proposal if the UNIFI ISO 20022 Payments Message CustomerCreditTransferInitiationV02 (Msg ID pain.001.001.02) is used.
Note 2: For Sweden, application SE active, and sending the UNIFI ISO 20022 Payments Message CustomerCreditTransferInitiationV02 (Msg ID pain.001.001.03) to NORDEA or SEB. Sending the file to NORDEA requires Bank group NOR. Sending the file to SEB requires Bank group SEB. |
Debtor’s agent |
|
Work with template controls |
|
The template number 27 (Credit Transfer) displays the BP file maintenance/Credit Transfer data panel. |
|
GEN |
Work with business partner templates | Include the Credit Transfer panel in the applicable templates used in the Business partner file. |
|
|
|
Work with business partners
(Business partner file) |
|
|
Creditor, Ultimate creditor, Creditor’s agent |
|
Work with DI documents | Only applicable if the CDM handling will be used.
Select DI document BPARTNER connected to the subtype 1 and activate the files SRONAMCT SROSUKCT, SROLPCCT. Select DI document TABLE connected to the subtype 1 and activate the files SROELMCT and SROECDCT. |
Start from Work with DI documents.
Select BPARTNER and/or TABLE and drill down to Work with DI document subtypes. Select subtype 1 and drill down to Work with DI document subtype files. |
|
CDM |