You already send payment files to the bank — one file can hold dozens of payments. Each payment can then have a different fate: accepted, rejected for a bad IBAN, pending, settled, returned. This guide shows how to enable tracking once, keep sending payments as usual, and watch every order move from Submitted to Settled — all from the app, with clicks only.
After the file is uploaded, visibility ends. Someone has to open each bank portal, download history and settlement reports, and match end-to-end references by hand to see what was accepted, rejected, or is still pending. With several banks, this means several portals in parallel. A rejected payment is often found only after the deadline — and every bank reports it in its own format.
You enable tracking for each connection once. The app knows where to ask the bank and where to notify you.
You send payments as usual. Every end-to-end reference in the file becomes a tracked order automatically.
Orders appear in one list — with a status chip, connection, and last update. You filter, expand history, or clean up.
The system asks the bank for you — first whether the order was accepted, then whether it settled — and updates each order.
A group with several companies. One finance team pays for 5 companies, each with its own bank. One list shows every payment together — no portal hopping to find the one rejection.
An agency that pays for many clients. A payroll office or fiduciary runs payments for dozens of clients. Each order stays linked to its connection, with full history per payment when a client asks "where is my money?".
Finance team that lives in spreadsheets. You don't want to learn bank report formats. This flow feels like uploading a file and watching statuses change — no XML, no special knowledge.
For step-by-step visual instructions check out the presentation slides — they walk you through completing the setup.
Navigate to Banking → Order Tracker to open the tracked orders list, and to Banking → Tracker Subscriptions to tell each connection where to check statuses and where to send notifications.
Each tracked order moves from Submitted to Processing or Invalid, then to Pending, Settled or Rejected — plus Returned or Cancelled if the bank reports it later.
Before orders can move past Submitted, create a Tracker Subscription for each connection. Without it, orders stay Submitted — the system does not ask the bank and sends no notifications.
EBICS Connection — The connection to track (own connections only).
Transfer order type (optional) — Upload type used for payments, e.g. CCT, CDD, BTU. When set, only uploads of exactly that type are tracked; when empty, all upload types are tracked.
Settlement order type (optional) — Download type used for the settlement report, e.g. C54, BTD. Connections without it are skipped by the settlement check.
Webhook URL (optional) — External address notified on every status change with the end-to-end reference and the new status. When empty, statuses are still tracked, just no call is made.
Once tracking is enabled, any file you upload is split into tracked orders by itself — one order per end-to-end reference, starting as Submitted. You can also add an order by hand for payments sent from outside the app.
Navigate to Banking → Bank Operations. Select the connection and the upload order type (e.g. BTU). Upload your payment file. The system creates one Submitted order per end-to-end reference found in the file.
For payments uploaded outside the application (e.g. via another EBICS client), click Add Tracker in the Order Tracker toolbar. Fill in the connection and the end-to-end reference — the new order starts as Submitted so the bank checks can still pick it up.
Every order you track is saved here. Think of it like an inbox for payments — each line is one payment with its current status. You can keep as many orders as you like, for different months, banks, or purposes.
The Order Tracker page lists all your tracked orders (including orders on connections shared with you). Each row shows the end-to-end reference, the status chip, and details (connection and last update).
Use the filter dialog in the toolbar to narrow the list by Status and Connection; active filters are shown as removable chips above the table.
Row actions:
Expand (chevron icon) — Opens the inline history timeline: three steps (Submitted, Processing, Settlement) with status, creation date, and notification date per step. Hover a row for exact timestamps.
Delete (trash icon, owner orders only) — Removes the order with its history, after confirmation. Shared orders cannot be deleted.
Bulk delete — Select multiple rows with checkboxes to delete them at once.
Saving is step one. Knowing the outcome is step two. The system asks the bank on schedule — first whether each order was accepted, then whether it settled — so you don't have to download reports by hand.
Navigate to Settings → Cron. The page shows the Cron URL and all scheduled checks with their intervals and status. For any check that is not locked, click the play icon to run it immediately.
Submitted notifications (every 5 minutes) — Delivers pending status notifications in the background, so a slow external address never blocks your uploads.
Processing check (every 5 minutes) — Downloads the bank receipt (pain.002) per connection and marks orders as Processing or Invalid.
Settlement check (every hour) — Downloads the settlement report (camt.054) and marks orders as Pending, Settled, or Rejected.
While a check is running, it is locked so it cannot run twice. A stuck lock is released automatically after 5 minutes, or manually with the unlock icon next to the check.
Order Tracker gives one live list for every SEPA payment by end-to-end reference. One uploaded file with dozens of payments becomes dozens of tracked orders with status chip, connection and last update — no portal hopping across banks to find acceptances, rejections or settlement.
Submitted → Processing or Invalid (from bank receipt pain.002) → Pending, Settled or Rejected (from settlement report camt.054), plus Returned or Cancelled if reported later. Expand a row (chevron) for 3-step timeline: Submitted / Processing / Settlement with timestamps.
Per-connection config (Banking → Tracker Subscriptions) telling the system where to check and notify: EBICS Connection, optional Transfer order type (e.g. CCT, CDD, BTU — empty = all uploads), optional Settlement order type (e.g. C54, BTD), optional Webhook URL (notified with reference + new status on every change). Without it orders stay Submitted.
Via Settings → Cron: Submitted notifications every 5 min, Processing check (pain.002 download) every 5 min, Settlement check (camt.054 download) hourly. Click play to run now; running checks lock against double-run, stuck locks auto-release after 5 min or via unlock icon.
Click Add Tracker, enter connection + end-to-end reference — starts as Submitted so bank checks pick it up. Delete (owner only, trash icon, or bulk via checkboxes) removes order + history. Shared-connection orders are visible but not deletable.