Subscription Transfer Integrity
Use Fund Operations → FundOps Recon → Subscription Transfer Integrity to investigate the configured continuity checks for an existing transfer of subscription interests. This is different from Cash → Transfers, which concerns fund-owned cash accounts.
This tab reviews records; it does not create, approve or settle a transfer.
Understand the empty example
A transfer changes the holder of an existing fund interest. The source subscription preserves the original history. For a partial transfer, the target carries the transferred portion and a residual successor carries the retained portion; the original is closed rather than rewritten as though it had always been smaller.
That continuity is what the checks examine: predecessor and successor relationships, lifecycle dates, transferred and retained commitment, transfer-derived activities and eligible capital-account effects. A transfer amount describes an interest carried forward, not a new contribution into the fund. The example below is empty and demonstrates none of those execution steps.
Fictional organization, August 31, 2026, Entity cleared. No matching transfer-check rows were returned. No transfer execution or settlement is demonstrated by this screenshot.
Entity is derived from the source Subscription's Share Class. Clearing Entity broadens that scope. As of Date includes transfers effective on/before the cutoff. Effective Date is required for native Subscription Transfers.
The source population contains Pending Approval, Approved and Settled transfers. Other workflow statuses and future-effective transfers are outside this population. The result uses current stored transfer status and linked records; it does not reconstruct their historical state.
When rows are available, the configured default filter hides Recon Status = Matched. Check Filter, search text, Entity, date and the transfer's own status before interpreting No results. If the Not equals Matched condition is present, remove it and apply the filter to inspect passing checks; restore it for exception review.
No results means no displayed checks under the current population and filters. It does not prove a transfer was approved, executed or fully reconciled. The Dashboard can also show Clear with a zero population.
Read a control row, not a transfer total
Each check compares a particular expected consequence with the recorded consequence. One transfer therefore needs several rows: correct successor identity cannot establish correct commitment, and correct commitment cannot establish capital-account continuity. Read Expected and Actual for the named control rather than adding repeated transfer amounts.
A populated table has one row per transfer control check, not one row per transfer. One transfer may generate many rows. Checks shared by related transfers are shown on the first transfer in their group, rather than repeated for every sibling transfer.
Read Subscription Transfer, Control, Expected, Actual, Recon Status and Severity together. Several exceptions can require one source correction. Transferred amounts repeat across check rows; never sum them as separate commitment or capital movements.
Use the Subscriptions header group for Source, Target and Residual Subscription references. Source remains visible when collapsed. Use Transfer Details for status, scope, effective date, transferred commitment and capital-account value; Transfer Status remains visible when collapsed.
These controls and groups describe the populated table. The empty example has no record rows to expand.
Distinguish check status from execution status
Execution status determines which conditions the control exercises. Some successor and capital checks become applicable only after settlement. Their lack of an exception beforehand is not evidence that settlement has happened. Read Transfer Status first, then interpret each check under the rules for that stage.
- Invalid: the particular configured check failed. Compare Expected with Actual and inspect its source records.
- Open: the workflow-status check found an Approved transfer effective by the cutoff that has not reached Settled. This is not an accounting-period status.
- Matched: that check's exception condition did not trigger.
Many successor, lifecycle, activity and capital checks apply only to Settled transfers. Before settlement they can display Matched even though those completion conditions have not been exercised. Pending Approval is not itself flagged by the workflow-status check. Matched checks therefore do not prove approval or settlement; read Transfer Status independently.
Severity helps prioritize a failed check. A displayed severity on a Matched row is not, by itself, an exception.
Follow the continuity being tested
A partial transfer keeps the original Subscription as history and carries the two resulting interests in successor records: the transferred share in the Target and the retained share in the Residual. The controls check that those records continue the original participation without turning transferred capital into a new fund contribution. This describes the transfer model; the empty screenshot above demonstrates no transfer execution.
For a settled transfer, investigate the relevant families:
- Successors and lineage: target Subscription, and residual Subscription for a partial transfer, with the expected Share Class and predecessor links.
- Lifecycle: original source marked Transferred and closed on the effective date; successors Active where required.
- Commitment: target commitment agrees with the transferred commitment, residual agrees with the retained amount, and currency agrees with the source.
- Transfer activities: source commitment adjustment and successor commitment activities point back to the transfer with the expected signs and amounts.
- Capital accounts: the configured checks compare successor account availability, source close date and recorded transfer-out/transfer-in capital values.
The partial-transfer model preserves the original Subscription as history: it closes the original and carries the transferred and retained slices in target and residual successors. Do not reduce the original historical commitment merely to clear a check.
Commitment continuity and capital-account value are different measurements. Transfer-derived commitment activities express ownership continuity; they are not new fund contributions or distributions. Investor-to-investor consideration is not a fund cash receipt or payment.
These checks are not exhaustive approval of every economic, document or pro-rata condition. Some capital checks only apply when a source capital account exists, so Matched is not universal proof of capital-account completeness.
Correct the owning workflow safely
Open the Subscription Transfer reference and the specific Source, Target or Residual Subscription reference available in the row. Compare the issue with the transfer evidence and the authorized workflow's execution history.
For an Open or incomplete transfer, use the organization's authorized approval/settlement workflow and inspect any failed steps. Do not manually mark a transfer Settled, create duplicate commitment activities, or move capital values merely to make this grid pass. If that workflow is unavailable, ask the responsible administrator to enable or repair it.
Material corrections to settled history require the appropriate amendment/reversal process and review, rather than rewriting the original subscription or deleting its provenance.
Refresh the check in the same scope after an authorized correction and verify the particular checks and Transfer Status. This tab does not replace bank reconciliation, document review or accounting close controls. Row selection, when rows exist, supplies context for an available assistant workflow and does not authorize execution.