Valuation Run for Promise to Pay
Application component: Contract Accounts Receivable and Payable
App type: SAP GUI
Description:  Valuation of the promise to pay determines the level of fulfillment of the promise as a percentage between 0.00% and 100.00%. The system derives a status based on this level of fulfillment and your system settings. 
Key features:  Valuation takes place once the promise to pay is closed, normally a few days after the last partial payment is due. Valuation can lead to one of the following statuses: Promise Fulfilled Promise Fulfilled with Accepted Variances Promise Not Fulfilled  Using the valuation data determined, the system decides whether the valuation is saved and the promise to pay closed or whether there should be a further check at a later date. Upon creation of a promise to pay, the system automatically sets the first check date. The date is specified via event 0184. In the standard version, a date is set that is seven days after the due date of the middle installment. Example In the case of five installments, a check is scheduled seven days after the due date of the third installment. If there is an even number of installments, the system uses the earlier of the two middle installments. During the check, the decision must be taken whether a further check is necessary at a later date, and the promise is open until then, or whether the promise is to be closed in its current status. This decision is taken in event 0189. In the standard version, a new check date is set if the old check date was not after the due date of the last installment; otherwise, the promise is closed. In the standard version, the new check date is seven days after the due date of the last installment. If the date determined in this way is not in the future, the promise to pay is also closed. Logic for the Valuation In the valuation, the following is considered: How much of the promised amount has actually been paid, and how late were the payments. With regard to the delay in payment, in Customizing, you can define a number of tolerance days and what reduction in the valuation is made for each day in excess of these tolerance days. You define this for each company code. Example In Customizing, you have agreed 2 tolerance days and 1.0% reduction for each further day late. The following promise to pay has been given:100.00 on 3/1/2023 100.00 EUR on 4/1/2023 The following payments have been made:80.00 EUR on 3/8/2023 100.00 EUR on 4/9/2023 The system always assigns payments to the earliest due dates. Therefore, after the deduction of two tolerance days, the assignments are as follows:Amount Delay EUR 80.00 5 days, payment from 3/8/2023 EUR 20.00 37 days, payment from 4/9/2023 EUR 80.00 6 days, payment from 4/9/2023 Each of these assignments contributes to the level of fulfillment that is calculated from the percentage amount portion and the reduction due to the delay:Amount Portion Reduction factor Contrib. to level of fulfillment 40.00% (80/200) 0.95 (5 days) 38.00% 10.00% (20/200) 0.63 (37 days) 6.30% 40.00% (80/200) 0.94 (6 days) 37.60%  Total 81.90%  If items that were included in a promise to pay are cleared in another way (for example, due to a reversal, transfer, clearing of credit memos), the business partner only has to pay a reduced amount to fulfill the promise to pay. In the valuation, these other clearings are used to reduce the oldest due dates of the promise to pay. A valuation is then made as described above using the reduced installments. Example The following promise to pay has been given:100.00 on 3/1/2023 100.00 EUR on 4/1/2023 100.00 EUR on 5/1/2023 Of the receivables due, 120.00 is reversed. In the valuation, the promise to pay is treated as if the following installments had been agreed:80.00 EUR on 4/1/2023 100.00 EUR on 5/1/2023  Write-offs are not other clearings, since they are not deemed to be a waiver of the receivable; instead, they reflect the opinion that the receivable will probably not be collected. Valuation and Creditworthiness For promises to pay that are not fulfilled, an entry can be made to the creditworthiness of the business partner. In the standard version, the system checks whether a creditworthiness weighting is specified in Customizing in case of non-fulfillment. You can specify the creditworthiness rating for each category of promises to pay. If a creditworthiness weighting is specified, a new creditworthiness record is created with this value and the total creditworthiness of the business partner is reduced. Using event 0188, you can change the creditworthiness weighting determined in the standard system. Subsequent Changes to Valuation As soon as a promise to pay is closed, all further payments, withdrawals, or other clearings no longer influence the valuation. Therefore, a promise to pay should not be closed too soon after the last due date; on the other hand, it must be possible to make an adjustment for promises to pay where the valuation is later determined to be incorrect. In particular, this should prevent a business partner receiving a bad creditworthiness where this is not justified. With a special authorization, you can subsequently change the level of fulfillment and the status of a promise to pay manually. You have to justify the change with a comment. All subsequent changes are recorded. The creditworthiness is adjusted automatically. 
Business roles: Administrator - Accounts Payable and Receivable (FI-CA)| Accounts Payable and Receivable Accountant (FI-CA)
Administrator - Accounts Payable and Receivable (FI-CA): (is an add-on role to the Administrator)
Is responsible for the planning, scheduling and execution of jobs and mass activities within FI-CA, including critical Business processes, such as payment run, payment lot, dunning run. 

Accounts Payable and Receivable Accountant (FI-CA) : 
Deals with payment and credit clarification of B2B and B2C customers and works off complex customer requests according account clarification.