Originator information on wires: telling a name from a placeholder

Originator information is the data that identifies who sent a wire: the originator's name, address and, when the payment is ordered from an account, the account number. Under the US travel rule the originator's bank must put it in every transmittal order of $3,000 or more, along with the amount, the date and the banks involved (31 CFR 1010.410(f)). The hard part is not whether the field is filled, which any payments hub can check, but whether what is in it names anybody: "ONE OF OUR CLIENTS" fills the field and identifies no one, while "NA Holdings Ltd" looks odd and is a real company. Botminds' Funds Transfer Recordkeeping & Travel Rule gives that judgment to one agent, the Field agent, which reads every inbound and outbound wire, marks each required field present, missing, meaningless or incomplete, cites the rule and the example it relied on, and leaves every decision about the money to people.

What originator information is required on a wire?

For a US originator's bank sending $3,000 or more, three items describe the originator: its name, its address, and its account number when the payment is ordered from an account. The bank must also identify itself, by "the name and address or numerical identifier of the transmittor's financial institution", and include the amount, the execution date and the identity of the recipient's bank (31 CFR 1010.410(f)(1)). An intermediary bank passes the same items on, if it received them.

Two details trip up checks built on the message format. The account number is conditional, so a wire paid for by an official check at a branch can legitimately carry no originator account. And the address requirement still carries a clause for Fedwire orders sent before the sending bank's conversion to the "expanded Fedwire format", a 1990s change that the guide on the travel rule's old Fedwire clause examines. A rule engine that flags every wire without an account, or every Fedwire without an address, will be noisy in one case and wrong to excuse in the other.

Inbound wires from abroad were sent under the sending country's rules, not 1010.410(f). The receiving US bank has no travel rule duty for them; its duty is supervisory, to monitor for originator information that is missing or meaningless and respond. That is the test the rest of this guide is about.

What is manifestly meaningless information?

Manifestly meaningless information is a value that is present in the field but obviously does not identify the party. The phrase comes from the federal banking agencies' December 2009 guidance on cross-border funds transfers, which defines it in one clause: a field is "manifestly meaningless or incomplete" where "it is obvious, without further research or investigation, that the message does not identify parties to a transaction" (interagency guidance, FDIC FIL-72-2009; issued by the Federal Reserve as SR 09-9).

Each word in that definition limits the test. "Obvious" sets a high bar: a value that might be a real name is not meaningless. "Without further research or investigation" means the judgment is made from the message itself, not after a registry search. And "does not identify parties" is about identification, not accuracy. The same guidance says that neither the SWIFT format change nor the Basel Committee paper "suggests that intermediary banks must gather information relating to incomplete fields in all payment orders or must verify the accuracy of information contained in payment message fields."

What the agencies did expect is a method. "Banks should have, as part of their monitoring processes, a risk-based method to identify incomplete fields or fields with meaningless data," the guidance says, and banks processing cover payments "should within reasonable timeframes develop and implement plans for adapting automated monitoring systems." Seventeen years on, that is still the standard a checker is measured against: a method, risk-based and automated where volume demands it.

Can abbreviations be used for the originator name?

Yes. The FFIEC BSA/AML Examination Manual says that "Although the Travel Rule does not permit the use of coded names or pseudonyms, the rule does allow the use of abbreviated names, names reflecting different accounts of a corporation (e.g., XYZ Payroll Account), and trade and assumed names of a business", as well as the names of unincorporated divisions or departments (FFIEC manual, Funds Transfers Recordkeeping).

The prohibition on coded names is old and firm. In 1998 FinCEN quoted its own January 1997 guidance to banks: "[t]he use of a code name, or pseudonym is prohibited" under the travel rule, and it warned that a new customer request for a nominee or coded name "should be carefully evaluated by depository institutions as a potentially suspicious transaction" (FinCEN Issuance 98-1, 63 FR, January 26, 1998).

For a checker, the two lists pull in opposite directions. Abbreviations, trade names and account labels are exactly the values a keyword rule flags, because they are short, unusual or contain words like "client" and "account". Coded names are the values a keyword rule misses, because they look like names. That asymmetry is why a list of banned words, on its own, either floods the queue or lets the dangerous cases through.

Is a P.O. box acceptable as the originator address?

In certain circumstances, yes. The rule does not define "address", and the FFIEC manual records that FinCEN issued a regulatory interpretation in November 2003 (68 Fed. Reg. 66708) allowing mailing addresses, including post office boxes, in the transmittor address field. Under it, the address means "either the transmittor's street address or the transmittor's address maintained in the financial institution's automated CIF (such as a mailing address including a post office box)", as long as the bank keeps the transmittor's address on file and it is retrievable on request by law enforcement (FFIEC manual).

That makes the address the field where policy matters most. A country alone, like "PANAMA", is incomplete on any reading. A town and a country, like "Manama, Bahrain", is a judgment: the sample bank's policy accepts it on inbound wires, consistent with the hybrid address format, which requires a country code and a town at the least (Fedwire format FAQ; the ISO 20022 town name), while another bank might ask for more. Fedwire itself tells senders that its format is not their compliance standard: "We recommend that you consult with your compliance and legal departments" on what to include (Fedwire November 2027 release FAQ). The point for an evaluation is that the threshold should be a written, versioned setting the BSA Officer owns, not a rule buried in code.

Inside the Field agent: how one agent judges one field

The Field agent does one job: it turns a message into the fields the travel rule names and gives each a verdict with its reasons. It does not decide what happens to the wire, does not write to the sending bank and does not change a payment. On the sample wire below, an inbound USD 9,800.00 pacs.008 from a bank in Panama City, it read the message in 1.2 seconds and found seven of nine fields meaningful.

The wire laid out as the fields the travel rule names, each with a verdict

The library is where the judgment is made auditable. Every verdict on a meaningless value points to an entry, such as MV-03, "a generic reference to the sender's customer", which lists the phrases it matches, states what it does not match (a registered name that contains those words), shows its version and the BSA Officer who approved it, and counts how often a person has overturned it. An examiner who asks why a value was flagged gets a citation, not an explanation reconstructed after the fact.

The citation behind a verdict: a versioned library entry with its overturn count

What should a bank do with incomplete originator data?

Ask the bank that sent it, decide what to do with the funds while waiting, and keep count. For an inbound wire the usual sequence is a request to the originator's bank or the preceding intermediary, a decision to credit, hold or return, and a running record of which correspondents repeat; the Basel Committee's 2009 paper lists contacting the sending bank first among the possible responses, and expects the reasons for each decision to be documented. The guide on what the enforcement cases and supervisors expect covers repeat offenders and reporting.

For an outbound wire the answer is different: the bank is the originator's bank, the data is its own, and the wire should not leave without it. The solution's Record agent looks for the missing value in the bank's customer data before cut-off and proposes the fix for a supervisor to approve. The Field agent's role in both cases ends at the verdict, which is the design choice a buyer should test hardest: a checker that also decides cannot be checked.

What to look for in travel rule software

Judge a travel rule checker on the values it clears as much as on the values it flags. A tool that flags every short name will look thorough in a demonstration and bury the team in a week. The checklist below is what we would ask of any tool, ours included.

Where the solution fits less well is worth saying plainly. A bank that sends and receives a few dozen wires a week can review originator fields by hand with a written list, and should; the value of an agent rises with volume, with the number of foreign correspondents, and with how often the same channels produce the same gaps. And no tool knows your reviewers' standard until you measure it, which is why measuring how often two reviewers agree comes before choosing one. To see the Field agent's verdicts on a sample of your own wires, start from Funds Transfer Recordkeeping & Travel Rule, or read how to run a one-month test of AI on your wires.

Questions people ask

Is the originator's account number always required on a wire?

No. Under 31 CFR 1010.410(f)(1)(i) the originator's bank includes the account number only when the payment is ordered from an account (the travel rule paragraph by paragraph). A wire funded with cash or an official check at a branch can carry no originator account and still comply, provided the name and address are there.

What is the difference between missing and meaningless originator information?

Missing means the field is empty or absent. Meaningless means it holds a value that obviously identifies nobody, such as a placeholder phrase or the sending bank's own name on a customer payment. A field of blanks is missing in substance: Fedwire's format guidance warns senders not to fill free-text elements with spaces only, because it causes problems for receivers.

Can the receiving bank correct the originator name itself?

It should not invent or overwrite another bank's originator data. The right move on an inbound wire is a request to the sending bank, and a decision on the funds by a person. On an outbound wire the bank is the originator's bank and may add the value from its own verified customer data, with a checker approving the change.

How accurate is the Field agent?

No published figure would tell you how it performs on your correspondents' traffic, so the honest answer is to measure it. Run it over a past month of your wires, compare its verdicts with your reviewers', and count misses and false flags by field type; the confidence floor and the library are then tuned to your standard before anything goes live.

Does the travel rule apply to a beneficiary bank receiving incomplete originator data?

No. The FFIEC manual says the travel rule places no duty on beneficiary banks (funds transfer recordkeeping requirements sets out who owes what). The receiving bank's obligations are to keep the payment order and, under supervisory guidance, to have a risk-based way to spot transfers that lack complete originator information and respond to them.

Does checking originator information replace sanctions screening?

No. The 2009 interagency guidance says US banks "should screen transactor information on all automated funds transfers"; a transparency check and a sanctions screen use the same fields for different purposes. A meaningless originator name can defeat a screen, which is one reason the two teams should see each other's findings.