User Guide

What a report's status means

Every report in your cabinet carries one status:

Filtering. The cabinet's status filter narrows the list by any of these — Submitted / Processing / In review / Reviewed / Locked. Over the API the same lifecycle is reported as raw tokens — see the FAQ below.

When your report is in review

GVN automatically checks each report against your organization's reference data. If something does not add up, the report is queued for a human reviewer. You do not need to do anything — the review happens on the reviewer's side, and your report stays visible in your cabinet throughout.

When a reviewer is involved, the report's detail view shows one of three notices:

• In review — A reviewer is looking at this report. No action needed from you; corrections you have left remain available until the report locks.
• A reviewer made a correction — A reviewer recorded a corrected version. Your original is kept. The corrected text is a new version in the ledger, attributed to the reviewer; nothing you wrote is overwritten.
• Reviewed — no change needed — the reviewer confirmed your report as submitted and closed the review.

Either way the report ends at Reviewed, and its full version history — your original, your corrections, and any reviewer correction — stays on the record in the version ledger.

How a report locks

A report becomes Locked in one of three ways:

1. The third correction. Each report allows 3 corrections; using the third locks it on the spot: This report is locked — all 3 corrections used. Locked reports can't be edited.
2. Locking early. You do not have to use all 3. Press Lock report now in the report's detail view (or call POST /v1/transaction/{id}/finalize over the API) to finalize with corrections to spare. Locking early is irreversible: This report is locked — you finalized it early. Locked reports can't be edited.
3. A reviewer locks it. A reviewer can lock a report out-of-band (with a reason, recorded in the audit log) — typically to freeze a flagged report before resolving it.

Locked is not the end of the story. A locked report can still be reviewed — in fact, locking is the precondition: a reviewer can only resolve a flagged report after it is locked.

For reviewers: flags, resolution, rules

This section is for the admin role — the reviewer working in the admin console.

The queue and what each flag means

The admin report list surfaces flagged reports first, and the strip above it sums the queue in one glance: Needs attention: N mismatched · M unverifiable · K not verified (or All clear when nothing is flagged). A report's flag is the strictest open finding of the automated checks:

Resolving a flagged report, step by step

1. Lock the report first. Resolution runs only on a locked report — resolving an unlocked one is refused with 409 LOCK_REQUIRED: This report must be locked before it can be resolved. The report may already be locked (third correction, or the submitter's early lock); otherwise use the admin lock, which asks for a reason and writes it to the audit log.
2. Choose how to resolve. Open the report and press Resolve flag. Two ways:
   • Record a corrected version — records a new version authored by you (marked as reviewer). The original and every prior version are kept. Requires the full corrected text. It advances the report's corrections counter like any corrected version, but it cannot cost the submitter an edit — the report is already locked.
   • Confirm the report is correct — the text stands; the flag is dismissed with your reason. No new version.
   Both paths require a reason, and every resolution is written to the report log.
3. The report becomes Reviewed — and stays there. Reviewed is terminal: there is no reopen, and a second resolution of the same report is refused. The full trail — flag, lock, resolution, reason — remains in the report log.

Rules

The Rules tab lists the automated checks. Turn each rule on or off — an inactive rule is skipped by the engine and never flags a report. Rules are authored in code; to change or add a rule, contact your developer.

Questions submitters ask

Does a reviewer's correction use up my 3 corrections? It cannot cost you an edit: a reviewer only acts on a report that is already locked, and a locked report accepts no further corrections from you either way. The counter (Corrections 1 / 3 · 2 remaining) does count every corrected version in the ledger — so a reviewer's correction advances it too, marked as reviewer in the version history.

Can I edit a report after it is Reviewed? No. Reviewed is final — like Locked, it accepts no further corrections. The full version history stays visible in the ledger.

Will I lose my text if a reviewer corrects my report? No — corrections never overwrite. Your original is kept, along with every prior version, and the reviewer's text is simply the next version in the ledger.

My report says "Processing" again after I corrected it — is that right? Yes. A correction sends the report back through the automated checks: it reads Processing while they run, then returns to In review. The status stops changing when the report locks.

What statuses does the API return? The API reports the underlying lifecycle tokens; the cabinet shows the same lifecycle 1:1: SUBMITTED (Submitted), PROCESSING (Processing), REVIEW (In review), LOCKED (Locked) and REVIEWED (Reviewed). See GET /v1/transaction/{id} in the API reference.