/
eMandates pain message data elements

eMandates pain message data elements

Nr.

eMandates name

Description

Formatting rules

1

Creditor.AddressLine1

The Creditor's address – line 1
P.O. Box or street name + building + add-on (if any)

Max70Text

2

Creditor.AddressLine2

The Creditor's address – line 2
Postcode, City

Max70Text

3

Creditor.Country

Country of the postal address of the Creditor

[A-Z]{2,2}

4

Creditor.CreditorID

Direct Debit ID of the Creditor
(NL: IncasantID)

As described in AT-02 (Identifier of the Creditor) in the EPC SDD Implementation Guidelines.

5

Creditor.Name

Name of the Creditor

Max70Text

6

Creditor.TradeName

Name of the company (or daughter- company, or label etc) for which the Creditor is processing eMandates. May only be used when meaningfully different from Creditor.Name

Max70Text

7

DateTime

Date and time

UTC time format (YYYY-MM- DDThh:mm:ss.sssZ), ISO 8601.

8

Debtor.AccountName

Account holder name of the account that is used for the eMandate

Max70Text

9Debtor.DebtorBankID BIC of the Debtor BankBIC (ISO 9362)
10

Debtor.IBAN

Debtor's bank account number

IBAN (ISO 13616)

11

Debtor.SignerName

Name of the person signing the eMandate. In case of multiple signing, all signernames must be included in this field, separated by comma's. If the total would exceed the maximum of 70 characters, the names are cut off at 65 characters and ,e.a. is added after the last name.

Max70Text

12

eMandate.AmendmentReason

The reasoncode for amending the eMandate

Must be 'MD16' 
Means that amendment was requested by Debtor.

13

eMandate.DateTimestamp

Date and time at which the eMandate has been approved by the Debtor in the Debtor Bank domain

UTC time format (YYYY-MM- DDThh:mm:ss.sssZ), ISO 8601.

14

eMandate.DebtorReference

Reference ID that identifies the Debtor to the Creditor. Issued by the Creditor

Max35Text

15eMandate.eMandateID

ID that uniquely identifies the Mandate and is issued by the Creditor. 

Max35Text. Must be restricted to the SEPA character set

16

eMandate.MaxAmount 
ONLY USED IN B2B

The maximum amount per Direct Debit. Must be accompanied by the currency code. Only used in B2B, not in Core

An amount of 0.01 or more and 999999999.99 or less with no fractional digits, or two fractional digits separated by a dot. ActiveCurrencyCode: EUR

17

eMandate.PurchaseID

A purchaseID that acts as a reference from eMandate to the purchase-order

Max35Text

18

eMandate.Reason

Indicates the reason of the mandate

Max70Text

19

eMandate.SequenceType

Indicates type of eMandate: one-off Direct Debit or recurring.

'OOFF' or 'RCUR'

20eMandate.TransactionID eMandateTransaction ID. The value for this ID is taken from the Transaction.transactionID 16 digit number 
21

Message.NameID

Refers to the type of validation request that preceded the acceptance report

3 values:

  • Issuing
  • Amendment
  • Cancellation (only used in B2B, not Core)
22

ValidationService.ValidationReference

The reference to the eMandate validation log of the Validation Service. This reference is created by the Validation Service

Max128Text

23eMandate.FrequencyCount
CURRENTLY NOT USED
The number of the direct debit batch during a specific eMandate.FrequencyPeriodMaximum 18 numbers. No decimals allowed
24eMandate.FrequencyPeriod
CURRENTLY NOT USED
Period for the number of (eMandate.FrequencyCount) direct debitsSee eMandate.FrequencyPeriod codelist

eMandates data elements