5.1 Customer Master Data Management

The Accounts Receivable (AR) module is responsible for managing all customer accounting data, tracking receivables, and processing incoming payments. Centralized and accurate customer master data is crucial for the entire order-to-cash cycle. From a business process perspective, it ensures consistency across sales, fulfillment, and accounting departments and provides a solid foundation for effective credit management.

Similar to vendors, customers are classified using Customer Account Groups (e.g., Domestic, Export, One-Time). This grouping determines the number range for the customer account and controls the fields available on the master record screen.

A customer master record is created centrally using transaction code FD01. The creation process involves populating data across several key tabs:

• General Data: Contains basic information like the customer’s name and address.
• Company Code Data: Includes accounting-specific information such as the Reconciliation Account (linking AR to the G/L) and payment terms.
• Payment Transactions: Stores the customer’s bank details.

For business control purposes, a customer account can be blocked. The deep integration with the SD module is evident in the different block types that can be set: a Posting block prevents accounting entries, while an Order, Delivery, or Invoicing block can be used to halt specific sales processes. This is often done for customers with poor payment history. For customer records that are no longer needed, a deletion indicator can be set to mark them for archival.

With customer master records established, the system is prepared to handle the invoicing of goods and services.

5.2 AR Invoice and Credit Memo Processing

This section covers the creation and management of customer receivables, which is the process of recording the amounts owed to the company by its customers for goods delivered or services rendered.

A standard customer sales invoice is posted using transaction code FB70. This transaction creates a debit entry on the customer’s account (an open receivable) and a credit entry to a revenue G/L account. Key fields required include the Customer ID, invoice date, amount, and the relevant revenue G/L account.

If a document is posted incorrectly, it can be reversed using transaction code FB08. A Document Reversal can only be performed if the document contains no cleared items and was originally posted within the Financial Accounting module. This process creates a new document with inverse postings to nullify the original entry.

When a customer returns merchandise, often due to quality defects, a credit memo is issued for the Sales Return. This is posted using FB75. The transaction creates a credit on the customer’s account, reducing their outstanding balance, and a corresponding debit to a sales returns or revenue account.

Once invoices are issued, the next step in the cycle is to receive and post the corresponding payments from customers.

5.3 Incoming Payments and Credit Management

Managing incoming payments and customer credit effectively is vital for maintaining healthy cash flow and minimizing the financial risk associated with customer defaults. SAP AR provides robust tools for both payment processing and credit control.

A full incoming payment is posted using transaction code F-28. The user enters the bank account receiving the funds, the customer ID, and the payment amount. The crucial step is to Process Open Items, which allows the user to match the incoming payment against the specific open invoice(s) it settles, thereby clearing the invoice from the customer’s account.

If a customer pays less than the full invoice amount, it is handled as an Incoming Partial Payment. This payment is posted as a new, separate open item on the customer’s account and does not clear the original invoice. The invoice remains open until the full balance is paid.

To manage credit risk, customer credit limits are specified and controlled within a Credit Control Area. This organizational unit can be assigned to one or more company codes. A customer’s specific credit limit can be maintained using transaction code FD32. This limit is checked during sales order creation to prevent orders from exceeding the approved credit line.

For managing overdue receivables, SAP provides a dunning system. This automated process can be configured to trace overdue invoices and send reminder letters to customers according to a predefined schedule and escalation level.

Beyond the core subledgers of AP and AR, another critical FI submodule is Asset Accounting, which manages a company’s fixed assets.