With house bank accounts treated as master data instead of configuration objects including the latest enhancement, the bank account subledger concept, SAP S/4HANA Bank Account Management (BAM) aims to shift responsibility of bank account management life cycle from the technical teams to the cash and banking teams.
The need to formulate a treasury technology roadmap for your organization has never been more critical. This is particularly relevant for large complex organizations that are running SAP. The SAP S/4HANA move is complex and presents great opportunities and challenges. For the treasury within these large complex organizations it does not make sense to wait for the enterprise to formulate a roadmap as then the likelihood of the treasury requirements not being properly prioritized are high.
During the spring of 2021, Zanders and SAP joined forces once more to provide a three-part webinar series. The occurrence tackled the question: ‘How does Treasury fit in the SAP Central Finance journey?’
Traditionally the SAP Treasury functionality has been heavily focused on accounting, reporting, and monitoring of treasury transactions that have already been executed. But now, pre-trade processes can be optimized with SAP Trade Platform Integration (TPI).
In the previous part of this series on ‘How to setup virtual accounts in SAP’, we delved into the details of a scenario where virtual accounts are managed on GL account level using SAP FI module only. This article investigates how SAP In-house cash (SAP IHC) module can be used to manage virtual accounts in your ERP.