The Unsettled transactions screen shows transactions that failed (or were never collected) and for which either no dunning workflow is configured or all dunning steps have been exhausted. In most cases these transactions require manual follow-up to complete the collection.

The Unsettled transactions screen consists of:
The Unsettled screen shows a maximum of 500 transactions at a time.
If more transactions match your criteria, the following message is displayed:
List too long, showing limited results only. You can use filters to narrow it down.
You can refine the results using:
Both filter types can be combined.
Preset filters allow you to quickly segment unsettled transactions. The most relevant presets are:
Never collected
Transactions that were created but never sent to the bank, usually because the mandate was cancelled before collection. These transactions can only be collected manually.
Unsettled (default)
Transactions that were sent to the bank but failed, and for which either no dunning workflow is configured or all dunning steps have been exhausted.
Sent to collection agency
Transactions forwarded to a collection agency. Their status (unsettled, paid, or partially paid) depends on the feedback received via your collection agency integration (API or FTP).
The search field works within the currently displayed results and supports searching on most fields.
Exceptions:
Depending on the failure reason, different follow-up actions are available.
Actions can be applied:
For transaction-specific actions, you can click a single transaction line to open the details.
For a comprehensive list of all possible actions, you can read our support article about actions on unsettled transactions