Re: Using RangerMSP for tracking AYCE MSP Contracts
Hi ascendnet,
I believe the options which already exist in the application were covered along this thread. This doesn't completely cover the specific scenario you have described (in regards of the MSP contract with specific labor and parts items not being covered), and this is something we have noted for us to check how we can cover this kind of use case. A fully customizable contract (which lets you define how each item behaves) is something which is on our radar for a while now, and has been mentioned in the past.
At the moment, you may consider tracking items which are usually not supposed to be covered by your MSP contracts, using Charge reports. You can filter the report by the item, and by the billable flag, and see whether you have non-billable charges with this item which were logged this way by mistake (i.e. should be "billable"). This is not a fully automated solution, but should help you make sure you don't miss on any billable items.
I hope this helps.
Ethan
Hi ascendnet,
I believe the options which already exist in the application were covered along this thread. This doesn't completely cover the specific scenario you have described (in regards of the MSP contract with specific labor and parts items not being covered), and this is something we have noted for us to check how we can cover this kind of use case. A fully customizable contract (which lets you define how each item behaves) is something which is on our radar for a while now, and has been mentioned in the past.
At the moment, you may consider tracking items which are usually not supposed to be covered by your MSP contracts, using Charge reports. You can filter the report by the item, and by the billable flag, and see whether you have non-billable charges with this item which were logged this way by mistake (i.e. should be "billable"). This is not a fully automated solution, but should help you make sure you don't miss on any billable items.
I hope this helps.
Ethan
Comment