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. Complex types are elements that don't have an actual value themselves. They function as containers for sub-elements that having the actual values.

Index	ISO Message Element	eMandates Requirement
1	+ Message root	Mandatory
2	+ Group Header	Mandatory EPC. Complex type
3	++ Message Identification	Mandatory EPC Max35Text Format: maxLength: 35, minLength: 1
4	++ Creation Date Time	Mandatory EPC DateTime
5	+ Mandate	Mandatory EPC
6	++ Mandate Identification	Mandatory EPC eMandate.eMandateID
7	++ Mandate Request Identification	Mandatory eMAN Must be: NOTPROVIDED
8	++ Type	Mandatory EPC, Complex type
9	+++ Service Level	Mandatory EPC, Complex type
10	++++ Code	Mandatory EPC The identification code of the Scheme EPC Usage Rule: Only 'SEPA' is allowed.
11	+++ Local Instrument	Mandatory EPC, Complex type
12	++++ Code	Mandatory EPC The identification code of the Scheme EPC Usage Rule: Only 'CORE' is allowed to indicate a Core direct debit. Usage Rule: The mixing of different Local Instrument values is not allowed in the same message.
13	++ Occurrences	Mandatory EPC, Complex type
14	+++ Sequence Type	Mandatory EPC eMandate.SequenceType
15	+++ Frequency	Optional eMAN Usage rule: Not allowed in current implementation
16	++++ Type	Not allowed
17	++++ Period	Mandatory eMAN (if Frequency is provided), Complex type
18	+++++ Type	Mandatory eMAN (if Frequency is provided) eMandate.FrequencyPeriod
19	+++++ CountPerPeriod	Mandatory eMAN (if Frequency is provided) eMandate.FrequencyCount
20	++ Maximum Amount	Optional eMAN eMandate.MaxAmount Usage rule: Not allowed in current implementation
21	++ Reason	Optional eMAN, Complex type
22	+++ Code	Not allowed
23	+++ Proprietary	Mandatory eMAN (if Reason is provided) eMandate.Reason Usage rule: should not contain Sequence Type value
31	++ Creditor	Mandatory EPC Must be empty, Intentionally not filled further by the Creditor, as this will be filled by the Routing Service
38	++ Debtor	Mandatory EPC, Complex type May be empty
39	+++ Identification	Optional eMAN, Complex type
40	++++ Private Identification	Optional eMAN, Complex type
41	+++++ Other	Optional eMAN, Complex type
42	++++++ ID	Optional eMAN eMandate.DebtorReference
43	++ Debtor Agent	Mandatory eMAN, Complex type
44	+++ Financial Institution Identification	Mandatory eMAN, Complex type
45	++++ BICFI	Mandatory eMAN Debtor.DebtorBankID
46	++ Referred Document	Optional eMAN, Complex type Usage rule: only one occurrence is allowed
47	+++ Type	Mandatory eMAN (if Referred Document is provided), complex type
48	++++ Code Or Proprietary	Mandatory eMAN (if Referred Document is provided), complex type
49	+++++ Code	Not allowed
50	+++++ Proprietary	Mandatory eMAN (if Referred Document is provided), eMandate.PurchaseID

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

<?xml version="1.0" encoding="UTF-8"?>
<AcquirerTrxReq
	xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0"
	xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" productID="NL:BVN:eMandatesCore:1.0">
	<createDateTimestamp>2015-04-29T13:29:51.974Z</createDateTimestamp>
	<Issuer>
		<issuerID>TESTNL2A</issuerID>
	</Issuer>
	<Merchant>
		<merchantID>1234512345</merchantID>
		<subID>000000</subID>
		<merchantReturnURL>https://betaalvereniging.nl/returnPage.php?param1=true&amp;param2=3%202</merchantReturnURL>
	</Merchant>
	<Transaction>
		<expirationPeriod>PT15M</expirationPeriod>
		<language>nl</language>
		<entranceCode>12345ABCDE</entranceCode>
		<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>
	</Transaction>
	<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
		!-- Message Signature is placed. See iDx Signature section for more details--!
	</Signature>
</AcquirerTrxReq>

eMandate Initiation request from Creditor to Routing Service

Must be: NOTPROVIDED