Corporate Payments Explained: Real-World Banking Workflows

MT101 is a corporate payment initiation request to debit a customer's account, sent to banks or counterparts for domestic or international transfers; its ISO 20022 equivalent is pain.001.

Analyze the SWIFT MT101 message structure, outlining its five blocks—basic header, application header, user header, text block, and trailer—and their mandatory or optional fields.

Explore the structure of MT101 messages by examining block elements, including start and end indicators, block identifiers, separators, and how fixed parts combine with optional or variable blocks.

Zoom in on block four of the swift MT101 to analyze the text data, including sender reference and requested execution date, with sequence A mandatory and sequence B repetitive.

Nine network validated rules with error codes (C1, C2, etc.) apply to swift messages and affect multiple fields; usage rules guide constructing MT101 messages, and these have no error codes.

Explore how corporations initiate payments with empty MT101 and MT103 messages across four scenarios, detailing concentrating bank, debtor bank, data bank, intermediary bank, creditor bank, and beneficiary.

Explore how a concentrating bank processes MT101 payments by receiving MD 101 instructions, acting as debtor or forwarding bank, and issuing four follow-up messages.

Corporate AB generates an empty 101 to debit its subsidiary XYZ’s account at the debtor bank, with the concentrating bank forwarding MT101 and triggering MT103 to the creditor bank.

Corporate AB initiates an empty MT101 for its own account at databank, using the concentrating bank as forwarding agent to deliver it to databank, which then credits via MT103.

Corporation a sends an empty MT101 to debit its account at the concentrating bank, with a cross-border intermediary bank; the debtor bank then generates MT103 to the creditor bank.

Case four demonstrates a corporation initiating an mt101 to debit its own account via a concentrating bank with no intermediary, using empty 101 and 103 messages in a domestic payment.

Demonstrates initiating payments via SWIFT MT101, with a single debit from Saint-Gobain at Royal Bank of Scotland and multiple credits to beneficiaries at Royal Bank of Scotland and Barclays Bank.

Explain the MT101 message structure, detailing sequence A with sender and receiver, and sequence B with two transactions and mandatory fields like tag 20, 21, and 32.

Explore the MT101 narrative by examining how field 21R governs a single debit versus two debits for Saint Gobain’s payment to two beneficiaries, totaling 60,000 GBP.

Explain MT101 fields 50A and 57A as sender and beneficiary location indicators. Note 50A absence may indicate the sender owns the debit account; 71A charges can be ordering or shared.

Explain how MT101 uses field 50 A to designate the ordering customer across sequences A and B. Analyze the C three rule guiding single versus multiple debit accounts.

Explore how a Saint-Gobain payment uses a MT101 to fund two beneficiaries from debit accounts 31926819 and 31927829, with MT103 via Royal Bank of Scotland and Barclays Bank.

Explain the empty MT101 message, highlighting sequence A with sender and receiver, and sequence B funding two debit accounts for two beneficiaries, referencing the 103 message and BICs.

Explore how the MD 101 message narrative uses field 50 H in sequence B to fund multiple debit accounts, and how network validated rules illuminate MT101 use cases.

Explore how a parent company uses an empty SWIFT MT101 to debit a subsidiary’s account and pay a regional supplier via a forwarding bank, illustrating the end-to-end flow.

Explore the MT101 message by detailing sender and receiver, sequence A and B fields, the instructing party and ordering customer, debit and beneficiary accounts, remittance information, and charges.

An empty MT101 lets a parent debit a subsidiary's account through a forwarding bank, with remittance information 70 including the parent name for reconciliation.

Learn how the Swift MT101 payment message lets a parent company pay subsidiaries, driven by centralization and concentration, highlighting field 58 as the instructing party.

Explore a Swift MT101 scenario where a French parent company sends an empty MT101 to BNP Paribas for multiple beneficiaries via correspondent banks across Switzerland, Italy, and the United States.

Explore how a MT101 swift payment message is structured across sequences a and b, detailing sender, instructing party, beneficiaries, currency amounts, cross-border fx, and charges.

Explain the MT101 narrative of a single ordering customer paying multiple beneficiaries, including SEPA euro transfers, a cross-currency usd payment, and the fx options and cover vs serial payment structures.

Explore how the empty MT101 supports repatriation and refunds in cash management. Understand cash pooling as consolidating multiple accounts into a single pool to optimize liquidity and realize cost savings.

Explore a scenario where funds move from a Dresdner Bank secondary account to a BNP Paribas master account using MD 101, via a forwarding bank and creditor bank.

Explain the MT101 payment message structure, detailing sequence A fields, zero-balance and intercompany instruction codes, and the roles of master and slave accounts and the account servicing institution.

Explore the narrative of a SWIFT MT101 empty message used for funds repatriation between SLR's Dresdner Bank and BNP Paribas, including Cmsb and INTC instruction codes for cash pooling.

Explain how pain .001 replaces empty 101 in the RM world. Describe fields becoming elements and identify roles like initiating party, forwarding agent, debtor, debtor agent, creditor agent, creditor.

Compare MT101 and pain.001 side by side, outlining group header, payment information, and credit transfer structures, and map data elements such as creditor, creditor agent, remittance information, and instruction identifiers.

Learn how the MT101 empty 101 message works, its structure and usage rules, and how corporates pay from multiple or subsidiary accounts to support cash management, repatriation, with pain.001 mapping.