Skip to content
Human resources ⇄ Accounting and finance

BambooHR to Rillet integration — real-time, two-way sync

Keep BambooHR and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect BambooHR and Rillet

Keep the employee, department, and cost records that Rillet and BambooHR share consistent in real time, so the finance system and the people system stop drifting apart.

Rillet runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. BambooHR runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Bill, Journal Entry, Invoice Payment, Charge in Rillet with Job Information, Compensation, Time Off, Employment Status in BambooHR bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • 02 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • 03 Push approved Time Off into capacity and scheduling systems so project plans reflect real availability.
  • 04 Feed Compensation and custom-table data to a warehouse for HR analytics with field-level access control.

Common sync patterns

New person becomes a known record in finance

When someone is added in BambooHR, a matching employee or payee record appears in Rillet, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

Department and cost-center alignment

The org structure maintained in BambooHR keeps the departments or cost centers in Rillet current, so spend and headcount roll up the same way.

What you can sync between BambooHR and Rillet

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

BambooHR objects Rillet objects How this pairing syncs
Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. Invoice Payment Synced with incremental and full sync per the Stacksync docs. Employment Status is specific to BambooHR and Invoice Payment to Rillet — each maps to any object or custom field on the other side.
Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. Charge Synced with incremental and full sync per the Stacksync docs. Departments and Divisions is specific to BambooHR and Charge to Rillet — each maps to any object or custom field on the other side.
Custom Tables Company-specific effective-dated tables (assets, training, certifications); rows read and written so custom HR data isn't trapped in the HRIS. Reimbursement Synced with incremental and full sync per the Stacksync docs. Custom Tables is specific to BambooHR and Reimbursement to Rillet — each maps to any object or custom field on the other side.
Reports Saved company reports retrievable via API; read out on a schedule to feed a warehouse without rebuilding field-by-field queries. Custom Field Synced with incremental and full sync per the Stacksync docs. Reports is specific to BambooHR and Custom Field to Rillet — each maps to any object or custom field on the other side.
Employees The core person record with personal and work fields; read out to identity, payroll, and IT systems, and written back from recruiting or onboarding tools. Account Synced with incremental and full sync per the Stacksync docs. Employees is specific to BambooHR and Account to Rillet — each maps to any object or custom field on the other side.
Job Information Effective-dated job title, department, division, location, and reporting line; synced so org charts and provisioning systems track internal moves. Customer Synced with incremental and full sync per the Stacksync docs. Job Information is specific to BambooHR and Customer to Rillet — each maps to any object or custom field on the other side.

How changes propagate between BambooHR and Rillet

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

BambooHR Rillet Sub-second propagation

DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.

DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet BambooHR Sub-second propagation

DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.

DeliveryEach detected change is written to BambooHR through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • BambooHR: Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.
  • Rillet: Subject to the platform's API rate limits.
What ships with BambooHR ⇄ Rillet

Connect BambooHR and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BambooHR–Rillet connection.

Real-time

Two-way sync

Changes in BambooHR or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BambooHR or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single BambooHR or Rillet record.

Observability

Monitoring

Track your BambooHR ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BambooHR and Rillet.

How the BambooHR and Rillet connectors work

BambooHR

Integration surface
BambooHR API (REST, per-company subdomain)
Authentication
API key per user over HTTP Basic auth (key as username), scoped to that user's permission level in BambooHR; OAuth/OpenID available for SSO-enabled apps
Change detection
The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling; webhooks can fire on monitored field changes
Capabilities
read · write · webhooks
Rate limits
Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect BambooHR to Rillet — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate BambooHR and Rillet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    BambooHR connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BambooHR and Rillet objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · BambooHR ⇄ Rillet
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    BambooHR Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

BambooHR and Rillet integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 335 integrations available for BambooHR and Rillet.

Popular · 7 of 335
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.