What is SAP Bank Account Management (BAM)?

SAP Bank Account Management (BAM) is the part of S/4HANA Cash Management that holds a company's bank accounts as master data and controls how they are opened, changed, closed and reviewed. Each bank account record carries general data such as account number, IBAN and account holder, the link to its house bank account, and, in the full scope, payment approvers and overdraft limits. Users maintain it in the Manage Bank Accounts Fiori app (F1366A). SAP's current on-premise documentation files the capability under the heading Bank Relationship Management; the application component is still FIN-FSCM-CLM-BAM.

What is the difference between a house bank and a house bank account in SAP?

A house bank is the entity you create in SAP to represent a bank your company has a contract with; it is identified by company code plus house bank ID and stored in table T012. A house bank account is one of your company's own accounts at that bank, identified by a house bank account ID of up to five characters and stored in table T012K. In S/4HANA every house bank account is linked to a bank account master record through house bank account connectivity, and the house bank account is what payment transactions and postings reference. House banks are maintained in Manage Banks - Cash Management or transaction FI12_HBANK; house bank accounts in Manage Bank Accounts.

Is Bank Account Management included in S/4HANA?

A basic version is. SAP documents a basic cash management capability that is delivered with SAP S/4HANA: you can manage banks and house banks, define bank accounts and house bank accounts with common attributes only, see accounts in a list view, and import, export and replicate them. Workflow, dual control or two-person verification for account changes, the bank hierarchy view, payment approvers, overdraft limits and bank account reviews belong to SAP S/4HANA Finance for cash management, which needs its own licence, the business function FIN_FSCM_CLM and the Full Scope setting in the Define Basic Settings Customizing activity.

How is BAM different from the old house bank configuration?

In SAP ERP, house banks and their accounts were created in the implementation guide under Financial Accounting, Bank Accounting, Bank Accounts, Define House Banks, so they were Customizing; SAP's Simplification List says they are no longer configuration data and are maintained as master data instead. In S/4HANA, house bank accounts are migrated into bank account master data, either with transaction FCLM_BAM_MIGRATION or automatically through the Start and Monitor Data Migration activity, and that migration is mandatory even for the basic scope. After it, bank accounts are maintained by business users in the Manage Bank Accounts app. SAP's own best-practice content for S/4HANA Cloud Public Edition states that bank accounts are not transportable to the production system and must be maintained there.

What is the Manage Bank Accounts app?

Manage Bank Accounts (Fiori app F1366A) is the standard app for bank account master data in S/4HANA. With it you search, create, copy, edit, close and delete bank accounts, attach documents, create the house bank account on the House Bank Account Connectivity tab, and start a bank account review. In the full scope, changes made in this app to open, copy, modify, close or reopen an account are subject to workflow, dual control or two-person verification. A reduced variant, documented as Manage Bank Accounts (Basic Cash Management), covers customers on the basic scope.

SAP Bank Account Management (BAM) in S/4HANA

SAP Bank Account Management (BAM) is the part of S/4HANA Cash Management that holds your company's bank accounts as master data — account number, IBAN, the link to the house bank account, payment approvers, overdraft limits — and controls how those accounts are opened, changed, closed and reviewed. A basic version is delivered with S/4HANA; approval workflows, the bank hierarchy view, payment approvers and account reviews need the separately licensed SAP S/4HANA Finance for cash management. That reads like an administrative footnote. Here's what the projects teach instead: BAM looks like housekeeping and behaves like plumbing. It's the quiet layer under S/4HANA Cash Management, and when a bank account estate is a mess, that mess doesn't stay in BAM — it surfaces as broken cash visibility and reconciliation two modules downstream, where nobody thinks to blame the account master.

Everything SAP-specific below was checked against SAP Help (S/4HANA 2025, on-premise and private edition), the SAP Fiori apps reference library and, for the history, SAP's Simplification List for S/4HANA 2023; what I couldn't verify is listed near the end.

What BAM is, and the two scopes it comes in

One naming note first: SAP's current on-premise documentation files this capability under Bank Relationship Management, while the application component is still FIN-FSCM-CLM-BAM (Bank Account Management) and every project room still says BAM.

SAP documents two scopes, and the difference decides what you can promise treasury:

Capability	Basic cash management capability	SAP S/4HANA Finance for cash management
Manage banks and house banks	Yes — a subset of fields	Yes
Define bank accounts and house bank accounts	Yes — common attributes only	Yes
List view of bank accounts	Yes	Yes
Import, export and replicate bank accounts	Yes	Yes
Bank hierarchy view and user-defined hierarchies	No	Yes
Payment approvers and overdraft limits on the account	No	Yes
Workflow, dual control or two-person verification	No	Yes
Bank account reviews	No	Yes

The basic capability is, in SAP's words, "delivered with SAP S/4HANA": you select Basic Scope in the Customizing activity Define Basic Settings. The full scope needs the business function FIN_FSCM_CLM switched on, Full Scope selected in the same activity, and a licence — SAP tells you to contact your account executive first. Don't switch it on speculatively: SAP warns that the activation cannot be reversed in a live system.

In the field the basic version is usually called "BAM Lite", and the name is SAP's own: its Simplification List for S/4HANA defines "Bank Account Management Lite (BAM Lite)" as a basic version of Bank Account Management that is part of the basic cash management capability, for customers without the SAP S/4HANA Finance for cash management licence. The current SAP Help pages don't use it; there the terms are the basic cash management capability and, as scope items, Basic (BFA) and Advanced (J77) Bank Account Management.

House banks and house bank accounts in S/4HANA

A house bank is the entity you create in SAP to represent a bank your company has a contract with; a house bank account is one of your company's own accounts at that bank. Both are, in SAP's words, "required for payment transactions and accounting". Four objects are involved, and keeping them apart solves most of the confusion:

Four objects, one chain. The link between the last two is what SAP calls house bank account connectivity. More drawings

Object	What it is	Maintained in
Bank	The bank itself — name, SWIFT/BIC, address	Manage Banks - Master Data, or transaction FI01
House bank	Your relationship with that bank, identified by company code + house bank ID	Manage Banks - Cash Management, or transaction FI12_HBANK
House bank account	Your account there as payments and postings see it; an ID of up to 5 characters	Manage Bank Accounts, House Bank Account Connectivity tab
Bank account	The BAM master record — IBAN, holder, approvers, limits, lifecycle status	Manage Bank Accounts

A company code can have several house banks, and one bank can carry several. The S/4HANA-specific part is the last two rows: each house bank account is linked to a bank account master record through house bank account connectivity. On the bank account you create a connectivity entry with the ID category Central System: House Bank Account, enter the company code, house bank ID and house bank account ID, and assign the G/L account that payment transactions post to. By default SAP allows one such central house bank account per bank account (the check is a configurable message), so that it "can uniquely represent the bank account in payment transactions and postings". Other ID categories link the bank account to a G/L account or to account records in remote SAP or third-party systems.

One thing the app doesn't do for you: after creating or changing a house bank account, SAP tells you to update the Customizing activity Set Up Bank Determination for Payment Transactions.

On the SAP GUI side the documentation looks inconsistent: the overview page names only Manage Bank Accounts and SAP NetWeaver Business Client (NWBC) for house bank accounts, while the Defining House Bank Accounts page adds that "alternatively, you can create house bank accounts using transaction FI12". SAP's Simplification List explains the history. Before S/4HANA 1809 "the transaction FI12 House Bank / House Bank Account is not available" and the Fiori apps replace it; with 1809 "the transaction FI12 has been reactivated" for house banks and house bank accounts. For bank accounts there is a condition: FI12 can be used when the bank account activation mode is Activate Directly, and with workflow or dual control in place SAP points you to Manage Bank Accounts or NWBC instead. So FI12 exists again, but the app is the path that works in every control mode.

The tables behind them

T012 — house banks. SAP's S/4HANA migration object for house banks selects "all house banks from the T012 table".
T012K — house bank accounts; the bank account migration object selects from it. In S/4HANA, per the Simplification List, the table "is redirected to the new BAM tables".
BNKA — the bank master, keyed by bank country and bank key. SAP's migration object for banks "automatically selects all bank keys from the BNKA table in the source system".
FCLM_BAM_AMD — the bank account master data table. SAP documents appending the structure CI_AMD_EXT to it for custom fields.
FCLM_BAM_ACLINK2 — named in SAP's change-document settings for bank account replication, with fields such as HKTID and HKONT. SAP gives no one-line definition of it, but its 2020 release note places the control key "defined with house bank accounts" in FCLM_BAM_ACLINK2-BKONT, which, with those field names, is consistent with it being the link between a bank account and its house bank account. That reading is mine.

SAP is also consolidating fields inside the BAM tables: as of S/4HANA 2020, FCLM_BAM_ACLINK2-BKONT is deprecated and FCLM_BAM_AMD-CONTROL_KEY is the single source of bank control keys. Control keys defined on house bank accounts "are no longer visible", and transaction FCLM_BKONT_MIGRATION consolidates them onto the bank accounts. The wider table map, including the bank master, is in the SAP Treasury tables reference.

From configuration to master data: what changes from ECC

The single most important thing to understand about BAM is a shift most migration teams underestimate. In classic SAP ERP/ECC, house banks and their accounts were configuration — created in the implementation guide under Financial Accounting → Bank Accounting → Bank Accounts → Define House Banks, in my experience transported through the landscape like any other setting, owned by the same people who owned the rest of the config. In S/4HANA, bank accounts are master data, managed centrally in Bank Account Management and maintained by business users. SAP's Simplification List says it in one line: house banks and house bank accounts are no longer "configuration data, instead they are maintained as master data".

That sounds like a technical detail. It isn't. It changes who owns the account, where it's edited, and how it changes. Three consequences SAP documents:

The migration is mandatory. SAP's configuration guide says you "must migrate your house bank accounts before using the basic capability of cash management" — so this applies even if you never license the full scope. There are two programs: the classic report (transaction FCLM_BAM_MIGRATION) and the automatic route through Start and Monitor Data Migration, which is the default.
Bank accounts don't travel by transport. SAP's best-practice content for S/4HANA Cloud Public Edition puts it flatly: "Since bank accounts are not transportable to the production system, they must be maintained manually there." What SAP provides instead is Import and Export Bank Accounts — an XML spreadsheet template with a test-run option — and replication of house banks, house bank accounts and bank accounts between systems through transaction DRFOUT.
Not everything migrates. SAP's direct-transfer migration object for bank accounts lists overdraft limits and signatories as out of scope.

Teams that treat the S/4HANA move as a straight technical upgrade discover this in testing — the same way they discover Cash Management is a redesign, not an upgrade. The house bank and account concepts survive the crossing; the ownership model does not. The rest of that crossing is in migrating SAP Treasury from ECC to S/4HANA.

The apps, with their Fiori IDs

The working surface is the standard Manage Bank Accounts Fiori app (F1366A in the Fiori apps reference). The IDs below are from the SAP Fiori apps reference library; the names are as SAP Help spells them.

App	ID	What it's for
Manage Bank Accounts	F1366A	Create, copy, edit, close, delete bank accounts; house bank account links
Manage Bank Accounts - Bank Hierarchy View	F1366	The same inventory as a bank hierarchy (a Web Dynpro app)
Manage Banks - Cash Management	F1574A	House banks, bank business partners and contact persons on an existing bank
Manage Banks - Master Data	F6437	Create and edit the bank itself
Review Bank Accounts	F1370A	Reviewers complete review tasks; initiators track them
My Inbox - For Bank Accounts	F2797	Approve or reject workflow change requests
Approve Bank Account Changes - Two-Person Verification	F6264	Approve or reject changes in two-person verification mode
Maintain Payment Approver	F1372	Replace, add or revoke a payment approver across many accounts (Web Dynpro)
Submit / Approve Bank Account Applications	F5861 / F5859	Request a new account before it exists as a record

The single Manage Banks app (F1574) is the one you'll find on older lists; SAP Help now labels it "Manage Banks (Deprecated)", and its job is split between F1574A and F6437. For the classic transactions around these apps, see the treasury transaction codes reference.

The bank account lifecycle: open, change, close, review

A bank account in BAM moves through documented statuses — Inactive (01), Active (02), Marked for Closing (09), Closing Request Sent to Bank (10), Closed at Bank (11) and Closed (15) — and only active accounts can be used in business operations. The three intermediate closing statuses are optional. When the bank account origination process is enabled, Inactive is not used; the opening side runs through Application Approved (22), Pre-Opening Preparation (24), the optional In Opening Process (26) and Opened at Bank (28) instead. One more status sits outside the main path: Withdrawn (99), for an account that was created from a bank account application which was then withdrawn.

Opening. Either create the account directly in Manage Bank Accounts, or have someone submit a bank account application; once that is approved, SAP creates an inactive bank account to be completed in Manage Bank Accounts.

Changing, with approval. In the full scope, SAP offers three bank account control modes, and they are less alike than the names suggest:

Mode	Where the approver acts	Can reject?	Approval steps
Dual control	Manage Bank Accounts — the Activate button	No	One step only
Two-person verification	Approve Bank Account Changes - Two-Person Verification	Yes	One step only
Workflow	My Inbox - For Bank Accounts	Yes	Configurable in Manage Workflows - For Bank Accounts (F2796)

All three cover the same six scenarios: opening an account, copying one to create a new one, modifying, closing and reopening it, and changing a payment approver across several accounts. For the workflow mode SAP predefines the Business Object Repository object FCLM_CR and a default workflow scenario, 78500050, which you copy in Manage Workflows - For Bank Accounts to build your own. In dual control a revision nobody activates simply stays inactive, and the account isn't blocked while it waits; in the other two modes it is locked while a change is pending. In dual control and two-person verification, any user authorised to activate bank accounts (authorisation object F_CLM_BAM, activity 63) other than the submitter can approve. In every mode, only changes to fields marked sensitive in Define Settings for Bank Account Master Data trigger the process. The general mode is set in Define Basic Settings; Define Settings for Bank Account Contract Types can override it per company code, account type and contract type, which SAP does not support for dual control. One trap: dual control and two-person verification are not supported with NWBC as the user interface.

BAM's real product isn't the account record. It's the answer to "which accounts do we have, and who can act on them?" — a question most companies can't answer cleanly until something forces them to.

Signatories. SAP's current term is payment approvers; the older word, signatories, survives in the import template and the migration object. They are held on the bank account and feed the payment approval workflow for payments made through it. That makes BAM the system record of who can act on what — the kind of thing that lives in a spreadsheet at most companies until an auditor or a fraud scare makes it everyone's problem. They are a full-scope feature, so confirm which scope you have before you promise treasury a full approval workflow.

Closing. Only an active account can be closed. You mark it for closing, record that the request has gone to the bank, and confirm once the bank has closed it. Depending on settings, SAP generates a closing request letter and emails it to the bank account contact person. A closed account can be reopened.

Reviewing. A review initiator selects active accounts in Manage Bank Accounts and chooses Initiate Review Process; reviewers — users with activity 31 on F_CLM_BAM — are notified, check each account in Review Bank Accounts, correct what's wrong and mark it complete. The due date on a review request is, per SAP, for information only; the review notes land in the account's history. It's the natural system anchor for a bank account rationalisation exercise.

Why BAM is the foundation, not a footnote

Here's where the plumbing metaphor earns its keep. BAM sits under three things treasury cares about every single day:

The cash position reads balances against these accounts.
Bank statement import — electronic bank statement processing — has to match incoming statements to the right account before a single line reconciles.
Outgoing payments and bank connectivity run through the same account definitions, feeding Bank Communication Management (BCM).

If the account master is wrong — a duplicated account, a stale connectivity link, a closed account still marked open — the failure shows up downstream, in the statement that won't auto-match or the position that doesn't tie out. Engineers spend a day chasing the reconciliation before someone thinks to check the account record. I've watched exactly that day get burned more than once.

One naming collision worth clearing up, because it confuses people in workshops. eBAM (electronic bank account management) is the external, bank-facing standard for opening, closing and maintaining accounts with the bank itself — the messages that flow between a corporate and its banks to actually provision an account. SAP's BAM is the internal, in-system master data record and its governance. They're complementary: eBAM is the conversation with the bank; BAM is your own governed inventory. A mature setup uses BAM as the internal book of record and connects it to the eBAM process so opening or closing an account is one governed flow rather than two disconnected ones. Confusing the two — or assuming BAM does the bank-side messaging on its own — is a common early-design mistake.

What SAP documents on the bank-facing side depends on the edition. For S/4HANA 2025 (on-premise and private edition), the Bank Correspondence page describes generated letters — an email with a PDF attachment, sent to a defined contact person — for three scenarios: opening an account, closing it, and updating payment approvers. For S/4HANA Cloud Public Edition (2608), SAP does document eBAM messages in the ISO 20022 format — an account opening request (acmt.007), a request acknowledgement (acmt.010) and an account report (acmt.014), routed through SAP Multi-Bank Connectivity — but for opening in-house bank accounts, where the other side is SAP's own In-House Banking, not an external bank. I found no SAP Help page that documents BAM exchanging acmt messages with an external bank.

What I couldn't verify

eBAM messages with an external bank. SAP documents them for in-house bank accounts in the Cloud Public Edition; I found nothing for external banks, in either edition.
The FI12 conditions on the 2025 release. SAP Help for 2025 still names FI12; the activation-mode condition is from the Simplification List for S/4HANA 2023, and I found no 2025 edition of that list.
Transports in ECC. SAP confirms house banks were configuration data; that they moved by transport is my experience, not a sentence I found.
A separate Fiori ID for Manage Bank Accounts (Basic Cash Management). SAP Help gives it its own topic; I found no distinct ID in the library.
SAP S/4HANA Cloud Public Edition. Its app set differs in places — the library lists a separate Manage Bank Account Reviews app (F7510) there — and this page isn't verified line by line against that edition.

The docs-vs-reality summary

The documentation frames Bank Account Management as administration: maintain your accounts, keep your signatories current, done. What a real project discovers is that a messy bank-account estate is the origin point of cash-visibility and reconciliation problems, not a side effect of them. Get BAM clean and governed and the cash position, the statement matching and the payment runs all have solid ground to stand on. Leave it as an afterthought and you'll pay for it every close — in the least visible, hardest-to-diagnose way SAP has to offer. BAM is boring right up until it's the reason nothing reconciles.