# Incomes Register filing

The Finnish Incomes Register (*Tulorekisteri*) is the national earnings database. Employers must report each salary payment to it. **Salaxy does this for every customer company, automatically. You build and call nothing.**
Examples use the **test** environment; see [Environments](https://code.salaxy.com/get-started/environments.md) for demo and production.

*Diagram: Two filing flows, both done by Salaxy. Top flow: a paid salary leads to an Earnings Payment Report, EPR, filed per salary. Bottom flow: the end of the month leads to a Payer Summary Report, PSR, filed once a month on day 5. Both reach the Incomes Register. A green box at the bottom says your integration has nothing to build or call. (Purple: filed by Salaxy. The two flows are independent of each other.)*

## What Salaxy files, and what you do not need to do

| | EPR, Earnings Payment Report (*palkkatietoilmoitus*) | PSR, Payer Summary Report (*työnantajan erillisilmoitus*) |
|---|---|---|
| **Granularity** | One per paid salary calculation | One per employer per month |
| **Content** | The earnings data of the salary | The employer's monthly health insurance contribution total. It is not a list of wages: the wages go in the EPR. |
| **Trigger** | The calculation reaches `paymentSucceeded` | The [monthly cycle](https://code.salaxy.com/integration/monthly-cycle.md), day 5 |
| **Changes** | One per calculation. A correction is a cancellation and a new report. | Replaceable. A changed month is re-filed as a replacement. |

You **do not** call, trigger, schedule or poll anything. As a partner you do not need an Incomes Register certificate (an accounting firm may: see [below](#who-is-named-as-the-filer)), and you must not file the same data yourself. There is **no endpoint** to start a filing.

## When a report goes out

- **EPR.** It is created when the salary calculation reaches `paymentSucceeded`. It is reported against the **salary date**, not the date the salary was approved or paid. Salaxy sends it 4 days after the salary date, one day before the deadline, or at once if that day has already passed. Salaxy then checks the Incomes Register until it has a final answer.
- **PSR.** The day-5 run files the previous month. A salary belongs to a month by its salary date. A month with paid salaries gets a report even for one small salary. A company that paid a salary in the last 12 months and none in the month gets a zero report. A company that has never paid through Salaxy gets nothing filed until its first salary.

## Late filing: the customer carries the penalty

The deadline is **5 calendar days after the payment date**. A report that is more than 8 days late is charged a daily fee, up to an annual cap. The fee falls on the **payer, the customer company**, not on Salaxy as the filer. Households that employ as private persons are exempt.

Because the EPR uses the salary date, a salary approved or paid long after its salary date is filed at once but with an old date, and is late. If your flow can hold a salary past its salary date (a bank approval, an approval queue, a weekly batch), the customer pays the penalty. Plan for it: show the salary date clearly, and keep the gap between approval and payment short.

## Who is named as the filer

| Role | Who |
|---|---|
| **Sender** | Salaxy by default. It is the filing identity and decides the certificate used to authenticate. |
| **Payer** | The customer company. It carries the late-filing penalty. |

An account can file under another sender, for example an accounting firm under its own business ID. The firm then needs its own Incomes Register certificate in place before any filing works. Its customer companies cannot accept the [click option](https://code.salaxy.com/integration/contract-options.md#the-company-accepts-the-terms-with-a-click) or commit a payment while that certificate is missing or expired. A setting that is not a valid Finnish company ID is ignored without an error, and Salaxy stays the filer. This is arranged with Salaxy, not through your integration. The sender is read when the day-5 run executes, so a customer that moves to another accounting firm before day 5 changes who files the **previous** month. Settle this before the move.

## Switching payroll systems in the middle of a month

The Incomes Register accepts **one** monthly summary per employer and month. Two filings for the same month are not additive. For a customer that moves to or from Salaxy during a month, agree who files that month. Usually the previous provider files the whole month and Salaxy switches off its own monthly report for that month: ask Salaxy support to do it before day 5. EPRs are not affected, so salaries paid through Salaxy are still reported.

## Test it

- In test and demo, EPR filing for a normal business ID returns **mocked** answers. The filing looks successful as in production, but nothing reaches the Incomes Register. A PSR is generated but not sent.
- A successful EPR in test therefore proves your workflow, not a real filing.
- To test against the Incomes Register's own test environment, ask Salaxy support to arrange a rehearsal under one of the reserved test business IDs.

## Checklist

- Do not file to the Incomes Register yourself, and do not ask your customers to.
- Make the salary date the real pay date, and avoid holding an approved salary past it.
- Tell customers that the late-filing fee falls on them, not on you or Salaxy.
- When a customer changes accounting firm or payroll system, plan who files the month before day 5.
- Do not treat a mocked success in test as proof of a real filing.

**Next:** [Salary slips and e-payslips](https://code.salaxy.com/integration/salary-slips.md)
