Employee database software
One record per employee, hire to exit
An employee database that keeps work details, contract, pay, documents, and history in one profile, with every change saved as a dated record.
One employee's data sits in four places
The contract is in a personnel file, the salary in a spreadsheet, the manager on a slide. After a promotion, old values get typed over, and nobody knows what changed when.
One employee database for every legal entity and country
Skailer is built for companies of 200 to 1,500 employees with several legal entities and countries. Each employment record carries its legal entity, so one database covers the whole group without a separate account per entity. Pay stays in the contract currency, reports roll up into one, and access can stop at an entity's boundary.
Keep every employee's data on one profile
Work info, time off, goals, feedback, documents, and tasks sit on the tabs of one profile, next to the photo and main details. Cmd/Ctrl + F jumps to any field, and each viewer sees only what their role opens.
Keep pay and contract history in each employee record
Each change to legal entity, contract, employment type, work pattern, FTE, or pay is a new record with an effective date and its author. Set a raise for next month, and it applies that day. Earlier records stay.
Let status update from dates so no one has to ask
Skailer calculates lifecycle status from start dates, approved time off, and termination dates, in the time zone of the organization or the legal entity. Nobody types it in, so it can't drift from the facts on the record.
Capture data where it starts so HR doesn't retype it
Hire a candidate from Recruiting and the offer data carries over. Preboarding surveys write to the new hire's own fields, existing staff come in by CSV or XLSX import, and changes sync both ways with Slack and Google.
Add the fields your company tracks to the profile
Work permits, laptops, a mentor: custom fields hold one value per employee, and custom tables hold many records, with dated history when needed. New fields stay hidden until a role gets access.
HR database: what employee data you can store
Skailer's employee database stores everything HR keeps about a person: personal details, employment and contract terms, pay, time off, attendance, and documents. Anything else your company tracks, such as visa dates, skills, laptops, or certifications, you add as custom fields or tables. They work like built-in data: filter the People list by them, build reports on them, and export them. Each value is visible only to the roles you choose.
Time off and attendance have their own module: see leave management and attendance tracking.
| Data | What you can store | What Skailer adds |
|---|---|---|
| Personal details | Name, contact details, date of birth, emergency contacts | Employees update their own details, and changes that need sign-off go through approval |
| Position and structure | Job title, department, manager, location | Every change is a dated record with a reason, and the org chart is drawn from these records |
| Employment and contract | Legal entity, contract type, employment type, work pattern, FTE, probation | One profile across all your entities and countries |
| Pay | Base pay, bonuses, allowances, gross and net | Pay in the contract currency, reports in one currency, earlier values kept in the history |
| Time off | Leave balances and approved absences | Status changes to On leave on its own |
| Attendance | Clock-in and clock-out, planned vs actual timesheets | Hours sit on the same profile as leave and contract terms |
| Documents | Contracts, policies, signed documents | Signed copies are saved to the profile with a signing report |
| Hiring data | Offer details, preboarding answers | Filled in automatically from Recruiting and preboarding surveys |
| Anything else you track | Visa and work permit dates, skills, certifications, devices, dependents | 15 field types, custom tables with many records per person, your own columns in Position, Employment and Compensation, all usable in filters and reports |
Give the rest of Skailer one set of facts
Onboarding, time off, permissions, and offboarding read the same profile. The employee record holds the data. The org chart shows the structure built from it.
What is employee database software in Skailer?
Skailer's employee database software is the Core HR record that keeps one profile per employee: work details, employment terms, pay, documents, and tabs from other modules. Changes to position, contract, and pay are dated records, and lifecycle status is calculated from those dates. Custom fields add your own data. Skailer records what each person is paid and what they cost; your payroll provider calculates and pays it.
Keep employee data secure, in the EU, and GDPR compliant
Each role gets no access, view, or edit rights per field, and pay lines have their own permissions. Through employee self-service, people change only what their role allows; everything else goes through a request with approval. All HR data stays in the EU, and every change is logged.
What one record per employee saves, in the model
Source: Skailer ROI model, 500 employees
RECORD MANAGEMENT
DATA ERRORS
DATA RECONCILIATION
Employee database management: 3 ways compared
Employee record keeping usually happens in spreadsheets and shared drives, in a basic HR database, or in Skailer. Past values, status, and access end up in different places.
| Capability | Spreadsheets & drives | Basic HRIS database | Skailer |
|---|---|---|---|
| Where a person's data lives | Several files and folders | One profile, documents often elsewhere | One profile with pay, documents, module tabs |
| Past values | Typed over | Current value for most fields | Dated records for position, contract, pay |
| Why a change happened | In someone's email | Optional comment | Required reason on every position change |
| Employment status | A column someone updates | A field HR sets | Calculated from start, leave, and exit dates |
| Data at hire | Copied from the offer by hand | Often synced from an ATS | Offer data and preboarding answers |
| Who sees what | Anyone with the link | Access levels | View or edit per field, per role |
How the employee database system works
See how teams use Skailer
Employee database software: common questions
What is employee database software?
Employee database software, also called an HR database, keeps one record per employee: personal details, job, contract, pay, time off, and documents. It replaces paper personnel files, spreadsheets, and shared drives as the place HR checks first. In Skailer, the employee database is part of Core HR, so onboarding, time off, reviews, and reports all read the same record.
What data should an employee database include?
At minimum, personal details, job and contract terms, pay, time off, attendance, and documents. Companies with several legal entities also need the entity and currency on every employment record. In Skailer, you add anything else as custom fields or tables, such as visa dates, skills, or equipment, and use it in filters and reports.
How is Skailer's employee database different from a spreadsheet?
A spreadsheet holds the last value someone typed. In Skailer, each change to position, contract, or pay is a new record with an effective date, so earlier values stay in the history. Status is calculated from those dates, each field is visible only to the roles you choose, and every module reads the same profile.
Can one employee database cover several legal entities and countries?
Yes. Every employment record carries its legal entity, so one profile covers employees across all your entities and countries. Pay is stored in the contract currency and reported in one currency. Access can be limited to one entity, location, or reporting line. All entities are included in one plan, from €12 per employee per month.
Is employee data secure and GDPR compliant?
HR data is stored in the EU, in AWS Frankfurt. Each role gets no access, view, or edit rights per field, and pay has its own permissions. Every change shows who made it and when. Skailer has passed Google CASA Tier 2, and a SOC 2 Type II audit is in progress. A DPA is available for every customer. See security.
Can I import my existing employee data?
Yes. Import people, positions, pay, custom fields, and tables from CSV or XLSX. During implementation, the Skailer team migrates your employee records for you at no extra cost, usually over 6–8 working sessions. See implementation.
Can employees update their own details?
Yes. Through the employee self-service portal, people update their personal details and emergency contacts themselves. Changes that need sign-off, such as bank details or an address change, go through a request with approval in Flows, and approved values are written to the profile. Which fields people can edit is set per role.
Does the employee database keep salary history?
Yes. Base pay, bonuses, allowances, and employment terms are each stored as dated records. Add a new record with the date the change takes effect, and earlier ones stay in the history for the roles allowed to see it.
Is an employee record the same as an Employer of Record (EOR)?
No. An Employer of Record is a service that legally employs staff for you in a country where you have no entity. An employee record is the data your company keeps about its own people, and Skailer doesn't act as an employer.
See your employee records in Skailer
Bring one employee's data from wherever it lives today. We'll show it as one Skailer profile.
