eMandate Amendment request from Creditor to Routing Service

The following table describes which elements are sent to the Routing Service by the Creditor in the eMandate Amendment request.

eMandates mapping to ISO pain.010: Creditor to Routing Service

Index	ISO Message Element	eMandates Requirement
`<Document>`
`-<MndtAmdmntReq>`
`--<GrpHdr>`
3	Message Identification `<MsgId>`	Identifies the eMandate message from the Creditor. Max35Text Format: maxLength: 35, minLength: 1
4	Creation Date Time `<CreDtTm>`	Creation date and time of the eMandate message by the Creditor. UTC time format (YYYY-MM- DDThh:mm:ss.sssZ) ISO 8601.
`--<UndrlygAmdmntDtls>`
`---<AmdmntRsn>`
`----<Rsn>`
8	Code `<Cd>`	`eMandate.AmendmentReason`. The reasoncode for amending the eMandate. Must be 'MD16'.Means that amendment was requested by Debtor.
`---<Mndt>` (contains the info on the Amendment eMandate)
10	Mandate Identification `<MndtId>`	`eMandate.eMandateID` See ID's for format
11	Mandate Request Identification `<MndtReqId>`	Must be: `NOTPROVIDED.` Will be filled by the Routing Service later with `eMandate.TransactionID`eMAN
`----<Tp>`
`-----<SvcLvl>`
14	Code `<Cd>`	The identification code of the Scheme. Must be: SEPA
`-----<LclInstrm>`
16	Code `<Cd>`	The identification code of the Instrument (Core /B2B). Must be: CORE to indicate a Core direct debit or B2B to indicate a B2B direct debit. The mixing of different Local Instrument values is not allowed in the same message.
`----<Ocrncs>`
18	Sequence Type `<SeqTp>`	`eMandate.SequenceType.` Indicates type of eMandate: one-off Direct Debit or recurring. Format: 'OOFF' or 'RCUR'
`--- <Rsn>` Optional
27	Proprietary `<Prtry>`Optional (only when provided)	`eMandate.Reason`eMAN
`--<Cdtr> (`Must be empty, Intentionally not filled by the Creditor, as this will be filled by the Routing Service)
`--<Dbtr>` May be empty
`---` <Id>
`----<PrvtId>`
`-----<Othr>`
46	ID <`Id`> Optional	`eMandate.DebtorReference .` Reference ID that identifies the Debtor to the Creditor. Issued by the Creditor. Format: Max35Text. eMAN
`--<DbtrAgt>`
`---<FinInstnId>`
49	BICFI `<BICFI>`	`Debtor.DebtorBankID .` BIC of the Debtor Bank of the eMandate that needs to be amended. See ID's for format. Note: This ID differs from `Debtor.DebtorBankID` in index 66 in case the Debtor has a bankswitch eMAN
`-- <RfrdDoc>` Usage rule: only one occurrence is allowed
`--- <Tp>`
`---- <CdOrPrtry>`
54	Proprietary `<Prtry>`	`eMandate.PurchaseID. The` purchaseID that acts as a reference for the Creditor from eMandate to a purchase-order. Format: Max35Text eMAN
`---<OrgnlMndt>` (Contains the information of the original eMandate that needs to be amended)
`----<OrgnlMndt>`
58	Mandate Identification `<MndtId>`	`eMandate.eMandateID`. The emandate ID of the to be amended (e)Mandate. Does not change with amendment, so must be the same as the `eMandate.eMandateID` in field 10
`-----<Cdtr/>` Must be left empty
`-----<Dbtr/>` Must be left empty
`-----<DbtrAcct>`
`------<Id>`
63	IBAN `<IBAN>`	`Debtor.IBAN`. Must contain the IBAN of the original to be amended (e)Mandate eMAN
`-----<DbtrAgt>`
`------<FinInstnId>`
66	BICFI `<BICFI>`	`Debtor.DebtorBankID.` Must contain the `Debtor.DebtorBankID` of the original (e)Mandate. Note: This ID differs from `Debtor.DebtorBankID` in index 49 in case the Debtor has a bankswitch eMAN

Example Message

<!--see iDx docs for non-container iDx message content-->
<container>
	<Document
		xmlns="urn:iso:std:iso:20022:tech:xsd:pain.010.001.04"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
		<MndtAmdmntReq>
			<GrpHdr>
				<MsgId>Message1234567890</MsgId>
				<CreDtTm>2015-04-29T13:42:08.708Z</CreDtTm>
			</GrpHdr>
			<UndrlygAmdmntDtls>
				<AmdmntRsn>
					<Rsn>
						<Cd>MD16</Cd>
					</Rsn>
				</AmdmntRsn>
				<Mndt>
					<MndtId>1234567890</MndtId>
					<MndtReqId>NOTPROVIDED</MndtReqId>
					<Tp>
						<SvcLvl>
							<Cd>SEPA</Cd>
						</SvcLvl>
						<LclInstrm>
							<Cd>CORE</Cd>
						</LclInstrm>
					</Tp>
					<Ocrncs>
						<SeqTp>OOFF</SeqTp>
					</Ocrncs>
					<Cdtr />
					<Dbtr>
						<Id>
							<PrvtId>
								<Othr>
									<Id>12345-67890</Id>
								</Othr>
							</PrvtId>
						</Id>
					</Dbtr>
					<DbtrAgt>
						<FinInstnId>
							<BICFI>TESTNL2A</BICFI>
						</FinInstnId>
					</DbtrAgt>
				</Mndt>
				<OrgnlMndt>
					<OrgnlMndt>
						<MndtId>1234567890</MndtId>
						<Cdtr />
						<Dbtr />
						<DbtrAcct>
							<Id>
								<IBAN>NL28INGB0007597526</IBAN>
							</Id>
						</DbtrAcct>
						<DbtrAgt>
							<FinInstnId>
								<BICFI>INGBNL2A</BICFI>
							</FinInstnId>
						</DbtrAgt>
					</OrgnlMndt>
				</OrgnlMndt>
			</UndrlygAmdmntDtls>
		</MndtAmdmntReq>
	</Document>
</container>
<!--see iDx docs for non-container iDx message content-->

Incassomachtigen/eMandates Implementation docs for Merchants and MSP's

eMandate Amendment request from Creditor to Routing Service

Analytics

Related content