Unit 7 - SAP FSCM Biller Direct
Unit 7 - SAP FSCM Biller Direct
Table of Contents
SAP Biller Direct supports the entire communication process, from presenting the bill to clarifying discrepancies
and reconciling accounts and payments.
SAP Biller Direct is a Java-based application, which allows organizations to work closely together with their
customers and partners.
Definition of EBBP
EBPP is a platform used by billers and customers to send and pay bills electronically.
The customer downloads the bill electronically from a link to a server set up by the biller, or opens the
The biller sends bills electronically to the consolidator, which then converts the format as necessary
and posts the bills with the appropriate value-added tax to the relevant customer.
Biller Direct
1:n relationship (point-for-point)
You can present the bill in the portal, send a URL, and the customer can manually process the
bill.
Customer licenses the software and installs it.
If there is a strong increase in sales, this is not beneficial for customers who receive their bills
from several portals.
Biller Consolidator
n:m relationship (network)
You send the bill to the customer's ERP system or present the bill in the portal.
Service provider provides the service and the customer pays for this service.
Customer does not install any software requiring a license, but connects instead to the
Consolidator
If there is a low increase in sales, the network efficiency is not used to its advantage.
7.1.1 Summary
SAP Biller Direct is a Java-based component of SAP Financial Supply Chain
Management, and along with SAP Biller Consolidator provides an SAP solution for
electronic bill presentment and payment (EBPP).
By using SAP Biller Direct, the customer receives the electronic bill either by
downloading from a link (text message or e-mail) to a server set up by the biller, or by
opening the file directly as an e-mail attachment. The customer can then carry out
further activities electronically (for example, approving payments, clearing credit for
invoices, or creating requests or complaints).
Along with the processes set previously in the B2C scenarios, SAP Biller Direct can also
be set up for different B2B scenarios, such as assigning open items, comparing
balances, maintaining master data, or preparing reports. As an alternative to the
services offered by service providers to their customers, Biller Direct can also be used as
a service offered by customers to their service providers, and can be used to track
invoices assigned to customers in the customer system (payer direct).
Web user: a user who logs on to SAP Biller Direct using the Web browser and processes data
from there (for example, the person at the business partner responsible for paying the bills over
the Web); the Web user is created as a user in the back-end system – however, you cannot
assign an individual role or profile to this user.
Reference user (also: Communications user): a user in the back-end system (with a "reference
user" attribute) that is assigned to the Web user in master data maintenance, and that also has
the authorizations and roles that the Web user should have (for example, you can create an
individual communications user for read access only); for performance reasons, the
authorization profile is not assigned directly to the user master record of the individual Web
user, but instead indirectly using reference users
Pool user: a technical user with which data is transferred and which is used for read (or in
certain cases also write) access to the back-end system (improved load control and
performance)
To manage Web users who display and edit their bills using SAP Biller Direct, you must make the
following settings in the master data:
One user master record for each Web user: You must create a user master record in SAP
Accounts Receivable Accounting for each Web user who accesses SAP Accounts Receivable
Accounting. The relevant customer (with reference to the BUS3007 object) and a reference user
with the required authorizations are then assigned to this master data record.
Several reference user master records: A reference user master record is created for each
authorization profile.
One pool user master record: allows read access in the back-end system; by bundling Web users
who have display authorization only, you can improve performance without compromising data
security at the same time.
7.1.2 User Logon to SAP Biller Direct and Authentication SAP Biller Direct
In the scenario shown here, the Web users are created directly in the SAP ERP system.
All Web users are authenticated using their Web user accounts (user name and
password) that are defined in the SAP ERP system.
At the time of logon, the Java front end reads the relevant authorizations from the
reference user assigned to the Web user.
The customers assigned to the Web user (when the master data is maintained) are read
from the USAPPLREF table in the SAP ERP system.
SAP Biller Direct also supports authentication using external directory services. In this
case, user data is not saved in the SAP ERP system, but instead on a server that is
addressed by LDAP (Lightweight Directory Access Protocol). LDAP was conceived as an
open standard for global or local directory services in a network or on the Internet. In
principle, a directory is treated in the same way as a telephone book. The directories
have been set up to support a high volume of inquiries, but the data in the directory
should not be changed very often. SAP recommends using LDAP to map large user
numbers because: :
LDAP has been optimized for reading large user numbers.
LDAP optimizes performance compared to user management in SAP (this is due
to technical limitations).
LDAP can take user data from the SAP system, therefore facilitating user data
administration.
All Web users who display and pay bills using SAP Biller Direct have to authenticate themselves.
This can be done in the following ways:
The Web user enters a user name and password. The system then carries out an
authentication check with the user master record (of the Web user), which is created in
the back-end system.
A single sign-on ticket (SAP SSO2 ticket) is transferred. If the Web user has already
logged on to a portal and called SAP Biller Direct in this portal, no further logon is
necessary if the portal supports the SAP SSO2 ticket. The portal system (for example,
SAP Workplace) has already authenticated the user and retains the user data in the
form of an X.509 certificate. SAP Biller Direct then evaluates this SSO2 ticket and grants
the user access.
Summary
In order to manage Web users, who display and edit their bills using SAP Biller Direct, you must
create a user record for each Web user in the SAP ERP system used as a back-end system. You
have to assign the corresponding customer and reference user to this record to control the
authorization. In addition, a pool user is defined in the SAP system to manage the technical data
transfer from the back-end system to the SAP Biller Direct front end (above all for read access).
The authentication of the SAP Biller Direct user can be checked against the SAP system defined
as the back-end system, or against other, external directory servers. The authentication in SAP
Biller Direct can also be linked to the single sign-on process.
The following objects from SAP Accounts Receivable Accounting or other components are
displayed in SAP Biller Direct:
Bills: can come from different billing components (for examples, SAP Sales or CRM). To
display the bills in the Web application, the components transfer their billing data to a
shared interface.
Open items: items in the customer account of SAP Accounts Receivable Accounting
(outstanding receivables, payments made, credit memos, payments on account, down
payments, and bill of exchange)
Inquiries/Complaints from a customer entered using SAP Biller Direct are stored in the
customer's account as texts for the original bill, or as a dispute case in SAP Dispute
Management.
Master Data: (for example, addresses, bank details, control parameters) is primarily
displayed in master data fields.
7.3.2 Administrative Data in SAP Biller Direct/Maintain user data in SAP Biller Direct
Along with the address, bank details and so on, the following control parameters are
displayed and managed in the user data in SAP Biller Direct:
Notification of a new bill or credit
Type of notification (text message, e-mail) and corresponding addresses
Notification period
Additional creation of a paper bill
If you change the master data in the Web application (for example, you create new
bank or credit card details for payment or in the user data), the corresponding master
data objects are immediately updated in the SAP back-end system. Therefore (for
example) if you change the customer's address, the address is changed immediately in
the SAP ERP system, and new bank or credit card master data is defined immediately for
the SAP customer.
Alongside these immediate updates in the SAP system, you can also configure the use of
an internal service request for the master data changes, so that a processor along with
the biller must first release the changes before they take effect.
If a customer adds new bank or credit card master data, an internal plausibility check is
carried out in the SAP system. For example, the validity of the bank number and account
number is checked, or whether a credit card number belongs to the correct credit card
organization (this is done using the credit card check digit).
The customer payments that have been confirmed in the Web application appear in the
application as allocated. Only when you run a payment program are the relevant bills
cleared and payments can no longer be reversed.
As long as the allocated bill has the status In Process (until the payment run is carried
out), the only account-based difference between the allocated bill and an open bill is
that the allocated bill has the specific payment method for SAP Biller Direct.
For these bills, the Web user can stop the payment by displaying the bill, choosing Paid
Bills, and clicking Cancel Payment in the Action column.
The payment method and the bank details are then removed from the relevant item,
the bill is reassigned the status Open and it reappears on the Open Bills tab page.
o The bill approval function can be activated in the customer's user data in SAP Biller
Direct.
o During billing, a payment block is then set automatically for documents posted in SAP
Accounts Receivable Accounting. This payment block is removed only when the
customer has approved the bill in SAP Biller Direct (under "Invoices to approve").
Summary
A customer can use SAP Biller Direct to display open and paid bills, credit memos, and
payments. Bills can be downloaded in XML (and PDF) format.
Customers can display and maintain their own administrative data (address data, bank
data, credit cards, user name, and password).
To settle open bills, the customer can pay one or more of the bills in full or in part, or
clear it/them using a credit memo. The customer can select payment by credit card or
automatic debit, or enter new payment details. In the case of inquiries or complaints,
comments ordispute cases can be created for the bills.
Provided that the bill selected for payment is still In Process, the customer can cancel
the payment.
The customer, who uses SAP Biller Direct to display account and billing information, can be
informed automatically of changes to the account by various means of communication. Such
changes can be caused by new bills or credit memos.
Included in these communication methods are text messages (short message service) for cell
phones, and e-mails (encoded if required). In the latter case, the customer receives an e-mail that,
along with the general information about the bill, can contain a hyperlink that takes the customer
to the biller's portal page. This way, the biller avoids having to send a bill in paper form. The
following notification formats are possible within the e-mail:
o Plain text (text only e-mail with links)
o HTML
o PDF attachment (SAP Accounts Receivable Accounting only)
o Combination of plain text or HTML with a PDF attachment
To send the notification from the SAP system, one of the certified system interfaces is required
(RDI, SAPconnect, or the SAP spool system).
When the customer uses SAP Accounts Receivable Accounting, inquiries can be made in SAP Biller
Direct about a bill, credit memo, or partial payment. SAP Biller Direct creates a text for the item
with the entered comments. The processor can display this text using Extras Texts, and respond
to it, for example, by sending a reply.
Additionally, the EBPP_AR_CONTACTS report provides a list of documents for which SAP Biller
Direct texts have been entered:
You can find the relevant documents by searching according to the entry date of the
comment.
To create a reply, select the relevant document from the list and choose Display text.
A screen appears, which contains the text that the customer entered. You can then
enter your reply.
Above the reply, the system generates a heading that indicates that the text is a response.
As of SAP Biller Direct 3.0, customers can create dispute cases in SAP Dispute Management directly
using SAP Biller Direct. Dispute cases can be created for both partial payments and entire bills. The
minimum system prerequisite for this scenario is R/3 Enterprise or FI-CA 4.72.
Internal processing of dispute cases can start immediately after a dispute case has been created in
the SAP back-end system.
If SAP Dispute Management has been activated, the (basic) contact management solution can no
longer be implemented.
Summary
The customer, who uses SAP Biller Direct to display account and bill information, can be informed
automatically of changes to the account (for example, of new credits or bills) by various means of
communication (text message or e-mail).
Inquiries or complaints can be entered on the SAP Biller Direct interface directly as a comment
(contact management integrated in SAP Accounts Receivable Accounting) or as a dispute case in
SAP Dispute Management.
By configuring the Java components in SAP Biller Direct and by implementing BAdIs in SAP Accounts
Receivable Accounting, the following settings for SAP Biller Direct can be made:
Setting the Web user documentation, the interface texts, and the interface design
Setting the language
Setting the SAP Biller Direct session and the Web user's display of bills, payments, and
credits
7.4 SAP Biller Direct System Architecture
* Integration with SAP Dispute Management is available as of R/3 Enterprise or FI-CA 4.72 only.
The following SAP components can be integrated as a back-end system:
SAP Accounts Receivable Accounting (at least FI-AR as part of SAP R/3 4.6C)
SAP Contract Accounts Receivable and Payable (at least SAP FI-CA 4.64)
The biller is using, for example, SAP Accounts Receivable Accounting in release SAP R/3 4.6C:
o The biller is also using an SAP Web Application Sever on which SAP Biller Direct is installed.
o The back-end system on the SAP Application Server ("ABAP environment") communicates with
the front end SAP Biller Direct using Remote Function Call (RFC).
o The customer requires a Web browser to display bills and customer information.
o To access the Biller Direct front end, the customer logs on to the Web server with a user ID and
password.
Use :
The purpose of this activity is to determine whether the web users can release their bills for payment by
payment card.
Configuration :
Manu Path IMG FSCM Biller Direct Process Integration with Accounts
Receivable Accounting Release Credit Cards
On the change view “ Additional Payment Method classes” Overview screen, Choose new Entries.
Save
Use :
The purpose of this activity is to create separate payment methods for SAP biller Direct, so that the web
user can make payment using either bank collect ( automatic or debit ) or credit card.
Configuration :
Manu Path IMG Financial Accounting Accounts Receivable and accounts payable
Business Transactions Incoming Payments Automatic Incoming
Payments Payment Method/Bank Selection for Payment Program Set
up Payment Methods per Country for Payment Transactions
Transaction Code
On the change View “ Payment Method/Country”: overview Screen, Choose new Entries.
Country IN
Pmt Method
Description Biller Direct bank Collection
Payment Method for Incoming Payments
Payment Method dassification : Selected
Debit Memo
Bank Details Selected
Document Type For Payment DZ
Clearing Document Type DZ
Use Classic Payment medium
Program ( RFFO* )
Payment Medium program RFFOD_U
Key in Code line 05
Name of Print LIST3S
Country IN
Payment Method XXX
Description Biller Direct Kridit Karte
Payment Method for Incoming Payments
Payment Method dassification : Selected
Card Payment
Document type for Payment DZ
Clearing Document Type DZ
Use Classic Payment medium Selected
Program ( RFFO* )
Payment Medium program RFFOD_U
Save
The Purpose of this activity is to assign the SAP biller Direct payment methods to the company code.
Configuration
Manu Path IMG Financial Accounting Accounts Receivable and Accounts Payable
business Transactions Incoming Payments Automatic Incoming
Payments Payment Method/Bank Selection for Payment Program Set
Up Payment Methods per Company Code for Payment Transactions
Transaction Code
On the change View “ Maintenance of Company Code data for a Payment Method” Screen, Choose New
Entries.
Save
The purpose of this activity is to define the bank determination and bank clearing accounts for the bank
collection ( automatic debit ) payment method of SAP Biller Direct
Configuration
Manu Path IMG Financial Accounting Accounts Receivable and Accounts Payable
business Transactions Incoming Payments Automatic Incoming
Payments Payment Method/Bank Selection for Payment Program Set
Up bank Determination for Payment Transactions
Transaction Code
On the Display view “ Bank Selection”: Overview screen, Select the xxx ( Paying company code ) line, and
choose Ranking Order.
Pmt method
Currency INR
Rank Order 1
House Bank DB
House Bank XX
Pmt Method X
Currency INR
Account ID GIRO
Bank Subaccount xxxxx
The purpose of this activity is to specify which payment methods can be used is SAP biller Direct.
Configuration
Manu Path IMG Financial Accounting Accounts Receivable and Accounts Payable
SAP FSCM SAP Biller Direct Edit Payment Methods
T Code
On the change View “ maintenance of EBPP Payment Methods : Overview screen, choose new Entries.
Save
9 Assign Text ID
The purpose of this activity is to define the text ID used in SAP biller Direct when a Web user creates
inquiries, complaints and give reasons for any partial payments.
Configuration
Manu Path IMG Financial Accounting Accounts Receivable and Accounts Payable
Business Transactions Incoming Invoice/Credit memos Carry Out
and check Document Settings Define Text Ids for Documents
T Code
On the maintain Text Determination Configuration : List screen, make the following entries:
ID 005
Description Correspondence Biller Direct
Relevant Text Selected
Save
The purpose of this activity is to assign the text ID to be used in SAP Biller Direct
Configuration
Manu Path IMG Financial Accounting Accounts Receivable and Accounts Payable
SAP Financial Supply Chain Management SAP Biller direct Assign
Text ID
T Code
On the change View “ text Ids for Biller Direct complaint texts”: Details screen, make the following
entries :
Text ID 005
Save
The purpose of this activity is to specify whether Web users can make partial payments, partial
settlement of credits in SAP Biller Direct.
Configuration
Manu Path IMG FSCM Biller Direct Process Integration with Accounts
Receivable Accounting Define Partial Payment and Currency
T Code
On the Change View “ Biller Direct Settings for Business Partner” Overview screen, Choose New Entries.
The purpose of this activity is to output types used by the notification process.
Configuration
Manu Path IMG Sales & Distribution Basic Functions Output Control Output
Determination Output Determination Using the Condition Technique
Maintain Output Determination for Billing Documents Maintain Output
Types
T Code
Select the FINO ( Output type ) line, and choose Processing routines.
On the Change View “ processing routines”: Overview screen, Choose New Entries.
Use
The Purpose of this activity is to define the output determination for documents.
Configuration
Manu Path IMG Sales & Distribution Basic Functions Output Control Output
Determination Output Determination Using the Condition Technique
Maintain Output Determination for Billing Documents Maintain Output
Type Determination Procedure
T Code
On the change View “ Procedures”: Overview screen, Select V10000 ( Procedure ) line, and choose
control data.
Sapphire Global Consulting Services | SAP FSCM – Unit 7 : Biller Direct 25
SAP FSCM – Unit 7 Biller Direct
Use
The purpose of this activity is to specify a range of numbers that are acceptable for each credit card.
Configuration
Manu Path IMG Sales & Distribution Billing payment Cards Maintain Card
Categories Determine card categories
T Code
On the change View “ Payment Cards” : Determine Categories”: Overview screen, choose new entries.
Type AMEX
Seq 1
Cat 01
Choose Limit Checkmark.
Choose Execute.
Type VISA
Seq 1
Cat 01
Choose Limit Checkmark
Type MC
Seq 1
Cat 01
Use
The purpose of this activity is to define and link for each payment card type a receivable account.
Configuration
Manu Path IMG Financial Accounting Accounts receivable and Accounts Payable
SAP FSCM SAP Biller Direct Set Account Determination for Credit
Cards
T Code
On the Determine Work Area : Entry screen, enter BP01 as Paying Company Code, and choose Enter.
Use
The purpose of this activity to define and link for each payment card type a receivables account.
Configuration
Manu Path IMG Sales and Distribution Billing Payment Cards Authorization
and Settlement Maintain Clearing House Account Determination
Assign G/L Accounts
T Code
On the Assign G/L accounts screen, select a Salse org/Card cat. Line.
On the change View “ Sales Org/Card cat”: Overview screen, choose new Entries.
13 QISRSCENARIO Configuration
Configuration
T Code
14 Master Data
The purpose of this activity is to create condition records used in the billing document for sending
notification messages
Manu Path Easy Access Logistics Sales and Distribution Master Data Output
Billing Document Create .
T Code VV31
On the Create output – Condition Records : billing screen, make the following entries:
On the key Combination screen, select billing Type and choose Enter.
On the Create Condition Records ( Send Link Immediate ): Fast entry screen, make the Following entries.
Choose Communication
On the Credit Output condition Records : Billing screen, make the following entries :
On the create Condition Records ( send Link per job ): Fast entry screen, make the following entries:
Choose Communication.
Choose Save
On the Create Output Condition Records : Billing screen, make the following entries:
On the key Combination screen, select Billing Type and Choose Enter.
On the Create Condition Records ( Send Link per Job ); Fast Entry screen, make the following entries :
Choose Communication
Customer :
Company Code :
Choose Enter
3. Choose the payment transaction tab and enter the following bank details:
Ctry : IN
Bank Account : x
BnkT : E000
Type : MC,
Valid to : 12/2008,
Cat :01,
1. In this step you enter a valid email address for the company code
2. Access the transaction using transaction code SM30.
3. In the Maintained Table view : Initial Screen enter V_T001 in the Table/View fields, choose
Maintain.
4. Double-click on company code BP01
5. Choose the address icon ( or select Goto – Address or context menu – address ).
6. Enter a valid email address in the Email Fields.
7. Choose other communication.
8. Select INT ( Communication Methods ), and choose Enter
9. Make sure that the Checkbox for field Standard number is selected.
10. Save your entries.
Use
The purpose of this activity is to grant additional profiles to SAPJSF SU01, so that requests for
Biller Direct registration can be processed.
Configuration
On the user maintenance: initial screen, enter the following information and choose change.
SAP_BC_JSF_COMMUNICATION is
listed here.
Choose Save
Use
The purpose of this activity is to create an implementation for APAP_EBPP_NOTIFY2 BADI that
will crate the content of the notification email message.
Configuration
The purpose of this activity to assign a number range object to the notification type.
Configuration :
Use
You only need to configure the JCO RFC server if you are using passive enrollment to register
end users of SAP Biller Direct – that is, if customers fill out an application online to request a
user for SAP Biller Direct.
Configuration :
Unicode Selected
Default Settings Selected
Choose Save and back
9.4.2.5 Configuration of the Logo dialog for Biller Direct user creation ( optional )
Use
You only need to perform this activity id the logon dialog to create an user for the Biller Direct Scenario
does not contain the field ‘Business partner’, but display two fields for password entry. Please check the
Business Procedure for Scenario W22 to fin the proceed user for user creation with the Biller Direct Web
Front end.
Functional Overview
Customers can see all of their bills and credit notes in the Internet.
Customers can create dispute cases for both partial payments and the entire invoice
They can select a contact person out of the customer contact list
Suppliers can see all of their invoices including their status (e.g. if they are paid or not)
They can also view additional payment information (e.g. check number)
Business Benefits
Lower cost of billing with no printing and postal charges
Efficient processing of payments and exceptions including better explanation of payment deductions
Data integration with accounts receivable, accounts payable, cash management and dispute
management