import { Callout } from "zudoku/ui/Callout";

# International payments

Payments outside the SEPA area or in foreign currency: how to carry out international payments in 365 business Banking via EBICS or as a pain file.

A SEPA credit transfer is only possible in euros to an IBAN at a bank within the SEPA area. All other payments are **international payments**, for example a payment in US dollars, to a bank in Switzerland or in Asia, or to a recipient without an IBAN. 365 business Banking hands it in via EBICS as a **foreign credit transfer** if your bank offers the order, or writes it as a pain.001 file with the payment scheme *International*, which you upload in your bank's online banking.

**Applies to:** EBICS (if the bank offers the foreign credit transfer) · camt/pain file with the payment scheme *International*

## Connections for international payments

| Connection | International payment |
|---|---|
| EBICS | yes, as a separate foreign credit transfer order (`XCT` under EBICS 3.0, `AXZ` under EBICS 2.5) if your bank offers it for the EBICS participant. 365 business Banking detects international payments per line. |
| camt/pain file, payment scheme *International* | yes, as a pain.001 file to upload in online banking |
| PSD2/XS2A via finAPI | no; SEPA payments only, including to other SEPA countries |

<Callout type="info" title="SWIFT via Cobase from version 18.5">
From version 18.5, 365 business Banking also connects bank accounts via SWIFT, with Cobase as provider, for bank statements and payments outside the SEPA area. For more information, see [SWIFT payments via Cobase](../features/details/swift-payments.mdx).
</Callout>

## What applies to every international payment

- The recipient has a released bank account with name, IBAN or national account number, and **SWIFT Code** (BIC).
- If the payment is in a currency other than euro or goes to a bank outside the EU/EEA, it also needs the recipient's town and country. Business Central takes these details from the address of the vendor, customer or employee, or from the remit-to address. If the country is missing, it is determined from the IBAN or the BIC.
- The payment method on the journal batch has the banking **Payment Method** *SEPA Credit Transfer* or *SEPA Collective Credit Transfer*. There is no separate payment method for international payments. *SEPA Instant Credit Transfer* is not possible, because instant credit transfers are only available within SEPA.

<Callout type="note" title="IBAN or account number, BIC is mandatory">
Outside SEPA, a recipient does not need an IBAN. The national account number and the BIC of their bank identify the account. If an IBAN is entered, Business Central checks it. Without a BIC, an international payment cannot be routed. A payment with only a bank code (without BIC) is not supported by 365 business Banking.
</Callout>

## Via EBICS

Via EBICS, no separate selection is required for an international payment. 365 business Banking checks every line of the payment journal individually. A payment in euros to an IBAN at a bank in the SEPA area stays a SEPA credit transfer. A payment in another currency, to a recipient without an IBAN or to a bank outside the SEPA area becomes a foreign credit transfer.

### Prerequisites

- The bank account is connected via [EBICS](../connections/ebics/index.mdx), and your EBICS contract includes the foreign credit transfer (`XCT` without option, or `AXZ`).
- Whether your bank offers the foreign credit transfer for the participant, 365 business Banking reads from the order overview in the bank's customer data (HTD) when the account is connected. It is not shown in the **Capabilities** FactBox on the bank account card. If the bank does not offer the order, **Carry Out Payment** stops with a message (see [Troubleshooting](#troubleshooting)). If your bank added the order to the contract later, choose **Refresh Customer Data (HTD)** on the EBICS participant card.

### Step by step

1. Open the **Payment Journal** with the journal batch of the EBICS account.
2. Enter the lines with **Currency Code**, amount, **Message to Recipient** and the recipient's bank account, or have them suggested. SEPA and international payments can be in the same journal.
3. Choose **Payment** > **Carry Out Payment** and confirm the question "Do you want to carry out the payment for payment journal …?".
4. If a payment of more than EUR 12,500 goes to a recipient outside Germany, Business Central asks: "… of these payments go to a recipient outside Germany and amount to more than EUR 12,500. Payments to non-residents over EUR 12,500 must be reported to the Deutsche Bundesbank under section 67 of the German Foreign Trade and Payments Ordinance (AWV). … Do you want to continue?" Choose **Yes** to continue. Choose **No** to cancel the process (see [Notes](#notes)).
5. If the journal holds international payments, the **Carry Out Payment** page shows every order under **Orders** with the number of payments, the totals per currency and the message ID. If the journal also contains SEPA payments, two orders are shown: "SEPA credit transfers: … payments, … - message ID …" and "Foreign credit transfers: … payments, … - message ID …". Check the orders and choose **Next**.
6. Business Central hands in the SEPA credit transfers and the foreign credit transfers as separate orders. If your bank contract requires a second signature, release the orders in your banking program. See [Second signature at the bank (VEU)](../connections/ebics/distributed-signature.mdx).
7. Post the journal once the lines have the **Payment Status** *Completed*.

### What you see afterwards

- For a mixed journal, the message "The payment was handed in at your bank as two orders: the SEPA credit transfers under order number … and the foreign credit transfers under order number …. Both stay pending until your bank has carried them out." If the journal contains only international payments, the message is "The foreign credit transfers were handed in at your bank under order number …. …"
- The lines are *Pending*. Your bank reports on foreign credit transfers in a status report of its own (pain.002; under EBICS 3.0 `REP` with option `XCT`, under EBICS 2.5 order type `AXS`). **Update Payment Status** and the scheduled follow-up fetch it and set the lines to *Completed* or *Rejected*.
- On the **EBICS Submissions** page the foreign order is marked in the **Foreign Credit Transfer** column. If it holds several currencies, **Multiple Currencies** is marked as well, and no total is shown. See [EBICS jobs and submissions](../connections/ebics/jobs-and-submissions.mdx).

### What the file looks like

The foreign credit transfer is always a pain.001.001.09 following the German Banking Industry Committee's rules for foreign payments:

- Charge bearer *SHAR* (shared charges) and service level *NURG* (non-urgent) on every payment.
- One payment block per currency and execution date. In a collective credit transfer, the payments of a block share one base of the **end-to-end reference**, each with an ending of its own (`-1`, `-2` …). See [End-to-end reference and collective payments](../bank-payment/carry-out-payment.mdx#end-to-end-reference-and-collective-payments).
- The foreign order has a message ID of its own. The SEPA file keeps its own message ID.

An urgent same-day payment in euros is a [euro urgent payment](euro-urgent-payment.mdx) with a banking payment method of its own, not a foreign credit transfer.

## As a pain file

### Prerequisites

- A bank account with the [ISO 20022 file setup](../connections/iso20022-file/setup.mdx) and the **Payment Scheme** *International*. With the *International* scheme, any currency is allowed, the BIC is mandatory, and the recipient account does not have to be an IBAN.
- The file must state the currency of the account the payment is made from. Business Central uses the **Currency Code** of the bank account card for this. If it is blank, the local currency (LCY) is used.
- A payment journal batch with this bank account and a payment method with the banking payment method *SEPA Credit Transfer* or *SEPA Collective Credit Transfer*. The bank account's payment scheme determines the processing.

### Step by step

1. Open the **Payment Journal** with the journal batch of the international account.
2. Enter the lines with **Currency Code**, amount, **Message to Recipient** and the recipient's bank account, or have them suggested.
3. Choose **Payment** > **Carry Out Payment** and confirm the question. If asked, also confirm the question about the reporting obligation under section 67 AWV with **Yes**.
4. Business Central checks the payments against the format and offers the file `pain.001_<message ID>.xml` for download.
5. Upload the file in your bank's online banking and authorize it there.
6. Post the journal once the bank has accepted the file.

After saving, the lines have the status *Completed*. This status only means that the file was written. For details on the file route, see [Export a payment file](../connections/iso20022-file/export-payment.mdx).

Direct debits are not possible with the *International* scheme, because direct debits are a SEPA-only procedure.

## Notes

- **AWV reporting.** Payments to non-residents over EUR 12,500 must be reported to the Deutsche Bundesbank under section 67 of the German Foreign Trade and Payments Ordinance (AWV). On **Carry Out Payment**, Business Central reminds you of this when a payment goes to a recipient whose address or bank is outside Germany and amounts to more than EUR 12,500 after conversion. This applies to every connection and to both SEPA and international payments. The app does not create the report itself, and no payment file contains this report. File it separately, for example through the Bundesbank's reporting portal. Choose **No** to cancel the process.
- For the file route, the payment scheme belongs to the bank account. A file account with *International* cannot be combined with the SEPA services PSD2/XS2A or EBICS. See [Combine banking services](../connections/mixed-operation.mdx). Via EBICS, you do not need a separate account for this, because the international payments are made from the same EBICS account.
- Verification of Payee (VoP) is only available for IBANs within the SEPA area. See [Verification of Payee (VoP)](../bank-payment-vop.mdx).

## Troubleshooting

Even before the file is written, **Carry Out Payment** checks every line:

| Message | Cause and remedy |
|---|---|
| "Recipient details are incomplete for payment journal line …. An international credit transfer needs the recipient name, the IBAN or the account number, and the BIC." | Complete name, IBAN or account number, and the **SWIFT Code** on the recipient's bank account. |
| "The … of payment method … cannot be used for bank account …. Bank account … pays under the international (SWIFT) rules, and instant credit transfer exists only within SEPA. …" | File account with the payment scheme *International*: Use a payment method with the banking payment method *SEPA Credit Transfer* or *SEPA Collective Credit Transfer*. |
| "Payment journal line … cannot be carried out as an instant credit transfer. Instant credit transfers exist only in euro, to an IBAN at a bank in the SEPA area. …" | EBICS: The line is an international payment in a journal for instant credit transfers. Carry it out from a journal with *SEPA Credit Transfer* or *SEPA Collective Credit Transfer*. It is then handed in as a foreign credit transfer. |
| "The bank account … of … is not released for payments. …" | Release the recipient's bank account. See [Recipient bank accounts](../bank-payment/recipient-bank-accounts.mdx). |
| "The bank does not offer foreign credit transfers for this EBICS participant (XCT/AXZ). …" | The bank's order overview does not list the order for this participant. No order is handed in, not even for the SEPA payments. Ask your bank to add the order to your EBICS contract and then choose **Refresh Customer Data (HTD)** on the EBICS participant. |
| "The bank does not offer SEPA credit transfers for this EBICS participant (SCT/CCT). …" | The contract only includes the foreign credit transfer. The journal's SEPA payments are not handed in. Have your bank enable the SEPA order. |
| "The SEPA credit transfers were handed in at your bank under order number …. Their … payments are pending, so do not hand them in again. The foreign credit transfers could not be handed in, …" | The second order failed. The SEPA payments have been handed in. Only the international payments are still open in the journal. Resolve the reason given and carry out the payment again. Only the open lines are handed in. |

If a payment cannot be written in the format, Business Central reports "The payment cannot be written as …:" with a list of reasons. Typical reasons for international payments:

| Reason in the message | Remedy |
|---|---|
| "Line … has no recipient BIC. An international payment cannot be routed without naming the recipient bank." | Enter the **SWIFT Code** on the recipient's bank account. |
| "Line … has no recipient account. An international payment needs an IBAN or a national account number." | Enter the IBAN or account number on the recipient's bank account. |
| "Line … has no recipient town and country. A foreign credit transfer outside the EU/EEA or in a currency other than euro needs the postal address of the recipient." | Enter the town and country of the recipient (or on the remit-to address). |
| "Line … has no currency. An international payment is not assumed to be in euro." | Enter the **Currency Code** on the line. |
| "The payment has no debtor account currency. An international payment must state the currency of the account it is paid from." | Enter the **Currency Code** on the bank account card. |

## See also

- [Payments via EBICS](../connections/ebics/payments.mdx)
- [Euro urgent payment via EBICS](euro-urgent-payment.mdx)
- [Set up a bank account for camt/pain files](../connections/iso20022-file/setup.mdx)
- [SEPA credit transfer](sepa-credit-transfer.md)
- [Carry out payment: process per bank connection](../bank-payment/carry-out-payment.mdx)
- [EBICS foreign credit transfer and euro urgent payment (new feature)](../features/details/ebics-foreign-urgent-payments.mdx)