sepa solutions in sap fi-casapidp/... · - through convergent invoicing/is-u invoicing when issuing...

SEPA Solutions in SAP FI-CA Jürgen Köhling, FI-CA Development

July 30, 2013

© 2013 SAP AG. All rights reserved. 3 Customer

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.


Agenda

FI-CA and Industries

Which SEPA Functionality Already Exists?

Which New SEPA Functionality Was Developed?



IS-M

Media

FI-

CAX FS-CD

Insurance

IS-U

Utilities

PSCD

Public

Sector

RM-CA

Telco

Loans

Leasing

Retail

Transportation

Student Accounting

Social Services

Online Shops

High Tech

Claims Management

Policy Management

Mail Order

BRIM

O2C

SEPA

Dev FI-CA

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

Which New SEPA Functionality

Was Developed?


New Functions in FI-CA – Mandates in Master Data (1)

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

Notes

1825941


New Functions in FI-CA – Mandates in Transaction Data (2)

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”)

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

Notes

1825929

Notes

1825943


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.

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.

Notes

1825940


New Functions in FI-CA – Pre-Notification (4)

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:

Notes

1825942



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 Document



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



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

Mandate

Account Balance

Pre-Notification



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 List /Mass Reversal



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


New Functions in FI-CA – Reversal/ Returns(10)

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

Notes

1825944


New Functions in FI-CA – Correspondence Request (11)

A Choose between printing immediately or printing later through correspondence request

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

From the Detail Screen

Direct printing via Popup and

choose between „print“ and

„delayed“ also possible now


New Functions in FI-CA – Correspondence Print (12)

Print through standard correspondence print (FPCOPARA)

Notes

1825941


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).


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 Payment Data


New Functions in FI-CA – Due Dates (15)

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

Today: 20.03 Due: 08.04 Select by 08.04 Payment

run/FRST

Payment

run/RCUR

06.04 03.04

Note

1876823


New Functions in FI-CA – Due Dates (16)

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

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)

Items due: 08.04

Note

1876823


New Functions in FI-CA – COR1 (17)

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)

Note

1867435

Payment List with COR1 customized

(Item due 26.07, FRST, 1 day)

(Calender EU => weekend 27/28.07)

(Without COR1)


Planned Availability of the New SEPA Functions

Jan Feb Mar Apr May Jun Jul Aug Sept Oct Nov Dec

Delivery

Through

SAP Notes

(1853345)


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 [email protected]

or [email protected] by e-mail

mailto:[email protected]

mailto:[email protected]


More Information

http://www.service.sap.com/SEPA SEPA Bank Transfer, Direct Debit, Mandates with

SAP

http://www.service.sap.com/SEPA

https://training.sap.com/de/de/course/wdsepa-sepa-berweisung-lastschrift-und-mandate-mit-sap-classroom-001-de-de/

https://training.sap.com/de/de/course/wdsepa-sepa-berweisung-lastschrift-und-mandate-mit-sap-classroom-001-de-de/

Thank You

Please visit the stands

in the foyer

Accounting

Globalization

Real Estate

Consulting

Mandates

Banking

Media

FI-CA

CRM

HCM

SD

sepa solutions in sap fi-casapidp/... · - through convergent invoicing/is-u invoicing when issuing...

Documents