Gusto is one of the most widely used payroll platforms among American small businesses, so reviewers encounter its distinctive, uncluttered stub design regularly. The design itself is easy to admire and, unfortunately, easy to imitate: a template that borrows the general look of a Gusto stub can appear entirely plausible at a glance. The durable difference between genuine and fabricated documents is rarely visual. Real Gusto payroll produces earnings rows that multiply out, withholding lines that track statutory percentages against the right taxable bases, and year-to-date columns that accumulate correctly—an interlocking web of numbers that casual fabrication tends to break somewhere.
Keep two cautions in view. First, a clean file proves nothing by itself: a careful forger can satisfy every visual and arithmetic check on a single stub, which is why decisions that matter should escalate to source verification. Second, an imperfect file is not evidence of fraud—small-business employees print stubs from browsers, photograph them, and forward compressed copies, and every step degrades structure and metadata. One useful provenance fact: Gusto accounts belong to the employee, and access commonly continues after a job ends, so asking for a freshly downloaded original is usually a reasonable, low-friction request.
A polished pay stub is not proof of authenticity. Unusual metadata is not proof of fraud. Every signal here is a reason to ask a better question—never a verdict.
What a genuine Gusto pay stub typically contains
Gusto's stub layout is more standardized than most, but it still evolves over time and varies with each employer's pay items, so read the following as commonly observed traits of genuine Gusto stubs rather than a fixed specification. Internal consistency across the whole document matters more than any single design cue:
- The employer's legal name and address typically appear in a header block, with Gusto identified as the payroll platform on the stub, and the employee's name and address nearby.
- The pay period is shown as an explicit start-and-end date range with a distinct pay date, commonly labeled plainly rather than abbreviated into codes.
- Hourly earnings rows typically present rate, hours, and an amount equal to rate times hours; salaried employees show a period salary amount, with overtime or bonus items on separate labeled rows.
- Withholding is itemized—federal income tax, Social Security, Medicare, and applicable state lines—separately from benefit deductions such as health premiums or retirement contributions.
- Current-period and year-to-date figures are paired for earnings, taxes, and deductions, with YTD values that accumulate plausibly given the pay date's month.
- Net pay is stated prominently and equals gross earnings minus the itemized taxes and deductions, often accompanied by a payment method or direct-deposit reference.
- A stub downloaded from the employee's Gusto account is typically a text-layer PDF with selectable text; a flat image per page indicates a scan, photo, or reconstruction and weakens most downstream checks.
Field-level checks anyone can run
1. Request a fresh download from the employee's account
Because Gusto accounts are the employee's own and access commonly persists beyond employment, asking the applicant to log in and download the stub fresh is usually easy. That file preserves far more verifiable structure than screenshots or rescans. Never request the applicant's login credentials.
2. Hash the document before reviewing it
Take a SHA-256 fingerprint of the received file immediately so any later substitution is detectable and your decision is tied to a specific document. Ocolta's free scanner computes the hash locally; nothing leaves your machine.
3. Reconcile gross to net
Add the earnings rows to confirm gross, then subtract every tax and deduction line; the result must equal the stated net pay exactly. Fabricated stubs frequently adjust one figure and leave the rest stale. Write the arithmetic down rather than approximating it.
4. Verify rate-times-hours on each earnings line
Genuine Gusto stubs carry the components of each hourly calculation. Multiply rate by hours for each row and compare to the printed amount, checking that overtime rates bear a sensible relationship to the base rate. A mismatch pinpoints exactly which figure to ask about.
5. Audit the YTD accumulation
With consecutive stubs, each line's year-to-date should equal the previous stub's YTD plus the current amount, and no YTD figure may ever shrink mid-year. With one stub, compare YTD gross against the pay date: a March stub carrying ten months of implied earnings deserves a question.
6. Check withholding plausibility
Social Security withholding commonly runs 6.2% of Social Security taxable wages up to the annual wage base, Medicare 1.45%. Remember that pre-tax benefits alter the taxable bases, so compute from the stub's own taxable figures where available before treating a deviation as meaningful.
7. Map the pay cadence
Small businesses on Gusto commonly pay weekly, biweekly, or semimonthly. Confirm the period length matches the claimed cadence, that pay dates land consistently, and that any bank statement in the file shows deposits matching the stub's net amounts on corresponding dates.
8. Track stub or payment numbering
Where a check number or payment reference appears, it should move in one direction across sequential stubs from the same employer. Repeated identifiers on different pay dates, or references formatted differently between supposedly consecutive stubs, are worth raising.
9. Inspect typography under magnification
Gusto's layouts are typographically consistent, which makes tampering comparatively visible. Zoom to 400% on the net pay and YTD figures: look for digits off the baseline, subtle font substitutions, or numbers that break the column's alignment relative to neighboring rows.
10. Confirm employer details against the application
The employer's name and address on the stub should match the application, any offer letter, and public records you can reasonably consult. If an EIN is printed, it should follow the standard nine-digit format. Inconsistent employer identity across documents strengthens the case for source verification.
11. Review PDF creator and modification metadata
A stub presented as a direct Gusto download should not need a general-purpose editing tool in its producer field or a modification timestamp weeks after creation. Such anomalies are legitimate byproducts of printing and merging too—so respond by requesting the original, not by concluding fraud.
12. Be skeptical of uniformly round figures
Percentage-based taxes almost guarantee odd cents somewhere on a genuine stub. A document where gross, each withholding line, and net pay all land on whole dollars resembles generic template output more than processed payroll, and it justifies asking for supporting documents.
What Ocolta’s free scan checks automatically
Several of the checks above are mechanical, and mechanical work belongs to software. Ocolta’s free Integrity Scan runs entirely in your browser—the file never leaves your device—and reports the supported signals it can actually observe: whether the declared file type matches its binary signature, which software the PDF says created and produced it, creation and modification timestamps, incremental revision pointers, embedded scripts or attachments, and a SHA-256 fingerprint of the exact file you reviewed. For paystubs it also recomputes the core arithmetic—gross pay minus deductions against net pay—and explains benign causes to consider for each observation. The PDF tamper checker runs the structural subset on any PDF. Every result keeps “unable to determine” on the table; the scan never claims a pay stub is authentic or fraudulent.
When to escalate beyond file review
Treat file review as triage. For a lease, loan, or hire, close the loop with employment verification through an authorized verification service or a documented call to the employer at a number you found independently—directory listings or the employer's own website, never the contact details printed on the stub. Follow a written verification policy, apply identical criteria to every applicant, record what you checked and why, and involve legal counsel before document-review findings feed any adverse decision.
When the file itself deserves a deeper look before you escalate externally, Ocolta’s AI Deep Review ($5 per document, no subscription) asks a model to organize fraud-risk and AI-generation indicators—evidence locations, confidence, benign explanations, limitations, and next checks. It reports observations, not verdicts, and it can return “unable to determine.” See pricing for 5-review and 25-review packs.
Frequently asked questions
Can Ocolta tell me whether a Gusto stub is fake?
No tool can make that determination. Ocolta's free scan examines structure, metadata, revision history, and the stub's own math—gross-to-net reconciliation, earnings multiplication, YTD chaining—entirely locally, and reports observations with an explicit unable-to-determine outcome. It does not certify authenticity, allege fraud, or contact Gusto or the employer.
What should I check first on a Gusto stub?
Run the two-minute math: gross minus itemized taxes and deductions must equal net, and year-to-date columns must exceed current amounts by a margin that fits the pay date's month. These recomputations are objective, fast, and catch careless fabrications more reliably than studying the logo or layout.
Does clean metadata mean a Gusto stub is genuine?
No, and messy metadata does not mean it is fake. Metadata is easy to alter and easy to disturb innocently through printing, browser exports, and file merges. Use metadata as a prompt to request a freshly downloaded original from the employee's Gusto account, never as a standalone verdict.
Can an applicant still access Gusto stubs after leaving the job?
Commonly, yes. Gusto accounts are tied to the employee rather than solely to the employer, and access to past pay documents typically continues after employment ends. That makes a fresh self-service download a reasonable request even from applicants citing a former employer—though policies can change, so allow for exceptions.
Do not tell an applicant that a document is “fake” based on file review alone. State the observation, request the same follow-up your written policy requires in comparable cases, apply consistent criteria to every applicant, and preserve an unable-to-determine outcome. Obtain legal review before using document findings in an adverse decision.