FI / FICObeginner

FICO Accounts Receivable Part 1: What AR Does and How It Connects

Key takeaway

Accounts receivable tracks what customers owe and makes sure the company collects it. Learn the AR cycle — customer master, invoice (mostly from SD billing), incoming payment, clearing, dunning — the reconciliation account link to GL, and the reports that show collection health.

What this complete series covers

Learn Accounts Receivable 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 Receivable.
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 Receivable clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: FICO Accounts Receivable Part 1: What AR Does and How It Connects
Understand why Accounts Receivable exists as a subledger, how it fits into company code and sales organization structures, and how customer master data drives postings, payments and reporting.
Part 2: FICO Accounts Receivable Part 2: Posting Keys, Payment Terms and Customer Invoice Flow
Learn how AR configuration elements - posting keys, terms of payment, tolerance groups - drive the runtime document flow of a customer invoice from entry through GL update.
Part 3: FICO Accounts Receivable Part 3: Incoming Payments and Automatic Clearing
Explains how incoming customer payments are recorded, matched, and cleared against open items, covering manual clearing, the automatic payment/clearing program, bank statement inte
Part 4: FICO Accounts Receivable Part 4: AR Architecture Across S/4HANA Deployments
An architect-level examination of how Accounts Receivable design decisions change across ECC, S/4HANA on-premise/private cloud, and S/4HANA public cloud, covering Universal Journal
Part 5: FICO Accounts Receivable Part 5: Dunning, Credit Management and Dispute Handling
Covers the design and operational mechanics of the dunning process, integration between AR and Credit Management for exposure control, and structured dispute case handling, includi

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
✅ AR is a sub-ledger: each customer account rolls into a GL reconciliation account.
✅ Most customer invoices come from SD billing; FI invoices (FB70) are for non-sales items.
✅ Incoming payments clear open items fully, partially or with a residual item.
✅ Dunning and credit management help collect overdue amounts and control risk.
⚠️ Unapplied cash (payments not cleared against invoices) hides the true overdue position.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What AR does
Part 2: Posting keys, payment terms and invoice flow
Part 3: Incoming payments and clearing
Part 4: Architecture and migration
Part 5: Dunning, credit and disputes

━━━━━━━━━━━━━━━━━━━━
▶ 1. CUSTOMER MASTER

Business partner with company code data: recon account, payment terms, dunning procedure.

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

SD billing → accounting document; FI invoice for other income.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PAYMENT

Bank statement or manual posting; clearing.

━━━━━━━━━━━━━━━━━━━━
▶ 4. COLLECTION

Dunning, credit limits, disputes.

━━━━━━━━━━━━━━━━━━━━
▶ 5. REPORTING

Open items, aging, days sales outstanding (DSO).

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

Create a customer BP.
Post an FI invoice and a payment.
Clear and check FBL5N.

✅ CHECKPOINT: the invoice shows cleared with the payment.

Code example

ABAP Code

===== CORE TRANSACTIONS =====BP (customer role FLCU00/FLCU01) | VF01 billing → FI | FB70 FI invoice | F-28 incoming payment | FBL5N open items | F150 dunning ===== POSTINGS =====Invoice: Dr Customer 1,180 (→ recon 121000) | Cr Revenue 1,000 | Cr Output tax 180Payment: Dr Bank 1,180 | Cr Customer 1,180 (clears invoice)

Real project scenario

A mid-size distributor had high "overdue" figures although customers had paid. Cash was posted on account without clearing. Introducing electronic bank statement with search strings and daily clearing reduced unapplied cash by 80%.

Common mistakes

Payments on account.
Posting to recon accounts.
No dunning.
Ignoring disputes.
Wrong payment terms.

Best practices

Automate clearing.
Protect recon accounts.
Run dunning regularly.
Track disputes.
Monitor DSO.

Interview angle

Questions: "Explain the AR cycle", "How do SD invoices reach FI?", "What is DSO?"
Strong answer: sub-ledger, SD integration, payments and clearing, collection tools, reporting.

Practice this lesson

Quick check

1. Where do most customer invoices in an SAP system originate?

2. When a customer invoice is posted in FI, the subledger (customer) account is updated. How does the corresponding general ledger update occur?

3. What does the customer account group primarily control in a customer master record?

Interview questions

1. When a customer master is created using the Business Partner model in S/4HANA for Order-to-Cash, what are the key data levels (general data, company code data, sales area data) that must be maintained, and how do the company code segment fields specifically drive AR accounting behavior?

Answer it in your own words first, then compare.

2. A distributor's overdue report is high though customers say they paid. Explain the AR cycle and how you fix it.