2026-10-18
NewImprovementFixA report used to be a form with a name. It now knows which regulatory form it implements, so an unusual matter report can be escalated to a suspicious matter report on the same case, with the answers that still apply carried across and the ones left behind named with their reason.
Alongside that: AUSTRAC's suspicious matter report v3.0 as an official template you adopt rather than build, a setup flow for a new organisation that ends with your AML/CTF programme in place, and agent reasoning whose numbered citations point at real findings.
- NewReport types, and escalating an unusual matter report to a suspicious matter report — a report template now declares the regulatory form it implements: unusual matter report, AUSTRAC suspicious matter report, threshold transaction report, international funds transfer instruction or other. You set it in the template builder. A report copies it when created and keeps it, and an amendment carries it. Report cards and picker cards show the type as a badge, and starting a report of a type the case already has a live draft of warns you, naming that draft, without blocking. A submitted unusual matter report's menu now offers Escalate to SMR. It is refused on a draft, so the record keeps the unusual matter as it stood when suspicion was formed. The dialog asks which suspicious matter report template to use and for the basis for suspicion, which is required, then creates a new suspicious matter report draft on the same case, linked to the unusual matter report, which is not superseded. Both cards show the link, and an audit event records both reports and the basis. Reports created before report types existed stay untyped and do not offer Escalate to SMR; there is no backfill, so set the type on the template and new reports pick it up.
- NewAUSTRAC suspicious matter report v3.0 in a template library — Settings → Report templates now has a Template library above your own templates. Each entry shows its schema version, the regulator, its field count, the deadline and the jurisdiction, and shows AUSTRAC's test file assessment requirement before you adopt. Preview opens the full form, fillable but not saved. Adopt adds it to your list in one action and it is immediately fillable; adopting twice is refused, and adopting is audited. Official templates are read-only: save, publish and discard all refuse them, and every template in your list is marked Official, Internal (previously Authored) or Fork. Only a report started from the official template reads Conforms to AUSTRAC Suspicious matter report v3.0. The template itself carries 157 fields in ten sections, from the reporting entity and who formed the suspicion through grounds for suspicion, involved parties, related transactions and other Australian government agencies to attachments. Every coded answer stores AUSTRAC's own code, across 15 answer lists including all 52 designated services, and AUSTRAC's conditional rules are quoted word for word in each field's help until conditional fields land.
- NewEscalation carries the unusual matter report's answers across — when you escalate, the answers that still apply move to the suspicious matter report draft. Answers are matched by what a field means rather than by its label, so a relabelled, retyped, reordered or moved field still carries, and older templates and already-filed unusual matter reports carry too. Offence and designated-service codes are translated into AUSTRAC's, and an option that could map two ways is deliberately left out rather than guessed. An answer the suspicious matter report refuses is not copied, and each one left behind is named with its reason. You are told how many answers came across and how many stayed behind.
- NewA setup flow for a new organisation — creating an organisation now runs About you, Your organisation, Invite your team, AML/CTF programme and Ready. About you takes your name and an optional time zone, and saves before an organisation exists. Your organisation takes the name, live or sandbox and the reporting currency. Invite your team stages invites with an email and a role, Member or Admin; a failed invite stays listed with its error, and Skip moves on. AML/CTF programme takes your programme documents, each listed with its status. A Your workspace preview fills in as you answer, and Ready links to integrations, policies and report templates in the new workspace. Joining by invitation is unchanged, and sign-in itself stays at your identity provider. The sign-out and authentication error pages were rebuilt on the same design.
- ImprovedA recommendation's reasoning cites its evidence — the agent's written reasoning on a case now carries numbered citations. Each number is a chip: hovering reads the finding it cites and clicking scrolls to it in the evidence list, where cited findings show their number. Before this, the stored reasoning was written in a second, separate pass with a generic prompt, so the numbers could not match the evidence and none of our writing rules applied to the text actually stored. The reasoning and the evidence are now written in one pass, evidence first, so a number always points at a real finding and is limited to a claim that finding states, and a procedure is named by its document title. Headings, which the prompt had always forbidden, also stopped appearing.
- ImprovedThe reporting workspace — the report editor has a header pinned under the case strip that shows which part you are in, with a jump-to-part menu. The report's transactions are now picked from the case: tick the case's transfers to add them, or add one by hand. The templates page has two tabs, Templates and Library templates, with counts; your templates are grouped under Internal and Official, each row leading with its report type, and the library tab opens with an explainer card where an adopted entry reads In use and View in Templates switches tab and scrolls to it. The template builder header now says where the template stands: Unpublished changes with a Publish button, All changes published with no button or Publish disabled with the reason on hover for a template with no fields or no name. The amendment entry on the report menu now reads Open amendment with a Draft or Filed badge, because Correct lodgement is a different action on the same menu. The reporting currency picker from Settings is shared with onboarding, searchable by code or name. A submit now also refuses an answer too long for its field, an option or jurisdiction it does not know or a table past its row limit. Reports filed before this change keep their exact documents, so an earlier filing still renders and its signature is unaffected. View on map is hidden when a case has no transfers, and suspicious matter report part names and descriptions were rewritten in plain terms.
- ImprovedTimes the agent writes are normalised — the case agent was rewriting times it had been given, so the product could no longer recognise a time and show it in the reader's own zone. Every time in agent prose is now checked against the times its tools actually returned and rewritten from the returned instant. A workflow time, such as alert received, case opened or a due date, shows in each reader's own zone; an on-chain or vendor time stays in UTC, as it does on the case page. A time no tool returned is reduced to its label or left as written rather than presented as a linked instant.
- FixedA form lodged with a regulator can no longer be forked — the official AUSTRAC suspicious matter report, threshold transaction report and international funds transfer instruction templates can no longer be forked. A fork drifts from the schema the lodgement is built from and stops following the regulator's revisions. The official template view hides Fork and says why. Internal forms, such as an unusual matter report, still fork.
- FixedPinning one side of a swap — when an officer pinned one side of a swap from the case map, that side was recorded as a plain transfer rather than a swap, and the other side was never suggested. A pinned side is now read against the whole transaction, and when it is a swap the sides the pin left out are suggested. Pinning a transfer the case had only suggested now confirms that suggestion instead of being refused as a duplicate; the officer's own relationship and note are kept, and they are recorded as the author so they can edit the note they wrote. Sides pinned from the map before this fix may already be stored as a plain transfer, and because a known type is never overwritten they stay as they are.