SAP TCodes · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
F110
F110 is the SAP transaction code for Automatic Payment Program (FI). It runs the automatic payment program, selecting due open items (vendor invoices) and creating payments (e.g. bank transfers), the workhorse of accounts-payable payment.
Quick answer
F110 runs the automatic payment program, selecting due open items (vendor invoices) and creating payments (e. g. bank transfers), the workhorse of accounts-payable payment.
Key takeaways
- Run date and identification.
- Parameters: company codes, payment methods, vendors, next payment date.
- Proposal (preview of what will be paid) then payment run.
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It runs the automatic payment program, selecting due open items (vendor invoices) and creating payments (e.g. bank transfers), the workhorse of accounts-payable payment.
Key fields and screen
- Run date and identification.
- Parameters: company codes, payment methods, vendors, next payment date.
- Proposal (preview of what will be paid) then payment run.
- Payment media (files/forms) generation.
Tips
- Always review the proposal before the actual run.
- Correct payment method/bank determination is essential.
- Exceptions/blocks show why an item was not paid.
Common errors
- Items not selected (payment block, wrong due date, missing bank data).
- No valid payment method for the vendor/country.
- House-bank/bank-determination configuration errors.
Common pitfalls
- Using the wrong variant (e.g. create vs change vs display).
- Missing prerequisite master data or config.
- Not checking the resulting document/postings.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of F110?
Frequently asked questions
What does F110 stand for in SAP?
F110 is the SAP transaction code for Automatic Payment Program (FI). It runs the automatic payment program, selecting due open items (vendor invoices) and creating payments (e.g. bank transfers), the workhorse of accounts-payable payment.
What is the order of steps for F110?
Run date and identification. Parameters: company codes, payment methods, vendors, next payment date. Proposal (preview of what will be paid) then payment run.
What else is worth knowing about F110?
Always review the proposal before the actual run. Correct payment method/bank determination is essential. Exceptions/blocks show why an item was not paid.
What tends to go wrong with F110?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.