BRAZIL XML V3 STP Guide V94-Tax_and_Utilities
BRAZIL XML V3 STP Guide V94-Tax_and_Utilities
Welcome to the STP Guide for the XML pain.001.001.03 file format. This guide has been customized to provide information related to the specific
countries and transaction types your company has requested.
Bank of America provides electronic data interchange services to clients as a means of effecting payments and collecting funds via direct debit. Clients
have the opportunity to realise the benefits of STRAIGHT THROUGH PROCESSING (STP), by applying both standard and Bank of America defined
formats and keywords.
STP has been developed at Bank of America as a result of significant systems investment over many years. The formats are almost entirely based upon
industry-accepted formats. However, a few keywords have been especially designated by Bank of America to enable clients to effectively communicate
their funds transfer routing requirements. Our Client’s adherence to the use of these keywords ensures the maximum opportunity to realise the benefits
of STP whilst accessing a wide range of clearing systems and diverse funds transfer and collection services available through Bank of America.
This document is organized in the following manner. The format may vary slightly depending upon the selected country(s).
Introductory Section:
* Permitted and Non-Permitted Characters
* Definition of Character Set Codes Used in this Document
* Regulatory Requirements
* Regional Support Contacts
Format Quick Reference - a guide to the overall layout of the XML.pain.001.001.03 file format Glossary
The permitted character set is a subset of the level A character set, as specified in ISO 9735.To ensure successful processing of your messages, use
only the following characters:
Digits: 0-9
Letters: A-Z (Upper Case ASCII)
Blank space (Should not be the first character of a line or field)
Special characters:
Comma ,
Hyphen - (Should not be the first character of a line or field.)
Parenthesis, left ( (Should not be the first character of a line or field. Should not be used in Post Code fields)
Parenthesis, right ) (Should not be the first character of a line or field. Should not be used in Post Code fields)
Period .
Slash, forward /
End of line: Carriage return, Line Feed sequence (2 characters)
Reserved characters:
Internally, our systems will convert your origination file to other file formats. As such, the following characters that must not appear in the content/value
of the origination file from client, as they will cause processing failure:
Asterisk (*), Plus Sign (+), Colon (:), Apostrophe (‘), and Tilde (~)
No other symbols or punctuation marks may be used unless specifically designated for a particular message. A colon is used only as a field label
delimiter.
Additionally, do not use any of the following character strings (note colons in the left-hand column)
AMI: QTA
LLLL: VVVV (two "Vs" as in "Victory")
MAC: YZYZ
MMMM: ZCZC
NNNN: String of periods
Transaction references should NOT include double slash "//". Other fields may include a double slash.
Characters involving an accent - i.e. an umault, acute, grave, cedilla tilda etc. should not be used since these characters are not acceptable to the SWIFT
system. Even if the bank’s EDI formats can support such characters, a payment with these accented characters will fail and cause SWIFT rejects.
• The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form, except when used as markup
delimiters, or within a comment, a processing instruction, or a CDATA section.
• If these characters are needed elsewhere, they MUST be escaped using either numeric character references or the strings
"&" and "<" respectively. The right angle bracket (>) may be represented using the string ">", and MUST, for compatibility,
be escaped using either ">" or a character reference when it appears in the string "]]>" in content, when that string is not marking
the end of a CDATA section.
a. CDATA sections may occur anywhere character data may occur; they are used to identify escape blocks of text containing characters which
would otherwise be recognized as markup. CDATA sections begin with the string "<![CDATA[" and end with the string "]]>":]
b. Within a CDATA section, only the CDEnd string is recognized as markup, so that left angle brackets and ampersands may occur in their literal
form; they need not (and cannot) be escaped using "<" and "&". CDATA sections cannot nest.
The following are the conventions used in this document to define the format for each field.
AN Alphanumeric, a sequence of any printable characters. Significant characters should be left justified. Leading and trailing
spaces are not allowed.
DT Date, in YYMMDD or CCYYMMDD format. CC is century.
ID Code values taken from a predefined list
N Numeric data (Inclusive of decimal point for amount values).
A Alpha only - numbers not allowed
R Required
C Conditional - conditions depend on the type of payment, refer to STP rules
O Optional - depends on client's business requirements - for example, information to the beneficiary is optional
"…" Use the value specified within the quotes
Example: A field with an format attribute of "AN 5/20" means it can contain data of type alphanumeric with a minimum length of 5 and
a maximum length of 20.
REGULATORY REQUIREMENTS
To comply with regulatory requirements, all Wire Transfers (Domestic high value, Foreign Currency, Cross Border transfers and MultiBank transactions)
must include full and meaningful name and address details for both the ordering party and the receiving (beneficiary) party. Where a shared service
centre is processing transactions on behalf of subsidiary entities, the underlying subsidiary entity's name and address details should be quoted. As a
minimum, please include the following business attributes:
Name 1
Address Line 1
City or Town
Zip or Postcode (where used in mailing addresses)
State Code (for Addresses in US and Canada)
Country Code
Failure to comply with these regulatory requirements can result in delays or the payment being blocked or returned.
Bank of America offers file-based and SWIFT FIN MT101 payment capabilities in Brazil through its branch in Sao Paulo.
File-based payments:
Clients initiating payments by file transmit their payment instructions to Bank of America, and we forward the instructions on to our branch in Sao Paulo.
Both Previous Day and Current Day reporting is available for all accounts held with our Brazil branch through Bank of America Information Reporting.
Clients who are members of the SWIFT SCORE program and maintain with Bank of America Brazil may transmit their MT101s directly Bank of America
Brazil using SWIFT Code MLBOBRSX, or to another Bank of America SWIFT BIC code if a “Single BIC” program is arranged. Clients can receive
SWIFT MT940 and MT942 messages from BofAML Brazil for Previous and Current Day Reporting, respectively.
The following Brazilian payment types are offered through Bank of America Brazil
Brazil (GBS)
Processing Country Notes
For Brazil (unit 1306), the Originator account MUST be provided as 12 digits starting 1306.
Branch Transaction Types Supported via XML Pain 001.001.03 (Credit Transfer CTv3)
Transaction Transfer Transaction Description
Type
Please refer to separate Cutoff Times document for value date rules.
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Receiving Bank Country Code R PmtInf/CdtT Ctry 2 2 A BR
rfTxInf/Cdtr
Agt/FinInst
nId/PstlAdr
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail Document Number - R PmtInf PmtInfId 1 30 AN
Not Argentina
Extra Payment Detail CONVENIO R PmtInf/Dbtr/ ../SchmeNm/Pr Othr/Id 1 20 N Bank Service Contract Code
Id/OrgId try == (Convenio Agreement)
"CONVENIO"
Extra Payment Detail Enrollment Number R PmtInf/CdtT ../SchmeNm/Pr Othr/Id 11 14 N fill CPF if the Beneficiary is a
rfTxInf/Cdtr/ try == Taxpayer (11 numeric) fill CGC
Id/OrgId "EMBARGO" or CNPJ if the Beneficiary is a
Corporate Taxpayer (14 Numeric)
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Receiving Bank LongSortCode R PmtInf/CdtT MmbId 8 12 N ISPB/COMPE BankCode and
rfTxInf/Cdtr BranchCode
Agt/FinInst
nId/ClrSys
MmbId
Receiving Bank SortCode Qualifier R PmtInf/CdtT ClrSysId/Cd 5 5 AN OPTIONAL - Country specific
rfTxInf/Cdtr code or XXXXX
Agt/FinInst
nId/ClrSys
MmbId
Receiving Bank Country Code R PmtInf/CdtT Ctry 2 2 A BR
rfTxInf/Cdtr
Agt/FinInst
nId/PstlAdr
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail CONVENIO R PmtInf/Dbtr/ ../SchmeNm/Pr Othr/Id 1 20 N Bank Service Contract Code
Id/OrgId try == (Convenio Agreement)
"CONVENIO"
Extra Payment Detail Enrollment Number R PmtInf/CdtT ../SchmeNm/Pr Othr/Id 11 14 N fill CPF if the Beneficiary is a
rfTxInf/Cdtr/ try == Taxpayer (11 numeric) fill CGC
Id/OrgId "EMBARGO" or CNPJ if the Beneficiary is a
Corporate Taxpayer (14
Numeric)
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Receiving Bank LongSortCode R PmtInf/CdtT MmbId 8 12 N ISPB/COMPE BankCode and
rfTxInf/Cdtr BranchCode
Agt/FinInst
nId/ClrSys
MmbId
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail Document Number - R PmtInf PmtInfId 1 30 AN
Not Argentina
Extra Payment Detail CONVENIO R PmtInf/Dbtr/ ../SchmeNm/Pr Othr/Id 1 20 N Bank Service Contract Code
Id/OrgId try == (Convenio Agreement)
"CONVENIO"
Extra Payment Detail Enrollment Number R PmtInf/CdtT ../SchmeNm/Pr Othr/Id 11 14 N fill CPF if the Beneficiary is a
rfTxInf/Cdtr/ try == Taxpayer (11 numeric) fill CGC
Id/OrgId "EMBARGO" or CNPJ if the Beneficiary is a
Corporate Taxpayer (14
Numeric)
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Debtor Tax Id R PmtInf/Dbtr/ ../SchmeNm/C OthrId/Id 11 14 N Fill CPF if the Debtor (Drawee)
Id/OrgId d == TXID is a Taxpayer (11 numeric) fill
CGC or CNPJ if the Debtor
(Drawee) is a Corporate
Taxpayer (14 Numeric)
Receiving Bank Country Code R PmtInf/CdtT Ctry 2 2 A BR
rfTxInf/Cdtr
Agt/FinInst
nId/PstlAdr
Ultimate Debtor Tax Id C PmtInf/CdtT ../SchmeNm/C OthrId/Id 11 14 N When different to Debtor (Payer),
rfTxInf/Ultm d == TXID fill CPF if the Ultimate Debtor
tDbtr/Id/Or (Drawee) is a Taxpayer (11
gId else numeric) fill CGC or CNPJ if the
PrvtId Ultimate Debtor (Drawee) is a
Corporate Taxpayer (14
Numeric)
Extra Payment Detail Original Amount R PmtInf/CdtT RfrdDocAmt/D 1 15 N
(Boleto) rfTxInf/RmtI uePyblAmt
nf/Strd
Extra Payment Detail Due Date (Boleto) R PmtInf ReqdExctnDt 8 8 N
Extra Payment Detail CONVENIO R PmtInf/Dbtr/ ../SchmeNm/Pr Othr/Id 1 20 N Bank Service Contract Code
Id/OrgId try == (Convenio Agreement)
"CONVENIO"
Extra Payment Detail Commitment ID R PmtInf/CdtT EndToEndId 1 30 AN
rfTxInf/PmtId
Extra Payment Detail Document Number R PmtInf/CdtT Prefix with 44 44 N Bar code from Boleto
Text rfTxInf/Instr /BRTL/
ForDbtrAgt
Purpose Attribute Necessity Segment Qualifier Element Min Max Charset Content Notes
Payment Type (TRF or XML Code Value R PmtMtd 3 3 AN TRF
CHK)
Payment Method Code Code List R PmtInf/CdtT SvcLvl/Cd or 4 4 AN <SvcLvl/Cd> = URGP
rfTxInf/Pmt ChqTp
TpInf or
../ChqInstr
Secondary Payment Code List R PmtInf/CdtT Purp/Prtry or 3 4 AN <Prtry> = T11
Method Code rfTxInf Purp/Cd
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Debtor Tax Id R PmtInf/Dbtr/ ../SchmeNm/C OthrId/Id 11 14 N Fill CPF if the Debtor (Drawee)
Id/OrgId d == TXID is a Taxpayer (11 numeric) fill
CGC or CNPJ if the Debtor
(Drawee) is a Corporate
Taxpayer (14 Numeric)
Receiving Bank Country Code R PmtInf/CdtT Ctry 2 2 A BR
rfTxInf/Cdtr
Agt/FinInst
nId/PstlAdr
Extra Payment Detail CONVENIO R PmtInf/Dbtr/ ../SchmeNm/Pr Othr/Id 1 20 N Bank Service Contract Code
Id/OrgId try == (Convenio Agreement)
"CONVENIO"
Extra Payment Detail Document Number R PmtInf/CdtT Prefix with 44 44 N Bar code from Tax & Utility
Text rfTxInf/Instr /BTAX/
ForDbtrAgt
Purpose Attribute Necessity Segment Qualifier Element Min Max Charset Content Notes
Payment Type (TRF or XML Code Value R PmtMtd 3 3 AN TRF
CHK)
Payment Method Code Code List R PmtInf/CdtT SvcLvl/Cd or 4 4 AN <SvcLvl/Cd> = URGP
rfTxInf/Pmt ChqTp
TpInf or
../ChqInstr
Secondary Payment Code List R PmtInf/CdtT Purp/Prtry or 3 4 AN <Prtry> = T16
Method Code rfTxInf Purp/Cd
Transfer Currency ISO Currency Code R PmtInf/CdtT InstdAmt/@Ccy 3 3 A BRL
rfTxInf/Amt
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Debtor Tax Id R PmtInf/Dbtr/ ../SchmeNm/C OthrId/Id 11 14 N Fill CPF if the Debtor (Drawee)
Id/OrgId d == TXID is a Taxpayer (11 numeric) fill
CGC or CNPJ if the Debtor
(Drawee) is a Corporate
Taxpayer (14 Numeric)
Receiving Party Taxpayer Name R PmtInf/CdtT Nm 1 30 AN Bank will truncate to this maximum
rfTxInf/Cdtr
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail Document Number - R PmtInf PmtInfId 1 30 AN
Extra Payment Detail Tax Reference R PmtInf/CdtT Prefix with 1 17 N Tax Reference
rfTxInf/Instr /REFN/
ForCdtrAgt
Extra Payment Detail Revenue Code R PmtInf/CdtT Prefix with 1 6 N Fed. Revenue’s tax Code
rfTxInf/Instr /ENYC/
ForCdtrAgt
Extra Payment Detail Reference Period R PmtInf/CdtT Prefix with 8 8 N Tax Calculation period
rfTxInf/Instr /REFP/
ForCdtrAgt
Extra Payment Detail Due Date R PmtInf/CdtT Prefix with 8 8 N Tax Due Date
rfTxInf/Instr /DDUE/
ForCdtrAgt
Extra Payment Detail Principal Amount R PmtInf/CdtT Prefix with 1 Unlimited N Principal Amount
rfTxInf/Instr /PAMT/
ForCdtrAgt
Extra Payment Detail Penalty Amount R PmtInf/CdtT Prefix with 1 Unlimited N Penalty Amount
rfTxInf/Instr /PENA/
ForCdtrAgt
Extra Payment Detail Fine Amount R PmtInf/CdtT Prefix with 1 Unlimited N Fine Amount
rfTxInf/Instr /FINA/
ForCdtrAgt
Extra Payment Detail Value for interest R PmtInf/CdtT Prefix with 1 Unlimited N Interest Amount
rfTxInf/Instr /INTA/
ForCdtrAgt
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Debtor Tax Id R PmtInf/Dbtr/ ../SchmeNm/C OthrId/Id 11 14 N Fill CPF if the Debtor (Drawee)
Id/OrgId d == TXID is a Taxpayer (11 numeric) fill
CGC or CNPJ if the Debtor
(Drawee) is a Corporate
Taxpayer (14 Numeric)
Receiving Party Taxpayer Name R PmtInf/CdtT Nm 1 30 AN Bank will truncate to this maximum
rfTxInf/Cdtr
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail Tax Reference R PmtInf/CdtT Prefix with 1 17 N Tax Reference
rfTxInf/Instr /REFN/
ForCdtrAgt
Extra Payment Detail Revenue Code R PmtInf/CdtT Prefix with 1 6 N Fed. Revenue’s tax Code
rfTxInf/Instr /ENYC/
ForCdtrAgt
Extra Payment Detail Reference Month R PmtInf/CdtT Prefix with 6 6 N Tax Month & Year
rfTxInf/Instr /REFP/
ForCdtrAgt
Extra Payment Detail INSS Amount R PmtInf/CdtT Prefix with 1 Unlimited N INSS Amount
rfTxInf/Instr /INSS/
ForCdtrAgt
Extra Payment Detail Value for Other R PmtInf/CdtT Prefix with 1 Unlimited N Other Entity Amount
rfTxInf/Instr /OENT/
ForCdtrAgt
Extra Payment Detail Penalty Amount R PmtInf/CdtT Prefix with 1 Unlimited N Penalty Amount
rfTxInf/Instr /PENA/
ForCdtrAgt
Ordering Party Postal Address R PmtInf/Dbtr/ Concatenation 5 110 AN Regulatory requirement - Please
PstlAdr of Elements refer to the Introduction
Debtor Tax Id R PmtInf/Dbtr/ ../SchmeNm/C OthrId/Id 11 14 N Fill CPF if the Debtor (Drawee)
Id/OrgId d == TXID is a Taxpayer (11 numeric) fill
CGC or CNPJ if the Debtor
(Drawee) is a Corporate
Taxpayer (14 Numeric)
Receiving Party Taxpayer Name R PmtInf/CdtT Nm 1 30 AN Bank will truncate to this maximum
rfTxInf/Cdtr
Receiving Party Postal Address R PmtInf/CdtT Concatenation 5 110 AN Regulatory requirement - Please
rfTxInf/Cdtr/ of Elements refer to the Introduction
PstlAdr
Textual Information Data O PmtInf/CdtT Ustrd or Strd 0 140 AN Bank will truncate to this Maximum
rfTxInf/RmtI loop
nf
Extra Payment Detail Tax Reference R PmtInf/CdtT Prefix with 1 17 N Tax Reference
rfTxInf/Instr /REFN/
ForCdtrAgt
Extra Payment Detail Revenue Code R PmtInf/CdtT Prefix with 1 6 N Fed. Revenue’s tax Code
rfTxInf/Instr /ENYC/
ForCdtrAgt
Extra Payment Detail Reference Period R PmtInf/CdtT Prefix with 6 6 N Tax Month & Year
rfTxInf/Instr /REFP/
ForCdtrAgt
Extra Payment Detail Due Date R PmtInf/CdtT Prefix with 8 8 N Tax Due Date
rfTxInf/Instr /DDUE/
ForCdtrAgt
Extra Payment Detail Tax Code R PmtInf/CdtT Prefix with 1 12 N State Enrollment / Municipality Code /
rfTxInf/Instr /TCDE/ Declaration Number
ForCdtrAgt
Extra Payment Detail Label / Debt Number R PmtInf/CdtT Prefix with 1 13 N Label / Debt Number
rfTxInf/Instr /LNUM/
ForCdtrAgt
Extra Payment Detail Installment Number R PmtInf/CdtT Prefix with 1 13 N Installment Number
rfTxInf/Instr /PAMT/
ForCdtrAgt
Extra Payment Detail Revenue Amount R PmtInf/CdtT Prefix with 1 Unlimited N Revenue Amount
rfTxInf/Instr /REVA/
ForCdtrAgt
Extra Payment Detail Value for interest R PmtInf/CdtT Prefix with 1 Unlimited N Interest Amount
rfTxInf/Instr /INTA/
ForCdtrAgt
Extra Payment Detail Fine Amount R PmtInf/CdtT Prefix with 1 Unlimited N Fine Amount
rfTxInf/Instr /FINA/
ForCdtrAgt
Please follow these straight-through processing guidelines when effecting payments from accounts domiciled in any of the countries in this guide to
Brazil:
Transaction Type will be "SWIFT" - see STP rules for this transaction type in the STP formatting rules section appropriate to the country / branch where
the debit account is serviced for generic rules for a SWIFT (cross-border) payment.
Important Note: Payments to Brazil MUST contain the full name and address of the Ordering Party, and MUST contain the address
and phone number of the Receiving Party.
Ver 94 27-Nov-15 Page 26
Bank of America STP Guide
Glossary
CBR Central Bank Reporting (CBR) is an obligation to submit reports of cross-border payment data to the central bank
of a country for statistical reporting. Not all countries require CBR, and the rules for complying with CBR for
those countries that do require it may vary. Consult with your Bank of America Implementation Advisor for more
Country Code A two-letter alpha code that identifies a specific country. Visit www.iso.org and search for "Country Codes" to
obtain the latest complete list.
GBS Branch A four-digit number that identifes a specific branch of Bank of America.
IBAN The International Bank Account Number (IBAN) is an international standard used to identify bank account
numbers in Europe and elsewhere. SWIFT is the official IBAN registrar. The IBAN registry can be found by
visiting www.swift.com and performing a search for "IBAN Registry"
Intermediary Bank A bank through which funds may pass en route to the Receiving Bank as part of the processing of a payment.
ISO Currency Code A three-letter alpha code that represents a specific world currency. Visit www.iso.org and search for "Currency
Codes" to obtain the latest complete list.
Ordering Party The party that is initiating a payment. Typically, this will be your company
Receiving Account The account of the ultimate beneficiary of the funds being paid.
Receiving Bank The bank at which the account of the ultimate beneficiary of the funds is held.
Sort Code A number assigned to a specific bank, or a specific branch of a bank, to allow for automated processing of
electronic payments and collections. They are most commonly used in Australia, Canada, Denmark, Germany,
Ireland, Sweden, and the United Kingdom.
SWIFT BIC A SWIFT Bank Identifier Code (BIC) is a globally-used eight or eleven-character code that identifies a specific
bank. An eight-character BIC is composed of a bank code (four characters), country code (two characters), and a
location code (two characters). An eleven-character BIC has the same composition as the eight-character code,
with the addition of three characters to identify a specific bank branch.