Skip to main content
TrulyCritic original research

Rippling Test Results 2026

Every workflow we tested in a vendor-provided Redwood sandbox, including the ones that failed. Each record carries a test ID, an observed result, a severity, an evidence label, a date and the limitation that stops the result from being generalized.

9Test records
8Reviewed findings
AEvidence confidence
Oct 2026Testing window
By Khyati Sharma, Author & EditorPublished October 28, 2026Last tested October 2026CC BY 4.0

What this page is

This is the public test log behind TrulyCritic’s Rippling review. The review narrates what the results mean for a buyer. This page keeps the records themselves visible and citable: what we attempted, what the product did, how strong the evidence is and what remains unproven.

Of 9 documented workflows, 6 passed, 1 produced a partial result and 2 failed materially. A pass covers the sampled workflow only. A failure describes what happened in this sandbox and configuration; it is not a claim that every customer will see the same outcome.

Test environment and scope

Test environment
Vendor-provided Redwood sandbox
Testing period
October 2026, multiple sessions across two weeks
Coverage
HR, payroll, time, benefits, finance, IT, AI, API, reporting and migration
Not verified
Production tax filings, carrier transmission, bank settlement, global payroll or EOR execution, physical device delivery and production-scale performance
Evidence confidence
A: substantial hands-on testing
Data
Fictional seeded company and employee records. No real paystubs, bank details, tax identifiers or credentials are shown.

How to read a record

Three labels appear on every record. They answer different questions, so a row can pass a workflow and still carry an important limitation.

Status: what the workflow did

Passed
The sampled workflow completed as expected in this configuration.
Partial
The workflow completed only after a correction, or only part of it was observable.
Material failure
The workflow broke or produced a materially wrong result that a buyer would have to catch.

Severity: what it means for a buyer

Observation
Recorded behaviour with no material commercial consequence on its own.
Important limitation
Works as designed, but the design shifts risk to the administrator or the buyer.
Material failure
A failure that could change a purchase decision or require a workaround.

Evidence: how we know

Every record on this page is labelled Hands-on tested: we performed the workflow ourselves in the vendor sandbox. Nothing here is reproduced from vendor documentation, a sales demo or a third-party review. If a step was not performed, it appears under what this does not prove rather than in the result.

The test records

Test IDs are stable. Cite a record by ID and date. Limits are part of the record, not a disclaimer added afterwards. Select a test ID to open its full record.

Rippling hands-on test records with test ID, module, workflow, result, status, severity, evidence type, date and limitation
Test IDModuleWorkflow and observed resultStatusSeverityEvidenceDateLimitation
TC-HR-OFF-001View captureHR / ITOffboarding access reviewTermination, final pay, documents and 21 app-access assignments appeared in one guided process.PassedObservationHands-on testedOctober 2026We did not verify revocation inside every connected third-party application or physical device recovery.
TC-PAY-EXCL-001View capturePayrollEmployee exclusion from a draft pay runRippling named an employee missing bank and tax details and allowed the wider payroll run to continue.PassedImportant limitationHands-on testedOctober 2026The control protects continuity but shifts responsibility to the administrator; final payment and tax filing were not verified.
TC-HR-TRANS-001View captureHR / PayrollEmployee transition with a job templateA $17/hour template value became $17/year for a salaried employee; the workflow continued without a transition approval policy.Material failureMaterial failureHands-on testedOctober 15, 2026Sandbox configuration and the absence of an approval policy influenced the outcome; this is not a claim that Rippling always miscalculates compensation.
TC-TIME-PTO-001View captureTimePTO request and cancellationEight paid hours appeared on the schedule and timesheet, then reversed cleanly after cancellation.PassedObservationHands-on testedOctober 16, 2026Human manager approval and the final paycheck for the leave event were not tested.
TC-BEN-401K-001View captureBenefitsSampled 401(k) deductionA 2% election on $3,750 produced a $75 employee deduction and a separate $75 employer contribution.PassedObservationHands-on testedOctober 2026No live carrier enrollment or carrier transmission was completed.
TC-FIN-REIM-001View captureFinanceExpense reimbursement to paystub$497.16 in expense reimbursements plus a $200 recurring cell-phone reimbursement reached the paystub with an approval trail.PassedObservationHands-on testedOctober 17, 2026Bank settlement and a completed external ledger sync were not verified.
TC-AI-BENCH-001View captureAICross-module payroll and benefits analysisConstrained answers were useful; a complex payroll-totals query required correction and human verification.PartialImportant limitationHands-on testedOctober 2026Single-session observations, not a controlled accuracy or latency benchmark.
TC-MIG-IN-001View captureMigrationBulk employee importTwo clean records reached final review, then failed at finalization; IT onboarding records appeared without searchable HR profiles.Material failureMaterial failureHands-on testedOctober 16, 2026The root cause was not identified; this does not prove that every production import fails.
TC-API-REV-001APIAuthentication, pagination, scopes and token revocationThe sampled API controls worked as expected, including scope enforcement and token revocation.PassedObservationHands-on testedOctober 2026No load, rate-limit or production-scale testing was performed.

Screenshots open the same WebP files published in the review. All captures contain fictional seeded data and were reviewed for personal, bank, tax and credential exposure before publication. Download the records as JSON under the same CC BY 4.0 terms.

Record detail

Each record states what we attempted, what the product did, and what the result does not prove. Test IDs match the table above and the findings in the review.

TC-HR-OFF-001PassedObservationHR / IT · October 2026

Offboarding access review

What we did
We opened a termination workflow for a fictional employee and followed every step through final pay, documents, responsibility transfer and app-access review.
What happened
Termination, final pay, documents and 21 app-access assignments appeared in one guided process.
What this does not prove
We did not verify revocation inside every connected third-party application or physical device recovery.
View the capture for TC-HR-OFF-001 →
TC-PAY-EXCL-001PassedImportant limitationPayroll · October 2026

Employee exclusion from a draft pay run

What we did
We opened a draft pay run containing a fictional employee with three critical missing fields.
What happened
Rippling named an employee missing bank and tax details and allowed the wider payroll run to continue.
What this does not prove
The control protects continuity but shifts responsibility to the administrator; final payment and tax filing were not verified.
View the capture for TC-PAY-EXCL-001 →
TC-HR-TRANS-001Material failureMaterial failureHR / Payroll · October 15, 2026

Employee transition with a job template

What we did
We completed an employee transition using a job template, reviewing job information, team, compensation, documents, payroll, app access, RPass (Rippling's password and app-access layer) sharing and notification.
What happened
A $17/hour template value became $17/year for a salaried employee; the workflow continued without a transition approval policy.
What this does not prove
Sandbox configuration and the absence of an approval policy influenced the outcome; this is not a claim that Rippling always miscalculates compensation.
View the capture for TC-HR-TRANS-001 →
TC-TIME-PTO-001PassedObservationTime · October 16, 2026

PTO request and cancellation

What we did
We submitted an eight-hour US Vacation Policy request for a fictional hourly employee, then canceled it.
What happened
Eight paid hours appeared on the schedule and timesheet, then reversed cleanly after cancellation.
What this does not prove
Human manager approval and the final paycheck for the leave event were not tested.
View the capture for TC-TIME-PTO-001 →
TC-BEN-401K-001PassedObservationBenefits · October 2026

Sampled 401(k) deduction

What we did
We reviewed benefits settings and a draft pay run for a fictional employee with a 2% employee 401(k) election.
What happened
A 2% election on $3,750 produced a $75 employee deduction and a separate $75 employer contribution.
What this does not prove
No live carrier enrollment or carrier transmission was completed.
View the capture for TC-BEN-401K-001 →
TC-FIN-REIM-001PassedObservationFinance · October 17, 2026

Expense reimbursement to paystub

What we did
We reviewed a $443.26 Hilton reimbursement and a $53.90 Uber reimbursement for a fictional employee, including the approval chain, accounting state and paystub payout.
What happened
$497.16 in expense reimbursements plus a $200 recurring cell-phone reimbursement reached the paystub with an approval trail.
What this does not prove
Bank settlement and a completed external ledger sync were not verified.
View the capture for TC-FIN-REIM-001 →
TC-AI-BENCH-001PartialImportant limitationAI · October 2026

Cross-module payroll and benefits analysis

What we did
We asked Rippling AI to compare payroll runs, find active benefit deductions, reconcile retirement deductions and retrieve payroll totals.
What happened
Constrained answers were useful; a complex payroll-totals query required correction and human verification.
What this does not prove
Single-session observations, not a controlled accuracy or latency benchmark.
View the capture for TC-AI-BENCH-001 →
TC-MIG-IN-001Material failureMaterial failureMigration · October 16, 2026

Bulk employee import

What we did
We uploaded a two-person CSV, mapped fields and tenant values, completed required-field validation and reached final review.
What happened
Two clean records reached final review, then failed at finalization; IT onboarding records appeared without searchable HR profiles.
What this does not prove
The root cause was not identified; this does not prove that every production import fails.
View the capture for TC-MIG-IN-001 →
TC-API-REV-001PassedObservationAPI · October 2026

Authentication, pagination, scopes and token revocation

What we did
We authenticated against the sandbox API, paginated a list endpoint, checked that scopes limited access, and revoked a token.
What happened
The sampled API controls worked as expected, including scope enforcement and token revocation.
What this does not prove
No load, rate-limit or production-scale testing was performed.

What these tests do not cover

The records are stronger on configuration and workflow than on anything that depends on production money movement, third parties or time. None of the following was verified, and no record should be read as evidence for it.

  • Production tax filings or legal outcomes
  • Real bank settlement
  • Carrier enrollment transmission
  • Physical device delivery
  • Third-party account creation inside every connected application
  • Production-scale performance and uptime
  • Complete global payroll or EOR execution
  • A full customer implementation
  • Long-term support resolution quality
  • Mobile app experience

How to cite these results

The records are published under CC BY 4.0. Attribute TrulyCritic and link to this page or the specific test ID.

TrulyCritic. “Rippling Test Results 2026: Nine Documented Workflows.”October 28, 2026. https://www.trulycritic.com/research/rippling-test-results-2026.

For a single record: TrulyCritic, Rippling test record [ID], October 2026. Do not cite a record as evidence of behaviour outside its stated module, configuration or limitation.

Corrections and version

These records are dated and versioned. If a result is wrong or not reproducible, send the test ID, what you observed and a source to hello@trulycritic.com. A correction is logged here with the test ID, the date and what changed. A finding is only removed if the underlying fact is wrong or the test cannot be reproduced.

Published
October 28, 2026
Records version
2026.10 · 9 records
Corrections issued
None as of October 19, 2026