Interactive tool

Treasury System-of-Record Map

The cleanest treasury architectures follow one rule: every data domain has exactly one system of record, and everything else is a consumer. Map yours here — name the owner, the consumers and the flow for each domain. It's the tool behind the system-of-record guide and the reference architecture.

Data domain	System of record	Consumers	Integration

Markdown table

# Treasury system-of-record map

Rule: each data domain has exactly one system of record. Everything else is a consumer or a copy.

| Domain | System of record | Consumers | Integration |
| --- | --- | --- | --- |
| Cash position & balances | TMS / S4HANA Cash Mgmt | Treasury, reporting | Real-time / intraday |
| Bank statements (raw) | Bank → ERP (EBS) | AR/AP, cash mgmt | Daily import |
| Outgoing payments | ERP / payment hub | Banks, treasury | Batch + approval |
| FX & derivatives deals | TMS | GL, risk, reporting | On deal capture |
| Debt & investments | TMS | GL, reporting | On deal capture |
| Bank & account master | Bank Account Mgmt | All systems | On change |
| Cash forecast | TMS / planning | Treasury, FP&A | Daily / weekly |
| Accounting entries (GL) | ERP / General Ledger | Close, reporting | On posting |

The seeded rows are a common starting point, not a prescription — rename, re-own and extend them for your landscape. The value isn't the table; it's the argument it forces: for each domain, who owns the truth? Nothing you type here leaves your browser.