Publish and apply salary revisions

Before you start

Talento turns information that is often scattered across spreadsheets, documents, and isolated decisions into a connected system. You can define how work is organised, assign a contract to each employee, prepare effective-dated salary structures, and retain every compensation revision in their history.

The aim is not merely to store a salary. By connecting job positions, contracts, and salary tables, you can:

• apply consistent criteria to people doing comparable work;
• prepare future reviews without changing current remuneration;
• check who a new table will affect before applying it;
• explain where each amount came from and when it took effect;
• reduce errors involving legal entities, currencies, working time, seniority, or classification;
• provide better data for cost reports, job valuation, and pay equality.

iInformation

This guide is for administrators, HR teams, and managers with authorised access. Employees do not manage their contracts or salaries through this workflow. What each manager can review or change depends on their permission and employee scope.

Salary tables let you prepare collective agreements, internal bands, or compensation policies by legal entity and currency. Read access allows viewing; edit access allows preparing drafts; manage access allows publishing and applying revisions.

Publish a version and compare contracts

Publishing turns the draft into a permanent version. Review the date, notes, bands, amounts, and currency first. After publication, you cannot edit or delete the version; clone it as a new draft to prepare changes.

Select Compare employees to see the effect on active, visible contracts for the legal entity. Talento tries to match each contract using:

• the legal entity of the employee's office;
• the job position and its professional group;
• applicable seniority;
• workload percentage;
• the version's bands and supplements.

The comparison shows the current gross salary, minimum, reference, maximum, proposal, and difference. If every included line has a reference amount, their sum becomes the proposal. If there is no complete reference and the salary is below the minimum, Talento proposes the minimum. A salary above the maximum is flagged for review but is not reduced automatically.

Contracts without a base band, with a different legal entity, or with ambiguous associations appear as not applicable. Correct the position, entity, or table rows first, then compare again.

Apply compensation revisions

In the comparison, review each employee before selecting them. You can adjust the proposed amount and add individual notes. Then confirm Apply selected revisions.

Talento creates a separate compensation revision for every selected contract. The revision retains:

• source salary-table version;
• effective date;
• annual gross salary and currency;
• workload percentage;
• matched rows;
• annualised concepts and amounts;
• author and notes.

A reduction requires a reason. If the contract has changed since you opened the comparison, Talento rejects that application to prevent changes based on stale data; refresh the page and review it again.

Applying a table does not change the published version or any earlier revisions. It also does not change contracts that you did not select or that fall outside your access scope.

!Important

Publishing and applying are separate decisions. Publishing locks the rules; applying creates salary changes on contracts. Compare the results, validate the affected population, and confirm the effective date before applying.

Maintain data quality and permissions

Before a collective review, confirm:

1. every employee has the correct active office, legal entity, job position, and contract;
2. professional groups, families, and levels are not duplicated;
3. seniority is calculated from the intended basis in each row;
4. workload and currency are consistent;
5. non-salary concepts are excluded from annual gross salary;
6. base bands do not overlap;
7. the comparison includes exactly the expected population;
8. reviewers and people applying changes have only the permissions they need.

Separate responsibilities where possible: one person prepares the draft, another reviews the comparison, and an authorised person publishes or applies it. Record the overall reason in the version and any exceptions in the individual revision.

If a manager cannot see an employee, do not expand permissions without checking the scope. Review Permissions and visibilities and confirm that salary access and the management relationship are correct.

Result

You can check the result on the settings page, in the relevant list, or in the status described in the steps above.

Common problems

If an option is missing, check the active module, the specific permission, and the record scope. If the settings are correct and the problem continues, keep the message shown and contact support.