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.
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) |
EBICS
EBICS can send both SEPA and non-SEPA (international) payments when your bank enabled those order types on the EBICS contract. Ask the bank for non-SEPA explicitly if you need it; many contracts are SEPA-only by default.
| Scheme | Action |
|---|---|
| SEPA | Authorize via email → confirm the link → Cortena uploads SCT pain.001 via EBICS |
| International | Same Authorize via email flow → Cortena uploads XCT (international) pain.001 via EBICS |
Nothing reaches the bank until email authorization is accepted. See Authorize EBICS payments via email and EBICS with Cortena.
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 |
| EBICS | Authorized on (after email confirm) |
| 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
- EBICS: SEPA and non-SEPA via EBICS upload (when the bank enabled both)
- Embat: SEPA operations · non-SEPA file
- Agicap: SEPA and non-SEPA via pain file
Tips and limitations
- Related: FinAPI, EBICS with Cortena, and Embat treasury.
- International FinAPI payments are download-only. Cortena does not open a Web Form for non-SEPA.
- EBICS international upload requires the bank to have enabled non-SEPA payment orders on your EBICS subscriber.
- 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 |
| EBICS SEPA / international | Authorize via email (then bank upload) |
| 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 |