What the fingerprint establishes
SHA-256 maps the exact bytes of a file to a fixed-length digest. A second reviewer can hash the same file later and check whether the bytes match. Even a one-character change should produce a different digest. The calculation here runs in your browser; the selected statement is not uploaded to this site.
What it does not establish
A hash does not prove that a broker issued the file, that every account was disclosed, or that the file existed on a particular earlier date. For a credible audit, preserve issuer provenance, account identity, complete period coverage, opening and closing balances, deposits and withdrawals, and trade-level population. A timestamp or independent custody record must accompany any claim about when the digest was committed.
A useful handoff packet
Keep the original file unmodified. Save the hash, file size, statement period and broker name in a private evidence log. Redact personal information only in a separate copy; the redacted copy will have a different hash. An analyst should reconcile cash flows and risk metrics from the original source, not infer performance from a filename or screenshot.
Worked chain of custody
Imagine a broker exports a monthly statement. Hash the untouched download and record the digest, exact file size, broker portal, export time and statement period in your private log. If you redact the account number for a reviewer, hash that redacted copy separately and label the relationship between the two files. A later matching digest shows byte-level continuity of the corresponding file. It cannot show whether the portal export was complete, whether another account was omitted or whether the file was created before the time you logged.
What an independent reviewer needs
Supply a consistent opening and closing balance, transaction history, deposits, withdrawals, fees and any broker corrections for the same account and period. Have the reviewer reconcile those fields against source records before calculating a return. For a public claim, describe exactly which account and dates were covered and who performed the review. A cryptographic timestamp can help establish when a digest was committed, but it is a separate step from verifying issuer identity or recomputing performance.
Privacy is part of the evidence design
An evidence packet can prove a narrow public claim without exposing a full account number or private transactions to every reader. Keep the original under controlled access, publish a scoped verification statement and provide a separate redacted exhibit where appropriate. Document who had access to each version. Redaction protects the account holder, but it also removes information, so an independent reviewer must state what they actually saw.