business process proceduressapidp/... · web viewtherefore, in addition to the entity described in...

Banking Services 8.0

October 2014

English

SAP Payment Engine for SEPA Direct Debit (L81)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices SAP Payment Engine for SEPA Direct Debit (L81): BPD

Copyright

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE of 47

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE of 47


Contents

SAP Payment Engine for SEPA Direct Debit.......................................................................................51 Purpose........................................................................................................................................ 52 Prerequisites................................................................................................................................ 6

2.1 Master Data and Organizational Data...................................................................................62.2 Multiple Entities – Independent Testing.................................................................................62.3 Disclaimer............................................................................................................................. 7

3 Process Overview Table...............................................................................................................84 Process Steps............................................................................................................................ 12

4.1 DM initiated SEPA Direct Debits.........................................................................................124.1.1 Verifying XML Message...............................................................................................124.1.2 Process Payment Orders in Payment Engine..............................................................124.1.3 Execute activities on due date......................................................................................154.1.4 Displaying Payment Item (Informational)......................................................................17

4.2 Incoming customer payment file..........................................................................................184.2.1 Importing file.................................................................................................................184.2.2 Process incoming Payment Orders in the Payment Engine.........................................204.2.3 Executing activities on due date...................................................................................224.2.4 Displaying Payment Items on current and clearing accounts (Informational)...............24

4.3 Incoming interbank payment file..........................................................................................254.3.1 Importing file.................................................................................................................254.3.2 Process incoming Payment Orders in the Payment Engine.........................................274.3.3 Executing activities on due date...................................................................................284.3.4 Displaying Payment Items on current and clearing accounts (Informational)...............30

4.4 Exception Handling.............................................................................................................314.4.1 Refund of a Payment Transaction................................................................................314.4.2 Return of a Payment Transaction based on not existing account................................35

5 Appendix.................................................................................................................................... 395.1 1_SEPA_DD_Pain.008.001.02_RDS_mix.xml....................................................................395.2 2_SEPA_DD_Pacs.003.001.02_RDS_internal.xml.............................................................425.3 2_SEPA_DD_Pacs.003.001.02_RDS_internal_AccNotExist.xml........................................45

© SAP SE of 47


SAP Payment Engine for SEPA Direct Debit

1 Purpose The purpose of this document is to describe or support testing of a complete entire account life cycle with SEPA direct debit functionality, from the creation of the mandate to the execution of the payment order in Payment Engine.The following assumptions/ guidelines are considered:

The SDD scheme considered is CORE (from bank to customer or customer to customer transactions)

Amount must be in Euro Country of Receiver must be a SEPA member IBAN and BIC replace account number and sort code

In this document are explained all the relevant processes to all process related to an account life cycle (that is: account creation, replication, and so on) are explained in detail in the corresponding BPD document. This also applies for all concerning to Master Data management (that is: Business Partner creation, Bank key creation) that is explained in the Master Data Procedure documentation.The SEPA Direct Debit (SDD) Process scheme starts with the creation of a mandate that basically is a signed agreement between debtor and creditor where the debtor authorizes to be direct debited in its bank account due to a payment. Afterwards, the creditor must transfer the required data to its bank to initialize the direct debit process and also must inform the debtor that this process is ongoing.With the initialization of the direct debit process triggered with the Creditor’s Bank a series of clearing messages between the Creditor’s and the Debtor’s Bank with ISO20022-XML-Format.Finally, as a result of the mentioned messages between the banks the Direct Debit is executed at the bank of the Debtor.Referenced scenarios from the following documents:

Business Scenarios References

Payment transactions initiated by Deposits Management

Account closure process with account closure order with transfer to reference account at an external bank

“L34 – Current Account Life Cycle”

Create notice on amount with forward order incl. collections from an external reference account

“L35 – Savings Account Life Cycle”

Opening of saving account with start amount via SDD

“L35 – Savings Account Life Cycle”

Incoming customer payment transactions

Bank receives a customer file with collection of invoices


Incoming interbank payment transactions

Bank receives a file from the clearing house with transactions for their customer (SDD)


Exception Handling

© SAP SE of 47


Refund of an SEPA Direct Debit that was posted several weeks before based on customer objection


Return of an SEPA Direct Debit based on not existing account


2 Prerequisites

2.1 Master Data and Organizational DataDefault ValuesThe organizational structure and master data of your company have been created in your Banking Services system during implementation, to the extent it is required to execute this rapid-deployment solution (for example, business partner, reference account, or internal accounts).The organizational structure reflects the structure of your company with respect to some specific settings such as name, currency, and so on.

2.2 Multiple Entities – Independent TestingOnce the content of this rapid-deployment solution has been implemented, it will provide:

One CMU (contract managing unit) with associated Bank Posting Area (0001), which is described in detail in this Business Process Documentation

Up to 20 additional CMUs with associated bank posting areas, which can be used to represent a branch structure and to test the business processes independently (since the posting date is set for each bank posting area and if several people are testing independently, this might differ for each person).

The scope of this rapid-deployment solution is to provide one contract managing unit with associated bank posting area to run through the defined life cycle of deposit accounts as described. It may, however, be necessary to have several independent entities for using / testing the processes within the life cycle of these deposit accounts.Therefore, in addition to the entity described in detail in this Business Process Documentation, the possibility of using several additional entities is also mentioned.These entities can be used to:

Represent a type of branch structure Test the business processes independently

Independent testing with several entities might be necessary due to the following reasons: The posting date is set for each bank posting area and must be changed to simulate a

deposit life cycle If several people are testing independently, this might differ for each person

For this reason, in addition to the example mentioned within the following sections for entity:

Bank Key (*) Bank Name (*) Bank Posting Area (BPA)

Contract Manager (CMU) (*)

Initial Posting Date for the BPA (*)

12345678 RDS Bank 0001 RDS Bank 03.01.2000

20 additional entities are provided as follows:

© SAP SE of 47


Bank Key (*) Bank Name (*) Bank Posting Area (BPA)

Contract Manager (CMU) (*)

Initial Posting Date for the BPA (*)

11111111 RDS Bank Branch 1 BR01 RDS Bnk BR01 03.01.2000




















If the entities were personalized when the solution was implemented, the values for testing are adjusted accordingly.To facilitate independent testing, each of the above-mentioned entities can be assigned to a single tester. This enables you to avoid conflicts in the posting date settings and testing can be performed completely independently.Note that each life cycle of a deposits account starts with an initial Posting Date for the Bank Posting Area on 03.01.2000. If you want to test more than one life cycle for each Bank Posting Area, you have to adjust the starting date of the life cycle to the current Posting Date. All other dates mentioned for examples in the respective life cycles have to be adjusted accordingly. If you are not sure what the current posting date is, you can check it as follows:For more details, refer to the corresponding section in the Master Data Procedure Document “Set Posting Date for Payment Transactions” (155.89)The necessary activities to be performed in this step are:

Check Posting Date for Payment Transactions in Deposit Management System Check Posting Date for End-of-Day Processing

2.3 Disclaimer

© SAP SE of 47


Note that certain process steps described in this document will only lead to the specified results if you use the proposed currency (EUR) and the proposed amounts.If you use another currency (such as USD), the proposed amounts would have to be adjusted.

3 Process Overview TableAll processes described in this life cycle are executed in the Banking Services system.

Process step / Step of Scope item

External process reference

Business condition

Business role (not technical role for BP)

Transaction code Expected results

DM initiated SEPA Direct Debits

Verifying XML Message

Payment transaction was sent to Payment Engine via Web service

SXMB_MONI XML message successfully sent to Payment Engine.

Process Payment Orders in Payment Engine

Process the direct debit sent from Banking Services in the Payment Engine.

/PE1/PO_EXPERT Payments are processed in Payment Engine and outgoing file created.

Execute activities on due date

Advance the reconciliation date to the due date and process all queued transactions

Display Payment Item (Informational)

Check the balance of the nostro account and the customer account.

Payment item posted on nostro account and customer

© SAP SE of 47




Business condition



account in Banking Services.

Incoming customer direct debit file

Import file Import the file for the respective converter ID with multiple processing controls

/PE1/FH_IPM_EXPERT An appropriate file is imported.

Process Payment Orders in Payment Engine

Process the direct debit sent from Banking Services in the Payment Engine.

/PE1/PO_EXPERT Payments are processed in Payment Engine and outgoing file created.



Display Payment Item (Informational)


BCA_CN_KFG Ordering party item, recipient party items and clearing item are posted to the respective accounts.

Incoming interbank direct debit file

© SAP SE of 47




Business condition



Import file Import the file for the respective converter ID with multiple processing controls

/PE1/FH_IPM_EXPERT An appropriate file is imported.

Displaying Payment Items on current and clearing accounts

Check the balance of the clearing and current accounts.

BCA_CN_KFG Ordering party posted on clearing account. Recipient party items are posted to the recipient account.



Displaying Payment Items on current and clearing accounts


Payment item posted on nostro account and customer account in Banking Services.

Exception Handling

Refund of a Payment Transaction

Refund of SEPA Direct Debit based on customer objection.

BCA_PAYMITEM_RETURN

A new payment order is created.The customer

© SAP SE of 47




Business condition



account is credited with the original amount with a backdated value date.A refund interest is calculated and posted to the PL Clearing account.

© SAP SE of 47


4 Process Steps 4.1 DM initiated SEPA Direct Debits4.1.1 Verifying XML Message

UseAfter creating the payment transaction order in Banking Services a web service call is triggered to Payment Engine. This step process is used to verify the XML message for the SEPA direct debit sent from Banking Services to Payment Engine via web service.

Procedure1. Access the Integration Engine using the following navigation path:

SAP Menu Enter transaction code for Integration Engine Monitoring

Transaction code SXMB_MONI

2. Select the menu entry “Monitor for Processed XML Messages” via Integration Engine Monitoring.

3. On the Selection screen on the tab Standard Selection Criteria – End of Execution, choose From Date/Time and To Date/Time and enter your execution data.

4. On the monitor screen choose your message and verify the following values:

Field name User action and values Comment

Overall Status Status “Processed successfully” Icon “checkered flag”

Sender Interface

Receiver Interface

5. Open your XML message by double click6. Validate values in the XML message that they match the values of the payment order initiated in

Banking Services.

4.1.2 Process Payment Orders in Payment Engine

UseThis step processes the payment orders sent from Banking Services to Payment Engine via service call. Payment Engine posts the ordering party item to a reconciliation account with BS and routes the recipient transaction to the respective external channel including the needed clearing posting.

Procedure1. Access the transaction using the following navigation path:

SAP Menu Payment Engine Payment Order Management Edit Payment Orders (Expert)

Transaction code /PE1/PO_EXPERT

2. In the Select Clearing area dialog-box make the following setting:

© SAP SE of 47



Clearing Area Enter your clearing area,for example, RDS000

3. On the Dynamic Selection screen on the left side in the Restriction of Data Set for Orders, choose Created on and enter the following data:


Created on Choose the actual calendar date All payment orders created on this date will be shown.

Created at Enter a from/to time when the payment order has been created

Optionally this can be used to reduce number of payment orders being selected

If no restriction is selected, the first 200 orders will be shown on the next screen.4. Choose Execute (F8).5. On the Payment Orders and Payment Items screen in the box on the left hand side under

Orders you will find all payment orders created on the calendar date entered.6. Double-click on your payment order from the list.7. Please note down the number of the incoming payment order (will be referred to as incoming

order) 8. On the Display Payment Order check the following values:


Order Type 100102 SEPA SDD Order (incoming)

PO Tech. Status 110 Ready for processing The payment order is not processed yet, but only created

9. Expand the Expand/Collapse Item Overview Section.10. The Ordering Party and the Recipient are shown. Check if the value in the field Amount

corresponds to the direct debit amount.11. Choose Process Order.12. Confirm the dialog-box with Yes and then Continue (Enter) 13. A log is displayed showing all success, info and error messages. Check that no errors are raised

and confirm the popup.14. Check the following values:


PO Tech. Status 128 Inbound Processing Completed The payment order has been processed by the Payment Engine.

15. Expand the Expand/Collapse Item Overview Section.16. Double–click the ordering party item17. Check the following values:


PI Tech. Status 29 Future date Posting The ordering transaction is

© SAP SE of 47



posted with interbank settlement date (=due date) as posting date

18. Choose the Refresh button on the left side just above the orders of your Bank Posting Area.19. Double–click the recipient party item.20. Check the following values for the external recipients:


PI Tech. Status 30 Collected The external recipient transactions are collected for batch forwarding to the clearing system

Prenote ID (under references)

No prenote has to be created

21. Navigate into the collector from the Clearing Information Tab of an external recipient by clicking the magnifying glass icon after the Collec./Queue.

22. Choose Item Assignment, confirm the popup with Yes and close the log.23. Leave the screen and check that there is now a sequence number filled.24. Choose the collector again by clicking the magnifying glass icon after the Collec./Queue.25. Choose Close confirm the popup with Yes and close the log.26. Select Final Process, confirm the popup with Yes and close the log.27. Check the following values for the collector:


Collector Status 04 Completed and Posted

Collector Processing Post Items Collectively

28. Choose tab Associated Payment Order29. Check the following values for the outgoing payment order:Another order has been created. If

you expand it you will see that there is 1 Ordering Party Item, 1 Recipient Party Item and 1 Clearing Item.

30. Please note down the number of the outgoing payment order (will be referred to as outgoing order)

31. Choose Show Payment Order.

This is a periodical step and part of the job automation.If job automation is used, the step does not need to be executed manually.

32. Check the following values:


Order Type PACS3O SDD outgoing order (Interbank)

PO Tech. Status 228 Processed by Output Manager – finalization pending

A file has been created by the output manager.

© SAP SE of 47


This shows that the payment order successfully created the expected format.33. Expand the Expand/Collapse Item Overview Section.34. Double–click the clearing item35. Check the following values:


PI Tech. Status 29 Future date Posting The clearing transaction is posted with interbank settlement date (=due date) as posting date

36. Open the Windows Explorer.37. Access the transaction using the following navigation path:

Windows Explorer (your server)) RD8_work (*)(RD8 stands for the Banking Services System out

(*) Personalized entry – replace the explorer path with the path for your file share (for details see Quick Guide).

38. Check if there is a text document created with the current calendar date and the current time stamp.

39. Open the text document and check the values.

4.1.3 Execute activities on due date

UseAs SEPA Direct Debits are executed before they are due the queued transactions have to be posted when the due date is reached.


SAP Menu Payment Engine Periodic Processing End-of-Day Processing Set Day/End-of-Day Processing

Transaction code /PE1/EOD_SET_DATE



2. In the transaction screen, enter the following data:3. Run the report 10 times using Execute pushbutton until the new posting date is 5 working days

after today and the status is Day processing.4. Run the poller to post queues. Access it using the following navigation path:

SAP Menu Payment Engine Periodic Processing Processes Execute Processes

Transaction code /PE1/POLLER

5. In the transaction screen, enter the following data:

© SAP SE of 47



Queues: Check and Post Required Clearing Time

TICK Executing Queues: Check and Post Required Clearing Time


Update and Close Queues

TICK


6. Choose the Execute pushbutton.7. Run the poller to update future dated positngs. Access it using the following navigation path:

SAP Menu Payment Engine Periodic Processing End-of-Day Processing Update Status of Items for Future Posting

Transaction code /PE1/PIZ_UPDATER




9. Choose the Execute pushbutton.10. Check original payment orders11. Access the transaction using the following navigation path:








Payment Order Number

Enter the 2 numbers you noted down before

The original incoming and outgoing payment order will be selected

14. Choose Execute (F8).15. Double–click the first order (incoming payment order)16. Expand the Expand/Collapse Item Overview Section.17. Double–click the ordering party item18. Check the following values:

© SAP SE of 47



PI Tech. Status 31 Posted The ordering party item is posted on the Banking Services account

19. Double–click the second order (outgoing payment order)20. Expand the Expand/Collapse Item Overview Section.21. Double–click the clearing item22. Check the following values:


PI Tech. Status 31 Posted The clearing item is posted on the Banking Services account

4.1.4 Displaying Payment Item (Informational)

UseThe transaction can be used to view the payment item on the customer account and afterwards on the clearing account.


SAP Menu Financial Services Account Management Account Turnovers, Balances and Key Figures Display Balances and Key Figures

Transaction code BCA_CN_KFG

2. On the Display Balances and Key Figures screen, enter the following data:


Bank Country Enter bank countryFor example:

Bank Key Enter bank keyFor example:

Account Number Enter your account number Enter customer account of the ordering party item

IBAN Enter the IBAN of the focused account. For example: leave blank

This is an optional field.

3. Choose Display Payment Items.4. In the General selections area, leave Item Status blank. 5. Choose the Execute pushbutton.6. Go back using the Back pushbutton7. Check the payment item on the clearing account (Nostro-account).8. On the Display Balances and Key Figures screen, enter the following data:

© SAP SE of 47





Account Number Enter your account number Enter Nosto account for external bank



9. Choose Display Payment Items.10. In the General selections area, leave Item Status blank. 11. Choose the Execute pushbutton.

4.2 Incoming customer payment fileUseThis step processes the payment orders sent from corporate with collection of invoices into Payment Engine (PAIN.008 file). Payment Engine posts the ordering party item and the internal recipient party items to the current accounts within the bank (Banking Services). The clearing of the payment for external bank can be seen on the Nostro account.

4.2.1 Importing file

UseThis step is used to import the file for the respective converter ID with multiple processing controls.

PrerequisitesAn appropriate file must exist for loading. Below are example data for Clearing Area RDS000.

Tag Name User action and values Comment

ReqdColltnD Posting date + 2 work days

<CdtrAcct><Id>

<IBAN>

DE60123456780000000100 An current account with posted money is in active status

<CdtrAgt><FinInstnId> <BIC>

RDSBDEF1000

<InstdAmt Ccy="EUR"> (Under the <DrctDbtTxInf>)

100.03

<MndtRltdInf><MndtId>

MndtId-RDS01 Refer to chapter 4.15 in L34 or chapter 4.8.2.1 in L35 to create a mandate

© SAP SE of 47



</Dbtr><DbtrAcct><Id>

<IBAN>


<DbtrAgt> <FinInstnId> <BIC>

RDSEDEF1000

<InstdAmt Ccy="EUR"> "(Under the <DrctDbtTxInf>)

100.04

<CdtrSchmeId> <Id> <PrvtId> <Othr> <Id>

DE98ZZZ09999999999 Creditor ID

Refer to chapter 5.1 1_SEPA_DD_Pain.008.001.02_RDS_mix.xml under appendix to get the whole sample data for clearing area RDS000. Save the data as xml format in your local folder (For example, C:\RDS000).

Procedure1. Open the Windows Explorer.2. Access the transaction using the following navigation path:

Windows Explorer (your server) RD8_work (*) (RD8 stands for the Banking Services System in

(*) Personalized entry – replace the explorer path with the path for your file share (for details see Quick Guide)Locate the sample PAIN.008 payment file. (For example, C:\RDS000)

3. Go back to the SAP Menu and access the transaction using the following path:

SAP Menu Payment Engine File Handler Import/Process File (Expert)

Transaction code /n/PE1/FH_IPM_EXPERT

4. On the Import File (Expert) enter the following entries:


Converter ID SEPA_N

Input Format /XML

Medium /555

Channel /SEPA

Physical File Name Selected

© SAP SE of 47



File Path / Log. File Name

Enter your file pathfor example /RD8_work/in/1_SEPA_DD_Pain.008.001.02_RDS_mix.xml (*)

Processing Control Process (Online)

(*) Personalized entry – replace the explorer path with the path for your file share (for details see Quick Guide)

5. Choose Execute (F8).6. A green message at the bottom of the screen informs that the file has been imported

successfully. that is “File 1_SEPA_DD_Pain.008.001.02_RDS_mix.xml imported successfully; see log overview for PE process”.

Below error messages from the log can be ignored. Ordering customer identification failed. Message no. /PE1/MSG_LOG_GUI089 Customer ID could not be determined as no customer SLA was found. Message

no. /PE1/MSG_PO_EH022Check with the next steps that the file was successfully converted to a payment order and successfully posted the transactions towards the accounts.

4.2.2 Process incoming Payment Orders in the Payment Engine

UseThis step is to display the payment orders in Payment Engine after importing. Payment Engine posts the ordering party item and the internal recipient party items to the current accounts within the bank (Banking Services). The clearing of the payment for external bank can be seen on the Nostro account.




2. On the Select Clearing area dialog box make the following setting:


Clearing Area Enter your clearing areaFor example, RDS000

3. On the Dynamic Selection screen on the left side in the Restriction of Data Set for Orders choose Created on and enter the following data:


Created on Choose the actual calendar date All payment orders created on this date will be shown

4. Choose Execute (F8).5. The report provides a list of all payment orders within the selected timeframe of your clearing

area.

© SAP SE of 47


6. On the Payment Orders and Payment Items screen in the box on the left hand side under Orders (your Clearing Area, for example RDS000) you will find all payment orders created on the calendar date entered.

7. Double-click on your payment order from the list.8. On the Display Payment Order check the following values:


Order Type 100102 – SEPA SDD order (incoming)

PO Tech. Status 128 Inbound Processing Completed

9. Expand the Expand/Collapse Item Overview Section.10. The Ordering Party and the Recipient are shown. Check if the value in the field Amount

corresponds to the direct debit amount.11. Expand the Expand/Collapse Item Overview Section.12. Double–click the ordering party item13. Check the following values:


PI Tech. Status 29 Future date Posting The ordering transaction is posted with interbank settlement date (=due date) as posting date

14. Choose the Refresh button on the left side just above the orders of your Clearing Area.15. Double–click the recipient party items16. Check the following values for the internal recipients:


PI Tech. Status 30 Collected The recipient transactions are parked in a queue until the due date is reached


‘’ No prenote has to be created

17. Check the following values for the external recipients:


PI Tech. Status 30 Collected The external recipient transactions are collected for batch forwarding to the clearing system



18. Navigate into the collector from the Clearing Information Tab of an external recipient clicking the magnifying glass icon after the Collec./Queue.

19. Choose Item Assignment, confirm the popup with Yes and close the log.20. Leave the screen and check that there is now a sequence number filled21. Choose the collector again by clicking the magnifying glass icon after the Collec./Queue.22. Choose Close confirm the popup with Yes and close the log.23. Select Final Process, confirm the popup with Yes and close the log.

© SAP SE of 47


24. Check the following values for the collector:


Collector Status 04 Completed and Posted

Collector Processing Post Items Collectively

25. Choose tab Associated Payment Order26. Check the following values for the outgoing payment order: Another order has been created. If

you expand it you will see that there is 1 Ordering Party Item, 1 Recipient Party Item and 1 Clearing Item.

27. Please note down the number of the outgoing payment order (will be referred to as outgoing order)

28. Choose Show Payment Order.29. Check the following values:


Tech Status 228 Processed by Output Manager – finalization pending

An outgoing file has been created

30. Press the Select button after the payment order reference31. Please note down the number of the outgoing payment order (will be referred to as outgoing

order) 32. Expand the Expand/Collapse Item Overview Section.33. Double–click the clearing item34. Check the following values:





35. Open the Windows Explorer.36. Access the transaction using the following navigation path:



37. Check if there is a XML document created with the current calendar date and the current time stamp.

38. Open the XML document and check the values.

4.2.3 Executing activities on due date


Procedure

© SAP SE of 47


1. Access the transaction using the following navigation path:



Field name User action and values CommentClearing Area Enter your clearing area,

for example, RDS0002. In the transaction screen, enter the following data:3. Run the report 10 times using Execute pushbutton until the new posting date is 5 working days










TICK


6. Choose the Execute pushbutton.7. Run the poller to update future dated positngs. Access it using the following navigation path:






9. Choose the Execute pushbutton.10. Check original payment orders11. Access the transaction using the following navigation path:



© SAP SE of 47








Enter the 2 numbers you noted down before

The original incoming and outgoing payment order will be selected

14. Choose Execute (F8).15. Double–click the first order (incoming payment order)16. Expand the Expand/Collapse Item Overview Section.17. Double–click the ordering party item18. Check the following value:


PI Tech. Status 31 Posted The ordering party item is posted on the Banking Services account

19. Double–click the internal recipient party item(s)20. Check the following value:


PI Tech. Status 31 Posted The internal recipient party item is posted on the Banking Services account

21. Double–click the second order (outgoing payment order)22. Expand the Expand/Collapse Item Overview Section.23. Double–click the clearing item24. Check the following values:


PI Tech. Status 31 Posted The clearing item is posted on the Banking Services account

4.2.4 Displaying Payment Items on current and clearing accounts (Informational)

UseThe transaction can be used to view the payment items posted to the respective accounts:

Ordering Item Recipient Item (internal) Clearing Item

© SAP SE of 47







Bank Country Enter bank countryFor example: DE

Bank Key Enter bank keyFor example: 12345678

Account Number Enter your account number Enter account number Ordering customer

account Recipient customer

account Nostro account




4.3 Incoming interbank payment fileUseThis step processes the payment order with SEPA Direct Debits sent from the clearing house into

Payment Engine (PACS.003 file). The ordering party item is posted to clearing account in Banking Services (future dated item). The multiple recipients are processed - queued and posted on due date to the customer accounts in Banking Services.

4.3.1 Importing file

UseThis step is used to import the file for the respective converter ID with multiple processing controls.

PrerequisitesAn appropriate file must exist for loading. Below are example data for Clearing Area RDS000.


<SndgInst> RDSEDEF1000

© SAP SE of 47



<RcvgInst> RDSBDEF1000

<TtlIntrBkSttlmAmt Ccy="EUR">

100.04

<IntrBkSttlmDt> Posting date + 2 work days

<InstgAgt> <FinInstnId> <BIC>

RDSEDEF1000

<IntrBkSttlmAmt Ccy="EUR">

100.04

<ReqdColltnDt> Posting date + 2 work days

<MndtRltdInf><MndtId>

MndtId-RDS01 Refer to chapter 4.15 in L34 or chapter 4.8.2.1 in L35 to create a mandate

<CdtrAcct> <Id> <IBAN>

DE58876543210000000002

<CdtrAgt><FinInstnId> <BIC>

RDSEDEF1000


<IBAN>


<DbtrAgt> <FinInstnId> <BIC>

RDSBDEF1000

<CdtrSchmeId> <Id> <PrvtId> <Othr> <Id>

DE98ZZZ09999999999 Creditor ID

Refer to chapter 5.2 2_SEPA_DD_Pacs.003.001.02_RDS_internal.xml under appendix to get the whole sample data for clearing area RDS000. Save the data as xml format in your local folder (For example, C:\RDS000).

Procedure1. Open the Windows Explorer.2. Access the transaction using the following navigation path:

Windows Explorer (your server) RD8_work (*) (RD8 stands for the Banking Services

© SAP SE of 47


System in

(*) Personalized entry – replace the explorer path with the path for your file share (for details see Quick Guide)Locate the sample PACS.003 payment file. (For example, C:\RDS000)

3. Go back to the SAP Menu and access the transaction using the following path:

SAP Menu Payment Engine File Handler Import/Process File (Expert)

Transaction code /PE1/FH_IPM_EXPERT

4. On the Import File (Expert) enter the following entries:


Converter ID SEPA_N

Input Format /XML

Medium /555

Channel /SEPA

Physical File Name Selected

File Path / Log. File Name

Enter your file pathfor example / 2_SEPA_DD_Pacs.003.001.02_RDS_internal.xml (*)

Processing Control Process (Online)

(*) Personalized entry – replace the explorer path with the path for your file share (for details see Quick Guide)

5. Choose Execute (F8).6. A green message at the bottom of the screen informs that the file has been imported

successfully.

Below error messages from the log can be ignored. Ordering customer identification failed. Message no. /PE1/MSG_LOG_GUI089 Customer ID could not be determined as no customer SLA was found. Message

no. /PE1/MSG_PO_EH022Check with the next steps that the file was successfully converted to a payment order and successfully posted the transactions towards the accounts.

4.3.2 Process incoming Payment Orders in the Payment Engine

UseThis step is to display the payment orders in Payment Engine after importing. The ordering party item is posted to clearing account in Banking Services (future dated item). The multiple recipients are processed - queued and posted on due date to the customer accounts in Banking Services.1. Access the transaction using the following navigation path:



© SAP SE of 47









area.6. On the Payment Orders and Payment Items screen in the box on the left hand side under

Orders (your Clearing Area, for example RDS000) you will find all payment orders created on the calendar date entered.



Order Type PACS3I - incoming payment order (interbank)

PO Tech. Status 128 Inbound Processing Completed

9. Expand the Expand/Collapse Item Overview Section.10. The Ordering Party item and the Recipient Party items are shown. Check if the number in the

field Amount corresponds to the amounts in the payment file.11. Check the following values:



12. Choose the Refresh button on the left side just above the orders of your Clearing Area.13. Double–click the recipient party items14. Check the following values for the internal recipients:


PI Tech. Status 30 Collected The recipient transactions are parked in a queue until the due date is reached

4.3.3 Executing activities on due date


© SAP SE of 47







2. In the transaction screen, enter the following data:3. Run the report 10 times using Execute pushbutton until the new posting date is 5 working days










TICK


6. Choose the Execute pushbutton.7. Run the poller to update future dated postings. Access it using the following navigation path:






9. Choose the Execute pushbutton.10. Access the transaction using the following navigation path:

SAP Menu Payment Engine Payment Order Management Edit Payment

© SAP SE of 47


Orders (Expert)








Enter the number you noted down before

13. Choose Execute (F8).14. Check original payment orders15. Double–click the incoming payment order16. Expand the Expand/Collapse Item Overview Section.17. Double–click the ordering party item18. Check the following value:


PI Tech. Status 31 Posted The ordering party item is posted on the nostro account in Banking Services

19. Double–click the internal recipient party item(s)20. Check the following value:


PI Tech. Status 31 Posted The recipient party item is posted on the Banking Services account

Please note down the Posting Date and recipient account no. They will be used in following step 4.4.1 -Refund of a Payment Transaction.

4.3.4 Displaying Payment Items on current and clearing accounts (Informational)

UseThe transaction can be used to view the payment items posted to the respective accounts:

Ordering party: payment item on clearing account Recipient parties: payment items on customer accounts on due date


SAP Menu Financial Services Account Management Account

© SAP SE of 47


Turnovers, Balances and Key Figures Display Balances and Key Figures






Account Number Enter your account number Enter account number Recipient accounts clearing account



3. Choose Display Payment Items.4. In the General selections area, leave Item Status blank. 5. Choose the Execute pushbutton.6. Validate the payment items posted on the accounts.

4.4 Exception Handling4.4.1 Refund of a Payment Transaction

UseThe Bank receives collections of SEPA Direct Debits via clearing house for their customers. Collections for recipients are posted on due date (see chapter 4.3.1). After some period of time customer protests against posted direct debit on her account and claims refund. Compensation interest needs to be calculated for time period and posted to technical P&L account as revenue. This interest is part of refund send back to creditor bank. Note: In case the recipient account does not provide sufficient funds the bank can create a return for this transaction. The processing is similar to the refund process but is out of scope for this RDS.

Prerequisites SEPA Direct Debits from chapter 4.3.1 is posted on the recipient accounts


SAP Menu SAP Menu Financial Services Account Management Account Turnovers, Balances and Key Figures Payment Item Return Payment Item

Transaction code BCA_PAYMITEM_RETURN

2. Enter account details of the recipient account.

© SAP SE of 47


Field name Description User action and values Comment

Bank Country

Bank Key

Account Number

Select one recipient account from chapter 4.3.1

Posting Date Select posting date

3. On the Return Payment Item screen, double-click the payment item created in chapter 4.3.4. On the Return Recipient Item screen, choose Return.5. On the Return dialog text, select the medium, payment method and select one of the pre-defined

return reasons (for example 70 Protest). The transaction type is defaulted according to the configuration settings.

6. Choose Continue (Enter). 7. A new Payment Order is created. Display Payment Order using the following navigation path:

SAP Menu SAP Menu: Financial Services Account Management Account Payment Transaction Orders Payment Order Display Payment Order

Transaction code BCA_PO_DISPLAY

8. Check the Recipient Items of the payment order. One recipient party item is an external item for the returned item and one internal item for the calculated compensation (refund interest).

9. Access the transaction using the following navigation path in order to send the external recipient to Payment Engine via Outgoing Payment Dispatcher:

SAP Menu Financial Services Account Management Periodic Tasks Payment Transaction System Start Outgoing Payment Dispatcher

Transaction code BCA_PO_OPD_MASS_RUN

10. On the Outgoing Payment Dispatcher screen, enter the following data:


Simulate Process Unticked The selection results can be already displayed in the simulation mode, but nothing is executed.

Bank Posting Area Enter bank posting area, for example: 0001

Posting Date Enter posting date,for example: the current posting date

You can leave the field blank if there are only several new contract disbursed.

11. Choose Execute (F8).12. The report provides a log with an overview of all payment orders processed successfully.13. Check with the next steps that the transaction was successfully converted into a payment order

and successfully posted towards the accounts.14. Access the transaction using the following navigation path:

© SAP SE of 47















Order Type 100101 Standard Order (incoming)

PO Tech. Status 110 Ready for processing

22. Expand the Expand/Collapse Item Overview Section.23. The Ordering Party and the Recipient are shown. Check if the number in the field Amount

corresponds to the amount of the original payment order in Banking Services.24. Check recipient party item


Predecessor Item Reference to the original item This references the original item and sets the transaction as returned so that it cannot be returned again.

25. Choose Process Order.26. Confirm the dialog-box with Yes and then Continue (Enter) below the error and info messages.27. Check the following values:



28. Choose the Refresh button on the left side just above the orders of your Bank Posting Area.29. Go to the clearing information tab of an external recipient item with status “collected” and click

on the magnifying glass icon.

© SAP SE of 47


30. Click on “Item Assignment” and click yes on the Item Assignment pop-up, followed by continue on the next prompt.

31. Click on “Close Subordinate Collector” and click yes on the “Close collector” pop up, followed by continue on the next prompt.

32. Click on “Final Prcoess.:Subord.Coll.”

33. Then click yes of the “Finally Process Objects” pop up, follow by continue on the next prompt.

34. Go back to the payment order expert display

35. Go to the “References” tab of the recipient payment item, and click on the “Outgoing PO” magnifying glass symbol.

36. Click Execute on the Outgoing Payment order to generate the output file

37. Check the following values:


Order Type PACS4O Return outgoing order (Interbank)

Order Type

PO Tech. Status 230 Processed by Output Manager PO Tech. Status

This shows that the payment order successfully created the expected format.38. Open the Windows Explorer.39. Access the transaction using the following navigation path:




41. Open the text document and check the values.The transaction can be used to view the payment items posted to the respective accounts:

Ordering party: payment item on clearing account with Banking Services Clearing Item: payment items on nostro account








© SAP SE of 47



Account Number Enter your account number Enter account number Nostro account clearing account




4.4.2 Return of a Payment Transaction based on not existing account

UseThe Bank receives collections of SEPA Direct Debits via clearing house for their customers. Collections for recipients are posted on due date (see chapter 4.3.1). On due date the account is closed and is therefore first send to a CPD account and from there manually returned to the sender.

Prerequisites Update sample file 2_SEPA_DD_Pacs.003.001.02_RDS_internal_AccNotExist.xml for

following tags’ content and then repeat chapter 4.3 with this new import file.


<IntrBkSttlmDt> Posting date + 2 work days

<ReqdColltnDt> Posting date + 2 work days


<IBAN>

DE75123456780000564564 (as example)

Its account does not exist.

Refer to chapter 5.3 2_SEPA_DD_Pacs.003.001.02_RDS_internal_AccNotExist.xml under appendix to get the whole sample data for clearing area RDS000. Save the data as xml format in your local folder (For example, C:\RDS000).


SAP Menu SAP Menu Financial Services Account Management Account Turnovers, Balances and Key Figures Payment Item Return Payment Item

Transaction code BCA_PAYMITEM_RETURN

2. Return a transaction from the suspense account

© SAP SE of 47


Field name Description User action and values Comment

Bank Country Enter bank countryFor example: DE

Your bank countryFor example: DE

Bank Key Enter bank key your bank keyFor example: 12345678

Account Number

Enter the suspense account number

0000100000

Posting Date Select posting date

3. On the Return RecipientItem screen, choose Return.4. On the Return dialog text, select the medium, payment method and select return reasons 20 –

“Account Closed”.5. Choose Continue (Enter) to return the payment item. The status of the payment item becomes

Returned.6. A new Payment Order is created. Display Payment Order using the following navigation path:

SAP Menu SAP Menu: Financial Services Account Management Account Payment Transaction Orders Payment Order Display Payment Order

Transaction code BCA_PO_DISPLAY

7. Check the Recipient Items of the payment order. One recipient party item is an external item for the returned item and one internal item for the calculated compensation.

8. Access the transaction using the following navigation path in order to send the external recipient to Payment Engine via Outgoing Payment Dispatcher:

SAP Menu Financial Services Account Management Periodic Tasks Payment Transaction System Start Outgoing Payment Dispatcher

Transaction code BCA_PO_OPD_MASS_RUN

9. On the Outgoing Payment Dispatcher screen, enter the following data:


Simulate Process Unticked The selection results can be already displayed in the simulation mode, but nothing is executed.

Bank Posting Area Enter bank posting area, for example: 0001

Posting Date Enter posting date,for example: the current posting date

You can leave the field blank if there are only several new contract disbursed.

10. Choose Execute (F8).11. The report provides a log with an overview of all payment orders processed successfully.12. Check with the next steps that the transaction was successfully converted into a payment order

and successfully posted towards the accounts.13. Access the transaction using the following navigation path:

© SAP SE of 47















Order Type 100101 Standard Order (incoming)

PO Tech. Status 110 Ready for processing

21. Expand the Expand/Collapse Item Overview Section.22. The Ordering Party and the Recipient are shown. Check if the number in the field Amount

corresponds to the amount of the original payment order in Banking Services.23. Check recipient party item


Predecessor Item Reference to the original item This references the original item and sets the transaction as returned so that it cannot be returned again.

24. Choose Process Order.25. Confirm the dialog-box with Yes and then Continue (Enter) below the error and info messages.26. Check the following values:



27. Choose the Refresh button on the left side just above the orders of your Bank Posting Area.28. Go to the clearing information tab of an external recipient item with status “collected” and click

on the magnifying glass icon.

© SAP SE of 47


29. Click on “Item Assignment” and click yes on the Item Assignment pop-up, followed by continue on the next prompt.

30. Click on “Close Subordinate Collector” and click yes on the “Close collector” pop up, followed by continue on the next prompt.

31. Click on “Final Prcoess.:Subord.Coll.”32. Then click yes of the “Finally Process Objects” pop up, follow by continue on the next prompt.33. Go back to the payment order expert display34. Go to the “References” tab of the recipient payment item, and click on the “Outgoing PO”

magnifying glass symbol.35. Click Execute on the Outgoing Payment order to generate the output file36. Check the following values:


Order Type PACS4O Return outgoing order (Interbank)

Order Type

PO Tech. Status 230 Processed by Output Manager PO Tech. Status

This shows that the payment order successfully created the expected format.37. Open the Windows Explorer.38. Access the transaction using the following navigation path:




40. Open the text document and check the values.The transaction can be used to view the payment items posted to the respective accounts:

Ordering party: payment item on clearing account with Banking Services Clearing Item: payment items on nostro account








Account Number Enter your account number Enter account number Nostro account

© SAP SE of 47

clearing account




5 Appendix 5.1 1_SEPA_DD_Pain.008.001.02_RDS_mix.xml<?xml version="1.0" encoding="UTF-8"?><!--Sample XML file generated by Christoph Markert - D053760<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02 C:\Users\Christoph\Documents\pain.008.001.02.xsd">

<CstmrDrctDbtInitn><GrpHdr>

<MsgId>MsgID-RDS01</MsgId><CreDtTm>2011-01-17T09:30:47Z</CreDtTm><NbOfTxs>2</NbOfTxs><InitgPty>

<Nm>Ordering Party Name</Nm></InitgPty>

</GrpHdr><PmtInf>

<PmtInfId>PmtInfID-RDS01</PmtInfId><PmtMtd>DD</PmtMtd><PmtTpInf>

<SvcLvl><Cd>SEPA</Cd>

</SvcLvl><LclInstrm>

<Cd>CORE</Cd></LclInstrm><SeqTp>RCUR</SeqTp>

</PmtTpInf><ReqdColltnDt>2000-01-05</ReqdColltnDt><Cdtr>

<Nm>Ordering Party Name</Nm><PstlAdr>

© SAP SE of 47


<Ctry>DE</Ctry><AdrLine>Dietmar-Hopp-Allee 16</AdrLine><AdrLine>69190 Walldorf - Germany</AdrLine>

</PstlAdr></Cdtr><CdtrAcct>

<Id><IBAN>DE60123456780000000100</IBAN>

</Id></CdtrAcct><CdtrAgt>

<FinInstnId><BIC>RDSBDEF1000</BIC>

</FinInstnId></CdtrAgt><DrctDbtTxInf>

<PmtId><EndToEndId>EndToEndId-RDS01</EndToEndId>

</PmtId><PmtTpInf>

<LclInstrm><Cd>CORE</Cd>

</LclInstrm></PmtTpInf><InstdAmt Ccy="EUR">100.03</InstdAmt><DrctDbtTx>

<MndtRltdInf><MndtId>MndtId-RDS01</MndtId><DtOfSgntr>2000-01-01</DtOfSgntr>

</MndtRltdInf><CdtrSchmeId>

<Nm>CreditorIDName-RDS01</Nm><Id>

<PrvtId><Othr>

<Id>DE98ZZZ09999999999</Id><SchmeNm>

<Prtry>SEPA</Prtry></SchmeNm>

</Othr></PrvtId>

</Id>

© SAP SE of 47


</CdtrSchmeId></DrctDbtTx><DbtrAgt>

<FinInstnId><BIC>RDSBDEF1000</BIC>

</FinInstnId></DbtrAgt><Dbtr>

<Nm>John Smith</Nm></Dbtr><DbtrAcct>

<Id><IBAN>DE98123456780000000095</IBAN>

</Id></DbtrAcct>

</DrctDbtTxInf><DrctDbtTxInf>

<PmtId><EndToEndId>EndToEndId-RDS01</EndToEndId>

</PmtId><PmtTpInf>

<LclInstrm><Cd>CORE</Cd>

</LclInstrm></PmtTpInf><InstdAmt Ccy="EUR">100.04</InstdAmt><DrctDbtTx>

<MndtRltdInf><MndtId>MndtId-RDS01</MndtId><DtOfSgntr>2000-01-01</DtOfSgntr>

</MndtRltdInf><CdtrSchmeId>

<Nm>CreditorIDName-RDS01</Nm><Id>

<PrvtId><Othr>

<Id>DE98ZZZ09999999999</Id><SchmeNm>

<Prtry>SEPA</Prtry></SchmeNm>

</Othr></PrvtId>

© SAP SE of 47


</Id></CdtrSchmeId>

</DrctDbtTx><DbtrAgt>

<FinInstnId><BIC>RDSEDEF1000</BIC>

</FinInstnId></DbtrAgt><Dbtr>

<Nm>Receiver Party Name</Nm></Dbtr><DbtrAcct>

<Id><IBAN>DE43876543210087654322</IBAN>

</Id></DbtrAcct>

</DrctDbtTxInf></PmtInf>

</CstmrDrctDbtInitn></Document>

5.2 2_SEPA_DD_Pacs.003.001.02_RDS_internal.xml<?xml version="1.0" encoding="utf-8"?><MPEDDDnfBlkDirDeb xmlns="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb" schemaLocation="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb $MPEDDDnfBlkDirDeb.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SndgInst>RDSEDEF1000</SndgInst> <RcvgInst>RDSBDEF1000</RcvgInst> <SrvcId>COR</SrvcId> <TstCode>T</TstCode> <FType>DNF</FType> <FileRef>111013CORT000036</FileRef> <FileBusDt>2000-01-01</FileBusDt> <RoutingInd>ALL</RoutingInd> <FileCycleNo>01</FileCycleNo> <NumDDBlk>1</NumDDBlk> <NumPCRBlk>0</NumPCRBlk> <NumREJBlk>0</NumREJBlk> <FIToFICstmrDrctDbt> <GrpHdr> <MsgId>RDS20111231000000000001</MsgId> <CreDtTm>2000-01-01T11:20:55Z</CreDtTm> <NbOfTxs>1</NbOfTxs> <TtlIntrBkSttlmAmt Ccy="EUR">100.04</TtlIntrBkSttlmAmt>

© SAP SE of 47


<IntrBkSttlmDt>2000-01-05</IntrBkSttlmDt> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Prtry>ST2</Prtry> </ClrSys> </SttlmInf> <InstgAgt> <FinInstnId> <BIC>RDSEDEF1000</BIC> </FinInstnId> </InstgAgt> </GrpHdr> <DrctDbtTxInf xmlns="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb" schemaLocation="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb $MPEDDDnfBlkDirDeb.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <PmtId> <EndToEndId>EndToEndId-RDS02</EndToEndId> <TxId>RDS020110131000000040717</TxId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> <LclInstrm> <Cd>CORE</Cd> </LclInstrm> <SeqTp>RCUR</SeqTp> </PmtTpInf> <IntrBkSttlmAmt Ccy="EUR">100.04</IntrBkSttlmAmt> <ChrgBr>SLEV</ChrgBr> <ReqdColltnDt>2000-01-05</ReqdColltnDt> <DrctDbtTx> <MndtRltdInf> <MndtId>MNDTID-RDS01</MndtId> <DtOfSgntr>2000-01-01</DtOfSgntr> </MndtRltdInf> <CdtrSchmeId> <Id> <PrvtId> <Othr> <Id>DE98ZZZ09999999999</Id> <SchmeNm> <Prtry>SEPA</Prtry>

© SAP SE of 47


</SchmeNm> </Othr> </PrvtId> </Id> </CdtrSchmeId> </DrctDbtTx> <Cdtr> <Nm>Ordering Party Name</Nm> <PstlAdr> <Ctry>DE</Ctry> <AdrLine>Dietmar-Hopp-Allee 16</AdrLine> <AdrLine>69190 Walldorf - Germany</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>DE58876543210000000002</IBAN> </Id> </CdtrAcct> <CdtrAgt> <FinInstnId> <BIC>RDSEDEF1000</BIC> </FinInstnId> </CdtrAgt> <Dbtr> <Nm>Receiver Name</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>DE98123456780000000095</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>RDSBDEF1000</BIC> </FinInstnId> </DbtrAgt> </DrctDbtTxInf> </FIToFICstmrDrctDbt></MPEDDDnfBlkDirDeb>

5.3 2_SEPA_DD_Pacs.003.001.02_RDS_internal_AccNotExist.xml

© SAP SE of 47


<?xml version="1.0" encoding="utf-8"?><MPEDDDnfBlkDirDeb xmlns="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb" schemaLocation="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb $MPEDDDnfBlkDirDeb.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SndgInst>RDSEDEF1000</SndgInst> <RcvgInst>RDSBDEF1000</RcvgInst> <SrvcId>COR</SrvcId> <TstCode>T</TstCode> <FType>DNF</FType> <FileRef>111013CORT000036</FileRef> <FileBusDt>2000-01-01</FileBusDt> <RoutingInd>ALL</RoutingInd> <FileCycleNo>01</FileCycleNo> <NumDDBlk>1</NumDDBlk> <NumPCRBlk>0</NumPCRBlk> <NumREJBlk>0</NumREJBlk> <FIToFICstmrDrctDbt> <GrpHdr> <MsgId>RDS20111231000000000001</MsgId> <CreDtTm>2000-01-01T11:20:55Z</CreDtTm> <NbOfTxs>1</NbOfTxs> <TtlIntrBkSttlmAmt Ccy="EUR">100.04</TtlIntrBkSttlmAmt> <IntrBkSttlmDt>2000-01-05</IntrBkSttlmDt> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Prtry>ST2</Prtry> </ClrSys> </SttlmInf> <InstgAgt> <FinInstnId> <BIC>RDSEDEF1000</BIC> </FinInstnId> </InstgAgt> </GrpHdr> <DrctDbtTxInf xmlns="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb" schemaLocation="urn:S2SDDDnf:xsd:$MPEDDDnfBlkDirDeb $MPEDDDnfBlkDirDeb.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <PmtId> <EndToEndId>EndToEndId-RDS02</EndToEndId> <TxId>RDS020110131000000040717</TxId> </PmtId> <PmtTpInf> <SvcLvl>

© SAP SE of 47


<Cd>SEPA</Cd> </SvcLvl> <LclInstrm> <Cd>CORE</Cd> </LclInstrm> <SeqTp>RCUR</SeqTp> </PmtTpInf> <IntrBkSttlmAmt Ccy="EUR">100.04</IntrBkSttlmAmt> <ChrgBr>SLEV</ChrgBr> <ReqdColltnDt>2000-01-05</ReqdColltnDt> <DrctDbtTx> <MndtRltdInf> <MndtId>MNDTID-RDS01</MndtId> <DtOfSgntr>2000-01-01</DtOfSgntr> </MndtRltdInf> <CdtrSchmeId> <Id> <PrvtId> <Othr> <Id>DE98ZZZ09999999999</Id> <SchmeNm> <Prtry>SEPA</Prtry> </SchmeNm> </Othr> </PrvtId> </Id> </CdtrSchmeId> </DrctDbtTx> <Cdtr> <Nm>Ordering Party Name</Nm> <PstlAdr> <Ctry>DE</Ctry> <AdrLine>Dietmar-Hopp-Allee 16</AdrLine> <AdrLine>69190 Walldorf - Germany</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>DE58876543210000000002</IBAN> </Id> </CdtrAcct> <CdtrAgt> <FinInstnId>

© SAP SE of 47


<BIC>RDSEDEF1000</BIC> </FinInstnId> </CdtrAgt> <Dbtr> <Nm>Receiver Name</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>DE75123456780000564564</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>RDSBDEF1000</BIC> </FinInstnId> </DbtrAgt> </DrctDbtTxInf> </FIToFICstmrDrctDbt></MPEDDDnfBlkDirDeb>

© SAP SE of 47