> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rippling Integration: Setup and Sync

> Connect Rippling to DualEntry, choose which workers to sync, map pay items to GL accounts, and post each Rippling pay run as journal entries.

Connect [Rippling](https://www.rippling.com/) to DualEntry so each finished payroll in Rippling posts to your ledger as journal entries, without retyping the payroll register. Information only flows one way: DualEntry reads payroll from Rippling and never changes anything in Rippling.

This page is written for the accountant or controller who sets up the integration. One step needs your Rippling admin, and it is marked. Everything else you can do yourself in DualEntry.

> [!NOTE]
>
> The Rippling integration is in beta. Plan a working session for the first setup, and read [Current limitations](#current-limitations) before you rely on it for a close. DualEntry support can join you for the first connection if you'd like help.

## Who does what

Setting up Rippling involves up to three people, and most of the work is yours. The table below lists each task and who needs to do it, so you can book time with the right person before you start.

| Task | Who does it | Why |
| - | - | - |
| Add the Rippling **App Management** package to your Rippling plan | Your Rippling account manager, at your request | Rippling only lets outside apps like DualEntry connect when your plan includes it. |
| Approve DualEntry in Rippling (step 1) | A Rippling admin | Rippling only lets an admin approve a connection to another app. |
| Choose Connect in DualEntry (step 1) | Anyone in DualEntry whose role can edit integrations, such as an Admin | Connecting changes your organization's settings. |
| Choose settings, map accounts, and check the first sync (steps 2 to 4) | You, the accountant or controller | These are accounting decisions. |

If you are not a Rippling admin, sit with your Rippling admin for step 1, which takes a few minutes. You don't need IT or an engineer for any step.

## Before you start

Gather these before you open the integration. Having them ready keeps the setup to a single session.

* **Confirmation that your Rippling plan includes App Management.** Ask your Rippling account manager if you're not sure. Without it, the connection fails with "Failed to connect integration".
* **Time with your Rippling admin** for step 1, unless you are the admin.
* **A payroll vendor in DualEntry**, for example "Rippling". DualEntry tags every payroll journal entry with this vendor so you can find them later.
* **GL accounts in your [chart of accounts](https://docs.dualentry.com/accountants/core-financials/general-ledger/chart-of-accounts.md)** for wages and other payroll expense, employer taxes, employer benefit contributions, amounts withheld from pay (taxes, benefits, retirement, garnishments), and an **offset account**. The offset account is the account DualEntry credits to balance the payroll expense, usually an accrued payroll or payroll clearing account.
* **A DualEntry company for each Rippling legal entity** you pay people from. A legal entity is Rippling's name for each registered business you run payroll for.
* **Optional: a classification such as Department**, if you want payroll split by department on your reports. See [How to Set Up and View Classifications](https://docs.dualentry.com/accountants/platform-configuration/classifications.md).

## Step 1: Connect DualEntry to Rippling

Connecting opens Rippling in your browser so a Rippling admin can approve DualEntry, then brings you back. This is the step that needs your Rippling admin.

1. In DualEntry, go to **Configuration → Company → Integrations** and open the **All integrations** tab.
2. On the Rippling tile, choose **Connect**. Rippling opens in the same browser tab.
3. **Rippling admin:** sign in to Rippling if asked, review the access DualEntry asks for, and approve it.
4. Rippling sends you back to DualEntry, where Rippling now shows as connected.

Right after you connect, DualEntry reads your Rippling setup (legal entities, departments, workers, and pay items) so you have something to map. It does not post any payroll yet.

DualEntry asks for read-only access to payroll, workers, companies, departments, and groups. If your Rippling admin approves only part of that, the connection still completes, but the parts that weren't approved stay empty. For example, if payroll access is missing, no pay runs appear when you sync. If something you expect is missing, ask your Rippling admin to approve the full access, then connect again from the Rippling tile.

## Step 2: Choose what to sync and how to post it

The integration's settings decide which workers DualEntry posts payroll for and how the journal entries are dated. Set them before the first sync, because changing them later doesn't change entries that already posted.

Open the Rippling integration and choose the **Rippling Settings** tile. Under **Worker Types**, turn on each kind of worker you pay through Rippling. All three are off when you first connect, and nothing posts until you turn at least one on.

* **Sync W-2 Employees**: your own employees, with taxes withheld from their pay.
* **Sync 1099 Contractors**: self-employed contractors, paid without withholding.
* **Sync EOR/PEO**: workers employed for you by a third party. An EOR (employer of record) legally employs people for you, usually in a country where you have no business set up. A PEO (professional employer organization) shares employment of your workers and runs their payroll, taxes, and benefits. DualEntry posts both as one total per pay run, the way you'd record the provider's invoice.

Rippling, not DualEntry, decides which kind each worker is, based on how they're set up in Rippling.

Under **Settings**, choose the **Accounting Basis**:

* **Accrual** (the default): each W-2 pay run posts an expense entry dated the last day of the pay period, and a second entry dated the pay date that records the payment. If the pay period ends on the pay date, you get one entry.
* **Cash**: each W-2 pay run posts one entry dated the pay date.

Under **Advanced Settings**, turn on **Include Terminated Employees** if a final paycheck can land after someone leaves.

Then choose the **Rippling Default Accounts Mapping** tile and fill in the accounts for each worker type you turned on:

* **Default Offset Account (W-2)**: the offset account for employee payroll.
* **Contractor Offset Account**: the offset account for contractor payments.
* **EOR Offset Account** and **EOR Employment Expense**: the payable to Rippling and the expense account for EOR and PEO payroll.
* **Cash / Bank Account** (contractors and EOR only, optional): the bank account credited when the payment date is later than the expense date. Leave it empty to pay these through Accounts Payable instead.

## Step 3: Map your Rippling data

Mapping means telling DualEntry which of your DualEntry records matches each Rippling item, for example which GL account Rippling's "Regular Pay" belongs in. Each kind of item has its own tab on the integration page. Until the required tabs are complete, the integration shows setup as incomplete and posts nothing.

Work through these tabs:

* **Companies** (required): pick the DualEntry company for each Rippling legal entity. This decides which company's books each payroll lands in.
* **Payroll Vendor** (required): pick the vendor you created for Rippling.
* **Employees — Companies** (shown when you have more than one company): DualEntry matches each worker to a company from their Rippling legal entity. Fix any rows it couldn't match.
* **Accounts (W-2)** (required when W-2 is on): one row for each kind of pay, tax, deduction, or garnishment that appears in your Rippling payroll. Each row's name shows who paid it, the kind of line, and Rippling's name for it. Choose a **DualEntry DR Account** (the account debited) for every row. **DualEntry CR Account** (the account credited) is optional; leave it empty to use your **Default Offset Account (W-2)**.
* **Accounts (Contractors)** (required when contractors are on): choose accounts for **Contract Labor** and **Reimbursement**.
* **Departments** (optional): pick the classification value for each Rippling department, and set **Department Classification Name** under **Settings** to the classification you use, such as Department. DualEntry doesn't match departments by name, so map each one you want on your reports. Departments you leave unmapped post without a department.

New pay items can appear on **Accounts (W-2)** after later payrolls, for example the first time someone gets a bonus. Check that tab whenever a sync reports a missing account. EOR and PEO payroll use the two EOR accounts from step 2, so there is nothing to map for them here.

The **Users**, **Pay Runs**, and **Pay Statements** tabs list what DualEntry imported from Rippling. They don't need mapping and never hold up setup.

## Step 4: Run the first sync and check the entries

Run the first sync yourself instead of waiting for the daily schedule, so you can check the entries while setup is fresh.

1. On the Rippling integration page, choose **Sync**. The button's label changes as you go: it reads **Initial sync** while setup is still incomplete, **Sync** once setup is complete but nothing has synced yet, and **Resync** after the first sync finishes.
2. When the sync finishes, open the **Data Sync** tab. **Synced** lists what posted, and **Error** lists anything that didn't.
3. Open a few journal entries in [Journal Entries](https://docs.dualentry.com/accountants/core-financials/general-ledger/journal-entries.md) and compare the totals with the matching Rippling payroll register.

The first sync brings in finished pay runs from the last 12 months. To bring in older history, set **Initial Cut Off Date** in the integration's settings to an earlier date before you sync. The cutoff can only reach further back. A date within the last 12 months doesn't shorten the window, so pay runs from before a recent go-live date still import. DualEntry only imports pay runs that are approved or paid in Rippling. Drafts appear once they're approved.

## How pay runs become journal entries

A pay run is one payroll in Rippling, such as the 10/15/2026 payroll. DualEntry turns each finished pay run into a small set of summary journal entries, not one entry per person.

* **W-2 employees**: one set of entries for each company and currency in the pay run. A pay run that covers three legal entities posts three sets.
* **Contractors**: one entry per contractor, in the currency they were paid in.
* **EOR and PEO**: one entry for the whole pay run.

Every entry carries your payroll vendor, so you can filter for Rippling payroll entries during close.

Payroll taxes are combined into one line per GL account by default. Turn off **Consolidate Payroll Taxes** under **Settings** if you want a separate line for each tax.

DualEntry checks that every entry balances before it posts. Small rounding differences across many workers, up to one cent per line of the entry and at least five cents, go to a rounding line on the offset account. If an entry is off by more than that, DualEntry doesn't post it and lists it under **Error**, so an unbalanced entry never reaches your ledger.

## Give people DualEntry access from Rippling (optional)

The integration can also give DualEntry access to people your Rippling admin chooses, so you don't invite them one at a time. You can skip this section if you only need payroll.

To use it, your Rippling admin creates a group in Rippling named exactly **PROVISIONING** and adds the people who should have DualEntry access. Rippling calls this kind of group a supergroup. DualEntry then:

* Creates a DualEntry user for each member who doesn't have one, with the **View-Only** role. A DualEntry admin can give them a different role afterwards.
* Matches people to existing DualEntry users by email address.
* Updates access shortly after someone is added to or removed from the group in Rippling, without waiting for the daily sync.

If an admin changes one of these users by hand in DualEntry, the integration leaves that user alone from then on. If the group doesn't exist, or your Rippling admin didn't approve access to groups in step 1, nothing happens and payroll still syncs.

Signing in to DualEntry with your Rippling login (single sign-on) is a separate option. It needs settings exchanged between Rippling and DualEntry, so contact DualEntry support to set it up.

## Sync schedule and history

After the first sync, the integration checks Rippling once a day for new pay runs. Choose **Resync** on the integration page when you need a payroll in the ledger sooner.

Later syncs only redo what can still change. A paid pay run that posted cleanly isn't fetched again. An approved pay run is checked again until it's paid, because it can still change in Rippling. A pay run with an error is retried on each sync, so once you fix the cause, the next sync posts it.

## Current limitations

The Rippling integration is in beta and has these limitations today:

* **Setup takes a working session.** Plan for a session with your Rippling admin available for step 1, rather than a few-minute install.
* **Changes don't rewrite posted entries.** Changing a mapping, an account, or the accounting basis affects new entries only. To apply a change to payroll that already posted, resync those pay runs. See [Retry, resync, and archive](https://docs.dualentry.com/accountants/integrations/managing-syncs.md).
* **Departments are mapped by hand.** Map each department on the **Departments** tab; DualEntry doesn't create or match them for you.
* **One-way only.** DualEntry reads from Rippling. It doesn't send accounts, journal entries, or vendors back.
* **Finished payroll only.** Draft and in-progress pay runs don't appear until they're approved or paid in Rippling.
* **Connection problems show a general message.** If connecting fails, DualEntry shows "Failed to connect integration" without the reason. Check the items in the troubleshooting table below.

## Troubleshoot sync errors

Payroll that didn't post appears on the integration's **Data Sync** tab under **Error**, with a message for each item. Rippling's own service status is at [status.rippling.com](https://status.rippling.com/).

The following table lists the problems you're most likely to see and how to fix each one:

| What you see | What it means | What to do |
| - | - | - |
| "Failed to connect integration" when connecting | Usually your Rippling plan doesn't include App Management, or the person approving in Rippling isn't a Rippling admin. | Confirm App Management with your Rippling account manager, then have a Rippling admin choose **Connect** again. |
| Workers or departments don't appear after connecting | Your Rippling admin didn't approve access to that information in step 1. | Ask your Rippling admin to approve the full access, then connect again from the Rippling tile. |
| No pay runs appear after a sync | Pay runs come in on a sync, not when you connect. A sync imports them only when at least one worker type is on, and only pay runs that are approved or paid in Rippling. | Turn on a worker type under **Rippling Settings**, check the pay run's status in Rippling, then choose **Resync**. If pay runs are still missing, ask your Rippling admin to approve payroll access, then connect again from the Rippling tile. |
| Nothing posts, even though setup is complete | No worker type is turned on. | Turn on at least one worker type under **Rippling Settings**. |
| A payroll line has no mapped account | A new kind of pay, tax, or deduction appeared on **Accounts (W-2)** or **Accounts (Contractors)** without an account. | Choose an account for the new row, then resync the pay run. |
| The offset account for a worker type isn't set | That worker type is on but its offset account on the **Rippling Default Accounts Mapping** tile is empty. | Set the offset account. Other worker types keep posting meanwhile. |
| A worker's type can't be determined | The worker isn't set up as an employee, contractor, or EOR or PEO worker in Rippling. | Fix the worker's employment type in Rippling, then resync. |
| A journal entry is out of balance | The entry is off by more than a few cents, so DualEntry held it back. | Compare the pay run with Rippling's payroll register and contact DualEntry support. |
| The connection needs to be reconnected | Rippling stopped accepting DualEntry's access, for example after an admin change in Rippling. | Choose **Reconnect** and have a Rippling admin approve again. |
| A sync stopped because Rippling was busy | Rippling limited how fast DualEntry could read data. | Wait. The next daily sync, or a **Resync** later, picks it up. |
| People weren't given DualEntry access | The **PROVISIONING** group doesn't exist in Rippling, or access to groups wasn't approved. | Have your Rippling admin create the group and approve access to groups, then connect again from the Rippling tile. |

## Result

After you complete these steps, every approved or paid Rippling pay run posts to DualEntry as journal entries for each company, currency, and worker type you turned on, with departments applied where you mapped them. For other payroll providers, see the [Gusto integration](https://docs.dualentry.com/accountants/integrations/payroll-and-hr/gusto.md), the [Justworks integration](https://docs.dualentry.com/accountants/integrations/payroll-and-hr/justworks.md), or the [Deel integration](https://docs.dualentry.com/accountants/integrations/payroll-and-hr/deel.md) for contractor-heavy teams. For actions that work the same on every integration, see [Retry, resync, and archive](https://docs.dualentry.com/accountants/integrations/managing-syncs.md). To connect other systems, return to [Integrations](https://docs.dualentry.com/accountants/integrations/index.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.