Skip to main content
Cogentic
← All release notes

Every finding says where it came from

Case findings are now graded lead or evidence, and a finding that cites nothing is a lead. Sanctions and scam-signal screening become platform capabilities that run on every investigation, a screen no provider answered is reported as unavailable rather than clean, and the identity record your KYC vendor holds finally reaches the agents as evidence they can cite.

2026-10-04

NewImprovementFix

This week the product stopped taking an unsourced claim at face value. Every case finding now carries a grade — evidence if it cites a source, a lead if it does not — and the agents that name a typology or reach a disposition read evidence only. Alongside that, two new screens run on every investigation, your customers' identity records became citable evidence, and a sanctions screen that no provider actually answered now says so instead of reading as clean.

  • NewFindings are graded lead or evidence — every case finding now carries a grade derived from the sources it cites, strictest source wins. A finding that cites nothing, or cites only procedure, is a lead. The typology, disposition and case-naming agents read evidence only, and a lead cited in a decision is dropped. The grade shows as a badge on the case summary.
  • NewCase documents and SOP sections are citable sources — an uploaded case document or a section of your SOP can now be cited by a finding the same way a vendor's answer can. That is what lets an uncited finding be graded a lead: there is now a legitimate source for the evidence that does not come from a vendor.
  • NewSanctions screening runs on every investigation — sanctions becomes a capability in its own right rather than one vendor's call. Cogentic sanctions screening resolves Chainalysis OFAC, OpenSanctions and Breadcrumbs behind a single platform provider and merges their answers. Any provider that could not confirm a list is named on the result, so a clean screen nobody actually checked cannot pass as one.
  • NewScam-signal screening on every address — a sixth capability screens each address as it joins a case, behind one Cogentic product, and derives named signals rather than a bare score. There is deliberately no sanctioned outcome in its vocabulary: a heuristic or community signal is enhanced-due-diligence evidence, never a designation.
  • NewAn OSINT investigation agent inside the case — the scam-signal work now has an agent of its own in the case investigation, producing graded findings alongside the rest.
  • NewYour KYC records reach the agents — the identity record your vendor holds was fetched, verified and shown on every case, and decided nothing. Each cited customer's KYC now reaches the findings agent as citable evidence and the disposition weighs what it produces. The agent sees allow-listed facts and computed ones — age at the alert, whether a document had expired, nationalities from passports and ID cards — never document numbers, email, phone, address or IP address.
  • NewReporting-entity details in settings — record the legal entity that files your regulatory reports, the branch it files from and that branch's address, in Settings → General. They prefill the reporting-entity part of a case report, Part H in the AUSTRAC sample UMR.
  • NewTwo customers can declare the same wallet — an address no longer belongs to exactly one customer. Previously the second customer to declare a whitelisted exchange address was refused, and the refusal threw out their whole record, so that person never reached a case at all: no name, no reference, no KYC. Each wallet also carries an optional custody declaration, and a shared unhosted wallet is flagged in the investigation.
  • NewSay how a customer was onboarded, and who holds the wallet — the customer push now takes a KYC method of direct or reliance, with the partner named under reliance, and a wallet's custody carries the custodian for a hosted wallet. Under reliance your organisation keeps the liability while the records sit with the partner, so the partner is the fact worth carrying onto the case.
  • NewConfirm or dismiss a suggested customer — a customer the product suggested on a case could be seen but not acted on, so the suggestion stayed pending for the life of the case. Each suggested customer now offers Confirm and Dismiss.
  • NewConnect your own Arkham key — Arkham becomes a vendor your organisation connects with its own key, rather than one the platform supplies. The platform attribution provider is now Cogentic screening, which resolves Routescan explorer nametags and Breadcrumbs behind a single name.
  • ImprovedA sanctions screen nobody answered is unavailable, not clean — when no provider answers for an address, that screen is now reported as unavailable and a false-positive close is held for the run. A provider that is not configured, or that fails beside another that did answer, is no longer reported to the case officer, the agents or chat. Before this a missing key could produce a clean screen, or hold a case over wording that pointed at configuration rather than the investigation.
  • ImprovedCustomers are a card on the case summary — cited customers moved out of the case header, which is meant for a glance, into their own card on the Summary tab beside Transfers. Each row carries the basis for the citation, any name mismatch or stale record, and the actions. The header keeps a count that links to the card, and the review banner counts pending customer suggestions beside transfers.
  • ImprovedCase tabs at the top — the case page's tabs move to the top with a slimmer Dossier, and the customer layout is now the same across every sheet that shows one.
  • FixedA customer pushed with a user identifier was invisible to the KYC vendor — the product asked the vendor by applicant ID regardless of what kind of identifier your organisation had actually pushed. A customer pushed with an external user identifier was looked up as an applicant ID and refused on every investigation. The lookup now follows the identifier's type, and a mismatch between the two is flagged on the case rather than hiding the customer.
  • FixedApplicant not found is an answer, not an outage — a vendor's 404 for a customer who was never onboarded, or was onboarded under a different identifier, was treated as a failed call and surfaced as an error. It is now recorded as a not-found verification finding, which is what it is.
  • FixedReport drafts lost what you typed after an invalid field — a value outside its bounds or a malformed date refused the autosave, which dropped everything entered after it. Those now save in a draft and show the reason under the field, and the report is refused at submit with the same words. Caps that protect the export still block the save, because that value must never reach the record.
Design partnersFounding pricing, locked. And a say in what we build next.