Escrow Evidence: The Event Log, the Acceptance Package, and the Signed Link
What an escrow leaves behind for the auditor — and why none of it can be edited afterwards.
An escrow that closes cleanly leaves a paper trail behind it. Six months later the buyer’s compliance officer asks what happened on transaction ESC-2026-000412, and the answer has to come from records nobody could have touched in the meantime. Three things make up that trail: the event log on the escrow, the evidence package generated at acceptance, and the signed download links that record who looked.
The event log
Every state transition appends a row to the escrow’s event log: created, waiver requested and confirmed, deposit reference generated, deposit confirmed, delivery prompt sent, accepted, released, dispute opened, dispute resolved, refunded, split, cancelled — and notes for the sub-steps that don’t flip a status, such as the first half of a four-eyes confirmation. Each row carries the actor, their role (buyer, seller, finance ops, compliance or system), the details and the timestamp. Updates and deletes are blocked at the database. A correction is a new row, never an edit. Because evidence that can be edited isn’t evidence.
The log is displayed on the escrow detail page for both parties. It is not exported as a ZIP; it is read where it lives.
The acceptance package
When the buyer accepts delivery, the platform generates an evidence package of type escrow_acceptance: a cover with the acceptance confirmation and the checklist answers, the outbound manifest with every item, grade and serial, the delivery photos taken on that outbound, and the buyer’s signature — user, timestamp and IP. The acceptance itself is the canonical record; if the package cannot be generated (an outbound with no resolvable assets, say), the acceptance still stands and the failure is logged rather than blocking the release.
Evidence packages come as a summary PDF, with a ZIP variant that adds the photo files and the erasure certificates linked to the assets. The escrow page lists the packages linked to the transaction for buyer and seller alike once the escrow has moved past pending deposit, and links through to the package detail. Shipping and delivery already produce their own outbound evidence; the release does not generate anything extra beyond the acceptance package.
Who looked
Downloads go through short-lived signed links, and every download is logged as document access — fail-closed. If the access event cannot be written, the download does not succeed. Somebody asking “who has the evidence” gets a row, not a guess.
The other two documents
A mutual escrow waiver produces its own PDF, with both signatures and the Belgian terms, filed under documents and shown on the deal. And inside a dispute, evidence is not a loose pile: each timeline entry points at its source package or uploaded document and says which party brought it — buyer, seller, compliance or system — so the case file reads in order, with attribution, from claim to settlement impact.