In SAP Financial Accounting automatic payment program, which of the following statements about payment runs are true?

Introduction / Context:
The automatic payment program in SAP helps organizations process large volumes of incoming or outgoing payments efficiently. Understanding how the payment proposal, exception list, and payment methods work is essential for correctly configuring and using the payment run. This question asks which statements about payment runs are true, focusing on the flexibility of the proposal, the role of the exception list, and the requirement that payment methods be allowed in master records.

Given Data / Assumptions:

- The organization uses the automatic payment program to pay vendors and possibly customers. - The payment program generates a payment proposal before the actual payment run. - The proposal includes an exception list showing items that could not be included. - Payment methods must be set up in both Customizing and the master records in order to be used.

Concept / Approach:
The automatic payment program follows a structured process. First, it selects open items based on parameters and generates a proposal. Users can review and adjust this proposal, for example by blocking certain items or changing payment methods. The exception list highlights items that were not selected and explains why. Only after the proposal is accepted does the system create actual payment documents and possibly payment media. Payment methods used in the run must be allowed in vendor or customer master records to ensure that the chosen method is valid for that business partner.

Step-by-Step Solution:
Step 1: Consider the statement about the payment proposal. SAP allows users to edit, delete, and recreate the proposal until they are satisfied, so this statement is true. Step 2: Evaluate the statement about the exception list. The exception list is produced as part of the proposal and lists open items that could not be included in the payment run, making this statement true. Step 3: Review the statement about payment methods. For an automatic payment run, a payment method must be allowed in both the payment program parameters and the vendor or customer master record, so the statement that a payment method must be entered in the account master record to be used is true. Step 4: Since all three individual statements are correct, the option that states all of them are correct must be the right answer. Step 5: Select option d, which confirms that all listed statements are true.

Verification / Alternative check:
In SAP, if you generate a payment proposal, you can return to the proposal, modify it, or delete it and run the selection again. When reviewing the proposal, you see an exception list that explains why certain items were not picked, such as blocked accounts or missing payment methods. If a vendor doesn't have the payment method allowed in the master record, the system will not select that vendor for that method, proving that the statement about master record settings is also correct.

Why Other Options Are Wrong:
Options a, b, and c each include only one part of the picture and ignore the others. While each of these is correct by itself, the question asks which statements about payment runs are true overall. Only option d acknowledges that all of the described behaviours occur in the SAP automatic payment program. There is no statement suggesting any of a, b, or c is false, so rejecting option d would not fit the actual system behaviour.

Common Pitfalls:
A common pitfall is forgetting to review the exception list, which can lead to unanswered questions about why some invoices were not paid. Another mistake is running payments without carefully checking or adjusting the proposal, potentially causing incorrect payments. Users also sometimes misunderstand the relationship between payment methods in configuration and master data, leading to missing or incorrect methods on vendor or customer accounts. Knowing that the proposal is editable, that the exception list is part of the proposal, and that payment methods must be allowed in master records helps avoid these issues.

Final Answer:
All three statements accurately describe how the automatic payment program works in SAP. Therefore, the correct option is All of the above statements about the payment run behaviour are correct.