Statutory Registers Under Indian Labour Laws: 2026 Guide

Ask any labour inspector what they look at first when they walk into an establishment, and the answer is almost always the same: the registers. Statutory registers are the official, prescribed records that Indian employers must maintain under a web of central and state labour laws — attendance, wages, overtime, leave, fines, advances, accidents and more. For HR managers and founders at small and mid-sized businesses, these records are not paperwork for paperwork's sake. They are the primary evidence of whether your organisation pays people correctly, treats them lawfully and can defend itself when questioned. This guide walks through the statutory registers most Indian employers need, how the newer labour codes are reshaping them, how to maintain them digitally, and how to build a record-keeping system that survives an inspection without a scramble.

One caveat before we begin: labour law in India is a layered, evolving field. Requirements differ by state, by industry, by headcount and by the stage of implementation of the new labour codes. Treat everything here as practical orientation, not legal advice — and always verify current, applicable requirements against official notifications for your state and sector, or with qualified counsel.

Why Statutory Registers Matter for Indian Employers

It is tempting to see registers as a relic of an older, ledger-bound era of compliance. That view is expensive. Statutory registers sit at the intersection of three high-stakes situations every employer eventually faces.

Inspections and enforcement

Labour enforcement in India operates largely through inspections — increasingly scheduled through online inspection systems in many states, but still anchored in document verification. When an inspector (or "inspector-cum-facilitator" under the newer framework) examines your establishment, registers are the first artefacts requested. Clean, current, internally consistent registers signal a well-run establishment and usually shorten the interaction. Missing or contradictory registers invite deeper scrutiny, adverse notes, show-cause notices and, in serious cases, prosecution.

Disputes and litigation

When a former employee claims unpaid overtime, wrongful deduction or denial of leave encashment, the burden often shifts to the employer to prove what actually happened. Courts and labour authorities give significant weight to contemporaneous records. A muster roll and wage register maintained in the ordinary course of business is persuasive evidence; a spreadsheet reconstructed after the dispute arose is not. In practice, the employer with better records usually has the stronger case.

Audits, due diligence and funding

For growing SMBs, statutory registers surface in unexpected places: customer vendor-compliance audits, ISO and social-compliance certifications, and investor due diligence. A startup raising a round or an SMB bidding for an enterprise contract will frequently be asked to demonstrate labour law registers and filings for the past several years. Gaps discovered at that stage can delay deals or force indemnities. Records compliance, in other words, is not just a legal obligation — it is commercial hygiene.

There is also a quieter benefit. The discipline of maintaining a muster roll, wage register and leave register accurately forces payroll, attendance and HR data to reconcile. Many payroll errors are caught not by payroll software but by the act of preparing statutory records that must agree with each other.

The Legal Landscape Behind Labour Law Registers

Understanding why there are so many registers helps you organise them. India's labour framework historically consisted of dozens of separate central enactments, each with its own rules prescribing registers and forms, plus state-level rules and state-specific laws such as the Shops and Establishments Acts. The frameworks most relevant to record keeping for a typical SMB include:

• Minimum wages framework — registers evidencing that employees receive at least the notified minimum rates, including wage records, muster rolls and overtime records.
• Payment of wages framework — records of wages paid, deductions made, fines imposed and advances given.
• Shops and Establishments Acts — state legislation covering commercial establishments (offices, shops, IT companies, services firms), each state prescribing its own registers for attendance, wages, leave and holidays.
• Factories framework — for manufacturing units, an extensive set of registers covering adult workers, leave with wages, accidents, health and safety.
• Contract labour (CLRA) framework — registers for principal employers and contractors covering contract workers deployed at an establishment.
• EPF and ESI frameworks — largely electronic today, but still requiring underlying records such as eligibility registers, contribution records and accident records, along with inspection books.
• Other thematic laws — maternity benefit records, bonus registers, gratuity-related records, equal remuneration records and, where applicable, records under building and construction worker or migrant worker frameworks.

Layered on top of this is the consolidation effort: the four labour codes (on wages, industrial relations, social security, and occupational safety, health and working conditions) are designed to replace most of the older central laws and to rationalise registers and returns. Implementation has been phased and uneven across states, which means many employers in 2026 are operating in a transition environment — old-law registers in some respects, code-based formats in others, depending on state notifications. We cover this in detail below; the operational takeaway is simple: confirm which regime applies to your establishment in your state right now, and revisit that question periodically.

Core Statutory Registers Every Employer Should Know

Whatever the governing statute, the same functional records appear again and again. If you understand these eight, you understand most of Indian employee records compliance.

Muster roll / attendance register

The muster roll is the daily attendance record — who was employed, who was present, absent or on leave, on each working day. It typically captures employee name, designation, dates, and daily presence markings, and often working hours and rest intervals.

Why it matters: the muster roll is the foundation on which everything else rests. Wages, overtime, leave accrual and even headcount-based applicability of laws all trace back to attendance. Inspectors routinely cross-check the muster roll against the wage register; mismatches (an employee marked absent but paid, or present but unpaid) are among the most common adverse findings.

Practical tips:

• Keep the muster roll updated daily, not reconstructed at month-end.
• Ensure biometric or app-based attendance data can be exported into the prescribed register format.
• Record leave and holidays explicitly rather than leaving blanks; blanks invite questions.

Wage register / register of wages

The wage or salary register records, for each wage period, the components of pay: rates of wages, gross earnings, allowances, overtime, deductions (statutory and otherwise) and net amount paid, along with the date and mode of payment and often an acknowledgment of receipt.

Why it matters: this is the single most examined record in wage-related disputes and minimum wage inspections. It must reconcile with the muster roll (days worked), with bank transfer records (amounts paid) and with wage slips issued to employees.

Practical tips:

• Show wage components in the structure required by the applicable format, not just your internal payroll heads.
• Keep the register consistent with wage slips — discrepancies between the two are an easy adverse finding.
• Where wages are paid by bank transfer, retain the payment confirmation trail alongside the register.

Register of fines

Where an employer imposes fines on employees for prescribed acts or omissions, the law generally requires a dedicated register recording the employee, the act or omission, the amount of fine, and how the realised amounts were utilised (fine proceeds are typically to be applied only to notified purposes). Fines are tightly regulated — permissible only for specified conduct, subject to caps and procedural safeguards.

Practical tip: many SMBs impose ad-hoc "penalties" (late-coming deductions beyond proportionate wage cuts, damage recoveries) without realising these fall within the regulated fines-and-deductions regime. If you fine at all, maintain the register; if the register would be empty because you never fine, know that a nil register may still be expected in some formats.

Register of deductions for damage or loss

Separate from fines, deductions made for damage to or loss of goods or money entrusted to an employee are usually recorded in their own register, capturing the circumstances, the amount, and evidence that the employee was given an opportunity to show cause. Unauthorised or excessive deductions are a classic trigger for claims, so this register doubles as your procedural defence.

Overtime register

Wherever employees work beyond prescribed daily or weekly hours, an overtime register records the extra hours and the overtime wages paid — generally at a premium rate. Overtime is a perennial inspection focus because under-recording is common: attendance systems show late log-outs while the overtime register shows nothing.

Practical tips:

• Align your overtime policy with legal limits on hours and spread-over, and record all qualifying overtime, not just pre-approved overtime.
• Reconcile overtime entries with attendance data monthly; unexplained gaps are risky.
• Remember that exemption assumptions (for example, that all "managerial" staff are outside working-hours rules) should be verified against the applicable law, not assumed.

Leave register / register of leave with wages

The leave register tracks each employee's leave entitlement, accrual, availment, balance and encashment — typically covering earned/annual leave and often other categories prescribed by the applicable state law. It supports leave-with-wages obligations and encashment calculations at exit.

Practical tips:

• Keep opening balances, accruals and closing balances arithmetically clean; sloppy carry-forward math is a frequent audit note.
• Ensure your HRMS leave data maps to the categories in the prescribed format.
• Record leave availed on the muster roll consistently with the leave register.

Register of advances

Where employers grant wage advances or loans recoverable from wages, a register of advances records the amount advanced, purpose, instalments and recoveries. Recovery of advances is regulated (limits on instalment size, no interest beyond what is permitted), so the register protects both parties.

Accident register and safety-related records

Establishments covered by factory law, and workplaces generally under safety frameworks, maintain records of accidents and dangerous occurrences — what happened, to whom, the injury, and the reporting done. ESI-covered establishments also maintain an accident book supporting employee injury claims. Even in low-risk office environments, an accident record is inexpensive insurance: when an employee is injured at work, contemporaneous records determine how smoothly compensation or ESI processes run.

Employee register / register of employment

Many frameworks require a master register of persons employed: name, parentage or spouse name, date of birth, address, date of joining, designation, category (skilled/unskilled, supervisory), wage rates and exit details. Under consolidated formats this often becomes the anchor register into which other records link. Treat it as your canonical employee master, and keep it synchronised with your HR system of record.

Registers Under the Shops and Establishments Act

For most services businesses — IT companies, agencies, clinics, retailers, restaurants, offices of any kind — the state Shops and Establishments Act is the primary day-to-day labour statute. Two things make it tricky for record keeping:

1. It is state-specific. Each state (and sometimes union territory) has its own Act and rules, with its own prescribed forms, register formats, visible notices and language requirements. A register format valid in Karnataka may not match what Maharashtra or Telangana prescribes.
2. It covers the basics comprehensively. Registration of the establishment, working hours, weekly holidays, leave, wages, employment of women (including conditions for night work where permitted), and displays/notices — each generating a record or register.

Commonly prescribed records under Shops and Establishments frameworks include:

• Registration certificate of the establishment (displayed and renewed as required by the state).
• Attendance and hours-of-work records, including rest intervals and weekly off days.
• Leave register and leave books or cards for employees.
• Wage records aligned with the state's format.
• Notices to be displayed: working hours, holiday lists, contact details of the establishment and, in many states, abstracts of the law.
• Records relating to employment and termination of employees.

Because formats vary, the practical approach for a multi-state employer is to maintain a superset data model — capture every field any of your states requires — and generate state-specific formats from it. Several states have also moved Shops and Establishments compliance online, allowing or requiring electronic registers and intimations; check your state's labour department portal for what is currently accepted.

If you operate in multiple states, assign explicit ownership per state. The most common multi-state failure mode is assuming the head-office state's compliance covers branches. It does not: each establishment generally needs its own registration and its own registers.

Registers Referenced Under EPF, ESI, CLRA and Wage Laws

EPF and ESI records

Provident fund and employee state insurance compliance is now predominantly electronic — contributions, returns and member records flow through the respective online portals. But portal compliance does not eliminate record keeping:

• Eligibility and coverage records: evidence of which employees are covered, wage details used to determine coverage and contributions, and declarations/nomination forms collected at joining.
• Contribution trails: challans, electronic return acknowledgments and reconciliations between payroll, the wage register and portal filings.
• Inspection book / records for inspectors: establishments are generally expected to keep records available for inspection by EPF and ESI authorities, including historic contribution and employment data.
• Accident records for ESI purposes, as noted above.

The risk here is subtle: because filing happens online, SMBs assume "the portal is the record." In a dispute about coverage or contribution shortfall years later, you will need your own organised archive — payroll registers, ECR acknowledgments, and the joining documents that established each employee's wage and coverage status.

Contract labour (CLRA) records

If you engage workers through contractors — security, housekeeping, facility management, staffing agencies — the contract labour framework creates parallel record obligations:

• The principal employer typically maintains a register of contractors engaged at the establishment.
• Each contractor maintains registers of the contract workers employed, along with muster rolls, wage registers, deduction, fine, advance and overtime registers for those workers, and issues wage slips and (in traditional formats) employment cards.
• Registration and licensing documents (principal employer registration, contractor licences) where thresholds are met.

Principal employers should not treat contractor records as someone else's problem. If a contractor defaults on wages, liability can travel upward. A monthly ritual of collecting and verifying contractor compliance evidence — wage registers, payment proof, PF/ESI challans for deployed workers — is one of the highest-value compliance habits an SMB can build.

Minimum wages and payment of wages records

These frameworks are the source of many of the core registers described earlier — wage registers, muster rolls, overtime, fines and deductions registers — along with obligations to issue wage slips and display notices of minimum wage rates. The essential compliance question they answer is binary and unforgiving: can you demonstrate, from your own records, that every employee received at least the applicable minimum wage for the time they worked, paid on time, with only lawful deductions? Your registers are how you answer yes.

The Labour Codes and the Consolidated Register Concept

The four labour codes were enacted to subsume most central labour laws, and one of their explicit aims is ease of compliance: fewer registers, common definitions (notably a uniform definition of "wages"), single registrations, and unified returns. On the records front, the direction of travel includes:

• Consolidated register formats replacing multiple overlapping registers — the rules framed under the codes contemplate a small set of registers (covering matters such as employee particulars, attendance, wages, overtime, and leave) instead of the dozens prescribed under legacy laws.
• Electronic maintenance expressly recognised, with registers and records permitted to be kept in electronic form and returns filed online.
• Wage slips and appointment letters as universal obligations, formalising practices many employers already follow.
• Inspector-cum-facilitator model and randomised, often web-based inspection allocation, which increases the importance of being continuously ready rather than tidying up when an inspector is known to be coming.

Two crucial caveats for 2026:

1. Implementation status varies. Bringing the codes into force requires central and state-level steps, and states have moved at different speeds on rules and notifications. Depending on your state and sector, you may be governed by legacy laws, by the codes, or practically by a mixture during transition. Do not assume the codes' simplified registers have replaced your legacy obligations until you have verified the position for your establishments.
2. Formats follow rules, and rules change. Even where codes are in force, prescribed register formats come from rules and notifications that get amended. Build your system to adapt to format changes rather than hard-coding one template.

The safe operating posture: maintain data at a granularity that can populate either regime's formats, and get a definitive answer from counsel or your compliance vendor on which formats to produce for each state, reviewed at least annually.

Combined and Unified Register Formats

Even before the labour codes, the government pursued ease-of-compliance initiatives that allowed employers to maintain combined or unified registers — a rationalised set of common formats accepted across multiple central laws, instead of maintaining near-duplicate registers under each statute separately. The logic is obvious: a muster roll under one law and an attendance register under another capture essentially the same facts.

For SMBs, the practical implications are:

• You may not need as many physical registers as a literal reading of each law suggests. Where combined formats are permitted for the laws applicable to you, one well-designed register can serve several statutes.
• Acceptance can vary. Central rationalisation applies to central rules; state laws (especially Shops and Establishments) may still prescribe their own formats. Confirm with your state labour department or advisor which unified formats are accepted for your establishments.
• Field completeness is the trick. A combined register only works if it captures the union of all required fields. When designing or buying a system, evaluate it on field coverage, not just on whether it prints something labelled "muster roll".

Register types at a glance

The table below maps the common register types to the frameworks that typically require them and the core purpose each serves. Treat it as an orientation map, not an exhaustive statement of law.

Electronic Registers: Digital Maintenance and Validity

Can statutory registers be maintained digitally? Broadly, yes — and increasingly, that is the expectation rather than the exception. Electronic governance law in India generally recognises electronic records where a law requires documents to be maintained, several legacy rules were amended over the years to permit computerised registers, many state Shops and Establishments regimes allow electronic records or online filings, and the labour codes explicitly contemplate electronic registers and returns.

But "digital is allowed" comes with operational conditions you should engineer for:

• Producibility on demand. Whatever the storage medium, you must be able to produce legible registers — on screen or printed in the prescribed format — when an inspector or authority asks. A database you cannot render into the required format quickly is a compliance risk.
• Integrity and authenticity. Electronic records should be tamper-evident: audit trails of edits, controlled access, and a clear record of who entered or changed what and when. Some contexts expect authentication (signatures or digital signatures) on registers; know where yours does.
• Format fidelity. Digital does not mean freeform. If a rule prescribes columns, your export should present those columns.
• State-by-state acceptance. A minority of state or local requirements may still expect physical registers, ink-signed documents or physical displays at the premises. Verify locally before going fully paperless, and keep physical copies where required.
• Backups and continuity. An electronic register you lost in a laptop crash is worse than a torn physical register; it looks like concealment. Backups, retention and export capability are compliance features, not IT niceties.

Digital vs physical registers: an honest comparison

The pragmatic answer for most SMBs in 2026 is digital-first with print-on-demand: maintain records electronically in a system that can generate prescribed formats, and print or physically maintain only what your specific states still require on paper.

Retention Periods: How Long to Keep Labour Records

Retention is where good record-keeping programmes quietly fail. Registers get maintained diligently and then discarded during an office move — right before the year they cover becomes relevant to a claim.

Retention periods in Indian labour law vary by statute and state, and the labour codes' rules prescribe their own periods. Rather than memorising a matrix that may change, adopt these principles:

• Know the prescribed minimum for each record type in your applicable regime, and treat it as a floor, not a target.
• Retain beyond the minimum where disputes are plausible. Limitation periods for claims, the possibility of delayed EPF/ESI coverage disputes, and due diligence look-back windows all argue for longer retention of wage and service records.
• Retain service-history records effectively for the employment lifetime plus a buffer. Records establishing dates of joining and leaving, wages and service continuity feed gratuity, pension and retiral calculations decades later.
• Balance against data protection. Under India's data protection regime, personal data should not be kept forever without purpose — retention schedules should have an end as well as a beginning (more in the DPDP section below).

Indicative retention thinking (verify against current law)

Again: these are risk-management postures, not statutory statements. Pull the actual prescribed periods for your applicable laws and states, document them in a retention schedule, and review that schedule annually.

How to Set Up a Statutory Record-Keeping System: Step by Step

Here is a practical build sequence an HR manager or founder can execute over a few weeks.

Step 1: Map your applicability

• List every establishment (registered office, branches, warehouses, stores, factories) by state.
• For each, identify the governing frameworks: Shops and Establishments vs factories law, EPF/ESI applicability, CLRA exposure, industry-specific laws, and the current labour-code implementation position in that state.
• Note headcount thresholds you are near — several obligations switch on at specific employee counts, so record where you stand and set a trigger to reassess as you hire.

Step 2: Build the register inventory

• For each establishment, list every register, record, display and notice required, with its prescribed format and language.
• Mark which can be maintained electronically and which (if any) must be physical or displayed on premises.
• Identify where combined/unified formats can replace multiple registers.

Output: a one-page-per-location compliance register inventory. This document alone puts you ahead of most SMBs.

Step 3: Fix the data sources

• Attendance: ensure your biometric/app attendance system is the single source, covers everyone (including trainees and part-timers), and exports cleanly.
• Payroll: ensure payroll heads map to the wage components prescribed formats expect, and that payroll uses attendance data rather than a parallel spreadsheet.
• Employee master: consolidate joining data, statutory declarations and nominations into one HR system of record.

Step 4: Generate registers as a by-product, not a project

The sustainable design is one where registers are generated from operational data at the close of each period — attendance closes, payroll runs, registers render. If register preparation is a separate manual monthly project, it will decay. A modern HRMS with document management, such as CozyHR for Indian SMBs, can hold the employee master, attendance and payroll in one place and keep the resulting records organised per employee and per establishment, which is precisely the structure inspections and audits demand.

Step 5: Assign ownership and cadence

• Name one owner per establishment for register upkeep, and one central owner for the programme.
• Set a monthly close checklist: registers updated, reconciliations done (muster roll vs wage register vs bank payouts vs PF/ESI filings), contractor evidence collected.
• Set a quarterly review: formats still current? Any new state notifications? Headcount thresholds crossed?

Step 6: Reconcile ruthlessly

The single highest-value habit: monthly three-way reconciliation between attendance, payroll and statutory filings. Most register findings are not "register missing" but "registers disagree." Catching disagreements internally each month means an inspector never catches them for you.

Step 7: Archive with intent

• Define the retention schedule (per Step above), storage location, backup policy and destruction process.
• Archive by establishment, by year, by record type — the way an inspector or auditor will ask for it.
• Test retrieval twice a year: can you produce the wage register for a named month at a named branch within an hour?

Inspection Preparedness: Passing the Test Before It's Scheduled

Inspections under modern regimes are often randomly allocated and sometimes announced at short notice. Preparedness is therefore a standing state, not an event. Beyond registers, inspectors typically look at registrations and licences, displayed notices, wage slips, timely payment evidence, statutory filings and, where relevant, contractor compliance.

Labour compliance checklist for inspection readiness

Two behavioural rules for the inspection itself: designate who speaks and who fetches documents (unbriefed employees volunteering guesses cause avoidable trouble), and never fabricate or backdate a record to fill a gap discovered during an inspection — an honest gap is a finding; a fabricated record is an offence.

Common Record-Keeping Gaps in Indian SMBs

Pattern-matching across small and mid-sized employers, the same gaps recur:

• Registers exist only at head office. Branches in other states have no local registers or registrations, on the assumption that central records suffice.
• The payroll vendor is assumed to be handling it. Payroll processors compute salaries; unless explicitly contracted, they are not maintaining your statutory registers or state-specific formats. Check what your vendor actually delivers.
• "White-collar" complacency. Founders assume registers are for factories. Offices under Shops and Establishments Acts have their own register, leave, hours and display obligations.
• Contract staff invisibility. Housekeeping and security personnel appear in no register on either side — the contractor is informal, and the principal employer never asked.
• Overtime that officially doesn't exist. Attendance logs show consistent long hours; the overtime register is blank. This mismatch is easy for an inspector to spot because the contradiction is in the employer's own systems.
• Unmapped deductions. Ad-hoc recoveries (asset damage, notice-period shortfalls, "penalties") processed through payroll with no supporting register or due-process trail.
• Format drift. Registers maintained in whatever layout the software produces, never checked against the currently prescribed format for the state.
• No exit-side records. Full-and-final statements exist as emails; leave encashment computations, gratuity workings and settlement acknowledgments are nowhere in the file.
• Founder-dependency. All compliance knowledge lives with one person; when they leave, the registers stop.

Each of these is cheap to fix once named. The expensive version is discovering them in a due-diligence report or an inspection note.

The Onboarding-to-Exit Document Trail

Registers are periodic records; alongside them runs a per-employee document trail. A defensible personnel file, from hire to exit, typically looks like this:

At onboarding:

• Offer letter and appointment letter (now a general expectation under the codes' approach) with wage structure.
• Identity, address and age proof; educational and experience documents as relevant.
• Statutory declarations and nomination forms for PF, ESI (where covered), gratuity and other benefits.
• Bank details for wage payment; consent/notice documentation for handling personal data (see DPDP below).
• Entry in the employee register and, from day one, the muster roll.

During employment:

• Wage slips every period; increment and revision letters.
• Leave records, attendance regularisation trails, overtime records.
• Any fines/deductions documentation with show-cause trail.
• Disciplinary records, if any, maintained with due process.
• Accident/incident records where applicable; maternity benefit records where applicable.

At exit:

• Resignation/termination documentation and acceptance.
• Full-and-final settlement working: last wages, leave encashment computed from the leave register, deductions with basis, gratuity where eligible.
• Relieving and experience letters; recovery of assets documented.
• Exit updates to the employee register, PF/ESI records and any required exit intimations.
• Settlement acknowledgment from the employee.

The register system and the personnel file system should reference each other: the leave register proves the encashment number in the settlement; the muster roll proves the last working day. When both exist and agree, post-exit disputes become short conversations.

Employee Records in the DPDP Era: Privacy Meets Compliance

Statutory registers are, by definition, collections of personal data — names, addresses, wages, attendance, sometimes health and accident information. India's digital personal data protection regime adds a second lens to record keeping. Without turning this into a privacy treatise, HR teams should internalise a few principles:

• Legal obligation is your friend, but not a blank cheque. Processing employee data to comply with labour law obligations is a legitimate basis — but it covers the data the law requires, for the purposes the law requires. Collecting far more than needed "because the form had a field" is the habit to break.
• Notice and transparency. Employees should know what data you hold, why, and for how long. A short, plain-language employee privacy notice covering statutory records is quickly becoming standard practice.
• Minimisation and accuracy. Collect what the registers and filings require; keep it accurate (employees correcting their own master data via self-service helps both privacy and register quality).
• Retention with an end date. The same retention schedule built for labour compliance should specify when records are deleted or anonymised after their statutory and dispute-defence purposes lapse. "Keep everything forever" is no longer a defensible default.
• Security and access control. Wage data and personal identifiers deserve role-based access, encryption in modern systems, and audit logs. A leaked salary register is now a data protection incident, not just an HR embarrassment.
• Vendors are your responsibility. Payroll processors, compliance vendors and HR software providers process employee data on your behalf; contracts should reflect data protection obligations, and you should know where the data resides.

The reassuring news: the disciplines overlap. A well-designed records system — single source of truth, defined retention, access controls, audit trails — is simultaneously good labour compliance and good data protection. Verify the current state of data protection rules and their application to employment records as the regime's implementation matures.

Frequently Asked Questions

Which statutory registers apply to a small office with under ten employees?

Applicability depends on your state's Shops and Establishments Act, your industry and specific thresholds. Even very small establishments typically face registration, attendance, wage and leave record expectations, though some obligations relax below certain headcounts. Map your specific state's requirements rather than assuming small means exempt — several core obligations have no minimum headcount.

Can all statutory registers be maintained in Excel or an HRMS instead of physical books?

Largely yes: electronic maintenance is broadly recognised, and the labour codes explicitly contemplate it. The conditions that matter are producibility in the prescribed format on demand, integrity (audit trails, controlled edits), and any residual state-specific requirements for physical records or displays. Plain Excel meets the "electronic" bar but fails the integrity bar easily — files can be edited without trace — which is why systems with audit logs are safer.

What is the difference between a muster roll and an attendance register?

Functionally, very little — both record daily presence of employed persons. Different statutes historically used different names and formats, and combined-register initiatives have merged them in many contexts. What matters is that one authoritative daily attendance record exists per establishment and that it reconciles with wages paid.

Do the new labour codes mean I can stop maintaining the old registers?

Only where and when the codes and their rules are actually in force for your state and sector — and implementation has been phased and uneven. Until you have verified the position for each of your establishments, the safe course is to maintain records at a level of detail that satisfies both the legacy formats and the codes' consolidated formats, and to get a definitive regime determination from counsel or your compliance vendor, refreshed periodically.

Who is responsible for registers of contract workers — the contractor or the principal employer?

Both have roles. The contractor maintains the employment, muster and wage records for the workers they employ; the principal employer maintains its own records (such as a register of contractors) and carries oversight exposure — including potential liability if the contractor fails to pay wages or contributions. Prudent principal employers collect and verify contractor compliance evidence monthly before releasing payments.

How long should we retain registers after an employee leaves?

Statutory minimums vary by record type, statute and state, so document the actual prescribed floors for your regime. As risk management, wage and attendance records are commonly retained for several years beyond the minimum, and service-history records (joining, wages, continuity) effectively for the employment lifetime plus a buffer, because retiral benefits and delayed claims reference them. Balance this with data protection: your retention schedule should have defined end points, after which records are deleted or anonymised.

What happens if registers are missing or incomplete during an inspection?

Outcomes range from advisory observations and directions to rectify, to show-cause notices, monetary consequences and, in serious or repeat cases, prosecution — severity depends on the statute, the nature of the lapse and the regime in force. Practically, missing registers also weaken your position in any parallel wage or service dispute, because you lose the evidentiary high ground. If a gap exists, rectify prospectively and document the correction honestly; never backdate.

Are digitally signed or system-generated registers accepted by inspectors?

Increasingly yes, particularly in states with online inspection and filing systems, and the labour codes' framework anticipates electronic records and returns. Acceptance in the field can still vary by state and by individual office, so keep your registers printable in prescribed formats, know your state's position on signatures and authentication, and where doubt exists, confirm with the local labour office or your advisor.

Conclusion: Make Records a System, Not a Scramble

Statutory registers are where Indian labour law becomes tangible: every principle about fair wages, limited hours, lawful deductions and safe workplaces ultimately reduces to a row in a register that either exists or does not. For an SMB, the winning posture is unglamorous and completely achievable — know which records apply to each establishment, generate them automatically from attendance and payroll data, reconcile monthly, retain deliberately, and be able to produce any record within the hour. Do that, and inspections become routine, disputes become defensible, and due diligence becomes a formality.

The teams that get there stop treating registers as a filing chore and start treating them as a data problem with a system solution. If you are still stitching this together across spreadsheets, folders and a payroll vendor's PDFs, it may be time to consolidate. CozyHR, an HRMS built for Indian SMBs, brings attendance, leave, payroll data and document management into one place — so your registers, personnel files and audit trails stay organised by employee and establishment, ready whenever someone official comes asking. Try it, tighten your record-keeping in a quarter, and then verify your specific register formats and retention periods with your state's current notifications or your counsel — because in labour compliance, the details are always local and always current.