What problem does it solve?
Payroll requires its own accuracy, privacy and statutory controls rather than being embedded inside Dispatch or HR.
Part of HalNora One · Independent product
Development QAPayroll & workforce pay
A standalone payroll product being built cautiously around Canadian requirements.
HalNora Payroll is being developed separately from Dispatch driver settlement and Accounting. Current workflows use synthetic development data while statutory accuracy, payments, filings and production security continue validation.
Designed around
- People & payroll tenancy
- Pay groups & schedules
- Time input/import
- Draft pay-run workflow
- Review & approval safety
- Privacy controls
- Reporting foundations
- Future Accounting handoff
Current status
Payroll v16.2 reports 160/160 non-hook tests passing with TypeScript clean. Staged MFA protections advanced, but database-backed authenticated E2E, mandatory MFA and Canadian statutory validation remain open; live payroll/banking/CRA/Accounting flows are disabled.
Live development statusDevelopment QA
Current focusDatabase-backed authenticated E2E, mandatory MFA, PostgreSQL identity safeguards, statutory calculation validation and later banking/CRA/Accounting integration.
Last updatedOctober 12, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
Problem, capability, connection and current stage.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
What is it being built to do?
People/pay-period inputs, time and scheduling context, guided draft pay-run workflows, privacy controls and future statutory/payment integrations.
How does it connect?
HR can provide approved employee/workforce context; Payroll owns pay calculation and future remittance/payment workflows; Accounting receives approved posting events.
Where is it today?
Development QA. v16.2 reports 160/160 non-hook tests passing; mandatory MFA, database-backed E2E and statutory validation remain open.
Current direction
What this product is being built to do.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Tenant & people setup
Maintain payroll-specific business/people context without conflating employees with Dispatch drivers or merchant users.
Schedules & pay groups
Build controlled scheduling/pay-group foundations for repeatable payroll workflows.
Time input
Support synthetic time import and review flows as a precursor to approved pay calculations.
Draft pay runs
Create and review development-stage pay-run structures without triggering real payment.
Review separation
Use explicit reviewer/safety controls where approvals or evidence are involved.
Privacy hardening
Protect payroll GET surfaces and keep sensitive workforce data permission-scoped.
Reporting foundations
Prepare audit/review outputs without claiming statutory filing readiness.
Integration contract
Plan Payroll→Accounting posting as an explicit future contract rather than direct ledger access.
Product boundary
Payroll is separate from driver settlement and Accounting.
Driver settlement remains an operational Dispatch function. Payroll owns employee pay workflows. Accounting will only receive approved payroll financial events after that integration is formally validated.
HALNORA ONE ARCHITECTURE
Connected, not coupled.
Cross-product integrations use explicit contracts and preserve authoritative ownership rather than letting adjacent products write directly into this product’s core records.
How the HalNora platform works →Release discipline
What still has to be proven.
Development checkpoints are useful evidence, but they are not a substitute for authenticated production acceptance.