Transfers Analysis
Automatically detect and match inter-account transfers to eliminate double-counting in cash flow analysis, approve, reject, or manually create matches.
Last updated
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
- Navigate to Transfers: Open the Advanced Analysis tab and select the Transfers sub-tab.
- Automatic Detection:
- The first time you open Transfers on a project, DocuClipper looks for matching pairs on its own and the table fills in when it finishes. Click Detect Transfers to look again after adding statements.
- A pair is approved automatically only when it is certainly money moving between one owner's accounts: the two amounts are exactly equal and opposite, both post on the same day, and both accounts have the same holder on the Accounts tab. Every other pair (a day apart, a different amount, different owners, or an account with no holder set) is listed as Waiting for review for you to approve or reject. DocuClipper never guesses an owner, so set each account's holder on the Accounts tab if you want same-day transfers between them approved for you.
- A pair you already approved or rejected keeps your decision when you detect again.
- Review Matches:
- View the results table showing paired transactions
- Check accounts, dates, descriptions, and amounts. An account shows the name you gave it on the Accounts tab, or the last four digits of its number (for example …9797); hover over it to see the full value.
- Review the match status (Waiting for review, Approved, Rejected). Status and the Approve / Reject buttons stay pinned at the right edge of the table while you scroll the other columns.
- Approve or Reject:
- Above the table, a line says how many pairs are waiting for review. Approve all approves every pending pair at once, once you have looked them over.
- Click Approve for a pair that is a real transfer between the client's own accounts
- Click Reject for a pair that is not a transfer. Rejected pairs are hidden so the table lists the transfers.
- Change your mind: Every decision can be reversed. An approved pair has a Reject button. To bring back a rejected pair, turn on Show rejected above the table (it shows how many pairs are rejected) and click Approve on that row.

Approved pairs are what the rest of Advanced Analysis treats as transfers between the client's own accounts: Recurring and Flow of Funds leave both sides out, and the Report's Transfers card counts them as approved. The card's Waiting for review number is the pending pairs this tab lists.
Manual Transfer Creation
- Open Creator: Click Add Transfer to expand the manual creation interface.
- Select Transactions:
- Use the left table to select the source transaction
- Use the right table to select the destination transaction (it must be a different transaction on a different account)
- Create the transfer: Click Create Transfer to link the selected transactions.

Understanding the Results Table
Each row pairs two transactions. The (A) columns are one side of the transfer and the (B) columns are the other:
- Account (A): First account: the name you gave it on the Accounts tab, or the last four digits of its number
- Date (A): Transaction date
- Description (A): Transaction description
- Amount (A): Transaction amount, with cents (typically negative for outgoing)
- Account (B): Second account, shown the same way
- Date (B): Transaction date
- Description (B): Transaction description
- Amount (B): Transaction amount (typically positive for incoming)
- Status: Waiting for review, Approved or Rejected. Rejected pairs show only while Show rejected is on.
- Actions: Approve and Reject for a pair waiting for review, Reject for an approved one, Approve for a rejected one.
Status and Actions stay pinned to the right edge of the table, so you can approve or reject a pair without scrolling sideways.
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