SAP Automatic Payment Program F110: Complete Tutorial

What Is the SAP Automatic Payment Program F110?

The SAP automatic payment program F110 tutorial is your gateway to understanding one of the most powerful tools in accounts payable. Transaction F110 (also called the Automatic Payment Program or APP) automates the process of paying your vendors based on rules you define. Instead of manually selecting invoices and creating payment documents, F110 does the heavy lifting for you.

Think of it like this: you set the rules, and F110 follows them. You tell it "pay all invoices over 30 days old to vendors in Germany via bank transfer," and it identifies those invoices, groups them intelligently, and proposes payments. This saves hours of manual work, reduces errors, and improves your cash flow forecasting.

In this tutorial, we'll walk through the key steps to set up and run F110, plus some practical tips from real-world implementations.

Why F110 Matters for Your SAP Workflow

Before we dive into the buttons and fields, let's talk about why F110 is worth mastering:

• Speed: Process hundreds of invoices in minutes instead of hours.
• Consistency: Apply the same payment rules every time—no human error.
• Cash visibility: Forecast exactly when payments will leave your bank account.
• Audit trail: Every payment decision is logged and traceable.
• Flexibility: Handle complex scenarios like partial payments, withholding taxes, and multiple currencies.

Most mid-size and large organizations run F110 weekly or monthly. Some run it daily. Once you configure it properly, it becomes almost invisible—it just works.

Key Prerequisites Before Running F110

F110 doesn't work in a vacuum. You need to have certain master data and customization in place:

• Vendor master data: Vendors must have payment terms, payment methods, and bank details configured in transaction FK01.
• Company Code settings: Define your default payment method, house bank, and payment dates in customization (OBA1, OBAI).
• Invoices ready: Open items (invoices) must exist in table BSAK (open vendor line items) and be due for payment.
• Payment method configuration: Ensure your payment methods (like SEPA, check, wire transfer) are set up correctly in transaction FBZP.

If any of these is missing, F110 will either exclude vendors or fail to run smoothly. Check these first.

Step-by-Step: Running the SAP Automatic Payment Program

Now let's get hands-on. Here's how to execute F110 in a typical scenario:

1. Open transaction F110 (type F110 in the command line or navigate via SAP Menu > Accounting > Accounts Payable > Periodic Activities > Automatic Payment Program).
2. Enter the Run Identification. This is a unique name for this payment run, like "WEEKLY_PAY_01" or "MONTHLY_SEP". Use a consistent naming convention so you can trace runs later.
3. Select your execution mode: Choose between "Test" (proposal only, no actual payments) or "Production" (creates real payment documents). Always test first.
4. Go to the Proposal tab and enter your selection criteria:
   • Company Code(s) you want to pay from
   • Vendor ranges (or leave blank for all)
   • Payment method (e.g., 'T' for transfer, 'C' for check)
   • Posting date and value date
   • Currency
5. Click "Proposal" button (or press F8). F110 will now query table BSAK for open invoices matching your criteria and show you a list of proposed payments.
6. Review the proposal. Look for anything unexpected:
   • Are vendors and amounts correct?
   • Are payment methods appropriate?
   • Are there invoices you expected to see?
   If something's wrong, you can exclude specific items or vendors before posting.
7. Save and execute. Once you're satisfied, click the "Save" button, then "Execute" (or "Post" depending on your mode). This creates payment documents in the system.
8. Generate payment medium. After execution, F110 creates a payment medium file (SEPA XML, BAI format, etc.) that you can send to your bank. This happens in the same transaction—just click "Payment Medium" to generate and download.
9. Verify and post to bank (outside SAP). Your bank team takes the payment file and processes it through your banking portal.

That's the core flow. In test mode, nothing posts to the general ledger. In production, payment documents are created immediately and invoices are marked as paid (or partially paid).

Important Tables and Fields to Know

As you work with F110, you'll encounter these SAP objects:

• BSAK: The table containing open vendor line items (invoices, credit memos). F110 reads from here.
• REGUH: Payment header information—where F110 stores the actual payment document.
• REGUP: Payment line items—the individual vendor invoices included in each payment.
• LFB1: Vendor master payment terms (table view). Check here if a vendor isn't being picked up by F110.
• TPAY: Payment methods configuration. If a payment method isn't working, check here.

You won't usually edit these tables directly, but knowing them helps you troubleshoot. For example, if a vendor isn't being proposed, check their LFB1 record to confirm payment terms and bank details are filled in.

Common F110 Pitfalls and How to Avoid Them

From real-world implementations, here are the mistakes we see most often:

Missing Payment Terms: A vendor won't be included in the proposal if their payment terms aren't defined. The system doesn't know when they're due. Check FK01 (vendor master) to confirm Net 30, Net 60, etc. is entered.

No Bank Details on Vendor Master: If F110 doesn't know how to pay a vendor (no bank account or payment method), they'll be skipped. Go to FK02 (vendor master maintenance) → Payment Transactions tab and fill in bank details and preferred payment method.

Open Items in Wrong Status: If an invoice is marked "cleared" or has a payment in progress, F110 won't see it. Use transaction FBL1N (vendor line items) to check the status of invoices.

Currency Mismatch: F110 groups payments by currency. If you select USD but vendors are invoiced in EUR, they won't match. Either run separate F110 runs per currency, or configure the payment run carefully.

Test Mode Confusion: Running F110 in test mode creates a proposal but no actual payments. New users often forget they're in test mode and wonder why payments didn't post. Always check the execution mode indicator at the top of the screen.

Best Practices for F110 Success

Here's what separates smooth F110 operations from chaotic ones:

• Schedule it: Run F110 on the same day each week or month. This creates predictability for your team and vendors.
• Use test runs: Always run a test proposal before posting. Print the proposal and have someone else review it.
• Document payment runs: Keep a log of run IDs, dates, amounts, and approval details. This is your audit trail.
• Monitor the log: After execution, check the F110 log for warnings or errors. Some vendors may have been excluded for reasons you need to understand.
• Communicate with vendors: Let vendors know your payment schedule. They'll appreciate the predictability, and you'll reduce inquiry emails.
• Reconcile payments: After payments post, verify that the amount leaving your bank matches what F110 created. This catches configuration errors early.

Next Steps in Your F110 Journey

You now understand the fundamentals of the SAP automatic payment program F110. The next natural step is to dive deeper into customization—configuring payment methods for your specific house banks, setting up withholding tax rules, or automating recurring payments.

Ready to accelerate your SAP learning and master F110 in a practical environment? Head over to Automate & Graduate for interactive tutorials and guided exercises that will take your finance automation skills to the next level.