This article explains how to define increases that apply from a given month in the Increases step of a budget plan: for example "a 25% raise for everyone in January and 35% for the Software department", "a 10% interim raise for everyone in July" or "the staff shuttle expense goes up 15% from September". In a plan that starts from Teamso data, the approved forward dated raises in Teamso arrive in this table by themselves.
The owner of the plan, a person the plan is shared with for editing, or a person with the Workforce Cost Forecast Admin Permission changes the increase rows. A person the plan is shared with for viewing only sees the table.
Before you start
You opened a budget plan (Create, edit, copy, share and archive a budget plan).
The employees are in the plan. You need them to choose a department, position or employee as the scope and to recognise employees in Excel.
For an expense increase, the expense must first be added in the Expenses step (Add and edit expense scenarios).
Step by step
Add an increase
In the budget plan, open the Increases step from the step bar. 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.
In Scope, choose who the increase applies to: All employees, Employee, Position, Department, Company, Workplace or Timesheet type. For any type other than all employees, choose one or more values in the field next to it.
In Target, choose what goes up: Salary, an item of the Benefits and bonuses group (e.g. Bonus, Meal card) or an expense of the plan in the Expenses group. In a plan opened with a headcount breakdown, Headcount is at the top of the list.
In Start month, choose the month the increase applies from. It applies from that month to the end of the plan.
In Increase type, choose how the increase is applied:
Percentage increase: the value is a percentage (10% by default). A negative percentage lowers the value; it must be above -100 and at most 1,000.
Add amount: the value is added to the current salary (or expense). Not available for benefits and bonuses.
New amount: the salary (or item, expense) becomes this amount.
For headcount: Add people (a negative value lowers the headcount), New count and Percentage increase.
Enter the value. The prefix follows the type: % for a percentage, TL for an amount, # for people. Salary amounts are in the employee's salary type and unit: an amount added for a net paid employee is added to the net salary, an amount added for a daily paid employee is added to the daily wage.
Click Add. The row is added at the end of the table and gets a dot that shows it is not saved yet. If the report was calculated at least once, the line under the fields shows the approximate effect of the increase on the yearly cost and its percentage; before that it shows the approximate effect on the salary (or expense) total. The effect of benefit and headcount increases shows when the report is calculated (See the estimated cost effect of a change).
A second increase for the same scope, target and start month cannot be added: This group already has an increase in this month. Edit the existing row. is shown.
Quick raise (Raise scenario template)
A plan opened with the Raise scenario template opens on this step with the Quick raise card on top.
In Raise rate enter the rate for every employee's salary.
Pick the Start month and click Add raise. A percentage increase row with the scope All employees and the target Salary is added to the table; save it with Save or Next.
To compare rates, open a copy of the plan with Copy and try another rate in the copy.
If the table already has a raise for all employees in that month, The table already has this raise for everyone in this month. is shown.
Increase rules
Rules in the Import menu and the ⓘ icon next to the step title show these rules:
If several increases meet an employee in the same month, the most specific scope wins; increases are not added up. The order is: employee, timesheet type, position, department, workplace, company, all employees. If the scopes are equal, the earlier row in the list wins.
Increases of different months are applied one after another: with 15% in January and 10% in July, a salary of 95,000 becomes 109,250 in January and 120,175 in July.
A salary below the minimum wage is raised to the minimum wage. This does not change the base of later increases.
Add amount adds to the current salary, New amount sets the salary to that amount. Add amount is based on the salary of that month (after earlier increases).
To keep one employee out of a group increase, add a 0% increase for that employee in the same month; the employee scope is the most specific.
Use the table
The Import menu in the card header holds Sample Excel, Upload Excel, Add from library and Rules; Rules shows the increase rules.
Sample Excel downloads the increase template (see "Upload from Excel" below).
You can edit the cells like in Excel: select a cell and start typing or press Enter, save with Enter, cancel with Esc. In the Increase cell you can also change the increase type. You can paste from Excel, fill down with Ctrl+D and undo with Ctrl+Z. You edit the scope with the pencil icon.
The Source column shows where the row comes from: Teamso (an approved forward dated raise in Teamso), Awaiting approval (a raise added from suggestions that is not approved in Teamso yet), Added manually, Excel, Suggestion, AI suggestion, Library (a set added from the scenario library; Scenario library) or Changed (a row from Teamso or a suggestion that you changed). If you change or delete a raise that came from Teamso, later changes in Teamso do not bring it back.
The ⓘ icon next to the step title sums up the increase rules.
You can copy a row right below it with the copy icon and delete it with the trash icon. A row whose target is no longer in the plan (e.g. its expense was deleted) or whose start month is outside the plan period is marked red and is not calculated until you fix it.
Save and scenario conflicts
Your changes are saved at once when you click Save or Next at the bottom of the page, and Increase scenarios saved is shown. If a row is invalid, no row is saved; the Not saved. Fix the marked rows. band appears.
If increases with different scopes meet the same employee in the same month and target, the Scenario conflict dialog opens.
The dialog shows which increases conflict, the employees concerned and which increase applies. For example, with 25% for everyone and 35% for the Software department in January, Software employees get 35%; increases are not added up.
To go on with this rule, click Save with this rule. To change the rows, click Edit; the conflicting rows are marked.
If a suggestion or the AI assistant (not an approved raise from Teamso) added a conflict, the Conflicts awaiting your decision band appears at the top of the step. Click Review conflicts, check the rule in the dialog and click Save with this rule. The rows do not change; the decision is kept and the readiness check no longer counts the conflict. An approved raise from Teamso wins over a group increase of the same month; it needs no confirmation.
If you go to another step without saving, the Unsaved changes dialog opens. Your changes are also kept as a draft in this browser.
Upload from Excel
In the Import menu click Sample Excel to download the template. The Increases sheet of the template has these columns: Employee ID (the Teamso registry number or the row number in the plan), Full name (optional), Target (from the list), Start month (MM.YYYY, e.g. 01.2027), Value, Increase type (Percent, Add amount or New amount). You find the employee IDs on the Employees sheet.
Write one increase for one employee on each row. Add group increases (department, position, all employees) on the screen.
In the Import menu click Upload Excel, choose the file and click Upload Excel.
If the file is valid, the rows are added at the end of the table with the Excel source. Remember to save the table.
If the file has any invalid value, no row of the file is added and the Invalid values dialog opens.
The table shows the row number, employee ID, error type and value: Employee not found, Invalid target, Invalid start month, Invalid increase type, Invalid value or Duplicate row. Use the Error type filter to see one type. Rows with an empty value are errors too. Fix the file and upload it again with Choose another file.
If the column headers differ from the template, the Invalid file headers dialog shows the Expected columns and the Columns in the file side by side.
Result
Saved increases mark the plan as "needs recalculation". When the report is created, salary and benefit increases apply to the related months of each employee; bonuses entered as a salary multiplier follow the raised salary. Expense increases apply to the expense amounts. Headcount increases change the groups' head count month by month; in the report a group's cost is multiplied by that month's head count. For the Headcount target the default scope is Workplace (Headcount based budget).
Common problems
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.
Solution: 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 group already has an increase in this month. is shown.
Cause: An increase with the same scope, target and start month already exists.
Solution: Edit the existing row or choose another month or scope.
Symptom: The Scenario conflict dialog opens when you save.
Cause: Increases with different scopes meet the same employee in the same month and target.
Solution: Check which increase applies by the rule in the dialog; if it is right, click Save with this rule, otherwise change the rows with Edit.
Symptom: Add amount cannot be chosen for a benefit or bonus.
Cause: Items can have a different amount each month, so there is no single base to add to.
Solution: Use Percentage increase or New amount.
Symptom: A row is red and says "Target removed".
Cause: The row's expense was deleted in the Expenses step.
Solution: Change the row's target or delete the row.





