CTR-TREASURY · version 1

Treasury and Cash Management — Cash positions

The registry reports this feed at 71 minutes against a 60-minute commitment, so it is already outside its promise before it is even live.

In reviewNever checked

What the contract says

These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.

Entity

Cash position · bidirectional

Primary key

accountId + valueDate

Declared volume

3,200 records a day

Freshness commitment

1 h

Owner

L. Duarte · Treasury Operations

Vendor

Kyriba · critical criticality · modeled

Cardinality

One account to one position per value date. A restated position replaces rather than appends, which makes replay behavior specific and the contract spells it out.

Write-back rule

None in this version. A cash movement initiated by an agent is out of scope until the bank gateway contract exists, and that contract is blocked.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewApproved

D. Contreras · Jul 2, 2026

Privacy reviewApproved

Maitre Olivier Lascaux · Jul 22, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

Review is open. No sample has been taken because the treasury sandbox has no representative balances in it.

The field list

4 fields · 2 key · 0 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.

Field	Source	Target	Type	Flags	Drift	Validation
Account id	account.id	cashPosition.accountRef	string(24)	keyinternal	Never checked	Must resolve to a bank account in the register.
Value date	position.valueDate	cashPosition.valueDate	date	keyinternal	Never checked	A restatement for an existing value date replaces the prior row and writes a replay record.
Closing balance	position.closing	cashPosition.closing	decimal(18,2)	internal	Never checked	Signed. Currency mandatory.
Currency	position.ccy	cashPosition.currency	string(3)	internal	Never checked	ISO 4217.

What has passed the staging boundary against this contract

1 batch · 1,260 arrived · 1,196 admitted · 64 quarantined · 0 rejected

Staging boundary

Batch	Arrived	In	Admitted	Quarantined	Rejected	Result	Gate
STG-0023	Aug 18, 07:00	1,260	1,196	64	0	Partly admitted	1,196 admitted · 64 quarantined · 0 rejected outright.

Rejects raised against these batches

1 reason covering 64 records. Each one names a field, what was observed and what the contract expected.

Bank account not present in the account register64 records · 2 h oldOwner assigned

Observed: 9 accounts opened at the source this month

Expected: An account in the register

STG-0023 · field bankAccountRef · queue quarantine · L. Duarte

Replay windows

1 window recorded against this contract.

Replay register

RPL-010Completed

Late arriving · Aug 11, 2026 to Aug 12, 2026

A value date restatement arrived from one banking partner after the position had been struck.

1,240 replayed · 1,198 held at the idempotence key · 0 duplicates created

Write-back routes into this system

1 route designed against Treasury and Cash Management.

Write-back register

confirm-value-date · Cash positionDesigned, never live

WB-TREASURY-01 · agent · authority FI6-AUTH-A1 · policy FI6-POL-200

2 attempted · 0 written to a production system

What goes stale when this feed does

2 asserted figures depend on Treasury and Cash Management. The rule on each row is what the surface does when the feed misses its commitment.

Freshness

Figure	Where it is shown	Role	On stale	Note
Reconciliation breaks open	Reconciliation ledger	contributing	Mark it stale	Cash-side balances feed three of the eight ledgers.
Group cash position	Finance cockpit	primary	Suppress the figure	Treasury is the position of record. It is currently outside its own freshness commitment.

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.

This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.