Writing

FATF Recommendation 16: the information that has to travel

The travel rule does not judge a transfer. It checks that the transfer carries who it is from and who it is to, so that someone downstream can.

Enso Intelligence · Dhaka/June 19, 2026 · 5 min

A rule about completeness, not legality

Most anti-money-laundering rules ask whether something looks suspicious. FATF Recommendation 16, the travel rule, asks something narrower and, in its way, more basic: does the transfer carry the information about who is sending it and who is receiving it? The rule requires that originator and beneficiary details accompany a wire transfer along the entire payment chain, so that every institution that touches it, and any investigator who later examines it, can see the parties involved.

The point of the rule is not to decide that a particular transfer is laundering. It is to ensure that the information needed to make that judgment, by anyone, anywhere along the chain, travels with the money instead of falling off it. A transfer that arrives stripped of its originator information is a problem not because it is provably illicit, but because it has become unscrutinizable, and unscrutinizable is exactly what a launderer wants a transfer to be. So the violation here is not suspicion. It is incompleteness.

The check is presence and accuracy

{
  "rule_id": "AML-TRAVEL-16",
  "title": "Transfer missing required originator or beneficiary information",
  "source": "FATF Recommendation 16 (the travel rule)",
  "severity": "block",
  "expected_outcome": {
    "action": "review",
    "message": "Required originator or beneficiary information is missing from this transfer above the applicable threshold. FATF Recommendation 16 requires it to accompany the transfer. Do not forward without the required details; obtain or request them."
  },
  "conditions": [
    { "type": "conditional_logic", "operator": "AND", "clauses": [
      { "type": "numeric_comparison", "path": "transfer.amount", "operator": ">=", "target": "regime.travel_rule_threshold" },
      { "type": "field_missing_any", "fields": ["transfer.originator.name", "transfer.originator.account", "transfer.beneficiary.name", "transfer.beneficiary.account"] }
    ]}
  ],
  "deterministic": true,
  "validation_status": "expert_reviewed"
}

This is a completeness check, gated by a threshold. Above the applicable amount, the required fields must be present. The rule is mechanical in the best sense: the information is there or it is not, and which fields are required and at what threshold are data the rule reads, because they vary by jurisdiction and have been extended over time, notably to cover transfers between crypto-asset service providers, where the same obligation now applies to transfers that the original rule, written for traditional wires, never imagined.

That extension is itself an illustration of the rules-and-data split. The obligation, that identifying information must travel with a transfer, did not change when it was applied to crypto. The scope of what counts as a covered transfer changed, and that scope is data. The rule that checks for completeness did not need rewriting to cover a new kind of transfer. It needed the new transfer type added to what it applies to.

Fail closed, toward holding the transfer

The conservative direction here is to hold rather than forward. When required information is absent, the transfer is not waved through on the assumption it is probably fine. It is held for the information to be obtained, because forwarding an incomplete transfer is precisely the act the rule prohibits, and an institution that passes along money it cannot attribute has not met its obligation, whatever the transfer turns out to be. Missing information is not a reason to proceed cautiously. It is a reason to stop until the information is there.

The point

Recommendation 16 is a clean example of an obligation that is about completeness rather than judgment. It does not ask whether a transfer is suspicious. It asks whether the transfer carries who it is from and who it is to, so that the question of suspicion can be asked, by anyone, at any point along the chain. The check is the presence of required fields above a threshold, both of them data, and the discipline is to hold an incomplete transfer rather than forward it. It is the unglamorous backbone of financial transparency: not a clever detection, just the insistence that money does not move without saying where it came from and where it is going.