Comparing a PDF With an Original: A Reviewer’s Checklist

A PDF comparison is useful only when you know what the reference represents. A second attachment from the same message may be another version, but it is not automatically an independently confirmed original. Start by identifying who supplied each file, when it was obtained, and which version the organization intended you to use.

The practical objective is to locate meaningful differences and explain their consequence. It is usually possible to answer that question without deciding who changed a file or whether anyone acted dishonestly.

Establish the reference before comparing pages

Keep the received PDF and the reference in separate, clearly named locations. Do not open either in an editor and save over it. Record whether the reference came from an issuer portal, an established organizational contact, an earlier approved submission, or the same sender. Those origins support different levels of confidence.

If the reference is uncertain, follow the request for an original PDF before using the word “original” in your report. A useful note is “reference downloaded from the established supplier account on 13 September.” “Original received from someone” leaves the important question unanswered.

Write down the intended comparison: all visible content, a replacement schedule, a particular total, or a group of identification fields. This scope prevents an unrelated formatting difference from consuming the review.

Build a page map

Compare page counts and thumbnail sequences first. A cover sheet can shift every subsequent page number, making a direct page-one-to-page-one comparison misleading. Match section headings, printed page labels, table continuations, and appendices.

Use a small map such as “received page 4 corresponds to reference page 3.” Mark an unmatched page as unmatched; do not quietly assume it replaces the nearest page. If an appendix is missing, record that before examining tiny font differences elsewhere.

For a long document, check the first and last page of each section and every page mentioned in the contents. Then inspect the entire sequence for repeated or skipped material. Our page replacement review explains how to pursue a page-specific discrepancy without interpreting it as proof of substitution.

Compare the content in separate passes

First read the fields that drive the business task: document number, effective date, stated scope, quantity, name, or total. Next inspect surrounding qualifications and footnotes. A matching headline value does not resolve a changed condition beneath it.

Then compare presentation: images, tables, marks, and any explanatory notes. Record a difference in a signature image as a visible difference; a picture does not establish cryptographic signature validity.

For supported automated comparison, Acrobat Pro offers comparison of PDF versions and a difference report. Its settings include different treatment for scanned documents and text-oriented files. Adobe’s comparison documentation.

Treat the report as a navigation aid. Open each material highlight in both source files. A program may group a moved paragraph as multiple changes, while a short but important condition deserves individual attention. Record the tool settings alongside the report so another reviewer can reproduce the same comparison.

Separate file differences from business differences

Different file sizes or software names do not tell you which visible field changed. Two exports can present the same business information while containing different bytes. Conversely, two pages that look similar at ordinary zoom can differ in a single digit.

Use the distinction between identical-looking PDFs and identical files when describing the result. Metadata mismatch, absent dates, or several end-of-file markers cannot independently establish fraud or a changed business statement.

If useful, run a CleanPDF edit-trace check on an authorized working copy. It can identify some modification and hidden-information traces. It does not perform issuer confirmation, certify authenticity, or replace the side-by-side comparison described here.

Work through a concrete discrepancy

In a fictional example, a five-page service schedule is compared with an issuer-provided four-page version. The extra first page is a covering letter. After mapping pages, the reviewer finds the same line items but a different delivery date in one table.

The correct finding is specific: “Received page 3 shows 21 October; reference page 2 shows 28 October.” The next step is to ask which schedule is current. The covering letter and the date difference belong in separate observations, because one explains pagination while the other affects the task.

Do not phrase the finding as “the PDF was forged.” The comparison has established a discrepancy, not its cause.

Close the review with an explicit boundary

Save the page map, material differences, reference origin, and unresolved questions together. State which pages and features were examined, particularly if you excluded attachments, comments, or signature validation. Use a PDF review report to keep observations distinct from conclusions.

A useful outcome is “visible scope and quantities match; effective date awaits issuer confirmation.” That gives the next person enough information to act and preserves the uncertainty that the files alone cannot resolve.