Excel or software? When spreadsheets stop working for a security company

An honest look at running a security company's payroll, billing and records in Excel: where spreadsheets break, when they are still fine, and how to move off them.

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

Excel is fine for a security company’s payroll, billing and records while one careful person owns each sheet, the guard count is small, and payroll, attendance and invoices do not have to be reconciled across many files. It stops working when several people edit copies of the same sheet, when SSF and TDS formulas are rebuilt by hand every month, when each client has its own salary and billing sheet, and when nobody can say who changed a figure or why.

This article is an honest comparison. It does not claim software saves a particular amount, because that depends entirely on your company. It shows where spreadsheets typically break for a guard company in Nepal, where they are still the right tool, and how to move off them without breaking a month’s payroll.

Why do security companies run on Excel in the first place?

Because it works at the start, and because it is flexible. A company with 30 guards at four clients can keep one salary sheet, one attendance sheet and an invoice template. The owner or accountant knows every formula. A new client is a new tab.

Excel also has real strengths:

  • Everyone in the office already knows it.
  • It costs nothing extra.
  • It handles any odd arrangement: a guard paid a special rate for one month, a client billed per post rather than per guard, a one-off deduction.
  • The accountant can open it and check the numbers without learning anything new.

The problems arrive gradually, as guards, posts and clients grow and as more people touch the files.

Where does Excel break for a security company?

1. Version drift: which sheet is the real one?

The typical pattern: the accountant has “Salary Mangsir.xlsx”. HR adds new joiners to a copy. The operations manager updates attendance in another copy and emails it. Someone saves “Salary Mangsir FINAL.xlsx”, then “Salary Mangsir FINAL v2.xlsx”.

By payday there are three files with slightly different numbers. The one used for payment is whichever was open last. A guard who joined on the 12th is in one file and not the other. A rate change approved by the owner made it into the attendance copy but not the salary copy.

Shared drives and online spreadsheets reduce this, but they do not remove it. People still download, edit offline and re-upload, and an online sheet still lets anyone overwrite a formula.

2. SSF and TDS formula errors

Payroll formulas in Nepal are not complicated, but they are easy to get slightly wrong, and a slightly wrong formula is wrong for every guard, every month, without any warning.

SSF on the wrong base. SSF contributions are 31% of basic remuneration: 11% from the employee and 20% from the employer, according to the Social Security Fund. Dearness and other allowances are not part of the base.

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) Difference
Employee SSF 11% 1,452.00 2,494.80 1,042.80 over-deducted
Employer SSF 20% 2,640.00 4,536.00 1,896.00 over-calculated
Total 31% 4,092.00 7,030.80 2,938.80

The mistake is a single cell reference: the formula points at the gross column instead of the basic column. Copied down 300 rows, it is wrong for 300 guards. On a three-guard post on these figures, the guards together are over-deducted 3,128.40 a month. Nobody notices until a guard compares payslips with a friend at another company.

Last year’s tax rules left in a copied sheet. Tax slabs and rules change with each year’s Finance Act. For FY 2083/84, for example, a law-firm briefing on the Finance Act 2083 reports that the 1% first band is not applied to individuals who contribute to the contribution-based social security fund. A salary sheet copied forward from last year keeps last year’s slabs and last year’s logic unless someone remembers to update every formula, and every copy.

Opted-out and special cases. Staff who are not SSF contributors, staff with a mid-month raise, staff who moved posts mid-month: each needs a different formula or a manual override. In Excel, manual overrides are typed numbers sitting where a formula used to be. Next month, someone copies the sheet and the typed number comes with it.

3. Ranges, hard-typed numbers and hidden rows

Common spreadsheet faults that show no error:

  • SUM ranges that miss new rows. The total is SUM(H2:H120). A new guard is added at row 121. The salary total, the bank file and the SSF total are all short by one guard.
  • Hard-typed numbers over formulas. Someone typed 18,500 into a net pay cell to “fix” a guard’s pay. The formula is gone, and nobody can see that it was replaced.
  • Hidden rows and filtered views. A filter left on hides terminated guards, and also hides one active guard whose status was mistyped.
  • Broken links between files. The salary sheet pulls days worked from the attendance file. The attendance file was renamed. The link shows the last cached value.

4. One sheet per client, multiplied

Security companies bill by client and often pay by post. In Excel this usually means a salary sheet per client, an attendance sheet per client and an invoice per client. With 15 clients that is at least 45 files a month, and the same guard can appear in several of them if he covered a shift elsewhere.

Problems that follow:

  • A guard’s rate is changed in one client’s sheet but not in the master list.
  • A guard moved from Client A to Client B mid-month is paid in both sheets, or in neither.
  • The invoice for a client is retyped from the salary sheet, so the number of guards billed does not match the number paid.
  • Reports across all clients (total SSF, total TDS, total payroll) need someone to add up 15 sheets by hand.

5. No audit trail

In Excel you cannot easily answer: who changed this guard’s basic from 13,200 to 14,000, when, and who approved it? Version history in online sheets shows edits, but not approvals, and not in a way an auditor or owner can review quickly.

This matters when:

  • A guard disputes a deduction months later.
  • An auditor or tax officer asks how a figure was arrived at.
  • The owner wants to know why this month’s payroll is higher than last month’s.
  • A staff member leaves and nobody understands their formulas.

6. Billing and IRD requirements

Issuing tax invoices is a separate question from payroll. Businesses that are required to use IRD-approved billing software cannot meet that requirement with a spreadsheet template, however neat. Whether and when your company must use such software depends on IRD rules for your business, so confirm it with your accountant or IRD. Our guide to IRD-approved billing software in Nepal covers this in more detail.

When is Excel still fine?

Excel is a reasonable choice when most of the following are true:

Condition Why it matters
One person owns payroll and edits the master sheet No version drift; that person knows every formula
Guard numbers are small and stable Few joiners, leavers and transfers to track
Few clients, each with a simple arrangement Few sheets to reconcile
Rates rarely change mid-month Fewer manual overrides
Invoices are already issued from a separate approved system The spreadsheet is not your billing record
An accountant checks every month’s sheet against a checklist Formula errors are caught before payment

Even then, a few habits make Excel much safer:

  • Lock formula cells and protect the sheet, so only inputs can be typed over.
  • Keep one master employee list and look up rates from it, rather than typing rates into each client sheet.
  • Use structured tables (Insert, Table) so ranges grow automatically when rows are added.
  • Add check totals: total basic times 11% should equal total employee SSF; the number of guards paid should equal the number on the attendance sheet.
  • Save one file per month as read-only after payment and never edit it again.
  • Review the tax and SSF formulas at the start of every fiscal year, in Shrawan, against the new Finance Act.

What are the signs it is time to move off Excel?

Rather than a headcount, look for these signs:

  • Month end takes days of reconciling salary, attendance and invoice files.
  • More than one person edits payroll files, and copies are emailed around.
  • You have found the same guard with different rates in different files.
  • Client invoices are retyped from salary sheets.
  • You cannot say who changed a figure or who approved it.
  • A guard or client has found a payroll or billing error before you did, more than once.
  • Only one person understands the spreadsheet, and the business stops if that person is away.
  • You need to issue IRD-approved invoices and are not sure your current process qualifies.

If two or more apply, it is worth evaluating software. Our buyer’s checklist for security guard management software in Nepal covers what to look for.

What does software do differently, and what does it not fix?

Be clear about what changes and what does not.

Area Excel Payroll and billing software
Employee data Copied into each sheet One record per employee, used by payroll, billing and reports
SSF and TDS Formulas per sheet, edited by hand Rules set once, applied the same way to every employee
Mid-month changes Manual override cells Recorded as a revision with an effective date
Client sheets One file per client Batches filtered by client or post from the same data
Approvals Email or verbal Recorded approval before payment
Change history Limited or none Who changed what, and when
Invoices Template, often retyped Generated from the same client and post records

What software does not fix:

  • Bad input data. If a guard’s basic is entered wrongly, software will calculate the wrong SSF just as reliably as Excel. Garbage in, garbage out.
  • Wrong settings. Software applies whatever rules it is configured with. Someone still has to check that the SSF rates, tax year and allowances are set correctly.
  • Process gaps. If attendance is not recorded properly at the posts, no system will pay correctly.
  • The need for review. An accountant should still review each batch before approval.

How do you migrate from Excel to software?

A safe migration takes one or two payroll cycles. Rushing it is how companies end up paying a month twice or not at all.

Step 1: clean the employee master

Before importing anything, build one clean list of every active employee:

  • Full name, exactly as on citizenship.
  • Phone number.
  • PAN and SSF ID, where they exist. Leave them blank if missing. Do not fill in another number to make the column look complete.
  • Bank name and account number.
  • Basic, dearness and other allowances.
  • Current client and post.
  • Joining date.

Remove duplicates. Mark leavers as inactive rather than deleting them. This step usually takes longer than expected, and it is the most valuable part of the migration, because it fixes errors that have been sitting in your sheets for months.

Step 2: set up clients, posts and rates

Enter each client, each post at each client, and the shift rates for each post. Check that the number of posts and guards matches what you bill.

Step 3: import and check

Import the employee list, then spot-check: pick ten guards at random and compare every field with your Excel sheet.

Step 4: run in parallel for a month

Run the next month’s payroll in both Excel and the new system. Compare guard by guard:

Check Excel Software Action if different
Number of guards paid Find the missing or extra person
Total basic Check rates and joiners
Total employee SSF Check the base: basic or gross?
Total TDS Check slabs, SSF status, annualisation
Total net pay Trace guard by guard

Every difference has a cause. Often it is a mistake in the old spreadsheet that nobody had spotted. Decide which figure is right before payday.

Step 5: switch and archive

When the parallel run matches, or every difference is explained, pay from the new system. Save the old Excel files as read-only archives and stop editing them.

Checklist: Excel or software for your security company

  • List every file used for payroll, attendance and billing in one month.
  • Count how many people edit those files.
  • Check that SSF is calculated on basic, not gross, in every sheet.
  • Check that this year’s tax slabs and rules are in every sheet that calculates TDS.
  • Check every SUM range covers all rows, including recent joiners.
  • Look for typed numbers in cells that should hold formulas.
  • Confirm that invoice guard counts match payroll guard counts for each client.
  • Confirm with your accountant whether you must issue invoices from IRD-approved software.
  • Decide whether you can answer “who changed this figure and who approved it”.
  • If moving: clean the employee master, import, run one month in parallel, reconcile, then switch.

Where StrataMax fits

StrataMax was built to replace the separate payroll, attendance and billing spreadsheets that security and outsourcing companies in Nepal keep reconciling. Salary batches with SSF, TDS, overtime and approvals, and IRD-approved invoices, come from the same employee, client and post records, and employees can be imported from Excel. See how payroll works in StrataMax, or book a demo and bring one of your current salary sheets to compare.

Frequently asked questions

Can a security company run payroll in Excel?

Yes, and many do. Excel works while one careful person owns the sheet, the guard count is small, rates rarely change and there is one client sheet per month to reconcile. It becomes risky when several people edit copies, formulas are rebuilt each month, and payroll, attendance and billing live in separate files that must agree.

What are the most common Excel payroll errors?

The usual ones are SSF calculated on gross instead of basic, last year's tax slabs left in a copied sheet, SUM ranges that miss newly added rows, hard-typed numbers over formulas, and two versions of the same sheet with different figures. None of them shows an error message, so they are found late, often by a guard or a client.

When should a security company move from Excel to software?

Look at the signs rather than a headcount: month end takes days of reconciling, more than one person edits payroll, you cannot say who changed a figure, client invoices are retyped from salary sheets, or the same guard appears with different rates in different files. Any two of these together are a good reason to evaluate software.

How do you move payroll from Excel to software safely?

Clean the employee master first, import it, set up clients, posts and rates, then run the software in parallel with your Excel sheet for at least one month and reconcile every difference before you switch. Keep the old sheets as read-only archives.

Sources

  1. Social Security Fund: amount to be deposited in the fund (contribution rates)
  2. Pradhan & Associates: income tax rates for FY 2083/84 (2026/27)

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.