SWIFT Message Types Explained: A Complete Guide to MT Categories, Banking Transactions, and Microsoft BizTalk Integration

Introduction: Understanding SWIFT Messaging in Global Banking

International banking depends on standardized communication between financial institutions. Every day, banks, payment processors, investment firms, and financial service providers exchange messages containing payment instructions, transaction confirmations, account information, and other financial data.

One of the most established frameworks for this communication is the SWIFT messaging system.

SWIFT, which stands for the Society for Worldwide Interbank Financial Telecommunication, provides financial institutions with a secure messaging network and standardized formats for exchanging financial information.

Traditional SWIFT messages are commonly identified by their MT (Message Type) codes, which indicate the purpose and structure of a particular financial communication.

For example, MT103 has historically been associated with customer credit transfers, MT202 with financial institution transfers, and MT940 with account statements.

To help financial institutions integrate these standardized messages into enterprise applications, Microsoft developed the BizTalk Accelerator for SWIFT, commonly known as A4SWIFT.

Microsoft's documentation identifies a broad collection of SWIFT message types organized into ten principal categories, ranging from system communications to cash management.

Understanding these categories helps banking professionals, software developers, and financial technology companies recognize how different financial messages support everyday banking operations.

What Is Microsoft BizTalk Accelerator for SWIFT?

Microsoft BizTalk Accelerator for SWIFT (A4SWIFT) is a specialized integration solution designed to help financial institutions process SWIFT financial messages within Microsoft BizTalk Server environments.

BizTalk Server provides enterprise application integration and business process automation capabilities, allowing organizations to exchange information between different software platforms.

The accelerator adds functionality specifically designed for financial messaging.

It helps organizations implement SWIFT-related message processing, validation, transformation, and integration workflows.

Why Financial Institutions Use SWIFT Integration Solutions

Banks typically operate multiple interconnected systems, including core banking applications, payment processing platforms, compliance systems, treasury management software, and accounting applications.

These systems may use different data structures and communication protocols.

SWIFT integration software helps bridge these differences by supporting standardized financial message processing.

For example, a bank's payment application might generate transaction details using an internal data structure.

An integration platform can transform that information into an applicable SWIFT message format before it is submitted to an authorized messaging interface.

Similarly, incoming financial messages can be validated, interpreted, and routed to the appropriate internal applications.

This approach supports operational consistency and helps reduce manual processing requirements.

However, compatibility with a historical SWIFT message definition does not automatically mean that the message remains permitted for current production use.

Financial institutions must follow the applicable SWIFT standards release, network rules, and service requirements.

Understanding the SWIFT MT Messaging System

SWIFT MT messages follow a standardized numbering system.

Most business messages use a three-digit identifier, with the first digit indicating the broad category of financial activity.

For example:

• MT1xx identifies customer payments and cheque-related communications.
• MT2xx identifies financial institution transfers.
• MT3xx identifies treasury and foreign exchange transactions.
• MT5xx identifies securities-related communications.
• MT7xx identifies documentary credits and guarantees.
• MT9xx identifies cash management and account reporting.

Within each category, individual message codes identify specific business functions.

This classification helps financial institutions distinguish between payment instructions, transaction confirmations, requests, reports, and other financial communications.

Microsoft's A4SWIFT documentation organizes the supported MT messages into categories 0 through 9.

Category 0: FIN System Messages

Category 0 includes system-level communications associated with the operation and administration of the SWIFT FIN messaging environment.

Unlike ordinary customer payment instructions, these messages support technical operations such as message delivery notifications, session administration, system reporting, and message retrieval.

Examples documented by Microsoft include:

Why Category 0 Matters

System messages help financial institutions monitor communication activity and manage technical interactions with a messaging infrastructure.

For example, delivery notifications can provide information about the handling of a message within a communication system.

Similarly, retrieval-related messages can support the investigation or recovery of relevant message information.

These capabilities are important for maintaining operational visibility and supporting financial messaging administration.

A delivery notification should not, however, be confused with proof that the underlying financial transaction has been settled or that the beneficiary has received the funds.

Category 1: Customer Payments and Cheques

Category 1 covers customer payment instructions and cheque-related financial communications.

Historically, this category has been especially important in international banking because it includes message types used to communicate customer credit transfers.

Common Category 1 Messages

Understanding MT103

MT103 is one of the most recognizable traditional SWIFT message types.

It has historically been used to communicate a single customer credit transfer between financial institutions.

A customer transfer message may contain information identifying the ordering customer, beneficiary, transaction amount, currency, and institutions involved.

This information helps banks process the payment instruction through the relevant financial infrastructure.

However, an MT103 message is not itself a guarantee of successful settlement or proof that money is available in the beneficiary's account.

The Role of MT199

MT199 is a free-format message used for communications that do not require a more specialized message type within Category 1.

Depending on the applicable rules and business context, it may be used to exchange information related to payment investigations or other banking communications.

Because it is free-format, its meaning depends on the content and context of the particular message.

MT199 is not a special payment instrument and does not independently transfer or release funds.

ISO 20022 and Customer Payments

The SWIFT cross-border payment environment has undergone significant modernization.

Following the conclusion of the main MT and ISO 20022 coexistence period in November 2025, applicable cross-border payment instructions transitioned to ISO 20022 messaging requirements.

For modern implementations, financial institutions should consult current CBPR+ specifications and applicable ISO 20022 message definitions, including the pacs message family.

Category 2: Financial Institution Transfers

Category 2 includes messages used for financial transactions between banking institutions.

These messages support interbank transfers, settlement-related activities, and related financial communications.

While Category 1 primarily addresses customer payment instructions, Category 2 focuses on transactions involving financial institutions.

Common Category 2 Messages

Understanding MT202

MT202 has historically been used to instruct transfers between financial institutions.

It belongs to the interbank messaging category rather than the customer credit transfer category.

This distinction matters because customer payment messages and interbank transfer messages serve different business purposes.

For modern cross-border payment implementations, institutions must evaluate the applicable ISO 20022 equivalents and rules rather than assuming that historical MT202 workflows remain valid for every payment scenario.

Why Category 2 Is Important

Interbank messaging supports financial relationships between banks and other participating institutions.

These relationships can involve settlement arrangements, correspondent banking services, and transfers made for the financial institutions' own accounts.

Standardized messaging helps participating institutions exchange relevant instructions consistently.

Category 3: Treasury, Foreign Exchange, Money Markets, and Derivatives

Category 3 includes messages associated with treasury operations and financial market transactions.

Banks and other market participants use treasury-related communication to manage foreign exchange positions, money market transactions, loans, deposits, and derivative contracts.

These activities require detailed and consistent transaction records.

Common Category 3 Messages

The Role of MT300 in Foreign Exchange

MT300 is traditionally associated with foreign exchange transaction confirmation.

When financial institutions enter foreign exchange transactions, they need to exchange consistent details about the agreed trade.

Such details may include the currencies, amounts, exchange rate, and settlement arrangements.

Standardized confirmation messages help participating institutions compare transaction records and identify potential discrepancies.

Treasury Messaging and Risk Management

Accurate treasury messaging supports transaction confirmation, settlement preparation, reconciliation, and operational risk management.

These activities are important because financial market transactions can involve significant values and complex contractual arrangements.

Consistent messaging helps financial institutions manage these processes more effectively.

Category 4: Collections and Cash Letters

Category 4 focuses on financial communications associated with collections and cash letters.

Collection processes may involve banks acting on behalf of customers to handle payment-related documents or collect amounts due under specified arrangements.

Common Category 4 Messages

How Collection Messages Support Banking Operations

Collection-related messages allow financial institutions to exchange information about payment handling, acceptance, refusal, and other collection activities.

For example, an acknowledgement message can confirm receipt of a particular communication, while an advice of non-payment can communicate an unsuccessful collection outcome.

These messages support the administration of collection processes and help financial institutions maintain consistent records.

Category 5: Securities Markets

Category 5 includes messages associated with securities trading, settlement, custody, corporate actions, and related financial activities.

Securities markets involve multiple participants, including investment firms, custodians, brokers, asset managers, and settlement organizations.

Standardized messages help these participants exchange information about securities transactions and holdings.

Common Category 5 Messages

Securities Settlement Messages

Messages such as MT540, MT541, MT542, and MT543 have historically been used to communicate securities receipt and delivery instructions.

The relevant message type distinguishes between securities movements involving payment and those without an associated payment instruction.

This distinction is important for securities settlement operations.

Corporate Actions

Corporate action messages support communications relating to events affecting securities.

Examples include dividend distributions, rights issues, and other corporate events.

Messages such as MT564 and MT565 help participating institutions communicate information and instructions related to these events.

Why Securities Messaging Matters

Securities transactions often involve complex processes and multiple financial organizations.

Standardized communication supports transaction accuracy, reconciliation, settlement management, and the exchange of information throughout the securities lifecycle.

Category 6: Treasury Markets and Precious Metals

Category 6 includes messaging associated with precious metals, syndicated facilities, and related treasury activities.

Financial institutions participating in metals markets may need to confirm trades, communicate transfer instructions, and report account information.

Common Category 6 Messages

Precious Metals Transactions

Financial institutions involved in precious metals trading may need standardized communications to document transactions and account movements.

These messages help distinguish trade confirmations, transfer instructions, notices, and account statements.

Syndicated Facilities

Category 6 also includes messages associated with syndicated financing arrangements.

Such arrangements may involve multiple financial institutions participating in a lending facility.

Messages can support communication relating to drawdowns, interest calculations, fees, and principal payments.

Category 7: Documentary Credits and Guarantees

Category 7 focuses on documentary credits, guarantees, and related trade finance communications.

Trade finance plays an important role in international commerce by supporting transactions between buyers, sellers, and financial institutions.

Letters of credit and bank guarantees can help parties manage contractual and payment-related risks.

Common Category 7 Messages

Understanding MT700

MT700 has historically been used to communicate the issuance of a documentary credit.

A documentary credit is a financial arrangement in which a bank undertakes an obligation under specified terms and conditions, commonly involving the presentation of compliant documents.

These arrangements are frequently associated with international trade.

Understanding MT760

MT760 is a traditional message type associated with guarantees.

Bank guarantees and similar instruments can provide contractual protection for parties involved in certain transactions.

The rights, obligations, validity, and enforceability of an instrument depend on its actual terms and applicable legal framework.

The existence of an MT760 message alone does not prove that a guarantee is authentic, enforceable, or financially backed.

What Is MT799?

MT799 is a free-format message in Category 7.

Its purpose is to facilitate general communication when a more specialized message format is not appropriate.

Although MT799 is sometimes discussed in connection with trade finance transactions, it does not automatically constitute a payment undertaking, bank guarantee, or proof of funds.

Financial institutions must assess its actual content and context.

Category 8: Travellers Cheques

Category 8 includes messages historically associated with travellers cheques.

Travellers cheques were once widely used as an alternative to carrying large quantities of cash during international travel.

Although modern electronic payment methods have substantially reduced their everyday use, historical financial messaging documentation includes message types for related activities.

Common Category 8 Messages

Why These Messages Were Important

Travellers cheque systems required financial institutions to communicate information about sales, settlement, refunds, stock management, and inventory adjustments.

Standardized messaging supported these processes across participating institutions.

Today, these message definitions are primarily useful for understanding historical financial infrastructure and maintaining relevant legacy applications.

Category 9: Cash Management and Customer Status

Category 9 includes messages associated with cash management, account reporting, balance information, and customer account activity.

These messages have historically been important for corporate treasury departments and financial institutions managing account information.

Common Category 9 Messages

Understanding MT940

MT940 has historically been used to communicate account statement information.

Banks and corporate customers can use account statements to reconcile transactions, review account activity, and support financial reporting.

Understanding MT950

MT950 is a statement message commonly associated with account reporting between financial institutions.

It provides structured information relevant to the account activity covered by the statement.

The Importance of Cash Management Messaging

Cash management requires accurate information about account balances, incoming funds, outgoing payments, and transaction activity.

Standardized account reporting helps organizations manage liquidity, maintain financial records, and reconcile banking transactions.

Microsoft SWIFT System and Control Messages

In addition to the ten MT categories, Microsoft's A4SWIFT documentation identifies system and control messages for GPA and FIN Control services.

These include messages associated with technical communication activities such as login requests, logout commands, session selection, and acknowledgements.

Examples include:

These system messages differ from the ordinary business-focused MT categories because they support technical operations rather than directly representing commercial banking transactions.

Summary of SWIFT MT Message Categories

The following table provides a quick reference to the message categories described in Microsoft's A4SWIFT documentation.

This classification demonstrates the extensive range of financial activities historically supported by SWIFT MT messaging.

How ISO 20022 Is Changing SWIFT Messaging

The international financial industry has increasingly moved toward ISO 20022, an international standard designed to support more detailed and structured financial information.

Traditional MT messages use predefined message structures, while ISO 20022 financial messaging commonly uses XML-based formats.

ISO 20022 supports richer data structures, making it possible to exchange more detailed information about financial transactions.

Key Advantages of ISO 20022

Improved data quality: Structured financial information can reduce ambiguity and support more consistent transaction processing.

Enhanced automation: Detailed data can help financial institutions automate payment processing, reconciliation, and reporting.

Stronger compliance capabilities: More structured information can improve the effectiveness of transaction screening and financial crime monitoring.

Better interoperability: Common financial messaging models help different payment systems and institutions exchange information consistently.

Support for innovation: Modern messaging standards create opportunities for improved payment services and financial technology integration.

The main coexistence period for traditional MT and ISO 20022 cross-border payment instructions ended in November 2025.

However, this does not mean that every MT message across every SWIFT service has been discontinued.

Different financial sectors and services maintain their own implementation requirements and migration schedules.

What Financial Software Developers Should Know

Developers creating applications for financial institutions must understand that supporting a particular message format involves more than recognizing its message identifier.

A compliant implementation may require message validation, correct field formatting, applicable business rules, security controls, and compatibility with the relevant messaging infrastructure.

For software integration projects, important considerations include:

1. Message compatibility: Determine which message types and standards releases apply to the intended financial service.
2. Validation: Ensure financial messages meet the applicable structural and business requirements.
3. Data transformation: Map internal application information to the required financial message structures.
4. System integration: Connect payment, treasury, securities, or reporting applications through approved interfaces.
5. Operational monitoring: Maintain appropriate transaction logs, error handling, and message processing controls.
6. Standards maintenance: Review changes to financial messaging standards and update applications when necessary.

Organizations working with Microsoft BizTalk environments should also verify their deployed accelerator version and supported standards release before selecting message schemas for production systems.

The Future of Financial Messaging and Banking Integration

Financial messaging will continue evolving as banks modernize their infrastructure and adopt new standards.

The transition toward ISO 20022 reflects growing demand for structured financial information, improved interoperability, and more automated processing.

Financial institutions are also exploring new technologies for cross-border payments, digital assets, financial market infrastructure, and transaction reporting.

These developments increase the importance of common data models and reliable communication standards.

Although traditional MT messages remain relevant in certain areas, financial software developers must recognize the continuing modernization of messaging requirements.

Understanding both historical MT formats and current ISO 20022 standards will help organizations maintain existing systems while planning future integrations.

Conclusion

SWIFT message types are an important part of the technical foundation of international banking and financial communication.

Microsoft's BizTalk Accelerator for SWIFT documentation provides an extensive historical reference covering system messages, customer payments, interbank transfers, treasury transactions, securities, trade finance, travellers cheques, and cash management.

Each MT category represents a specific area of financial activity, helping financial institutions communicate using consistent message structures.

From MT103 customer credit transfers and MT202 interbank transactions to MT760 guarantees and MT940 account statements, these message definitions have supported a broad range of banking operations.

However, the financial messaging landscape continues to evolve.

The increasing adoption of ISO 20022 means that institutions must distinguish historical message compatibility from current network requirements.

For banks, fintech companies, and software developers, understanding these messaging standards remains essential for building reliable integrations, supporting financial operations, and preparing for future developments in global banking.