NC Payments Documentation - NAVAX documentation is intended to explain the connections within the application. It is designed as a reference which provides all the information needed

NC Payments

Setup Documentation

NCP 8.00 for Microsoft Dynamics NAV 2015* *NC Payments 8.00 is available for Microsoft Dynamics NAV 2013, Microsoft Dynamics NAV 2013 R2 und Microsoft Dynamics NAV 2015.

SETUP DOCUMENTATION

FEHLER! VERWEISQUELLE KONNTE NICHT GEFUNDEN WERDEN.8.00

NAVAX | Deutschland | Österreich | Schweiz Seite 2 von 31

DISCLAIMER

This documentation serves for information purposes only. In case of using the manual for other purposes NAVAX Consulting GmbH rejects any guarantee because of material defects and/or title defects.

NAVAX Consulting GmbH rejects any adhesion for direct and/or indirect damage – irrespective of whether on a contractual or legal basis -, which may arise in connection with application and/or other use of the documentation, as well as any errors and/or omissions in this publication. This documentation can be changed at any time if necessary without previous announcements by NAVAX Consulting GmbH.

The content of this documentation is protected by copyright. Without written permission of NAVAX Consulting GmbH no part of this documentation may be multiplied or transferred for any purposes, irrespective of whether by electronic or mechanical means.

Microsoft Dynamics® NAV, Microsoft Dynamics® AX, Microsoft Dynamics® CRM, Microsoft SharePoint, QlikView and Corporate

Planner are registered trademarks. Further mentioned product and company names may be protected by copyright terms of their legal owners.

The content of this documentation may be subject to change without prior notice. This documentation may be used for internal purposes only. Disclosure to third parties is prohibited.

SETUP DOCUMENTATION



NC PAYMENTS 8.00 | SETUP DOCUMENTATION

Publisher | NAVAX Author | Michael Koch Date | 2015

Copyright © 2015 NAVAX Consulting GmbH

NAVAX Consulting GmbH EURO PLAZA | Technologiestraße 8 A-1120 Vienna Phone: +43 50 8383-0 Fax: +43 50 8383-199

E-mail: [email protected]

mailto:[email protected]

SETUP DOCUMENTATION



Introduction

The processes and scenarios defined in this documentation were developed using the product NC Payments 8.00. This documentation is intended to explain the connections within the application.

It is designed as a reference which provides all the information needed for working with Microsoft Dynamics NAV.

Dear reader,

This documentation was drafted and reviewed most thoroughly. In case you still have any proposals for improvements, please do not hesitate to let us know.

Of course we also have pleasure in receiving your compliments.

We wish you a pleasant read,

NAVAX Consulting GmbH

Visit our website www.navax.com

Target group

In first place, this documentation is addressed to those users working with NC Payments 8.00.

We recommend the user to have basic knowledge of data processing.

Structure

The structure of this documentation is process-oriented. Each chapter contains a step-by-step description of the most important functions for working with NC Payments.

Masks and functions

Any masks, functions or fields mentioned in this documentation are highlighted in “bold”.

Example:

To create a new data set click the New button in the Home menu bar. A new window “Document Card” opens in which you can define the following fields: Code, Description.

Notices

NOTICE: THERE ARE PARTS IN THIS DOCUMENTATION WHICH ARE HIGHLIGHTED IN ITALIC CAPITAL LETTERS. THESE CONTAIN INFORMATION OF SPECIAL IMPORTANCE.

Further information: There are parts in this documentation which are highlighted in italic letters. These contain additional information.

Links

This document contains links to other documents, both within and outside of this documentation to provide further important information.

http://www.navax.com/

SETUP DOCUMENTATION



Table of Contents

General ..................................................................................... Fehler! Textmarke nicht definiert.

1. Payment Setup ...................................................................... Fehler! Textmarke nicht definiert.

1.1 General FastTab ....................................................................................................................................... 8

1.2 Payment File FastTab ............................................................................................................................. 10

1.3 Payment Notification FastTab ............................................................................................................... 13

1.4 Payment Notification FastTab ............................................................................................................... 13

1.5 Import FastTab ...................................................................................................................................... 14

1.6 Version FastTab ..................................................................................................................................... 15

1.7 Functions ............................................................................................................................................... 15

2. Bank Code Setup .................................................................................................................. 16

2.1 Download Function ............................................................................................................................... 16

2.2 Import Function/Export Function .......................................................................................................... 17

2.3 Bank Code Table Description .............................................................. Fehler! Textmarke nicht definiert.

3. Currency Setup ..................................................................................................................... 19

3.1 Currency Table Description ................................................................ Fehler! Textmarke nicht definiert.

4. Country/Region Setup ........................................................... Fehler! Textmarke nicht definiert.

4.1 Country/Region Table Description ..................................................... Fehler! Textmarke nicht definiert.

5. Languages ............................................................................................................................ 21

5.1 Languages Table Description .............................................................. Fehler! Textmarke nicht definiert.

6. Pmt. Notification Text Setup ................................................................................................. 21

6.1 Pmt. Notification Text Table Description ........................................... Fehler! Textmarke nicht definiert.

7. XML Schemas Setup ............................................................................................................. 23

7.1 Download Function ............................................................................................................................... 23

7.2 Import Function/Export Function .......................................................................................................... 25

7.3 XML Schemas Table Description ............................................................................................................ 25

8. SEPA Mandate Text Setup .................................................................................................... 27

8.1 SEPA Mandate Text Table Description .................................................................................................. 28

9. Bank Account Setup............................................................... Fehler! Textmarke nicht definiert.

9.1 Transfer FastTab .................................................................................................................................... 28

9.2 Customer Bank Account Setup .............................................................................................................. 29

9.3 Vendor Bank Account Setup ............................................................... Fehler! Textmarke nicht definiert.

10. Technical Annex ................................................................................................................. 31

SETUP DOCUMENTATION



General

Introduction NC Payments

The NC Payments module extends the Microsoft Dynamics NAV standard by the possibility to create or import payment files based on national standards or SEPA notifications (European Union, Switzerland, Monaco, Iceland, Liechtenstein, and Norway). The following formats are supported by NC Payments:

Dom. Credit Transfer (PAYMUL)

Int. Credit Transfer (PAYMUL)

Direct Debit (DIRDEB)

Non-SEPA Credit Transfer

SEPA Credit Transfer

SEPA Direct Debit

MT101 Dom. Credit Transfer

MT101 int. Credit Transfer

NOTICE: DIRECT DEBITS (DIRDEB) AND SEPA-DIRECT DEBITS ARE ONLY POSSIBLE FOR CUSTOMERS.

NC Payments is integrated in Financial Accounting and allows to create a payment file of payment and bank collection suggestions, based on the open items of vendors and customers, and subsequently to import these into a bank software.

NC Payments consists of one basic- and three sub-modules:

1.001.710 – NC Payments – Basic

The Basic Module allows to record and to administer external bank connections and all the necessary information relating to the payment files.

Furthermore, it contains the national notifications “Dom. Credit Transfer” and “Int. Credit Transfer” (PAYMUL) for vendors and Direct Debit (DIRDEB) for customers.

Thus, the Basic Module allows

to create payment files (for vendors) for domestic or international credit transfers from a national bank account by means of a national bank software.

to create payment files (for customers) for bank collections and direct debits from a national bank account to a national bank account. Additionally, test-, suggestion-, and pmt. notification reports are provided.

1.001.720 – NC Payments – SEPA

The SEPA (Single Euro Payments Area) sub-module allows to create payment files based on SEPA XML notifications. Thus, based on (Non-) SEPA credit transfers, open items (invoices) can be transferred to a payment file in the “Customers and Vendors” module, and subsequently be imported into a bank software.

Furthermore, the module allows to create payment files based on SEPA direct debits to perform the collection of open customer ledger entries (invoices).

Equally, credit transfers in the form of a credit memo based on the SEPA credit transfer can be performed.

The module allows credit transfers and collections of invoices by means of a bank software within the European Union/European Economic Area.

SETUP DOCUMENTATION



1.001.730 – NC Payments – Import

The NC Payments Import module extends the Microsoft Dynamics NAV standard and the NC Payments module by importing various media that can then be edited.

1.001.730 – NC Payments – Import is a separate Granule which was created for NC Payments.

The following formats are supported:

camt.052

camt.053

camt.054

MT940

CREMUL

NOTICE: SEE ALSO THE “NCP800_DOCUMENTATION_IMPORT” DOCUMENTATION.

1.001.740 – NC Payments – MT101

The MT101 sub-module allows to create payment files based on MT101 notifications. Furthermore, it allows to transfer open items to a payment file in the “Vendors and Customers” module, and subsequently to import these into a bank account software.

NOTICE: TO USE THE SEPA (1.001.720), NC PAYMENTS - IMPORT (1.001.730) AND NC PAYMENTS - MT101 (1.001.740) SUB-MODULES, THE NC PAYMENTS – BASIS (1.001.710) BASIC MODULE IS REQUIRED.

1. Payment Setup

Before the NC Payments module can be started, basic information must be recorded in the Payment Setup. (Departments > Payments > Administration > Payment Setup). It is recorded separately for every mandate.

NOTICE: THE PAYMENTS PERMISSION SET “NCP-EDIT” CAN BE CREATED/UPDATED VIA THE CREATE PERMISSIONS MENU ITEM.

NOTICE: BASIC INFORMATION (DRIVE PATHS, ETC) REGARDING THE PAYMENT OR MANDATE CAN BE RECORDED IN THE PAYMENT SETUP WINDOW. IT MUST BE RECORDED SEPERATLY FOR EVERY MANDATE.

SETUP DOCUMENTATION



1.1 General FastTab

1.1.1 LCY Code

This fields indicates the LCY Code.

1.1.2 ISO LCY Code

In this field the ISO LCY code must be recorded (E.g. EUR for Euro, USD for US Dollar, etc.).

NOTICE: WHEN THE PAYMENTS SETUP IS OPENED FOR THE FIRST TIME, THE ISO LCY CODE FIELD IS PREDEFINED AS “EUR”, IF THE LCY CODE IS “EUR” OR “EURO”.

1.1.3 External Bank Account Search

In this field the option for the external bank account search, which will later be considered in the payment suggestion, is selected.

Main Bank Account – when the payment suggestion is opened, the application attempts to determine the External Bank Acc. field in the journal by means of the Main Bank Account.

Last Transaction – when this option is selected the application attempts to determine a value my means of the last transaction. The last transaction of the bank account with the same Payment Type, Customer-/Vendor No. and Currency Code will be searched.

Last Transaction/Main Bank Account – if this option is selected the Main Bank Account and Last Transaction are used simultaneously.

NOTICE: IF A VALUE IS AVAILABLE FOR THE VENDOR/CUSTOMER LEDGER ENTRY IN THE EXTERNAL BANK ACCOUNT CODE FIELD, IT WILL BE SUGGESTED IN BOTH CASES.

SETUP DOCUMENTATION



1.1.4 Add XXX to External SWIFT Code

If this check box is selected, XXX will be added to SWIFT codes of the external bank account.

1.1.5 Create Bal. Account Line

This field defines how the journal lines will be rearranged, after the cash receipts and payments were created.

NOTICE: IF THE CREATE BALANCE ACC. LINE IN THE PAYMENTS SETUP IS SELECTED, THE DOCUMENT TYPE OF INDIVIDUAL JOURNAL LINES WILL BE MODIFIED (IF CERTAIN CONSTELLATIONS EMERGE, ALSO SEE NCP 7.10) IN CREATING THE PAYMENT FILE. THESE MODIFICATIONS WILL THEN BE SAVED.

ONCE THE TRANSACTION IS VOIDED, THE DOCUMENT TYPE WILL BE RESET TO THE INITIAL VALUE.

1.1.6 Modify allowed after “File Created”

If this check box is selected, the adjustment in a journal can still be modified after its creation.

1.1.7 Due Date Calculation

This field is filled to predefine the Last Due Date field based on the job date when payment suggestion is opened.

1.1.8 Discount Date Calculation

This field is filled to predefine the Last Discount Date field based on the job date when the payment suggestion is opened.

1.1.9 Posting Date Calculation

This field is filled to predefine the Posting Date field based on the job date when the payment suggestion is opened.

Further information – Balance Entry Line: It is only created, if more than one journal line per balance entry line exists.

It is only created for various document types, if Applies-to Doc. No. is selected for all the affected balance entry lines. In this case, the document type of the affected journal lines is set to Payment.

Further information – External Bank Acc. Search: If no appropriate transaction can be found, the payment suggestion searches for the main bank account. If only one bank account exists, this one will be used.

The following conditions for suggesting external bank accounts apply:

Payment Type “SEPA”:

If “SEPA” is set for both the own and the external bank account.

If the ISO currency code of the respective transaction is defined as “EUR”.

Payment Type “Non-SEPA”:

If the payment type “SEPA” is not available.

Domestic EDIFACT (PAYMUL/DIREDEB):

If the ISO country code of both the own and the external bank account is defined as “AT”.

If the ISO currency code of the respective transaction is defined as “EUR”.

Int. EDIFACT (PAYMUL):

If the payment type “Dom. EDIFACT” is not available.

SETUP DOCUMENTATION



If the own bank account is defined as “AT” in the ISO country code.

If the external bank code contains a value in the ISO currency code (e.g. “AT”, if the ISO currency code of the transaction is not “EUR”/ “Domestic” is not available.

MT101 Dom. Credit Transfer:

If the ISO country codes of the own and the external bank accounts are identical.

MT101 Int. Credit Transfer:

If the “MT101 Dom. Credit Transfer” payment type is not available.

1.2 Originator FastTab

NOTICE: WHEN THE PAYMENTS SETUP IS OPENED FOR THE FIRST TIME, THE NAME AND NAME 2 FIELDS AND ALL THE ADDRESS INFORMATION FROM THE COMPANY DATA IS SUGGESTED/PREDEFINED.

1.2.1 Creditor ID

This field indicates the originator’s Creditor ID.

NOTICE: A CREDITOR ID CAN BE REGISTERED AT THE E.G. THE AUSTRIAN NATIONAL BANK (WWW.OENB.AT)

Further information: The Austrian Creditor ID has the following structure:

Digit 1-2: ISO Currency Code (two digit, alphanumeric)

Digit 3-4: Check Digit (two digit, numeric)

Digit 5-7: Business Area Code (three digit, alphanumeric)

Digit 8-18: National Identification Feature (eleven digit, numeric)

1.2.2 Contact Department (PAYMUL/DIRDEB)

This field indicates the originator’s contact department for PAYMUL/DIRDEB.

1.2.3 Contact Person (PAYMUL/DIRDEB)

This field indicates the responsible person for PAYMUL/DIRDEB in the contact department.

1.2.4 Phone No. (PAYMUL/DIRDEB)

This field indicates the phone no. of the responsible person for PAYMUL/DIRDEB in the contact department.

1.3 Payment File FastTab

1.3.1 Payment Type

This field indicates the appropriate payment type:

Dom. Credit Transfer (PAYMUL)

Int. Credit Transfer (PAYMUL)

Direct Debit (DIRDEB)



SEPA Direct Debit

MT101 Int. Credit Transfer

MT101 Dom. Credit Transfer

http://www.oenb.at/

SETUP DOCUMENTATION



1.3.2 Folder

This field indicates the folder, where the payment file will be saved. If the Show “Save As” check box is ticked off, selecting a folder is not necessary.

In this case, an entry will be used as a suggestion in the Save As window.

1.3.3 File Name

This field indicates the name of the created payment file. The following placeholders can be used in the File Name field:

%1 Day

%2 Week

%3 Month

%4 Year

%5 Year 4 digits

%6 Bank Account No.

%7 File Reference (Message Reference)

%8 Clearing Entry No.

%9 User ID

1.3.4 Show Save As

If Show Save As is selected, a Save As window is available in the payment file creation process.

1.3.5 Archive Payment File

If this check box is selected, the selected payment file will also be saved.

NOTICE: AN ARCHIVED PAYMENT FILE IS A COPY OF THE PAYMENT FILE, WHICH WILL BE STORED IN THE DATABASE.

1.3.6 Remittance Info. Length

This field indicates the maximum length of the remittance info.

1.3.7 Remittance Info.

This field determines the structure of the payment type remittance info. The following placeholders can be used in the Remittance Info. field:

%1 Document Type

%2 External Document No. or Document No.

%3 External Document No.

%4 Document No.

%5 Currency

%6 Amount

%7 Discount

SETUP DOCUMENTATION



%8 Vendor No./Customer No.

%9 Our Account No.

%10 Gen. Journal Batch Line Description

%11 Document Date

%12 Payment Text

NOTICE: USE SQUARE BRACKETS (E.G. [DISCOUNT: %7]), IF YOU ONLY WANT TO OUTPUT THE TEXT, IF THE PLACEHOLDER CONTAINS A VALUE. BY RECORDING A NUMERIC VALUE IN ANGLE BRACKETS IMMEDIATELY AFTER THE PLACEHOLDER (E.G. “%1<2>” OR “[INFO: %10<15>]”), THE MAXIMUM LENGTH OF THE PLACEHOLDER CAN BE LIMITED. WHEN THE PAYMENTS SETUP IS OPENED FOR THE FIRST TIME, A SUGGESTION FOR THIS FIELD IS PROVIDED.

Further information: The remittance info. is currently preallocated with the following value:

[%2-][%5%6][-Disc%7].

1.3.8 Remittance Info. Header

For “Dom. Credit Transfer (PAYMUL)” and “Direct Debit (DIRDEB)”, a remittance info. header can be recorded.

If a text is recorded in the respective caption field, it will be considered in the remittance info.

Further information: Example:

Caption Remittance Info.:

Info/Amount (Discount)

Remittance info:

%1%2/%6[(%7)]

Result:

Info/Amount (Discount)

Payment 00112300/12.500 (500)

Payment A312-5/1000

Payment B312-5/990(10)

Payment 01004565B/2300

1.3.9 Collective Transaction

This option determines, if in creating the payment files the transactions are summarized and will therefore be forwarded to the bank as a collective transaction.

The following transactions are not affected:

Individual credit transfers

Credit transfers, for which a payment reference is provided.

SETUP DOCUMENTATION



Further information: Otherwise journal lines with identical vendor nos./customer nos./bank acc. nos./external bank acc. codes and currency codes are attempted to be summarized in one transaction and then be forwarded to the bank.

It is also possible for credit transfers to consider discounts, which were recorded via Applies-to Doc. No. in the journal. This requires the collective transaction to have a positive amount. (Vice versa for bank collections).

This function is especially useful, if Summarize per Customer or Summarize per Vendor is not used for the payment suggestion.

Once the journal lines are summarized, the appropriate payment entry is marked as Collective Transaction. Furthermore, the Description field in the payment entry is filled with Collective Transaction. Doc. No. and Posting Date are only filled, if there is no deviation within the Collective Transaction. If the journal lines contain different values, the field is left blank.

1.3.10 Always Create Notification

This option determines, if in creating the payment file a notification is always created, irrespective of whether or not the remittance info. can be forwarded completely.

1.4 Pmt. Notification FastTab

1.4.1 Payment Notification Nos.

In this field the code of the appropriate number series is recorded.

1.4.2 Pmt. Notification Text Exists

This field indicates, if a notification text exists. The Notification Text Setup window can be opened via AssistEdit.

1.5 Pmt. Notification E-Mail FastTab

1.5.1 SMTP Server

In this field the SMTP server name (DNS name or IP address) is recorded.

1.5.2 SMTP Server Port

In this field the SMTP server port is stored.

NOTICE: BY DEFAULT THE SMTP SERVER ALLOWS THE PORT 25 FOR OUTGOING AND INCOMING COMMUNICATION FOR ROLE BASED CLIENTS AND MICROSOFT DYNAMICS NAV SERVER. FURTHERMORE, THE FIRE WALL SETTINGS SHOULD BE CHECKED.

1.5.3 Authentication

This field indicates the authentication used by the SMTP e-mail server. The following types of authentication are supported:

Anonymous

NTLM

Basic

NOTICE: THE DEFAULT SETTING IS ANONYMOUS, IF NO USER ID OR PASSWORD INFORMATION IS REQUIRED. THE BASIC AUTHENTICATION IS USED IN AN AZURE APPROPRIATION.

SETUP DOCUMENTATION



1.5.4 User ID

This field indicates the unique user ID.

1.5.5 Password

This field indicates the SMTP server password.

1.5.6 Secure Connection

This field indicates, if the SMTP e-mail server setup requires a secure connection (cryptography- or safety protocol, e.g. Secure Sockets Layer/SSL). If the security settings are not activated, the check box must be deactivated.

1.5.7 HTML Formatted

This field indicates, whether or not the e-mail text can be formatted. If the check box is selected, a HTML code can be stored in the e-mail.

Example:

<h1>Dear ladies and gentlemen,</h1>

<p>Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.</p>

<b>Yours sincerely</b>

1.5.8 Sender Name

In this field the name of the sender can be recorded.

1.5.9 Sender E-Mail

In this field the e-mail address of the sender can recorded.

1.5.10 CC E-Mail

In this field the e-mail address(es) of one (or more) copy recipient(s) can be recorded.

1.5.11 BCC E-Mail

In this field the e-mail address(es) of one (or more) blind copy recipient(s) can be recorded.

1.6 Import FastTab

1.6.1 Field No. Payment Reference

This field determines, which customer ledger entry field contains the payment reference.

This field considers the functions in the bank acc. reconciliation for the adjustment suggestion (after importing a MT940 file).

NOTICE: SINCE THERE IS NO UNIVERSAL RULE, AT WHAT TIME THE REFERENCE WILL BE DETERMINED OR HOW THE REFERENCE WILL THEN BE MADE AVAILABLE FOR THE CUSTOMER FOR PAYMENT, THIS FIELD AND THE ASSIGNMENT OF THE REFERENCE MUST BE PROGRAMMED INDIVIDUALLY IF NECESSARY.

1.6.2 Belegnr. Mit Auszugsnr. Vorbelegen

Ist das Kontrollkästchen aktiviert, wir die Belegnummer des Bankkontoauszugs bis zu den Debitorenposten der Belegart Zahlung mitgebucht.

SETUP DOCUMENTATION



1.6.3 Save Embedded Import File

If this check box is selected, a copy of the payment file is saved in the database for every clearing entry.

1.7 Version FastTab

1.7.1 Version

This field indicates both the latest version and the prior versions. The Download button provides Bank Codes, Payment Codes and XML Schemas for downloading.

1.7.2 Bank Codes Date

This field indicates the last download/import date of bank codes in the database.

1.7.3 Payments Codes Date

This field indicates the last download/import date of payments codes in the database.

1.7.4 XML Schemas Date

This field indicates the last download/import date of XML schemas in the database.

1.8 Functions

1.8.1 Send Test Message

This function allows to test the settings of the pmt. notification e-mail functionality. If this function is activated, the e-mail address, which the PN test message will be sent to, must be recorded in the Send Test Message to field.

1.8.2 Create Permissions

In this field, the standard permissions (roles) can be created/updated.

1.8.3 Initialize Currencies

This function fills in the Payments ISO Code field in the Currencies table. For every existing ISO code, the availability of a currency with the same code is tested. In this case will be checked, if the Payments ISO Code field contains a value. If there is no value available, the ISO code will be recorded in the field.

1.8.4 Initialize Country/Region

This function fills in the Payments ISO Code and SEPA fields in the “Country/Region” table. For every existing ISO code, the availability of a currency with the same code is tested. In this case will be checked, if the Payments ISO Code field contains a value. If there is no value available, the ISO code will be recorded in the field. Afterwards, for every SEPA country (according to the ISO code), the SEPA field is selected.

NOTICE: EXPORT VENDOR/CUSTOMER BANK ACCOUNTS AND IMPORT VENDOR/CUSTOMER BANK ACCOUNTS – THESE TWO FUNCTIONS USED TO BE AVAILABLE AS MENU ITEMS IN SETUP > EXPORT/IMPORT BANK ACCOUNTS. THEY ARE NOW AVAILABLE AS FOLLOWS:

1.8.5 Export Vendor/Customer Bank Accounts

This function allows to export all the vendor and customer bank accounts.

1.8.6 Import Vendor/Customer Bank Accounts

This function allows to import all the vendor and customer bank accounts from a file. For importing the bank accounts, the following options are provided:

SETUP DOCUMENTATION



Maintain and Complete Blank Fields This option completes only those bank account fields, which do not contain data (if data records for the respective bank account in the file are available)

Overwrite, if New Value Exists This option overwrites those bank accounts, for which individual data records were changed (compared to prior data records). In this case, all the data records of this bank account will be updated.

Overwrite All This option updates all the data records of all bank accounts.

2. Bank Codes Setup

2.1 Download

Besides the manual setup (Import) of bank accounts, NC Payments allows to download bank codes via the Download function field and to import them into the table automatically.

By default there are no data records in the Bank Codes table.

1. Click Bank Codes in the Payments content area. 2. Click the Download function field in the Bank Codes window. The bank codes download will be

started and the data records will be filled in the table automatically.

NOTICE: EXISTING BANK CODE FILES CAN ALSO BE IMPORTED VIA THE IMPORT FUNCTION. IF THE TABLE ALREADY CONTAINS THE DATA RECORDS, A WINDOW WITH THE FOLLOWING OPTIONS APPEARS:

“Create only new Records”

This option only creates new Payments Import Codes.

“Create new records & overwrite existing Records”

This option overwrites/updates the available codes (E.g. Description field.)

NOTICE: ONCE THE FILES ARE IMPORTED/DOWNLOADED, THEY WILL BE DISPLAYED IN THE BANK CODES TABLE.

SETUP DOCUMENTATION



3. After successfully importing the bank codes, the table could look as follows:

2.2 Import/Export Function

1. Click the Import function button on the Actions tab to import the file “NCP710_BankCodes.xml”

NOTICE: IF THE TABLE ALREADY CONTAINS DATA RECORDS, THE DOWNLOAD OPTIONS ARE LIKEWISE AVAILABLE FOR IMPORT.

2. For export, click the Export function button on the Actions tab to export all the data records of the Bank Codes table. A file “NCP7.10_BankCodes” will be created.

NOTICE: ALL THE DATA RECORDS WILL BE EXPORTED. IT IS NOT POSSIBLE TO ONLY EXPORT SELECTED DATA RECORDS.

SETUP DOCUMENTATION



Further information: When a file is exported, “NCP710_BankCodes.xml” is used as title by default.

2.3 Bank Codes Table Description

2.3.1 SWIFT-Code

This field indicates the current SWIFT code of the respective bank.

NOTICE: IF A SWIFT CODE IS ADDED MANUALLY, IT WILL BE CHECKED FOR ITS LENGTH, SINCE ONLY SWIFT CODES OF EIGHT AND ELEVEN CHARACTERS ARE VALID. THE FIRST SIX CHARACTERS MUST BE LETTERS, THE FOLLOWING TWO OR FIVE MAY BE LETTERS AND/OR DIGITS.

2.3.2 Bank Branch No.

This field indicates the bank branch no. of the respective bank.

2.3.3 Name

This field indicates the name of the imported/downloaded bank.

2.3.4 ISO Country Code

This field indicates the ISO country code of the respective bank code.

NOTICE: WHEN A NEW SWIFT CODE IS RECORDED, THE ISO COUNTRY CODE FROM THE SWIFT CODE WILL BE DETERMINED AUTOMATICALLY. ADDITIONALLY, THE NO. OF ASSIGNED BANK ACCOUNTS AND CUSTOMER/VENDOR BANK ACCOUNTS WILL BE INDICATED – ARRANGED BY SWIFT CODE AND BANK BRANCH NO. – IN THE CODES SETUP.

2.3.5 Outdated

If this check box is selected, the respective bank code is considered outdated.

NOTICE: IF BANK CODES ARE SELECTED VIA THE DOWNLOAD FUNCTION (OR THE FILE IMPORT IS PERFORMED WITH A CURRENT BANK CODE FILE), ONLY THOSE BANK CODES, WHICH NO LONGER EXIST IN THE CURRENT REGISTER OF THE AUSTRIAN OR GERMAN NATIONAL BANK, ARE MARKED AS OUTDATED. THE OUTDATED FIELD CAN ALSO BE SELECTED MANUALLY BY THE USER.

2.3.6 No. of Bank Accounts (SWIFT Code)

This field indicates the no. of bank accounts, for which the respective SWIFT code is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE BANK ACCOUNTS, FOR WHICH THE RESPECTIVE SWIFT CODE IS STORED, CAN BE INDICATED.

2.3.7 No. of Bank Accounts (Bank Branch No.)

This field indicates the no. of bank accounts, for which the respective bank branch no. is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE BANK ACCOUNTS, FOR WHICH THE RESPECTIVE BANK BRANCH NO. IS STORED, CAN BE INDICATED.

2.3.8 No. of Customer Bank Accounts (SWIFT Code)

This field indicates the no. of customers (respectively their bank accounts), for which the respective SWIFT code is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE CUSTOMERS (RESPECTIVELY THEIR BANK ACCOUNTS), FOR WHICH THE RESPECTIVE SWIFT CODE IS STORED, CAN BE INDICATED.

SETUP DOCUMENTATION



2.3.9 No. of Customer Bank Accounts (Bank Branch No.)

This field indicates the no. of customers (respectively their bank accounts), for which the respective bank branch no. is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE CUSTOMERS (RESPECTIVELY THEIR BANK ACCOUNTS), FOR WHICH THE RESPECTIVE BANK BRANCH NO. IS STORED, CAN BE INDICATED.

2.3.10 No. of Vendor Bank Accounts (SWIFT Code)

This field indicates the no. of vendors (respectively their bank accounts), for which the respective SWIFT code is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE VENDORS (RESPECTIVELY THEIR BANK ACCOUNTS), FOR WHICH THE RESPECTIVE SWIFT CODE IS STORED, CAN BE INDICATED.

2.3.11 No. of Vendor Bank Accounts (Bank Branch No.)

This field indicates the no. of vendors (respectively their bank accounts), for which the respective bank branch no. is stored.

NOTICE: BY CLICKING THE DRILLDOWN FIELD, THOSE VENDORS (RESPECTIVELY THEIR BANK ACCOUNTS), FOR WHICH THE RESPECTIVE BANK BRANCH NO. IS STORED, CAN BE INDICATED.

3. Currencies Setup

In the Currencies setup, detailed information about the individual currencies can be recorded. The setup can be performed manually or by importing a CSV file.

NOTICE: WHEN SETTING UP THE CURRENCY CODES, PLEASE NOTE THAT FOR EVERY CURRENCY (EXCEPT LCY), WHICH WILL BE USED IN PAYMENTS, AN ENTRY IN THE CURRENCIES WINDOW MUST EXIST.

1. Click Currencies in the content area. 2. Record the ISO currency code of respective currency code in the ISO Code Payments field. 3. If desired, apply further adjustments to the currencies. 4. A completed setup of the currency codes after the adjustments could look as follows:

NOTICE: FOR THE LCY, NO CURRENCY CODE MAY BE RECORDED. THE ISO CURRENCY FOR THE LCY IS SELECTED IN THE PAYMENTS SETUP.

SETUP DOCUMENTATION



Further information: Currencies in Payments must be clearly identifiable, since for banks a uniform standard of designating currencies was introduced. The standard designation may differ from a certain national designation. For setting up the Payments ISO Code it is recommended to adapt the designation to the code.

NOTICE: CURRENCIES ARE PART OF THE STANDARD MICROSOFT DYNAMICS NAV APPLICATION. TO ENSURE THAT NC PAYMENTS CAN OUTPUT THE CORRECT ISO CURRENCY CODE IN CREATING THE ELECTRONIC DATA, FOR EACH CURRENCY CODE THE APPROPRIATE ISO CURRENCY CODE MUST BE STORED. PLEASE NOTE THAT FOR EVERY CURRENCY (EXCEPT LCY), WHICH WILL BE USED IN PAYMENTS, AN ENTRY IN THE CURRENCIES WINDOW MUST EXIST.

3.1 Currencies Table Description

3.1.1 ISO Code Payments

In this field the ISO code of the appropriate country is recorded. Multiple fields of the Payments Setup refer to this field. (See e.g. Payments Setup, Sender FastTab, Country/Region Code field)

4. Countries/Regions Setup

In NC Payments, the ISO Code Payments and the SEPA fields were added to the Country/Region setup. The country of a bank account determines, how transactions and/or collections can be performed. Assigning the country code is possible in the Card of the respective bank account, Countries/Regions Code field, General FastTab.

1. Click Countries/Regions in the content area. 2. Record the ISO country/region code for the appropriate country/region in the ISO Code Payments

field.

SETUP DOCUMENTATION



3. Select the SEPA check box, if the respective country is a member of the European Union/European Economic Area.

4. Edit the Address Format per Country/Region. The following options are provided:

Post Code+City

City+Post Code

City+County+Post Code

Blank Line+Post Code+City 5. Edit the Contact Address Format per country/region. The following options are provided:

First

After Company Name

Last

4.1 Countries/Regions Table Description

4.1.1 ISO Code Payments

In this field the ISO code of the respective country is recorded. Multiple fields of the Payments Setup refer to this field. (See e.g. Payments Setup, Originator FastTab, Country/Region Code field)

4.1.2 SEPA

Select the SEPA check box, if the respective country is a member of the European Union (EU)/European Economic Area (EEA).

NOTICE: COUNTRIES ARE PART OF THE STANDARD MICROSOFT DYNAMICS NAV APPLICATION. DETAILED INFORMATION ABOUT THE COUNTRY SETUP IS AVAILABLE IN THE FINANCIAL ACCOUNTING MANUAL. EVERY COUNTRY, WITH WITCH YOU WANT TO PERFORM A TRANSACTION, REQUIRES THE ISO CODE PAYMENTS. FOR COUNTRIES OF THE EUROPEAN UNION, THIS CODE IS IDENTICAL WITH THE EU COUNTRY CODE.

5. Languages

The Languages setup allows to define and to setup different language codes.

1. Click Languages in the content area. 2. Record the language code for the appropriate language and thereby assign the alternative language

text in the Alternative Language Code Payments field. 3. If desired, apply further adjustments.

5.1 Language Table Description

5.1.1 Alternative Language Code Payments

This field allows to assign standard text codes.

6. Pmt. Notification Text Setup

The subject and text for forwarding the pmt. notification via e-mail are stored in the Pmt. Notification Text setup. The text can be stored according to the language code.

1. Click Pmt. Notification Text in the content area. 2. Apply adjustments as selecting the appropriate language code, payment file text, subject or e-mail

text. 3. A completed setup of the pmt. notification texts after the adjustments could look as follows:

SETUP DOCUMENTATION



NOTICE: THE NC PAYMENTS MODULE PROVIDES THE ADDITIONAL “ALTERNATIVE LANGUAGE CODE PAYMENTS” FIELD, WHICH ALLOWS TO ASSIGN STANDARD TEXT CODES FOR THE RESPECTIVE LANGUAGE.

6.1 Pmt. Notification Text Table Description

6.1.1 Language Code

This field indicates the language in a three-character string.

6.1.2 Payment File Text

In this field the payment file text is recorded via a placeholder. When a new “pmt. notification text” data record is created, a default value is preallocated in this field.

NOTICE: AFTER EVERY PLACEHOLDER, FURTHER PLACEHOLDERS CAN BE RECORDED (SEPERATED BY “;” – E.G.: %1 PMT. NOTIFICATION NO.; …). IF NO LANGUAGE CODE IS RECORDED, THE FIELDS WILL BE PREALLOCATED IN GERMAN. IF A LANGUAGE CODE IS RECORDED, THE FIELDS WILL BE PREALLOCATED IN ENGLISH.

6.1.3 E-Mail Subject

When a new “Pmt. Notification Text” data record is created, a default value is preallocated in this field.

NOTICE: IF NO LANGUAGE CODE IS RECORDED, THE FIELDS WILL BE PREALLOCATED IN GERMAN. IF A LANGUAGE CODE IS RECORDED, THE FIELDS WILL BE PREALLOCATED IN ENGLISH.

6.1.4 E-Mail Text Exists

This field indicates, if an e-mail text is stored (Yes/No).

NOTICE: FOR SEPA/XML TRANSACTIONS WITH A PMT. NOTIFICATION, A NOTE “SEE NOTIFICATION”, FOLLOWED BY THE PMT. NOTIFICATION NO. IS RECORDED IN THE PAYMENT FILE.

SETUP DOCUMENTATION



FOR EDIFACT AND MT101 PAYMENTS, THE TEXT DEPENDS ON THE ISO COUNTRY CODE OF THE EXTERNAL BANK ACCOUNT. FOR AT, CH, AND GER, SEE PMT. NOTIFICATION, FOLLOWED BY PMT. NOTIFICATION NO. IS RECORDED. THIS LOGIC ALSO APPLIES FOR SEPA/XML PAYMENTS.

THE TEXT CAN ALSO BE STORED IN THE PAYMENTS MENU > SETUP > PMT. NOTIFICATION TEXT > PAYMENT FILE TEXT. IF NO PMT. NOTIFICATION TEXT CAN BE FOUND OR IF THE FIELD IS BLANK, THE TEXT WILL BE DETERMINED BY USING THE PREVIOUSLY DESCIBED LOGIC.

DETERMINING THE LANGUAGE CODE IS ATTEMPTED AS FOLLOWS:

1. THE CUSTOMER’S LANGUAGE CODE

2. ALTERNATIVE LANGUAGE CODE

Further information: The first attempt is to find a standard text code with the customer’s language code. If no standard text code for the respective language code can be found, Alternative Language Code Payments, which can be assigned to every language code, is used for the search, but only, if a language code is stored for the respective customer.

If there is no language code stored for the respective customer, standard text codes without a language code will be searched for. The same procedure is performed, if there is a language code stored, for which no standard text code can be found and the Alternative Language Code Payments field is blank

If no standard text code was found, the language code is indicated in the customer’s Language Code Pmt. Notification Text field in the suggestion.

If a standard text code was found, the language code of the standard text code is recorded in the Language Code Pmt. Notification Text. The language code can still be edited before sending. An e-mail can only be sent, if a Pmt. Notification Text with an E-Mail Subject exists. If an E-Mail Text is stored additionally for a Pmt. Notification Text, it is automatically recorded in the e-mail. When all the data are reviewed, every e-mail can be sent either individually or collectively.

The Pmt. Notification register allows to

Display all the necessary information for the SMTP server.

Determine, if all the sent payment notification mails are to be forwarded to another e-mail address as a copy or a blind copy (e.g. for internal archiving, notifications etc.).

When sending the e-mail, the pmt. notification report is attached as a HTML file or as a PDF file in more recent NAV releases. The Pmt. Notification E-Mail Sent field in the payment entry is set to “Yes”, and address, time and date of the e-mail are saved. If a pmt. notification is resent, this information is updated automatically.

7. XML Schemas Setup

7.1 Download Function

7.1.1 Download Function

Besides the manual setup (Import) of XML schemas, NC Payments allows to download schemas via the Download function field and to import them into the table automatically.

By default there are no data records in the XML Schemas table.

1. Click Administration > XML Schemas in the content area. 2. Go to the Actions tab in the XML Schemas window.

SETUP DOCUMENTATION



3. Click the Download function button, to start downloading the latest data records. If XML schemas already exist, the following options are provided:

“Create only new Records”

This option only creates new Payments Import Codes.

“Create new Records & overwrite existing Records”

This option overwrites/updates the available codes (E.g. Description field.)

NOTICE: ONCE THE FILES ARE IMPORTED/DOWNLOADED, THEY WILL BE DISPLAYED IN THE XML SCHEMAS TABLE.

4. After successfully importing the XML schemas, the table could look as follows:

NOTICE: SINCE THE STRUCTURE OF SEPA NOTIFICATIONS MAY CHANGE, WHEREAS THE CONTENT MOSTLY STAYS THE SAME, THE XML SCHEMAS WINDOW IS PROVIDED. IT ALLOWS TO UPDATE A NOTIFICATION WITHOUT ADDITIONAL IMPLENTATION EFFORTS OR CHANGES OF THE APPLICATION.

THE UPDATES OF NOTIFICATIONS VIA DOWNLOAD FUNCTION ARE INCLUDED IN THE SERVICE CONTRACT/ANNUAL SERVICE CHARGE.

SETUP DOCUMENTATION



7.2 Import Function/Export Function

7.2.1 Import Function

1. Click the Import function button on the Actions tab to import the “NCP710_XMLSchemas.xml” file.

NOTICE: IF DATA RECORDS ARE ALREADY AVAILABLE IN THE TABLE, THE SAME OPTIONS AS FOR DOWNLOAD ARE PROVIDED FOR IMPORT.

7.2.2 Export Function

1. Click the Export function button on the Actions tab to export all the data records of the XML Schemas table. A file “NCP7.10_XMLSchemas” will be created.

NOTICE: ALL THE DATA RECORDS WILL BE EXPORTED. IT IS NOT POSSIBLE TO ONLY EXPORT SELECTED DATA RECORDS.

Further information: When a file is exported, “NCP710_XMLSchemas.xml” is used as title by default.

7.3 XML Schemata Table Description

7.3.1 Type

This field indicates the XML schema type. The following types are available:



SEPA Direct Debit

7.3.2 Code

This field indicates the XML schema code (Version to XML pain).

7.3.3 ISO Country Code

In this field the country, for which the schema is used, is recorded (can be edited and is not required to be recorded explicitly).

NOTICE: IF AN ISO COUNTRY CODE IS STORED IN AN XML SCHEMA, THE ISO COUNTRY CODES OF THE BANK ACCOUNT AND THE SCHEMA MUST BE IDENTICAL WHEN THE PAYMENT FILE IS CREATED.

7.3.4 Description

This field provides information about the XML schema.

Example:

SCT – AT – Rulebook 3.2 – Version 2

SDD – DE – Rulebook 7.0 – Version 2.7

7.3.5 IBAN Only possible

This field indicates, if the schema supports transactions without a SWIFT code provided. If the check box is selected in the respective line, the two fields Dom. IBAN Only and Int. IBAN Only can be selected.

NOTICE: THE SWIFT CODE OF THE OWN BANK ACCOUNT MUST ALWAYS BE PROVIDED.

7.3.6 Dom. IBAN Only

If this check box is selected, domestic credit transfers are possible without a SWIFT code.

SETUP DOCUMENTATION



7.3.7 Int. IBAN Only

If this check box is selected, international credit transfers are possible without a SWIFT code.

7.3.8 IBAN or Bank Acc. No. possible

This field indicates, if the schema supports transactions without an IBAN provided. If IBAN or Bank Acc. No. possible is available, the IBAN or Bank Acc. No. check box can be selected.

NOTICE: THE IBAN OF THE OWN BANK ACCOUNT MUST ALWAYS BE PROVIDED.

7.3.9 IBAN or Bank Acc. No.

If IBAN or Bank Acc. No. is selected, the content of the Bank Acc. No. field is recorded in the payment file, if no IBAN is provided.

NOTICE: THE IBAN MUST ALWAYS BE RECORDED IN THE OWN BANK ACCOUNT.

7.3.10 Batch Booking

This field determines, how the transaction will be booked by the bank. By default, this field is blank and is not recorded on the payment file.

NOTICE: WHEN “YES” OR “NO” IS SELECTED, THE INDICATOR, IF THE RESPECTIVE TRANSACTION IS A BATCH BOOKING (“YES”) OR A SINGLE BOOKING (“NO”), IS SELECTED IN THE PAYMENT FILE.

IF AN APPROPRIATE AGREEMENT ON SINGLE BOOKINGS WITH THE CUSTOMER IS AVAILABLE, EVERY TRANSACTION WILL BE LISTED INDIVIDUALLY ON THE SENDER’S BANK STATEMENT, BUT ONLY, IF “NO” IS SELECTED. BY DEFAULT IT IS ALWAYS A BATCH BOOKING (DEFAULT/PRE-AGREED: “YES”)

7.3.11 Extended Character Set

If this check box is selected, a conversion of characters will be performed in this schema.

Valid characters:

abcdefghijklmnopqrstuvwxyz

ABCDEFGHIJKLMNOPQRSTUVWXYZ

0123456789

/-?:().,’+

Space character

Additional, automatic conversion: < into “<”, > into “>”, & into “&”, „ into “&quot”, ‘ into “'”

NOTICE: IF THE EXTENDED CHARACTER SET CHECK BOX IS NOT SELECTED, A “&” WILL AUTOMATICALLY CONVERTED INTO A “+”. ALL OTHER CHARACTERS WILL BE REPLACED BY A SPACE CHARACTER.

7.3.12 Charges Selection possible

This field indicates, if the schema allows charges selection.

7.3.13 Urgent Payment possible

This field indicates, if the schema supports urgent payments.

7.3.14 Date of Specification

This field provides internal information on the schema.

7.3.15 Last Date Modified

This field provides internal information on the schema.

SETUP DOCUMENTATION



7.3.16 In Use

This field indicates, if the selected schema is assigned to bank accounts.

NOTICE: AFTER THE DOWNLOAD, SEVERAL XML SCHEMAS ARE STORED IN THE LIST. XML/SEPA AND NON-SEPA PAYMENT FILES SUPPORT SEVERAL BATCH JOBS (B-LEVEL) WITHIN A FILE. AFTER THIS PROCESS, THE XML SCHEMAS MUST BE ASSIGNED TO THE APPROPRIATE BANK ACCOUNT.

Further information:

In more recent rulebooks, the pre-settings have changed. When such schemas are used, the transaction reference is recorded in the EndToEndID. Thereby a unique ID for a future assignment is granted.

If a payment reference was provided, it is no longer recorded in the EndToEndID. In this case, the payment reference is recorded in the file as a structured remittance info. An unstructured remittance info. is in this case no longer available/valid.

There are no changes in older schemas. The following pre-settings apply: The payment reference is still recorded in the EndToEndID (respectively “NOTPROVIDED”, if no payment reference is provided). Providing a transaction reference is no longer possible. Furthermore, when a payment reference is provided, a remittance info. is not allowed/will not be recorded in the file.

8. SEPA Mandate Text Setup

1. Click SEPA Mandate Text in the content area. 2. Click the New function button, to create a new SEPA mandate text. 3. Fill the fields with all the necessary information. 4. A completed SEPA mandate text setup could look as follows:

Before e.g. a direct debit can be performed via SEPA direct debit notification, an agreement with the business partner must be made.

The SEPA mandate form report allows to create the form from Microsoft Dynamics NAV. It is possible to store different standard text codes, depending on direct debit type and direct debit sequence.

SETUP DOCUMENTATION



8.1 SEPA Mandate Text Table Description

8.1.1 Direct Debit Type

In this field the following direct debit types can be selected.

CORE

B2B – Business to Business

COR1

All

8.1.2 Direct Debit Sequence

In this field the following direct debit sequences can be selected.

One-Off

Recurrent

All

8.1.3 Language Code

Indicates the language in a three-character band.

8.1.4 Text Exists

This field indicates, if an e-mail text is stored (Yes/No).

NOTICE: THE WINDOW FOR RECORDING THE E-MAIL TEXT CAN BE OPENED BY CLICKING “YES”/”NO”.

NOTICE: FOR CREATING A NEW SEPA MANDATE TEXT, THE LANGUAGE CODE MUST BE IDENTICAL WITH THE CUSTOMER’S LANGUAGE CODE (CUSTOMER > FOREIGN TRADE FASTTAB > LANGUAGE CODE FIELD).

9. Bank Accounts Setup

To perform SEPA transactions, the appropriate schemas from the XML Schemas section must be assigned to a bank account.

1. Click Bank Accounts in the content area. 2. Mark the appropriate bank account and click Manage > Edit. 3. Open the Transfer FastTab to display the extended fields of the payment.

NOTICE: FOR EDITING THE FIELDS ON THE TRANSFER FASTTAB, COUNTRY/REGION CODE (GENERAL FAST TAB), BANK ACC. NO., BANK BRANCH NO., IBAN AND SWIFT CODE MUST ALSO BE FILLED WITH INFORMATION.

Edit the remaining fields on the Transfer FastTab.

9.1 Transfer FastTab

9.1.1 SEPA Credit Transfer Schema

In this field the appropriate XML schema from the XML Schemas section is recorded.

9.1.2 SEPA Direct Debit Schema


SETUP DOCUMENTATION



9.1.3 Non-SEPA Credit Transfer Schema


9.1.4 Bank Currency Code (PAYMUL/DIRDEB)

In this field the currency code, with which the bank keeps the account, is stored.

NOTICE: IF THE BANK KEEPS THE ACCOUNT WITH THE LCY, THE FIELDS CAN BE LEFT BLANK.

9.1.5 Sender Identification (PAYMUL/DIRDEB)

In this field a unique character band, which identifies the sender, is recorded. This character band must be agreed with the sender.

NOTICE: THE CHARACTER BAND IS OBLIGATORY AND MUST NOT CONTAIN SPACE CHARACTERS.

9.1.6 Receiver Identification (PAYMUL/DIRDEB)

In this field a unique character band, which identifies the receiver, is recorded. This character band must be agreed with the receiver.

NOTICE: THE CHARACTER BAND IS OBLIGATORY AND MUST NOT CONTAIN SPACE CHARACTERS.

9.1.7 SWIFT-Code MT101 Agency

In this field the SWIFT code of the agency is recorded.

9.2 Customer Bank Acc. Setup.

The bank account setup allows to perform bank collections or transactions correctly.

1. Click Customers in the content area. 2. Mark the appropriate customer and click the Navigate tab > Bank Accounts. 3. Mark the appropriate bank account and click Manage > Edit function button.

NOTICE: FOR EDITING BANK ACCOUNTS, COUNTRY/REGION CODE (GENERAL FAST TAB), BANK ACC. NO., BANK BRANCH NO., IBAN AND SWIFT CODE (TRANSFER FASTTAB) MUST ALSO BE FILLED WITH INFORMATION.

4. Mark the Main Bank Account check box of the bank account which you want to use for the payment.

NOTICE: IF THE CUSTOMER USES ONLY ONE BANK ACCOUNT, IT IS NOT NECESSARY TO SELECT THE CHECK BOX.

5. Edit the remaining fields on the Transfer FastTab in the now opened Customer Bank Account Card window (of the respective bank account).

NOTICE: VIA PAYMENTS > CUSTOMERS > BANK ACCOUNTS > SEPA MANDATES ANY NUMBER OF SEPA MANDATES CAN BE ASSIGNED TO ONE CUSTOMER BANK ACCOUNT.

THE FINAL DIRECT DEBIT CREATED FIELD IN THE CUSTOMER SEPA MANDATES WINDOW DISPAYS, IF A PAYMENT ENTRY WITH THE DIRECT DEBIT SEQUENCE “FINAL” EXISTS.

THE FIRST DIRECT DEBIT CREATED FIELD CAN BE SELECTED MANUALLY, IF NO PAYMENT FILES EXIST FOR A MANDATE, WHICH WAS USED IN OTHER SYSTEMS OR BEFORE A DATA TRANSFER.

FOR DETERMINING THE MANDATE IN THE PAYMENT SUGGESTION, THE FOLLOWING IS CONSIDERED:

MANDATES, FOR WHICH THE DATE OF MANDATE FIELD IS FILLED WITH A DATE ON OR BEFORE THE CURRENT DATE.

SETUP DOCUMENTATION



MANDATES, FOR WHICH THE MANDATE VALID UNTIL FIELD IS LEFT BLANK OR FILLED WITH A DATE AFTER OR ON THE CURRENT DATE.

Further information: When a mandate was found it will be determined, if there are already assigned payment entries.

For one-off mandates the application checks, if the First Direct Debit Created field is selected or if payment entries already exist. In this case the next mandate will be searched. Otherwise the mandate will be suggested.

For recurring mandates the application checks, if a payment entry with the direct debit sequence “Final” exists. In this case the next mandate will be searched. Otherwise the mandate will be suggested. The direct debit sequence will be set to “First”, if no payment entry exists so far and the “First Direct Debit Field Created” field is not selected. Otherwise the direct debit sequence will be set to “Recurring”.

Changing information in the journal or assigning mandates in the journal manually, which was/were not stored in the customer bank account, is still possible. The Mandate ID field can also be selected via a Lookup field in the journal.

9.3 Vendors Bank Account Setup

The vendor bank accounts are required to perform transactions to vendors.

1. Click Vendors in the content area. 2. Mark the appropriate vendor and click the Navigate tab > Bank Accounts. 3. Mark the appropriate bank account and click Manage > Edit

NOTICE: FOR EDITING BANK ACCOUNTS, COUNTRY/REGION CODE (GENERAL FAST TAB), BANK ACC. NO., BANK BRANCH NO., IBAN AND SWIFT CODE (TRANSFER FASTTAB) MUST ALSO BE FILLED WITH INFORMATION.

4. Mark the Main Bank Account check box of every bank account, which shall be used for the payments.

NOTICE: IF THE CUSTOMER USES ONLY ONE BANK ACCOUNT, IT IS NOT NECESSARY TO SELECT THE CHECK BOX.

SETUP DOCUMENTATION



10. Technical Annex

Documents

NC Payments Documentation - NAVAX documentation is intended to explain the connections within the application. It is designed as a reference which provides all the information needed