United States dollar (USD) from Belgium to United States of America
Overview
The payment processing of this currency is considered to be highly standardized.
Public holidays in United States of America (*)
- January 1st, 2026
- January 19th, 2026
- February 16th, 2026
- May 25th, 2026
- June 19th, 2026
- July 4th, 2026
- September 7th, 2026
- October 12th, 2026
- November 11th, 2026
- November 26th, 2026
- December 25th, 2026
Weekend in United States of America (*)
- Saturday-Sunday
Additional information
• Available charge option: OUR/SHA/BEN
You can check the ABA code of the beneficiary's bank on the Central Bank site in the USA at the following address: https://www.frbservices.org/resources/routing-number-directory?_gl=1*1adp0i8*_gcl_au*OTg4NjYxNzI5LjE3NDc0MTcwMDk.
• Central bank of the United States of America:
http://www.federalreserve.gov/faqs/about_12594.htm
Please be advised that in some cases the OUR fee option doesn’t work as expected. We remind you that a payment processed with an OUR fee option is a payment where the full amount is supposed to be credited to the beneficiary without deductions. Usually the OUR option is preserved throughout the payment chain and the full amount reaches the beneficiary. However, the US intermediary of the beneficiary banks may convert the OUR charge code to 'SHA' (shared cost system): as a result, fees may be deducted from the principal amount, which means the beneficiary will not receive the original instructed amount.
In case the beneficiary is inside of USA, OUR charge code will not be maintained as the local clearing does not allow OUR, so potentially the principal amount will be impacted.
Guidelines
| Data | Specification | Description | Format | Mandatory / recommended | Example Pain 001 |
|---|---|---|---|---|---|
| Local Clearing System | Fedwire code or BIC SWIFT code | In order to enable the correct routing of the payment in the domestic clearing, either the Fedwire code (also known as ABA code) or BIC code (branch identifier included, if provided) should be used. In certain cases, the Fedwire code could be included within the domestic account number. Please ask your beneficiary to indicate separately this code and the domestic account number. In MT, please note the Fedwire code is required to be in field 57D, and the BIC code is in field 57A. For more information on format requirements in MT and MX, please see Appendix XXXII. |
See Appendix | Mandatory | <CLRSYSMMBID>See Appendix</CLRSYSMMBID> |
| Beneficiary Account Number | Domestic account number | It's important that the domestic account number of the beneficiary complies with the local account format of the destination country. | Local BBAN Format | Mandatory | <CDTRACCT> <ID> <OTHR> <ID>BBAN</ID> </OTHR> </ID> </CDTRACCT> |
| Beneficiary Name | Beneficiary's full legal name | The full legal beneficiary name needs to be written out in full, without initials, abbreviations or acronyms. | Free text | Mandatory | <CDTR> <NM>Jon Appelseed</NM> </CDTR> |
| Beneficiary Address | Beneficiary's physical full address | In principle a full address consists of a street number, street name, city, postal code, province and country name. PO Box should not be used unless it is in conjunction with the street address. Please note each country has its own specificities in terms of address, we strongly advise to check with your beneficiary. As of November 2026, only semi-structured or fully structured addresses will be allowed. Every address will have to include at least a country code and a town name in structured fields. Please refer to the Appendix XXXVI for deadlines and examples in the different available formats. |
Free text | Recommended | <CDTR> <PSTLADR> <ADRLINE>See appendix</ADRLINE> </PSTLADR> </CDTR> |
| Payment Purpose | Detailed purpose of payment | A clear reason / purpose of payment consists of a full written description (in English) of the nature of payment and needs to be provided in the remittance information avoiding abbreviations. For example, providing an invoice number without guiding text is considered as insufficient and can result in errors or delays. In addition, in case of payments linked to goods shipped via maritime transport, it is highly recommended to indicate the list of vessels (name + IMO number) involved. | Free message | Recommended | <RMTINF> <USTRD>Payment of travel expenses invoice n 123456789</USTRD> </RMTINF> |
| Data | Specification | Description | Format | Mandatory / recommended | Example MT101 * |
|---|---|---|---|---|---|
| Local Clearing System | Fedwire code or BIC SWIFT code | In order to enable the correct routing of the payment in the domestic clearing, either the Fedwire code (also known as ABA code) or BIC code (branch identifier included, if provided) should be used. In certain cases, the Fedwire code could be included within the domestic account number. Please ask your beneficiary to indicate separately this code and the domestic account number. In MT, please note the Fedwire code is required to be in field 57D, and the BIC code is in field 57A. For more information on format requirements in MT and MX, please see Appendix XXXII. |
See Appendix | Mandatory | :57D://See Appendix |
| Beneficiary Account Number | Domestic account number | It's important that the domestic account number of the beneficiary complies with the local account format of the destination country. | Local BBAN Format | Mandatory | :59:BBAN |
| Beneficiary Name | Beneficiary's full legal name | The full legal beneficiary name needs to be written out in full, without initials, abbreviations or acronyms. | Free text | Mandatory | :59:Jon Appelseed |
| Beneficiary Address | Beneficiary's physical full address | In principle a full address consists of a street number, street name, city, postal code, province and country name. PO Box should not be used unless it is in conjunction with the street address. Please note each country has its own specificities in terms of address, we strongly advise to check with your beneficiary. As of November 2026, only semi-structured or fully structured addresses will be allowed. Every address will have to include at least a country code and a town name in structured fields. Please refer to the Appendix XXXVI for deadlines and examples in the different available formats. |
Free text | Recommended | :59:See appendix |
| Payment Purpose | Detailed purpose of payment | A clear reason / purpose of payment consists of a full written description (in English) of the nature of payment and needs to be provided in the remittance information avoiding abbreviations. For example, providing an invoice number without guiding text is considered as insufficient and can result in errors or delays. In addition, in case of payments linked to goods shipped via maritime transport, it is highly recommended to indicate the list of vessels (name + IMO number) involved. | Free message | Recommended | :70:Payment of travel expenses invoice n 123456789 |
For additional information concerning the MT101 Format Specifications, please consult Knowledge Centre (swift.com)