# SAP F110 Payment Run: No Payments and the Exception List > Source: https://netray.co/erp-help/sap-f110-payment-run-exception-list-no-payments-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer When F110 selects nothing or lists vendors in the exception list, the cause is one of four things: the parameters or free selection excluded the items, an item or vendor is blocked, no valid payment method or bank was found in FBZP, or the due date check did not consider the item due in this run. Display the proposal log and exception list to find which. ## Kind error ## System sap ## Erp SAP ECC / S/4HANA ## Module FI-AP Automatic Payments ## Query SAP F110 payment run no payments proposal exception list ## Alternate Queries - F110 proposal no items selected - SAP payment run vendor not paid exception list - F110 no valid payment method found - SAP automatic payment program bank determination error ## Applies To SAP ECC 6.0 and S/4HANA on-premise Automatic Payment Program (F110, FBZP); Fiori payment apps on S/4HANA use the same underlying program ## Steps ### How to diagnose an F110 run **Items:** On the Parameters tab check Posting Date, Docs entered up to, Run Date and Identification, and that the company code, payment method and next payment date are filled. The next payment date decides which items must be paid now. Use Free Selection to confirm no restriction accidentally excludes vendors, for example a supplier range or document type filter. Choose Proposal, run it, then display Proposal, Edit, Exception List. Each row shows the vendor, document, and the reason, such as no valid payment method or blocked for payment. Open the Additional Log tab before the proposal and set the flags for due date check, payment method selection and line items of payments. Rerun the proposal and read the log for the vendor in question. Check the vendor in FK03 or XK03, payment transactions tab: payment methods, payment block and house bank. Check the open items in FBL1N for a payment block key or a disputed item. Check FBZP: All company codes, paying company codes, payment methods in country and company code, bank determination, and house banks. Missing amount limits or currency for the method is a common reason for no valid method. Fix the issue, then edit the proposal (Proposal, Edit) to include items manually if needed, or delete and recreate the proposal. Schedule the payment run, then check the Status tab and Payment Medium output for the file or spool. ## Sections ### What F110 does and which tables it fills **Body:** F110 runs the Automatic Payment Program in two steps. The proposal selects open items, assigns payment methods and bank accounts, and writes results to payment proposal tables (REGUH for headers, REGUP for items). The payment run then posts documents and creates payment media. The exception list shows items or vendors the program could not or would not pay. The program is driven by customizing in FBZP rather than by the vendor screen alone. A vendor with a payment method that is not allowed in the paying company code is dropped, even when the vendor master looks right. The log and exception list tell you whether the failure is a master data issue or a configuration gap. ### Typical exception reasons **Body:** No valid payment method means no method on the vendor or invoice is also defined in the company code and country, or the amount falls outside the method's minimum and maximum limits. Bank determination errors mean there is no house bank with a ranking and an available account for the currency and method, or no balance for the account in the available amount table. A payment block (a key in the vendor line item, such as R for invoice verification), a vendor block in the master, or a one time vendor with incomplete bank data also removes items. Another common case is that the item is not yet due: the program pays items that fall due before the next run date, using the terms of payment and the next payment date, so a run date too early selects nothing. **Code:** F110 Automatic payment run (parameters, proposal, run) FBZP Payment program configuration FBL1N Vendor line items (payment block, due date) FK03 Display vendor (payment transactions) F-53 Manual outgoing payment Tables REGUH (payment header), REGUP (payment items), PAYR (check data) ### Safe ways to correct and rerun **Body:** Do not change customizing in production to rescue a single run. Use F-53 to pay urgent invoices manually and fix FBZP through transport for the next scheduled run. Within the run, you can edit the proposal to block an item or release a vendor with the change function, which is faster than deleting and recreating it. If a run has already posted partially, check the Status tab and the payment run log before restarting. A run that terminated can leave the status incomplete, and rerunning without a check can create a duplicate payment. Review the run log, payment media creation and the REGUH status with your finance team before releasing the bank file. ## Pitfalls - Setting a Run Date earlier than the invoice due date and getting an empty proposal. - Editing FBZP directly in production to fix one vendor and breaking others. - Forgetting the Additional Log flags, so the exception list gives no useful reason. - Rerunning a partially posted payment run without checking the status, causing duplicate payments. - Ignoring amount limits in payment method configuration for the company code. ## Ai Angle A grounded assistant like ERPray can read open items, vendor master payment data and the proposal tables REGUH and REGUP, then explain for a named vendor why it was not paid: block key, missing method, bank, or due date. It shows the queries and cannot start payment runs. Posting and releasing payments stays with authorised AP staff and the finance approval process. ## Faq ### Why is my F110 proposal empty? **Answer:** Most often the run date or next payment date makes no items due, the parameters exclude the company code or payment method, or all items carry a payment block. Display the proposal log with the due date check flag set to see why items were not selected. ### What does no valid payment method found mean? **Answer:** None of the payment methods on the vendor or invoice is allowed for the paying company code and country in FBZP, or the amount is outside its limits. Add the method in the company code settings or correct the vendor master and rerun the proposal. ### How do I pay one urgent invoice outside the run? **Answer:** Use F-53 for a manual outgoing payment, or add the item to the proposal in F110 by editing it. F-53 posts the payment and clearing directly, so it will not be included again by the next automatic run as long as the item is cleared. ### Where can I see payment data after the run? **Answer:** In F110 on the Status and Log tabs, and in tables REGUH and REGUP for payment headers and items. Payment media are in the spool or through the Payment Medium Workbench (DMEE or PMW) output, and check data is stored in PAYR. ## Search terms SAP F110 payment run, F110 exception list, SAP payment proposal empty, FBZP payment method bank determination, SAP no valid payment method found, SAP automatic payment program, REGUH REGUP tables, F-53 manual payment, SAP vendor payment block, SAP F110 additional log --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json