LEI, FATF Recommendation 16 and Mandatory Versus Optional Elements

A Legal Entity Identifier, known as an LEI, is a 20 character code that uniquely identifies a legal entity, such as a company, a fund, or a bank, anywhere in the world. The LEI is issued by an authorised body, it is renewed each year, and it is stored in a public database with the entity name and address. In ISO 20022 messages, the LEI appears in the party identification block, alongside the name and the address, and it is used where the scheme or the regulation requires a precise identification of a legal person. A payment from a company to another company may carry the LEI of both parties, so that the receiving bank, the clearing system, and the regulator can all identify the parties without ambiguity, even when two companies have similar names. FATF Recommendation 16, known as the travel rule, requires that a payment message carries accurate originator and beneficiary information, and that the information travels with the payment through the whole chain. For the debtor, the message must carry the name, the account number, and either an address, a national identity number, a customer identification number, or a date and place of birth. For the creditor, the message must carry the name and the account number. The rule applies to cross border wire transfers, and it is designed to stop money laundering and terrorist financing by making sure no payment is anonymous. If the debtor data is missing or incomplete, the next bank in the chain must ask for it, reject the payment, or suspend it, depending on its risk policy. The travel rule is where the difference between schema mandatory and business rule mandatory becomes visible. In the pacs.008 schema, the debtor postal address is optional, with cardinality 0..1, so a message without an address passes schema validation. Under CBPR+ market practice and the travel rule, however, the address or an alternative identifier is mandatory, so the same message is rejected by the receiving bank even though the schema accepted it. A business analyst must therefore build a rule table that shows, for each field, whether the schema requires it, whether the scheme requires it, and whether the bank own policy requires it. The strictest of the three decides whether the message can be sent. Missing or truncated party data is one of the most common reasons a cross border payment is delayed, and the cost is real. A payment with a debtor name but no address may sit in a queue at the next bank while the operations team asks for the missing data, and the creditor may not be paid for days. A truncated name may fail sanctions screening, because the screening system cannot match a partial name. ISO 20022 helps, because the new format carries full names and structured addresses, but only when banks populate the fields. Testing should cover a missing address, a missing LEI, a truncated name, and a payment to a beneficiary in a high risk country. A system that leaves the address blank because the schema allows it is wasting the standard.