Skip to content
Corporate & Investment Banking My progress Français

Home / Corporate Banking / International Trade & Transaction Banking / Module 12

12Payments & Cash Management

Moving and Managing a Corporate's Money · Accounts, Payments, Collections, Liquidity Management and Treasury Connectivity

Running a group’s accounts: paying, collecting and steering its cash.

Reading time
1 h 00
Sections
52
Exercises
19
Recall questions
31
Quiz questions
15
Its place in Corporate Banking
  1. Origination
  2. Structuring
  3. Credit Analysis & Rating
  4. Approval
  5. Execution & Booking
  6. Servicing
  7. Monitoring
  8. Workout & Exit
  • KYC
  • Compliance
  • Risk
  • Legal
  • Operations
  • Finance
  • Data
  • Technology
  • Reporting
  • Treasury / ALM

Bridges to Capital Markets & Securities Services

This module teaches payments and cash management from zero, but goes deep enough for a professional

It assumes no prior knowledge of payment systems or of corporate treasury and builds every idea from its foundations. Yet it goes deep enough to be useful to someone who sells cash management to corporate treasurers, implements a payment factory or a cash pool, runs payment operations or fraud controls, designs connectivity between banks and enterprise systems, or leads a transformation around instant payments and ISO 20022.

Wherever a concept is technical, we stop and explain it in plain language before using it again. Wherever a term is jargon, we define it once and then rely on it.

Two threads run through everything: the business and the technology

The business thread covers what corporate treasurers need — visibility of cash, control of payments, efficient use of liquidity, protection against fraud — and how banks meet those needs with accounts, payment and collection services, cash pooling, virtual accounts and treasury centralisation structures such as payment factories and in-house banks; and why this low-risk, deposit-rich, fee-generating business is among the most valuable in corporate banking.

The technology thread covers the payment systems that move money — SEPA, instant payments, high-value systems, correspondent banking and SWIFT — the ISO 20022 message standard that now carries most of them, the channels that connect corporates to banks — host-to-host, SWIFT, EBICS, APIs — the statement and reporting data on which treasury depends, and the screening and fraud controls that every payment must pass.

Where this module sits in the Corporate Banking track

This module closes the International Trade & Transaction Banking block. Every product in the previous modules ends in a payment: a letter of credit is honoured, a supplier invoice is paid early, an export credit is disbursed, a commodity cargo's proceeds land in a collection account. Payments and cash management is the infrastructure on which all of them settle, and the daily relationship through which a bank knows its corporate clients best. The Treasury and ALM module that follows will look at the same deposits and liquidity from the bank's own side.

How to read this module

Read it as a narrative, not a reference card

Each part assumes you have read the ones before it. If you are short on time, read the section titles and the "In a nutshell" boxes first.

Each coloured box plays a fixed role

The boxes play the same roles as in the earlier modules: Key insight, Going deeper, IT & data lens, Worked example, Watch out, In a nutshell, Common misconception, Practice and Explain it back.

One running case: Helion's treasury transformation

Our bank is one of the main banks of Helion Industries, the Lyon aerospace and energy group of the earlier modules. Helion has grown by acquisition and now operates in 25 countries with about 120 bank accounts at 14 banks. Its group treasurer cannot see the group's cash in one place before midday, pays suppliers from dozens of local systems with different controls, and holds idle cash in some subsidiaries while others use overdrafts. Helion launches a request for proposals to centralise its cash management. Our bank wins the mandate to set up a payment factory, a cash pool, virtual accounts for its receivables, and modern connectivity to its treasury management system. Every number is invented to teach a mechanic.

The module is built to be worked, not only read

Practice boxes contain the calculations and designs cash management bankers and treasurers actually work on: the interest benefit of a cash pool, the liquidity value of operational deposits, value dates and cut-off times, charge options on cross-border payments, intercompany positions in a payments-on-behalf-of structure, the savings from virtual accounts, and the mapping of ISO 20022 messages to treasury needs.

A suggested path through the document

Four sessions work well: Part 1, what treasurers need and the product map; Part 2, the end-to-end flows of payments, collections, pooling and centralisation, in two sittings; Parts 3 and 4, the actors and the systems; Part 5, risks, two episodes and the transformation agenda.

What you will master

You will understand the corporate treasurer's needs

You will know why visibility, control, liquidity and security drive every cash management decision, and how a group's banking structure grows complex through acquisitions.

You will know the payment systems

You will know how SEPA credit transfers, instant payments, direct debits, high-value systems and correspondent banking work, and what ISO 20022 changes.

You will be able to design a cash management solution

You will be able to combine accounts, payment and collection services, virtual accounts, cash pooling, payment factories and in-house banks into a coherent structure for a multinational group.

You will understand the bank's economics

You will know why operational deposits are so valuable to banks, how fees and float contribute, and why cash management is the anchor of a corporate relationship.

You will be able to map the actors and the systems

You will know who does what among treasurers, banks, infrastructures, SWIFT, technology providers and regulators, and the systems and messages that connect them.

You will recognise the risks and the transformation agenda

You will know where payments fail — fraud, cyber-attacks, operational outages, sanctions breaches — and how instant payments, verification of payee, open banking and real-time treasury are reshaping the business.

1Context and the Big Picture

Before following a payment from Helion's treasury to a supplier's account, you need to understand what corporate treasurers want from their banks, how money actually moves between banks, the map of cash management products, and why banks value this business so highly.

What corporate treasurers need

Four needs behind every request

A group treasurer is responsible for making sure the company can always pay what it owes, that its cash is used efficiently, and that its money is safe. In practice, four needs drive every cash management decision.

Need Question it answers Typical solutions
Visibility Where is our cash, in which accounts and currencies, right now? Account reporting, statements, treasury management systems
Control Who can pay what, through which process, with which approvals? Payment factories, centralised channels, approval workflows
Liquidity Is idle cash being used to reduce debt or earn interest? Cash pooling, sweeping, in-house banks, investments
Security and compliance Are payments protected against fraud and errors, and compliant with sanctions and regulations? Controls, verification, screening, segregation of duties

How complexity accumulates

Helion's current situation is typical. Each acquired company came with its own banks and accounts; local finance teams pay suppliers from local systems; subsidiaries in some countries hold cash while others borrow; treasury collects balance information from banks in different formats, some by downloading files manually. The treasurer's first goal is to see everything in one place; the second, to control and centralise; the third, to optimise.

Figure 1 Helion today and tomorrow. A fragmented landscape of local banks, accounts and systems becomes a centralised structure with one payment factory, one cash pool and one view of cash.

How money moves between banks

Money is a bank entry

When Helion pays a supplier, no banknotes move. Helion's bank debits Helion's account and, directly or through intermediaries, causes the supplier's bank to credit the supplier's account. Between the two banks, the payment is settled either through a payment system in which both participate, or through correspondent accounts that banks hold with each other. Ultimately, banks settle with one another in central bank money, on accounts at the central bank.

The main payment systems in Europe

System What it does Characteristics
SEPA Credit Transfer (SCT) Euro credit transfers across the Single Euro Payments Area Executed by the next business day; low cost
SEPA Instant Credit Transfer (SCT Inst) Euro credit transfers in seconds, 24/7/365 Maximum 10 seconds end to end; mandatory in the euro area under the Instant Payments Regulation
SEPA Direct Debit (SDD) Creditor-initiated collections under a debtor's mandate Core scheme for consumers, B2B scheme for businesses
T2 (TARGET2's successor) Eurosystem real-time gross settlement for large and urgent euro payments Settles in central bank money, payment by payment
EURO1 and STEP2 EBA CLEARING systems for large-value and retail euro payments Private clearing systems settling in T2
National systems CHAPS and Faster Payments in the UK, Fedwire and ACH in the US, and others Each currency has its own infrastructure

Gross and net settlement

Payment systems settle either gross — each payment individually and immediately, as in T2, CHAPS or Fedwire, used for large and urgent payments — or net — payments are accumulated and only the net positions between banks are settled at set times, as in most retail systems. Instant payment systems combine immediate crediting of the beneficiary with settlement arrangements that guarantee the receiving bank.

Cross-border payments and correspondent banking

To pay a supplier in Brazil in reais, or in Vietnam in dollars, there is no single system. Helion's bank sends the payment through correspondent banks: banks that hold accounts for one another in the relevant currencies, linked by SWIFT messages. A dollar payment from Lyon to Hanoi may pass through Helion's bank, its US correspondent, the Vietnamese bank's US correspondent and the Vietnamese bank. Each step adds time, cost and the possibility of a deduction or delay. SWIFT gpi, introduced in 2017, lets banks track each payment end to end using a unique reference.

The G20 has made faster, cheaper, more transparent and more accessible cross-border payments a priority, with targets set for 2027: for wholesale payments, most should be credited within an hour and the remainder within a business day; costs and transparency should improve markedly. Progress reports by the Financial Stability Board show that the targets are hard to meet, but they drive initiatives on ISO 20022, longer operating hours of payment systems, and links between instant payment systems in different countries.

The cash management product map

Five families

Family Products Client need
Accounts Current accounts in many currencies and countries, account structures, virtual accounts Holding and identifying money
Payables Credit transfers, instant payments, high-value payments, cross-border payments, payroll, cards Paying suppliers, staff, taxes
Receivables Incoming payments, direct debits, virtual-account collections, card acquiring, lockbox Collecting and identifying receipts
Liquidity management Physical cash pooling, notional pooling, sweeping, intercompany loan tracking, investments Using cash efficiently
Channels and information E-banking, host-to-host, SWIFT, EBICS, APIs, statements and intraday reporting Connecting and seeing
Figure 2 The cash management product map. Accounts sit at the centre, with payables flowing out, receivables flowing in, liquidity management concentrating balances, and channels connecting it all to the treasurer.

Payables: paying suppliers, staff and the state

Corporates make a small number of large payments — to suppliers of materials, tax authorities, lenders — and a large number of small ones — salaries, expenses, small suppliers. They need the right instrument for each: SEPA credit transfers for routine euro payments, instant payments where speed matters, high-value payments for large or time-critical amounts, cross-border payments for foreign suppliers, cards for travel and small purchases.

Receivables: collecting and identifying

For a company, receiving money is easy; knowing what it is for is hard. Customers pay several invoices at once, quote wrong references, or pay into the wrong account. Reconciliation — matching each receipt to the invoices it settles — is one of the most labour-intensive tasks in finance departments. Direct debits, which the creditor initiates, and virtual accounts, which give each customer a unique account number, make it much easier, as Part 2 shows.

Liquidity management: putting cash to work

A group with cash in some subsidiaries and overdrafts in others pays more interest than it needs to. Cash pooling concentrates balances, physically or notionally, so that surpluses offset deficits. Larger groups go further, with an in-house bank that acts as a bank to its own subsidiaries.

Why banks value cash management

Deposits, fees and relationship

Cash management earns banks three kinds of income. Fees on payments, accounts, channels and services. Net interest income on the deposits that clients keep in their operating accounts — usually the largest component, especially when interest rates are positive. And relationship value: a bank that runs a client's cash management sees its business daily and is the natural provider of credit, FX, trade and other products.

Operational deposits are especially valuable

Under the Basel liquidity rules, the liquidity coverage ratio requires banks to hold liquid assets against the deposits that could leave in a 30-day stress. Deposits that corporates hold for operational purposes — to run their payments and cash management with the bank — are considered stickier: the outflow assumption is typically 25 per cent, against 40 per cent for non-operational corporate deposits. Operational deposits therefore cost the bank less in liquidity buffers and are worth more.

A low-risk, high-return business

Cash management consumes little capital — it is mainly a service business, with credit exposure limited to intraday and overdraft lines — and its revenues are recurring. Returns on capital are high, which is why many banks treat transaction banking as a strategic priority. The other side of the coin is heavy investment: payment systems, channels, compliance and security require large, continuous technology spending.

Work these through before reading on. Full solutions are in the Answer Key.

1.1 Which instrument?

Choose an instrument for each of Helion's payments: (a) monthly salaries for 3,000 employees in France; (b) a 40 million euro tax payment due today; (c) an urgent 80,000 euro payment to a supplier that will release a shipment only on receipt; (d) a 2 million dollar payment to a supplier in Brazil; (e) collection of monthly maintenance fees from 400 airline and utility customers in Europe.

(a) SEPA credit transfers in a bulk payroll file. (b) A high-value payment through T2, or instant if within limits and accepted by the beneficiary. (c) A SEPA instant credit transfer. (d) A cross-border SWIFT payment in dollars, tracked with gpi. (e) SEPA B2B direct debits under mandates.

1.2 Operational deposits

A bank holds 500 million euros of corporate deposits from a client; 300 million qualify as operational. Using outflow rates of 25 per cent for operational and 40 per cent for non-operational corporate deposits, compute the stressed outflow, and compare with the case where none qualify.

300 × 25% + 200 × 40% = 75 + 80 = 155 million euros. If none qualified: 500 × 40% = 200 million euros.

1.3 The cost of fragmentation

Three subsidiaries hold balances of +30, +20 and −45 million euros. Credit balances earn 1.0 per cent and overdrafts cost 5.0 per cent. Compute the group's annual net interest without pooling and with balances offset in a pool earning 1.0 per cent on the net.

Without pooling: 50 × 1.0% − 45 × 5.0% = 0.5 − 2.25 = −1.75 million euros. With pooling: net +5 million × 1.0% = +0.05 million. Benefit: 1.8 million euros a year.

Explain to a friend who runs a small business why a large company with money in one subsidiary and an overdraft in another is wasting money, and what a bank can do about it.

      1. What are the four needs of a corporate treasurer?

      2. How does a payment move between two banks?

      3. Distinguish gross and net settlement, with examples.

      4. Why are cross-border payments slower and costlier than domestic ones?

      5. Name the five families of cash management products.

      6. Why are operational deposits valuable to banks?

      1

      1. Which is NOT one of the corporate treasurer's needs?

      2. Gross versus net settlement:

      3. In what money do banks settle with each other?

      2The End-to-End Flow

      This part follows Helion's cash management from the account structure to the pooled balance at the end of the day: a supplier payment through eight steps, cross-border payments and their charges, collections with direct debits and virtual accounts, cash pooling, and the payment factory and in-house bank that bring it all together.

      Step zero — The account structure

      Accounts are the foundation

      Before anything moves, Helion needs the right accounts in the right places. The cash management design starts with an account structure: which entities hold accounts, in which currencies and countries, with which banks, linked to which pools. Our bank proposes to reduce Helion's 120 accounts to about 45: one operating account per entity and currency where local operations require it, header accounts for the pools, and virtual accounts for receivables.

      Opening and maintaining accounts

      Each account requires KYC on the entity, documentation of its authorised signatories and of who may give instructions through which channel, and local legal and tax formalities. For a group in 25 countries, account opening is a project in itself. Electronic bank account management — standardised messages for opening, changing and closing accounts and managing signatories — reduces the paperwork, but adoption remains uneven.

      A supplier payment in eight steps

      Step What happens Key control
      1. Invoice approval The invoice is matched and approved in the ERP Three-way match, segregation of duties
      2. Payment proposal and approval The payment run selects due invoices; treasury approves Dual approval, limits, sanity checks
      3. File creation and transmission A payment file is generated and sent to the bank Format validation, secure channel, signatures
      4. Bank validation The bank authenticates the file and checks format, duplicates and limits Authentication, duplicate detection
      5. Screening Sanctions and fraud screening Filters, fraud rules, verification of payee
      6. Execution and routing The bank debits the account and routes each payment through the right system Cut-off times, FX, liquidity
      7. Status reporting The bank returns statuses: accepted, rejected, executed Rejections handled quickly
      8. Statement and reconciliation The bank reports the debits; treasury and accounting reconcile Automated matching
      Figure 3 A supplier payment from Helion's ERP to the supplier's bank account. Each step has its message and its control.

      Steps 1 and 2 — From invoice to approved payment

      The ERP decides what to pay

      Rhône Usinage, the supplier met in the supply chain finance module, has delivered parts and invoiced Helion. Helion's ERP matches the invoice with the purchase order and the goods receipt and schedules it for payment on its due date. Each week, the payment run selects the invoices due and proposes payments, grouped by currency and bank account. Treasury reviews the proposal, checks unusual items, and two authorised people approve it.

      Step 3 — File creation and transmission

      ISO 20022 payment initiation

      The ERP or the treasury management system generates a payment file in the ISO 20022 pain.001 format — "customer credit transfer initiation" — containing, for each payment, the debtor account, the creditor's name, account number and bank identifier, the amount, currency, requested execution date and remittance information that tells the supplier which invoices are being paid. The file is signed and sent to the bank through a secure channel, as Part 4 explains.

      Step 4 — Bank validation

      What the bank checks before accepting

      Our bank authenticates the sender, verifies the signature and the authority of the approvers, validates the file's format, checks for duplicates — the same file or payment sent twice — and checks that the account has the funds or credit line. Files that fail are rejected immediately with a pain.002 status report explaining why.

      Step 5 — Screening

      Sanctions and fraud

      Every payment passes through sanctions screening, which compares names, addresses, banks and countries with sanctions lists, and fraud detection, which compares the payment with the client's normal behaviour: a new beneficiary, an unusual amount, an unusual country, a change of supplier bank details just before payment. Alerts are reviewed by analysts; true matches are blocked or reported.

      Verification of payee

      Since October 2025, payment service providers in the euro area must offer a verification of payee service before a credit transfer is executed: the payer's bank checks with the payee's bank whether the name provided matches the account's holder, and informs the payer of a match, close match or no match. The service targets a common fraud in which a supplier's bank details are fraudulently changed. Similar services exist in the United Kingdom as Confirmation of Payee.

      Step 6 — Execution and routing

      Choosing the system

      For each payment, the bank chooses the route: SEPA credit transfer for routine euro payments; SEPA instant for urgent ones; T2 for large or time-critical euro amounts; correspondent banking for other currencies and countries. It debits Helion's account and sends the payment in the corresponding interbank format — for SEPA, ISO 20022 pacs.008 messages.

      Cut-off times and value dates

      Each system and route has cut-off times: a payment received by the bank before the cut-off is executed that day; after it, the next business day. The value date is the date from which the debit or credit counts for interest. Treasurers plan payment runs around cut-offs to avoid late payments and to control when cash leaves their accounts.

      Cross-border payments and their charges

      Paying a supplier in Brazil

      Helion pays 2 million dollars to a Brazilian supplier. Our bank converts euros to dollars if Helion's account is in euros, then sends the payment through its US correspondent to the Brazilian bank's correspondent, with a SWIFT gpi reference that lets Helion track it.

      Who pays the charges?

      Option Meaning Effect
      SHA (shared) Each party pays its own bank's charges Intermediaries may deduct fees from the amount
      OUR Payer pays all charges Beneficiary should receive the full amount
      BEN Beneficiary pays all charges All charges deducted from the amount

      Step 7 — Status reporting

      Knowing what happened

      The bank reports the status of each payment — accepted, rejected, pending, executed — through pain.002 messages. Rejections after acceptance, such as a closed beneficiary account, come back as returns. A treasurer who knows within minutes that a payment failed can fix it before the supplier complains; one who learns it from the supplier days later cannot.

      Step 8 — Statements and reconciliation

      Reporting the movements

      At the end of the day, the bank sends a statement in camt.053 format, listing every movement with its references; during the day, camt.052 intraday reports and camt.054 notifications show movements as they happen. Helion's treasury system loads them, updates its cash position, and passes the movements to accounting, which matches debits with the payments made and credits with the invoices they settle.

      Collections: getting paid and knowing by whom

      Incoming credit transfers

      Most of Helion's customers pay by credit transfer. The challenge is reconciliation: a customer may pay four invoices with one transfer, deduct a credit note, or quote an internal reference. Rich ISO 20022 remittance information helps, if the customer's bank and system populate it.

      Direct debits

      For recurring collections — maintenance contracts, service fees — Helion can use SEPA direct debits: with the customer's signed mandate, Helion's bank collects the amount from the customer's bank on the due date. The Core scheme gives the debtor a right to a refund for eight weeks without justification; the B2B scheme, for business customers, gives no such right but requires the debtor's bank to verify the mandate. Direct debits give the creditor control of the timing and near-perfect reconciliation.

      Virtual accounts

      Our bank proposes virtual accounts for Helion's aftermarket business: each customer receives a unique account number — a virtual IBAN — that routes its payments into one of Helion's real accounts, while identifying the payer automatically. When a customer pays, the bank's report shows the virtual account, and Helion's system knows instantly who paid.

      Liquidity management: cash pooling

      Physical pooling

      In a physical cash pool, or zero-balancing structure, the balances of participating accounts are transferred each evening to a header account held by the group's treasury entity: surpluses move up, deficits are covered by transfers down, and each participating account ends the day at zero — or at an agreed target balance. The group earns interest on its net position; the transfers create intercompany loans between the treasury entity and each subsidiary, which must be recorded and remunerated at arm's-length rates.

      Notional pooling

      In a notional pool, no money moves: the bank calculates interest on the sum of the participants' balances, as if they were combined, while each account keeps its own balance. Notional pooling avoids intercompany loans but requires cross-guarantees between participants and is constrained by accounting rules on offsetting and by banks' capital and leverage requirements, which have made it less widely offered, particularly across currencies.

      Figure 4 Physical and notional pooling. In a physical pool balances are swept to a header account each evening; in a notional pool they stay in place and the bank calculates interest on the combined position.

      Legal and tax constraints

      Pooling is not always possible or simple. Some countries restrict cross-border pooling or require central bank approvals; intercompany loans must respect transfer-pricing rules, thin-capitalisation rules and, in some countries, withholding tax; directors of subsidiaries must ensure participation is in their company's interest. Groups therefore often run a euro pool and pools in other major currencies, with countries such as China, India or Brazil managed separately.

      Centralisation: payment factory, POBO and in-house bank

      The payment factory

      A payment factory centralises the execution of the group's payments in one place — here, Helion's treasury centre in Lyon. Subsidiaries approve invoices in their ERPs; the factory receives payment instructions, applies group controls, formats files and sends them to a small number of banks through one connectivity channel. Controls, fraud prevention and bank charges improve; local bank accounts and channels can be closed.

      Paying and collecting on behalf of

      In a payments on behalf of structure, or POBO, the factory pays suppliers from the treasury entity's own account on behalf of the subsidiaries that owe them; each payment creates an intercompany position between the subsidiary and the treasury entity. Collections on behalf of, or COBO, does the same for receipts. POBO and COBO reduce the number of accounts dramatically, but raise legal, tax and accounting questions — for example, invoices addressed to the subsidiary but paid by another entity — that must be checked country by country.

      The in-house bank

      An in-house bank goes further: the treasury entity acts as a bank to the subsidiaries, holding intercompany accounts for each, on which POBO payments, COBO receipts, pool sweeps and intercompany loans are booked. Subsidiaries see an internal statement; the group's external banking is concentrated on a few accounts. Large multinationals typically combine a payment factory, pooling and an in-house bank, supported by their treasury management system.

      Figure 5 Helion's target structure: subsidiaries send invoices to the payment factory, which pays on their behalf through the in-house bank, with balances concentrated in the euro cash pool.

      Work these through before reading on. Full solutions are in the Answer Key.

      2.1 Cut-off

      Helion's treasury sends a SEPA credit transfer file at 17:30 on a Friday; the bank's cut-off for same-day execution is 16:00. When is the payment executed, and what could Helion have done if the payment was urgent?

      After Friday's cut-off, the SEPA credit transfer is executed on the next business day, Monday. For urgency, Helion could have sent a SEPA instant payment, available 24/7, or sent the file before the cut-off.

      2.2 Charges

      Helion pays 50,000 dollars to a supplier in India with SHA charges. Our bank charges Helion 20 euros; an intermediary deducts 30 dollars; the beneficiary's bank deducts 20 dollars. How much does the supplier receive? What would change with OUR?

      The supplier receives 50,000 − 30 − 20 = 49,950 dollars; Helion pays its own bank's 20 euros. With OUR, the supplier should receive 50,000 dollars, and Helion pays all charges, including intermediary and beneficiary bank charges billed to it.

      2.3 POBO

      Helion's payment factory pays, on behalf of three subsidiaries, supplier invoices of 1.2 million, 0.8 million and 2.5 million euros from the treasury entity's account. What intercompany positions arise, and how are they settled?

      Each subsidiary owes the treasury entity the amount paid on its behalf: 1.2, 0.8 and 2.5 million euros, booked on its intercompany account in the in-house bank. They are settled by netting with amounts the treasury entity owes the subsidiaries, such as COBO receipts and pool positions, by periodic settlement, or by intercompany loans bearing interest.

      2.4 Virtual accounts

      A company receives 6,000 payments a month; 75 per cent are matched automatically and each manual match takes 5 minutes. With virtual accounts, the automatic rate reaches 96 per cent. How many hours a month are saved?

      Before: 1,500 manual matches × 5 minutes = 125 hours. After: 240 × 5 = 20 hours. Saving: 105 hours a month.

      2.5 Intercompany interest

      In Helion's euro pool, the subsidiary with −50 million euros has effectively borrowed from the header account for a year. At an arm's-length intercompany rate of 3.00 per cent, what does it pay, and what do the subsidiaries with surpluses receive at 1.75 per cent? Does the group's total interest change?

      The −50 million subsidiary pays 1.5 million euros; the −30 million subsidiary pays 0.9 million; the surplus subsidiaries receive 120 × 1.75% = 2.1 million. The header earns 0.6 million externally. The treasury entity's net is 1.5 + 0.9 + 0.6 − 2.1 = 0.9 million. The group's total remains +0.6 million: intercompany interest redistributes it between entities.

      Explain to a relative how a company with dozens of subsidiaries can pay all its suppliers from one place, and why it needs its bank to tell it every movement on its accounts.

          1. Name the eight steps of a supplier payment and a control at each.

          2. What is verification of payee, and which fraud does it target?

          3. What are cut-off times and value dates?

          4. Explain SHA, OUR and BEN.

          5. How do SEPA Core and B2B direct debits differ?

          6. Distinguish physical and notional pooling, and name a constraint on each.

          7. What are a payment factory, POBO and an in-house bank?

          2

          1. What is verification of payee?

          2. What do cut-off times determine?

          3. What is the last step of a supplier payment?

          3Roles, Actors, and Interactions

          Cash management connects a corporate's treasury, accounting and IT teams with banks, payment infrastructures, SWIFT, technology providers and regulators. This part maps the cast, explains how multinationals choose and organise their banks, and shows how the cash management mandate ties into the rest of the corporate relationship.

          The cast of cash management

          Party Role
          Group treasury Defines cash management policy, bank relationships, pooling, payment controls
          Shared service centres and local finance Approve invoices, run accounts payable and receivable, reconcile
          Corporate IT Runs the ERP, the treasury management system and the connectivity
          Cash management banks Provide accounts, payments, collections, pooling, channels and reporting
          Partner and local banks Provide in-country services where the main bank has no presence
          Payment infrastructures Clear and settle payments: T2, EBA CLEARING, national systems
          Scheme managers Write the rules of payment schemes, such as the European Payments Council for SEPA
          SWIFT Provides messaging between banks and, for some corporates, between corporates and banks
          Technology providers Treasury management systems, ERP vendors, connectivity and fintech providers
          Regulators and central banks Payment services law, instant payments, anti-money laundering, oversight of infrastructures
          Figure 6 The cast of cash management. The corporate's treasury and systems connect through channels to its banks, which connect through infrastructures and SWIFT to every other bank.

          Inside the corporate

          Group treasury

          Helion's group treasury — a dozen people in Lyon — sets policy: which banks the group uses, which accounts may exist, how payments are approved, how cash is pooled and invested, how FX and interest-rate risks are hedged. It runs the payment factory and the in-house bank, and owns the relationship with cash management banks. Its main tool is the treasury management system, which holds cash positions, forecasts, intercompany accounts, debt and hedges.

          Shared service centres and local finance

          Day-to-day accounts payable and receivable are handled by shared service centres — Helion has one in Poland and one in Portugal — and by local finance teams. They approve invoices, prepare payment runs, apply cash and chase customers. Their efficiency depends heavily on the quality of the bank's reporting.

          Corporate IT

          The ERP, the treasury system and the connectivity to banks are run by IT. Many cash management projects succeed or fail on IT resources: mapping ERP data to ISO 20022 formats, testing files with each bank, managing security certificates.

          Inside the bank

          The cash management team

          Team Role
          Coverage and transaction banking sales Owns the client relationship for cash management; leads RFP responses
          Solution structuring Designs account structures, pooling, payment factory and connectivity solutions
          Implementation Opens accounts, sets up channels, tests files, migrates the client
          Client service Answers daily queries, investigates payments, handles exceptions
          Product management Defines products, pricing, roadmaps, scheme participation
          Operations Processes payments, investigations, returns, cheques where they survive
          Compliance and fraud Sanctions and fraud screening, KYC and account monitoring
          Technology Payment engines, channels, APIs, statements

          Implementation is a profession

          Winning a cash management mandate is the beginning, not the end. Implementing Helion's new structure — opening 45 accounts in 25 countries, setting up host-to-host connectivity, testing every payment type, migrating pools, closing old accounts — will take twelve to eighteen months and dozens of people on both sides. Clients judge banks heavily on implementation quality, and a poor implementation can sour a relationship for years.

          How multinationals organise their banks

          Fewer banks, clearer roles

          Large groups typically reduce the number of cash management banks to a few, assigning roles: one or two global or regional banks for the main currencies, pooling and the payment factory, and local banks where regulation or market practice require in-country accounts — for example to pay taxes, salaries or local suppliers in some countries.

          Overlay structures

          In an overlay structure, the group keeps local accounts with local banks for in-country payments and collections, and sweeps the balances into accounts with the overlay bank, which runs the regional pool. The overlay bank provides the concentration and reporting; the local banks provide local services. Global banks with large networks can offer in-country accounts in many countries themselves, reducing the need for local partners.

          Partner bank networks

          Banks without branches in every country offer coverage through partner banks: correspondent relationships with local banks that open accounts for the client, connected to the main bank's channels and reporting. The client sees one bank; behind it, several work together.

          The request for proposals

          How Helion chose its bank

          Helion's RFP asked banks for their proposed account structure, pooling solution, payment factory and POBO support, country coverage, channels and formats, reporting, fraud controls, implementation plan, references and pricing. Banks were scored on solution fit, coverage, technology, implementation capability, service and price — and on their commitment to Helion's credit facilities.

          Credit and cash management are linked

          Helion's 600 million euro revolving facility, met in the first module, is provided by six banks. Each expects a share of Helion's ancillary business — cash management, FX, trade — in return for committing credit. Treasurers allocate cash management mandates partly to reward relationship banks; banks that lend without winning ancillary business often reduce their commitment at the next refinancing. Cash management is therefore part of the bank's overall wallet with the client, as the coverage module explained.

          Payment infrastructures and scheme managers

          Who runs the rails

          The Eurosystem runs T2 for large-value euro payments and TIPS for instant payment settlement in central bank money. EBA CLEARING, owned by banks, runs EURO1 for large-value and STEP2 and RT1 for retail and instant euro payments. National clearing houses run domestic systems. The European Payments Council writes and maintains the SEPA schemes' rulebooks. Banks participate directly, or indirectly through another bank.

          SWIFT

          SWIFT is a cooperative owned by its member banks that provides the messaging network for cross-border payments, securities and trade, and for many market infrastructures. It also lets large corporates connect to their banks through SWIFT, using one channel for all banks. It operates the Customer Security Programme, introduced after the cyber-attacks described in Part 5, which requires users to attest compliance with security controls.

          Technology providers and fintechs

          TMS, ERP and connectivity providers

          Treasury management systems — from providers such as Kyriba, FIS, ION and SAP — sit between the corporate's ERP and its banks, generating payment files, receiving statements, and calculating positions. Connectivity providers and SWIFT service bureaux link corporates to banks. Fintechs and payment institutions offer payment and collection services, often specialised in cross-border or e-commerce payments, sometimes competing with banks and sometimes using them as infrastructure.

          Regulators

          The European framework

          The Payment Services Directive, revised in 2015 as PSD2, regulates payment services, requires strong customer authentication for electronic payments, and obliges banks to give licensed third parties access to accounts through APIs with the customer's consent — the basis of open banking. A further revision, splitting the framework into a directive and a directly applicable regulation, has been negotiated by EU institutions. The Instant Payments Regulation of 2024 requires euro-area payment service providers to offer instant euro payments at no higher price than standard transfers, with verification of payee. Anti-money laundering rules apply to every payment.

          Work these through before reading on. Full solutions are in the Answer Key.

          3.1 Bank roles

          Helion operates in France, Germany, the UK, the US, Brazil, India, China and Vietnam. Propose a banking structure — global, regional and local roles — and say where in-country accounts are likely to be needed.

          A global or regional bank for euro, sterling and dollar accounts, the euro pool and the payment factory in Europe and the US; in-country accounts with a local or partner bank where regulation or practice require them, likely in Brazil, India, China and Vietnam, managed separately or through overlay sweeps where permitted.

          3.2 RFP scoring

          List six criteria Helion should use to score cash management proposals, and explain why the lowest price should not decide alone.

          Solution fit; country coverage; technology and channels; reporting and data; implementation plan and references; service model; fraud and security controls; price; credit commitment. Price alone ignores implementation risk, service quality and the cost of a failed migration, which far exceed fee differences.

          3.3 Wallet

          One of Helion's six revolving-facility banks receives no ancillary business. What may it do at the next refinancing, and what could Helion offer it?

          It may reduce or withdraw its commitment at the next refinancing. Helion could offer it a share of ancillary business: a local cash management role, FX hedging, trade finance, or a role in a future bond or acquisition financing.

          Explain to a friend why a large company's choice of bank for its everyday payments is linked to which banks lend it money.

              1. Name the parties involved in a corporate's cash management.

              2. What does group treasury do, and what is its main tool?

              3. Why is implementation so important in cash management?

              4. What is an overlay structure?

              5. How are cash management and credit linked?

              6. What do PSD2 and the Instant Payments Regulation require?

              3

              1. What is group treasury's main tool?

              2. Why is implementation so important in cash management?

              3. What does an in-house bank do?

              4Systems, Data, and IT

              Cash management is one of the most technology-intensive businesses in banking: millions of payments a day, near-zero tolerance for error, twenty-four-hour instant processing, and direct connections to clients' systems. This part opens the seven building blocks of the cash management stack, explains the ISO 20022 messages that now carry most payments, and shows how channels and data are changing.

              Seven building blocks run a cash management business

              Block Purpose Typical tools
              Core accounts Balances, postings, interest, fees, account structures Core banking systems
              Payment engine and payment hub Validation, routing, execution, scheme connectivity, returns Payment hubs from specialised vendors or in-house
              Liquidity management Pooling, sweeps, notional calculations, intercompany tracking Liquidity management modules
              Virtual accounts and receivables Virtual account structures, matching, collections Virtual account platforms, reconciliation tools
              Channels E-banking, host-to-host, SWIFT, EBICS, APIs Channel platforms, API gateways
              Screening and fraud Sanctions filters, fraud detection, verification of payee Screening engines, behavioural analytics
              Reporting and data Statements, intraday reports, analytics Reporting engines, data platforms
              Figure 7 The cash management stack. The payment hub and core accounts sit at the centre, connected to channels on the client side and to payment systems on the market side, with screening in the flow.

              The payment hub

              One engine for many rails

              Banks historically ran separate systems for each payment type — domestic, SEPA, high-value, cross-border. Modern banks consolidate them into a payment hub that receives payments from every channel, validates and enriches them, applies screening, chooses the route, connects to each scheme or correspondent, and handles returns and investigations. A hub makes it easier to add new rails, such as instant payments, and to apply consistent controls.

              Instant payments change the architecture

              Instant payments must be processed in seconds, around the clock, every day of the year. Screening, fraud checks, liquidity management and account posting must therefore work in real time, without the batch windows and overnight processing that legacy systems relied on. For many banks, the Instant Payments Regulation forced a modernisation of the whole payment chain, including real-time sanctions screening and continuous liquidity management for their positions in TIPS or RT1.

              ISO 20022: the common language of payments

              Rich, structured messages

              ISO 20022 is an international standard for financial messages, using structured data with defined fields for parties, addresses, amounts, purposes and remittance information. It replaced older formats in SEPA from the start, in T2 in March 2023, in CHAPS in 2023, in the US Fedwire system in 2025, and in SWIFT cross-border payments, where the coexistence period with the older MT messages ended in November 2025.

              Message Purpose Between
              pain.001 Customer credit transfer initiation Corporate to bank
              pain.002 Payment status report Bank to corporate
              pain.008 Direct debit initiation Corporate to bank
              pacs.008 Customer credit transfer Bank to bank
              pacs.009 Financial institution credit transfer Bank to bank
              pacs.004 Payment return Bank to bank
              camt.052 Intraday account report Bank to corporate
              camt.053 End-of-day statement Bank to corporate
              camt.054 Debit and credit notification Bank to corporate

              Why structure matters

              Structured data improves three things. Screening: names, addresses and countries in separate fields produce fewer false alerts than free text. Reconciliation: structured remittance information lets the beneficiary match payments to invoices automatically. Straight-through processing: fewer manual repairs at each bank along the chain. The benefits come only if every party in the chain populates the fields properly — a work in progress for many corporates and banks.

              Channels: how corporates connect

              Five channels

              Channel Description Typical users
              E-banking portal Web or mobile access; manual uploads, approvals, reports Small companies, local entities, back-up
              Host-to-host Direct secure file transfer between the corporate's systems and the bank Large corporates with one main bank per region
              SWIFT for corporates One SWIFT connection for all banks Large multinationals with many banks
              EBICS Standard bank-corporate protocol used in France, Germany and Switzerland Corporates in those markets
              APIs Real-time calls for payments, balances and statuses Corporates and fintechs integrating banking into their systems

              From files to APIs

              File-based channels send payments in batches and receive reports periodically. APIs let a corporate's system initiate a payment, check its status or query a balance in real time, one call at a time. They suit instant payments, real-time treasury and embedding payments into business processes, such as paying a supplier the moment goods are received. Most large corporates will run files and APIs side by side for years.

              Corporate connectivity depends on security credentials that expire: certificates for host-to-host and EBICS, SWIFT keys, API tokens. Many payment outages at corporates are caused not by bank failures but by an expired certificate or an unmanaged credential change. Treasury and IT should keep an inventory of channels, credentials and expiry dates, and test failover to a back-up channel.

              Liquidity management systems

              Pools, sweeps and intercompany tracking

              Liquidity management systems run the end-of-day sweeps of physical pools, calculate notional pool interest, record the intercompany positions created by sweeps, compute intercompany interest, and report to the treasurer. For international groups, they handle multiple currencies, time zones and cut-offs — sweeping Asian accounts before European ones, and European before American.

              Virtual accounts and receivables

              Many numbers, one real account

              A virtual account platform issues account numbers that are not real accounts but route to a real account, with the virtual number attached to each incoming payment. The bank can create thousands for one client, attach them to customers, projects or subsidiaries, and report them in camt messages. Virtual accounts also support POBO and COBO structures, by allowing payments and receipts on behalf of different entities through one real account.

              Screening and fraud

              Real-time controls on every payment

              Sanctions screening compares parties, banks and countries with lists; fraud detection analyses behaviour: new beneficiaries, changed bank details, unusual amounts and times. For instant payments, both must decide in fractions of a second. Verification of payee adds a name check before execution. Banks increasingly use machine learning to reduce false positives and detect new fraud patterns, and share fraud information through industry schemes where law allows.

              Reporting and data

              From statements to real-time treasury

              Corporates used to receive one statement a day. With intraday reports, real-time notifications and APIs, treasurers can see positions continuously and forecast cash more accurately. Banks also use the data — with appropriate consent and confidentiality — to offer analytics: cash-flow forecasting, benchmarking of payment terms, detection of anomalies in the client's flows.

              Work these through before reading on. Full solutions are in the Answer Key.

              4.1 Messages

              Which ISO 20022 message does each of these use: Helion sends its weekly supplier payments; the bank tells Helion one payment was rejected; Helion collects maintenance fees by direct debit; Helion's system receives notice of a customer's payment on a virtual account; the bank sends the end-of-day statement; a supplier's bank returns a payment to a closed account.

              pain.001; pain.002; pain.008; camt.054; camt.053; pacs.004.

              4.2 Channel choice

              Recommend channels for: Helion's group payment factory working with three banks; a small subsidiary in Vietnam with one local bank; Helion's e-commerce spare-parts shop wanting to confirm customer payments instantly.

              Payment factory with three banks: SWIFT for corporates, or host-to-host with each bank; small Vietnamese subsidiary: the local bank's e-banking portal; e-commerce shop: APIs with real-time notifications.

              4.3 Instant readiness

              List five changes a bank's systems need to process instant payments 24/7.

              Real-time account posting 24/7; real-time sanctions and fraud checks; continuous liquidity management for instant settlement positions; verification of payee service; channels and APIs available 24/7 with real-time status; operations and support coverage outside business hours.

              4.4 Structured data

              Explain how structured addresses in ISO 20022 reduce sanctions false positives, with an example.

              With free text, a screening engine may match words anywhere in an address line against a list, for example a street name matching a sanctioned person's name. With separate fields for name, street, town and country, it can screen the name against names and the country against country lists, reducing false matches.

              Explain to a colleague in IT why switching a bank's payments from overnight batches to instant processing changes almost every system involved.

                  1. Name the seven building blocks of the cash management stack.

                  2. What does a payment hub do, and why do banks build them?

                  3. What is ISO 20022, and which systems have adopted it?

                  4. Name the pain, pacs and camt messages used in a payment's life.

                  5. Compare the five channels between corporates and banks.

                  6. Why does structured data matter for screening and reconciliation?

                  4

                  1. What does a payment hub do?

                  2. Which system has adopted ISO 20022?

                  3. Which is NOT a block of the cash management stack?

                  5Risks, Pain Points, and Transformation

                  Payments look routine until they fail. A fraudulent instruction, a cyber-attack, a system outage or a sanctions breach can cost a client or a bank millions in minutes. This part maps the risks, studies the Bangladesh Bank cyber-heist and the European move to instant payments with verification of payee, and sets out the transformation agenda.

                  A MECE map of cash management risk

                  Risk What goes wrong Typical control
                  Payment fraud Fake supplier bank details, CEO fraud, account takeover Verification of payee, call-backs, dual approval, behavioural analytics
                  Cyber Attackers compromise the bank's or the client's systems to send payments Security controls, SWIFT CSP, segregation, monitoring
                  Operational and outage Systems fail, files lost or duplicated, cut-offs missed Resilience, back-up channels, duplicate checks
                  Sanctions and AML Payments to sanctioned parties; laundering through accounts Screening, monitoring, KYC
                  Intraday liquidity and credit Overdrafts, intraday exposures, failed settlement Limits, liquidity management
                  Third-party and infrastructure Failure of a payment system, cloud provider or vendor Contingency arrangements, DORA requirements
                  Legal and regulatory Breach of payment rules, data protection, consumer protections Compliance, documentation
                  Figure 8 Where cash management risks arise along the payment chain: fraud at the client and initiation stages, cyber and outage in the systems, sanctions in screening, infrastructure risk in settlement.

                  Business email compromise

                  The most common fraud against corporates is business email compromise: a fraudster impersonates a supplier, an executive or a lawyer by email, and persuades the company to change a supplier's bank details or to make an urgent confidential payment. The company authorises the payment itself, so the bank executes it correctly — and the money is moved on within hours. Prevention depends on the client's controls — call-backs on a known number before changing bank details, dual approval, training — and on bank tools such as verification of payee and behavioural fraud detection.

                  Two episodes that reshaped payments

                  The Bangladesh Bank heist, 2016 — when the attackers had the keys

                  What happened

                  In February 2016, attackers who had compromised the systems of Bangladesh Bank, the central bank of Bangladesh, sent dozens of fraudulent SWIFT payment instructions to the Federal Reserve Bank of New York, which held the central bank's dollar reserves, asking for nearly 1 billion dollars to be transferred to accounts in the Philippines and Sri Lanka. Most were stopped, partly because of a spelling error and partly because of checks on the beneficiaries, but around 81 million dollars reached accounts in the Philippines and was laundered through casinos; only a fraction was recovered. The attackers had studied the bank's procedures, installed malware that hid the fraudulent messages from the bank's staff, and timed the attack around weekends and holidays in Bangladesh, New York and the Philippines.

                  Root cause

                  Weak security around the bank's SWIFT connection and internal systems, allowing attackers to send authenticated messages; and controls that could be bypassed by malware hiding the evidence.

                  The lesson

                  The SWIFT network itself was not breached, but the attack showed that the security of a payment network is only as strong as its weakest user. In response, SWIFT launched its Customer Security Programme, requiring every user to implement and attest compliance with mandatory security controls, and introduced tools to detect anomalous payment patterns. Banks reinforced the separation of payment systems from general IT, monitoring of payment flows, and controls on unusual instructions.

                  Instant payments and verification of payee, 2024–2025 — when speed required new protection

                  What happened

                  The EU's Instant Payments Regulation, which entered into force in April 2024, required payment service providers in the euro area to be able to receive instant euro credit transfers by January 2025 and to send them by October 2025, at a price no higher than standard transfers, and to offer verification of payee for all credit transfers by October 2025. Non-euro EU countries follow later. The regulation also requires sanctions screening based on daily checks of the provider's own clients against EU lists, rather than screening each instant payment individually.

                  Root cause of the problem it addressed

                  Instant payment schemes had existed in the euro area since 2017, but adoption was patchy and prices often higher than for standard transfers. At the same time, instant payments make fraud faster: once a payment is credited in seconds, it can be moved on before anyone notices.

                  The lesson

                  Speed and safety must be designed together. Making instant payments the norm required banks to rebuild their payment chains for real time and, simultaneously, to add a new check — verification of payee — that addresses the most common fraud. For corporates, instant payments create new possibilities — paying suppliers on receipt, real-time treasury — and new obligations to control who can initiate payments.

                  Persistent pain points

                  Cross-border payments remain slow and opaque for some corridors

                  Despite gpi and ISO 20022, payments to many emerging markets still pass through several correspondents, with deductions, delays and requests for information. The G20 targets for 2027 will be hard to meet for these corridors.

                  Fragmented connectivity

                  Multinationals still connect to many banks through different channels and formats. Even with ISO 20022, each bank implements the standard with its own variations, so corporates must test and maintain each connection separately.

                  Cash forecasting

                  Treasurers consistently name cash forecasting as one of their hardest tasks. Bank data shows what has happened; forecasting requires data from sales, procurement and operations, which sit in different systems.

                  Operational resilience

                  Corporates depend on their banks' systems being available, and banks depend on infrastructures and technology providers. The EU's Digital Operational Resilience Act, applicable since January 2025, requires financial entities to manage ICT risks and oversee critical third-party providers.

                  Five transformation moves

                  Move What it means Benefit
                  Instant and real-time treasury Instant payments, real-time reporting, 24/7 liquidity Faster cash conversion, better visibility
                  APIs and embedded payments Payments initiated and tracked from ERPs and business processes Automation, fewer files
                  Data-driven services Forecasting, analytics, anomaly detection on clients' flows Better treasury decisions
                  Stronger fraud prevention Verification of payee, behavioural analytics, shared fraud intelligence Fewer losses
                  New settlement assets Tokenised deposits, wholesale central bank digital currency experiments Programmable, round-the-clock settlement

                  Tokenised deposits and programmable money

                  Several large banks have launched or tested tokenised deposits — bank deposits represented on a distributed ledger — that let corporates move money between their own accounts in different locations around the clock, and potentially program payments to execute automatically when conditions are met. Central banks, including the Eurosystem, are exploring settlement of such transactions in central bank money. These developments remain early, but could change how intra-group liquidity and conditional payments work.

                  Figure 9 Helion's cash management roadmap: rationalise accounts and centralise payments, then connect in real time, then use data for forecasting and automation.

                  Work these through before reading on. Full solutions are in the Answer Key.

                  5.1 Business email compromise

                  Helion's accounts payable team receives an email, apparently from Rhône Usinage, announcing new bank details for future payments. Design the controls that should apply before the change.

                  Treat the email as unverified; call the supplier on a phone number already on file, not one in the email; require the change through a formal process with documentary evidence; apply dual approval to master data changes; hold the first payment to the new account for additional review; use verification of payee; train staff on the pattern.

                  5.2 Classify the risk

                  Name the risk: a payment file is sent twice and executed twice; a fraudster takes control of a treasury user's credentials and approves payments; an instant payment to a sanctioned entity is executed; T2 suffers an outage on a tax payment date.

                  Duplicate file: operational risk. Stolen credentials: cyber and fraud risk. Instant payment to a sanctioned entity: sanctions risk. T2 outage: infrastructure risk.

                  5.3 Verification of payee

                  Helion's payment to a supplier returns a "close match" result: the name differs slightly from the account holder's. What should Helion do, and who bears the risk if it proceeds?

                  Helion should check with the supplier through a known channel whether the account belongs to it before paying. If it proceeds despite the warning, it generally bears the risk if the payment turns out to be misdirected, because it was informed of the mismatch.

                  5.4 Business case for real-time treasury

                  Helion's treasurer says intraday visibility and instant payments could reduce the cash buffer it keeps across subsidiaries from 150 million to 100 million euros. If that cash would otherwise reduce borrowing costing 4.00 per cent, what is the annual value?

                  50 million euros × 4.00% = 2 million euros a year.

                  Explain to a relative how criminals could steal millions from a central bank without breaking into the global payment network, and what banks changed afterwards.

                      1. Name the main risks of cash management and a control for each.

                      2. What is business email compromise, and how can it be prevented?

                      3. What happened in the Bangladesh Bank heist, and what did SWIFT do afterwards?

                      4. What does the Instant Payments Regulation require?

                      5. Why does speed increase fraud risk?

                      6. Name the five transformation moves.

                      5

                      1. What is business email compromise?

                      2. What did SWIFT do after the Bangladesh Bank heist?

                      3. Which risk concerns banks advancing funds before end-of-day settlement?

                      Module Summary — The Six Ideas That Matter Most

                      If you retain only a handful of things, retain these. Each compresses a part of the module into a single, load-bearing idea.

                      Treasurers need visibility, control, liquidity and security

                      Groups grow complex banking landscapes through acquisitions. Cash management aims to see all cash in one place, control every payment, put idle cash to work and protect the group against fraud and errors.

                      Money moves on rails and through correspondents

                      SEPA credit transfers, instant payments, direct debits, T2 and national systems move domestic and euro payments; correspondent banking linked by SWIFT, now tracked with gpi, moves cross-border payments, with charges and delays.

                      A payment is a controlled chain of messages

                      Invoice approval, payment run, pain.001 file, bank validation, screening and verification of payee, execution within cut-offs, pain.002 status and camt statements: each step has its control, and failure at any step costs time or money.

                      Centralisation creates value

                      Account rationalisation, virtual accounts, physical and notional pooling, payment factories, POBO and COBO, and in-house banks reduce costs, improve control and put cash to work, within legal and tax constraints.

                      Cash management anchors the relationship

                      Fees, deposits — especially operational deposits with lower liquidity requirements — and daily insight make cash management a strategic, low-capital business, linked to credit through the client's wallet.

                      Faster money needs stronger controls

                      The Bangladesh Bank heist and the move to instant payments show that speed and safety must be designed together. ISO 20022, APIs, real-time screening, verification of payee and resilience rules define the modern payment business.

                      Process Cheat Sheet — A Supplier Payment on One Page

                      A single reference for a payment's life. Everything below is developed in full in Part 2.

                      Step Who acts Message or data Key control
                      Invoice approval Accounts payable ERP invoice Three-way match
                      Payment run Treasury Payment proposal Dual approval
                      Transmission Treasury system pain.001 Signature, secure channel
                      Validation Bank File checks Authentication, duplicates, funds
                      Screening Bank Screening results Sanctions, fraud, verification of payee
                      Execution Bank pacs.008 or other Cut-offs, routing, FX
                      Status Bank pain.002 Rejections handled
                      Reporting Bank and treasury camt.052, camt.053, camt.054 Automated reconciliation

                      Key numbers to remember

                      Item Rule or figure
                      SEPA instant maximum execution time 10 seconds, 24/7/365
                      Instant Payments Regulation, euro area Receive by January 2025; send and verification of payee by October 2025
                      SEPA Core direct debit refund right Eight weeks, no justification needed
                      LCR outflow, operational corporate deposits 25 per cent
                      LCR outflow, non-operational corporate deposits 40 per cent
                      ISO 20022 in T2 Since March 2023
                      SWIFT MT/ISO 20022 coexistence for cross-border payments Ended November 2025
                      G20 cross-border payments targets 2027
                      DORA application January 2025

                      The one-sentence version

                      Payments and cash management give corporates visibility, control and efficient use of their cash through accounts, payments, collections, pooling and connectivity — and give banks stable deposits and the closest daily relationship with their clients — provided money moves correctly, instantly and safely.

                      Sources and further reading

                      Regulatory positions and market facts stated in this module reflect sources available in mid-2026. Treat every date and figure below as a fact with a shelf life and verify it before relying on it in client work.

                      How to read this section

                      Descriptions of payment systems and rules are simplified for learning; scheme rulebooks and legal texts govern. Figures flagged as illustrative — Helion and all worked examples — are invented to teach a mechanic.

                      Primary instruments and standards referenced

                      Short name used in the module Instrument Relevance
                      PSD2 Directive (EU) 2015/2366 on payment services Authentication, account access, payment rules
                      Instant Payments Regulation Regulation (EU) 2024/886 Instant euro payments and verification of payee
                      SEPA Regulation Regulation (EU) No 260/2012 SEPA credit transfers and direct debits
                      EPC rulebooks European Payments Council SCT, SCT Inst, SDD Core and B2B Scheme rules
                      Basel III LCR Liquidity coverage ratio Treatment of operational deposits
                      DORA Regulation (EU) 2022/2554 on digital operational resilience ICT risk and third parties
                      ISO 20022 International standard for financial messaging Payment and reporting messages
                      SWIFT CSP SWIFT Customer Security Programme Security controls for SWIFT users

                      Dated facts and where they come from

                      T2 replaced TARGET2 with ISO 20022 in March 2023; CHAPS moved to ISO 20022 in June 2023; Fedwire in July 2025; SWIFT's MT and ISO 20022 coexistence for cross-border payments ended in November 2025. The Instant Payments Regulation entered into force in April 2024, with deadlines in January and October 2025 for the euro area. DORA has applied since 17 January 2025. The Bangladesh Bank heist occurred in February 2016; SWIFT launched its Customer Security Programme in 2016. The G20 cross-border payments targets for 2027 are monitored by the Financial Stability Board. Sources: official texts, ECB, Bank of England, Federal Reserve and SWIFT publications, and contemporaneous reporting.

                      Where to go deeper

                      The European Payments Council publishes the SEPA rulebooks. The ECB and national central banks explain T2, TIPS and the Eurosystem's payment strategy. SWIFT publishes ISO 20022 guidance and its Customer Security Controls Framework. The Financial Stability Board publishes annual progress reports on the G20 cross-border payments targets. Treasury associations publish surveys of treasurers' priorities.