Why is my asset replacement / warranty / OS upgrade not showing up in the IT budget?

Why is my asset replacement / warranty / OS upgrade not showing up in the IT budget?

There are many possible reasons why an asset action would not show up in the IT Budget. Here's a list of the general rules used to determine if an action makes it to the budget.
Remember: every Company's Asset Category is customizable. The values from one company are not necessarily the values in another company since the account's Asset Category templates get copied over when you first access a company.

Budget Actions Early

All three main policies have the ability to be budgeted early by a certain number of months. For example, if the Asset's End of Life date is set to July 1st and the budget early setting is set to 4 months, then the replacement action will be budgeted on March 1st. This only affects the budgeted actions, not the Asset's expiration itself, but it may cause the action to change quarter, or even year.

Warranty Renewal

Warranty Renewal actions are only considered if:
  1. The Asset's (calculated or manually set) End of Life is in the future
  2. The Asset's current Warranty Expiration Date is set
  3. The applicable Warranty Coverage Policy is either "Until End of Life" or "For X Years".
  4. If the applicable Warranty Coverage Policy is set to "For X years", the Asset's Purchase Date is set
  5. The time between the current Warranty Expiration Date and the Asset's End of Life respects the Asset Category's "Renew warranty only if more than ___  months until asset end of life" setting
  6. The Asset is not a Virtual Asset
The dates on which the Warranty Renewal actions are scheduled in the budget are affected by the "budgeting buffer" setting set in the Asset Category's settings. For example, if you set renewal to be budget 3 months in advance, then the date will the Warranty Expiration date minus 3 months.
Note: This may cause the action to appear in (overdue) actions if the warranty is set to expire in less than the number of month set.
The renewal amount will be calculated based on the number of years to buy and the yearly renewal amount set. For example, if we can buy 3 years of warranty at a yearly annual cost of $150, then $450 will be budgeted every 3 years until the Asset's End of Life is reached. The last renewal could very well be for only 1 or 2 years though.

OS Upgrade

OS Upgrade actions are only considered if:
  1. The Asset's (calculated or manually set) End of Life is in the future
  2. The Asset's current OS End of Life Date is set
  3. The applicable "OS End of Life Policy" is "In-place Upgrade"
  4. The time between the OS End of Life Date and the Asset's End of Life respects  the Asset Category's "Upgrade OS only if more than ___ months until asset end of life" setting

End of Life

Asset's End of Life replacement are only considered if:
  1. The applicable "End of Life Policy" is "Replace"
The End of Life date is affected by multiple factors:
  1. The Asset's Purchase Date + the defined Lifespan gives the calculated End of Life of the Asset.
  2. If the "OS End Of Life Policy" is set to "Force End of Life", than the Asset's End of Life will be the earliest date between the calculated End of Life and the OS End of Life date.
  3. If the "OS End Of Life Policy" has option "Force End of Life for Others" checked and the difference between Asset's calculated End of Life and the OS End of Life is smaller than the specified buffer, the End of Life asset will be set the OS End of Life date.
Note: This may cause the date to be in the past and the budget actions to appear in the (overdue) section.

    • Related Articles

    • How to Structure your Asset Categories?

      A Budget is not a Quote One of Propel Your MSP's goals is to create a precise budget for the next 3 or 5 years. But a budget is not a detailed quote, nor should it be. It's a tool to help MSPs have a productive discussion with their client about the ...

    • How to Manage License Renewals in the QBR Budget?

      This article covers how to manage licences or vendor contracts (e.g. Cisco Support Contract, Microsoft Subscription, etc.) in Propel Your MSP. Two options are available depending on the way that the licenses are stored in your PSA. License Stored as ...

    • Automatic OS End of Life Date Detection

      When importing Assets from your PSA, Propel Your MSP can automatically detect and set the OS End of Life date if imported fields are properly formatted as a recognized OS. The PSA Fields that play a role are: OS Type OS Info For example, the ...

    • Getting Started - Asset Lifecycle - A Quick Tour

      Asset Lifecycle Management Data Origin Propel Your MSP retrieves Assets and Agreements data by importing them from your ConnectWise Manage instance. It also queries some of the major manufacturer`s APIs to fetch Warranty Expiration date and Purchase ...

    • FAQ - Warranty Lookup

      Manufacturer vs Serial Number To know which manufacturer's API to query, Propel Your MSP relies on the following information: Asset's Manufacturer Asset's Serial Number Asset's Model Number Asset's Tag Number In cases where the Manufacturer is blank, ...