eMandate Initiation request from Creditor to Routing Service

The following table describes which elements are sent to the Routing Service by the Creditor in the eMandate initiation request. Only for the elements that have actual values the Index and element requirement is given.

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

Index	ISO Message Element	eMandates Requirement
`<Document>`
`-<MndtInitnReq>`
`--<GrpHdr>`
3	Message Identification `<MsgId>`	Identifies the initial 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.
`--<Mndt>`
6	Mandate Identification `<MndtId>`	`eMandate.eMandateID`
7	Mandate Request Identification `<MndtReqId>`	Must be: `NOTPROVIDED.` Will be filled by the Routing Service later with `eMandate.TransactionID`eMAN
`--<Tp>`
`---<SvcLvl>`
10	Code `<Cd>`	The identification code of the Scheme. Must be: SEPA
`---<LclInstrm>`
12	Code `<Cd>`	The identification code of the Instrument (Core /B2B). Must be: CORE to indicate a Core direct debit and B2B to indicate a B2B direct debit. The mixing of different Local Instrument values is not allowed in the same message.
`--<Ocrncs>`
14	Sequence Type `<SeqTp>`	`eMandate.SequenceType .` Indicates type of eMandate: one-off Direct Debit or recurring. Format: 'OOFF' or 'RCUR'
20	Maximum Amount`<MaxAmt Ccy="EUR">`Optional	`eMandate.MaxAmount`eMAN. Only allowed in B2B, not in Core
`--- <Rsn> Optional`
23	Proprietary `<Prtry>`Optional	`eMandate.Reason`eMAN
`--<Cdtr/> (`Must be empty, Intentionally not filled by the Creditor, as this will be filled by the Routing Service)
`--<Dbtr>`
`---` <Id>
`----<PrvtId>`
`-----<Othr>`
42	ID `<Id>`	`eMandate.DebtorReference .` Reference ID that identifies the Debtor to the Creditor. Issued by the Creditor. Format: Max35Text eMAN
`--<DbtrAgt>`
`---<FinInstnId>`
45	BICFI `<BICFI>`	`Debtor.DebtorBankID .` BIC of the Debtor Bank. See ID's for format eMAN
`-- <RfrdDoc>` only one occurrence is allowed
`--- <Tp>`
`---- <CdOrPrtry>`
50	Proprietary `<Prtry>`	`eMandate.PurchaseID.` A purchaseID that acts as a reference for the Creditor from eMandate to a purchase-order. Format: Max35Text eMAN

^{Pain.009 message (new eMandate)}

Example Message

<!--see iDx docs for non-container iDx message content-->
<container>
	<Document
		xmlns="urn:iso:std:iso:20022:tech:xsd:pain.009.001.04"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
		<MndtInitnReq>
			<GrpHdr>
				<MsgId>Message1234567890</MsgId>
				<CreDtTm>2015-04-29T13:29:51.974Z</CreDtTm>
			</GrpHdr>
			<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>
		</MndtInitnReq>
	</Document>
</container>
<!--see iDx docs for non-container iDx message content-->