Best Practice & Strategy Library: Duplicated Transactions

Rob_French
Posts: 69 QUANTEXA TEAM
Duplicated transactions can be pulled into aggregated transactions for multiple reasons such as:
1) The transaction being internal between two customers of the bank.
2) Through the SWIFT message system creating messages about the same transaction in two different message types.
To find out how best to handle them in Quantexa please use the following best practice page:
https://community.quantexa.com/kb/articles/51-handling-duplicated-transactions-draft
1) The transaction being internal between two customers of the bank.
2) Through the SWIFT message system creating messages about the same transaction in two different message types.
To find out how best to handle them in Quantexa please use the following best practice page:
https://community.quantexa.com/kb/articles/51-handling-duplicated-transactions-draft
0
Topics
- Topics
- Support
- Support
- 12 Quantexa Community Library
- 1.4K Academy
- Insights & Innovation
- Insights & Innovation
- 3 NEW: Product Demos
- Launch the Customer Intelligence Demo
- Launch the Trade AML Demo
- 11 User Research Panel
- Latest from Quantexa
- Connect
- 95 Getting Started
- 326 Quantexa News & Announcements
- 14 Release Announcements
- 29 Community Digest
- 32 Quantexa News Intelligence
- Get Involved
- 41 Get Rewarded
- 11 Quantexa Career Development