Projects - Set date for change of charge rate
Staff members gets pay reviews each year, which means their cost change. But we are unable to get the change to commence from a certain date so reporting for prior year projects won't be accurate. any way we can put a change commencement date so reporting is more accurate?
-
Leanne Restante commented
I'm surprised that this feature isn't available. This defeats the point of having projects within Xero. I'm sure this is a very easy fix as all other systems have this programmed into their systems.
There are a few issues like this within Xero - and therefore, if not improved I will need to move us away from using this system.
-
Heide Baer commented
Thanks for supporting this idea Anna - I think a new project doesn't even fix the problem: because the charge rates are practice-wide. I've been thinking the way around is to publish the profitability reports over the date range of the current rates, then update for new rates. You just have to remember that actual costs of older projects should be viewed in published reports, and can't be viewed live or on a new/modified report. (Which is less than ideal!)
-
Anna Gillings commented
Massively important please - its essential if you want to understand the true cost of a project where rates have changed. If there is a workaround - other than a new project every time the rate changes (which is an admin nightmare) please do let us know! Thanks
-
Emma Rosenblatt (Accounts) commented
This is such an important feature that needs to be added to projects. We have just realised ourselves that all previous reporting is not even a close representation to what actually happened because of this issue.
Please fix this!
-
Heide Baer commented
I agree - this would be an important feature.
My alternative suggestion, if effective dates cannot be associated with cost rates, would be to be able to adjust/set staff cost rates by Project - or right in the Task (eg, list of staff with access and default cost rates showing, with the ability to customize).
FYI I have a client that needs this right now, but if it ever does make it into the pipes for development, I'd appreciate a notification :)