Biller Direct Case Study

Embed Size (px)

DESCRIPTION

Biller Direct case explanation

Citation preview

  • Biller DirectStreamline Cash Processing and Enhance the Customer Experience

    Mike MartinMonsanto

  • *What Well Cover Business drivers behind Monsantos implementationOur implementation timelineReview standard and customization options available through Biller Direct Identifying business requirements Understanding application challenges Key learningsDemo

  • Business DriversIncrease customer satisfactionAccess to financial statusOnline delivery of Invoices, Reports and StatementsCustomer expectationsInefficient order-to-cash processPayment processing efficienciesLarge volume of paper invoices and statementsCost of invoicing and reconciliationSignificant online application use by our customersCustomers expect online payment capabilityGlobal solution

    *

  • Return on InvestmentReduce order-to-cash cycle timeAccess to invoicesNext day access following order fulfillmentIncrease working capitalOpportunity to reduce delay in cash receipts up to five daysCost savingsLockbox cost reductionsLimits staff requirementsOnline payments significantly limit exception processingPrint and mailing opportunities Enables online-only receipt of documents and reports*

  • Timeline Biller Direct 2012 rollout to 12 businesses integrated to SAP ERP Central Component*Development to Pilot LaunchPhase 2 to Company-wide launchFrench language for CanadaSAP ECC 6.0 UpgradeCanada launch

    200720082009 MAR OCT MAY OCT JAN MAR

  • Standard Biller Direct FunctionalityOpen billsDisplay/downloadPay (partial or full)Clear credits/debitsPaid billsDisplay/downloadIn processProcessed30 days/12 months/5 years/ Unlimited (Response time impact)Cancel PaymentView bills associated with paymentCreate Payment Advice/Display Payment Advice*

  • Standard Biller Direct Functionality (cont.)Balances and line itemsDownloadMonthly balances (Debit/Credit/Balance/Sales)Administrative dataUpdate addressCreate/Change/Delete Bank DetailsChange/Withdraw direct debit authorizationNotification preferences (Email/SMS)Switch accountMultiple SAP payer accounts can be assigned to single user idFAQLogoff*

  • Our Must-Haves for the DesignOpen Items-Payment (standard Biller Direct-Open Bills)Filter document typesFlag future due credits as Non-PayableAdd line item dataDelivery Number/Purchase Order Number/Child customer name/Line item description (reason code)Prepayment-On Account Payment (custom screen)Allows payments in excess of account balancePayments not specific to an invoicePayment History (standard Biller Direct-Payment)Limit increment of time available for visibility 30 Days/90 Days/1 Year/2 Years*

  • Our Must-Haves for the Design (cont.)Statements (custom screen)Provide ability to receive electronic-only statementsStatements archived and accessible for 12 monthsCustom reports available through archiveBank Accounts (custom screen based on administrative data)Limits ability to Add and Edit bank information onlySwitch Account (standard Biller Direct)Contact Us (custom screen)FAQ (standard Biller Direct)

    *

  • Application Challenges Data Fields and FiltersFunctionality available to Add and Filter dataAddition of Delivery Number, Purchase & Order NumberFilter Document type, Reason code, Down Payment requestsSubObjects selection flexibility assignment field values or partner typeDelete cancelled prepayments from appearing on the open items screen Prevent selection of future dated creditsDisplay PDF icon for invoices ONLY if document exists in the archiving systemAdd additional fields to the open items and CSV download file

    *

  • *Open Items-Payment View

  • *Open Items-Payment View (cont.)

  • Challenges Prepayment-On AccountCustom screen development using Web DynproGenerate customer down payment request Update Event log Modification to include down payment requests in payment history and exclude from open billsUpdates to payment proposalParameter ID modification required for visibility on FBL5NPrepayment utilizes Special GL *

  • *Prepayment-On Account View

  • Statements

    Implemented custom design using object type DRAWSAPDocument is not linked and requires further developmentDefine the object_id on the linkage table and require a means to extract the list of statements through the Web site

    Design can be utilized to store any ABAP, Smartform, or SAPScript generated report in the archive

    Provides customer the ability to elect Online only*

  • Statement Archive Design *Customer Statement is generated andindicator set to Send to DocumentumDocument Receivedby Documentum using HTTP Security CertificateProcessing

    Statement Converted toOTF format sentto archive by FMs inprogram

    Documentum Content RepositorySecurity Certificate

  • *Statement View

  • Bank AccountsModification of screen utilizing standard RFC to update Customer Master to eliminate the Delete functionFunction allows for edits but NOT deletions

    *

  • Switch AccountsProvides ability to have multiple accounts per User IDModified to to arrange the object hierarchy Implemented functionality to assign text/label to a SubObject

    *

  • Other ChallengesCreating custom screens Web Dynpro Java development (SAP NetWeaver Development Infrastructure)Implementing a foreign languageSupporting SAP ERP Central Component 6.0 UpgradeNo user exits to enhance Biller Direct Java Web applicationModification is the only optionImplementation of SAP Enterprise PortalSingle Sign-On (Portal to Biller Direct)Integration of custom functionality Prepayment-On Account with standard Biller Direct Example: Payment history, cancellation, payment proposal, payment run, audit log, etc.

    *

  • User Management Engine configuration limits and flexibility

    Multiple accounts accessible through single User IDEstablishing User Access utilizing Pooled reference userfscm_refuser authorization profiles for ECC accessobjtype_0 BUS3007 customer identifierobjkey_0 company code + customer numberStandard row limitation of ten (four accounts)Enhanced to 30 lines, see SAP Note 869852*

  • *User Management Engine (cont.)Utilizing SubObjects enables filtering capabilitySubObjects available for Branch accounts filtering Display Only due to conflict with Head Office bank accounts

    Pooled reference user setupobjtypeebpp_spartobjkeyCompany code + customer number + unique qualifier

  • Key LearningsPerformance issuesLarge volume of Open ItemsSAP claims resolution version 6.02 (Pagination)Custom approach through use of Summary and Invoice Query

    *

  • Key Learnings (cont.)Performance Issues (cont.)Payment history screen for five years and unlimited selectionAddressed through two-year limitReversal issueFBRA does not remove Payment Method at time of reversalCapture by subsequent proposal will result in a double debit of customer bank accountCreated new transaction code for reversals that removes payment methodSelect all/deselect all Not available through standard Open Bills (display view)SAP modified standard Biller Direct screen*

  • Key Learnings (cont.)Payment Proposal LimitationsNo error messages or flagLock/posting failureSAP NotesCorrection for SubObject processing in R/3 4.6cApply SAP Note 1152361User Management Engine limitation of 10 linesApply SAP Note 869852 to increase from 10 to 30 linesSAP R/3 EBPP Log truncates the Portal User ID to 12 characters SAP recognizes this issue but there are no plans yet for an upcoming releaseJSP modification to handle CSV download delimiters (, instead of ;) so properly formatted by ExcelApply SAP Note 1086466*

  • Key Learnings (cont.)Involve SAP before making changesUse SAP NetWeaver Development Infrastructure to deploy Biller Direct Web application modificationsRoll out application in a pilot program to limited customersPerform thorough testingReconciliation report Payment proposal, payment run, and 820 confirmationCall centerSubObjects are not supportedKnowledge Management (Portal)On-the-fly updates for Pure HTML pagesHome, FAQ, and Outages*

  • ResourcesSAP GuidesConfiguration GuideModification GuideSecurity GuideInstallation Guidehttp://help.sap.com/erp2005_ehp_04/helpdata/en/43/72fc28e1356fcae10000000a1553f6/frameset.htm

    SAP Financials Expert April 2007, Volume 6/Number 4

    SAP Building Blocks (W22: FSCM Biller Direct) http://help.sap.com/bp_bblibrary/600/BBlibrary_start.htm

    *

  • *Key PointsUnderstand the full extent of your business user requirements Engage companies that have implemented Biller DirectSAP User Groups/SAP Financial Customer Value NetworkIdentify pilot group of customers to test and for initial launchDevelop with business growth in mind and utilize tables and avoid hard codingPrototype out-of-the-box solution and compare with requirementsBuild appropriate back-end monitoringEstablish clear expectations with your financial institution for ACH debit requests and confirmations

  • *Your Turn!How to contact me:[email protected]

    Provide real time financial information to your customers Ability to deliver statements and customer specific reports - Our customers expected online financial detail and payment functionality