Create Allocation
Use Fund Operations → Allocations → Create Allocation to define who participates in an investment, income or expense. The form creates a participation scheme, its participant entries and its covered-item links together.
This is an operating attribution setup. Period profit/loss allocation runs belong in Accounting → Fees & Capital Allocations. Saving this form does not post journals, settle cash, calculate fees or close a period.
Prepare the relationship
Decide what economics are being shared before entering the form. The covered item is an existing Investment, Expense or Income. Participants are the Share Classes or Subscriptions receiving that participation. Their percentages distribute the item’s economics under the scheme from its effective date.
This is why the form needs both participants and covered items. A 100% participant total without the correct item would allocate the wrong subject; the correct item without the intended participants would assign its economics incorrectly. The form creates the relationship, not another underlying cost, cash payment or period allocation result.
Start with the existing source record and intended participants. Check the receiving Entity, currency, economic ownership and effective date. In Data, inspect existing schemes, entries and covered items before creating another scheme. Clear the Entity filter if a relationship seems absent.
The selectors include records across the organization. A selectable record is not proof that it belongs in this allocation. Confirm compatible Entity and currency yourself; do not cover the same economic item twice merely because the form permits another submission.
Enter participants and covered items
Fictional example: Cedarbridge Reporting Class R receives 100% of Reporting administration expense, effective August 1, 2026. This is the separate Reporting Example LP, not the Core Class A example.
- Under Participants, select the actual Share Class or Subscription. Use Add participant for additional owners.
- Enter each Percentage in percentage points: 100 means 100%, not 1%. The participants must total 100%; do not repeat the same participant.
- Under Details, enter a recognizable Name and the Effective date.
- Select the existing Covered item: an Investment, Expense or Income. Use Add item when the same scheme legitimately covers additional records. Recheck the full covered-item set before saving.
The example names the scheme Cedarbridge Reporting Expense Participation, selects Class R #3, enters 100, and covers Expense #2, a USD100 administration accrual in Entity #3. It attributes that existing expense; it does not create another USD100 expense or settle its USD40 remaining payable.
Review the three-table preview
The preview lets you examine the relationship before persistence. Follow the proposed scheme reference from its participant rows to its covered-item rows and verify both sides, not just the row count. Generated IDs can change during Save, so the saved scheme’s actual references must be read back before relying on them.
The native preview shows three proposed rows across three tables: one scheme, one Class R entry and one Expense #2 covered-item link. Preview IDs are provisional; they are not saved record IDs.
Check Allocation Schemes for the name and effective date; Allocation Entries for the participant type/ID, scheme link and percentage; and Allocated Items for the source type/ID and scheme link.
The preview displays the stored allocation fraction 1 for the input 100. The Data table formats that same fraction as 100.00%. These are two representations of the same participation.
Finalized At is automatically populated from the effective date by this form. It is not evidence of independent approval, accounting finalization or a closed period.
If the preview is missing or reports an error, correct the inputs or ask your administrator to inspect the form configuration. Do not use Save to test a failed preview.
Save once and verify the result
Select Save allocation only after the preview matches the intended relationship. Wait for the submission to finish, then open Data and find the named scheme. Verify its actual saved ID across the participant entry and covered item; do not search solely for the preview's proposed IDs.
The fictional demonstration saved Scheme #3, Entry #3 and Allocated Item #3. Entry #3 links Scheme #3 to Class R #3 at 100%; Item #3 links that same scheme to Expense #2. The preview showed #2, demonstrating why you must read back the saved IDs.
Reporting Entity #3 selected. The three tables show the saved Scheme #3, Class R Entry #3 at 100.00%, and Expense #2 covered through Item #3. The separate Core scheme remains unchanged.
The saved rows establish the participation relationship only. Before submitting in a live organization, check with the responsible administrator whether this form also triggers a workflow or agent and what it changes. After saving, verify those actions in their own execution results; the scheme's presence alone does not prove they completed.
If the result is uncertain, check Data and All responses before retrying. Repeating a successful submission can create another scheme; a cleared form is not, by itself, proof of the saved relationships.
For corrections, find the existing records and respect permissions and locks. Use FundOps Recon → Allocation Scheme Integrity and Allocation Coverage to investigate relationships; use the relevant accounting workflow for accounting runs and postings.