> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Pay Premium

> Send worked hours and leave to Pay Premium (Finvalda) over its API.

![Pay Premium in Begin](https://mintcdn.com/beginltd/McvKODNCR83M5cZk/images/cover/integrations-pay-premium-light.png?fit=max\&auto=format\&n=McvKODNCR83M5cZk\&q=85\&s=7a6937a6a0be0fb26db7a96fe6ce3e99)

Send each person's worked hours and leave for a month to Pay Premium, the Finvalda payroll system. Begin writes the hours into the Pay Premium timesheet and the leave as leave records, which Pay Premium then books through its own rules.

Your role needs permission to manage integrations to open **Settings → Integrations**.

## Connect Pay Premium

**1. Get the API details**

Ask whoever runs your Pay Premium server for the AlgosWebService address (it ends in
`AlgosWebService.svc`), an API user and its password, and the database name of your company. The
address must be reachable from the internet over HTTPS.

**2. Enter them in Begin**

Open **Settings → Integrations → Pay Premium** and choose **Connect** under **Connection**. Fill
in **API URL**, **Username**, **Password** and **Database name**, then save.

**3. Match people**

Set each person's **Payroll export code** on their
[profile](https://docs.begin.eu/for-managers/people/member-profiles.md) to their employee code in Pay Premium. A person
without one, or with a code Pay Premium does not know, is left out and counted in the run's
details.

**4. Check the codes**

Open **Field mappings**. Worked hours go under FD, rest-day work under DP, holiday work under DŠ
and overtime under VD. Change a code if your company uses another, and map each absence type to
its Pay Premium code to send leave too.

## What is sent

Each worked day becomes one timesheet row per code, in minutes, with the night part of the worked time in its own column. The row goes on the person's contract in force that day. When a person has several contracts that day, Begin picks the one employment contract; if there is no single one, that person is not sent and the run says so. When overtime has no code, overtime hours go under the worked-hours code.

Leave goes as a leave record, one per absence. Code `A` is booked as annual leave and code `L` as sick leave; any other code is sent as an unpaid or special period of that code. Only whole-day absences are sent. An absence that lasts part of a day is counted in the run's details for you to enter in Pay Premium by hand, and the run ends with a warning. Annual leave or an unpaid period that runs from one contract into the next is not sent; the run names it so you can enter it by hand.

## Run a month

In **Manual run**, pick a whole month and start it. This integration has no schedule. Leave **Include unconfirmed hours** off in **Advanced settings** unless payroll should include work that has not been approved.

Before sending, Begin reads what Pay Premium already holds for that month and sends only what is missing. Running the same month again is safe: a day already there with the same minutes is skipped. A day Pay Premium holds with different minutes, or a leave record over the same days that differs, is not overwritten; the run names it so you can correct it in Pay Premium.

The run stops before sending anything when Pay Premium does not know one of the mapped work-time codes, when two people share an export code, or when the Pay Premium API is older than version 15.

**Pay Premium: access and limits**

* **Who can:** the default Administrator role manages integrations; Manager and Employee do not. A custom role can carry that permission.
* **Where:** **Settings → Integrations → Pay Premium**; integration access per role is in **Settings → Permissions**.
* **Not supported:** creating new employees in Pay Premium, changing or deleting leave Pay Premium already holds, scheduled runs, and part-month periods.
* **Limits:** rows Pay Premium has already imported into its payroll calculation are refused by Pay Premium and named in the run's details. A send that Pay Premium did not answer in time may already be stored; running the month again skips what it holds. The run details keep the first 50 errors.

## Next

> [card] [Run the integration](https://docs.begin.eu/for-managers/integrations/running-payroll-integrations.md)
>
> Choose a month, run it and check the result.

> [card] [Choose an integration](https://docs.begin.eu/for-managers/integrations/available-integrations.md)
>
> Compare providers and connection methods.

## Still need help?

> [card] [Contact support](mailto:support@heybegin.eu)
>
> Email the Begin team and we'll get back to you.

> [card] [Ask Begin AI](?assistant=open)
>
> Open the AI assistant and get instant answers based on these docs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.