At this time within the SPH file the end date is not operational. Meaning that unless you add a new effective date entry for the same *Role ID> Resource> Project Contract ID> Pricing* the rate does not end ever. The end date within the SPH table is not functional. What we would expect is for the end date to trigger a return to a "standard rate" that is input into the SPH table each year. This trigger prevents our rates from rolling over multiple years. If a client goes from a non-standard rate to a standard rate, with the inoperable end date, it necessitates that each resource has a new entry in the SPH file for the life of the project. If there is a prevailing reason that the end date is not operational I would greatly appreciate an explanation. If it is possible to reconsider the effectiveness of the end date we would greatly appreciate that functionality to be updated.