T012K table — House Bank Account IDs (Compatibility-Oriented in S/4HANA)
T012K is the classic house-bank account-ID table linking company code and house bank to individual account IDs and related bank or G/L attributes. In S/4HANA Bank Account Management changed the bank-account data model, so legacy T012K reads can be redirected through compatibility views and should not be treated as the sole authoritative account master.
A consultant-focused reference for T012K covering its purpose, key fields, joins, safe query restrictions, proof steps, release context, ownership and recurring interpretation traps.
Published 20 Sept 2026· 703 words
What it stores
T012K stores individual account IDs underneath a company-code house bank, including bank account and G/L linkage attributes. Each row must be interpreted using the complete technical key and the application process that writes it. A consultant should first establish whether the row represents current state, a dated master-data slice, a document item, a history event, an index entry or a compatibility representation. Organizational levels, validity dates, fiscal years, ledgers, languages, statuses and sequence numbers are part of the grain whenever those dimensions exist. The table should be read as evidence of application behavior, not as an isolated spreadsheet. Confirm the owning business object and configuration before deciding that a value is wrong.
Key fields
House-bank ID plus account ID within the company-code context identifies a configured house-bank account. The account ID used by payments is not interchangeable with a G/L-account number or the external bank account number.
- BUKRS — company code.
- HBKID — house bank ID.
- HKTID — account ID under the house bank.
- Bank-account and G/L linkage fields — classic account configuration context.
- S/4HANA Bank Account Management — authoritative governance context for new designs.
How it joins the data model
Relate a T012K account ID to its parent house-bank entry in T012 and the relevant FI payment and bank-account settings. Keep company code, house bank and account ID aligned throughout the selection.
- BUKRS and HBKID to T012
- bank master through T012 to BNKA
- HKONT to SKB1 and SKA1 with company code and chart of accounts
How to read it safely
For a missing payment proposal account, verify the configured house bank first, then its account ID, permitted currency and relevant payment-method bank determination. Test in the authorized payment workflow rather than writing directly to configuration tables.
How to prove it in the data
Take one reproducible example from the relevant SAP screen, report or application log. Record its full displayed key, organizational context, key date, language and status. Locate the matching T012K row using those values, then follow the documented parent and child joins without dropping key components. Compare the result using the same key date and ledger. When values differ, test for leading-zero conversion, multiple validity slices, inactive history, parallel ledgers, fiscal-year boundaries, archived data and asynchronous replication. Save the read-only evidence before escalating. If the row is wrong, reproduce the maintenance path in a non-production system and route the fix to the application owner rather than changing the table.
ECC vs S/4HANA
SAP S/4HANA simplification documentation lists T012K with compatibility-view redirection for Bank Account Management. New designs should use the current Bank Account Management objects and released APIs or views, while T012K remains useful for compatibility and classic configuration analysis.
Common pitfalls
- Selecting by one convenient identifier and silently mixing organizational units, years, ledgers, languages or validity periods.
- Joining on a partial key or descriptive value and creating duplicates that appear to be legitimate business rows.
- Ignoring inactive, deletion, reversal or status indicators and reporting retained history as current state.
- Assuming this table is authoritative without checking S/4HANA simplification, Business Partner synchronization, Universal Journal, MATDOC, CDS views or an external cloud source.
- Treating a missing row as proof that an event never occurred even though logging, replication, authorization and archiving scope can differ.
- Updating table rows directly instead of correcting data through the supported transaction, app, API or migration process.
Whose problem this is
FI payment configuration and treasury manage house-bank accounts and selection rules. Bank-data access needs controlled authorization; infrastructure teams support only proven environment or authorization failures.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/t012kERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.