MBS Connect | Vendor-independent integration hub
Vendor-independent integration hub

Connect the systems your business already depends on.

MBS Connect turns disconnected applications, data, documents and workflows into one governed operating layer. It gives approved systems a common way to exchange information, trigger work, move documents, return results and evidence what happened.

System agnosticDesigned to sit between existing systems rather than forcing a new application stack.
API-firstCreates a reusable, structured approach to JSON/API exchange and process orchestration.
Private by designWorks inside the organisation’s ecosystem with authorised relationships, logs and controls.
One secure hub connecting approved business systems
The integration problem

Systems work well individually, but work breaks down between them.

Manual hand-offs create delay, cost and operational risk.

Most organisations already have strong specialist applications. The issue is rarely whether one system can do its job; it is whether the full journey across systems can be controlled, monitored and supported.

  • 01Data is duplicatedThe same client, matter, account, asset or transaction information can sit in several places, with different field names and update patterns.
  • 02Work moves manuallyTeams rely on spreadsheets, email, downloaded files, portal checks and re-keying to move work forward.
  • 03Integrations become brittlePoint-to-point scripts and isolated system chains create hidden dependencies and make future change harder to manage.
  • 04Visibility is limitedIT, operations, risk and management need clearer evidence of what ran, what failed, what changed and what still needs attention.
What MBS Connect is

A controlled integration layer for end-to-end work.

MBS Connect provides one reusable hub for secure data exchange, process orchestration, monitoring and audit. Systems connect once as resources, then MBS Connect coordinates how those resources exchange data, documents, outputs and status.

Reusable resource connections

Core systems, portals, databases, cloud services and third-party APIs are configured as reusable resources. Updates to shared connection details can then be managed centrally instead of repeated across multiple profiles.

CRMDMS / ECMPortals

Common JSON/API layer

Connected applications can call MBS Connect in a consistent way. The platform validates payloads, maps fields, handles vendor-specific API logic and returns clean outputs to approved destinations.

JSONAPI callsOutputs

Integration Process Orchestrator

Multi-step integration workflows can manage branching, waits, retries, temporary artefacts, document routing, status updates and completion events without hard-coding each customer process.

BranchingRetriesArtefacts

Monitoring and audit

Dashboards, event logs, run history, transaction identifiers, status information and diagnostic messages help support teams understand what succeeded, what failed and why.

Run historyEventsDiagnostics

Security and control

Authentication, authorisation, secrets handling, role-based access, environment controls and data-retention settings are treated as platform features rather than afterthoughts.

OAuthTokensRoles

Built to extend

New connectors and profiles can be added as modules or add-ins, sharing the same administration, logging, deployment and support principles as existing connections.

Add-insProfilesModules
One controlled hub

Move from point-to-point integrations to a reusable operating model.

Traditional integration grows one connection at a time. MBS Connect changes the pattern by centralising connection details, common endpoints, integration profiles and orchestration logic.

Before: system-to-system chainsEach connection may carry its own authentication, data structure, error handling and support dependency.
After: reusable governed connectionsSystems connect into MBS Connect as resources, and the hub coordinates trigger, mapping, routing, status, outputs and audit.
Outcome: clearer supportIT teams can monitor, support and extend integration through one controlled platform layer.
MBS Connect logo
Client management
Compliance tools
Documents
Reporting
Signature & portals
Cloud services
How it works

A controlled sequence of inputs, activities and outputs.

Any authorised system capable of calling the MBS Connect API can initiate a process. MBS Connect then runs the configured integration steps and returns defined outputs for the calling system or another approved destination.

1TriggerA form, portal, CRM update, case event, scheduled job, reporting alert or external API call starts the process.
2Input mappingThe payload is received, validated and mapped into the relevant integration profile.
3OrchestrationThe process runs configured steps such as searching, creating folders, sending requests and applying conditions.
4Artefact handlingDocuments or generated files can be held temporarily while the next step is decided.
5Output mappingStatus, references, links, documents, metadata, verified data or exception messages are returned cleanly.
6MonitoringEvent history, run logs and diagnostics help IT, support and operations evidence and troubleshoot the process.
Relationship modelMBS Connect manages the relationship between approved systems.
Authorised triggerForm, event or API call.
Secure exchangeMapped JSON/API payload.
Controlled routingDocuments, artefacts and outputs.
Audit & monitoringLogs, status and exceptions.
What changes for the organisation

Clearer value for business, IT, operations and control teams.

The platform is designed to support the people who own the business outcome and the teams responsible for keeping the technical estate secure, supportable and auditable.

Business leaders

More value from existing technology investment and faster, lower-friction change without replacing every core application.

IT teams

Fewer point-to-point dependencies, centralised configuration, clearer support ownership and reusable integration patterns.

Operations

Less re-keying, fewer spreadsheets, smoother hand-offs and more reliable status across teams and departments.

Risk & compliance

Stronger traceability, evidence, exception handling and auditability across end-to-end journeys.

Client-facing teams

Faster client, customer, citizen or stakeholder journeys because information and documents move between systems automatically.

Data & reporting

Cleaner operational, client, matter, portfolio, billing and process data for reporting, oversight and management information.

Support teams

Better diagnostics and run history, making it easier to understand incidents and reduce key-person dependence.

Change teams

A practical route to start with one high-value workflow, then expand into a wider integration operating model.

Existing connections

Controlled relationships. Private by design. Built to extend.

MBS Connect sits inside the organisation’s ecosystem, acting as the secure relationship layer between approved systems. Each connected system remains authoritative; MBS Connect manages the trigger, mapping, routing, status, outputs and audit trail between them.

01Existing and planned connectionsUse current and planned add-ins to connect core systems, identity and compliance tools, portals, SharePoint, AWS, Docusign and other approved applications.
02Connected-system relationshipsMBS Connect manages the integration relationship without requiring every source system to understand every downstream system.
03Privacy and data controlData is exchanged only through authorised relationships, with role-based access, token and secrets governance, sensitive-field handling and controlled retention.
MBS Connect logo

Identity & compliance

VerifyID-PalYotiMesh IDScreening APIs

Client management

Quantios CoreNavOneSalesforceDynamics 365HubSpot

Cloud & services

LaserficheSharePointAWSAzureSQL / data

Business processes

ExcapsulaFormsWorkflowApprovalsCase events

Portals & sharing

Objective ConnectDocusignClient portalsMobile apps

Intelligent services

ABBYYOCRReportingAnalyticsData warehouse
Example use cases

Useful wherever work depends on several systems completing one journey.

MBS Connect is sector and application agnostic. The same integration model can support regulated financial services, legal, fiduciary, public sector, healthcare, insurance and broader corporate operations.

Unified client, customer, citizen or case lifecycle

MBS Connect can synchronise records between core platforms, CRM, document management, portals and specialist systems while preserving the source-of-truth role of each approved application.

  • Propagate address, status, risk, priority or relationship changes.
  • Reduce re-keying and mismatch risk.
  • Maintain clearer visibility across the full journey.
Illustrative flowFrom system update to controlled downstream actions.
Lifecycle
1Core record changesCRM, case or administration system sends an authorised trigger.Trigger
2MBS Connect maps the updateFields are validated and routed through the correct profile.Map
3Downstream systems receive clean outputsDocument, portal, compliance and reporting systems are updated as required.Output

E-IDV, CDD and compliance evidence

A form or workflow can call MBS Connect, send identity data to an approved provider, retrieve JSON results and documents, map verified fields and file evidence back to the right destination.

  • Send identity verification or screening requests.
  • Retrieve CDD reports and supporting documents.
  • Return verified data and status to the calling workflow.
Illustrative flowControlled e-IDV request and evidence handling.
Compliance
1Workflow captures dataInput fields are passed to MBS Connect through an authorised API call.Input
2Provider activity runsMBS Connect sends the request, waits for status and parses the JSON response.Run
3Evidence is routedReports and verified outputs are written back to DMS, workflow or core records.Evidence

Document movement, signature and controlled sharing

Generated reports, signed documents, audit trails and external workspace outputs can be moved between approved systems without relying on manual download-and-upload routines.

  • Create folders or workspaces.
  • Hold files as temporary artefacts while routing decisions are made.
  • Import final documents and audit evidence into the correct records.
Illustrative flowDocument generated in one service, used by another and filed with evidence.
Documents
1Document producedA report, signed pack or portal artefact is created by an approved service.Create
2Temporary artefact heldMBS Connect holds the file inside the process while the next step is decided.Hold
3Final destination updatedThe document is filed, linked, shared or returned with a clear audit trail.File

Approvals, payments and commitments

Approval workflows can be connected to finance, banking, grants, procurement or billing systems so that only authorised and evidenced activity progresses.

  • Connect approval decisions to payment or commitment systems.
  • Feed metadata back into reporting and reconciliation outputs.
  • Surface exceptions and status for operations and oversight.
Illustrative flowApproved transaction through controlled integration.
Finance
1Approval completedWorkflow generates a decision, evidence pack or transaction reference.Approve
2Finance profile runsMBS Connect maps the request and calls the approved banking or finance endpoint.Route
3Status returnedReferences, errors or completion status feed back to the originating process.Status

Cross-platform reporting and oversight

MBS Connect can push key events and metadata into data warehouses or reporting platforms, combining process metrics with core operational data.

  • Feed management information, Board packs and regulatory reports.
  • Combine workflow events with core system data.
  • Expose bottlenecks, throughput and exceptions across the estate.
Illustrative flowProcess event to insight and oversight.
Reporting
1Event capturedProcess, document or system event creates a structured record.Event
2Metadata normalisedFields are mapped into common reporting structures.Normalise
3Data warehouse updatedDashboards and reports receive better cross-platform data.Insight

Sector-specific workflows on the same reusable platform

The architecture is deliberately application agnostic. A bank, fiduciary provider, wealth manager, law firm, insurer, healthcare provider or public body can apply the same controlled pattern to different approved systems.

  • Connect core, portal, compliance, document and reporting platforms.
  • Add sector-specific services as demand emerges.
  • Reuse the same support, logging and governance principles.
Illustrative flowOne integration model, many sectors.
Agnostic
1Sector event occursClient review, matter opening, claim, case, payment, onboarding or renewal.Event
2Approved systems are coordinatedProfiles define the right routes, data contracts and document rules.Coordinate
3Outputs are evidencedStatus, exceptions, documents and references are visible for support and audit.Evidence
Sector examples

The same integration challenge appears across many industries.

MBS Connect is especially relevant where organisations operate under scrutiny, need strong evidence, and depend on several specialist platforms to complete one business process.

TCSPs & fiduciary providers

Client and entity lifecycle management, KYC refresh, risk reviews, AEOI, payments, workflow evidence and document filing.

Outcome: stronger control across client and entity journeys.

Banking & payments

Connect onboarding, account servicing, screening, payments, document management, reporting and customer portal activity.

Outcome: fewer manual hand-offs in regulated customer journeys.

Wealth management

Portfolio monitoring, client reviews, suitability evidence, document collection, CRM updates and reporting dashboards.

Outcome: cleaner client, portfolio and review data.

Legal services

Matter opening, due diligence, conflict checks, billing, time recording, document management and external legal data services.

Outcome: less duplicate entry across matter and compliance systems.

Public sector & membership bodies

Citizen, member or case journeys across portals, case systems, document repositories, approvals and reporting functions.

Outcome: better service visibility and stronger evidence of activity.

Insurance, healthcare & corporates

Claims, policy administration, HR, procurement, contract management, approvals, document generation and internal reporting.

Outcome: a reusable framework for high-volume operational processes.
Technical overview

Enough structure for IT teams, without making every process a bespoke build.

MBS Connect separates connection management, integration profiles and orchestration logic so that each area can be maintained and extended more safely.

Connect Core ServiceManages secure communication, application-level controls, available resources, global settings and environment parameters.
Web administration interfaceProvides a controlled surface for connection profiles, integration profiles, API/user security, event monitoring and system management.
Integration layer and add-insPackages connector logic, OAuth/token handling, API actions, JSON extraction and reusable activities.
Integration Process OrchestratorRuns multi-step processes with branching, waits, retries, artefact handling, outputs, execution logging and run history.
MBS Connect architecture at a glanceWeb UI, integration layer and orchestration runtime.
MBS Connect
3Managed architecture layers
GovernedAccess, profiles and execution
TraceableRuns, outputs and audit history
ReusableConnections, actions and workflows
Web user interfaceConnection profile editors, integration profile editors, API/user security and system management.
Integration layerAPI layer to integration profile methods, JSON extraction, built-in authentication API and safe access to resource settings.
IPO runtimeWorkflow designer, activity palette, condition handling and variable management.
Controlled process lane
TriggerAuthorised API call
MapValidated JSON payload
RouteConfigured activities
OutputClean outputs and logs
Security and governance

Designed for controlled, auditable data movement.

MBS Connect is intended for organisations that need integration to be manageable, evidenced and aligned with existing security and change controls. It supports a more controlled model than ad-hoc scripts, manual exports or unmanaged system-to-system chains.

Identity and accessRole-based access controls and alignment with existing identity platforms where required.
Secrets governanceToken, credential and connection settings managed as part of the platform configuration.
Audit and monitoringEvent logs can include timestamps, affected resources, status, transaction IDs and diagnostic messages.
Change controlResource and profile changes can be promoted between environments using agreed deployment patterns.
Document controlDocuments and generated files can be routed through approved destinations, with temporary artefacts handled within the process.
Data minimisationSensitive-field handling and retention settings can be considered within each approved integration profile.
What it is not

MBS Connect complements existing systems; it does not replace them.

The platform is best understood as the connector and conductor between systems, not as another core business system competing with them.

Not a replacement CRM or core systemIt sits between approved systems and helps them exchange data, documents and status.
Not limited to one vendor stackThe model is designed to be vendor-independent and application agnostic.
Not simply a migration toolIt can support structured movement of data and documents, but its broader role is orchestration.
Not a collection of isolated scriptsThe product direction is modular, governed, centrally configured and reusable.
Not a substitute for judgementIt supports controlled execution, evidence and data movement while business decisions remain owned by the organisation.
Delivery approach

Start with one high-value workflow. Expand into a reusable integration operating model.

MBS Connect can be introduced in controlled waves. The aim is to prove value quickly, avoid trying to change everything at once, and then extend the same connection and orchestration pattern to further systems and departments.

Stage 01Discovery & mappingMap existing systems, interfaces and manual integration points such as file exports, emails and spreadsheets.
Stage 02Solution designDefine target integration patterns, data ownership, master sources, synchronisation rules and conflict handling.
Stage 03Connect configurationSet up resources, connection profiles, integration profiles and add-ins for the agreed use cases.
Stage 04Testing & cutoverRun integration testing and user acceptance testing across representative scenarios before a controlled go-live.
Stage 05Monitor, optimise & expandUse dashboards and logs to fine-tune flows, then extend to additional systems, departments and processes.
Built to grow with the organisationNew approved systems can be added as resources and reused across multiple processes, reducing the need to start from scratch each time.
Next steps

Identify the first workflow where integration friction is costing time, risk or visibility.

A practical starting point is usually a workflow that already crosses several systems, involves repeated manual hand-offs, creates compliance evidence, or requires better operational monitoring.

1. Choose the workflowFocus on a process where manual re-keying, documents and approvals create a clear pain point.
2. Map the systemsIdentify source systems, destination systems, data fields, documents, triggers and required outputs.
3. Prove the modelConfigure a controlled integration profile, test it, monitor it and expand from there.

Integration availability, configuration scope and delivery sequencing will depend on the customer environment, approved vendor APIs, security requirements and agreed implementation approach.

Thank you for completing the form.  Please click below to download our factsheets.