What can you control with the reason code in Accounts Receivable? Note: There are 3 correct answers to this question.

Question

Options

• AThe exclusion of disputed residual items from credit limit checks
• BThe account where a residual item is posted
• CThe type of payment notice sent to a customer
• DThe special G/L indicator for the down payment
• EThe document type of the payment

• A
  73% (16)
• D
  9% (2)
• E
  18% (4)

Explanation

In SAP Accounts Receivable, reason codes are assigned during payment processing when a customer pays less (or more) than invoiced, creating a residual item. They carry three key controls: they can flag residual items as disputed, which tells the system to exclude those amounts from credit limit calculations (A); they can specify the G/L account where the residual difference is posted, allowing different reasons (e.g., price dispute vs. short payment) to hit different accounts (B); and they can trigger specific customer correspondence, such as a deduction notice or dispute letter, based on the code assigned (C).

Why D is wrong: The special G/L indicator for down payments is configured separately on the special G/L transaction itself - reason codes play no role in down payment processing.

Why E is wrong: The document type of a payment posting is determined by the payment method and posting key configuration, not by the reason code.

Memory tip: Think of reason codes as answering three questions when a customer underpays - Where does the difference go? (account), Is this disputed? (credit limit exclusion), and What do we tell the customer? (notice type). If it doesn't involve the residual item or customer communication, reason codes aren't involved.

No community discussion yet for this question.