Pricing
Get your exposure report
Facility Management & Security

At 3% margin, compliance is not overhead.
It is the bid.

Hundreds of client sites, a handful of people at each, twelve-hour shifts, high attrition, and minimum wage that changes by state, zone and skill category. You are the employer of record for every one of those workers — PF, ESI, PT, LWF, bonus and gratuity all sit with you. So does the invoice.

yfy runs your roster, your payroll, your statutory position and your client billing off the same approved daily muster — and generates the compliance pack your enterprise clients keep asking for.

Finnovo Tech Functional Pvt Ltd · Hyderabad · ISO 9001:2015 · ISO 27001:2022 · ISO/IEC 27701:2019 · Billing starts at go-live, not at signature
What applies to you

Your licence stack is longer than your client's

Your client holds one CLRA registration. You hold a licence for every one of their establishments, a PSARA licence in every state you guard in, and a minimum wage obligation that differs by district. Nobody else in the contracting chain carries this much paper.

Private Security Agencies (Regulation) Act, 2005
What it requires
A licence from each state's Controlling Authority. Prescribed training for guards and supervisors under that state's PSARA rules. Character and antecedent verification, through the police, for every person deployed.
Where agencies get caught
The licence is per state and time-bound. A lapse rarely stops today's operation — it stops the next tender, and it is the first document an enterprise client's procurement team asks for.
Contract Labour (Regulation & Abolition) Act, 1970
What it requires
A contractor licence tied to each principal employer establishment, plus wage registers, muster rolls and returns per establishment.
Where agencies get caught
Every new client site creates a new licence obligation. In most agencies this lives in one person's spreadsheet, and nobody knows what expires next month.
Minimum Wages Act, 1948
What it requires
The notified floor for that state, that zone, and that skill category — unskilled, semi-skilled, skilled. Security services and housekeeping are frequently separate scheduled employments with their own notified rates.
Where agencies get caught
This is not a compliance line item. It is your entire cost base, it is revised by notification without much warning, and a rate revision you priced a contract before is margin you have already lost.
Payment of Wages Act, 1936
What it requires
Deductions only of the kinds the Act permits, within the prescribed limits.
Where agencies get caught
Uniform, equipment, training and ID recoveries are routine in this sector and a routine source of inspection findings and worker disputes.
EPF & MP Act, 1952 · ESI Act, 1948
What it requires
Contributions and returns, per establishment code.
Where agencies get caught
Workers who move between client sites inside one month are where the contribution arithmetic goes wrong, in both directions.
Payment of Bonus Act, 1965 · Payment of Gratuity Act, 1972
What it requires
Statutory bonus and gratuity provisioning.
Where agencies get caught
You carry both across a workforce with high churn and multi-site service, so the eligibility and continuity calculations are genuinely hard.
Weekly Off, National and Festival Holidays
What it requires
Under the applicable state establishment act — several states have their own National and Festival Holidays legislation.
Where agencies get caught
Twelve-hour security shifts and continuous-cover contracts make weekly-off compliance a scheduling problem, not a policy problem.
POSH Act, 2013
What it requires
Internal committee, annual return, and training.
Where agencies get caught
A largely female housekeeping workforce deployed at a client's premises sits in a genuinely awkward place between two employers' obligations. Worth having an answer ready.

Almost every threshold above has been amended by one or more states. That is exactly why we resolve applicability per state, against that state’s deployments, rather than against a national headcount — and why we publish which jurisdictions we have loaded rather than claiming all of them.

The problem

Five leaks, and four of them are invisible in a monthly total

Where agency margin quietly drains between site supervisor muster and finance billing.

The aggregate ceiling, split the wrong way
One guard at three client sites in a month, on three different rates. The statutory ceiling applies once, on the worker's aggregate for that month, and then apportions back across each client line. Computed per line instead — which is what a spreadsheet does — you either over-deduct from the worker or under-remit to the department. Both cost you, and neither shows up in a total.
Attendance arrives late, so cash arrives late
Supervisors send sheets, photographs and phone calls. Someone keys them in. A three-day delay at site becomes a two-week delay on the invoice. On a 3% margin, working capital is the business.
Billed days drift from paid days
The two figures are calculated separately, from different sources, by different people. The gap is your margin, and it is usually discovered at year end when it is far too late to bill for it.
Compliance proof rebuilt by hand, every time
A client asks for the pack. Someone spends three days assembling challans, registers and wage records. It is never quite complete, and an incomplete pack gives an enterprise client a defensible reason to hold a payment.
Licences and verifications found lapsed by the client
PSARA renewals, guard training records and police verification discovered at an audit rather than tracked to an expiry date.
Four of these five are symptoms of the same thing: attendance, payroll and billing are three records in your business instead of one.
How we are built

Approve the day once. Everything downstream reads the same record.

The roster-day spine: single-entry attendance guarantees that what was worked is what is paid, billed, and evidenced.

Output 1

Worker payroll

Wages, overtime and lawful deductions for the person who actually stood at that site on that day.

Output 2

Statutory liability

PF, ESI, PT, LWF, bonus and gratuity — all yours as employer of record, all computed from the same approved day.

Output 3

Client billing

Billed days cannot drift from paid days, because they are the same row.

Output 4

GST invoice

Your markup applied per contract, invoice raised with the attendance evidence already attached.

The arithmetic nobody gets right. Aggregate the worker's month across every client site. Apply the statutory cap once, on the total. Apportion the liability back to each client line. Every rupee traces to a day, a site and a client — which is the only version of this that survives both a client audit and an inspection.

Site muster

The best attendance system is the one that gets used at 6am at a gate with one bar of signal

Built specifically for distributed supervisors managing remote posts with low signal.

No app to install

A supervisor opens a link sent by SMS. No download, no app-store account, no IT ticket, no training session. For a workforce of a few people at each of two hundred sites, this is the difference between a system that works and one that gets abandoned in month two.

Works offline

Marks are held on the device and sync when signal returns. A basement car park or a dead zone at a plant gate does not stop the muster.

Saves on every tap

There is no submit button to forget. Each mark is stored as it is made, so a dropped connection loses nothing and nobody has to re-enter a shift.

Cover and replacement in one tap

When a guard does not show, the supervisor records who covered the place — on the spot, at the site, not reconstructed from memory at month end. That single behaviour is where most billed-versus-paid drift originates.

Geo-tagged, timestamped and tied to the site, so a man-day is evidenced rather than asserted — whether the question comes from your client or an inspector. Where you already have biometric devices at larger sites, those feed the same muster.
The volume problem

High churn is not a people problem you can fix. It is a throughput problem you can systemise.

A two-thousand-worker agency may onboard and exit several hundred people a month. Each one is a joining record, a statutory enrolment, a uniform issue, a verification file, a site deployment and eventually a full and final settlement. Attrition in this sector is not going to fall. The cost of processing it can.

Bulk onboarding, entered once

Joining records, PF and ESI enrolment data, bank details and identifiers captured once and reused everywhere downstream. Nobody re-keys a PAN into a second system, which is where most enrolment errors originate.

Deployment in batches, with the right wage

Assign hundreds of workers to sites in one action, with each site's client contract, state, zone and skill category — and therefore the right minimum wage floor — attached automatically rather than selected by hand.

Verification & training as a gate

Where PSARA applies, a person without current antecedent verification or the prescribed training is visible before deployment rather than discovered at a client audit.

Exit that settles itself

Uniform, equipment and ID recovery ride an obligation ledger into full and final settlement, so an unreturned item becomes a lawful, recorded deduction rather than someone editing payroll by hand under time pressure.

Continuous service is held against the worker rather than the deployment, so a person who moves between three client sites over two years has one service history — which is what makes gratuity eligibility and bonus continuity correct rather than approximate.
What you hold

Every licence, every registration, every verification — with an expiry date attached

The document that ends a tender is the one nobody knew had lapsed.

PSARA licence, per state
CLRA licence, per client establishment
EPF registration
ESI registration
Professional tax registration
Labour welfare fund registration
Workmen's compensation / EC insurance
Shops & Establishment registration per site
Guard training records, per person
Police / antecedent verification, per person
Certificate of incorporation, GST, PAN
Client contracts and rate cards

Per-state establishment codes matter more here than anywhere. EPF, ESI, LWF and CLRA licence numbers differ by state for the same agency — so a challan you produce for a Karnataka client has to be reconcilable to the workers deployed in Karnataka, under the right code. We hold them per state, not as one flat number on your company record.

The commercial edge

Your client's exposure is real. Being the agency that removes it is a pricing position.

Under CLRA §21, EPF §8A and ESI §40, your principal employer becomes the payer of last resort for your defaults. Their board knows it. Their procurement team has been asked to reduce it. Most agencies experience that as an audit. It can be a differentiator instead.

A generated monthly compliance pack

ECR and ESI challans, wage registers, muster records and statutory evidence — packaged per client contract, produced rather than assembled. What currently takes three days becomes a download.

A scoped client window

Give your principal employer a read-only view of their own deployment: workers, attendance, statutory position. Their contract only, nothing else, ever. Enforced at the platform, not configured.

Your brand, not ours

White-label the portal your clients see — your name, your domain, your branded documents. Four rendering planes: the application, PDF and spreadsheet output, email from your own sending domain, and custom domains with automatic TLS.

An agency that can hand a client a live compliance view is no longer competing on rate. It is removing a risk from their balance sheet — and that is a conversation with procurement, not with purchasing.

What your client receives, every month, per contract

The automated compliance evidence bundle that unlocks client payments.

Wage register and wage slips for deployed workers
Evidence the notified statutory floor was met at their establishment, for their workers.
PF ECR and ESI monthly contribution filings
Proof the contributions covered their deployment specifically — not that you filed something for someone.
Challans and payment receipts
Held against the correct wage month. A bank statement is not evidence; an acknowledged return and stamped receipt are.
Attendance record per worker per day
Geo-tagged and timestamped, letting clients reconcile the days they were billed against an auditable record.
The CLRA register set for their establishment
Precisely what a statutory inspection at their premises will ask them to produce.
Licence and verification status for personnel
PSARA training certificates and police antecedent verification records, current as at the pack date.
Bonus and gratuity provisioning position
Increasingly requested by listed clients assessing their own residual exposure.

Generated from the records the month already created. What currently takes three days and arrives incomplete becomes a download that is complete by construction.

How this is set up

Most FM agencies need one lens. Large ones need both.

Configure the platform to match your operating model with zero custom engineering.

SituationLensWhere to read more
You supply manpower to client sitesSupplier lens. Roster, payroll, statutory, billing, client proof.Staffing view →
You sub-contract labour yourself — specialist trades, pest control, technical servicesPrincipal employer lens. You verify your sub-contractor's bill before you pay it, on the same platform.Principal employer view →
BothOne tenant configuration field. Most integrated FM groups above ₹200 crore run both.Ask us in the first call
Frequently Asked Questions

Commercial and operational answers

Honest limits: What we do not do

We state our operational boundaries clearly so expectations align before you sign an agreement.

  • We are not a CAFM or CMMS. Work orders, asset maintenance scheduling, helpdesk for building systems — not ours. We run the workforce, the statutory position and the billing.
  • We do not source or recruit. Onboarding through to deployment, payroll and billing, yes. Finding guards and housekeeping staff is your business and your channels.
  • PSARA support means tracking, not filing. Licence expiry, training records, verification records. Not the government application itself.
  • We do not deliver training content. Course delivery and certificate evidence, yes — the curriculum is yours or your accredited training partner's.
  • India only. Deliberately. The depth in state minimum wage, professional tax, labour welfare fund and CLRA exists because we did not spread across jurisdictions.
  • We have three ISO certifications and few public references. We would rather prove the engine on one month of your own roster and billing than show you someone else's logo.

See what your clients would find — before they look

Send us one month: your deployed roster with client sites, that month's payroll register, one client invoice, and your PF and ESI challans. We reconcile them against the statute and show you exactly where the gaps are. Then we show you the pack you could be handing every client, every month, instead of building it by hand.

Roster-to-payroll reconciliation: paid days vs billed days per client site
Minimum wage compliance per site, state, zone and skill category
PF, ESI, PT and LWF checked against challans with aggregate-cap apportionment
Statutory bonus and gratuity provisioning position
A sample client-facing compliance pack for one of your contracts
Two weeks · under NDA · read-only. Nothing installed, nothing migrated, no workers moved.
Get your compliance proof pack Book a call with a statutory architect
Statutory references reviewed: September 2026 · Finnovo Tech Functional Pvt Ltd · Madhapur, Hyderabad