RECORD TO REPORT · APP
How does the Automatic Payment Program control disbursements?
The Automatic Payment Program selects eligible payables, proposes the payment decision, produces payment output, and records a controlled payment and clearing trail.
PROCESS ROLE
APP separates payment selection from approval and bank execution
Payment methods, due dates, blocks, payment terms, bank selection, payment media, approvals, and proposal logs make each payment run explainable before funds move.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Make only eligible items payable
Supplier data, due dates, payment methods, blocks, bank data, and open-item status determine the candidate population.
Review the payment decision
The proposal groups items, determines payment methods and banks, and exposes exclusions, payment blocks, and exceptions.
Authorize the run and output
A responsible approver releases the controlled payment run and its bank file, print, or supported payment channel.
Reconcile bank settlement
Payment documents, bank-clearing accounts, acknowledgements, rejections, and electronic statements prove the final result.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Eligibility and bank determination
Company code, payment method, currency, due date, payment block, supplier bank data, payment terms, house bank, and ranking order govern selection.
Approval and segregation
Proposal review, payment release, file approval, bank signatory, change control, and run-log retention separate preparation from authorization.
Exception handling
Proposal exclusions, payment rejections, cancelled files, reversals, duplicate protection, and bank-statement mismatches need visible owners.
DIAGNOSTIC EVIDENCE
Retain the decision trail for a payment run
A payment run is complete only when selection, approval, output, posting, and bank confirmation can be traced for the same population.
Run date, company code, selected and excluded items, payment method, bank determination, warnings, and approver.
Payment document, payment medium or API reference, value date, amount, currency, bank account, and release status.
Bank acknowledgement, electronic statement item, clearing account, rejection, reversal, and reconciliation result.
PAYMENT CONTROL
A proposal excludes a blocked invoice
The payment proposal selects due supplier invoices but leaves one item excluded because of a payment block. The reviewer approves the eligible population, and the excluded item remains visible for the AP owner.
- Selection is reproducible
- Exclusions are explained
- Approval precedes output
- Bank confirmation closes the loop
See how continuous accounting, operational cut-off, parallel subledger workstreams, GL close, reporting, group hand-off, and period control connect.