[Moneytree LINK] Duplicate and Changed Transaction Records

In the transaction data provided through Moneytree LINK, for some financial institutions the same transaction may be retrieved more than once (duplicated), or the content of an already-retrieved transaction (such as the remitter's name) may change afterward. This FAQ explains the nature of these events and the points we ask you to keep in mind when using the data.

In transaction records retrieved from some financial institutions, the following may occur:

Neither is a loss or error in the data; both arise because the same transaction cannot be reliably matched as a single, identical record within the system. The individual transaction details themselves are retrieved accurately, based on what the financial institution provided at the time of retrieval.

This tends to be relatively more likely during periods with a high volume of transactions. That said, it does not always occur, and whether and how often it happens varies depending on the financial institution and timing.

This stems from the fact that, in the way some financial institutions provide their data, a permanent identifier for uniquely distinguishing each transaction is not always assigned. In such cases, it is technically difficult for the system to reliably match a transaction as the same, existing record versus a new one, which can result in duplication or a change in content.

This is not a defect in our service, but a structural characteristic arising from the data-provision specifications on the financial institution's side. Similar events can occur across services that retrieve and aggregate financial institution data as a common, industry-wide characteristic, and other major account-aggregation services also provide similar guidance on comparable events in their official FAQs.

No. This event is strictly a "duplication" or "change in content" of transaction records, and is different from data loss or tampering. The individual transaction details that are retrieved remain accurate, based on what the financial institution provided at the time of retrieval.

If you use transaction records for reconciliation or matching workflows, duplicate records or changes in content may cause discrepancies in amounts or record counts. We kindly ask that you consider designing your operations on the assumption that such events may occur (for example, by implementing duplicate checks).

We are continuously working on improvements to structurally reduce the occurrence of this event. At the same time, because a significant part of the cause lies in the data-provision specifications on the financial institution's side, it is difficult for us to guarantee a complete resolution or a specific timeline. We will share updates as progress is made.

If you have any questions about this event, or would like to discuss its impact on your specific case or specific Financial Institutions, please contact our JIRA Service Desk. We will look into your case and assist you as much as we can.