{"id":1030,"date":"2025-12-10T12:29:18","date_gmt":"2025-12-10T12:29:18","guid":{"rendered":"https:\/\/www.icacourse.in\/blog\/?p=1030"},"modified":"2026-03-20T05:51:07","modified_gmt":"2026-03-20T05:51:07","slug":"accounts-receivable-process-in-sap","status":"publish","type":"post","link":"https:\/\/www.icacourse.in\/blog\/accounts-receivable-process-in-sap","title":{"rendered":"Accounts Receivable Process In SAP: A Complete Guide"},"content":{"rendered":"<p>Accounts receivable process in SAP is crucial for your financial record keeping. It helps most of the businesses to maintain their cash flow in correct order. The end-to-end AR process begins with the creation and maintenance of customer master data (general, company code, and sales area data) in transaction XD01\/FD01.<\/p>\n<p>Sales orders created in SD automatically generate billing documents (F1\/F2 invoices) via VF01, which post accounting entries to FI-AR, debiting customers and crediting revenue.<\/p>\n<p>Incoming payments are in record through F-28 (manual) or automatic payment programs, clearing open items and updating customer accounts.<\/p>\n<p>Dunning programs (F150) automate overdue reminders, while credit management (FD32) controls customer credit limits. Standard reports like FBL5N (customer line items), aging reports, and the Accounts Receivable Information System provide real-time insights.<\/p>\n<div class=\"block\">\n<h3 style=\"margin-left: 3%!important;\">Table of Contents<\/h3>\n<ul>\n<li><a href=\"#1\">What Are Accounts Receivable?<\/a><\/li>\n<li><a href=\"#2\">What Is The Working Mechanism Of Accounts Receivable Cycle Works On SAP?<\/a><\/li>\n<li><a href=\"#3\">Explain Accounts Receivable Value Flow In SAP?<\/a><\/li>\n<li><a href=\"#4\">Accounts Receivable Process Flowchart In\u00a0 SAP<\/a><\/li>\n<li><a href=\"#5\">Accounts Receivable Steps &amp; Process In SAP<\/a><\/li>\n<li><a href=\"#6\">Accounts Receivable Business Process In SAP<\/a><\/li>\n<li><a href=\"#7\">Critical Steps In SAP AR Business Process To Know<\/a><\/li>\n<li><a href=\"#8\">SAP Accounts Receivable Document Types<\/a><\/li>\n<li><a href=\"#9\">Common AR Document Types<\/a><\/li>\n<li><a href=\"#10\">Distinction Between SAP FIORI &amp; SAP FICO<\/a><\/li>\n<li><a href=\"#11\">How Does SAP FICO Incorporate Cost Accounting?<\/a><\/li>\n<li><a href=\"#12\">KPI Accounts Receivable In SAP<\/a><\/li>\n<li><a href=\"#13\">FAQ(Frequently Asked Questions)<\/a><\/li>\n<li><a href=\"#14\">Final Takeaway<\/a><\/li>\n<\/ul>\n<\/div>\n<h2 id=\"1\">What Are Accounts Receivable?<\/h2>\n<p>Accounts Receivable (AR) means the money a company owes to its customers for goods or services delivered but not yet paid. These are short-term amounts, typically due within 30 to 90 days, recorded as current assets on the balance sheet. AR arises when a business extends credit to customers, allowing payment after delivery. Application of Accounts Receivable process in SAP can assist you in meeting your goals with ease.<\/p>\n<p>In practice, AR involves invoicing customers, tracking payments, and managing overdue accounts. It\u2019s a key component of the order-to-cash cycle, impacting cash flow and financial health. Businesses use AR aging reports to monitor payment timelines and dunning processes to chase late payments. Effective AR management ensures timely collections, reduces bad debts, and maintains liquidity.<\/p>\n<p><script src=\"https:\/\/cdnjs.cloudflare.com\/ajax\/libs\/image-map-resizer\/1.0.10\/js\/imageMapResizer.min.js\"><\/script><br \/>\n<script>window.onload = function() { imageMapResize(); }<\/script><br \/>\n<img decoding=\"async\" src=\"https:\/\/www.icacourse.in\/assets\/img\/blog\/sap-fico-cta-banner-online.webp\" alt=\"GST Certification Course\" usemap=\"#image-map\" \/><\/p>\n<map name=\"image-map\">\n<area title=\"Sap Certification Course Online\" alt=\"Sap Certification Course Online\" coords=\"360,408,465,435\" shape=\"rect\" href=\"https:\/\/www.icacourse.in\/courses\/sap-fico-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" \/>\n<area title=\"Sap Recorded Course Online\" alt=\"Sap Recorded Course Online\" coords=\"501,407,644,434\" shape=\"rect\" href=\"https:\/\/www.icacourse.in\/courses\/sap-fico-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" \/>\n<area title=\"Sap Certification classroom Course\" alt=\"Sap Certification classroom Course\" coords=\"675,406,828,436\" shape=\"rect\" href=\"https:\/\/www.icajobguarantee.com\/courses\/sap-fico-course?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" \/> <\/map>\n<h2 id=\"2\">What Is The Working Mechanism Of Accounts Receivable Cycle Works On SAP?<\/h2>\n<p>The complete Order-to-Cash (O2C) cycle that feeds Accounts Receivable in SAP (ECC or S\/4HANA) works as follows:<\/p>\n<h3>1. Customer Master Data Creation<\/h3>\n<p>Create\/maintain customers using XD01 or FD01 (central data, company code, and sales area views). Credit limit and payment terms are here (FD32 for dynamic credit management).<\/p>\n<h3>2. Sales Order Creation<\/h3>\n<p>Sales order creation is done in an SD module with pricing, delivery, and payment terms. It is a crucial Accounts Receivable Process in SAP that you need to take care off.<\/p>\n<h3>3. Outbound Delivery &amp; PGI<\/h3>\n<p>Goods are picked, packed, and the Post Goods Issue (PGI) is done \u2192 inventory reduced and Cost of Goods Sold posted. It is another crucial accounts receivable process in SAP that you should be well aware of.<\/p>\n<h3>4. Billing Document Creation<\/h3>\n<p>Invoice\/F2 billing document generation from delivery\/sales order \u2192 automatically releases accounting document to FI-AR:<\/p>\n<p>Dr. Customer (Accounts Receivable)<\/p>\n<p>Cr. Revenue + Tax<\/p>\n<h3>5. Accounts Receivable Posting<\/h3>\n<p>An open item is there in a customer account (visible in FBL5N). Reconciliation accounts (usually 130000) links subledger to G\/L. Accounts receivable process in SAP can help you in meeting your goals with complete ease.<\/p>\n<h3>6. Incoming Payment Receipt<\/h3>\n<ul>\n<li>Manual: F-28 (post incoming payment + clear open items)<\/li>\n<li>Automatic: F110 (payment program) or lockbox\/Electronic Bank Statement (FF_5 \/ FEBA) Payment clears the invoice \u2192 customer open item status becomes \u201cCleared\u201d.<\/li>\n<\/ul>\n<h3>7. Credit Management<\/h3>\n<p>If credit limit exceeds \u2192 sales order\/delivery\/billing gets blocked until released (VKM1\/VKM4). However, you should maintain proper credit management tools to make things work well in your way. Accounts Receivable Process In SAP cannot ignore the process of proper credit management.<\/p>\n<h3>8. Dunning For Overdue Items<\/h3>\n<p>Automated overdue reminders sent according to the dunning procedure defined in customer master.<\/p>\n<h3>9. Account Analysis &amp; Reporting<\/h3>\n<ul>\n<li>FBL5N: Customer line item display<\/li>\n<li>FAGLL03 \/ S_AC0_52000887: G\/L view<\/li>\n<li>FDI1 \/ FDI2: AR aging reports<\/li>\n<li>F.27: Periodic account statements<\/li>\n<\/ul>\n<h3>10. Period End Closing<\/h3>\n<ul>\n<li>F.14 \/ F.07: Carry forward AR balances<\/li>\n<li>Bad debt provisions, forex revaluation (FAGL_FC_VAL), regrouping of receivables\/payables.<\/li>\n<\/ul>\n<h2 id=\"3\">Explain Accounts Receivable Value Flow In SAP?<\/h2>\n<p>Accounts Receivable (AR) refers to the amounts customers owe a business for products or services that have been provided but remain unpaid. Gaining a clear understanding of how values flow through the Accounts Receivable process in SAP is crucial for effective cash flow management, optimizing working capital, and ensuring accurate financial reporting. The following sections provide a detailed, structured overview of these AR value flows:<\/p>\n<h3>1. Customer Master Data Creation( F1 Customer Role)<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>Prior to initiating any Accounts Receivable transactions, the customer master record must be created or modified in SAP through transaction codes such as XD01 (full customer creation including SD) or FD01 (FI-only customer creation). This record captures general information (such as name and address), company code-level settings (reconciliation account, payment terms, tolerance group), and, when applicable, sales area data for SD integration. Accounts receivable process in SAP is crucial for your brand development.<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>At this stage, no actual financial amounts are posted; however, the master data configuration lays the critical groundwork for all subsequent AR activities. In SAP S\/4HANA, the customer is assigned the appropriate Business Partner role (e.g., \u201cCustomer\u201d with FI role), which establishes the link between the subledger and the corresponding General Ledger reconciliation account.<\/p>\n<ul>\n<li><b>Example:<\/b><\/li>\n<\/ul>\n<p>A new client named \u201cVelotics\u201d is set up with an approved credit limit of $50,000 and standard payment terms of net 30 days.<\/p>\n<h3>2. Credit Sale &amp; Invoice Creation ( Lead To Cash Integration)<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>The Order-to-Cash cycle begins in the Sales and Distribution (SD) module with the creation of a sales order via transaction VA01. This is followed by outbound delivery (VL01N\/VL02N) and the generation of a billing document (customer invoice) using transaction VF01, which instantly triggers an automatic posting to the Accounts Receivable subledger in Financial Accounting (FI).<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>The billing document simultaneously increases the customer\u2019s open-item balance in the AR subledger and posts the corresponding amount to the designated GL reconciliation account (typically an \u201cAccounts Receivable \u2013 Trade\u201d account). This transaction recognizes revenue in the profit and loss statement while recording a current asset (Accounts Receivable) on the balance sheet.<\/p>\n<ul>\n<li><b>SAP Specifics:<\/b><\/li>\n<\/ul>\n<p>In SAP S\/4HANA, seamless SD-FI integration ensures that the moment the billing document is released to accounting, a real-time accounting document is generated in the Universal Journal (ACDOCA). For instance, a Rs 10,000 invoice results in an immediate debit to the customer\u2019s subledger account and a credit to the relevant revenue account(s) determined via account determination (VKOA).<\/p>\n<ul>\n<li><b>Example:<\/b><\/li>\n<\/ul>\n<p>When Velotics is billed Rs 10,000 for a shipment of bicycles, the system automatically raises the customer\u2019s Accounts Receivable balance by Rs 10,000 and recognizes Rs 10,000 in sales revenue.<\/p>\n<h3>3. Customer Payment Processing (Incoming Payments)<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>Incoming customer payments are captured either manually through transaction F-28 (Post Incoming Payments) or via automated channels such as electronic bank statements, lockbox imports, or EDI payment files in SAP S\/4HANA. Once posted, the payment automatically clears the corresponding open invoices and reduces the outstanding balance in the customer\u2019s Accounts Receivable account.<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>The bank or cash account is debited to reflect the cash receipt, while the customer\u2019s Accounts Receivable account is credited, eliminating or decreasing the open item. This transaction appears as a positive cash inflow under operating activities in the statement of cash flows. The structured Accounts Receivable process in SAP ensures that every value movement follows the correct sequence from invoice creation to final settlement.<\/p>\n<ul>\n<li><b>SAP Specifics:<\/b><\/li>\n<\/ul>\n<p>SAP provides multiple posting methods: manual (F-28\/F-26), semi-automated (lockbox program or FF_5 for EBS), and fully automated (EDI\/IDoc or payment advice processing). The system intelligently matches incoming amounts to open items using reference numbers, amounts, dates, or assignment fields. For instance, a Rs 10,000 incoming payment is automatically offset against the matching Rs 10,000 invoice, bringing the customer\u2019s open balance to zero.<\/p>\n<h3>4. Discounts &amp; Payment Terms<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>When a customer settles an invoice within the agreed early-payment discount window (for example, 2% reduction if paid within 10 days), the allowed cash discount is automatically or manually applied at the time of payment posting.<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>The customer\u2019s Accounts Receivable balance is cleared in full for the original invoice amount, the bank account is increased only by the net amount received, and the difference is recognized either as a cash discount expense or as a reduction in revenue.<\/p>\n<ul>\n<li><b>SAP Specifics:<\/b><\/li>\n<\/ul>\n<p>Early-payment terms (e.g., 2\/10 net 30) are configured in the customer master record and inherited by the invoice. During payment entry in F-28 (or via automatic payment programs\/lockbox), the system proposes or validates the eligible discount based on the payment date. For instance, a Rs 10,000 invoice settled early triggers a Rs 9,800 bank receipt and a Rs 200 posting to the cash discount granted account.<\/p>\n<ul>\n<li><b>Example:<\/b><\/li>\n<\/ul>\n<p>Velotics remits Rs 9,800 within the 10-day discount period to settle a Rs 10,000 invoice, resulting in the system granting and posting a Rs 200 cash discount while fully clearing the receivable.<\/p>\n<h3>5. Dispute Management<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>When a customer challenges an invoice\u2014for instance, due to pricing inaccuracies\u2014a dispute case is opened in SAP S\/4HANA using Dispute Management (transaction UDM_DISPUTE or via Fiori apps). These cases are systematically monitored until resolution, which may result in issuing a credit memo, partial adjustment, or a write-off.<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>Upon resolution via credit memo, the customer\u2019s Accounts Receivable balance is decreased, and a corresponding adjustment is made either to revenue or to a dedicated returns\/allowances account. In the case of a write-off, the receivable is eliminated, and a bad-debt or doubtful-accounts expense is recognized.<\/p>\n<ul>\n<li><b>SAP Specifics:<\/b><\/li>\n<\/ul>\n<p>Dispute Management is tightly integrated with Accounts Receivable, enabling users to generate dispute cases directly from open items in FBL5N or via automated workflows. For example, a Rs 1,000 disputed amount can be settled by releasing a Rs 1,000 credit memo (document type DG), which simultaneously reduces the AR balance and reverses the original revenue recognition.<\/p>\n<ul>\n<li><b>Example:<\/b><\/li>\n<\/ul>\n<p>Velotics raises an objection to a Rs 1,000 billing line due to an incorrect unit price; after verification, a Rs 1,000 credit memo is posted, instantly lowering the outstanding receivable by the same amount.<\/p>\n<h3>6. Collections &amp; Dunning<\/h3>\n<ul>\n<li><b>Process:<\/b><\/li>\n<\/ul>\n<p>SAP Collections Management uses intelligent, rule-based prioritization (often enhanced with AI) to identify overdue receivables and generate targeted worklists for collection specialists (transaction UDM_SPECIALIST). Simultaneously, the dunning program (transaction F150) automatically issues reminder notices or letters for past-due invoices.<\/p>\n<ul>\n<li><b>Value Flow:<\/b><\/li>\n<\/ul>\n<p>No immediate financial posting occurs until the customer settles the amount; however, proactive dunning and collections activities shorten the collection cycle and lower Days Sales Outstanding (DSO). When configured, overdue interest can be calculated and added as an additional receivable.<\/p>\n<ul>\n<li><b>SAP Specifics:<\/b><\/li>\n<\/ul>\n<p>Dunning procedures escalate communication intensity according to the number of days past due (e.g., friendly reminder \u2192 firm notice \u2192 legal warning), delivered via print, email, or workflow. For instance, a Rs 5,000 invoice that is 60 days overdue automatically triggers the appropriate dunning level, prompting the customer to pay.<\/p>\n<ul>\n<li><b>Example:<\/b><\/li>\n<\/ul>\n<p>Velotics receives an automated dunning notice for a $5,000 invoice that is significantly overdue, which successfully drives the customer to remit payment shortly thereafter. This capability represents one of the most vital components of the end-to-end Accounts Receivable process in SAP.<\/p>\n<h2 id=\"4\">Accounts Receivable Process Flowchart In\u00a0 SAP<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1033\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/Accounts-Recievable-Flow-Chart-In-SAP-300x204.png\" alt=\"Accounts Receivable process Flowchart \" width=\"751\" height=\"511\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/Accounts-Recievable-Flow-Chart-In-SAP-300x204.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/Accounts-Recievable-Flow-Chart-In-SAP-768x522.png 768w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/Accounts-Recievable-Flow-Chart-In-SAP.png 811w\" sizes=\"auto, (max-width: 751px) 100vw, 751px\" \/><\/p>\n<div class=\"block\">Image Source : erp.pics.com<\/div>\n<div class=\"blockquote\">\n<p>Few related topics for your knowledge<\/p>\n<ul>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/sap-fico-vs-sap-hana\" target=\"_blank\" rel=\"noopener\">SAP FICO Vs SAP HANA: Which Is Better<\/a><\/li>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/procure-to-pay-process\" target=\"_blank\" rel=\"noopener\">Analyzing The Procure To Pay Process: A Comprehensive Overview<\/a><\/li>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/how-sap-fico-works-in-manufacturing-industry\" target=\"_blank\" rel=\"noopener\">How SAP FICO Works In Manufacturing Industry<\/a><\/li>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/sap-fico-transaction-codes\" target=\"_blank\" rel=\"noopener\">SAP FICO Transaction Codes: List Of T-Codes To Remember<\/a><\/li>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/why-smart-finance-pros-are-rushing-to-learn-sap-fico\" target=\"_blank\" rel=\"noopener\">Why Smart Finance Pros Are Rushing To Learn SAP FICO<\/a><\/li>\n<li><a href=\"https:\/\/www.icacourse.in\/blog\/sap-mm-interview-questions-and-answers\" target=\"_blank\" rel=\"noopener\">50+ SAP MM Interview Questions and Answers Revealed<\/a><\/li>\n<\/ul>\n<\/div>\n<h2 id=\"5\">Accounts Receivable Steps &amp; Process In SAP<\/h2>\n<p>The Accounts Receivable process in SAP is the financial part of the Order-to-Cash (O2C) cycle. It begins when a customer places an order and ends only when the company receives full payment and all open items are cleared. Below is the complete, real-world sequence as implemented in SAP ECC and SAP S\/4HANA.<\/p>\n<h3>1. Customer Master Data Set Up<\/h3>\n<p>Before any transaction, a customer record must exist. In S\/4HANA, this is created as a Business Partner (transaction BP) with the role \u201cFI Customer\u201d and optionally \u201cCustomer\u201d (for SD). In ECC, use XD01 (with SD) or FD01 (FI-only). Key fields include the reconciliation account (e.g., 130000 \u2013 Trade Receivables), payment terms (net 30, 2\/10 net 30, etc.), credit limit, and tolerance group. No financial posting occurs at this stage, but this step is mandatory for all subsequent AR activity.<\/p>\n<h3>2. Sales Order Creation<\/h3>\n<p>The process starts in the Sales and Distribution (SD) module with transaction VA01. A sales order is created specifying material, quantity, pricing, and delivery date. SAP performs an automatic credit check (if configured). No FI posting yet.<\/p>\n<h3>3. Outbound Delivery &amp; Picking<\/h3>\n<p>Using VL01N or VL02N, a delivery document is created, and goods are picked from the warehouse. Still no FI posting. Accounts Receivable Process in SAP can help you in making the correct outbound delivery.<\/p>\n<h3>4. Post Goods Issue<\/h3>\n<p>When goods leave the warehouse (VL02N \u2192 Post Goods Issue), inventory is reduced and Cost of Goods Sold (COGS) is recorded in Materials Management (MM). This step triggers the possibility of billing.<\/p>\n<h3>5. Customer Invoicing &amp; Billing<\/h3>\n<p>Transaction <b>VF01<\/b> (or collective run VF04) creates the billing document (usually type F2 \u2013 standard invoice). This is the most important step for AR:<\/p>\n<ul>\n<li>The moment the billing document is saved and released to accounting, SAP automatically creates an FI accounting document.<\/li>\n<li>Typical posting: Debit: Customer (Accounts Receivable subledger) Credit: Revenue account(s) Credit: Output tax (VAT\/GST) if applicable<\/li>\n<li>In S\/4HANA, everything is written instantly to the Universal Journal table <b>ACDOCA<\/b>.<\/li>\n<\/ul>\n<h3>6. Down Payment<\/h3>\n<p>Customer is asked to pay in advance.<\/p>\n<ul>\n<li>Step 1: Create down payment request (F-37).<\/li>\n<li>Step 2: Receive money (F-29) \u2192 Dr Bank, Cr Special G\/L account (indicator \u201cA\u201d).<\/li>\n<li>When final invoice is created later, the down payment is automatically cleared against the invoice.<\/li>\n<\/ul>\n<h3>7. Incoming Customer Payment<\/h3>\n<p>When the customer pays, several options exist:<\/p>\n<ul>\n<li>Manual posting: <b>F-28<\/b> (most commonly used)<\/li>\n<li>Automatic bank statement import: <b>FF_5<\/b> or lockbox<\/li>\n<li>Automatic payment program or EDI Posting: Debit: Bank or Cash account Credit: Customer (clears the open invoice) The invoice status changes from \u201cOpen\u201d to \u201cCleared\u201d in the system.<\/li>\n<\/ul>\n<h3>8. Credit Memos<\/h3>\n<p>For returns, pricing corrections, or goodwill:<\/p>\n<ul>\n<li>SD route: <b>VF01<\/b> with billing type RE \u2192 credit memo.<\/li>\n<li>FI route: <b>FB75<\/b> Posting: Dr Revenue\/Returns, Cr Customer \u2192 reduces AR balance.<\/li>\n<\/ul>\n<h3>9. Dispute Management<\/h3>\n<p>If a customer disputes an invoice, a dispute case is created (transaction UDM_DISPUTE in S\/4HANA). The disputed amount is flagged, and resolution may lead to a credit memo or write-off.<\/p>\n<div class=\"block\">\n<table style=\"padding: 0; border: 0!important;\" width=\"100%\" align=\"center\">\n<tbody>\n<tr>\n<td style=\"padding: 0; border: 0!important;\" colspan=\"2\" align=\"center\">\n<h3 style=\"background: #3E4095; color: #fff!important;\">Rule the Market with Professional SAP Training<\/h3>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 0; border: 0!important;\" align=\"center\"><a class=\"btn btn-primary\" style=\"color: #fff!important; text-decoration: none!important;\" href=\"https:\/\/www.icacourse.in\/tag\/online-sap-courses?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" rel=\"noopener\">SAP Certification Courses<\/a><\/td>\n<\/tr>\n<tr>\n<td style=\"border: 0!important;\" colspan=\"4\" align=\"center\"><strong> Explore All SAP Courses <\/strong><br \/>\n<a href=\"https:\/\/www.icacourse.in\/courses\/sap-fico-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" rel=\"noopener\">SAP FICO Course online<\/a> | <a href=\"https:\/\/www.icacourse.in\/courses\/sap-mm-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" rel=\"noopener\">SAP MM Course Online<\/a> | <a href=\"https:\/\/www.icacourse.in\/courses\/sap-pp-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" rel=\"noopener\">SAP PP Course Online<\/a> | <a href=\"https:\/\/www.icacourse.in\/courses\/sap-sd-course-online?utm_campaign=SAP_CTA&amp;utm_source=Blog\" target=\"_blank\" rel=\"noopener\">SAP SD Course Online<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2 id=\"6\">Accounts Receivable Business Process In SAP<\/h2>\n<p>The SAP Accounts Receivable (FI-AR) business process is the financial completion of the Order-to-Cash (O2C) cycle. It records money owed by customers, ensures timely collection, and accurately reflects receivables in financial statements. Below is the real-world, end-to-end business process as implemented in SAP ECC and SAP S\/4HANA.<\/p>\n<h3>1. Pre-requisites &amp; Master Data<\/h3>\n<ul>\n<li>Customer Master Data<\/li>\n<li>Created as Business Partner (S\/4HANA \u2013 transaction BP) or via XD01\/FD01 (ECC).<\/li>\n<li>Critical fields:<\/li>\n<li>\u2013 Reconciliation account (e.g., 130100 \u2013 Trade Receivables \u2013 Domestic)<\/li>\n<li>\u2013 Payment terms (e.g., 0001 = payable immediately, 0012 = 2\/10 net 30)<\/li>\n<li>\u2013 Credit limit &amp; risk category (links to Credit Management)<\/li>\n<li>\u2013 Tolerance group, dunning procedure, house bank<\/li>\n<li>This determines how every future transaction will be posted.<\/li>\n<\/ul>\n<h3>2. Order Creation &amp; Credit Check<\/h3>\n<ul>\n<li>Sales order created (VA01).<\/li>\n<li>System performs automatic credit check (static or dynamic) using FD32 (ECC) or UKM_CASE (S\/4HANA).<\/li>\n<li>If credit limit exceeded \u2192 order is blocked for delivery until released by credit team.<\/li>\n<\/ul>\n<h3>3. Delivery &amp; Goods Issue<\/h3>\n<ul>\n<li>Outbound delivery (VL01N\/VL02N) \u2192 Post Goods Issue (PGI).<\/li>\n<li>Inventory reduced, COGS posted (MM-FI integration).<\/li>\n<li>Billing now becomes possible.<\/li>\n<\/ul>\n<h3>4. Customer Invoicing- The Birth Of Accounts Receivable<\/h3>\n<ul>\n<li><b>Key moment for AR<\/b>: Billing document created via <b>VF01<\/b> (or collective VF04\/VF06).<\/li>\n<li>Billing type F2 (standard invoice), F1 (delivery-related), etc.<\/li>\n<li>The instant the invoice is released to accounting: \u2192 Automatic FI document is generated (document type RV). \u2192 Posting: Dr. Customer (open item in subledger) Cr. Revenue accounts (determined via VKOA) Cr. Output tax (VAT\/GST)<\/li>\n<li>In S\/4HANA: Everything lands real-time in <b>ACDOCA<\/b> (Universal Journal).<\/li>\n<\/ul>\n<h3>5. Payment Receipt &amp; Clearing<\/h3>\n<ul>\n<li>Customer pays via bank transfer, check, card, etc.<\/li>\n<li>Recording options: \u2013 Manual: <b>F-28<\/b> (most common), F-26 (fast entry) \u2013 Automatic: Electronic bank statement (FF_5), lockbox, EDI, payment advice<\/li>\n<li>Posting: Dr. Bank \/ Cash Cr. Customer \u2192 open item cleared<\/li>\n<li>Status changes from \u201cOpen\u201d to \u201cCleared\u201d (visible in FBL5N).<\/li>\n<\/ul>\n<h3>6. Special Payment Scenarios<\/h3>\n<ul>\n<li><b>Early Payment Discount<\/b>: If terms allow 2\/10 net 30 and customer pays within 10 days \u2192 F-28 automatically proposes discount \u2192 Dr. Cash Discount Granted (expense).<\/li>\n<li><b>Partial \/ Residual Payments<\/b>: Customer pays less \u2192 either partial payment (original invoice remains) or residual item (new open item created).<\/li>\n<li><b>Down Payments \/ Advances<\/b>: F-29 \u2192 special G\/L indicator \u201cA\u201d \u2192 cleared automatically when final invoice posted.<\/li>\n<\/ul>\n<h3>7. Adjustments &amp; Corrections<\/h3>\n<ul>\n<li><b>Credit Memos<\/b> (returns, pricing errors, rebates): SD route: VF01 (type RE) \u2192 FI route: FB75 \u2192 Dr. Revenue\/Sales Deductions, Cr. Customer<\/li>\n<li><b>Debit Memos<\/b> (under-billing): Opposite posting.<\/li>\n<\/ul>\n<h3>8. Collections &amp; Dunning<\/h3>\n<ul>\n<li><b>Dunning<\/b> (F150): Automated reminder letters\/emails for overdue items. Levels escalate: Level 1 (friendly), Level 4 (legal action possible). Can add dunning interest \u2192 Dr. Customer, Cr. Interest Income.<\/li>\n<li><b>Collections Management<\/b> (S\/4HANA): Transaction UDM_SPECIALIST \u2192 AI-driven worklists, promise-to-pay tracking.<\/li>\n<\/ul>\n<h3>9. Dispute Management<\/h3>\n<ul>\n<li>Customer disputes invoice \u2192 create dispute case (UDM_DISPUTE).<\/li>\n<li>Disputed amount flagged \u2192 resolution via credit memo, write-off, or escalation.<\/li>\n<\/ul>\n<h3>10. Bad Debts &amp; Write off<\/h3>\n<ul>\n<li>Uncollectible receivables \u2192 write-off via<\/li>\n<li>\u2013 Manual: F-30 with clearing<\/li>\n<li>\u2013 Automatic programs<\/li>\n<\/ul>\n<h2 id=\"7\">Critical Steps In SAP AR Business Process To Know<\/h2>\n<p>The SAP Accounts Receivable (FI-AR) business process is the financial backbone of the entire Order-to-Cash (O2C) cycle. It begins the moment a customer is promised goods or services and ends only when cash is received, open items are cleared, and the books are reconciled. The process is the same in principle in SAP ECC and SAP S\/4HANA, though S\/4HANA delivers real-time postings, embedded analytics, and a simplified data model (Universal Journal \u2013 ACDOCA). Below are the key steps every organization using SAP follows, explained in practical, real-world detail.<\/p>\n<h3>1. Customer Master Data Creation &amp; Maintenance<\/h3>\n<p>Everything starts here. No invoice can be posted without a valid customer master record.<\/p>\n<ul>\n<li>In SAP S\/4HANA: Use transaction <b>BP<\/b> (Business Partner). One Business Partner can have multiple roles \u2014 \u201cFI Customer\u201d (for FI-AR) and \u201cCustomer\u201d (for SD).<\/li>\n<li>In ECC: <b>XD01<\/b> (creates customer with SD + FI views) or <b>FD01<\/b> (FI-only). Key mandatory fields for AR:\n<ul>\n<li>Reconciliation account (e.g., 130000 \u2013 Domestic Trade Receivables) \u2013 this is the GL account to which all customer postings summarize.<\/li>\n<li>Payment terms (e.g., 0001 = immediate, 0014 = 2\/10 net 30).<\/li>\n<li>Credit control area &amp; credit limit (links to credit management).<\/li>\n<li>Dunning procedure and dunning block.<\/li>\n<li>Tolerance group (defines acceptable under\/over payment amounts). Without correct master data, invoices will fail to post or post to wrong accounts.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>2. Sales Order Creation &amp; Automatic Credit Check<\/h3>\n<p>Sales department creates the sales order using <b>VA01<\/b>.<\/p>\n<p>At save, SAP automatically performs a credit check (if activated):<\/p>\n<ul>\n<li>Static check: Total receivables + order value vs credit limit.<\/li>\n<li>Dynamic check: Includes open orders and deliveries. If limit is exceeded \u2192 order is blocked for delivery (credit block). Credit team releases via <b>VKM1<\/b> (ECC) or Fiori \u201cManage Credit Blocks\u201d (S\/4HANA). No FI posting occurs yet, but this step prevents creation of new receivables that are likely uncollectible.<\/li>\n<\/ul>\n<h3>3. Outbound Delivery &amp; Post Goods Issue<\/h3>\n<p>Logistics creates delivery (<b>VL01N\/VL02N<\/b>) \u2192 picks and packs \u2192 executes Post Goods Issue.<\/p>\n<p>At PGI:<\/p>\n<ul>\n<li>Inventory is reduced.<\/li>\n<li>Cost of Goods Sold (COGS) is posted (MM-FI integration). This step makes the transaction billable.<\/li>\n<\/ul>\n<h3>4. Customer Invoice Creation &#8211; The Moment AR Is Born<\/h3>\n<p>This is the single most important step for Accounts Receivable.<\/p>\n<p>Billing team runs <b>VF01<\/b> (single) or <b>VF04\/VF06<\/b> (collective billing).<\/p>\n<p>Common billing types:<\/p>\n<ul>\n<li>F2 = Standard customer invoice<\/li>\n<li>F1 = Delivery-related invoice Upon saving and releasing the billing document to accounting:<\/li>\n<li>SAP automatically creates an FI accounting document (document type RV).<\/li>\n<li>Posting: Dr. Customer (open item in subledger) Cr. Revenue account(s) \u2013 determined via account determination transaction <b>VKOA<\/b> Cr. Output tax (VAT\/GST) if applicable In S\/4HANA, the entry is written instantly to the <b>Universal Journal (ACDOCA)<\/b> \u2013 no more reconciliation between FI and CO. At this exact moment, Accounts Receivable increases on the balance sheet and revenue is recognized.<\/li>\n<\/ul>\n<h3>5. Down Payment \/ Advance Payment Handling<\/h3>\n<p>Many companies require partial or full payment before delivery.<\/p>\n<ul>\n<li>Create down payment request in SD (<b>F-37<\/b>).<\/li>\n<li>When customer pays: <b>F-29<\/b> with special G\/L indicator \u201cA\u201d. Posting: Dr. Bank | Cr. Customer Down Payment Clearing (special G\/L account).<\/li>\n<li>When final invoice is later created, SAP automatically clears the down payment against the invoice.<\/li>\n<\/ul>\n<h3>6. Incoming Customer Payment &amp; Open Item Handling<\/h3>\n<p>The core daily activity of any AR clerk.<\/p>\n<p>Payment receipt options:<\/p>\n<ul>\n<li>Manual posting: <b>F-28<\/b> (Post Incoming Payments) \u2013 most widely used.<\/li>\n<li>Fast entry: <b>F-26<\/b>.<\/li>\n<li>Automatic: Electronic bank statement (<b>FF_5<\/b>), lockbox, payment advice, EDI. Posting: Dr. Bank \/ Main Bank \/ Incoming Check account Cr. Customer \u2192 open invoice is cleared (status changes from Open \u2192 Cleared). The system matches using reference number, amount, document number, or assignment field.<\/li>\n<\/ul>\n<h3>7. Early Payments &amp; Cash Discounts<\/h3>\n<p>If payment terms offer discount (e.g., 2\/10 net 30), and customer pays within 10 days:<\/p>\n<p>In F-28, SAP automatically calculates and proposes the discount based on payment date.<\/p>\n<p>Example for Rs 10,000 invoice:<\/p>\n<p>Customer pays Rs 9,800 on day 8 \u2192<\/p>\n<p>Bank A\/c \u2014&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- Dr Rs 9800<\/p>\n<p>Cash Discount Granted A\/c \u2014&#8212;&#8212;&#8212;&#8212;&#8212;- Dr Rs\u00a0 200<\/p>\n<p>To Customer A\/c \u2014&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;Cr Rs 10,000<\/p>\n<p>The discount is an expense (or revenue reduction depending on configuration).<\/p>\n<h2 id=\"8\">SAP Accounts Receivable Document Types<\/h2>\n<p>Here are the key SAP Accounts Receivable (FI-AR) Document Types explained in clear text format (standard in SAP ECC and S\/4HANA):<\/p>\n<h3>1. DR- Customer Invoice<\/h3>\n<p>This is the standard document type for posting normal invoices to customers. Used in transactions like FB70 (single-screen) or F-22 (classic). It posts a debit to the customer receivable account.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1034\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DR-Customer-Invoice-300x285.png\" alt=\"DR Customer Service \" width=\"731\" height=\"694\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DR-Customer-Invoice-300x285.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DR-Customer-Invoice.png 591w\" sizes=\"auto, (max-width: 731px) 100vw, 731px\" \/><\/p>\n<div class=\"block\">Image Source : Blog. SAP Press.com<\/div>\n<h3>2. DG- Customer Credit Memo<\/h3>\n<p>Used when issuing a credit note to a customer (e.g., for returns, price corrections, discounts after invoicing). Posts a credit to the customer account. Transaction: FB75 or F-27.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1036\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DG-Customer-Credit-Memo-300x279.png\" alt=\"\" width=\"617\" height=\"574\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DG-Customer-Credit-Memo-300x279.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DG-Customer-Credit-Memo.png 546w\" sizes=\"auto, (max-width: 617px) 100vw, 617px\" \/><\/p>\n<h3>3. DZ &#8211; Customer Payment<\/h3>\n<p>Standard document type for incoming payments from customers (cash, check, bank transfer, payment cards). Used in F-28 (manual incoming payment), F-32 (clear open items), or automatic payment programs. Posts a credit to the customer and debit to bank\/cash.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1037\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DZ-customer-Payment-300x274.png\" alt=\"DZ Customer Payment \" width=\"695\" height=\"635\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DZ-customer-Payment-300x274.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DZ-customer-Payment.png 604w\" sizes=\"auto, (max-width: 695px) 100vw, 695px\" \/><\/p>\n<h3>4. DA- Customer Debit Memo<\/h3>\n<p>Rarely used. Represents an additional debit to the customer (e.g., undercharged invoice correction). A DA document is used to charge a customer an additional amount after the original invoice has already been issued.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1039\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DA-Customer-Debit-Memo-300x259.png\" alt=\"DA Customer Debit Memo \" width=\"701\" height=\"605\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DA-Customer-Debit-Memo-300x259.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/DA-Customer-Debit-Memo.png 485w\" sizes=\"auto, (max-width: 701px) 100vw, 701px\" \/><\/p>\n<div class=\"block\">Image Source : Guru99.com<\/div>\n<h3>5. RV- Billing Document Transfer<\/h3>\n<p>Automatically generated when an SD billing document (created via VF01\/VF04) is released to accounting. This is how most customer invoices from Sales &amp; Distribution reach FI. Usually uses external number range 01.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1040\" src=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/RV-Billing-Document-Transfer-300x296.png\" alt=\"RV Billing Document Transfer \" width=\"695\" height=\"686\" srcset=\"https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/RV-Billing-Document-Transfer-300x296.png 300w, https:\/\/www.icacourse.in\/blog\/wp-content\/uploads\/2025\/12\/RV-Billing-Document-Transfer.png 517w\" sizes=\"auto, (max-width: 695px) 100vw, 695px\" \/><\/p>\n<div class=\"block\">Image Source : saplogisticsexpert.com<\/div>\n<h2 id=\"9\">Common AR Document Types<\/h2>\n<ul>\n<li><b>AB<\/b> \u2013 General Accounting Document Used for various clearing, reversal, or year-end postings. Can appear in customer clearing if mixed with G\/L items.<\/li>\n<li><b>KG<\/b> \u2013 G\/L Account Credit Memo Not purely AR, but sometimes appears when crediting a G\/L account linked to customer items.<\/li>\n<li><b>KZ<\/b> \u2013 Vendor Payment Appears in AR when clearing customer open items that are linked to vendor items (netting\/intercompany).<\/li>\n<li><b>SA<\/b> \u2013 G\/L Account Document Standard G\/L posting (FB50). May appear in customer documents if G\/L lines are involved.<\/li>\n<li><b>SK<\/b> \u2013 Cash Journal Document Used when posting via cash journal (not common for regular AR).<\/li>\n<\/ul>\n<h2 id=\"10\">Distinction Between SAP FIORI &amp; SAP FICO<\/h2>\n<p>There are several points of differences between SAP FIORI &amp; SAP FICO that you must be well aware off. Some of the key points to remember here are as follows:-<\/p>\n<table class=\"table-responsive\">\n<tbody>\n<tr>\n<th>Aspect<\/th>\n<th>SAP FIORI<\/th>\n<th>SAP FICO<\/th>\n<\/tr>\n<tr>\n<td><b>What It Is\u00a0<\/b><\/td>\n<td>User Interface (UI) \u2013 How you interact with SAP<\/td>\n<td>Business Module \u2013 What SAP does for finance<\/td>\n<\/tr>\n<tr>\n<td><b>Category\u00a0<\/b><\/td>\n<td>Front-end \/ Design \/ Apps<\/td>\n<td>Back-end \/ Functionality \/ Processes<\/td>\n<\/tr>\n<tr>\n<td><b>Focus\u00a0<\/b><\/td>\n<td>User experience, simplicity, mobility<\/td>\n<td>Financial accounting and controlling<\/td>\n<\/tr>\n<tr>\n<td><b>Examples\u00a0<\/b><\/td>\n<td>Fiori Launchpad, apps like &#8220;My Inbox&#8221; for approvals<\/td>\n<td>Posting journals, running balance sheets, cost allocation<\/td>\n<\/tr>\n<tr>\n<td><b>Dependancy\u00a0<\/b><\/td>\n<td>Can be used with any SAP module (including FICO)<\/td>\n<td>Core SAP module; can be accessed via SAP GUI or Fiori<\/td>\n<\/tr>\n<tr>\n<td><b>Access Method\u00a0<\/b><\/td>\n<td>Through Fiori Launchpad (browser\/mobile)<\/td>\n<td>Traditionally via SAP GUI (transaction codes like FB01), but now also via Fiori apps<\/td>\n<\/tr>\n<tr>\n<td><b>Users\u00a0<\/b><\/td>\n<td>Everyone (business users, executives)<\/td>\n<td>Finance professionals<\/td>\n<\/tr>\n<tr>\n<td><b>Implementation\u00a0<\/b><\/td>\n<td>Configured via SAP Fiori apps library; needs activation<\/td>\n<td>Configured via IMG (SPRO) paths for FI\/CO settings<\/td>\n<\/tr>\n<tr>\n<td><b>Relation\u00a0<\/b><\/td>\n<td>Fiori is the &#8220;face&#8221; \u2013 it can display FICO data in a simple way<\/td>\n<td>FICO is the engine Processes the data that FIORI Shows.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"11\">How Does SAP FICO Incorporate Cost Accounting?<\/h2>\n<p>Cost accounting is not performed in FI \u2014 it is 100% handled inside the CO (Controlling) module. FI only records the financial transaction, while CO answers the questions \u201cWhere did the cost go?\u201d, \u201cWhy was it incurred?\u201d, and \u201cWhich product\/customer caused it?\u201d.<\/p>\n<h3>1. Cost Element Accounting<\/h3>\n<p>Every P&amp;L expense or revenue account in FI must have a corresponding <b>cost element<\/b> in CO.<\/p>\n<ul>\n<li>Primary cost elements = directly linked to a GL account (e.g., salary, electricity, material consumption).<\/li>\n<li>Secondary cost elements = used only inside CO for allocations (no FI posting, e.g., assessment cost elements). Without a cost element, you cannot post any cost in Controlling.<\/li>\n<\/ul>\n<h3>2. Cost Center Accounting<\/h3>\n<p>The foundation of overhead cost controlling.<\/p>\n<ul>\n<li>Costs are first posted to <b>cost centers<\/b> (e.g., Production Dept, Marketing, IT, Administration).<\/li>\n<li>You can plan costs per cost center, compare plan vs. actual, and run reports (e.g., S_ALR_87013611).<\/li>\n<li>Cost centers are organized in a hierarchy (standard hierarchy in OKKP).<\/li>\n<\/ul>\n<h3>3. Internal Orders<\/h3>\n<p>Used for short-term cost collection and monitoring.<\/p>\n<p>Examples: trade fair, marketing campaign, plant maintenance order, small investment project.<\/p>\n<p>Real orders (type 01) affect the P&amp;L and can be settled; statistical orders (type 02) are only for reporting.<\/p>\n<h3>4. Activity-Based Costing<\/h3>\n<p>Overhead costs are allocated using activity types (e.g., machine hours, setup hours, number of purchase orders).<\/p>\n<p>You define prices per activity (KP26) and the receiving object (production order, product) is charged based on confirmed quantities.<\/p>\n<h3>5. Product Cost Controlling<\/h3>\n<p>The heart of manufacturing cost accounting.<\/p>\n<ul>\n<li>Calculates <b>standard cost<\/b> of a finished product (CK11N) using BOM + routing + activity prices.<\/li>\n<li>Collects actual costs on production orders or process orders.<\/li>\n<li>Calculates variances (input price, quantity, resource usage, scrap, etc.).<\/li>\n<li>Releases standard price (CK40N) which becomes the inventory valuation price.<\/li>\n<\/ul>\n<h3>6. Material Ledger &amp; Actual Costing<\/h3>\n<p>Instead of standard costing, you can revalue inventory and cost of goods sold at actual prices every month.<\/p>\n<p>Very common in companies with volatile raw material prices (chemicals, metals, food).<\/p>\n<h3>7. Settlement &amp; Allocation<\/h3>\n<p>Costs collected on cost centers, internal orders, or production orders are moved to the final cost object:<\/p>\n<ul>\n<li>Settlement of production orders \u2192 material (increases inventory value)<\/li>\n<li>Assessment\/Distribution cycles (KSU5, KSV5) \u2192 move overhead from support cost centers to production cost centers<\/li>\n<li>Activity allocation (KB21N) \u2192 charge based on activity consumption<\/li>\n<\/ul>\n<h2 id=\"12\">KPI Accounts Receivable In SAP<\/h2>\n<p>Here are the most important and universally used Accounts Receivable KPIs in SAP environments, explained one by one with their meaning, calculation logic, typical targets, and where you can find them in the system.<\/p>\n<h3>1. Day Sales Outstanding Or Day Receivable Outstanding<\/h3>\n<p>The single most important AR KPI worldwide. It tells you on average how many days it takes to collect money from customers after a sale.<\/p>\n<p>Formula: (Average Accounts Receivable balance over the last 12 months \u00d7 365) \u00f7 Credit sales revenue in the last 12 months.<\/p>\n<p>Good target: 30\u201345 days (varies by industry \u2013 retail is often &lt;30, manufacturing 45\u201360, project business &gt;90).<\/p>\n<p>In SAP: Fiori app \u201cDays Sales Outstanding \u2013 Overdue\u201d (F2217) or classic reports FDI2\/FDI0.<\/p>\n<h3>2. Average Days Delinquent Or Average Days Past Due<\/h3>\n<p>Measures how many days, on average, customers are late beyond their payment terms.<\/p>\n<p>It shows the effectiveness of your collection team (DSO includes payment terms, ADD only measures delay).<\/p>\n<p>Good target: less than 5\u201310 days.<\/p>\n<p>In SAP: Fiori \u201cOverdue Receivables\u201d app (F2215).<\/p>\n<h3>3. Best Possible DSO<\/h3>\n<p>Theoretical minimum DSO if all customers paid exactly on the due date.<\/p>\n<p>Formula: (Current receivables that are not yet due \u00d7 365) \u00f7 Credit sales last 12 months.<\/p>\n<p>The gap between actual DSO and Best Possible DSO shows how much room for improvement exists.<\/p>\n<h3>4. Percentage Overdue Receivables<\/h3>\n<p>Total overdue amount divided by total receivables \u00d7 100.<\/p>\n<p>Good target: below 10\u201315% of total AR.<\/p>\n<p>In SAP: Same Overdue Receivables Fiori app or FBL5N with dynamic selections.<\/p>\n<h3>5. Aging Structure<\/h3>\n<ul>\n<li>Shows receivables split into time buckets: 0\u201330 days, 31\u201360 days, 61\u201390 days, 91\u2013180 days, &gt;180 days overdue.<\/li>\n<li>Healthy target: more than 80% of receivables in the 0\u201330 days bucket and less than 5% over 90 days.<\/li>\n<li>In SAP: Fiori \u201cA\/R Aging Analysis\u201d (F2216) or classic report S_ALR_87012178.<\/li>\n<\/ul>\n<h3>6. AR Turnover Ratio<\/h3>\n<ul>\n<li>How many times per year the receivables balance is collected.<\/li>\n<li>Formula: Credit sales last 12 months \u00f7 Average receivables.<\/li>\n<li>Good target: 8\u201312 times per year (higher is better).<\/li>\n<\/ul>\n<h2 id=\"13\">FAQ(Frequently Asked Questions)<\/h2>\n<h4>1. What Is The Accounts Receivable FI- AR Module In SAP?<\/h4>\n<p dir=\"auto\">Accounts Receivable (FI-AR) is a sub-module in SAP Financial Accounting (FI) that manages customer transactions, including invoicing, credit memos, incoming payments, and open item tracking. It integrates tightly with Sales and Distribution (SD) for automatic invoice posting from sales orders and with the General Ledger (GL) for real-time updates. In SAP S\/4HANA, it uses Business Partners for centralized customer master data.<\/p>\n<h4>2. How Are The Customer Master Data Created In SAP For Accounts Receivable?<\/h4>\n<p dir=\"auto\">Customer master data is created using transaction codes like BP (Business Partner in S\/4HANA), XD01, or FD01. In S\/4HANA, assign the &#8220;FI Customer&#8221; role to the Business Partner. Data includes general information (name, address), company code-specific details (reconciliation account, payment terms), and sales area data for SD integration.<\/p>\n<h4>3. How Are Customer Invoices Posted In The SAP AR Process?<\/h4>\n<p dir=\"auto\">Invoices are typically posted automatically from SD billing documents (VF01). For manual posting, use transaction FB70 (debit memo) or F-22. The posting creates open items on the customer account and updates the GL reconciliation account.<\/p>\n<h4>4. How Are The Incoming Payments Processed And Applied In SAP AR?<\/h4>\n<p dir=\"auto\">Incoming payments are posted using transaction F-28 (manual) or automated via bank statement imports\/lockbox. Payments clear open invoices through automatic or manual matching, reducing the customer&#8217;s AR balance. Partial, residual, or full clearing options are available.<\/p>\n<h4>5. What Is The Dunning Process In SAP Accounts Receivable?<\/h4>\n<p dir=\"auto\">Dunning is an automated reminder process for overdue invoices. Configure dunning procedures (transaction FBMP), assign to customers, and run dunning (F150) to generate letters\/notices at defined intervals based on overdue days and amounts. It helps manage collections efficiently.<\/p>\n<h2 id=\"14\">Final Takeway<\/h2>\n<p>Hence, these are some of the crucial aspects of Accounts Receivable Process In SAP can make things work well in your way while meeting your goals with complete ease. Ensure that you know the facts well while meeting your goals with complete ease.<\/p>\n<p>You can share your views and opinions in our comment box to meet your goals with complete ease. So, share your views on it while meeting your needs with ease.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Accounts receivable process in SAP is crucial for your financial record keeping. It helps most of the businesses to maintain their cash flow in correct order. The end-to-end AR process begins with the creation and maintenance of customer master data (general, company code, and sales area data) in transaction XD01\/FD01. Sales orders created in SD [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1042,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[68],"class_list":["post-1030","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sap","tag-accounts-receivable-process-in-sap"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/posts\/1030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/comments?post=1030"}],"version-history":[{"count":15,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/posts\/1030\/revisions"}],"predecessor-version":[{"id":1864,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/posts\/1030\/revisions\/1864"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/media\/1042"}],"wp:attachment":[{"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/media?parent=1030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/categories?post=1030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.icacourse.in\/blog\/wp-json\/wp\/v2\/tags?post=1030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}