RECORD TO REPORT · BANK
How do bank statements confirm cash movement?
Payment and receipt postings describe what the company initiated. Bank statements provide external confirmation and clear interim accounts when matching succeeds.
GL ACCOUNTANT OUTCOME
Use this capability inside the complete close
Learn the business purpose, SAP record, controls, diagnostic evidence, and hand-offs for this capability. Complete all R2R 202 guides to form the role-level knowledge foundation; company policy, local procedures, system authorization, and supervised execution remain workplace requirements.
PROCESS ROLE
Bank accounting separates initiated cash from bank-confirmed cash
House-bank accounts, bank clearing accounts, payment media, statement formats, external transaction codes, posting rules, matching, and reprocessing connect internal instructions to external settlement.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Create a payment or receipt
Approved payable or receivable items produce payment, incoming-payment, or bank-clearing postings through the governed channel.
Receive the bank statement
Statements enter manually, through supported file formats or APIs, or through separately licensed bank connectivity.
Post and clear automatically
External transaction mapping, posting rules, references, amounts, dates, and processing rules identify open items and clearing accounts.
Resolve unmatched items
Accountants assign, post, clear, reverse, document, and monitor items that could not be processed automatically.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Bank master and account model
House bank, account ID, bank account, main and clearing G/L accounts, currency, signatory, and payment-method assignments protect ownership.
Statement processing
Format, transaction type, external transaction mapping, posting rule, interpretation algorithm, processing rule, and duplicate protection shape automation.
Exception and channel governance
Maker-checker approval, file or API security, bank acknowledgement, rejected payment handling, reprocessing reason, and account reconciliation protect cash.
DIAGNOSTIC EVIDENCE
Prove initiation, bank confirmation, and clearing
A posted payment does not by itself prove that the bank settled it. Follow both the internal instruction and external confirmation.
Selected items, approval, payment document, payment medium or API status, value date, bank determination, and rejection.
Statement ID, format, external transaction, amount, currency, reference, posting rule, processing status, and import log.
Matched open item, bank clearing account, main bank posting, clearing document, residual item, reprocessing reason, and reconciliation result.
DAILY CONTROL
The company paid; the bank now confirms
A supplier payment credits a bank clearing account. The subsequent electronic bank statement confirms settlement, clears the interim balance, updates the main bank account, and leaves any unmatched fee for controlled reprocessing.
- Instruction is approved
- Statement is authentic and complete
- Clearing account resolves
- Exceptions remain visible
See how continuous accounting, operational cut-off, parallel subledger workstreams, GL close, reporting, group hand-off, and period control connect.