Reconciliation Job
Pronunciation: rek-un-sil-ee-AY-shun JAHB
Definition
A reconciliation job is a scheduled or triggered execution that loads defined source records, applies matching rules, creates results, and updates exception queues for a specific scope and cutoff. It needs run identity, versioned configuration, checkpoints, restart safety, totals, and completion evidence. Reconciliation Job requires named ownership and auditable controls for matching evidence, cutoff control, and exception resolution. The operational record should capture source record, counterpart record, matching rule, cutoff, amount, currency or asset, exception reason, and resolution evidence for Reconciliation Job, including the handoff to Reconciliation .
Overview
A reconciliation job is a scheduled or triggered execution that loads defined source records, applies matching rules, creates results, and updates exception queues for a specific scope and cutoff. It needs run identity, versioned configuration, checkpoints, restart safety, totals, and completion evidence.
For Reconciliation Job, the failure model should include missing records, reused references, cutoff mismatches, duplicate matches, wrong currencies, hidden fees, unresolved suspense, forced balancing, partial refunds, late settlement changes, and corrections without approval evidence. The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence.
Reconciliation Job should remain distinct from Reconciliation and Reconciliation Engine, because each can represent a different stage, record, control, or financial outcome.
Important failure modes include missing records, duplicate matches, timing differences, hidden fees, currency mismatches, stale files, and adjustments that force balances to agree without explaining the cause. For Reconciliation Job, this point supports the definition’s focus on reconciliation job is a scheduled or triggered execution that loads defined source records, applies matching rules, creates results.
Controls should keep original source records immutable, use stable match keys, explain many-to-one or one-to-many relationships, and route unresolved differences to an aged exception queue. For Reconciliation Job, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Reconciliation Job should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Reconciliation Job should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.
For Reconciliation Job, ownership should be assigned to a named team, and every exception should retain its source evidence, decision reason, approval, resolution, and closing timestamp.
Key Takeaway
A reconciliation job is a scheduled or triggered execution that loads defined source records, applies matching rules, creates results, and updates exception queues for a specific scope and cutoff. Its matching scope, cutoff, exceptions, and resolution evidence must be explicit.
Sources
- Principles for Financial Market Infrastructures — BIS CPMI-IOSCO (2026-08-01)
- Conceptual Framework for Financial Reporting — IFRS Foundation (2026-08-01)