Transfers Analysis

Transfers Analysis - DocuClipper Knowledge Base

Transfers Analysis #

Overview #

The Transfers feature automatically detects and matches transactions that represent money movements between different accounts. This is essential for understanding the complete financial picture and avoiding double-counting in financial analysis.

What It Does #

  • Automatic Detection: Uses algorithms to identify potential transfer transactions between accounts
  • Transaction Matching: Pairs corresponding debit and credit transactions that represent the same money movement
  • Manual Creation: Allows you to manually create transfer matches when automatic detection misses them
  • Status Management: Track approval status of detected transfers

How Transfer Detection Works #

The system analyzes transactions looking for:

  • Similar amounts on different accounts within a time window
  • Opposite transaction types (one debit, one credit)
  • Matching or similar descriptions
  • Reasonable timing between transactions

How to Use #

  1. Navigate to Transfers: Go to Analyze → Transfers tab
  2. Automatic Detection:
    • Click "Detect Transfers" to run automatic matching
    • The system will analyze all transactions and identify potential matches
  3. Review Matches:
    • View the results table showing paired transactions
    • Check account names, dates, descriptions, and amounts
    • Review the match status (pending, approved, rejected)
  4. Approve or Reject:
    • Click "Approve" for valid transfers
    • Click "Reject" for false positives

Manual Transfer Creation #

  1. Open Creator: Click "Create Transfer" to expand the manual creation interface
  2. Select Transactions:
    • Use the left table to select the source transaction
    • Use the right table to select the destination transaction
    • Apply filters to find specific transactions
  3. Create Match: Click "Create Match" to link the selected transactions

Understanding the Results Table #

Transaction 1 (Source) #

  • Account1: Source account name
  • Date1: Transaction date
  • Description1: Transaction description
  • Amount1: Transaction amount (typically negative for outgoing)

Transaction 2 (Destination) #

  • Account2: Destination account name
  • Date2: Transaction date
  • Description2: Transaction description
  • Amount2: Transaction amount (typically positive for incoming)

Status Information #

  • Status: Current approval status (pending, approved, rejected)
  • Actions: Available actions (approve, reject, delete)

Common Use Cases #

  • Financial Analysis: Eliminate double-counting in cash flow analysis
  • Fraud Investigation: Track money movements between accounts
  • Asset Tracing: Follow funds as they move through different accounts
  • Reconciliation: Ensure all transfers are properly matched

Best Practices #

  • Review All Matches: Don't auto-approve; manually verify each suggested match
  • Check Timing: Ensure transfer dates make logical sense
  • Verify Amounts: Amounts should match exactly or have explainable differences (fees)
  • Document Decisions: Keep notes on why matches were approved or rejected
  • Regular Updates: Re-run detection after adding new transaction data

Export Options #

Export the transfers table to CSV for external analysis or reporting.

Troubleshooting #

Missing Transfers #

  • Check if transactions are in different date ranges
  • Verify account names are correctly identified
  • Use manual creation for complex cases

False Positives #

  • Review transaction descriptions carefully
  • Check for legitimate duplicate transactions
  • Consider timing differences between accounts
Was this article helpful?
Updated on February 15, 2026