Pay stubs are easy to forge, and the highest-risk applications are often the ones that look the cleanest. A single “verified” PDF can be generated in minutes, and a polished format tends to disarm judgment right when the decision has the most downside.
In Richmond City and the surrounding counties, screening mistakes show up later as nonpayment, mid-lease conflict, and avoidable legal exposure. The goal is not to interrogate applicants. The goal is to verify the income claim using consistent, defensible standards that do not drift between people or properties.
A screening policy that survives disputes usually separates two things: the objective income requirement and the objective proof requirement. Screening decision tradeoffs stay stable when every application is evaluated on the same rules. Verification recordkeeping standards matter because documentation is what remains after the phone calls, the impressions, and the pressure to “just approve it.
Table Of Contents
Why fake pay stubs succeed
What “verification” actually means
Red flags that justify deeper checks
A defensible proof standard for W-2 employees
A defensible proof standard for variable and self-employed income
Two scenarios: clean file and messy file
Edge cases that commonly break weak policies
Risk and liability traps to avoid
Time and cost drivers that change the process
Common mistakes that create disputes
Simple decision path
FAQ
Conclusion
Next Step
Key Takeaways
A pay stub is not proof of income on its own; proof is the cross-check between the stub, the deposit trail, and an independent verification of employment.
Any “extra scrutiny” trigger must be written as objective criteria, not a gut feeling, and applied the same way in Henrico County, Chesterfield County, Hanover County, and Richmond City.
When a consumer report or a third-party reference check influences a denial or conditional approval, an adverse action notice is required under the FCRA.
A stronger file is often built by allowing multiple acceptable document combinations rather than demanding one perfect document that is easy to fake.
Documentation discipline is a Fair Housing protection tool, not just an operational preference.
Why Fake Pay Stubs Succeed
Fake stubs work for three reasons.
- They exploit speed. Most screening failures are time failures. When a vacancy, a showing calendar, and a move-in date compress the decision window, the process shifts from verification to plausibility.
- They exploit one-document policies. If the policy treats “two recent pay stubs” as the whole requirement, an applicant only needs to forge one artifact. A cross-check policy forces consistency across sources.
- They exploit inconsistent enforcement. If one applicant is asked for deposit history and another is not, the file starts to look like discretion. Discretion is where disputes live, even when the decision itself was reasonable.
For those wanting a deeper dive into this topic, RentEngine (a PMI James River partner) recently did an in-depth investigative report on how easy it is to obtain fake pay stubs.
What “Verification” Actually Means
Verification is an evidence test, not a confidence test.
A pay stub answers one question: what the applicant claims the employer paid. Verification answers different questions:
Does the employer exist and match the applicant’s claim?
Does the applicant have a real, ongoing employment relationship?
Do deposits match the claimed net pay and cadence?
Does the income pattern support the rent obligation after accounting for variability?
When verification is defined this way, the process becomes repeatable regardless of property type, HOA pressure, or owner preferences.
Red Flags That Justify Deeper Checks
A policy that “goes deeper” needs triggers that are factual and document-based.
- Formatting anomalies. Fonts changing mid-line, inconsistent spacing, misaligned columns, missing withholding lines, or a “too perfect” layout that looks like a template export rather than a payroll system output.
- Math inconsistencies. Year-to-date totals that do not reconcile with the pay period amount, or taxes that do not scale plausibly with gross pay.
- Employer opacity. Email-only contact, personal (e.g. gmail) addresses, phone numbers that route to generic voicemail, or a company name that does not map cleanly to a real entity.
- Deposit mismatch. Pay stub says biweekly net pay of $2,000, but deposits are irregular, smaller, or from unrelated senders.
- Timing pressure. A move-in date that requires approval within hours, paired with a refusal to provide standard corroborating documents.
A deeper check is not a higher standard. It is the same standard satisfied through more than one independent source.
A Defensible Proof Standard For W-2 Employees
A workable standard for most W-2 wage earners uses corroboration rather than volume.
Core concept. The file is strongest when two independent sources agree: payroll evidence or bank deposit evidence, supported by a basic employer verification.
Acceptable documentation combinations often look like:
Three recent pay stubs plus recent deposit history that shows matching payroll deposits, or
One pay stub plus an employer verification plus deposit history that covers at least one full pay cycle, or
A year-end wage document plus deposits that support current continuity when the job recently changed.
Employer verification should stay narrow. The verification question set that tends to hold up is: position, start date, pay frequency, and whether employment is active. Anything beyond that starts collecting data that is not needed to make the decision.
Recordkeeping constraint. Keeping a copy of the key corroborating documents and a short verification note creates a file that can be defended later without reconstructing memory.
A Defensible Proof Standard For Variable And Self-Employed Income
Variable income is where weak policies either over-deny or over-approve.
Core concept. The relevant question is stability, not the best month. The proof standard shifts from “current pay rate” to “documented inflow trend.”
Acceptable documentation combinations often look like:
Bank deposit history that shows recurring inflows consistent with the stated business activity, plus recent invoices or contracts that show ongoing work, or
A tax-year income document plus current-year deposits showing continuity, or
Platform earnings statements plus deposits when the applicant’s income is primarily gig-based.
Tax transcripts are often mentioned in financial contexts, but they are not simple for housing providers to obtain. The IRS’s transcript processes are designed around taxpayer access and authorized programs such as IVES, and they come with timing and identity controls that do not fit most rental timelines. The practical implication is that a screening policy should not depend on transcript delivery to function.
Two Scenarios: Clean File And Messy File
Scenario 1: The Clean W-2 File That Still Needs Verification
A hospital employee applies for a townhome in Chesterfield County. The stubs look normal. The credit is decent. The rental history is thin because the applicant lived with family.
A verification-first decision uses three checks:
- Deposit match. The bank history shows two biweekly deposits from an employer name that matches the stub, with amounts that align to the net pay.
- Employer confirmation. The employer’s HR line confirms active employment, start date, and pay frequency.
- Policy consistency. The same deposit match and employer confirmation are required for every wage-earner file, even when the stubs “feel” real.
This file usually moves quickly because corroboration is fast when the documents are real.
Scenario 2: The Polished Stub With A Deposit Trail That Does Not Agree
An applicant applies for a single-family home in Henrico County. The pay stubs are unusually polished, show a large salary, and list a small business as employer. The applicant wants a fast decision and offers to pay more upfront.
The deposit history shows cash app transfers, irregular amounts, and no deposits from the employer listed on the stub.
A defensible response is not a subjective judgment about character. It is an objective failure to meet the proof standard.
If a third-party reference check, a credit report, or another consumer report influenced the decision, an adverse action notice obligation may be triggered even when the problem was “income verification,” because the definition of a consumer report can include reference checking services used for employment verification.
Edge Cases That Commonly Break Weak Policies
New job with no stubs yet. Offer letters alone are easy to fabricate. A stronger file uses an offer letter plus an employer verification.
Seasonal work. Seasonal income can be legitimate and still fragile. The decision point is whether the documented off-season income supports the rent, not whether the peak season does.
Commission-heavy roles. Commission stubs can swing. The proof standard should shift to a longer deposit window rather than demanding “higher stubs.”
Multiple income sources. Multiple sources can improve stability, but only if each source is documented and consistent. The mistake is counting a source because it exists, without verifying its continuity.
Applicants with housing assistance. A policy should clearly separate “portion paid by subsidy” from “portion paid by resident,” with documentation that verifies the resident portion using the same proof rules as any other applicant. HUD-regulated units also have a different application fee cap under Virginia law, which is a compliance detail that becomes relevant in mixed portfolios.
Risk And Liability Traps To Avoid
Fair Housing drift. HUD has emphasized that tenant screening practices, including those driven by third-party screening tools and automated recommendations, can create discriminatory effects when criteria are overbroad or not well-justified. The operational takeaway is that every “red flag” trigger should be written as an objective document inconsistency, not a person-based judgment.
Consumer report compliance. When a consumer report influences denial, higher deposit requirements, or the need for a co-signer, the FCRA adverse action notice is part of the decision process, not an optional courtesy. The CFPB describes required elements such as identifying the reporting company and disclosing the applicant’s right to a free copy within 60 days and the right to dispute inaccuracies.
Over-collection of sensitive data. Collecting more documents than necessary increases breach risk without improving decision quality. A narrower, corroboration-based policy can be both stronger and safer.
Inconsistent exceptions. “Normally this would be required, but…” becomes indefensible fast. Exceptions should be defined as alternate document combinations, not case-by-case discretion.
Time And Cost Drivers That Change The Process
Manual verification time. Live employer verification can be fast or it can be days. The policy needs a fallback that does not collapse into guesswork when HR is slow.
Third-party verification services. Outsourcing employment verification can still fall under consumer report rules depending on the provider and the information used. The FTC’s landlord guidance treats certain reference-checking services as consumer reports that trigger adverse action obligations when they influence a denial.
Fraud escalation. The cost is usually not the screening fee. The cost is the eviction timeline, turn costs, and the opportunity cost of a unit tied up in nonpayment. Those costs are similar across Richmond City and the counties, even when rent levels differ.
Common Mistakes That Create Disputes
Mistaking neatness for truth. Clean PDFs are easy. Corroboration is harder to fake.
Treating “extra scrutiny” as a vibe. If the trigger cannot be written as a factual inconsistency, it should not exist.
Relying on screenshots. Screenshots of payroll apps or bank balances are easy to manipulate. Deposit history and bank statements are still forgeable, but cross-checking patterns catches more fraud than a screenshot ever will.
Skipping adverse action compliance. A decision can be substantively correct and still create liability if the required notice was not provided when a consumer report influenced the outcome.
Letting urgency set the standard. A fast move-in request is not proof of ability to pay.
Simple Decision Path
The decision path below is designed to be consistent across property types, including HOA-managed townhomes, older housing stock with higher utility variability, and single-family homes where maintenance costs make nonpayment risk more consequential.
First, define the income rule in writing as a fixed ratio or fixed threshold that does not change by person or by persuasion.
Second, define the proof rule as corroboration, using acceptable document combinations rather than a single required document.
Third, apply objective triggers for deeper verification based on document inconsistencies and deposit mismatches.
Fourth, document the specific reason a file did or did not meet the proof rule, using short, factual notes.
Fifth, when a consumer report influenced an unfavorable decision or a conditional approval, issue the required adverse action notice with the required disclosures.
FAQ
Are pay stubs enough to verify income for a rental application?
A pay stub is evidence of a claim, not proof. A defensible verification standard usually requires corroboration through deposit history and an independent employment verification.
What is the most reliable way to catch fake pay stubs?
Mismatch is the most reliable signal: the pay stub cadence and net pay should align with the deposit trail, and the employer details should map to a real, reachable entity.
Should a landlord call the employer directly?
Employer verification can be part of a strong file, but it should stay narrow and consistent. Confirming active employment, start date, and pay frequency often provides more value than open-ended questioning.
Can a landlord ask for bank statements in Virginia?
Virginia law does not generally prohibit requesting bank documentation as part of screening, but the operational risk is inconsistency and over-collection. A written policy that uses bank documentation as a corroboration tool, applied uniformly, reduces Fair Housing and privacy exposure.
When is an adverse action notice required in tenant screening?
If a consumer report influences an unfavorable decision or less favorable terms, the FCRA requires an adverse action notice. That can include denial, higher deposit, or requiring a co-signer when a credit report, background report, or certain reference-checking reports influenced the outcome.
What must an adverse action notice include?
The CFPB describes required elements such as identifying the screening company and disclosing the applicant’s right to a free copy of the report within 60 days and the right to dispute inaccurate information.
What is the maximum application fee in Virginia?
Virginia law caps the application fee at $50, plus actual out-of-pocket third-party screening costs, with a lower cap for HUD-regulated units.
How does HUD’s tenant screening guidance affect small housing providers?
HUD’s guidance emphasizes that screening policies and tools can create discriminatory effects when criteria are overbroad, opaque, or not tied to legitimate housing interests, including when third-party screening tools or automated systems are involved.
Conclusion
Fake pay stubs are a process problem, not a personality problem. A file becomes defensible when the policy defines proof as corroboration and applies the same document rules regardless of property, county, or applicant narrative.
In the Richmond metro area, the most reliable protection is consistency: fixed criteria, written triggers for deeper verification, and documentation that can be understood months later without relying on memory. When consumer reports influence decisions, adverse action compliance is part of doing the job correctly, not a separate administrative step.
Next Step
A screening standard is only as strong as its repeatability. Screening decision tradeoffs tend to become simpler when the proof rule is defined as corroboration rather than document volume. Verification recordkeeping standards reduce disputes because the file shows what was relied on, what was inconsistent, and why the application did or did not meet the same rules used for every other applicant.
