F110

By /

Tutorial on Using Transaction F110 in SAP for Automatic Payment Runs

Transaction F110 in SAP is used to process automatic payment runs for vendors and customers. This transaction is a highly efficient way to handle payments in bulk, reducing manual data entry and ensuring timely payments. Here’s a detailed guide on how to use F110 and a breakdown of each field.

Step-by-Step Guide for Using F110:

1. Access Transaction F110

  • Open SAP, and in the command field, enter F110 to access the Automatic Payment Transactions screen.

2. Define the Payment Run Parameters

Once in the F110 screen, you’ll be in the Parameters section, where you define the scope and specifics of the payment run:

  • Run Date: This is the date the payment run is being executed. It should be the current date or a date in the future when you want the payment run to occur.
  • Identification: This is a unique identifier for the payment run. You can enter any alphanumeric code to distinguish this run from others. For example, you could use the format 20240906A (for a run on September 6, 2024, marked as the first run of the day).

3. Enter the Parameters for the Payment Run

After specifying the run date and identification, click on the Parameters button. This opens the section where you set up the criteria for the payment selection. Let’s go over each field:

Company Code:
  • Enter the company code for which you are processing the payment. You can include multiple company codes if necessary, by adding each one individually.
Payment Method:
  • Specify the Payment Method (e.g., Bank Transfer, Check, Direct Debit). Payment methods are preconfigured in SAP and control how payments are executed (e.g., bank transfer, check, etc.). Some examples include:
    • T: Bank Transfer
    • C: Check
    • D: Direct Debit
Next Payment Date:
  • This field determines the earliest date on which payments will be made. Typically, you would set this to the current date or a future date if you want the payments to be made later.
Document Date:
  • Enter the document date range for the items you want to include in the payment run. This range will filter documents based on the date the invoices or transactions were created.
Vendor/Customer Accounts:
  • Specify the range of Vendor or Customer Accounts you want to include in the payment run. You can also leave this blank if you want the system to consider all open items for payment.
Free Selection (Optional):
  • In the Free Selection tab, you can set additional criteria to further filter the documents, such as specific document types or other parameters not covered in the primary fields.

4. Set Additional Parameters (Optional)

Before you proceed, review or define some additional settings if necessary:

Payment Methods per Country:
  • Under this section, you can define which payment methods apply to specific countries. For example, you might choose to pay international vendors via wire transfer but local vendors via check.
Vendor/Customer Sorting:
  • Use this setting to sort how the payment run should prioritize paying vendors or customers. This can be useful if you have special terms with specific vendors or want to pay certain invoices first.

5. Create the Proposal

Once the payment parameters are defined, the next step is to create a payment proposal:

  • Click on Proposal in the main menu and then choose to Start Proposal. This process doesn’t execute any payments but rather generates a list of open items eligible for payment based on the criteria you provided.
  • Review the Proposal: The system will create a Proposal List, where you can review all the invoices and items selected for payment. Check for any issues or errors (e.g., missing bank details, blocked invoices) and correct them as needed. Use the Edit Proposal option to exclude items or make adjustments before proceeding.
Common Errors to Review:
  • Blocked Invoices: Invoices might be blocked for payment (e.g., missing approval), so review the block reasons and remove them if they are no longer valid.
  • Missing Payment Methods: Ensure all vendors/customers have a valid payment method assigned. If not, you may need to update the master data.

6. Execute the Payment Run

After reviewing the proposal and ensuring everything is correct, you are ready to run the actual payment process:

  • Click on Payment Run. SAP will now process the payments according to the settings provided in the parameters.
  • Payment Documents: Once the payment run is completed, the system generates payment documents for each transaction processed. These documents are crucial for tracking payments and can be used for auditing purposes.
  • Clearing of Open Items: SAP will automatically clear the open items associated with each vendor or customer account once the payment is made.

7. Payment Media (Output)

After executing the payment run, the next step is to generate the payment media (e.g., electronic bank files, checks, or payment advice notes) to notify the banks or vendors of the payments:

  • Go to the Payment Media tab and generate the output for the payment medium. Depending on your company’s setup, this could involve generating a file for electronic transfer to the bank (such as a DME file or ACH file).
  • You can also print checks (if the payment method is set to C) or print/send payment advice letters to vendors informing them of the payment.

8. Review the Logs

SAP generates logs after the payment run and the proposal. These logs provide detailed information on what was processed, any errors, and a summary of the payments made:

  • Payment Proposal Log: This log helps identify issues like blocked payments or missing data before the actual payment run is executed.
  • Payment Run Log: Review this log to confirm that all payments were processed successfully. It provides details on the payment documents created and any issues encountered during execution.

9. Reprint Payment Documents or Advice Notes

In case any payment documents or advice notes need to be reprinted, you can do so via the Print Program (T-code FBZ5). This is particularly useful if a document failed to print or if a check needs to be reissued.

Fields Summary

  • Run Date: Date of the payment run.
  • Identification: Unique ID for the payment run.
  • Company Code: Specifies which company code to process payments for.
  • Payment Method: Defines how payments will be made (e.g., bank transfer, check).
  • Next Payment Date: The earliest date on which payments will be made.
  • Document Date: Filters transactions by their creation date.
  • Vendor/Customer Accounts: Specifies which vendor/customer accounts to include in the run.
  • Free Selection: Additional criteria for filtering documents.
  • Proposal: A draft list of payments to review.
  • Payment Run: Executes the actual payment transactions.
  • Payment Media: Generates payment files, checks, or advice notes.

Summary

Transaction F110 in SAP is a powerful tool for automating payment processes. By following this detailed guide, you can set up and execute payment runs efficiently while ensuring that vendor and customer payments are made on time. Regularly review logs, proposals, and payment documents to catch any errors before the payments are processed, ensuring smooth financial operations.

Scroll to Top