The Fake Pay Stub Trick That Uses a Real Employer — a Real Job, an Invented History

Most advice about fake pay stubs — ours included — starts with the employer: is the company on the stub a real, registered business? That check catches a lot, because a large share of income fraud is built on invented employers. But there’s a version of the trick that sails straight past it — and past the credit check, the registry lookup, and a phone call to the employer’s real front desk. It doesn’t invent the employer. It borrows a real one.

Anatomy of the trick: real facts, invented history

Here’s the pattern, drawn from a real case we reviewed (details changed and generalized). An applicant genuinely lands a job at a major national retailer — a real offer, a real location, a real hourly rate. The job just hasn’t started yet, or started days ago. That’s a problem for a rental application, which wants to see steady income now. So the applicant builds a pay stub — template sites and design tools make this a ten-minute job — and builds it out of true facts: the real company, the real store address, the exact hourly rate from the offer letter. Then they add the one thing they don’t have: history. A year-to-date total suggesting eight months of steady paychecks that never happened.

Why it beats the checks you’d normally run

Walk through what a careful landlord would do with that stub. Look the company up in the state registry — it’s there, of course; it’s a household name. Search the address — a real location of that business. Check the hourly rate against the industry — plausible, because it’s the real rate. Even call the company through an independently found number and you might get a yes — the person may genuinely be in the system as a new or incoming hire. Every fact you can verify is true. The lie isn’t in any single fact. It’s in the timeline.

The calendar math that catches it

A pay stub’s year-to-date field quietly tells you when the employment started — you just have to ask it. Divide the year-to-date gross by the per-period gross, and you get the number of pay periods worked this year. Then look at the calendar and ask: does that number fit this person’s story?

Worked example. A stub dated mid-August shows $1,400 gross per biweekly period and $23,800 year-to-date. Divide: $23,800 ÷ $1,400 = 17 pay periods. Seventeen biweekly periods is 34 weeks — which means this employment started around the first week of January. Now put that next to the rest of the application: an offer letter dated August 4th, a start date “last month,” a resume showing a different job this spring. If the year-to-date says January and the paper trail says August, one of them is fiction — and the year-to-date total on a home-made stub is the one that’s easy to type and hard to keep consistent.

The pattern behind the pattern: fakes die in the totals

Here’s the deeper lesson from cases like this. People faking a pay stub usually get the per-period lines right — one paycheck is easy to calculate, and the tax rates are one search away. What they botch are the cumulative fields, because those have to stay consistent with the calendar, the tax rates, the hours, and each other, all at once. On a genuine, machine-generated stub they always reconcile. On a fake, they rarely all do:

• Year-to-date taxes as a percentage. Social Security should sit at 6.2% of year-to-date gross and Medicare at 1.45% — the same rates as any single period. On the fake we reviewed, the per-period lines were perfect and the year-to-date columns worked out to over 9% and 2% — impossible numbers a calculator exposes in seconds.
• Year-to-date hours × rate vs year-to-date gross. If the stub shows cumulative hours, multiply them by the hourly rate. If that lands nowhere near the year-to-date gross, the fields were invented separately.
• Taxable wages vs gross. Federal taxable wages lower than gross pay only happens when pre-tax deductions explain the gap. If the stub shows the difference but every pre-tax deduction reads $0.00, the numbers don’t hold together.
• The timeline itself. Year-to-date implies a start date. Offer letters, start dates, and references imply another. They must agree.

What to do about it as a landlord

You don’t need software to run the first pass — you need three minutes and the willingness to do division. Compute the implied pay periods from the year-to-date. Check the year-to-date tax percentages. Ask when the job started, and see whether the paperwork agrees with the arithmetic. And if an applicant’s income story is *new job, starts soon* — that’s not automatically disqualifying, but it’s a different risk than *eight months of steady pay*, and you deserve to know which one you’re actually being shown. The rest of the document checks — metadata, template tells, the employer behind it — still apply; this trick just proves the employer being real doesn’t end the conversation.

This class of fake is exactly why ProofSweep examines documents together, not one at a time — the pay math and year-to-date consistency, the document’s own metadata, the employer’s real-world records, and whether the papers in the file agree with each other about the timeline. A stub built on real facts looks perfect in isolation. Documents keep their stories straight; fakes usually don’t. Have a pay stub checked before the keys change hands.