Activity
Use Fund Operations → Subscriptions → Activity to inspect or maintain the event ledger for subscriptions: commitments, notices, contributions, distributions and other recorded categories. It edits the same underlying activity records that appear in Data → Subscription Activity.
This is a source-event ledger. Use Record Explorer when the question is how an event was settled or posted.
Scope the ledger
Choose Investor, Subscriber, one or more Subscription(s) and an optional From/To date range. The date range filters Event Date, including its endpoints; either date can be used alone.
Selecting explicit Subscription(s) takes precedence over the Investor filter in this dataset. The Subscriber filter still applies. Verify the selected subscription itself rather than assuming Investor will further restrict an explicit subscription selection.
This tab has no Share Class, Entity or As of Date selector. Its date range is not an as-of valuation: it restricts the event rows shown. Do not assume filters carried in the browser URL from another tab apply here.
Read commitments, requests and funding
Read the ledger as a sequence of events affecting a participation. A commitment records the undertaking to participate. A capital call records the request for funding, while a contribution records the funding event. Because these categories answer different questions, their values cannot be added as though every row were another cash receipt.
The event date places each record in the operating history. To establish cash receipt, inspect the contribution’s linked split and its parent transaction. This is why a subscription contribution can carry a negative source value while its associated bank movement is positive.
Native Activity tab with Cedarbridge Core Subscription selected and July 1–31, 2026 entered. The ledger shows three fictional USD events in date/ID order.
On July 1, the Core subscription records a +USD100,000 Commitment and a −USD100,000 Capital Call. The commitment establishes the recorded participation; the call records the funding notice. On July 5, a separate −USD100,000 Contribution records the funded event and references that call.
The next question is whether cash arrived. The contribution's source value is negative, while its linked bank receipt is +USD100,000. These signs describe different records; compare the category and relationship before changing a sign or adding amounts.
A simple sum across these categories is not net settlement or paid-in capital. Keep notices, funded activities and valuations distinct in an analysis.
Follow the notice and source
Notice Id is an event-to-event relationship: it identifies the call or distribution notice to which the selected activity responds. Source Type and Source Id identify a separate originating record when used. A notice can therefore be traceable even when the optional source pair is blank. Neither relationship supplies the bank movement or the uploaded evidence file.
Same rows after horizontal scrolling. Under Traceability, the contribution references Notice #2. The leftmost subscription text is partly offscreen; the first image identifies the selected subscription.
Expand Traceability to inspect Notice Id, Source Type and Source Id. Notice Id links an activity to its notice in the subscription-activity table. Source Type and Source Id provide a different source relationship when populated; identical numeric IDs in different tables do not identify the same object.
In this example the contribution's Notice Id is populated, while Source Type/Id are blank. That does not erase its notice relationship. A notice reference also does not establish that the amount is settled or posted.
Expand Settlement for due and expiration dates; the collapsed group retains Settlement Method. Event Date, due date and expiration date serve different purposes. A blank settlement method does not by itself prove missing cash, and an in-kind method describes a non-cash settlement rather than supplying a settlement date.
Edit the actual event, not a copy
Use the available cell editor to correct an evidenced source error, subject to permissions and locks. The Subscription reference identifies the owning master. Check category, value, currency, date, notice and any source relationship together before saving.
Use Insert only when the activity is genuinely absent. First check this ledger, the Data table, filters and existing source document or notice. Do not create a second contribution because its cash link is missing.
After saving, refresh and verify the same event. Changes here also affect the Data tab and downstream consumers of that activity. Attaching a document, selecting a row or setting a method does not itself create a cash settlement or a posted journal. Do not bypass a lock to make an accounting correction.
Resolve the next question
For a missing event, check the subscription selection, date range and source records first. For a disputed notice relationship, inspect the notice's subscription, category, date, currency and amount before changing the reference.
For an existing event without cash or accounting, open Subscriptions → Record Explorer, choose Subscription Activities in Table and select the event in Record / ID. Inspect Cash Splits, Journal Entries and Journal Lines. Use FundOps Recon for source/notice integrity checks and Cash Recon for amount or settlement-link exceptions. Keep unpaid events visible so the missing link can be investigated.