1. Knowledge Base
  2. Time Sheets
  3. Setting up the Time Sheet Module

Explaining the Time Sheet Manager Settings

Setting up the Time Sheet module for your requirements.

In the Time Sheet Manager, you can configure various elements of this module, including certain areas being visible, coding requirements and more.

We'll explain the different sections and what the various settings do.

To access the Time Sheet Manager, start at Settings > Time Sheet Manager, located in the right hand column.

Once in this view, you will see the following options:

General settings

  • Allowance required: Enable this field if you use allowances in your time sheet workflow. Then, you can access the Allowance types and Allowances definitions options in the Time Sheet menu, and the Allowance tab within a Time Sheet User Group.
  • Track Allowances: This setting causes the Allowances tab to be visible within the Time Sheet edit and approval view, so you can view allowances that have been selected or calculated for a time sheet.
  • Overtime: Enable this field to access overtime settings and fields in the Time Sheet User Group view.
  • Default time sheet overtime threshold: When the Overtime field has been enabled, this field sets the threshold that must be met before time can be recorded as overtime.
  • Always apply overtime adjustment: Any time over the Default overtime threshold will be recorded automatically as overtime.
  • Crew workflow required: Enable this setting to allow any crew time workflows and functions to be visible. If you are not using crew time you can untick this setting.
  • Allow yard/asset recoveries: This allows a yard item to be shown and selected for a time sheet. This setting is only relevant to customers using both the Time Sheet module and the Yard module.

Cycle settings

  • Initial cycle start date: This should match the first day of your first pay cycle in Lentune.
  • Frequency: This sets your pay cycle frequency which determines how your time is displayed and batched in Lentune. If you run multiple pay cycles you should set the most frequent one here, i.e. Weekly.
  • Default working day definition for user groups: Your working day definition allows the system to recognise the working days and relevant public holidays for your team. These are then set for your User Groups. You can create multiple working day definitions if you have teams based in different regions. You can leave this field blank to set your working day definitions for your individual User Groups, or you can set a default definition here, to use for all user groups.
  • Display time sheet cycle end date: The default pay cycle date in the Time Sheets view is the Cycle start date. You can choose instead to use the Cycle end date by ticking this field.
  • Minimum meal break duration: You can set a minimum meal break duration which will be enforced in time sheet entries. This is applied when the Time sheets are processed in the process screen by a Time Sheet Admin.

Public Holiday Settings

  • Auto create public holiday entries: Enable this setting so that any public holiday statutory days, as defined via your Working Day Definitions will be created automatically for your users in the relevant time sheet cycle.
  • Default public holiday time sheet entry type: Choose which of your entry types that the automatically created public holidays should be associated with.
  • Default public holiday project: If you require a project code to be used for public holiday entries, you can set a default project for all entries.
  • Default public holiday cost code: If you require a cost code for your public holiday entries, you can set the default cost code for all entries.
  • Time Sheet entry coding is required for public holiday: Enable this if you want the Time Sheet coding requirements to apply to public holiday entries.

Approval Settings

  • Time sheet entry cost code is required: Enable this field to enforce a cost code to be entered for a time sheet entry before it can be approved.
  • Time sheet entry cost code is required for new entry: Enable this field to enforce a cost code to be entered before a time sheet can be saved.
  • Time sheet entry project is required: Enable this field to enforce a project to be assigned for all time sheet entries.
  • Time sheet entry project is required for leave: If leave is entered as a normal time sheet entry (i.e. not as a leave request), enable this field to enforce a project code to be used for leave entries that are entered this way.
  • Time sheet entry project is required for leave request: Enable this field to enforce a project to be required for leave entered through the leave request workflow.
  • Show full timesheet by default: Enable this field to show the approver the full time sheet for a user, even if the approver doesn’t have access to approve all entries within the time sheet.

Leave settings

  • General Ledger required for “leave” entry type: Enable this field to enforce Entry Types to have a General Ledger code.
  • Send email when leave request is approved: Recommended to allow your users to be advised when their leave requests have been approved.
  • Leave Request calendar feed url: To generate the URL to import your leave entries into your own outlook/gmail calendar. For more information please refer to Export Leave Requests.

Export Settings

This area will be managed for you by a member of the Lentune team.


Need more help? We’re here! We hope our article was helpful! If you need more info or want to connect, drop us an email at support@lentune.com.

Thank you. We love to hear from you!

Last updated: 22 February 2024