Accounts Receivable
Accounts Receivable (AR) in SAP FI covers the management of customer accounts, invoices, payments, credit exposure, and dunning as a sub-ledger fully integrated with the General Ledger. This topic progresses from business purpose and master data through configuration, posting logic, integration with Sales and Distribution and Treasury, reconciliation and dispute handling, and the changes introduced by S/4HANA's Universal Journal and cloud deployment models.
Overview
Accounts Receivable (AR) in SAP FI covers the management of customer accounts, invoices, payments, credit exposure, and dunning as a sub-ledger fully integrated with the General Ledger. This topic progresses from business purpose and master data through configuration, posting logic, integration with Sales and Distribution and Treasury, reconciliation and dispute handling, and the changes introduced by S/4HANA's Universal Journal and cloud deployment models.
Lessons in this topic
- Incoming Payment Processing and Automatic Clearing in Accounts ReceivableExplains how incoming customer payments are recorded, matched, and cleared against open items, covering manual clearing, the automatic payment/clearing program, bank statement integration, and the accounting postings generated at each step.
- Dunning, Credit Management Integration, and Dispute Handling in Accounts ReceivableCovers the design and operational mechanics of the dunning process, integration between AR and Credit Management for exposure control, and structured dispute case handling, including troubleshooting common production issues in these interconnected processes.
- Accounts Receivable Purpose, Organizational Structure and Customer Master DataUnderstand 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.
- Architecting Accounts Receivable Across S/4HANA Deployments: Universal Journal, Cloud Constraints, and Migration GovernanceAn 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 implications, extensibility governance, migration risk, and long-term operating model trade-offs.
- Configuring Posting Keys, Terms of Payment and the Customer Invoice Document FlowLearn 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.
Interview questions covered
- Walk through how a customer bill of exchange receivable is posted using a Special GL indicator, and how this integrates with bank accounting when the bill is later discounted or collected through the house bank.
- Walk through how a customer bill of exchange receivable is posted using a Special GL indicator in AR, and explain how it integrates with bank accounting when the bill is later discounted or collected through the house bank.
- What standard reports or tools would you use to review a customer's dunning history and current dunning level, and how does an SD-driven credit or delivery block interact with the dunning process for that customer?
- What standard reports or tools would you use to analyze a customer's dunning history and current dunning levels, and how does an SD-driven credit or delivery block interact with the dunning process for that customer?
- A customer makes a partial payment covering only part of one large overdue invoice, leaving the remaining balance open. During the next dunning run, the customer receives a dunning notice showing the full original invoice amount rather than the reduced open balance. How would you troubleshoot this?
- What standard SAP reports or tools would you use to build a portfolio-level dunning KPI view (e.g., dunning level distribution, total dunned amount by customer segment) across a large customer base, and how would you incorporate the SD credit/delivery block status into this reporting?
- In SAP Business Partner architecture, how is a customer master created and what is the relationship between the Business Partner, Customer, and the underlying roles required for Order-to-Cash processing?
- In an Order-to-Cash scenario, a customer underpays an invoice due to a pricing dispute and AR posts this using residual payment. Explain how the residual open item's tax treatment integrates with the original SD billing document's tax code, and what happens when SD later issues a credit memo to resolve the dispute, from a tax reconciliation perspective.
- In S/4HANA, how is a customer created using the Business Partner (BP) model for Order-to-Cash, and how does the relationship between BP, Customer role, and the resulting general/company code/sales area data differ from the classic customer master approach used in ECC?
- A customer partially pays an overdue invoice, but the dunning run still sends a dunning letter for the full original invoice amount rather than the remaining open balance. How would you troubleshoot this?
- A customer down payment is posted using Special GL indicator F (request) then A (received), and later applied against the final invoice via F-39/clearing. The special GL account clears correctly in FI, but the corresponding house bank sub-account never shows the offsetting bank statement clearing, leaving an open item in the bank clearing account. How would you troubleshoot this integration issue?
- What configuration approach would you use to govern changes to customer master fields (such as reconciliation account, payment terms, and dunning procedure) that directly impact the AR closing process, and how do sensitive-field controls, change document tracking, and mass-maintenance tools fit together?
- In S/4HANA, when a Customer is created using the Business Partner model to support Order-to-Cash, what is the relationship between the Business Partner, the Customer role, and the resulting general data, company code data, and sales area data, and which company code segment fields most directly drive AR accounting behavior?
- A customer makes a partial payment against an overdue invoice using incoming payment posting, creating a new residual open item for the unpaid balance. However, the next dunning run entirely skips this customer's invoice from the dunning proposal even though the residual balance is clearly overdue. How would you troubleshoot this?
- Your organization operates centralized collections across multiple company codes, and customers frequently take unauthorized cash discounts on tax-relevant invoices when paying via lockbox. Standard incoming payment postings via cash discount clearing are creating small tax discrepancies between the original invoice tax amount and the discounted payment tax base, and this is surfacing in tax reconciliation reports at quarter-end. As the architect, how would you design a solution to handle this at scale?
- A customer pays an invoice slightly short of the full amount due to a disputed shipping charge, and this is posted using residual payment. Explain how the residual open item is created, how the tax originally posted on the invoice is treated, and what downstream tax reporting implications this raises.
- A customer pays an invoice short by a small amount citing a tax dispute, and you post this using residual payment. Explain how the residual item is created, how tax is handled, and what downstream reporting/tax implications arise.
- Walk through the end-to-end process of posting a customer security deposit or bank guarantee using a Special GL indicator against an outstanding invoice, and explain how its later release or forfeiture integrates with bank accounting when the guarantee funds are held at the house bank.
- A customer makes a partial payment against a single large overdue invoice using incoming payment processing (not residual), leaving the balance open on the same invoice line item. During the next dunning run, the collections team notices the dunning notice still shows the original full invoice amount instead of the reduced open balance, and the customer disputes the notice. As the FI consultant supporting collections, how would you investigate and correct this?
- What standard reports or tools would you use to review open customer disputes and confirm whether disputed invoices are correctly excluded from the dunning proposal, and how do these dispute cases interact with the dunning block on the affected line items?