A manually prepared case walkthrough. No actual file processing or checking engine runs on this page.
These synthetic examples explain the distinction between transferred values, arithmetic and comparison scope. The shown conclusions are illustrative expected findings, not results calculated by this website.
Case 01 / Same data, incorrect calculation
The copied value matches. The arithmetic does not.
The source writes a total of 25.00 for three items at 8.00 each. The transferred table also writes 25.00.
The transfer check can agree while a separately approved quantity × price rule finds an arithmetic difference. A correct copy does not make the source calculation correct.
What needs a person’s confirmation?
Confirm that quantity and unit price use the same units and scope, and that the line total should be quantity × unit price. Discounts, tax, scaling or rounding conventions may change the appropriate rule.
Case 02 / Same overall sum, different rows
A matching total can hide changed cells.
Two values are swapped during a transfer. The overall sum remains 30.00, so checking only that sum would miss the row-level differences.
Synthetic comparison using an agreed unique row key
Row key
Source value
Transferred value
Illustrative finding
A
12.00
18.00
Changed
B
18.00
12.00
Changed
Overall sum
30.00
30.00
Unchanged
Illustrative expected finding
A comparison tied to unique row keys A and B identifies two changed values, even though the aggregate total agrees. The matching total alone is not enough evidence of a correct transfer.
What if the keys or columns are ambiguous?
Column mapping and unique row identifiers require confirmation. If the supplied data does not identify rows reliably, an uncertain result should remain uncertain rather than being labelled a match.
Case 03 / A confirmed list is still a limited scope
One checked table does not cover a document.
For this illustration, a person has confirmed that the selected scope contains two tables. Only the first table has been compared.
Synthetic scope register
Confirmed table
Comparison state
What can be concluded?
Table 1
Selected values reviewed
Conclusion is limited to those values
Table 2
Not yet compared
Requires further work
Illustrative expected finding
The declared scope remains incomplete: one of two confirmed tables still needs comparison. Even checking both would not independently prove that the list contains every table or that the rest of the PDF is correct.
What does scope confirmation establish?
A person’s confirmed register defines the denominator for that selected task. It is not automatic proof of a PDF’s completeness, authenticity or correctness.
Bring a real question to a private test
Define what a useful check means.
Discuss a limited pilot for your table formats, rules and review workflow. Agree the data-handling environment before sharing sensitive documents.