Let’s Seal

Seal and verify accounts & audit reports

Financial statements, audit reports, and tax filings that prove their own authenticity — so a bank, an investor, or a regulator can confirm the accounts are the version you signed off, unaltered and fixed in time.

For accountants, auditors, tax advisers, and bookkeepers.

Open the app Developer docs
What a seal proves

Four guarantees, in accounting & audit

The figures can't be altered

A changed number, note, or opinion fails verification. The signed-off accounts are provably the accounts — no quiet edits after the fact.

The firm that issued them, named

Every statement and report names the practice that sealed it, chaining to a published root — the attribution a bank or regulator expects.

Fixed to the reporting date

The moment of issue is timestamped on Bitcoin, so a set of accounts or an audit opinion can't be back- or forward-dated.

Verified independently

A lender, an investor, or a regulator confirms the report against public infrastructure — no access to, or trust in, your systems required.

How it works

From your file to a proof anyone can check

The same pipeline every time — the seal and the timestamp travel with the file, so the proof is self-contained.

Your file
Your signed PDF
Seal
Signed over every byte · PAdES
Anchor
Bitcoin timestamp + public transparency log
Proof page
A permanent /d/… link travels with the file
Anyone verifies
Free, public, offline-capable — for anyone
The proof travels inside the file. Verification stands on the published root, the transparency log, and the Bitcoin ledger — so a court, a bank, or a counterparty can check it independently, forever.
Step by step · the web app

Seal it in the app — no setup

  1. 1

    Sign in as your practice

    Open app.letsseal.org and sign in. Your firm gets its own certificate authority for sealing accounts and reports.

  2. 2

    Upload the finalised accounts

    Drop in the financial statements or audit report. It's sealed over the whole file, so any later edit to a figure or note is caught.

  3. 3

    Anchored and logged automatically

    The fingerprint is timestamped on Bitcoin and written to the public transparency log. The client gets a normal PDF that also verifies.

  4. 4

    Issue with a proof link

    Every report has a permanent proof page. The client passes the link to their bank or investors, who confirm the accounts are genuine and unaltered.

Step by step · the CLI

Automate it from your terminal or CI

The sealbot CLI does the same thing, scriptably — one command per file, straight into your pipeline.

# Seal a set of finalised accounts under your practice
$ sealbot seal financial-statements-fy26.pdf --org examples
sealed   financial-statements-fy26.pdf
  proof  https://letsseal.org/d/5a2e88…10bd
  anchored to Bitcoin · recorded in the transparency log

# Seal a whole run of client reports at once
$ sealbot watch /srv/reports --mode seal --org examples
watching /srv/reports … sealing new & changed PDFs (idempotent)

# A bank or regulator confirms the report — public, no account
$ sealbot verify audit-report-fy26.pdf
✓ authentic · unaltered · sealed by Let's Seal Examples

Seal finalised accounts and reports one at a time or in a run. Each carries a permanent proof link — a lender or regulator verifies it against public infrastructure, with no access to your systems.

Full CLI & API reference
See it in action

What a proof looks like, and what you can seal

Issuer verified — controls letsseal.org
Authentic & unaltered
Document
A sealed set of financial statements
Issuer
Let’s Seal Examplesletsseal.org
SHA-256
64-hex fingerprint ✓

Anchored on Bitcoin

Recorded in the public transparency log

Public and free to verify — by anyone, with standard tools.
Open the live proof

A single use case, many documents. Each of these is sealed the same way:

  • A sealed set of financial statements

    Live proof

    Open the proof page the way a lender reviewing the accounts would: it shows the statements are authentic, unaltered since sign-off, issued by the named firm, and timestamped on Bitcoin.

  • An audit report or opinion

    Seal the signed audit report so a regulator or investor can confirm the opinion is exactly as issued — decisive when accounts are relied on for a transaction.

  • A tax return or computation

    Seal the filed return so an adviser, lender, or authority can verify it's the version submitted, unaltered and dated.

  • A SOC 2 / ISO report

    Assurance reports sealed on issue, so a customer's security team can confirm the report they received is genuine and current — not a recycled or edited copy.

Live proofs are real documents sealed under the “Let’s Seal Examples” organisation.

Common documents

What you’ll seal

  • Financial statements
  • Audit reports
  • Tax returns
  • Management accounts
  • SOC reports
  • Engagement & representation letters
Questions

Straight answers

Does this replace an auditor's signature?
No. It's the cryptographic layer beneath it: the seal proves the report is authentic, unaltered, issued by your firm, and fixed in time. The professional opinion is still yours — the seal just makes the document tamper-evident and independently checkable.
How does a bank verify a set of accounts?
They open the proof link, or drop the PDF into the public verifier. It confirms the accounts are the signed-off version, unaltered, and issued by you — with no call to your practice.
Can accounts stay verifiable for years?
Yes. The seal and the Bitcoin anchor outlive any single vendor, so a set of accounts sealed today stays independently verifiable indefinitely, with standard tools.
Does the client need special software?
No. They get a normal PDF that opens anywhere, and it also verifies against the public portal and any standard PAdES validator.

Start sealing accounting & audit documents

Free and open. Seal in the app, automate from the CLI, and hand anyone a proof they can verify themselves.

Open the app All use cases