A lean SG fund's daily book — priced off Yahoo / Google Finance and reconciled to a broker statement. Run the close, then break it — and watch the control that catches it, the hit to investors, and a Claude-drafted memo update live.
Impact on the number & on investors
Exception memo drafted by Claude
A lean MAS-registered manager (RFMC, AUM < S$250M) prices off Yahoo / Google Finance and reconciles a broker CSV; a larger EAM plugs into Bloomberg and a private-bank custody feed. The close reads either. Logos are illustrative source systems — synthetic data, not integrations.
Yellow-bordered cells are editable — book qty, broker qty, the mark (SGX in S$, US in US$), and the one USD/SGD rate. Break the book-vs-broker tie, mis-key a price, oversize a name, or bump the FX rate — then hit Run the close or just watch the controls react.
| Ticker | Name | Ccy | Book qty edit | Broker qty edit | Mark edit | →SGD | Prior | MV (S$) | Recon |
|---|
The broker executed these fills today; the book has to record each one. Toggle "Booked" off to simulate a trade that filled at the broker but never made it into the sheet — and watch the position, the cash, and the reconciliation break. Note the NAV can look perfectly normal.
| Time | Ticker | Side | Qty | Price | Value (S$) | Booked toggle | Broker | Recon |
|---|
Everything recomputes from the numbers you type. The seven controls here are exactly what MAS expects an FMC to run — NAV-calculation and valuation controls, independent custody reconciliation. Detection is deterministic; the memo is the one thing an AI writes. Fictional Singapore fund, synthetic data — a number is guilty until every source ties out.