How to implement a security guard management system: from Excel data to go-live
A step-by-step rollout plan for a security guard management system: data preparation, Excel import, setup order, a parallel payroll month, training and go-live.
- StrataMax team
- 9 min read
- 4 sources
On this page
Figures in this article are checked as of 15 November 2026. Rules change with each budget and gazette notice, so confirm current rates with the IRD, SSF or your tax adviser before you rely on them.
To implement a security guard management system, work in this order: pick a start month and an owner, clean the employee data, set up company rules, clients, posts and shifts, import employees from Excel, load opening balances, run one full payroll month in parallel with your old sheets, train office staff and pilot the guard app, then go live with a checklist. Most failed rollouts skip the data clean-up or the parallel month.
This guide is for owners and managers who have already chosen a system. If you are still comparing options, use our scorecard and demo test plan first. If you are still deciding whether to leave Excel at all, read Excel or software? When spreadsheets stop working.
What does a guard management system replace?
It helps to name what is being retired, so nobody keeps the old copy running “just in case”.
| Today | After go-live |
|---|---|
| Personnel files and ID copies in folders | Employee profiles with documents |
| Deployment sheet per client | Clients, posts, shifts and dated assignments |
| Paper attendance registers and phone calls | Check-in and check-out on the guard app, or attendance entered by supervisors |
| Leave forms | Leave requests and balances |
| Salary sheets in Excel | Payroll batches with approval and history |
| Invoice templates | Invoices from the billing module |
| Issue registers for uniforms | Equipment issue and return records |
| Visit diaries and incident files | Patrol visit and incident records |
What should you decide before you start?
Who owns the project?
Name one person with authority to make decisions and chase people, usually the operations head or the senior accountant. Without an owner, setup questions sit unanswered for weeks.
Which month will you start in?
Choose the first live payroll month with care:
- Avoid the Dashain allowance month (usually Asoj or Kartik) as the parallel month. The festival allowance is one month’s basic, prorated for less than a year’s service, and it adds a second set of calculations to reconcile.
- Think about the fiscal year. FY 2083/84 started on 1 Shrawan 2083 (17 July 2026) with new TDS slabs. Starting in Shrawan means the system calculates the whole year’s TDS from the start, with no year-to-date figures to load.
- Avoid months with big staffing changes, such as a new client starting with many guards.
What is in scope for go-live?
Go live with payroll and the structure it needs (employees, clients, posts, shifts, assignments, leave). Add billing, patrol visits, incidents and equipment in a second phase if the team is small. Trying to switch everything in one month spreads attention too thin.
How do you prepare employee data?
This is the longest step. Export everything you have into one sheet per data type, then clean it.
| Field | Why it matters | Common problems |
|---|---|---|
| Full name | Matching across files | Spelling differs between salary and attendance sheets |
| Phone number | App login, matching | Old numbers, shared numbers |
| ID details | Identity | Missing for older staff |
| PAN | TDS records | Missing, or the citizenship number typed in its place |
| SSF ID | SSF deposits | Missing for recent joiners |
| Bank account | Salary payment | Closed accounts, wrong branch |
| Joining date | Leave, festival allowance, notice periods | Only the year known |
| Basic and dearness allowance | SSF base, festival allowance | Only gross recorded |
| Post and shift | Assignments | Out of date |
Three rules make the rest easier:
- Never fill a gap with a guess. If a PAN is missing, leave it blank and put the guard on a missing-data list. A guessed value looks real and nobody checks it again.
- Split gross into basic and dearness allowance. SSF is 31% of basic remuneration (11% employee, 20% employer), and the Dashain allowance is one month’s basic. A sheet that holds only gross cannot drive either.
- Give each guard one row. Duplicates from old postings are the most common cause of guards being paid twice.
How do you import from Excel?
- Download the system’s import template rather than adapting your own sheet. Column names and formats matter.
- Copy your cleaned data into the template, column by column, and check dates are in the format it asks for.
- Run the import’s validation step first if it has one. Fix every error in your sheet, not by hand in the system afterwards, so the sheet stays the clean source.
- Import a small batch first, for example one client’s guards, and check ten records field by field.
- Import the rest, then compare the guard count in the system with your payroll headcount.
If you need to import again later to update records, use the system’s own ID for each guard as the match key, not the name.
In what order should you set up the system?
Each step depends on the ones before it.
| Step | What to set up | Depends on |
|---|---|---|
| 1 | Company details, fiscal year, SSF rates, tax settings | Nothing |
| 2 | Users and roles | Step 1 |
| 3 | Clients | Step 1 |
| 4 | Posts, with address and site area for attendance | Step 3 |
| 5 | Shifts, with pay rate and overtime rate | Step 4 |
| 6 | Employees (the import) | Step 1 |
| 7 | Salary for each employee: basic and dearness allowance | Step 6 |
| 8 | Assignments of guards to posts and shifts, with start dates | Steps 5 and 7 |
| 9 | Opening balances: leave, advances, equipment issued | Step 6 |
| 10 | Billing: invoice numbering, client rates, e-billing set-up | Steps 3 and 4 |
Two settings deserve special attention:
- Overtime rates. The Labour Act 2074, section 31(1), sets overtime at 1.5 times basic remuneration, and caps overtime at 4 hours a day and 24 a week (section 30(1)). Set each shift’s overtime rate deliberately, and write down how you worked it out.
- E-billing. If your business must issue invoices electronically and report them to CBMS, you need IRD-approved software and a permit from your own tax office to use it. Start that conversation early; it is not a setting you can switch on in a day.
How do you run the first payroll month in parallel?
Run the same month in both the old sheets and the new system, from the same attendance, and compare every guard’s net pay, SSF and TDS. Set the tolerance for statutory amounts at zero.
Worked example: finding an SSF difference
A guard earns NPR 13,200 basic plus 9,480 dearness allowance, a gross of 22,680.
| Item | Old Excel sheet | New system | Difference |
|---|---|---|---|
| Employee SSF | 22,680 × 11% = 2,494.80 | 13,200 × 11% = 1,452.00 | 1,042.80 |
| Employer SSF | 22,680 × 20% = 4,536.00 | 13,200 × 20% = 2,640.00 | 1,896.00 |
The old sheet applied SSF to gross. The law’s base is basic remuneration, so the new system is right and the sheet has been over-deducting from this guard. Check: 2,494.80 − 1,452.00 = 1,042.80, and 4,536.00 − 2,640.00 = 1,896.00. Finding this is a good outcome, but decide with your accountant how to correct past months before you switch.
Classify every difference
| Cause | Example | Action |
|---|---|---|
| Error in the old sheet | SSF on gross, a SUM range that missed new rows | Fix forward; decide on past months |
| Data error | Wrong basic, wrong joining date | Correct the data in the system |
| Setup error | Wrong overtime rate on a shift | Correct the setup and re-run |
| Policy difference | An allowance the old sheet paid that nobody configured | Decide the policy, then configure it |
Do not switch until every difference has a named cause. If more than a handful remain open, run a second parallel month.
Keep the deadlines
The parallel month is still a real month. SSF must be deposited within 25 days after the month ends, and TDS deposited and the statement filed within 25 days too. Pay and file from the old process until you switch. Our monthly payroll compliance checklist lists the deadlines.
How do you train office staff?
Train by role, using your own data, not a demo account.
| Role | What they need to do confidently |
|---|---|
| HR | Add and update employees, documents and certificates; approve leave |
| Operations | Manage posts, shifts and assignments; review attendance |
| Accounts | Run, check and submit payroll; bank file; invoices and receipts |
| Approver (owner or manager) | Review and approve payroll; read the change history |
| Patrol officers and supervisors | Record patrol visits; review their posts |
Write a one-page month-end routine for accounts: which reports to check, in which order, and who approves. Pair each person with a backup, so month end does not depend on one login.
How do you roll out the guard app?
- Pilot with one client and its posts for two weeks.
- Install and log in with each guard in person, at the post or at the office. Many guards will not do it from a message.
- Test a check-in at the post while someone is there, to confirm the site area is set right.
- Fix site areas that are too tight (guards flagged while on post) or too loose.
- Explain what the app records and why: attendance at the post, not tracking off duty.
- Roll out client by client, keeping paper registers at a post only until its guards are checking in reliably.
Keep a fallback for posts with poor signal or guards without smartphones, such as supervisor-entered attendance.
What usually goes wrong?
- Starting the import before the data is clean, then fixing records one by one in the system.
- No parallel month, so the first error is found by a guard on payday.
- Two systems kept alive after go-live, with people editing both.
- Everyone given full access “for now”, and never restricted.
- Opening leave balances and advances forgotten, so the first final settlement is wrong.
- Overtime rates copied from the old sheet without checking how they were derived.
- Training once, at go-live, with nobody trained for staff who join later.
Go-live checklist
- Project owner named; start month chosen away from the Dashain allowance month.
- Employee data cleaned: one row per guard, basic and dearness split, missing fields listed, not guessed.
- Company settings, SSF rates and FY 2083/84 tax settings checked by the accountant.
- Users created with roles; nobody has more access than the job needs.
- Clients, posts with site areas, shifts with pay and overtime rates set up.
- Employees imported and headcount matched to payroll.
- Assignments, leave balances, advances and equipment issued loaded.
- One full payroll month run in parallel; every difference classified and resolved.
- Bank payment file tested with your bank.
- Office staff trained by role, with backups; month-end routine written.
- Guard app piloted at one client; site areas adjusted; fallback agreed.
- E-billing permit in place before invoicing from the system, if required.
- Old sheets archived as read-only on the go-live date.
Implementing StrataMax
StrataMax is set up with your team in the order above: clients, posts and shifts, a bulk employee import from Excel that leaves missing fields blank, then payroll with SSF, TDS, overtime, Dashain allowance, approvals and version history. Billing is IRD-approved with CBMS reporting, and the Android app covers assignments, check-in and check-out against the site area, leave requests and patrol visits. Book a demo to plan a rollout with your own data.
Frequently asked questions
How long does it take to implement a security guard management system?
Plan for at least two payroll cycles: one to prepare and import data and set up clients, posts and pay rules, and one full month run in parallel with your existing payroll. The data clean-up usually takes longest, because it exposes errors that have sat in the spreadsheets for years.
What data do you need before importing guards into new software?
For each guard: full name, phone, ID details, PAN, SSF ID, bank account, joining date, current basic and dearness allowance, current post and shift, leave balances, outstanding advances and equipment issued. Leave a field blank and list it as missing rather than filling it with a guess.
Why run payroll in parallel when switching systems?
Running one month in both systems and reconciling every difference proves the new setup is right before guards are paid from it. Differences usually come from old spreadsheet formula errors, data errors or setup mistakes, and each needs a named cause before you switch.
In what order should you set up a guard management system?
Company settings and tax and SSF rules first, then users and roles, clients, posts, shifts and rates, then employees and their salaries, then assignments and opening balances, and finally billing. Each step depends on the one before it.