How matching works
Both files are converted to the same transaction schema. Transactions are matched on booking date and amount; when several candidates exist, the one with the same payment reference wins. Matched pairs are then compared on reference, counterparty account and value date. Unmatched transactions are listed per side.
Typical uses: validating a bank's CAMT.053 against the CODA you import today before switching formats, checking an accounting package's export, or finding the missing transaction when balances don't agree.