Final submission approval
Use this guide when an authorization asks for approve_submission. This is the
review step before an irreversible payer submit boundary.
When approval appears
approve_submission can appear when:
- the authorization was created with
policy.finalSubmission = requires_approval - Collate reached the final payer-submit boundary
- sandbox or another safety gate prevents automatic final submit
- Collate needs reviewer acknowledgement before a submit-capable manual handoff
Do not assume approval appears only for one policy value. Always follow the current authorization response.
Review snapshot
submission.reviewSnapshot is embedded on the authorization.
Route summary, answers, attachments, and warnings to the approval
authority. That can be a reviewer, a policy service, or another controlled
backend process. Treat warnings as approval-visible information, not validation
errors.
Approve
Read the latest authorization
Read immediately before approval so the reviewer sees the current snapshot.
Stale snapshots
Answer or attachment writes can change the package. If you approve an old
snapshot, the API returns 409 review_stale.
Recover by reading the latest authorization, presenting the new snapshot, and
confirming with the new authorization version and snapshot ID.
Live review
Use Live sessions to show a read-only payer-channel view while the case is active. Live-session grants are transparency tools; the authorization remains the source of truth for whether final approval is open.