What happens when a background check goes wrong

Background Check

Most conversations about background screening focus on the upside:faster hiring, better candidates, less admin. That’s the easy resell.. The harder question is what happens when a check fails, and why it so often catches people off guard. Checks can fail. And when they do, the cost rarely lands on the person who ran them. It lands on the business, sometimes years later in a stressful audit, a headline, or a hire who turned out to be someone else entirely.  

Screening is one of those processes nobody examines closely until something goes wrong, and by then it’s too late. This isn’t an argument for fear. It’s an argument for knowing where the gaps are before you need to find out the hard way. Here are four of the most common ways background checks go wrong, what each one actually costs, and what separates a process that catches the problem from one that waves it through.

1. You hired someone who was never really there

A standard background check confirms that a name has the employment, education and criminal history attached to it. What it doesn’t always confirm is that the person sitting in the interview actually owns that name. That gap is where identity fraud lives, and it’s a growing problem as the tools to exploit it become cheaper and easier to access. Stolen identity documents can now easily pass basic document validation. Remote hiring has removed the in-person gut feel check that used to catch the obvious cases. And generative AI has lowered the bar dramatically. Gartner predicts that by 2028, one in four candidate profiles worldwide will be fake, and around 17 per cent of hiring managers already report running into a candidate using deepfake technology. At the extreme end, there are documented cases of organised fraud schemes where operatives pose as remote workers, drawing salaries while sitting inside company systems with legitimate access credentials.

The consequence here isn’t just a bad hire. It’s granting a fabricated person access to your systems, your data, and your customers. The financial exposure runs from data theft to money laundering, and the reputational damage of announcing that one of your employees never existed is hard to recover from. We’ve talked about  synthetic candidate fraud before and the takeaway is the same: a single source of truth is no longer enough.

Preventing this means layering verification rather than relying on one document. Biometric checks confirm the live human matches their ID. Liveness detection during video steps flags deepfake artefacts. IP, VPN and geolocation signals catch a candidate who claims to be in Sydney but is answering from somewhere else entirely. A screening process built on multiple verification sources rather than a single uploaded document is the practical defence here.

2. The check came back clean when it shouldn’t have

The second failure is subtler and, in some ways, even more dangerous. In some cases, the check runs. It comes back clear. And it’s wrong. A real criminal record, a sanctions match or a professional disqualification existed, but your screening didn’t surface it.

This usually traces back to narrow coverage. A search run in one jurisdiction misses a record held in another. Name-only matching misses results filed under an alias or a former name. Stale or thin data sources miss recent entries. A watch list that covers some sanctions regimes but not others leaves a gap exactly where a determined bad actor will exploit it. The candidate looks clean because the search wasn’t wide enough to see otherwise.

The cost isn't just legal exposure, it's whatever harm the person goes on to cause..If a court later finds the record was discoverable through reasonable screening, the fact that your check missed it offers little protection. 

In sectors that carry a duty of care, such as aged care, healthcare and any role working with children or vulnerable people, a missed disqualification isn’t just a liability issue. It’s a safety failure that can end careers and hurt people, and the organisation usually wears the consequences publicly.

The defence for this is breadth and rigour. Checks that draw on a wide data network, with verifications available across more than 190 countries and over 4,000 data sources, are far harder to slip past than a single local search. Alias and former-name matching, proper AML and sanctions watch list screening, and current data sources all narrow the gap. 

When you’re evaluating a provider, the question isn’t “do you check criminal history?” It’s “how widely do you search, what sources do you draw on, and how do you handle aliases and former names?” 

3. The check was fine. Two years ago.

Lots of organisations screen thoroughly on day one, then move on. The trouble is that credentials have expiry dates. A visa lapses, a Working With Children Check runs out, a health practitioner's AHPRA registration falls due for renewal, and screening once captures none of that.

This is the point-in-time screening trap. The check was accurate the day it ran, and potentially meaningless six months later, because nothing was watching the gap between hire and today. The employee carries on in the role. Payroll keeps paying. And on paper, you’re now employing someone without valid work rights, or letting an unregistered practitioner treat patients, or keeping someone on a child-facing roster with an expired clearance.

The damage tends to arrive all at once, usually on audit day, when the lapse is discovered alongside the uncomfortable fact that it has been live for months. Immigration penalties for employing someone without work rights are real and steep, and they can attach to the employer regardless of whether the oversight was deliberate. The regulatory and safety exposure in licensed sectors is worse. None of it is malicious. It’s simply what happens when screening is treated as a one-off event instead of an ongoing state.

The shift that fixes this is moving from single checks to continuous monitoring. Ongoing compliance monitoring keeps visa status, work rights, licences and certifications under continuous watch, with real-time alerts the moment something changes or approaches expiry, and scheduled re-screening for higher-risk roles. The goal is to be audit-ready every day of the year, not scrambling the week a regulator calls.

4. The regulator asked for proof and you couldn’t find it

The last failure is not about a check being wrong. It’s about not being able to prove a check was ever done properly. A regulator, an auditor or a court can potentially ask you to demonstrate that you lawfully and thoroughly screened a particular person. But when you go looking, the evidence is scattered across inboxes, spreadsheets, and someone’s memory of a phone call. You can’t produce a clean, time-stamped trail.

In many cases the breach isn’t the screening itself, it’s the failure to evidence it. Consent given verbally but never logged. Personal information kept longer than it should have been, or accessible to people who had no business seeing it. 

Under the Australian Privacy Act, as amended in late 2024, the penalties for getting this wrong are tiered: up to $3.3 million for a body corporate for a mid-tier interference, rising to a statutory maximum of $50 million, three times the benefit gained, or 30 per cent of turnover for a serious interference. These aren't theoretical figures either, Australian Clinical Labs was ordered to pay $5.8 million over a single data breach.

The good news is that this is mostly a discipline problem, and a good platform enforces that discipline for you. Consent captured before each check and stored against it. Every action logged with a timestamp and a user. Retention rules that delete personal information on schedule and role-based access so data isn’t floating around the business. Certifications such as ISO 27001 and SOC 2, encrypted storage, and one source of truth instead of a filing system held together by goodwill are crucial. When the request comes, you can produce the record in minutes rather than discovering you never kept it.

The thread running through all four

Each of these failures has the same shape. A process that's single-source where it should be layered, point-in-time where it should be continuous,undocumented where it should be evidenced. A strong screening process is the opposite on all three counts: it verifies identity from more than one angle, it keeps watching after the hire, and it can prove every step on demand.

That is the real question to put to any screening provider. Not just whether they run the checks, but whether their process is built to catch what a shallow one misses, and whether they can prove it did. The difference between the two only shows up on the worst day, which is exactly why it’s worth asking before you need to find out. . Frequently asked questions

What happens if a background check misses something?

A missed finding can expose your business to negligent hiring liability, along with any harm the person goes on to cause in the role. The usual culprit is narrow coverage: a single-jurisdiction search, name-only matching that ignores aliases, or thin data sources. Broader, multi-source screening with alias matching and current data sources is what reduces the odds of something slipping through.

How do you prevent identity fraud in hiring?

You verify identity from more than one angle rather than trusting a single document. That means biometric checks that confirm the live person matches their ID, liveness detection to flag deepfakes during video steps, and IP or location signals that catch a candidate who is not where they claim to be. Layered verification is the practical defence, since stolen documents can pass a basic check on their own.

What is the cost of a missed adverse finding?

It's rarely just the cost of re-hiring. Depending on the role, it can include negligent hiring claims, regulatory penalties in licensed sectors, and the direct harm caused by someone who should never have been in the position. In duty-of-care settings like aged care, healthcare or work with children, a single miss can carry consequences that no recruitment saving comes close to offsetting.

Can a background check expire?

The check itself is a snapshot, accurate on the day it runs. But credentials it confirms can absolutely expire. Visas, work rights, Working With Children Checks and professional registrations all have end dates. If nobody is monitoring those dates, a person who was fully compliant at hire can be non-compliant months later without anyone noticing. Continuous monitoring with expiry alerts is what closes that gap.

How long should background check records be kept?

Long enough to demonstrate compliance, and no longer than the law requires. Retention periods vary by jurisdiction and check type, so the practical answer is to set retention rules deliberately and enforce them automatically, rather than keeping everything forever or deleting on an ad hoc basis. Under the Australian Privacy Act, holding personal information longer than necessary is itself a compliance risk, so configurable retention with automatic deletion is the safer setup.

How do you build an audit trail for background checks?

Capture consent before each check and store it against that check, log every action with a timestamp and a user, and keep results in one system rather than scattered across inboxes and spreadsheets. Role-based access and configurable retention round it out. A platform that handles this automatically means an audit becomes a quick export, not a frantic search through old emails.

What is the most common background check failure?

In practice, it's rarely a dramatic missed criminal record. The more common failures are simpler, like a check that was done correctly at hire and never revisited, so an expired visa or registration goes unnoticed until an audit surfaces it. It's also the most preventable, because ongoing monitoring turns a one-off check into a continuous compliance state.