Question 1

What is Fenori?

Accepted Answer

Fenori is a private compliance platform for regulated financial institutions. The deployed flagship is 24-hour financial-crime surveillance: continuous monitoring of every customer entity, risk movement explained with citations, cases prepared and routed to officers for judgement. The broader platform spans 16 compliance functions and 89 disciplines and is co-built with design partners. Officers retain decision authority on every regulator-facing action.

Question 2

What is 24-hour surveillance?

Accepted Answer

Fenori's 24-hour surveillance is a continuous monitoring layer that sits above the bank's existing financial-crime stack. Every customer, counterparty, beneficial owner, and signal is watched 24 hours a day. Risk movements are explained with citations. When something matters, Fenori surfaces a case that is already triaged and evidenced. Officers retain decision authority on every regulator-facing action.

Question 3

How does Fenori detect under-reporting risk?

Accepted Answer

Every officer disposition is classified against Fenori's recommendation. The Under-Reporting Risk Monitor continuously tracks high-risk closures, SAR overrides, sanctions escalations cleared, EDD triggers dismissed, missing-evidence closures, and team- or typology-level clearing drift. Anomalies are surfaced for QA sampling and MLRO review, never auto-actioned.

Question 4

Is Fenori on-premises?

Accepted Answer

Yes. Fenori is deployed on hardware inside your institution. Every case file, investigation output, SAR draft, and audit record stays on your premises. No customer data leaves the bank-controlled environment. The deployment requires no inbound network access; all maintenance channels are outbound-only and encrypted.

Question 5

What compliance functions does Fenori cover?

Accepted Answer

Fenori covers 16 compliance functions and 89 disciplines. The flagship 24-hour financial-crime surveillance layer is deployed today across Financial Crime Prevention (AML, KYC, EDD, sanctions, PEP, fraud, trade finance, correspondent banking, tax, audit, regulatory reporting, credit risk). The other 15 functions are on the platform roadmap, co-built with design partners: Market Conduct (MAR, insider dealing, best execution), Operational Resilience (DORA, third-party risk), Prudential and Capital (ICARA, large exposures), Data and Privacy (GDPR, DSAR), Transaction Reporting (EMIR, SFTR), ESG (SFDR, taxonomy), and more.

Question 6

How is Fenori different from other compliance tools?

Accepted Answer

Fenori is built bespoke per institution. Nothing is delivered default. Each deployment is tailored to your data, your policies, your escalation paths, your output formats, and your regulators. It runs on-premises and sits on top of the systems your officers already use rather than replacing them.

Question 7

How do institutions deploy Fenori?

Accepted Answer

Through the Founding Cohort: a 60-day founder-led deployment open to three financial institutions in 2026. Investment is GBP 30,000 covering complete deployment, hardware, founder access, and infrastructure. Founding partners receive 40% off year-one pricing for full commercial conversion.

Question 8

Does Fenori see my data?

Accepted Answer

No. Fenori does not have standing access to your case data. Any remote maintenance access is explicitly logged, time-limited, and revocable by your IT team. Case files, SAR drafts, and audit records remain on your premises and are governed by individual Data Processing Agreements under GDPR Article 28.

Question 9

Does Fenori file SARs autonomously?

Accepted Answer

No. Fenori cannot file, close finally, freeze assets, exit customers, notify regulators, or make final legal determinations autonomously. Fenori drafts SAR narratives, assembles supporting evidence, maps entity networks, and prepares the filing in your regulator's required format, but the MLRO retains full sign-off authority on every submission. Fenori reduces SAR drafting from days to minutes while keeping the human decision gate intact. This applies to STORs, regulatory returns, and board papers as well.

Question 10

How does Fenori handle MLRO sign-off and four-eyes review?

Accepted Answer

Escalation paths, sign-off thresholds, and four-eyes requirements are configured per institution to mirror your internal policy. Senior Manager and MLRO approval gates are baked into the workflow. Fenori prepares evidence packages and recommendations; officers retain decision authority on disposal, escalation, and filing. Every approval is captured in the audit trail with timestamp, identity, and supporting context.

Question 11

Can Fenori be configured to my regulator's filing format?

Accepted Answer

Yes. Filing authorities, output templates, and submission schemas are set at deployment for your jurisdiction. Fenori produces SARs in your FIU's format, regulatory returns in your supervisor's schema (FCA, EBA, FINMA, MAS, BaFin, Finanstilsynet, and others), board papers in your house style, and DSAR responses in your regulator-required structure. Multi-jurisdiction deployments are supported.

Question 12

Does Fenori reduce false positives in transaction monitoring?

Accepted Answer

Yes. Fenori applies weighted risk scoring with transparent calculations and legitimate-explanation tests on every alert. Cross-document reasoning links signals that span source systems and identifies pattern repetition across cases. Typical deployments see order-of-magnitude reductions in unjustified escalations and 15x faster alert disposal, calibrated to your institution's risk appetite and historical baseline.

Question 13

What audit trail does Fenori produce for regulators?

Accepted Answer

Every search, document access, analytical step, model inference, user action, escalation, and approval is captured in an encrypted audit log with seven-year retention. All inferences are cited back to source documents. Full model governance records, prompt logs, and decision provenance are available to internal audit and supervisory examination. Audit records are tamper-evident and remain on your premises.

Question 14

How does Fenori support DORA compliance?

Accepted Answer

Fenori covers DORA obligations end to end including ICT incident classification and regulatory reporting, third-party risk management with vendor due diligence and exit planning, critical third-party regime compliance, business continuity tolerance review, and operational resilience testing. Outputs are formatted for your competent authority's expected templates.

Question 15

What is the difference between Straight-through, Human-in-the-loop, and AI Workspace modes?

Accepted Answer

Straight-through mode handles high-volume dispositions where evidence is conclusive, such as clear direct sanctions screen matches or repeat-pattern fraud signals. Human-in-the-loop mode covers investigations requiring officer judgement, where Fenori prepares the evidence and recommendation and the officer decides. AI Workspace is a conversational environment where compliance officers run ad-hoc investigations, request reports, work on documents, and consult specialist agents for any compliance question. Which mode applies to which discipline is configured per institution. Fenori cannot take any regulator-facing action autonomously regardless of mode.

Question 16

Does Fenori replace our case management system?

Accepted Answer

No. Fenori sits on top of the systems your officers already use. It connects through authenticated read access to your existing case management, transaction monitoring, customer data, and document repositories. Officers continue working in their familiar tools; Fenori contributes investigation output, drafted filings, and evidence packages back into them. Nothing is delivered default, every integration is configured to your stack.

Question 17

How long does Fenori take to deploy?

Accepted Answer

Founding Cohort partners go live in 60 days end to end: weeks 1 to 2 cover hardware shipping, AMS deployment, and officer training; weeks 3 to 4 run real workload with weekly feedback; weeks 5 to 6 settle workflow and gather measurable output quality data; weeks 7 to 8 are the conversion decision window. Standard commercial deployments follow a similar but longer cadence depending on the number of compliance functions activated.