One record per real customer, assembled from the ERPs, the CRM and the portals, with every source key kept.
Today the same customer is a sold-to in SAP, a party in Oracle, an account in Salesforce and a row in three spreadsheets, each with its own number, spelling and address.
With Lima the customers are read where they live, matched on VAT ID or tax number and DUNS, assembled field by field and published as one golden record per real customer, with every source key underneath. All sales orders, deliveries, invoices, open receivables, opportunities and tickets for the customer, across the systems, with live counts are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Two records match when a strong key agrees, or when name and address agree closely and no strong key disagrees.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Legal | parent company, subsidiaries, branches, from registries and D&B |
| Sales | sales organisation, region, key-account team |
| Billing | payer, sold-to, ship-to relationships from the ERP |
| Industry | sector and sub-sector codes |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | VAT ID has the format of its country and passes the VIES check postcode matches the country's pattern currency is in the code list |
| Row | a ship-to address carries the same country as its region code a customer with a credit limit has a verified legal name and registration number a blocked customer carries a reason and a date |
| Business | open orders plus open receivables stay under the credit limit every child of a legal parent uses the parent's payment terms or an approved exception revenue by sales region equals the sum of its customers |
| Transactions in the bed | Read from |
|---|---|
| Sales orders | SAP VBAK · VBAP; Oracle order headers and lines |
| Deliveries and shipments | SAP LIKP · LIPS; 3PL feeds |
| Invoices and receivables | SAP BSID · ACDOCA; Oracle AR |
| Opportunities and quotes | Salesforce Opportunity, Quote |
| Service tickets | ServiceNow incidents and cases |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens all sales orders, deliveries, invoices, open receivables, opportunities and tickets for the customer, across the systems, with live counts.
Bank details and credit limits masked for most roles; contacts visible to the account team; personal data of contacts under the privacy policy. The twelve layers apply on every door; see security.
POST /api/v1/golden/customer/lookup
{
"legal_name": "Northbay Logistics Inc",
"country": "US",
"vat_id": "",
"postcode": "94306"
}200 OK
{
"golden_id": "C-00842",
"confidence": 0.94,
"legal_name": "Northbay Logistics, Inc.",
"xref": {
"sap": "0000048210",
"oracle": "300000012",
"salesforce": "001Ab00000QxL2m"
},
"open_orders": 184
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Customer general data read from KNA1 · ADRC (business partner BUT000 in S/4).
Open the SAP S/4HANA page →Party and account read from HZ_PARTIES · HZ_CUST_ACCOUNTS (REST: accounts).
Open the Oracle Fusion Cloud page →Account read from Account. 3 objects, the keys in Salesforce fields, the write path and the prerequisites.
Open the Salesforce page →Customer read from CONFORMED.CUSTOMER. 3 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Customer read from silver.customer. 3 objects, the keys in Databricks fields, the write path and the prerequisites.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A distributor with 21,000 customer records in SAP and 34,000 accounts in Salesforce found 6,100 pairs describing the same company. After the first match run the sales team saw open orders, overdue invoices and open tickets on one account page, and the credit team stopped approving limits twice for the same buyer.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Consumer goods, Industrial manufacturing, Telecom, Financial services. The industry pages show the domains each starts with.
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.