Time Tracking & Attendance
ISGUS ZEUS
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ISGUS GmbH · www.isgus.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ISGUS ZEUS, judged from the vendor's American pages, is strongest on time capture and absence and planning: the judges credit own-manufactured badge, fingerprint and face-recognition terminals in three named models, a mobile app that saves bookings on the device when the connection drops and syncs them on reconnect, leave requests and sick leave with approvals and visible balances, and scheduling with substitution suggestions and planner-approved shift swaps. It is weakest on working time law: beyond a promise of reliable, audit-ready records, the judges found no public information on break, daily-maximum or rest-period rules under German working-time law, and the captured compliance copy addresses US labor laws. Sovereignty scores 1-2: the pages name ISGUS US, LLC as copyright entity, describe it as part of ISGUS in Germany, state no region for the ISGUS Cloud, and offer an on-premises installation. Project and billing sits at 4; payroll export spans 4 to 6 around the one named coupling, SAP HCM. Scores cluster tightly, and pricing transparency scores 0, with no public prices on the captured pages.
Speaks for it
- Own-manufactured badge, fingerprint and face-recognition terminals plus shop-floor kiosks
- Mobile-app bookings are saved on the device when the connection drops and synchronised on reconnect
- Leave requests, sick leave, approvals and visible balances, with substitution suggestions and planner-approved shift swaps
- A named SAP HCM coupling with automatic transfer in monthly, weekly, daily or individual cycles
- An on-premises installation offered alongside the ISGUS Cloud
Held against it
- No public information on break, daily-maximum or rest-period rules under German working-time law, with the captured compliance copy aimed at US labor laws
- No public information on corrections with an audit trail of who changed a booking
- No public information on rates, billable flags, budget tracking or an invoice-ready export
- No public information on night, Sunday and holiday surcharges or on a lock step before transmission, and no payroll provider named beyond SAP HCM
- The ISGUS Cloud's region is not stated and no subprocessor information is published, with ISGUS US, LLC as the named copyright entity
Best for
- You run shift-based sites with weak connectivity and need own-made terminals plus a mobile app that keeps recording through outages
- Your planning burden is substitutions and employee-initiated shift swaps that need planner approval with justification
- You already run SAP HCM and want time data transferred automatically in monthly, weekly, daily or individual cycles
- Your policy requires keeping data on your own infrastructure, and a published on-premises installation matters
Avoid if
- You carry the German working-time recording duty and need documented break, daily-maximum and rest-period enforcement
- You invoice clients from tracked time and need rates, billable flags and an invoice-ready export
- Your payroll runs on a provider other than SAP HCM and you need a named system with night, Sunday and holiday surcharge handling
- Your procurement requires a stated cloud hosting region and published subprocessor information before signing
The scores
Capture in the real workplace
Show reasoningHide reasoning
How this is scored
How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
0 — One browser timer and nothing else; anyone away from a desk records nothing.
3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.
5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.
8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.
10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.
The Operations Lead
Own-manufactured badge, fingerprint and face-recognition terminals plus shop-floor kiosks and a mobile app for bookings, requests and approvals mean desk, workshop and field each have a real capture path, and bookings made offline are stated to be saved on the device and synchronised on reconnect. We found no public information on GPS or geofenced check-in or on bulk corrections with an audit trail of who changed what, which keeps it below the top band. 1 2 3
The Payroll Officer
Self-manufactured badge, fingerprint and face-recognition terminals plus a branded app with offline booking storage and automatic sync give desk, shop-floor and mobile workers first-class capture paths. I found no public information on GPS or geofenced check-in limits, nor on a bulk correction path with a record of who changed what — which is what I need before I close a month. 1 2 3 9
The Works Council Advocate
Own-manufactured badge, fingerprint and kiosk terminals sit beside a mobile app whose offline behaviour is stated plainly — bookings are stored on the device and synchronised on reconnect — so desk, deskless and shop-floor capture all look first-class. We found no public information on GPS or geofenced check-in, nor on a correction workflow with approval and an audit trail of who changed what. The fingerprint and face-recognition terminals would be a co-determination negotiation before any works council approval. 1 2 3
The Agency Owner
They manufacture their own badge, fingerprint and face-recognition terminals plus shop-floor kiosks, and the mobile app saves bookings on the device and syncs them once the connection returns — capture paths for desk, shop floor and field all exist. I found no public information on geofenced or GPS check-in, and none on a correction workflow with an audit trail of who changed what, which is what keeps recorded time defensible. 1 2 3 9
The Field Supervisor
This is the part they clearly get right for a site with no signal: they manufacture their own badge, fingerprint and face-recognition terminals including shop-floor kiosks, and the mobile app saves every booking on the device when the connection drops and syncs it when the line comes back — that survives a basement at 6am. Requests and approvals run through the app with a push to the supervisor, so a foreman can settle a fix on the spot. I found no public information on geofenced check-in, bulk corrections, or any audit trail showing who changed a punch. 1 2 3 7 9
The Skeptic
A manufacturer of its own badge, fingerprint and face-recognition terminals in three named models, plus a mobile app whose bookings are stored on the device when the connection drops and synchronised on reconnection — capture breadth a buyer can check by model number. I found no public information on GPS or geofenced check-in and its limits, and none on bulk corrections attributable to a person with an audit trail of who changed what. 1 2 3 9
Working-time law & audit record
Show reasoningHide reasoning
How this is scored
Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.
0 — Hours are summed and nothing else; no break handling, no limits, no retention statement.
3 — Break deduction exists but is a flat rule; no daily maximum or rest-period checks, and no stated retention period.
5 — Configurable break rules, warnings on the 8/10-hour daily maximum and the 11-hour rest period, and per-employee reports covering the recording duty.
8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, and an export built for an inspection.
10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.
The Operations Lead
The pages promise reliable, audit-ready records and scheduling that supports compliance with labour regulations, and terminals show time accounts and last punches, but we found no public information on break and rest-period rules, eight- and ten-hour limits, a retention period or an export built for an inspection. The captured compliance language addresses US labor laws, and nothing maps the record to the German recording duty or the ArbZG. 3 7 8
The Payroll Officer
The pages promise "reliable, audit-ready records" and warn that mishandled breaks and overtime bring penalties, but that is positioning, not a rule set — I found no public information on configurable break or rest-period enforcement, daily maximums, retention, or tamper-evident change history. The compliance copy I did find is aimed at US labor law, and the German recording duty is not addressed in what was captured. 3 7
The Works Council Advocate
Beyond the words "reliable, audit-ready records" and a claim of compliance with labour regulations, the captured pages frame their labour-law help around US labor law. We found no public information on break rules, daily maximum or rest-period checks, retention periods, or tamper-evident change history — the material a works council needs under the German recording duty. Per-employee punch journals exist as reports, but that alone does not make a statutory record. 3 7 8
The Agency Owner
The captured pages pitch US labor-law compliance and 'audit-ready records' as a claim without detail, and mention overtime and mishandled break periods only as risks to avoid. I found no public information on configurable break rules, warnings on the daily maximum or the eleven-hour rest period, a retention period, or anything mapping features to the German recording duty. 4 5 7
The Field Supervisor
Beyond a claim of reliable, audit-ready records, terminals showing time accounts and remaining holidays, and a general promise of compliance with labour regulations, the captured pages give nothing on break rules, the daily maximum, the eleven-hour rest period, retention, or an export built for an inspection — and the compliance talk I did find is aimed at US labor law. For a German site carrying the recording duty, I found no public information that the ArbZG rules are modelled at all. 3 6 7
The Skeptic
Every compliance sentence I can find is a claim with no feature behind it: 'audit-ready records' and 'legal accuracy' with no module named, no retention period, no change history, and plausibility checks at the terminal with no published rule behind them. The captured pages frame compliance around US labor laws; I found no public information on how any of this satisfies break, daily-maximum or rest-period rules under German working-time law. 3 7
Absence & shift planning
Show reasoningHide reasoning
How this is scored
Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.
0 — No absence handling; vacation lives in a separate calendar or spreadsheet.
3 — Vacation requests with approval, but entitlement is manual, carry-over is not handled and there is no rostering.
5 — Automatic entitlement and carry-over, sickness recording, an absence calendar, and basic shift planning with availability.
8 — Public-holiday calendars per location, pro-rata entitlement, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.
10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.
The Operations Lead
Vacation requests and sick leave with approvals and visible balances, plus a roster with under- and over-staffing updates, holiday calendars, substitution suggestions, planner-approved shift swaps and notifications through terminal, mailbox, email and push — that is the half of attendance I actually fight with, and it is evidenced. We found no public information on pro-rata entitlement or rest-period checks on shift templates, which is what holds it below the top. 6 7 8
The Payroll Officer
Leave requests, approvals, balances, sick leave and holiday calendars are evidenced, and the scheduling side is genuinely built out: substitution suggestions, shift swaps with planner approval and justification, qualifications and staffing-level views in real time. The gaps are on my side of the ledger — I found no public information on automatic entitlement, carry-over or pro-rata calculation, and no rest-period checks when a roster is published. 3 6 7 8
The Works Council Advocate
Leave requests and approvals, balances, sick leave, holiday calendars and a roster showing staffing levels, qualifications and availability are all evidenced, with updates on under- and over-staffing. The substitution suggestions and the employee-initiated shift swap with planner approval and justification are exactly the workflows that keep a plan honest. We found no public information on automatic entitlement and carry-over, pro-rata rules, or rest-period checks inside the roster. 6 7 8
The Agency Owner
Vacation requests and sick leave are automated with approvals and visible leave balances, and the swap and substitute machinery is genuinely strong — planner approval with justification, interactive acceptance, and multi-channel shift offers when staffing runs short. I found no public information on automatic entitlement calculation, carry-over, or rest-period checks inside the plan, which is what separates a roster from a compliance risk. 6 7 8
The Field Supervisor
Vacation requests and sick leave are recorded with approvals and visible leave balances, and the planning side is genuinely site-ready: shift offers go out via the terminal messenger, mailbox, email and push, substitutes are suggested the moment someone drops out, and swaps are agreed through the mobile app and approved or rejected with a justification. Under- and over-staffing updates and holiday calendars are mentioned. I found no public information on automatic entitlement calculation, carry-over, or rest-period checks before a roster is published. 3 6 7 8
The Skeptic
Leave requests, sick leave and balances are evidenced, and Staff Scheduling is concrete: substitution suggestions with interactive accept or reject, shift swaps the planner approves with justification, holiday calendars, qualification and availability views, and updates on under- and over-staffing. I found no public information on automatic pro-rata entitlement or on rest-period checks applied when shift templates are built. 6 7 8
Project, cost-centre & billing
Show reasoningHide reasoning
How this is scored
Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.
0 — Attendance only; no project, task or cost-centre dimension at all.
3 — A free-text note or a single project field, with no rates, no billable flag and no per-project reporting.
5 — Projects and tasks with a billable flag and per-project reports, plus a rate per person or per project.
8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.
10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.
The Operations Lead
Cost centres, order and project start and end, quantities and job costing per customer, facility and task recorded right at the terminal is a genuine allocation spine for a workshop operation. We found no public information on rates, billable flags, per-project reporting or any invoice-ready export, so the recorded time cannot be shown to carry through to money. 3 8 9
The Payroll Officer
Recorded time can carry customer, facility, task, cost-centre and order data straight from the terminal, with real-time import of customer sales orders — the allocation dimension is real and multi-level. The billing half of the journey is undocumented: I found no public information on rates, a billable flag, budget tracking or any invoice-ready output. 1 3 9
The Works Council Advocate
Recorded time can carry customer, facility, task, cost-centre, order and quantity structure, assigned manually or automatically at the terminal — a workshop fit rather than an agency one. We found no public information on rates, billable flags, budget tracking or an invoice-ready export, so we cannot see the time becoming revenue from these pages. 1 3 8 9
The Agency Owner
The allocation skeleton is solid: terminals record cost centres and order or project start and end, labour times differentiate per customer, facility and task, and customer sales orders import in real time — more structure than most attendance tools ever get. But an agency lives on the rate card and the invoice, and I found no public information on rates per person or project, a billable flag, budget tracking with warnings, or any invoice-ready export. 1 3 8 9
The Field Supervisor
Booking the work is well covered — terminals take cost centre, order and project start and end, quantities and operations, and labour times can be tracked and differentiated per customer, facility and task, assigned manually or automatically. But that is where it stops for a shop that has to invoice: I found no public information on rates, a billable flag, per-project reporting or an invoice-ready export. 1 3 8 9
The Skeptic
Job costing is real and shop-floor-shaped — times per customer, facility and task, cost centres and order start and end booked at the terminal, sales orders imported in real time, employee validation tables keeping assignments clean. It is a production-data story rather than a billing one: I found no public information on rates, billable flags, budget tracking or an invoice-ready export. 3 8 9
Payroll handoff
Show reasoningHide reasoning
How this is scored
How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.
0 — No payroll path stated; the month leaves as a spreadsheet someone retypes.
3 — Generic CSV said to be usable for payroll, with no named system, no defined format and no handling of surcharges.
5 — A named payroll integration or a documented export format for at least one major system, covering hours, absences and overtime.
8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.
10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.
The Operations Lead
There is a named coupling with SAP HCM, automatic data transfer into the HR system in monthly, weekly, daily or individual cycles, and a claim of seamless interfaces for any payroll processing provider in the market. That provider claim names no second system, and we found no public information on surcharge handling, a lock step before transmission or retro corrections after the close — the adaptation to individual needs reads as project work rather than a maintained integration. 2 9 11
The Payroll Officer
There is one named, vendor-maintained coupling into SAP HCM, transfers run automatically on monthly, weekly, daily or individual cycles, and the broader claim is seamless interfaces for any payroll provider in the market — which names no one else and defines no format. For my run the decisive pieces are absent: no public information on night, Sunday and holiday surcharges, no lock step before transmission, and no handling of corrections that arrive after the close. 2 9 11
The Works Council Advocate
A named coupling with SAP HCM, plus an automatic transfer of time data in monthly, weekly, daily or individual cycles, takes retyping out of the month-end. The promise of seamless interfaces for any payroll provider in the market is generic; we found no public information on DATEV or other named payroll systems, on surcharge handling for night, Sunday and holiday work, or on a lock step before transmission. 2 9 11
The Agency Owner
The month moves automatically to avoid 'typing and calculation errors', in monthly, weekly, daily or individual cycles, and the SAP HCM coupling is a named, concrete integration. Beyond SAP the pages promise 'seamless payroll interfaces for any payroll processing provider in the market' without naming them, and I found no public information on surcharge handling, mid-month changes, or a lock step before transmission. 2 9 11
The Field Supervisor
There is a dedicated SAP Communication module coupling time and attendance to SAP HCM, transfer runs in monthly, weekly, daily or individual cycles, and the vendor states seamless payroll interfaces for any payroll processing provider in the market with automatic transfer to avoid retyping. I found no public information on night, Sunday and holiday surcharges, a lock step before transmission, or a named German provider such as DATEV. 2 7 9 11
The Skeptic
'Seamless payroll interfaces for ANY payroll processing provider in the market' is a sentence no buyer can verify, and the software is described as 'prepared for' payroll integration and adapted to individual needs. The one named coupling is SAP HCM; I found no public information on any named payroll accounting system, on night, Sunday and holiday surcharges, or on a lock step before transmission. 2 9 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.
0 — Non-EU vendor and contracting entity, hosting region unstated or non-EU, subprocessors not named.
3 — EU hosting offered as an option, but the contracting entity is non-EU or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but the subprocessor chain includes non-EU providers without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.
The Operations Lead
The captured pages contract under ISGUS US, LLC with no hosting region stated for the ISGUS Cloud and no subprocessor list published, and we found no public information on where hosted data would sit or who processes it. The German parentage and the on-premises option keep this off the floor, but as a buyer weighing European sovereignty I cannot see the residency or the processing chain on public pages. 2 7
The Payroll Officer
Every captured page names ISGUS US, LLC as the entity, the German parent is mentioned, and beyond that the picture is undocumented — I found no public information on where the ISGUS Cloud runs, the contracting jurisdiction, or a single subprocessor. The one solid point for a European buyer is a genuine on-premises option, which keeps the data on your own floor. 2 7 8
The Works Council Advocate
The captured pages give an American copyright and contracting entity, ISGUS US, LLC, described as part of the long-established ISGUS in Germany, and we found no public information on the ISGUS data centre's region or on any subprocessor. The genuine on-premises installation option is the one lever of control we can see, and for co-determination that is worth something. 2 7 8
The Agency Owner
The captured pages are the American arm: copyright sits with ISGUS US, LLC, which describes itself as part of the long-established ISGUS in Germany, the data-centre region is not stated, and no subprocessor list is published. The on-premises option is the one genuine sovereignty lever here; on where cloud data actually lives, I found no public information. 2 7 8
The Field Supervisor
The captured pages present a US contracting entity, ISGUS US LLC, as part of the long-established German parent, and while an ISGUS data center and a full on-premises installation are both offered, the region of that data center is not stated and no subprocessor list is published. For my sites the on-premises path is the one thing keeping this off the floor; everything else about where the data lives is undocumented on these pages. 1 2 7 8
The Skeptic
The pages put ISGUS US, LLC as the copyright entity, described as part of ISGUS in Germany, while hosting is an 'ISGUS data center' with no region stated; I found no public information on data residency, the contracting entity's jurisdiction, ownership, or a single subprocessor. An on-premises installation path is offered and genuinely published, which is the one documented escape for a buyer whose data must stay in-house. 2 7 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A per-user headline exists, but hardware, modules or a minimum seat count are unpriced or unmentioned.
5 — Per-user prices public for the main tiers with the billing period stated, but at least one commonly needed piece (terminal hardware, planning module, payroll export) sits in an unpriced bundle.
8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.
The Operations Lead
No prices appear on the captured pages — no per-user figure, no module price, nothing for the terminals — only a demo, a free consultation and an ROI calculator, which is a sales conversation rather than a number. I cannot compute my annual invoice for 200 heads from public information. 1 6
The Payroll Officer
I found no public prices at all — no per-user figure, no module pricing, no terminal pricing, nothing from which to compute an annual invoice. The path offered is a free consultation, a demo and an ROI calculator that speaks to savings rather than cost. 1 11
The Works Council Advocate
We found no public price information on any captured page — the offered path is a free consultation, and the ROI calculator speaks to savings rather than to a per-user price, term or invoice. A buyer can compute nothing from these pages. 1 6 11
The Agency Owner
There is not one public price on any captured page — every route ends in a free consultation, a demo or a downloadable brochure. An ROI-Calculator is named in the product menu but no pricing facts are captured, so a buyer cannot compute an annual invoice for their headcount from public pages alone. 1 7
The Field Supervisor
No price appears on anything I was shown — not per user, not for modules, not for the terminals they manufacture themselves; the route to a number is a free consultation, a demo and downloadable brochures. The ROI calculator on the site is about return on investment, and I found no public information that would let a buyer compute an annual invoice for a given headcount. 1 3 6
The Skeptic
A vendor that manufactures its own terminals shows no price for any of them, and I found no public information on per-user fees, module prices, billing periods, minimum terms or setup costs. The buyer's route to any number is a free consultation, a demo and an ROI calculator — a return figure, not an invoice. 1 3
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- We found no public information on pricing on the pages we read (isgus.com, isgus.com/software-modules/time-recording-from-isgus-with-the-zeus-mobile-app-we-make-time-tracking-mobile, isgus.com/terminals/terminals-for-time-data-management, isgus.com/solutions/digital-overview-of-the-working-time-frame-of-your-employees, isgus.com/workforce-management-software-provider/compliance-with-working-time-regulations, isgus.com/solutions/staff-scheduling and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.isgus.com Checked 29 Sep 2026 Details →
- 2 Capture in the real workplace — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 3 Capture in the real workplace — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 4 Working-time law & audit record — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 5 Working-time law & audit record — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 6 Absence & shift planning — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 7 Absence & shift planning — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 8 Project, cost-centre & billing — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 9 Project, cost-centre & billing — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 10 Payroll handoff — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →
- 11 Payroll handoff — found from sitemap www.isgus.com Checked 1 Oct 2026 Details →