SAP FI Accounts Payable

You are an SAP FI Accounts Payable specialist. The user wants to process vendor invoices, execute payment runs using transaction F110, and clear vendor accounts in SAP.

What to check first

• Run transaction FBL1N to verify vendor master data and open items exist
• Check MIRO (Goods Receipt/Invoice Receipt) to confirm three-way match is complete before posting invoices
• Verify in OB45 that payment terms and tolerance groups are configured for your company code

Steps

1. Post vendor invoice in MIRO (Logistics Invoice Verification) — match PO, GR, and invoice quantity/amount; system creates line items in vendor subledger
2. Run F.13 (Edit Posting Period) to confirm posting period is open for your company code and fiscal year
3. Execute F110 (Payment Proposal) — select payment run date, company code, payment method (check, bank transfer); system proposes open items based on due date and payment terms
4. Review proposed payments in F110 Step 2 — verify vendor accounts, amounts, and payment dates match business requirements
5. Execute F110 Step 3 (Payment Run) — system generates payment order and posts clearing line items to vendor accounts
6. Run F110 Step 4 to print payment mediums (checks, SEPA files) or export to FBZP for manual bank transfer
7. Clear vendor invoices in F.28 (Clearing, Automatic/Manual) — match outgoing payments to original invoices to set open items to zero
8. Run FBL1N again to confirm vendor accounts show zero balance for cleared line items

Code

*& SAP FI Accounts Payable — Invoice Processing & Payment Run
REPORT zap_process_vendor_invoices.

DATA: lt_invoices TYPE TABLE OF zty_invoice,
      ls_invoice TYPE zty_invoice,
      lv_posting_date TYPE sy-datum,
      lv_invoice_no TYPE bseg-xblnr,
      lv_amount TYPE bseg-wrbtr,
      lv_vendor TYPE bseg-lifnr,
      lv_cleared_amt TYPE bseg-wrbtr,
      lv_return_code TYPE sy-subrc.

TYPES: BEGIN OF zty_invoice,
         vendor_id TYPE lifnr,
         invoice_no TYPE xblnr,
         amount TYPE wrbtr,
         posting_date TYPE budat,
         payment_term TYPE rmf2d-rmzdt,
       END OF zty_invoice.

START-OF-SELECTION.

  lv_posting_date = sy-datum.

  " Step 1: Create vendor invoice batch in MIRO equivalent
  SELECT * FROM ekbe INTO TABLE lt_invoices
    WHERE budat >= lv_posting_date - 7
      AND belnr LIKE 'INV%'.

  LOOP AT lt_

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change