SEPA Credit Transfer Customer-to-Bank/User Documentation
Contents |
About this document
This document describes how to install, configure and use the SEPA Credit Transfer Customer-to-Bank module for Openbravo.
About SEPA Credit Transfer
SEPA Credit Transfer is an European Credit Transfer system for payments in EUR. It is the official credit schema since February 2014.
The SEPA Credit Transfer (SCT) Scheme enables payment service providers (PSPs) to offer a core and basic credit transfer service throughout SEPA for either single or bulk payments. The scheme's standards facilitate payment initiation, processing and reconciliation, based on straight-through-processing (STP). The scope is limited to payments made in euro, within the 33 SEPA countries. The PSPs executing the credit transfer must formally participate in the SCT Scheme.
About SEPA Credit Transfer implementation for Openbravo
The SEPA Credit Transfer implementation for Openbravo is distributed as a commercial module that can be directly installed by the user through the Module Management window.
This modules is based on the Remittances infrastructure for Openbravo. It is highly recommend to read its Configuration Manual and the User Documentation before working with the SEPA Credit Transfer module.
The final objective of the module is to generate a XML file compatible with the SEPA Credit Transfer standard based on the ISO 20022, that can be sent to a bank to pay money to your vendors.
Installing the module
The SEPA Credit Transfer is a commercial module that requires:
- an Openbravo Professional Subscription
- the Remittances infrastructure for Openbravo
- the SEPA Framework and Utilities module
To install the module and its dependencies, you just need to login as System Administrator, go to the Module Management window, search for the SEPA Credit Transfer Customer-to-Bank module and install & rebuild the system as usual.
Configuring the module
Applying the dataset
Go to the Enterprise module management window and apply the SEPA Credit Transfer Customer-to-Bank dataset as it is shown in the screenshot.
Remittance infrastructure dataset needs also to be applied.
The SEPA Credit Transfer Customer-to-Bank dataset adds:
- A new Payment Method called SEPA Credit Transfer Customer-to-Bank
- Several Remittance Types that support different SEPA Credit Transfer schema versions. All these remittance types are associated to the previous payment method.
Current supported schema versions are:
- pain.001.001.03
- pain.001.001.04
Each country and bank may support different schema versions. Contact your bank and ask about the right version to use. Currently, the most extended version is *pain.001.001.03.
Configuring the Remittance Type Parameters
As you can see in the previous screenshot, the remittance type contains a set of parameters that define the way the XML SEPA file will be generated. In general it shouldn't be necessary to modify these parameters, but depending on your country or bank specific rules, you may need to change any of them. It is recommend to use the default configuration and, if the bank doesn't accept the file, then try to change the configuration accordingly.
This is the list of parameters:
- STRICT_VALIDATION: Set to Y by default. If set to Y (Yes), Openbravo will run a strict validation of the XML file against the XSD schema version. This kind of validation may detect some errors in the XML file structure or even into the data (for example an invalid BIC).
- Use_Nm_ForIdentifiers: Set to Y by default. If set to Y (Yes), the business partner and organization identifiers will include the respective name as part of the identifier. In some countries, the identifier may not include the Name; in this case set the parameter's value to N.
- Use_Id_ForIdentifiers: Set to Y by default. If set to Y (Yes), the business partner and organization identifiers will include an unique identifier based on the tax id. In some countries, the identifier may not include this Id, but only the Name. In this case set the parameter's value to N.
- Use_AT-02_toGenerateId: Set to N by default. If set to Y (Yes), the identifiers for business partner and organization will be created using the algorithm defined in the SEPA Rulebook under AT-02. The final ID will be a combination of the 2-digits ISO country code + control digits (which are generated on the fly by Openbravo) + business code (from Business_Code parameter) + tax id. If this configuration parameter is set to N (No), the identifier will be directly the tax id. Note that when the Use_Id_ForIdentifiers is set to N, no ID will be included into the file, so the Use_AT-02_toGenerateId parameter won't be taken into account.
- BIC_SWIFT_MANDATORY: Set to Y by default. If set to Y (Yes), the BIC (SWIFT) code associated to the financial account or to the business partner account will be required when creating the SEPA file; in case the BIC is not found for any of the accounts involved into the remittance, the process will fail informing about the problem. If your bank accepts to leave the BIC code blank, you can set the value to N, and the file will be created without this information.
- GENERATE_BUSINESSPARTNER_IBAN: If set to Y (Yes), the business partner's IBAN code will be generated on the fly based on the account number and either the bank account country declared at the Business Partner's Bank Account tab or the business partner location. By default this parameter is set to 'N', because SEPA authorities recommend to force your business partners to inform about the IBAN code instead of generating it on the fly.
- DebtorIdentifier:Id+Business_Code (from 0.5.4): Set to N by default. Some banks requires the debtor's identifier to be the combination of the Tax ID and a suffix that represents a Business Code. If your bank requires this formula, set both DebtorIdentifier:Id+Business_Code and Use_Id_ForIdentifiers to Y, and define the value for the Business Code parameter
- Business_Code (since 0.5.4): Represents the business code that is used by some banks to identify the debtor's contract. Specify here the value that will be used in case either DebtorIdentifier:Id+Business_Code or Use_AT-02_toGenerateId are set to Y. By default this value is set to ZZZ and it is not used by the SEPA Credit Transfer.
- GroupBy_Duedate: Set to N by default. If set to Y (Yes) remittance lines can be grouped by due date in one <PmtInf> (payment information) section.
- CategoryPurpose_Code (since 1.0.5): Blank by default. Represents the value of the CtgyPurp tag, which indicates the type of transactions available in the remittance file. Usually you can leave empty this value (so the tag won't be included into the XML file). For example, in Spain the value must be set to SALA to indicate a payroll remittance, or to PENS in case of a pension remittance.
Configuring the Financial Account
IBAN and BIC (Swift Code)
If you haven't entered it before, you must define the IBAN and bank BIC (Swift Code) associated to the financial account. Openbravo will automatically validate the IBAN code format based on the bank's country.
This information is mandatory in order to generate the SEPA XML file. If you try to generate the file without providing this information, the process will fail informing about the problem.
Optionally, you can set the BIC (Swift Code) as not mandatory by setting the remittance type parameter called BIC_SWIFT_MANDATORY to N.
Associate the Payment Method
Finally, the SEPA Credit Transfer Customer-to-Bank payment method must be included into the list of payment methods for the financial account.
This payment method:
- allows only Payment OUT transactions
- with an Automatic execution, linked to the "In Remittance" execution process.
- without Upon Receipt/Deposit/Reconciliation accounts, because remittances have their own accounting process linked to the accounts defined at the remittance type.
Configuring the Business Partners
IBAN and BIC (Swift Code)
If you haven't entered it before, you must define for each business partner:
- either the Generic Account nº, if "Use Generic Account Nº" option or "Use SWIFT + Generic Account Nº" option is selected in the field "Bank Account Format".
- In that case, Openbravo can generate business partner's IBAN code on the fly based on the Generic Account Nº entered by setting the remittance type parameter called GENERATE_BUSINESSPARTNER_IBAN to Y.
- or the IBAN code, if "Use IBAN" option is selected in the field "Bank Account Format"
It is also possible to define the bank BIC (Swift Code) associated to each business partner.
Optionally, and in case it is not known, you can set the BIC (Swift Code) as not mandatory by setting the remittance type parameter called BIC_SWIFT_MANDATORY to N.
This information is mandatory in order to generate the SEPA XML file. If you try to generate the file without providing this information, the process will fail informing about the problem.
Generating the SEPA Credit Transfer XML file
The remittances must be created and executed at the Remittance window.
In order to get the SEPA Credit Transfer XML file it is necessary to create a new record and enter:
- The SEPA Credit Transfer remittance type version compatible with our bank, for example pain.001.001.03.
- The transaction date
- Expected date
- Name to identify this remittance
- the Financial Account linked to the bank receiving the SEPA XML file.
After that you just need to select the payments/orders/invoices to be included into the file. This can be done through the Select Payments and Select Orders or Invoices buttons, which open a popup where you can pick the records. Remember that you can also add payments associated to any payment method by setting the Show payments for alternative payment methods to Yes.
Once you have included all the lines, you must process the remittance (clicking the Process button). This will enter the list of Bank Instructions that will be used for creating the file. Inside this tab, you can review or even modify some data.
To generate the SEPA XML file, just click on the Create Remittance File button. If everything is OK, your browser will download the file ready to be sent to the bank. In case of errors, the system show the error description and won't generate the file.
Finally, you just need to send the SEPA XML file to your bank that should import it successfully.
EPC Guidelines
SEPA XML file generated from Openbravo fulfill the EPC Guidelines for the basic Latin characters set, therefore:
Common characters such as "á" or "Á" will be replaced as "a" and "A" in the SEPA XML file, same applies to characters "ñ" and "Ñ" which will be replaced as "n" and "N".
The character "\n" that indicates a new paragraph will be replaced as " ", that indicates an "empty" space.
Finally, any other character not in the following list will be removed from the SEPA XML file:
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 N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
/ - ? : ( ) . , ' +
Space