# SEPA vs international payment batches

How Cortena splits payment batches into SEPA and International, and what to do on Payments for FinAPI, Embat, and Agicap.

When you send invoices for payment, Cortena groups them into separate batches for **SEPA** and **International**. Each batch shows a clear badge so you know which rail to authorize or download.

**Who this is for:** AP and treasury operators who pay suppliers through FinAPI, Embat, or Agicap and need to handle EU SEPA payments separately from international (non-SEPA) ones.

## 1. How batches are split

On **Payments**, each open batch is keyed by provider **and** payment scheme. SEPA and International never share the same queue.

When you **Send for payment** on a mixed selection, Cortena partitions invoices into separate batches:

| Scheme | When |
| --- | --- |
| **SEPA** | Supplier IBAN is in the SEPA zone **and** currency is **EUR** |
| **International** | Everything else the provider supports (non-EUR, non-SEPA IBAN, or for Embat also account + BIC/routing without IBAN) |

Batch headers show a pill: **SEPA** or **International**. An optional **Receives new invoices** chip marks the batch that still accepts new queue members.

## 2. What to do on Payments (by provider)

### FinAPI

| Scheme | Action |
| --- | --- |
| **SEPA** | **Authorize payment** (or **Retry authorization**) → complete the FinAPI Web Form |
| **International** | **Download pain XML** → upload the pain.001 file to your bank manually (no Web Form) |

### Embat

Both schemes enqueue export when you **Send for payment**. On Payments you may see **Export queued…**, then **Retry export** if stuck, or **Processing export…**.

| Scheme | How Embat receives it |
| --- | --- |
| **SEPA** | Embat **operations** API |
| **International** | pain.001 file upload. Set **Non-SEPA payment file bank ID** in Embat settings first |

### Agicap

Same Payments actions as Embat (auto pain import; **Retry export** if needed). One handoff covers both schemes; the pain file uses SEPA or non-urgent service level based on the batch.

## 3. Dates and history labels

| Provider | Date label on completed batches |
| --- | --- |
| FinAPI | **Authorized on** |
| Embat / Agicap | **Sent for payment on** |

History sections: **Action required** and **Authorized and completed**. Status badges include **Authorized** and **Completed**.

## 4. Payment rails strip

The **Payment rails** strip on Payments summarizes what each connected provider can do, for example:

- FinAPI: SEPA EUR · non-SEPA manual XML
- Embat: SEPA operations · non-SEPA file
- Agicap: SEPA and non-SEPA via pain file

## Tips and limitations

- Related: [FinAPI: connect your bank and pay from that account](https://help.cortena.ai/guides/integrations/finapi) and [Embat treasury](https://help.cortena.ai/guides/integrations/embat-treasury).
- International FinAPI payments are download-only. Cortena does not open a Web Form for non-SEPA.
- Embat international file upload requires the setting **Non-SEPA payment file bank ID**.

## Quick reference

| Task | Where |
| --- | --- |
| See scheme | **Payments** → batch badge **SEPA** / **International** |
| FinAPI SEPA | **Authorize payment** |
| FinAPI international | **Download pain XML** |
| Embat / Agicap | Auto-export on send; **Retry export** if stuck |
| Embat non-SEPA bank | **Settings → Integrations → Embat** → **Non-SEPA payment file bank ID** |
| Capability overview | **Payment rails** strip |