How salary changes propagate

A salary change, step by step

Jane was on £45,000. Her manager bumps her to £50,000 effective 1 August 2026.

In HR

1. Open Jane's employee detail page > Contracts tab.
2. Click New contract.
3. Set:
   • Effective from: 1 August 2026
   • Gross salary: 50000 (other fields copy from her current contract)
4. Save.

Jane's contract history now shows two rows: the old one (closed on 31 July) and the new active one (from 1 August). Her record never loses the history of what she was paid before.

In Finance, a few seconds later

• Settings > Team — Jane's row shows £50,000
• Reports > P&L projection — August onwards reflects the new salary
• Reports > Cash flow — the August payroll outflow goes up accordingly

You don't need to do anything in Finance. There's no "sync" button or "import" step.

How fast is it?

Usually within a few seconds. Under heavy load, it can take up to a minute. Refresh if you don't see it immediately.

What if I backdate the change?

You can set the effective date to a past date. HR's contract history will record the back-date correctly, and Finance's "current" view updates straight away.

For historical reports that were already produced (e.g. last month's P&L), the figures use the salary that was in force at the time. If you want them re-run with the corrected salary, open the report and click Refresh.

What if the change is for the future?

Set the effective date in the future (e.g. "effective 1 October"). Jane's current salary stays as £45,000 in both products until 1 October, when she automatically transitions to £50,000.

Multiple changes

If you change Jane's salary again before the first change took effect (e.g. you made a typo), just create another new contract. The system handles overlapping correctly and only the most-recent change is "active" at any given date.

Next

Chapter 4 covers the rare cases where something hasn't flowed through and what to do.