Transfers Recon
Use Cash & Treasury → Cash Recon → Transfers Recon to compare each transfer with the cash splits representing its outflow and inflow.
A Transfer describes the intended movement between accounts. Its two cash legs are linked cash-split records. This read-only reconciliation checks those relationships; it does not send money or execute the transfer.
The transfer header describes one intended movement between accounts. Its outflow and inflow are two representations of that movement at the source and destination. Both must be present and each must cover the header amount; adding the legs together would double the intended transfer.
This is why the check keeps a separate Difference for each side. One side can be correct while the other is absent or misallocated. The stored Transfer Status describes workflow progress; the recalculated Recon Status describes the linked cash evidence under this control.
Choose the scope and inspect filters
Select Entity and As of Date. Entity follows the transfer header. The cutoff uses the first available date in this order: Settled Date → Expected Settle Date → Requested Date. Canceled transfers are excluded.
The saved table is configured to hide Recon Status = Matched. Inspect Filter in your current session; remove that exclusion if present when you want to inspect passing rows. Search and other table filters can also narrow the displayed population.
Fictional Cedarbridge Example Fund LP #1, August 31, 2026: no transfer records are displayed, and no table-filter condition is active in this screenshot. An empty view does not demonstrate transfer settlement or a passing comparison.
An empty table means no rows are displayed under the current scope and table state. Check dates, Entity, canceled status and filters before interpreting it as a clean control.
Read both legs separately
For a populated row, compare Transfer Amount and Currency with Outflow Linked, Inflow Linked, each Difference, From Account and To Account. Recon Issue explains the first detected break.
Each Difference = linked leg amount − Transfer Amount. Linked amounts are positive magnitudes; the underlying outflow cash split can correctly be negative.
- Unmatched / Missing Both Cash Legs: neither principal leg is linked.
- Mismatched: a leg is missing or a leg total differs, unless an earlier Invalid condition applies.
- Invalid: unusable amounts, unexpected roles, missing required allocations, negative explicit allocations, or account/currency conflicts.
- Matched: both usable principal legs pass the account/currency/allocation checks and each absolute difference is less than 0.000001. This is stricter than the 0.01 tolerance in Cash Splits Recon.
Transfer Status is the stored business status, separate from the calculated Recon Status. Matched does not establish bank execution, approval, ownership continuity, GL posting or period sign-off.
Understand links before changing them
Cash Split Links identifies the target as Transfers plus its Related Id. A recognized stored principal-outflow/inflow role takes precedence; otherwise the account relationship can determine the leg. Same-account transfers use the split's sign.
A split with one business link can fall back to its absolute split amount when Allocated Amount is blank. Shared splits require explicit allocations. Enter transfer-link allocations as positive magnitudes; do not copy a negative cash outflow into Allocated Amount.
Scroll for leg link counts, dates, cash-split IDs and transaction references. A single leg reference is shown only when that leg has exactly one link. Multiple links can be valid, so a blank single-reference field does not by itself mean the leg is missing.
Trace and resolve an exception
- Open Transfer ID and compare intended amount, currency, accounts and dates with the supporting evidence.
- Inspect each linked cash split and parent transaction. Where Explorer → Open explorer is available, it targets Cash → Transaction Explorer with the transfer context; verify the returned IDs and scope. Otherwise open Cash and investigate the legs directly.
- Use Transfers in Cash for the intended transfer record, and Data for authorized changes to splits and business links. Respect permissions and locks.
- Refresh the same scope and inspect both differences, Recon Issue and actual source records. Continue to bank evidence and accounting checks; disappearance from an exception view is not proof of settlement.
The cutoff scopes transfer headers; linked leg totals use current links and can include later-dated or reversed transactions. Explorer availability separately requires an eligible, non-reversed linked transaction through the cutoff. Do not assume all these surfaces show identical populations.
Do not manufacture a missing bank leg, duplicate a transaction or change a factual amount to clear the check. A transfer between accounts also does not automatically prove a change of economic owner.
Transfer Status records the business status; Recon Status is recalculated from the linked cash legs. They can differ. A blank single-split reference can also be valid when a leg has multiple links—inspect the links before concluding that a cash leg is missing.