Skip to main contentSkip to content
LabourOSHWC CodeForms › Form XIII
Prescribed Form

Form XIII — Register of employees

Form-level filing, reconciliation and evidence guide.

Prescribed instrument: Annexure VII to the OSHWC Central Rules, 2026. Verify the current electronic filing mode and competent authority before submission.

Purpose and filing control

Form

Form XIII

Purpose

Register of employees

Referenced by

Rule 72

Owner

Employer, contractor, manager, authorised signatory or competent authority according to the form

Submission mode

Electronic portal where prescribed; retain generated acknowledgement and signed source data

Source review

2026-07-17

Preparation checklist

  1. Use the Gazette format and do not omit mandatory fields merely because a portal screen differs.
  2. Reconcile identity, establishment, worker, wage, safety and licence data to source systems.
  3. Attach supporting evidence and preserve the maker-checker approval.
  4. Record submission time, transaction ID and authority acknowledgement.
  5. Correct errors through the authorised amendment route rather than overwriting the original filing.

Linked Rules

Evidence file

Official source

Finin2min · Finance & Law Explained in 2 Minutes
Author: CA Nikhil Gupta · Reviewed by CA Nikhil Gupta · Last reviewed 10 September 2026.
Educational purposes only. Exact notified law, rules, schemes, regulator instruments, judicial decisions, state overlays, portal behaviour and facts must be checked before reliance. Verify with a qualified professional.

Practical guide: Form XIII — Register of employees

The points below turn Form XIII — Register of employees into a practical workflow so that the page can be used for a filing, computation, review or professional working paper rather than only as a definition.

Using this form in practice

Before completing Form XIII — Register of employees, identify the exact proceeding, registration or compliance event that has triggered the form. Read the linked rule together with the latest portal/Gazette version, because a form can be prescribed in the rules while the actual filing channel, attachments or workflow is implemented electronically.

Completion checklist

Match legal name, registration identifiers, period, jurisdiction and signatory details to the records already held by the authority. Reconcile every amount/date with the return, notice, order, books or supporting certificate that creates the filing obligation. Do not reuse data from an earlier period without checking it.

Evidence to retain

Keep the submitted form or acknowledgement, working papers used to populate it, authorisation of the signatory, supporting invoices/certificates/notices and proof of submission or service. If the form responds to an officer action, retain that communication and the chronology of your response.

Common failure points

Frequent problems are using an obsolete form version, selecting the wrong period or jurisdiction, inconsistent identifiers, incomplete attachments and treating a generated acknowledgement as proof that the underlying legal requirement was satisfied. Correct the underlying data first rather than only correcting the form.

Five-point final check