Accounts Receivable in SAP FI

What Is Accounts Receivable in SAP FI?

Accounts Receivable (AR) is a subledger inside SAP FI used to manage and record accounting data for every customer of the business. The module handles customer invoices, approvals, incoming payments, credit checks, dunning, and related reporting activities that drive the customer-to-cash cycle.

Every posting that is made in Accounts Receivable is updated in the General Ledger (G/L) in real time through a reconciliation account. This keeps the customer subledger and the G/L permanently in balance, which means finance teams do not have to run extra synchronization jobs at period close.

The Accounts Receivable submodule also offers a deep set of standard reports and forecasting features. Teams use these to track customer outstanding balances, days sales outstanding (DSO), payment trends, and disputed items.

Why Accounts Receivable Matters for Finance Teams

Accounts Receivable is more than a posting tool. It is the financial control point for everything a company is owed by its customers. A clean AR process protects cash flow, supports working-capital planning, and reduces bad-debt write-offs.

In SAP FI, AR provides three core benefits:

• Integrated postings: Sales invoices from SAP SD post automatically to AR, removing manual rekeying.
• Real-time visibility: Open items, partial payments, and credit limits are visible to credit controllers immediately.
• Audit readiness: Document numbers, change logs, and reversal rules give auditors a complete paper trail.

Core Processes Covered in SAP FI Accounts Receivable

The Accounts Receivable submodule supports the chief processes shown below. Each one maps to a set of transaction codes (T-codes) that finance users run every day.

• Maintain customer master data
• Credit management and risk categories
• Invoice and credit memo processing
• Cash receipts and incoming payments
• Account analysis and reconciliation
• Reporting, dunning, and statements

Key SAP T-Codes for Accounts Receivable

The table below lists the SAP transaction codes that finance users rely on the most. Bookmark these because they cover roughly eighty percent of daily Accounts Receivable work.

FD01  Create Customer Master (Company Code)
XD01  Create Customer Master (Centrally)
FD02  Change Customer Master
FD03  Display Customer Master
FB70  Post Customer Invoice
FB75  Post Customer Credit Memo
F-28  Post Incoming Payment
F-32  Clear Customer Open Items
FBL5N View Customer Line Items
FD10N Display Customer Balances
F.27  Customer Statement Print
F150  Dunning Run

How Accounts Receivable Connects to the General Ledger

Every customer master record is linked to a reconciliation account in the General Ledger. When a user posts an invoice with FB70, SAP posts the customer line in AR and, at the same time, posts an offsetting entry to the reconciliation account in the G/L.

This design means the AR subledger and the G/L are always in balance. Reports such as FBL3N (G/L line items) and FBL5N (customer line items) can be reconciled at any moment without a batch job.

In SAP S/4HANA, this link is even tighter because of the Universal Journal (table ACDOCA). All financial postings, including AR documents, live in one line-item table, which removes data redundancy and enables embedded analytics on real-time AR data.

Step-by-Step Example: Posting and Clearing a Customer Invoice

The flow below shows a typical Accounts Receivable cycle, from creating the customer to clearing the payment. Each step references the SAP T-code used in production systems.

Step 1) Use FD01 (or BP in S/4HANA) to create the customer master record. Maintain general data, company code data, and sales area data.

Step 2) Use FB70 to post a customer invoice for, say, USD 10,000. SAP debits the customer reconciliation account and credits revenue.

Step 3) When the customer pays, use F-28 to post the incoming payment. SAP debits the bank G/L and credits the customer, clearing the open item.

Step 4) Run FBL5N to confirm the invoice now shows as a cleared item and the customer balance is back to zero.

Step 5) At month end, run F.27 to send statements and F150 to trigger the dunning run for overdue accounts.

Customer Master Data and the Business Partner Approach

The customer master is the foundation of Accounts Receivable. It stores the company name, address, payment terms, tax data, dunning data, and reconciliation account.

In classic SAP ERP, customers were created with FD01 or XD01. In SAP S/4HANA, the business partner (BP) approach replaces these transactions. A single business partner record can carry multiple roles (customer, vendor, employee), which removes duplicate data and supports a unified view of the trading relationship.

For more detail, follow the guides linked at the bottom of this article on creating, changing, and blocking customer records.

Credit Management and Dunning

SAP FI offers two layers of credit control. The classic FI-AR credit management uses credit control areas, customer risk categories, and credit limits stored in the customer master. The SAP S/4HANA Credit Management (FIN-FSCM-CR) module adds a rules-based engine, external credit data, and scoring through SAP Credit Management.

Dunning is the formal reminder process. Using F150, finance teams run dunning by company code, dunning area, and customer. SAP picks overdue items, assigns dunning levels, and prints or emails dunning letters with the correct text per level.

Incoming Payments, Partial Payments, and Residual Items

SAP supports three ways to settle a customer invoice:

• Standard incoming payment: The payment equals the invoice. Use F-28 to clear the open item in one step.
• Partial payment: The customer pays less than the invoice. SAP leaves the original invoice open and posts the payment as a separate open item linked by the invoice reference.
• Residual item: The customer pays less than the invoice. SAP clears the original invoice and creates a new open item for the remaining balance.

The choice between partial and residual depends on internal policy. Partial payment keeps the audit trail of the original invoice. Residual item creates a clean balance to dun later.

SAP Cash Application: Machine Learning for AR

SAP Cash Application is an SAP Business Technology Platform service that uses machine learning to match incoming bank statement items to open AR invoices. The model learns from past matches and proposes the best candidate, which cuts the manual work of cash application teams.

Customers report match rates of seventy to ninety percent on stable payment patterns, which frees finance staff from rekeying and speeds up DSO improvement projects.

SAP Joule and Embedded Analytics for AR

SAP Joule is the generative AI copilot embedded across SAP S/4HANA Cloud. For Accounts Receivable, Joule can answer natural-language questions such as “show me overdue customers above fifty thousand dollars” or “summarize disputed invoices for this region” without writing a query.

Combined with the Universal Journal and embedded analytics, finance teams now move from static aging reports to live, drillable AR dashboards. This is the direction that modern SAP FI Accounts Receivable is heading.

Apply It: SAP FI Accounts Receivable Tutorial Series

The articles below walk through each Accounts Receivable activity in SAP step by step. Follow them in order to build a complete, hands-on understanding of the customer-to-cash cycle.

1. Create a Customer Master Data
2. Change Customer Documents
3. How to Display Changes in Customer Master
4. How to Block or Delete a Customer
5. Create Customer Account Group
6. One Time Customer
7. How to Post a Sales Invoice
8. Document Reversal
9. Sales Returns – Credit Memo
10. How to Post Incoming Payment
11. How to Post a Foreign Currency Invoice
12. Incoming Partial Payments By Residual Method
13. Incoming Partial Payments By Partial Payment Method
14. How to Reset AR Cleared Items
15. Credit Control for the Customer

FAQs