| Docs Help
  AppSource  
Print this pageEntire manual (printable version)
Docs  /  NAVAX Payment  /  Setup  /  Exports

 XML Schemas


2025/07/04 • 15 min. to read
The XML format is the Europe-wide recognized standard for payment transactions and is actively promoted by the European Payments Council (EPC) and the EU. The goal is to standardize the multitude of national payment formats and, in the long term, to fully replace them with the XML format. This harmonizes and simplifies the processing of transactions both between banks and for end customers from a technical perspective. On this page, you manage the XML schemas required for exporting payment files in Business Central. The schemas define how the data from Business Central is mapped to the respective fields of the XML file.

Accessing the XML Schemas

The management of XML schemas is done via the Exports Setup page. Use the XML Schemas action to access the overview and management of existing schemas.

Downloading SEPA XML Schemas

  1. Open the NCP Exports Setup page. You can access this page via Tell me what you want to do or from the Business Central homepage via the NAVAX Payment menu, Administration, NCP Exports Setup. For more information, see Setup, Exports, Exports Setup.
  2. On the NCP Exports Setup page, select the XML Schemas action to open the overview of available XML schemas in Dynamics 365 Business Central.
  3. Click the Download action to download the provided SEPA XML schemas.

    Note

    If no permission has yet been granted to establish an online connection via NAVAX Payment, you will be prompted to do so. An internet connection is required for the download.

    Important

    If an error occurs during the download, please check the required settings. For more information, see Appendix, Installation Notes..
  4. The system automatically downloads the SEPA XML schemas from the official source and saves them in Dynamics 365 Business Central. If XML schemas already exist, you will be prompted to decide how to proceed.
    • Create only new records Only schemas that do not yet exist in the database will be downloaded. Existing schemas will not be overwritten.
    • Create new records & overwrite existing records All downloaded schemas will be created in the database. Existing schemas will be overwritten with the default values. Custom adjustments will be lost.
    • Create new records & update existing records (keep settings) All downloaded schemas will be created in the database. Existing schemas will be updated, custom adjustments will remain. Only the fields changed in the downloaded schema will be updated.

    Note

    If you have questions or problems with the download or the SEPA schemas (e.g., if they are rejected by the processing software), please contact your payment transactions contact person. Please provide us with detailed information so that we can help specifically. If the bank rejects the schema, the exact error message is required for analysis.
  5. After a successful download, a dialog appears with an overview of the downloaded schemas.

Exporting SEPA XML Schemas

  1. Open the NCP Exports Setup page. You can access this page via Tell me what you want to do or from the Business Central homepage via the NAVAX Payment menu, Administration, NCP Exports Setup. For more information, see Setup, Exports, Exports Setup.
  2. Select the Export action.
  3. The system exports all schemas to an XML file and saves it in the Download folder on your computer under the name NCPE_XMLSchemas.xml.

Tip

After exporting the XML schemas, you will receive an XML file containing all schemas currently present in your database. You can keep this file as a backup or import it into another Dynamics 365 Business Central environment. After the export, check whether the file is complete and contains all the desired schemas. This ensures that you can always access your configuration or share it when needed. The following section explains how to import these backups into Business Central.

Importing SEPA XML Schemas

  1. Open the NCP Exports Setup page. You can access this page via Tell me what you want to do or from the Business Central homepage via the NAVAX Payment menu, Administration, NCP Exports Setup. For more information, see Setup, Exports, Exports Setup.
  2. Select the Import action.
  3. Select the local XML file you want to import. You can drag & drop a file into the Import XML Schemas dialog or use the Drop file here to upload or click here to browse button to select a file from your computer.
  4. The system checks the file and imports the schema into the database.
  5. The system automatically downloads the SEPA XML schemas from the official source and saves them in Dynamics 365 Business Central. If XML schemas already exist, you will be prompted to decide how to proceed.
    • Create only new records Only schemas that do not yet exist in the database will be downloaded. Existing schemas will not be overwritten.
    • Create new records & overwrite existing records All downloaded schemas will be created in the database. Existing schemas will be overwritten with the default values. Custom adjustments will be lost.
    • Create new records & update existing records (keep settings) All downloaded schemas will be created in the database. Existing schemas will be updated, custom adjustments will remain. Only the fields changed in the downloaded schema will be updated.

Tip

Importing previously exported XML schemas allows you to easily transfer already configured schemas to other Dynamics 365 Business Central environments. This is especially useful if you have made individual adjustments to the schemas, for example to meet specific requirements of your bank. It can also be helpful during upgrades. This saves time and avoids errors, as you do not have to set up the schemas manually again. You can find out how to create a backup of the schemas in the section Exporting SEPA XML Schemas above.

Notes

  • For smooth payment processing, it is important to always use up-to-date SEPA XML schemas. We ensure that new or changed schemas are made available for download promptly as soon as official adjustments are published.
  • If you have questions about compatibility or specific formats, please contact support.

Special Notes NON-SEPA Credit Transfers

The continuously increasing regulations to prevent money laundering, terrorist financing, embargo circumvention, etc., usually require the full name of the recipient and the corresponding address to be provided. The recipient's financial institution, which may be subject to additional regulations of the respective country, can refuse acceptance or is obliged to return the transaction if the information provided is insufficient. Although the minimum requirements of the payment systems are low (country code and city), it is still advisable to provide as complete information as possible.

Adding Lines in the XML Schema

On the NCP Exports XML Schema Lines page, you can add new lines to customize the XML schema as needed. This is useful if you want to include additional information or meet specific requirements for your payment files. New lines are always inserted above the currently selected line and can then be edited. Make sure that the new line receives a position number greater than that of the previous line. After adding new lines, you should use the Update Position Numbers action to re-sort the position numbers so that the order in the schema remains correct.

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 Payment Transactions
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 NCP Exports 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 The field Batch Booking determines how the transactions are booked by the bank. By default, this field remains empty, and the indicator () is not written into the payment file. If you specify Yes or No, the indicator is set in the payment file to indicate whether it is a Batch Booking (Yes) or a Single Booking (No).

Note

Only if there is a corresponding agreement with the bank for single bookings, each transaction will be displayed individually on the client's account statement when specifying No. Otherwise, or by default, it is always a batch booking (default/pre-agreed: Yes).
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.
Instant Payment possible Indicates that the schema supports instant 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.

NCP Exports XML Schema Lines, Fields
Level Specifies the level. The level can be understood as the parent XML nodes (e.g., GrpHdr, PmtInf..), within the level the position numbers are assigned per child XML node. Available options:
  • A1
  • B1
  • C
  • B2
  • A2
Position Specifies the position of the line in the schema. Use the action Update Positions to re-sort the position numbers per Level, this is necessary after inserting a new line.
Indentation Specifies the indentation, which hierarchically arranges the child XML nodes. The field is not visible on the page, use the actions Indent or Outdent to indent or outdent the XML nodes.
Tag Specifies the tag name or node name for the XML node.

Tip

By clicking on the field, the text editor opens, which facilitates the editing of the tag. This is especially helpful when the tag is long.
Start Tag Specifies that the node should be a start tag. By enabling this field, you can indicate that it is an XML node that should contain a start tag. If you activate the field, but not the End Tag field, a parent node is created (e.g., <Tag>). If both fields are activated, a child node is created (thus the XML node is closed in the same line, e.g., <tag>Value</tag>).
End Tag Specifies that the node should be an end tag. By enabling this field, you can indicate that it is an XML node that should contain an end tag. If you activate the field, but not the Start Tag field, a parent node is created (e.g., <Tag>). If both fields are activated, a child node is created (thus the XML node is closed in the same line, e.g., <tag>Value</tag>).
Value Specifies the value to be used as the inner text in this XML node. Using the AssitEdit function opens the NCP Exports XML Schema Values page, which provides you with some standard values to choose from, but you can also enter a custom value in the field. For more information, see Setup, XML Schema Values.
Default Value Specifies the default value, a default value is understood as a constant. For example, in a SEPA domestic transfer in Austria, the <PmtMtd> node always needs to have the value TRF. For more information, see Setup, XML Schema Values.
Maximum Character Count Specifies the maximum number of characters valid for the value of the XML node.
XML Displays the XML of the tag. This column helps you understand the structure of the XML file.
Attribute Specifies that the XML node contains an attribute. Enter the attribute name and value in quotation marks.
Skip Specifies that the XML node should be skipped when a condition is met. The values Yes, If - OR, and If - AND are available. The Skip - If empty and Skip - If not empty fields define the values for the condition.
Skip - If empty Specifies the value used for the condition to skip. So if the set value for the XML node is empty, it will be skipped.
Skip - If not empty Specifies the value used for the condition to skip. So if the set value for the XML node is not empty, it will be skipped.

Special notes NON-SEPA Credit Transfers

The continuously growing regulations to mitigate money laundry, terror financing, embargo bypassing a.s.o. in most cases require the presentation of the name and the address of the counter party of the transaction. Moreover, the financial institution of the counter party, that may be additionally regulated by the country of residence, can reject or even is forced to reject the transaction, if the presented information is insufficient. Even if the minimum requirements of the payment systems are low (country code and town name), it is advised to present an at most complete set of address data.

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

    With this action, you reset the allowed character set for all XML schemas to the default value. This will overwrite all individual customizations and use the standard character set for all schemas.

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.

  • Reset Allowed Characters

    With this action, you reset the allowed characters for the purpose field in the payment file to the default value. The default value includes the following characters: abcdefghijklmnopqrstuvwxyzäüößABCDEFGHIJKLMNOPQRSTUVWXYZÄÜÖ0123456789/-?:().

NCP Exports XML Schema Lines, Actions

  • Indent

    Use this action to indent lines.

  • Outdent

    Use this action to outdent lines.

  • Update Position Numbers

    Use this action to update the position numbers. This is required after you have inserted new line(s).

  • New Line

    Use this action to add a new line to the schema. The new line is inserted above the selected line in the list; the position can then be adjusted using the Update Positions action.

  • Delete Line

    Use this action to delete a line from the schema. The line is removed from the list, and the positions of the other lines are automatically adjusted.

Related information

Submit feedback for

In this topic

★ Featured App

DE|EN Imprint
◀☰▶
△