> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# CADOC 4010 and 4016: validation required

> Use authoritative regulatory requirements to validate any CADOC 4010 or 4016 mapping before operational use.

The previous ready-to-submit template guidance on this page has been withdrawn.

Reporter can render templates from configured data sources, but the current product source does not establish a CADOC regulatory mapping. In particular, Midaz treats `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 `available_balance_after` (including a value grouped by account and route) as a supported regulatory balance. Do not use the previous examples as a basis for a CADOC submission.

## What to do instead

***

1. Obtain the applicable official CADOC layout and validation rules.
2. Define the mapping from your institution's source data to that layout.
3. Validate field semantics, aggregation, dates, and identifiers with your compliance team.
4. Test the generated file against the authoritative validator before operational use.

Reporter generates the output you define. It does not validate a regulatory data model or certify a submission.