You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mdebarros opened this issue
Jun 18, 2021
· 0 comments
Assignees
Labels
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceoss-coreThis is an issue - story or epic related to a feature on a Mojaloop core service or related to it
It is calculating the amount incorrectly for every settlementModel that matches the ledgerAccountTypeId.
Severity:
High
Priority:
Critical
Expected Behavior
settlementWindowContent table should contain:
An entry for cach settlementWindow matching a speccific currency
Each entry should also contain the associated settlementModel id matching the currency and ledgerAccountTypeId where settlementGranularityId = Enum.Settlements.SettlementGranularity.NET
settlementContentAggregation table must reflect the above entry, providing an "amount" calculation for each participant+participantRole combination
Steps to Reproduce
Create more than one settlementModel for two different currencies
Send several transfers that match one of the above currencies
Close the associated settlementWindow, and monitor the settlementContentAggregation amounts being "double" counted
elnyry-sam-k
changed the title
Central-settlements is calculating amounts incorrectly for every settlementModel that matches the ledgerAccountTypeId.
Central-settlements calculating amounts incorrectly for every settlementModel that matches the ledgerAccountTypeId
Jun 21, 2021
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceoss-coreThis is an issue - story or epic related to a feature on a Mojaloop core service or related to it
Summary:
Central-settlements is calculating amounts incorrectly based on the Insert SQL statement: https://github.com/mojaloop/central-settlement/blob/master/src/models/settlementWindow/facade.js#L220.
It is calculating the amount incorrectly for every settlementModel that matches the ledgerAccountTypeId.
Severity:
High
Priority:
Critical
Expected Behavior
Steps to Reproduce
Specifications
Notes:
The text was updated successfully, but these errors were encountered: