[{"data":1,"prerenderedAt":147},["ShallowReactive",2],{"in-one-picture":3},[4,29,40,51,97,136],{"slug":5,"name":6,"pictures":7},"treasury-management-systems","Treasury Management Systems",[8,15,22],{"name":9,"title":10,"desc":11,"caption":12,"path":13,"post":14,"pillar":5},"gartner-no-quadrant","The Gartner Magic Quadrant for treasury management systems that does not exist","On 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.","There is no Gartner Magic Quadrant for corporate treasury management systems — only what sits next to it.","\u002Fblog\u002Fgartner-magic-quadrant-treasury-management-systems","Is There a Gartner Magic Quadrant for TMS?",{"name":16,"title":17,"desc":18,"caption":19,"path":20,"post":21,"pillar":5},"tms-modular","A modular treasury management system: modules on a shared core","A 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.","Each module can be added, left out or replaced; the core is what all of them stand on.","\u002Fblog\u002Fmodular-vs-monolithic-treasury-management-system","Modular Treasury Management System vs Monolithic Suite",{"name":23,"title":24,"desc":25,"caption":26,"path":27,"post":28,"pillar":5},"tms","Where a treasury management system sits","The 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.","A TMS is never an island — it sits between the ERP, the banks, market data, and the people and controls around it.","\u002Fblog\u002Fwhat-is-a-treasury-management-system","What Is a Treasury Management System (TMS)?",{"slug":30,"name":31,"pictures":32},"cash-and-liquidity-management","Corporate Cash & Liquidity Management",[33],{"name":34,"title":35,"desc":36,"caption":37,"path":38,"post":39,"pillar":30},"cash-position-forecast","Cash position and cash forecast","On 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.","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.","\u002Fblog\u002Fcash-positioning-vs-cash-flow-forecasting","Cash Positioning vs Cash Flow Forecasting: The Difference",{"slug":41,"name":42,"pictures":43},"treasury-risk-management","Treasury Risk Management",[44],{"name":45,"title":46,"desc":47,"caption":48,"path":49,"post":50,"pillar":41},"isda-csa","The ISDA Master Agreement, its trades and the collateral under a CSA","A 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.","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.","\u002Fblog\u002Fisda-csa-and-collateral-management","ISDA Agreements, CSAs and Collateral Management",{"slug":52,"name":53,"pictures":54},"treasury-systems-architecture","Treasury Systems Architecture & Connectivity",[55,62,69,76,83,90],{"name":56,"title":57,"desc":58,"caption":59,"path":60,"post":61,"pillar":52},"statement-formats","One bank statement in three formats","Three 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.","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.","\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","Bank Statement Formats: MT940 vs camt.053 vs BAI2",{"name":63,"title":64,"desc":65,"caption":66,"path":67,"post":68,"pillar":52},"camt-054","One statement line, and the notification that itemises it","A 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.053 confirms the cash; camt.054 explains it. The amounts are illustrative.","\u002Fblog\u002Fcamt-054-notification-explained","camt.054: The Debit\u002FCredit Notification and When You Need It",{"name":70,"title":71,"desc":72,"caption":73,"path":74,"post":75,"pillar":52},"ebics","EBICS as one channel between a company and its banks","You 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.","EBICS carries the file; the file carries the content — pain going out, camt coming back.","\u002Fblog\u002Febics-european-bank-connectivity","EBICS Explained: European Bank Connectivity",{"name":77,"title":78,"desc":79,"caption":80,"path":81,"post":82,"pillar":52},"iso-20022-families","The three ISO 20022 message families a treasury meets","You, 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.","pain goes from you to your bank, camt comes back, and pacs travels between banks — a corporate never sends one.","\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","ISO 20022 for Corporates: pain, camt and pacs Messages",{"name":84,"title":85,"desc":86,"caption":87,"path":88,"post":89,"pillar":52},"mt-to-mx","An MT message and its ISO 20022 (MX) equivalent","On 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.","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.","\u002Fblog\u002Fiso-20022-migration-mt-to-mx","ISO 20022 Migration: Moving from SWIFT MT to MX (CBPR+)",{"name":91,"title":92,"desc":93,"caption":94,"path":95,"post":96,"pillar":52},"mt-messages","MT101, MT103 and MT202 on the payment chain","A 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.","Who is talking to whom, and whose money is it — the two questions that separate the three.","\u002Fblog\u002Fmt101-vs-mt103-vs-mt202","MT101 vs MT103 vs MT202: Which SWIFT Message Does What",{"slug":98,"name":99,"pictures":100},"sap-treasury","SAP Treasury & Cash Management",[101,108,115,122,129],{"name":102,"title":103,"desc":104,"caption":105,"path":106,"post":107,"pillar":98},"sap-bcm","SAP Bank Communication Management as the gate between SAP and the bank","Payments 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.","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.","\u002Fblog\u002Fbank-communication-management-bcm-sap","Bank Communication Management (BCM) in SAP",{"name":109,"title":110,"desc":111,"caption":112,"path":113,"post":114,"pillar":98},"sap-apm","SAP Advanced Payment Management as the single path for payments","Three 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.","Many sources, one hub, one controlled path to the banks.","\u002Fblog\u002Fsap-advanced-payment-management-apm","SAP Advanced Payment Management (APM)",{"name":116,"title":117,"desc":118,"caption":119,"path":120,"post":121,"pillar":98},"sap-bam","Bank, house bank, house bank account and bank account in SAP","Four 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.","Four objects, one chain. The link between the last two is what SAP calls house bank account connectivity.","\u002Fblog\u002Fsap-bank-account-management-s4hana","SAP Bank Account Management (BAM) in S\u002F4HANA",{"name":123,"title":124,"desc":125,"caption":126,"path":127,"post":128,"pillar":98},"sap-ebs","A bank statement going through SAP's electronic bank statement processing","A 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.","Four steps, and one exit for whatever fails one of them: post-processing, where a person finishes the job.","\u002Fblog\u002Fsap-ebs-posting-rules-and-interpretation-algorithms","SAP Electronic Bank Statement: Posting Rules and Algorithms",{"name":130,"title":131,"desc":132,"caption":133,"path":134,"post":135,"pillar":98},"sap-tables","Where one SAP Treasury deal is stored","One 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.","One deal, three Treasury tables, and from there the trail into FI.","\u002Fblog\u002Fsap-treasury-tables","SAP Treasury Tables: Where Deals, Flows and Positions Live",{"slug":137,"name":138,"pictures":139},"finance-systems-delivery","Finance Systems Delivery",[140],{"name":141,"title":142,"desc":143,"caption":144,"path":145,"post":146,"pillar":137},"raid-log","The four lists in a RAID log","Four 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.","Four different kinds of entry in one working record — and the differences between them are the point.","\u002Fblog\u002Fraid-log-risks-assumptions-issues-dependencies","RAID Logs: Risks, Assumptions, Issues and Dependencies",1791564243575]