Choosing security guard management software in Nepal: a buyer's checklist

What to check before buying security guard management software in Nepal: payroll rules, IRD billing, posts, equipment, patrols, mobile app and support.

  • StrataMax team
  • 10 min read
  • 3 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.

When you choose security guard management software in Nepal, check eight things: payroll that follows Nepal’s rules (SSF on basic, current-year TDS, overtime, Dashain allowance), billing from IRD-approved software if you are required to use it, guards organised by client and post, equipment issue and return, patrol and incident records, a mobile app for field staff, role-based control over who sees and changes data, and a proper import from Excel with local support behind it.

The rest of this checklist explains what to look for under each heading, what to ask in a demo, and how to compare vendors fairly. It is written for owners, operations heads and accountants of security guard companies, and it applies just as well to outsourcing and manpower companies that place staff at many clients.

Why is generic HR or accounting software not enough?

A security company has a shape most HR and accounting packages were not designed for:

  • Hundreds of guards are paid monthly, but they work at posts belonging to clients, on shifts with different rates.
  • Guards move between posts and clients during the month.
  • Each client is billed separately, often per post or per guard, and pays after withholding TDS.
  • Uniforms, torches, radios and boots are issued to each guard and must come back.
  • Supervisors visit posts, and incidents at posts must be recorded and reported to the client.
  • Most of the workforce is in the field, not at a desk.

Software that handles payroll but not posts, or billing but not guards, leaves you reconciling between systems, which is the problem you were trying to escape.

Does the payroll follow Nepal’s rules?

Payroll is where mistakes cost the most trust. Check these specifics, not a general “Nepal payroll supported”.

SSF

According to the Social Security Fund, contributions are 31% of basic remuneration: 11% from the employee and 20% from the employer. Dearness and other allowances are not part of the base. Contributions must be deposited within 25 days after the end of each month under the Contribution Based Social Security Act 2074, section 4(4), as amended in 2082.

In the demo, check:

  • SSF is calculated on basic, not gross, by default.
  • Employees who are not SSF contributors can be handled correctly.
  • The software produces the totals you need for the monthly deposit.

TDS

  • Tax slabs are updated for the current fiscal year (FY 2083/84 now) and you can see which year’s rules a batch used.
  • The calculation treats SSF contributors and non-contributors differently where the law does.
  • Annual income is projected sensibly for guards who join or leave mid-year.

Overtime, allowances and mid-month changes

  • Overtime is recorded against the employee and added to the batch at a rate you control per shift. The Labour Act 2074, section 31, sets the overtime rule; ask how the vendor applies it and check it with your own adviser.
  • Dashain (festival) allowance can be run once per employee and period, prorated for staff with less than a year of service.
  • A raise or post change in the middle of a month is split correctly between the old and new rates.

Control and outputs

  • Each batch is approved before payment, and approvals are recorded.
  • Changes after approval leave a trail: who changed what, when, and why.
  • Payslips for every employee, and a bank payment file your bank accepts.
  • Salary periods in Bikram Sambat months, because that is how your guards and accountant think about pay.

Is the billing IRD-approved, and does it fit how you bill?

If your business must issue invoices from IRD-approved billing software, a spreadsheet template or a generic invoicing app does not meet the requirement. Confirm with your accountant whether it applies to you, then check:

What to check Why it matters
The vendor can show the IRD approval for its billing software Approval belongs to specific software, not to a vendor’s other products
Invoices are reported to IRD’s central billing system, and you can see each invoice’s sync status Unreported invoices are a compliance gap you may not notice
Invoices carry your PAN, the buyer’s PAN, VAT and amount in words Check the layout against IRD’s tax invoice requirements with your accountant
Credit notes and cancellations are handled against the original bill Mistakes are corrected without deleting history
Receipts record TDS withheld by the client Receivables stay correct when clients pay net of TDS
Sales register, sales return register and VAT summary are available Your accountant needs these every month
Invoices come from the same client and post records as payroll No retyping of guard counts from salary sheets

For more on the requirement itself, read our guide to IRD-approved billing software in Nepal.

Are guards organised by client and post?

This is the backbone of the system. Without it, payroll and billing cannot share data.

  • Each client has one or more sites or posts.
  • Each post has its shifts and rates.
  • Each guard is assigned to a post, and the assignment has dates, so transfers are on record.
  • Payroll can be run per client or per post, and billing reads from the same assignments.
  • An employee profile holds personal details, PAN, SSF ID, bank details, documents (citizenship, guard ID, contracts) and status (active, inactive, suspended, terminated).

Ask the vendor to show a guard who moved from one client’s post to another’s on the 15th of the month, and how that guard appears in payroll and in both clients’ invoices.

Does it track uniforms, equipment and certificates?

Guards hold company property. Without records, it walks away when they leave.

  • Issue and return per employee, with the date.
  • Whether a return was full, partial or none, and the condition on return.
  • Stock levels and an audit log per item.
  • Training and compliance certificates (basic guard training, fire safety, first aid) with expiry dates, so you can see whose training needs renewing.

Ask: when a guard is terminated, can the office see in one place what he still holds?

How does it handle patrols and incidents?

Supervision records are what you show clients when they ask what they are paying for.

Patrol visits. A patrol officer visits a post, checks the guard on duty, and records findings, a conclusion and photos. Check that visits can be scheduled in advance, that each visit has a status (scheduled, in progress, completed, missed), and that missed visits stay on record. Our guide to patrol visits across many posts explains why that matters.

Incidents. Check for a fixed list of incident types, a severity scale, witnesses, photos and other media, a status (open, investigating, closed), and dated follow-ups until the incident is closed. Ask whether incidents are linked to the client and post, so a monthly client summary is easy to produce.

Also ask exactly where each record is created: in the web app by the office, in the mobile app by field staff, or both. Vendors differ, and it affects your process.

What can field staff do in the mobile app?

Most of your people never sit at a computer. The mobile app is how they connect to the system. Ask for a list of what it actually does, then check each item on a phone in the demo:

  • Duty assignments: where and on which shift each person is posted.
  • Check-in and check-out, and how location is used.
  • Leave requests and approval status.
  • Patrol visits for patrol officers.
  • Notifications from the office.
  • Which phones it runs on. Many guards use low-cost Android phones, so check the platforms supported and try it on a modest device.

Ask what data the app collects (for example location), when, and what the privacy policy says. Guards and unions will ask.

Who can see and change your data?

Payroll and personal data need control.

  • Roles and permissions. Can you decide which roles can view, create, edit, delete or approve in each module? An HR assistant may need to edit profiles but not approve payroll.
  • Separation between companies. Your data should be in its own workspace, not visible to other customers.
  • Audit trail. Who changed a salary, an invoice or a profile, and when.
  • Export. Can you export your data if you leave? Ask in what format.
  • Login security. Password rules, session handling, and what happens to a departed employee’s access.

Can it import your existing Excel data?

You have years of data in spreadsheets. Ask:

  • Can employees be imported from Excel in bulk, and updated in bulk later?
  • What happens to rows with missing data, such as a guard with no SSF ID? A good import leaves missing fields blank and flags them; it does not make up a value.
  • Will the vendor help set up clients, posts and pay rules with your team?
  • Can you run one month in parallel with your Excel payroll to compare?

Our article on moving from Excel to software covers the migration steps in detail.

What support will you actually get?

Month end is when you need help, and it is the same week for every customer.

  • Where is the support team, and in which languages do they work?
  • How do you reach them: phone, email, chat?
  • Who updates the software when tax slabs, SSF rules or minimum wage change, and how quickly?
  • Is setup and training included, and who does it?
  • How are updates delivered, and do you get notice before changes?

What should you ask in a demo?

Do not watch a generic tour. Send the vendor three or four of your real scenarios in advance and ask them to run them live.

Scenario What a good answer looks like
A guard on NPR 13,200 basic plus 9,480 dearness: show his SSF Employee SSF of 1,452.00 and employer SSF of 2,640.00, calculated on basic only
A guard who moved posts on the 15th Pay split between the two posts; both clients billed for the right days
A staff member who is not an SSF contributor TDS and deductions handled differently, without a manual override
Dashain allowance for a guard with 7 months’ service Prorated allowance, paid once, not repeated next month
An invoice with a mistake A credit note against the original, with the original kept
A client that paid net of TDS Receipt recorded with TDS withheld; receivable closed correctly
A missed patrol visit Shown as missed, with the reason, not deleted
An approved batch that needs a correction Unapproval with a reason, and a record of what changed
A new HR assistant joins A role that can edit profiles but cannot approve payroll

For the first scenario, the arithmetic is 11% × 13,200 = 1,452.00 and 20% × 13,200 = 2,640.00. If the demo shows 2,494.80 for the employee, the software is using gross (22,680) as the base.

How should you compare vendors fairly?

Use the same scoring sheet for each vendor and score only what you saw working, not what was promised.

Area Must have Seen in demo? Notes
SSF on basic, TDS for current FY Yes
Overtime, Dashain, mid-month revisions Yes
Payroll approval and change history Yes
IRD-approved billing, reported to IRD If required
Credit notes, receipts with TDS, registers If billing in scope
Clients, posts, shifts, assignments Yes
Equipment issue and return Usually
Certificates with expiry Usually
Patrol visits and incidents Usually
Mobile app for field staff Usually
Roles and permissions Yes
Excel import and setup help Yes
Local support at month end Yes

Ask for references from companies of a similar size and type, and call them. Ask what went wrong in their first three months, not only what went right.

Buyer’s checklist: security guard management software in Nepal

  • SSF calculated on basic remuneration, with the 11% and 20% split, and non-contributors handled.
  • TDS on the current fiscal year’s slabs, with the year visible on each batch.
  • Overtime, Dashain allowance and mid-month salary revisions shown working.
  • Payroll batches approved before payment, with change history.
  • Payslips and a bank payment file your bank accepts.
  • Bikram Sambat salary periods and dates.
  • IRD approval shown for the billing software, if you must use it; invoices reported to IRD.
  • Credit notes, receipts with TDS withheld, and sales registers.
  • Clients, posts, shifts and dated assignments as the core structure.
  • Employee profiles with documents, PAN, SSF ID and status.
  • Equipment issue and return with condition; certificates with expiry dates.
  • Patrol visits with statuses including missed; incidents with severity and follow-ups.
  • A mobile app tested on a modest Android phone, with a clear privacy policy.
  • Roles and permissions you control; separate workspace; data export.
  • Bulk Excel import that leaves missing data blank; help with setup.
  • A parallel payroll month planned before switching.
  • Support contacts, languages and month-end availability confirmed.
  • References from similar companies called.

Where StrataMax fits

StrataMax is one option to put through this checklist. It is built in Kathmandu for security guard and outsourcing companies, and covers payroll with SSF, TDS, overtime, Dashain allowance and approvals, IRD-approved billing, guard profiles, equipment, patrols, incidents and an Android app for field staff. See how it works for security companies, or book a demo and bring your own scenarios from the table above.

Frequently asked questions

What should security guard management software in Nepal do?

At minimum it should run payroll under Nepal's rules (SSF on basic, TDS on the current year's slabs, overtime and Dashain allowance), bill clients from IRD-approved software where you are required to, organise guards by client and post, and track equipment, patrols and incidents. It should also control who can see and change data, import your existing Excel records, and come with local support.

Does security guard software need to be IRD-approved?

The billing part does if your business is required to issue invoices from IRD-approved billing software. Ask the vendor to show the approval and how invoices are reported to IRD, and confirm with your accountant whether the requirement applies to you.

What questions should I ask in a software demo?

Ask the vendor to run your own scenarios: a guard who changed post mid-month, an employee who is not an SSF contributor, a Dashain allowance run, a client invoice with a credit note, and a missed patrol visit. Also ask who can approve payroll, how changes are tracked, how your Excel data is imported, and what support looks like at month end.

How long does it take to switch from Excel to guard management software?

Plan for at least one full payroll cycle run in parallel with your existing sheets, after the employee data is cleaned and imported. The cleaning step usually takes the longest, because it surfaces errors that have been sitting in the spreadsheets.

Sources

  1. Social Security Fund: amount to be deposited in the fund (contribution rates)
  2. Contribution Based Social Security Act 2074, section 4: contribution to be deposited
  3. Labour Act 2074, Nepal Law Commission English translation

Next step

Let StrataMax do this every month

Payroll with SSF and TDS, IRD-approved billing and every guard and post on one record. Book a 30-minute walkthrough.