Where the customer data comes from
Lerian CCS keeps no copy of your customer base. Lerian Reporter renders the daily ACCS001 file from your customer data against a registered template. Lerian CCS reads the rendered bytes and creates one batch line item per operation in the file. The Reporter is a mandatory upstream. Lerian CCS refuses to start without the Reporter address, and an unreachable Reporter takes Lerian CCS out of the ready state. With neither the ACCS001 template identifier nor its name set, the approval fails with
MYS-0008.
Reporting (ACCS001)
A batch belongs to one movement date. One rule answers which movement date the institution may transmit now, and whether a supplied date is acceptable. A date outside the rule fails with
CCS-0012.
The batch then walks a state machine:
Every state from
ACCEPTED down is terminal. Approve and reject are the operator decisions on a batch under review. A generate request can also approve the batch at once, with a written reason. Approve dispatches the render and parks the batch, so no synchronous path reaches the hand-off. A render that gives up ends in RENDER_FAILED, and recovery is a fresh batch.
BACEN answers on the inbound file channel. An ACCS002 carries the file-level verdict. An ACCS003 carries one verdict per record, and Lerian CCS matches each verdict to its line item by the regulatory tuple. A verdict that matches no line item fails closed rather than dropping in silence. An accepted record promotes its relationship into the accepted position. A refused record leaves an error row your operators can read.
After FORMAT_REJECTED or PARTIALLY_REJECTED, an operator can create a resend batch from that batch.
A background monitor asks, per configuration and movement date, whether BACEN acknowledged a remittance dated on that date. It answers PRESENT, MISSING or UNDETERMINED. The obligation holds even with no movement, so MISSING is a regulatory omission. UNDETERMINED says the control could not answer.
Pending requisitions and penalty reports (CCS0009 and ACCS009)
An operator can ask BACEN which requisitions the institution has not answered (CCS0009). Lerian CCS lists each gap that BACEN reports. BACEN sends penalty reports as ACCS009. That document is a columnar text report with no XML layout. Lerian CCS parses it and stores the occurrence.
Transfers (ACCS010 and CCS0010)
An operator records an outbound transfer as a draft, with the receiving institution’s CNPJ root and the legs it covers. Your operators list transfers newest first, up to 200 per page, and read any transfer with its legs. Another institution can also transfer relationships to yours. Lerian CCS reads the sender’s ACCS010 copy and records the transfer as
RECEIVED. An operator confirms it, and Lerian CCS sends a CCS0010. BACEN’s answer moves the transfer to ACKNOWLEDGED or REFUSED.
Compliance and injunctions (ACCS004)
BACEN publishes the position it holds for the institution as an ACCS004. Lerian CCS parses that report and runs a reconciliation against the accepted position it keeps. Only one run per configuration may be in progress. A run ends as
COMPLETED with its match and divergence counts, or as FAILED with a diagnostic. Your operators list the divergences of a run, with each document masked to its last four characters.
The comparison keys on a keyed hash of the document. A divergence row keeps the document encrypted.
An injunction records a judicial BLOCK or UNBLOCK against one document for one configuration, under LC 105/2001. A block holds that identity out of the remittance. An operator can revoke an active injunction, and the revocation is soft.
Audit trail and events
Every state change writes an entry to an append-only audit log, inside the same transaction as the change itself. Each entry carries the SHA-256 of the previous entry combined with the canonical form of the record, so the entries form one chain per institution. An operator can ask the service to verify a chain end to end. Lerian CCS also publishes a business event when the ACCS001 batch goes to Lerian STA. It writes the event through a transactional outbox, so the event and the state change it reports commit together. Event publication over the streaming topic stays off until an operator turns it on.