Skip to main content
People move house, get a new tax code or change their hours. You record each change from the date it applies, one satellite at a time, and Intermezzo keeps the history. The rules are in Changing data; this page walks through the common cases.

Example: the tax code changes from 1 December

1

Read the satellite

2

Send the whole satellite from the new date

Send every field of tax, with valid_from set to the date of the change and If-Match set to the ETag you read.
Request
Request body
3

Check the timeline

The PUT returns 200 with the new edition. Get Tax Editions now shows 1257L from 2026-04-06 to 2026-12-01, and 1263L from 2026-12-01.
HMRC also changes tax. When HMRC sends a new tax code or a student loan notice, Intermezzo writes a new edition with created_by set to the notice, for example hmrc:P6. If that happens between your GET and your PUT, the PUT returns 412 EDITION_MISMATCH: read the satellite again and decide whether your change still applies. The other satellites work the same way: Create Core Edition, Create Address Edition, Create Job Edition, Create Insurance Edition, Create Bank Edition.

Standing pay

Salary and other pay that is paid every period lives in the compensation satellite; see Compensation.