Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Description

Currently where an Adjustment Timesheet is required, the import process must mimic what is required in the UI, for example:

...

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, in both cases no item would be supplied for Reimbursement, as that item is unchanged.

No Credit Interpret (NCI)

In this release we have provided the ability to avoid the credit process during interpretation (the process whereby the interpreter offsets the target timesheet values from the adjustment timesheet).

...

  • The logic to credit (offset) the target timesheet’s transactions to find the balance between target and adjustment, 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). We suggest you do not edit data in the UI, as data will no longer be as per the VMS, plus you cannot enter negative quantities in Time & Attendance, these can only be applied via Timesheet Import.

  • Where timesheets have been imported in error, they can be backed out via ‘Recall’ or ‘Reject’ if submitted, and then ‘Cleared’ in ‘Rejected or ‘Incomplete. If the timesheet has been ‘Approved’, providing it has not been released to Pay and or Bill, it can be 'Reversed’ from the Interpreter and then 'Cleared’.

  • If you import iterations of a timesheet out of order ie; negative timesheets first, and then release these to pay prior to including other timesheet iterations for that week end date, there may be issues in the pay process as the net result may impact 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, if not this 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, if incorrect, a subsequent adjustment is required to fully negate the quantity, prior to the next iteration with the correct positive quantity and or rate. This is to ensure that the corresponding Leave Requests are created, then cancelled, 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

This enhancement is designed to support data import from third party system, where:

  • import data needs to be honored exactly as per the VMS output.

  • iterations of a timesheet could potentially 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.

Configuration

No additional configuration is required to support ‘No Credit Interpret’.

...