# Integration overview

An integration has two parts: a **build path**, which decides who builds the user interface, and the **integration topics**, which you work through in order. Each topic page starts with an overview, then shows the options under "Which fits you?". Skip the options that do not apply to you.

## Choose your build path

*Diagram: Two build paths side by side. Embedded Salaxy UI: Salaxy Business for companies and Salaxy Pro for accounting firms run inside your product, in an iframe or opened from it with single sign-on; less work. Your own UI: you build the screens on the REST API; more work. In both paths the Salaxy payroll engine does the calculation, the payments and the Incomes Register filing. Under it, your payment channel can fetch the invoices, pay them and report back. (Purple: Salaxy builds it. Grey: you build it. The payroll engine is the same in both paths; the payment channel is optional in each.)*

| | 1. Embedded Salaxy UI | 2. Your own UI |
|---|---|---|
| **Who builds the UI** | Salaxy: **Salaxy Business** for companies and **Salaxy Pro** for accounting firms, in an iframe in your product under your own design, or at least opened from your product with single sign-on | You, on the REST API |
| **What you build** | Single sign-on for your users, customer account creation (and accounting firm accounts for Salaxy Pro), and usually a payment channel and the monthly accounting data pull. Employees and payrolls are done in the Salaxy UI | Every payroll screen: customer onboarding, employments, payrolls and calculations, and the payment status. Salaxy's onboarding screens can handle the company's sign-up |
| **Effort** | Less | More |
| **Example** | A property management, accounting or financial management system that adds payroll for its customers and their accounting firms | A financial or HR app with its own payroll screens |
| **Start with** | [Embedded white label](https://code.salaxy.com/white-label/index.md) | [REST API — getting started](https://code.salaxy.com/get-started/rest/index.md) |

Both paths are **Finland only**. For other countries, and for anything conversational, use the agentic path: see [MCP or REST?](https://code.salaxy.com/about/mcp-or-rest.md). An agent can also do a single job inside either path — for example, a payroll assistant inside your product.

**Paths can be combined.** For example, an embedded integration also imports workers or worktime through the API ([Worktime import](https://code.salaxy.com/integration/worktime-import.md)), or your own UI covers some tasks and the embedded Salaxy UI the rest.

Salaxy Pro also works standalone: accounting firms sign in to it directly. That is not an integration, so it is not a build path here.

## What every integration needs

Salaxy sets these up with you once, before you build. Each has its own topic page.

| Item | Who does what | Topic |
|---|---|---|
| Partner account and technical accounts | Salaxy creates them; you create the certificate your backend signs with | [Partner and technical accounts](https://code.salaxy.com/integration/partner-account.md) |
| Service model | Salaxy sets it up: what the customer companies you bring get, and what is locked | [Service models](https://code.salaxy.com/integration/service-models.md) |
| Payment channel | Salaxy pays from a customer funds account, or your channel pays; you build your channel | [Payment channels and SEPA payment files](https://code.salaxy.com/integration/payment-channels.md) |
| Accounting model | Salaxy sets it up: where the accounting entries go | [Accounting models](https://code.salaxy.com/integration/accounting-models.md) |

## Partner or company?

- **Partner:** you serve many customer companies, often through their accounting firms. You need the one-time setup topics below. If accounting firms sit between you and the companies (three-tier), you also need the [Pro API](https://code.salaxy.com/integration/pro-api.md) for the accounting firm view.
- **Company:** you connect your own systems to your own Salaxy account. You can skip most of the one-time setup.

## Integration topics

The topics are in the order an integration usually goes. Some topics say which build paths need them; the others apply to every path. Building with a coding agent? Start with [Integration in a day with a coding agent](https://code.salaxy.com/integration/with-a-coding-agent.md).

**1. Setup and onboarding (one-time)**
- [Partner and technical accounts](https://code.salaxy.com/integration/partner-account.md) — your partner account, technical accounts and certificate
- [Account structure](https://code.salaxy.com/integration/account-structure.md) — partner → company, partner → accounting firm → company, or mixed
- [Contract options](https://code.salaxy.com/integration/contract-options.md) — how a customer company authorises Salaxy
- [Service models](https://code.salaxy.com/integration/service-models.md) — what Salaxy fixes for the companies you bring
- [Payment channels and SEPA payment files](https://code.salaxy.com/integration/payment-channels.md) — who pays the salaries, and how
- [Accounting models](https://code.salaxy.com/integration/accounting-models.md) — where the accounting entries go
- [Customer account creation](https://code.salaxy.com/integration/customer-accounts.md) — create or assure a customer company account
- [Company settings](https://code.salaxy.com/integration/company-settings.md) — for your own UI; the Salaxy UIs have their own settings screens
- [Accounting firm account creation](https://code.salaxy.com/integration/accounting-firm-accounts.md) — an accounting firm account, with its customer companies under it
- [Pro API (accounting firm tier)](https://code.salaxy.com/integration/pro-api.md) — one view over every customer company of an accounting firm

**2. People** — for your own UI; in the Salaxy UIs, employees are kept on screen, unless you import them
- [Employees and employments](https://code.salaxy.com/integration/employments.md)
- [Tax cards](https://code.salaxy.com/integration/tax-cards.md)
- [Dimensions (cost centres)](https://code.salaxy.com/integration/dimensions.md)
- [Worktime import](https://code.salaxy.com/integration/worktime-import.md)

**3. Payroll**
- [Payroll lifecycle and statuses](https://code.salaxy.com/integration/payroll-lifecycle.md)
- [Salary calculations](https://code.salaxy.com/integration/calculations.md) — for your own UI; in the Salaxy UIs, payroll is done on screen

**4. Payments**
- [Invoices and payments](https://code.salaxy.com/integration/invoices-and-payments.md)

**5. Reporting and filings**
- [Accounting data](https://code.salaxy.com/integration/accounting-data.md)
- [Holiday pay debt](https://code.salaxy.com/integration/holiday-pay-debt.md)
- [Monthly cycle](https://code.salaxy.com/integration/monthly-cycle.md) — the reports and invoices Salaxy makes each month
- [Incomes Register filing](https://code.salaxy.com/integration/incomes-register.md) — earnings payment reports, which Salaxy files for you

**6. Optional features**
- [Salary slips and e-payslips](https://code.salaxy.com/integration/salary-slips.md)
- [Messages and notifications](https://code.salaxy.com/integration/messages-and-notifications.md) — message threads, and the notice to the worker after payment
- [Events from the embedded white label](https://code.salaxy.com/white-label/events.md) — what the payroll UI tells your page

**7. Go live**
- [Go-live checklist](https://code.salaxy.com/integration/go-live.md)

## The API rules

Every REST integration follows the same rules for [errors](https://code.salaxy.com/reference/errors.md), [queries and paging](https://code.salaxy.com/reference/queries.md), [retries and idempotency](https://code.salaxy.com/reference/idempotency.md), and [events and polling](https://code.salaxy.com/reference/polling.md). They are in the Reference, next to the [REST API reference](https://code.salaxy.com/reference/rest-api.md).
