Every HR process – payroll, attendance, leave, performance – ultimately depends on one thing being right first: an accurate, complete, current record of who actually works for the business, in what role, in which department, and since when. Get that foundation wrong and every process built on top of it inherits the same inaccuracy.
AccDoo’s Employee Management module is that foundation – the shared employee record every other HRMS module reads from and writes to. This page covers what it includes; the modules that draw on it most heavily, like payroll and performance management, have their own dedicated pages covering that specific depth.
Why This Matters for Sri Lankan Businesses
Sri Lankan businesses growing past a size where the owner or a single HR person personally knows every employee’s details by memory often discover their employee records are scattered – some in a spreadsheet, some in physical personnel files, some only in whoever’s memory happens to still be accurate. A departmental restructure or a designation change gets updated inconsistently across these scattered sources, if at all.
There’s also a real compliance dimension: accurate employee records – start dates, designations, department history – matter directly for EPF/ETF contribution history, for demonstrating consistent treatment across similar roles, and for having a defensible record if an employment dispute or audit ever requires one.
A Day in the Life
A logistics company in Colombo has grown from fifteen to sixty employees over three years. Employee records live partly in a spreadsheet HR maintains, partly in physical files for signed documents, and partly in departmental managers’ own informal notes about who reports to whom. When a departmental restructure happened last year, three different records ended up with three different versions of which team a handful of employees actually belonged to.
With AccDoo’s Employee Management module, that same business maintains one record per employee – personal details, department, designation, reporting line, and every document – that every other module reads from directly. A departmental restructure is one update, reflected instantly and consistently everywhere that employee’s department matters, from payroll cost centers to performance review routing.
What’s Included
- Employee records – personal details, contact information, and employment history in one place per employee
- Departments & designations – organizational structure maintained centrally, with employees assigned consistently across every module
- Document management – contracts, identification, certifications and other employee documents stored securely against each employee’s record
- Transfers & promotions – organizational changes logged as part of the same employee history, not tracked separately from the rest of their record
- Acknowledgements – company policies distributed and acknowledgement tracked per employee, with a clear record of who has and hasn’t confirmed receipt
Setting This Up
Setting up Employee Management typically starts with migrating current staff records from whatever mix of spreadsheets and physical files a business is currently using – a one-time data entry effort that, once complete, means every employee’s information lives in exactly one place going forward rather than several inconsistent ones.
Department and designation structures are configured to match how the business actually organizes itself, which can be as simple or as detailed as needed – a small business might need only a handful of departments, while a larger, multi-branch operation might configure a more detailed structure reflecting distinct teams at each location.
What to Watch For
A common mistake during migration is copying over inconsistent historical data without cleaning it up first – if three different records disagreed about an employee’s exact start date or designation before the migration, importing all three without resolving the discrepancy just moves the same inconsistency into the new system rather than fixing it.
Another is treating the initial setup as a one-time project rather than an ongoing discipline – employee records need updating as transfers, promotions and departmental changes actually happen, not batched up and entered periodically, since other modules depend on this data being current, not eventually current. A payroll run calculated against a department assignment that changed two weeks ago but was never updated will quietly misallocate that employee’s cost to the wrong department in every subsequent report until someone notices and corrects it.
Real Numbers, Not Guesses
A business with sixty employees maintaining records across scattered spreadsheets and physical files commonly spends four to six hours a month on record-keeping tasks – updating a designation change here, filing a document there, answering an internal question about who reports to whom that requires checking multiple sources to answer confidently.
With one centralized employee record, that same maintenance work typically drops to under two hours a month, since updates happen once rather than needing propagation across several disconnected sources, and questions about organizational structure can be answered directly rather than requiring a cross-check across scattered records. Across a full year, that difference adds up to roughly two to three full working days reclaimed – not from any single dramatic change, but from removing the small, repeated friction of maintaining the same information in more than one place.
Making the Switch
Migrating employee records onto AccDoo is usually the very first step in adopting HRMS at all, since every other module – payroll, attendance, leave – depends on this data existing first. A reasonable approach is a phased migration: enter core details (name, role, department, start date) for every employee first, then progressively add historical documents and detailed history as time allows, rather than waiting for every historical document to be scanned before starting to use the system at all.
For businesses with unionized staff or specific collective agreement terms attached to certain roles, migrating those terms accurately as part of the employee record ensures that context isn’t lost – a detail worth confirming explicitly during setup rather than assuming it will be remembered informally going forward.
Questions Sri Lankan Buyers Actually Ask
Can I store employee documents like contracts and certifications in AccDoo? Yes – documents can be stored securely against each employee’s record, rather than kept in separate physical or digital files disconnected from their other information.
Does updating an employee’s department automatically reflect in payroll and reporting? Yes – because every module reads from the same employee record, a department or designation change updates consistently everywhere that information is used.
Can I track an employee’s full history of transfers and promotions? Yes – transfers and promotions are logged as part of the same employee record, building a complete history rather than existing as disconnected one-off notes.
How do I know if employees have acknowledged a new company policy? Policy acknowledgement is tracked per employee, giving a clear, exportable record of who has and hasn’t confirmed receipt of a specific policy.
Can I migrate employee records from a spreadsheet I’m already using? Yes – existing employee data can typically be imported as a starting point, rather than manually re-entered one employee at a time.
Can I search for an employee by department, role or any other field? Yes – employee records are searchable and filterable across every field, making it fast to find a specific employee or a group matching certain criteria.
Does the system track probation periods and confirmation dates? Yes – probation status and confirmation dates are part of the standard employee record, visible alongside other employment details.
Can I generate an org chart directly from the employee data? Yes – since reporting lines are part of each employee’s record, an organizational chart can be generated directly from that data rather than maintained as a separate document.
How This Fits the Full AccDoo Platform
Employee Management is the foundation every other HRMS module builds on – payroll calculates EPF, ETF and APIT against these records, attendance and leave track against this same employee list, and performance management logs history against these same profiles. Getting this foundation accurate and centralized is what makes every other HRMS module actually reliable, since a module is only ever as accurate as the employee data it’s drawing from. This same foundation extends into AccDoo ERP too: an employee record here is the same one used if that person is also assigned to a project in Project Management, or flagged as an approver in a purchasing workflow, meaning the connection between HRMS and ERP isn’t a separate integration – it’s the same underlying record, referenced consistently everywhere a person’s identity matters across the whole platform.
Sri Lankan Market Context
Sri Lankan businesses crossing from a small, personally-managed team into a genuine mid-sized organization – typically somewhere past twenty or thirty employees – commonly discover that informal, memory-based employee tracking has quietly become a real liability, not because anyone was careless, but because the informal approach that worked at ten employees simply doesn’t scale to sixty.
For multi-branch Sri Lankan businesses specifically, having one centralized employee record accessible from head office, rather than separate branch-level records that need periodic manual consolidation, is what makes company-wide HR reporting and planning genuinely possible rather than a manual assembly exercise every time it’s needed. A head office team reviewing headcount across ten branches wants one consistent source of truth, not ten branch managers’ individually maintained spreadsheets that each define “current staff” slightly differently.
Who This Is Built For
Any Sri Lankan business with employee records currently scattered across spreadsheets, physical files and informal notes, particularly those that have grown past the point where one person can reliably remember every employee’s current role and history.
The Bigger Picture
Consider the specific moment this gap becomes visible: an audit, a labour tribunal inquiry, or simply a new HR hire trying to understand the organization for the first time, all depend on being able to answer “who works here, in what role, since when” quickly and confidently. A business that can answer that in seconds from one system is in a fundamentally different position than one that needs to cross-reference three inconsistent sources and hope they eventually agree.
There’s also a succession and continuity angle worth naming: institutional knowledge about who’s who and who reports to whom often lives entirely in one long-serving HR person’s head in smaller Sri Lankan businesses. When that person is unavailable or eventually leaves, a centralized, accurate employee record is what prevents that departure from becoming an organizational memory crisis on top of a staffing one. A new HR hire inheriting a well-maintained centralized record can become productive within days; one inheriting scattered, undocumented knowledge often spends their first several weeks simply trying to reconstruct a picture that should have been available from day one.
Getting Started
Explore Payroll Software or Onboarding Software above to see how they build directly on this foundation, or book a demo to see one connected employee record used across the full employee lifecycle.