Financial Contract Accounting — Lesson 3: Payments, Payment Lots, Returns, Dunning, Collections, and Installment Plans

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing payments and payment lots.
• Perform and validate returns, dunning, and collections using reviewable system evidence.
• Evaluate the condition where open items remain uncleared because payment references, clearing priorities, and account relationships are inconsistent and select proportionate corrective action.

Detailed Topics

• Payments applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Payment Lots applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Returns applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Dunning applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Collections applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Installment Plans applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a high-volume finance operation managing contract-based receivables and payments across millions of customer items. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the FI-CA posting, clearing, collections, and close control dossier. It also tests the exception where open items remain uncleared because payment references, clearing priorities, and account relationships are inconsistent.

Hands-On Exercise

Complete a controlled SAP exercise covering Payments, Payment Lots, Returns, Dunning, Collections, and Installment Plans and preserve the verified result in the FI-CA posting, clearing, collections, and close control dossier.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences payments and payment lots.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the FI-CA posting, clearing, collections, and close control dossier should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “open items remain uncleared because payment references, clearing priorities, and account relationships are inconsistent” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The FI-CA posting, clearing, collections, and close control dossier connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Payments, Payment Lots, Returns, Dunning, Collections, and Installment Plans, explain the resulting SAP behavior, and defend the outcome through the FI-CA posting, clearing, collections, and close control dossier.