One source of truth for who's who.
Reporting lines, entities, locations and roles on one record that payroll, attendance, leave and the agent all read from.
Capabilities
What the record holds
Contracts and documents
Signed contracts, visas, certifications and policy acknowledgements filed against the person, with expiry dates that prompt before they lapse.
Salary and grade history
Every change with its effective date and the approval behind it, so a payslip from eighteen months ago can still be explained.
Org chart and reporting lines
A live chart generated from the records themselves rather than a slide someone redraws each quarter.
Departments, entities and locations
Multi-entity structures with the right rules applied per location, which is what makes multi-country payroll possible at all.
How it fits together
One record, and what it removes
Most HR stacks are several products behind a shared sign-in. Integrations move data between them, but every hop is a place where a leaver, a mid-month joiner or a changed bank account can exist in one system and not the others.
- Documents that expire
- How pay history is versioned
- Structure
Employee records
Everyone, in one place
Teamio has one employee record and every module reads and writes to it directly, so reconciliation stops being a task because there is nothing to reconcile.
By the numbers
What it looks like in practice
Because the record is shared, a single instruction can cross module boundaries. Onboarding a hire creates the record, issues the contract, configures payroll and requests access, five modules from one sentence.
1
Record every module reads
Dated
Every salary and grade change
Multi
Entities, locations and rules
0
Reconciliation between systems
In practice
What the record holds, and who reads it
One record, written once, read by every module that needs it.
Filed against the person
Signed contracts, visas and certifications filed against the person with expiry dates that prompt before they lapse.
Dated and approved
Every change with its effective date and the approval behind it, so a payslip from eighteen months ago can still be explained.
Reporting lines
A live org chart generated from the records themselves rather than a slide someone redraws each quarter and which is wrong within a month.
Entities and locations
Multi-entity structures with statutory rules applied per location, which is what makes multi-country payroll possible at all.
Read by every module
Payroll, attendance, leave and Tio all read this record directly. Nothing is copied, so nothing can disagree.
Compared
Where the reconciliation goes
The same event, handled by separate systems and by one record.
FAQ
Common questions
What happens to a record when someone leaves?
It is retained with their employment history intact, because payroll, tax and legal obligations outlive the employment. Access to it follows your retention policy rather than being deleted on the last working day.
Can we import our existing records?
Yes. Records import from a spreadsheet, with the columns mapped to fields and validation run before anything is committed, so problems surface during import rather than in the first payroll run.
Who can see an employee's record?
Access follows the permission scope on each role, so a manager sees their own team while a payroll administrator sees the fields their job requires and not the rest.
See it running on your own data.
We will show the module working against records that look like yours, not a generic demo.
Explore more
Onboarding
A paperless flow the new hire completes before day one. Contract, documents, payroll details…
Employee Self Service
Payslips, leave balances, documents and requests, available to the employee directly instead of…
Workforce Analytics
Attendance trends, absence, overtime and cost per head tracked in real time. Ask for any cut…