In one picture

17 ideas from treasury, SAP and bank formats, each drawn once. A picture shows only what its article says; the article is the link under it.

Treasury Management Systems

  • The Gartner Magic Quadrant for treasury management systems that does not existOn the left, an empty two-by-two chart with a question mark in it, labelled no TMS quadrant. On the right, under the words what exists, three things — Peer Insights reviews, a 2011 quadrant for the bank side, and other analysts' coverage.?Peer Insights reviewsA 2011 quadrant, bank-sideOther analysts' coverageno TMS quadrantwhat exists
    There is no Gartner Magic Quadrant for corporate treasury management systems — only what sits next to it.
    Is There a Gartner Magic Quadrant for TMS?
  • A modular treasury management system: modules on a shared coreA wide block labelled Core treasury system. Four modules plug into it from above — Cash and liquidity, Payments, Risk and hedging, and In-house banking. One of them, Risk and hedging, is lifted out of its slot, which is left empty.Core treasury systemCash andliquidityPaymentsRisk andhedgingIn-housebankingmodules on one shared core
    Each module can be added, left out or replaced; the core is what all of them stand on.
    Modular Treasury Management System vs Monolithic Suite
  • Where a treasury management system sitsThe TMS in the middle of four things. The ERP on one side, with data flowing in and accounting entries flowing back. The banks on the other, with statements coming in and payments going out. Market data feeding it from above. People and controls beneath it.TMSERPBanksMarket dataPeople and controls
    A TMS is never an island — it sits between the ERP, the banks, market data, and the people and controls around it.
    What Is a Treasury Management System (TMS)?

Corporate Cash & Liquidity Management

  • Cash position and cash forecastOn the left, a sheet marked today with one firm figure and a tick, labelled cash position, confirmed. An arrow leads to a chart of four weeks — the first bar solid, the next three dashed outlines — labelled cash forecast, estimated.todayw1w2w3w4cash positionconfirmedcash forecastestimated
    The position is what you have now and can confirm; the forecast is what you expect, and it gets less certain the further out it looks.
    Cash Positioning vs Cash Flow Forecasting: The Difference

Treasury Risk Management

  • The ISDA Master Agreement, its trades and the collateral under a CSAA folder labelled ISDA Master Agreement holds three trades — one agreement, many trades. Below it stand two parties, one out of the money and one in the money. An arrow carries collateral from the party that is out of the money to the party that is in the money, and is labelled CSA.ISDA Master Agreementone agreement, many tradesCSAcollateralout of the moneyin the money
    The Master Agreement puts every trade with a counterparty under one contract; the CSA makes whoever is out of the money post collateral to the other.
    ISDA Agreements, CSAs and Collateral Management

Treasury Systems Architecture & Connectivity

  • One bank statement in three formatsThree sheets side by side. MT940 is lines that begin with tags such as :20:, :61: and :86:. camt.053 is XML, each entry inside an Ntry element. BAI2 is comma-separated records that begin with a record code such as 03, 16 and 49.MT940camt.053BAI2:20::61::86:<Ntry></Ntry>03,,16,,49,,tagged linesXMLrecords
    The same end-of-day statement in three shapes — SWIFT's tagged lines, ISO 20022 XML, and the comma-separated records used mainly in the US.
    Bank Statement Formats: MT940 vs camt.053 vs BAI2
  • One statement line, and the notification that itemises itA camt.053 statement, with a balance above and below its entries, shows a single booking of 12,400. An arrow leads to a camt.054 notification that lists the three items inside that booking — 4,100, 5,300 and 3,000 — adding up to the same 12,400. The notification carries no balance.camt.053camt.05412,4004,1005,3003,00012,400one linewhat is inside itbalance
    camt.053 confirms the cash; camt.054 explains it. The amounts are illustrative.
    camt.054: The Debit/Credit Notification and When You Need It
  • EBICS as one channel between a company and its banksYou on the left, your banks on the right, and one secured channel labelled EBICS between them. A pain file travels from you to the banks, and a camt file travels back.EBICSpaincamtYouYour banks
    EBICS carries the file; the file carries the content — pain going out, camt coming back.
    EBICS Explained: European Bank Connectivity
  • The three ISO 20022 message families a treasury meetsYou, your bank and other banks. An arrow from you to your bank is labelled pain. An arrow from your bank back to you is labelled camt. A two-way arrow between your bank and other banks is labelled pacs. A key reads pain, you instruct; camt, bank reports; pacs, bank to bank.paincamtpacsYouYour bankOther banksyou instructbank reportsbank to bank
    pain goes from you to your bank, camt comes back, and pacs travels between banks — a corporate never sends one.
    ISO 20022 for Corporates: pain, camt and pacs Messages
  • An MT message and its ISO 20022 (MX) equivalentOn the left, a small sheet labelled MT with three lines, each a tag followed by text that is cut off. An arrow leads to a larger sheet labelled MX with three named fields — Dbtr, Cdtr and RmtInf — each with room for its content. Underneath, tight fields on the left and structured fields on the right.MTMX………<Dbtr><Cdtr><RmtInf>tight fieldsstructured fields
    The same instruction twice — squeezed into fixed tags and tight fields in MT, with a defined field for each piece of data in ISO 20022.
    ISO 20022 Migration: Moving from SWIFT MT to MX (CBPR+)
  • MT101, MT103 and MT202 on the payment chainA corporate sends an MT101 to a bank. That bank sends an MT103 to another bank and, separately, an MT202. The MT101 and the MT103 are marked as carrying a customer's money; the MT202 is marked as the banks' own.MT101MT103MT202CorporateBankBanka customer's moneythe banks' own
    Who is talking to whom, and whose money is it — the two questions that separate the three.
    MT101 vs MT103 vs MT202: Which SWIFT Message Does What

SAP Treasury & Cash Management

  • SAP Bank Communication Management as the gate between SAP and the bankPayments from SAP enter BCM, drawn as a gate with four steps — batch, approve, sign and release. An arrow labelled channel carries the released batch to the bank, and an arrow labelled status comes back from the bank to BCM.BCMbatchapprovesignreleasechannelstatuspaymentsbank
    BCM is the gate, not the wire — it batches, approves, signs and releases; the connectivity channel transmits; the bank's status comes back to be watched.
    Bank Communication Management (BCM) in SAP
  • SAP Advanced Payment Management as the single path for paymentsThree sources — payroll, accounts payable and treasury — each send their payment requests to APM. APM is drawn as a hub with four steps — route, aggregate, transform and forward — and one arrow leaves it for the banks.APMPayrollAPTreasuryrouteaggregatetransformforwardpayment requestsbanks
    Many sources, one hub, one controlled path to the banks.
    SAP Advanced Payment Management (APM)
  • Bank, house bank, house bank account and bank account in SAPFour objects in a chain. A bank, held in table BNKA, leads to a house bank, T012, which leads to a house bank account, T012K. The house bank account is joined by a chain link to the bank account — the Bank Account Management master record, FCLM_BAM_AMD.BankBNKAHouse bankT012Bank accountFCLM_BAM_AMDHouse bank accountT012K
    Four objects, one chain. The link between the last two is what SAP calls house bank account connectivity.
    SAP Bank Account Management (BAM) in S/4HANA
  • A bank statement going through SAP's electronic bank statement processingA bank statement enters EBS, drawn as a machine with four numbered steps: import, interpret, post and clear. Two arrows leave it. One goes to a ledger marked with a tick, labelled cleared. The other goes to a tray holding a single sheet, labelled post-processing.EBS1 import2 interpret3 post4 clearstatementclearedpost-processing
    Four steps, and one exit for whatever fails one of them: post-processing, where a person finishes the job.
    SAP Electronic Bank Statement: Posting Rules and Algorithms
  • Where one SAP Treasury deal is storedOne deal fans out into three tables. VTBFHA holds the deal, VTBFHAPO its flows and VTBFINKO its conditions. From them an arrow leads to the FI side, drawn as a ledger listing BKPF, BSEG and ACDOCA.VTBFHAthe dealVTBFHAPOits flowsVTBFINKOits conditionsBKPFBSEGACDOCAone dealFI
    One deal, three Treasury tables, and from there the trail into FI.
    SAP Treasury Tables: Where Deals, Flows and Positions Live

Finance Systems Delivery

  • The four lists in a RAID logFour cards. R, Risks, might happen. A, Assumptions, treated as true. I, Issues, has happened. D, Dependencies, needed from others. Under them, the words one working record.RRisksmight happenAAssumptionstreated as trueIIssueshas happenedDDependenciesneeded from othersone working record
    Four different kinds of entry in one working record — and the differences between them are the point.
    RAID Logs: Risks, Assumptions, Issues and Dependencies