Kenjo vs Personalwolke

Kenjo

Digitale Personalakte, Organigramm, Dokumentenmanagement and digitale Unterschrift are all named as modules, which clears the flat-structure anchor — but there is no evidence anywhere of change history, custom fields, or effective-dated contract and compensation records. The evidence names features; it never shows history that survives an edit, and I cannot credit what is not documented.

Personalwolke

A digitale Personalakte, Personalverwaltung and a digital payslip/reporting feature are confirmed, but the evidence is silent on org structure, custom fields, effective-dated change history and field-level permissions — I cannot verify whether a contract or salary change overwrites what was there. Excel/PDF export exists but nothing shows the export reproduces the record intact.

Kenjo

"Vorbereitende Lohnabrechnung" and "Abrechnungsmanagement" exist as named modules, but no payroll system is named — no DATEV, no Lohn und Gehalt, no export format, nothing on mid-month joiners and leavers. The only integration evidence is "APIs und Integrationen" locked inside the unpriced, demo-gated Connect tier, which is exactly the payroll-relevant capability a buyer cannot evaluate.

Personalwolke

A 'Schnittstelle Lohn/Gehalt' is offered as an option and 'vorbereitende Lohnabrechnung' plus 'Lohnverrechnungsanbindung' are claimed, but no payroll system is named, no format is documented, and there is nothing on mid-month joiners/leavers or a pre-payroll check. That is a re-typing risk dressed as a handoff.

Kenjo

Urlaubsverwaltung, Zeiterfassung, a Zeiterfassungs-Terminal and Schichtplanung are all evidenced, so this is more than a timer — but there is no evidence of automatic entitlement or carry-over, sickness recording, break and rest rules, or any documentation of the ArbZG recording duty. The one compliance signal, "Warnmeldungen bei Nichteinhaltung des Arbeitsrechts," sits in the unpriced Connect tier; working-time law is not an upsell.

Personalwolke

Working-time capture via start/stop, web/app and terminals is real, and Urlaubsaliquotierung for entry, part-time, exit and Karenz plus 'komplexe Zeitwirtschaft inkl. Berechnung' gives genuine depth. But nothing documents the ArbZG recording duty, tamper-evident records, holiday calendars, overtime accounts or works-council-configurable limits — the compliance posture around the recorded data is unevidenced.

Kenjo

An ATS exists as a priced add-on (249 €/month) and Onboarding/Off-Boarding is a named module, so both halves of the join path exist — but there is no evidence of a careers page, structured stages, or the candidate-to-employee handover without re-entry. And I must be precise: the 6-month application deletion and 2-year talent-pool rule in govern people applying to Kenjo itself, not a product capability that deletes my applicants' data on schedule; a product-side deletion date is not evidenced.

Personalwolke

The module list is Time, Travel, Project Time and HR-Expert; nothing evidences applicant tracking or onboarding, and therefore nothing on the automated applicant deletion at a stated deadline my office requires. Silence on the join path is a finding, not a neutral.

Kenjo

No DPA is published or offered anywhere in this sheet — for the processing I would actually be handing over, that is disqualifying at this score level. The privacy policy is decent for Kenjo's own house: DPO contact, Art. 15–21 rights, no profiling, named subprocessors with countries, and "automatisch gelöscht" retention for transcripts and analytics data — but every one of those auto-deleting retention periods covers Kenjo's website, sales and own-hiring data, not customer employee records. Nothing evidences a product role model beyond tier packaging, an audit log of who read what, configurable retention per data category, or monitoring I could switch off in front of a works council.

Personalwolke

The DPA exists only 'auf Anfrage' — an unpublished DPA is a finding by my standard — and the evidence shows no retention periods, no executable deletion, no role model beyond none stated, no audit log of who read what; only SSL transmission and 2FA as technical basics. That the vendor's own site runs Hotjar for behavioural analysis does not encourage me about analytics habits.

Kenjo

The contracting entity is solidly German — Kenjo GmbH, Berlin, Amtsgericht Charlottenburg HRB B 183681B, German VAT — and several subprocessors are published with countries and addresses.

Personalwolke

The server stands in Austria within the EU and the imprint names an Austrian Firmenbuch entity, but that entity (Workflow HR Systems GmbH) does not match the vendor of record (Workflow EDV GmbH), leaving the contracting party unclear. More importantly, no product subprocessor list is published at all — I cannot tell whose hands the data passes through, and website analytics tools are the only processors named.

Kenjo

Starter at 6 € and Growth at 10 € per employee, the monthly/annual toggle with 10 % saving, the 249 € recruiting add-on and the onboarding fee from 400 € are all public — more than most vendors show. But Connect, which holds the APIs, integration and compliance-warning capabilities a payroll handoff depends on, is "DEMO BUCHEN" with no price, and minimum term and VAT treatment are unstated, so an HR lead still cannot compute the full annual invoice.

Personalwolke

The model is public — monthly rent based on employee count and modules, 30-day free trial, an acknowledged one-time setup fee and multi-module discounts — but not a single euro figure for any tier, module, setup fee or minimum appears. An HR lead cannot compute even a rough annual invoice from these pages.