Request a Demo
OverviewCapabilitiesData qualityDomain catalogueBy roleBy industryCompareMigrateOutcomesResources
Capabilities Stewardship

A queue a person can clear, with the evidence on every line.

Proposals arrive sorted by confidence and value at stake: merges, splits, fixes, enrichments and rule failures.

Request a demoSee it in the walkthrough
proposalconfidencevalue at stakeactionmerge Acme Comp. ↔ Acme Components0.91€1.2M open POsapprovesplit cluster 7 (14 records, 3 companies)0.62€380Kopen gridrefresh contact e-mail (decayed)0.55lowverifynew supplier from portal, no match—onboardingcreateVAT check failed for L-00912ruleblocks paymentfixsorted by confidence × value · filters by domain, source, rule, ageON ONE PROPOSALthe two records side by sidewhich rule fired, which fields agreedthe transactions of each recordwhat merges, what staysapprove · reject · ask · deferevery decision is a training example
The steward queue and what one proposal shows. The sort is confidence times value at stake, so the pairs that matter most come first.
612
pairs in the first supplier queue on the showcase estate
showcase
41 min
to clear it
showcase
14
records in the largest cluster, opened as a grid
showcase
4
actions per proposal: approve, reject, ask, defer
product
100%
of decisions logged with the reason
product
Step by step

How a proposal is born, judged and applied

Something proposesA match rule scores a pair between the lines; a rule finds a row that fails; a model suggests an enrichment; an agent drafts a fix; a colleague raises a change request.
What one proposal shows

The two records side by side, and what would change

Proposal 4,118 · merge · confidence 0.91 · €1.2M open POsrule R-supplier-04fields agreed 5 of 6approve · reject · ask · defer
fieldSAP 0000104471portal SUP-88213golden after merge
legal nameACME COMPONENTS GMBHAcme ComponentsAcme Components GmbH
VAT IDDE812345678DE 812 345 678DE812345678 · VIES ok
addressWERKSTR. 12 BOEBLINGENWerkstraße 12, 71034Werkstraße 12, 71034 Böblingen
IBAN•••• 4471•••• 4471same account · verified 12 Aug
open POs62 · €1.2M062 · €1.2M

The transactions decide many hard cases: two suppliers with the same name and different verified bank accounts stay apart; two with the same VAT ID and shared invoices merge. Because the transactions sit in the same bed, they are on the proposal, live.

Large clusters

Fourteen records, three companies, one grid

A cluster with many records opens as a grid: one row per source record, the match scores between them as columns, a proposed split into groups, and the transactions per group. The steward drags rows between groups, and the grid shows the golden record each group would produce. Approve applies the split as one decision.

The grid is the same high-performance grid used everywhere, so a cluster of a thousand records behaves like one of fourteen.

Sortconfidence × value at stake, then age
Filtersdomain · source · rule · owner · age · value band
Bulk actionsapprove all above a score, reject all from a source, reassign
Service levelsa proposal older than its domain's limit escalates to the domain owner
Trainingevery decision is a labelled example for the domain's model
Terms on this page

ProposalA suggested merge, split, fix or enrichment with its evidence, waiting for a decision or applied automatically within its allowed range.
Value at stakeThe open orders, revenue, stock or payments attached to the records in a proposal.
ClusterThe group of source records that matching found to describe one entity.
Questions

How much of the queue can be automated?

Pairs above the merge line merge automatically; fixes of a type that stewards approve consistently can be allowed through, per action type, and taken back. The AI-assisted page explains the ladder.

Can several stewards share a domain?

Yes. Proposals are assigned by rule (source, region, category) and can be reassigned; the log records who decided.

What happens to a wrong merge?

Unmerge restores the source records with their history; the decision and the reversal both stay in the audit trail.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.

Request a demoHow the first day runs