# Tan Gravam > Complex enterprise work, redesigned with AI. Tan Gravam writes about enterprise AI transformation, workflow design and systems architecture, grounded in 18 years of SAP, finance, treasury and enterprise-systems work — combining Enterprise AI thinking with deep field evidence from finance systems, practical tools, workflow teardowns and software experiments. The writing is in two bands. Enterprise AI is the subject: transformation (which work to redesign, and what the economics have to show), workflow design (the boundaries between rules, models, humans, state and the exception path) and systems (architecture, controls, identity, evaluation and observability). Finance systems, treasury and SAP are the field evidence underneath it — the domains where these lessons were learned. The products are built, not just written about. The best-verified material is the reference tier: field-level pages on ISO 20022 payment and statement messages (pain.001, pain.002, pain.008, camt.052, camt.053, camt.054), SWIFT MT940, MT942 and MT10x, BAI2, and SAP Treasury (transaction codes, tables, Fiori app ids, TRM product types, EBS posting rules, DMEE). Every code they document is also in one lookup at https://gravam.com/reference. See "Sourced articles" below — the field-level pages are listed first. This is a curated map. The full Markdown text of every article is at https://gravam.com/llms-full.txt — one request, no HTML to parse (it is over a megabyte). Single articles are available as Markdown too: take any /blog/ URL and request https://gravam.com/md/. Same text as the corpus file, one article at a time, for a fetcher working to a byte budget. ## Topics The writing is organized into topic hubs, each a deep guide to one domain: - [Enterprise AI Transformation](https://gravam.com/topics/enterprise-ai-transformation): Where AI actually creates value inside a large organization: choosing the work worth transforming, redesigning it end to end, and measuring what changed. - [AI Workflow Design](https://gravam.com/topics/ai-workflow-design): How to redesign a complex enterprise workflow around AI: what stays deterministic, what AI can judge, where a human decides, and what state the work needs. - [Enterprise AI Systems](https://gravam.com/topics/enterprise-ai-systems): The architecture behind enterprise AI: how agents fit existing systems, what the control layer owns, and how oversight, data and observability are designed. - [Treasury Management Systems](https://gravam.com/topics/treasury-management-systems): How to assess, select and implement a treasury management system — from business case and requirements through RFP, testing, cutover and go-live. - [Corporate Cash & Liquidity Management](https://gravam.com/topics/cash-and-liquidity-management): How corporate treasury runs cash and liquidity: cash positioning vs forecasting, cash pooling, in-house banks, payment factories and global cash visibility. - [Treasury Risk Management](https://gravam.com/topics/treasury-risk-management): How corporate treasury manages financial risk: FX exposure, interest rate risk, counterparty and credit risk, hedging and hedge accounting — plainly explained. - [Treasury Systems Architecture & Connectivity](https://gravam.com/topics/treasury-systems-architecture): How treasury systems fit together: reference architecture, bank connectivity (SWIFT, API, EBICS), MT940 and camt.053 formats, and ERP–TMS integration. - [SAP Treasury & Cash Management](https://gravam.com/topics/sap-treasury): Field notes on SAP treasury: TRM, One Exposure, FQM_FLOW, Flow Builder, liquidity items, bank statement integration and BCM — from real implementations. - [Building AI Products](https://gravam.com/topics/building-ai-products): How I turn recurring problems into focused AI products — idea selection, an outcome-first process, a solo Nuxt/Supabase stack, pricing and kill criteria. - [Finance Systems Delivery](https://gravam.com/topics/finance-systems-delivery): Intake, scope, ownership, fit-gap, UAT, cutover and governance for enterprise finance-systems programmes — turning vague demands into delivery decisions. ## Sourced articles Every article that carries the primary documents it was checked against, with the date each was verified. The field-level reference pages come first — message formats, tables, transaction codes, configuration objects (every code they document is also in https://gravam.com/reference) — followed by the regulation, buying-guide and enterprise-AI pieces whose specific claims were verified at source; each page's own scope note says what was and was not checked: - [BAI2 File Format: Records, Type Codes and How to Read One](https://gravam.com/blog/bai2-file-format-explained): Every BAI2 record explained: the 01–99 hierarchy, balance codes 010/015/040/045, credit vs debit type-code ranges, the funds-type field and control totals. - [camt.052 vs MT942: The Intraday Report, Field by Field](https://gravam.com/blog/camt-052-intraday-account-report-vs-mt942): camt.052 and MT942 side by side: what each intraday report carries, the balances camt.052 may omit, MT942's floor limit and totals, and where banks diverge. - [camt.053 Structure: Reading the Statement Field by Field](https://gravam.com/blog/camt-053-structure-and-fields): The camt.053 statement field by field: GroupHeader to TransactionDetails, OPBD/CLBD balance codes, the Bank Transaction Code, and where bank files diverge. - [MT940 Format: The Tags, Line by Line](https://gravam.com/blog/mt940-format-tags-explained): Every MT940 tag explained: :20:, :25:, :28C:, the :61: statement line subfield by subfield, the bank-specific :86:, and the :62a:/:64:/:65: balances. - [pain.002 Status and Reject Codes: Reading the Bank's Reply](https://gravam.com/blog/pain-002-status-and-reject-codes): How to read a pain.002 status report: group, payment and transaction level, the ACTC/ACCP/ACSC status codes, and reject reasons like AC01, AC04 and AM04. - [SAP Treasury Fiori Apps: What Replaces Which Transaction](https://gravam.com/blog/sap-treasury-fiori-apps): A verified map of the Fiori apps for SAP Treasury and Cash Management in S/4HANA — F6157 to F2332 — with the classic transaction each replaces or complements. - [SAP Treasury Tables: Where Deals, Flows and Positions Live](https://gravam.com/blog/sap-treasury-tables): The database tables behind SAP Treasury and Risk Management — the VTBFHA deal family, FEBKO/FEBEP, FQM_FLOW and the FI link — verified against SAP Help. - [SAP Treasury Transaction Codes: The Ones That Matter](https://gravam.com/blog/sap-treasury-transaction-codes): A verified reference of SAP Treasury and Risk Management transaction codes — FTR_CREATE to TPM20 — grouped by working area and checked against SAP Help. - [Bank Communication Management (BCM) in SAP](https://gravam.com/blog/bank-communication-management-bcm-sap): SAP Bank Communication Management (BCM) is the controlled gateway between SAP and the banks for payments — batching, approval workflow, signatures, monitoring. - [Bank Connectivity Security: Keys, Certificates and Controls](https://gravam.com/blog/bank-connectivity-security): The security layer under treasury bank connectivity: certificate and key lifecycle, mTLS, OAuth, key rotation, HSM, SWIFT CSP, and who owns the technical user. - [Bank Statement Formats: MT940 vs camt.053 vs BAI2](https://gravam.com/blog/bank-statement-formats-mt940-camt053-bai2): MT940, camt.053 and BAI2 are the main bank statement formats treasury imports: legacy SWIFT, modern ISO 20022, a US format. How they differ and which to use. - [Build vs Buy a Treasury Management System](https://gravam.com/blog/build-vs-buy-treasury-management-system): For almost every corporate, buying a TMS beats building one, because a package embeds decades of connectivity and compliance. When build makes sense, and why. - [Business Partner Configuration for SAP Treasury](https://gravam.com/blog/business-partner-configuration-sap-treasury): The SAP Business Partner is the master-data object for the counterparties, issuers and banks a treasury deals with — and every TRM deal is captured against it. - [camt.054: The Debit/Credit Notification and When You Need It](https://gravam.com/blog/camt-054-notification-explained): What camt.054 is — a notification of debits and credits, not a statement — how it differs from camt.053 and camt.052, and the lump-sum breakdown it exists for. - [Cash Flow at Risk (CFaR) Explained](https://gravam.com/blog/cash-flow-at-risk-cfar): Cash Flow at Risk measures the worst shortfall in a company's cash flow versus plan over a period at a chosen confidence level — the corporate answer to VaR. - [EBICS Explained: European Bank Connectivity](https://gravam.com/blog/ebics-european-bank-connectivity): What EBICS is — an internet-based European standard for exchanging payment and statement files with banks — and where it fits alongside SWIFT and host-to-host. - [Electronic Bank Account Management (eBAM)](https://gravam.com/blog/electronic-bank-account-management-ebam): Electronic bank account management (eBAM) handles opening, closing, mandates and signatories digitally, not on paper. Why account admin is broken. - [Electronic Bank Statement Processing in SAP](https://gravam.com/blog/electronic-bank-statement-processing-in-sap): Electronic bank statement (EBS) processing in SAP imports, interprets and posts bank statements, clearing open items. The pain lives in the posting-rule config. - [FQM_FLOW Reconciliation & Troubleshooting in S/4HANA](https://gravam.com/blog/fqm-flow-reconciliation-and-troubleshooting): When a cash flow is missing or wrong in S/4HANA, the answer is in FQM_FLOW. A triage guide: why a flow is invisible, which source to check, when to rebuild. - [Hedge Accounting Explained](https://gravam.com/blog/hedge-accounting-explained): Hedge accounting aligns the timing of a hedge's gains and losses with the hedged item, so the P&L shows they offset. Why it exists, and the three hedge types. - [Hedge Documentation for Hedge Accounting](https://gravam.com/blog/hedge-documentation-requirements): Hedge documentation: what you must designate at inception — objective, instrument, hedged item, risk and effectiveness method — for hedge accounting. - [Hedge Effectiveness Testing and the Hedge Ratio](https://gravam.com/blog/hedge-effectiveness-testing): Hedge effectiveness testing proves your hedge offsets the hedged risk — the evidence you need to keep hedge accounting and avoid artificial P&L swings. - [Hedge Management in SAP](https://gravam.com/blog/hedge-management-in-sap): Hedge Management in SAP is the risk half of SAP's Hedge Management and Accounting area — Hedge Accounting, switched on separately, designates and posts. - [How to Run a TMS Selection Process](https://gravam.com/blog/how-to-run-a-tms-selection-process): A TMS selection process is the structured path from ‘we need a system’ to ‘we chose the right one’ — requirements, RFP, scripted demos, scorecard, references. - [Interest Rate Benchmark Reform: LIBOR to SOFR](https://gravam.com/blog/interest-rate-benchmark-reform-libor-sofr): The move from LIBOR to risk-free reference rates like SOFR and SONIA — why it happened, how RFRs differ, and what the transition meant for corporate treasury. - [Intraday Liquidity Management: The Operating Model](https://gravam.com/blog/intraday-liquidity-management): Cash is a moving position through the day, not a daily number. How to run intraday liquidity: payment queues, cut-offs, intraday credit and alerts. - [Is There a Gartner Magic Quadrant for TMS?](https://gravam.com/blog/gartner-magic-quadrant-treasury-management-systems): There is no dedicated Gartner Magic Quadrant for treasury management systems. What Gartner actually covers, and how to shortlist a TMS without a quadrant. - [ISDA Agreements, CSAs and Collateral Management](https://gravam.com/blog/isda-csa-and-collateral-management): How the ISDA Master Agreement, its schedule and the Credit Support Annex document and collateralise the counterparty risk in over-the-counter derivatives. - [ISO 20022 Migration: Moving from SWIFT MT to MX (CBPR+)](https://gravam.com/blog/iso-20022-migration-mt-to-mx): The industry migration from legacy SWIFT MT messages to ISO 20022 MX for cross-border payments and reporting, and what CBPR+ means for corporate treasury. - [ISO 20022 Payments Explained: pain.001 and pain.002](https://gravam.com/blog/iso-20022-payments-pain-001-pain-002): ISO 20022 is the global XML standard for financial messaging. For payments, pain.001 is the instruction you send and pain.002 the status back. What they are. - [Liquidity Items in SAP Cash Management](https://gravam.com/blog/liquidity-items-in-sap-cash-management): Liquidity items classify cash flows by purpose. The IMG nodes, the derivation queries, the Origin codes D/C/X and the apps — verified against SAP Help. - [Market Data in SAP Treasury](https://gravam.com/blog/sap-treasury-market-data-management): SAP treasury market data — FX rates, interest curves, security prices, indexes — is the reference TRM values everything on; its quality drives every number. - [Migrating SAP Treasury from ECC to S/4HANA](https://gravam.com/blog/migrating-sap-treasury-ecc-to-s4hana): Migrating SAP treasury from ECC to S/4HANA isn't an upgrade — it's substantially a re-implementation, because S/4HANA redesigned Cash Management. Why, and how. - [MT101 vs MT103 vs MT202: Which SWIFT Message Does What](https://gravam.com/blog/mt101-vs-mt103-vs-mt202): MT101 is a corporate's payment instruction, MT103 a bank-to-bank customer transfer, MT202 an interbank transfer. How they differ and what replaced them. - [NIST AI RMF: The Functions and Categories, Explained](https://gravam.com/blog/nist-ai-rmf-functions-and-categories): All four functions and 19 categories of the NIST AI Risk Management Framework, with subcategory counts — and which finance controls already cover each one. - [One Exposure from Operations & FQM_FLOW Explained](https://gravam.com/blog/one-exposure-from-operations-fqm-flow): One Exposure from Operations is the hub at the centre of S/4HANA Cash Management — a single store (FQM_FLOW) every cash-relevant flow feeds. Why it exists. - [pain.001 Structure: The Fields That Actually Matter](https://gravam.com/blog/pain-001-structure-and-fields): Inside the pain.001 file: GroupHeader, PaymentInformation and the transaction level — which fields treasury maps, and where bank implementations differ. - [pain.008: SEPA Direct Debit Initiation Explained](https://gravam.com/blog/pain-008-direct-debit-initiation): pain.008 (CustomerDirectDebitInitiation) is the ISO 20022 message a creditor sends to pull funds — mandates, FRST/RCUR sequence types, Core vs B2B, refunds. - [Planning Levels and Groups in SAP Cash Management](https://gravam.com/blog/planning-levels-and-groups-in-sap): Planning levels ride on G/L accounts, groups on business partners — and both land in BSEG. The IMG nodes, the rebuild activity and the flow types beside them. - [Real-Time Treasury: What It Actually Means](https://gravam.com/blog/real-time-treasury): Real-time treasury is the shift from batch to continuous operations, driven by instant payments and APIs. What changes, and where it genuinely matters vs batch. - [SaaS vs On-Premise Treasury Management System](https://gravam.com/blog/saas-vs-on-premise-treasury-management-system): Cloud SaaS is the default TMS deployment model; on-premise the exception for control, data-residency or integration. How they differ on cost, upgrades and exit. - [SAP Advanced Payment Management (APM)](https://gravam.com/blog/sap-advanced-payment-management-apm): SAP Advanced Payment Management (APM) is the S/4HANA payment hub that centralizes payment requests from many systems and orchestrates them toward the banks. - [SAP Bank Account Management (BAM) in S/4HANA](https://gravam.com/blog/sap-bank-account-management-s4hana): SAP Bank Account Management (BAM) governs bank accounts and house banks as master data in S/4HANA — the base cash position, statements and payments rest on. - [SAP Cash Management in S/4HANA](https://gravam.com/blog/sap-cash-management-s4hana): SAP Cash Management in S/4HANA — business function FIN_FSCM_CLM, the three areas, the Fiori apps, the IMG spine and the One Exposure data layer, verified. - [SAP Credit Risk Analyzer](https://gravam.com/blog/sap-credit-risk-analyzer): The Credit Risk Analyzer is the SAP TRM component that measures counterparty risk and manages limits — checking deals against limits and flagging breaches. - [SAP DMEE: How Payment File Formats Are Built](https://gravam.com/blog/sap-dmee-payment-file-format-tree): The DMEE format tree explained — node types, the mapping procedures, tree type PAYM, the FPAY* source structures, and where DMEE sits between F110 and PMW. - [SAP EBS Posting Rules and Interpretation Algorithms](https://gravam.com/blog/sap-ebs-posting-rules-and-interpretation-algorithms): The SAP EBS configuration chain — external transaction codes, posting rules, account symbols, posting areas 1 and 2, interpretation algorithms, search strings. - [SAP In-House Cash (IHC)](https://gravam.com/blog/sap-in-house-cash-ihc): SAP In-House Cash runs an internal bank — bank areas, IHC payment orders, the IHC_DB_PN tables, the BAdIs, and the newer In-House Banking apps, verified. - [SAP Market Risk Analyzer](https://gravam.com/blog/sap-market-risk-analyzer): The Market Risk Analyzer is the SAP TRM component that values positions and measures market risk — NPV, sensitivities, VaR — all driven by market data. - [SAP Payments: BCM, APM & Output Management Boundaries](https://gravam.com/blog/sap-bcm-apm-output-management-architecture): Where does payment output management end, Bank Communication Management begin, and Advanced Payment Management fit? Boundaries in SAP's outgoing-payment stack. - [SAP Portfolio Analyzer](https://gravam.com/blog/sap-portfolio-analyzer): The Portfolio Analyzer is the SAP TRM component that measures portfolio returns and performance versus benchmarks — and when it's actually worth implementing. - [SAP Transaction Manager: Deals and Instruments](https://gravam.com/blog/sap-transaction-manager): The Transaction Manager is the core of SAP TRM, where financial deals live — money market, FX, securities and derivatives, from capture to accounting. - [SAP Treasury Deployment & Edition Comparison](https://gravam.com/blog/sap-treasury-deployment-and-edition-comparison): On-premise, S/4HANA Cloud Private or Public Edition — how the deployment choice shapes SAP treasury: extensibility, upgrade control, TCO and the real drivers. - [SAP Treasury Implementation Roadmap & Module Selection](https://gravam.com/blog/sap-treasury-implementation-roadmap-and-module-selection): Which SAP Treasury modules do you need, in what order? A decision-led roadmap across TRM, Cash Management, BCM, APM and In-House Cash, scoped to release. - [SAP TRM Accounting & Posting Architecture](https://gravam.com/blog/sap-trm-accounting-and-posting-architecture): How a treasury deal becomes a G/L posting in SAP TRM: account determination via symbols, valuation areas for parallel accounting, and ledger reconciliation. - [SAP TRM Position Management and Valuation](https://gravam.com/blog/sap-trm-position-management-and-valuation): How SAP TRM turns captured deals into managed positions and values them under parallel accounting bases, posting the results to Financial Accounting. - [SAP TRM Product Types and Transaction Types, Explained](https://gravam.com/blog/sap-trm-product-types-and-transaction-types): How SAP Treasury classifies deals: fixed product categories, configurable product types like 51A and 60A, transaction types, and the layers below. - [SAP TRM vs a Standalone TMS: Embedded or Best-of-Breed?](https://gravam.com/blog/sap-trm-vs-standalone-tms): Run treasury inside SAP (TRM) or buy a standalone TMS? A vendor-neutral look at the embedded-vs-best-of-breed trade-off, the real drivers, and who each fits. - [Security Boundaries for Enterprise AI Agents](https://gravam.com/blog/enterprise-ai-agent-security-boundaries): An agent that reads untrusted content can be instructed by it. What the boundaries are, which of them hold under pressure, and which are theatre. - [Should You Connect an AI Agent Directly to Your ERP?](https://gravam.com/blog/connecting-ai-agents-to-your-erp): Practitioners say don't, vendors say it's supported. They answer different questions. Three things a direct connection costs — one of them commercial. - [SWIFT gpi: Tracking Cross-Border Payments](https://gravam.com/blog/swift-gpi-tracking-cross-border-payments): SWIFT gpi makes cross-border payments faster and trackable end to end, giving each a unique reference (UETR) so you can follow its status. What treasury gets. - [The Best Treasury Management System: How to Choose](https://gravam.com/blog/best-treasury-management-system): There is no single best TMS — the right one depends on your category. A vendor-neutral guide to the four kinds of TMS, who each fits, and how to decide. - [The Enterprise AI Control Layer](https://gravam.com/blog/the-enterprise-ai-control-layer): You cannot make an AI system safe by improving the model. Safety lives in a control layer between your systems of record and the agents acting on them. - [The EU AI Act's High-Risk Rules Are a Control Environment](https://gravam.com/blog/eu-ai-act-high-risk-requirements-finance-systems): The high-risk deadline moved to December 2027. What the rules ask for did not move — and a finance function already runs most of it under other names. - [The OWASP LLM Top 10 (2026), Read From a Finance Seat](https://gravam.com/blog/owasp-llm-top-10-2026-for-enterprise-finance): All ten 2026 entries with what changed from 2025 — and which of them a finance or treasury deployment actually meets first. - [Treasury Bank Connectivity: SWIFT, Host-to-Host, API, EBICS](https://gravam.com/blog/treasury-bank-connectivity-swift-host-to-host-api-ebics): SWIFT, host-to-host, API and EBICS — how corporate treasury connects to banks, compared on reach, cost, real-time capability and setup effort. - [Treasury Exposure Data Quality](https://gravam.com/blog/treasury-exposure-data-quality): Every hedge and risk decision rests on exposure data. How to make it trustworthy — accuracy, completeness, timeliness, adaptability — and who owns each. - [Treasury Management System Total Cost of Ownership](https://gravam.com/blog/treasury-management-system-total-cost-of-ownership): The TCO of a TMS is the full lifetime cost: not just the licence, but implementation, integration, internal effort, upgrades. Why the licence is the tip. - [Treasury Risk Aggregation & Reporting](https://gravam.com/blog/treasury-risk-aggregation-and-reporting): How to aggregate treasury risk across exposures, entities and instruments — and report it so it drives a decision, not just fills a pack. - [What Is SAP Treasury and Risk Management (TRM)?](https://gravam.com/blog/what-is-sap-treasury-and-risk-management): SAP Treasury and Risk Management (TRM) manages financial transactions and risk: capturing deals, valuing them, measuring risk, and posting to accounting. ## Cornerstone articles The essential reading in each domain — start here: ### Enterprise AI Transformation - [What AI Transformation Actually Means](https://gravam.com/blog/what-ai-transformation-actually-means): Adopting AI tools, automating a task and redesigning the work are three different things. The difference, and a four-question test for which one you're doing. - [Why Most AI Pilots Never Become Operating Systems](https://gravam.com/blog/why-most-ai-pilots-never-become-operating-systems): A pilot proves capability. Running the work needs state, an exception path, decision rights and an owner — which is why good demos never become the system. - [How to Find Workflows Worth Redesigning With AI](https://gravam.com/blog/how-to-find-enterprise-workflows-worth-redesigning-with-ai): Eight dimensions you can observe rather than debate — frequency, effort, input, judgement, exceptions, error cost, state, control — and the verdict they give. - [How to Measure ROI From an AI Workflow](https://gravam.com/blog/how-to-measure-roi-from-an-ai-workflow): Licences times adoption times a guess measures deployment, not outcome. The ten metrics that move when work is redesigned, and how to baseline them credibly. - [Where to Start With Enterprise AI](https://gravam.com/blog/where-to-start-with-enterprise-ai): Not with a pilot. A sequence borrowed from enterprise systems delivery — and the three steps in it that change when the component is probabilistic. ### AI Workflow Design - [The Anatomy of an AI-Native Enterprise Workflow](https://gravam.com/blog/anatomy-of-an-ai-native-enterprise-workflow): Take a complex process apart: what must stay deterministic, what AI genuinely does well, what a named human decides, and the state the work has to hold. - [AI Automation vs Augmentation vs Autonomy](https://gravam.com/blog/ai-automation-vs-augmentation-vs-autonomy): Three genuinely different designs, not three rungs of a ladder. The criteria that decide which one a piece of enterprise work actually deserves. - [Human Decision Rights in AI-Native Workflows](https://gravam.com/blog/human-decision-rights-in-ai-native-workflows): The useful question is not what AI can automate. It is who is allowed to decide what — a rights matrix over every action a workflow contains. - [Designing the Exception Path](https://gravam.com/blog/designing-the-exception-path): Demos are built on the clean case; enterprise work lives in the other one. Detection, queue, escalation, resolution and the write-back almost everyone omits. ### Enterprise AI Systems - [Why Enterprise AI Is an Architecture Problem](https://gravam.com/blog/why-enterprise-ai-is-an-architecture-problem): Enterprise AI stalls on architecture, not model quality: who owns the record, what the AI may write, under whose identity, and how it is logged and rolled back. - [How AI Agents Fit Into Existing Enterprise Systems](https://gravam.com/blog/how-ai-agents-fit-into-existing-enterprise-systems): The four placements an AI agent can take beside your existing systems — read-only, propose-and-queue, scoped write, orchestrator — and what each one demands. - [The Enterprise AI Control Layer](https://gravam.com/blog/the-enterprise-ai-control-layer): You cannot make an AI system safe by improving the model. Safety lives in a control layer between your systems of record and the agents acting on them. - [Agent Identity: Who Is the AI Acting As?](https://gravam.com/blog/agent-identity-and-permissions): Delegated, shared, agent-specific or temporary — the four identities an AI agent can act under, and what each one costs you in attribution and blast radius. - [Security Boundaries for Enterprise AI Agents](https://gravam.com/blog/enterprise-ai-agent-security-boundaries): An agent that reads untrusted content can be instructed by it. What the boundaries are, which of them hold under pressure, and which are theatre. ### Treasury Management Systems - [What Is a Treasury Management System (TMS)?](https://gravam.com/blog/what-is-a-treasury-management-system): A treasury management system (TMS) manages cash, liquidity, payments, risk and bank connectivity — what it does, when you need one, and how it fits. - [Building the Business Case for a Treasury Management System](https://gravam.com/blog/treasury-management-system-business-case): How to build a credible TMS business case: the quantifiable benefits, the full cost of ownership, and how to make it stand up to CFO scrutiny. - [Treasury Management System Implementation Guide](https://gravam.com/blog/treasury-management-system-implementation-guide): How a TMS implementation really runs: mobilize, design, bank connectivity, data migration, testing, cutover, hypercare. The phases, timeline and critical path. - [Why TMS Implementations Fail (and How to De-Risk Yours)](https://gravam.com/blog/why-tms-implementations-fail): Why TMS implementations fail: rarely the software — it's the treasury change. IT-project thinking, bank connectivity, dirty data, no one owning the outcome. ### Corporate Cash & Liquidity Management - [The 13-Week Cash Flow Forecast: A Practical Guide](https://gravam.com/blog/13-week-cash-flow-forecast): A rolling, week-by-week projection of cash in and out over the next quarter, on a direct receipts-and-disbursements basis. Why 13 weeks, and how to build one. - [How to Build a Daily Cash Position](https://gravam.com/blog/how-to-build-a-daily-cash-position): A daily cash position is a consolidated view of the cash available today across every account and currency — prior-day vs intraday, actuals vs expected. - [How to Achieve Global Cash Visibility](https://gravam.com/blog/how-to-achieve-global-cash-visibility): Global cash visibility is seeing all the group's cash (every account, currency and bank) in one timely view. Mostly a data problem: full statement coverage. - [What Is an In-House Bank? A Treasury Guide](https://gravam.com/blog/what-is-an-in-house-bank): An in-house bank is a central treasury acting as a bank for the group — internal accounts, intercompany funding, on-behalf-of payments and netting. ### Treasury Risk Management - [What Is Treasury Risk Management?](https://gravam.com/blog/what-is-treasury-risk-management): How a company identifies, measures and manages its financial risks — liquidity, FX, interest rate, counterparty — keeping risk within appetite, not at zero. - [FX Risk: Transaction, Translation and Economic Exposure](https://gravam.com/blog/fx-risk-transaction-translation-economic-exposure): FX risk comes in three types — transaction, translation and economic exposure. Why classifying them correctly is where FX management actually starts. - [Hedge Accounting Explained](https://gravam.com/blog/hedge-accounting-explained): Hedge accounting aligns the timing of a hedge's gains and losses with the hedged item, so the P&L shows they offset. Why it exists, and the three hedge types. - [Risk Appetite and Risk Limits in Treasury](https://gravam.com/blog/risk-appetite-and-limits-in-treasury): Treasury risk appetite is how much financial risk a company chooses to bear; risk limits are the measurable guardrails that enforce it — why both matter. ### Treasury Systems Architecture & Connectivity - [A Reference Architecture for Corporate Treasury](https://gravam.com/blog/reference-architecture-for-corporate-treasury): How a corporate treasury landscape fits together: ERP, TMS, bank connectivity and market data, joined by defined interfaces, with a system-of-record matrix. - [What Is the Treasury System of Record?](https://gravam.com/blog/treasury-system-of-record): A treasury system of record is the single authoritative source for its data. Designating one, and the TMS-vs-ERP boundary, ends 'which number is right?' - [Treasury Bank Connectivity: SWIFT, Host-to-Host, API, EBICS](https://gravam.com/blog/treasury-bank-connectivity-swift-host-to-host-api-ebics): SWIFT, host-to-host, API and EBICS — how corporate treasury connects to banks, compared on reach, cost, real-time capability and setup effort. - [Bank Connectivity Security: Keys, Certificates and Controls](https://gravam.com/blog/bank-connectivity-security): The security layer under treasury bank connectivity: certificate and key lifecycle, mTLS, OAuth, key rotation, HSM, SWIFT CSP, and who owns the technical user. ### SAP Treasury & Cash Management - [What Is SAP Treasury and Risk Management (TRM)?](https://gravam.com/blog/what-is-sap-treasury-and-risk-management): SAP Treasury and Risk Management (TRM) manages financial transactions and risk: capturing deals, valuing them, measuring risk, and posting to accounting. - [SAP Cash Management in S/4HANA](https://gravam.com/blog/sap-cash-management-s4hana): SAP Cash Management in S/4HANA — business function FIN_FSCM_CLM, the three areas, the Fiori apps, the IMG spine and the One Exposure data layer, verified. - [One Exposure from Operations & FQM_FLOW Explained](https://gravam.com/blog/one-exposure-from-operations-fqm-flow): One Exposure from Operations is the hub at the centre of S/4HANA Cash Management — a single store (FQM_FLOW) every cash-relevant flow feeds. Why it exists. - [SAP Transaction Manager: Deals and Instruments](https://gravam.com/blog/sap-transaction-manager): The Transaction Manager is the core of SAP TRM, where financial deals live — money market, FX, securities and derivatives, from capture to accounting. ### Building AI Products - [My Product Operating System for Building Multiple AI Apps](https://gravam.com/blog/my-product-operating-system): The product operating system I use to build several focused AI products solo: choosing which problem to build, shipping fast, and killing what isn't working. - [How I Use AI Without Letting AI Make Product Decisions](https://gravam.com/blog/how-i-use-ai-without-letting-ai-decide): Using AI to build products means AI owns the how — code, scaffolding, drafts — while I keep the what and why: the problem, outcome, cuts and pricing. - [Why Most AI-Built Apps Feel Like Demos](https://gravam.com/blog/why-most-ai-built-apps-feel-like-demos): Why AI apps feel like demos: they look finished but solve nothing — AI made the product decisions. It optimizes for plausible; products win by being pointed. ### Finance Systems Delivery - [Project Intake Process for Finance and Engineering Teams](https://gravam.com/blog/project-intake-process-for-finance-and-engineering-teams): How a team receives, shapes and decides on incoming work before committing people: the stages, the fields that matter, and four honest decisions. - [Testing Strategy for Finance Systems: SIT, UAT, Regression](https://gravam.com/blog/testing-strategy-for-finance-systems): A testing strategy defines how you prove a finance system works before go-live — unit, SIT, UAT and regression. In finance, the numbers must reconcile too. - [User Acceptance Testing for Finance Systems](https://gravam.com/blog/user-acceptance-testing-for-finance-systems): UAT is where the people who'll use a finance system verify it does what they need, with real scenarios and reconciling numbers. Why finance UAT is different. - [Cutover and Go-Live for Finance Systems](https://gravam.com/blog/cutover-and-go-live-for-finance-systems): Finance system cutover is the tightly-planned transition from old to new — migration, switchover, go-live — in a short, high-stakes window. ## Tools Free, interactive, no-signup tools that pair with the writing — each solves a real task: - [TMS Vendor Scorecard](https://gravam.com/tools/tms-vendor-scorecard): Weighted scorecard to compare treasury-system vendors on your priorities. Set weights, score 1–5, see the ranking live, export CSV. - [13-Week Cash Flow Model](https://gravam.com/tools/13-week-cash-flow-model): A working direct cash-flow template: enter weekly receipts and payments, get the running closing balance, and see the week you'd go short. Export CSV. - [Project Intake One-Pager](https://gravam.com/tools/project-intake-one-pager): Turn a raw request into a decision-ready one-pager — problem, outcome, scope, owner, open questions — and commit, shape, pause or decline. Copy or download. - [TMS Business-Case Calculator](https://gravam.com/tools/tms-business-case-calculator): Turn your own numbers — hours saved, idle cash, fees, losses avoided — into a treasury-system business case: annual benefit, payback period and multi-year ROI. - [Cutover & Go-Live Checklist](https://gravam.com/tools/cutover-go-live-checklist): A go/no-go checklist where the critical items gate the verdict: run a finance-system cutover (readiness, migration, validation smoke tests), or the five AI pilot exit gates. Copy, download, or email yourself the link. - [System-of-Record Map](https://gravam.com/tools/system-of-record-map): Map each treasury data domain to its single system of record, consumers and integration — the one-owner-per-domain discipline. Export as a markdown table. - [Hedge Effectiveness Checker](https://gravam.com/tools/hedge-effectiveness-checker): Enter each period's change in fair value for the hedging instrument and the hedged item; get the dollar-offset ratio against the 80–125% reference band plus a regression (slope, R², correlation). Export CSV. - [SAP Treasury Module & Edition Selector](https://gravam.com/tools/sap-treasury-module-selector): Tick your treasury needs and see which SAP components address them — Cash Management, Transaction Manager, One Exposure, the Analyzers, BCM, APM, IHC — each linked to a full guide, plus the edition trade-offs to weigh. Export markdown. - [AI Product Idea Scorecard](https://gravam.com/tools/ai-product-idea-scorecard): Score your product idea on the signals that decide whether it's worth building — real problem, distribution, narrow scope, a genuine edge — with two must-haves that gate the call, and get a commit / shape / park / pass verdict. Export markdown. - [TMS RFP Template Builder](https://gravam.com/tools/tms-rfp-template): Assemble a complete treasury-system RFP: company context, prioritized requirements by module (every prompt asks how, not whether), vendor questions on implementation, pricing, support and roadmap, plus the evaluation weights fixed in the document — then copy or download it as markdown. - [RAID Log Template](https://gravam.com/tools/raid-log-template): Start a working RAID log: add risks, assumptions, issues and dependencies — each with the owner, due date and next action that make an entry real — then export it as markdown or CSV. ## Engagements Paid work, all of it with 18 years in SAP, finance, treasury and enterprise systems behind it. Scope and price depend on the workflow, so none is published — see https://gravam.com/work-with-me for the buying questions answered plainly, including whether there are client references yet: - [AI Workflow Redesign Sprint](https://gravam.com/work-with-me#redesign-sprint): For a workflow you already know is a problem: slow, manual, exception-ridden, or quietly expensive. One complex enterprise workflow, redesigned end to end around AI: what stays deterministic, what AI reads or proposes, who decides, the state it holds and the exception path — with the architecture and controls the redesign implies. - [AI Workflow Opportunity Scan](https://gravam.com/work-with-me#opportunity-scan): For before you have chosen which workflow to change. An assessment of the real workflows in a function against the things that decide whether AI changes their economics — returning a ranked shortlist with the reasoning visible, and a defensible reason for the two or three worth pursuing. - [Enterprise AI Architecture Review](https://gravam.com/work-with-me#architecture-review): For when something is already being built or already running. A review of where an AI capability sits relative to the systems of record: what it may write and under whose identity, how its actions are logged and reconciled, what happens when a dependency is unavailable, and what rollback means. ## Products - [Delivery Sheet](https://gravam.com/products/delivery-sheet): Turn vague leadership asks into clear, reviewable delivery decisions — before your team commits. - [Workomap](https://gravam.com/products/workomap): The global map of SAP professionals — see where the SAP world lives and works, and put yourself on it. - [Yollardayız](https://gravam.com/products/yollardayiz): Live border-crossing waits for the sıla yolu — which gate, and when, backed by data instead of hearsay. - [Listemizde](https://gravam.com/products/listemizde): Don't lose the places you trust — found through real community recommendations, not paid rankings. ## More - [Writing](https://gravam.com/blog): Every published article, newest first, filterable by topic. - [All topics A–Z](https://gravam.com/topics): Index of every article by its subject term — the term-level way into the corpus. - [Code reference](https://gravam.com/reference): Every code the reference posts document — SAP transaction codes, tables and Fiori app ids, ISO 20022 reject reasons, camt.053 balance types, MT940 and BAI2 codes — each with its meaning and a link into the section that explains it. Derived from the articles themselves, so it cannot disagree with them. - [About Tan Gravam](https://gravam.com/about): Enterprise AI practitioner and systems architect — 18 years in SAP, finance, treasury and enterprise systems. - [LinkedIn](https://www.linkedin.com/in/tangravam/): The primary channel — the same profile the site's Person schema lists under sameAs. - [Work with me](https://gravam.com/work-with-me): AI workflow redesign sprint, opportunity scan and enterprise AI architecture review. - [Newsletter](https://gravam.com/newsletter): Gravam newsletter — one practical idea at a time on enterprise AI, workflow design and systems architecture — sent when there is one worth sending, never on a schedule for its own sake. - [Contact](https://gravam.com/contact): Get in touch about redesigning a workflow with AI, enterprise AI architecture, or finance-systems work. - [Full corpus](https://gravam.com/llms-full.txt): Every reviewed article in full, as Markdown — the complete text, not just the cornerstones. - Single article as Markdown: https://gravam.com/md/ for any https://gravam.com/blog/.