Why cheap or generic payroll software fails security and outsourcing companies

Where generic payroll tools break for guard and manpower companies in Nepal: post rates, client batches, SSF on basic, Dashain allowance, approvals and billing.

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

Cheap or generic payroll software fails security and outsourcing companies not because it is cheap, but because it was built for a different kind of employer. It assumes one workplace, one monthly rate per person and one payroll run for the whole company. A guard company pays by post and shift, runs payroll client by client, moves guards in the middle of the month, calculates SSF on basic not gross, prorates the Dashain allowance, and has to make sure that what it pays each month matches what it bills each client.

When a tool cannot model those things, the work does not disappear. It moves back into spreadsheets, manual overrides and late-night reconciliation, and the tool becomes a printer for numbers worked out somewhere else. This guide shows where generic payroll breaks for a guard or manpower company in Nepal, what each failure looks like in real numbers, and a set of tests to run with your own data before you buy anything.

Why do security companies choose cheap or generic payroll tools?

The reasons are understandable:

  • The software looks simple. A clean screen with “employees”, “salary” and “payslip” seems to cover everything.
  • Setup is quick. You can enter 50 employees in an afternoon.
  • It works for the office. Accountants, HR and managers on fixed monthly salaries are handled well.
  • The monthly fee is low, and payroll feels like a solved problem.

The trouble starts later, usually in the second or third month, when guards change posts, a client asks why the invoice and the duty roster disagree, or a guard asks why his SSF deduction went up when his basic did not.

What makes security and outsourcing payroll different?

Office payroll Guard and manpower payroll
One workplace Dozens or hundreds of posts at many clients
One salary per person Rates that can vary by post, shift and client
Few mid-month changes Transfers, relief duty and replacements every month
Overtime is rare 12-hour shifts make overtime routine
One payroll run Separate figures needed per client, for billing and client queries
No link to sales Every guard paid should be a guard billed
A few staff ask questions Hundreds of guards check their payslips closely

Under the Labour Act 2074, s.61, a labour-supply company pays its placed workers “in the capacity of the employer”. So the security company carries all the statutory payroll duties for every guard, at every client, every month.

Where does generic payroll software break?

1. It stores one rate per employee, not per post or shift

Many contracts set rates at the post level: a night shift at a bank pays differently from a day shift at an office, and a supervisor post differs from a guard post. A generic tool holds one salary on the employee record. When the guard moves, someone edits the salary by hand, and the old rate is lost.

What to look for: rates attached to posts and shifts, so that a guard’s pay follows where and when he worked.

2. It runs one company-wide batch instead of client-wise batches

Clients ask questions about their own guards: who worked, how many days, at what rate. Outsourcing companies need per-client figures to bill each client. A single company-wide salary sheet forces you to filter and re-total by hand. Our guide to payroll for outsourcing companies with staff at many clients explains why per-client batches matter.

What to look for: salary batches you can run or filter by client and post from the same employee data.

3. It calculates SSF on gross, or as a fixed amount

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 in the base. Many generic tools default to a percentage of gross, or let you type a fixed amount once and forget it.

Take a guard on NPR 13,200 basic plus 9,480 dearness allowance (gross 22,680):

Calculation Correct (on basic 13,200) Wrong (on gross 22,680)
Employee SSF, 11% 1,452.00 2,494.80
Employer SSF, 20% 2,640.00 4,536.00
Total deposit, 31% 4,092.00 7,030.80

The arithmetic: 13,200 × 11% = 1,452.00 and 13,200 × 20% = 2,640.00. On gross, 22,680 × 11% = 2,494.80 and 22,680 × 20% = 4,536.00.

The wrong method over-deducts 2,494.80 − 1,452.00 = 1,042.80 from each guard every month. Across 100 guards on the same pay, that is 1,04,280.00 a month taken from guards that should not have been. A fixed-amount entry fails the other way: when a guard’s basic rises, the SSF does not.

4. It treats the Dashain allowance as a flat bonus

The Labour Act s.37 requires a festival allowance of one month’s basic remuneration a year, prorated for a worker with less than a year of service. A generic “bonus” field pays whatever you type. It does not know the basic, the service period or whether the person was already paid this year.

A guard on 13,200 basic with nine completed months should get 13,200 × 9 ÷ 12 = 9,900.00, not 13,200 and not a month’s gross of 22,680. Our Dashain allowance guide covers the proration rules.

What to look for: the allowance calculated from basic, prorated by service, and paid once per employee per period.

5. It cannot split a month when something changes

A guard gets a raise from the 16th, or moves from a day post to a night post halfway through the month. A generic tool pays the whole month at one rate.

Example: a guard on 12,170 basic is revised to 13,200 from day 16 of a 30-day month.

  • Days 1 to 15: 12,170 × 15 ÷ 30 = 6,085.00
  • Days 16 to 30: 13,200 × 15 ÷ 30 = 6,600.00
  • Basic for the month: 6,085.00 + 6,600.00 = 12,685.00
  • Employee SSF: 12,685.00 × 11% = 1,395.35

Paying the whole month at either rate is wrong by 515.00 of basic, one way or the other.

6. It has no idea of shifts, overtime limits or overtime rates

The Labour Act 2074 sets normal hours at 8 a day and 48 a week (s.28(1)), caps overtime at 4 hours a day and 24 hours a week (s.30(1)), and requires overtime pay of 1.5 times basic remuneration for regular hours (s.31(1)). A guard on a 12-hour shift works 4 hours of overtime every shift.

A generic tool usually has a single “overtime amount” box. You work out the hours and the rate somewhere else and type the result in. Nothing tells you when a guard has gone over 24 hours in a week. Our overtime calculation guide works through the methods with guard shift examples.

What to look for: overtime recorded against the employee and the shift, at a rate you set per shift, with the hours visible for checking against the legal limits.

7. Anyone can change anything, and nothing records it

In many low-cost systems, any user with access can edit a salary figure after it has been calculated, and there is no record of who did it. During a dispute with a guard, a client or an auditor, you cannot show what the figure was, who changed it and who approved the change.

What to look for: a recorded approval before payment, a version history of each batch, and a clear trail of changes after approval.

Every guard on the payroll for a client should appear in that client’s invoice, and every invoiced guard should be on the payroll. When payroll and billing live in different systems with different employee lists, mismatches go unnoticed: a relief guard who is paid but never billed, or a post that was billed for a guard who left.

If you must issue invoices from IRD-approved billing software, the payroll tool cannot fill that gap on its own.

What do these failures actually cost?

Exact costs depend on your company, so this guide does not put a savings figure on them. What can be stated is where each failure shows up:

Failure Who notices first What follows
SSF on gross Guards checking payslips Refunds, re-filing, loss of trust
SSF figures entered late or wrong The Fund Interest of 10% on the contribution amount (Contribution Based Social Security Act s.9(1))
Dashain allowance under- or over-paid Guards, or your auditor Corrections in a busy month
Mid-month changes ignored The guard, or the client Disputes and manual arrears
No overtime limits checked A labour inspection Breach of s.30(1)
No audit trail The owner, during a dispute No way to prove a figure
Paid but not billed Nobody, until month-end reconciliation Lost revenue

SSF must be deposited within 25 days after the end of each month (Contribution Based Social Security Act 2074 s.4(4), as amended in 2082). TDS on salary has the same 25-day deadline under the Income Tax Act s.90. A payroll process that needs a week of manual fixing makes those deadlines harder to meet.

What should you test before buying payroll software?

Do not judge a payroll tool on a demo with the vendor’s sample data. Ask for a trial and run your own cases. Each test below has an answer you can check by hand.

# Test Expected result
1 Guard on 13,200 basic, 9,480 dearness, SSF contributor Employee SSF 1,452.00; employer SSF 2,640.00
2 Same guard, not an SSF contributor No SSF; 1% first-band tax on taxable income applies (FY 2083/84)
3 Raise from 12,170 to 13,200 from day 16 of a 30-day month Basic 12,685.00; employee SSF 1,395.35
4 Guard moves from a day post to a night post mid-month Each part of the month paid at its own post’s rate
5 Dashain allowance, 13,200 basic, 9 months of service 9,900.00
6 Run the Dashain allowance twice for the same period The second run is blocked or flagged
7 26 twelve-hour shifts in a month 104 overtime hours visible; paid at your shift rate
8 Run one client’s batch on its own Only that client’s guards and totals
9 Change a figure after approval The change is recorded with who and when
10 Export the bank file and payslips Your bank accepts the file; payslips show every line

For test 2: in FY 2083/84 the first band is 1% up to NPR 10,00,000 of taxable income, and SSF contributors do not pay that 1%.

If a tool fails a test, ask the vendor how they would handle it. A clear answer with a workaround you can live with is better than a vague promise.

Is a more expensive tool automatically better?

No. Price tells you little about fit. A costly enterprise system built for factories or banks can fail the same tests as a cheap one. Judge every option by the tests above, by how easily your accountant can check its numbers, and by whether it can run your next month’s payroll without a spreadsheet on the side.

The real cost to compare is not the subscription. It is the subscription plus the hours your staff spend fixing, reconciling and explaining payroll every month, plus the risk of a late deposit or a dispute you cannot answer.

Checklist: before you commit to payroll software

  • SSF is calculated on basic by default, at 11% and 20%.
  • Non-SSF staff are handled separately for tax.
  • FY 2083/84 tax slabs are in place, and you can see which year’s rules a batch used.
  • Rates can be set per post and per shift.
  • Mid-month revisions and transfers are split by date.
  • Dashain allowance is calculated from basic, prorated, and paid once per period.
  • Overtime hours are recorded per shift and visible against the 4-hour daily and 24-hour weekly limits.
  • Batches can be run or filtered by client.
  • Each batch is approved before payment, and approved batches keep a version history.
  • Payslips and a bank file are produced from the same batch.
  • Payroll guard counts can be matched to client invoices.
  • You have run all ten tests above with your own data.

Where StrataMax fits

StrataMax was built for security and outsourcing companies in Nepal, so the cases above are its everyday work: salary batches with SSF on basic, TDS on the FY 2083/84 slabs, overtime at the rate you set for each shift, Dashain allowance, salary revisions with effective dates, approvals, version history, payslips and a connectIPS bank file. It also has IRD-approved VAT billing with CBMS reporting. See how StrataMax payroll works, or book a demo and bring the ten tests above with your own guards and posts.

Frequently asked questions

Why does generic payroll software fail security companies?

Because it assumes one employer, one workplace and one rate per person. Guard companies pay by post and shift, run payroll client by client, move guards mid-month and must reconcile payroll with what each client is billed. A tool that cannot model posts, clients and shift rates pushes that work back into spreadsheets.

Is cheap payroll software always a bad choice?

No. The price is not the problem; the fit is. A low-cost tool can be fine for head-office staff on fixed salaries. Test any tool, cheap or expensive, with your own guards, posts and rates before you commit, and judge it by whether it passes those tests.

What should I test before buying payroll software for a security company?

Run your own cases in a trial: a guard on 13,200 basic should show SSF of 1,452.00, not a figure based on gross; a guard who changed post mid-month; a salary revision with an effective date; a Dashain allowance for someone with nine months of service; overtime at your shift rate; a batch for one client only; and a change after approval that leaves a trace.

How do I know if my payroll software calculates SSF correctly?

Check one guard by hand. SSF is 31% of basic remuneration, 11% from the employee and 20% from the employer, with dearness and other allowances left out. For a guard on 13,200 basic and 9,480 dearness, the employee share is 1,452.00 and the employer share 2,640.00. If the software shows 2,494.80, it is using gross.

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 (FAOLEX mirror)
  4. Inland Revenue Department: tax rates for natural persons, income year 2083/84

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.