No recipient accountNo AI analysisExport-ready
PRODUCT
A neutral record for PDFs. Built for real work.
Receipt captures what is observable, delivery, access, review activity, and acknowledgement, then turns it into a clean record you can keep on file.
Receipt is not an e-signature tool and does not verify identity by default.
Receipt Record
Residential Conveyancing
Acknowledged
Document
Client Care Letter - Residential Conveyancing
Version hash: 9f2c...a81d
Recipient
Alex Smith
alex@client.com
Acknowledged
Yes
12 Feb 2026, 09:22
First opened
09:17
Scroll depth
100%
Time on page
4m 32s
Timeline
09:17
Opened
09:19
Reached 50% scroll
09:22
Acknowledged
Receipt records observable events (delivery, access, review activity, acknowledgement).
Export PDF record
WHY IT EXISTS
Because "we sent it" is not evidence.
Receipt is for moments where you need a clean record, not a debate.
Neutral by design
Records what happened, when it happened, and what was viewed, without assumptions or interpretation.
Frictionless for recipients
One link. Open the PDF in-browser. Review it. Acknowledge it if required.
Clean output for the file
Exports a tidy record with timestamps and activity fields, consistent and audit-friendly.
What it records
Receipt stays neutral: timestamps, activity, and acknowledgement.
Fields
• delivered_at / first_opened_at
• max_scroll_percent
• time_on_page_seconds
• acknowledgement + submitted_at
• (optional) ip + user_agent
• document hash / version
Where teams use it
Practical use cases that need evidence, not opinion.
Client care letters
Policy updates
Terms notices
Internal rollouts
Supplier governance
What it is not
Not e-signature
Receipt does not replace signing workflows.
Not consent capture
It does not claim intent, agreement, or comprehension.
Not analysis
No AI interpretation. No sentiment. No conclusions.