cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Why add condition REA1 Rebate Accruals from Sales Condition Contract into an SD Order/Invoice

david_evans_gsk
Explorer
0 Likes
476

I've started in Condition Contract Management.  I believe I understand the delta accruals and settlement process.  I've created a condition contract with REA1 (Rebate Accrual) condition set to 5% and RES1 (Rebate) condition set to 5%.

In my hypothetical example I have $100 a month in sales, and my condition contract runs for a year from Jan to Dec.  I started the Condition Contract in March, so there was a delta accrual for the $200 sales that had already been in Jan and Feb is done (5% of the 2 months is $10).  I post a new sales invoice in March for $100 and can see business volume.

My question is, I've seen some clients put the REA1 condition in the billing document pricing proc as a statistical condition.  So in March there's a 5% rebate sitting the invoice (business volume).  I can see some sense if you are testing and want to see how much of a rebate/accrual you have (and if there are others hitting the sales invoice).  But this will impact performance.  Would there be other reasons (eg you don't run a delta accrual every month - but instead have the sales invoice document post to accruals)?  Also why set it up this way, if you have scales, or realise you have made a mistake in the rebate % half way through the year - then you will have to do more work to correct (or you would not have the scales working properly) - whereas the delta accrual process is better?

 

Accepted Solutions (0)

Answers (0)