Onboarding

Base Apps → Subscriptions

A new subscription needs review before it can be accepted and funded. Use Fund Operations → Subscriptions → Onboarding to find the participation in the configured lifecycle queues and inspect its recorded document, compliance and funding reviews.

Each queue shows the same editable subscription master according to its saved Stage. Moving a record into review changes that field; the evidence and review outcomes must still be checked separately.

Find a subscription in the right scope

A queue is a view of subscriptions selected by saved lifecycle fields. Moving the same subscription to another Stage changes where it appears; it does not create a replacement participation. This lets reviewers keep a single identity while work progresses from submission toward acceptance and funding.

Queue placement and review completion answer different questions. The first says where the work is routed; the second requires the actual document, compliance or funding evidence. An active subscription can leave these queues while still remaining available in Data.

Select Entity, then narrow by Investor, Subscriber or Share Class when needed. Entity follows the subscription's receiving Share Class. Check these relationships before assuming a subscription is missing.

The four sections are Submitted, In Review, Accepted and Awaiting Funding. Expand the section you need; collapse the others to make room. These cards are work queues within the tab, not additional app pages.

Membership follows the saved Stage field. Subscriptions whose Status is Active or Transferred are excluded even when their Stage matches a queue. Document, compliance and funding fields do not themselves calculate queue membership.

This explains why the active USD100,000 Core Subscription from the other examples is in Data but absent here. Its absence does not prove document or compliance reviews were completed. Clear filters and inspect the existing record in Data before creating a replacement.

Read the onboarding example

Entity2 Cedarbridge Onboarding Practice LP and Class B — Onboarding Practice selected. Submitted is expanded; the other three queues are collapsed.

The fictional Cedarbridge Onboarding Practice Subscription #2 belongs to the selected Class B and has proposed Commitment Amount USD25,000, Commitment Currency USD, Status Pending and Stage Submitted. Its legal subscriber is Cedarbridge Example Holdings Ltd.

This is separate from the funded Entity 1/Class A example. It has no signed agreement, completed review evidence, funded activity, cash settlement or journal. Effective and submission dates are blank. A row in Submitted does not prove that a document was submitted.

Review the different fields

Treat each review field as a claim about a particular task. A document status concerns evidence review; compliance fields concern the named checks; funding status concerns funding. No single Stage change proves all of those claims. Read their evidence separately before recording an outcome or advancing the subscription.

Scroll horizontally to inspect Status, Stage, Onboarding Status, Documents, Compliance and Funding Status. Open supported references or the relevant record's document control to inspect actual evidence, subject to your permissions.

Stage places the subscription in a queue. Status describes the master record and can remove it from these queues. Onboarding Status is another stored review field; it is not interchangeable with either.

Documents shows subscription-document review, supporting-document review and signatures statuses. Compliance shows the recorded statuses for KYC (Know Your Customer, or customer due diligence), AML (anti-money-laundering review) and Blue Sky filings (filings under U.S. state securities laws). The group labels organize related columns; their key review fields remain visible within the groups. A blank field is unresolved information, not an approval.

Record review outcomes only when supported by your organization's evidence and authorized reviewers. Neither a colored label nor a manually changed Stage is independent proof that a review occurred. Funding Status must likewise be checked against actual contribution and settlement records.

Move the same record into review

When authorized to move a subscription into review:

1. Confirm the subscription ID, subscriber, receiving class and current Stage.
2. Scroll to its Stage cell, double-click to open its editor and choose In Review. This dropdown saves the selected value; wait for the update to finish.
3. Refresh the app to update the other queues. Confirm the same ID and commitment under In Review and its absence from Submitted.
4. Reopen or reload the view to verify the change persisted. Review fields and underlying evidence remain separate.

Same fictional subscription #2 after its saved Stage change and a page reload. Submitted is collapsed and In Review is expanded. The amount and identity are unchanged.

Same In Review row after horizontal scrolling: Stage is In Review while the document-review and signatures fields remain blank. Identity and commitment are shown in the preceding image.

Farther right on that same row, KYC, AML, Blue Sky filing and Funding Status remain blank. Scrolling has not changed the selected Entity, class or subscription.

This action changes the existing subscription's Stage. It does not sign a document, perform KYC/AML checks, grant portal access, receive funds, create contribution activities or post journals. The example stops at In Review; it does not simulate acceptance or funding.

Use Data to correct an evidenced master-record error or create a genuinely missing subscription. Choose the actual Subscriber, receiving Share Class, currency and appropriate Stage explicitly; do not assume inserting into a particular queue supplies all lifecycle fields automatically. Respect permissions and row locks.

Continue to funding and accounting

When a subscription is accepted or awaits funding, use its activities and supporting evidence to determine the next task. Continue to Activity for dated events and notice references, and Record Explorer for cash settlement and accounting links. The Accepted queue does not confirm funding; Awaiting Funding is not a calculated bank shortfall.

Use FundOps Recon for notice/activity integrity and Cash Recon for settlement exceptions. A contact association or Stage change does not invite an investor or enable portal access; those are separate actions in Investor Profiles.

Row selection makes supported actions/context available; selecting rows does not execute those actions. Review any external notification or access action separately before proceeding.