Cash Recon Dashboard

Base Apps → Cash Recon

Start at Cash & Treasury → Cash Recon → Cash Recon Dashboard to decide which cash-record layer needs investigation.

The cash chain has several dependencies: imported evidence must connect to system movements; movements must be fully divided into splits; splits must explain business use and ownership. A dashboard control tests one dependency at a time. Failure points to the layer requiring investigation rather than proving the entire receipt or payment is wrong.

Population is essential to that reading. A feed-side test with no feed rows has no unsupported transactions to discover. The reverse transaction-side test can find them because it starts from the recorded system movements. Similarly, complete split arithmetic does not establish the business purpose or bank support of those splits.

In the Entity #2 example, three system receipts exist without bank-feed support. The feed-side check has nothing to examine, while the transaction-side check identifies the three missing relationships. Read each count with its population before treating Clear as evidence of completion.

The dashboard links to the detail checks. Corrections belong to the underlying record or relationship; return here after the specific issue has been rechecked.

Set scope before reading the numbers

Select Entity and As of Date. Wait for the cards and Control Summary to finish loading. After changing filters, check both sections; if either still shows the previous scope, use the app's top Refresh data button and confirm the results again. A temporary zero while loading is not clearance.

Fictional Cedarbridge Onboarding Practice LP #2, October 21, 2026: three transactions have no feed link, and one unapplied split remains Open. The other controls count no exceptions.

Recon Exceptions shows seven shortcut cards. Control Summary has eight controls: Missing Owners appears only in the table.

Understand the layers

• Feed → Transactions: one bank-feed item compared with its transaction links.
• Transactions → Feed: one system transaction compared with its feed links. These first two controls review opposite sides of the same relationship.
• Transactions → Splits: one transaction compared with its complete split allocation.
• Cash Splits: one non-unapplied split compared with its business-record allocations.
• Missing Owners: those non-unapplied splits checked separately for valid stored ownership.
• Balances: one owner/account/currency group checked for unresolved ownership. This is not a bank-versus-GL balance comparison.
• Transfers: one non-canceled transfer compared with its principal outflow and inflow legs.
• Unapplied Cash: one unapplied split checked for application or a valid offsetting component.

Population is the number of records or groups checked. Exceptions is the number that fail, broken down into Invalid, Unmatched, Mismatched and, for Unapplied Cash, Open. Excluded identifies ignored feed items with no transaction link. Cleared means the unapplied-cash offset check passes.

Clear means zero counted exceptions, including when Population is zero. Counts are not dollars or unique financial events: one record can appear in several control populations and fail more than one control. Do not add these counts to estimate cash exposure.

In this example, Feed → Transactions is Clear with Population 0, while Transactions → Feed has 3 Unmatched. The three recorded receipts are USD250, USD400 and USD80, but none has a feed link. Complete split allocation and the corrected USD250/USD400 business links do not resolve that missing evidence. The USD80 unapplied receipt counts as one Open exception.

Activities without any cash split—such as the separate fictional USD420 income—are not an additional population here. Review activity settlement in FundOps and Cash & Activity as well.

Follow a control to the records

Use the control name to choose the comparison, then inspect its actual issue and typed source references. The same split can fail ownership and application checks, while another control counts its parent transaction. Several counts can therefore describe one underlying movement, and fixing one relationship can change more than one count.

Click a card or linked Control name, then verify the installed app, native tab, Entity, cutoff and table filters.

Clicking Transactions → Feed in Control Summary opened Account Transactions to Feed Recon with the same Entity and cutoff. Transactions #6, #5 and #4 show Missing Activity Feed Link. This verifies the three-record drilldown in this example.

Use the relevant tab guide to interpret the reason, then trace the split in Cash → Transaction Explorer. For the missing feed links, follow Account Transactions to Feed Recon; for the parked receipt, follow Unapplied Cash Recon.

Cash Splits and Missing Owners both open Cash Splits Recon. Their counts are independent, while the destination can show the combined cash/owner exception queue; inspect Recon Status and Owner Issue separately rather than expecting either count to equal all displayed rows.

Recheck scope when counts differ

Details can retain passing records, saved table filters or a different exception population. Balances shows all eligible groups; Unapplied Cash Recon can also show Cleared rows.

There is a current date-rule difference: Dashboard Transfers prioritizes Requested → Settled → Expected Settle Date; Transfers Recon prioritizes Settled → Expected Settle → Requested Date. A transfer can therefore enter the dashboard before appearing in the detail at the same cutoff. Inspect its dates and explain the population difference; do not alter factual dates to force agreement.

Most other cutoffs follow parent feed/transaction dates, while links and ownership use current records. Reversed transactions remain included in these dashboard calculations. Tolerances are control-specific; the Cash Splits one-cent tolerance is not universal.

Complete the investigation

After an authorized source correction, refresh the detail and dashboard under the same scope and verify the underlying records. Use Bank Tie-Out separately for bank → system cash → GL evidence. These eight controls do not include Bank Tie-Out, Data Locks or account/period sign-off.

This dashboard is read-only, with control-row selection disabled. It does not match cash, execute payments, post journals, lock records or approve a close.

A control can show Clear with Population 0 because it had no records to check. The USD80 receipt can fail more than one control, so adding exception counts does not give the number of distinct transactions or the cash amount at risk.