Activity Feed Recon
Use Cash & Treasury → Cash Recon → Activity Feed Recon to ask: has each imported bank/broker feed item been represented by the appropriate system account transaction(s)?
A feed item is external-source evidence. An Account Transaction is the system cash record. Account Transaction Links connect the two. This page shows one row per feed item, even when that item has several links.
Read the comparison
Difference = Matched Amount − Feed Amount. Matched Amount sums the allocations on Account Transaction Links. If the relationship is truly one feed to one transaction, a blank allocation can use the transaction's full amount. If either side has multiple links, explicit allocations are required.
- Unmatched: no Account Transaction Link, with an otherwise valid feed amount.
- Invalid: an unusable amount or relationship—for example a missing target/allocation, account/currency mismatch, or an ignored feed that still has a transaction link. Read Recon Issue for the first detected problem; more than one may need correction.
- Mismatched: the links pass those validations but their signed total does not match.
- Matched: this feed-level comparison passes.
- Excluded / Expected No Transaction: the feed is explicitly marked ignored and has no transaction links. Excluded is a recorded decision to review, not automatic evidence that ignoring the item was appropriate.
The absolute Difference must be below 0.000001 to pass. This is stricter than a one-cent tolerance, so a displayed 0.00 can still conceal a failing difference. The source feed's stored Match Status is separate from this calculated Recon Status.
Start with scope and the exception filter
Select Entity and As of Date. Entity follows the feed's legal account; it does not follow a cash split's business owner. The cutoff includes feed items whose Feed Date is on or before that date. Use the table's Filter for Account, currency, issue or other returned fields; Account, Year and Accounting Period controls from other tabs do not scope this check.
The default table filters hide Matched and Excluded. An empty table can mean all returned feed items are hidden—or that no eligible feed data exists.
Fictional Cedarbridge Example Fund LP #1, August 31, 2026: no rows under the two default filters. This is an exception view, not proof that the bank feed is complete.
Open Filter, remove only Recon Status — Not equals — Matched, and choose Apply Filters. Keep the Excluded condition while inspecting matched records; remove it separately when reviewing deliberately ignored feed items. Restore the exception filters afterward.
The same scope now shows three USD feed items: #1 +100,000, #2 −40,000 and #3 −1,200. Each has one transaction link, the same signed Matched Amount and Difference 0. No feed, transaction or link was changed to reveal these rows.
Investigate the exact records
A one-to-one relationship can explain the entire feed amount with one transaction. In a shared relationship, allocations identify which portion of each endpoint is being matched; repeating full amounts would overstate coverage. Follow the explicit link references, not equal numeric IDs, and retain the exact endpoints when a shortcut opens a broader list.
Use Cmd/Ctrl-click on Activity Feed ID to open the typed source record. Where there is exactly one link, the available transaction/link reference can identify that relationship. Multiple links need individual inspection; a blank single-record reference does not mean the links are missing.
Linked Transactions opens Account Transactions to Feed Recon. Keep the feed ID and its linked transaction IDs from this page, then find those exact transactions at the destination. Check the visible filters instead of assuming every displayed row belongs to the selected feed. The default Matched filter can hide the transactions you need; an empty result does not establish that the relationship is missing.
Where available, Open explorer leads to Cash → Transaction Explorer. Confirm the destination's records and scope before tracing Feed → Transaction → Split → Activity → Accounting. This route requires an eligible non-reversed transaction with splits; a missing Explorer link alone is not a failed match.
Resolve at the owning record and recheck
- Confirm the original feed evidence, account, currency, signed amount and intended transaction(s). A matching amount alone does not prove identity.
- Distinguish an ingestion gap, an incorrect transaction, a missing relationship and a wrong allocation. Use the authorized cash/source workflow to correct the actual cause, respecting permissions and locks.
- Refresh this check with the same scope and inspect the exact IDs again. Also check Account Transactions to Feed Recon and Account Transaction Splits Recon before continuing to business settlement and accounting.
A link from a cash split to an income, expense or capital activity is a Cash Split Link, not an Account Transaction Link. Correcting the business association cannot repair this feed comparison. Do not create a duplicate transaction or mark a feed ignored simply to clear an exception.
This table supports row selection for context. It does not accept matches, initiate payments, post journals, lock records or sign off a period.
Understand the date boundary
As of Date limits the parent feed population. The comparison uses current links and counterpart values without a separate linked-transaction date or reversal filter. It is not a frozen historical reconciliation. Reversed transactions can still contribute here, even though the Explorer has narrower eligibility. No FX conversion occurs.
Removing the Matched filter reveals the three passing comparisons in this example. For an entity with transactions but no bank feed, Activity Feed Recon can also be empty because there are no feed items to check. Use Account Transactions to Feed Recon to find transactions without feed support.
Continue with Account Transactions to Feed Recon through the native Cash Recon tabs, or return to the Cash Recon guide above.