Help · Team leaders and HR

Importing salaries and contracts: add, overwrite or rebuild the history

The three modes of the salary and contract import, what each does to the history, the preview and confirmation for Rebuild, and what is inherited when the file does not bring a field.

Updated on

Help centre

In People → Import, the Update salaries and contract action updates the contract and pay of people who already exist in the app from a CSV or Excel file. It never creates employees: rows with no match are skipped.

No file yet? In the Upload step, download the salaries and contracts template as .xlsx or .csv: it has the columns this action accepts, with the names the importer recognises, and an example row to delete. See Import templates.

Who can do it

The owner and HR.

The three modes

In the Options step, you choose how to handle the history of people who already exist.

  • Add new entries (default). The current entry closes the day before the effective date and a new one is created with the file's values. The history is kept. This is the right mode for pay rises.
  • Update the existing ones (overwrite). Corrects the current entry's values without creating history. It is for cleaning up wrong data, not for pay rises.
  • Rebuild the history from the file. Each of the person's rows is an entry with its own start date, from oldest to newest, and their existing compensation history is deleted and replaced by the file's. The oldest date becomes the hire date, if the contract start is mapped.

When the same person appears in several rows, the file is their history: Rebuild is selected and the other two modes are unavailable.

Preview and confirmation for Rebuild

Rebuild deletes entries, so Selfcare first shows what will happen:

  1. With Rebuild selected, the button in the Options step becomes Review and rebuild the history.
  2. The preview opens. For each person you see the file rows, the current entries (which will be deleted) and the new ones, with start, end, reason, base salary, Coverflex, expense allowance and IHT (exemption from working hours). If the hire date changes, that shows too.
  3. Anyone with closed payslips appears with the warning and is not changed. Rows without a date or base salary appear with the problem.
  4. Tick I understand that these people's current entries will be deleted and click Rebuild the history of N people.

The confirmation is also checked on the server: if the file, the mapping or the fields change after the preview, the import is refused and you have to review again. Everything runs in a single transaction: if anything fails, nothing is changed.

What is inherited when the file does not bring a field

A column you do not map never deletes data.

  • With Add and Overwrite, whatever the file does not bring stays as in the current entry.
  • With Rebuild, each new entry inherits from the person's most recent entry: paid months, meal allowance (subsídio de alimentação), seniority bonus (diuturnidades) and other components. It also inherits the Coverflex wallet, the expense allowance and the IHT when those columns are not mapped.

The preview lists the inherited terms.

Hire date and holidays

If the import changes the contract start date (with Rebuild, the oldest date in the file; with Overwrite, the contract start column), the person's year-end holiday closures are recalculated with the new date.

Audit log

Each entry deleted and each entry created by Rebuild is recorded in the audit log, one by one, with the values before and after. The IBAN never appears in the log or in the preview.

Not using Selfcare yet?

In a 45-minute demo we show you holiday requests, expenses and payslips.

Importing salaries and contracts: add, overwrite or rebuild the history · Help centre · Selfcare