The EU and the EPC (European Payments Council) are intent on using the XML format as a standard in European payment transactions. At the moment, efforts are being made to minimize the numerous different national variants of payment transaction solutions and ultimately to eliminate them completely. The XML format should replace all other formats in order to standardize the processing of transactions on a technical level Europe-wide. This format is to be introduced and accepted as a standard both in the interbank sector and by customers.
Use this page to manage the XML schemas that are required for exporting the payment file. These schemas are used to map the data from Business Central to the fields in the XML schema file.
Fields
| Type | Specifies the type of XML schema. Possible values are: SEPA Credit Transfer, SEPA Direct Debit and Non-SEPA Credit Transfer |
| Code | Specifies the code of the XML schema. This code meets the SEPA standard of the schema. You can find more information on this on Stuzza |
| ISO Country Code | Specifies the countries for which the schema is valid. Some countries have different requirements of the ISO standard. |
| Description | The field Description is a combination of the abbreviation of the field Type, the ISO country code and the rulebook version of the schema. This only applies to downloaded schemas. If you have created a schema yourself, the Description is assigned by you. |
| IBAN Only possible | The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code. |
| Dom. IBAN Only | The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code. If Dom. IBAN Only is set, domestic transactions are also allowed without SWIFT Code. |
| Int. IBAN Only | The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code. If Int. IBAN Only is set, foreign transactions are also allowed without SWIFT Code. |
| IBAN or Bank Account No. possible | The field IBAN or Bank Account No. possible indicates that the schema also supports transactions without IBAN. |
| IBAN or Bank Account No. | The field IBAN or Bank Account No. possible indicates that the schema also supports transactions without IBAN. If IBAN or account number is set, the account number of the recipient bank is written to the payment file if no IBAN exists. |
| Address Specification possible | Indicates that the schema supports address information. |
| Originator Address | The field Address Specification possible views whether the scheme supports address data. The field Originator Address specifies whether the address data of the originator, which was stored in the NCPE Payments Export Setup, should be written to the payment file. |
| Recipient Address | The field Address Specification possible indicates that the scheme supports address data. The field Recipient Address specifies the address data of the recipient that should be written to the payment file. |
| Batch Booking | Specifies how the transaction is posted on the bank side. That is, whether it is a collective posting ('Yes') or an individual posting ('No'). |
| Extended Character Set | Specifies if the expanded character set should be activated. |
| Charges Selection possible | Indicates that the schema allows the specification of charges. |
| Urgent Payment possible | Indicates that the schema supports urgent payments. |
| Date of Specification | Specifies the date of the specification. |
| Last Date Modified (Schema Lines) | Shows whether, and if so, when the schema lines were last changed. |
| In Use | Indicates that the scheme is in use. |
