01
Gather the right information
Record the agreed information or the document’s digital fingerprint.
Use cases
Know when an important record changes.
Create a signed record of a document or approval so later versions can be compared with the original.
Documents & approvals
Documents & approvals: the decision behind the check
A changed payment amount or contract field may be visually easy to miss. Compare the exact received version against the signed evidence and route a mismatch to the responsible issuer; a familiar filename is not enough.
Use cases
Documents & approvals workflow
02
Make the checks visible
Compare the presented information with the signed record.
03
Keep the next step clear
Share the result and ask the issuer to resolve any differences.
Details and limitations
Documents & approvals: practical requirements
Who uses which workspace
The team responsible for the document creates its record through Console or an integrated application. Record the exact version being approved and retain the original file. A recipient needs that file if only its fingerprint was recorded. Two documents with the same filename can contain different bytes, while a format conversion can change bytes without changing the reader's interpretation.
A focused acceptance exercise
Approve a test document, share its evidence and compare an altered amount in a separate copy. Test how the team handles a legitimate revision and whether recipients can find the previous version. Do not describe an unsigned attachment as fraudulent solely because there is no compatible record to compare it with.