Reconciles book positions against the custodian, listing quantity, value and missing-position breaks
One command in the Fund operations pack, available in the CLI, as an MCP tool and as a JavaScript import: fundops reconcile.
What it needs, and why
Every input is checked before anything is calculated. book is required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
book | yes | What are the book and custodian positions: account, security, quantity and market value? | Breaks are found by matching account and security. |
Requests it answers
- “reconcile against the custodian”
- “why do the positions not match”
- “ledger breaks”
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 reconcile --book '[{"account":"A1","security":"VTI","quantity":100,"marketValue":27500}]' --custodian '[{"account":"A1","security":"VTI","quantity":90,"marketValue":24750}]'
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.