A SWIFT Message Is Not a Sanctions Clearance. It Is a Request for Several Banks to Decide.

The Message Has Good Manners. The Payment Has Several Chaperones.

A SWIFT message arrives beautifully dressed.

Its BIC is in order.

Its account identifier has the right number of digits.

Its currency and amount agree with the instruction.

Its value date is entirely presentable.

Everyone is tempted to call that a cleared payment.

It is not.

It is a request.

More precisely, it asks several banks to decide whether to do the next thing.

Each of them has a different account relationship.

A different legal exposure.

A different customer record.

A different policy.

And a different queue of people trying to make Friday afternoon less memorable.

SWIFT carries messages, confirmations and status reports.

It does not move the money, hold the money, or own the money.

The monetary event happens when one bank debits or credits an account it maintains.

That difference is not conceptual embroidery.

A US$750,000 payment can be authenticated by your customer, syntactically valid as a message, accepted by your bank, and then held by a correspondent, because the correspondent is being asked to make an entry against its own liability.

The message has travelled.

The correspondent has inherited nobody else’s comfort.

Which irritates the modern preference for a single green tick.

Your tick says that a certain system reached a certain opinion at a certain time.

It does not say that the next bank holds the same customer evidence, applies the same sanctions programmes, reads the same narrative the same way, or has agreed to carry the same legal risk.

Some people call that duplication.

They are permitted to call it that until the first exception, at which point the vocabulary becomes more contractual.

A message may travel through many banks; clearance does not travel with it.

Start With the Twelve Fields

Do not store payment_status = sent.

That field is how a payment acquires an afterlife.

Store the twelve wire-control fields: ordering customer, beneficiary, instructing bank, correspondent chain, BIC, account identifier, purpose, currency, amount, value date, screening result, disposition authority.

Complete, because the payment is not one fact.

It is a bundle of claims.

Who is asking.

Who is to receive.

Which banks you have asked to act.

Where value is expected to move.

What the payment says it is for.

And who decided its present fate.

Ordering customer and beneficiary are not display names.

A screen that reduces an entity to a trading name has already begun the kind of fiction that later requires a weekend.

Your KYC file distinguishes the legal customer, the relationship type, the product, the jurisdictions.

The people acting for your customer.

The capabilities requested.

The counterparties expected.

The activity stated.

The geographic reach claimed.

For an entity, add formation and registration details, governing powers, representatives, direct owners, indirect owners, controllers, and the people authorised to act.

Relationship facts.

They belong to the relationship bank.

The BIC and account identifier answer something else entirely: where the instruction purports to go.

The instructing bank and correspondent chain answer whom the message asks to act along the way.

Map that chain explicitly.

A serial payment and a cover-payment arrangement produce different message and funding paths.

Neither is an invisible plumbing choice.

Your control record names every bank that receives a version of the instruction.

Its account relationship.

The route event you expect from it.

If a bank is asked to debit one institution’s dollar nostro account and pay another for a third party’s benefit, that bank is not an obedient courier with a nicer font.

It owns the decision to debit an account it owes.

Purpose, currency, amount and value date are equally operational.

A small payment can be held on a name match.

A very large one can proceed where it is documented and carries no prohibited feature.

Amount alone neither creates nor removes the risk.

A requested value date is not a promise that every bank works to your clock.

Article 4A allows separate cut-offs for orders, amendments and cancellations.

A customer deadline of 16:00 makes a 16:01 instruction received on the next funds-transfer business day, even where the rail is still open.

The poor minute will have quite a career.

Screening result and disposition authority finish the record.

Not cleared.

That is the word a system uses when it has misplaced the adult.

Record which bank screened.

Which message version it screened.

Which list and configuration applied.

What candidate arose.

Which identifiers were compared.

Who made the disposition, and on what legal or policy basis.

Then record the result as a result at that bank, and no further.

KYC Is a Relationship. Screening Is a Decision About This Instruction.

Your sending bank’s KYC does matter.

It should be able to say who the legal customer is, who may instruct, what the ownership-and-control map shows, what the relationship is for, which products and corridors were approved, and what evidence supports the conclusion.

A U.S. covered legal-entity customer can require each natural person owning 25% or more of equity interests, and one controlling individual, under the FinCEN CDD Rule.

That is a collection requirement in one regime.

It is not a universal definition of control, and it is certainly not a portable certificate for a correspondent three institutions away.

Your ownership map is a dated map, not a handsome attachment to the account-opening case.

It identifies direct owners.

Intermediate entities.

Control by other means.

Authorised people.

Then the source for each link, the calculation date, the numerator and denominator where arithmetic matters, and your rule for joint holdings, voting rights and rounding.

A half-owner of a company owning half your customer holds a quarter indirectly.

Useful arithmetic.

It tells a correspondent nothing about whether this beneficiary, purpose, jurisdiction or narrative carries a prohibited feature.

So transaction screening is a different control altogether.

It examines your customer, the beneficiary, the banks, the narrative, the country data and the ownership information, against the controls applicable to this transfer.

It can also examine the full party set where policy requires.

Customer.

Beneficial owners.

Directors or controllers.

Authorised signers.

Relevant connected parties.

Your relationship bank may know a great deal about its customer.

The intermediary knows a different thing: whether it is willing and able, under its own obligations, to make this account entry now.

There are three queues, and they should not be merged merely because a dashboard has a limited appetite for nouns.

List and data update.

Candidate generation.

Adjudication.

An unchanged list, a missing alias and an incorrect clearance are three different failures.

So are a loose fuzzy-match threshold, a tight one, an omitted passport number, and a BIC that is present and tied to the wrong route.

The threshold is not an industry magic number.

It depends on names, scripts, languages, identifiers, and your capacity to resolve the resulting candidates before access is granted.

People keep trying to turn this into a slider.

The slider then acquires a committee.

Your adjudicator compares full and former names.

Dates and places of birth.

Citizenship.

Addresses.

Passport or national identifiers.

Company numbers.

Ownership.

Geography.

No match means the candidate was resolved against the available identifiers.

It does not mean an operator looked at a common name, sighed with feeling, and let the payment become somebody else’s operations problem.

One Route, Several Decisions

Take a familiar case.

A Canadian buyer pays a Singapore exporter in dollars.

Your buyer enters beneficiary details, account number, beneficiary-bank BIC, currency, purpose text, requested value date, charge instruction.

The corporate mandate requires two authorised employees above a stated amount.

Your originating bank validates credentials, entitlements, template, balance or credit line, amount limits, duplicate indicators, mandatory fields.

Possibly also the fact that a new beneficiary has appeared at exactly the moment somebody in Treasury would rather be at home.

The originator can accept the order and debit or firmly hold the buyer’s account.

That changes available cash.

It does not make the Singapore beneficiary able to spend anything.

Lacking a direct dollar relationship with the receiving bank, the originator instructs a correspondent.

That correspondent verifies message integrity, available funds, compliance data and its own account relationship.

A different correspondent may settle through Fedwire, or through CHIPS.

Not interchangeable verbs.

Fedwire processes individual credit transfers in real time and calls a processed transfer immediate, final and irrevocable.

Its published business day runs from 21:00 Eastern Time on the preceding calendar day to 19:00 ET, with an earlier deadline for third-party transfers.

Regulation J supplies your framework.

Operating Circular 6 adds security procedure, message syntax, format, media, settlement, operating hours and charges.

A customer instruction is necessary.

It is not, charmingly, sufficient.

CHIPS lives differently.

An incoming payment can wait in a central queue while bilateral or multilateral offsetting and prefunded balances make release liquidity-efficient.

A queued payment is not a released payment.

At the beneficiary end, the receiving bank checks the beneficiary account, sanctions data, payment purpose and required local reporting data before it accepts and credits.

Under the U.S.-law funds-transfer leg, Article 4A treats the transfer as complete on acceptance by the beneficiary bank.

The Singapore bank remains under its own legal and contractual framework.

Account advice, settlement event and usable beneficiary credit stay three distinct events.

Tiresome, and true.

Classify the Disposition Before Anyone Calls It a Delay

Compliance issue is not a disposition.

It is a way of ensuring Legal receives an unhelpful sentence next Tuesday.

A hold pauses processing while the bank seeks information or resolves an alert.

The owner is the bank holding the instruction.

Your record states the candidate or data gap.

The affected amount.

The message version.

The information requested.

The clock.

The escalation authority.

Not a rejection.

Not a promise that the payment proceeds once the queue is less festive.

A reject is a decision not to process the instruction at that point.

Your record keeps the reason, the authority, the message version, the recipient bank, the time.

And whether your customer or the prior bank gets a request for corrected data.

A bank may reject a technically valid message because beneficiary address, purpose, legal-entity data or travel-rule information cannot meet its policy.

Format validation is the lowest floor in the building.

A return follows a prior movement or acceptance event, and sends funds or an instruction back along the relevant route.

It is not a reject with better manners.

Your return record needs the original payment identifiers, the amount, the currency, the settlement or account-entry state, the route, the reason, the owner, and the resulting reconciliation item.

The original value date stays part of the evidence. Replacing it with the date of the return is an imaginative approach to ageing.

A freeze or block restricts access to funds under the applicable legal or policy authority.

It requires a disposition authority and a legal or policy ground. Not an operator’s confidence that the payment looks awkward.

Disclosure about a compliance hold can itself be legally restricted. Which makes a clear internal record more important, not less.

OFAC’s framework names five components for a risk-based sanctions compliance programme: management commitment, risk assessment, internal controls, testing and auditing, training.

Your screen is a component in that machinery.

It is not the machinery’s moral centre.

So every exception record you keep holds the message version submitted to each bank.

The source clarification.

The repair.

The list version.

The configuration version.

The candidate identifiers.

The disposition.

The named decision maker.

The legal or policy basis.

The next action.

The timestamps.

A source refreshed quarterly does not make the same current-status claim as a real-time official registry, even where both produce the same company number.

Passed vendor check is too coarse as well.

Keep the provider version, the assurance result, the assertion time, and the exact attributes asserted.

The fact is not that a vendor blinked green. The fact is what it said, when, under which version, about which attribute.

Finality Is Not Clearance, and a Recall Is Not a Cancellation

There is one last piece of social confusion.

Somebody sees sent.

Somebody else sees an acknowledgement.

A third sees a debit.

By late afternoon your commercial team has built a small mythology in which the wire is basically there.

It may be.

The route decides.

A CHIPS payment can be queued before release.

A Fedwire payment has the finality its rules specify.

Your beneficiary bank can receive an account advice and still credit immediately, limit the credit pending a data question, or return it where the account is closed or prohibited.

Settlement finality protects settled account entries.

It settles none of the fraud, mistake, commercial-contract or restitution claims that follow.

If your originator discovers fraud, it contacts its bank at once.

Before acceptance or release at the relevant point, cancellation may still be possible.

After settlement and beneficiary-bank acceptance, your operational act is a recall or return request along the actual chain.

Preserve the evidence.

Ask that available proceeds be preserved too.

It is not a generic stop command shouted at SWIFT, which has the unfortunate habit of being a messaging service rather than a bank with a large red button.

The Ladder, Because a Green Tick Is Not an Authority

Payment instruction?

Go to the ordering customer and its relationship bank.

Message validity?

Go to the sending bank and the applicable standard.

Customer due diligence?

Go to the relationship bank’s KYC record.

Intermediary screening?

Go to each correspondent’s own disposition record.

Beneficiary credit?

Go to the receiving bank.

Legal block?

Go to the competent authority and the bank applying the restriction.

Override of a hold?

Demand a named compliance officer.

This is not an argument against speed.

It is an instruction to preserve the decisions your speed has to pass through, before anybody starts promising a customer that the money is on its way.

A message may travel through many banks; clearance does not travel with it.