[{"data":1,"prerenderedAt":233},["ShallowReactive",2],{"topic-treasury-systems-architecture":3,"topic-faq-treasury-systems-architecture":182,"topic-nav-counts-treasury-systems-architecture":227},[4,15,21,27,32,38,44,50,59,66,73,78,83,88,93,98,104,109,114,120,125,130,136,140,144,148,152,157,162,167,172,177],{"path":5,"title":6,"description":7,"type":8,"language":9,"date":10,"order":11,"cluster":12,"minRead":13,"cornerstone":14},"\u002Fblog\u002Fbai2-file-format-explained","BAI2 File Format: Records, Type Codes and How to Read One","Every BAI2 record explained: the 01–99 hierarchy, balance codes 010\u002F015\u002F040\u002F045, credit vs debit type-code ranges, the funds-type field and control totals.","text",null,"2026-08-03",3.4,"connectivity",14,false,{"path":16,"title":17,"description":18,"type":8,"language":9,"date":10,"order":19,"cluster":12,"minRead":20,"cornerstone":14},"\u002Fblog\u002Fcamt-054-notification-explained","camt.054: The Debit\u002FCredit Notification and When You Need It","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.",3.25,9,{"path":22,"title":23,"description":24,"type":8,"language":9,"date":10,"order":25,"cluster":12,"minRead":26,"cornerstone":14},"\u002Fblog\u002Fmt940-format-tags-explained","MT940 Format: The Tags, Line by Line","Every MT940 tag explained: :20:, :25:, :28C:, the :61: statement line subfield by subfield, the bank-specific :86:, and the :62a:\u002F:64:\u002F:65: balances.",3.3,11,{"path":28,"title":29,"description":30,"type":8,"language":9,"date":10,"order":31,"cluster":12,"minRead":26,"cornerstone":14},"\u002Fblog\u002Fpain-002-status-and-reject-codes","pain.002 Status and Reject Codes: Reading the Bank's Reply","How to read a pain.002 status report: group, payment and transaction level, the ACTC\u002FACCP\u002FACSC status codes, and reject reasons like AC01, AC04 and AM04.",4.07,{"path":33,"title":34,"description":35,"type":8,"language":9,"date":36,"order":37,"cluster":12,"minRead":26,"cornerstone":14},"\u002Fblog\u002Fcamt-053-structure-and-fields","camt.053 Structure: Reading the Statement Field by Field","The camt.053 statement field by field: GroupHeader to TransactionDetails, OPBD\u002FCLBD balance codes, the Bank Transaction Code, and where bank files diverge.","2026-08-02",3.2,{"path":39,"title":40,"description":41,"type":8,"language":9,"date":36,"order":42,"cluster":12,"minRead":43,"cornerstone":14},"\u002Fblog\u002Fmt101-vs-mt103-vs-mt202","MT101 vs MT103 vs MT202: Which SWIFT Message Does What","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.",3.5,7,{"path":45,"title":46,"description":47,"type":8,"language":9,"date":36,"order":48,"cluster":12,"minRead":49,"cornerstone":14},"\u002Fblog\u002Fpain-001-structure-and-fields","pain.001 Structure: The Fields That Actually Matter","Inside the pain.001 file: GroupHeader, PaymentInformation and the transaction level — which fields treasury maps, and where bank implementations differ.",4.05,12,{"path":51,"title":52,"description":53,"type":54,"language":9,"date":55,"order":56,"cluster":12,"minRead":57,"cornerstone":58},"\u002Fblog\u002Fbank-connectivity-security","Bank Connectivity Security: Keys, Certificates and Controls","The security layer under treasury bank connectivity: certificate and key lifecycle, mTLS, OAuth, key rotation, HSM, SWIFT CSP, and who owns the technical user.","pattern","2026-07-28",6.5,6,true,{"path":60,"title":61,"description":62,"type":54,"language":9,"date":55,"order":63,"cluster":64,"minRead":65,"cornerstone":14},"\u002Fblog\u002Ftreasury-data-lineage","Treasury Data Lineage: Source to Reported Number","Answer 'where did this number come from?' in minutes, not days: trace any treasury figure from source transaction to reported number — and who owns each hop.",1.87,"architecture",5,{"path":67,"title":68,"description":69,"type":8,"language":9,"date":70,"order":71,"cluster":72,"minRead":57,"cornerstone":14},"\u002Fblog\u002Faccess-management-and-user-provisioning-treasury","Access Management and User Provisioning in Treasury Systems","A treasury system can move money, so who can do what inside it is a first-order control. Access management is the foundation segregation of duties stands on.","2026-07-24",8.5,"controls",{"path":74,"title":75,"description":76,"type":8,"language":9,"date":70,"order":77,"cluster":72,"minRead":65,"cornerstone":14},"\u002Fblog\u002Faudit-trails-and-logging-treasury-systems","Audit Trails and Logging in Treasury Systems","A treasury audit trail must capture who did what, when, and to what — the tamper-evident record that proves segregation of duties and approvals actually worked.",8.7,{"path":79,"title":80,"description":81,"type":8,"language":9,"date":70,"order":82,"cluster":72,"minRead":57,"cornerstone":14},"\u002Fblog\u002Fdisaster-recovery-business-continuity-treasury","Disaster Recovery and Business Continuity for Treasury","Keeping treasury running through an outage: how RTO and RPO drive the design, and why the manual fallback is the plan that actually saves the payment.",8.9,{"path":84,"title":85,"description":86,"type":8,"language":9,"date":70,"order":87,"cluster":12,"minRead":57,"cornerstone":14},"\u002Fblog\u002Febics-european-bank-connectivity","EBICS Explained: 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.",2.5,{"path":89,"title":90,"description":91,"type":8,"language":9,"date":70,"order":92,"cluster":12,"minRead":57,"cornerstone":14},"\u002Fblog\u002Fiso-20022-migration-mt-to-mx","ISO 20022 Migration: Moving from SWIFT MT to MX (CBPR+)","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.",4.1,{"path":94,"title":95,"description":96,"type":8,"language":9,"date":70,"order":97,"cluster":72,"minRead":57,"cornerstone":14},"\u002Fblog\u002Fpayment-fraud-prevention-in-treasury","Payment Fraud Prevention and Controls in Treasury","Payment fraud prevention in treasury: the main threats are BEC, invoice redirection, insider diversion and standing-data tampering — and how to stop them.",8.3,{"path":99,"title":100,"description":101,"type":8,"language":9,"date":70,"order":102,"cluster":12,"minRead":103,"cornerstone":14},"\u002Fblog\u002Freal-time-treasury","Real-Time Treasury: What It Actually Means","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.",4.7,4,{"path":105,"title":106,"description":107,"type":8,"language":9,"date":70,"order":108,"cluster":12,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fswift-gpi-tracking-cross-border-payments","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.",4.3,{"path":110,"title":111,"description":112,"type":8,"language":9,"date":70,"order":113,"cluster":64,"minRead":43,"cornerstone":14},"\u002Fblog\u002Ftreasury-data-quality-and-governance","Treasury Data Quality and Governance","Treasury data quality decides which numbers you can trust — cash, exposure, valuation, forecast are all computed from it, and governance keeps it clean.",1.85,{"path":115,"title":116,"description":117,"type":8,"language":9,"date":70,"order":118,"cluster":119,"minRead":57,"cornerstone":14},"\u002Fblog\u002Ftreasury-integration-patterns-files-apis-middleware","Treasury Integration Patterns: Files, APIs and Middleware","Treasury integration patterns — batch files, APIs and middleware — and their trade-offs, plus why point-to-point connections collapse under their own weight.",5.5,"integration",{"path":121,"title":122,"description":123,"type":8,"language":9,"date":70,"order":124,"cluster":64,"minRead":57,"cornerstone":14},"\u002Fblog\u002Ftreasury-master-data-management","Treasury Master Data Management","Treasury master data is the static reference data everything depends on — banks, counterparties, instruments, settlement instructions — and ownership is key.",1.8,{"path":126,"title":127,"description":128,"type":8,"language":9,"date":70,"order":129,"cluster":64,"minRead":57,"cornerstone":14},"\u002Fblog\u002Ftreasury-reporting-and-analytics-architecture","Treasury Reporting and Analytics Architecture","Treasury reporting architecture explained — operational, warehouse and BI layers — and why every reported number is only as trustworthy as its source.",1.9,{"path":131,"title":132,"description":133,"type":8,"language":9,"date":134,"order":135,"cluster":12,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","Bank Statement Formats: MT940 vs camt.053 vs 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.","2026-07-23",3,{"path":137,"title":138,"description":139,"type":8,"language":9,"date":134,"order":65,"cluster":119,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fdesigning-erp-tms-integration","Designing ERP-to-TMS Integration","ERP TMS integration design: what flows each way, batch vs real-time, reconciliation and ownership — so your ERP and treasury system stay in step.",{"path":141,"title":142,"description":143,"type":8,"language":9,"date":134,"order":57,"cluster":119,"minRead":103,"cornerstone":14},"\u002Fblog\u002Finterface-monitoring-and-reconciliation","Interface Monitoring and Reconciliation for Treasury Systems","Treasury interfaces fail silently and partially. Monitoring proves each ran; reconciliation proves the data arrived intact. How to design both from the start.",{"path":145,"title":146,"description":147,"type":8,"language":9,"date":134,"order":103,"cluster":12,"minRead":135,"cornerstone":14},"\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","ISO 20022 Payments Explained: pain.001 and 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.",{"path":149,"title":150,"description":151,"type":8,"language":9,"date":134,"order":43,"cluster":119,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fmarket-data-in-treasury-systems","Market Data in Treasury Systems","Market data (FX rates, interest curves, prices) is the external reference data treasury needs to value positions. How to source, control and integrate it.",{"path":153,"title":154,"description":155,"type":8,"language":9,"date":134,"order":156,"cluster":64,"minRead":65,"cornerstone":58},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","A 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.",1,{"path":158,"title":159,"description":160,"type":8,"language":9,"date":134,"order":161,"cluster":72,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fsegregation-of-duties-in-treasury-systems","Segregation of Duties in Treasury Systems","Treasury moves money, so it's a prime fraud target. Segregation of duties means no one person can initiate, approve and release a payment or trade alone.",8,{"path":163,"title":164,"description":165,"type":8,"language":9,"date":134,"order":166,"cluster":119,"minRead":103,"cornerstone":14},"\u002Fblog\u002Fstraight-through-processing-in-treasury","Straight-Through Processing in Treasury","Straight-through processing (STP) means a transaction flows from initiation to settlement with no manual re-keying. Why every manual touchpoint is a risk.",7.5,{"path":168,"title":169,"description":170,"type":8,"language":9,"date":134,"order":171,"cluster":12,"minRead":103,"cornerstone":58},"\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics","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.",2,{"path":173,"title":174,"description":175,"type":8,"language":9,"date":134,"order":176,"cluster":64,"minRead":103,"cornerstone":14},"\u002Fblog\u002Ftreasury-data-model","The Treasury Data Model","The treasury data model is the structure of a treasury system's data — the core entities and the reference data they depend on. Why every output rests on it.",1.7,{"path":178,"title":179,"description":180,"type":8,"language":9,"date":134,"order":181,"cluster":64,"minRead":103,"cornerstone":58},"\u002Fblog\u002Ftreasury-system-of-record","What Is the 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?'",1.5,[183,194,205,216],{"path":51,"title":52,"order":56,"faq":184},[185,188,191],{"question":186,"answer":187},"What secures a treasury bank connection?","Layered controls, not one setting. Transport is secured with TLS — often mutual TLS (mTLS), where both the client and the bank present certificates — so each end proves who it is and the channel is encrypted. Messages are additionally signed (proving origin and integrity) and often encrypted (protecting content), so a payment file is trustworthy even independent of the pipe it travelled through. Access is authorised: client certificates, EBICS keys, or OAuth client credentials for APIs. And all of it rests on identity and key management — whose keys, stored where, rotated when — plus monitoring so an expiry or anomaly is caught before it stops payments.",{"question":189,"answer":190},"What is SWIFT CSP and is it mandatory?","The SWIFT Customer Security Programme (CSP) is a mandatory programme for SWIFT users to protect their SWIFT-related infrastructure against cyber threats. Its core is the Customer Security Controls Framework (CSCF), which defines a baseline of mandatory controls (that all in-scope users must implement) and advisory controls (recommended, and some become mandatory over time). Users attest their compliance annually. The controls are aligned to recognised standards such as ISO 27002, PCI DSS, SOC 2 and NIST CSF. It applies to SWIFT connectivity specifically — but its principles (segregation, least privilege, monitoring, integrity) are a sound baseline for any bank channel.",{"question":192,"answer":193},"How often should bank connectivity certificates and keys be rotated?","On a defined schedule and before expiry — never reactively after payments have already failed. Certificates and keys have finite lifetimes; the risks are an unnoticed expiry (which silently breaks a channel) and a stale credential that outlives the person or purpose it was issued for. Good practice is a tracked inventory of every certificate and key with its expiry, owner and channel; rotation planned well ahead of expiry; and automated expiry monitoring that alerts weeks in advance. Rotation itself is a coordinated change with the bank, tested in a non-production channel where possible, with a rollback path.",{"path":153,"title":154,"order":156,"faq":195},[196,199,202],{"question":197,"answer":198},"What does a corporate treasury systems architecture look like?","At its simplest, four layers connected by defined interfaces: source systems (the ERP, holding the ledger, AP and AR), the treasury system (a TMS or the ERP's treasury module, handling cash, risk and payments), bank connectivity (the channel to banks for statements and payments), and market data (FX and interest rates). The value and the risk are in the interfaces and in deciding which system is the source of record for each type of data.",{"question":200,"answer":201},"Which system should be the system of record for each treasury data domain?","One system per domain: the ERP owns the general ledger, the TMS owns the cash position and exposures, and bank master data has one owner rather than being maintained in several places. Defining the system of record for each domain is the most important architectural decision because it prevents duplicate maintenance and reconciliation.",{"question":203,"answer":204},"What data flows between the ERP and the TMS?","The ERP typically sends AP\u002FAR and reference data to the TMS, and the TMS sends accounting entries (and sometimes payment status) back to the ERP's general ledger — through defined interfaces. The design should be interface-based and governed, not a web of point-to-point extracts, and it should follow the system-of-record decisions so each field flows from its owner.",{"path":168,"title":169,"order":171,"faq":206},[207,210,213],{"question":208,"answer":209},"What is the difference between SWIFT, host-to-host and API bank connectivity?","SWIFT is a shared network that reaches many banks through one standardized connection — good for multi-bank reach, higher in cost and complexity. Host-to-host is a direct, secure file exchange between your systems and one specific bank — efficient for a few high-volume relationships. API connectivity is real-time and modern, bank-by-bank, best where you need instant balances or payment status. EBICS is a standard used mainly in parts of Europe. Most corporates use a mix, chosen by bank and need.",{"question":211,"answer":212},"Which bank connectivity method is best for corporate treasury?","It depends on your bank landscape. If you deal with many banks across regions, SWIFT's single multi-bank connection is attractive. If you have a few strategic banks with high volumes, host-to-host is efficient. Where real-time balances or instant payment status matter, APIs are the direction of travel. In Europe, EBICS is common. There is no single best answer — most treasuries combine channels.",{"question":214,"answer":215},"Is connectivity the same as file format?","No, and confusing them causes trouble. Connectivity is the channel — how the message travels (SWIFT, host-to-host, API, EBICS). The format is the content — what the message says (MT940 or camt.053 for statements, pain.001 for payments). You choose a channel and a format per bank, and both have to be agreed and tested.",{"path":178,"title":179,"order":181,"faq":217},[218,221,224],{"question":219,"answer":220},"What is a system of record in treasury?","A system of record is the single, authoritative source for a given set of data — the system whose version is treated as definitive when systems disagree. In treasury, it's the system that holds the master version of deals, cash positions, exposures and bank data, typically the treasury management system. Designating one system of record per data domain is what lets an organization answer 'which number is right?' with certainty instead of a debate.",{"question":222,"answer":223},"What is the difference between a system of record and a system of engagement?","A system of record holds the authoritative, master version of data — it's where the truth lives. A system of engagement or reference is a system that consumes and presents that data for a particular use, without owning it. A dashboard or a reporting layer can be a system of engagement built on top of the treasury system of record. The distinction matters because only the system of record's copy is authoritative; everything else is a view.",{"question":225,"answer":226},"Should the TMS or the ERP be the system of record for treasury data?","It depends on the data domain, and the key is drawing a clean boundary. Typically the TMS is the system of record for treasury-specific data — deals, positions, exposures, bank statements and connectivity — while the ERP remains the system of record for the general ledger and accounting. Problems arise when both systems claim ownership of the same data and sync bidirectionally, creating two competing versions of the truth. Decide who owns what, once, explicitly.",{"enterprise-ai-transformation":43,"ai-workflow-design":57,"enterprise-ai-systems":228,"treasury-management-systems":229,"cash-and-liquidity-management":230,"treasury-risk-management":229,"sap-treasury":231,"building-ai-products":231,"finance-systems-delivery":232},16,21,31,32,27,1787475407366]