> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.heartsome.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Passing changes on to your payroll administration

Learn how, as an HR admin, to pass changes in contracts, salaries, personal details, sick reports and leave on to whoever pays your salaries.

Do you have an accountant or payroll provider who handles salaries? Then they need to know who joined, who left and whose pay changed. Heartsome makes a file for that. You don't have to keep track of it yourself or type it out.

#### Where do you find it?
Go to HR → Reports → Payroll export.

#### How does it work?
The page has two tabs: Exports, where you make and download the files, and Monthly overview, where you see per month what's changing. See "The monthly overview" below.

On the Exports tab, under What do you need? you choose between three kinds of export:
* **Baseline**: everyone as they stand now. This is the starting point for your payroll administration, and you make it once.
* **Follow-up export**: all changes since the previous export. From then on, this is the one you use every time.
* **A period of your own**: the changes entered between two dates, for example to resend a month.

| Tip: a kind that isn't available yet is greyed out. The Follow-up export is only available after your first baseline.

#### The first time: making a baseline
1. Go to HR → Reports → Payroll export.
2. Choose Baseline.
3. Click Make baseline and confirm with Make baseline.
4. You'll see the message "Your export is ready. Download it below." and the export appears under Exports.
5. Download the file (see "Downloading the file" below) and give it to your payroll administration.

The baseline includes every colleague who has a running contract now, or one that has yet to start: contracts, salaries, personal details, sick reports and leave. Is a colleague's leaving already recorded? Then the last day is in it too.

|| Note: a baseline is read from the data as it is now. You can't download it again later as it was then (see "How long is a file available?"). Moving to a different payroll provider? Then make a new baseline. You can do that with New baseline.

#### After that: making a follow-up export
Make a follow-up export when something has changed in Heartsome that your payroll administration needs to know. For example, before the monthly payroll run.
1. Go to HR → Reports → Payroll export.
2. Choose Follow-up export. Below it you'll see since when: "Changes since \[date and time]".
3. Click Make follow-up export.
4. Download the file under Exports.

Heartsome remembers where the previous export ended. The next follow-up export carries on from that moment. That way your payroll administration gets every change exactly once, even if two HR admins export at the same time.

|| Note: make two follow-up exports right after each other, and the second one will be empty. There's nothing new.

#### Exporting a period of your own
Want to resend a period without affecting the follow-up export? Then make an export for a period of your own.
1. Choose A period of your own.
2. Fill in the From date and the To date.
3. Click Export period.

A period of your own leaves the follow-up export alone. The next follow-up export still starts where the previous follow-up export ended. You don't need a baseline for this, for example if your payroll administration already has all your colleagues.

|| Note: a period of your own starts on 1 November 2026 or later. Before that, not enough was recorded to fill the file properly.

#### Downloading the file
Under Exports you'll see every export you've made, with its Kind, Period and who Made it. On the right are two buttons:
* **.csv**: for your payroll administration. This is the file a payroll system reads in.
* **.xlsx**: to read yourself. This opens in Excel.

Both files contain exactly the same.

**How long is a file available?**
* A **follow-up export** and a **period of your own** can always be downloaded again.
* A **baseline** stays available for 7 days. After that it says "No longer available". For a baseline, the date you can download it until is shown under the buttons.

| Tip: download the baseline straight away and keep it somewhere safe.

#### The monthly overview: what's changing this month?
Before a payroll run you want to know: what's changing this month, and does my payroll administration already have it? You see that on the Monthly overview tab.
1. Go to HR → Reports → Payroll export.
2. Click Monthly overview.
3. Use the arrows next to the month to move to another month.

For each colleague you see what's changing, in plain language and with the date it takes effect. For example "New employee", "Contract extended", "Salary", "Leaving the company", "Holiday payout", "Reported sick" or "Unpaid leave". At the end of each line it says whether your payroll administration has it yet:
* **Passed on \[date]**: it's in a follow-up export you made on that date.
* **Passed on with the baseline**: it was already in the baseline.
* **Not passed on yet**: it will be in your next follow-up export.

If something hasn't been passed on yet, there's an amber dot on the Monthly overview tab. Hover over it to see how many changes there are, for example "3 changes not passed on yet". The dot only appears once you've made a baseline.

| Tip: take a quick look at the monthly overview just before you make a follow-up export. You'll see exactly what's going to be in the file.

Good to know:
* **You only see what is changing, not the contents.** For personal details it says which detail changed, such as "Name" or "Address", but not the new value. For sickness you only see the stage and the date.
* **Did you undo something?** Then the undoing is a line of its own, for example "Salary reverted". The earlier change stays, because your payroll administration already received it.
* **Do you only use periods of your own?** Then Heartsome doesn't know what has been passed on already, and you won't see a status. A message above the overview says so.
* **How far back can you go?** You can go back twelve months at most. Looking ahead has no limit. A month without changes says "No changes in this month".
* A pay rise you enter well over a year in advance isn't in the monthly overview. It does go out with the export.

#### What's in the file?
The file holds a small group of rows for each change. These are the kinds of change:

| Kind of change | What it is |
| ---- | ---- |
| `baseline` | A colleague as they appear in the baseline |
| `starter` | A new colleague, with contract, salary and personal details |
| `contract_extension` | A new contract that follows on from the previous one, for example an extension |
| `contract_change` | A change to an existing contract, such as the hours or the employment type |
| `salary_change` | A different salary |
| `leaver` | A colleague leaving, with their last day |
| `holiday_payout` | Leave to be paid out or settled when someone leaves |
| `contract_deleted` | A contract that was deleted while it was running or yet to start |
| `personal_change` | A different name, date of birth, address, bank account, identification number or employee number |
| `sickness` | A sick report, a partial recovery or a full recovery |
| `leave` | Leave that affects pay: unpaid leave, a sabbatical, pregnancy, maternity, partner or parental leave |

**About sick reports:** they only hold the dates and the percentage the colleague is sick. A reason or notes are never included. Is it a relapse within four weeks? Then it says which sick report it belongs to, so your payroll administration doesn't apply new waiting days. See [Managing absence](https://help.heartsome.co/en/article/managing-absence-tftxoz/).

**About leave:** ordinary holiday and other paid types aren't included, because they're paid as normal. Every leave in the file shows the type as it's called in Heartsome. Heartsome doesn't know whether you pay that leave or not. Your payroll administration does.

**About a colleague leaving:** the last day and the leave to be paid out end up in the file automatically when you record the leaving. See [When a colleague leaves](https://help.heartsome.co/en/article/when-a-colleague-leaves-13a3r0p/) and [Settling leave when someone leaves](https://help.heartsome.co/en/article/settling-leave-when-someone-leaves-ur3zej/).

#### How do you read the file?
The file has one row for each field that changed. Rows that belong to the same change share a `change_id`. The column headings are always in English, even if you use Heartsome in Dutch. That's on purpose: a payroll system maps on those names.

| Column | What's in it |
| ---- | ---- |
| `change_id` | The number of the change. Rows with the same number belong together |
| `employee_number` | The employee number |
| `employee_id` | The colleague's number in Heartsome |
| `employee_name` | The name |
| `change_type` | The kind of change, see the table above |
| `effective_date` | From when the change applies |
| `field` | Which detail changed, for example `salary_amount` or `hours_per_week` |
| `old_value` | The value before. Empty for something new |
| `new_value` | The value after |
| `entered_at` | When the change was entered in Heartsome |
| `entered_by` | Who entered the change |
| `source` | Where the change came from, for example the contract form or the import |

A pay rise looks like this:

| change_type | effective_date | field | old_value | new_value |
| ---- | ---- | ---- | ---- | ---- |
| `salary_change` | 2026-12-01 | `salary_amount` | 3000 | 3200 |
| `salary_change` | 2026-12-01 | `salary_currency` | EUR | EUR |
| `salary_change` | 2026-12-01 | `salary_interval` | month | month |

All values are written as text in the file, so a number like an employee number or BSN keeps its leading zero.

| Tip: fill in the Employee number under People → [name] → Profile, in Payroll information, and it appears in the `employee_number` column. That helps your payroll administration find the right colleague.

#### Good to know
* **A change that was undone isn't in it.** Did you create a contract and delete it again before exporting? Then your payroll administration never hears about it. The same goes for a leaving you recorded and then cancelled.
* **A change is in the export from the day you enter it.** Enter a pay rise on 3 November that took effect on 1 November, and it appears in the first export after 3 November. `effective_date` holds the date it takes effect.
* **Only colleagues your payroll administration knows.** That means colleagues with a running contract, a contract yet to start, or one that ended this month or last month. Someone who left long ago doesn't need to be in it.
* **Two contracts at once?** Then you'll see "Two contracts running at once" at the top of the page. The export knows one contract per colleague and can't pass on both. Click the colleague's name and end one of the two contracts on Employment. See [Recording and changing contracts](https://help.heartsome.co/en/article/recording-and-changing-contracts-166b5vl/).
* **Removing a colleague your payroll administration already knows?** Then the leaving won't reach them, because removing wipes the whole history. Heartsome warns you about this and suggests recording the leaving instead. Choose Remove anyway only if you're really sure.
* **Is an export already being made?** Then you'll see "Another export is being made. Try again in a moment." Try again after a few seconds.
* **The file contains sensitive details**, such as bank account numbers, identification numbers and salaries. Share it only with your payroll administration, and not by plain email or in a group chat.

#### Who can do what?
* **HR admin and account owner**: can make and download exports.
* **Managers, Hiring admins, Billing admins and other colleagues**: don't see the page.