Maker/checker review for reports

a report can now go to a reviewer before it is filed. The author sends it to any member other than themselves, with an optional message, and the report moves from draft to in review. Only the assigned reviewer can approve, and approval freezes and signs the report through the same step submitting uses: the AUSTRAC check, attachment pinning, the content hash and the signer. The approver is recorded as the signer and the report is marked as reviewed.

The reviewer can send it back with a reason, which returns it to draft; the author or requester can withdraw it; and the author, the reviewer or an Owner or Admin can reassign it. While a report is in review only the assigned reviewer can save it, and archiving is refused until the review is withdrawn. Filing without review is still allowed and is recorded as not reviewed, unless your organisation turns on the setting that makes review compulsory. That setting refuses to turn on for an organisation with fewer than two members who can edit reports.

A Reviews page groups reports by the day they were sent; each row expands to its case with transfers, alerts and reports, and carries a Review button. Today gained a Reports for review list above alerts for review, and the greeting counts them.

The reviewer is emailed when a report is sent for review or reassigned, and the requester when it is sent back or approved. Those emails carry no free text: not the review message, the send-back reason, the approval note or the report's title. These are draft suspicious matter reports, and that text would otherwise sit in mailboxes and lock-screen previews outside the product's access control and audit trail. The email names the case and the report reference and links to it.

an empty required answer no longer files silently. The officer gives a reason for each one, once, when the report leaves their hands. On send for review the author gives a reason for each empty required answer. On approve the author's reasons are read-only and the approver gives a reason only for a gap nobody explained, which replaces the earlier "Approve with N required answers empty" checkbox. Filing without review shows a new dialog only when there are gaps; with none, Submit files straight away as before.

Each reason is limited to 1,000 characters and a shortcut applies the same reason to the rest. The reasons appear under each empty answer on the review screen, the shareable report page and the PDF and Word exports. They are not in the AUSTRAC XML, which has no place for them. An amendment carries its original's reasons.

Submit and Approve are now three-step sheets: Submit runs Fields, Checks then Reviewer, and Approve runs Fields, Checks then Confirm. Fields leads with the count, such as "4 empty fields need a reason", then who explained the rest and when, then the fields still owed a reason; "view missing fields" lists every field by part so any one can be changed. Checks blocks filing on answers in the wrong format and warns about case transfers left out of Part F without blocking.

The AUSTRAC check, the same one filing refuses on, now runs under Checks: it blocks Approve and "file now", and shows as a note when sending for review. Reviewer offers "send for review" or "file now", with reviewer avatars and an optional message, and the button names the action. A completed step can be clicked to go back, and closing a sheet keeps its draft until the report is sent or approved.

Viewer already existed as a role: every write outside a small allowlist was refused and a Viewer was never assigned to a case. But the interface still showed a Viewer every write control, so each click ended in an error. A Viewer now sees a "View only" badge and does not see controls they cannot use, across cases, chat, reports, documents and settings. The report editor opens read-only, with no form, Save, Submit or autosave; previously autosave saved a new draft's defaults the moment a Viewer opened it, and the write was then refused.

An admin can invite a Viewer or change an existing member to one. Before the change the product asks for confirmation and says the member's open cases will be unassigned and they will stop being a default assignee, and it does both together with the change. A write that does get past the interface is refused and now reads "Your access is view-only." Viewers can still download documents.

a case could carry many subject wallets but each investigation screened only one, so an officer working a customer with 30 wallets got evidence about one of them while the agents were told about all 30. Screening all of them on every run would multiply what the vendors cost, so each run now picks at most 5 subject wallets needing fresh vendor screens, plus wallets whose existing evidence is still reusable, up to 20 wallets in total.

Officer requests go first, oldest first, then wallets never attempted, then wallets by last attempt. The order converges over successive runs, so a wallet whose vendor keeps erroring cannot starve the others. At most 5 distinct transfer counterparties are screened per run, never-tried ones first. Evidence counts as reusable while the know-your-transaction, sanctions (7 days) and open-source intelligence (24 hours) results are all still fresh.

You can ask for specific subjects to be screened, each subject shows its screening state and when it was last screened, and the case shows its coverage as a count of wallets screened against the total, excluding wallets on chains that cannot be investigated. The agent cannot recommend closing a case as a false positive while a screenable wallet is unscreened. Each subject is screened separately, and a sanctions fact reads "Screened" rather than "No hits".

each "procedure relied on" row on a case named the cited section by heading, document and version and nothing else, so to see what a recommendation rested on you had to find the document in Settings, open the right version and hunt for the section. The document name and version is now a link that opens a sheet showing the exact text the agent read for that section, word for word, with a button to download the document version it came from.

A citation is stored as a line span of one published version, and published versions cannot be edited, so republishing a document as a new version does not change what an older citation shows. A procedure written inside Cogentic has no file to download, so the sheet shows the extract alone. If the document was deleted the row stays plain text and the sheet says the text is no longer available. If the recommendation was rewritten since the page loaded, the sheet says so and asks for a reload. The extract loads when the sheet opens, not with the case page.

your organisation can now store default answers. They are applied once, when a report is created and when a table row is added or carried in; an existing report never changes because a setting changed. Defaults and case data join on what a field means rather than on its identifier, so they survive relabelling, and a stored answer to a question no longer offered is ignored. The recommended set is chosen to be AUSTRAC-safe: account type is a virtual asset wallet, and there is no default for account holder, which AUSTRAC refuses for that account type, or for whether the party is an individual or a business, which the customer picker answers.

Reporting settings is now one page with Entity, Reviews and Defaults tabs, replacing the separate filing-details and default-answers pages. Only an Owner or Admin can change them, and changes are audited. Escalation's notice also changed: when answers are left behind it names a left-behind table column once with a row count, grouped by report part and collapsible, instead of one line per cell, and an escalated report shows a strip naming the report it escalated to or came from.