| Master Data SetupTo set up SEPA functionality in LN: - Specify additional settings in Common and Finance/Logistics (direct
debit only)
- Create an XML layout
- Maintain mapping elements
- Modify payment method
- Create direct debit mandates (optional)
Specifying additional settings in Common and Financials The first step in setting up master data for SEPA direct
debits is to specify additional settings in the following sessions: - General Company Data (tccom0502m000)
- Business Partners (tccom4500m000) (optional)
- CMG Parameters (tfcmg0500m000)
In the General Company Data (tccom0102s000) details session, under Registration, specify a creditor identifier and,
optionally, a business entity identifier. Field | Description |
---|
Creditor Identifier | The creditor identifier is required in the SEPA direct debit file. The identifier
specified here will be defaulted to the Direct Debit Mandate (tfcmg0127m000) session, where it can be
overwritten. | Business Entity Identifier | The business entity identifier can
optionally be used as an identifier for the direct debit company in the direct
debit file. |
- In the Business Partner (tccom4100s000) details session, on the Detailed tab, specify the business entity identifier
(optional).
- In the CMG Parameters (tfcmg0100s000) details session, on the Direct Debits tab, specify a number group and series
to be used for direct debit mandates.
Creating an XML layout The first step in setting up master data for SEPA credit
transfers and direct debits is to define an XML layout. To create an XML layout: In the XML Payment/Receipt Layouts (tfcmg0524m000) session, specify a new layout
code. The XML Payment/Receipt Layout (tfcmg0624m000) starts. - Define the layout header fields.
- Click Save Function.
- On the Actions menu, click Initialize.
Note - XML layouts are version controlled.
- The status can be Initial, Active, or Expired.
Field | Description |
---|
Layout | The XML layout
code. | Version | The version number, generated
automatically. | Receipts/Payments | Indicates whether the XML
layout refers to payments or receipts. | Separator | The character used for
concatenation of mapping elements when multiple LN data is mapped to an
XML tag. | Group Payment Information | If this check box is selected, payment and direct debit
files payment information tags are grouped together. Consequently, the payment
information tag (PmtInf) is specified only once for the combination of bank,
payment method and (planned) payment/debit date. If this check box is cleared, the payment information is
specified for every composed payment/receipt line for the payment or direct
debit batch. | Status | XML version status, see
below. | Convert XML Output | No Conversion The XML file will be created in UTF-8 format. Basic Character Set After creating the XML file in UTF-8 format, characters
that do not comply with the EPC SEPA specification are converted to dots. Extended Character Set After creating the XML file in UTF-8 format, characters
that do not comply with the EPC SEPA specification are converted to characters
that better represent the original characters. For example, the '&'
character would be converted to the '+' character.
| Amount Format | The amount formats, for example decimal and thousand
separator sign, can be overruled. For more information on Amount Format refer
to Amount format. | Date Format | The date formats can be overruled. For more information
on Date Format refer to Date format | UTC Format | UTC time |
Command | Description |
---|
Initialize | An empty layout can be initialized. All tags in the ISO 20022
format will be initialized. Initialization can be repeated if the status of the
layout is Initial. Initialization can be performed with an
overwrite option (which equals reinitialization), or without overwrite. In the
latter case, existing tags (including mapped elements) are not modified and
missing tags will be added with the Select check box cleared. Note When you activate an XML layout, tags that are not
selected will be retained. | Activate | Sets the status of the XML layout to Active. | Expire | Sets the status of the XML layout to Expired. | Generate XML | Starts the Select Payment / Direct debit Batch for XML File Generation (tfcmg0224m000) session. |
Viewing an XML layout In the XML Payment/Receipt Layouts (tfcmg0524m000) and XML Payment/Receipt Layout (tfcmg0624m000) sessions, the View XML Layouts command allows you to display the XML
layout in a (GBF) tree view. In this view, various colors and icons indicate
whether mappings are missing. Right-clicking an XML tag will take you straight
to the appropriate XML layout line for viewing or editing. XML layout version status Status | Description |
---|
Initial | If the status is Initial, you can change layout details. | Active | A layout with status Active cannot be changed. To make changes, copy the current layout to a new
version number. To use the layout with the new version
number: - Set the status of the active layout to Expired.
- Set the status of the layout with the new version
number to Active.
Note Alternatively, you can set the status of the layout with
the new version number to Active at once. The status of the previous version will
then be set to Expired automatically. | Expired | The layout can no longer be used. |
LN generates default XML tags and their mappings to payment/ receipt elements.
These default values XML tags and their mappings are based on the
recommendations as laid down in the EPC (European Payments Council)
rulebooks. Maintaining XML tags The EPC rulebooks and guidelines allow for bank or
country-specific requirements in the XML file to be sent to the bank. These
local or specific requirements can be fulfilled using optional XML tags.
Therefore, you can add, delete, or edit XML tags in the initialized default
layout. To delete an XML tag, select the appropriate XML-tag line and
use the Delete command in the session menu. If the XML tag type is mandatory
because it was specified as a minimum requirement in the EPC Rulebook, the
layout line cannot be deleted. Note An XML tag can be deleted only if any child tags were
deleted. To Edit an
XML tag (layout status: Initial), double-click the required XML-tag line to
start the XML Payment/Receipt Layout Lines (tfcmg0125m000) details
session. Field | Description |
---|
XML Tag Identifier | The XML tag number. | XML Tag | The XML tag name. | XML Tag Description | The XML tag description. | XML Tag Type | Defines a set of values and the allowable operations on
those values. This field indicates what sort of value is expected for this tag.
This is compared with the element type of mapping elements. If a mismatch
occurs, the user is informed. For mapping XML elements to LN records, the
following data types exist: Attribute For example, currency code, quantity Boolean Yes/No Date Absolute date Decimal Number Node Only for parents String Alphanumeric code UTC Date Time-zone-independent date
| Parent XML Tag Identifier | The number in this field indicates the parent
of the current XML tag, which is used to construct the XML tree
structure. | Sequence in Parent | A parent tag can have multiple child tags. This field
indicates the sequence in which the current tag occurs for the
parent. | Mandatory | If this check box is selected, the layout line cannot
be deleted. | Select | If this check box is selected, the XML tag will be
included in the file generation. | Map to Payment Element | If this check box is selected, the tag value for this
layout line will be set based on one or more LN table fields or
variables. Fixed text means the value specified by the user will be used as a
(static) tag value. Map to Payment Element and Fixed/Prefix Text are mutually exclusive. | Fixed/Prefix Text | See the Map to Payment Element field | Maximum Text Characters | The maximum number of text characters
allowed. | Choice | If this check box is selected, the tag is a mutually
exclusive choice element. If two child elements are marked as Choice, the user is informed about this when both
tags are selected. Note This field is predefined and merely indicates whether
the tag is considered to be a choice field according to the EPC rulebooks. | Transactional | If this check box is selected, the data for this line
is based on the actual transaction. The transactional tags are repeated as many
times as there are transactions. | Sort Sequence | The sequence of the XML tag in the file. Sort Sequence is a system-generated sequence of the
XML file. After activation, all selected lines should have a non-zero value
here. This field is for technical reasons only and disabled for user
input. |
Caution! Do not to change XML Tag Type, Parent XML Tag Identifier, or Sequence in Parent values unless the format that is
required by the bank necessitates this change. Guidelines for editing - If the Select check box is selected, almost all fields are
editable. However, if the tag is generated as, for example, the payment
identifier, it only makes sense to change the following fields:
- XML Tag Description
- Mandatory
- Map to Payment Element
- Fixed/Prefix Text
- Maximum Text Characters
- Choice
- The value of the Sort Sequence field is generated and cannot be
changed.
- Only when you create a new tag can you change the following
fields:
- For a particular local requirement, you can define that a tag
is mandatory. If the Map to Payment Element check box is selected, this means that the tag must
be mapped, or is already mapped in case of a default generated tag, to data in LN. If this check box is cleared, the
tag is specified at runtime and/or a fixed text can be added. The Fixed/Prefix Text field and the Map to Payment Element check box are mutually exclusive.
To add an XML tag, in the XML Payment/Receipt Layout (tfcmg0624m000) session, on the XML Payment/Receipt Layout
Lines tab, click the New Layout Details button. Exporting and importing XML layouts In the XML Payment/Receipt Layouts (tfcmg0524m000) session, commands available on the appropriate menu
allow you to export or import XML layouts through the following
sessions: - Export XML Payment/Receipt Layouts (tfcmg0224m100)
- Import XML Payment/Receipt Layouts (tfcmg0224m200)
After you export an XML layout, you might want to modify the
layout code and version number of the export file. Suppose, for example, you
have exported layout TEST version 3 from your test environment, and wish to import it in your live environment as
layout SEPA version 1. In that case,
proceed as follows: - Open the export file.
- Search for the LayoutCode tag.
- Replace
TEST with SEPA . - Change the value of the Version tag from
3 to 1 .
Export XML Payment/Receipt Layouts (tfcmg0224m100) Use this session to export XML layouts to an
XML file. Selection Range | Layout | The XML layout
code. | Version | The version number. | Options | Only Latest Active Version | If this check box is selected, only the latest version
(status Active) of the selected XML layouts is exported. | Export | Export Location | Select Local System or Server,
as required. | Export Directory | Click the browse button to select the directory in
the Browse For Folder dialog box. | Export File Name | Click the browse button to select the file in the
Open dialog box in the selected
directory. |
Import XML Payment/Receipt Layouts (tfcmg0224m200) Use this session to import XML layouts from
an XML file. Import | Import Location | Select Local System or Server,
as required. | Import Directory | Click the browse button to select the
directory in the Browse For Folder dialog box. | Import File Name | Click the browse button to select the
file in the Open dialog box in the selected directory. | Options | Error Report | If this check box is selected, LN prints a report of
any errors that occur. |
| |