The Agreement Additions table lets you view all of the addition lines on agreements for all of your clients or an individual client. The table also allows overrides for previous values of product cost or product price on a line to line basis.

The program filters on:

1. A specific month the addition was in use on the agreement  
2. Selection can be for one company or all companies
3. On a particular SKU or if blank, all SKUs
4. Just look at additions in certain Agreement Type(s), or if blank all Agreement Types are selected.

For any changes to take effect, click on the Filter button.

Each line of the table can be edited by clicking on the pencil image at the beginning of the line. All of the addition lines displayed can be edited by clicking on the square to the right of the pencil on the first (header) line and then clicking on the pencil image.

Information provided for each addition line

Each addition line in the table represents one line of information from your PSA data that is used to create an invoice.  There are also four fields in the line (highlighted in yellow below) that are set in MSPCFO to override an incorrect or missing  value from your PSA. MSPCFO does not change any data in your PSA, but when MSPCFO sees the Client/Agreement/Addition line that is unique, the program will correct a cost that may be inaccurate.  MSPCFO never corrects revenue, quantity, cycles ---- only costs. The fields that are captured are (override fields are in yellow):

1. Invoice Date
2. Client Name
3. Agreement Name
4. Product SKU
5. Product Category
6. Product Subcategory
7. Less Included
8. Quantity - Unit Quantity minus the less included
9. Unit Cost
10. Unit Price
11. Product Unit Value(Is this used?)
12. Override Product Cost
13. Override Product Price
14. Billing Cycle frequency
15. Override Start Date
16. Override End Date
17. COGS Margin for this addition (Unit Cost/Unit Price)
18. Forced Margin
19. Exclude From Health Check

Overrides

The table can be used to correct/update historical values that are missing from the PSA information. These values could be missing (zero value) or incorrect. The fields that can be updated:

1. Override Product Cost - Replacement cost for addition line historically.

2. Override Product Price - Unit product price for the addition line historically. (Note: Not a price override, but just the portion that will be revenue for product. The remainder of the price will go to labor).

3. Override Start Date - If the override is not needed from the beginning of the addition line, this start date will be the first date (month portion) that the override is used.

4. Override End Date - The last month that the override will be used. After the ending month, the new corrected values from your PSA will be used.

5. Forced Margin - Forcing labor into an addition line where the cost/price is greater than the COGS % cut off.  A % is used as a margin for the product and then the remainder of the revenue goes to labor.  This feature is useful when the revenue and price vary on a product per month. The margin stays constant for the product and the remainder of the revenue goes to labor.

Example:
Min COGS % = 35%
Cost per unit = $100
Price of unit = $150
Forced Margin = 15%  (entered as .15)
The Forced Margin adds a 15% margin to the cost of $100 = $117.65.
The remainder of the revenue per unit is allocated to labor ($32.35)

6. Exclude From Health Check - Any addition in a product-only (L&S) agreement is assumed to be a product with a cost. There is no labor revenue attributed to this type of agreement, therefore everything is product. In a small percentage of products, there may be no cost (ex.: product has been completely written off). Setting this line to "Yes" will stop the line item from showing in the Health Check/Agreeements/License and Subscription agreements with high margins.

An example of a cost override:

For Client 22271/Agreement 296/Product 121785, the cost of the product is missing in the PSA. Once recognized, the MSP will make the change to the cost in the PSA. This change in the PSA will only take effect for invoices going forward. An override in MSPCFO in the Agreement Additions table will correct the costs historically going back for all months it was used.

To override this value in MSPCFO, the following steps should be taken:
Click on the pencil to open up the override screen - Edit Agreement Addition.

In the Edit Agreement Addition screen, the cost of the product should have been $100 but was never added. An override price of $100 is added along with an Override End Date which means the MSP should put the correct cost in the PSA by the month in the Override End Date. MSPCFO will then go back and use the correct date from the PSA. It is best practices to correct the PSA with the cost as soon as possible. The override can overlap the good data for a while since both values should be the same.

The Override Price allows a certain part (or all) of the revenue to be product. The main reason this override is used is for products with very low costs that do not meet the standard rules to be product and not revert to mostly labor. Speak to your CSR for more details on overriding the product price.

If Override Start Date is not used, the override will take effect for all of the months the addition line has been in place. If used, you can limit the time span the override is used historically to be a shorter period of time.

Once you save, you will see the values in the addition line.