Governed GRN presentation timing

Overview

GRN timing is a presentation and controlled-document rule; it does not create a second receipt workflow. Moduvio owns four fixed lifecycle stages: RECEIPT_RECORDED, QUARANTINE_POSTED, INSPECTION_DISPOSED and INSPECTION_ACCEPTED. A tenant rule may select from these stages using only the supported declarative fields—never tenant code, SQL or callbacks.

A new receipt created while a policy is published pins the exact immutable policy version, rule, stage catalogue, evaluation context and checksums. A later policy publication applies only to later receipts. Receipts created before timing governance retain LEGACY_NO_POLICY immediate presentation, while a new receipt whose published definition cannot be verified records POLICY_ERROR and fails closed only for presentation and document issuance.

Tenant Administrators operate the governed lifecycle in the GRN timing policies screen. Receipt readers see the exact timing mode, reached stages, pinned rule and hashes from Goods receipts → View; authorised receipt writers can issue the eligible record there. This bounded UI does not add a generic document-template screen. The controlled issuance has one fixed GOODS_RECEIPT_NOTE contract and one code-owned GRN_PDF_RENDERER_V1 artefact. Both are created once from the same immutable payload and are idempotent for the receipt. An authorised grn_document:download user may retrieve the encrypted-at-rest, checksummed PDF through an authenticated audited route. Issuance and download never print, email, publish or deliver externally and never change authority allocation, physical receipt, quarantine, inspection, custody, current stock or stock-ledger order.

What to do

1. 1
   Inspect the fixed catalogue

   As Tenant Administrator, open Administration → GRN timing policies. Review the four server-owned stages, catalogue version and checksum before drafting.

2. 2
   Draft safely

   Create a policy or replacement version with ordered, non-ambiguous rules using only receipt source, authority type, classification, procurement mode, category, criticality or route predicates.

3. 3
   Validate and simulate

   Validate the exact draft, open Simulate, enter representative receipt facts and retain the resolved rule and result hash. Both operations are zero-domain-side-effect checks.

4. 4
   Publish independently

   Submit the validated, successfully simulated version. A different Tenant Administrator reviews and publishes it; the author or submitter cannot publish their own version.

5. 5
   Verify each receipt

   Open Goods receipts, find the receipt and choose View. Compare reached stages with the exact pinned presentation and document-issuance thresholds; legacy-immediate and policy-error modes are explicit.

6. 6
   Issue once eligible

   An authorised receipt writer enters an Issuance note and chooses Issue controlled record. This freezes one JSON payload and one PDF artefact; reopening or retrying returns the same issuance and PDF identity rather than rendering again.

7. 7
   Download with separate authority

   A user with receipt read, site/clearance scope and grn_document:download chooses Download PDF. Moduvio verifies the stored PDF hash and size and audits the read; it performs no external delivery or domain transition.

Continue learning