What Lerian SISBAJUD does and does not do
- It receives orders as files. A remittance file reaches the Mensageria as a Lerian STA event. The Mensageria has no HTTP operation that accepts an order, and it does not poll for files. Plugin SISBAJUD accepts orders over HTTP only on the direct channel.
- It separates the regulatory side from the ledger side. The Mensageria keeps the files and the order record. Plugin SISBAJUD makes the ledger writes.
- It does not start work when a deadline time arrives. Response files are generated at configured intervals. Set those intervals so that each cycle ends inside the BACEN response window.
Who it serves
Lerian SISBAJUD serves banks and financial institutions that must honour judicial asset orders under the CNJ/BACEN SISBAJUD regime. One Mensageria serves many institutions. It reads the CNPJ root from the header of each file and matches it to an institution registered on the Mensageria. Each institution has its own orders and files.
Glossary
For how Lerian SISBAJUD sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces.

