Employment Verification APIs for HR and BGV Teams

Employment verification for HR and BGV teams

Employment verification APIs help HR teams, staffing companies and background verification providers compare a candidate's declared work history with records returned by supported verification sources. DocuExprt brings these checks into a configurable workflow, so your team can review discrepancies and pass results to its existing systems.

Use this guide to understand the available checks, the information needed to run them, and where a reviewer should step in. For the broader solution, explore background verification automation or HR document verification and onboarding.

Choose the check that fits your workflow

What your team reviews

Illustrative review outcome — fictional example, not an API response or a hiring decision.

Coverage and exception handling

Source availability, candidate records and enabled checks affect what can be returned. Do not assume complete work-history coverage for every candidate. Plan for missing records, delayed updates, name differences and temporary source failures. Overlapping dates are a review signal, not proof of misconduct.

Confirm the required authorization and candidate-consent process before running checks. Route uncertain results to a designated reviewer; retain the evidence needed for your organization's process. For deployment and integration choices, see the enterprise document verification platform.

Planning an integration? Bring your expected monthly verification volume, required checks and HRMS/ATS details. Request an employment verification demo to review coverage, a sample result and the integration approach. Use synthetic or appropriately authorized sample data.

Why Employment History Verification Matters for Enterprise HR

The Cost of Getting It Wrong

A single bad hire at the mid-management level costs organizations between $50,000 and $240,000 when you factor in recruitment costs, onboarding, lost productivity, severance, and rehiring. For senior roles, that figure can exceed $500,000.

But the real risk is not just financial. In regulated industries like banking, insurance, healthcare, government, an unverified hire can trigger compliance violations, regulatory penalties, and reputational damage that far exceeds the hiring cost.

Resume Fraud Has Reached Crisis Levels

The numbers tell the story:

The gap between detection capability and fraud sophistication is widening. Nearly two-thirds (62%) of hiring professionals believe candidates are now better at faking identities with AI help than HR teams are at detecting deception.

Manual Verification Is Broken

Traditional employment verification methods have fundamental limitations:

• Phone-based reference checks take 3-7 business days per candidate and depend on former employers answering
• Letter-based verification can take 2-4 weeks and is easily forged
• Manual EPFO checks require candidates to produce physical documents that can be fabricated
• No real-time cross-verification between claimed experience and actual records

For organizations processing 50+ hires per month, manual verification becomes a bottleneck that either slows hiring or gets skipped entirely creating the compliance gaps that regulators exploit.

Regulatory Compliance Is Non-Negotiable

In India's BFSI sector, RBI and SEBI mandate robust employee screening for anyone in positions of financial responsibility or with access to sensitive customer data. Key requirements include:

• Fit and Proper criteria for directors and key functionaries at banks and NBFCs
• KYC staff screening — employees handling KYC must themselves be verified
• Third-party vendor verification for anyone accessing customer data
• Audit trail maintenance — regulatory audits sample random employee records, and missing verification documentation triggers serious compliance findings
• DPDP Act compliance — explicit consent, purpose limitation, and data minimization for all candidate data processing

How Employment Verification APIs Work

Employment verification APIs connect your HR systems directly to government databases, returning verified employment records in real time. Here is the core architecture:

The Three Government Database Layers

API vs. Manual Verification Comparison

How to Check Employment History Using UAN

There are two routes. The candidate can view their own Service History on the EPFO member portal, or an employer or BGV provider can fetch the same record through a consent-based API check.

Both read the same EPFO data. The difference is who handles it on the way to you.

Route 1: The candidate checks it on the EPFO member portal

Every member can see their own record on the EPFO Unified Member Portal.

1. Log in with the UAN, password and the one-time password sent to the registered mobile.
2. Open the View menu and choose Service History.
3. Read the list of establishments linked to the UAN, with member IDs and dates of joining and exit.
4. Download or capture the page and share it with the employer.

That last step is the weak point. A shared screenshot or PDF is a document, not a source check, and it can be edited before it reaches you.

Treat it as a claim to verify, not as proof. If you must accept one, run it through a document tampering check first.

Route 2: The employer or BGV provider checks it through an API

The candidate approves the check, and the API returns the employment record straight into your system. No candidate-handled file sits in between.

The returned history is then compared against the resume automatically, so reviewers see only the mismatches.

When UAN data will not answer the question

UAN records only show employment that was reported to EPFO. Plan a second check for these cases:

• Employers outside EPF coverage, such as smaller establishments, overseas roles and informal work.
• Older PF accounts never linked to the candidate's current UAN.
• Employees never enrolled in EPF, which can include some higher-salaried staff.
• Recent roles where the employer's filings have not caught up yet.

For these gaps, a PAN and Form 26AS check, forensic checks on relieving letters and salary slips, or direct employer confirmation fill in the picture.

A missing record is a reason to verify another way. It is not proof that the candidate lied.

Is UAN Employment Verification Legal? Where the Data Comes From

UAN employment records come from the returns employers file with EPFO. Checking them is lawful when the candidate knows about the check, has agreed to it, and the data is used only for verification.

The legal risk sits with vendors who skip those steps, not with the check itself.

What the DPDP Act means for employment checks

Under India's Digital Personal Data Protection (DPDP) Act, 2023, a candidate's employment and identity records are personal data.

The Act includes a "legitimate use" ground for employment purposes. Whether it covers pre-hire checks run by a third-party vendor is not settled, so most enterprises and BGV providers take explicit, check-specific consent anyway.

The DPDP Rules, 2025 were notified in November 2025, with most business obligations applying from May 2027. Consent records built today will need to hold up then.

Five questions to ask any employment verification vendor

Buyers serving multinational and regulated clients now ask these before signing. Any vendor should answer all five in writing.

1. Where does each check's data come from? Ask for the route, check by check.
2. Is consent captured before every check? And is it stored with the result?
3. Does any check work without the candidate knowing? Treat that as a red flag, especially for Aadhaar-linked lookups.
4. What is retained, and for how long? Documents, results and logs.
5. What certifications cover the platform? Security audits and ISO 27001 at minimum.

DocuExprt runs employment checks on a consent-first workflow. The consent flag, source and timestamp are logged with each result, so your audit file shows who agreed to what.

During an evaluation, ask the team to walk through the source route for each check you plan to use.

Getting candidates to say yes to the consent request

Candidates hesitate when an unfamiliar company asks for access to their records. This is common when a BGV provider sends the request on an employer's behalf.

Deployments that get high consent rates do four things:

• Warn candidates early. HR mentions the check at offer stage and names who will send it.
• Name the hiring company in the request, not only the vendor.
• Say which records will be checked and why, in one or two lines.
• Never ask for an OTP or password. Candidates approve access themselves.

DocuExprt's Employment Verification APIs

DocuExprt provides five employment verification API endpoints that cover the full spectrum of employment history checks:

1. UAN-To-Employment-History API

The flagship employment verification endpoint. Input a UAN number and receive the complete EPFO employment history.

Input: UAN Number
Returns:

• Employee name (as registered with EPFO)
• All employer names and establishment IDs
• Date of joining and date of exit for each employer
• Member IDs across employers
• PF filing status and contribution history
• Exit reason codes

Primary use case: Validate a candidate's claimed work experience against official EPFO records. If a candidate claims 5 years at Company X but EPFO records show only 2 years, the discrepancy is flagged automatically.

2. PAN-To-Employment-Status API

Input a PAN number and verify current employment status through income tax records.

Input: PAN Number
Returns:

• Current employment status
• TDS deduction history (Form 26AS data)
• Income declarations cross-referenced with employment claims

Primary use case: Detect moonlighting and dual employment. If a candidate claims to be unemployed but Form 26AS shows active TDS deductions from another employer, you know immediately. Since the pandemic, moonlighting investigations have grown 4X since 2019 — this API catches what HR interviews cannot.

3. Aadhaar-To-UAN Lookup

When a candidate doesn't know their UAN number (common for blue-collar and early-career workers), this API bridges the gap.

Input: Aadhaar-linked details
Returns: Associated UAN number(s)

Primary use case: Enable employment history verification for candidates who only have their Aadhaar number available. Chain this with the UAN-To-Employment-History API for complete verification.

4. UAN-To-UAN Verification

Validates that a UAN number is genuine and active within the EPFO system.

Input: UAN Number
Returns: UAN validity status, associated details

Primary use case: Quick validation before running the full employment history lookup. Filters out fake or inactive UAN numbers.

5. Name Match API

Cross-references names across multiple documents and database records to catch identity discrepancies.

Input: Name strings from different sources
Returns: Match confidence score, variation analysis

Primary use case: Verify that the name on the resume, PAN card, Aadhaar card, and EPFO records all belong to the same person. Catches identity fraud where candidates use another person's employment history.

Building an Employment Verification Workflow in DocuExprt

DocuExprt's visual workflow builder lets you create a complete employment verification pipeline using five node types without coding. Here is a production-ready workflow architecture:

Workflow Architecture: Employee Background Verification

Step-by-Step Workflow Setup

Step 1: Configure Input Node

Set up the Input node to accept candidate data from multiple sources:

• File upload: Resume/CV in PDF, image, or scanned document format
• Form fields: PAN number, UAN number (optional), Aadhaar number (optional)
• Bulk upload: CSV file with multiple candidate records for batch processing
• API trigger: Incoming webhook from your ATS (Applicant Tracking System)

Step 2: Configure Processing Nodes

Add four processing nodes in parallel:

1. AI Document Extraction — DocuExprt's AI extracts candidate name, claimed employers, job titles, tenure dates, and education from the uploaded resume. Works with 20+ languages including Hindi, Telugu, Tamil, and Gujarati.
2. UAN-To-Employment-History API — Fetches the complete EPFO employment history using the candidate's UAN number.
3. PAN-To-Employment-Status API — Checks current employment status and TDS history via the PAN number.
4. Name Match — Cross-references the candidate name from the resume against names in EPFO and PAN records.

Step 3: Configure Conditional Node

The Conditional node is where DocuExprt's agentic AI makes autonomous decisions:

• IF resume claims match EPFO records (employer names, dates within ±30 days) → Route to "Verified" output
• IF minor discrepancies exist (date differences of 30-90 days, minor name variations) → Route to "Review Required" output
• IF major discrepancies exist (missing employers, fabricated tenure, identity mismatch) → Route to "Failed" output with flagged issues
• IF PAN-To-Employment-Status shows active employment elsewhere → Flag "Moonlighting Detected"

Step 4: Configure Output Node

Generate structured verification reports:

• PDF verification report with pass/fail/flag status for each check
• Discrepancy summary highlighting specific mismatches between resume and records
• Compliance audit trail with timestamps, data sources, and API response logs
• Integration output — push results back to your HRMS or ATS via webhook

Step 5: Configure Evaluation Node

Set confidence scoring thresholds:

• High confidence (>95%): Auto-approve, no human review needed
• Medium confidence (70-95%): Route to HR team for manual review with pre-populated discrepancy notes
• Low confidence (<70%): Auto-reject with detailed reason codes

Industry Use Cases

BFSI Employee Onboarding Workflow

The challenge: RBI and SEBI mandate background verification for all employees with financial responsibility. Banks and NBFCs processing 100+ new hires per quarter need verification that is both thorough and fast.

The workflow:

1. New hire submits resume + PAN + UAN via the HRMS integration
2. DocuExprt extracts claimed experience and runs parallel API checks
3. Employment history is cross-verified against EPFO records
4. Active employment status is checked to ensure the candidate has resigned from their previous role
5. Verification report is generated with compliance-ready audit trail

The result: Verification turnaround drops from 7-14 days to under 2 minutes. Compliance documentation is auto-generated for regulatory audits. HR teams process 100+ verifications per day instead of per month.

IT/ITES Mass Hiring Workflow

The challenge: Large IT companies process hundreds of candidates per week during campus recruitment drives and lateral hiring cycles. Manual verification at this scale either becomes the hiring bottleneck or gets skipped.

The workflow:

1. Batch upload candidate CSV from ATS (500+ candidates)
2. DocuExprt processes all candidates in parallel using bulk API calls
3. Candidates are auto-sorted into Verified / Review / Failed categories
4. HR team only manually reviews the 10-15% flagged candidates
5. Results are pushed back to ATS with verification status

The result: 500 candidate verifications that would take a 5-person team 2 weeks complete in under 4 hours. Moonlighting detection catches dual-employment cases that interviews never surface.

Government & Defence Contractors Workflow

The challenge: Security clearance requires complete employment history cross-verification for 10+ year periods. Every gap must be accounted for. Audit trails must be tamper-proof.

The workflow:

1. Extended employment history pulled for the full EPFO tenure
2. Every employer in the candidate's history is verified against EPFO establishment records
3. Gaps between employments are flagged for follow-up
4. All verification data is stored with immutable audit logs
5. Role-based access control ensures only authorized personnel view sensitive records

The result: Complete 10-year employment history verified and documented in minutes. Audit-ready reports satisfy defense procurement compliance requirements.

Background Verification Companies Workflow

The challenge: BGV companies are intermediaries that need to process verifications at scale for their enterprise clients. They need API-first architecture, white-label capabilities, and token-based pricing.

The workflow:

1. Client submits verification requests via API
2. DocuExprt processes UAN, PAN, and Aadhaar lookups
3. Results are returned via webhook or API polling
4. Token-based pricing means BGV companies pay per verification, not per seat

The result: BGV companies reduce per-verification costs by 60-80% while delivering results in seconds instead of days. API-first architecture means zero manual intervention for standard checks.

Integration Guide

REST API Endpoints

DocuExprt's employment verification APIs follow standard REST conventions with JSON request/response formats:

Authentication: API key-based authentication with workspace-level isolation

Available Endpoints

Illustrative API Request (UAN-To-Employment-History)

The examples below illustrate a possible integration. Confirm the current endpoint, authentication, request fields and response schema with DocuExprt before implementation. They are not a guarantee of fields returned for every candidate.

{
  "uan_number": "1001XXXXXXXX",
  "consent": "Y",
  "reason": "employment_verification"
}

Illustrative API Response

{
  "status": "success",
  "data": {
    "employee_name": "Rajesh Kumar",
    "uan": "1001XXXXXXXX",
    "employment_history": [
      {
        "employer": "ABC Technologies Pvt Ltd",
        "establishment_id": "DLCPM0012345",
        "member_id": "PY/DLH/0012345/001/0001234",
        "date_of_joining": "2019-06-15",
        "date_of_exit": "2022-03-31",
        "exit_reason": "resignation"
      },
      {
        "employer": "XYZ Financial Services Ltd",
        "establishment_id": "MHBAN0067890",
        "member_id": "PY/MH/0067890/001/0005678",
        "date_of_joining": "2022-04-18",
        "date_of_exit": null,
        "exit_reason": null
      }
    ],
    "total_employers": 2,
    "pf_filing_status": "active"
  },
  "request_id": "req_abc123xyz",
  "timestamp": "2026-03-05T10:30:00Z"
}

Integration Options

• Direct API calls — Use from any language/framework with HTTP support
• Webhook callbacks — Register webhooks for async processing of bulk requests
• No-code workflow builder — Build complete verification pipelines without writing code
• Cloud storage integration — Input from and output to Amazon S3, Azure Blob, GCP, or local folders
• HRMS/ATS connectors — Push/pull data from your existing HR systems

Pricing Model

DocuExprt uses token-based pay-per-document pricing. Each API call consumes tokens based on the complexity of the verification:

• No monthly minimums or seat-based licensing
• Volume discounts for enterprise accounts
• Free trial tokens available for testing