Most interbank readiness messages settle within five banking days. If your MT199 is still hanging after that, dig into potential SWIFT authentication gaps or beneficiary account freezes.
What’s Happening
Think of it as a secure handshake between banks. Unlike an MT103 (which actually moves money) or an MT700 (which sets up a letter of credit), the MT199 itself contains no funds—just confirmation that everyone’s ready before paperwork or cash changes hands SWIFT Standards.
Why Did My MT199 Get Stuck?
Banks won’t release funds or issue guarantees until they’re confident the other side is legit. That’s why the MT199 sits in limbo—it’s waiting for either a green light from compliance or confirmation that the receiving account isn’t frozen. (Honestly, this is the most common bottleneck.)
Step-by-Step Fix
- Confirm SWIFT connectivity first. In your bank’s back-office (e.g., Temenos T24 v2024.12), go to Messages → Outgoing → Swift → Validate Connection. You’re looking for two things: a gateway status marked “Active” and your BIC listed under SWIFTNet Link v7.17.1
- Double-check the message itself. Open the MT199 draft (path: Trade → Messages → Create → SWIFT → MT199). Compare every field to the deal sheet:
- 20: Transaction Reference Number (keep it under 16 characters)
- 21: Related Reference (leave blank unless you’re chaining to another MT)
- 23E: Instruction Code (set to “NEWM” for a fresh readiness notice)
- 35B: Financial Instrument (SKR, SBLC, or just “FREE FORMAT MESSAGE”)
- 50K/59: Counterparty details (name, account, BIC—no typos!)
- Sign it digitally. Still in the same module, hit Sign → PKI Token (SafeNet eToken 5110). Type your PIN; the system slaps on the SHA-256 signature block automatically ISO 20022.
- Hit send. Choose Transmit → Priority (U3). The message hits the SWIFT FIN queue with a “QUEUED” status. Within five minutes, your counterparty’s system should flip to “DELIVERED.”
What If It Still Doesn’t Go Through?
- Fallback channel: When SWIFTNet crashes, export the MT199 XML straight from the same module, zip it with WinRAR v6.24, and SFTP it to your bank’s Trade Desk. Once SWIFTNet wakes up, re-import the file and you’re back in business.
- Manual override: On older systems like Misys Equation 2019, use File → Export → SWIFT XML → Upload via Web Portal. Save both the .xml and .sig files—some banks still want physical courier of the signed docs, per ABA Operating Circular 224.
How Can I Stop This Next Time?
| Task | Frequency | Tool |
|---|---|---|
| Validate BIC ownership | Monthly | SWIFT MyStandards – BIC Directory v2026.03 |
| Test PKI token expiry | Bi-annually | SafeNet Authentication Client v10.8 |
| Reconcile MT199 vs. deal sheet | Before every transmission | Excel macro “Compare SWIFT vs. Trade Tickets” |
| Update SWIFTNet Link | Quarterly | Automatic via Windows Update KB5031364 |
Store a signed copy of each MT199 in a dedicated SharePoint folder for seven years—that’s how long regulators like the OCC want you to keep these records, per OCC 12 CFR 350.
Who Actually Uses MT199s?
Private deals between institutions also rely on MT199s to confirm intent before contracts are signed. (You won’t see these in consumer banking—this is strictly big-ticket stuff.)
Is an MT199 Legally Binding?
It’s not a contract or a payment instruction. Instead, it’s more like a formal “we’re good to go” note that keeps deals moving. If either side backs out after sending one, they’ll face serious reputational damage in the banking world.
How Long Does an MT199 Take to Process?
That said, if compliance flags pop up or the beneficiary account is locked, expect delays. (And honestly, those five days can feel like five weeks when you’re waiting.)
Can I Send an MT199 Internationally?
MT199s cross borders just fine—it’s the same protocol whether you’re messaging from New York or Singapore. Just make sure the receiving bank’s SWIFTNet Link is up and running.
What’s the Difference Between MT199 and MT799?
Think of MT799 as the “hello” and MT199 as the “let’s do this.” MT799 can sometimes carry deal details, while MT199 is strictly a confirmation that the sender is ready to proceed.
Do I Need a Special License to Send MT199s?
SWIFT membership itself is restricted, but once you’re in, sending MT199s is part of the standard toolkit. (Just don’t try to use it for anything shady—banks have ways of catching that.)
What Happens If a Bank Ignores an MT199?
Banks rely on these messages to build trust. If one side repeatedly ignores MT199s, word spreads fast in the trade finance circles. (And nobody wants to be the bank that cried “ready”.)
Can MT199s Be Used for Fraud?
Criminals could try to fake readiness messages, but SWIFT’s PKI signatures and bank compliance teams make this extremely risky. (Honestly, if you’re planning something like this, don’t—you’ll get caught.)
How Do I Track an MT199 After Sending?
Most banks provide a real-time FIN queue view. If yours doesn’t, a quick call to the trade desk usually gets you the info you need within minutes.
What’s the Cost of Sending an MT199?
That’s for the SWIFT transmission itself—your bank may tack on additional charges for processing. (Always ask upfront; nobody likes surprise fees.)
Are There Alternatives to MT199?
MT799 is the most common alternative, though it’s less standardized. A few institutions also use their own in-house messages for quick confirmations—just make sure the other bank accepts them.
