Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document treasury accounting journals and close support while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
IFRS 9
IFRS 9 addresses classification and measurement, impairment, and hedge accounting for financial instruments. Treasury systems may support instrument records, valuations, designations, effectiveness, journals, and disclosures, while accounting policy and judgments remain accountable decisions.
ASC 815
ASC 815 contains U.S. GAAP requirements for derivatives and hedge accounting. Treasury systems supporting U.S. GAAP must preserve instrument terms, designation, risk, method, assessment, measurement, journals, and disclosure evidence.
PCAOB AS 2201
AS 2201 establishes requirements for audits of internal control over financial reporting integrated with financial-statement audits. Treasury-system changes can affect significant accounts, risks, controls, evidence, interfaces, reports, and change management within an ICFR assessment.
2021 ISDA Definitions
The 2021 ISDA Definitions provide standardized terms for interest-rate derivatives documentation. Treasury platforms handling interest-rate derivatives should preserve product terms, calendars, rates, fallbacks, calculations, events, confirmations, valuations, and lifecycle changes.
Operating domains
Treasury accounting, reconciliation, and close
The evidence chain connecting bank events, treasury deals, valuations, accruals, settlements, classifications, journals, reconciliations, approvals, disclosures, and general-ledger close.
Intercompany liquidity and in-house banking
The operating structure for centralizing cash, payments, receivables, funding, FX, netting, and internal account relationships across legal entities while preserving legal, tax, accounting, and control boundaries.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should treasury accounting journals and close support produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?