Understanding the XML File for SEPA Direct Debits

To process SEPA direct debits for JD Edwards EnterpriseOne, you use the JD Edwards EnterpriseOne Automatic Debit program (P03B571). The Automatic Debit program generates the SEPA Direct Debit Extractor report (R743005) or the SEPA Direct Debit Multiple XML Extractor report (R743005A) from the standard Auto Debit table (F03B575). These reports generate the required XML file or files and saves them in the Business Intelligence Publisher (BI Publisher) folders (Release 9.2 Update).

You can either generate a single XML file for all of the mandate sequence types or multiple XML files, each corresponding to a mandate sequence type. You use the SEPA Direct Debit Extractor report (R743005) to generate a single XML file and the SEPA Direct Debit Multiple XML Extractor report (R743005A) to generate multiple XML files (Release 9.2 Update).

Note: To generate multiple XML files, the system uses the R743005A program, which in turn uses the R743005 program to generate individual XML files for each mandate sequence type. Therefore, you must set the Bank Format Version (R743005) processing option for the R743005A program to specify the version of the R743005 program that the system will use.

From the F03B575 table and the SEPA Direct Debit Mandate table (F743002), the SEPA Direct Debit Extractor report and the SEPA Direct Debit Multiple XML Extractor report extract the receipts of the debtors who have active mandates associated within the period that you process the collection (Release 9.2 Update). For each debtor, the report creates a record in the XML file with the mandate data and the receipt information.

To generate the XML file for SEPA direct debits, the system selects the active mandates based on the following criteria:

  • Local Instrument Type

  • G/L Bank Account

  • Creditor Address Number

  • Debtor Address Number

  • Ultimate Debtor Address Number

To generate the XML in the format that is required by the banks for direct debits, the system uses Oracle's BI Publisher, which is integrated with the JD Edwards EnterpriseOne software.

You run the XML in the automatic debit process to generate the Automatic Debit Statement report, Errors report, and Structured and Unstructured Remittance reports for both single and multiple invoices. You select a version to print the specific report. When you run the XML, the embedded BI Publisher for JD Edwards EnterpriseOne invokes a report definition. This definition relates the report-specific templates to the report and presents the output in the specified format.

This table lists the reports that are generated, the report definitions and versions associated with the reports, and the output format of the reports:

Report

Report Definition

Source Version

Output Format

SEPA Direct Debit Errors Detail

None

None

PDF

SEPA Direct Debit Auto-Debit Statement

None

None

PDF

SEPA Direct Debit - Strc - Mult Remittance XML

RD743005A

XJDE0001

XML

SEPA Direct Debit - Error and Detailed Collection

RD743005B

XJDE0001

PDF

SEPA Direct Debit - Unstr - Mult Remittance XML

RD743005C

XJDE0002

XML

SEPA Direct Debit - Error and Detailed Collection

RD743005G

XJDE0002

PDF

SEPA Direct Debit - Struct - Singl Remittance

RD743005D

XJDE0003

XML

SEPA Direct Debit - Error and Detailed Collection

RD743005H

XJDE0003

PDF

SEPA Direct Debit - Unstru - Singl Remittance

RD743005F

XJDE0004

XML

SEPA Direct Debit - Error and Detailed Collection

RD743005I

XJDE0004

PDF

The reports are described as follows:

SEPA Direct Debit Errors Detail: The R03B571 program generates the SEPA Direct Debit Errors Detail report to inform the errors generated by the Auto Debit (R03B571) process. If the R03B571 program finds errors, the XML file will not be generated. Instead, the program generates this report in PDF format (Release 9.2 Update).

SEPA Direct Debit Auto-Debit Statement: The R743005 program generates the SEPA Direct Debit Auto-Debit Statement report to inform the receipts included in the XML that is generated by the SEPA Direct Debit Extractor process. If no errors occur when you run the R03B571 program, the R03B575 program displays the processed invoices in the PDF and the R743005 program exports the processed invoices into the XML.

SEPA Direct Debit - Strc - Mult Remittance XML: You must run the XJDE0001 version of the report to generate the SEPA Direct Debit Structured Multiple Remittance XML output that you send to the bank for processing the direct debits.

SEPA Direct Debit - Error and Detailed Collection: You can run the XJDE0001 version of the report to generate the PDF output with error and detailed collection information for structured transaction involving multiple invoices.

SEPA Direct Debit - Unstr - Mult Remittance XML: You must run the XJDE0002 version of the report to generate the SEPA Direct Debit Unstructured Multiple Remittance XML output that you send to the bank for processing the direct debits.

SEPA Direct Debit - Error and Detailed Collection: You can run the XJDE0002 version of the report to generate the PDF output with error and detailed collection information for an unstructured transaction involving multiple invoices.

SEPA Direct Debit - Struct - Singl Remittance XML: You must run the XJDE0003 version of the report to generate the SEPA Direct Debit Structured Single Remittance XML output that you send to the bank for processing the direct debits.

SEPA Direct Debit - Error and Detailed Collection: You can run the XJDE0003 version of the report to generate the PDF output with error and detailed collection information for a structured transaction involving a single invoice.

SEPA Direct Debit - Unstru - Singl Remittance XML: You must run the XJDE0004 version of the report to generate the SEPA Direct Debit Unstructured Single Remittance XML output that you send to the bank for processing the direct debits.

SEPA Direct Debit - Error and Detailed Collection: You can run the XJDE0004 version of the report to generate the PDF output with error and detailed collection information for an unstructured transaction involving a single invoice.

Note: BI Publisher for JD Edwards EnterpriseOne does not enable the use of proof and final modes.

The JD Edwards EnterpriseOne system supports the creditor transmitting the XML file to the creditor bank. You can instruct your bank to initiate transactions once both parties sign the mandate and you prenotify the debtor. The system supports both recurrent and one-off collections.

(Release 9.2 Update) When you run the R03B571 program, the system validates the data sent to the XML file. If any of the mandatory information is missing, the R03B571 program does not generate any XML file and reports the error in the PDF file.

Note: (Release 9.2 Update) When you run the R03B571 program, the system performs the SEPA validations only if you set the value of the Bank Format Program processing option as R743005 or R743005A.
Note: (Release 9.2 Update) If there are multiple invoices for multiple payors, Payor A, Payor B, and Payor C, and there is an error during the validation process for one of the invoices for Payor A when you run the R03B571 program, then the system will process the invoices for the other payors that passed the validation but not for Payor A.

These are the validations and the associated errors if the validations fail:

Validations

Error Codes

Error Description

Mandate exists.

K74E053

There is no mandate associated with the debtor who's being processed.

Mandate is active and the mandate active date is equal to or before the date used to process the debit transfer.

K74E054

Associated mandate is not active or the mandate active date is in the future.

Mandate is not canceled.

K74E055

Mandate being processed has been canceled.

Currency code is valid.

K74E060

The currency code specified for EURO in processing options of R743002 does not match the transaction currency code of one of the records being processed from Auto Debit Invoice Select and Build table (F03B575).

There is no blank value in the processing options fields.

K74E061

The processing option fields cannot be left blank.

Creditor mailing name is set up in the Address Book system.

K74E062

Creditor mailing name is not set up in the Address Book system. You must set up the mailing name using Address Book Revisions program. (P01012).

Creditor tax Id is set up in the Address Book system.

K74E063

Creditor tax Id or additional tax Id is not set up in the Address Book system. You must set up the tax Id or additional tax ID using Address Book Revisions program (P01012).

Creditor mailing address is set up in the Address Book system.

K74E064

Creditor mailing address is not set up in the Address Book system. You must set up the mailing address using Address Book Revisions program (P01012).

Creditor country is set up in the Address Book system.

K74E065

Creditor country is not set up in the Address Book system. You must set up the creditor country using Address Book Revisions program (P01012).

Creditor IBAN is set up in the system.

K74E066

Creditor IBAN is not set up in the system.You must set up IBAN using IBAN By G/L Bank Account program (P700030).

Creditor BIC is set up in the system.

K74E067

Creditor BIC (SWIFT Code) is not set up.

You must set up the BIC (SWIFT Code) using Revise Bank Information program (P0030G).

Creditor bank account is SEPA.

K74E068

Creditor bank account is not set up as a SEPA bank account. You must set up the bank account as a SEPA bank account using SEPA Account Setup program (P0030G).

Ultimate creditor mailing name is set up in the Address Book system.

K74E069

Ultimate creditor mailing name is not set up. You must set up the mailing name using Address Book Revisions program (P01012).

Ultimate creditor tax Id is set up.

K74E070

Ultimate creditor tax Id is not set up. You must set up the tax Id using Address Book Revisions program (P01012).

Debtor mailing name is not set up.

K74E071

Debtor mailing name is not set up. You must set up the debtor mailing name using Address Book Revisions program (P01012).

Debtor tax Id is set up.

K74E072

Debtor tax Id is not set up.

You must set up the tax Id or additional tax Id using Address Book Revisions program (P01012).

Debtor mailing address is set up.

K74E073

Debtor mailing address is not set up. You must set up the mailing address using Address Book Revisions program (P01012).

Debtor country is set up.

K74E074

Debtor country is not set up.

You must set up the country using Address Book Revisions program (P01012).

Debtor IBAN is set up.

K74E075

Debtor IBAN is not set up. You must set up the IBAN using IBAN By Address Number Bank Account program (P700030).

Debtor BIC is set up.

K74E076

Debtor BIC (SWIFT Code) is not set up. You must set up the BIC (SWIFT Code) using Bank Account by Address program (P0030A).

Debtor bank account is SEPA.

K74E077

Debtor bank account is not set up as a SEPA bank account. You must set up the SEPA bank account using SEPA Account Setup program (P0030A).

Ultimate debtor mailing name is set up.

K74E078

Ultimate debtor mailing name is not set up.

You must set up the mailing name using Address Book Revisions program (P01012).

Ultimate debtor tax Id is set up.

K74E079

Ultimate debtor tax Id is not set up.

You must set up the tax Id using Address book Revisions program (P01012).

Note: The R03B571 program validates that all the receipts selected are in euro. The code that represents euro currency is the one that you entered in the processing option. If the receipt is not in euro, the report shows an error and the information for that receipt is not included in the XML file. You must set up the Auto Debit report (R03B571) to process the receipt in euro.

The R743005 and R743005A reports update the following fields on the SEPA Direct Debit Mandate table when an XML file is successfully generated for a mandate (Release 9.2 Update):

  • Last collection date (this is the last transaction date of the mandate).

  • Transactions counter (this is the number of direct debits under the mandate).

  • Active field with N if the type of mandate is one-off or last so that the report does not process recurrent direct debit transactions in the future.