...
The following describes the fields and their purpose:
Excerpt |
---|
Field | Description | Rules | |
---|
AWR Active | This controls the visibility and management of AWR for the country. | It is defaulted to unchecked. When checked on, the fields in the section will be enabled for entry as well as other fields and functionality is enabled in the rest of the system. Should this flag be set to checked, and then unchecked, this will not remove any existing AWR data, it will just hide the fields and data from the screens.
| | Qualifying Weeks Before Parity | This sets how many weeks before the job order reaches parity. For the UK, the payee must have worked for 12 weeks and from the 13th week, they have reached parity. | | | Reset After Weeks Not Worked | This sets how many weeks a job order has not been worked in before it resets the AWR clock back to zero. | The default is 6 but can be changed at any time. If this value is subsequently changed, when the reset service runs, it will use the new value going forward. It will not reassess for prior missed periods.
| | Clock Count Basis | The legislation states that the AWR clock starts from the job start date which could be in the middle of a timesheet period. However, if applying based on the job start date rather than the timesheet period, will have minimal effect on when the payee reaches parity but can add confusion where the timesheet period and AWR period is not aligned. | | | AWR Adjustment Reason | Where the system determines to pay the difference in rates for a timesheet that should have been at parity but was not due to a late timesheet not being received, an adjustment reason is needed when the adjustment timesheet is automatically created. | | | Monitoring Not Required for Payee Types | To select which payee types should not be monitored for AWR. Not all payee types are affected by this legislation e.g. Contractor and CIS. This field allows you to select those payee types that should not be monitored. This will then stop the need for entering parity rates against the job as well as not recording the clock history against the job. | The default is Contractor, CIS, PAYE/Deemed but can be changed. If this value is subsequently changed, only new jobs created will be affected.
| | Clock Reset/Pause Assessment Day | There is a Windows service that runs on the day selected of when it needs to assess if a timesheet has been received or not to then record if the clock should be paused or reset based on the Reset After Weeks Not Worked setting. The same service is used to determine if an absence for a period should also be paused or re-set based on the setting against the Absence Type. As each organisation has its own internal process to specify at what point in the week there is a timesheet cut off, this needs to be defined. | | | Clock Reset/Pause Assessment Time (24 hour) | This works alongside Clock Reset/Pause Assessment Day and is to specify at what time of day should the Windows service should activate on the day specified. As each organisation has its own internal process to specify what the cut off day and time would be to receive timesheets to process, this needs to be defined. | | | Initialisation Status | When you have applied the updates to the Agency Worker Regulations section and clicked Save Changes, you have the option for initialising your data to: Pre-populate parity rates in standard rates, the same as the pre-parity rates Pre-populate parity rates in agreement rates, the same as the pre-parity rates Apply the clock count to job orders
Please click here for further information about this process. | The options shown will be: Not Started Not Required In Progress Complete
Once the initialisation process has been completed, it cannot be processed again.
| Image Modified |
|
...
Benefits
To automatically manage when a job order reaches parity, the parity rates and enhanced holiday accrual rate are applied without any manually monitoring.
...