Skip to main content

Importing employees into a budget plan from Excel

How to download an Excel template with the fields you choose in Workforce Cost Forecast, upload your own payroll file without the template and map its columns (with AI), save the mapping, upload the file and see errors and warnings row by row, download…

This article explains how to bring employees into a budget plan from an Excel file. Use it for a structure that has no employees in Teamso (a new branch, a hypothetical team) or to add people from a list outside Teamso. The plan's owner, a person it is shared with as Can edit, and people with Workforce Cost Forecast Admin do this; a person in View mode cannot upload files.

Values from Excel are written to this budget plan only; employee records in Teamso do not change. The uploaded file is not stored. First name, last name, national id and registry number are never sent to the calculation service.

Before you start

Step by step

Preparing the template

  1. Click Employee import in the plan's step strip.

    Employee import step and the last applied file
  2. Click Download Excel template. The Prepare the Excel template window opens.

  3. Choose the fields to add to the template. Type in Search fields to find a field, or click Select all to add every field. The counter shows how many fields you chose (e.g. 13 / 86 fields selected).

    • Fields marked Required are always in the template and cannot be removed: First name, Last name, Start period, End period, Company, Workplace, Salary, Salary type, Pay period.

    • The cost centre columns (CC name, CC code, CC percentage) are added together.

    Prepare the Excel template window with the field picker
  4. Click Download template. The file has three sheets:

    • Employees: the columns you chose. Columns with options (Salary type, Incentive law, Yes/No fields) have a drop-down list on rows 2 to 1001.

    • Notes: the meaning of every column, whether it is required and its valid values.

    • Lists: the values of the drop-down lists.

  5. Fill in the template. Each row is one employee.

    • Dates are DD.MM.YYYY, periods MM.YYYY (e.g. 01.2027). For an employee who starts or leaves within a month you may write the full date in the period column.

    • An empty Pay currency means TL. For a USD, EUR or GBP salary without a rate in the row, the plan's exchange rate assumption is used; a rate in the row applies to that employee.

    • For several cost centres separate the values with a semicolon (e.g. CC name "Sales;Marketing", CC percentage "60;40"). The percentages add up to 100; for a single cost centre an empty percentage counts as 100.

    • When Workplace equals the name of a Teamso branch the row is linked to that branch; otherwise it stays as free text.

Uploading and previewing the file

  1. Click Choose and upload a file (or Upload a new file if you uploaded one before).

  2. In an Excel plan that already has employees, the Existing data will be deleted window opens: the new file deletes every employee detail and the employee level timesheet, expense and increase scenarios. Click Upload file to continue.

    Existing data will be deleted warning
  3. Drag and drop your file or click to choose it, then click Continue.

  4. If the file is not the Teamso template (your own payroll or staff export), the Column mapping step opens; see Mapping your own file below. If you saved a mapping for a file with the same header structure before, this step is skipped and the preview shows "Saved mapping applied."; Change mapping takes you back to the mapping step.

  5. The Preview step shows the status of every row:

    • Valid: the row is applied as it is.

    • Warning: the row is applied, but a value was adjusted. For example a period outside the plan was moved to its first or last month, or the law number of a retired employee or of social security document type 2 was set to 0000.

    • Error: the file cannot be applied until the row is fixed. What happened, what to do names the column and what to enter.

    Valid, warning and error rows in the preview
  6. While a row has an error, Apply is disabled. Click Download rows with errors as Excel: the file is the one you uploaded with an Errors and warnings column at the end (errors red, warnings yellow) and an Errors sheet. Fix the file; you do not need to delete the added column.

  7. Upload the fixed file with Choose another file and click Continue.

  8. When no error is left, click Apply. The rows you saw in the preview are written as they are; a message such as "38 rows applied; 3 rows imported with a warning" appears.

Mapping your own file (Column mapping)

You can upload the file from your accounting or HR software without turning it into the template. Headers such as "Adı Soyadı", "TCKN", "Gross salary" or "Hire date" are mapped free of charge with Teamso's dictionary. AI is used for the columns the dictionary cannot map or is unsure about; it only gets the header and at most 5 sample values of those columns. Values of personal columns such as names, national id, registry number, birth date, phone, e-mail and IBAN are never sent to AI, only their shape. First and last name columns ("Personelin ismi", "Personelin soy ismi") are recognised free of charge from the words of their headers, and a column of valid Turkish national ids ("Kimlik") from its values, even when the dictionary does not know the header; AI is not asked about them. When the field AI proposes does not fit the values of the column (Salary type for a column of amounts, the salary for a column of "brüt" and "net"), the proposal is not taken and the column keeps the dictionary's proposal or stays unmapped.

  1. The band at the top says how many columns are mapped. If a column is left open, the digital credit confirmation opens when you click Continue; if you confirm, AI maps the remaining columns (1 digital credit per mapping, once for the same file). If you do not confirm, or AI is not available right now, you map the columns yourself and no credit is used. Map with AI runs AI later. If you upload the same file again, the AI mapping is reused without a new credit, and the band says so. If AI features are turned off for your company, the AI option is not shown.

    Column mapping step: sample values, proposed field and confidence
  2. Sample values shows the first values of each column; personal columns show "Personal data, kept hidden".

  3. In Field you can change the proposed field in the list. Choose Do not import for a column you do not need (a note, a phone) and First and last name (one column, split) when first and last name are in one column; the last word is taken as the last name. A value transform shows under the field, e.g. "Number format: 1.250,50", "Values: B → Gross, N → Net" or "Month format: MMMM yyyy" ("Ocak 2027" is read as 01.2027).

  4. Confidence shows how sure the proposal is (High, Medium, Low) and where it came from (Dictionary, AI suggestion, Saved mapping). A row you changed shows Your choice. Check the medium and low rows.

  5. Values for all rows lists the required fields your file does not have (e.g. End period, Company, Workplace, Pay period). No default is set silently; choose the value written to all rows for each. A value taken from a header such as "Monthly Gross Salary" is preselected and says which header suggested it. If a required column has empty cells (e.g. a leaving date filled only for leavers), the value you choose is written to the empty rows only. First name, Last name and Salary need a column of the file.

    Values for all rows and saving the mapping
  6. With Save this mapping ticked, enter a Mapping name (e.g. "Accounting staff file"). The mapping is saved for your company when you apply the file; a file with the same header structure is then mapped without asking and without AI.

  7. Click Go to preview. Preview and apply work as in the steps above.

Managing saved mappings

In the file step, Saved mappings appears when your company has saved mappings.

  1. The list shows each mapping's name, number of columns, how often it was used and the file's headers.

  2. The person who saved a mapping or a module admin can rename it with the pencil and delete it with the bin. After a mapping is deleted, files with its header structure are mapped again.

    Saved mappings window

Excel in a Teamso plan

In a plan opened with Teamso data, Add from Excel in the Data sources step opens the same window. There are two kinds of Excel import; you choose in the file step:

  • Add new employees: the rows become new employees from "Excel" next to the employees that came from Teamso. A national id already in the plan is an error.

  • Update existing employees: rows are matched to the plan's employees by Registry no or National id. Only the cells you filled are written and marked as your values; the Teamso value is kept and you can go back to it in the grid. Rows without a match are listed as Not applied. The file needs a registry number or national id column.

Result

The applied employees appear in the plan's Employee details step and the report is marked for recalculation. The Employee import step shows the name, row count and date of the last applied file. An Excel plan has no Actuals step, because no employee matches the Teamso payroll.

Common problems

Symptom: "No column headers found."
​Cause: The header row of the template was deleted, or the first rows have no recognised header.
​Fix: Put the header row back, or download a new template and move the values into it.

Symptom: "No employee rows found."
​Cause: There is no filled row under the header row.
​Fix: Add at least one employee row.

Symptom: A column shows Not mapped in the Column mapping step.
​Cause: The header is not in the dictionary and AI was not used, or AI found no field either.
​Fix: Map the column to a field in the list or choose Do not import.

Symptom: "AI is not available right now; no credit was used."
​Cause: The AI service cannot be reached at the moment.
​Fix: Map the columns yourself or click Map with AI again shortly.

Symptom: "This file could not be mapped with AI because of the personal data in it; no credit was used."
​Cause: Although the values of personal columns go as their shape only, a person's data was still in the request, so Teamso did not send it to AI. Trying again does not change the result.
​Fix: Map the columns yourself. Map with AI is not offered again for this file.

Symptom: Go to preview is disabled and says "Choose a value for all rows of the required fields".
​Cause: No value was chosen for a required field the file does not have.
​Fix: Choose a value for each field under Values for all rows.

Symptom: The preview shows an error such as ""Half" is not valid for Salary type."
​Cause: A value of a column with options matches no option.
​Fix: Correct the value in the file; abbreviations such as "B", "N" or "Monthly" are mapped automatically.

Symptom: "This national id is also in row 4."
​Cause: The same person is in the file twice.
​Fix: Delete one of the rows.

Symptom: "The national id is not valid."
​Cause: The number is not 11 digits or its check digits do not match.
​Fix: Check the number; if you do not know it, leave the column empty.

Symptom: "Cost centre percentages must add up to 100".
​Cause: The percentages separated by semicolons do not add up to 100.
​Fix: Correct them so that they add up to 100.

Symptom: "A file may have at most 5,000 employee rows".
​Cause: The file is over the limit.
​Fix: Remove rows; for a larger team consider splitting the plan.

Related articles

Did this answer your question?