HR.One
An HR integration layer that calculates attendance in one place, from the card swipe to the ERP, and records every correction with a trace. Today time and attendance; the goal, full scope HR management.
HR.One starts as an on premises time and attendance platform. It collects clock in and clock out events from the existing time and attendance software, calculates every day of every employee with rules HR writes on screen, and transfers the result to the ERP without loss and without duplicates. Our goal goes further: a full scope HR management and integration layer for both organisations and individual users.
Problem
Time and attendance terminals record the card swipe; the ERP and payroll want days and hours. In most organisations the work between the two is still done by hand. Events are exported, shift, overtime and leave rules are applied in spreadsheets or in the memory of a few people, and the result is keyed into the ERP by hand or with one off scripts.
Three things get lost along the way. Because corrections overwrite the raw record, nobody can later show what changed. When a rule changes, its effect on past months is unknown. When a transfer to the ERP stops halfway, finding which record went through and which went twice takes a line by line comparison.
The problem grows in organisations with several companies, sites and terminal brands. Every site has its own rules, every terminal software its own database, every ERP its own interface, and the knowledge that ties them together usually sits with a single person.
Approach
HR.One keeps data in three layers. The raw event never changes. An HR correction is written as a separate row with its reason and linked to the old record. Rules change the timesheet, not the raw swipe. Every day's result can therefore be explained by the event and the rule it came from.
Events are taken from the time and attendance software the terminals are connected to: pushed over REST, read from a database, from a CSV or JSONL file (local folder, FTP, SFTP, SMB) or from a SOAP service. There are ready presets for the ZKTeco BioTime and Meyer PDKS databases. A card is matched to a person first by explicit mapping, then by valid card number, then by employee number. An ambiguous event is never assigned to someone by guesswork; it lands in the unmatched events list.
Timesheet rules are written on screen. Each rule changes a single setting and can apply to a company, site, unit, collar group, calendar, terminal or a single employee. The specific overrides the general, a time bound rule sits on top of the permanent one, and two rules that conflict at the same level cannot be saved. The rule tester shows which rule won for one employee on one day and which ones were overridden. Shifts and night shifts, breaks, tolerances, overtime, weekly rest days, public holidays and leave coming from the ERP are all calculated inside this engine.
The result reaches the ERP at least once and is never written twice. Temporary errors are retried; permanent errors land in a visible queue. Days in a locked period are not recalculated and cannot be corrected; periods closed in the ERP are read into the platform as well. There are ready connectors for Uyumsoft Liox and IFS (versions 10 and Cloud); other ERPs connect over REST, SOAP, OData, SQL or file channels without writing code.
Technical Decisions
No code in settings
Every tolerance, duration and threshold is a typed setting whose default and explanation are written on screen. Users never type cron expressions, regular expressions or JSON: durations are entered as a number and a unit, schedules with a picker. The server accepts only these narrow formats as well. Attendance is run by HR, not by a developer.
Testing without touching the real ERP
The ERP connection is set up through a seven step wizard: what is being connected, connection details, connection test, code mapping, preview, a real send to the test environment and go live. Errors come back in plain language with their cause and fix. The platform includes a test ERP that runs only on the local address and offers selectable failure scenarios, so the whole flow can be exercised end to end without writing to a real ERP.
A single gate to go live
Every path that can write to the ERP passes through the same gate; a connector that has not passed it cannot write to the ERP. Approvals are bound to a fingerprint of the connection and mapping settings. If an address, key or mapping changes, the approval goes stale and the step reopens. Organisations that want it can require two different people to approve going live.
Records that cannot be altered
Writes from outside the application to the raw event, audit, period lock and ERP delivery tables are rejected at database level. The audit log is hash chained and the integrity of the chain can be verified. A rule change that affects past days first shows its effect and is recalculated only after approval.
Race conditions settled by design
What happens when a period lock and a recalculation run at the same time, when a person mapping changes while a calculation is running, or when two moves in the organisation tree collide was decided in the design and pinned down by tests. Single use approvals and session refresh keys are spent exactly once.
On premises, a single file
HR.One runs on the organisation's own server as a single executable, installed as a Windows service or a Linux systemd unit. The interface is embedded in that file and does not reach out to an external content network. Sign in can use LDAP/Active Directory, OIDC or SAML; two step verification is mandatory and sensitive actions require re authentication.
Outcome
HR.One is in development. The time and attendance core, the rule engine, ERP delivery, guided integration, authorisation and audit are in code and under test; the interface is in Turkish and English. The product is tested by more than nine hundred Go tests, and the authorisation test walks through every endpoint of the application one by one.
We are just as open about what does not exist yet. Device drivers that connect directly to terminals, mobile and QR clock in, employee self service (leave and overtime requests, approval flow), timesheet approval and installation packages are on the roadmap. HR.One does not calculate payroll; it writes attendance to the ERP and the payroll system as days and hours.
A live connection to a real ERP has not been made yet; the next step is the first pilot installation. The long term goal is a full scope HR layer where organisations and individual users manage their HR work in one place, talking to the ERP and other systems.
Pilot installation
If you would like to try HR.One in your own time and attendance and ERP environment, fill in the form. Let us talk about which terminal software and which ERP you use and how many companies and sites you work with, and clarify the scope together.
Talk about a pilot