Treasury has proposed cutting Banque Misr’s UAE branches off U.S. correspondent accounts
An August 2026 FinCEN proposal would bar U.S. banks from correspondent accounts for Banque Misr’s UAE branches, citing about $1.8 billion in suspected Iranian shadow-banking activity. The parent bank is not the target written on the page.
A branch, not a whole franchise
On 28 August 2026 FinCEN proposed a rule that would stop U.S. financial institutions from keeping correspondent accounts for Banque Misr’s branches in the United Arab Emirates. The notice, as described in the agency’s release and the filings around it, also looks at indirect access: a foreign bank’s U.S. dollar account used as a pass-through to those branches. This is a proposal. It is not a final special measure, and it is not a sanction on the Arab Republic of Egypt or on every office that carries the Banque Misr name. The geographic cut is the part correspondents skip. Many institutions still score “Banque Misr” as one line on a country sheet. The proposal, if it follows the text Treasury put out, is aimed at the UAE branches as defined in the rule. A Cairo booking and a Dubai booking are not the same fact. If your core system cannot hold a branch geography separate from the parent brand, you cannot implement this notice properly even after it becomes final. You can only panic at the logo.
The figures the proposal cites
Agency material around the proposal cites roughly $1.8 billion in potential Iranian shadow-banking volume involving more than one hundred front companies transacting through Banque Misr UAE accounts between early 2024 and mid-2026. About $520 million of that is described as falling in the most recent twelve-month window. Faircroft is reporting those figures as the proposal’s figures. They are built from the agency’s account of bank activity. They are not a criminal judgment against the branch, and they are not a finding that each of those dollars was proved in court to be Iranian state money. Iranian shadow banking, in this telling, is about dollar access. Brokers settle with paper firms in Dubai or Abu Dhabi. Those firms clear through banks that still have a U.S. correspondent. The typology is old. The branch-specific framing is what is new in 2026, and it is what makes a sloppy “Egypt, high risk” score both too wide and too narrow. Too wide, because it punishes offices the rule may not name. Too narrow, because a UAE branch of an Egyptian bank may sit in your Middle East book under a Gulf label and never meet the Egypt rule you thought would catch it.
What to ask while the text is still a proposal
Questionnaires to foreign correspondents should ask about Egyptian-owned books in the Gulf, not only about “Gulf banks” as a lump. They should ask whether the respondent holds accounts for Banque Misr’s UAE branches or processes payments for customers of those branches through a U.S. dollar account. Negative answers belong in the file with an officer’s name and a date. “Not that we are aware of” is not an answer unless you can show the search. Enhanced due diligence, if the rule is final in anything like its proposed shape, will mean knowing your respondent’s foreign correspondents and being able to say those correspondents will not clear a Banque Misr UAE leg without a review. Expect longer onboarding on Middle East trade finance. Expect argument from relationship managers who have banked the parent for twenty years and do not think of the UAE branch as a separate risk. The argument is understandable. The rule text, if adopted, will not care. A proposed rule is already a diligence artefact. Counterparties will ask for it in 2026 renewals before any final Federal Register notice. Decide a house standard now: freeze new exposure to the named branches, or keep onboarding and document a heightened review. Do not let Geneva and Dubai improvise different answers. Do not freeze the entire Egyptian franchise because the headline said Banque Misr. Read the branch definition. Attach it.
Trade finance is the cover story people will offer
Oil-linked trade is the sentence many shadow-banking narratives use. A letter of credit that names a commodity and settles through an exchange house is not, by itself, a crime. It is a reason to ask how the bank validates the end user and the intermediaries. If your trade desk cannot say which Banque Misr office is on a given instrument, the proposal has already found your gap. Legacy master agreements rarely encode branch geography. Someone has to add the field, or accept that the field will be filled in by an examiner. Screening vendors will not treat a proposed branch measure like an SDN entry. Put the legal names of the UAE branches on an internal list marked proposed. Take them off, or harden them, when the final text moves. The owner of that list should not be “the vendor.”
What this page will not claim
It will not claim Banque Misr has been convicted of sanctions evasion. It will not claim every customer of the UAE branches was a front. It will not tell you to exit Egypt. It will say that in August 2026 the U.S. Treasury proposed cutting specific UAE branches off American correspondent access, cited on the order of $1.8 billion in suspected shadow-banking activity, and that indirect dollar access is part of the design. Verify the rule text before you act. Comment periods exist so the final rule can change. Your file should show you read the final text, not only the August headline.
How a 2026 file should look in practice
Keep a single page that a credit officer can read without a lawyer in the room. Date of the proposal: 28 August 2026. Status: proposed, until a final rule says otherwise. Target as written: Banque Misr’s UAE branches, not the parent as a slogan. Figures cited by the agency: about $1.8 billion across the window described, of which about $520 million in the latest year, involving more than a hundred front companies. Those numbers stay attributed. Under that, a list of your respondents who bank Egyptian groups in the Gulf, the date you asked them about these branches, and the name of the officer who filed the reply. Add one redacted payment sample if you have one, and a blank line for the final rule so nobody pretends the August text is the end of the story. Trade operations should tag instruments with the branch that books them. If the core system only has a country of the parent, say so in the minute and fund a field, or accept that you cannot comply with a branch-level measure except by exiting the whole name. Exiting the whole name may be where you end up. It should be a decision, not an accident of a bad data model. And when the comment period closes, assign someone to read the final Federal Register text the week it appears. A proposal that is narrowed, or aimed at a tighter definition of “UAE branch,” will make last summer’s freeze look careless. A proposal that is adopted as written will make last summer’s shrug look worse.