One Identity · Companies & people

Every company once, in every system.

Five of your systems know Brezmira. None of them knows it is the same Brezmira. One Identity gives every company and person one permanent ID that all your systems share, without replacing any of them.

Én identitet

Brezmira OOD

CompanyBulgaria

org_01a1…c4b1
VAT
BG204817361from ERP · Marketplace
EIK
204817361from Invoicing
Company type
OOD written “ООД”from Invoicing
Nettside
brezmira.examplefrom CRM · held
Phone
+359 2 000 0000from Sheet · held
Person
Ivo Petrov works at Brezmirafrom CRM · held

Finnes i

ERPInvoicingMarketplaceCRMSheet

2 records held for a person

As each record arrives

Four answers. No guesses.

Nothing is cleaned once and left to go stale. Every record a system sends is matched the moment it arrives, and gets one of four answers.

  1. 01

    Same record

    Its company is updated.

    A record a system sent before comes again, with a new address. Only that company changes.

  2. 02

    Sure match

    It joins the company.

    The same registered number, or for a person the same e-mail. It joins, by itself, and says why.

  3. 03

    Nothing similar

    A new company.

    No number, name, phone or website comes close. It gets its own permanent ID.

  4. 04

    Maybe

    Held for a person.

    Close, but not sure. It waits for someone who knows, and is never joined by a guess.

Sure: a registered number

The VAT number and 18 kinds of national register number in 15 countries. “BG204817361” and “204817361” are read as one number. A German HRB number counts only with the court that issued it.

  • VAT
  • BGEIK
  • DEHRBwith its court
  • DEHRAwith its court
  • NLKvK
  • ATFN
  • BEKBO
  • CZIČO
  • SKIČO
  • HUCg.
  • DKCVR
  • ESNIF
  • ITREA
  • GRGEMI
  • ROONRC
  • ROCUI
  • FRSIREN
  • PLKRS
  • PLNIP

Held: everything that only looks alike

  • The same number, but another name
  • The same name in the same country
  • The same phone or website
  • A number two companies already hold
  • A number from a system you trust less

Two records with different numbers of the same kind are never joined: they are two companies. A phone or website that five or more companies share is not counted at all.

A person decides once. The next time the record comes, it goes straight to its company.

Merging and undoing

Every merge can be undone.

A wrong merge in most systems is for ever. Here each one is written down with who made it and why, and can be taken back.

Audit logorg_01a1…c4b1
  1. Joined

    БРЕЗМИРА ООД joined BrezmiraSure: the EIK is the VAT number without “BG”

    Matching
  2. Held

    Brezmira Meat Products waits for a personHeld: same website, another name

    Matching
  3. Oppgjort

    Brezmira Meat Products is BrezmiraSame company

    A curator
  4. Merged

    Brezmira Trade merged into BrezmiraSame name, no number yet

    A curator
  5. Undone

    Brezmira Trade is its own company againIts own EIK arrived: a separate company

    A curator
  • The company kept keeps its ID.The other ID still answers, and points to it. Names, numbers, contacts and links move over.
  • Every value says where it came from.When two systems disagree about an address, you see both, and whose you trust first.
  • Your systems’ own merges are followed.Merge two customers in your ERP and their identities merge too.
  • People too.The same person in the CRM and on the marketplace becomes one, tied to the company they work at.
Your systems stay

Ask first. Hear every change.

Each system keeps working as it does today. It sends its records, asks before it creates a customer, and is told by webhook when a company changes, merges or splits. One API, and a key for each system.

Before creating a customerwrites nothing
GET /v1/identities/match?vat=BG204817361
Answer
Sure by VAT number
Selskap
Brezmira · OOD · Bulgaria
Finnes i
ERP C-1042 · Invoicing D-88310
Your ids
C-1042 You already have this one.
Webhook · signedidentity.merged
  • ERPDelivered0.4 s
  • InvoicingDelivered0.6 s
  • CRMTrying again in 5 minattempt 2

In order for each system. Retries after 1 min, 5 min, 30 min, 2 h, 6 h, 12 h and 24 h, then it is marked failed, to send again with one click.

Invoicing has gone quiet. No full run for 31 hours; it usually sends one every 26.

  • Personal details maskedNames, e-mails and phones of people are hidden from viewers, and left out of webhooks unless you say so.
  • Walled off in the databaseEach business’s data is walled off by the database itself, not only by the app.
  • Keys bound to one systemA system’s key pushes and asks for that system only. The full key is shown once.
  • In the EUThe API, the database and the dashboard run in Frankfurt.
I vår egen avdeling

It runs under our own systems first.

MeatBorsa trades meat every day on these systems. When one wrong merge slipped through, a person found it and undid it, and the record shows who and why.

4 systems share it
BOSS, Ledgvero, the MeatBorsa marketplace, and Registry, which only adds to companies that exist
11,862 people
found in our systems and tied to one identity each
7,879 people
linked to the company they work at
117 people merged
in one pass: by e-mail or phone, or the same name at the same company

Send us two customer lists.

An export from your ERP and one from your invoicing, as they are. We show you how many are the same company, how many we would join by number, and how many we would hold for you to decide.