SEPA Solutions in SAP FI-CA Jürgen Köhling, FI-CA Development July 30, 2013 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. © 2013 SAP AG. All rights reserved. Customer 3 Agenda FI-CA and Industries Which SEPA Functionality Already Exists? Which New SEPA Functionality Was Developed? © 2013 SAP AG. All rights reserved. Customer 4 FI-CA and Industries FI-CA and Industries BRIM O2C Retail Leasing Loans Media Utilities Telco IS-M IS-U RM-CA Online Shops Transportation High Tech FICAX FI-CA © 2013 SAP AG. All rights reserved. Mail Order Student Accounting Social Services Claims Management Policy Management Public Sector Insurance PSCD FS-CD SEPA Dev Customer 6 Which SEPA Functionality Already Exists? SEPA Functions in FI-CA as of 6.00 FI-CA uses mandate management as one application It can already do the following: Create and change SEPA mandates in a mass run, for example from automatic debit authorizations Manually create, change, and display mandates Maintain SEPA mandates (FPP2) in business partner master data maintenance for bank details Create, change, and display SEPA mandates (FPP4) in the transaction for maintaining bank data Create SEPA direct debits in a payment run (if the payment method is a SEPA payment method) Create SEPA-conformal XML payment media for SEPA_DD and SEPA_CT Print SEPA mandates Save SEPA mandates as scanned file attachments through Generic Object Services © 2013 SAP AG. All rights reserved. Customer 8 Which New SEPA Functionality Was Developed? New Functions in FI-CA – Mandates in Master Data (1) Notes 1825941 Mandate can be specified in the contract account (insurance object/ PS contract object). Possible to assign the same mandate to different contract accounts (insurance objects/ contract objects) Check for the existence of a valid/suitable mandate for the SEPA payment method in the object Notes 1825932, 1825933 © 2013 SAP AG. All rights reserved. Customer 10 New Functions in FI-CA – Mandates in Transaction Data (2) Notes 1825929 Mandate can be specified in the FI-CA document (create/post, change, display, mass change, change documents). Specification of the mandate can be transferred from the upstream system (SD / CRM / payment plan item/request/user-defined caller of “Post Document”) Notes 1825943 The mandate can also be specified in other document-like constructs (installment plan, promise to pay, payment specification, …) Check for the existence of a valid/suitable mandate for the SEPA payment method in the document © 2013 SAP AG. All rights reserved. Customer 11 New Functions in FI-CA – Synchronization of Bank Data (3) When changing banks (move/new bank as of 01.04), the mandate can be adjusted (new IBAN) or a new one can be created on the date of the change. This is analogous to overwriting the bank data (change bank immediately). Check for the existence of open direct debit pre-notifications. Notes 1825940 When creating new bank data, you can set up a reference to the mandate; when you delete them, the mandate can be reversed. If you change/create bank data, a print job can be created for the mandate. © 2013 SAP AG. All rights reserved. Customer 12 New Functions in FI-CA – Pre-Notification (4) Notes 1825942 An explicit direct debit pre-notification (date, amount, mandate, creditor ID) can be created so: - Through a separate pre-notification run (analogous to the payment run), incl. new correspondence - Through Convergent Invoicing/IS-U Invoicing when issuing an invoice, incl. adjusted correspondence - (In future) From upstream systems, if they manage such an object (correspondence from upstream system) Implicit direct debit pre-notifications (“Mandate on invoice”) are possible because the mandate can be in the document. Separate correspondence (installment plan/promise to pay) were enhanced correspondingly and can also include the mandate reference. Paying Company Code: © 2013 SAP AG. All rights reserved. Customer 13 New Functions in FI-CA – Pre-Notification (5) Which items are to be pre-notified? - All that I select (partner/ contract account/ contract/user-defined selection through document fields) - All required by the payment method - All intended for pre-notification during posting - All intended for manual pre-notification The need for pre-notification can therefore be determined, dependent on user-defined document data and master data. Payment Method © 2013 SAP AG. All rights reserved. Document Customer 14 New Functions in FI-CA – Pre-Notification (6) Pre-notification run - Item selection/grouping/payment method selection/mandate selection as for payment run - Instead of posting, a new “direct debit pre-notification” object is created (status “open”) - Direct debit pre-notification is entered in the mandate - Items are protected from other settlements/changes © 2013 SAP AG. All rights reserved. Customer 15 New Functions in FI-CA – Pre-Notification (7) After the pre-notification run - Items have been selected and are protected from other settlements/changes - Pre-notification data is visible in the document, account balance, mandate, payment data, … Document Pre-Notification Account Balance Mandate © 2013 SAP AG. All rights reserved. Customer 16 New Functions in FI-CA – Pre-Notification (8) New object: Direct debit pre-notification - Transactions for display (also from archive)/ change/reverse - Reports for list/mass reversal/archiving Individual items can be removed from the pre-notification, and can be added again provided that no changes were made in the interim. Remove Item © 2013 SAP AG. All rights reserved. List /Mass Reversal Customer 17 New Functions in FI-CA – Pre-Notification (9) Pay in accordance with pre-notification (payment run) - Selection by execution date of the pre-notification, grouping in accordance with pre-notification - Bank data and mandate from the pre-notification are read and checked (!) - Posting/payment medium - Posting document entered in mandate management/status change of pre-notification Mandate Pre-Notification © 2013 SAP AG. All rights reserved. Customer 18 New Functions in FI-CA – Reversal/ Returns(10) Notes 1825944 Settlement of a pre-notified item leaves pre-notification data in the item Reversal of the pre-notification removes pre-notification data from items (“free again”) A pre-notified receivable cannot be reversed Reversal of a payment document removes pre-notification data from the item (“free again”) and can undo mandate use Analog returns -> New returns activity Returns Activities © 2013 SAP AG. All rights reserved. Customer 19 New Functions in FI-CA – Correspondence Request (11) Choose between printing immediately or printing later through correspondence request A New correspondence types (0047/SEPA Mandate and 0048/Pre-Notification) with PDF forms and SmartForms. Correspondence request from the following: - Mandate display (Dialog) - Or synchronization of bank data (Customizing) - Time (after saving/after creating) After printing, mandate changes (through new event) can be made From the List Direct printing via Popup and choose between „print“ and „delayed“ also possible now From the Detail Screen © 2013 SAP AG. All rights reserved. Customer 20 New Functions in FI-CA – Correspondence Print (12) Notes 1825941 Print through standard correspondence print (FPCOPARA) © 2013 SAP AG. All rights reserved. Customer 21 New Functions in FI-CA – Payment Run FRST/RCUR (13) Separate payment runs for FRST / RCUR can be achieved through the additional characteristic for the run ID, but require that the same items are read n times. It is not possible to define FRST/RCUR in the items themselves or filter them when selecting items. Strategy: First, the RCUR run (98%), then the FRST run (2%), where the FRST run should look further to the future (and then see some of the next RCUR debits again). © 2013 SAP AG. All rights reserved. Customer 22 New Functions in FI-CA – Payment Run Sorting XML (14) A payment run can create debits with various mandate types/sequence types/execution dates. Event 00 in payment medium Customizing is used for sorting. The following fields from the payment record can be evaluated there to fill the sort field as you wish: - Mandate type (B2B/non-B2B) - Sequence type (FRST/RCUR) - Execution date Payment List © 2013 SAP AG. All rights reserved. Payment Data Customer 23 New Functions in FI-CA – Due Dates (15) Note 1876823 The payee should receive pre-notification 5-14 days before the due date in accordance with general terms and conditions; can also be regulated differently. Target: Execution date= Due date for item. If pre-notification is too late, the execution date can be after the due date because of FRST/RCUR dates. No collection before the announced date, tolerances for late collection in Customizing 03.04 Today: 20.03 Select by 08.04 © 2013 SAP AG. All rights reserved. Payment run/FRST 06.04 Payment run/RCUR Due: 08.04 Customer 24 New Functions in FI-CA – Due Dates (16) Note 1876823 Target: Execution date = Due date (do not collect too late) Target : Latest possible selection of items (do not settle too soon) Target : Observe SEPA lead times (no complaints from banks) Target : Keep announced date (no complaints from customers) Pre-notification run on 20.03 20.03 20.03 Selected by 08.04 08.04 08.04 Ann. execution date 08.04 08.04 08.04 Payment run on 03.04 / 06.04 08.04 12.04 Selected by 08.04 08.04 12.04 Execution date 08.04 10.04/13.04 14.04/17.04 Items due: 08.04 © 2013 SAP AG. All rights reserved. Customer 25 New Functions in FI-CA – COR1 (17) Note 1867435 Leadtimes and local instrument codes can be defined on level country – country / bank – bank. Payment run (and prenotification) take into account the specifications given there and produce prenotifications or payment documents with according execution dates. Payment media creation shows sequence type and local instrument code in XML. Payment List (Item due 26.07, FRST, 5 days) Payment List with COR1 customized (Item due 26.07, FRST, 1 day) (Without COR1) (Calender EU => weekend 27/28.07) © 2013 SAP AG. All rights reserved. Customer 26 Planned Availability of the New SEPA Functions Delivery Through SAP Notes (1853345) Jan Feb Mar © 2013 SAP AG. All rights reserved. Apr May Jun Jul Aug Sept Oct Nov Dec Customer 27 Customer Test System in the Cloud Interested customers can remotely access our customer test system in the cloud The system version is EhP6, SP07 and contains all the SEPA developments in the FI-CA area presented today The system is set up as an RM-CA system The system has been available for several days; we grant you 14 days’ access to the system Prerequisite for use is a signed feedback agreement, already met by many customers If you are interested, please contact daniel.fabian@sap.com or michael.seitz@sap.com by e-mail © 2013 SAP AG. All rights reserved. Customer 28 More Information http://www.service.sap.com/SEPA © 2013 SAP AG. All rights reserved. SEPA Bank Transfer, Direct Debit, Mandates with SAP Customer 29 Thank You Accounting Globalization Real Estate Consulting Mandates Banking Media FI-CA CRM HCM SD Please visit the stands in the foyer
