Problem
The settlement flow introduced in #211 only works for transactions between registered Securo users, or from a Securo user to a non-registered user, not the other way around.
In practice, many synced bank transactions involve participants who are not registered in Securo yet. This prevents users from marking existing transactions as settlements when:
- A Securo user transfers money to a non-registered participant
- A non-registered participant transfers money to a Securo user
As a result, users may need to create duplicate manual settlement transactions even when a matching synced transaction already exists.
Proposed Solution
Extend the settlement transaction flow to support transactions involving non-registered participants, reusing the existing settlement matching flow introduced in #211
Alternatives Considered
Requiring all group participants to register before settlements can be linked:
It creates friction for casual or temporary splits
Continuing to require manual settlement creation for non-registered users:
It duplicates transactions that already exist in synced bank data
Additional Context
This issue is a follow-up to #184.
The goal is to make settlement matching work consistently regardless of whether both participants are registered Securo users.
Problem
The settlement flow introduced in #211 only works for transactions between registered Securo users, or from a Securo user to a non-registered user, not the other way around.
In practice, many synced bank transactions involve participants who are not registered in Securo yet. This prevents users from marking existing transactions as settlements when:
As a result, users may need to create duplicate manual settlement transactions even when a matching synced transaction already exists.
Proposed Solution
Extend the settlement transaction flow to support transactions involving non-registered participants, reusing the existing settlement matching flow introduced in #211
Alternatives Considered
Requiring all group participants to register before settlements can be linked:
It creates friction for casual or temporary splits
Continuing to require manual settlement creation for non-registered users:
It duplicates transactions that already exist in synced bank data
Additional Context
This issue is a follow-up to #184.
The goal is to make settlement matching work consistently regardless of whether both participants are registered Securo users.