Académique Documents
Professionnel Documents
Culture Documents
Product Manager
SAP AG
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
CD-ROM
3%
Disk
3% Paper Only
71%
Tape
2%
70 bio.
60 bio.
50 bio.
Bills per year
40 bio.
30 bio.
20 bio.
10 bio.
0 bio.
2000 2001 2002 2003 2004
World Europe*
Europe UK
Germany
31,72% 8,64% 7,18%
Italy
6,13%
North America
54,41%
France Sweden
7,32% 0,98%
Asia
13,87% Norway Denmark Finland
0,42% 0,49% 0,56%
* percentage of ww figures
Worldwide 144 billion transactions
Source: IBM Corp./Dove Assoc. 1999
Traditional Billing:
Billing:
Biller
Payer
Create Send
Create Send Reconsile
Paym. Paym. Dunning
Bill Bill A/R
Remind. Remind
Biller
Receive/
Check Dispute Payment Archive
Down-
Bill Bill Order Bill
load Bill
Payer
Source: PSW3/DMR
$ 10.00
$ 8.00 $ 7,17
$ 6.00
$ 4.00
$ 2,30
$ 2.00 $ 1,45
$ 1,12
$ 0,56
$ 10.00
$ 8.00 $ 7,17
$ 6,67
$ 6.00
$ 4.00
$ 2,67
$ 2.00 $ 1,73
$ 0,17
Cross-selling opportunities
Stickiness of participants
9000
8000
Number of billers
7000
6000
Low -volume
5000
Medium-volume
4000
3000 High-volume
2000
1000
0
2000 2001 2002 2003 2004
Others
13% Faster collection
25%
Automatic
Processing
6%
Fewer returns
15%
Less work
41%
Source: Gartner 1999
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
Customer
Invoice/Push Model (E-mail notification)
Biller 2 Invoice/Pull Model
Thick Consolidation
Thin Consolidation
Invoice details & marketing data
2. Invoice
Biller 3. Access/Payment Authorization Customer
Clearing
BSP Biller
Consolidator Model Service
(sender-oriented) Provider
Biller Customer
CSP Customer
Consolidator Model Service
(receiver-oriented) Provider
Biller Customer
Proprietary Consolidator
Consolidator Model and/or
Switch
Biller Customer
1. Invoice File
BSP Biller 2. Access/Payment
Consolidator Model 3. Remittance
Service Authorization
(sender-oriented) Detail File Provider
Biller Customer
Seller Buyer
4b. Payment
6a. Bank Order 6b. Bank
statement statement
Other Sellers Other Buyers
E-Markets
5a. Buyer Initiated Credit Payment 5b. Buyer Authorized Debit
Gateway
Billers Bank Customers Bank
(Biller Payment Provider) (Customer Payment Provider)
Direct Biller:
+ Lower transaction costs
+ Suitable for large billers (min. 1 mio. invoices p.a.)
+ Control of invoice layout
+ Control of data access
+ Data analysis and reporting capabilities
Higher implementation and maintenance costs
Customers need to visit different web sites to see their bills
(Thick) Consolidator:
+ Implementation and hosting done by consolidator
+ Outsourcing of accounting possible
+ Lower transaction costs
+ One central invoice repository for customers
Sensitive data is transferred to consolidator
No direct customer access
Potential liquidity disadvantage
SAP AG 2001 Product Management GBU Financials
Consolidators: Three Times More Than Biller Direct
3000
Number of bills (mio.)
2500
Portals/others
2000
Consolidators/BSPs
1500 PFMS
Bank CSPs
1000
Biller Direct
500
0
2000 2001 2002 2003 2004
Banks can act as both CSP and BSP as well as billers contributing
their own bills for payment
Portal AOL
7% 13%
PFM
37%
Bank Broker
42% 1%
Source: Jupiter Communications 1999
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
open interfaces
AP Cash Orbian
Orbian
BL Cash
Cash Cash
AR TM Management
Management
CA CFM
CFM
Sales Channels:
1. Market Places
2. Company Portales Order Handling
3. Direct Sales
4. ....
Credit Check
Credit Management:
One central Credit-Linit for
all sales channels
Link to third party services
Customer Contact via EBPP
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
Customer
Invoice/Push Model (E-mail notification)
Biller 2 Invoice/Pull Model
Thick Consolidation
Thin Consolidation
Invoice details & marketing data
Bill
Overview mySAP
Credits
Financials
Offset Overview
Integration
Credits With Bill Detail
Open items Dispute mySAP.com
Message Integration
E-mail Payment Flexible
Notification History Layout
Partial Credit Card
Payments Direct Support
Debit Support
Customer
creates a
purchase order
using the
Internet Sales
Service of their
supplier
PC4BIZ
Supplier
receives the
customers
order
The order from
the Internet can
be processed
directly in R/3
Customer
receives e-mail
containing an
Internet link
that provides
access to the
EBPP B2C
scenario
Customers can
see all of their
invoices in the
Internet
It is possible to
display the
orders for each
invoice
Customer can
authorize
payment by
credit card or
direct debit
Credit memos
can be used for
payment
The supplier
receives the
information
about the
payment
authorization in
the R/3 system
real time
Reduction in Information
Up to 25%*
telephone and about whether
postal costs or not the Up to 10%*
vendor has
Clear and received the
precise payment
Up to 10%*
information
received from
customers
Source:
* Discussions with customers
Reports can be
obtained
without
Up to 10%*
needing to call
and ask the
Source:
vendor
Vendor is
unable to
assign
payments from
customer to
receivables in
AR Accounting,
or needs further
information
Vendor sends
an e-mail
requesting that
the customer
provides details
of assignment
Customer
receives e-mail
containing an
Internet link
that provides
access to the
EBPP B2B
scenario
Collaborative
Account
Statement
Customer logs
on to the EBPP
B2B scenario
Collaborative
Account
Statement
Vendor defines
which accounts
the customer
has access to
Customer has
an overview of
the open items
and can carry
out assignment
Customer can
display the
master data and
change it
Customer can
display
balances and
give the balance
confirmation
Customer has
an overview of
his account,
including all
payments made
and all open
items
Customer
carries out
assignment
(possibly with
notes)
Customer has
an overview of
the assignments
made
Customer can
add further
notes to his
assignments
Customer has
an overview of
the balances,
sales volume,
and line items
Customer can
download this
information into
Excel
Customer has
an overview of
the balances
and can confirm
the balance
online
Customer can
download this
information into
Excel
Customer has
an overview of
his master data
and bank data
Customer can
change this data
and send it
back to the
vendor online
Accountant
receives
notification via
workflow
Accountant
checks
customers
assignment and
clears open
items
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
Company Network
+ + Billing details
and assignment
H H of open items
T T
T T
P P Billing Application
S S (e.g. SD, CRM
Billing)
Browser
HTTP Response
use of
BO bank
- attributes Struts-config.xml
BO bill
- attributes Java Beans
makes use of
JSP
Class
Files
Key value pairs SAP Java Connector (JCO)
Dispatch Business
Controller
(Servlet) 2 Logic
Event (Action)
HTTP Request
1
Client Struts-config.xml
(Browser) Forward
4 3
Update 6
HTTP Response
View Model
(JSP) 5 (Application
State)
Get
<Tag>
Source: IBM
SAP AG 2001 Product Management GBU Financials
SAP Java Connector: Architecture
SAP System
J2EE Ingredients:
Design and programming model to create multi-tier applications
Platform (APIs and XML-based configuration tools)
Reference implementation (application server which demonstrates
J2EE capabilities)
Test suite (to test compatibility of components with J2EE platform)
J2EE characteristics:
distributed applications based on Java
components architecture
embedded in internet technology
includes several programming paradigms (e.g. Client-Server, 3-tier
architecture...)
Benefits of JSPs:
Separation of design and business logic
Java servlets can be displayed as HTML pages
processed
HTML
page
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
Release 3.0
(B2C/B2B: GA)
Release 2.0
(B2C: GA/B2B: CA)
Release 1.0
(B2C/B2B: CA)
Demo Version
(B2C: Charter Cl.)
1 Why EBPP?
2 EBPP Models
6 Roadmap
7 Summary
Cost savings
CRM Enhancement
Reduction of float
AMR, 2001
Link: EBPP
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.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered
trademarks of Microsoft Corporation.
IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400,
OS/390, and OS/400 are registered trademarks of IBM Corporation.
ORACLE is a registered trademark of ORACLE Corporation.
INFORMIX-OnLine for SAP and Informix Dynamic ServerTM are registered trademarks of Informix
Software Incorporated.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP
EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the
world. All other products mentioned are trademarks or registered trademarks of their respective
companies.