SAP F110 Payment Run Checklist (Free, PDF/Excel)

0%

0 of 29 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Before the run

Confirm the posting period for payments is open (OB52).CRITICALPost all vendor invoices that should be due in this run and check they are not blocked for payment.CRITICALReview payment block reasons in open items (FBL1N) and clear blocks that no longer apply.Check vendor master data: bank details, payment method and payment terms are filled.Verify house bank and account configuration in FBZP for each paying company code.CRITICALConfirm exchange rates are loaded for foreign currency payments.Check that manual payments already made (F-53) are cleared so they are not paid twice.CRITICAL

Parameters and selection

Enter run date and a unique run identification in F110.CRITICALOn the Parameters tab set posting date, next payment run date, company codes and payment methods.Set the account range for vendors and the special G/L indicators to include (for example down payment requests).Choose sensible next payment date so items due before the next run are paid now.Save the parameters and check the status line shows that parameters were entered.Use a test run first when changing configuration or vendors in bulk.

Proposal

Schedule the payment proposal and wait for the status to show it was created.CRITICALOpen the proposal list and review blocked items and exceptions.Check the exception list for missing payment method, bank details or currency issues.Review the largest payments and any unusual vendors before approval.CRITICALEdit the proposal to block or release items where needed, then keep the changes.Confirm total proposed payment amount matches the cash plan or treasury forecast.

Payment run and output

Schedule the payment run only after the proposal is approved.CRITICALCheck the log: documents posted, errors and open items not paid.Schedule the print or data medium step to create checks, payment advices and the bank file.Download or transmit the bank file with the controls required by your bank (signature, approval).CRITICALArchive the payment run log and the file as evidence for audit.

After the run

Reconcile the bank clearing account with the payment file total.CRITICALCheck vendor accounts for paid items using FBL1N and clearing documents.Investigate items not paid and update owners (blocks, missing data).Note recurring exception causes and fix master data or configuration.Update the cash forecast with the actual paid amounts.

Aim to complete all critical items. Treat any unchecked critical item as a reason to pause before the payment run step, because posted payments and bank files are hard to reverse.

Get an exception check before the proposal

Ask how a read-only report could flag blocked items and missing bank data ahead of every payment run.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Tick each item as you work through a run and use the critical flags to decide when to stop. Export the completed list to PDF or Excel and attach it to your payment approval record. Copy the groups into your own procedure and add company-specific controls such as dual approval of the bank file.

Run it every payment cycle, not only when something goes wrong.
Treat critical items as stop points.
Archive the completed list with the run log.

The F110 sequence

F110 works in four stages. First you maintain parameters: run date, run identification, company codes, payment methods, vendor range and the next payment date. Then SAP builds a payment proposal, selecting open items due by the next payment date and applying payment block, method and bank logic. After review and edits, the payment run posts payment documents and clears the items. Finally the print or data medium step produces checks, advices and the bank file.

Where runs usually fail

Most problems originate before F110: blocked invoices, missing bank data, an unopened posting period, or manual payments not cleared. The proposal exception list tells you which vendors were skipped and why. Configuration in FBZP governs paying company codes, payment methods per country, bank selection and forms, so repeated exceptions often point to a setup gap rather than a one-off.

Controls and audit

Segregation of duties matters here: the person who maintains vendor bank details should not run or release payments. Keep a log of who approved the proposal and who released the bank file, and review changes to vendor bank data before each run. Dual approval at the bank side is a separate control layer you should keep in addition to SAP approvals.

Frequently Asked Questions

What is the difference between a proposal and a payment run?

The proposal only selects and lists the items that would be paid and does not post anything. The payment run posts payment documents and clears the open items, so it changes the ledger. Always review the proposal first.

Why were some invoices not included in the proposal?

Typical reasons are a payment block, an item not yet due by the next payment date, missing payment method or bank data, a locked vendor, or a company code not in the parameters. The exception list in the proposal shows the reason per item.

Can I reverse a payment run?

Individual payment documents can be reversed, but a bank file that has been sent cannot be recalled by SAP. That is why you should reconcile before sending the file and keep approvals in place.

How often should I run F110?

It depends on your payment calendar, often weekly or daily. Run it on a schedule that matches payment terms and cash planning, and set the next payment date so no item falls due between runs.

If you want an early warning on blocked items, missing bank data or unusual payments before the proposal, Netray can discuss a read-only check over your SAP open items.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP F110 Automatic Payment Run Checklist