All Collections
EdgeLink
EdgeLink Verify
EdgeLink Transaction Matching
EdgeLink Transaction Matching
Exempt Edge avatar
Written by Exempt Edge
Updated over a week ago

In certain situations, a company might share a transaction with an EdgeLink-connected party who already has that transaction in their system. To avoid the risk of creating a duplicate transaction, the EdgeLink system will scan the receiving party's system and present possible transaction matches, allowing a connection to be established between the newly transited data and their existing data.

This system scan will only be performed when information flows from the Issuer to the Dealer, therefore the initiation event can only be performed by the Issuer, and the reconciliation event can only be performed by the Dealer.

Here is a high-level of what each party can expect:

For Issuers

All transaction that are sent from your system to a connected Dealer are automatically verified for possible matches, therefore your day-to-day processes are not affected. The only difference that this verification introduces to your system is in the form of an option to send individual transactions to a connected party.

This option is presented for any transaction in your system that belongs to an offering that is EdgeLink connected, but that is not currently matched to a transaction in the Dealer's system, and that is not pending to be accepted by them.

Within the Overview of these transactions, there is an option called "Send EdgeLink Transaction". Clicking this will not change anything in your system but it will send this transaction to your connected party, allowing them to either create it as a new transaction or match it to one of their existing transactions.

For Dealers

All transactions that are sent to you from a connected Issuer are verified to ensure that the Investor, Advisor, and Account connected to this transaction are known. Additionally, these transactions are scanned to determine if you might already have this transaction in your system. If any possible matches are determined, you are asked to select the correct match or indicate that this is a new transaction. In this way, you have control over how this incoming data is accepted into your system, avoiding the creation of duplicates. If no possible match is found, then the system will assume that this is a new transaction and will create it in your system without requiring your confirmation.

In the table posted above, the details of the transaction received from the Issuer are indicated in the top section, and the detailed of the possible matching transaction are displayed in the drop-down menu highlighted in red.

Please note, if any differences exist between your existing transaction and the Issuer's, selecting to match them together will modify your transaction data to match the Issuer's.

For an in-depth exploration of this process and your options, please refer to the guide linked below:

Did this answer your question?