RTGS XML is a settlement boundary

What the public implementation shows

The control plane includes RTGSHelpers alongside NSI models, file services, settlement downloads, and net settlement outputs.

RTGS generation converts a controlled net position into the downstream settlement representation expected by the formal rail. This is the implementation fact behind the note; the architectural reading begins from that visible boundary rather than from an assumed production story.

Operating principleThe final file format is only the last step in a governed settlement transformation.

The decision behind the mechanism

Keeping mapping helpers and artifact services explicit makes the transformation reviewable independently from transaction ingestion.

A correct net total can still become a wrong settlement instruction when debtor, creditor, amount, account, or date fields are mapped incorrectly. The mechanism matters because it gives that failure a named boundary, durable evidence, and a controlled response instead of leaving the outcome to timing or operator guesswork.

• Generate only from an approved net settlement state.
• Validate participant and account identifiers.
• Reconcile XML totals back to NSI totals.
• Store and control the generated artifact.

How the control should be operated

Generation should validate totals, participant identifiers, scheme dates, schema constraints, and artifact identity before controlled release.

The handoff from instant-payment activity to final settlement remains auditable. The reusable lesson is not to copy a class or endpoint in isolation, but to preserve the relationship between identity, state, authority, evidence, and operational ownership.