Setup
BIC
Business Identifier Code.
IBAN
International Bank Account Number.
SEPA Creditor Identifier (CI)
This identifier relates to mandate reference. It is used by the payer's bank and the debtor’s bank to verify each SEPA Direct Debit.
Unique mandate reference (UMR)
This identifier is given by the creditor to mandate. It must be unique for each mandate in combination with the SEPA Creditor Identifier.
- Assignment (GESTCA)
- Task management (GESABT)
- Import/export templates (GESAOE)
- Payment methods (GESTAM)
- Companies (GESCPY)
- Structures (GESANM)
- Sequence number values (MODCPT)
- Parameter values (ADPVAL )
General parameters
Open: Setup > General parameters > Parameter values
You can set parameters to provide default entry values. The following group is applicable to SEPA mandates:
TC (Common data) chapter / SDD (SDD management) group
To add or amend the default parameter, click Detail from the Actions menu.
SDDMGT |
Manage SDD (SEPA Direct Debit) mandates?
You must set this parameter to Yes.
Defined at the folder level.
Context: Control is applied to sales invoices. |
Sequence numbers
Open: Setup > General parameters > Sequence number definition > Assignment
Open: Setup > General parameters > Sequence number definition > Structures
Open: Development > Utilities > Miscellaneous > Sequence number values
Unique mandate reference structure
The unique mandate reference is a mandatory information in the SDD process and must be communicated to the debtor. Therefore, the mandate reference should be included in the mandate letter signed by the debtor. The Unique Mandate Reference is not an editable field in Sage X3.
In order to automatically manage mandate numbers in Sage X3, the sequence number structure for the management of SEPA mandate must be defined.
- The sequence number Assignment function (GESTCA) defines the sequence number which is used. Sequence numbers used by SEPA mandates are in the module A/P-A/R accounting.
- Document type. Mandate reference.
- Sequence. SDD.
- Manual:
- Set to Yes if the Mandate reference is manually entered.
- Set to No if the Mandate reference is assigned automatically.
- To generate SEPA mandate sequence numbers automatically the components that make up the structure of the sequence numbers have been defined as follows. You can use the Structures function (GESANM) to change the components to suit your organization.
Sequence number counter Description Default components SDD Mandate reference 5-character company, plus
10-character complement, plus
5 sequential numbers.
For example, BE078ZZZ050D00000008.
Complement. In the case of a direct debit, the complement refers to the Customer code.
Structures (GESANM): SEPA mandates number structure (predefined)
- Now set the sequence number start value. You can do this using one of the following methods:
- Select the Reset to zero check box in the Miscellaneous block.
- Use the Sequence number values function (MODCPT), if available, to set the start value for each component of the counter.
Sequence number values (MODCPT): SDD - SEPA mandates sequence number
Limitations
Length of the unique mandate reference
The SEPA rulebooks allow up to 35 characters for the unique mandate reference. But it Sage X3, the counter length is limited to 20 characters. The automatically generated UMRs are also limited to 20 characters.
As a reminder, the customer code (supplement) can be set to a maximum of 15 characters.
Companies
Open: Setup > Organizational structure > Companies
Like the mandate reference, the SEPA Creditor Identifier (CI) is a mandatory information in the SDD process. It has been created in the SDD scheme to allow debtors as well as their banks to return to the creditor for refunds and complaints, and to check the existence of a mandate upon presentation of a collection by the creditor.
These actions needed a unique identification of creditors, meaning that each CI only refers to one creditor. A single creditor, however, is free to use more than one CI or only to use one CI for the initiation of collections in all SEPA countries. The CI is part of the unique mandate-key composed of the CI and the unique mandate reference.
Setup
-
Acct section:
- SEPA creditor identifier. The CI structure is based on the following algorithm:
- Position 1-2 populated with the ISO country code.
- Position 3-4 populated with the check digit according to ISO 7064 Mod 97-10.
- Position 5-7 populated with the Creditor Business Code (if not used then populated with ZZZ).
Position 8 onwards populated with the Creditor National Identifier. This is the country specific part of the identifier which corresponds to the national identifier of the creditor. The Creditor National Identifier part of the CI varies by country.
- SEPA creditor identifier. The CI structure is based on the following algorithm:
Limitations
One CI per company
In Sage X3, only one CI can be set per company. It is not possible to create different versions of the same CI or to have several CI per company.
- For France: FR12ZZZ123456
- For Belgium: BE78ZZZ050D000000008
- For Portugal: PT97ZZZ123456
- For Germany: DE97ZZZ12345678901
Import/export templates
Open: Setup > Usage > Imports/Exports > Import/export templates
Templates delivered with your system for importing and exporting SEPA mandates are available in the Import/export templates function (GESAOE).
MDT template
Use this template to import and export mandates.
This table lists the available data elements. Depending on the direction of flow, some data elements are mandatory.
No. |
Table |
Field |
Description |
---|---|---|---|
1 |
MANDATE |
CPY |
Company |
2 |
MANDATE |
UMRNUM |
Mandate reference |
3 |
MANDATE |
DES |
Description |
4 |
MANDATE |
ACS |
Access code |
5 |
MANDATE |
STA |
Status |
6 |
MANDATE |
TYP |
Type |
7 |
MANDATE |
PAYTYP |
Payment type |
8 |
MANDATE |
SIGDAT |
Signature date |
9 |
MANDATE |
SIGCTY |
Signature place |
10 |
MANDATE |
MAIMDTFLG |
Main mandate |
11 |
MANDATE |
FNLFLG |
Final |
12 |
MANDATE |
PAYNBR |
No. of direct debits |
13 |
MANDATE |
WIOFIRSEQ |
Without first sequence |
14 |
MANDATE |
CPYADD |
Company address code |
15 |
MANDATE |
MIGFLG |
Migration |
16 |
MANDATE |
NTLMIGIDT |
Migration national ID |
17 |
MANDATE |
BPCNUM |
Customer code |
18 |
MANDATE |
BPCADD |
Customer address code |
19 |
MANDATE |
IBACOD |
IBAN code |
20 |
MANDATE |
AMDFLG |
Amendment flag |
21 |
MANDATE |
FNLDBT |
Final debtor |
22 |
MANDATE |
UDLCON |
Underlying contract |
23 |
MANDATE |
SITNAM |
Name of signatory |
24 |
MANDATE |
SITFNC |
Function of signatory |
MDTEXP template
This table lists the available data elements.
No. |
Table |
Field |
Description |
---|---|---|---|
1 |
MANDATE |
CPY |
Company |
2 |
MANDATE |
UMRNUM |
Mandate reference |
3 |
MANDATE |
DES |
Description |
4 |
MANDATE |
ACS |
Access code |
5 |
MANDATE |
STA |
Status |
6 |
MANDATE |
TYP |
Type |
7 |
MANDATE |
PAYTYP |
Payment type |
8 |
MANDATE |
SIGDAT |
Signature date |
9 |
MANDATE |
SIGCTY |
Signature place |
10 |
MANDATE |
MAIMDTFLG |
Main mandate |
11 |
MANDATE |
FNLFLG |
Final |
12 |
MANDATE |
PAYNBR |
No. of direct debits |
13 |
MANDATE |
ENDDAT |
Mandate end date |
14 |
MANDATE |
WIOFIRSEQ |
Without first sequence |
15 |
MANDATE |
CPYADD |
Company address code |
16 |
MANDATE |
MIGFLG |
Migration |
17 |
MANDATE |
NTLMIGIDT |
Migration national ID |
18 |
MANDATE |
BPCNUM |
Customer code |
19 |
MANDATE |
BPCADD |
Customer address code |
20 |
MANDATE |
IBACOD |
IBAN code |
21 |
MANDATE |
BICCOD |
BIC code |
22 |
MANDATE |
TOTSDDPAY |
Total direct debits |
23 |
MANDATE |
NBRSDDPAY |
Number of payments |
24 |
MANDATE |
AMDFLG |
Amendment flag |
25 |
MANDATE |
FNLDBT |
Final debtor |
26 |
MANDATE |
UDLCON |
Underlying contract |
27 |
MANDATE |
SITNAM |
Name of signatory |
28 |
MANDATE |
SITFNC |
Function of signatory |
29 |
COMPANY |
SCINUM |
SEPA creditor ID |
30 |
BPCUSTOMER |
BPCNAM |
Company name |
31 |
BPADDRESS |
BPADES |
Description |
32 |
BPADDRESS |
BPAADDLIG(0) |
Address line |
33 |
BPADDRESS |
BPAADDLIG(1) |
Address line |
34 |
BPADDRESS |
BPAADDLIG(2) |
Address line |
35 |
BPADDRESS |
POSCOD |
Postal code |
36 |
BPADDRESS |
CTY |
City |
37 |
BPADDRESS |
SAT |
Country |
38 |
BPADDRESS |
CRY |
Country |
39 |
BPADDRESS |
CRYNAM |
Country name |
40 |
BPADDRESS |
TEL(0) |
Telephone |
41 |
BPADDRESS |
TEL(1) |
Telephone |
42 |
BPADDRESS |
TEL(2) |
Telephone |
43 |
BPADDRESS |
TEL(3) |
Telephone |
44 |
BPADDRESS |
TEL(4) |
Telephone |
45 |
BPADDRESS |
FAX |
Fax |
46 |
BPADDRESS |
MOB |
Mobile phone |
47 |
BPADDRESS |
WEB(0) |
Internet address |
48 |
BPADDRESS |
WEB(1) |
Internet address |
49 |
BPADDRESS |
WEB(2) |
Internet address |
50 |
BPADDRESS |
WEB(3) |
Internet address |
51 |
BPADDRESS |
WEB(4) |
Internet address |
52 |
BPADDRESS |
FCYWEB |
Website |
53 |
HISTOMDT |
PAYDAT |
Direct debit date |
54 |
HISTOMDT |
PAYNUM |
Payment no. |
55 |
HISTOMDT |
FRMNUM |
Slip no. |
56 |
HISTOMDT |
SEQTYP |
Sequence type |
57 |
HISTOMDT |
DPT |
Dispute reason |
58 |
HISTOMDT |
AMT |
Amount |
59 |
HISTOMDT |
CUR |
Currency |
Payment methods (GESTAM)
Open: Common data > BP tables > Payment methods
Use the Payment methods function (GESTAM) to define payment methods applicable to SEPA mandate processes and functions.
Setup
In the Management block, select the SSD management check box to specify that the payment method is linked to the SDD mandate management mode (SEPA Direct Debits). In this case, the Statement field becomes inactive. Therefore, it is not possible to enter a statement code for a SDD mandate type. In other words, the SDD open items never appear on a statement. Conversely, the Statement field becomes active when the SDD management box is cleared.
Task management
Open: Usage > Batch server > Task management
Use the Task management function (GESABT) to create new batch tasks or to modify the characteristics of existing tasks.
Mandate validation (VALMDT)
Setup of the task for mandate validation: VALMDT.
Mandate closing (MDTCLS)
Setup the task for mandate closing: MDTCLS.