Clean payroll prep
Operational reports and payroll-prep exports keep provider handoff files separate from day-to-day reports.
Timekeeping
Employees can enter time or clock in/out based on policy. Admins review worked hours, paid non-work time, drive time, and location context when enabled.
Launch posture
Core launch surface
Time entry, clock flows, leave context, and payroll-prep exports are launch-critical product paths.
Employee time entry and admin timecard review
Capture manual time-entry, clock, and admin review states after final demo data is reset.
These points describe shipped product behavior or explicitly scoped setup readiness. Final screenshots and recordings will be captured from the product after demo data is frozen.
Operational reports and payroll-prep exports keep provider handoff files separate from day-to-day reports.
Time entry mode, browser location capture, geofence policy, break minutes, review state, and payroll-period locks are enforced through server route seams rather than only through UI controls.
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
The current path supports controlled trial activation. No-card demo tenants remain support-approved so capacity, provider setup, sensitive uploads, and data-retention expectations stay bounded.
Paid access normally ends at the end of the billing period, then the workspace enters a 30-day export/reactivation window unless a verified deletion request is completed earlier.
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
Launch mobile support is responsive web/PWA-oriented. Employees get scoped offline read context and supported queued writes with visible sync states; native app-store apps and broad offline admin operation are not part of launch scope.
Yrka uses optional analytics on the public site to understand page interest. The authenticated app does not load GA4.