FinCense enhances investigation and operational efficiency with these new updates in November. Linked parties are now viewable for screening alerts, showing related entities for each hit. Additionally, screening alert details can be configured within the modular “Further Information” section.

November also brought new APIs for loading customer and party profile data programmatically, via endpoints. Read on for the details.

Linked Party Information

We bring tools for enhanced investigation in the form of the “Related Parties” section, which draws from the configured watchlists. Each identified party can be viewed to show their relationships, and watchlist record and details:

• “Related Parties” section appears per-hit when available
• Clickable identifiers (e.g., W1234567) with Name and relation
• In-place modal shows full details: Name, Aliases, Gender, DOB, Nationality, Type, IDs, Further Information, etc.
• Consistent layout with standard hits; no navigation loss
• Empty-state messaging (“No related parties found”) and graceful error handling

This is available across all our screening products within the alert details.

{{product-cta-1}}

Impact to Our Clients

• Faster triage: Surface connections instantly; fewer context switches and data lookups.
• Deeper understanding: Network view reduces false positives by clarifying relationships.
• Higher investigation quality: Standardised modal ensures consistent evidence capture.

Configurable, Modular Information Blocks

Configure the “Further Information” blocks to aid in investigation of screening alerts, by displaying information in a rich, readable and flexible format. Using JSON schemas, the information interface can be defined in multiple, ordered blocks:

• Information blocks can be individually configured via JSON schema
• Displayed information respects order and metadata defined in JSON
• Default legacy view is used if JSON or block types are invalid

Impact to Our Clients

• Configurable narratives: Present the right facts with the right component (table, list, media, etc).
• Cleaner audits: Structured blocks produce clearer, shareable artefacts.
• Multilingual ready: Works with global language inputs and RTL/CJK layouts.

APIs for Customer Onboarding

Complementing our existing ETL approach, the new APIs for developers allow customer  and party data to be uploaded, and updated in near real-time, in an environment driven by  continuous integration / delivery. This initial development includes:

• Endpoints for create/update/upsert customer/party profiles
• Support for both bulk or single ingestion
• Asynchronous ingestion with job status polling
• Validation errors returned with per‑field detail

This feature works with current ETL jobs, supports multi-language script for easy localisation, and is secured via Keycloak.

Impact to Our Clients

• Quicker time‑to‑value: Automate loads without waiting for ETL windows.
• Lower ops overhead: Idempotent upserts cut re‑runs and manual fixes.
• Governed access: Keycloak‑secured service roles align with enterprise IAM.