Account Transaction Splits Recon
Use Cash & Treasury → Cash Recon → Account Transaction Splits Recon to ask: has each system transaction amount been fully divided across its cash splits?
An Account Transaction records the account movement. Its Cash Splits divide that amount for ownership and business treatment. This control shows one row per transaction and compares the parent amount with the signed sum of its splits.
Understand the comparison
Difference = Sum of Cash Splits − Transaction Amount. The calculation preserves signs. An outgoing −400 transaction needs signed splits totaling −400, not +400.
- Unmatched / Missing Cash Split: a valid nonzero transaction has no split.
- Invalid: the transaction amount is missing/zero, or at least one split amount is missing/zero. Read Recon Issue for the first detected problem; other issues may remain.
- Mismatched / Amount Mismatch: splits exist with usable amounts, but their signed total differs from the transaction.
- Matched: the signed split total covers the transaction to this control's tolerance.
The absolute Difference must be below 0.000001, not within one cent. A two-decimal 0.00 display may conceal a smaller failing amount. Read Currency with the figures; no FX conversion is performed.
A passing total does not validate the split's owner, purpose, activity association, bank feed, GL posting or period sign-off. Equal-and-opposite incorrect split amounts could still net to the correct parent amount; investigate their economic meaning separately.
Start with the exception view
Select Entity and As of Date. Entity follows the transaction's legal account, not its split owners. The cutoff uses the transaction Date. Use the table Filter for Account, Currency or Recon Issue; Account, Year and Accounting Period selections from other tabs do not scope this check.
By default, Recon Status — Not equals — Matched hides passing rows.
Fictional Cedarbridge Onboarding Practice LP #2, October 21, 2026: no exceptions under the default table filter. The three manual transactions still exist.
To inspect them, open Filter, remove the Matched condition and choose Apply Filters. Restore it afterward when returning to the exception queue.
Transactions #6 +USD80, #5 +USD400 and #4 +USD250 each have an equal Sum of Cash Splits, Difference 0 and Recon Status Matched. Only the table filter changed between these two images.
Compare results across controls
These same three transactions are Unmatched in Account Transactions to Feed Recon because no bank feed was supplied. They are Matched here because their split amounts total correctly. Each control is answering a different question.
The USD80 split #6 is unapplied, with no owner or business-activity link. It still contributes USD80 to transaction #6's split total. Its passing arithmetic does not identify the sender or resolve unapplied cash. Continue to the unapplied-cash controls and Integrity to investigate.
Transaction #5 also illustrates the boundary: its USD400 split is linked to Income #2, but the Explorer still shows Missing feed and Missing journal. A transaction's stored Posted status does not substitute for journal evidence.
Follow the exact transaction and all its splits
Cmd/Ctrl-click Account Transaction ID to open that source record. Use Explorer → Open explorer to open its eligible splits in Cash → Transaction Explorer. Confirm the actual transaction and split IDs at the destination before proceeding.
If there are several splits, inspect every split and their combined signed amount. A single Cash Split reference is returned only when exactly one exists; a blank single-reference field on a multi-split transaction is expected.
The Explorer is built around cash splits and excludes reversed transactions. A transaction with no splits, or a reversed transaction, may have no Explorer link here. Its direct source reference remains the investigation path.
The Transaction Explorer guide explains stage expansion and totals. Feed, Transaction, Activity and Accounting rows are context; add the parent split amounts only.
Correct the underlying split and recheck
- Verify the transaction's factual account, amount, currency and date against its evidence.
- Inspect all split records. Identify a missing leg, duplicate leg, wrong sign, or wrong amount before editing. Correct through the authorized cash workflow and respect existing locks and permissions.
- Refresh this check with the same scope. Confirm the exact parent ID, all split amounts and Difference, then review Cash Splits Recon for business links and the relevant bank/GL controls.
Do not change the parent transaction simply to force the total to zero, or place an unexplained residual in a new split without evidence and the appropriate treatment.
As of Date limits parent transaction dates; current splits are rolled up without historical versioning. Reversed transactions remain in the reconciliation population even though the Explorer omits them. The table supports selection for context, not financial execution, journal posting, locking or sign-off.
The unidentified USD80 receipt passes this control because its split equals its transaction amount. Its payer, ownership and application remain separate questions. To consider transaction #5 fully reconciled, also review its bank evidence, business association and accounting.