> ## 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.

# Reporter trial-balance classification contract

> Trial-balance reporting must join classifications through the operation routeCode resolved from accountingEntries, not the deprecated external code field.

<Badge stroke icon="calendar-days" iconType="regular">August 17, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## Affects

***

Teams that build trial-balance reports from Midaz operations and Reporter templates.

## What changed

***

`OperationRoute.code` is deprecated external compatibility data. Midaz does not assign it regulatory meaning or write it to operations. For new accounting classifications, define rubric codes in `accountingEntries` and join report data through the resolved `routeCode` on each operation. The guide does not certify COSIF or BACEN submissions.

This is a documentation correction that aligns the reporting guide with the implemented data contract. Runtime behavior did not change.

## Impact

***

**Classification: Action required.** Reports or mappings that use `OperationRoute.code` as their classification source must move to `routeCode` and validate their regulatory mapping independently.

## What you need to do

***

Review trial-balance templates and data joins. Use the rubric codes in `accountingEntries` for new classifications and `routeCode` from each operation when joining report data. Keep regulatory mapping approval in the controls that own it.

## Resources

***

* [Prepare trial-balance reporting](/en/products/reporter/creating-trial-balance-report)