Loading
Because a deal that goes through four revisions leaves a trail spread across email, a chat thread and two attachments. Reconstructing why the price dropped 8% takes an afternoon and produces a guess.
Every issued quote or proposal is kept as a version, with a diff against the one before it, the person who made the change and the reason recorded against it.
Versions are immutable once issued. A new version records what changed at the line level, so the difference between v3 and v4 is a list rather than two documents to compare by eye.
A Bexley Group renegotiation ran to five versions. The history showed the 8% reduction came with two removed line items, which is why the margin held — a fact the quarterly review would otherwise have got wrong.
It records what changed in the document. What was said in the call that prompted the change belongs in the activity timeline, and only if somebody logged it.
Discount approvals attach to the version they governed, e-signature records which version was executed, and Books bills from the accepted one rather than the latest one.
No. A change produces a new version, which is what makes the history worth anything.
Only what you sent them. Internal versions stay internal.
For the life of the record, subject to your retention policy.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.