Moonlighting: what employment records can and cannot show

How the check actually works

Despite the name, there is no moonlighting database. What exists is a set of records that show formal employment over time, and a moonlighting check is the work of laying them side by side and looking for periods that overlap.

The main source in India is the EPFO member record behind a candidate's Universal Account Number. That record shows which establishments made provident fund contributions for a person and for which months. If two different establishments were contributing for the same months, that is visible, and it is visible without either employer being asked anything.

Two other sources contribute. A directorship and DIN check at the MCA register shows whether the person holds a directorship in another company, which is a different kind of outside interest but often the more significant one. And a standard employment verification establishes what the candidate declared, which is what the records get compared against.

What it will never see

This is the part that gets skipped in the sales conversation, and it is a large part.

• Freelance and consulting work. Paid on invoice, no provident fund, no trace in the records this check reads.
• Work for a foreign employer. Outside the Indian formal employment system entirely.
• Informal and cash-paid work. No record anywhere.
• Employment below the EPF threshold. Smaller establishments outside the scheme do not appear.
• A business run through family members. Nothing in the candidate's own name to find.
• Anything that is not employment at all. An advisory role, an equity stake, a side project.

Taken together that is a lot of possible outside activity that this check is structurally blind to. It matters because an employer who believes a clear moonlighting check means "no outside work" has bought a false reassurance. What it means is "no second formal employment appears in the records searched".

Four ordinary reasons an overlap appears

An overlap in contribution records is genuinely common, and most of the time it is not two jobs at once.

1. Notice period

The most frequent cause by a wide margin. An employee serves out a notice period while the new employer, having taken them on from a nominal start date, has already begun contributions. The records show both establishments contributing for the same month or two. Nobody did anything wrong.

2. Delayed exit processing

An employer that is slow to close a payroll record can keep contributing after the person has actually left. The candidate has no visibility of this and no way to prevent it.

3. Contractual handover or transition

Consultancy and services firms sometimes retain a person formally for a transition period after they have started elsewhere, with the client's knowledge. It is on the record as concurrent employment and it was agreed by everyone involved.

4. A transfer between group entities

A move from one entity of a group to another can appear as two establishments, briefly overlapping, when it was one continuous job.

None of that is exotic. It is the everyday texture of formal employment records, and a process that treats an overlap as a finding will generate a steady stream of accusations against people who did nothing.

The policy has to come before the check

Here is the question that decides whether this check is worth buying: what does your contract say?

Moonlighting in India is largely a contractual matter. Whether an employee may hold other work depends on the employment contract, any exclusivity or conflict-of-interest clause, and the employer's own policy. If a contract is silent, an employer who discovers a second job has discovered a fact, not a breach.

So the sequence that works is: decide the policy, write it into the contract and the handbook, tell people what it says, and then run a check that tests against it. The sequence that produces problems is buying the check first, finding an overlap, and then working out in a hurry whether it was against anything.

It is also worth deciding what the policy is actually protecting. In most cases the concern is not that somebody has a second income; it is conflict of interest, use of company data and equipment, and availability. A policy written against those three things is easier to defend than a blanket ban, and it points the check at the cases that matter.

When it is worth running

The pattern is the same one in scoping a package by role: run the check where it maps to a real exposure, not because it is available.

What to do when you find one

Ask the candidate, before you conclude anything. Given the four causes above, the most likely explanation for an overlap is one the candidate can document in a day: a resignation letter with dates, a settlement statement, an email confirming a transition arrangement.

If it turns out to be genuine concurrent employment, then the decision is yours and it should be made against the contract, the policy and the role rather than against a general feeling about moonlighting. And it should be recorded, for the same reason every other flagged finding should be: so the decision is reviewable later by somebody who was not in the room.

The dedicated check page is moonlighting check, and the general principle for handling any flag is in how to read a discrepancy.