Pay Stub Distributor

The problem this kills

Distributing pay stubs by email is a privacy incident waiting to happen. One wrong address, one stub attached to the wrong message, and you've leaked someone's pay to a coworker. Then there's the steady drip of "can you resend my stub?" requests, the stubs sitting in inboxes forever, and the total lack of proof about who actually received what.

If your payroll provider has weak self-service - or you handle a chunk of employees manually, on contractors, or across a couple of entities - you're stuck doing this by hand every run. It's tedious, it's risky, and a single misroute is the kind of mistake that lands on a desk above yours.

What you'll build

A private, login-only portal that turns each pay run into a clean, auditable distribution:

• You upload the batch of stub PDFs for a run plus a mapping of which file goes to which employee (a CSV/Sheet, or a filename convention the tool reads automatically).
• The tool auto-matches every file to an employee and shows you the result.
• You review and approve the mapping before anything goes live - because a misrouted stub is a breach, nothing publishes until a human signs off.
• Once approved, stubs are published per employee, locked down so each person can ever see only their own.
• Employees log in and download their stubs; they get an email letting them know a new one is ready.
• Every view and download is written to an access log so you can prove exactly who accessed what, and when.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code), which then builds the tool with you step by step - no prior coding needed.

It opens by interviewing you about your business - your pay schedule, how your stub files are named, which fields identify an employee, your typical and peak run sizes, and your messy edge cases (terminated employees, name changes, multiple entities, corrected stubs). It reflects a short tailored spec back to you and waits for your thumbs-up, so the tool fits how you actually run payroll instead of a generic template.

From there it walks through: setting up the database with strict row-level security, the secure upload and storage of PDFs, the auto-matching engine, the admin review-and-approve screen, the employee portal, the email notifications, and the access log - each step ending with a ready-to-paste prompt.

The governance it includes (this is the point)

This tool handles some of the most sensitive data you touch, so the controls are built in from the start:

• Login required - only your team and your employees can get in.
• Row-level security so an employee can never see another employee's stub, full stop - it's enforced in the database, not just the screen.
• Encrypted file storage for every PDF.
• A hard human approval gate: the tool drafts the file-to-employee mapping, you review it, and only after you approve does anything become visible to employees.
• Duplicate guards so the same stub (same employee + pay date) can't be published twice.
• A complete access/delivery log: who uploaded, who approved, who viewed, who downloaded, and when.

Who it's for

Payroll admins and ops people at organizations whose payroll provider doesn't offer good self-service - or who distribute stubs manually for some or all of their people. If you've ever emailed a PDF and held your breath, this one's for you.

You've got this - paste the first prompt and let the agent interview you.