One record per worker, from the HR system of record, matched to the ERP, the directory and the ticketing system.
Today HR, the ERP, the identity directory and the ITSM tool each hold a worker record; a mover keeps the old cost centre in two of them for weeks.
With Lima the employees are read where they live, matched on worker id and work e-mail, assembled field by field and published as one golden record per real employee, with every source key underneath. Positions, reporting line, assets, tickets and access roles for the worker, with the organisation unit page 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.
Salary and personal identifiers stay in HR; the golden record carries the pointers and the organisational facts other systems need.
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 |
|---|---|
| Organisation | company → division → department → team |
| Reporting line | manager chain, versioned |
| Cost | cost centre hierarchy |
| Location | region, country, site |
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 | work e-mail matches the company domains FTE is between 0 and 1 cost centre exists and is open |
| Row | an active worker has an active manager a leaver has an end date and closed access a position sits in exactly one organisation unit |
| Business | headcount per cost centre matches the approved plan or carries an exception a manager with more than 15 direct reports is flagged no access role survives 30 days after the end date |
| Transactions in the bed | Read from |
|---|---|
| Time and absence | Workday time tracking |
| Expenses | expense system |
| Tickets and assets | ServiceNow |
| Payroll totals | aggregates only |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens positions, reporting line, assets, tickets and access roles for the worker, with the organisation unit page.
Personal identifiers and pay data stay in HR; the golden record exposes organisational facts by role; access to names by team. The twelve layers apply on every door; see security.
POST /api/v1/golden/employee/lookup
{
"work_email": "priya.sharma@example.com"
}200 OK
{
"golden_id": "E-20117",
"confidence": 1.0,
"position": "Item SME",
"cost_centre": "CC-4410",
"manager": "E-19822"
}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.
Worker read from Get_Workers (Human Resources).
Open the Workday page →Employee mini master read from PA0001 · PA0002 (HR mini master in S/4).
Open the SAP S/4HANA page →Worker read from PER_ALL_PEOPLE_F · PER_ALL_ASSIGNMENTS_M (REST: workers).
Open the Oracle Fusion Cloud page →User read from sys_user. 2 objects, the keys in ServiceNow fields, the write path and the prerequisites.
Open the ServiceNow page →Worker read from CONFORMED.WORKER. 2 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A telecom operator matched 38,000 worker records across Workday, SAP and ServiceNow. Movers changed cost centre in one place, and the finance team's headcount reconciliation dropped from three days a month to a report.
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; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Industrial manufacturing, High-tech and semiconductor, Financial services, Telecom. 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.