whats-best.ai
Search Sign in

Absence Management

Rippling

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Rippling Ireland Limited · www.rippling.com

Report an error on this page Is this your product? →

Link to this page

Rippling: AI-assisted analysis on whats-best.ai Rippling: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Rippling at a glance

Vendor
Rippling Ireland Limited
Headquarters
Not stated on the vendor’s pages as of 13 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 13 Oct 2026
Free plan
Not stated on the vendor’s pages as of 13 Oct 2026
Panel verdict
The AI panel rates Rippling 1.5/5, the mean of 6 judges. Rippling is an all-in-one HR, payroll, IT and finance platform from Rippling People Center Inc. how scores are made
As of
Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources

Rippling alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

Treats every sick day as special-category data, because the law does. Asks who can see a reason or a certificate, how long absence records are kept and deleted, whether access is logged, where the data is hosted, and which subprocessors send the push notification that says someone is ill.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Panel median The Data Protection Officer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Data Protection Officer
Entitlements & German leave rules 1.5 of 5 1.5 of 5
Requests, approvals & team calendar 3 of 5 2.5 of 5
Sick leave, eAU & continued pay 0 of 5 0 of 5
Payroll handover, time tracking & API 3 of 5 3 of 5
Health data, access & works council 2 of 5 1.5 of 5
European sovereignty 0.5 of 5 0.5 of 5

Entitlements & German leave rules

How this is scored

Whether the tool computes leave the way German and Austrian law and contracts do: entitlements per contract and working-time model, part-time proration, carry-over and expiry with the required notice, public holidays per federal state, half days and hourly leave, and special leave types.

0 — A fixed number of days per person typed in by hand; no carry-over, no proration and no public holidays.

3 — Annual entitlements and national public holidays, with carry-over as a manual adjustment and no statement on part-time or regional holidays.

5 — Entitlements per employee with automatic proration for joiners, leavers and part-time working days, public holidays per German federal state or Austrian region, half days, configurable carry-over with an expiry date, and custom leave types.

8 — Several working-time models per employee with changes over time recalculated, hourly leave, carry-over expiry with automatic notices to employees before leave lapses, special leave and parental leave types with their own rules, and entitlement changes logged.

10 — Leave law modelled and documented: entitlement rules per contract or collective agreement, statutory minimum and contractual leave kept apart where they expire differently, balances recalculated retroactively with an audit trail, and the rules a tool applies published in its help centre.

Report an error

The Data Protection Officer

The developer pages show leave policies, leave types, accruals and balances as first-class objects, and a request can carry custom hours on its start and end dates. We found no public information on part-time proration, public holidays per German federal state, carry-over with expiry dates, or German special-leave and parental-leave types. For a German buyer the leave engine's German specifics rest on nothing more than a generic compliance-in-185-countries claim. 3 6 8 5

Report an error

Requests, approvals & team calendar

How this is scored

The everyday flow: an employee requests leave on a phone, the right person approves, a substitute is named, and the team can plan around it — judged on configurable approval chains and on what colleagues are allowed to see.

0 — Leave requested by email or in a shared calendar; no approval step and no record of who approved.

3 — Requests with a single approver and a team calendar, but no substitutes, no blocking rules and every absence reason visible to everyone.

5 — Mobile requests and approvals, approvers per team or department, substitutes named on the request, a team calendar that shows absence without the reason, email or push notifications, and calendar sync.

8 — Multi-level approval chains, minimum staffing rules or blackout periods, delegation while the approver is away, configurable calendar visibility per role, Microsoft Teams or Slack integration, and every request, approval and cancellation logged.

10 — Approval logic that matches a real organisation: rules per location, team and leave type, conflicts checked against staffing and shift plans before approval, a complete history per request, and reporting on pending and overdue approvals.

Report an error

The Data Protection Officer

The approval machinery is real: multi-approver logic, re-routing when the primary approver is on vacation, routing by department and tenure, reminders, and each leave request carrying a reviewer and a review timestamp, with mobile requests in the app. We found no public information on the team calendar side — substitutes named on the request, what a colleague may see about another's absence, or calendar sync — and that visibility question is the one my lens weighs heaviest. 3 7 8 11

Report an error

Sick leave, eAU & continued pay

How this is scored

Sick notifications and the German electronic certificate of incapacity: whether the tool retrieves the eAU from the health insurer itself or through a named payroll system, how sick days are counted towards the six-week continued-pay and BEM thresholds, and how child-sick days and certificates from private insurance are handled.

0 — Sickness recorded as another leave type with no word on the eAU, certificates or thresholds.

3 — A sick-leave type with a document upload, and "eAU" mentioned without saying who retrieves it or how.

5 — Sick notification by the employee in the app, the eAU retrieval process documented — by the tool itself or via a named payroll system — with the retrieval status visible to HR, and child-sick days as a separate type.

8 — eAU retrieval from the statutory health insurers documented end to end with the certified software named, retrieval results written back to the absence, sick days counted towards the six-week continued-pay limit per illness, BEM thresholds flagged to HR only, and paper certificates for privately insured employees handled.

10 — Sick leave handled as the regulated process it is: eAU retrieval automated with error and follow-up handling, continued-pay and sickness-benefit transitions tracked, BEM invitation workflow supported, reasons and documents restricted to named roles, and the whole process documented in the help centre.

Report an error

The Data Protection Officer

Sickness appears nowhere as its own process: no word on the eAU, on certificates, on how sick days count toward the six-week continued-pay limit, or on child-sick days. Leave types and leave requests exist as generic objects in the API, but every regulated step of German sick leave is undocumented. A sick day is special-category data; a buyer cannot learn from these pages how the product treats it. 8 12

Report an error

Payroll handover, time tracking & API

How this is scored

Getting absences into the payroll run with the right codes and keeping balances consistent with time tracking: exports or integrations for the payroll systems German companies use, time-account interaction, and an API.

0 — No export beyond a screen list; absences are retyped into payroll.

3 — A CSV or Excel export of absences per month, with no named payroll system and no API.

5 — A documented export or integration for DATEV (LODAS or Lohn und Gehalt) or another named German payroll system, absence types mapped to payroll codes, and a documented API.

8 — Several named payroll integrations, absence and overtime balances shared with time tracking, configurable payroll codes per leave type, monthly closing that locks past periods, webhooks, and an API with published limits.

10 — Payroll handover that closes the month: absences, sick days and eAU results delivered to payroll in its own format with corrections flagged, a period lock with an audit trail, a versioned API with a deprecation policy, and the full absence history exportable at contract end.

Report an error

The Data Protection Officer

German payroll is claimed ITSG-certified and DATEV-integrated, time and payroll sit in one system without manual transfer, and the public REST API covers leave requests, accruals and balances with scopes and bearer authentication. We found no public information on absence-to-payroll code mapping, monthly period locks, webhooks or published API limits. The global payroll API documentation requires signing in with an account, which a buyer cannot audit before contracting. 1 3 8 9 5

Report an error

Health data, access & works council

How this is scored

What the tool does with data that is health data in law: who can see a sickness reason or certificate, how long absence records are kept, whether access is logged, and whether the vendor documents what a works agreement on absence recording needs.

0 — Nothing stated about who sees sick data or how long absences are kept.

3 — Roles for employees, managers and admins, but sickness reasons and documents visible to managers by default, and no retention setting.

5 — Sick-leave reasons and certificates restricted to HR by configurable permissions, colleagues see only "absent", retention or deletion of absence records configurable, and a DPA available.

8 — Field-level permissions per leave type, access to health-related records logged, retention rules per record type with automatic deletion, employees able to see their own records, and documentation aimed at works councils or a works agreement.

10 — Health data governed and evidenced: Art. 9 GDPR processing explained per feature, deletion runs logged and reportable, audit logs exportable, no analytics or AI features run on sickness data without explicit configuration, and the vendor publishing a template or checklist for the works agreement.

Report an error

The Data Protection Officer

The permission model is genuinely granular — profiles bound to attributes rather than persons, scoped to a reporting line or a whole department, with view, edit and approve actions — yet we found no public information on who may see a sickness reason or certificate, on retention or deletion of absence records, on access logging, or on a data-processing agreement. Nothing is aimed at works councils or a works agreement. And the AI features are marketed as running across all modules on one shared employee-data basis, including burnout prevention, with no public word on whether sickness data is fenced off from them — exactly the question a works agreement will ask. 1 3 11 12

Report an error

European sovereignty

How this is scored

Where absence and sickness data lives, who the contracting entity is, and who the subprocessors are — including email, push-notification and support providers. Independently sourced by the sovereignty pipeline.

0 — Non-EU vendor and contracting entity, hosting unstated, and subprocessors unnamed.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — email, push notifications, analytics or support — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, and a DPA that covers sickness data as special-category processing.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, and certification published.

Report an error

The Data Protection Officer

The group sits in San Francisco, the European entity is named only in the German imprint, and the captured pages leave data residency, ownership and every subprocessor — including whoever would deliver a push notification saying an employee is ill — unnamed. No EU hosting commitment, no subprocessor list with locations, and no certification is published. From public pages a buyer cannot tell where absence and sickness data would live or who else touches it. 4 12

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per employee or per user, which features (eAU, payroll export, time tracking) sit in which tier, minimum users and the minimum term.

0 — No public prices at all; every tier is a sales conversation.

3 — A starting price exists, but the pricing basis or which features it covers is unstated — the invoice is unknowable.

5 — Tier prices public with the pricing basis given, but at least one commonly needed piece (eAU, payroll export, time tracking, extra admins) is unpriced or "on request".

8 — Every tier priced publicly with its basis, add-on prices listed, minimum users, minimum term and VAT treatment given.

10 — Complete price computability: the annual invoice derivable for a given headcount and feature set, with every add-on, setup fee and overage published.

Report an error

The Data Protection Officer

The captured pricing page names module groupings and even asks whether modules can be bought separately, but not one figure appears — no per-employee price, tier price, minimum users, minimum term or VAT treatment. Numbers come only through a demo request or account sign-in. From public pages alone the annual invoice is not computable. 1 2 1

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined — uncited Report an error

Questions about Rippling

Is Rippling European?

No. whats-best.ai classifies Rippling as Rest of world.

Where does Rippling store data?

Not stated on the vendor’s pages as of 13 Oct 2026.

Does Rippling have a free plan?

Not stated on the vendor’s pages as of 13 Oct 2026.

What are the best alternatives to Rippling?

As of 15 Oct 2026, the panel rates Kenjo (3/5), flair (2.5/5) and HRlab (2.5/5) highest among the other 16 Absence Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Kenjo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Rippling alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Rippling? Tell us Report an error on this page

Sources (12)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.rippling.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  2. 2 Pricing page www.rippling.com Checked 13 Oct 2026 Details →
  3. 3 Time and absence www.rippling.com Checked 13 Oct 2026 Details →
  4. 4 Legal notice www.rippling.com Checked 13 Oct 2026 Details →
  5. 5 Entitlements & German leave rules — found from sitemap developer.rippling.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  6. 6 Entitlements & German leave rules — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
  7. 7 Requests, approvals & team calendar — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →
  8. 8 Requests, approvals & team calendar — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
  9. 9 Payroll handover, time tracking & API — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
  10. 10 Payroll handover, time tracking & API — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
  11. 11 Health data, access & works council — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →
  12. 12 Health data, access & works council — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →