SAP Bank Communication Management Configuration Guide

SAP Bank Communication Management (BCM) helps organizations control how payment batches are created, approved, transmitted, and monitored. It connects the payment run, Payment Medium Workbench, approval workflow, bank acknowledgments, and operational monitoring into one traceable process.

This practical guide explains the main SAP BCM configuration sequence, IMG paths, transaction codes, approval design, monitoring tools, and troubleshooting checks for SAP S/4HANA projects. Always validate transactions, workflow templates, and application behavior against your installed S/4HANA release and support-package level.

SAP BCM Process at a Glance

Execute the payment proposal and payment run in F110 or F111.
Collect eligible payments with FBPM1 using report SAPFPAYM_MERGE.
Apply BCM grouping rules and create payment batches.
Route batches through automatic approval or one-to-four approval levels.
Generate the payment medium after final approval and transmit it to the bank.
Import bank acknowledgments and update batch and payment-item statuses.
Monitor exceptions, approvals, bank responses, and reconciliation status.

Key SAP BCM Transactions and Reports

Transaction or report	Purpose
SFW5	Activate business function FIN_FSCM_BNK.
OBPM4	Assign selection variants to payment-medium formats.
OBPM5	Reserve payment-run IDs for BCM processing.
FBPM1 / SAPFPAYM_MERGE	Collect, merge, and batch eligible payments.
BNK_APP	Process batch approvals and rejections in SAP GUI.
BNK_MONI	Monitor payment batches and obtain the BCM run ID and date.
BNK_MONIP	Analyze payment-level batching status and rule failures.
BNK_MONIA	Review approval history and timestamps.
SWE2 / SWI2_DIAG	Check event linkage and diagnose workflow errors.
SLG1 / SM37 / SM58	Review application logs, background jobs, and transactional RFC errors.
FTE_BSM	Open Bank Statement Monitor for end-of-day statement monitoring.

1. Activate Bank Communication Management

Transaction: SFW5
IMG access: SPRO > Activate Business Functions

Activate enterprise business function FIN_FSCM_BNK through the approved development, quality-assurance, and production transport process. Business-function activation changes system behavior and is not a normal reversible configuration setting, so complete regression testing and change-control approval before production activation.

2. Prepare Payment Medium Workbench

Transaction: OBPM4
IMG path: SPRO > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Automatic Outgoing Payments > Payment Media > Make Settings for Payment Medium Formats from Payment Medium Workbench > Create Payment Medium Formats

BCM depends on a working Payment Medium Workbench configuration. Confirm the payment method, DMEE format, selection variant, file path, and bank-specific requirements before testing BCM. Use OBPM4 to assign the correct SAPFPAYM selection variant to the payment-medium format.

For a focused file-format review, use the SAP DMEE Wire and ACH Payment File Checklist.

3. Reserve Payment-Run IDs for BCM

Transaction: OBPM5
SAP menu: Accounting > Financial Supply Chain Management > Bank Communication Management > Environment > Current Settings > Reservation for Cross-Payment Run Payment Media

Reserve the intended payment-run identifiers and enable the BRM indicator. A reserved run cannot bypass BCM by creating the payment medium directly from the original F110 or F111 run. Use specific run-ID patterns when some payment processes must remain outside BCM, and remember that reservation changes apply to new payment runs rather than previously created runs.

4. Define Basic Approval Settings

IMG path: SPRO > Financial Supply Chain Management > Bank Communication Management > Basic Settings > Basic Settings for Approval

Define the rule currency and exchange-rate type used to compare payment amounts.
Set the resubmission interval for payments postponed by the first approver.
Enable Signature Required only after the SSF setup, user master data, signature method, and end-to-end approval test are complete.

5. Configure Payment Grouping Rules

IMG path: SPRO > Financial Supply Chain Management > Bank Communication Management > Payment Grouping > Rule Maintenance
Rule test report: RBNK_RULID_EVALUATE through SA38 or SE38

Grouping rules determine which payments form a BCM batch. Assign clear priorities because the priority controls which rule wins when multiple rules match. Use only necessary attributes, confirm that every rule has green status, and test the sign of outgoing payment amounts because they commonly appear as negative values.

Additional grouping fields can split a rule into more granular batches, such as separate batches by payment method. Configure them under Payment Grouping > Additional Criteria for Payment Grouping only when source data and approval responsibilities support the same granularity.

6. Design Automatic and Multilevel Approval

IMG path: SPRO > Financial Supply Chain Management > Bank Communication Management > Release Strategy

Automatic payments: Mark low-risk rules under Mark Rules for Automatic Payments (No Approval) only after the control owner accepts the design.
Initial approval: Configure BNK_INI responsibilities using release setting BNK_BNK_INI_REL01.
Additional approval: Configure BNK_COM release conditions and workflow using BNK_BNK_COM_REL01 and Additional Release activities.
Workflow templates: Validate the standard workflow and release-procedure template IDs in the installed release before production use.

BCM supports up to four approval levels. BNK_INI is the initial approval step; BNK_COM is used for later approval steps. Conditional release procedures can require additional approvals for selected rules, payment types, or higher-value batches.

7. Configure Workflow Linkage and Approvers

Transactions: SWDD, SWE2, SWEQADM, SWI2_DIAG, SWI1, and SWIA

Assign approvers through release-strategy responsibilities and confirm event linkage for business object BUSISB001 in transaction SWE2. A linkage can be deactivated after an error, so investigate the root cause before reactivation. Responsibilities may be time-dependent and can use users or organizational objects; define priorities when responsibilities overlap.

8. Execute and Monitor the BCM Payment Cycle

After F110 or F111, run FBPM1 or schedule SAPFPAYM_MERGE. The merge program copies eligible payment lines into BCM-specific runs while keeping the original payment-run information for traceability. Approvers process assigned batches in BNK_APP or the release-appropriate Approve Bank Payments Fiori app. Monitor the process using BNK_MONI, BNK_MONIP, and BNK_MONIA.

Current SAP documentation identifies the on-premise Approve Bank Payments implementation app as F0673A; confirm the app ID, catalogs, spaces, and authorizations for the selected product release.

9. Bank Acknowledgments, Statuses, and Alerts

Transactions and reports: S_EBJ_98000208 / RBNK_IMPORT_PAYM_STATUS_REPORT, FILE, ALRTCATDEF, RBNK_BATCH_TIMEOUT_MONITOR, SM36, and SM37

BCM can receive ISO 20022 pain.002 status reports through the configured integration channel or file import. Maintain separate logical paths for input, successful archive, and error processing. Map external bank status codes to internal BCM statuses by company code and house bank, and test partial acceptance so a rejected item does not incorrectly produce an accepted batch header.

Use ALRTCATDEF for alert categories and configure timeout thresholds under Payment Status Management. Schedule RBNK_BATCH_TIMEOUT_MONITOR with SM36 and monitor execution in SM37.

10. Bank Statement Monitor

Transaction: FTE_BSM

Bank Statement Monitor provides a centralized view of expected statements, posting completeness, balance differences, statement sequences, and reconciliation status. Legacy releases may use IMG settings and transaction FTE_BSM_CUST. Current SAP S/4HANA 2025 FPS01 documentation maintains end-of-day statement settings in Manage Bank Accounts > Bank Statement Data and provides FCLM_BSM_MIGRATION for migrating legacy settings.

For related configuration controls, review the SAP Electronic Bank Statement BAI2 Configuration Checklist.

Common SAP BCM Problems and Checks

Problem	What to check
No batch after FBPM1	OBPM5 reservation, OBPM4 format variant, BNK_MONIP status, SLG1 object FBPM, SM37 jobs, and RBNK_RULID_EVALUATE.
Workflow does not start	BUSISB001 linkage in SWE2, SWI2_DIAG errors, SWEQADM, work items in SWI1 or SWIA, and failed RFC calls in SM58.
Payment file was not created	PAYM* and BNK_INI_REL* jobs in SM37, batch error in BNK_MONI, OBPM4 variant, and release-appropriate retry reports.
User cannot approve	Release responsibility, workflow agent assignment, F_STAT_MON authorization, Fiori role/catalog, and locked work-item status.
Incorrect or missing bank status	pain.002 mapping, FILE paths, transformation, logical archive/error directories, and batch-versus-item aggregation.

Production-Control Warning

BNK_MERGE_RESET is a repair tool, not a routine production procedure. Restrict its authorization and do not use it after the first approval or in production unless current SAP guidance or SAP Support explicitly authorizes the action. A normal recovery path is to reject the batch in BNK_APP and reverse the applicable payment documents through the approved process, such as FBRA for eligible FI payment documents.

SAP BCM Implementation Checklist

Activate FIN_FSCM_BNK through controlled transports using SFW5.
Complete PMW, DMEE, payment method, file-path, and OBPM4 configuration.
Reserve only intended payment-run IDs in OBPM5 and test F110/F111 behavior.
Configure basic approval settings, grouping rules, and additional grouping criteria.
Configure automatic approval, BNK_INI, BNK_COM, responsibilities, templates, and SWE2 linkage.
Test approval, return, resubmission, payment removal, rejection, automatic approval, and final file creation.
Validate bank acknowledgments, alerts, timeout monitoring, application logs, and background jobs.
Document production recovery, reversal, authorizations, and SAP Support escalation procedures.

Continue with SAP Cash and Liquidity Management Training

BCM works best when it is designed with bank account management, payment automation, bank statements, cash position, and liquidity forecasting. Use the SAP Cash & Liquidity Management S/4HANA Setup Checklist for a broader readiness review.

Learn SAP Cash & Liquidity Management

Release note: SAP transactions, reports, workflow templates, Fiori apps, and support limitations can change by S/4HANA release. Confirm production steps in current official SAP documentation and the installed customer system.