Schedule a demo
BUSINESS PARTNERS · CRM

One business partner, your whole operation.

OMNIA CRM manages accounts, contacts, opportunities, and vendors on the same Business Partner, the single master of business partners shared by every module of the platform: AML alerts, risk, CMDB, CMMS, sales. The same business partner is a sales customer, a risk subject, the owner of an asset in CMDB and of equipment in CMMS, with no ETL between silos.

1 same business partner across the whole platform 1 Business Partner, six roles KYC as a gate, not a separate procedure Leads → pipeline → proposal, with no re-entry
What it solves

The CRM that doesn't live isolated from the rest of the business.

Most CRMs are an island: sales works off yesterday's export, compliance asks for the same documents all over again, and the asset that CMDB or CMMS manages "belongs" to a different customer in a different system. OMNIA CRM shares the same Business Partner that runs across the whole platform, a single record where the customer, vendor, employee, prospect, salesperson, and manufacturer roles coexist, not four separate records to reconcile. That same business partner is the reference across the whole platform.

1 record
the same business partner in sales, compliance, CMDB, and CMMS
1 business partner · 6 roles
customer/vendor/employee/prospect/salesperson/manufacturer, booleans
% ownership
ownership link crossed in the 360, not in a separate sheet
Gate KYC
configurable requirements and documents before onboarding
Capabilities

Everything the business partner relationship needs.

From the commercial record to the closed opportunity, with risk, KYC, and lead capture in the same place, not six different screens.

Single master

One business partner, your whole operation

Customer, vendor, employee, prospect, salesperson, and manufacturer coexist in the same business partner record, with no duplicated data. Whoever is a customer in sales is also a risk subject in compliance, the owner of an asset in CMDB, and of equipment in CMMS.

SINGLE BPONE RECORDNO ETL
Commercial record

Credit, tax, and hierarchy

Credit limit and balance used, credit status, open balance, and payment terms per business partner; tax ID, group, and parent-child hierarchy for parent companies with subsidiaries, all on the same BP, not in an attachment.

CREDITTAX IDHIERARCHY
Sub-entities

Addresses, contacts, and bank accounts

Each business partner carries its own addresses (billing, shipping, payment, delivery), contacts with title and phone, and the bank accounts to pay or collect from them, without leaving the BP record.

ADDRESSESCONTACTSACCOUNTS
360 view

Risk + links + alerts + KYC

The same record crosses the business partner's risk level and category, its ownership links with the exact % of ownership, open AML alerts and cases, and the KYC file status, an alert opens the customer directly, no hunting for a UUID.

RISKLINKS %AML
Governed onboarding

KYC as a gate, not a separate procedure

Due diligence requirements and required documents, configurable by role and criticality, with validity and status per business partner, onboarding isn't complete until the KYC file is up to date.

REQUIREMENTSDOCUMENTSONBOARDING GATE
Lead capture

Leads, pipeline, and portal

Commercial dashboard with leads (including the ones coming in through the contact center), a funnel with configurable stages, and direct conversion to a sales document with no re-entry; a self-service portal so the customer can see their own case.

LEADSPIPELINEPORTAL
360 View

One record, not five tabs from other systems.

You open the business partner and it's already crossed with what matters for a decision: how much risk it represents, who else it's linked to by ownership, which alerts are open, and whether its KYC file is current.

  • Risk by level and category, not an isolated number with no context for why.
  • Links / ownership relationship with the exact % of ownership between related business partners.
  • Open AML alerts and cases, an alert opens the customer directly, no copying a UUID by hand.
  • KYC file status: which requirement is missing, which one expired, which one is current.
Single customer across the whole platform

One contact. One event. The whole platform knows.

OMNIA CRM doesn't export or sync in batch: it publishes the change as an event and the rest of the platform reacts, the same mechanism used by service, compliance, and billing.

How the data travels

You update a business partner once. The whole operation finds out.

When you update a contact or close an opportunity, the change travels through the same event ring the rest of OMNIA uses, it's not a separate integration someone has to maintain, or a replica that falls out of sync.

contact/account updated → domain event
  service (ITSM) → sees the same contact on the next ticket
  compliance (GRC) → recalculates risk if the profile changes
  CMDB/CMMS → the same business partner is still the owner of the asset/equipment
  billing → issues with current data, no duplicate entry
  → one identity, zero manual reconciliation

Same identity, not a mirror

It's not a copy synced every night: it's the same Business Partner, with roles, seen from every module, all pointing at the same record.

The copilot already knows it

The contact center identifies the business partner by the incoming number and builds the 360, risk and KYC included, before the agent even answers.

No double entry

The won opportunity converts into a sales document and then into a contract/policy, the business partner's data is never typed in again.

Why not a separate CRM

Salesforce manages its own customer. OMNIA CRM manages the same business partner as your whole business.

An off-the-shelf CRM does one thing very well: the pipeline. But it keeps its own contact, and someone has to integrate it, by hand or with an iPaaS, with the ERP, the service desk, and the compliance module. OMNIA CRM is part of OMNIA Workspace: it doesn't integrate the master of business partners, it shares it.

Traditional CRM (Salesforce and similar)
  • The contact lives in the CRM; ITSM, CMMS, and GRC each keep their own copy.
  • An integration (or an iPaaS) syncs the data between systems, by batch or custom connections.
  • The customer's risk, KYC, and AML alerts are looked up in another platform.
  • The won opportunity gets re-entered in the ERP or the contracts system.
OMNIA CRM · part of OMNIA Workspace
  • The contact is the same Business Partner used by ITSM, CMMS, GRC, and billing.
  • There's no integration to maintain: it's one record, with roles, shared by every module.
  • Risk, ownership links, AML alerts, and KYC live in the same 360 record.
  • The won opportunity converts into a sales document with no re-entry at all.
Let's start

A CRM that already knows the rest of your business.

We'll show you OMNIA CRM working with your own case, accounts, pipeline, vendors, or the risk and KYC 360, connected to the rest of OMNIA Workspace, not as an isolated demo.

ESEN
Get a quote