Rule · BCB · 8 Dec 2006 · Carta Circular 3254
Firms preparing files for Circular 3,290 must use fixed-length ASCII .txt records without headers. Alphanumeric fields require space padding, while numeric fields must use leading zeros. Debits or credits with multiple values must be broken into separate lines, each showing full sender or recipient identification.
Divulga leiaute das informações de que trata a Circular 3.290, de 2005.
In accordance with the provisions of the sole paragraph of Article 5 of Circular 3,290 of September 5, 2005, we disclose the layout to be adopted for providing the information provided therein:
Seq Field Type Size Decimals DESCRIPTION OBSERVATIONS ===================================================================== 1 Client Name A 30 No accents of the client or cedilla.
--------------------------------------------------------------------- 2 Type A 1 Type of payer or receiver:
Individual
(1) or Legal
Entity (2)
--------------------------------------------------------------------- 3 Client's CPF/CNPJ A 14 Client's CPF of the client or CNPJ. CNPJ or CPF with period, hyphen or slash, aligned to the right.
--------------------------------------------------------------------- 4 Sisbacen Code A 5 Sisbacen Code Sisbacen of the institution depending on the client. Code with check digits, if period, slash or dependent.
--------------------------------------------------------------------- 5 Branch (if A 10 Branch Code the case) Code of the branch holding the account, when dealing with a client. Code without hyphen and without check digit, aligned to the right.
--------------------------------------------------------------------- 6 Account (if A 20 Account Number the case) Number of the account when dealing with a client. Full account number with check digit, without periods or hyphens, aligned to the right.
--------------------------------------------------------------------- 7 Date D 8 Date of transaction of funds. DDMMYYYY.
--------------------------------------------------------------------- 8 D/C A 1 Inform if the event is a debit (payment) or credit (receipt). D = Payment (Debit) C = Receipt (Credit)
--------------------------------------------------------------------- 9 History A 30 Description of the debit or credit.
--------------------------------------------------------------------- 10 Document (if A 10 Document Number the case) Number of the debit or credit.
--------------------------------------------------------------------- 11 Amount N 15 2 Amount of debit or credit. Two decimal places included in the field size, without period or comma, aligned to the right.
--------------------------------------------------------------------- 12 Payer's Name A 30 Name of the or Payee recipient or receiver of funds (in the case of debit), or of the depositor or sender of funds (in the case of credit). No accents or cedilla.
--------------------------------------------------------------------- 13 Type A 1 Type of payer or receiver:
Individual
(1), Legal
Entity (2) or Non- resident (3)
--------------------------------------------------------------------- 14 Payer's/Receiver's CPF/CNPJ/ A 14 Payer's/Receiver's Passport Number CPF, CNPJ or passport number of the recipient or receiver of funds (in the case of debit), or of the depositor or sender of funds (in the case of credit). CNPJ or CPF without period, hyphen or slash, aligned to the right.
--------------------------------------------------------------------- 15 Sisbacen Code A 5 Sisbacen Code Sisbacen of the recipient institution or receiver of funds (in the case of debit), or of the depositor or sender of funds (in the case of credit). Code with check digits, without period, slash or dependent.
--------------------------------------------------------------------- 16 Institution's A 10 Institution's Branch Branch Code of the destination or receiver of funds. Code without hyphen and without check digit, aligned to the right.
--------------------------------------------------------------------- 17 Institution's A 20 Institution's Account Account Number of the relationship account. Full account number with check digit, without periods or hyphens, aligned to the right.
The files must be prepared in text format (.txt extension), with fixed-length records, ASCII standard, for use in PC-type microcomputers, generated without headers and without fillers, and numeric fields must be in external decimal format ("display", "unpacked" or "zoned"). In the case of missing information, fill alphanumeric (A) fields with spaces and numeric (N) fields with leading zeros.
If a debit and/or credit consists of two or more values (for example, a deposit consisting of several checks and/or part in cash, or an authorized debit for the issuance of administrative checks or DOCs), the entry must be broken down into as many lines as there are installments, with the complete identification of the depositor/sender or recipient/receiver appearing on each line.
BRASÍLIA, December 8, 2006.
Department of Combat against Financial Illicit Activities and Supervision of Foreign Exchange and International Capital Markets
Ricardo Lião
Chief
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
A newer document in RegAlert replaces this one.
“Circular Letter No. 3,254 of December 8, 2006 is revoked.”
“In accordance with the provisions of the sole paragraph of Article 5 of Circular 3,290 of September 5, 2005, we disclose the layout to be adopted for providing the information provided therein:”
“electronic files maintained by financial institutions shall be forwarded to the Central Bank of Brazil, when requested, according to the layout published in Circular Letter 3,254 of December 8, 2006”
Amended 1 time · last 2010-06-14
More like this from BCB
BCB published 8 documents in the last 30 days. We email you each new one the day it's published.
Source: Banco Central do Brasil — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated