Employer Intelligence Registry
Legal name, aliases, registration identifiers where relevant, incorporation/status history, addresses and corporate relationships.
Experience · Employer · History · Official Channels
Employment verification is source-heavy by design. DCS Bonafide resolves the legal employer identity, trusted HR route, corporate history and claimed chronology before document forensics are treated as supporting evidence.

Each capability is a visible part of the verification workflow—not a hidden AI score.
Legal name, aliases, registration identifiers where relevant, incorporation/status history, addresses and corporate relationships.
Current/historical domains, careers domains, HR verification emails, official phones and verification portals with source class.
Joining/leaving dates, designations, overlaps, gaps, role progression and employer-name/status history.
Parent/subsidiary relationships, mergers, acquisitions, rebrands and defunct/struck-off context.
Inbound header evidence, domain match, DKIM/SPF/DMARC support, Reply-To/Return-Path and registry-derived callbacks.
Experience, relieving, offer and appointment letters can provide supporting evidence without outweighing official-source confirmation.
The system distinguishes plausible consulting, notice periods, part-time work and group-company transfers from unresolved chronology conflicts. Company-existence evidence confirms the organization, but does not by itself prove an individual was employed there.
Official HR route independently resolved
Two-month overlap → clarification signal, not fraud
Role progression and entity history consistent
Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.
The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.
Independent experience verification before hiring or onboarding
Source routing and chronology intelligence at scale
Employment evidence inside admissions or mobility cases
Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.