FI / FICObeginner

FICO Accounts Payable Part 1: What AP Does and How It Connects

Key takeaway

Accounts payable records what the company owes suppliers and pays it on time. Learn the AP cycle — supplier master, invoice, approval, payment and clearing — the reconciliation account link to the general ledger, and how AP integrates with procurement (MM).

What this complete series covers

Learn Accounts Payable in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Accounts Payable.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Accounts Payable clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: FICO Accounts Payable Part 1: What AP Does and How It Connects
Understand the business and accounting purpose of Accounts Payable, how it fits within FI, and why accurate vendor liability tracking is critical to financial reporting and cash management.
Part 2: FICO Accounts Payable Part 2: Supplier Master Data and Core AP Configuration
Explore how vendor master data is structured, the key configuration elements (account groups, reconciliation accounts, payment terms) that drive AP behavior, and why correct setup
Part 3: FICO Accounts Payable Part 3: Invoice Posting, Payment Terms and Three-Way Match
Explains how vendor invoices are posted in FI, how payment terms drive cash discount and due date calculation, and how Logistics Invoice Verification reconciles purchase orders, go
Part 4: FICO Accounts Payable Part 4: Enterprise AP Architecture, Migration and Governance
An architect-level view of designing Accounts Payable for large, multi-entity, multi-system landscapes, covering Universal Journal implications, ECC-to-S/4HANA migration risks, pay
Part 5: FICO Accounts Payable Part 5: Automatic Payment Program Configuration and Payment Runs
Covers the configuration building blocks of the Automatic Payment Program including paying company codes, payment methods, house banks and ranking, and walks through the proposal,

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ AP is a sub-ledger: each supplier has an account whose balance rolls into a GL reconciliation account.
✅ Invoices come from procurement (MIRO, PO-based) or directly in FI (FB60 / Fiori) for non-PO spend.
✅ Payment terms determine due dates and cash discounts; the payment run pays due items and clears them.
✅ Special GL transactions (down payments, guarantees) are shown separately from normal payables.
⚠️ Never post directly to the reconciliation account — the sub-ledger and GL would no longer match.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What AP does
Part 2: Supplier master and core configuration
Part 3: Invoice posting, payment terms and three-way match
Part 4: Architecture, migration and governance
Part 5: Automatic payment program

━━━━━━━━━━━━━━━━━━━━
▶ 1. SUPPLIER MASTER

Business partner with company code data: reconciliation account, payment terms, payment methods, bank data.

━━━━━━━━━━━━━━━━━━━━
▶ 2. INVOICE

PO invoice (MIRO) or non-PO invoice (FB60); tax; withholding tax where applicable.

━━━━━━━━━━━━━━━━━━━━
▶ 3. APPROVAL AND BLOCKS

Payment blocks, workflow, three-way match variances.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PAYMENT

Automatic payment program (F110) or manual payment; bank file.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CLEARING AND REPORTING

Open items cleared; aging and supplier balances.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a supplier (business partner, supplier role).
Post a non-PO invoice.
Pay it and check clearing in FBL1N.

✅ CHECKPOINT: the invoice shows as cleared with the payment document.

Code example

ABAP Code

===== CORE TRANSACTIONS =====BP (supplier role FLVN00/FLVN01) | FB60 non-PO invoice | MIRO PO invoice | F110 payment run | FBL1N open itemsF-47/F-48 down payment request/down payment | F-44 manual clearing ===== POSTINGS =====Invoice: Dr Expense 1,000 | Dr Input tax 180 | Cr Supplier 1,180 (→ recon account 211000)Payment: Dr Supplier 1,180 | Cr Bank 1,180 (clears the invoice)

Real project scenario

A mid-size manufacturer found supplier balances in FBL1N did not match the payables GL account. Someone had posted directly to the reconciliation account in a legacy period. After migration to S/4HANA the account was set to "post automatically only" and the difference was corrected via supplier postings.

Common mistakes

Posting to reconciliation accounts.
Non-PO invoices for PO spend.
Uncontrolled bank changes.
Ignoring payment blocks.
No aging review.

Best practices

PO-based invoicing where possible.
Dual control on bank data.
Review open items and aging.
Use payment blocks deliberately.
Automate payments.

Interview angle

Questions: "Explain the AP cycle", "What is a reconciliation account?", "What is a special GL transaction?"
Strong answer: sub-ledger concept, invoice types, terms, payment and clearing, special GL, controls.

Practice this lesson

Quick check

1. Which special GL indicator is typically used when posting a vendor down payment request or down payment in SAP FI-AP?

2. What is the effect on a vendor's account balance when a credit memo is posted against that vendor in Accounts Payable?

3. Why must supplier sub-ledger totals always equal the payables reconciliation account?

Interview questions

1. Supplier balances in FBL1N don't match the payables GL account. Explain AP basics and how you'd investigate.

Answer it in your own words first, then compare.

2. What is a Business Partner (BP) with the Supplier role in SAP, and what basic master data elements make up a supplier record?