One P&L your PMs, controllers and risk all sign.
P&L, position, exposure and risk reporting on Microsoft Fabric and Power BI — reconciled across trading, risk and finance systems, secured by desk, and documented to the standard a product controller will sign.
Four mornings every fund recognises.
The desk P&L and the controllers' P&L disagree, again.
A unified P&L model reconciles both views to the same positions and marks, and shows where the break is before anyone emails.
An allocator asks for attribution by strategy over three years.
Historical loads and a governed semantic model
The single, documented layer that defines every measure (what "P&L" or "net exposure" means) once, so every report reads the same definition.
Risk needs exposure by counterparty, sector and tenor, now.
Position and exposure reporting on the same model as P&L, so risk and returns are never two different books.
ODD asks how the numbers get from OMS to the deck.
Every measure documented, every number walkable back to source, every desk seeing only its own book.
Five deliverables, one governed model.
Unified P&L
Daily and month-to-date P&L reconciled across OMS, risk and finance; break analysis by desk and instrument; sign-off workflow with a record of who signed what.
Position and exposure reporting
Gross and net, delta-adjusted, by strategy, sector, counterparty and tenor, with limit utilisation on the same model as P&L.
Reconciliation and validation
Automated reconciliations between systems and the administrator, exception queues with owners, and ageing of unresolved breaks.
Investor and management reporting
Attribution, performance and factsheet packs generated from governed measures, with the narrative stored as data so it can be audited later.
Historical loads and migrations
Back-loading years of positions and P&L into one governed history, and retiring the spreadsheets that used to hold it.
How an engagement runs
A named senior analyst, embedded with your controllers and risk team, working your hours. The founder stays on the account as lead.
Two weeks with your P&L, your systems and the people who sign it. Output: a measure dictionary everyone agrees on.
One governed semantic model in your tenant. Every report, every desk, every investor pack reads from it.
Parallel runs and validation dashboards until product control signs off. Senior review is part of the plan, not a surprise.
Hypercare with a defined response window, then a steady-state seat. The person who built it is the person who supports it.
A unified daily P&L across trading, risk and finance systems
The fund ran three P&L views that never fully agreed. We built one semantic model reconciling desk P&L to the controllers' view, with validation dashboards, historical loads and desk-level security, reviewed at senior product-control level.
Read the caseA good fit when
You run on Microsoft or are moving there. Your CTO or COO owns the reporting problem. One to three people know where every number comes from and would like to stop being the only ones. You want the model to outlive the vendor.
Not a fit when
You want a hosted SaaS you never see inside. You need a Snowflake and Tableau shop (we work in the Microsoft stack by choice). You want a pool of interchangeable developers billed by the sprint.
Things people ask before the first call.
Which systems have you reconciled P&L across?
Can each desk see only its own book?
What does hypercare mean in practice?
Do you replace our fund administrator or OMS?
Send us the P&L that never ties.
Thirty minutes with the founder. We will tell you where the break is likely to be and what a fix looks like.