Currently a batch needs to be settled through a matrix, Settlement also needs to support a scenario where transfers are immediately settled as the transfers are received in Settlement.
The settlement model configuration will delegate whether gross or net settlement scenarios should be used for the settlement model.
The processing will be updated to work as follows:
Transfer is received in Settlement and allocated to a batch
A new batch will be created if one doesn't already exists, the batch will be created in a SETTLED status
The settlement matrix settle event will be fired at configured intervals in order to update POSITION and LIQUIDITY balances for the participant
Goal:
As a <stakeholder|persona>
I want to
so that
Acceptance Criteria:
[ ] TBD
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
[ ] TBD [ @? ]
Done
[ ] Acceptance Criteria pass
[ ] Designs are up-to date
[ ] Unit Tests pass
[ ] Integration Tests pass
[ ] Code Style & Coverage meets standards
[ ] Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
Currently a batch needs to be settled through a matrix, Settlement also needs to support a scenario where transfers are immediately settled as the transfers are received in Settlement. The settlement model configuration will delegate whether gross or net settlement scenarios should be used for the settlement model.
The processing will be updated to work as follows:
SETTLEDstatusGoal:
As a<stakeholder|persona>I want toso thatAcceptance Criteria:
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
Done
Pull Requests:
Follow-up:
Dependencies:
Accountability: