Skip to main content

Ongoing Monitoring: Source vs Destination Accounts

Within the Alloy schema of a transaction, there are two main Alloy concepts: Source and Counterparty (formerly called Destination). Understanding these two concepts will be essential for effective transaction management.

Source Account

The Source Account is an account where the evaluating transaction is connected to, and owned, by the Source Entity.

A Source Entity is the who onboarded or holds an account managed by your financial institution. They represents the party being evaluated in a transaction evaluation as well as the subject of an Investigation (previously “case”) but not necessarily the originator of the transaction.

A Source Entity can have multiple source accounts—for example, a checking and savings account.

Counterparty Account

The Counterparty Account (formerly Destination Account) is where the evaluating transaction is connected to, and owned by the counterparty. This is the other side of the transaction who the entity is interacting with to send the money to (or receive the money from if a return is being processed).

A Counterparty is the opposing party of the transaction that is not the source entity of the evaluating transaction. The counterparty can be a person that holds an account managed by your financial institution, but also external merchant account that provides goods and services to the source entity.

Like a Source Entity, a Counterparty can have multiple accounts—for example, a Counterparty can have a checking and savings account.

Where Source and Counterparty Appear in the Dashboard

When you open a transaction evaluation in the dashboard, the transaction summary shows the money movement for the evaluated transaction: the dollar amount, the transaction status, and the accounts between which the money was exchanged, from the source account to the counterparty account. The card header varies based on the type of transaction that occurred.

Counterparty details submitted with the transaction event (such as counterparty ID, type, name, account number, and country code) are also visible on the transaction record in the evaluation view.

Data Flow Diagram

The Data Flow Diagram presented below provides a visual representation of the data flow between the “Source” and “Counterparty” objects within the Alloy framework. This diagram serves as a tool to understand the movement of transactions between these key concepts.

Screenshot 2023-07-17 at 11.05.14 AM.png

Example

Jane Doe is the account owner at a financial institution, Alloy Bank. Jane Doe purchases an item on Amazon. In this example, Jane Doe is the Source Entity, because they are the entity being screened. Amazon is the Counterparty , because it is what the entity is interacting with to send the money to.

If Jane Doe returns the item to Amazon, Amazon is still the Counterparty . Even though the money is being returned to the entity in the transaction, Amazon remains the Counterparty.

Did this answer your question?