Cash Splits Recon
Use Cash & Treasury → Cash Recon → Cash Splits Recon to review two independent questions: does each cash split reconcile to its business-record allocations, and does it have a valid stored owner?
This page shows one row per non-unapplied cash split requiring review. It is different from Account Transaction Splits Recon, which compares each transaction with the sum of its splits.
Understand what the queue returns
A cash split has two independent responsibilities: identify the owner of its cash portion and explain that portion through business links. The queue retains a row when either responsibility fails its configured rule. A matched allocation therefore remains reviewable if the saved owner is missing, while a valid owner cannot repair an unsupported business link.
The amount comparison begins from the split. An explicit allocation states how much of that split belongs to the related source; it does not claim the whole source has been settled. This distinction lets a fully allocated payment portion coexist with an unpaid remainder on the business record.
Select Entity and As of Date. Entity follows the transaction's legal account; the cutoff uses the parent transaction's Date. The table's search, Filter and Sort narrow the returned exceptions.
A split is omitted when Recon Status = Matched and Owner Status = Valid. This exclusion happens in the dataset itself. Clearing table filters cannot reveal the complete passing population. Use Cash → Data or Transaction Explorer to inspect those records.
Fictional Cedarbridge Onboarding Practice LP #2, October 21, 2026: no returned exceptions. Splits #4 and #5 still exist with USD250 and USD400 allocated to Incomes #1 and #2 and stored Entity ownership. Split #6, the USD80 unapplied receipt, is excluded from this control and appears in Unapplied Cash Recon.
This empty queue does not establish complete bank evidence, full activity settlement or correct GL posting. It also does not prove that every existing owner is economically appropriate.
Read cash reconciliation and ownership separately
Recon Status tests the split's amount and business links:
- Unmatched / Missing Related Record: no business link for an otherwise usable split amount.
- Invalid: a missing/zero split amount, unsupported/missing target, missing source amount, or an allocation that is required but absent. Recon Issue shows the first detected issue.
- Mismatched / Amount Mismatch: the usable matched total differs from the split by more than 0.01.
- Matched: this amount/link comparison passes. A difference of exactly 0.01 passes this control, unlike the stricter transaction/feed controls.
Supported business targets are Subscription Activities, Investment Activities, Expenses, Incomes and Transfers. Identify the target with both its type and ID.
Owner Status is separate. Valid means the stored Owner Type + Owner resolves to an existing Entity or Share Class. Missing/invalid fields keep the row in this queue even if Recon Status is Matched. Inspect Owner Issue for the specific problem.
Derived ownership is a diagnostic aid from the business relationships; it does not fill the stored owner or prove that an existing owner agrees with the intended economic attribution. Verify that attribution against the underlying records and evidence.
Interpret amounts without overstating the check
Difference = Matched Amount − absolute Cash Split Amount. Matched Amount normally uses the absolute value of the signed total of link allocations. Opposite-signed allocations net before the absolute value is taken.
A single link without an allocation may fall back to its related-record amount. Multiple links on a split require explicit allocations; a non-transfer source shared across links also requires explicit allocations. Inspect every leg rather than copying the full source amount onto each relationship.
An explicit allocation compares the split with its allocated portion, not necessarily the related record's full amount. A USD400 split allocated USD400 to a USD420 income can therefore pass this check while the income remains partly unpaid or the association is wrong. The Integrity guide shows an incorrect target and its correction.
This grid does not display a Currency column. Open the parent transaction to confirm currency; dollar formatting is not FX conversion. The check does not independently validate cash direction, source currency, source date, correct category, full settlement or GL posting.
Trace and correct the owning record
- Retain the Cash Split ID and inspect Recon Issue and Owner Issue separately. Scroll horizontally for Related Types, Owner, Account Transaction ID, Entity, Account and Split Notes.
- Cmd/Ctrl-click a typed reference to inspect its source. Explorer → Open explorer opens Cash → Transaction Explorer for the split; verify the returned IDs. The link can exist even when the Explorer excludes a reversed transaction, so an empty Explorer does not prove deletion.
- For an authorized correction, use Data: Cash Splits owns the amount, purpose and stored owner; Cash Split Links owns Related Type, Related Id and Allocated Amount. Respect permissions and locks.
- Refresh this queue with the same scope, then recheck the source records, Integrity and the relevant feed/GL controls. Disappearance confirms only that the row no longer fails this queue's conditions.
Do not change a factual amount, assign an arbitrary existing owner or create a duplicate receipt to clear a warning. Account Transaction Links belong to feed-to-transaction matching; they do not repair business split links.
The grid is read-only and selectable for context. It does not apply cash, initiate payments, post journals, lock rows or sign off a period. As of Date limits parent dates; classification, owners and links use current state. Reversed transactions remain eligible.
A Matched split remains visible when its stored owner is missing or invalid. Splits #4 and #5 can be absent after their links and owners pass, while the USD80 unapplied split #6 is reviewed separately in Unapplied Cash Recon.