AribaPay Operational Details

Transcription

1 AribaPay AribaPay Operational Details

2 Table of Contents 3 Onboarding and Setup 4 Payment Initiation and Flow 5 Postpayment Process and Responsibilities 6 Third-Party Participation in AribaPay in the United States AribaPay delivers a trusted, integrated, and comprehensive solution that transforms the pay in the procure-topay process. The solution gives buyers and their suppliers complete control over business-to-business (B2B) payments with more confidence, more efficiency, and more visibility. Now you can complete the procure-to-pay process simply, securely, and with a high degree of certainty about who is paying, to whom, for what, and when. Available from Ariba, an SAP company, AribaPay capitalizes on the power of the Ariba Network to facilitate buyer-supplier collaboration, along with the global reach and security of the Discover Network from Discovery Financial Services (DFS). This document provides a high-level and plainlanguage overview of the relevant operational details of the AribaPay solution. The information it contains is intended to bridge the gap between an introductory discussion and a full detailed examination of the solution. 2 / 6

3 Onboarding and Setup The process for onboarding and setting up suppliers on AribaPay (see Figure 1) is as follows: 1. The buyer defines the objectives needed to meet the business case. 2. Ariba develops recommendations on how AribaPay can allow suppliers to help achieve these objectives. 3. The buyer approves the suppliers that should be included in AribaPay. 4. The approved suppliers are enabled on the Ariba Network and assigned an Ariba Network identification number (ANID). 5. Each supplier takes the following steps: a. Accepts the AribaPay terms of use b. Identifies and authorizes two individuals (known as the requestor and approver ) to sign up the bank account c. Provides bank account details, a copy of its W9 form, and proof of banking (such as a voided check or letter from its bank) 6. The requestor approves the final submission of information. 7. The approver approves the final submission of information. 8. DFS conducts regulatory checks to support compliance with Office of Foreign Assets Control (OFAC), Know Your Customers (KYC), and Anti-Money Laundering (AML) requirements. 9. The suppliers are assigned an AribaPay merchant identification number (AP-MID). 10. The suppliers are notified that the activation process is complete. 11. The buyer is notified that the suppliers are activated. 12. The buyer configures the enterprise resource planning (ERP) system to direct payments to each supplier through AribaPay. 13. The enablement process is completed. The buyer and suppliers are now ready for AribaPay transactions Figure 1: Supplier Onboarding for AribaPay Buyer Issue project notification Change payment method to AribaPay Ariba Send trading relationship request Create lead list and send to Discover Network Issue welcome letters Notify buyer that supplier is ready Payment processor Issue with credentials to payment processor site Conduct regulatory checks Send AP-MID to Ariba Supplier Accept relationship request and AribaPay task Log in Accept participant agreement Assign requestor and approver Complete enrollment form Upload W9 and proof of banking Have requestor input AP-MID and agree to terms of use Have approver input last 4 digits of bank account and approval Receive payments 3 / 6

4 Payment Initiation and Flow The buyer s ERP system remains the system of record and is responsible for placing invoices in a fully approved, ready-to-pay status. The pay cycle also continues as it does today. AribaPay is the settlement method. The process for executing a payment (see Figure 2) consists of the following steps: 1. The buyer creates and sends a payment instruction file (PIF) to the Ariba Network before 7 p.m. EST. 2. The Ariba Network validates the PIF. 3. The Ariba Network matches the vendor ID to its ANID and AP-MID, which serve as proxies for sensitive account and payment information. 4. The PIF is sent to the Discover Network for payment processing and settlement based on the AP-MID linkage. 5. The Discover Network acknowledges its receipt of the PIF. 6. The Discover Network validates the PIF. 7. The Discover Network sends a message to the Ariba Network of acceptance or failure within 30 minutes of receiving the file. 8. The Discover Network uses the preexisting ANID and AP-MID match to effect payment. 9. The Discover Network sends a payment status message back to the Ariba Network within two hours of receiving the PIF. 10. The buyer s account is debited through Fedwire to fund the settlement account in the Discover Network. 11. The supplier receives payment from the Discover Network. 12. Suppliers can access remittance details in three ways: Cyber Threat Xchange (CTX) integration with their bank, integration with the Ariba Network, or use of a commaseparated-values (CSV) file that can run on a scheduled or ad hoc basis. Figure 2: Flow of Funds Payment instruction file AribaPay buyer Remittance details SAP Remittance details AribaPay supplier Track and trace Ariba Track and trace PIF = Remittance.csv Remittance Details. csv Remittance request messages Remittance status messages Discover Network Confirm receipt of buyer funds and release supplier funds Buyer bank account T = Transaction date T + 1 day Fedwire drawdown Discover Network settlement account T + 2 days Automated Clearing House (ACH) credit Supplier bank account Remittance data Payment Tracking data Funds movement 4 / 6

5 Postpayment Process and Responsibilities During the postpayment process, Ariba and DFS are responsible for performing the following functions: Ariba handles all incoming support calls from AribaPay customers through the Ariba Customer Support service. Ariba determines whether the root cause of the inquiry is best resolved by Ariba or DFS. DFS performs regulatory checks on all suppliers to help ensure that they are legitimate companies and allowed to do business in the United States. Ariba makes rich remittance information on every invoice and payment instantaneously available for both the buyer and the supplier whenever needed. If something happens during the payment transaction (for example, if the supplier changes its business information or address), DFS tracks down the supplier to resolve the issue and enable payment. The Ariba support desk engages DFS if needed to resolve payment issues. Any portion of the AribaPay service related to the management, processing, or transmission of payments or funds is provided by DFS only. 5 / 6

6 Third-Party Participation in AribaPay in the United States The roles of Ariba and DFS in providing AribaPay are outlined below: Ariba offers subscriptions to AribaPay in the United States subject to AribaPay customers agreeing to the Buyer Payment Activation Terms and Conditions administered by DFS, as well as terms with Ariba specific to AribaPay. AribaPay does not provision or facilitate an offering to consumers, but only to businesses and organizations. Ariba does not provide, nor is responsible for, any portion of the payment processing services. DFS provides certain features and functionality of AribaPay that streamline the process of making and receiving payments, track the status of anticipated payments, and facilitate the communication and consumption of reconciliation information. DFS solely provides the processing of payments, debiting or crediting of bank accounts, holding of funds and account numbers, and other actions as payment processor. AribaPay customers are responsible for: Initiating payment transactions through AribaPay Determining if AribaPay meets their own particular internal, legal, and regulatory requirements related to submitting and processing the payments of outstanding invoices Implementing appropriate security precautions regarding which named users have authority to initiate payment transactions Studio SAP 40829enUS (15/11) 6 / 6

7 No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.