Clearing File
Pronunciation: KLEER-ing FYLE
Also known as: Payment Clearing File, Payments Clearing File
Definition
Clearing File is a structured file containing payment instructions, returns, adjustments, control totals, or settlement information exchanged for clearing processing. In a payment system, teams should validate format and control totals, secure transmission, prevent duplicate submission, track acknowledgments, and reconcile every accepted and rejected record. The definition must identify the authoritative record, stable identifiers, relevant timestamps, owner, and permitted actions because provider, bank, ledger, and customer-facing states may differ. Key risks include truncation, duplicate files, wrong effective dates, corrupted records, and batch totals that do not match item detail. The term describes a production control or measurement, not merely a status label.
Overview
Clearing File is a structured file containing payment instructions, returns, adjustments, control totals, or settlement information exchanged for clearing processing. In a payment system, teams should validate format and control totals, secure transmission, prevent duplicate submission, track acknowledgments, and reconcile every accepted and rejected record. Clearing may include validation, exchange, netting, returns, and position calculation, but completion of clearing is not necessarily final settlement.
Its practical purpose is to transform payment instructions into validated obligations and positions that can be settled under the rules of a payment system. Clearing File is closely connected to Clearing Processing , Batch Payment Reconciliation , and ACH Return . Operationally, the implementation should validate format and control totals, secure transmission, prevent duplicate submission, track acknowledgments, and reconcile every accepted and rejected record. The principal risks include truncation, duplicate files, wrong effective dates, corrupted records, and batch totals that do not match item detail. The implementation should identify the obligation, participants, settlement asset, accounts or addresses, value date, liquidity source, posting sequence, and evidence of finality.
Clearing File should remain distinct from Clearing Processing, Batch Payment Reconciliation, and ACH Return, because each can represent a different stage, record, control, or financial outcome.
Testing should include malformed or duplicate messages, file control totals, participant cutoff, rejected items, return processing, net position calculation, resubmission, and connectivity failure during a processing window. Important failure modes include insufficient liquidity, duplicate instructions, wrong settlement assets, delayed delivery, participant default, unmatched evidence, and premature claims of finality.
Controls should validate instructions, funding, destination, currency or asset, cutoffs, and participant positions before treating a settlement step as complete. For Clearing File, this point supports the definition’s focus on structured file containing payment instructions, returns, adjustments, control totals, or settlement information exchanged for clearing processing.
Key Takeaway
Clearing File should be defined through authoritative evidence, explicit ownership, controlled exceptions, and measurable production safeguards.
Sources
- CPMI Glossary — Bank for International Settlements (2026-08-03)
- ISO 20022 Universal Financial Industry Message Scheme — ISO 20022 Registration Authority (2026-08-03)
- CHIPS Payment System — The Clearing House (2026-08-03)
- Principles for Financial Market Infrastructures — CPMI-IOSCO (2026-08-03)