For tax preparers
Skip the December Mail Run. Send Year-End Letters as URLs.
Write your year-end CYA letter once. Publish it at /yourfirm/2025-year-end-clientname. The client opens a link, no portal login, no lost PDF attachment, no reprint.
What changes when CYA letters live at a URL
Read receipt that actually works
View count and time-on-doc show whether the client opened the letter. No more 'did you get my letter?' calls in January.
Update without resending
Add a line item to the missing-info checklist, re-publish with one command, same URL. No reprinting, no re-emailing, no version confusion.
One URL per client, version history
/yourfirm/2025-year-end-smith is a clean URL with every draft saved automatically. Document what the client received and when.
Versus paper mail and PDF email
| Anchorify | Paper mail / PDF email | |
|---|---|---|
| Client opens without creating an account | ✓ | ✓ |
| Client can re-read at same URL anytime | ✓ | ✗ |
| Confirm client read it | view count + time-on-doc | no (read receipts unreliable) |
| Update without resending | ✓ | ✗ |
| Version history | unlimited | ✗ |
| Cost per letter (direct) | $0 (free tier) | $2-4+ (paper) |
| Staff time per 100 letters | minutes | 2-4 hours (paper) |
| Password protection per letter | ✓ | ✗ |
| Resend on demand without file hunt | ✓ | ✗ |
FAQ
What about Circular 230 record retention?
IRS Circular 230 section 10.28 requires practitioners to return client records on request but does not specify how long you must retain your own copies. Best practice from accounting professional bodies is 7 years. A stable URL is a living copy of what you sent the client, accessible on demand. It does not replace backup in your practice management system; it replaces the delivery step.
Can I send a unique CYA letter per client?
Yes. Each publish creates a separate URL with its own slug, version history, and read analytics. Use /yourfirm/2025-year-end-smith for one client and /yourfirm/2025-year-end-jones for another. You can batch-publish from a script that fills in template variables per client.
What about confidential tax data in the letter?
CYA letters typically contain status summaries, not raw return data. For letters that reference sensitive figures, set a per-share password from the dashboard or CLI. Raw return copies belong in encrypted channels. Anchorify is appropriate for the summary letter the client re-reads, not for documents that must stay inside a secure portal.
Can I password-protect each link?
Yes. Each share has its own optional password, set independently. The client gets the URL and the password. No Anchorify account is required to read the letter.
Clear the December backlog without the mail run.
Free during beta. Sign in with Google to start.