Glossary

Best-of-breed — choosing the strongest product for each function and owning the joins between them. Available to organisations that will actually staff the ownership, and expensive to those that assume they will.

Chain owner — the person accountable for the boundaries end to end. Not a department; a named individual with allocated time and the standing to convene the module owners.

Effective dating — recording the dates a reference data value was valid, so a report spanning a reorganisation uses the right structure for each part. Supported by most products and used by few implementations.

Idempotency — the property that sending the same data twice does not create duplicates. Determines whether a failed transfer is a rerun or a cleanup.

Join — the handover of data between two systems that model the world differently. Four of them in a standard chain, five where agency workers exist.

Master — the single system authoritative for a piece of data. Identity and each reference dimension need exactly one; the commonest failure is having none.

Rule register — a list of every pay rule and the single system that applies it. An afternoon to produce and the most valuable artefact in this subject.

Tolerance — the difference between scheduled and actual that passes without review. Without one, every shift is an exception and the review becomes rubber-stamping.

Terms used loosely by vendors

"Integration" frequently means an export exists. Ask for the interface specification.

"Single source of truth" is meaningful only when the sentence names what it is the source of.

"Real-time" without a replay path is worse than nightly with one.

"Compliant" describes a configuration for named jurisdictions, never a product.

"Implementation in N weeks" assumes your identity and reference data are clean.

How to read these notes

Start with the foundations if figures do not reconcile and nobody knows why — identity and reference data sit underneath everything else.

Start with the joins if you know which boundary is broken.

Start with buying if a purchase is proposed.

Start with running it if the estate works and costs too much to keep working.

Nothing here is legal advice, and the notes say so where it matters.

On the absence of numbers

How to treat any figure in this collection.

No implementation durations are quoted, because they are dominated by the state of your identity and reference data rather than by the product.

No savings figures, which depend entirely on what the joins currently cost you.

No product comparisons.

Every number worth having here is one you produce from your own systems, and the notes say how to produce each.

A practical configuration prompt

During configuration, use this documented connection to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.