Skip to content
Integrations

Runs with what you already run.

Compliance software integrations for regulated firms, by name: the administered book from Quantios Core, screening through ComplyAdvantage or your own World-Check One or Dow Jones licence, identity verification with Sumsub, GBG and ID-Pal, evidence in your own SharePoint tenancy, company facts from public registries such as Companies House, Microsoft Entra ID sign-on, one-click exports, and your existing registers and histories brought in at onboarding.

Runs with

The ecosystem, by name.

The systems the platform syncs with, screens through and signs in from. Bring-your-own providers run under the screening licence your firm already holds, at no extra charge.

  • MicrosoftEntra ID · SharePoint
  • Quantios CoreClient book sync
  • ComplyAdvantageCommercial-grade screening
  • World-Check OneScreening · your licence
  • Dow JonesScreening · your licence
  • OpenSanctionsBaseline screening data
  • SumsubIdentity verification
  • GBGIdentity verification
  • ID-PalIdentity verification
  • Companies HouseRegistry pre-fill · watch
  • OpenAPIThe documented API

The integrations

  • Client book sync

    Quantios Core

    Your administered book syncs from Quantios Core: the entities you run there are the entities you monitor here, with structure, licence type and jurisdiction driving what the obligations library, the risk taxonomy and the starter controls populate for each. Nothing is re-keyed, and no entity is missed because it was not on the list that day.

    The Entities module

  • Sanctions, PEP, adverse media

    Screening providers

    Client screening runs against sanctions, PEP and adverse-media lists at take-on and continuously after it. Baseline screening, built on OpenSanctions data, is bundled with every plan; commercial-grade coverage runs through ComplyAdvantage; and firms holding their own LSEG World-Check One or Dow Jones licences bring them at no extra charge. Matches queue for four-eyes adjudication, and confirmed outcomes feed the PEP and screening registers automatically.

    Client due diligence

  • Sumsub · GBG · ID-Pal

    Identity verification

    Document and biometric identity checks run inside take-on, routed to the right provider for the client’s jurisdiction: Sumsub, GBG or ID-Pal. The outcome lands on the client file as evidence, with the provider, the result and the timestamp recorded, and a failed check raises an action rather than sitting in a portal nobody re-opens.

    Client due diligence

  • Evidence in your tenancy

    Microsoft SharePoint

    Due diligence evidence can live in your own SharePoint tenancy. The platform links files where they are, holds references and metadata rather than copies, and flags a linked file that changes or disappears at source, so the client file cites documents your firm still controls.

    Client due diligence

  • Companies House and more

    Public registries

    Company facts pre-fill from public registries, including Companies House, when a case opens, and the book is watched for registry changes that should trigger a review, so what the file says stays anchored to what the registry says.

    Client due diligence

  • Entra ID, every tier

    Single sign-on

    Single sign-on with Microsoft Entra ID; SAML on request. Access is role-based and entity-scoped from the first login; multi-factor authentication and deprovisioning follow your identity provider.

    Security summary

  • One click, every format

    Exports

    Every register and every report leaves the system in one click: CSV and Excel workbooks, PDF, and board-ready slide decks for the committee pack, white-label for firms running client books. What the committee takes into the meeting is what the system holds, without a number retyped.

    The Reports module

  • Imported at onboarding

    Your existing data

    Registers, risk assessments and monitoring histories come across from your spreadsheets and systems during onboarding, imported for you and checked with you, per entity, so no function and no client starts from zero.

    How onboarding works

  • OpenAPI, end to end

    The documented API

    The platform’s API ships as an OpenAPI specification with a browsable reference, covering the surface the product itself runs on. It is the foundation for the connectors, for customer integrations and for agent access; integration scoping is part of the onboarding conversation, not a change request after it.

    How onboarding works

Run something else? Tell us what your stack looks like. Integration scoping is part of the onboarding conversation, not a change request after it.

Talk to the team
Questions

Questions about integrations.

What does the Quantios Core integration do?
It keeps the entities you administer in step between the two systems: the client book you run in Quantios Core is the client book Vantage Point monitors, with each entity's structure, licence type and jurisdiction driving what its obligations library, risk taxonomy and starter controls populate. It removes the re-keying of entities and the risk of an entity being missed.
Which screening and identity providers does Vantage Point work with?
Baseline screening is built on OpenSanctions data and bundled with every plan. Commercial-grade coverage runs through ComplyAdvantage, and firms holding their own LSEG World-Check One or Dow Jones Risk & Compliance licences bring them at no extra charge. Identity verification is routed by jurisdiction across Sumsub, GBG and ID-Pal.
Which identity providers work with single sign-on?
Microsoft Entra ID, with SAML available on request. Single sign-on is on every tier; multi-factor authentication and deprovisioning follow the identity provider, and access inside the product stays role-based and entity-scoped.
What can we export?
Every register and every one of the ten report types, one click: CSV, Excel, PDF or a board-ready slide deck, so the committee pack, an auditor's sample or a regulator return leaves the system reconciling with the records it came from. Firms running client books can white-label reports and send them to clients under their own name.
How does existing data come across?
During onboarding. Registers, risk assessments and monitoring histories are imported from your spreadsheets and systems by the onboarding lead, per entity, and checked with you before go-live. It is part of onboarding, not a project you run yourselves.
Is there an API?
Yes, documented end to end: the platform's API ships as an OpenAPI specification with a browsable reference, covering the surface the product itself runs on. It is the foundation for the connectors, for customer integrations and for agent access, and integration scoping is part of the onboarding conversation.
We run something else. Can it be integrated?
Tell us what your stack looks like. Data syncs between systems through API integrations, with Quantios Core the first connector and more following; integration scoping is part of the onboarding conversation, not a change request after it, and the team will say plainly what can be connected for you.
Next step30 min · Tailored · No deck

See it running on your structure.

A 30-minute walkthrough using your entities, your licences and a real workflow you bring to the call. No slide deck.