ADR / 008

Run reconciliation as a permanent control, not an exception process

Delivery guarantees fail silently. A scheduled comparison of expected and actual populations—with an owner for every kind of difference—is part of the architecture, not cleanup.

Reference pattern

Independently created. Contains no employer or client implementation detail, internal names or figures.

01Context

Customer creation, order status and performance segments move between a CRM, an ERP and a data platform. Each flow has retries and alerts, yet users discover the differences months later: customers still pending in the CRM that exist in the ERP, segments never removed, a company missing from an invoice load.

02Decision drivers

  1. D01

    Any delivery mechanism can lose, duplicate or reorder

  2. D02

    Differences found by users destroy trust in the data

  3. D03

    Repair needs an owner, not a shared inbox

  4. D04

    Reruns and repairs must be safe

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Ad-hoc checks when someone complainsLow-volume, low-stakes flowsDivergence accumulates unseenRejected
Rely on delivery guarantees and alertsFlows with end-to-end exactly-once semanticsAlerts see failed calls, not records that never arrivedRejected
Scheduled reconciliation with classified differencesAny flow whose divergence has a business costNeeds comparison keys, a tolerance, a cadence and ownersSelected

Every option is right under some premises. The verdict applies to the context above.

04Decision

For every flow whose divergence has a business cost, define a reconciliation contract: the expected population, the comparison key, the attributes compared, the tolerance, the cadence, and an owner and repair action for each class of difference—match, difference, missing, unexpected. Run it on a schedule, publish the result as a business-state measure, and make every repair idempotent so a rerun never makes things worse.

05Consequences

What this choice changes elsewhere in the system.

  1. Observability

    Silent divergence becomes visible within one cadence.

  2. Ownership

    Every class of difference has an owner and an action; nothing lands in a shared inbox.

  3. Measurement

    Reconciliation results are measured like any other process KPI.

  4. Integration design

    Integration design must provide stable comparison keys from the start.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

A flow moves inside one transactional system.

02

Divergence in the flow has no business cost.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. Data case / 03Operationalizing analytical signals back into CRMAn activation contract for analytical signals: a small set of governed, read-only values and segments at account grain, with as-of date, version, provenance and an explicit exit—published as the full expected state, applied idempotently and reconciled against what the CRM actually holds.Data & IntegrationsRevenue OperationsAutomationArchitecture case · 11 min
  2. Automation case / 02Designing closed-loop automation from signal to action and exitAutomation as the maintenance of an expected downstream state: entry, update, exit and re-entry designed per transition, system-managed and human-owned work told apart, reruns that converge instead of adding, and reconciliation as the control loop that repairs only what is safe.AutomationRevenue OperationsData & IntegrationsArchitecture case · 11 min

Decisions this one depends on, or constrains.

  1. ADR / 007Treat uncertain integration outcomes as unknown, not failedA timeout says nothing about whether the receiver committed. Model ‘unknown’ as its own state, resolve it by request key, and only then retry or fail.Proposed patternIntegration · Resilience · ERP
  2. ADR / 010Automate exits, not only entriesEvery automation that creates work when a record enters a state must also define what happens when it leaves it—or the downstream state goes stale.Proposed patternAutomation · RevOps · Data
  3. ADR / 001Make ERP customer creation asynchronousProtect the commercial workflow from ERP latency while making pending state and recovery explicit.Proposed patternIntegration · ERP · Resilience
  4. ADR / 005Separate commercial identity from legal customer identityAn account is a commercial relationship; a legal entity is a registered organization; an ERP customer is that entity in one of our companies. Model three linked identities—not one record that means all of them.Proposed patternIdentity · CRM · ERP