User Tools

Site Tools


accrual_process

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
accrual_process [2024/08/20 19:46] tina.roblesaccrual_process [2024/08/20 19:55] (current) tina.robles
Line 183: Line 183:
  
 Our standard reporting source has those terminated contract’s accruals available, but a given client could filter it out of their totals if they desired. Our standard reporting source has those terminated contract’s accruals available, but a given client could filter it out of their totals if they desired.
 +-----
  
 **__NEW ACCRUAL PROCESS__** **__NEW ACCRUAL PROCESS__**
Line 211: Line 212:
  
 (**ability to perform these actions is limited to users with access to these setting only**) (**ability to perform these actions is limited to users with access to these setting only**)
 +
 +-----
  
  
Line 259: Line 262:
  
 **NONE** – This would not accrue any value for any lumpsum event on the contract.   **NONE** – This would not accrue any value for any lumpsum event on the contract.  
 +
 +-----
  
  
Line 275: Line 280:
  
 {{:pasted:20240820-183310.png}} {{:pasted:20240820-183310.png}}
 +
 +-----
  
  
Line 304: Line 311:
  
 The order in which the above are selected drives the order in which we look for the data to use.   If you chose SALE, LIST and COMPANY – we would first look for a sale value for the time frame, product and customer.  If none could be found, we would then look for a LIST value for that item and time frame.   If none could be found, we would look for a COMPANY value for that item and time frame. The order in which the above are selected drives the order in which we look for the data to use.   If you chose SALE, LIST and COMPANY – we would first look for a sale value for the time frame, product and customer.  If none could be found, we would then look for a LIST value for that item and time frame.   If none could be found, we would look for a COMPANY value for that item and time frame.
 +
 +-----
  
  
Line 317: Line 326:
  
 **1069_accrual_sale** is a supplemental file that the client can use to validate the values in the detail file where a sales invoice was the source used to generate the accrual amount.   **1069_accrual_sale** is a supplemental file that the client can use to validate the values in the detail file where a sales invoice was the source used to generate the accrual amount.  
 +
 +-----
  
 **REPORTING IN TABLEAU** **REPORTING IN TABLEAU**
Line 558: Line 569:
  
 Lumpsum Actuals - always match the claim actuals paid against the contract lumpsum.  Lumpsum Actuals - always match the claim actuals paid against the contract lumpsum. 
 +
 +-----
  
  
Line 565: Line 578:
 If we create claims for these contracts automatically, they will be included in the actuals as they are claims that were created in TPM.  If we create claims for these contracts automatically, they will be included in the actuals as they are claims that were created in TPM. 
  
 +-----
  
-**__WHY WOULD ACCRUALS BE A DIFFERENT VALUE THAN THE ACTUALS__**+ 
 +**__WHY WOULD ACCRUALS BE A DIFFERENT VALUE THAN THE ACTUALS?__**
  
  
Line 572: Line 587:
  
 If you are accruing based off sales data a customer may not submit rebates against all the volume purchased.  This will cause a difference also.   If you are accruing based off sales data a customer may not submit rebates against all the volume purchased.  This will cause a difference also.  
 +
 +-----
  
  
Line 580: Line 597:
  
 When you setup a contract both at sku level and lump for the same spend make sure both are not setup to accrue or you will overstate your accruals. When you setup a contract both at sku level and lump for the same spend make sure both are not setup to accrue or you will overstate your accruals.
 +
 +-----
  
  
accrual_process.1724183195.txt.gz · Last modified: 2024/08/20 19:46 by tina.robles