Skip to main content
Configuring Tanda's Organisational Settings

A guide to configuring and customizing your organisational settings in Tanda.

Updated over a month ago

This help guide will discuss how to access and configure your organisational settings, allowing you to customise your experience and get the most out of Tanda.

1. Accessing and Editing Your Settings

Important: You require admin-level permissions to configure, edit, and access your organisational settings. If you cannot access the settings outlined in this guide, you likely have the incorrect permission level.

To access and edit your settings, log in to Tanda in a web browser, then navigate to the settings wheel in the top right corner of the page and click on 'All Settings.'

You should then see a page titled Settings & Configuration, as below:

We will explain what each of these settings means and how to configure them throughout the rest of this article. You can use the 'Search settings' feature to find each of the settings we discuss.

Note: To minimise the risk of accidentally modifying a setting, any changes you make will only take effect after clicking the 'update settings' button at the bottom of each settings page.

If you intended to update a setting but your changes haven't taken effect, this is usually the reason.


2. General Settings

To access General Settings, navigate to Settings > General.

2.1 Public Holidays

Public Holiday Region


Select your desired public holiday region based on your business location. This setting will pre-fill your account with all your region's state and federal public holidays.

If you need clarification on which dates will apply, click 'Show Pre-Built Holidays' to see a list of which dates will apply if you select that region.


Public Holiday Dates

In addition to pre-filling public holidays, you can also manually configure the dates of any local public holidays (e.g. your local show day). Use this setting only if the pre-fill above doesn't capture the public holiday.

Note: If your organisation operates across multiple locations, you can select different public holiday regions for each location under Workforce > Teams > Edit > Show advanced options.

For more details, see our public holiday help guide.

2.2 Shift Feedback

Next, you can enable our shift feedback feature. To do so, tick this setting to turn it on or uncheck it to turn it off.

If enabled, staff will receive a short weekly feedback survey via the Tanda Mobile App, allowing them to provide feedback on topics like communication, management, morale, and more.

You can easily edit the categories employees can provide feedback on by clicking 'Edit Shift Feedback Categories.' Then, select either 'Edit' or '+ Add New Category' as desired.

You can access this feedback via the Shift Feedback Report under the Reports tab. For more details, see our shift feedback help guide.

2.3 Salaried Staff (Allocation)

This setting controls how you calculate the per-shift costs of salaried staff.

There are three options:

  1. Split using an hourly rate: This method is calculated by dividing the employee's weekly salary by their contracted weekly hours. If contracted hours are unavailable, their rostered hours will be used instead.

  2. Split evenly by rostered days: This method is calculated by dividing the employee's weekly salary by the number of rostered days. This method will not have variances and works well for any timesheet.

  3. Split salary evenly by days in year: This method is calculated by dividing the employee's yearly salary by the number of days in the year (365). This method will not have variances and works well for any timesheet.

2.4 Advanced Settings

Show Weekends on Timesheets and Rosters

If enabled, weekends will be shown on your timesheets and rosters. If disabled, Saturdays and Sundays will not show up when viewing timesheets or rosters (unless someone has clocked in on that day). This makes it easier to navigate Tanda if your business only operates on weekdays.

Session Inactivity Timeout (Days)

This setting specifics the time (in days) before users are logged out after being inactive. For example, if set to 30 days, a user would be logged out of their account after 30 continuous days of inactivity in Tanda.

Enforce Two Factor Authentication

If you enable this setting, all employees with admin or manager-level permissions must use two-factor authentication when logging in to Tanda. This setting does not apply to users with employee-level permissions.

For more details, see our help guide on managing two-factor authentication.


3. Permissions

To access permission settings, navigate to Settings > Permissions.

3.1 Manager Permissions

Allow team managers to see costs: This setting controls whether team managers can see staff costs on rosters, timesheets, and staff profiles. If enabled, managers can only see costs for the staff they manage. No matter what, they can never see costs for staff they don't manage.

You can also allow only certain managers to see staff costs. To do so, leave this setting disabled. Instead, navigate directly to each manager's profile and check or uncheck the 'can see staff costs' setting as appropriate.

Protect manager data (salaries, hourly rates & performance reviews): When enabled, this setting hides managers' wages from other managers even if they can view them on the roster. Managers can still view employee wages, and general managers can still see team managers' salaries.

Keep manager costs visible in total roster costs: If ticked, team manager wages are included in total roster costs. Please be aware that with this setting enabled, managers can theoretically determine other managers' salaries by adding and removing shifts to a roster and subtracting the total cost change.

Allow team managers to edit/approve their own timesheets: If enabled, managers can edit and approve their timesheets. When this setting is unticked, managers can still view their timesheets but cannot edit any times or approve their timesheets.

Receive qualification update alerts: Use this setting to determine who receives an alert if a qualification is due to expire. If enabled, Team Managers and General Managers will only receive alerts for teams they manage, while Admins and Payroll Officers will receive alerts for all expiring qualifications.

3.2 Employee Permissions

Allow staff to add times to their own timesheets: When ticked, this setting allows employees to fill in blank timesheet entries. Employees won't be able to edit existing times; they can only fill in blank ones. As such, you can use this setting to ensure employees enter times if they forget to clock in/out.

Allow staff to make changes to all timesheet fields: This setting lets employees add allowances and edit award tags on their timesheets. A manager must still approve any changes. This feature is useful if you require further information from employees, such as allowing them to enter their travel allowance so they can enter the kilometres travelled.

Allow staff to view their Timesheet Export Summary: This setting allows staff to see their Timesheet Export Summary. The Timesheet Export Summary shows a visual breakdown of how their gross pay was calculated for a timesheet. The main benefit of displaying this summary is that employees can see when specific pay rates were applied and why.

Allow staff to clock breaks: When ticked, this setting enables a break button on the time clock or Mobile App, allowing employees to record break times during their shifts.

Allow staff to see their own estimated wages: When this is ticked, staff will see estimated gross wages for their rostered shifts in the Mobile App. These wages are clearly marked as estimated to ensure staff understand they might not accurately reflect what they will earn, particularly if they work different hours than initially rostered.

Allow staff to view the full roster: This setting allows staff to view the entire roster, not just their shifts. That way, they know who is working each day and who their manager is. You can nominate whether staff can see the full roster for only the teams they work in or their entire location.

Allow staff to enter leave requests: When ticked, employees can enter their own leave requests via the Mobile App or web browser. Otherwise, staff won't see the leave option and will need a manager to create a leave request on their behalf manually. To learn more about submitting leave requests, visit our help guide.

Allow staff to view the full leave calendar: If enabled, this setting allows staff to view the full leave calendar for either the teams they work in or their entire location. That way, they can see who else is taking leave and plan accordingly.

Employees can enter unavailability: This setting allows employees to enter their own unavailability requests. To learn more about unavailability, see our help guide.

Allow staff to update qualifications: If enabled, employees can update any qualifications that apply to them. Changes will still require manager approval. Learn more about qualifications via our help guide.

3.3 Advanced

Default Passcode Length

This setting defines the default passcode length used when clocking in via a Tanda time clock. By default, this is set to 4 digits. This setting is useful for large organisations that quickly exhaust all possible 4-digit combinations or if your organisation already has a numerical code of a different length that employees need to remember.

Customise Access & Roles

Use this setting to customise access and role permissions. On this page, you can edit the access and permission settings for each default role type in granular detail. You can also create and configure a new role type by selecting + New.

You will then be prompted to name your new role, enter a description, and define the role type (either admin, manager, or employee). Employees can only see their own information, while managers can see the information of staff they manage, and admins can see all information, provided the access hasn't been disabled below.

From here, expand each drop-down menu to customise the permission settings for that role. For example, in the image below, you can choose whether team managers can create a location. Toggle this setting on/off as desired.

If you're ever unable to access something in Tanda and you're unsure why (or you want to restrict someone else's access), we'd recommend navigating to this page (Settings > Permissions > Show Advanced Settings > Customise Access & Roles Here) and cross-referencing the permission settings with the action you were trying to perform.


4. Shift Breaks

On this page, you can nominate whether to enable the break rules setting. Additionally, you can configure whether paid meal breaks count as time worked, whether to enforce minimum break durations, and whether to require staff to nominate which break they're taking.

4.1 Configure Break Rules

When the 'Enable Break Rules' setting is ticked, this setting allows you to configure break rules to help with scheduling and compliance.

Additionally, you can nominate whether each break is paid and whether a clock-in is required.

For more details on configuring this setting, see our dedicated help guide along with the common use cases below.

Common Use Cases

Use Case 1: Clock Lunch Break & Show Unpaid Breaks

Many customers want their employees to clock into their lunch breaks but merely show records on their timesheets for shorter paid rest breaks.

In this example, the system is configured for one un-clocked paid break after 4 hours, a clocked unpaid break after 5 hours, and a second un-clocked paid break after 7 hours.

Employees can still clock in and out of the paid break if they want to. The system will match the rule if they do.

Note: If you have automatic breaks turned on and an employee clocks a break, any unpaid automatic breaks will no longer apply to the timesheet.

Use Case 2: Clock All Breaks (Paid and Unpaid)

Compliance-focused customers sometimes prefer to have employees clock all paid and unpaid breaks. This configuration provides strong evidence that the break was taken if there is ever a dispute.

To set this up, select 'clock in required' on each break rule. This will prevent the break from appearing on the timesheet unless it's physically clocked.

Use Case 3: Employees Don't Clock Any Breaks

Finally, some organisations don't require employees to clock in or out for breaks. In this case, ensure you have not selected the 'clock in required' box. Tanda will automatically apply the break rule to the timesheet.

Adjusting the Break Thresholds

Default Rules

If everyone at your company follows the same break rules, you can adjust the default break rules to suit your requirements.

Award rules and regulations typically define how long employees can work before they're entitled to a break. Consult your award for the appropriate break times and lengths for your employees. You can add each break your employees are entitled to by creating or editing a break rule.


Custom Rules

As well as the pre-set default rules, you can click + New to create a custom rule set. You can use this custom rule set for staff who follow particular break rules that are different to the default. To do so, select who the rule applies to based on award templates or staff tags—you will be shown a list of which staff match your filter.

Then, enter the shift duration and break length, and specify whether this is a paid break or a clock-in is required.

Multiple Rules

You can also create multiple rules within a single rule set if different break lengths apply to different shifts.

See the below example, where the break lengths increase as the shift length increases. For an 8-hour shift, the employee will receive one unpaid 30-minute break and two paid 10-minute breaks:

Notes

  • When multiple custom rule sets apply to the same employee, you will see a notice similar to the one below. In this case, all rules from both custom rule sets will apply unless the rules conflict. If multiple rules conflict for a given shift length, we will apply the rule with the longest break length.

  • A custom rule will override the default rule for any employees to which it applies.
    For example, if the default rule specifies a break after 5.5 hours, and a Custom Rule specifies that full-time workers will get a break after 7 hours, full-time workers will only receive an automatic break once they have worked for 7 hours. In other words, if one or more custom rule sets apply to an employee, the default rule set is ignored. If desired, you can use this setting to effectively override automatic breaks rules for certain employees.


5. Rosters

5.1 Shift Replacements And Swapping

These settings control the following features:

  • Enable shift replacements: When ticked, staff can use the mobile app to request a replacement when they can't work a scheduled shift.

  • Recipients of shift replacements chosen by staff: If enabled, staff can choose who will replace their shift.

  • Allow staff to initiate one-to-one swaps: If enabled, staff can request to swap shifts with another team member directly.

  • Shift replacements and swaps require manager approval: This setting applies to both shift replacements and shift swaps. If ticked, a manager must approve any proposed shift replacement/swap.

To learn more about shift replacements, see our help guide.

5.2 Shift Acknowledgement

When ticked, the Enable Shift Acknowledgement feature helps manage staff attendance by asking employees to acknowledge their shifts once a roster is published. This allows managers to more easily identify rostering errors or clashes. It also ensures employees can't use an excuse such as "I didn't realise I had been rostered" if they unexpectedly miss a shift.

To learn more, see our help guide.

5.3 Vacant Shift Claiming

Use the following settings to customise the vacant shift claiming feature:

  • Enable Vacant Shift Claiming: When turned on, this feature allows you to create and publish vacant shifts for employees to claim. For example, you could publish a shift from 4p-9p on Thursday, with no staff attached to work it. Available staff can then volunteer to work this shift.

  • Vacant Shift Claiming requires Manager Approval: If ticked, a manager must authorise a vacant shift claim before assigning it to an employee.

  • Secondary Teams: When ticked, this feature allows staff to be 'secondary team' members who can pick up vacant shifts in case primary team members are unavailable. Learn more about this setting here.

To learn more about the vacant shift claiming feature, see our help guide.

5.4 Predictive Scheduling

When the 'automatically build optimal rosters based on your staffing requirements' feature is enabled, users can automatically build and fill rosters with the "Build Empty Schedule" and "Assign Staff to Shifts" buttons on rosters.

To learn more, see our predictive scheduling help guide.

5.5 Labour Budgets

When ticked, the Enable Labour Budgets feature lets you view labour cost budgets by team or location.

For a more detailed breakdown, see our help guide.

5.6 Validations

Roster validations are coloured warnings that appear on rostered shifts to alert managers that a rule or limit has been broken. For example:

You must enable roster validations by ticking the 'Enable roster validations' setting.

From here, you can configure each of our roster validations by toggling each setting on or off.

You can set each roster validation as 'enabled' or 'blocking'. If you tick 'enabled', you will receive a warning whenever you violate that roster validation rule. If you tick 'blocking', you will receive a warning and be blocked from publishing that roster until you resolve the error.

Additionally, you can create custom roster validation rules that apply to all staff or custom rules for specific employees or groups of staff (filtered by tags, locations, ages, etc.). To do so, click + New under Additional Validation, then select who the rule applies to, when it applies, and what validations they should receive.

To learn more about roster validations, see our help guide.

5.7 Advanced Settings

The 'Rosters start on' setting changes the start day of your roster. Changing this setting takes some time to process. We recommend doing so at the end of your day if you ever need to update this setting.

Similarly, the setting 'Use a consistent roster cycle start date for all users' means that all users in your organisation will have the same roster cycle start day. This setting affects the order in which regular hours of work are displayed on employee profiles but will not change existing regular hours of work patterns.

Finally, the 'Assisting Teams' feature allows staff from one team to be counted towards another team in your Predictive Workforce requirements.


6. Timesheets

6.1 General

Firstly, you will need to configure general timesheet settings.

Allow staff to approve their own timesheets (in addition to manager approval) via the mobile app: Some awards require staff to sign off on their timesheets to allow the staff to verify they're being paid correctly. When this setting is enabled, staff may approve their timesheet, which confirms the timesheet is correct, or request an amendment. Amendment requests will not block timesheet exports. Manager approval is still required.

Enable Custom Export Dates: When enabled, this setting adds a date picker to the 'timesheet export to payroll' page. That way, you can export timesheets over a custom date range.

6.2 Shift Auto-Approval

When enabled, this setting means that shifts will be automatically approved when they meet specific criteria. Managers will not have to approve these shifts when your nominated criteria are met. You can specify the following auto-approval criteria:

  • Start and Finish Time: Shifts will be auto-approved if employees' start and finish times match their rostered schedule.

  • Cost Variance: Shifts will be auto-approved if the shift cost matches the scheduled cost.

  • Shift Length: Shifts will be auto-approved if the shift length matches the scheduled length.

  • GPS Data: Shifts will be auto-approved if clock-in GPS coordinates match your worksite.

You can select more than one of these criteria for auto-approval.

Below this, you can also enable Shift Variance Approval. When selected, this setting will require employees to leave a comment via the Mobile App if there is a variance between their actual and scheduled shift times.

You can also enable Shift Ratings, which prompts managers to give each shift a star rating when approving shifts. Team managers will see this rating on employee profiles and when scheduling, to help choose the best employee for each shift. To learn more, see our shift ratings help guide.

6.3 Shift Checks

Tick this setting to enable and configure our shift checks feature. Tanda's Payroll Checks and Shift Checks allow you to configure validations that check important payroll information is accurate and valid. These checks can be configured to either block you from performing an action entirely or warn you that certain conditions aren't being met.

To learn more, see our pay checks help guide.

6.4 Remote Clock-ins

This setting determines whether staff can clock in remotely via the Mobile App. You can enable this for all teams or select only specific teams that can.

To learn more, see our help guide.

6.5 Clock-in/out Rounding

Time Clock rounding is used to automatically round the times recorded on the Time Clock or Mobile App.

You can use this setting to specify the rounding time for clock-ins/clock-outs. For example, if you set this to 5 minutes, a clock-in time of 8:57 am will be rounded up to 9:00 am. Similarly, a clock-out time of 5:02 pm will be rounded down to 5:00 pm.

You can also specify whether you want clock-in and clock-out times to use smart rounding. Smart rounding sets the direction of rounding to be one-way, rounding the clock-in/clock-out time towards the shift.

For example, let's say an employee is rostered to start at 9 am. If they clock in at 8:56 am, their time will be rounded up to 9:00 am. However, if they clock in at 9:02, this will not round back to 9:00 am—unless you have ticked 'round clock-ins to rostered times'. If so, clock-ins/outs will round back to the rostered time in both directions as long as it is within your specified rounding margin.

Timesheet rounding is optional. To apply no rounding to timesheets, leave these fields blank.

In this section, you can also set up clock-out rounding for any automatic breaks you have configured that specify "clock-in required."

6.6 Advanced Settings

Click 'Show Advanced Settings' to configure the following features:

  • Enable team switching: If enabled, this setting allows users to clock out of their current shift and directly into their next shift on a different team.

  • Show an extra drop-down to adjust shift costs (award tag): Tick this setting if you want an additional drop-down menu to appear on timesheets with a list of award tags you can apply to an employee. For example:

  • Maximum shift length (hours): Define the maximum length employees can work, as dictated by your award. By default, this is set to 14 hours. If the maximum shift duration is exceeded, Tanda automatically changes the employee's shift status to "clocked out." As such, the next time employees use the time clock, they are prompted to clock in rather than out. This ensures that if an employee forgets to clock out, Tanda doesn't create an unreasonably long shift the next time they clock in.

  • Minimum duration between shifts (hours): Define the minimum time between shifts. This will be dictated by your award. By default, this is set to 8 hours.

  • Overtime averaging period (weeks): Define your overtime averaging period in weeks. This can be different from your timesheet lengths.
    ​​
    For example, you could have bi-weekly timesheets (you run payroll every second week) but calculate overtime weekly. In this example, if overtime is applied after 40 hours each week, and an employee worked 42 hours in Week 1 of a timesheet and 30 hours in Week 2, they would get overtime for Week 1 since they exceed 40 hours/week.

    Alternatively, you might have weekly timesheets (you run payroll every week) but calculate overtime over 4 weeks. In this case, staff would incur overtime if they worked more than 152 hours over 4 weeks (assuming a standard 38-hour work week). In most cases, this would only show up on every fourth timesheet.

    If you change this setting, ensure your earnings rules match your changes. For example, if you set a two-week overtime averaging period, the overtime field on your earnings rules should be 80 hours (not 40).


7. Leave

These settings control your leave and unavailability behaviours in Tanda.

7.1 Unavailability

An unavailability request is when an employee nominates that they're unavailable to work. An unavailability request can be recurring (i.e. you're unavailable every Thursday) or one-off. Managers can use this information when rostering. Unavailability is distinct from leave, which is a request for time off work.

Use these settings to define the minimum number of days' notice required for an unavailability request.

If a staff member attempts to submit an unavailability request without sufficient notice, they will be blocked from doing so, along with a notification explaining why, as below.


Additionally, you can define whether unavailability requests require manager approval. If this setting is disabled, unavailability requests will be automatically approved but managers will still be notified.

7.2 Default Leave Behaviour

The following settings control what happens when an employee submits a leave request in Tanda.

Display Predicted Leave Accruals: When this setting is enabled, employees will see their predicted future leave balances when requesting leave. For example, if an employee requested annual leave three months in advance, they would see both their current balance and their predicted balance three months into the future. Learn more about this setting here.

Cost leave on weekends: By default, Tanda assumes that staff generally only take leave on weekdays. If your business operates 7 days a week, you’ll need to enable this option so that leave requests are calculated and exported if they fall on a weekend.

Default leave hours per full day of leave: When a leave application is entered into Tanda, the 'Total Hours' field auto-populates. That information is pulled from this setting by multiplying the number of days in your leave request by the default leave hours per full day. By default, this is set to 7.6 hours, the figure most businesses use for a standard business day. To update this, enter a new number in the field.

No default leave hours: If this setting is enabled, the above setting will be disabled. When ticked, the 'Total Hours' leave field will not auto-populate. Instead, employees must manually enter how many hours of leave they're requesting.

When an employee requests leave, notify: Use this setting to manage who is notified when an employee submits a leave request. Select between 'Nobody', 'Admins', 'Employee's Team Managers', and 'Admins & Employee's Team Managers.'

7.3 Autofill Leave Requests

Use this setting to create strategies that dictate how a leave cost breakdown is auto-filled (i.e. where are the hours for a leave request drawn from?).

To create a new leave autofill rule, click + New.

Then, select who the rule will apply to via tags. Finally, select how leave requests are auto-filled (and in which order) between published rosters, unpublished rosters, and regular hours of work.

For example, let's say a part-time employee requests leave for a day when they usually work a 5-10pm shift, as defined by their regular hours of work. Instead of auto-filling a 7.6-hour day of leave, you can configure a leave rule to first check part-time employees' regular hours of work for leave requests. In that case, the leave request would auto-fill to be 5 hours. You can configure as many of these rules as required.

For a more detailed breakdown of this setting, please see our help guide.


8. Attendance

Many organisations like to track employee attendance—especially punctuality—and take appropriate action for non-punctual employees. You can control your attendance tracking via these settings. You can easily report on this information via our Attendance Report and Attendance Points Report.

8.1 Clock-in/out Punctuality

Use these fields to define your punctuality leeway for clock-ins and clock-outs, includinf outliers that should be excluded.

For example, if set to 5 minutes, a clock-in at 4:58 pm for a 5:00 pm start time would be considered on time.

You can also set punctuality outliers. For example, if an employee shows up at 10:09 am for a 9:00 am start time, their clock-in will not be counted, as they are so far outside their rostered start time that it is considered an outlier.

8.2 Point System

With the above rules set, you can also implement a points-based attendance system. Tanda's points-based attendance feature makes it easy for admins/managers to track these statistics and enforce the appropriate levels of discipline.

You can create a new rule set by selecting + New Rule Set. Then, enter the rule type, points, and expiry date.

For a detailed breakdown of this feature, please see our points-based attendance help guide.


9. Shift Questions

The shift questions feature asks staff questions via either the Time Clock or Mobile App when specific criteria are met, such as clocking in too early.

To configure this feature, navigate to Settings > All Settings > Shift Questions and click + New Question to configure your first question.

From here, you will need to enter the following information:

  • For: Select whether the question is intended for the Time Clock, Mobile App, or both.

  • When: Nominate whether the question is asked when an employee Clocks In, Clocks Out, at their Break Start, or Break Finish.

  • Only If: Select the criteria under which the question should be asked, e.g. 'Earlier than scheduled.'

  • Lenience (minutes): Set the lenience for which clock-ins/outs are considered early or late.

  • Determine An Action (ask a question or prevent a clock-in): Select what happens when someone tries to clock in/out outside of your nominated lenience. You can either ask a question or prevent the clock-in entirely.

  • Ask: Enter the question you want to ask when these criteria are met, e.g., "Why have you clocked out late?"

  • Then: Nominate what happens after an employee has answered your question. e.g. "Add a timesheet comment."

  • Is Required: Tick this to make the question mandatory, or leave it unticked to make answering the question optional.

  • Add Quick Responses (Optional): Use this to add quick, common responses that employees can select. For example, if the question is "Why have you clocked out late?" you might add a common response, "My manager asked me to stay back." Employees will see a free text box if you leave this field blank.

To learn more, see our shift questions help guide.

FAQs

Can I include a free text field for employees to type an answer?

Yes. To do so, leave Section 2. 'Add Quick Responses (Optional)' blank and ensure you have selected 'Add a timesheet comment.'

How can I view answers to shift questions?

You can navigate directly to the Shift Comments Report via the Reports tab.

What order are shift questions asked in?

Shift questions are asked in alphabetical order. Therefore, you can add a number before each question to change the order.


10. On-Cost Config

To view on-costs, such as payroll tax and superannuation, in your roster costs, you can configure the setting through Settings > All Settings > On-cost Config.

Note: On-costs configured in Tanda serve as estimates only. They are not exported or paid through Tanda.

When your account is created, three on-costs are set up automatically: Workcover, Cost of Leave Accrued, and Superannuation.

How are Workcover, Cost of Leave Accrued, and Superannuation on-costs calculated?

These on-costs are calculated as percentages of the wage cost independent of one another. So, these on-costs are calculated using the following formulae:

Workcover on-cost = wage cost x workcover multiplier
Leave on-cost = wage cost x leave multiplier
Superannuation on-cost = wage cost x super multiplier

Total wages including on-cost = workcover on-cost + leave on-cost + super on-cost + wage cost

Example:

An employee's wages for the week total $100, excluding on-costs.

The Workcover on-cost is set to 10%.

The Leave on-cost is set to 19%.

The Super on-cost is set to 10.5%.

Total wages including on-cost = ($100 x 0.1) + ($100 x 0.19) + ($100 x 0.105) + $100.

Therefore, including on-costs, the total for this employee is $139.50.


Edit and Create New On-cost Configurations

You cannot directly edit pre-configured on-costs. To make changes to these pre-set fields:

  1. Create a + New config using the blue button.

  2. Copy the details from the existing on-cost into the new configuration.

  3. Make the required changes to the new configuration and click 'Create on-cost config'.

  4. Navigate to the old on-cost configuration and use the red Delete on-cost config button to remove it.

To create a new on-cost field:

  1. Click the blue + New config button.

  2. Name the configuration. This is important if you want to set up multiple on-costs for different costs or locations.

  3. Select which staff the on-cost applies to based on their classification tags.

  4. Select the location(s) to which the on-cost applies. This is particularly useful for payroll tax, where businesses set different rates for operations in different states.

  5. Enter the value (%) that applies.

  6. Select whether on-costs should only apply to ordinary hours or all worked hours.

  7. Select whether the on-cost is for superannuation.

  8. Once complete, click the green Create on-cost config button.

Viewing On-Costs on the Roster

To view the total cost of your roster, including on-costs, navigate to the Rosters page. Then, click the arrow as shown above to expand the view of your roster stats.

From here, select 'Total Cost with On-Costs' from one of the drop-down menus.

Viewing On-Costs in Cost Reports

To view on-costs within our Reports, navigate to Reports > Cost Reports and select the relevant report.

From here, use the toggles shown below to include or exclude on-costs.

You can find a more specific breakdown of your on-costs in the Real Wage Cost report. Learn more about cost reports in our help guide.

11. Organisation Notifications

11.1 Notifications & Tasks

Use the notifications & tasks page to configure your organisational notification settings. On this page, you can choose who receives notifications and under which criteria. For example, you can select who receives notifications if an employee is late or has an overtime risk. For each notification type, you can choose whether the employee, manager, or account admin is notified—or all of the above.

You can also schedule tasks on this page, such as emailing an employee if their timesheet needs to be completed. Use the side menu to navigate between Key Alerts and Scheduled Tasks.

To manage your personal notification settings, navigate to your notification preferences, as shown below.

11.2 SMS Log

The SMS log provides a log of all SMS' sent from your account, including the recipient and delivered status. This record can be useful to prove an SMS was delivered.

12. Communications

Use this page to configure Tanda's communication and live chat settings.

Tick the 'Enable Live Chat' box to enable this feature. When enabled, this allows direct chats between employees as well as group chats. If this setting is disabled, you can still share announcements.

You can also configure who employees and managers can start chats with. Select between:

  • Can't start chats

  • Staff in teams they work in

  • Staff in locations they work in

  • Anyone

Finally, you can configure your push notification settings for communications. Choose whether people receive notifications if chats or announcements are posted and if they receive push notifications while on leave.

To learn more, see our communications help guide.

Did this answer your question?