Skip to main content
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 three areas of that obligation:
  • Reporting (ACCS001). Lerian Reporter renders your daily remittance file, and Lerian CCS submits it to BACEN through Lerian STA.
  • Compliance (ACCS004). Lerian CCS reconciles the position BACEN reports against the accepted position it holds, and records judicial block and unblock orders.
  • Transfers (ACCS010 and CCS0010). Lerian CCS records a transfer that another institution sends, and confirms it. It also records an outbound transfer as a draft.
All BACEN XML passes through one codec. Files carry the CCSDOC, BCARQ and SISARQ envelopes, and messages carry the BCMSG and SISMSG envelopes. The codec uses UTF-16BE with a byte-order mark. The regulatory XML stays in object storage, and the API and the broker messages carry file references only. Lerian CCS isolates each institution in its own database schema.

​
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.
  • Records the transfers other institutions send, and confirms them.
  • Writes every state change to an append-only audit log.
Lerian CCS does not:
  • Connect to BACEN directly. 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.
  • 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 it cannot confirm that the remittance arrived. One deployment can serve several institutions. Each keeps its own schema, configuration, and conglomerate members.

​
Glossary

See also Native messaging and partner interfaces.