Is OUTCFI22 a valid SWIFT code?

Yes. OUTCFI22 has the right format and is in our directory for METSO OYJ, ESPOO. Confirm with the beneficiary that it is the bank that holds their account.

What is the difference between OUTCFI22 and OUTCFI22XXX?

None. OUTCFI22 is the 8-character form of OUTCFI22XXX; XXX at the end means the head office. Either works.

SWIFT/BIC · Finland

OUTCFI22

METSO OYJ · Head office · ESPOO

Code details

SWIFT/BIC: OUTCFI22 (OUTCFI22XXX)
Institution: METSO OYJ
Office: Head office
Branch code: XXX · head office
Address: RAUHALANPUISTO 9, 02230 ESPOO
City: ESPOO
Country: Finland

What OUTCFI22 means

OUTCFI22XXX

OUTCBank code
Four letters chosen by the institution.
FICountry code
Finland (ISO 3166)
22Location code
Where the institution sits on the SWIFT network. A 1 in second place marks a passive participant.
XXXBranch code
XXX, or nothing at all, means the head office.

Paying an account at this bank

You will also need the beneficiary’s IBAN. Finland IBANs have 18 characters and start with FI. IBAN format and example → Check an IBAN →

Questions

Is OUTCFI22 a valid SWIFT code?: Yes. OUTCFI22 has the right format and is in our directory for METSO OYJ, ESPOO. Confirm with the beneficiary that it is the bank that holds their account.
What is the difference between OUTCFI22 and OUTCFI22XXX?: None. OUTCFI22 is the 8-character form of OUTCFI22XXX; XXX at the end means the head office. Either works.

Sending to OUTCFI22?

TrillioniPay shows the fee and the rate before you confirm, and the day the money should land.

Join the waiting list When will it arrive?

About this data

Codes are checked against our directory of banks on TrillioniPay corridors. Always confirm the code with the beneficiary’s bank before sending a payment. Last updated: 23 September 2026.

Institution names and addresses: Global Legal Entity Identifier Foundation (GLEIF) LEI data, available under CC0. The address is the legal entity’s registered or head-office address, which can differ from the office SWIFT lists.

SWIFT © and database rights August 2026. All rights reserved. This Mapping Table has been developed by SWIFT. Any use of the Mapping Table, in whole or in part, is subject to the BIC/LEI Mapping Table License Agreement as published with the Mapping Table available on GLEIF's website. The Mapping Table is updated monthly. For the latest BIC information and updates, always refer to www.swift.com/bic .