AlexisHR connector

Use your AlexisHR data for reporting, automation and AI.

Data Panda pulls your AlexisHR people register, employments, time off, onboarding workflows, compensation and Nordic payroll exports into the same warehouse as your finance, sales and operations data. From one place we turn it into dashboards, automations, AI workflows and lightweight apps that HR, finance and team leads use during the month, not only the morning of a board meeting.

AlexisHR

About AlexisHR

The Stockholm HRIS for European SMBs and scale-ups, now part of Simployer One.

AlexisHR was founded in 2019 in Stockholm by Emil Kilhage, Erik Jansson and Jon Rathsman. The platform is in use at companies across more than 65 countries today, with a customer base that leans into Sweden, the Nordics and the Netherlands: Bokio, Norrsken, Zound Industries, Qred, Dryft and Modular Finance sit among the named logos. In February 2024 Simployer acquired AlexisHR, and the product has since been folded into the Simployer One suite as the HRM module. The connector itself, the API and the data model continue to operate under the Alexis name on api.alexishr.com.

The product covers the HRIS scope an SMB or scale-up expects from a single tool: employees and employments, departments, offices, teams, contracts, compensation and bonuses, time off requests, types and policies, timesheets, competences and competence levels, custom fields, onboarding and offboarding workflows and an AI chatbot that lets HR, managers and employees ask the people record in natural language. AlexisHR is ISO 27001 and SOC 2 certified, GDPR and Schrems II aligned, and stores data inside Europe. The platform plugs into the local payroll layer Nordic SMBs care most about, with named connectors for Fortnox, Kleer, Nmbrs, Crona Lon and Visma.net Payroll, plus identity (Okta, Microsoft Entra, JumpCloud, Google Workspace), recruiting (Teamtailor) and collaboration (Slack, Microsoft Teams). A REST API on api.alexishr.com with bearer-token auth and webhooks for employee created, updated, deleted, onboarded and offboarded events exposes the same data for the use cases the prebuilt connectors do not cover. In a warehouse next to your ERP, CRM and ticketing data, the Alexis record finally answers the questions an Alexis view alone does not: time-to-fully-onboarded per office, time-off concentration against delivery capacity, or whether headcount on the approved plan is keeping pace with the revenue the sales team is forecasting.

What your AlexisHR data is for

What you get once AlexisHR is connected.

HR and workforce reporting

Headcount, hiring, time off, onboarding state and compensation on one page across every office and country.

Headcount and FTE per office, department and country, against the approved plan
Time-to-fully-onboarded per role family, office and onboarding cohort
Time-off concentration per delivery team, week-by-week, against capacity

Process automation

Turn Alexis joiner, mover and leaver events into the downstream work the rest of the stack expects, without a per-tool handoff.

Provision identity and SaaS access the day a joiner record posts in Alexis
Push payroll exports (Fortnox, Nmbrs, Kleer, Crona Lon, Visma.net) into the GL per legal entity
Free SaaS seats and revoke access the moment a leaver record posts

AI workflows

Put the people record, competences and onboarding history behind AI that reads the full workforce picture.

Attrition-risk scoring on tenure, onboarding-completion and compensation signals together
Time-to-fully-onboarded forecasting per office and role family
Natural-language Q and A across the people register, contracts and policy library

Custom apps on your data

Lightweight tools on Alexis data for managers and team leads who should not need an Alexis seat to read their own team.

Manager workbench with team headcount, open roles, time-off and onboarding state
Group finance cockpit with payroll cost per legal entity and per cost centre
Onboarding tracker with the steps that consistently slip in each office

Use cases

Use cases we deliver with AlexisHR data.

A list of concrete reports, automations and AI features we have built on AlexisHR data. Pick the one that matches your situation.

Time-to-fully-onboardedDays from joiner start to onboarding workflow complete, per role, office and cohort.

Headcount-versus-planActive and pending hires against the approved plan per office, BU and country.

Time-off concentrationApproved Alexis time-off across teams and offices, mapped onto delivery capacity.

Compensation band coverageSalary and bonus records per role family and country plotted against the policy bands.

First-year attrition by officeVoluntary leavers within twelve months of hire, per office, manager and cohort.

Nordic payroll reconciliationFortnox, Nmbrs, Kleer, Crona Lon and Visma.net payroll exports tied back to the GL per entity and cost centre.

Span of control per officeDirect reports and layers per leader across every office in the group.

Document and contract coverageRequired Alexis documents and signed contracts in place per worker and country.

Competence coverage by teamRequired competences and competence levels per team plotted against the staffed roster.

Timesheet coverageSubmitted, approved and missing timesheets per worker, project and pay period.

Real business questions

Answers you will finally get.

How long does it really take to get an Alexis joiner from start date to fully onboarded?

Days between the start date in Alexis and the moment every onboarding workflow step has closed, per office, role and cohort. People ops sees the office where the median onboarding runs nine days longer than Stockholm does, and the workflow step that consistently holds the cycle, instead of trusting that the onboarding board cleared on time.

Where is time-off concentration about to push delivery past capacity?

Approved time-off in Alexis aggregated per delivery team and week, plotted against the team's committed delivery capacity. Operations sees the week where two senior backend developers and a tech lead are all out at the same time on the same project, before the project lead notices the standup is half-empty.

Are the payroll exports tying back to the general ledger per entity?

Alexis's payroll-export output for Fortnox, Nmbrs, Kleer, Crona Lon, Visma.net and the rest reconciled with the GL postings per legal entity and cost centre. Group finance sees the entities where the personnel-cost line on the management report ties back cleanly, and the ones where a manual journal still papers over an Alexis-to-GL gap, before the next group close opens that gap again.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Alexis payroll-export output per legal entity and country lined up with the GL and the headcount plan. Group close stops waiting on a Fortnox or Nmbrs payroll export per country, and the personnel-cost line on the management report ties back to the Alexis record it came from.

For sales leaders

Quota coverage against the staffed seller roster from Alexis, with start dates and onboarding state. Sales leadership sees when Nordic or Benelux mid-market falls below coverage because two AE roles slipped past their target start, before the forecast call surfaces it.

For operations

Joiner onboarding state, time-off concentration and headcount across offices in one capacity picture. The COO sees which office is letting joiners drift past day thirty without finishing onboarding and which delivery teams carry the absence concentration this quarter.

Ideas

What you can automate with AlexisHR.

AlexisHR

Pair with Slack

Drive joiner and leaver Slack moments from the Alexis timeline

Joiner records in Alexis post a welcome message on day one in the team channel and ping the manager when an onboarding step has been waiting longer than the agreed window, per office. Leaver records do the reverse: a manager ping when access revoke has not closed within the policy window, and an HR-channel summary of the cases that drifted past policy. People ops stops running a weekly handoff queue across HR and IT by hand.

AlexisHR

Pair with Okta

Drive Okta provisioning from the Alexis people record

Active employees, departments, offices and managers in Alexis drive group membership and SaaS app assignment in Okta per role and office. A joiner record in Alexis lights up the right Okta groups on day one without a ticket, a department change moves the access set the same day, and a leaver record revokes access the moment it posts. IT stops running a manual joiner-mover-leaver queue alongside the Alexis onboarding board.

AlexisHR

Pair with Fortnox

Reconcile Alexis payroll exports with Fortnox postings per entity

Alexis's Fortnox payroll-export output lands next to the Fortnox journal postings per legal entity and cost centre in the warehouse. Group finance sees the entities where the personnel-cost line on the management report ties back to the Alexis export it came from, and the ones where a manual journal still patches an Alexis-to-Fortnox gap. Group close stops waiting on a payroll-to-GL reconciliation file per Swedish entity.

AlexisHR

Pair with monday.com

Cross Alexis time-off with monday.com delivery boards

Approved time-off in Alexis lands next to the assignee, sprint and due date of every monday.com item in the warehouse. Delivery leads see the week where two assignees on the critical path are both out, the sprint that lost half its committed capacity to a planned absence, and the boards where time-off concentration explains a slipped milestone better than any retrospective ever will. The planning conversation moves up two weeks.

AlexisHR

Pair with HubSpot

Match HubSpot pipeline coverage to the Alexis-staffed sales team

Active sellers, ramp dates and territory assignments in Alexis keep the HubSpot pipeline-coverage view in sync with the staffed sales team per region. Revenue leaders see when Nordic or Benelux mid-market drops below coverage because two AE roles slipped past their target start in Alexis, weeks before the forecast call catches it. Joined to closed-won ARR per HubSpot owner, the seat cost stops being a flat licence line and becomes a number per rep that carries against the revenue they closed.

AlexisHR

Pair with Exact Online

Reconcile Alexis Nmbrs and Visma.net exports with Exact Online per entity

Alexis's Nmbrs and Visma.net payroll-export output for the Benelux and Nordic entities lands next to the Exact Online journal postings per legal entity and cost centre in the warehouse. Group finance sees the entities where the personnel-cost line on the management report ties back to the Alexis export it came from, and the ones where a manual journal still patches an Alexis-to-Exact gap. Group close stops waiting on a payroll-to-GL reconciliation file per country.

AlexisHR

Pair with Microsoft Entra

Drive Microsoft Entra group membership from the Alexis directory

Active employees, departments and managers in Alexis drive Microsoft Entra group membership and conditional-access scope per role and office. A joiner record lights up the right Entra groups on day one, a department change shifts the access set the same day, and a leaver record disables the account the moment it posts. IT stops running a manual provisioning queue alongside the Alexis onboarding board.

AlexisHR

Pair with HiBob

Read Alexis and HiBob people records side by side at group level

A group with Alexis running the Nordic and Benelux entities and HiBob running the UK or DACH entities ends up with two people records that hold half of the picture each. The warehouse holds both on a common employee key, so group HR finally sees one headcount-versus-plan, one time-to-fully-onboarded across regions, one comp-band view across both systems and one engagement-versus-attrition signal across the entire group. The board pack stops being a copy-paste exercise across two HRIS exports.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your AlexisHR data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From AlexisHR to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

AlexisHR connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Which AlexisHR tables land in the warehouse?

The connector pulls Employees and Employments, Departments, Offices, Teams and team membership, Compensation, Bonuses and Additional Compensation, Leaves, Leave Types and Leave Transactions, Timesheets and Timesheet Entries, Competences, Competence Levels and employee-competence assignments, Custom Fields and Children (dependents). Onboarding and offboarding workflow state come in via the employee onboarded and offboarded webhooks. Authentication runs through an AlexisHR REST API bearer token scoped to your tenant on api.alexishr.com, with webhooks for employee created, updated, deleted, onboarded and offboarded events.

Is this still AlexisHR or is it Simployer One now?

Both names refer to the same product. Simployer acquired AlexisHR in February 2024 and folded it into the Simployer One suite as the HRM module. The connector itself, the API host (api.alexishr.com), the bearer-token auth, the data model and the webhook event names continue to operate under the Alexis name, so a tenant set up before or after the rebrand pulls the same way. The Peliqan catalog keeps the connector under the Alexis slug for that reason.

How does it work with the Nordic and Benelux payroll partners?

AlexisHR itself plugs into Fortnox, Kleer, Nmbrs, Crona Lon and Visma.net Payroll, among others. We pull the payroll-export records that Alexis produces for those partners into the warehouse next to the GL, so the personnel-cost line on the management report ties back to the Alexis export it came from, per legal entity and cost centre. Where you also want the partner-side run records (the Nmbrs payslips, the Fortnox postings), we add the partner system as a separate connector and join on entity and pay period.

How are compensation and other sensitive Alexis fields handled?

Compensation, bonus and review-content fields can be kept in restricted schemas that only HR, finance and reward roles reach, while the directory, headcount, time-off and onboarding data powers the dashboards the rest of the business uses. Access is enforced in the warehouse, not in each dashboard, so a new operations report cannot accidentally surface a salary band it should not see.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your AlexisHR setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors