Remote Integrations

Remote lists 60+ integrations on its marketplace, the broadest catalogue of any 100%-owned-entity EOR. Coverage spans HRIS tools from BambooHR to Workday, ATS platforms from Greenhouse to Ashby, and accounting connections including QuickBooks and Xero.

For a buyer evaluating whether Remote will fit into their existing tech stack, that number tells you less than knowing what those integrations actually do once connected. In Whichapp’s buyer interviews with 12 companies that migrated to Remote in 2024–2025, integration reliability for the Salesforce CRM connection was the most frequently cited gap: specifically, that contact records sync correctly but opportunity data associated with a newly onboarded employee does not propagate without a manual trigger.

Most are event-triggered rather than fully bi-directional. A new hire created in BambooHR flows to Remote. A salary change made in BambooHR does not automatically update Remote pricing payroll record.

That gap matters at the exact moment payroll runs and the two systems are holding different compensation figures.

This page maps what Remote integrates with, how deep those connections run, and where they break down.

If your stack runs on BambooHR and Greenhouse and your finance team can handle a monthly manual reconciliation step in QuickBooks, Remote’s integration layer will cover you.

If you need real-time payroll-to-GL mapping or automatic compensation sync flowing downstream, you are planning workarounds before you have started. Read the full Remote review for the provider-level assessment; this page covers integrations specifically.

For a broader shortlist, see the best employer of record providers.

What tools does Remote.com integrate with?

Remote’s integration catalogue breaks into five functional categories. The sync direction matters as much as the tool name, so it is listed for each.

HRIS (BambooHR, Workday, HiBob, Personio, Humaans, Rippling HRIS module, Namely): event-triggered. New hire records flow from your HRIS into Remote when a hire is initiated.

Changes to existing records, including compensation updates, do not sync automatically in most cases.

ATS (Greenhouse, Lever, Ashby, Workday Recruiting, Teamtailor): event-triggered on hire decision. Candidate data pushes to Remote when your ATS marks the role as filled.

Custom fields and right-to-work documentation still require manual input in Remote.

Accounting and payroll (QuickBooks Online, Xero, NetSuite via custom config): export-only. Remote pushes a payroll summary to your accounting platform after each payroll run.

There is no real-time sync and no journal-level line-item mapping.

SSO and identity (Okta, Google Workspace SAML, Microsoft Azure AD): authentication for employee portal access.

Okta SCIM provisioning is supported, meaning you can create and deactivate Remote employee accounts via your identity provider.

Automation platforms (Zapier, Make): trigger and action based. Remote has a Zapier app and a Make connector, extending reach to thousands of tools that are not native integrations.

These rely on Remote’s published triggers rather than a dedicated API connection, and Zapier and Make billing applies separately.

The practical upshot: if your hiring stack uses any combination of BambooHR, Greenhouse, Slack, and QuickBooks, Remote covers all four natively.

The question is whether “covers” means what you need it to mean, which the next three sections answer specifically.

How deep are Remote.com’s HRIS integrations?

BambooHR is the most common HRIS in Remote’s customer base and worth examining in detail because it illustrates the model Remote uses across its HRIS connectors.

When you mark a candidate as hired in BambooHR, the integration creates a corresponding record in Remote with the employee’s name, job title, start date, country, and department. That is the part that works reliably.

The friction starts when records change after initial creation.

If you update the employee’s salary in BambooHR three months later, that change does not automatically flow to Remote. Payroll continues at the previous rate until someone raises a change request in Remote directly.

In practice, companies running BambooHR and Remote without a documented compensation change process will encounter payroll discrepancies at the point of their first salary review cycle.

Workday sits at the more complex end of Remote’s HRIS integration list. The connector requires custom configuration rather than a plug-and-play setup.

Companies running Workday HCM for domestic payroll and Remote EOR for international headcount face a dual-system reconciliation challenge that the integration reduces but does not eliminate. The depth of sync depends on which Workday modules the company has licensed.

If you are evaluating Remote on a Workday-heavy stack, expect IT involvement in the initial configuration and a testing period before going live.

HiBob, Personio, and Humaans follow the same event-triggered pattern as BambooHR. They are adequate for companies where Remote is the downstream system of record for international employees and the HRIS manages everything else.

They create friction for companies where compensation changes originate in the HRIS and need to flow downstream to payroll without a manual step.

If automatic compensation sync is a hard requirement for your stack, the right comparison is Remote vs Rippling: Rippling owns the HRIS layer, which means what looks like an integration from Remote’s perspective is native data access from Rippling’s.

Which ATS tools does Remote.com connect to?

Remote’s ATS integrations are the most operationally reliable part of its connector stack, and they address a real pain point: the manual re-entry of offer letter data into a second system on hire day.

With Greenhouse, the integration activates when you mark a candidate as hired. Remote receives the employee’s legal name, job title, start date, department, and compensation details if those are stored in Greenhouse Offers.

The onboarding workflow in Remote starts automatically rather than waiting for an HR ops team member to create the record manually.

The fields that still require human input in Remote are right-to-work documentation, benefits elections, and any custom employment terms that do not map to a standard Greenhouse Offers field.

Non-standard contract clauses, IP assignment addendums, and non-compete terms need to be flagged separately in Remote before contract generation begins.

See the Remote onboarding guide for the full step-by-step from ATS hire decision to payroll-ready employee.

Ashby’s Remote connector transfers structured offer data including compensation bands and equity details, which tends to map more cleanly into Remote than exports from older ATS platforms that store offer terms in free-text fields.

For scale-up teams running Ashby, this reduces the manual field-mapping step that appears with less structured offer data.

Lever connects via a similar event-triggered model.

Workday Recruiting is available for enterprise customers who use Workday as their ATS as well as their HRIS, though it shares the same configuration complexity as the Workday HCM integration.

ATS integrations do not replace the need to brief your onboarding specialist on non-standard hires. Any candidate whose offer includes terms that deviate from Remote’s standard contract template requires a direct communication to the specialist before Remote generates the employment contract.

The integration handles the routine; the exceptions still require a human handoff.

Does Remote.com sync payroll data with accounting software?

Remote connects to QuickBooks Online, Xero, and NetSuite, but the word “sync” overstates what these connections do. They are post-run exports: after Remote processes a payroll cycle, it pushes a payroll summary to your accounting platform.

There is no real-time sync and no two-way reconciliation.

In QuickBooks Online, the export arrives as a summary entry covering gross payroll, employer taxes, and net pay totals by country. It does not break down by cost centre, department, or individual employee.

The chart of accounts mapping between Remote’s export fields and your QBO account codes is a one-time manual setup on first use. Finance teams at companies with a single cost centre and a small international headcount will find this sufficient.

Finance teams who need to allocate payroll costs across departments or reconcile to the general ledger at a line-item level will be doing that mapping manually after every payroll run.

Xero works on the same principle.

One additional consideration for Xero users in markets where Xero has a native payroll module (UK, Australia, New Zealand): check whether Remote’s payroll export will conflict with or duplicate payroll data from any domestic employees who are on Xero’s own payroll feature.

The two systems are not designed to talk to each other, and the accounting entries need to be managed carefully to avoid double-counting employer costs.

NetSuite is supported via custom configuration rather than a standard out-of-the-box connector.

It is viable for enterprise finance teams with technical resource to configure the integration, but it is not a connector you activate from a settings menu.

If your finance team requires payroll-to-GL reconciliation at a journal-entry level without manual work, this is the area where Remote most clearly lags the benchmark.

The Remote vs Deel comparison covers accounting integration depth across both providers.

What does the Remote.com Connect API give you?

Remote’s developer API, branded as Remote Connect, is a REST API with OAuth 2.0 authentication.

It is the right option for companies whose tech stack includes tools not covered by Remote’s native connector list, or for engineering teams who want to build automated HR workflows that run without manual triggers.

The API covers employee management (create, update, offboard), payroll data retrieval, time-off management, and contractor operations. Webhook events are available for: employee onboarded, payroll run completed, document signed, time-off approved, and employee terminated.

A sandbox environment is available for development and testing before connecting to the production account.

The practical use cases where the API adds genuine value: connecting Remote to a proprietary HRIS or internal workforce management tool that does not appear in Remote’s native connector catalogue automating offboarding workflows triggered by an internal HR system event

Syncing Remote payroll data into a custom finance dashboard or data warehouse and automating contractor onboarding at volume when you are connecting a talent marketplace to Remote rather than processing individual hires one at a time.

One limitation worth noting: the API covers operational endpoints well but does not expose compliance configuration data for programmatic management. Entity-level tax settings and country-specific statutory fields cannot be managed via API.

Compliance configuration still requires platform UI access, which matters for companies with complex multi-country setups who want to automate as much of their Remote administration as possible.

API access is included in the standard Remote subscription. There is no separate developer tier or API access fee.

Rate limits apply at the standard tier (Remote’s documentation specifies the current limits, which vary by endpoint).

Where do Remote.com’s integrations fall short?

Four failure modes appear consistently in companies that have deployed Remote integrations at scale. They are not edge cases; they are the predictable consequences of the event-triggered model.

Compensation change processed in HRIS, not mirrored in Remote. Your HR team updates salary in BambooHR during a pay review cycle. The event that triggers the Remote sync is new hire creation, not record update.

Remote continues processing payroll at the old figure until someone raises a change request directly in Remote. The fix is a documented process step: every compensation change in your HRIS must generate a parallel change request in Remote before the next payroll run.

Companies that discover this failure mode do so at the point of their first salary review after going live.

Workday termination event fails to trigger Remote offboarding in time. For companies using Workday as their HRIS, the termination event needs to be tested thoroughly before going live.

If the integration is not configured correctly, a terminated employee’s Remote record stays active, payroll continues, and the error surfaces when the finance team reconciles headcount.

A manual parallel check during the first month of operation is not a sign that the integration is broken; it is a sensible verification step while you confirm the trigger is working reliably.

Finance team expects QuickBooks at cost-centre level, receives a country total.

This expectation mismatch is common in companies where finance has been told Remote “integrates with QuickBooks.” It does, but the integration delivers a country-level payroll total, not a line-item breakdown.

If your management accounts require cost-centre-level payroll allocation, you are doing that manually. Setting this expectation with finance before go-live avoids a difficult conversation three months later.

ATS sends hire record but non-standard offer terms are missing. The Greenhouse or Ashby integration transfers standard offer fields.

Custom contract addenda, non-standard IP clauses, equity vesting terms, and sign-on bonus structures are not automatically included.

The Remote onboarding specialist receives a standard record and has no visibility of the non-standard terms unless the hiring manager flags them separately.

The result is a contract that does not reflect the offer letter, which requires an amendment cycle and delays the start date.

How does Remote.com compare to Rippling and Deel on integrations?

The clearest frame for the comparison is structural: Rippling owns its HRIS layer, Remote integrates with HRIS systems it does not own, and Deel does the same as Remote but with a wider ATS connector list.

Rippling’s accounting advantage is real: journal-level GL mapping means finance teams can reconcile payroll costs by department or cost centre without a manual step.

For companies where this matters, it is a structural difference, not a feature version. Deel pricing ATS breadth (Deel carries ~120-140 total integrations, with broader ATS coverage than Remote’s 5+ named connectors) covers more obscure ATS tools, but the sync depth for each connector is comparable to Remote’s.

If your ATS is not Greenhouse, Lever, or Ashby, Deel is worth checking before committing to Remote.

When are Remote.com’s integrations good enough?

Remote’s integration stack is a reasonable fit in four scenarios and a poor one in two.

It works well when your HRIS is BambooHR, HiBob, or Personio and you use Remote as the downstream system for international employees.

Event-triggered sync handles the key workflows without manual re-entry as long as compensation changes are processed as Remote change requests rather than HRIS-only updates.

It works well when your ATS is Greenhouse or Ashby and your hires have standard compensation structures. The integration eliminates the error-prone manual step of re-keying offer data.

Custom offer terms still need a separate handoff to the Remote specialist, but that is a one-person step rather than a full re-entry process.

It works well for engineering-led teams who can use the Remote Connect API to build custom workflows for tools outside the native connector list.

The API is well-documented and covers the operational endpoints that matter for HR automation.

It works well for finance teams who need payroll totals in QuickBooks or Xero and are comfortable with a monthly manual step to allocate those totals to cost centres in their chart of accounts.

It does not work well when your finance team requires real-time, journal-level payroll-to-GL reconciliation. That is a Rippling use case, not a Remote one.

It does not work well when your HRIS is the system of record for compensation and salary changes need to flow to payroll automatically without a parallel manual update.

The event-triggered model will generate payroll errors unless you build a disciplined change-request process, and that process needs to be enforced consistently or it will slip.

Companies with frequent salary changes or large headcount are more exposed to this risk than those with stable compensation structures.

Frequently asked questions about Remote.com integrations