SEPA in ERP Financials

SEPA in SAP ERP Financials Direct Debits in 4 Steps

Dr. Arndt Köster / Chief Product Owner ERP Financial Operations July 25, 2013

©  2013 SAP AG. All rights reserved. 2 Customer

Ausschlussklausel

Die Informationen in diesem Dokument sind vertraulich und urheberrechtlich geschützt und dürfen nicht ohne Genehmigung von SAP offengelegt werden. Diese Präsentation unterliegt weder Ihrem Lizenzvertrag noch einer anderen Service- oder Subskriptionsvereinbarung mit SAP. SAP ist in keiner Weise verpflichtet, in diesem Dokument oder einer dazugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Dieses Dokument oder jede dazugehörige Präsentation über die Strategie von SAP und mögliche zukünftige Entwicklungen, Ausrichtungen und Funktionen von Produkten und/oder Plattformen kann von SAP jederzeit aus beliebigen Gründen ohne vorherige Ankündigung geändert werden. Die Informationen in diesem Dokument stellen keinerlei Zusage, Versprechen oder rechtliche Verpflichtung zur Auslieferung von Materialien, Code oder Funktionen dar. Dieses Dokument wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt insbesondere, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. Dieses Dokument dient zu Informationszwecken und darf nicht in einen Vertrag eingebunden werden. SAP übernimmt keine Verantwortung für Fehler oder Unvollständigkeiten in diesem Dokument, es sei denn, solche Schäden wurden von SAP vorsätzlich oder grob fahrlässig verursacht.


Legal Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


SEPA Direct Debit “Four Corner Model”

Signed mandate

Mandate

Confirmation of direct debit

Clearing and

Settlement

Message between banks

Message between banks Initialization

of direct debit

Direct debit pre-notification

Customer

Customer Bank

Vendor

Vendor Bank

Data transfer


Prozess im FI-AR

Transfer FI

• Line item report • Open items with

SEPA mandate (editable)

Payment Proposal

• Proposal run for direct debit pre-notifications

• Proposal data set (editable)

Direct Debit Pre-Notification

• Display • Delete • Print • Line item report

Payment Run

• Scheduling by direct debit pre-notification

• Direct debit pre-notification and mandate usage


What To Do in 4 Steps

1. SEPA Activation

2. Migration Direct Debit à

Mandate

3. Payment Method and Electronic

Funds Transfer 4. Test

DEMO ERP-FI: SEPA Direct Debits in 4 Steps

Process Flow

1. SEPA Activation and Basic Settings 1.1 General Settings for SEPA (FI_APAR_SEPA_CUST) (1.2) SEPA Mandate Management: Changeable Fields (FI_APAR_SEPA_FIELDS) 1.3 Define Creditor Identifier (V_T042B) 1.4 Define IBAN / BIC for House Bank (FI12) 1.5 Procedure for Determining Mandate Reference (SEPA_MND_FM_CUST) 1.6 Mandate Reference: Interval Maintenance (SEPA_NR_MT) 1.7 SEPA Settings for Mandate Reference (SEPA_NR_CUST) 1.8 SEPA: Maintain Status Reasons (SEPA_RC_CUST) 1.9 SEPA: Maintain Unpermitted Status Transitions (SEPA_STATUS_CUST) 1.10 Local Inst. and Template Deadlines for SEPA Direct Debit (V_FSEPA_INST_CD) 2. Migration Direct Debit Mandate 2.1 External generation of IBAN (IBANMD) 2.2 Create SEPA Mandates in Mass Run (FI_APAR_SEPA_CONV) 2.3 Schedule Mandates (FSEPA_M4) 3. Settings for Payment Method & Electronic Funds Transfer 3.1 Change “Payment Method/Country" (OBVCS) 3.2 Take Payment Method into Account in Bank Selection (OBVCU) 3.3 Customer – Define SEPA Payment Method (FD03) 3.4 Payment Medium: Create Selection Variant (OBPM4) 4. Test 4.1 Enter Customer Invoice (FB70) 4.2 Customer Line Items (FBL5N) 4.3 Proposal Run and File Creation (F110)


Starting Point

o  Company Code: FIOP

o  Example Customer: SEPA-DEMO

o  DTAUS – Direct debit medium can be created


1.1. Activate SEPA

o  Transaction code: FI_APAR_SEPA_CUST

o  SAP Note 1784060 – SEPA Mandates: Basis for Customizing Enhancement

©  2013 SAP AG. All rights reserved. 11

Parameters can prevent external assignment of the

mandate reference.


1.3 Define Creditor Identifier (1/2)

o  Transaction code: SM30 (V_T042B)


1.3 Define Creditor Identifier (2/2)

o  “Direct Debit Pre-Notifications” field can remain initial.

o  SAP Note 1844531 – SEPA Direct Debit Pre-Notification

o  Functioning example identifiers from F1 Help


1.4 Define IBAN for House Bank Account

o  Transaction: FI12


1.5 Mandate Reference: Set Up Determination Procedure

o  Transaction code: SEPA_MND_FM_CUST

o  SAP Note 1813133 – Number Ranges for SEPA Mandates


1.6 Mandate Reference: Interval Maintenance

o  Transaction code: SEPA_NR_MT



1.7 Settings for Mandate Reference

o  Transaction code: SEPA_NR_CUST



1.8 Maintain Mandate Status Reasons

o  Transaction code: SEPA_RC_CUST

o  SAP Note 1841203 – SEPA Mandate: Status Change and Reason Codes


1.9 Restrict Status Transitions for Mandate Status

o  Transaction code: SEPA_STATUS_CUST

o  SAP Note 1841203 – SEPA Mandate: Status Change and Reason Codes


1.10 COR1 – Template Deadlines and Local Instrument

o  Transaction code: SM30 (V_FSEPA_INST_CD)

o  SAP Note 1865097 - SEPA: Support for COR1 (not released yet)


2.1 SAP Standard Report IBAN-Out-IBAN-Back Procedure

o  In the first step, the SAP transaction IBANMD (Program RFIBANMD) prepares the IBAN-out file, which can be uploaded in the IBAN Service Portal.

o  Then import the IBAN-back file, which is available for download in the IBAN Service Portal.

o  At the same time, the BIC (SWIFT Code) of the associated bank is checked.

o  For more details, see SAP Notes 1251446 / 7


2.2 Create Mandates : Mass Run

o  Transaction code: FI_APAR_SEPA_CONV

o  Recommendation: SAP Note 1856328 - RF_CONVERT_XEZER_TO_MANDATE


By signing this mandate form, you authorize (A) FIN Operations Company to send instructions to your bank to debit your account and (B) your bank to debit your account in accordance with the instructions from FIN Operations Company. This mandate is only intended for business-to-business transactions. You are not entitled to a refund from your bank after your account has been debited, but you are entitled to request your bank not to debit your account up until the day on which the payment is due.Please complete all the fields marked *.

SEPA Business-to-Business Direct Debit Mandate

Mandate reference with prefix


3.1 & 3.2 Create Payment Method for SEPA Direct Debit

o  SAP Note 1406227 - F110 ... Valid Payment Methods According to Country of Destination

o  Use “SAP SEPA” – Example for SEPA Formats

o  “SWIFT Code Required” can be omitted later

o  “Payment per due day”: Due day transferred to bank as “Requested Collection Date”


3.3 Define New SEPA DD Payment Method for Customers

o  Transaction code: FD02

o  In the transition phase, the existing payment method can be retained as a fallback option.


3.4 Payment Medium: Create Selection Variants for SEPA_DD

o  Transaction: OBPM4

o  Special condition type requirements can be fulfilled through format parameters

o  SAP Note 1841781 SEPA Composite SAP Note: Payment Medium


Test: Restrict Status Transitions for Mandate Status

Direct transition of “Entered” à “Active” was restricted.


Test: Reasons for Mandate Status

A status reason can be specified here for “Canceled” status.


Test: Set Mandate to “Active”

After receipt of the signed mandate, enhance it with the following:

ü  Place and date of signature ü  (Optional) IBAN ü  Mandate status “Active”


Test: Enter Customer Invoice


Test: Proposal Run for SEPA Direct Debit

o  Transaction code: F110

o  When using a SEPA payment method, the option for direct debit pre-notification is displayed automatically

o  SAP Note 1844531 – SEPA Direct Debit Pre-Notification

o  SAP Note 1864592 – Date Specifications for SEPA Direct Debits


Test: Check the XML File

o  Check the XML file against the bank schema (XSD schema file)

o  Here: IBAN and BIC of the house bank were not filled in Customizing

SEPA Composite SAP Notes ERP FI SEPA Composite SAP Note 1845689 – Direct Debits in FI-AR -  SEPA Composite SAP Note 1848201 – Master Data -  SEPA Composite SAP Note 1845440 – Mandate and IBAN -  SEPA Composite SAP Note 1841123 – Payment Programs F110 and F111 -  SEPA Composite SAP Note 1841781 – Payment Medium


Central SAP SEPA Web Page

http://service.sap.com/SEPA

Thank You

Arndt Köster SAP AG


© 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

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

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.

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

SEPA in ERP Financials

Documents

Transcript of SEPA in ERP Financials