Transaction Review

The Transaction Review page in the Braid interface provides a dedicated view of financial transactions that have either been flagged for review due to rule breaches or have already been reviewed and acted upon. The page helps track the status of these transactions, giving operators insight into those awaiting further action or already processed. However, the actual approval or rejection of transactions is managed through the Alerts area of Braid.

Key Features:

Transaction Review Table:

The Transaction Review Table lists all transactions that are either pending review or have already been acted upon. This allows the bank operations team to monitor the status of flagged transactions.

• Table Columns include:

• Payment ID: A unique identifier for each transaction.

• Created at: The timestamp when the transaction was initiated (e.g., 2024-10-07 17:00).

• Account Number: The account associated with the transaction (e.g., 40422144290).

• Amount: The monetary value of the transaction, showing credits (+) or debits (-).

• Customer: The customer initiating the transaction (e.g., SFTP Reports, FinZeo).

• Counterparty: The recipient or other party in the transaction (e.g., Michael Brown, Mona Katare).

• Transaction Type: Specifies the transaction type (e.g., ACH Originator Credit, Adjustment).

• Product ID: The associated product or service (e.g., 785994).

• Status: Displays the current status of the transaction (e.g., Pending Review, Reviewed).

Filtering, Columns, and Density Options:

• Filters: Narrow down the transactions list based on criteria such as date, status (pending or reviewed), customer, or transaction type.

• Columns: Customize which columns are visible for a more focused view of relevant transaction data.

• Density: Adjust the table density for a compact or expanded view.

Review Process for Flagged Transactions:

Transactions listed on this page are flagged due to rule breaches and require review. However, the approval or rejection of these transactions happens in the Alerts area. The Transaction Review page serves primarily as a tracking tool, while Alerts handle the actual decision-making process.

• Transaction Details Popup:

• Clicking on a transaction will bring up a popup that displays the detailed information about the transaction.

• Rules Breached: It will show which specific rules the transaction violated, providing context on why the transaction was flagged for review.

• Alerts Area:

• The Alerts area is where bank operations staff can take action (approve or decline) on these flagged transactions. This page serves as a reference to see which transactions require attention but does not allow direct approval/rejection from the Transaction Review page.

DataSeer Integration:

How to Use the Transaction Review Page:

Reviewing Transactions:

1. Navigate to the Transaction Review page:

• Select Transaction Review from the Transactions sub-menu to view all transactions pending review or that have been acted upon.

2. Inspect Transactions:

• Review the Status, Customer, and Transaction Type columns to get a snapshot of the transactions that need attention or have already been reviewed.

3. Use Filtering Options:

• Apply filters based on date, amount, customer, or status to quickly locate transactions that require review or have been processed.

Approving or Rejecting Transactions:

1. Monitor Alerts for Actionable Items:

• The actual approval or rejection process happens in the Alerts section of Braid. After reviewing details in the Transaction Review page, head to Alerts to take appropriate actions.

2. Transaction Details:

• Click on a transaction to open its detailed popup to view why it was flagged. The information displayed here is useful for decision-making in the Alerts area.

Best Practices:

• Regularly Check Alerts for Pending Actions:

• While the Transaction Review page lists flagged transactions, always ensure you're monitoring the Alerts area to take timely action on approvals or rejections.

• Use Filters to Organize Transaction Views:

• Utilize the filter options to streamline your view and focus on the most critical transactions. This will help to identify which transactions require prompt action in the Alerts area.

• Document Reviewed Transactions:

• Keep records of approved and declined transactions for audit purposes. Export the transaction data if needed for compliance and analysis.

Exporting Transaction Data:

1. Export: After reviewing transactions, you can export the data for further analysis or auditing.

• Click the EXPORT button to download the currently displayed transaction data.

• Exported data can be used to maintain compliance and support reporting requirements.