Fund accounting platform integration.
Patterns worked through during fund-accounting platform rollouts. Described as reusable approaches, with no vendor or employer named.
Where a rollout actually gets hard is the edges.
Across fund-accounting platform rollouts the recurring work is the same shape: getting pref-share reconciliation logic right, validating waterfall behaviour against expected outcomes, and discovering the edge cases a clean demo never shows. The hard part is rarely the configuration; it is the existing book, with its history and non-standard terms. These are described here as approaches rather than tied to any one platform or engagement.
Pref-share reconciliation
- Logic for reconciling preferred-share positions consistently.
- Accruals as well as positions; a preferred return builds over time, and both must tie out.
- Tie-outs against the source of truth, not the old system's copy of it.
Waterfall validation
- Expected-vs-actual checks on distribution waterfalls.
- Edge cases surfaced before go-live.
Recompute it yourself, then argue with the platform.
Build an independent expectation of what the platform should produce, then compare. Every difference has one of two answers: the platform is wrong, or the expectation is.
- Scripted checks
- Python against the spreadsheet exports, so whole batches of entities are re-checked, not spot-checked.
- Feedback
- Issues go to the vendor with the failing case attached; quirks get written down so nobody rediscovers them.
The reusable thing is the method, not the tool.
Platforms differ, but the discipline of validating a waterfall against what it should produce, and hunting deliberately for edge cases, transfers across all of them. So does the question of where the source of truth actually lives, covered separately in the cross-system reconciliation pattern. Holding the knowledge as a method rather than platform lore keeps it useful for the next rollout.
A capability pattern. No vendor named, no employer process, no figures.