Here is a small problem that blocks a lot of value. Your catering contract is number CS-2026-CATERING-0047. But:
- SAP knows it as agreement AGR-4401290.
- Oracle bills against project PRJ-SKG-CATER-26.
- ServiceNow tracks incidents under SVC0087341.
- Purchase orders all start with PO-CATER-.
- Flight operations load galleys using code CATPFC-12.
An invoice email arrives with the subject “INV-PFC-2026-07-1234 / AGR-4401290 July 2026 Catering”. Which contract is it? A person who knows the account can tell at a glance. A system cannot, unless someone has told it.
The reference map
ContractSense keeps a reference map for every contract: each identifier, which system uses it and how to match it. Some are exact values. Some are prefixes, like PO-CATER-. Some are patterns. When a document arrives, references are pulled from the subject, body and attachments and looked up in priority order: exact matches first, then prefixes, then patterns.
Why it matters
Reference resolution sounds like plumbing, and it is. But without it, nothing else works. You cannot check an invoice against tiers if you do not know which tiers apply. You cannot keep running totals if half the volume lands on the wrong contract.
Getting references right is one of the first things we do in a proof of concept, and one of the things customers say they value most. It turns a pile of documents into a connected record.