An automated workflow can report success while a downstream system remains incomplete, duplicated, delayed, or inconsistent. Reconciliation is the operating practice of comparing what should have happened with what actually exists after the workflow runs.
Define the expected end state
For each important workflow, document the records, statuses, notifications, approvals, or external actions that should exist when processing is complete. Use durable identifiers so the same business operation can be traced across connected systems.
Compare independent evidence
Do not rely only on the workflow engine saying that a step succeeded. Where practical, compare the workflow record with the destination system, queue, ledger, or other authoritative state. Record discrepancies without copying unnecessary sensitive data.
Separate delay from failure
Some systems are eventually consistent or process work asynchronously. Set a reasonable reconciliation window before declaring a mismatch, and distinguish work that is still pending from work that is genuinely missing or incorrect.
Make repair deliberate
Define whether a discrepancy should be retried, corrected manually, escalated, or left unchanged. Repairs should reuse stable operation identifiers where possible so the correction does not create a duplicate side effect.
Track recurring mismatch patterns
Group discrepancies by integration, failure mode, business process, and cause. Repeated mismatches can reveal weak retry design, missing validation, stale mappings, or unclear ownership.
Keep decision authority separate
Reconciliation can identify technical or operational differences. It should not independently reverse, approve, deny, or reinterpret legal, clinical, financial, employment, safety, or other regulated decisions unless an appropriately governed process explicitly authorizes that action.
Related knowledge
Use this with Automation Idempotency, Automation Retry Design, Automation Observability, and Automation Exception Queues.
References
This is general operational guidance and does not replace system-specific engineering, security, legal, regulatory, or professional review.