OperationRoute.code as an unconstrained legacy string. It does not make that field a 10-digit COSIF account code.
The source also does not establish that available_balance_after—including a value grouped by account and route—is a supported regulatory balance. Do not use the previous examples as a basis for a CADOC submission.
What to do instead
- Obtain the applicable official CADOC layout and validation rules.
- Define the mapping from your institution’s source data to that layout.
- Validate field semantics, aggregation, dates, and identifiers with your compliance team.
- Test the generated file against the authoritative validator before operational use.

