Checks that an LP capital account statement rolls forward, with commitment and fee checks
One command in the Fund operations pack, available in the CLI, as an MCP tool and as a JavaScript import: fundops lp-statement.
What it needs, and why
Every input is checked before anything is calculated. statement is required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
statement | yes | What are the beginning balance, contributions, distributions, income, gains, fees and ending balance? | The roll-forward needs every line. |
Requests it answers
- “does this capital statement tie”
- “audit the LP statement”
- “check my capital account”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Run it
node bin/wealth-skills.js fundops lp-statement --statement '{"beginningBalance":1000000,"contributions":250000,"distributions":100000,"incomeAllocation":20000,"realizedGainLoss":30000,"unrealizedGainLoss":50000,"managementFees":12500,"performanceAllocation":0,"otherExpenses":2500,"endingBalance":1235000}'Limits it inherits from wealth-fund-ops
- Reconciliation matches on account and security exactly as supplied; it does not map identifiers or apply corporate actions.
- NAV tie-out recomputes from the supplied assets and liabilities; it values nothing itself.
- Statement checks confirm the arithmetic and consistency with fund terms, not that the underlying values are right.
- Nothing here posts entries or strikes a NAV. Results go to the administrator or controller.
The full pack, its other 3 commands and what it deliberately leaves alone are on the Fund operations page.