2 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
3
match keys
catalogue
3
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today legal, tax, treasury and finance each keep an entity list; a new subsidiary appears in the ERP before legal has finished the registration.

With Lima the legal entities are read where they live, matched on LEI and registration number and jurisdiction, assembled field by field and published as one golden record per real legal entity, with every source key underneath. Company codes, ledgers, filings, mandates and intercompany flows for the entity, under any structure version are one click away, because the transactions sit in the same bed.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Entitylegal name, form, registration numbers, LEI, jurisdiction, incorporation date
wins: legal
Ownershipparent, share, effective dates
wins: legal, versioned
Representationcompany code, ledger, currency, fiscal calendar per system
wins: finance
Officers and signatoriesdirectors, authorised signatories with validity
wins: legal and treasury
How records match

The keys, in order

LEIregistration number and jurisdictionlegal name and country (fuzzy)

The legal hierarchy is the reference for consolidation; the management hierarchy is a second, separate tree.

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.

Where it sits

3 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Legal ownershipgroup → holding → entity → branch, with shares
Consolidationconsolidation group → entity
Managementregion → business unit → entity

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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
ColumnLEI has 20 characters and passes the check
jurisdiction is in the ISO list
Rowan active entity has at least one company code or an exemption
a merged entity has an end date and a successor
Businessownership shares of an entity's parents sum to 100% per date
every company code maps to exactly one entity
no intercompany posting names an entity outside the active structure
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Intercompany transactionsSAP ACDOCA; Oracle GL
Statutory filingslegal calendar
Bank mandatestreasury
entities by jurisdictionintercompany volumefilings dueownership changes per year

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens company codes, ledgers, filings, mandates and intercompany flows for the entity, under any structure version.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Ownership and officer data editable by legal; finance edits representation; all others read names and codes. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/legal-entity/lookup
{
  "lei": "5493001KJTIIGC8Y1R12"
}
response
200 OK
{
  "golden_id": "LE-0007",
  "legal_name": "Acme Components GmbH",
  "parent": "LE-0001",
  "share": 100,
  "company_codes": [
    "1200"
  ],
  "status": "active"
}

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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.

After two acquisitions a manufacturing group had 96 legal entities and four entity lists. One golden list with versioned ownership fed consolidation, tax and the ERPs; the year-end entity reconciliation became a query.

illustrative scenario · Legal entity and company code
Terms on this page

LEILegal Entity Identifier, a 20-character global code for a legal entity.
Company codeThe ERP unit that keeps a legal entity's books.
Consolidation groupThe set of entities combined in a set of group accounts.
Golden recordThe one record for a real legal entity, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Financial services, Industrial manufacturing, Consumer goods, Telecom. The industry pages show the domains each starts with.

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.