Generally it works best if the timesheet cycle is set to fit with the shortest cycle, for example place the assignment on Weekly timesheets so that the client can be billed weekly as required but the candidate's pay can be left to build up until the end of the month when 4 or 5 timesheets can be paid.
However, if it is essential that when the calendar month finishes mid-week, for example the 31st of the month falls on a Wednesday, if the usual timesheet start day for those weekly timesheets is Monday the system will produce a timesheet ranging from Monday 29th to Sunday 4th whilst on a standard Weekly Timesheet Timespan. If this is not suitable and you require the month split to be represented over two separate timesheets then it will be necessary to create your own Timesheet Timespan template that controls these dates. The only potential considerable to this arrangement is the candidate will have to complete two timesheets when the month split occurs.
For more information on this area of the system please refer to the following articles:
If the candidate is on a different pay cycle which does not coincide with the timesheet cycle and a custom Timesheet Timespan has not been used it is a case of having to adjust the timesheet in order to pay a different amount of units to what is being charged to the client. This should be done at the validation stage, after the units have been entered and the timesheet has been authorised but prior to payment and billing. This means amending the existing rate code line to reflect this, for example, 1 unit at the bill amount and removing the pay rate so this line is bill only. Another rate line can then be created in the timesheet to represent the pay only transaction, so 5 days at pay rate with a zero bill:
Also, if preferred, the timesheet could be amended to be bill only as mentioned above and a second, additional timesheet created for the same period to reflect the pay arrangement (please refer to the Related articles).