Embedded Into Your Platform
Payroll as a Native Feature in Your Platform
Ason enables you to offer payroll as a fully integrated feature within your platform. Instead of redirecting users to external systems or building payroll yourself, Ason runs payroll in the background - while your platform remains the single interface for your users.
API-First Payroll Engine
Your platform connects to Ason's payroll engine via API.
Your platform:
- Manages users, employees, contracts, and any relevant data
- Sends payroll-relevant case changes (e.g. changes, hours, absences)
- Triggers payroll runs
Ason:
- Processes payroll automatically
- Applies regulatory logic
- Generates results (payslips, reports, accounting data)
All results are returned via API and, through webhooks, your platform is notified in real time - allowing you to instantly display updates directly in your UI.
Ready-to-Use Frontend (React)
To accelerate implementation, Ason provides a fully functional, open-source payroll UI built in React (see Build your own solution).
This frontend:
- Is already connected to the Ason API
- Includes standard payroll workflows and views
- Can be used as a reference implementation or directly integrated
Your engineers can:
- Reuse components
- Adapt the UI to your design system
- Embed parts of the frontend directly into your platform
This enables you to turn payroll into a native feature quickly, without building everything from scratch.
Identity & Access Management (IAM) Integration
User authentication is handled through your platform's IAM. Your backend manages access and securely connects to Ason using a system user - a Zitadel machine-to-machine token, not a human login - ensuring users are routed to the correct payroll tenant without requiring a separate login.
Processing is asynchronous: most operations return results almost in real time, while more complex operations (e.g. closing a payroll period) may take a few minutes - either way, your platform is notified via webhook once it's done.
Code
Setup 1 (Recommended): Dedicated Ason PROD instance in Ason's Azure environment.
Setup 2: Start on the Ason PROD instance and migrate to a dedicated instance later (additional effort required).
User access and data are controlled by your platform, while Ason securely executes payroll processing in the background - no system switch, no additional login, no need for payroll expertise.
Use Case: Embed in Accounting Software
If your platform is an accounting/Fibu product, embedding Ason lets you add full Swiss payroll without building payroll logic yourself:
- Your platform sends employee and salary case changes as they happen
- Ason processes payroll and returns the accounting posting document via webhook after each period close
- Your platform imports the posting document directly into the customer's ledger - no manual re-entry
See Outputs for what's in the document and how wage types map to accounts.
Use Case: Embed in Workforce Management Software
If your platform already manages time tracking, absences or shift planning, you can keep owning that data and only feed Ason what it needs for payroll:
- Your platform stays the source of truth for hours, absences and scheduling
- Relevant changes (hours worked, absences, salary changes) are reported to Ason as case changes
- Results and payslips are returned via webhook and shown in your existing UI
You don't need to duplicate anything Ason doesn't need: employee master data can stay in your system, with only the fields Ason needs for a calculation sent as case changes (see New CaseChanges), and documents like payslips or contracts can be pulled into your system via Outputs instead of living only in Ason.
Summary & Next Step
With Ason embedded in your platform:
- Payroll becomes a native feature of your product
- Your users stay entirely within your platform
- Ason runs payroll in the background as infrastructure
Ready to try it? Head to the Quickstart.
Looking for a white-label, standalone UI instead? See Standalone White-Label Solution.