Skip to main content

Add timesheet scenarios (premiums, bonuses, benefits, overtime, deductions)

How to add payment, in kind benefit, shift, deduction and exemption items for chosen scopes and months in the Timesheet step of Workforce Cost Forecast, exclude employees, resolve conflicts, upload from Excel and save.

This article explains how to define premiums, bonuses, benefits, overtime or deductions for chosen groups and months in the Timesheet step of a budget plan. Every row you add goes into the payroll calculation as an item: for example "a 20,000 TL gross sales commission for the Sales department in March, June, September and December" or "a bonus of one salary for everyone in June and December". In a plan that starts from your Teamso data, the employees' benefits arrive in this table automatically.

The plan's owner, a person it is shared with for editing, or a person with the Workforce Cost Forecast Admin responsibility can change the timesheet rows. A person it is shared with for viewing only sees the table.

Before you start

Steps

Add a timesheet row

The Suggestions from Teamso card above the step shows bonus, premium and overtime suggestions drawn from your history; add one as a row with Add, or fill the form below with its values using Edit and add (Suggestions from Teamso).

  1. In the budget plan, open the Timesheet step in the step strip. On a short screen the add form starts closed when the list has rows; click Add a row in the card header to open it.

    Timesheet add row
  2. In Scope, choose who the row applies to: All employees, Employee, Position, Department, Company, Workplace or Timesheet type. For any type but All employees, choose one or more values in the field next to it.

  3. In Item, choose the item. Items are grouped by type: Payments, In kind benefits, Shifts and days, Deductions, Exemptions and carried over values. Type in the search box to find one. If you choose an item that is being phased out because of a legal change, the field says from which month it should not be used.

  4. Enter the value. The field's name follows the item: Amount for payments and deductions (per person, TRY), Days for regular work (at most 31), Hours for hour items (at most 232.5), Multiplier for a salary multiplier.

  5. For payments and in kind benefits, choose the Payment type: Gross, Net or Salary multiplier for payments, Net or Salary multiplier for in kind benefits. With Salary multiplier the value field takes a multiple of the salary with an "x" prefix (default 0.5, from 0.01 to 24); x1 is a bonus of one salary. Shift, deduction and exemption items have no payment type.

  6. In Period, keep All months or choose the months the row applies to.

  7. Click Add. The row is added at the end of the table with a dot that shows it is not saved. If the report was calculated at least once, the line under the fields shows the approximate effect of the row on the yearly cost and its percentage; before that it shows how many employees and employee months the row reaches and, for money items, its approximate amount (See the estimated cost effect of a change).

The same row (same item, scope, months, value and payment type) cannot be added twice: This scenario already exists. appears.

Regular work (days) cannot go to hourly paid employees, and Regular work (hours) cannot go to monthly or daily paid ones. If the scope has such an employee, saving shows a message like Regular work (days) cannot be assigned to employees paid hourly.; narrow the scope or exclude those employees.

Exclude employees

If a row with a department, position, company, workplace or timesheet type scope should not apply to some people in that group, exclude them.

  1. Click Exclude employees under the scope of the add row, or the same button in the Actions column of a table row.

    Exclude employees dialog
  2. The dialog shows how many employees are in the scope and how many are excluded. You can search by name.

  3. Tick the employees to exclude.

  4. Click Save. The row shows a note such as "1 excluded" under its scope.

An excluded employee does not get the item from this row; if another row applies to them, that row is used. For regular work items, an excluded employee does not get their working days from this row and their salary is not set to zero.

Use the table

Timesheet table
  1. Turn on Show carried over values above the table to see the values carried over from Teamso (cumulative income tax base, social security base carried from earlier months). These rows apply to the first month only and cannot be changed.

  2. The Import menu in the card header holds Sample Excel, Upload Excel and Add from library; Sample Excel downloads the timesheet template (see "Upload from Excel" below).

  3. A group scope row shows the number of excluded employees under its scope.

  4. An item being phased out shows from which month it should not be used. The months from then on are not sent to the calculation; we recommend changing the item.

  5. The Source column shows where a row comes from: Teamso benefit, Teamso payment, Added manually, Excel, Suggestion, AI suggestion, Library (a set added from the scenario library) or Changed (a row from Teamso you changed later). Select rows and use Save to library to keep them as a set, or Add from library in the Import menu to add a ready set (Scenario library). A row from Teamso you change or delete is not brought back by the next Teamso import.

Edit a row with the pencil icon, copy it right below with the copy icon, delete it with the bin icon. The search box, the Source and Item type filters and the sort in the column headers help you narrow the table.

Save and scenario conflicts

  1. Your changes are saved at once when you click Save or Next at the bottom of the page, and Timesheet scenarios saved appears. If a row is incomplete or invalid, no row is saved: Could not save. Fix the marked rows. appears and the rows with problems are marked.

  2. If the same item matches the same employee in the same month from more than one row, the Scenario conflict dialog opens.

    Scenario conflict dialog

    It shows which rows conflict, the employees and months affected, and which row applies. The rule: the most specific scope wins (employee, timesheet type, position, department, workplace, company, all employees, in this order). With equal scopes, the row higher in the list wins. Amounts are not added up. A month choice does not make a scope more specific: an "All months" row higher in the list wins over a "June only" row below it.

  3. Click Save with this rule to continue with this rule. Click Edit to change the rows; the conflicting rows are marked and opened for editing.

  4. If you move to another step without saving, the Unsaved changes dialog opens. Your changes are also kept as a draft in this browser.

Upload from Excel

  1. In the Import menu click Sample Excel to download the template. Its Timesheet sheet has these columns: Employee id (the Teamso registry number or the row number in the plan), Full name (optional), Item (from the list), Period (MM.YYYY, e.g. 03.2027), Amount, Payment type (Gross, Net or Salary multiplier; empty for shift, deduction and exemption items). The employee ids are on the Employees sheet.

  2. Write one item for one month of one employee on each row.

  3. In the Import menu click Upload Excel, choose the file and click Upload Excel.

  4. If the file is valid, its rows are added at the end of the table with the Excel source. Remember to save the table.

  5. If the file has an invalid value, no row of the file is added and the Invalid values dialog opens.

    Invalid values dialog

    The table shows the row number, employee id, error type and value: Employee not found, Invalid period, Invalid item, Invalid payment type, Invalid amount, Duplicate row or Salary period does not fit. Use the Error type filter to see one type. Rows with an empty amount are errors too. Fix the file and upload it again with Choose another file.

  6. If the column headers differ from the template, the Invalid file headers dialog shows the Expected columns next to the Columns in the file.

Result

Saved timesheet rows mark the plan as needing recalculation. When the report is created, each row is added as a payroll item to the chosen months of the employees in its scope. A salary multiplier multiplies that month's salary (after increases); for daily and hourly paid employees it applies to the monthly equivalent salary (daily wage x 30, hourly wage x 225).

Troubleshooting

Symptom: 3 rows of employees you may not see are not shown; they stay in the budget. appears.
​Cause: These rows are Teamso payments of employees in branches you are not responsible for, or whose salary you may not see.
​Fix: Nothing to do. The rows are used in the calculation and are not deleted when you save; seeing them needs the branch responsibility and the salary viewing permission.

Symptom: This scenario already exists. appears.
​Cause: A row with the same item, scope, months, value and payment type exists.
​Fix: Edit the existing row or choose other months or another scope.

Symptom: Saving shows ... cannot be assigned to employees paid ....
​Cause: An employee in the scope is paid by a period that does not fit the item (a day item for an hourly paid person or an hour item for a monthly paid one).
​Fix: Narrow the scope, exclude that employee or choose the fitting item.

Symptom: The Scenario conflict dialog opens when you save.
​Cause: The same item matches the same employee in the same month from more than one row.
​Fix: Check the row that applies by the rule in the dialog; click Save with this rule if it is right, otherwise Edit the rows.

Symptom: The Invalid values table lists Employee not found rows.
​Cause: The employee id is not the registry number or row number of an employee in the plan, or the employee was removed from the plan.
​Fix: Copy the id from the Employees sheet of the template.

Related articles

Did this answer your question?