Correspondent banking depends on information passing through several institutions without losing its meaning. Compliance weaknesses often arise when a bank understands its respondent institution at onboarding but lacks a clear view of the payment services subsequently used. A current respondent profile and reliable payment data need to support one another.
FATF’s correspondent-banking guidance supports managing risk proportionately rather than indiscriminately withdrawing services. FATF also revised Recommendation 16 in June 2025. That international standard is distinct from the domestic rules and implementation timetables that determine an individual bank’s current obligations.
Describe the service, not just the respondent
A respondent review should identify the services provided, expected payment activity, relevant customer types, geographic reach and permitted access arrangements. Record what the correspondent understands about the respondent’s control environment and the evidence supporting that assessment.
Avoid treating a questionnaire as the entire relationship review. Answers should be assessed against the services actually used and the issues observed during the relationship. If exceptions repeatedly involve a particular payment route, the review should investigate that pattern rather than simply accepting an unchanged annual declaration.
Map who has responsibility for each part of the relationship. Commercial teams, payment operations and financial crime specialists see different information. A shared review record should make those observations available to the decision maker while respecting confidentiality and information-sharing restrictions.
Test payment information as a controlled data chain
Identify the fields required under the applicable framework and document how they travel through internal systems. Check for missing data, invalid formats, unexplained substitutions and transformations that remove useful context. A field being populated does not establish that its content is meaningful.
Reconcile payment populations between the platform and relevant controls. Include rejected, repaired and reprocessed messages, since a count of successfully settled payments may omit operational events relevant to compliance. Record whether an exception reflects customer input, respondent practice, a message conversion or an internal processing defect.
Classifying causes matters. Repeated requests for the same information can be ineffective when the problem lies in the correspondent’s own mapping logic. Conversely, treating a respondent’s persistent data weakness as an internal technical incident may delay appropriate relationship escalation.
Create an exception process that produces decisions
Each material information issue needs an owner, a reasoned disposition and a traceable response. Define how operations seek clarification, when specialist assessment is required and how the outcome affects continued processing. Those rules should follow applicable law and the bank’s documented risk decisions; a generic service-level agreement cannot resolve every legal question.
Evaluate recurring exceptions at relationship level. A series of individually resolved cases may reveal a persistent weakness in the respondent’s processes. Consider the frequency, significance, responsiveness and recurrence after corrective action. This creates evidence for targeted engagement or other proportionate management decisions.
A hypothetical message-conversion problem
Assume that a correspondent changes its internal payment platform. The number of messages requiring manual repair rises for one respondent. Initial reporting interprets the increase as deterioration in the respondent’s controls.
A joint review compares the original message with the transformed internal record and finds that a new conversion rule is truncating information. The correspondent corrects the defect, identifies the affected period and assesses whether earlier processing decisions require review. The respondent’s risk assessment is then updated using corrected evidence.
The example shows why compliance metrics require operational interpretation. An exception rate can identify a problem, but it does not identify its cause. Decisions about the relationship should follow that investigation rather than precede it.
Prepare for standards changes without confusing legal status
Maintain separate records for international standards, enacted domestic requirements, supervisory guidance and planned internal enhancements. For payment transparency, document which requirement is already binding, which is being implemented and which remains subject to further rules or guidance. Avoid announcing that every global bank has the same deadline merely because a standard has been revised.
Management reporting can then focus on meaningful gaps: affected payment populations, unresolved data defects, material respondent exceptions and readiness dependencies. The central test is whether the bank can explain the information it receives, the decisions it makes with that information and how it responds when the information is inadequate.

