The Flagged Employment Verification, Two Mismatches Carried to Clearance

This teardown is for a candidate whose background check came back flagged because the title and dates verified for one past job don't match the resume, and who needs it cleared before the offer is pulled. I follow one composite case all the way from the status label to a cleared report. It has two flags on one line: an HR job code standing in for the working title, and an end date cut short by a corporate spin-off. Work through it with your own report open, and by the end each flag will be sorted, the right response will have gone to the right party, and every deadline will be written down.

The worked case: one past job, two flags

The case is a composite. It has one candidate, one past employer, and one report line with two flags, and both flags follow common patterns. The company names and codes are placeholders. The order of events, the clocks, and the decisions are the ones you will face.

What the resume said. Senior Data Analyst at Parentco, from her start month to the month she resigned.

What the report said.

• Employer: Parentco, verified.
• Title: "ANL-III", flagged Discrepancy.
• End date: the month Parentco spun its analytics unit off into a separate company, Newco. Flagged Discrepancy, and several months earlier than her resignation.

What actually happened. Her offer letter, her email signature, and every performance review called her Senior Data Analyst. Parentco's HR system stored only the job code. When the unit became Newco, she moved onto Newco's payroll with the same desk and the same manager, and it was Newco she eventually resigned from. Her resume listed one company name for the whole stretch because everyone inside used that name.

The pressure. She had a conditional offer, a start date three weeks out, and a pre-adverse notice that the recruiter emailed on a Monday. I call that Monday Day 0.

Each section below makes one decision in this case and then gives the general rule, so you can apply it to your own flagged line.

What does the status label on a flagged line mean?

A "Discrepancy" label means the screener reached a source and the title, the dates, or both differ from what you entered. "Unable to Verify" means the screener could not complete verification through its standard channels. It is not a finding that you never worked there.

Screening companies do not share a standard set of labels, and nothing beyond practitioner write-ups documents one. Here is what the recruiter-side write-ups agree on:

• Discrepancy. What it proves: your employment was confirmed and one field differs. When it misleads: when the source field holds something other than a title, such as an internal job code or a "Not Applicable" placeholder, and the screener compared the text character for character. In one documented case, an exchange title of "Not Applicable" was treated as a discrepancy against the candidate's real title.
• Unable to Verify. What it proves: the screener's normal channel failed, and nothing more. Failure rates differ a lot between screeners. One screener's own write-up puts best-in-class unable-to-verify rates under 10% and says many screeners run above 20%.
• Overall labels such as "Decisional", or a "consider" status. What it proves: someone at the employer now has to make a decision. One recruiter-side source says a one-month date gap usually shows up as Discrepancy or Decisional, not as a rejection.

The label on the line is not the employer's decision. Ask the recruiter for the adjudication status, meaning where the employer's own review of the report stands.

The case. Both fields were marked Discrepancy, which is the better of the two labels. The screener had confirmed she worked at Parentco and had found a record to compare against. Her first wrong turn came within the hour, when she drafted a reply to the recruiter that said "The report is wrong." It wasn't wrong. It correctly showed what a record held. Calling the report wrong would have committed her to proving an error that did not exist. She deleted that draft and sent two lines instead: an acknowledgment, and a request for the adjudication status and the notice date in writing.

How long do I have to respond to a pre-adverse action notice?

Before acting on the report, the employer must give you a copy of it and a written summary of your rights under the FCRA (the federal Fair Credit Reporting Act). The statute does not set a number of days. FTC staff called five business days "reasonable" in the Weisberg staff opinion letter of June 27, 1997. A dispute you file with the screening company runs on a separate clock: 30 days from when the screener receives it, which can be extended by up to 15 more.

Three things this table does not settle:

• When the pre-adverse clock starts. The Weisberg letter counts from the date of the notice. At least one screening vendor advises employers to count from when the candidate receives it. You won't know which your employer uses unless you ask.
• Whether any extension applies to you. The California, LA County, San Diego County, and New York City extra days all come from fair-chance laws, which are triggered by criminal history. California's rule that an emailed notice counts as received two business days after sending comes from the same body of rules. LA County's presumption that a final notice sent more than 30 calendar days after a timely response is untimely is also a criminal-history rule. Nothing public establishes that any of these apply to a flag that only concerns employment verification.
• State reinvestigation variants. Maine is shorter, at 21 calendar days. Vermont and Colorado set 30 business days, which is longer in calendar terms, and Massachusetts consumer notices also say 30 business days. Check your own state's statute if the difference matters.

The case. The notice was emailed on Monday, Day 0. Counting from the notice date, five business days ended the following Monday. Counting from receipt might have pushed it later, but she planned to the earlier date. She filed the screener dispute on Tuesday. If the screener logged it as received on Wednesday, the 30 days ended after her start date, and an extension could add 15 more. The numbers showed that the dispute could not finish before the employer was allowed to decide. So the recruiter packet had to save the offer, and the dispute's job was to fix the record.

The dispute clock runs about six times longer than the response window, and no federal rule I found makes the employer wait.

Where did the screener get the title and dates?

Many screeners read an employer data exchange instead of calling HR. An employer data exchange is a database that reports whatever the employer's payroll or HR system sent it. The Work Number is one, and it offers consumers a free Employment Data Report that lists the employment data participating employers have sent and every verifier that requested your data in the past 24 months.

Pull the report online through The Work Number's employee portal or by phone at 866-604-6570. Then read three things:

1. The entities. Which employers hold records on you, and under which legal names.
2. The flagged fields. The exact title and date values for the flagged job, character for character.
3. The verifier list. Whether the screener, or the employer that ordered the check, appears on it.

What the verifier list proves: that a pull happened. What it doesn't prove: which fields the screener used. How HR system fields map onto the exchange's "title" field is not published. If the screener is missing from the list, it got the data from somewhere else, such as a direct call or another database. In that case the Employment Data Report doesn't explain your line, and you need to ask the screener what its source was.

The case. She pulled the report online on the evening of Day 0. The Parentco record had the job code in the title field and the spin-off month as the end date. There was no Newco record at all, and the screener's request was on the verifier list. That told her three things. The screener had read the exchange. The exchange accurately reflected Parentco's HR system. And her Newco months had never been verified, because there was no record where the screener looked.

Is the mismatch a source error, a resume error, or a structural mismatch?

Every flagged field is one of three types, and the type decides who you contact. A source error means the record is wrong. A resume error means your line is wrong. A structural mismatch means two accurate records describe the same job differently, because of an internal job code, an acquisition, a spin-off, or an agency payroll.

How each type misleads you. A structural mismatch looks like an error until you see the system field behind it. A resume error looks structural when you want it to be. The test is whether the record would still be right if you had been the one maintaining it. If you would have entered the same value, the record is accurate and the disagreement is structural or yours.

The case.

• Title flag: structural (job code). The exchange accurately stores what Parentco's HR system stores. A dispute would ask the screener to "correct" an accurate record, so the fix is an explanation in the packet.
• End-date flag: structural (spin-off), with a resume part. The Parentco end date is correct. The Newco months were never checked. The resume used one employer name for two legal entities, which is a resume problem she owns.

Her second wrong turn was a half-finished exchange dispute form asking to extend the Parentco end date. Submitted, it would have asked the exchange to make an accurate record wrong. She stopped and rewrote the resume line to show both entities.

If you keep your history in Refolk, this correction lasts. Refolk writes the resume from your own records, so the corrected line (Parentco, then Newco after the spin-off, with the HR title noted) becomes the default in every version it tailors from then on. You don't have to remember to fix it each time.

What evidence settles each flag, and who reads it?

No screening company publishes which documents it accepts for which field, so ask the screener about each field before you send anything. Two things are documented publicly. A W-2 helps verify work history, but it carries no job title. And in one documented case, a signed offer letter was rejected and a W-2 or IRS transcript was demanded instead.

What each document can and cannot settle:

• Dates and entity. W-2s for each year from each entity, plus pay stubs. These are strong evidence for what they actually show: who paid you, and in which years.
• Title. Nothing public says which document a screener will accept for a title. Your options are an HR letter that maps the code to the working title, the offer letter, and a performance review. Expect to be asked for something else, and ask in advance.
• Spin-off or acquisition. Nothing public says whether screeners accept corporate notices. Send the public announcement or the employee notice to the recruiter as context, not as verification.

The person who reads your dispute is usually a verification specialist, and in Refolk's index of professional profiles that workforce is small and concentrated.

The US count is 1.80 times the India count, and HR and staffing account for 12.2% of the US total. The US all-industries figure is noisy: its sample includes chip-verification engineers and unrelated titles. The HR and staffing slice is the cleaner picture of who handles employment checks.

What this means for your packet: a handful of desks set the evidence norms, and the person reading your file probably handles many like it. Take one field at a time, name one document per field, and keep it to a page. The limit of this evidence is that it comes from a 25-profile sample. It shows how concentrated the work is, but it is not a census.

Subject: Background check - response to pre-adverse notice dated [date]

Hi [Name],

Thank you for sending the report. I am responding within the window. Could you confirm in writing the date your team counts the notice from, and the current adjudication status?

The report flags two fields on my [Employer] line. Both reflect how the records are structured rather than an inaccuracy, and I have attached documents for each.

1. Title. The report shows "[HR code]", which is [Employer]'s internal HR job code. My working title was [Title], as shown in the attached [document].

2. End date. The report ends my employment at [date], when [Employer] spun off [unit] into [New entity]. I continued in the same role at [New entity] until [date]. Attached: W-2s from both entities and the spin-off announcement.

I have asked [Screener] in writing to verify the [New entity] period and will forward its response when I receive it. If a different document would help your team, tell me which one and I will get it.

Corrected line for your file:
[New entity] (spun off from [Employer]), [Title], [start] to [end]
[Employer], [Title] (HR job code [code]), [start] to [spin-off date]

[Your name]

To: [Screener] consumer disputes
Re: Dispute of report [file number], [your full name], ordered by [employer]

I dispute the accuracy and completeness of the following item under 15 U.S.C. 1681i.

Item: Employment, [Employer]
Field disputed: [End date / Title / Employer name]
What the report states: [exact text from the report]
Why it is inaccurate or incomplete: [one sentence, e.g. "Employment continued at [New entity], formed when [Employer] spun off [unit], from [date] to [date]. That period was not verified."]
What I ask you to do: [verify the [New entity] period with its payroll or HR / correct the field to ...]
Enclosed: [list of documents]

Please send the results to me and to [employer], and please describe the method of verification used.

[Name, phone, email, date]

Step-by-step: from flagged line to cleared report

Go through these nine steps in order. Steps 5 and 6 can be swapped, and some guides put the dispute first, but both must go out before the pre-adverse deadline.

The case, by day.

• Day 0. Steps 1 to 3: labels read, deadline written, Employment Data Report pulled.
• Day 1. Step 4: both flags classified as structural. She emailed the screener asking which document it accepts for a title and which for dates and entity, and drafted the packet.
• Days 1 to 2. Step 6: dispute filed asking the screener to verify the Newco period. Step 5: packet sent, and the recruiter acknowledged it the same day.
• Step 7 skipped. The exchange record was accurate and there was no Newco record to correct.
• Clearance. The employer decided on the strength of the packet. The reissued report added the verified Newco period, and the title line kept the job code next to her explanation on file. The packet saved the offer, and the corrected report stops the next check from flagging the same line.

How does a flagged verification response go wrong?

Most failed responses fail in one of eight ways, and most of them come from treating the report as the enemy instead of as a record with a known source. Each item below says what the mistake looks like and the check that catches it.

1. Reading the label as a rejection. What it looks like: a panicked reply, or no reply at all. "Unable to Verify" is not a finding that you made the job up. Check: ask for the adjudication status, not just the line label.
2. Counting from the wrong start. What it looks like: you count from when you opened the email while the employer counts from when it sent it, and you miss the deadline by a day. Check: get the notice date confirmed in writing.
3. Assuming a fair-chance extension applies. This is the main false positive. The California, LA County, and San Diego County extensions are criminal-history rules. Assuming they extend a flag that only concerns employment can cost you the whole window. Check: plan to five business days unless the employer grants more in writing.
4. Sending the wrong document. What it looks like: you send an offer letter and get asked for a W-2, which carries no title. Check: ask the screener which document it accepts for each field before you send anything.
5. Disputing a structural mismatch as an error. What it looks like: a dispute asking the exchange to change an accurate job code. It goes nowhere and uses up time you don't have. Check: if you would have entered the same value yourself, explain it instead.
6. Disputing only with the screener. What it looks like: the report is fixed this time, but the exchange record stays as it was and the next check flags the same line again. Check: the verifier list in your Employment Data Report, and whether the exchange was the source.
7. Entering an employer name that differs from the payroll entity. What it looks like: an Unable to Verify on a job you plainly held, because you entered the client's name while an agency paid you, or the brand name instead of the legal entity. Check: match the employer name you entered to the name on your W-2.
8. Ignoring an informal deadline. In one public account, a recruiter told a candidate to resolve a date flag "in 2 days" or risk having the offer rescinded. That is shorter than the federal guidance, but arguing the point loses time. Check: send the packet inside the informal deadline anyway, and ask for the formal notice date in writing.

The opposite mistake is also costly. Screening data is wrong often enough that disputes change records.

How do I close the dispute out and keep the record clean?

A dispute is closed when the employer has a corrected report or your statement of dispute is on file, and the exchange record no longer shows the error. Until then, keep the clocks in your diary and keep every receipt.

Tracking the dispute. The screener has 30 days from receiving your dispute, plus up to 15 if you send new information during that period. It must notify the furnisher within 5 business days and send you results within 5 business days of finishing. If you ask how it verified the item, it must describe the method within 15 days of your request. A furnisher is whoever supplied the data: the exchange or the former employer.

If the employer decides before the dispute closes. I found no federal rule requiring the employer to hold its decision while a reinvestigation runs, so this is not established. A final adverse action notice must include:

• the screener's name, address, and toll-free phone number;
• a statement that the screener did not make the decision;
• your right to a free copy of the report within 60 days;
• your right to dispute.

If the reinvestigation doesn't resolve it. You can file a brief statement explaining the nature of the dispute, and it stays with your file. If the screener doesn't correct a genuine error, the CFPB says you can complain to the CFPB or the FTC. The CFPB complaint portal is at consumerfinance.gov/complaint. Its publication "A Closer Look: Background screening reports" explains the process.

Keeping it current.

• Re-pull your Employment Data Report after any exchange dispute closes and confirm the change is there.
• Keep the packet, receipts, and corrected report in one folder. The next employer's check will read the same sources.
• Use the corrected line everywhere. If Refolk holds your history, every tailored resume and cover letter it drafts already carries the entity split and the HR title note, so the next screener compares two records that agree.