/ platform · reconcile & map
Two systems agree on nothing.Something has to decide.
Reconciliation is where a field called cust_ref and a field called customerId become the same idea — recorded once, with the reasoning attached, rather than re-decided inside every integration that needs it.
/ the problem
Every integration re-answers the same question, privately.
Connect two systems and somebody decides that one field maps to another. That decision is real work: it needs the shape of both systems, some knowledge of what the business means by the word, and a judgement about the cases where they do not quite line up.
Then it is written into a connector, and it disappears. The next integration between the same two systems makes the decision again. A third team makes it differently. Nothing anywhere can tell you the three disagree, because there is no place where the decision was recorded — only three places where it was assumed.
This is the n×n problem, one level down
/ the approach
Reconcile against a canonical layer, not against each other.
Inferrex does not map system A to system B. It maps each system to a canonical representation — 1,733 canonical keys built from 38 specification formats — and derives the pair from the two halves.
That is what turns n×n into n. A system is understood once, against the shared layer, and every pairing it could ever take part in follows from that understanding rather than from another connector.
Inferred, then checked
Structure and candidate meaning are inferred from what the system publishes. What cannot be inferred confidently is surfaced as a question rather than guessed silently.
Recorded with its reasoning
A mapping carries why it was made. A reviewer can disagree with the reasoning rather than only with the result.
Reused by everything above
Integration, automation, governance and migration all read the same reconciliation. One correction propagates; it is not applied six times.
Re-checked when the system moves
A schema change re-enters reconciliation rather than breaking a pipe. See
Monitor & Heal/ honestly
It is not a field-mapping UI with a nicer theme.
A drag-and-drop mapper still asks a person to make every judgement, and still stores the result where only that integration can see it. Making the same work prettier does not make it reusable.
Inferrex is also not claiming that reconciliation is fully automatic. Some decisions are genuinely business decisions — whether your "active customer" includes the ones in a payment hold — and no amount of inference settles those. What changes is that the decision is asked once, recorded where everything can read it, and never silently re-made by the next connector.
Bring two systems that should agree and do not.
Reconciliation is easiest to judge on something you already know is messy.