How to Fit Employee Payslip Collection Into
Your Google Sheets Payroll Workflow

The Collection Gap in Payroll Reconciliation

The American Payroll Association estimates that payroll errors cost U.S. employers up to 1.2% of total payroll annually. A separate EY study found that fixing a single payroll error costs an average of $291 in staff time — and that full-time payroll employees lose an average of 29 weeks per year to error correction. The numbers are striking, but they obscure where the errors actually originate.

Most payroll reconciliation guides focus on the matching step: comparing the payroll register against bank withdrawals, verifying tax deposits against Form 941 filings, checking that gross-to-net calculations landed where they should. That matching step is important. But for a small business where employees receive payslips from an external provider — ADP RUN at $79/month plus $4 per employee, Gusto at $49/month plus $6, QuickBooks Payroll Core at $50 plus $6.50 — the matching step isn't where errors are born. Errors are born in the handoff. The payslip PDF lives in the employee's email inbox, their ADP portal, or their phone's camera roll. The reconciliation spreadsheet lives on the HR manager's laptop. Getting data across that gap means someone types: employee name, pay period, gross pay, federal withholding, Social Security, Medicare, state tax, net pay. For 15 employees. Every pay period. Before direct deposits go out.

That typing step is the bottleneck — and it's a bottleneck that dedicated payroll software doesn't solve. ADP doesn't extract data from a Gusto payslip so you can reconcile. Gusto doesn't read an ADP pay stub. The systems talk to themselves, not to each other. And the business owner who needs to verify that an employee's deductions are correct across two different payroll providers is stuck in the middle with a calculator and a spreadsheet.

Why Email Threads and Shared Folders Break at Payroll Scale

Most small businesses collect employee payslips the same way they collect everything else: email. "Send me your pay stub" lands in 15 inboxes. Fifteen employees forward or attach PDFs at various times over a 3-day window. The HR manager opens each attachment, locates the relevant numbers, and types them into a row. If an employee sends a screenshot instead of a PDF, the process stalls. If an employee sends last month's instead of this month's, nobody catches it until the numbers don't add up.

This model produces three failure modes that compound as headcount grows. First, version confusion: an employee forwards the wrong pay period's stub, and the mismatch isn't discovered until the reconciliation step when net pay in the spreadsheet doesn't match the direct deposit amount that already cleared. Second, format fragmentation: one employee sends a PDF download from ADP, another sends a phone screenshot of the Gusto app, a third photographs a printed stub on their kitchen counter. Each format requires a different mental workflow to extract data from. Third, the invisible assembly cost: the HR manager spends 1-2 minutes per payslip opening files, locating fields, and typing — which sounds trivial until you multiply it by 30 employees biweekly. That's an hour of pure hand-eye coordination per pay period, 26 times a year. And 26 hours of transcription is 26 hours of opportunities for a mistyped Social Security withholding to cascade into a year-end W-2 discrepancy.

This isn't a hypothetical edge case. A 2022 survey of HR practitioners on the Reddit r/humanresources subreddit described a 110-employee company running payroll through 15 separate Excel spreadsheets tracking bonuses, commissions, overtime, and deductions — with the HR generalist admitting "I'm terrified I'm going to make an error with someone's pay." Another post on r/Payroll described reconciliation taking "a full day" each cycle because "the entries never ever reconcile." These are real practitioners using real tools — ADP, spreadsheets, email — and still losing entire working days to the collection-and-entry gap.

Collection Link: A One-Way Data Pipe That Asks Nothing of Employees

A Collection Link is a shareable URL (formatted as /c/xxxx) that you generate from your ImageToTable.ai account. When someone opens that link, they see an upload page with a short verification code. They enter the code, drop their payslip files (PDF, JPG, PNG, screenshots — any common format), and submit. The files land in your account's processing queue. The person uploading doesn't need an account. They don't need to log in. They don't need to install anything. One link. One code. Files delivered.

This reverses the direction of the collection workflow. Instead of the HR manager chasing 15 employees for 15 files across email, Slack, and text messages, the link sits in one place — a company-wide email, a pinned Slack message, a recurring calendar invite — and employees push data into it on payday. The HR manager opens their Google Sheets sidebar when they're ready to process, and all the files are already there, organized in a queue.

For payroll reconciliation specifically, this matters in a way that generic file-sharing doesn't address. A shared Google Drive folder still requires the HR manager to open each file individually, locate fields, and type values. A Dropbox file request collects files but doesn't extract data. The Collection Link feeds directly into an extraction engine that populates a spreadsheet — the collection step and the data-entry step become a single pipeline rather than two sequential chores.

The Closed Loop: Upload to Queue to Extract to Reconcile

Here is the end-to-end workflow for a biweekly payroll cycle with the Google Sheets add-on:

At step 5, the spreadsheet looks the same as it always did. The difference is that instead of 15 individually typed rows, you have 15 extracted rows — each with the same fields, in the same columns, feeding the same downstream formulas. The employee never logged into anything. You never opened a PDF. The spreadsheet never changed.

This is the core of the Google Sheets payroll pipeline — a concept we covered in more detail in our guide to extracting timesheet photos into calculated wages. The same architecture applies to payslips: upload from the sidebar, extraction targets your columns, and the spreadsheet's existing logic handles everything downstream. For a deep dive on how the extraction itself works — including computed columns that calculate net pay verification from gross minus deductions — see extracting payslip data with net pay already computed.

What Stays Exactly the Same After You Add Extraction

This is the question that determines whether a workflow tool gets adopted or abandoned: what breaks? The small business owner who has spent three years refining a payroll reconciliation spreadsheet — with conditional formatting that highlights variances above $5, with SUMIFS that roll up deductions by department, with a pivot table that feeds the monthly P&L — has zero appetite for a tool that forces them to restructure anything.

The add-on doesn't touch your formulas. It writes extracted values into cells — the same cells you were typing into before, or a new sheet in the same workbook that your VLOOKUP or IMPORTRANGE references. Here is what continues to work without modification:

• Reconciliation variance checks. If column H is extracted net pay and column I is your bank's direct deposit amount, your =I2-H2 formula in column J continues to flag discrepancies. The formula doesn't know or care whether the value in H2 arrived by keyboard or by extraction.
• Department-level rollups. Your SUMIF that totals gross pay by cost center still works, as long as the department label column is populated. That column can be an extraction target like any other.
• Conditional formatting. Rules that highlight cells when net pay differs from expected continue to fire. Rules that color-code rows by pay period continue to apply.
• Pivot tables and charts. Refreshing a pivot table built on the extraction data range pulls in the new rows. A chart tracking monthly payroll costs by department updates automatically.
• Tax liability tracking. If you maintain a separate sheet that feeds Form 941 quarterly reconciliation, the extracted federal withholding and FICA columns populate it through your existing references.

This is the point of a workflow integration approach: you change the intake method — how data gets into the spreadsheet — and leave everything downstream untouched. It's the same principle as the employee expense collection workflow we covered in this series: the Collection Link handles intake, the sidebar handles extraction, and the spreadsheet handles everything else.

What the Sidebar Adds That Standalone Extraction Doesn't

You can extract data from a payslip using a standalone web tool: upload a PDF, get a CSV, download it, open it, copy the rows, paste them into your reconciliation sheet. That works for one payslip. For 15 employees every two weeks, that's 15 round trips to the download folder, 15 CSV files cluttering your desktop, and 15 paste operations into a sheet where the columns might not match.

The Google Sheets sidebar eliminates the middle steps by operating inside the sheet where the data ultimately lives. You define extraction columns — Employee Name, Pay Period, Gross Pay, Federal Tax, Social Security, Medicare, State Tax, Net Pay — and the extracted values append directly to the active sheet. There is no export file. No intermediate CSV. No paste step where a misaligned column pastes Social Security into the Medicare column.

The sidebar also respects the Collection Link queue — files arrive there, not on your desktop — so you never touch a raw file after initial setup. For the timesheet side of the payroll equation, the same add-on handles extracting timesheet data for payroll without typing. Both document types feed the same reconciliation spreadsheet from the same sidebar — payslip data in one sheet, timesheet data in another, everything rolling up to your payroll register.

Under the IRS Employer's Tax Guide (Publication 15), employers must keep records of all wage payments, tax withholdings, and employee information for at least four years. When extraction populates a Google Sheet with version history enabled, you get an auditable, timestamped trail of every payroll data entry — without the scan-and-file overhead of paper records. The data lives in a format you control, can export, and can hand to an auditor.

FAQ

Do my employees need to create an account to upload payslips?

No. The Collection Link requires only two things from the person uploading: the link itself and the verification code you set. They open the link, enter the code, upload their file, and close the browser tab. No registration, no login, no software installation, no permissions. This is why the link works for one-time seasonal workers, contractors, and employees who would never log into a payroll platform again after uploading one document.

Can I use the Collection Link with employees who get payslips from ADP or Gusto?

Yes. The link accepts PDFs downloaded from any payroll portal, screenshots of pay stub apps, and photos of printed stubs. If your employee can view their payslip on a screen, they can save or screenshot it and upload through the link. The extraction engine reads the content regardless of which payroll provider generated the document — the AI locates fields by understanding what they mean, not by matching a template.

What fields can the AI extract from a payslip?

You define the columns. Typical fields for payroll reconciliation include employee name, pay period dates, gross pay, federal income tax withheld, Social Security tax, Medicare tax, state tax, other deductions (401(k), health insurance, garnishments), and net pay. For providers handling multiple client companies, you can add inferred columns — for example, a column labeled "Pay Frequency (options: Weekly/Biweekly/Semimonthly/Monthly)" — and the AI will determine the pay period from the document and populate that field.

Does this work with non-English payslips?

Yes. The AI reads the semantic meaning of fields — "Bruttogehalt" on a German payslip, "Salaire brut" on a French one, "支給総額" on a Japanese one — and maps them to the column names you define regardless of language. The same collection link and sidebar workflow works across multilingual teams.

What happens to my existing payroll formulas when I add extraction?

Nothing changes. The add-on writes extracted values into cells. Formulas that reference those cells — SUMIFS, VLOOKUPs, variance checks, pivot table source ranges — continue to calculate as they always have. The spreadsheet's logic is downstream of the data; extraction only changes how data arrives, not how it's processed afterward. If you want to validate this before committing, you can run extraction into a new sheet within the same workbook and point your existing formulas at it, preserving the original typed sheet as a fallback during transition.

How is this different from emailing PDFs and using a standalone extraction tool?

Email + standalone extraction is three disconnected steps: collect files via email (scattered, unorganized), extract each file individually in a web tool (export/download), and manually paste results into your sheet (error-prone alignment). The Collection Link + sidebar replaces all three with one pipeline: uploads arrive in a queue already connected to your sheet, extraction appends directly to the active sheet from the sidebar, and you never touch a raw file or a download folder.

What does the IRS require for payroll recordkeeping?

IRS Publication 15 requires employers to keep all employment tax records — including amounts and dates of wage payments, employee names and SSNs, copies of W-4 forms, and dates of employment — for at least four years. Your Google Sheets payroll workbook with extraction data, combined with version history, provides a complete, timestamped record. For tax filing purposes, you'll still need your payroll provider's official reports (Form 941, Form 940, W-2s); extraction fills the reconciliation layer between provider reports and your internal records.

Build Your Payroll Collection Loop

Payroll reconciliation errors are expensive not because the math is hard but because the data collection step is so fragile that accuracy deteriorates before a single formula runs — an employee sends last month's stub, a PDF doesn't attach, a Social Security withholding gets mistyped by one digit. Fixing a single payroll error costs an average of $291, and with 1 in 5 payroll runs containing at least one error, small businesses are paying for a broken collection process every single pay period.

The collection link closes the gap between where payslip data lives (the employee's inbox or portal) and where it needs to go (your reconciliation sheet). One link, shared once. Employees upload in 30 seconds. Data lands in your queue. Batch extraction populates your sheet. The $291 per error you stop paying for, even once a month, covers the cost of the tool for the entire year — and your team gets those 26 hours of transcription back for work that actually requires a human. Set up a Collection Link, point it at your payroll sheet, and at the next pay period, watch the spreadsheet fill itself.