Capabilities Golden records

One record per real thing, pieced together from every system that knows it.

Lima reads the records for a customer, product or supplier where they live, standardises them, matches them in pairs, and assembles one golden record field by field.

1 · SOURCES, IN PLACESAP S/4HANALFA1 0000104471ACME COMPONENTS GMBHWERKSTR. 12, BOEBLINGENVAT DE812345678SalesforceAccount 001Ab…Acme Comp.Werkstrasse 12, 71034no VAT IDSupplier portalSUP-88213Acme ComponentsWerkstraße 12VAT DE 812 345 6782 · STANDARDISEname caselegal formstreet + no.postcodeVAT formatcountry3 · MATCH IN PAIRSSAP ↔ Salesforcescore 91Salesforce ↔ Portalscore 88SAP ↔ Portalscore 97merge above 90review 75 to 90apart below 75one cluster of three4 · SURVIVE · 5 · GOLDENAcme Components GmbHgolden id L-00731 · confidence 0.96legal nameregistry · SAPaddressportal · verifiedVAT IDportal · VIES oke-mailCRM · newesttermsSAP · contractlifecycleactive · tier 1xref: 0000104471 · 001Ab… · SUP-88213every value keeps source, rule, timeunmerge restores the three recordsillustrative values; the mechanics are the product’s
One supplier in three systems, assembled: cleanse, match in pairs, survive field by field, publish with the cross-reference. Illustrative values; the mechanics are the product's.
5
steps from source records to a golden record
product
2
thresholds per match rule: review and merge
product
9,340
golden suppliers from 41,800 source records on the showcase estate
showcase
100%
of values carry source, rule and time
product
1 click
to unmerge, with history kept
product
Step by step

How a golden record forms

The same five steps for every domain; the keys and the rules differ.

Read the source records in placeSAP, Oracle, the CRM, the portal, the lake: each object is registered and shows its rows at once, under the source's own permissions. Nothing is copied to start.
Construct, deduce, piece together

Three ways an attribute gets its value

Constructed

The value exists in one or more sources and survivorship picks the winner: legal name from the registry, address from the verified feed.

Deduced

The value follows from other values and a rule: lifecycle 'active' from open orders in the last 90 days; tier 1 from spend rank; legal form from the name.

Pieced together

The value is assembled from parts held in different places: the site list from SAP plants plus portal addresses; the contact list from CRM, portal users and order creators.

A deduced value is recalculated when its inputs change and carries the rule that made it; a pieced-together value keeps the source of each part. Both are as auditable as a constructed one.

Thresholds

Where a score lands decides what happens

075 · review90 · merge100No match: the records stay apartSteward reviewAuto-mergeBoth lines are set per domain and per rule; moving them changes how much work reaches the queue each morning.Every merge above the line is logged with its score and rule, and can be undone.
Two lines per rule. Moving them changes how much work reaches the queue each morning; every merge above the upper line is logged with its score and rule.

Both lines are set per domain and per rule, on your rows: the match run shows the pairs at each score before the lines are saved. A strong-key rule usually merges from a high score with a narrow review band; a name-and-address rule keeps a wide review band. The steward can move a line and see the queue change.

Survivorship

The winner per field, with the reason

golden supplier L-00731 · survivorship6 fieldsevery winner explainedoverride by steward allowed
fieldcandidateswinnerrule
legal nameSAP · CRM · registryAcme Components GmbHregistry rank 1
registered addressSAP · portal · Deutsche Post checkWerkstraße 12, 71034 Böblingenverified within 90 days
VAT IDSAP · portal · VIESDE812345678verification passed
contact e-mailCRM (Feb 2024) · portal (Jul 2026)j.keller@acme-components.defreshest verified; decay 9 months
payment termsSAP · contractNet 45contract rank 1
bank accountSAP · portal•••• 4471two-person verification
SAPCRM or portalregistry or verificationsteward edit

Rules are per field or field group: an address survives as a unit, a name survives with its legal form, a bank account survives only once verified. A steward's edit outranks every feed until a newer verified value arrives, and the audit trail shows the whole sequence.

Keys per domain

What identifies a record, by domain

The catalogue lists the keys for all thirty domains; these are the most common.

DomainStrong keysStandardised attributesDeciding evidence
CustomerVAT ID · DUNS · registration numberlegal name + country · street + postcodeshared invoices; e-mail domain
SupplierVAT ID · DUNS · LEI · verified IBANlegal name + country · addressa different verified IBAN keeps records apart
MaterialGTIN · manufacturer + part number · drawing numberdescription tokens · physical attributessame attributes with different words match
Sitegeocode · plant code in the crosswalkname + countrysame geocode, different role: one site
Employeeworker id · work e-mail · directory idname + hire dateHR is the system of record
Assetserial + manufacturer · asset tag · fixed-asset numbermodel + sitethe fixed-asset register reconciles

Every domain page names its keys and how they decide.

How master-data hubs usually do it

What is standard in the market, and what is different here

Match rules, survivorship strategies, thresholds, unmerge and cross-references are standard in every master-data hub, and buyers should expect them everywhere. The difference here is where the work happens: the hubs load a copy of the sources into their own store and match there; Lima matches on the rows in place and keeps the cross-reference as a join, so a source-side correction shows at once and the transactions of each record are on the proposal.

A second difference is what the matcher can see. A hub that holds master data only compares names and addresses. Lima's bed holds the transactions too, so shared invoices, common delivery addresses and order history count as evidence, and two suppliers with one name and two verified bank accounts stay apart.

Standard everywherematch rules · survivorship · thresholds · unmerge · cross-reference
Herematching on rows in place; cross-reference as a join
Evidencetransactions on the proposal, live
Explainabilityevery value with source, rule and time; a SQL view over the sources reproduces the winner
Reversalunmerge restores the sources with their history
Terms on this page

Strong keyAn identifier that alone establishes identity: VAT ID, DUNS, GTIN, IBAN, serial number within a manufacturer.
Match ruleA comparison of two records on chosen fields with a method and a score.
Merge line and review lineThe two scores per rule: merge automatically above the upper one; review between the two.
SurvivorshipThe rule that picks the winning value for each field: source rank, recency, verification, completeness, steward override.
Cross-referenceThe list of source keys that belong to one golden record, kept as a join.
UnmergeSplitting a golden record back into its source records, with the history kept.
Questions

What happens to the source records after a merge?

They stay in their systems, unchanged, and stay addressable by their own keys underneath the golden record. Write-back, where enabled, sends the golden values to them through their released interfaces.

How are thresholds chosen?

On your rows. The match run shows the pairs at each score, the steward sets the lines per rule, and the queue shows the effect. Lines are versioned like everything else.

Can two records with the same name stay apart?

Yes, when the evidence says so: a different verified IBAN, a different registration number, different transactions. The rule that keeps them apart is recorded on both.

Does a language model decide merges?

It proposes on the pairs a rule leaves open, with its reasoning; the thresholds and the steward decide. See AI-assisted.

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.