Inspect a complete Veto Record.
Follow a fictional payoff-demand hold from changed instruction to source check, open gap, office action, reviewer, timestamp, and hash.
Fictional sample · reviewer J. Martinez
- Disbursement
- Payoff demand · $184,920.16
- What changed
- Payee + wire destination
- Change via
- email · domain not verified
- Demand match
- amount and payee changed
- Source path
- known servicer path · no confirmation
- Open item
- trusted-source confirmation
- Evidence retained
- 5 of 6
- Office action
- Hold pending confirmation
- Reviewer
- J. Martinez · before release
- Signed
- 2026-05-26T14:28 UTC
- Record hash
- sha256:4e3cf8a1…6af713
Veto records the review. It does not approve, authorize, guarantee, insure, verify, release funds, or make wires safe to send. The escrow office remains the release authority.
Every line is traceable.
The sample shows how another reviewer can retrace the record: claim, source, check, result, limitation, and office action behind the hold.
Change via · revised payoff demand
- Claim
- The instruction under review is the revised amount, payee, and wire destination.
- Source
- A revised payoff demand received by email from a sender domain not already in the file.
- Check
- Sender, amount, payee, and destination compared against the payoff demand already in the file.
- Result
- Amount, payee, and destination changed. Sender domain was not already documented.
- Limitation
- A revised demand can be legitimate. A document alone does not prove source authority.
- Office action
- Hold revised demand pending trusted-source confirmation.
Callback · known servicer path
- Claim
- The revised demand came from the lender or servicer.
- Source
- The servicer contact path already in the file — not the number from the revised email.
- Check
- Called the known servicer path and asked for confirmation of the revised amount, payee, and destination.
- Result
- No confirmation before the release cutoff. A message and file note were retained.
- Limitation
- No answer does not prove the revised demand is false. It leaves source authority unconfirmed.
- Office action
- Hold until the known servicer path confirms or the file records another office decision.
Stayed open · trusted-source confirmation
- Claim
- The office had a trusted-source basis for the revised payoff demand.
- Source
- None on file.
- Check
- Searched the file for confirmation from the known servicer path or an updated demand from that path.
- Result
- Not present.
- Limitation
- Without it, the file cannot show a trusted-source basis for relying on the revised demand.
- Office action
- Hold pending confirmation. Funds not released.
Callback record
2026-05-26 13:50 UTC — Called through the known servicer path in the file.
Asked the servicer to confirm the revised amount, payee, and wire destination.
No confirmation before cutoff. Message and file note retained.
Outcome: revised demand not confirmed.
Event timeline
Revised payoff demand received by email. Amount, payee, and wire destination differed from the demand in the file.
Sender, amount, payee, and destination compared against the existing demand and file contact path.
Callback placed through the known servicer path in the file. No confirmation received before cutoff.
Trusted-source confirmation requested and noted in the file.
No trusted-source confirmation received. Office decision: hold pending confirmation. Funds not released.
Veto Record signed and recorded.
Use the same shape on one file.
A Veto Record earns its place when an owner can see what changed, what was checked, what stayed open, and what the office did.