Skip to main content

​
Refusals and revisions

The distinguishing screens are the ones where GreatBook declines to act and tells the user why. This walkthrough shows only the controls reached on the current local default branch.

​
An empty document does not enter the system

The live preview can render an empty schema while the user is composing. Save is a different operation, and it refuses an untouched document.
Empty supplier VAT invoice builder with a blank live preview

The empty builder is useful as a preview, but it is not yet a document of record.

Typewriter refusing to save an empty document and explaining that at least one field is required

Save is refused in place with a legible reason: fill in at least one field.

​
The maker cannot approve

After save, the author can inspect the rendered PDF and exact stored values. The same page states the separation-of-duties rule and does not offer a usable approval action to the author.
Saved document detail telling its author that they cannot approve their own document

The maker's own document says why another designated approver must sign it.

​
A correction is a new version

Revise does not overwrite the document that existed. It reopens the same schema with the v1 values, saves a new v2, and preserves both in the version history.
Version 1 supplier VAT invoice detail before revision

The original v1 remains a complete document of record before the correction begins.

Revision builder prefilled with version 1 values

Revise opens a prefilled builder headed revising v1.

Revision builder showing corrected quantity and note in the live preview

The corrected quantity and note appear in the live v2 preview before save.

Saved version 2 document showing it is awaiting a separate approval

The saved correction is v2 and still needs its own approval.

Typewriter version history showing current v2 and superseded v1

Version history identifies v2 as current and v1 as superseded; neither record is erased.

Reject, send back, the send-back refusal, and the posting separation-of-duties refusal are not pictured in this capture set. No review row could be created on the local current branch, so those decisions were not staged or reconstructed for screenshots.