> ## 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 CCS encoding and data-source contract

> Reporter CCS templates require UTF-16BE output, and multi-tenant data sources use the Reporter API.

<Badge stroke icon="calendar-days" iconType="regular">August 26, 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 author Reporter CCS templates or manage self-hosted Reporter data sources.

## What changed

***

ACCS001, ACCS005, and ACCS010 templates require the `{# reporter:output-encoding=utf-16be #}` directive. Reporter converts this output to UTF-16BE with a BOM.

Single-tenant self-hosted deployments can seed data sources with `DATASOURCE_<NAME>_*` variables. Multi-tenant deployments create and manage each tenant's data sources through the Reporter API. These are documentation corrections; no runtime release is announced.

## Impact

***

**Classification: Action required.** Templates using the previous UTF-8 declaration can produce files that do not meet the documented CCS output contract.

## What you need to do

***

<Steps>
  <Step>Add the UTF-16BE output directive to every ACCS001, ACCS005, and ACCS010 template.</Step>
  <Step>Validate generated files with the consumer that receives your CCS submission.</Step>
  <Step>Use the Reporter API, not startup seeding variables, to manage data sources in multi-tenant deployments.</Step>
</Steps>

### Deadline

Update and validate templates before the next CCS submission.

## Resources

***

* [CCS reports](/en/products/reporter/ccs-reports)
* [Connect Reporter to Midaz](/en/products/reporter/connecting-reporter-to-midaz)