> ## 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.
# Horizon
> Configure Horizon payroll types and exchange hours, absences and employee data.
export const BetaCallout = ({children}) => ;
Connect Horizon to send payroll data and read selected employee and contract details back into Begin. Have your Horizon administrator supply the connection details and the document and pay-type IDs your installation uses.
Payroll integrations are rolling out gradually. If **Settings → Integrations** is missing, ask us
about enabling it for your workspace. Your role also needs permission to manage integrations.
## Connect Horizon
Open **Settings → Integrations → Horizon** and turn on the header switch. This creates the setup
and opens **Setup**; the switch stays off until credentials are saved.
Enter **API URL**, **Username** and **Password**, choose **Save credentials**, then turn the
header switch on.
In **Advanced settings**, pick the salary document type for hourly and for monthly-paid people
from the lists Begin loads from your Horizon. If a list does not load, enter the ID your Horizon
administrator gives you. Pay-type IDs are optional; leave them blank unless the document type
does not pre-fill them.
Enable the required groups: **Hours and pay**, **Absences**, **Employee details** or
**Contracts**. Select which imported fields may update Begin.
## Match people and absences
Check personal codes in both systems before the first run. An employee must be matched in Horizon before their absence can be sent.
In **Field mappings**, map absence policies to the Horizon document types your payroll team uses. Horizon absence documents carry whole days: partial-day absences are skipped and named in the run’s errors.
Leave **Include unconfirmed hours** off to send approved hours only. Rejected and cancelled hours are always excluded, even when this setting is on. Imports update existing people and imported job records. They preserve job and pay rows created or edited by hand, and do not add everyone held in Horizon to Begin.
## Check the first result
Run one month from **Sync** and read the result before enabling automatic runs. Missing salary document types stop the relevant export; a missing type for one pay group can leave only some people processed.
If the run reports unverified pay types, ask your Horizon administrator to check the configured IDs. A successful connection alone does not prove that the document types or employee matches are correct.
**Horizon: access and limits**
* **Who can:** the default Administrator role manages integrations; Manager and Employee do not. A custom role can carry that permission.
* **Where:** integration access is controlled per role in **Settings → Permissions**.
* **Not supported:** Horizon has no reviewed Add people import like Merit Palk’s, and no contract-export data group.
* **Limits:** the run reports skipped absences with missing personal codes, unmatched employees, unmapped policies or unrecognised document types.
## Next
Choose a month, run it and check the result.
Compare providers and connection methods.
## Still need help?
Email the Begin team and we'll get back to you.
Open the AI assistant and get instant answers based on these docs.