Introduction

Ledgy integrates with 70+ HRIS platforms — including HiBob, BambooHR, Personio, Workday, SAP SuccessFactors, Humaans, and many more — to automatically sync employee data into your Ledgy account. This article explains how the integration works under the hood, what data flows where, and answers common questions about the architecture.

For the full step-by-step setup guide, see: How do I connect and sync my HRIS system with Ledgy?

How the integration works

Ledgy connects to your HRIS through Merge, a third-party integration platform that acts as a secure middleware layer between your HR system and Ledgy.

Here's how it works:

You authorise the connection — In Ledgy, you select your HRIS provider and enter authentication credentials. This creates a secure link between your HRIS and Merge.
Merge retrieves data from your HRIS — Merge connects to your HRIS using its API and pulls employee data on a regular schedule.
Ledgy reads data from Merge — Ledgy's API retrieves the normalised employee data from Merge and stores it in a cache on the Data Sync page.
You review and sync — You preview the retrieved data on the Data Sync page and manually trigger a sync to push it into your Ledgy stakeholder records.

This architecture means Ledgy never connects directly to your HRIS — Merge handles the connection, authentication, and data normalisation, while Ledgy reads the resulting data.

Data flow direction: one-way (HRIS → Ledgy)

The integration is one-way (unilateral). Data flows in one direction only:

HRIS → Merge → Ledgy

✅ Employee data is pulled from your HRIS into Ledgy
❌ Ledgy does not write data back to your HRIS
❌ Changes made in Ledgy are not pushed to your HRIS

This means your HRIS remains the source of truth for employee information. Any updates to employee data (name, email, address, employment status, etc.) should be made in your HRIS, and those changes will flow into Ledgy on the next retrieval and sync.

What role does Merge play?

Merge is a unified API platform that provides a single, standardised interface to connect with hundreds of HRIS providers. Instead of building and maintaining individual integrations with each HR platform, Ledgy uses Merge as a middleware layer.

What Merge does:

Connects to your HRIS using the provider's native API
Normalises data from different HRIS platforms into a consistent format
Handles authentication and credential management
Retrieves employee data on a regular schedule

What Merge does not do:

Merge does not store your data long-term — it acts as a pass-through
Merge does not write data back to your HRIS
Merge does not have access to your Ledgy account data (equity, cap table, etc.)

What Ledgy does:

Reads the normalised employee data from Merge
Caches the data on the Data Sync page for you to review
Syncs the data into stakeholder records when you trigger a sync
Manages field mapping, sync conditions, and stakeholder matching

How often is data retrieved?

Automatic retrieval: Ledgy automatically retrieves data from your HRIS (via Merge) once per day and stores it in the Data Sync cache.
Manual retrieval: You can click Retrieve Now on the Data Sync page at any time to pull the latest data from your HRIS.
Manual sync: Retrieved data is not automatically applied. You must click Sync Now (or select specific records and click Sync Selected) to push the cached data into your Ledgy stakeholder records.

This two-step process (retrieve → sync) gives you full control to review changes before they are applied.

What data is synced?

The integration syncs employee/HR data only. This includes fields such as:

Name, email, personal email
Address fields
Birthdate
Employment status, start date, termination date
Group/department, team
Pay rate, pay period, pay currency
Employment type
Custom HR fields (via Support-configured field mappings)

The integration does not sync equity or cap table data. Equity data is managed entirely within Ledgy.

For the full list of default and optional fields, see: How do I connect and sync my HRIS system with Ledgy?

Security and data handling

Credentials are entered during the linking flow and managed by Merge. Ledgy does not store your HRIS login credentials.
Data in transit is encrypted via HTTPS between all parties (HRIS ↔ Merge ↔ Ledgy).
Permissions — You need Admin access in your HRIS to authorise the connection. The integration uses read-only access to your HRIS data.

Frequently asked questions

Does Ledgy write data back to my HRIS?

No. The integration is strictly one-way. Data flows from your HRIS into Ledgy only. Ledgy never modifies, updates, or deletes records in your HRIS.

Can my HRIS see my Ledgy data (equity, cap table, etc.)?

No. The integration only pulls employee/HR data from your HRIS into Ledgy. Your HRIS has no visibility into Ledgy's equity data, cap table, or any other Ledgy-specific information.

What happens if I update an employee's details in Ledgy instead of the HRIS?

The change will only exist in Ledgy. On the next sync, the HRIS data may overwrite your manual change (for any fields that are mapped). To avoid this, always make employee data updates in your HRIS and let them flow into Ledgy via the integration.

Which HRIS platforms are supported?

Ledgy supports 70+ HRIS platforms through Merge, including HiBob, BambooHR, Personio, Workday, SAP SuccessFactors, Humaans, Rippling, Deel, Gusto, and many more. Visit the Ledgy Marketplace for the full list.