Leaving this course?

Lesson 1 of 5

Why a payment carries information at all

A payment instruction could, in principle, be nothing more than an amount and an account number. It carries more than that for one reason: so that the people handling it can tell who is actually paying whom.

The problem it solves. Money moving through several institutions becomes anonymous very quickly. Each bank sees the one before and the one after, and nobody sees the ends. Without information travelling with the payment, an institution in the middle cannot screen the real parties, and an investigator cannot follow the money afterwards.

So the standards require the information to travel. The FATF's Recommendation 16 — often called the wire transfer rule — requires that originator and beneficiary information accompany the transfer and stay with it through the chain. The same idea has since been applied to virtual asset transfers, where it is known as the travel rule.

What it is not. It is not a licence to collect whatever is convenient. The required set is defined, and collecting more personal data than the rules call for creates an exposure rather than a defence.

Who the rule serves, in order. Screening, first: an institution cannot check a name against a sanctions list if the name is not there. Detection, second: patterns only emerge when parties can be seen. Investigation, third: a case assembled afterwards depends on records that name people rather than accounts.

It applies to domestic payments too, with some allowance for how much travels where the information can be obtained quickly from the ordering institution. The common misconception is that this is a cross-border rule only.

And it is one of the few obligations that is genuinely about data quality. Most anti-money laundering duties ask for judgement. This one asks for fields to be populated accurately and passed on unchanged, which sounds administrative and is, in practice, the foundation everything else in the payment chain rests on.

Lesson 2 of 5

What must travel

The required set is short and specific. Knowing it precisely matters, because almost all of the practical failures are about one missing field rather than about anything conceptual.

About the originator — the person paying:

  • Name.
  • Account number, or a unique transaction reference where there is no account.
  • Address, or a national identity number, or a customer identification number, or date and place of birth. One of those, not all.

About the beneficiary — the person being paid:

  • Name.
  • Account number, or a unique transaction reference where there is no account.

Note the asymmetry. More is required about the payer than about the payee, which reflects what the ordering institution can actually know.

There is a threshold, and it is lower than people expect. For cross-border transfers below a de minimis amount — the FATF uses 1,000 US dollars or euro — a reduced set may be permitted, and the information need not be verified unless there is suspicion. Above it, the full set applies and the originator information has to have been verified.

Accuracy is the obligation, not plausibility. A name field containing "Customer" or "Our client" is populated and worthless. So is an address field reading "Nairobi" alone, or a reference that is the ordering bank's internal ticket number.

Batch files get a concession and not an exemption. Where many transfers are sent together to another country, the batch itself must carry full originator information, and each individual transfer must carry the account number or reference so that it can be traced back.

And the information must stay with it. Whatever is received has to be passed on. Dropping fields because a format is awkward is the failure the next lesson is about.

Lesson 3 of 5

Who is responsible where

Three roles, three different duties. Most confusion in this area comes from an institution applying the wrong one to itself.

The ordering institution — the payer's bank. It originates the data, and it is the only party in a position to know whether the information is true. It must obtain and hold the required information, verify the originator information for accuracy where the transfer is above the threshold or there is suspicion, and include it in the message. Everything downstream depends on this being done properly.

The intermediary institution — a bank in the middle. Its duty is to keep what it receives with the payment as it passes it on. Where a message format cannot carry everything, the information must still be retained and made available on request. It must also have procedures for handling transfers that arrive with information missing, which is the subject of the next lesson.

The beneficiary institution — the payee's bank. It must take reasonable measures to identify transfers lacking required information, verify the beneficiary where the information has not already been verified and the amount is above the threshold, and have risk-based policies for when to execute, reject or suspend a transfer that is incomplete.

One institution often holds several roles. A bank may originate some payments, sit in the middle of others and receive the rest. The obligations differ by role and not by institution, so a single internal policy that treats all payments the same will be wrong for two of the three.

And responsibility does not transfer with the payment. An ordering institution that sends poor data has not discharged anything by the fact that somebody downstream accepted it. The receiving institution's failure to object is not a defence for the party that created the problem.

Lesson 4 of 5

When it arrives incomplete

Payments arrive missing information every day, for reasons ranging from deliberate concealment to an elderly system that truncates a field at thirty-five characters. What an institution does about it is where the rule bites.

First, be able to notice. Identifying incomplete transfers requires either a control that checks the fields or a process that samples them. An institution that has never measured what proportion of inbound payments carry complete party information cannot say whether it complies, and most have not measured it.

Then decide, in advance, by category. The options are to execute, to reject, or to suspend pending the missing information. The decision should be made by policy — by corridor, by counterparty, by amount — rather than by whoever is at the screen. An undocumented practice is both a compliance gap and an operational one.

Ask the sender. A request for the missing information is normal, and the pattern of responses is itself informative. A counterparty that cannot identify its own customer within a reasonable time has told you something about its systems.

Repeat offenders are a relationship question, not a payments question. Where an institution persistently sends incomplete data, the response ranges from a conversation, to a contractual requirement, to restricting or ending the relationship. The standards expect this to be considered rather than tolerated indefinitely.

Beware the quiet fix. Populating a missing field with a default, a placeholder or the ordering bank's own details makes the message pass validation and destroys its meaning. It is also, where done to defeat downstream controls, the serious conduct the next lesson describes.

And record what you did. Which transfers were incomplete, what was requested, what came back, and what was decided. That record is the evidence that the control exists, and it is the material for the conversation with the counterparty.

Lesson 5 of 5

Why the data decides whether screening works

This obligation is usually filed under anti-money laundering. Its sharpest consequence is for sanctions, where incomplete data does not degrade the control gracefully — it switches it off silently.

Screening works on what is in the message. Originator, beneficiary, both institutions, intermediaries, and free-text fields. A name that is not there cannot be matched against any list, however good the matching engine.

And nothing reports the failure. When a field is blank, the screening engine finds no match, the payment passes, and every dashboard shows a control operating normally. This is why accepting degraded data is a decision with a consequence rather than an operational inconvenience.

Partial information is worse than none in one respect. A name with no address or date of birth produces either a missed match or an unresolvable alert, and the volume of unresolvable alerts is what pushes institutions to raise thresholds, which misses more. Poor data corrupts the control twice.

Altering a message to make it pass is a different order of seriousness. Removing or changing references to a party or a jurisdiction so that a payment clears downstream controls is deliberate conduct, it has attracted the largest penalties in the history of this field, and it is worth naming plainly in training rather than leaving as a technicality.

Which is why the ordering institution's job matters most. It is the only party that can put the truth in. Everything downstream is either preserving that or losing it.

The practical question for any institution. What proportion of the payments you send carry complete, accurate party information, and what proportion of those you receive do? Two numbers, rarely measured, and the honest starting point for everything in this course.

Knowledge check

Ten questions

Answer all ten questions, then check your answers. You need 9 out of 10 to pass and receive a certificate. If you score less, you will see which answers were right and wrong, and then go through the course again before you retake the check. Your answers, progress and times are kept only in this browser.

Standards and frameworks covered

The published frameworks this course teaches toward. Saolix is not affiliated with, endorsed by or accredited by any of these bodies; naming a standard is a citation, not a claim about its author.

Sources

The official documents this course relies on. Laws and guidance change, so check the current version.

  1. The FATF Recommendations (Recommendation 16 and its Interpretive Note), updated 2025 · Financial Action Task Force
  2. Proceeds of Crime and Anti-Money Laundering Act, 2009 (No. 9 of 2009) · Kenya Law
  3. Proceeds of Crime and Anti-Money Laundering Regulations, 2013 · Kenya Law
  4. Anti-Money Laundering and Combating of Terrorism Financing Guidelines · Central Bank of Kenya
  5. Correspondent Banking Due Diligence Questionnaire and its guidance · The Wolfsberg Group
  6. Sound management of risks related to money laundering and financing of terrorism · Basel Committee on Banking Supervision, Bank for International Settlements
  7. Committee on Payments and Market Infrastructures · Bank for International Settlements
  8. Financial Reporting Centre · Financial Reporting Centre, Kenya
  9. Guidance for a Risk-Based Approach for the Banking Sector · Financial Action Task Force
  10. Data Protection Act, 2019 (No. 24 of 2019) · Kenya Law