01
One employee record per person
Keep the employee, branch, role, leave, attendance, and payroll context together instead of rebuilding it across monthly sheets.
HR software · Nigeria
Move recurring HR work out of fragile spreadsheets and private inboxes. FASS scopes branch-aware employee records, payroll, leave, attendance, payslips, and manager or employee views around the organisation you actually run.
Abuja-based FASS · serving Nigerian organisations · written scope before we start
What this should improve
The right first release should make a specific customer journey, decision, handoff, or operational task easier to run. These are the capabilities this solution is intended to support.
01
Keep the employee, branch, role, leave, attendance, and payroll context together instead of rebuilding it across monthly sheets.
02
Employees can access their payslip and leave information while managers get the approvals and team views they need.
03
Separate locations when people, approvals, and payroll need it, while keeping an administrative view across the organisation.
How we work
Document branches, employee data, payroll inputs, leave rules, approvals, and the reports leaders need.
Prioritise the smallest useful HR and payroll module set for your organisation and current data quality.
Test the month-end journey as HR admin, manager, and employee so adoption problems surface early.
Use milestone delivery for integrations, statutory configuration, training, and additional HR modules.
Reference implementation
Explore branch-scoped HR admin, manager, and employee views with payroll, payslips, leave, attendance, and onboarding patterns.
Open the live demo →Public demos use fictional organisations and data. They are reference implementations for interface and workflow capability, not completed client engagements.
Before you start
Yes. FASS uses a branch-aware pattern that isolates employee, payroll, and leave data while giving HR administration an organisation-wide view.
The Vertical Starter pattern includes payroll runs, payslips, leave, attendance, loans, onboarding, and role views; production scope is configured to your rules and integrations.
No. The public HR demo uses fictional data to show the workflow. A production system is scoped and branded for your organisation separately.