Your company gains
- A negotiated share of verifier revenue
- No platform fee
- Less manual verification work
- A documented request and release trail
- A configurable implementation model
MyEmployment connects to your existing HRIS or payroll environment. Credentialed verifiers pay for completed employment and income verifications. Employees are notified when a request arrives, see who is asking and why, and have the opportunity to approve or deny. Your company receives a negotiated share of the verifier fee—up to $500,000 a year.
Built by operators with 30 years in employment verification and background screening.
The employer should not have to choose between financial value and employee protection. The model is designed to deliver both.
A third-party service answers requests using your workforce data and charges verifiers for the response. In many arrangements, the employer receives none of that transaction revenue.
Your HR team answers calls, forms, and requests manually. The work consumes staff time, but no verifier-fee revenue is created or returned to the company.
A live API or scheduled feed connects MyEmployment to your designated HRIS or payroll source. Your existing verification process remains active until testing and approval are complete.
A credentialed verifier submits an employment or income verification request with a documented purpose.
The employee sees who is asking and why and has the opportunity to approve or deny.
Eligible requests are answered from the employer's designated data source, the outcome is logged, and the negotiated revenue share is recorded.
A negotiated share of completed-verification revenue, paid to the employer while the organization remains on the platform.
Actual revenue depends on workforce size, verification volume, verifier mix, pricing, and negotiated terms. During the introductory call, MyEmployment will model the opportunity using your organization's numbers.
1 REQUEST WAITING
Wants to verify your employment and income for a home loan.
Employees are notified when a verification request arrives. They see the requester, the stated purpose, and the information being requested before an eligible release is processed.
The eligible verification proceeds.
The request stops and nothing is released.
The request follows employer-defined rules for credentialed verifiers and documented permissible purposes.
Data is queried from your designated HRIS or payroll source when an eligible request is processed. MyEmployment retains the request and audit record rather than a standing workforce copy.
A workforce file is delivered on an agreed schedule, with data location, access, and retention defined by contract.
Robert Mather founded and built a national employment verification and background screening company before exiting in 2022 to build MyEmployment. He has worked in the category for 30 years and has been a licensed private investigator since 1993.
His experience operating employment verification services—and challenging opaque incumbent practices—shaped MyEmployment's employee-notification, data-minimization, and revenue-sharing model.
David owns delivery and day-to-day operations, including implementation, HRIS and payroll integration, verifier support, and employee exceptions.
After the contract is signed, employers have a named operator with direct responsibility—not an anonymous support queue.
No. There is no employer platform fee or cost to switch. Verifiers pay for completed verifications, and the employer receives a negotiated share of the fee.
Terms are negotiated by relationship and informed by workforce size, verification volume, verifier mix, and pricing. MyEmployment models the opportunity using the employer's actual operating assumptions.
It remains active until MyEmployment is configured, tested, and approved for production. The transition is coordinated with the employer; nothing is shut off prematurely.
Participation is optional for current employees. There is no required mass enrollment or broad employee training. Employees can engage when a request arrives or set preferences earlier.
Eligible requests follow employer-defined fallback rules for credentialed verifiers with documented permissible purposes. The timing, request category, authorization handling, and exceptions are configured during implementation.
Former-employee workflows are configured with the employer, including how notices are delivered, which records are available, applicable waiting periods, and how authorized requests are handled.
MyEmployment credentials verifiers, requires a documented permissible purpose, logs each request and outcome, and gives employees notice and the opportunity to approve or deny at the time of the request. Specific workflows, fallback rules, and data-handling requirements are configured with the employer and reviewed as part of implementation.
Access is limited to credentialed verifiers that have passed the platform's vetting process and provide a documented permissible purpose for the request.
With a live API, data is queried from the employer's designated source at the time an eligible request is processed. With a scheduled feed, data location, access, and retention are defined by contract.
The SOC 2 Type 2 report, available under NDA, the proposed integration architecture, access controls, audit logging, data flow, retention terms, and the verifier credentialing process.
Yes. A white-label option is available for employers that want the employee and verifier experience presented under their own brand. Scope and requirements are discussed during implementation planning.
In 15 minutes, we will estimate the annual revenue opportunity, explain the employee experience, and map the likely integration and approval path for your organization.
Get a tailored revenue estimate