PDF for accountants — tax-season workflow tools

The tax-season PDF toolkit

Step by step — the bound-return workflow

1. Organise source PDFs in a numbered folder. 01_cover.pdf, 02_engagement_letter.pdf, 03_1040_signed.pdf, 04_schedule_a.pdf, etc. Filename numbering controls merge order.
2. OCR any scanned attachments first. Run Make PDF Searchable on each scanned 1099, K-1, or receipt so the final bound file is searchable end-to-end.
3. Redact PII in the source PDFs. Use Redact PDF to remove SSNs (except in the signed 1040 itself), EINs in non-essential attachments, and any account numbers not required for filing. True redaction — not rectangle annotation.
4. Merge in order. Drag the numbered source files into Merge PDF in filename order. Verify the preview matches the intended bind order before downloading.
5. Add page numbers, bates-stamp, lock, deliver. Add page numbers and bates prefix across the merged file. Lock with Protect PDF using an owner password (modifications restricted; viewing open). Compress if over 10 MB. Send via secure-email channel.

Related reading

• Small-business PDF tools: for the client-side of the workflow.
• PDF redaction guide: deeper dive on true redaction vs annotation.
• Bates numbering PDF: how to bates-stamp workpapers.
• PDF security guide: password types and what each protects.
• Searchable PDF: OCR for scanned 1099s and K-1s.
• Compress PDF: e-file and email-attachment size compliance.
• All ScoutMyTool PDF tools: the complete toolkit.

FAQ

How do I actually redact a SSN — not just hide it with a black rectangle?

Two different operations get confused here. Drawing a black rectangle over a SSN in any PDF annotation tool leaves the original SSN text intact in the underlying content stream — anyone with Acrobat Pro can select-copy the rectangle aside and read the SSN. True redaction removes the content entirely. In ScoutMyTool Redact PDF, draw the redaction rectangle, choose "Apply", and the tool removes the underlying text and replaces it with the redaction colour permanently. To verify: after redacting, try to select-copy the redacted region — you should get the redaction colour, not the original characters. For tax workpapers shared with the client or sent to the IRS, never rely on rectangle annotations; always use true redaction.

My firm requires bates numbering on every audit-defence file. How does it actually work?

Bates numbering is a sequential identifier stamped on every page so each can be cited by its bates number in correspondence, court filings, or response letters. Format is typically PREFIX-NNNNNN where prefix identifies the producing party or workpaper section, and NNNNNN is a zero-padded sequence number. For an accounting workpaper file, a common pattern is FIRMINITIALS-YYYY-MMDD-NNNNNN (e.g. RKH-2026-0415-000001). In ScoutMyTool Bates Numbering, set the prefix, starting number, position (bottom-right is conventional), and font size (8pt is standard). The numbers persist across PDF edits; if you later re-paginate the bundle, re-bates the whole file to keep sequence integrity.

Is it safe to use a free online PDF tool for client tax documents?

Only if the tool runs client-side. Tax documents contain SSNs, EINs, account numbers, and other PII covered by Section 7216 of the Internal Revenue Code (prohibiting disclosure of taxpayer information by preparers) and state-level privacy laws. Server-side PDF tools (Smallpdf, iLovePDF, Adobe online) upload the file to vendor infrastructure for processing — even if deleted within an hour, that is a disclosure. Client-side tools (ScoutMyTool, Apple Preview desktop, Adobe Acrobat desktop) keep the file on your machine. For tax work, default to client-side unless you have a written data-processing agreement with the vendor that addresses Section 7216 and state requirements.

How do I produce a single bound PDF of a complete client return with all attachments?

Workflow: organise the source files in a numbered folder structure (01_cover, 02_engagement_letter, 03_1040_signed, 04_schedule_a, 05_receipts, ...), each file named to sort correctly within its folder. Use ScoutMyTool Merge PDF to combine them in folder order. Add page numbers and a bates prefix across the merged file. Add a cover page if needed (Word document → PDF, prepended). Final pass: lock with an owner password so the client cannot accidentally modify, then send. The whole bind for a typical individual return takes 10–15 minutes once the source PDFs are organised.

My client sent me their 1099s as separate PDFs. How do I get the data out efficiently?

Two paths depending on volume. For under ~20 1099s, manually re-key into your tax software is fastest — OCR + extraction adds friction without saving time. For larger volumes, OCR each PDF (ScoutMyTool Make PDF Searchable, in batch), then either (a) extract specific boxes manually now that the text is searchable (Cmd-F "Box 1", "Box 4", etc.) or (b) export each PDF's text and post-process with a script that pulls box values by label. The bracket where automation pays off varies by firm — most US-side individual-return practices land at around 30+ documents before scripted extraction beats manual entry.

How do I keep an audit-trail of edits to a tax workpaper PDF?

Version with filename and date: keep each working iteration as a separate file rather than overwriting. Pattern: WP-{section}-{YYYYMMDD}-v{N}-{initials}.pdf, e.g. WP-RentalIncome-20260315-v3-RK.pdf. Combine with a master log spreadsheet (one row per change: date, file, change made, by whom, why). For PCAOB-regulated work, this informal version control is not sufficient — use a workpaper management system (Engagement, Caseware) which provides automated tracking. For tax-only and review-engagement work, filename-and-log is the customary practice.

Can I OCR a stack of receipts in one batch instead of one-by-one?

Yes — merge them into one PDF first, then OCR the merged file once. ScoutMyTool Merge PDF + Make PDF Searchable handle this in sequence. The merged-then-OCR'd file is one searchable bundle: Cmd-F finds keywords (vendor, date, amount) across all receipts at once. For very large batches (over ~200 receipts), break into 50-receipt chunks so OCR runs in a manageable browser tab — long-running OCR can exhaust browser memory on weaker laptops. After OCR, the bundle becomes the canonical "annual receipts" file for that client.

Citations

1. Internal Revenue Code Section 7216 — "Disclosure or use of information by preparers of returns" — restrictions on taxpayer-information disclosure.
2. AICPA — "Statements on Standards for Tax Services" — professional standards for taxpayer return preparation.
3. PCAOB Auditing Standard 1215 — "Audit Documentation" — workpaper requirements for public-company audits.
4. ISO 32000-1:2008 — "Document management — Portable document format" — base PDF specification.