Hospitality & shift-based businesses
Useful for organizations that need one place to manage employees, scheduled hours, actual punches, breaks, exception tracking, and export-ready monthly records.
Noesia Smart Waiter / Module Documentation
Pro Event-Driven IoC Isolated/X-Core Micro-Frontend Global Payroll Framework
PAYROLL
Enterprise-ready Payroll & Time Attendance framework for WordPress. Built as a global framework and localized through country bridge adapters, Payroll acts as the operational core for employee records, weekly planning, actual punches, break tracking, PIN / QR access, queue continuity, and immutable monthly exports. The module is intentionally positioned as a high-control foundation: it includes the structural logic and integration hooks, while local legal compliance and country-specific deployment must be validated and configured by a responsible developer or agency before production use.
Compliance Notice: Noesia Smart Waiter provides Payroll as an enterprise-ready structural framework. Country-specific legal compliance depends on local labor law, collective agreements, payroll practice, and state integrations. Customers should use a qualified local developer, integrator, or advisor to validate regional rules and implement the appropriate bridge adapter and company-specific mappings before production use.
Who is it for
Built for companies that need serious attendance control without losing implementation discipline
Managers, HR & Accountants
Useful when leadership needs clarity over who worked, where deviations happened, what is pending sync, and what has been finalized into immutable month archives.
Agencies, Integrators & ERP Partners
Perfect for custom B2B deployments and white-label local payroll projects. The module provides the structural base and developer bridge hooks to map local state rules responsibly.
Main Features
What the Payroll module actually delivers
Payroll Command Center
- Live overview for employees, scheduled hours, actual hours, and pending sync items.
- Queue and sync state visibility with retry actions.
- System health and integration awareness inside one operational surface.
Planner and workforce scheduling
- Month and week planning modes.
- Planner selection, focus date control, and range clearing tools.
- Worker assignment management and planner-specific control.
- Structured path to final month locking and export.
Staff / Employee directory
- Employee profiles with role, department, country code, bridge profile, hourly rate, and overtime rate.
- Active / inactive control for staff lifecycle management.
- Default weekly schedule template for planner convenience.
QR badge and PIN access
- Each worker can be authenticated with PIN or QR badge logic.
- Staff portal login supports PIN keypad and QR scanner flow.
- Fast kiosk-friendly access without forcing complicated manual workflows.
Clock in / out, breaks, and history
- Clock in, clock out, start break, and end break actions.
- Attendance history by employee and by month.
- Actual event history, audit trail, deviations, and exception-aware records.
- Support for unscheduled actual punches that require review.
Immutable lock and archive flow
- Lock Month & Export workflow for finalized periods.
- Immutable archive payload generation.
- Safer handoff to accountants, payroll middleware, or state-facing processes.
Offline queue & store-and-forward
- Queue-enabled transmission model with store-and-forward architecture.
- Offline timestamping and continuity-aware payload storage.
- Useful when dispatch must be retried instead of silently lost during connection loss or remote endpoint downtime.
Country bridge slots and developer hooks
- Global, Greece / Ergani, United States / FLSA, United Kingdom / HMRC, and EU bridge slots already exist as structural profiles.
- Hook points include country profile registration, queue enrichment, payload mapping, bridge contracts, and dispatch actions.
- Built to connect responsibly with state systems, ERP connectors, or country-specific middleware.
How to Access It
Where Payroll lives inside the platform
Admin path: open the Noesia Smart Waiter admin shell and select Payroll from the Pro module navigation.
Tier: this module belongs to the Pro layer.
Public path: the module also includes a secure Staff Portal workflow where workers can use PIN or QR to authenticate, punch, break, and review attendance history.
Important positioning: the module already contains the framework, queue, bridge contracts, and country slots, but correct production use still depends on the necessary implementation and validation by the developer responsible for the target company and country.
Setup / Configuration
Recommended setup before a company relies on Payroll in production
Configure the company’s operational settings first
Set queue enablement, retry limits, kiosk auto logout, cooldown rules, default bridge profile, default country code, and kiosk labeling before live staff start punching.
Create employee profiles responsibly
Add full names, employee codes, roles, departments, rates, country assignment, bridge profile, weekly schedule template, and activation state so the staff base is clean from day one.
Define the legal and technical adaptation layer
Choose whether the company will use the Global structural profile or a country-specific bridge slot such as Greece / Ergani, United States / FLSA, United Kingdom / HMRC, or EU local bridge mode, then let the responsible developer connect the real local logic.
Validate planner, portal, kiosk, and queue behavior
Before go-live, test clock in / out, break handling, month lock, archive payload, queue retry behavior, and any state-facing bridge adapter so the company does not mistake a framework installation for a completed legal deployment.
How to Use It
Typical operational flow from employee creation to monthly finalization
Create the employee record
Add the worker’s profile, rates, bridge profile, country code, and default weekly template so the planner and portal have a clean starting point.
Build the planner
Create a planner, choose month or week focus, assign employees, and prepare the expected schedule before actual attendance begins to accumulate.
Use kiosk or staff portal for attendance
Employees authenticate with PIN or QR badge, then clock in, clock out, start breaks, end breaks, and review their attendance history without needing a heavy external system for everyday actions.
Review actual vs scheduled reality
Managers compare planned hours to actual records, inspect deviations, confirm exceptions, and make sure unscheduled punches or break patterns are reviewed before finalization.
Lock month and dispatch responsibly
Once the period is confirmed, lock the month, generate the immutable archive, and use the bridge / queue layer to send the final payload to the accountant, ERP connector, or local state-facing implementation.
Screens / Interface Guide
The interface areas that matter most in Payroll
Payroll Command Center
The opening screen surfaces employees, scheduled hours, actual hours, queue status, sync state, and integration health so payroll operations can be understood quickly.
Planner toolbar and grid
This is the schedule control area for planner choice, view mode, focus date, refresh, clear range, worker management, delete planner, and month lock actions.
Staff / Employee Directory
The employee list is where companies review staff availability, bridge assignments, and profile health before assuming the planner can run reliably.
Employee Profile modal
This is where role, department, employee code, rates, default weekly schedule, country code, bridge profile, active status, PIN, and QR-ready identity are shaped for each worker.
Operational Settings tab
This tab controls queue behavior, kiosk timing, default bridge profile, country defaults, and the main company-wide operational rules for the module.
Framework Scope tab
This area explains the deliberate separation between the global structural core and the country-specific legal or ERP adapters that must be completed locally.
Developer Docs tab
Developers use this area to understand bridge contracts, queue payloads, dispatch points, and country profile registration paths.
Public Staff Portal / Kiosk
The public-facing worker surface supports secure PIN / QR access, attendance actions, and monthly history checks in a controlled self-hosted flow.
Common Workflows
Real examples of how companies use Payroll
Daily attendance capture with QR or PIN
Employees punch in from kiosk or portal, start and end breaks, and keep a clean event history without depending on paper sign-in habits.
Planner-based monthly preparation
Managers schedule the month in advance, then compare the reality of attendance against the planned structure to spot deviations and exceptions early.
Audit-friendly review before accountant handoff
Before closing the month, the team reviews history, actual hours, breaks, unscheduled punches, and queue state so the final archive is cleaner and more trustworthy.
Local country adapter deployment
The responsible developer maps the framework to a company’s country-specific logic, ERP, or state interface using the provided bridge hooks and transmission contract.
Troubleshooting
Common problems, likely causes, and the first fix path
The company expects legal compliance automatically
Issue: the module is installed, but the company assumes country compliance is now complete by default.
Why it happens: the core ships with the framework, queue, archive logic, and bridge slots, but not with every local law, tax rule, or certified transmission adapter already finalized for every jurisdiction.
What to do: make sure a responsible local developer or agency configures and validates the country-specific logic, ERP mapping, and state-facing bridge before live payroll reliance.
Employees exist, but the planner still feels incomplete
Issue: the planner opens, but the scheduling flow is not fully usable.
Why it happens: worker setup, planner creation, or assignment management may still be incomplete.
What to do: confirm employees are active, create the planner explicitly, assign workers, and verify the selected planner and view mode are correct.
Clock in / out fails from portal or kiosk
Issue: the worker reaches the portal but cannot complete an attendance action.
Why it happens: PIN / QR authentication may be wrong, portal state may have expired, or the worker profile may be inactive or misconfigured.
What to do: recheck employee status, confirm QR token or PIN, validate the worker record, and test again with a fresh portal session.
Queue stays pending
Issue: sync payloads remain in queue and do not disappear.
Why it happens: the queue system is working, but the real dispatch adapter or local country bridge is not connected or is failing.
What to do: inspect retry limits, dispatch actions, and the responsible bridge implementation instead of blaming the planner or attendance layer first.
Lock Month should be disabled but still looks available
Issue: the company is unsure whether a month can safely be finalized.
Why it happens: the team may not yet have reviewed actual punches, breaks, exceptions, or queue state before trying to archive.
What to do: finish operational review first, then lock only when the company is ready to preserve the month as immutable output.
Country profile is selected, but state submission still does not exist
Issue: selecting Greece, US, GB, or EU is treated as if the bridge is already fully active.
Why it happens: those profiles are structural bridge slots, not magical replacements for the real local adapter.
What to do: let the responsible developer implement the country-specific payload mapping and dispatch layer using the provided hooks.
Attendance history looks correct, but payroll formulas are still missing
Issue: time records exist, but company-specific payroll output is still incomplete.
Why it happens: attendance capture and payroll calculation are related, but country or company formula logic still needs to be connected.
What to do: treat the framework as the structural core and complete local formulas, declarations, and legal mapping through the developer adaptation layer.
The public portal works, but QR scanner access is inconsistent
Issue: PIN works, but QR usage depends on the device environment.
Why it happens: browser camera permissions, hardware conditions, or scanner availability can differ per device.
What to do: keep PIN access available as fallback, verify camera permissions, and test the actual devices used in the company’s environment.
FAQ
Fast answers before opening support
Is Payroll a Pro module?
Yes. Payroll belongs to the Pro layer.
Does the module support different countries?
Yes, as a framework. It already includes structural country bridge slots and developer hook points, but each country still needs responsible local implementation.
Is the framework enough on its own for legal deployment?
No. The module provides the enterprise-ready core, but the final legal and technical adaptation still belongs to the responsible developer or agency for the target country and company.
What bridge slots already exist structurally?
Global, Greece / Ergani, United States / FLSA, United Kingdom / HMRC, and a generic EU bridge slot.
Can employees use QR or PIN?
Yes. The module supports both QR badge and PIN-based attendance access.
Does it include a public staff portal?
Yes. Staff can authenticate, punch, break, and review attendance history from the secure portal flow.
Can I assign rates per employee?
Yes. Hourly and overtime rates are part of the employee profile layer.
Can I prefill work patterns?
Yes. A default weekly schedule template exists for planning convenience.
Does the module track breaks and exceptions?
Yes. It supports break tracking, event history, deviations, and unscheduled punch review.
Can a company lock a month and export it?
Yes. Lock Month & Export is part of the immutable archive workflow.
Is there retry / backup continuity when dispatch fails?
Yes. The queue model is designed to retain and retry transmission payloads rather than simply losing them.
Can developers connect this to local payroll or state systems?
Yes. The module exposes country profile registration, queue item filtering, payload preparation, bridge contract filtering, and dispatch hook points for exactly that purpose.
The Noesia Matrix
⚙️ THE NOESIA MATRIX: KERNEL FABRIC ARCHITECTURE
The Noesia Matrix is the shared architecture language and module fabric behind Noesia Smart Waiter. This module is not just a static page; it sits inside an isolate-first modular system designed for shell-driven navigation, clean section ownership, extensible widget zones, and future-safe expansion.
The architecture direction is intentionally high-control: modular ownership, isolated assets, lazy-ready behavior, clean settings flow, predictable prefixes, maintainable service boundaries, and enterprise-safe discipline around structure, security, and extensibility. Noesia transcends the definition of a standard WordPress plugin, operating as a robust platform built upon enterprise-grade Service-Oriented Design.
Here is how the core engine is designed to minimize bloat, maximize stability, and keep the experience consistently fast and responsive:
Event-Driven Inversion of Control (IoC): The platform follows an IoC pattern via a decoupled Event Bus. The central core acts as a “Logic-Less Host” (Blind / DUMMY Kernel). It does not tightly bind itself to module internals; modules announce their own presence, capabilities, and state through controlled registration flows.
The Micro-Frontend Paradigm (MFE): The UI is not a giant monolithic block. Each application behaves as an independent Micro-Frontend with its own dynamic assets, specialized logic, and UI contracts.
Strict Asset Isolation & Lazy-Loading: Resource usage stays disciplined. A module’s CSS, JavaScript, and data components are loaded only when the user reaches or interacts with that specific application surface.
Decoupled Registry Pattern: The dynamic discovery layer allows applications to be added or removed quickly without rewriting core logic. If one application encounters an issue, the architecture is designed to contain that impact instead of cascading it across the platform.
Enterprise-Grade Security & Stability: The platform is reinforced with strict input sanitization, dynamic registry routing, and defensive safety gates across the stack. The data layer and the user interface remain deliberately separated for maintainability and risk control.
The Result: A scalable hospitality and clinical operating system engineered to manage mission-critical workflows securely — from intimate cafés to high-traffic venues and sensitive medical environments.
Support
Support, escalation, and what to send first
Check first
- Confirm the plugin version.
- Confirm the module name is Payroll.
- Check whether the issue is about attendance, planner, queue, lock, or local bridge adaptation.
- Review the troubleshooting section above first.
Collect before opening a ticket
- One clear screenshot of the issue.
- The exact visible error or wrong operational state.
- Short steps to reproduce.
- Whether the issue happens always or only in a specific company setup or country mapping.
Open support only after the fast checks above
When you open a ticket, include one clean screenshot, the exact visible error text or wrong result state, short reproduction steps, and whether the issue is structural, company-specific, or country-adaptation-specific. That reduces back-and-forth and speeds up resolution.
Open Support Explore Modules
Explore all modules of Noesia Smart Waiter
Enter the application layer: Explore the full Noesia Smart Waiter ecosystem and discover how each isolated module helps serve hospitality, operations, business workflows, and the wider mission to reimagine life through smarter software.
Scroll into the Matrix: The catalog below is the live gateway to the platform. Move through Free and Pro environments, open each documentation page, and step directly into the next application surface.
