Skip to main content
Release notes

The Inbox

The Inbox is now the home page and ranks an officer's day by SLA, severity and due date. Organisations choose which alerts to bring in, which to investigate and how far back to import. The AUSTRAC suspicious matter report gains a transaction schedule, a prefill matched against lodged reports and a filed report that Cogentic stores once.

  • Release 2026-11-08
  • 7 new
  • 8 improved
  • 5 fixed

In this release

An officer used to open Cogentic on the Today page and work out where to start. The Inbox is now the home page. It ranks alerts, cases, reports and reviews in one order, with chat beside it.

Organisations now set how alerts arrive. A lookback brings in history, one threshold decides what Cogentic stores and a second decides what it investigates. An investigation runs only when an alert or an officer asks for one.

The AUSTRAC suspicious matter report gains a transaction schedule and a prefill matched against lodged reports. Cogentic stores a filed report's file once and hands over the copy the regulator received.

New7

Inbox

an officer now lands on the Inbox. The sidebar logo, onboarding, the organisation switcher and the error pages all go there, and the old Today and chat pages redirect to it.

The Inbox opens with a greeting and a sentence on where to start, drawn from what is past its SLA, what is due and the reports to finish or review. Your work shows four counts, and each opens a sheet: alerts to review on your cases by severity, cases assigned to you by SLA, reports by status then case, and report reviews oldest first with the time waiting.

Decide and Unassigned hold cards that open a sheet with the case's Dossier and summary. Skip moves to the next card. This week lists overdue work first, then each working day. One ranking runs throughout: past SLA first, then severity, then soonest due. Each top pick gives a short reason, such as "4 hours past SLA" or "Critical · due tomorrow".

A case still named after a vendor's identifiers now reads as its alert and subject, such as "Chainalysis alert" and the subject's name. The badge keeps the identifier. Officer feedback set the labels: "Alerts to review", "Report reviews", "Before today", "SLA due" and "Investigation running".

The ask bar suggests two questions from the officer's day. Asking opens the general chat in the Inbox's left rail, so the answer streams beside the work. The general chat can now read a case and answer "Why is CASE-2 past its SLA?" from it. It cannot change a case.

Existing alerts

each know-your-transaction integration (Chainalysis, Crystal and Elliptic) gains an Existing alerts card. An officer picks a lookback of none, 1, 3, 6 or 12 months. The card replaces the raw earliest-alert-date input.

After each live pass, the poll reads a few pages of the chosen range, oldest first, and saves its position after every page. The import applies the same filters as live alerts: severity floor, alert types, networks, assets and workflow statuses.

Imported alerts go on no case. They wait on a new Not on a case tab on the Alerts page, newest vendor date first. Each row has an Open case action that groups the alert with an open case on the same subject or opens a new one. Add to this case in case chat does the same.

Cogentic runs no enrichment and no investigation on an imported alert until an officer opens a case for it. Re-running, lengthening or shortening the lookback does not duplicate an alert.

Investigate threshold

each alert provider now has two thresholds where it had one minimum severity, grade or risk score. Bring in at or above is the existing floor and decides what Cogentic stores. Investigate at or above is new and decides what gets a case and an investigation.

Cogentic records an alert below the investigate threshold with no case, and it waits on the Not on a case tab. An organisation can bring Low alerts in and investigate only those above Medium.

An unset investigate threshold matches the floor, so existing integrations behave as before until an officer changes it. The investigate threshold cannot sit below the floor. The audit log records both the old and new values whenever a save moves either.

Bridge transfers

a bridge deposit used to read as a plain transfer, hiding that the funds left the chain. A bridge router that handed a token straight back read as a swap. Typing looked only at the transfer's shape.

Cogentic now recognises a bridge by its counterparty, in two ways. A registry lists 42 bridge contracts across Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, Scroll and Blast, each citing the bridge's own deployment list. Vendor attribution also counts where the vendor categorises the counterparty as a bridge.

A Bridge chip shows on every transfer row and in the transfer sheet's Type row. Map nodes draw as bridges and map edges carry a bridge count. The evidence records which basis typed each leg.

Cogentic does not yet link the destination-chain transfer. There is no backfill, so this applies to transfers typed from now on.

Transaction schedule

lodged reports key only the transactions their grounds turn on and put the rest in an attached spreadsheet, with each keyed transaction citing its row.

A draft report's attachments field now has a Generate transaction schedule button. The schedule lists every transfer on the case, oldest first, numbered T-1 onwards. Times are in Sydney time, units are exact and money is to the cent in both the organisation's currency and US dollars.

The report's transaction reference prefills from the schedule row, or from Cogentic's own reference when there is no schedule. Filing pins the schedule like any other attachment, and the AUSTRAC file embeds it. A transfer added to the case after you generate the schedule has no row until you generate it again.

Unidentified parties

an officer can now mark a non-customer party as unidentified. The party carries a description in the officer's words in place of a name, and records whether an image or recording is held.

An unidentified party holds no legal name, so Cogentic never stores or files the description as one. The party reads as "Unidentified person/company" everywhere, so no agent, web search or report row takes the description for a name.

From that version, the AUSTRAC report answers "Has the party been identified?" with No. It fills the description, the image answer and contact details, and leaves out every identified-only answer AUSTRAC refuses.

Improved8

Investigation runs: every evidence edit used to queue an investigation run, so an officer working a case started runs they never asked for.

A run now starts for two reasons. An alert: a new alert opens a case, or a different alert joins one. An officer: through the Investigate action, the Start investigation dialog or the case agent's tool.

An evidence edit, such as adding or removing a citation, reference, document, subject, wallet or party, now stamps the case. So does an accepted suggestion. The case then shows a banner reading "Evidence has changed since the last investigation" with an Investigate action. Enrichment still runs on an evidence edit.

AUSTRAC prefill: we compared the prefill with two reports lodged outside Cogentic. Each change below makes the prefill match what those reports lodged.

Where the business issued an asset into its customer's wallet, the prefill names the customer as payer with no payee. It prefers a verified document, such as a driver's licence or passport, over a vendor's online verification, and uses the online verification only when the party has nothing else.

Service and online-activity spans are date-only. "Date suspicion formed", "date reported" and the service span use Sydney days in place of UTC days. The officer enters transaction time in their own time zone, so a time copied from a Sydney-time schedule no longer lands 10 or 11 hours out. The AUSTRAC file still states Sydney time.

More of the form now prefills: transaction type for a purchase or sale of an issued asset, exchange rate, who controls and holds the asset, the accounts table from the case's wallets and the parties table from its customers. Escalating an unusual matter report carries across the reasons into "Crime type or threat", the case customer on each party and the other agencies reported to.

Templates follow the organisation's jurisdiction. The library lists its own regulators first, and a new report offers only the case's jurisdiction. Default answers is now its own page in the Reporting settings, beside Templates and Review.

AUSTRAC field mapping: each field on the AUSTRAC suspicious matter report template now records where its answer lands in the regulator's file. Publishing a regulator template verifies that mapping. A field with no place to land blocks publishing, and Cogentic names it.

We compared the generated file, part by part, with two reports lodged outside Cogentic, as AUSTRAC recorded them in its submission summaries. Sydney-time dates and times, party types, codes, party links, date ranges and identification all match.

The comparison found one difference, now fixed. The grounds for suspicion keep a blank line between paragraphs, as AUSTRAC prints them. They no longer render as one block.

No data from those filings is in Cogentic's systems, and the test fixtures are fictional. An end-to-end test now adopts the AUSTRAC template from the library, prefills a report on a case and downloads a file that validates against AUSTRAC's own schema.

Filed reports: every export of a filed report used to render it again. A later change could alter a filed report's contents or stop it exporting. The same report could also go out under several AUSTRAC file names, each spending one of the organisation's daily allowance.

The first export of a filed report's PDF or AUSTRAC file now stores that file with its name, size and checksum. Every later export hands over the same stored file. Working copies, the Word, CSV and workbook exports and any draft's export still render fresh.

A lodgement now names the exact file the regulator received. If nobody downloaded a report's filed form, the officer cannot record it as lodged and Cogentic asks them to download it first. Reports filed before this adopt their earliest export after filing as the filed file, so a lodged report keeps the contents the regulator received.

Nobody, in any role, can now delete a case holding a filed report. AUSTRAC requires a reporting entity to keep those reports.

Checks before review: an author stuck on a field could not send the report to a reviewer to ask how to answer it. Checks now lets a report go to review with wrong answers, each shown as a note that the reviewer must fix before approving. Filing without review still stops at Checks, and approval still refuses a wrong answer.

Case Summary: the Analysis card leads with the summary, then Typology, What we found and Procedure relied on. Cited findings come first in citation order, and uncited ones follow under their own label. Each finding leads with a chip, and a meta line gives the severity, the source kind and the vendor's name, which opens the source.

Procedure relied on is a summary card with the version and the sections the agent relied on, each quoting the clause it read. Citations are larger and open the finding in a sheet.

The decision form now carries a reason the agent drafts for the decision chosen, naming the reviewer for an escalation and marked "Drafted by Cogentic". It never replaces a reason the officer has written. On a case with no owner, the recommendation line offers "Assign to me".

The Dossier now states received and sent exposure apart, plus exposure with no direction reported, so the figures add up to the total. The verdict bar names up to five risky counterparties, most severe first, and folds the rest by band. The exposure table has a sortable Risk column. The risk score sits in the header row beside the assignee. A pending role suggestion has its own panel, headed "Suggested role: Suspect", with Accept, Edit and Dismiss.

Case map Trace: node and transfer sheets open wider. A click outside a transfer sheet stacked over a node sheet closes only the transfer sheet.

Trace gains a one-line explainer, and its filters sit in a labelled form behind "Transfer filter": trace transfer, direction, asset, window, before/after and address. View (List or By address) and Times (Relative or Absolute) are labelled toggles above the results. Each row opens the transfer sheet and has pin and unpin buttons, plus a menu to filter by the address, copy the address or copy the hash.

Fixed5

  • Adding a wallet from chat

    the chat Set subject card used to replace every live subject on the case. It now adds the wallet beside the existing ones and removes nothing. Cogentic reports a wallet already on the case, and reports a closed case as closed. The link starts with no role, so the investigation can still suggest one and the officer sets it separately. Cards already waiting in existing conversations still work.

  • Why it is cited

    when an officer accepted a suggested transfer, the reason Cogentic suggested it disappeared and left only a note restating the movement.

    Cogentic now keeps the reason and shows it on the transfer's row in Linked transfers, in a "Why it is cited" section on the transfer sheet and in the link history, each marked "Suggested by Cogentic". A transfer the officer added keeps the officer's own note, unmarked. This applies to citations from now on. The audit log is immutable, so earlier entries keep the restated movement.

  • Approver notes

    maker/checker asks an approver for a note when they partly wrote the report. Creating, sending or editing it as an earlier reviewer already left a record. Editing the draft did not.

    Cogentic now records a member's first real edit to a draft, and approval compares it with the point the review was requested. The approver sees "You worked on this report before this review. Add a note before approving it." An automatic save of a fresh draft's prefill does not count, and neither does a save that changes nothing. Cogentic did not record saves made before this shipped.

  • Report loading and autosave

    a failed request used to read as an empty record, so an officer could conclude nothing was filed, or file a duplicate.

    The Reports tab, the templates list, an open report and the Summary report cards now each say when they could not load, with Retry. "May have been deleted" shows only when the report is gone.

    A failed autosave shows a notice with "Retry now" and a status reading "Not saved. Retrying…". Cogentic retries after 2, 5 and 15 seconds, then every 30 seconds. It does not retry a save refused for the session, and asks the officer to sign in again. Closing or reloading the tab with an unsaved edit now asks first. Undoing an edit back to the saved value clears the failure.

  • Case page scroll

    every load of a case link scrolled the page down shortly after it painted and pushed the case header out of view. An officer opening a case from the board saw the jump. The case link now reaches the Summary with no second navigation, so the page stays put.