Overview of SAP Bank Communication Management

2 Minute Read

Share Post:

SAP ERP and Bank Communication Management

SAP Bank Communication Management helps implement various approval workflows for an organization’s payments before processing that Payment with the bank. An example is a workflow approval made by a payment manager for Payment due to a supplier. Once the manager approves this cash outflow, the AP person can initiate this transaction with the bank.  

Payments to be initiated are grouped in a payment run, and these batches are triggered for workflows. SAP Bank Communication Management Integration services monitor incoming and outgoing workflows to track the cash flow within an organization. Therefore, the banking process is streamlined with Fiori reports for clear communication with the bank. 

What is SAP Multi-Bank connectivity? 

It is a cloud-oriented solution offering a multi-bank digital channel between SAP and banks. The advantage of the UK’s SAP Bank Communication Management Integration services lies in its embedded SWIFT connectivity. In addition, many prefer this solution since it has incorporated several security measures.  

Who are eligible to use SAP MBC?  

A certain set of SAP customers can move on to SAP MBC and SAP BCM. They are:  

  • SAP customers on ECC using SAP ERP 6.0 or higher version 
  • SAP S/4HANA Cloud customers 
  • SAP S/4HANA on-premise edition customers 

What is new with SAP MBC? 

Many customers will be able to interact with different banks regularly. You can send and receive multiple files from the bank.  

When you want to communicate successfully with a bank, you must establish robust communication. It is possible with SAP MBC.  

Bank communication was a norm even before the introduction of SAP MBC. But bank communication was cost-effective and convenient when SAP MBC and SAP BCM Integration were introduced. 

The payment program (F110 or F111) runs and allows the download of payment media files that you can upload to an intermediate system which helps in the transmission of the payment file to and from the bank. This payment file generated is in the bank’s required format (MT100 or ISO 20022 XML). This process also allows encryption of the payment file before transmitting it to the bank for Payment.

Payment Scenario between non-SAP system

If payments are processed from a non-SAP system, the payment media file generated is the bank’s required (ISO 20022 XML) format and is sent for approval through the SAP BCM system.

The below flow represents a new offering for Payment Factory to implement a non-SAP payment through SAP BCM Implementation partner.

The accounting entries are tracked in the sources system (non-SAP), and only Payment is processed via the SAP BCM using BCM Connector.

SAP NetWeaver Process Integration
SAP New Offering in BCM

The process steps for implementing this non-SAP Payment are as follows: 

  1. Payment is processed in a non-SAP system, and a Payment medium (ISO 200 222 XML) file is generated. 
  2. Payment medium (ISO 200 222 XML) file interfaced into SAP. 
  3. SAP will convert the payment medium file (ISO 200 222 XML) into a payment batch (using function modules). You must write Custom function modules for other payment medium formats where function modules are unavailable. 
  4. Non-SAP Payment medium will be created as a batch in the bank monitor. 
  5. Non-SAP Payment medium batch available for approval in bank monitor. 
  6. Non-SAP Payment medium batch is approved or rejected. 
  7. On approval of the batch, the payment medium file will be encrypted and sent to the service provider for further processing. 


Payment Scenario between SAP system

Suppose the payments are processed in an SAP ERP system. In that case, the payment liabilities are created in the SAP system, and the corresponding processing of these payments is also done in the SAP system with the help of SAP Bank Communication Management for workflows. The approved file is then digitally encrypted and sent to the bank. Get in touch with our experts for the finest SAP BCM Implementation services.

You can achieve the processing of SAP BCM via the scope item J60 in SAP S/4HANA Cloud. 

  • Securely connect with encryption between SAP S/4HANA or SAP ERP (Digital Core), SAP Multi-Bank Connectivity, and the affiliated financial institutions/banks. 
  • Forward payment instructions to banks in the local required format 
  • Receive status notifications for payment instructions to track every Payment 
  • Receive bank statements in standard formats namely MT940, CAMT.053 and BAI2Receive lockbox messages BAI2 


SAP BCM can be achieved as a scope item activation when you use SAP S/4HANA Cloud ERP. This scope item is J60 (Accounts Payable) and 1EG (Bank Integration with File Interface). The image below shows the process flow of SAP Bank Communication Management achieved through the payment program in SAP S/4HANA Cloud. 

Post the payment program step, the scope item 1EG (Bank Integration with File Interface) can be used to complete the payment medium download and upload of bank statement steps. 

  1. J60 (Accounts Payable) – This creates the BCM batch and sends it for approvals 
  2. 1EG (Bank Integration with File Interface)- Helps in bank interface by creating the required payment medium file – downloads and uploads 

Handle everything from Banking and treasury automation with Payment Centralization and Automated payments. With Multicash payment factory, leverage Financial services network with Bank integration, Corporate connectivity, and treasury management.

To conclude

An SAP BCM Implementation Partner in the UK, like iQuantM, enables SAP FSN Connector for the best ERP Bank Connectivity features.

Get The Latest Updates

Subscribe to our Blog Posts

Notifications only about new new blog post updates.

Share Post:

Similar Topics

More Blogs