R48 Effective Cash Pooling and Facilities Process Diagram
Purpose, Benefits, and Key Process Steps Purpose The purpose of this scenario is to describe functional scope and processing of: Effective Cash Pooling, where a corporate customer holds multiple accounts and needs to: o Concentrate cash from multiple accounts on a single main account o Fund overdrawn accounts from the main account to avoid unnecessary debit interest expenses Facilities, a product allowing to monitor utilization of a credit line provided to a customer across multiple contracts (limited to overdrawing of multiple current accounts by a corporate customer; loan contracts not included) Benefits End-to-end scenario including creation / processing of: Corporate customers Customer accounts Payments Transfers and requests for transfers resulting from cash pooling Control of credit risk using the Facilities functionality Scenarios integrating SAP Banking Services and 205 SAP SE or an SAP affiliate company. All rights reserved. 2
Purpose, Benefits, and Key Process Steps Key Process Steps Create customer (business partner) Create customer accounts Create master contract (and include customer accounts in cash pooling and facilities hierarchies) Post debit and credit payments to customer accounts Execute sequence of relevant end-of-day activities such as settlement and cash pooling Process payment orders generated by the cash pooling Monitor Facility utilization (credit line) 205 SAP SE or an SAP affiliate company. All rights reserved. 3
Required SAP Applications and Company Roles Required SAP Applications SAP Banking Services 8.0 8.0 Company Roles Back office 205 SAP SE or an SAP affiliate company. All rights reserved. 4
Detailed Process Description Effective Cash Pooling and Facilities The process starts with capturing of customers details, representing various entities (branches) of a corporate customer An account is created for each such customer (branch, head office); the accounts may be: Held directly in the bank (internal) Held in another bank (external), in such case shadow accounts need to be created and associated with the actual account numbers held in another bank Master contract is created for the corporate customer, tying all involved accounts together (one main account head office, multiple sub-accounts branches) Debit and credit payments are posted to the sub-accounts End-of-day processes are executed, including settlement and cash pooling runs. Cash pooling run will result in payment orders generated to transfer credit balances from subaccounts to the main account and to fund debit balances on sub-accounts from the main account The payment orders need to be processed in Payment Engine (optional step depending on system setup) Facilities on-going monitoring of drawing from accounts participating in a credit line and making sure the overall limit is not exceeded 205 SAP SE or an SAP affiliate company. All rights reserved. 5
Effective Cash Pooling Scenario all accounts internal; variant without Payment Engine (/5) A BP A AB Create Business Partners Create relationships between business partners B C D BP BCA_CN_ACCT_0 SXMB_MONI Replicate Business Partner to Bank Analyzer AC Create participating accounts for the cash pool structure Distribute Account Master Data to Bank Analyzer AD Monitoring of Data Transfer in the Deposits Management System 205 SAP SE or an SAP affiliate company. All rights reserved. 6
Effective Cash Pooling Scenario all accounts internal; variant without Payment Engine (2/5) E BCA_CN_ACPOOL_0 F BCA_CN_ACPOOL_03 AE Create the Master Contract for ECP and Facility G H BCA_DISP_HIER_MC BCA_PPO2 AF Display the Cash Pool Master Contract I BCA_PAYMITEM_CREATE AG Display Hierarchies for the Master Contract AH Address potential technical issues in post processing AI Post payments to the subaccounts 2 205 SAP SE or an SAP affiliate company. All rights reserved. 7
Effective Cash Pooling Scenario all accounts internal; variant without Payment Engine (3/5) J SXMB_MONI 2 K BCA_CN_KFG Distribute Payment Items to Bank Analyzer L BCA_DATE_POST_SET M BCA_ACBAL_ACC_M AJ Monitoring of Data Transfer in the Deposits Management System N /FSBPR/RUN AK Displaying Balances and Key Figures AL Set Posting Date for Payment Transactions AM Execute Account Settlement (charges) AN Execute Combined Settlement 3 205 SAP SE or an SAP affiliate company. All rights reserved. 8
Effective Cash Pooling Scenario all accounts internal; variant without Payment Engine (4/5) O /FSECP/RUN 3 P BCA_ACBAL_ACC_M AO Execute Effective Cash Pooling Q BCA_DATE_EOD_SET AP Execute Account Settlement (interest) Distribute Settlement Data to Bank Analyzer AQ Set Posting Date for End of Day Processing 4 205 SAP SE or an SAP affiliate company. All rights reserved. 9
Effective Cash Pooling Scenario all accounts internal; variant without Payment Engine (5/5) R SXMB_MONI 4 S BCA_CN_KFG AR Monitoring of Data Transfer in the Deposits Management System T /FSECP/MONITOR AS Displaying Balances and Key Figures AT Cash Pool Monitor 205 SAP SE or an SAP affiliate company. All rights reserved. 0
Effective Cash Pooling Scenario all accounts internal; variant with Payment Engine (/5) A BP A AB Create Business Partners Create relationships between business partners B C D BP BCA_CN_ACCT_0 SXMB_MONI Replicate Business Partner to Bank Analyzer AC Create participating accounts for the cash pool structure Distribute Account Master Data to Bank Analyzer AD Monitoring of Data Transfer in the Deposits Management System 205 SAP SE or an SAP affiliate company. All rights reserved.
Effective Cash Pooling Scenario all accounts internal; variant with Payment Engine (2/5) E BCA_CN_ACPOOL_0 F BCA_CN_ACPOOL_03 AE Create the Master Contract for ECP and Facility G H BCA_DISP_HIER_MC BCA_PPO2 AF Display the Cash Pool Master Contract I BCA_PAYMITEM_CREATE AG Display Hierarchies for the Master Contract AH Address potential technical issues in post processing AI Post payments to the subaccounts 2 205 SAP SE or an SAP affiliate company. All rights reserved. 2
Effective Cash Pooling Scenario all accounts internal; variant with Payment Engine (3/5) J SXMB_MONI 2 K BCA_CN_KFG Distribute Payment Items to Bank Analyzer L BCA_DATE_POST_SET M BCA_ACBAL_ACC_M AJ Monitoring of Data Transfer in the Deposits Management System N /FSBPR/RUN AK Displaying Balances and Key Figures AL Set Posting Date for Payment Transactions AM Execute Account Settlement (charges) AN Execute Combined Settlement 3 205 SAP SE or an SAP affiliate company. All rights reserved. 3
Effective Cash Pooling Scenario all accounts internal; variant with Payment Engine (4/5) O /FSECP/RUN 3 P BCA_ACBAL_ACC_M AO Execute Effective Cash Pooling Q P E BCA_DATE_EOD_SET /PE/PO_EXPERT PE A Process payments in the Payment Engine AP Execute Account Settlement (interest) Distribute Settlement Data to Bank Analyzer AQ Set Posting Date for End of Day Processing 4 205 SAP SE or an SAP affiliate company. All rights reserved. 4
Effective Cash Pooling Scenario all accounts internal; variant with Payment Engine (5/5) R SXMB_MONI 4 S BCA_CN_KFG AR Monitoring of Data Transfer in the Deposits Management System T /FSECP/MONITOR AS Displaying Balances and Key Figures AT Cash Pool Monitor 205 SAP SE or an SAP affiliate company. All rights reserved. 5
Effective Cash Pooling Scenario 2 including external accounts (/5) A BP A AB Create Business Partners Create relationships between business partners B C D BP BCA_CN_ACCT_0 FS_TB_PXAC_SHAD Replicate Business Partner to Bank Analyzer AC Create participating accounts for the cash pool structure AD Assign Shadow Accounts Distribute Account Master Data to Bank Analyzer 205 SAP SE or an SAP affiliate company. All rights reserved. 6
Effective Cash Pooling Scenario 2 including external accounts (2/5) E BCA_CN_ACPOOL_0 F BCA_CN_ACPOOL_03 AE Create the Master Contract for ECP G H BCA_DISP_HIER_MC BCA_PPO2 AF Display the Cash Pool Master Contract I BCA_PAYMITEM_CREATE AG Display Hierarchies for the Master Contract AH Address potential technical issues in post processing AI Post payments to the subaccounts 2 205 SAP SE or an SAP affiliate company. All rights reserved. 7
Effective Cash Pooling Scenario 2 including external accounts (3/5) J SXMB_MONI 2 K BCA_CN_KFG Distribute Payment Items to Bank Analyzer L BCA_DATE_POST_SET M BCA_ACBAL_ACC_M AJ Monitoring of Data Transfer in the Deposits Management System N /FSBPR/RUN AK Displaying Balances and Key Figures AL Set Posting Date for Payment Transactions AM Execute Account Settlement (charges) AN Execute Combined Settlement 3 205 SAP SE or an SAP affiliate company. All rights reserved. 8
Effective Cash Pooling Scenario 2 including external accounts (4/5) O /FSECP/RUN 3 P BCA_ACBAL_ACC_M AO Execute Effective Cash Pooling Q P E BCA_DATE_EOD_SET /PE/PO_EXPERT PE A Process payments in the Payment Engine AP Execute Account Settlement (interest) Distribute Settlement Data to Bank Analyzer AQ Set Posting Date for End of Day Processing 4 205 SAP SE or an SAP affiliate company. All rights reserved. 9
Effective Cash Pooling Scenario 2 including external accounts (5/5) R SXMB_MONI 4 S BCA_CN_KFG AR Monitoring of Data Transfer in the Deposits Management System T /FSECP/MONITOR AS Displaying Balances and Key Figures AT Cash Pool Monitor 205 SAP SE or an SAP affiliate company. All rights reserved. 20
Facilities - Scenario 3 (/3) A BP A AB Create Business Partners Create relationships between business partners B C D BP BCA_CN_ACCT_0 SXMB_MONI Replicate Business Partner to Bank Analyzer AC Create participating accounts for the cash pool structure Distribute Account Master Data to Bank Analyzer AD Monitoring of Data Transfer in the Deposits Management System 205 SAP SE or an SAP affiliate company. All rights reserved. 2
Facilities - Scenario 3 (2/3) E BCA_CN_ACPOOL_0 F BCA_CN_ACPOOL_03 AE Create the Master Contract for ECP and Facility G H BCA_DISP_HIER_MC BCA_PPO2 AF Display the Cash Pool Master Contract I /FSFAC/DISP_HIER_MC AG Display Hierarchies for the Master Contract AH Address potential technical issues in post processing AI Display Facility 2 205 SAP SE or an SAP affiliate company. All rights reserved. 22
Facilities - Scenario 3 (3/3) J BCA_PAYMITEM_CREATE 2 K /FSFAC/DISP_HIER_MC AJ Post payments to the subaccounts (within fac. limit) L M BCA_PAYMITEM_CREATE PCOM AK Display Facility N /FSFAC/DISP_HIER_MC AL Post payments to the subaccounts (exceedf fac. limit) AM Post the transaction from Posting Control Office AN Display Facility 205 SAP SE or an SAP affiliate company. All rights reserved. 23
Thank you
205 SAP SE or an SAP affiliate company. 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 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 http://global2.sap.com/corporate-en/legal/copyright/index.epx 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. 205 SAP SE or an SAP affiliate company. All rights reserved. 27