Every handoff should leave a receipt.
A receipt is the record of a work handoff. It helps a person or system see what was requested, where it went, what happened, and whether the next step is safe to continue.
Work is requested
An agent, person, business process, or company system asks for work to be done.
A2AC creates a work record
The request becomes a structured record with context, target, expected result, and failure handling.
Rules are checked
A2AC checks the customer account, approved paths, and allowed systems before sending the work.
Work is sent
The work goes to an approved AI service, tool, worker, or company system.
Result or error returns
A2AC stores the answer or failure in a clear format that the next step can use.
The business process continues
The next agent, system, or person can inspect the receipt and continue with context.
Receipts make agent work inspectable.
Without receipts, a team has to read scattered messages and logs to understand what happened. With A2AC, the handoff itself becomes the record.
Error records keep work recoverable.
When a tool, model, browser action, or system connection fails, A2AC returns an error record. That record preserves the task, route, attempted action, failure detail, and next review step so another agent or person can retry, reroute, or close the task with context.
Receipts should fit existing operations.
A2AC receipts are meant to be useful outside the A2AC interface. Teams can send task records, error records, and summary receipt events to approved log sinks, monitoring tools, security systems, or data stores based on their deployment policy.