Salary verification in India means confirming, with documents and direct checks, what a candidate actually earned — not what their resume or offer negotiation claims. Every HR team runs this check differently. Few run it well. Some accept a payslip screenshot and move on. Others call the previous employer’s HR desk and hope someone picks up. Neither approach holds up when a bank later asks how a credit decision was made, or when an auditor asks how a compensation band was set for a lateral hire.
This guide breaks salary verification down into the exact documents, checks, and call scripts HR teams in India use — and where each one can still be gamed.
Want a faster way to run this check without adding headcount? Pietos runs employment and salary verification as a managed service — see how the process works below first.
Why Salary Verification Matters More in 2026 Than It Did Five Years Ago
Inflated salary claims are not new. What has changed is how easy they are to fabricate convincingly. Editable payslip templates circulate freely online. Bank statement generators produce realistic-looking PDFs in minutes. A candidate no longer needs design skills to manufacture a credible-looking income history — just a search engine.
This creates real exposure for HR teams:
- Compensation bands break. If one candidate’s inflated “last drawn salary” sets a new internal benchmark, every subsequent offer in that band gets skewed.
- Lending and BFSI decisions ride on HR data. Salary letters issued for loan applications, visa sponsorship, or landlord verification all trace back to what HR confirmed at hiring.
- Fraud rarely travels alone. A candidate willing to inflate a salary figure is statistically more likely to have misrepresented other parts of their history too — a pattern <cite index=”9-1″>Pietos has observed directly in fake payslip and fabricated degree cases uncovered during onboarding.</cite>
None of this means every candidate is dishonest. Most are not. But a verification process built only for the honest majority is a process with no defence when the minority slips through.
The Four Documents HR Actually Relies On
Salary verification in India draws on a small, consistent set of documents. Each proves something slightly different, and each has a different fraud ceiling.
1. Form 16 (Part A and Part B)
Form 16 is the annual TDS certificate every employer must issue to a taxed employee under Section 203 of the Income-tax Act, 1961, by 15 June following the financial year. <cite index=”41-1″>Part A carries the employer’s TAN, the employee’s PAN, and the acknowledgement numbers of quarterly TDS statements filed with the department</cite>. Part B carries the full salary breakup.
Why it matters for verification: Part A is generated directly from the TRACES portal, so its TDS figures should match the employee’s Form 26AS on the income tax e-filing portal. A genuine Form 16 can be cross-checked against government records. A forged one usually fails that cross-check the moment HR looks closely at TAN details or acknowledgement numbers.
2. Payslips (Last 3–6 Months)
Payslips show gross pay, deductions, and net pay for a specific cycle. They are the easiest document on this list to fabricate — and the one most HR teams still rely on most heavily.
Common red flags include unprofessional formatting, misaligned text, unusual fonts, and spelling errors</cite>, along with employer details that do not match public records. None of these checks alone is conclusive. Together, they narrow the field fast.
3. Bank Statements
Salary credits in a bank statement are harder to fabricate convincingly than a payslip, because they need to match a running account balance, not just a single document layout. <cite index=”5-1″>Bank statements confirm authenticity because salary credits show the real number that hit the account</cite> — not the number printed on a template.
HR should look for a consistent monthly credit from a recognisable payroll or corporate account, not round-number cash deposits that mimic a salary pattern.
4. EPFO Wage and Contribution Data
For any candidate covered under the EPF scheme, the Employees’ Provident Fund Organisation holds a month-by-month contribution record tied to their Universal Account Number. <cite index=”27-1″>Each entry shows the wage month the contribution was deposited for, alongside employee and employer contribution amounts</cite>, and it can be accessed through <cite index=”21-1″>the official EPFO member portal, where employees can activate their UAN, view their passbook, and check their contribution history</cite>.
EPFO data is the single hardest data point to fake, because it originates from the employer’s own statutory filing, not from a document the candidate controls. A mismatch between claimed salary and EPF wage base is one of the most reliable red flags available to HR.
Step-by-Step: How HR Verifies a Candidate’s Salary
Here is the sequence a disciplined HR team follows, in order of effort and reliability.
Step 1: Collect the base documents. Request Form 16 for the last two financial years, the last three to six payslips, and bank statements covering the same window. Ask for all three together, not one at a time — candidates who submit documents in stages have more room to adjust a later one to match an earlier inconsistency.
Step 2: Cross-check Form 16 against Form 26AS. Ask the candidate to share their Form 26AS or Annual Information Statement from the income tax portal, or verify the TDS figures independently if the organisation has access. A genuine Form 16 will reconcile. A fabricated one usually will not.
Step 3: Match payslip figures to bank credits. Line up net pay on the payslip against the actual monthly credit in the bank statement. A gap of a few hundred rupees is normal (rounding, minor reimbursements). A gap in the thousands, or a credit that does not appear at all, is not.
Step 4: Pull EPFO wage data where applicable. If the candidate’s UAN is available and the role falls under EPF coverage, compare the wage figures in the EPFO passbook against the claimed salary. This step alone catches a meaningful share of inflated claims, because it does not depend on any document the candidate can edit.
Step 5: Make direct contact with the previous employer. Call or email the HR or payroll desk at the candidate’s last employer, using contact details sourced independently — never a number the candidate provides. Confirm designation, tenure, and last drawn salary band. Keep the request narrow: most HR desks will confirm a salary range even when they will not confirm an exact figure, and a range is often enough to catch a material misstatement.
Step 6: Document the discrepancy trail, not just the conclusion. If something does not reconcile, record what was checked, what was found, and how it was resolved — not just a pass or fail. This record is what protects the organisation if the decision is questioned later.
Salary Verification vs Payslip Fraud Detection — Not the Same Job
These two get treated as interchangeable, and they are not. Payslip fraud detection asks whether a specific document is genuine — checking formatting, employer details, and issue patterns for signs of tampering. <cite index=”5-1″>Pietos’ guide on payslip fraud red flags in India walks through exactly what HR should watch for at the document level.</cite>
Salary verification is broader. It asks whether the number itself is real, using multiple independent sources — Form 16, bank credits, EPFO data, and direct employer contact — so that even a perfectly forged single document gets caught by a mismatch elsewhere. A team that only checks payslip formatting has done fraud detection. A team that cross-references four independent data points has done salary verification.
Red Flags That Should Slow Down an Offer
None of these alone should trigger a rejection. Together, they warrant a closer look before an offer is finalised.
- Payslip net pay does not match the bank credit for the same month
- Form 16 TDS figures do not reconcile with Form 26AS
- EPFO wage base is significantly lower than the claimed salary
- Previous employer’s HR desk has no record of the stated designation or tenure
- Candidate resists sharing bank statements after readily sharing payslips
- Document formatting is inconsistent across months from the “same” employer
Where Salary Verification Gets Legally Tricky
Salary verification touches personal financial data, which means it sits squarely inside India’s data protection framework. Under the Digital Personal Data Protection Act, HR needs documented, specific consent before collecting and processing a candidate’s bank statements, Form 16, or EPFO data — a blanket “I agree to background checks” line in an offer letter is not enough on its own.
There is also a payslip-issuance angle worth knowing on the employer side of the equation. <cite index=”53-1″>Since the Code on Wages, 2019 came into force on 21 November 2025, employers must issue a wage slip to every employee regardless of salary level</cite> — a rule enforced through the Chief Labour Commissioner’s office alongside state Shops and Establishments Acts. This matters for salary verification because it means a candidate’s current employer is legally obligated to have issued the payslip HR is trying to verify — one more reason a missing or inconsistent document is worth questioning rather than waiving.
Building This In-House, or Handing It to a Partner
Both paths work. The tradeoff is operational, not about capability.
Running salary verification in-house means someone on the HR team owns EPFO data pulls, Form 26AS reconciliation, and outbound calls to previous employers — for every hire, every cycle. That is manageable at low hiring volume. It becomes a full-time drag once an organisation is hiring at scale, because previous-employer HR desks do not always answer on the first call, and reconciliation across four document types takes real analyst time.
Outsourcing to a verification partner trades that time cost for a per-check fee. <cite index=”11-1″>Employers often save by outsourcing to specialists rather than maintaining the equivalent in-house team</cite>, particularly once salary verification sits alongside employment, education, and identity checks that already need a partner relationship.
Not sure which makes sense for your hiring volume? Pietos’ guide to background verification costs in India breaks down what each approach actually costs per hire.
A Salary Verification SOP You Can Copy
Use this as a starting checklist, then adjust thresholds to your risk tolerance:
- Collect — Form 16 (2 years), payslips (3–6 months), bank statements (3–6 months), all requested together
- Reconcile — Form 16 against Form 26AS, payslip net pay against bank credits
- Cross-check — EPFO wage data against claimed salary, where UAN is available
- Confirm — direct call to the previous employer’s HR desk, using independently sourced contact details
- Document — every discrepancy found, how it was resolved, and who signed off
- Escalate — any unresolved mismatch above your defined threshold to a second reviewer before the offer is finalised
What It Costs to Get This Wrong
The direct cost of a skipped salary check is easy to underestimate, because the damage rarely shows up immediately. An inflated salary accepted at face value resets the internal compensation benchmark for that role — every future negotiation for the same position starts from a number that was never real. In BFSI and NBFC hiring specifically, an unverified salary figure that later surfaces in a regulatory review becomes a documented compliance gap, not just an HR embarrassment.
Even a conservative fraud rate across a large hiring pipeline compounds into a meaningful cost once you account for the downstream compensation, training, and replacement expense of each bad hire. Salary verification is one of the cheapest checks in the entire pre-employment process relative to what a single missed case costs later.
How Pietos Helps
Pietos Solutions Private Limited runs salary and employment verification as part of its background screening service — Form 16 and 26AS reconciliation, EPFO/UAN wage cross-checks, and direct employer contact, with a documented discrepancy trail delivered alongside every report. It plugs into an existing hiring workflow without adding headcount to HR.
Ready to stop taking salary claims at face value? Talk to Pietos about setting up salary verification for your hiring pipeline — most teams are live within one hiring cycle.
Key Takeaways
- Salary verification confirms the number; payslip fraud detection confirms the document. Run both.
- Form 16, payslips, bank statements, and EPFO wage data each catch different types of misstatement — no single document is enough on its own.
- EPFO wage data is the hardest data point for a candidate to manipulate, since it comes from the employer’s own statutory filing.
- Consent under the DPDP Act must be specific to salary and financial data — a generic background-check clause does not cover it.
- Document the reconciliation trail, not just the final decision, so the process holds up under audit.
FAQ
No single law mandates salary verification itself. It is a discretionary HR risk control. However, once HR collects financial documents like bank statements or Form 16, DPDP Act consent requirements apply to that data.
Partially. Form 16, payslips, bank statements, and EPFO data together catch most discrepancies without a call. Direct contact remains the most reliable way to confirm designation and tenure, which documents alone cannot fully establish.
With the candidate’s consent and UAN, HR (or a verification partner) can review the EPFO passbook, which shows month-by-month wage and contribution figures tied to the employer that filed them.
Only employees whose income crossed the taxable threshold and had TDS deducted receive a Form 16. Candidates below that threshold will not have one — this is not itself a red flag.
How far back should HR check salary history? Two financial years of Form 16 and three to six months of payslips and bank statements is a practical standard for most roles. Senior or high-compensation roles often warrant a longer window.
