Docs  /  NCP Payments  /  Setup  /  Export

XML Schemas

2024/04/18 • 5 min. to read

In this topic

• Fields
• Setup, Actions
• XML Schema Card, Actions

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 whether the extended character set will be enabled. In general, the following characters are allowed: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 /-?:()., "space". Until now, the following additional characters were allowed for Austrian bank accounts: &; In addition, the following characters were automatically converted: < became "&lgt;" > became "&gt;" & became "&amp;" " became "&quot;" became "&apos;" If the field is set, the above conversion is performed in this schema. If the Extended Character Set field is not set, the & character is automatically converted to +, all other characters are replaced by a space. all other characters are replaced by a space. You can configure the character set by means of the action Allowed Character Set. For more information, see SEPA Requirements for an Extended Character Set (UNICODE Subset) - Best Practices
Umlaut Conversion	Specifies whether to use umlaut conversion when creating a payment file. Some banking institutions do not allow the use of umlauts. The conversion will: Ä or ä to an Ae or ae Ü or. ü to an Ue or ue Ö or ö to an Oe or oe
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.

Setup, Actions

• Download

  Via the action Download you can download or update schemata templates.

• Import

  With the import function schemas can be imported.

• Export

  With the export function schemas can be exported.

• Init Allowed Characters

  Using this action you can change the Allowed Character Set value, for all XML Schemas, to the default.

XML Schema Card, Actions

• &Copy from

  With Copy from you can create a copy of an existing schema and then edit it.

• Allowed Characters

  With this action you can configure the allowed characters that are valid for use in payment files. This is necessary if your bank allows a different character set than the SEPA standard.

• Init Allowed Characters

  Using this action you can change the Allowed Character Set value to the default.