PatternLab
Docs/How Neuron works

Identity resolution

Represent one business object without erasing its different source records.

One object, several representations

Example Manufacturing Pvt Ltd in CRM, EXAMPLE MFG in an ERP, and Example Manufacturing Private Limited in a contract may refer to the same customer. Names alone are insufficient to establish that identity.

SourceRepresentationSource ID
CRMExample Manufacturing Pvt LtdC-1842
ERPEXAMPLE MFG00982
ContractExample Manufacturing Private LimitedContract party text

Shared identity, preserved provenance

The intended ontology links these representations to a shared Customer identity. It does not delete or merge records in the original systems. Source-specific IDs and evidence must remain attached to the shared identity.

Conflicting IDs, reused names or uncertain matches require human review. An identity decision can affect every downstream relationship and result.

Current boundary

Cross-system entity resolution is not implemented. Invoice checks detect exact duplicate invoice IDs within the supplied invoice records. That narrower check does not resolve customers or suppliers across systems.