Skip to main content
Finmail
…
Back to compare

Send statements without a raw attachment

Finmail Product

Send statements without a raw attachment

The usual way to send a statement is to attach the PDF and hit Send. That is simple, and for many threads it is enough.

It is a poor default when the file will be forwarded, downloaded, and left sitting in someone else’s mailbox — a K-1 to an accountant, a brokerage statement to a tax preparer, a bank PDF to family counsel. Every downstream copy is another ordinary MIME attachment you no longer control.

Finmail Secure Share (on Professional and above) is for that job: give the recipient a password-protected, read-only link instead of stuffing the raw file on the message. It is not end-to-end encryption, and it is not a virtual data room.

When a raw attachment is the wrong tool

Use an ordinary attachment when the file is low-sensitivity, the recipient asked for email, or you already share a secure portal with them.

Prefer a link when:

  • you do not want the PDF replicated into every reply and auto-forward
  • the recipient does not need a Finmail account
  • you want an expiry, a password that travels on a separate channel, and an option to burn the snapshot after first successful unlock

This is personal-finance mail, not a fund-wide LP distribution list. If the thread belongs on the company tenant, leave it there — see a second mailbox for personal finance.

What you actually do

Two entry points; both create a share the recipient opens in the browser.

From an existing thread

  1. Open the message that holds the statement (or that you want the counterparty to read).
  2. Choose Secure Share from the message menu or toolbar.
  3. Set an expiry and a strong access password — not your mailbox login password.
  4. Send the link in mail. Send the password by phone, Signal, or another channel that is not the same inbox.

When composing

You can send the notification as a secure link rather than attaching files over SMTP. The recipient still unlocks the snapshot in the browser; the raw uploads are not added as ordinary MIME parts on that outbound message.

Recipients enter the password and read sanitized HTML. They cannot edit or forward from Finmail on your behalf. They can still screenshot or re-file what they see — a link is not a legal hold on their device.

Burn after read (optional): after the first successful unlock, the snapshot remains readable for a short window (five minutes) and then the link is unusable. Use it for one-time views; do not use it if the accountant needs to reopen the packet next week.

Revoke active links from share management when you no longer want the URL to work. Prefer short expiries.

Click-by-click UI is in the Secure Share help article.

Honest limits

  • Not Proton. If the requirement is zero-access encryption and Swiss hosting, Proton Mail is the product for that job. Secure Share is transport + passworded snapshot, with sanitized HTML.
  • Not a data room. There is no permission matrix, no Q&A log, no substitute for your accountant’s portal. Share the minimum thread, not your whole mailbox.
  • Password on the same mail as the link is weaker. A separate channel is the point of a password.
  • Hosted @finmail.com is still a hosted suffix. A cleaner outbound file does not make the From line as strong as a domain you own — hosted vs your own domain.
  • Team features are not required for this job. Composer approval and shared outbound are Team; this playbook is Professional.

If the problem you actually have is “my consumer From looks casual to a bank,” start with consumer mailbox vs professional identity, not with a share link.

Next step