...
This strategy may be frustrating where data for Standard Rates is being imported from a VMS system and adjustment data will only ever include the adjustment transactions. For example original timesheet had 8 Ordinary, plus a Reimbursement, and the hours should have been 7, so the data supplied for the adjustment is to either fully negate the 8 Ordinary to -8, and a subsequent adjustment has Ordinary of 7 hrs OR the adjustment is just for -1 Ordinary, and in both cases no item is would be supplied for Reimbursement, as that item is unchanged.
No Credit Interpret (NCI)
In this release we have provided the ability for Timesheet Import, where the Job is for Standard Rates to flag the import as to avoid the credit process during interpretation (the process whereby the interpreter offsets the target timesheet values from the adjustment timesheet). This new functionality can only be applied to Imported Timesheets for a Standard Rate Job, and will be triggered via a new setting in the timesheet import process called ‘No Credit Interpret’. Where true, this setting is true, the interpreter will not compare the adjustment timesheet to the target and the data is represented as per the items importedwill ensure the data imported will be represented ‘as is’ in interpreted adjustment timesheets.
To support this requirement, the following changes have been made:
In Time & Attendance > Timesheet Import > Import Settings we have added a new checkbox labelled 'No Credit Interpret.
By default this will not be ticked.
If you save a template, then this item will be stored with the template (if ticked or unticked) so you can manage the setting with your templates.
...
.
Where ‘No Credit Interpret’ has been ticked, slight changes have been made to import validations as follows:
The existing validation to ensure that the first (original) timesheet for a weekending date must have positive values, will not be triggered.
The logic will check the timesheets job, and if the job has Agreement Rates assigned, the data for that job will be excepted as this process is not supported for Agreement Rate jobs. In the Exception Report an error will display 'Agreement Rate data is not supported for No Credit Interpretation.'
All other existing validations will apply.
...
In Interpreter Review, where ‘No Credit Interpret’ has been stored against the imported interpreted timesheet, the :
The logic to credit the target timesheet’s transactions will not be run. As such the results will be what was imported, which will include positive and negative values (if using a negative
...
values in import to adjust quantity and or
...
reimbursements). As such in the Primary Interpretation Details Tab, you will not see any offset transactions.
In the Interpreted Timesheet Details Tab, ‘No Credit Interpret’ is displayed so users will be aware that this setting has been applied to the imported timesheet’s data.
...
Important Considerations
Grouping is still required if you wish to import more than one iteration of a timesheet in one file, for example Original and Adjustment data in one file. The ‘Adjustment Only’ setting in the job is only required if you want to treat all timesheet data including the first timesheet as adjustments.
If you Reject, Recall a NCI flagged timesheet in Time & Attendance or Reverse from Interpreter and then make changes to the timesheet in the UI, it will still be interpreted without offsetting the original timesheet data (where it is an adjustment).
You cannot enter negative quantities in Time & Attendance, these can only be applied via Timesheet Import.
If you import iterations of a timesheet out of order ie; negative timesheets first, and in interpreter release these to pay prior to approving other timesheet iterations for that week end date, the pay process the net result may have implications to your ability to process the pay batch. For example, if it is the first timesheet for a new fiscal year, the YTD needs to be greater than zero which will trigger an error preventing you from closing the pay batch.
Leave: Additional Item Leave is not supported out of order. The original positive quantity leave needs to be first and then fully negated prior to any subsequent adjustment change, this is to ensure that the corresponding Leave Requests are created, then credited, then re-created to support what is required. For example;
Original TS - 12.12.24 Annual Leave Qty 8
Adjustment TS 1 - 12.12.24 Annual Leave Qty -8
Adjustment TS 2 - 12.12.24 Annual Leave Qty 7.5.
Benefits
These enhancements are designed to support data import from third party system, where:
import data needs to be honored as per the VMS output.
iterations of a timesheet may be imported out of order ie; adjustment prior to the target timesheet.
adjustment data needs to be ‘drip fed’ onto timesheets. For example worked items are imported first, and then expenses and or overtime items are imported later.import data needs to generate multiple adjustment timesheets in one import for the same Job Order and same Week Ending Date to support different iterations of timesheets.
Configuration
Additional fields will need to be mapped in Time & Attendance > Timesheet Import Wizard > Field Mapping where new rates and or rate values are to be imported and where timesheet grouping is required for import of multiple adjustment timesheets for same Job Order and same Week Ending DateNo additional configuration is required to support ‘No Credit Interpret’.