How to Spot a Fake Pay Stub: Red Flags and Math Checks

If you need to know how to spot a fake pay stub quickly, start by assuming that clean design proves nothing. A fake stub can look polished and still fail the checks that matter: employer identity, gross-to-net math, tax and deduction logic, year-to-date continuity, and consistency with the rest of the income file. That is the fastest answer to how to tell if a pay stub is fake without becoming a payroll specialist.

In 2026, a standard US pay stub should generally show Social Security withholding at 6.2% up to $184,500 in wages and Medicare withholding at 1.45% with no wage base cap. A mismatch does not automatically prove fraud, because pay frequency, pre-tax deductions, corrections, and special payroll situations can change the numbers, but it does mean the document needs deeper review. That is why strong fake pay stub detection does not stop at visual inspection. The safest method is layered: start with fast surface checks, then test payroll math, then verify year-to-date movement, then compare the stub against other income documents.

Before you rely on a pay stub for a rental decision, loan file, hiring workflow, or fraud review, run these five checks first:

1. Confirm the employer is real and coherent. The company name, address, phone number, pay period, and pay date should fit together and match a real business presence, not just a logo and a letterhead-style layout.
2. Reconcile gross pay to net pay. If gross wages, deductions, taxes, and net pay do not tie out in a way that can be explained, the stub is not ready for approval.
3. Test whether the tax and deduction logic makes sense. Social Security, Medicare, federal and state withholding, and benefit deductions should behave like payroll data, not like numbers typed in to reach a desired net amount.
4. Check year-to-date totals for continuity. YTD wages, taxes, and deductions should move forward in a believable way from one pay period to the next, without sudden resets, jumps, or mismatched accumulation.
5. Compare the stub with the rest of the file. Names, addresses, employer details, pay frequency, deposit amounts, and income totals should line up with bank statements, W-2s, offer letters, employment verification responses, and application disclosures.

A pay stub becomes suspicious when it looks professional on the surface but breaks under one or more of these field-level checks. That is the standard you should use: not "does this look official?" but "does this document reconcile?"

---

Visual Red Flags That Deserve a Second Look

Visual review still matters, but it works differently than it used to. Modern pay stub generators and AI-assisted document editing can produce clean, typo-free stubs, so the fastest red flags are no longer just sloppy formatting. In a fake pay stub for apartment screening, the goal is usually to make income look higher, more stable, or more recent than it really is.

Start by asking whether the document behaves like a real payroll record or only imitates one. The most useful warning signs include:

• Employer branding that does not feel consistent. The company name, logo, email domain, and address should match each other. A polished logo with a generic Gmail address or a local business name paired with a national headquarters address deserves scrutiny.
• Generic or mismatched employer details. Fraudulent pay stubs often use vague employer names, incomplete addresses, or phone numbers that do not connect to the business the applicant claims to work for.
• Round numbers that look too convenient. Exact figures like $2,000.00 gross pay, $300.00 taxes, and $1,700.00 net pay can happen, but repeated round numbers across earnings, deductions, and year-to-date fields are a common sign of manual fabrication.
• Missing pay frequency or unclear pay period dates. A real stub usually tells you whether the employee is paid weekly, biweekly, semimonthly, or monthly. If the pay dates and pay period do not line up, the document moves into the "verify" pile.
• Fonts, spacing, and alignment that shift across the page. Mixed font sizes, uneven table spacing, numbers that do not align by decimal place, or labels that look copied in from another template are classic proof of income document fraud clues.
• An unusually clean layout with no payroll noise. Real stubs often include employer IDs, deduction codes, tax labels, accrual fields, or system-generated formatting quirks. Generator-produced documents can look too perfect, too sparse, or too generic, and the same pattern shows up when you review receipts for signs of forgery or AI generation.

In rental application screening, this matters because a casual visual check is exactly what many fraudulent pay stubs are built to survive. Someone trying to qualify for a unit may submit a document that looks cleaner than a real payroll statement, with tidy spacing, high income, and no obvious typo. That surface polish is why rental application income verification cannot stop at appearance. What matters is whether the details behave the way real payroll documents usually behave.

Context matters as much as design. If the applicant says they work full-time for a regional construction firm, but the stub shows a corporate logo that does not match the company website, a mailing address in another state, and a pay schedule that conflicts with the employer's stated hiring cycle, that is more than a formatting issue. It is a mismatch between the employer story and the document itself. The same kind of inconsistency shows up in other financial records too, which is why many of the habits used to spot invoice tampering red flags also help when reviewing proof of income.

At the same time, do not treat every presentation issue as proof of fraud. Payroll providers format stubs differently. Small employers may use basic systems. Some legitimate stubs omit logos, use plain layouts, or display deductions in unfamiliar ways. Visual anomalies are triage signals, not standalone proof. Their job is to tell you when to slow down, reconcile the numbers, and compare the stub against the rest of the file before you rely on it.

Reconcile Gross Pay, Taxes, and Net Pay

A fake stub can survive a visual scan and still fail basic math. This part of pay stub verification is not about becoming a payroll expert. It is about asking a narrower question: do the numbers on the stub support each other in a believable payroll sequence? If they do not, you should not rely on the document.

1. Start with pay frequency, hours, and base earnings. Match the pay period to the earnings logic. A weekly salary usually reflects annual salary divided by 52, a biweekly salary by 26, and a semi-monthly salary by 24. If the worker is hourly, regular hours multiplied by the stated rate should match regular earnings. If overtime is shown, the overtime line should also make sense. In many nonexempt cases, overtime pay is 1.5 times the base hourly rate. If a stub shows 10 overtime hours at $20 per hour, you would expect roughly $300 in overtime earnings, not another $200. Bonuses, commissions, holiday pay, and shift differentials can change gross pay, but they should be visible somewhere on the stub.

2. Separate gross pay from taxable wages before checking taxes. This is where many reviewers make the wrong call. Gross pay is not always the wage base used for every tax. Pre-tax deductions such as health insurance, HSA or FSA contributions, and certain cafeteria-plan benefits can reduce taxable wages. A traditional 401(k) deduction often reduces federal taxable wages but does not reduce Social Security or Medicare wages. So when you verify pay stubs, do not assume every tax should be calculated from the same number. Read the wage lines the payroll system actually uses.

3. Check FICA lines against current 2026 benchmarks. For current US payroll, IRS 2026 Social Security and Medicare withholding rates show that the Social Security tax rate is 6.2% for employees and employers, the 2026 Social Security wage base limit is $184,500, and the Medicare tax rate is 1.45% with no wage base limit. That gives you a fast benchmark for pay stub math validation:

• If the stub shows $2,000 in Social Security wages for the pay period, Social Security withholding should be about $124.
• If it shows $2,000 in Medicare wages, Medicare withholding should be about $29.

Higher-income employees may also show Additional Medicare Tax later in the year as a separate line. That can be legitimate. What is not legitimate is a Social Security or Medicare number that seems detached from the wage base shown on the stub.

4. Rebuild net pay from the top down. A trustworthy stub should reconcile in a clean sequence:

Gross pay minus pre-tax deductions equals taxable wage base or bases minus withholding taxes minus post-tax deductions equals net pay

Use the listed line items, not assumptions. Post-tax deductions can include garnishments, Roth contributions, union dues, or after-tax insurance. Allow for minor penny rounding, but not meaningful gaps. If the stated net pay cannot be produced from the listed earnings and deductions, that is one of the strongest signs the stub may be fabricated or altered.

The mismatches that matter most in pay stub verification are usually these:

• Gross pay does not match hours and rate. The stub lists 80 hours at $28, but regular earnings are nowhere near $2,240 and no other earning line explains the difference.
• Overtime math is wrong. Overtime hours appear, but the rate is identical to straight time or the overtime total is mathematically impossible.
• Withholding percentages make no sense for the wages shown. Social Security or Medicare withholding is too high, too low, or missing without a credible wage-base reason.
• Taxable wages ignore the listed deductions. The stub shows pre-tax benefits, but the wage lines behave as if those deductions do not exist, or the reverse.
• Net pay cannot be derived. Even after you account for taxes and deductions, the take-home pay still does not work.

One caution: different payroll outcomes do not automatically mean fraud. Legitimate differences can come from pre-tax deductions, benefit elections, overtime treatment, bonuses, and state or local withholding. The goal is not to force every stub into one rigid formula. The goal is to see whether the employer's own numbers are internally consistent. If they are not, the document should be treated as unverified.

If you review pay stubs regularly, do not run those checks from memory alone. Capture employer name, pay date, pay period, gross pay, tax lines, deductions, net pay, and year-to-date figures in a simple table as you go. That turns one-off math checks into a repeatable workflow and makes it easier to spot the mismatches that matter across multiple files.

Check Year-to-Date Totals Against the Rest of the Income File

A single pay stub can look polished and still be false. The more reliable test is a year-to-date pay stub check: compare the current stub to earlier stubs and outside records to see whether the numbers roll forward the way real payroll does. This is where many suspicious documents break down. A fabricated stub may balance on its own, but it often fails once you review the full income trail.

Start with prior pay stubs from the same employer. Each new stub should advance from the last one in a believable way. Check:

• Pay dates and pay periods: Dates should follow the employer's normal payroll cadence, with no overlapping periods or unexplained gaps.
• Current pay versus year-to-date totals: Gross pay, taxes, and deductions should increase by roughly the current-period amounts after each payroll run.
• Wage rates and hours: Hourly rate, salary amount, and overtime patterns should stay consistent unless there is a documented raise, bonus, commission payment, or schedule change.
• Withholding totals: Federal, state, Social Security, and Medicare year-to-date figures should climb steadily rather than reset, stall, or jump without a reason.
• Deduction carry-forwards: Health insurance, retirement contributions, garnishments, or other recurring deductions should show continuity across periods.
• Abrupt changes: A sudden drop in withholding, a new deduction, or a sharp overtime spike is not automatically fraud, but it does need an explanation you can verify elsewhere.

A practical way to review this is to line up two or three stubs side by side and trace the year-to-date totals forward. If a prior stub shows year-to-date gross pay of $18,400 and the next stub shows current gross pay of $2,300, the new year-to-date gross should land near $20,700. Do the same for tax withholdings and recurring deductions. Small differences can happen because of benefit timing or tax rounding. Large differences with no payroll explanation deserve escalation.

Then compare the stub to external records. Bank deposits should generally match the net pay and arrive on or near the pay date, allowing for normal bank processing delays. If the stub shows weekly net pay of $1,842.16 but the bank account shows irregular deposits, different amounts, or no matching payroll pattern, the income file stops being consistent. A bank statement verification checklist helps you test whether the deposit trail supports what the pay stub claims.

When year-end records are available, use them. W-2 cross-checks are especially useful because the form should broadly align with the final pay stub's year-to-date wages and tax withholding figures. Box 1 wages will not always equal gross pay because pre-tax deductions can change taxable wages, but the overall relationship should still make sense. If the final stub reports year-to-date federal withholding or wages that do not reconcile with the W-2 at all, that is a serious warning sign. This is also where structured review helps: W-2 extraction and field verification makes it easier to compare the same fields across documents without missing a mismatch hidden in formatting differences.

Treat cross-document consistency as a confidence test, not a single-document beauty contest. One meaningful mismatch, such as year-to-date taxes that do not roll forward or payroll deposits that never hit the bank, can justify a manual escalation. Several aligned documents, consistent pay periods, believable year-to-date totals, and clean W-2 cross-checks increase confidence that the income record is real.

Verify the Employer, Not Just the Stub

A pay stub can look polished and still be tied to a fake or misrepresented employer. That is why employer payroll verification should happen outside the document itself. Your goal is to confirm that the company exists, that the payroll pattern is plausible, and that the person submitting the stub has a story that fits what the employer actually does.

Start with the employer identity. Check the legal business name, not just the brand name in the header. Compare it against the company website, state business records if relevant to your process, and public contact details you source yourself. A real employer should usually have a coherent footprint: a working website, a business domain email pattern, a published phone number, and a basic public presence that matches the industry and location the applicant or employee claims.

Next, compare the employer story to the rest of the file. If someone says they work full-time for a regional construction firm, the stub should not point to a payroll contact email on a free mail domain or a business website that was created yesterday and has no trace of actual operations. The payroll cadence should also make sense. Weekly, biweekly, semimonthly, and monthly schedules create different gross pay and year-to-date patterns, so the employer's normal pay cycle should line up with what you saw in the math checks earlier.

Where the stub includes payroll identifiers, review them carefully. That can include an employer EIN, payroll account number, pay group, or processor reference. These details can help you test consistency across multiple stubs or against onboarding and tax documents. But do not treat a missing employer EIN as automatic proof of fraud. Some pay stub formats, especially employee-facing portal exports, omit identifiers that would appear on tax forms or internal payroll reports. The issue is not one missing field by itself. The issue is whether the employer details that are present hold together under independent checking.

If the file still raises questions, move to outside confirmation. Use a phone number or email address obtained from the employer's public website or a trusted directory, not the contact information printed only on the submitted stub. Ask for limited confirmation tied to your process, such as employment status, job title, or payroll frequency, and document who you contacted and when. Where your workflow supports it, services such as The Work Number can provide a more standardized verification path than a manual call.

If you only have one suspicious stub, treat it as a minimum-evidence case. Verify the employer independently, request the last two or three pay stubs or recent bank statements, compare deposit timing and amounts, and pause the approval decision until a second source corroborates the income.

A practical escalation path looks like this:

• Ask for more documents when the employer exists but the file is incomplete or lightly inconsistent, such as one odd deduction label or a stub format you cannot place.
• Verify with the employer when the company appears real but the payroll details do not reconcile cleanly with the applicant's role, schedule, or prior income documents.
• Pause the approval decision when identity, payroll timing, or contact information cannot be confirmed independently.
• Treat the stub as unreliable when inconsistencies repeat across documents, the employer cannot be verified through independent sources, or the submitter keeps providing replacements that still do not align.

In practice, this is the point where many reviews become defensible or fall apart. A suspicious pay stub should never be judged only by fonts and formatting. Once the employer behind it cannot be verified through independent channels, the document stops being supporting evidence and starts becoming part of the risk signal itself.

---

When Manual Review Stops Being Enough

Manual review works best when the file count is low and the document set is simple. It starts to break down when you are comparing two or three pay stubs per applicant, matching them to bank statements or W-2s, and doing that across a queue of repeated applications or employee files. At that point, even a careful reviewer starts relying too much on memory and visual impression, which is exactly why polished fraud slips through. A fake pay stub detection workflow at scale needs more than sharp eyes. It needs the same fields checked the same way every time.

The shift is straightforward: stop treating each PDF as a standalone image and turn every stub into a row of review data. In a structured pay stub review process, capture employer name, pay date, pay period, gross pay, Social Security wages, Medicare wages, deductions, net pay, and year-to-date gross in a single sheet. Then you can compare consecutive pay periods, flag broken gross-to-net math, spot missing deposit matches, and catch YTD jumps that do not line up with prior stubs.

That makes cross-document checks stronger and more defensible. Instead of writing that a stub "looked off," you can document the exact issue: Social Security withholding that does not match the wage base, a bank deposit that never appears, or a year-to-date total that jumps without support. The value is not just better fraud detection. It is an audit trail that explains why a file was approved, escalated, or rejected.

If your team wants to extract pay stub data into a spreadsheet for verification, the workflow should stay grounded in the same operational logic you already use for other financial documents: upload the file set, prompt for the fields you need, and review the output in a structured table. That is also the logic behind Invoice Data Extraction: it converts invoices and other financial documents, including payroll documents, into spreadsheet-ready output with source file and page references, so reviewers can compare extracted fields and jump back to the original stub when something does not reconcile.

A practical rule of thumb:

• Keep using manual checks when you review a small number of pay stubs, the risk is low, and the decision can be supported by one reviewer comparing the file against obvious benchmarks.
• Move to a more systematic workflow when reviewers are handling repeated applications, multiple supporting documents per case, higher fraud exposure, or enough volume that consistency and documentation matter as much as the initial detection itself.
• If two trained reviewers could reasonably reach different conclusions from the same file set, you have already crossed the line where repeatable document verification is worth implementing.