Vendor electronic payments – Credit transfer overview (EU)
This article provides general information about ISO 20022 credit transfers, which include Single Euro Payments Area (SEPA) credit transfers and any other electronic payments for vendors. A SEPA credit transfer is a specific type of payment in euros from one company or individual to another company or individual. The topic also explains how to set up and transmit a credit transfer payment file.
Table of Contents
- What is a credit transfer message?
- What are ISO 20022 and SEPA payments?
- What is a SEPA credit transfer?
- How is a credit transfer implemented?
- What credit transfer formats are currently supported in Dynamics 365 for Operations?
- What do I have to set up?
- What parameters are available for generating credit transfer payments?
- What are IBANs and BICs?
- How do I transmit a payment file to the bank?
The credit transfer message is a request that an initiating party (your company) sends to move funds from its own account to a creditor.
There are many country/region-specific and bank-specific implementations of credit transfer messages. Some of them are used within one country/region, and some are becoming standards. One well-established global standard is ISO 20022 and its initiation messages, such as Credit transfer. The following illustration shows the relations and coverage for selected credit transfer messages.
This topic describes how Microsoft Dynamics 365 for Operations implements credit transfers that are based on ISO 20022 credit transfers.
The Single Euro Payments Area (SEPA) is set up by the European Commission and dictates that all electronic payments are considered domestic, regardless of the country/region where the individual, business, or organization, and the bank are located. There is no difference between national payments and cross-border payments. The SEPA includes the 28 member states of the European Union (EU), and also Iceland, Liechtenstein, Norway, Switzerland, Monaco, and San Marino. The SEPA helps form a single market for payment transactions within the European Economic Area (EEA). Ultimately, the SEPA is expected to reduce the number of payment formats that banks, businesses, and individuals must work with.
The European Commission established the legal foundation for SEPA payments through the Payment Services Directive (PSD). The European Payments Council (EPC) supports the SEPA through the following activities:
- It sets the standards for SEPA electronic payments by using the ISO 20022 Universal financial industry message scheme XML format.
- It establishes rules and guidelines about the handling of euro payments.
The EPC, which consists of European banks, develops the commercial and technical frameworks for SEPA payment instruments. Three types of SEPA payments are used:
- Credit transfers
- Direct debits
A SEPA credit transfer is a payment from one company or individual to another company or individual.
Payments must be in euros, and must include the International Bank Account Number (IBAN) and the Bank Identifier Code (BIC) for both parties. (The BIC is also known as the Society for Worldwide Interbank Financial Telecommunication [SWIFT] code.) Additionally, transaction costs must be shared between both parties.
Credit transfers that occur between parties should use XML files that comply with ISO 20022 payment processing standards and the XML format, as specified by the EPC.
The credit transfer payment format for European countries is implemented by using the Electronic reporting (ER) and Methods of payment functionality in Dynamics 365 for Operations. A few credit transfer formats that are used in other regions still use the legacy payment framework. Among many other formats, there are twelve ISO 20022 credit transfer file formats that are available. These export formats conform to the SEPA ISO 20022 XML standard. They are used to generate non-euro payment transfers for countries/regions where they are used and euro payments as specified in version 8.2 of the SEPA Credit Transfer Scheme Rulebook that the EPC releases.
Before you can implement credit transfers, you must contact your bank to obtain the software that is required in order to upload electronic banking files. You will use that software to transfer the XML files that contain payment orders to your bank.
You should always go to the Shared asset library on Microsoft Dynamics Lifecycle services (LCS) and view the most up-to-date list of available files that have an asset type of GER configuration. The next section, “What do I have to set up?”, provides a link to the topic that explains how to create an LCS repository to review available configurations and import selected configurations.
- Before you can create credit transfer files, at least one active credit transfer configuration must be imported into your ER configurations. For instructions, see Download Electronic reporting configurations from Lifecycle Services.
- When you configure Accounts payable methods of payment, select the Generic electronic reporting check box, and select the appropriate credit transfer format (for example, ISO 20022 Credit transfer (AT)) as an export format configuration.
- You must also set up the legal entity and bank account information in Dynamics 365 for Operations.
- Bank account numbers, IBANs, and sometimes SWIFT codes (BICs) or other IDs are required in order to create valid credit transfer payments. Therefore, you must set up them for the vendor bank account and the bank account for the organization that is requesting the transfer.
- Additional information might be required, such as value-added tax (VAT) numbers for the parties that are referred to in the credit transfer message. This information must be set up for vendors and for the legal entity when it’s requested.
- Some Accounts payable methods of payment, mostly ISO 20022–based methods of payment, might require additional setup for Payment format code sets, such as Service type = SLEV. Those codes are used as additional tagging for payment transactions during payment processing. Default values of Payment codes, like Category purpose, Charge bearer, Local instrument and Service level can be set in two places. The first place is Accounts payable payment journal header and the second is Accounts payable methods for payments. Upon payment journal lines creation, Payment code values set on payment journal header are transferred to a journal line, if not set, the values from Methods of payment are used.
The list of specific parameters depends on the credit transfer format. The following table shows the parameters that are available when you generate a ISO 20022 credit transfer payment file for Germany in a vendor payment journal. By using the options that are available on the Run in the background tab, you can run payment generation in batch mode.
|Batch booking||Select this check box to include the batch booking tag in the XML file.|
|Processing date||Enter the date when the bank should process the payments.|
|Format||Select the format for remittance information, depending on the requirements of your country/region or bank:
|Number of invoices||Enter the number of invoices that the Payment advice report is printed from.|
|Sequence number||Enter a sequence number to identify the file. The sequence number appears on the Attending note report.|
|Print attending note||Select this check box to print the Attending note report.|
|Print control report||Select this check box to print a report that contains the payment information.|
|Print covering letter||Select this check box to print the Payment advice report.|
The International Bank Account Number (IBAN) and Bank Identifier Code (BIC) are used to identify any account in many countries/regions worldwide. These include the 34 SEPA countries/regions. Enter the BIC in the SWIFT code field and the IBAN in the IBAN field. For both the creditor’s bank account and the customer’s bank account, these fields are located on the Additional identification FastTab on the Bank account tab of the Bank accounts page. The use of BIC for SEPA payments is no longer enforced.
When you generate payments, the payment file is generated, and you’re asked to save it from your web browser to any available location. The next step is to send the XML file to your bank. This process varies from bank to bank. Follow the instructions from your bank to submit the files to the bank for processing.