From Muster Roll to Invoice: Closing the Month in Days, Not Weeks
In most agencies the month doesn't close — it just stops, somewhere in the middle of a reconciliation. Here is the five-stage close we designed for Hyper Ops.
Meenakshi Kainth
Chief Financial Officer · Capital, Compliance & Culture
Why month-end takes so long
The work itself is not slow. What is slow is re-doing it. Attendance changes after payroll is drafted; payroll changes after the invoice is typed; the invoice changes after the accountant has booked it. Each change ripples back through every copy. The fix is structural: lock each stage before the next one reads from it.
Stage 1 — Attendance approved
Each site's muster roll covers its own payroll window. Supervisors or field officers mark it daily — or upload a photo of the paper sheet — then submit. An approver checks deployed strength against the contract and approves, and the sheet locks. Present days are capped by the contract basis; extra days become Extra Duty.
Stage 2 — Payroll approved
Payroll for the site is built only from the approved sheet and the contract's rates. HR checks the register: paid days, wage lines, EPF on the capped base, ESIC applicability and PT for the state. Then it is submitted and approved by someone with approve rights.
Stage 3 — Payroll processed
Processing is the point of no return. Anyone who must not be paid this run is put on hold with a reason. The system posts every deduction and employer contribution to its ledger, freezes the wage slips and produces a bank upload file and pay sheet.
Stage 4 — Final invoice
The invoice uses the same approved days, priced at the contract's billing rate, with CGST/SGST or IGST decided by the client's state. When Finance generates the final invoice, a number is taken from the billing state's series for that fiscal year. Once issued, it can never be released or reused.
Stage 5 — Tally and close
Finance downloads the Tally voucher file, imports it, and uploads the final invoice PDF back against the site. The site now shows Processed on every charter, and the month is closed for it.
When something changes after payment
Amend, do not reopen. The paid sheet stays frozen as version 1; version 2 records and approves the correction. Payroll posts only the difference as arrears or recovery in the next run. Nothing already paid is silently rewritten.
A realistic calendar
For a window ending on the 25th, supervisors submit and Ops approves on the 26th–27th; HR approves payroll on the 28th–29th; payroll processes around the 30th–1st; final invoices and Tally follow on the 1st–3rd; PF and ESIC are deposited by the 15th.
Topics & keywords
- security agency month end process
- guard payroll and billing
- muster roll to invoice
- manpower billing process
- Hyper Ops
- HyperRevamp
Key Takeaways
- Lock each stage before the next stage reads it.
- Track the close per site and payroll window.
- Use amendments for corrections after payment instead of rewriting history.
Frequently asked
What if a client disputes the invoice?
Because the invoice uses exactly the approved attendance, you can share the muster roll for that window as backup. If attendance was wrong, correct it with an amendment.
Can we combine sites into one invoice?
Yes, for the same client in the same state. One invoice never spans two states.
Does this work for sites with different windows?
Yes. Every site closes on its own window; the charters group them by period.
