6.2 Feed Categorization: Match, Add, Transfer, Split & Bank Rules Engine

Feed Categorization: Match, Add, Transfer, Split & Bank Rules Engine

Quick Answer: In the QuickBooks Online For Review queue, every downloaded bank transaction requires an operational decision: Match (links the bank record to an existing transaction like an invoice payment or bill payment to avoid duplication), Add (creates a new transaction directly in the register), Transfer (records fund movements between two balance sheet accounts without touching the P&L), or Split (apportions a single transaction across multiple accounts, classes, or jobs). The Bank Rules Engine automates these assignments using customizable conditions (Bank Text, Description, Amount). While rules dramatically accelerate review velocity, the Auto-add setting must be deployed with extreme caution to prevent erroneous entries from bypassing human verification.

---

The For Review Queue: Core Operational Actions

When transactions download from connected bank and credit card feeds, they reside in the For Review tab as unposted staging data. To move them into the general ledger register, the user must select one of four primary actions.

                     [ Downloaded Feed Transaction ]
                                    │
             ┌──────────────────────┴──────────────────────┐
             ▼                                             ▼
  [ Transaction Exists in QBO? ]               [ New / Unrecorded Activity ]
             │                                             │
             ├──────────────┐               ┌──────────────┼──────────────┐
             ▼              ▼               ▼              ▼              ▼
        [ MATCH ]      [ MATCH ]         [ ADD ]      [ TRANSFER ]    [ SPLIT ]
       (1-to-1 Match) (1-to-Many)     (Single Cat)   (BS to BS Only) (Multi-Cat/Class)
             │              │               │              │              │
             └──────────────┴───────┬───────┴──────────────┴──────────────┘
                                    ▼
                     [ General Ledger Register Updated ]

---

1. The MATCH Action

The primary objective of bank feeds in an accrual-based or workflow-driven bookkeeping system is matching, not adding.

How Matching Works

QuickBooks Online continuously scans the general ledger for un-reconciled transactions whose dates, dollar amounts, and payee profiles align with the downloaded bank transaction. When QBO detects a candidate, it displays a green banner in the Action column stating "1 match found".

Transactions eligible for matching include:

• Money In: Receive Payment entries, Sales Receipts, Bank Deposits, open Customer Invoices (in certain automated matching workflows), and Customer Credit Memos.
• Money Out: Bill Payment checks, electronic Bill Payments, Expenses, manual Checks, Payroll liability disbursements, and Vendor Credits.

The Mechanics of Confirming a Match

When the user clicks Match:

1. QBO does not create a new general ledger transaction.
2. It links the bank transaction's digital clearing footprint directly to the existing transaction.
3. In the register, the transaction's reconciliation status automatically updates from blank to "C" (Cleared).
4. Income and expense accounts remain completely unaffected because they were already recognized when the original transaction (e.g., Invoice or Bill) was recorded.

Advanced Matching: 1-to-Many and Many-to-1 Matches

Real-world banking frequently involves bundled or grouped deposits that do not correspond to a single transaction in QBO:

• 1-to-Many Match (Grouped Customer Payments): A retail client deposits $2,500.00 cash/checks into the bank. In QBO, three separate customer payments were recorded to Undeposited Funds ($1,000, $1,000, and $500). When the $2,500 deposit appears in the feed, clicking on the row and selecting Find other matches reveals the match slider. The user selects all three individual payment records, verifying that the combined total equals $2,500.00 exactly.
• Resolving Small Differences (Match with Adjustment): If a customer pays an invoice for $500.00, but the bank feed shows $485.00 due to a $15.00 incoming wire fee, the user opens the match screen, selects the $500.00 invoice, and utilizes the Resolve difference section to add a -$15.00 line item categorized to Bank Service Charges.

[!IMPORTANT] The Catastrophic "Duplicate Revenue" Trap: If a user records a customer invoice and subsequently records a Receive Payment to the bank account, clicking Add (instead of Match) on the resulting bank feed deposit creates a second, independent deposit in the register. Result: Revenue is doubled on the Profit and Loss statement, and the original payment remains forever uncleared in the register, distorting Accounts Receivable and cash balances!

---

2. The ADD Action

The Add action creates a brand-new transaction directly from the bank feed into the general ledger register.

Appropriate Use Cases for Add

Add should be reserved strictly for transactions that have not been pre-recorded elsewhere in QBO, including:

• Point-of-sale debit card purchases (gas stations, coffee shops, hardware store runs).
• Direct bank fees, wire charges, and merchant service fees.
• Automatic electronic debits for recurring utility bills (where no Accounts Payable bill was entered).
• Interest earned on savings or money market accounts.

Required Data Fields for Clean Categorization

When adding a transaction, the user must populate the following metadata fields:

1. Payee: The Vendor (for money out) or Customer (for money in). Mandatory Best Practice: Always assign a payee. Adding expenses without a vendor breaks Form 1099-NEC/MISC tracking and makes vendor expense reporting useless.
2. Category: The specific Chart of Accounts account (Expense, Cost of Goods Sold, Fixed Asset, Income).
3. Description / Memo: Contextual notes explaining business purpose.
4. Class & Location: Tracking tags for segmented departmental or divisional reporting (if enabled in Account and Settings).

---

3. The TRANSFER Action

The Transfer action records an internal balance sheet movement between two financial accounts.

Permissible vs. Impermissible Uses of Transfer

The Dual-Feed Transfer Workflow

When funds move between two connected accounts (e.g., a $1,000 transfer from Checking to Savings):

1. In the Checking account feed, the $1,000 outflow appears. The user selects Transfer and designates Business Savings as the destination account, then clicks Transfer.
2. QBO posts the transfer to both registers immediately.
3. In the Savings account feed, the $1,000 inflow appears. QBO automatically recognizes the pre-existing transfer and changes the action to Match!
4. The user simply clicks Match in the Savings feed.

Critical Warning: If the user clicks Transfer or Add in both accounts, two separate transfers are posted, creating four general ledger legs and doubling the transaction!

---

4. The SPLIT Action

When a single bank transaction encompasses multiple expense categories, departmental classes, or billable customer jobs, the user must use the Split feature.

Split Configuration Mechanics

Clicking on a transaction row in For Review reveals the Split button next to the category field. The split drawer supports up to dozens of individual distribution lines.

Practical Splitting Scenario

A business owner charges $450.00 at Home Depot on the corporate debit card. The receipt represents three distinct operational expenditures:

• Line 1: Replacement circular saw blades (Tools & Equipment - Expense): $150.00 (Class: Field Operations)
• Line 2: Lumber and fasteners for the Smith Residence remodel (Job Materials - Cost of Goods Sold): $250.00 (Customer: Smith, John; Checkbox: Billable with a 15% markup)
• Line 3: Cleaning supplies and trash bags for the main office (Office Supplies - Expense): $50.00 (Class: Administration)

$\text{Line 1 } (\$150.00) + \text{Line 2 } (\$250.00) + \text{Line 3 } (\$50.00) = \text{Total Transaction } (\$450.00)$

The split interface maintains a running Amount to allocate counter. The user cannot save or add the transaction until the unallocated balance reaches exactly $0.00.

---

The Bank Rules Engine

Bank Rules allow firms to automate repetitive transaction categorization, dramatically reducing manual bookkeeping hours. Rules are accessed via Transactions > Bank rules (or Bookkeeping > Rules).

┌─────────────────────────────────────────────────────────────────────────────┐
│ Create Rule                                                                 │
├─────────────────────────────────────────────────────────────────────────────┤
│ Rule Name: Adobe Creative Cloud Software Subscription                        │
│ Apply to: [ Money out ] in [ All bank accounts ▾ ]                          │
│                                                                             │
│ Conditions: When a transaction matches [ ALL ▾ ] of these conditions:       │
│   [ Bank text   ▾ ] [ Contains        ▾ ] [ ADOBE *CREATIVE CLOUD ]         │
│   [ Amount      ▾ ] [ Is exactly      ▾ ] [ 59.99                 ]         │
│                                                                             │
│ Transaction Details:                                                        │
│   Transaction type: [ Expense   ▾ ]                                         │
│   Payee:            [ Adobe Systems Inc.           ▾ ]                      │
│   Category:         [ Software & Subscriptions     ▾ ]                      │
│   Class:            [ Overhead / Admin             ▾ ]                      │
│                                                                             │
│ [ ] Auto-add (Automatically confirm transactions this rule applies to)      │
└─────────────────────────────────────────────────────────────────────────────┘

Anatomy of a Bank Rule

1. Scope & Direction

• Rule Name: A clear, descriptive title.
• Direction: Money in (deposits, credits) or Money out (charges, checks, debits).
• Target Accounts: Can apply to All bank accounts or be restricted to specific accounts (e.g., applying exclusively to the corporate Visa).

2. Condition Logic: ALL vs. ANY

• Matches ALL (AND Logic): Every single specified condition must be met simultaneously for the rule to trigger. (Recommended for high precision).
• Matches ANY (OR Logic): If any single condition is met, the rule triggers. (Useful for capturing multiple vendor variations, e.g., "Bank text contains CHEVRON" OR "Bank text contains EXXON").

3. Condition Criteria & Operators

Rules evaluate transactions against three primary data fields:

• Bank Text vs. Description (Critical Exam Distinction):
  • Bank Text: The raw, unedited electronic data string transmitted directly by the bank clearing network (e.g., TST* THE COFFEE BEAN #412 LOS ANGELES CA). It is permanent and uncleaned.
  • Description: QuickBooks Online's simplified, algorithmically interpreted version of the payee string. Because QBO algorithms may misinterpret descriptions, using Bank Text is far more robust and reliable when constructing rules.
• Amount: Can evaluate amounts using operators: Is exactly, Is greater than, or Is less than. Combining amount conditions prevents rules from misclassifying unusual charges.
• Operators: Contains, Does not contain, Is exactly.

4. Action Assignment

Once triggered, the rule applies pre-set transaction details:

• Transaction Type: Expense, Transfer, Check, or Deposit.
• Payee: Pre-populates the vendor or customer.
• Category: Pre-populates the general ledger account.
• Tags / Class / Location: Automatically applies dimensional reporting metadata.

---

The Auto-Add Toggle: Benefits vs. Severe Audit Hazards

At the bottom of the rule creation screen lies the Auto-add switch: "Automatically confirm transactions this rule applies to."

How Auto-Add Operates

• When Auto-Add is OFF: Downloaded transactions matching the rule display a green "Rule" badge in the For Review queue with all fields pre-filled. The transaction remains in the staging area until a human bookkeeper reviews and clicks Add.
• When Auto-Add is ON: Downloaded transactions matching the rule completely bypass the For Review queue. They are immediately posted to the general ledger register without human review and move straight to the Categorized tab.

Auto-Add Risk Governance Matrix

Rule Priority Ordering

QuickBooks Online evaluates rules in sequential order from top to bottom (Priority 1, Priority 2, Priority 3...):

• If a transaction matches multiple rules, only the highest-priority rule executes.
• ProAdvisors can reorder rules by clicking the reorder handle and dragging rules up or down in the Bank Rules list.
• Structuring Strategy: Place narrow, highly restrictive rules at the top of the list (e.g., "Bank Text contains Chevron AND Amount > $150" coded to Equipment Fuel), and place broad catch-all rules lower down (e.g., "Bank Text contains Chevron" coded to Auto Fuel).