Description
To support the ability to include new Standard Rate Sets or updated Pay Rate and or Bill Rate valuesin an import file and or provide all timesheet iterations in one file, new validations have been added to timesheet import as follows:
Condition | Error Message | Comments |
A timesheet includes an additional item for which a pay rate cannot be specified (non-direct valuation) on the timesheet but a pay rate has been specified. This now only relates to Agreement Rate Jobs, as for Standard Rate Jobs a new pay rate can be added. | Additional item rate cannot be supplied. | The condition has been updated as this item will now only apply to timesheets for Agreement Rate Jobs. |
A manual item is not available in the Job Order for the import date supplied. This is now only applicable to Agreement Rate jobs. | Manual Item not available for this timesheet date. | This is now only applicable to timesheets for Agreement Rate Jobs as new Rate Sets can be updated within the timesheet import, as such the logic will not reject timesheets where a items are not in the job’s rates. |
For a Standard Rate Job, a new Pay Code/Import Code has been provided, however the related Bill Code/Import Code has not been supplied OR A new Pay / Import Code and Bill /Import code has been provided in the import, however the corresponding Pay / Bill Rate has NOT been provided. OR The new Pay and Bill code provided are not linked ie; Bill Code does not have the Pay Code provided, linked in the Bill Code Maintenance. | New Pay Code must include the corresponding Bill Code and the Pay and Bill rate values. | This is a new validation message to support where a user wishes to import a new Standard Rate set along with the import item. The right fields must be mapped and values provided to trigger the insertion of the rate set into the related job’s standard rates. Please be aware that where you wish to include a new Reimbursement item, the values required are:
|
Pay Code IS in the Job’s Standard Rates, and new Pay / Bill Rates have been provided, however they have provided a Bill/Import Code that is not linked to the Pay Code. | The Pay Code must be linked to the Bill Code provided and Flat Rate Bill Type must be available to the Job’s Country. | Where a new Rate Set is being imported, the system checks to see that the Pay Code provided is linked to the Bill Code provided. To support providing new Rate Sets with the import file, your system must be configured in Maintenance > Hierarchy > Country to support Standard Rate Bill Type of ‘Flat’. |
Target Timesheet is the system generated zero result timesheet and the first adjustment timesheet defined in the import file group is a negative timesheet. We cannot support this, first adjustment timesheet where the target is the zero result timesheet, must be positive. | Target Timesheet is original zero result timesheet. First Adjustment Timesheet must be positive | Where the ‘Debit / Credit’ timesheet strategy is being used to import Standard Rates, into a job flagged as ‘Adjustment Only’, the data first timesheet for the week ending date must be positive values as this will be the original timesheet for that week. |
Grouping value has been provided however data cannot be grouped as unable to sequence the values provided ie unable to group the data using the values provided. This could include where Grouping is only applied to some of the rows for the same week ending date. Must be applied to all rows to sequence. | Grouping values provided can’t be sequenced OR grouping values have not been provided for all rows with the same week ending date for the same job. | Where multiple iterations of a timesheet (same job same week ending date) are being imported, the grouping value must be assigned to all rows for that week ending date so the system can determine each iteration of the timesheet and the order. |
Benefits
These new validations support Agencies importing timesheet data from a third party VMS system by:
Removing the need to add new Standard Rates to the Job Order directly.
Providing the ability to Import multiple iterations of a timesheet for the same job and week ending date in one file, removing the need to have separate imports for each iteration of the timesheet.
Configuration
There is no configuration required.