7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 1/60
SEPA (Single European
Payment Area)
Solution Overview
Christian Mnich
Solution Manager, Bank Communication Management, SAP AG
J anuary, 2010
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 2/60
©SAP 2007 / Page 2
1. SEPA - Overview
2. Payment Instruments and Formats
3. SEPA Mandate Management
Agenda
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 3/60
©SAP 2007 / Page 3
SEPA - Vision And Definition
An area where citizens, companies, and others will be able to
make and receive payments in euro, within Europe, whether between or
within national boundaries under the same basic conditions, rights and
obligations, regardless of their location.
SEPA definition
Source: European Payments
Council Roadmap, 2004
“SEPA is the largest payments initiative ever undertaken within Europe and possibly the world.”
European Payments Council
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 4/60
©SAP 2007 / Page 4
Reasons for SEPA
Reasons for SEPA
Improved interoperability by standardizing fragmented payment markets
Reduced risk and complexity by simplifying cross-border payments
Reformation of the payment industry by harmonization and consolidation is supported
Idea of SEPA is used as an catalyst to upgrade payment infrastructures throughout Europe
Validity Area
The European Union – Euro Countries
Austria, Belgium, Cyprus, Finland, France, Germany, Greece, Ireland, Italy,Luxembourg, Malta, Netherlands, Portugal, Slovenia and Spain
The European Union – Non Euro Countries
Bulgaria, Czech Republic, Denmark, Estonia, Hungary, Latvia, Lithuania, Poland,Romania, Slovakia, Sweden, United Kingdom
The European Economic Area Iceland, Liechtenstein, Norway
And additionally - Switzerland
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 5/60
SEPA Countries
©SAP 2007 / Page 5
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 6/60
©SAP 2007 / Page 6
SEPA At A Glance – What Is It All About?
Single
Euro
Payments
Area
Implementation of new payment
instruments and
methods by 2008
Migration of
national paymentmethods (ti ll 201x)
Set-up of new
payment infra-structures
New data t ransfer method for
mass
payments
(SWIFT FileAct)
Establishment of new XML
payment
formats
(ISO 20022)
for SEPA
Replacement of national bank
account
numbers
by IBAN
Replacement of
national bankidentifiers by BIC
Common legal
framework byEurop.
Commission
(Payment Services
Directive)
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 7/60
Payment Instruments used in Europe*
* Source EPC - http://www.europeanpaymentscouncil.eu/knowledge_bank_detail.cfm?documents_id=183
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 8/60
©SAP 2009 / 8
PastPast TodayToday Beyond 201xBeyond 201x
Domesticpayments
Direct
debit
Credit
transfer
Credittransfer
SWIFT-Format
X-Border payments
SWIFT-Format
Europeanpayments
Domesticpayments
Direct
debit
Credittransfer
Direct
debit
Credittransfer
SWIFT-Format
XML-Format
XML-Format
National Format
X-Border payments
SWIFT-Format
Europeanpayments
National Format
Europeanand
Domesticpayments
Direct
debit
Credittransfer
XML-Format
XML-Format
X-Border payments
SWIFT-Format
SEPA Will Change the Payment Landscape
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 9/60
©SAP 2007 / Page 9
SEPA – Single Euro Payments AreaUpdate 2009
SEPA CT is live in Europe since Jan 28th 2008 Volume for SEPA transactions currently pretty low – only about 5% of the total credit transfer volume
Direct Debit planned for Q4/2009
Many uncertainties may prevent the timely launch and succesful take up of the scheme
There is currently no official end date for national credit transfers and direct debit schemes officiallyannounced
* Source ECB - http://www.ecb.int/paym/sepa/timeline/use/
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 10/60
©SAP 2009 / 10
SEPA – Single Euro Payments AreaConsequences
SEPA can be considered as a strategic topic to
optimize the whole process of the Financial ValueChain
Harmonized payment instructions for domestic andcross border payments
Credit Transfer, Direct Debit, Card payments
Can be used for domestic payments, cross borderpayments, commercial payments, Payroll payments
Points to consider
Payment structure and instruments, In-House Bank,Netting, Payments on Behalf, Centralized CashManagement
Bank Relationships and Bank Accounts
Bank communication – SWIFTNet/EBICS/Internet
Payment Formats (XML, MT, CSV, IDOC)
Bank Statement processing
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 11/60
©SAP 2009 / 11
SEPA Promise End-to-End InteroperabilitySAP Is on Both Sides
New Message Standards …
Based in UNIFI (ISO 20022) XML Message standards available for complete end-to-end communication
Ordering Customer Beneficiary Customer
Ordering
Customer’s
Financial Institution
Beneficiary
Customer’s
Financial
Institution
XML
Payment initiation
&
FIN MT 101
XML Bulk payments & FIN Category 1 & 2
XML Cash management
&
FIN Category 9
R
E
P
O
R
T
I
N
G
R
E
P
O
R
T
I
N
G
I
N
I
T
I
A
T
I
O
N
R E P O R T I N G
(I N T E R B A N K) P A Y M E N T S
XML Portfolio
FIN Portfolio
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 12/60
©SAP 2009 / 12
SEPA Package from SAP
SAP appreciates and supports the SEPA framework of the European Payment Council,improving straight-through processing and allowing increased transparency into paymentflows
SAP’s Business Suite is already enabled to help customers benefit from the new regulation
A dedicated SEPA package for the SAP Business Suite has been available since the end of 2007
SAP’s SEPA Package is available for all SAP customers with a maintenance contract that is
free of charge (SAP R/3 Enterprise onwards)
Support of new payment formats and inst ruments in SAP ERP
XML enablement of the new standard European SEPA payment formats
SEPA Credit Transfer based on EPC Rulebook 3.2
SEPA Direct Debit based on EPC Rulebook 2.3
Management of SEPA direct debit mandates
Support of IBAN and BIC SEPA Support of MT940 Bank Statements
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 13/60
©SAP 2007 / Page 13
SEPA
SAP updates planned 2010
Formats
SEPA Credit Transfer Update according to EPC Rulebook 3.2 (see SAP Note 1305012)
SEPA Direct Debit
Update to EPC Rulebook 3.3 (Core) and 1.2 (B2B)
IDOC Enhancements
Enhance PEXR2002 with new segment for SEPA related fields
– IBAN, BIC
– Mandate ID, Creditor ID, Sequence Type, Ultimate Debtor/Creditor
Applications
SAP FI
Update of mandate management according to EPC Rulebooks
In-House Cash
Support of new IDOC structure
Support of new SEPA direct debit and credit transfer Biller Direct
Support if IBAN and BIC in the UI
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 14/60
©SAP 2007 / Page 14
SAP Offering2 Alternatives of Your SEPA Implementation
Minimal solution:
„Master data undformat adjustments
have to suffice“
Streamline and OptimizeBank Communication withSAP Bank Communication
Management
Establish a payment factorywith SAP In-House Cash
Innovation
Standard Solution
SAP SEPA Package
Legal Change
Corporation
Strategic progression:
„Chance to optimize
FSCM process“
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 15/60
©SAP 2007 / Page 15©SAP 2008 / Page 15
What needs to be done
in order to send a SEPA CT to your bank
Bank to Bank
IBAN & BIC required
XML Format is mandatory
SEPA Adherence Agreement between Banks precondition
Customer to Bank
IBAN mandatory required, BIC not mandatory needed
Format – many – XML is just one option
XML, CSV, EDIFACT, SAP-IDOC, SWIFT MT, to be negotiated with the correspondingbank
BIC – SWIFT code required
! n:m relations, complex topic, bank services to use
IBAN - BIC
„Only the bank servicing an account can provide the correct International BankAccount Number (IBAN) of that account and the related Bank Identifier Code (BIC).
If you need an IBAN, you need to contact the owner of the account. If you attempt togenerate IBANs of your suppliers or other business partners, you risk having incorrectIBANs.
If you use an incorrect IBAN in your cross-border payment instructions, you risk
making payment to the wrong account or incurring a delay in payment and higherprocessing fees*.
Source: http://www.ecbs.org/iban/iban.htm#warning
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 16/60
©SAP 2007 / Page 16
How to start a SEPA project
SEPA can be considered a s a strategic topic to optimize the wholeprocess of the Financial Value Chain
Points to consider
Payment structure and instruments, In-House Bank, Netting,Payments on Behalf, Centralized Cash Management
Bank Relationships and Bank Accounts
Bank communication – SWIFTNet / EBICS / Internet
Payment Formats (XML, MT, CSV, IDOC)
Bank Statement processing
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 17/60
©SAP 2007 / Page 17
Results
Harmonized payment instructions for domestic and cross border payments
Credit Transfer
Direct Debit
Card payments
Can be used for domestic payments, cross border payments, commercial payments, Payrollpayments
Payments in EURO, within European Union, not urgent
Results
Fully automated processing of mass payments will result in high levels of efficiency
Beneficiary receives the amount within 3 days without any fees
Remittance information are not changed by the bank
Possible to use additional fields
Reporting Messages available
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 18/60
©SAP 2007 / Page 18
SEPA
Lower costs of payments
Lower total cost of ownership (TCO): fewer formats and so on
Increased transparency and better cash management forecast
Consolidation among banks
Potential for cash management centralization (Payment Factory) with SAP
In-House Cash
Replace excisting bank applications with SAP Bank Communication
Management
Reduce various cost intensive bank communication interfaces with SAPIntegration Package for SWIFT
Expected Consequences and Benefits of SEPA
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 19/60
©SAP 2007 / Page 19
1. SEPA - Overview
2. Payment Instruments and Formats
3. SEPA Mandate Management
Agenda
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 20/60
©SAP 2007 / Page 20
SEPA changes at a glance (SEPA Credit
Transfer and SEPA Direct Debit)
New formats and standards
Uniform ISO 20022 based SEPA xml format (mandatory for interbank use / recommended forclient/bank interface)
New data elements
IBAN and BIC to replace national bank code and account number
End-to-end data flow for Corporate process improvements: orderer reference field, full
remittance information, uniform standards and codes for exception processes
New processes
Harmonized execution timelines
Harmonized exception processes
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 21/60
©SAP 2007 / Page 21
New Payment Methods And Instruments
SEPA Credit Transfer (SCT)
Transfer from an originator (payer) to a beneficiary (payee) via the originator’s ownbank (originator bank), a clearing and settlement mechanism, and the beneficiary bank
SAP Note 1062489 and 1305012
SEPA Direct Debit (SDD)
Payment order triggered bya creditor (payee) to debit a debtor (payer)via the creditor bank, a clearing and settlement mechanism, and thedebtor's bank
SAP Note 1090321
Bank Statement MT940
SEPA support for MT940
SAP Note 1112530 and 1085596
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 22/60
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 23/60
©SAP 2007 / Page 23
What has been delivered so far?
For the New Payment Schemes:
SEPA Credit Transfer Scheme Rulebook
SEPA Direct Debit Scheme Rulebook
Supporting documents:
SEPA Data Model
UNIFI (ISO 20022) XML Standards Implementation Guidelines
PE-ACH/Clearing and Settlement Mechanism Framework
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 24/60
©SAP 2007 / Page 24
TodayToday 2008 – 201x2008 – 201x Beyond 201xBeyond 201x
SEPA will change the Payment Landscape
Domesticpayments
Direct
debit
Credit
transfer
Credittransfer
SWIFT-Format
X-Border payments
SWIFT-Format
Europeanpayments
Domesticpayments
Direct
debit
Credittransfer
Direct
debit
Credittransfer
SWIFT-Format
XML-Format
XML-Format
National Format
X-Border payments
SWIFT-Format
Europeanpayments
National Format
Europeanand
DomesticPayments
Direct
debit
Credittransfer
XML-Format
XML-Format
X-Border payments
SWIFT-Format
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 25/60
©SAP 2007 / Page 25
Four Corner Model: European Credit Transfer
Originator BeneficiaryNeeds to make a payment
BeneficiaryBank
Originator
Bank
Credit
beneficiary
accountCredittransfer
instructionClearing &
Settlement
Mechanisms
Debit or iginator‘s
account & send
credit transfer
message
Forwardcredit transfer
message
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 26/60
©SAP 2007 / Page 26
Definition: The Mandate is the authorization and expression of consent given
by the debtor to the creditor to allow such creditor to initiate collections for debiting the specific debtor’s account and to allow the debtor bank to comply
with such instructions…
Mandate Management
Debtor Creditor Creditor
Debtor Bank Creditor Bank
CSMs
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 27/60
©SAP 2007 / Page 27
Four Corner Model: Direct Debit
Debtor
gives the mandate to
the creditor to initiate
collections
receives the mandate
from the debtor to initiate
collections
Creditor
Signed Mandate
Creditor Bank
Mandate-related
Data Transmission
Debtor Bank
Pre-notification
Mandate
Direct Debit
Initiation
Direct Debit
ExecutionClearing &
Settlement
Mechanisms
Interbank
Message
Interbank
Message
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 28/60
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 29/60
©SAP 2009 / 29
Management of SEPA Direct Debit MandatesUsing SAP Business Suite
Features
Mandate administration including creation, change, statustracking, and deletion of mandates
Integrate the mandates and operational processes, such asperiodic payment runs – For example, each payment run willensure that SEPA Direct Debits are processed only when a validmandate exists
Apply mandate management to accounts receivable, and contractaccounts receivable and payable, so that mandate management
is useful in many industries, including insurance,telecommunications, media, and utilities
Integration to vendor/customer master data
The payment program checks the existence and validity of theSEPA mandate
The system stores the ID of the SEPA mandate in thepayment data and generates a SEPA-specific paymentmedium as a result
Print out mandates on paper using sample formsSEPA_MANDATE for PDF and SEPA_MANDATE forSmartForms
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 30/60
©SAP 2007 / Page 30
SAP Implementation
11 Creation of 2 new payment methods for:
SEPA Credit Transfer
SEPA Direct Debit
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 31/60
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 32/60
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 33/60
©SAP 2007 / Page 33
Date Medium Exchange Engine (DMEE)
Transaction
Information
Group
Header
Payment
Information
1.11.1 DMEE Configuration
Data Medium Exchange (DME) is a method of transferring payment
information by way of electronic files. (See SAP Note: 1062489)
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 34/60
©SAP 2007 / Page 34
SAP Notes
1.11.1 SEPA Credit Tansfer – SAP Notes
1062489: DMEE Format for SEPA CT
1071341: DMEE Format for SEPA CT in 4.6C
1.21.2 SEPA Direct Debit – SAP Notes
1090321: DMEE-Format for SEPA DD
1046199: Collective Note – Support for SEPA Mandates
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 35/60
©SAP 2007 / Page 35
Screenshots
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 36/60
©SAP 2007 / Page 36
SEPA Information in Account Statements
In addition to the remittance
information, theSEPA Credit Transfersand Direct Debits contain a set of special fields for the transmission of references. These reference fields canbe used by the ordering andbeneficiary party to streamline and
Automate the Reconciliation of Payments.
In order to distinguish these referencesin the account statements and toenable clients to automatically processthem across all banks, there will be a
uniform approach.
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 37/60
©SAP 2007 / Page 37
SAP Notes
1.31.3 Bank Statement Processing – SAP Notes
1112530: SEPA enhancements in MT940
1091178: Inform mandate management of returns
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 38/60
©SAP 2007 / Page 38
Enhanced IBAN solution (1)
To assign an IBAN to a vendor, creditor or business partner either:
Enter IBAN manually (bank key, bank country and bank account number
can are derived from the IBAN)
Enter bank country, bank key, bank account number (system proposes the
IBAN). Once confi rmed the IBAN is stored in the master record.
2 1
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 39/60
©SAP 2007 / Page 39
Enhanced IBAN solution (2)
Enhanced IBAN solution available as of mySAP ERP 2005
IBAN does not require a mandatory bank account number
Improved visibili ty of the IBAN
Optional activit ion (Transaction: F_TIBAN_WO_ACCNO)
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 40/60
©SAP 2007 / Page 40
SAP Notes
1.41.4 Bank Master Data – SAP Notes
1091178: Verfügbarkeit "IBAN ohne Bankkontonummer" im FI
1120972: BICPlusIBAN Directory
1019633: IBAN Schweiz und das SIC IBAN-Tool
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 41/60
©SAP 2007 / Page 41
Outbound delivery
SEPA Credit Transfer SP29
SAP R/3 Enterprise
SEPA Credit Transfer SP17 und SP18
SEPA Credit Transfer SP11 /EhP1 SP01 /EhP2 SP00
SAP ERP 2004
SAP ERP 6.0
Prerequisite:
- maintenance contract
Delivery asSupport
Package(s)
since Q3/2007
SEPA DD and third-party management SP12EhP2 SP02 /EhP3 SP00
SEPA DD and third-party management SP19
SEPA DD and third-party managementSP30
Further information/advice:- SAPNote 1062489- SAPNote 1090321- SAPNote 1071341
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 42/60
©SAP 2007 / Page 42
SEPA Competence Center
http://service.sap.com/SEPA
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 43/60
©SAP 2007 / Page 43
1. SEPA - Overview
2. Payment Instruments and Formats
3. SEPA Mandate Management
Agenda
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 44/60
©SAP 2007 / Page 44
Activation of the Mandate Management
•Activate it and determine the number of usehistory
•Include subscreens
•Add Function Modules that make datasupplements and further checks
•Define a form name for printing SEPAMandates
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 45/60
©SAP 2007 / Page 45
Use in Multiple Applications
•SEPA can be used by several applications: FI-CA, FI, Banking
• The system determines the default application, however it can be changed
•When the Mandate is displayed or changed the system determines automatically theapplication it belongs to
FSEPA_M1
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 46/60
©SAP 2007 / Page 46
Creating, Displaying and Changing Mandates I
• The dialog transactions for the SEPA Mandates are found under Accounts
Receivable -> Master Records
• The prerequisite is the activation and customizing presented previously
•Five new transactions facilitate the management of mandates:
• Create
• Change
• Display
• List
• Create in mass run
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 47/60
©SAP 2007 / Page 47
Creating, Displaying and Changing Mandates II
Features
In the dialog transactions for creating, displaying, and changing mandates, you can select dataon the initial screen using the following criteria:
Mandate
ID of vendor
IBAN
Business partnerContract account
Contract
Company code
If the system determines there is more than one mandate that meets the criteria, then it displaysthe results in a list in a dialog box. Double click on a row in the list to see detailed information for
it. In the detail view, the data for the mandate is displayed on the following tab pages:
On the initial screen, you can lock all existing mandates for the IBAN of the business partnerand the vendor ID by choosing the pushbutton Global Locks in the toolbar.
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 48/60
©SAP 2007 / Page 48
Creating, Displaying and Changing Mandates
III
Tab page Function
Basic data Shows the status, the validity, and the administrative data
Sender Shows the address and bank data of the sender of themandate (business partner)
Recipient Shows the address of the recipient of the mandate (companycode)
Use Shows the use of the mandate by the payment program
Versions Shows older versions of the mandate
When you save, the system (in the standard system) creates a twelve-character ID for eachmandate. If you want to have an ID that differs from this standard setting, then define event0570.
The functions for creating, displaying, and changing SEPA mandates are protected byauthorization objects F_KKSEPA and F_SEPA_MDT.
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 49/60
©SAP 2007 / Page 49
Maintaining Mandates in Payment Data
Processing
• You can create, change, and display mandates not only in the dialog transactions
specifically for this, but also in the processing transaction for payment data.
Prerequisites
For you to be able to create mandates for bank data, an IBAN has to be entered inthis bank data.
FD02
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 50/60
©SAP 2007 / Page 50
Maintaining Mandates in Payment Data
Processing II
By clicking the system automatically enters the data from the business partneron the Sender tab page, and the data from the company code on the Recipient tab page.
Subsequent changes to the address and bank data do not automatically result in changes tothe entries in the mandate.
If you want to specify your own default values that are different from these, define event 0572. The system specifies the default value for the vendor ID in event 0571. If you want a differentvalue, implement a customer-specific function module for event 0571.
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 51/60
©SAP 2007 / Page 51
Maintaining Mandates in Payment Data
Processing II
•After having filled out the status, validity and
generated the supplement data thecompleteness of the mandate can be checkedby choosing
• Thereafter, the mandate can be printed bychoosing
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 52/60
©SAP 2007 / Page 52
Printed Mandate
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 53/60
©SAP 2007 / Page 53
Maintaining Mandates in Payment Data
Processing III
• To change Mandates in the Payment Data Processing, choose
• The system selects the mandates that are assigned to the business partner andIBAN, and displays them in a dialog box.
•If the system is not able to find any mandates, it opens a dialog box and asks you tocreate a mandate. To create a mandate, confirm the dialog box and proceed asdescribed above.
•Select the mandate you want to change by double-clicking.
•Enter your changes and choose Continue.
In the same dialog box, you have the option of creating new mandates or creating
them with a template. Choose either the pushbutton or the pushbutton.
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 54/60
©SAP 2007 / Page 54
Creating Mandates in Mass Runs I
Generates mandates for the corresponding bank details in the Payment Transactionmaster records of the accounts receivable
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 55/60
©SAP 2007 / Page 55
Creating Mandates in Mass Runs II
Prerequisites:
•An IBAN has to be defined in the master record of the customer
•In the Bank Details the Collection Authorization selection box must be checked
•A corresponding SEPA Payment Method must be defined in the master record of thecustomer
• The items Foreign business partner allowed and Cust/vendor bank allowed abroadshould be checked in the Payment methods in company code customizing
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 56/60
©SAP 2007 / Page 56
Creating Mandates in Mass Runs III
In the output control of the Mass creation transaction, there are two importantcheckboxes to consider:
•No Duplicates: If checked, the system does not create a mandate when a bankaccount has already an assigned mandate
•No Partial Run: In this case, the system does not make any changes to the databaseor archive if an error occurs (all or nothing).
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 57/60
©SAP 2007 / Page 57
SAP Collaterals
Source: http://www.sap.com/treasury
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 58/60
©SAP 2007 / Page 58
Documentation
http://help.sap.com/erp2005_ehp_04/helpdata/en/9a/4de506f0c24412b51fb65301e9
901d/frameset.htm
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 59/60
©SAP 2007 / Page 59
Thank you!
Christian Mnich
SAP AG
Dietmar-Hopp-Al lee 16
69190 Walldorf
7/27/2019 Solution Overview Presentation - SEPA
http://slidepdf.com/reader/full/solution-overview-presentation-sepa 60/60
Copyright 2009 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 changedwithout prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP®product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Webpages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentumanderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP -Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP . Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne E inschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.
Alle Rechte vorbehalten.
Top Related