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

# What is Lerian CCS?

> Lerian CCS is your integration to the BACEN CCS register, from the daily remittance to position reconciliation and judicial injunctions.

**Lerian CCS** is the Lerian service for the **BACEN CCS** regulatory integration. CCS is the *Cadastro de Clientes do Sistema Financeiro Nacional*, the BACEN customer register of the National Financial System.

Lerian CCS covers four areas of that obligation:

* **Reporting (ACCS001).** Lerian Reporter renders your daily remittance file, and Lerian CCS submits it to BACEN through [Lerian STA](/en/rails/native/sta/what-is-lerian-sta).
* **Compliance (ACCS004).** Lerian CCS reconciles the position BACEN reports against the accepted position it holds, and records judicial block and unblock orders.
* **Detail requests (CCS0001 and CCS0003).** Lerian CCS records each BACEN request with its regulatory deadline and lists it for your operators.
* **Transfers (ACCS010 to ACCS012).** Lerian CCS records a relationship transfer to another institution and keeps its lifecycle state.

All BACEN XML passes through one codec. It carries the CCSDOC, BCARQ and SISARQ envelopes, UTF-16BE with a byte-order mark, and the official BACEN XSDs. The regulatory XML stays in object storage, and only file references travel over the wire.

Lerian CCS isolates each institution in its own database schema. The tenant identity comes from the validated access token, never from a request payload or a path parameter.

## What Lerian CCS does and does not do

***

**Lerian CCS does:**

* Builds the daily ACCS001 batch and submits it through Lerian STA.
* Records judicial injunctions as blocks and unblocks, and lets an operator revoke one.
* Receives, records, lists and cancels detail requests.
* Records relationship transfers and their lifecycle state.
* Writes every state change to an append-only audit log.

**Lerian CCS does not:**

* **Connect to BACEN directly.** [Lerian STA](/en/rails/native/sta/what-is-lerian-sta) owns the BACEN leg. Lerian CCS submits each file to Lerian STA over HTTP, and BACEN's answers return over the message broker.
* **Render the ACCS001 file.** Lerian Reporter renders it from your customer data, and Lerian CCS then builds the batch line items from the rendered bytes. The Reporter is a mandatory upstream.
* **Receive detail requests over HTTP.** Each request reaches Lerian CCS on the inbound file channel that Lerian STA feeds.
* **Apply its own database schema.** A separate migration job applies the schema before the service starts.

## Who it serves

***

Lerian CCS serves financial institutions that carry the daily CCS reporting obligation. That obligation stands even on a day with no movement, so a missing remittance is a regulatory omission. Lerian CCS grades that question per configuration and movement date, and raises a signal when the remittance never arrived.

One deployment can serve several institutions. Each keeps its own schema, configuration, and conglomerate members.

## Glossary

***

| Term                          | Meaning                                                                                                 |
| ----------------------------- | ------------------------------------------------------------------------------------------------------- |
| **CCS**                       | *Cadastro de Clientes do Sistema Financeiro Nacional*, the BACEN register of customer relationships.    |
| **Lerian STA**                | Lerian's integration to BACEN's file-exchange hub. It carries every CCS file both ways.                 |
| **Configuration**             | The per-institution settings a batch, a reconciliation, and an injunction belong to.                    |
| **Conglomerate member**       | A participant institution registered under one configuration.                                           |
| **Movement date**             | The date the ACCS001 file itself carries. One rule decides which date the institution may transmit now. |
| **Accepted position**         | The local mirror of the relationships BACEN has accepted.                                               |
| **ACCS001**                   | The daily remittance the institution sends to BACEN.                                                    |
| **ACCS002 and ACCS003**       | BACEN's file-level verdict and per-record verdicts on an ACCS001.                                       |
| **ACCS004**                   | The position report BACEN publishes for reconciliation.                                                 |
| **ACCS009**                   | The BACEN penalty report, a columnar text file with no XML layout.                                      |
| **ACCS010, ACCS011, ACCS012** | The relationship-transfer message family.                                                               |
| **CCS0001 and CCS0003**       | The BACEN detail requests, by person and by account.                                                    |
| **CCSDOC, BCARQ, SISARQ**     | The BACEN envelope elements that every CCS document carries.                                            |
| **Injunction (*liminar*)**    | A judicial block or unblock recorded against one CPF or CNPJ under LC 105/2001.                         |
| **LC 105/2001**               | The Brazilian bank-secrecy law that governs what an institution may disclose.                           |

See also [Native messaging and partner interfaces](/en/rails/native/native-messaging).