Single Euro Payments Area (SEPA) Implementation of Direct Debit-Technical Design

Vijay Simha on !-"ct- #!$ #%&!'( last mo)ifie) by Vijay Simha on $!-*an- #!+ !+&!, Version $

Single Euro Payments Area (SEPA) Implementation of DD(Direct Debit)(Technical)

Sep, 20 ! Intro"uction SEPA stands for Single Euro Payment Area. Its a system that is designed to create financial efficiency for countries using the currency Euro by providing a unified system in which to perform financial transactions. The SEPA see s to create a better system for credit transfers! an improved debit system and a cheaper way for individuals and firms to ma e transactions within member countries or regions. Implementation of SEPA ma es the customers life easier. Irrespective of the national area customers will be able to use the same card for all euro payments and also they need only one ban account in euro area. Intro"uction to SEPA process# The belo$ mentione" shoul" be "one for Implementation of SEPA business in any SAP system# % SEPA&Acti'ation&(an"ate&(anagement "ollowing are the activities which are to be done as part of this# i. SEPA mandate management has to be activated for the usage with S$$ %&'E and S$$ ()( from "I*A' payment processing. Apart from activating the SEPA +andate management we need to maintain the SEPA +andate management modifiable fields.

(elow is the path for activating the SEPA +andate +anagement and maintain the modifiable fields. I+, *- "inancial Accounting *- Accounts 'eceivable and Account Payable *- (usiness Transactions *- Incoming Payments *- +anagement of SEPA +andates *- ,eneral Settings.

I+, *- "inancial Accounting *- Accounts 'eceivable and Account Payable *- (usiness Transactions *- Incoming Payments *- +anagement of SEPA +andates *- $efine +odifiable "ields

ii.

%reation of new $+EE Payment "ormat tree for SEPA credit transfer and SEPA direct debit. SEPA.%T and SEPA.$$ are the $+EE formats provided by SAP. As we will be dealing with multiple countries it is always better to copy the $+EE formats and create new ones. If there is any custom re/uirement for any country create a user e0it and assign to the field that needs to be changed dynamically.

2% Pre )otification $ith payment run # 1ith a direct debit pre*notification! +ar ets can inform a payer in writing in advance of the debiting of his account. To do this! one has to schedule a run for the creation of

direct debit pre*notifications before the payment run! meaning before clearing the open items and creation of payment media. These correspond in structure to the payment advice notes! and therefore contain details of the run date! the amount to be collected! mandate I$! 2nified %reditor Identifier etc. "ollowing are the SAP notes to be implemented for SEPA Pre*notification.

$escription

"334# %ustom Selection for (atch Input

"334S# Selection %hec for %ustomers and 5endors

"3336SEPA# +andate re7ected as invalid after change

"(%8 # 'eversal possible despite cleared item

"3346"333 # (A$I for SEPA +andate usage

SEPA# $irect debit Pre*9otification

5alid SEPA mandate is not found in the system during

payment proposal processing

As part of the 9ote implementation 3:;4<=3! we need to implement manual steps given below for importing the Standard SAP "orm. SAP has provided te0t file by using this file we need to import the ob7ect "334.$$.P'E9&TI" into SAP by e0ecuting program 'ST>%'P. This is standard SAP form which will be used for sending Pre9otifications. SAP has provided >+? file by using this file we need to import the ob7ect "334.$$.P'E9&TI" into SAP using S"P transaction code. &nce it is uploaded! activate the form. &nce all the relevant &SS 9otes are implemented for SEPA $irect debit pre* notification! we will get option of chec bo0 for Pre*notification in "334 transaction and also pre*notification relevant standard program '""&A5IS.$$.P'E9&TI" and script form @"334.$$.P'E9&TI"A available in the system.

The abo-e chec. bo/ is chec.e) if 0e nee) to )o SEPA prenotification1

'""&A5IS.$$.P'E9&TI"# This is the payment advice print program that is used to print the pre*notifications the pre*notification "334.$$.P'E9&TI"# This is the standard SAP script which is used to send the pre* notifications.

2ase) on the user re3uirement( the form name can be change)

The new Bdirect debit pre*notificationB ob7ect is visible in the payment run @"334A! in the document display @"(4CA! in the line item display @"(?D9A and in mandate display @"SEPA.+=A. It can be deleted again if the direct debit pre* notification customer ob7ects to it @for e0ample! because the customer pays the bill himselfA. &therwise! the posting run and the payment medium creation are performed after the end of the specified wait time based on the direct debit pre*notifications.

!% *reation of SEPA (an"ates for payment transactions # (efore doing any transaction for any SEPA customer we need to have a mandate create for the %ustomer. (efore creating a mandate the %ustomer Should have I(A9 number. Transactions used # "SEPA.+3 "SEPA.+)

"SEPA.+C!"SEPA.+= )+TE# +andates can also be created from the payment tab of the %ustomer +aster >$43! "$43! >$4)!"$4). 9&TE# +andate 9umber can be either E0ternal or Internal 9umber. To ma e our wor easier technically we can use the below procedure using the below (APIEs# The table that is +aster for all the SEPA mandates is SEPA&(A)DATE% SEPA&(A)DATE# This is the Standard Smart form used to print the mandate details for any customer. Assume a file with the %ustomer and mandate Information is available

%hec if the customer is created by chec ing in the F9(3 table. If the %ustomer is present then chec if the %ustomer has I(A9 and (I% number. %hec if the mandate is not created for %ustomer with the mandate number using the (API SEPA.+A9$ATES.API.,ET. "or the (API SEPA.+A9$ATES.API.,ET pass the customer number in the importing parameter to chec if there is any mandate information present for the %ustomer SEPA.,ET.%'ITE'IA.+A9$ATE*snd.id = %ustomer 9umber .

ET45A6DATES contains the man)ate information that is fetche) from 2API base) on the 7ustomer 6umber1

6"TE &

SEPA.+A9$ATES.API.,ET "+ cannot be used for multiple mandate scenario. 1e can write ta e +,2I$ from 'E,2G table and go to SEPA.+A9$ATE table and get the I(A9 number and mandate number.

Three (APIES are ma7orly used to %reation and updating of the mandate details of the %ustomer. the for from a +andate particular the table SEPA.+A9$ATES.API.,ET for a (API.SEPA.+A9$ATE.%'EATE3

$ATE table +andate

n of +andate details (API.SEPA.+A9$ATE.%GA9,E3

mer

(an"ate *reation#

2se the (API (API.SEPA.+A9$ATE.%'EATE3 to create the mandate . (API.S.SEPA.+A9$ATE.%&++&9 structure which is importing parameter to the above mentioned (API has to be filled with the mandate information .This contains both the Sender @%ustomer $etails A and receiver details @%ompany code data A.

Then collect all the address information either from the file provided or from the customer master data and fill the Sender information in the structure (API.S.SEPA.+A9$ATE.%&++&9. Then based on the company code fetch the address details of the %ompany code and fill the 'eceiver information in the structure (API.S.SEPA.+A9$ATE.%&++&9. ES.+A9$ATE.%'EATE$ e0porting parameter in the above (API gives a success message if the mandates are correctly created for the customer. Error handling can be done with the return e0porting parameter.

If the mandate already e0ists then chec if there is any change in the mandate information. (an"ate mo"ification#

2se the (API (API.SEPA.+A9$ATE.%GA9,E3 to change the already e0isting mandate. (API.S.SEPA.+A9$ATE.%GA9,E structure which is importing parameter to the above mentioned (API has to be filled with the mandate information .This contains both the Sender @%ustomer $etailsA and receiver details @%ompany code data A.

In case ofup)ation is faile) it can han)le) by return parameter of the 2API

Display of (an"ates #
The create) man)ates can be chec.e) by 8SEPA45$ 9i-e the 5an)ate number or 7ustomer 6umber an) chec. for the 5an)ate information1

"n 7lic. on Enter the belo0 Screen appears 0hich )isplays all the information1

:e can also chec. the 5an)ate information through 7ustomer master )isplay f)# (/)# (/)#$(f)#$1

using transaction

7lic. on the Tab to chec. an) create the man)ate Details from 7ustomer master

Display the ,ist of (an"ates#

;se the transaction 8SEPA45+ to )isplay a list for customers for a particular company co)e1

5ention the company co)e in the belo0 transaction an) then e/ecute all the man)ates present for the company co)e 0ill be )isplaye)1 A list of man)ates 0ill be )isplaye) as sho0n in the belo0 screen shot1

The abo-e lights )epicts )ifferent status of the man)ates belo0 are the )iffernent status of man)ates1

Entere"

Acti'e To -e *onfirme" ,oc.e" *ancele" +bsolete *omplete" *omplete"

If 0e nee) to print a particular man)ate information then select the Print man)ate button on the top right corner of the list 1

8or this SAP has pro-i)e) a smartform SEPA45A6DATE1This can be customi<e) at central le-el an) the thus the man)ate can be create) an) man)ate information can be printe)1