Skip Headers
JD Edwards EnterpriseOne Applications Localizations for European Reporting and SEPA Processing Implementation Guide
Release 9.1

Part Number E15104-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Fields in the SEPA Payments XML File

This appendix contains the following topics:

Block A: Message Root

The following message root appears before the Group Header section in the XML scheme:

<?xml version="1.0" encoding="utf-8" ?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http:⇒
//www.w3.org/2001/XMLSchema-instance">
- <CstmrCdtTrfInitn>

Block B: Group Header Elements

A SEPA XML file includes one group header. The group header must be present in the file. Elements for the group header are:

Tag Description XML tag Source of Data Comments
Message identification <MsgId> The system generates an internal identification that consists of the company number, bank account number, and next number (74/01). Maximum of 35 characters.
Creation date and time <CreDtTm> The system generates a date and time stamp at the time of formatting of the message. The format is YYYY-MM-DDThh:mm:ss
Number of transactions <NbOfTxs> The system provides the total number of credit transfer transaction blocks in the message.

For example, if a message contains 1 group header, 1 payment information block and 4 credit transfer information blocks. In this case the number of transactions will set to 4.

Maximum of 15 numeric characters.
Control sum <CtrlSum> The system provides the total of all individual euro amounts included in the message. None
Initiating party name <Nm> The system prints the mailing name of the company that pays the voucher. The system gets this information from the Address by Date table (F0116). Maximum of 70 characters.
Initiating party organization ID <Id> This system uses the tax ID of company address number. None
Initiating party identification issuer <Issr> The system uses the value in the Initiating Party Identification Issuer processing option to determine the initiating party issuer. If you leave this processing option blank, the system does not display this tag on the report. None

Block C: Payment Information Elements

One or more blocks of payment information are included in a SEPA payment file. Payment information elements are:

Tag Description XML tag Source of Data Comments
Payment information ID <PmtInfId> The system generates an internal code. Maximum of 35 characters.
Payment method <PmtMtd> The system assigns the hard-coded value of TRF. None
Batch booking <BtchBookg> The system assigns the hard-coded value of False. None
Instruction priority <InstrPrty> The system uses the value in the Instruction Priority processing option to determine the instruction priority.

The values are HIGH and NORM.

None
Service level code <SvcLvl>

<Cd>

The system assigns the hard-coded value of SEPA. None
Local instrument code <LclInstrm>

<Cd>

The system assigns the hard-coded value of TRF. None
Category purpose code <CtgyPurp>

<Cd>

The system uses the value in the Category Purpose processing option to determine the instruction priority. None
Requested execution date <ReqdExctnDt> The system uses the payment date value from F04572. KKDGJ. None
Debtor name <Dbtr>

<Nm>

The system uses the mailing name from F0116.MLNM. Maximum of 70 characters.
Debtor postal address – country <PstlAdr>

<Ctry>

The system uses the first two lines of the address of the company. The system retrieves these values from F0116.ADD1 and F0116.ADD2.

The system uses the country of the company.

None
Debtor postal address line <AdrLine> The system uses two lines of address information. None
Debtor organization identification <Id> The system uses the tax ID of the initiating party. None
Debtor account ID IBAN <IBAN> The system uses the value from the IBAN field of the payment bank account of the debtor. None
Debtor account ID currency <Ccy> The system requires the currency of the debtor bank account for SEPA core payments. The system assigns the hard-coded value of EUR. None
Debtor agent BIC <BIC> The system uses the value from the BIC field of the payment bank account of the debtor. None
Ultimate debtor name <UltmtDbtr>

<Nm>

The system uses the mailing name from F0116.MLNM. Maximum of 70 characters.
Ultimate debtor organization ID <Id> This system uses the tax ID of the ultimate debtor. None
Charge bearer <ChrgBr> The system assigns the hard-coded value of SLEV. None

Block D: Credit Transfer Transaction Information

One or more credit transfer transaction information blocks are included in the XML file for each payment information block. Elements are:

Tag Description XML Tag Source of Data Comments
Instruction identification <InstrId> The system generates a unique key for each payment, comprised of the bank account, supplier, payment date, and the check control number. None
End to end identification <EndToEndId> The system generates a unique key for each payment, comprised of the bank account, supplier, payment date, and the check control number. None
Instructed amount <InstdAmt> The system displays the amount of the credit transfer in euro. The amount must be 0.01 or more and 999999999.99 or less. Only two decimal places are allowed.
Creditor agent BIC <CdtrAgt> The system uses the BIC code of supplier's bank account. None
Creditor name <Cdtr> The system uses the mailing name from F0116.MLNM. None
Creditor postal address country <PstlAdr>

<Ctry>

The system uses the first two lines of the address of the company. The system retrieves these values from F0116.ADD1 and F0116.ADD2.

The system uses the country of the supplier.

None
Creditor postal address line <AdrLine> The system allows two lines of address information. None
Creditor organization identification <Id> The system uses the tax ID of the supplier address. None
Creditor account ID IBAN <CdtrAcct>

<IBAN>

The system uses the IBAN code of the supplier bank account. None
Ultimate creditor name <UltmtCdtr>

<Nm>

The system uses the value from F0116.MLNM. None
Ultimate creditor organization ID <Id> The system uses the tax ID of the ultimate creditor. None
Purpose code <Purp>

<Code>

The system uses the value in the Payment Purpose processing option to determine the purpose code. This element describes the underlying reason for the payment transaction. The debtor uses this element to provide information to the creditor concerning the nature of the payment transaction.

The following group of elements specify the remittance information. The system uses the values in the Remittance Information Mode and Inform multiple invoices processing options to populate this element. The Remittance Information Mode processing option specifies the mode in which the system informs the remittance information. The Inform multiple invoices processing option specifies whether there are multiple occurrences of structured remittance or unstructured remittance per remittance information element. For SEPA core payments, the system allows only one occurrence of either structured or unstructured info.

Tag Description XML Tag Source of Data Comments
Unstructured <Ustrd> In an unstructured form, complete this element with the invoice number, invoice date, invoice total amount, invoice payment amount, and invoice discount amount. The element is optional, depending on the value in the Remittance Information Mode processing option.
Structured <Strd> Hard coded tag. The element is optional, depending on the value in the Remittance Information Mode processing option.
Code <CdOrPrtry>

<Cd>

The system assigns the hard-coded value of SCOR. None
Issuer <Issr> This system specifies the supplier name, which is the tag name of element creditor. None
Reference <Ref> The system specifies the invoice number. None

Reviewing an Example of XML code for SEPA Core Payments

Review the following example of the XML code for SEPA core payments:

<?xml version="1.0"???? encoding="utf-8" ?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http:⇒
//www.w3.org/2001/XMLSchema-instance">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>ABC/060928/CCT001</MsgId>
<CreDtTm>2008-09-28T14:07:00</CreDtTm>
<NbOfTxs>3</NbOfTxs>
<CtrlSum>2400.56</CtrlSum>
<InitgPty>
<Nm>Cobelfac</Nm>
<Id>
<OrgId>
<Othr>
<Id>0468651441</Id>
<Issr>KBO-BCE</Issr>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId> ABC/4560/2008-09-25</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<BtchBookg>false</BtchBookg>
<PmtTpInf>
<InstrPrty>HIGH </InstrPrty>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
<LclInstrm>
<Cd>TRF<Cd>
</LclInstrm>
<CtgyPurp>
<Cd>SUPP<Cd>
</CtgyPurp>
</PmtTpInf>
<ReqdExctnDt>2008-09-29</ReqdExctnDt>
<Dbtr>
<Nm>XXXXX</Nm> 
<PstlAdr>
<Ctry>CC</Ctry>
<AdrLine>XXXXXX </AdrLine>
<AdrLine>XXXXXX </AdrLine>
</PstlAdr>
<Id>
<OrgId>
<Othr>
<Id>0468651441</Id>
</Othr>
</OrgId>
</Id>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>BE68539007547034</IBAN>
</Id>
<Ccy>EUR</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>AAAABE33</BIC>
</FinInstnId>
</DbtrAgt>
<UltmtDbtr>
<Nm>XXXXX</Nm>
<Id>
<OrgId>
<Othr>
<Id>0468651441</Id> 
</Othr>
</OrgId>
</Id>
</UltmtDbtr>
<ChrgBr>SLEV</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId> ABC/4562/2008-09-28</InstrId>
<EndToEndId>ABC/4562/2008-09-28</EndToEndId>
</PmtId>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<Amt>
<InstdAmt Ccy="EUR">535.25</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>CRBABE22</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>SocMetal</Nm>
<PstlAdr>
<Ctry>BE</Ctry>
<AdrLine>Hoogstraat 156</AdrLine>
<AdrLine>2000 Antwerp</AdrLine>
</PstlAdr>
<Id>
<OrgId>
<Othr>
<Id>0468651441</Id> 
</Othr>
</OrgId>
</Id>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>BE43187123456701</IBAN>
</Id>
</CdtrAcct>
<UltmtCdtr>
<Nm>XXXXX</Nm>
<Id>
<OrgId>
<Othr>
<Id>0468651441</Id>
</Othr>
</OrgId>
</Id>
<UltmtCdtr>
<Purp>
<Cd>GDDS</Cd>
</Purp>
<RmtInf>(*)
<Ustrd>Invoice No/Invoice Date/ Invoice Total Amount/ Invoice Payment amount⇒
/ Invoice Discount Taken </Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>

(*) If Structured:

<RmtInf>
<Strd>
<CdtrRefinf>
<Tp>
<CdOrPrtry>
<Cd>SCOR</Cd>
</CdOrPrtry>
<Issr> Vision Operations</Issr>
</Tp>
<Ref>010806817183</Ref>
</CdtrRefInf>
</Strd>
</RmtInf>

Note:

The system displays transactions with a negative amount with positive sign in the XML, i.e., when the payment control group has some debit statement (negative payment). The system displays this negative payment with positive sign in the InstdAmt tag because the XML format (Payments - Maintenance 2009 document) only allow positives amounts.