[{"data":1,"prerenderedAt":390},["ShallowReactive",2],{"blog-\u002Fblog\u002Ftreasury-data-model":3,"blog-surround-\u002Fblog\u002Ftreasury-data-model":372,"blog-related-\u002Fblog\u002Ftreasury-data-model":380},{"id":4,"title":5,"audience":6,"body":10,"cluster":337,"date":338,"description":339,"draft":340,"extension":341,"factCheckedAt":342,"faq":343,"featured":340,"language":342,"meta":353,"navigation":354,"order":355,"originalAsset":342,"path":356,"pillar":357,"primaryKeyword":358,"relatedProject":342,"releaseScope":342,"reviewCycle":359,"reviewStatus":360,"reviewedBy":361,"searchIntent":362,"seo":363,"sources":342,"stem":364,"tags":365,"type":370,"updated":338,"__hash__":371},"blog\u002Fblog\u002Ftreasury-data-model.md","The Treasury Data Model",[7,8,9],"treasury-system-lead","solution-architect","data-architect",{"type":11,"value":12,"toc":325},"minimark",[13,42,47,58,62,65,104,107,111,118,150,157,161,189,193,213,217,239,243,260,264,296,299,302],[14,15,16,20,21,25,26,31,32,36,37,41],"p",{},[17,18,19],"strong",{},"The treasury data model is the structure of the data a treasury system holds — the core entities (deals, positions, cash flows, exposures) and the reference data (counterparties, bank accounts, instruments, currencies) they depend on, and how they all relate."," It's foundational because ",[22,23,24],"em",{},"everything the system produces derives from it",": every position, valuation, exposure, forecast, ",[27,28,30],"a",{"href":29},"\u002Fblog\u002Ftreasury-reporting-and-analytics-architecture","report"," and control is computed from this underlying data. Get the model coherent and ",[27,33,35],{"href":34},"\u002Fblog\u002Ftreasury-data-quality-and-governance","the reference data clean",", and the outputs are trustworthy; get it messy and every number inherits the flaw — silently, because a wrong figure still looks like a figure. The data model is the quiet foundation the whole ",[27,38,40],{"href":39},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","treasury architecture"," rests on.",[43,44,46],"h2",{"id":45},"what-it-is","What it is",[14,48,49,50,53,54,57],{},"A treasury system isn't really a set of screens — it's a structured body of ",[22,51,52],{},"data"," with logic on top. The data model is that structure: what entities exist, what each represents, how they connect, and which data is authoritative. Understanding it is understanding what the system fundamentally ",[22,55,56],{},"is",".",[43,59,61],{"id":60},"the-core-transactional-entities","The core (transactional) entities",[14,63,64],{},"The activity of treasury, as data:",[66,67,68,75,81,87,98],"ul",{},[69,70,71,74],"li",{},[17,72,73],{},"Deals \u002F transactions"," — the trades, loans, deposits and instruments treasury enters into.",[69,76,77,80],{},[17,78,79],{},"Cash flows"," — the individual payments and receipts a deal generates over its life.",[69,82,83,86],{},[17,84,85],{},"Positions"," — the aggregated holdings at a point in time (what you hold, in what).",[69,88,89,92,93,97],{},[17,90,91],{},"Exposures"," — the ",[27,94,96],{"href":95},"\u002Fblog\u002Ffx-risk-transaction-translation-economic-exposure","risk positions"," derived from deals and holdings.",[69,99,100,103],{},[17,101,102],{},"Balances"," — cash balances by account and currency.",[14,105,106],{},"These are created continuously and flow through the system in volume.",[43,108,110],{"id":109},"the-reference-master-data","The reference (master) data",[14,112,113,114,117],{},"The stable data that transactions ",[22,115,116],{},"refer to",":",[66,119,120,126,132,138,144],{},[69,121,122,125],{},[17,123,124],{},"Counterparties"," — the banks and trading partners deals are done with.",[69,127,128,131],{},[17,129,130],{},"Bank accounts"," — the accounts cash moves through.",[69,133,134,137],{},[17,135,136],{},"Instruments"," — the definitions of the financial instruments used.",[69,139,140,143],{},[17,141,142],{},"Currencies & calendars"," — the currencies, rates context, and business-day calendars.",[69,145,146,149],{},[17,147,148],{},"Standing settlement instructions"," — how and where payments settle.",[14,151,152,153,156],{},"Reference data is relatively stable, but ",[22,154,155],{},"shared by everything"," — so an error in it propagates everywhere.",[43,158,160],{"id":159},"master-vs-transactional-data","Master vs transactional data",[162,163,165],"callout",{"type":164},"tip",[14,166,167,168,171,172,176,177,180,181,184,185,188],{},"The distinction that keeps a data model clean: ",[17,169,170],{},"master data"," is stable, shared and ",[27,173,175],{"href":174},"\u002Fblog\u002Ftreasury-master-data-management","carefully governed"," (a wrong counterparty or bank account corrupts every transaction that references it); ",[17,178,179],{},"transactional data"," is high-volume activity that references the master. The classic modelling error is storing ",[22,182,183],{},"derived"," data (a position, a valuation) as if it were master data — positions should be ",[22,186,187],{},"computed"," from deals and rates, not maintained by hand, or they drift out of line with the reality they're supposed to summarise.",[43,190,192],{"id":191},"why-the-model-matters","Why the model matters",[14,194,195,196,198,199,203,204,208,209,212],{},"Everything the system outputs is ",[22,197,183],{}," from this data. A ",[27,200,202],{"href":201},"\u002Fblog\u002Fhow-to-build-a-daily-cash-position","cash position"," is computed from balances and flows; a valuation from positions and ",[27,205,207],{"href":206},"\u002Fblog\u002Fmarket-data-in-treasury-systems","market data","; an exposure from deals. So the data model's coherence is the ceiling on the trustworthiness of ",[22,210,211],{},"every"," output. A messy or inconsistent model doesn't announce itself — it just produces subtly wrong numbers that are very hard to trace back to their cause.",[43,214,216],{"id":215},"the-relationships","The relationships",[14,218,219,220,223,224,227,228,231,232,235,236,238],{},"The entities aren't independent — they form a chain: a ",[17,221,222],{},"deal"," generates ",[17,225,226],{},"cash flows"," and contributes to ",[17,229,230],{},"positions","; positions aggregate into ",[17,233,234],{},"exposures","; flows and balances feed the ",[17,237,202],{},". Understanding those relationships is what lets you see how a single mis-modelled deal ripples out into a wrong exposure and a wrong report. The model is the map of those ripples.",[43,240,242],{"id":241},"reference-data-quality","Reference data quality",[14,244,245,246,249,250,254,255,259],{},"Because reference data is shared by everything, its quality is decisive: a wrong bank account, a mis-defined instrument, a duplicated counterparty corrupts every transaction that touches it. Reference data therefore needs ",[22,247,248],{},"governance"," — controlled maintenance, ",[27,251,253],{"href":252},"\u002Fblog\u002Fsegregation-of-duties-in-treasury-systems","segregation of duties"," on changes, and a single authoritative source — exactly the ",[27,256,258],{"href":257},"\u002Fblog\u002Ftreasury-system-of-record","system-of-record"," discipline applied to the data the whole model depends on.",[43,261,263],{"id":262},"what-usually-goes-wrong","What usually goes wrong",[66,265,266,272,278,284,290],{},[69,267,268,271],{},[17,269,270],{},"Inconsistent master data."," The same counterparty or account defined differently in different places, so nothing reconciles.",[69,273,274,277],{},[17,275,276],{},"No clear model."," Data structured ad hoc, so relationships are unclear and outputs are hard to trust or trace.",[69,279,280,283],{},[17,281,282],{},"Derived data stored as master."," Positions or valuations maintained by hand instead of computed, so they drift from reality.",[69,285,286,289],{},[17,287,288],{},"Poor reference-data governance."," Uncontrolled changes to shared data, propagating errors everywhere.",[69,291,292,295],{},[17,293,294],{},"Duplicate entities."," The same real-world thing represented multiple times, fragmenting the data.",[14,297,298],{},"Model the core entities and their relationships coherently, separate master from transactional data, compute derived data rather than storing it by hand, and govern reference data as the shared asset it is — and the treasury data model becomes the dependable foundation every trustworthy output stands on. It's the least visible part of a treasury system and the one everything else quietly depends on.",[300,301],"hr",{},[14,303,304],{},[22,305,306,307,311,312,315,316,319,320,324],{},"Part of the ",[27,308,310],{"href":309},"\u002Ftopics\u002Ftreasury-systems-architecture","Treasury Systems Architecture guide",". See also ",[27,313,314],{"href":257},"the treasury system of record"," and ",[27,317,318],{"href":39},"the reference architecture",". The ",[27,321,323],{"href":322},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":326,"searchDepth":327,"depth":327,"links":328},"",2,[329,330,331,332,333,334,335,336],{"id":45,"depth":327,"text":46},{"id":60,"depth":327,"text":61},{"id":109,"depth":327,"text":110},{"id":159,"depth":327,"text":160},{"id":191,"depth":327,"text":192},{"id":215,"depth":327,"text":216},{"id":241,"depth":327,"text":242},{"id":262,"depth":327,"text":263},"architecture","2026-07-23","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.",false,"md",null,[344,347,350],{"question":345,"answer":346},"What is a treasury data model?","A treasury data model is the structure of the data a treasury system holds and how it relates — the core transactional entities (deals or transactions, positions, cash flows, exposures, balances) and the reference or master data they depend on (counterparties, bank accounts, financial instruments, currencies, calendars). It defines what each piece of data is, how the pieces connect, and which data is authoritative. Every report, valuation and control in the system derives from it, so a coherent data model is foundational to a treasury system working correctly.",{"question":348,"answer":349},"What is the difference between master data and transactional data in treasury?","Master (or reference) data is the relatively stable descriptive data that transactions refer to — counterparties, bank accounts, instruments, currencies, standing settlement instructions. Transactional data is the activity itself — deals, payments, positions, cash flows — which is created continuously and references the master data. The distinction matters because master data must be governed carefully (it's shared by everything and errors propagate widely), while transactional data flows through in volume. Confusing the two, or storing derived data as if it were master, corrupts the model.",{"question":351,"answer":352},"Why does the treasury data model matter?","Because everything the system produces derives from it. Positions, valuations, exposures, cash forecasts, reports and controls are all computed from the underlying data, so if the data model is incoherent or the reference data is wrong, every output inherits the flaw — silently, because a wrong number still looks like a number. A clean, consistent data model with well-governed reference data is what makes the system's outputs trustworthy; a messy one is a source of errors that are very hard to trace back.",{},true,1.7,"\u002Fblog\u002Ftreasury-data-model","treasury-systems-architecture","treasury data model","annual","reviewed","Tan Gravam","informational",{"title":5,"description":339},"blog\u002Ftreasury-data-model",[366,337,367,368,369],"treasury","data-model","master-data","reference-data","text","_7ld8JUD4-ekgsM4jdV8MBgPOXczASDHkYfMivTJsso",[373,377],{"title":374,"path":375,"stem":376,"type":370,"language":342,"draft":340,"children":-1},"Treasury Bank Connectivity: SWIFT vs Host-to-Host vs API vs EBICS","\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics","blog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics",{"title":378,"path":34,"stem":379,"type":370,"language":342,"draft":340,"children":-1},"Treasury Data Quality and Governance","blog\u002Ftreasury-data-quality-and-governance",[381,384,387],{"path":39,"title":382,"description":383},"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.",{"path":257,"title":385,"description":386},"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?'",{"path":174,"title":388,"description":389},"Treasury Master Data Management","Treasury master data is the static reference data everything depends on — banks, counterparties, instruments, settlement instructions — and ownership is key.",1785182343111]