Confirmation receipt showing what happened
A durable, human-readable receipt for every action an agent takes, serving as the shared record a user and an agency can each check if they later disagree about what happened.
The impact of agents
As agents file actions on a user's behalf at growing scale, each one settles into an official record the moment it is submitted. The user needs a durable, human-readable account of what was filed, when, by whom (or by what), and on what basis, so that proof of lodgment and the anchor for any later dispute survive the transaction. The record here is the action, the single filed transaction; the record of the authority it was filed under lives with the delegation itself, and a dispute usually needs both.
What must be verified
A durable, human-readable receipt records what was filed, when, by whom (or by what agent), under what delegation, and on what data. The agency issuing the receipt must retain it and make it retrievable to the user on request.
Protecting access
The receipt is evidence, and losing it costs the user when a dispute comes. A user on a shared or public device, with no inbox or storage of their own, can lose the receipt. A user who can't understand what the record says can't use it as evidence either.
Keeping the path open
- Issue the receipt in more than one form: on-screen, email, PDF, SMS summary, or paper on request.
- State in plain language what was filed and by what authority.
- Keep every receipt retrievable from the service later, so the moment of confirmation is never the only chance to hold the proof.
- Make the receipt screen operable by keyboard and screen reader, with the filing confirmation and reference number announced as they appear, not only displayed.
- Pre-populate dispute affordances from the action record, so the user who most struggles to narrate history never has to.
Response surface
Every agent action produces a durable, attributable record, issued to the user as a confirmation they can keep and cite later.
City Digital Services will assess your return. You’ll receive your notice of assessment within 14 days. This receipt stays in Your activity. You don’t need to keep this page open.
Maturity
- Established
For the confirmation receipt, a settled pattern across government and commercial services.
- Emerging Headline
For agent attribution on receipts, recording which agent acted and under what delegation, where agent-delegation identity protocols are proposed but not yet a ratified standard, and no receipt implementation is cited here.
- Frontier
For cryptographic receipt integrity on government agent actions, which remains undesigned.
Precedents
GOV.UK confirmation pages. A confirmation page must carry a reference number where one applies, what happens next and when, service contact details, links to related services, a feedback link, and a way to save the record. The ONS design system carries the same requirements. The design system specifies the contents centrally, so each service inherits them.
ATO lodgment receipt. On lodging through myTax the ATO emails a lodgment receipt carrying a unique receipt ID, and business lodgment confirmation screens can be printed or saved as PDF. The record leaves the agency's interface and reaches the person's own.
PSD2 transaction information. The Directive mandates detailed transaction information to consumers, which makes a legitimate charge easier to identify, and Strong Customer Authentication leaves an evidence trail behind each payment. One artifact serves as both receipt and dispute defense.
NIST IR 8202 on blockchain receipts. Smart contracts create periodic cryptographic receipts carrying a hash of the transaction data. Hashing makes tampering detectable without trusting the issuer's own record, at the cost of infrastructure a submission channel does not have.
What carries over to agent use
The GOV.UK and ATO patterns transfer directly as structural templates. For agent-mediated actions, the receipt must additionally record: (a) that an agent acted (not the user directly), (b) the identity or class of the agent, (c) the delegation authority under which it acted, and (d) the data sources it relied upon.
Blockchain-style cryptographic hashing of receipts is worth considering for high-stakes filings where receipt integrity may later be disputed: the user and the government each hold a hash that proves the receipt has not been altered.
Where things go wrong
Where this goes wrong is an agent action filed with no durable record, leaving the user unable to prove what was submitted, when, or under what authority once a dispute arises. A receipt can also satisfy the letter of this requirement while failing its point: one that gives a reference number but omits the data used or the delegation it acted under gives the user nothing to anchor a dispute to.
Sources
6 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.