Portfolio dashboard application audit
We test whether the application behind a portfolio dashboard produces figures that can be supported from source files, approved mappings, and documented calculation rules.
Most portfolio dashboards are a presentation layer. The financial risk sits in the application that loads custodian files, applies pricing, rolls performance, and publishes the tiles that investment committees actually read. Our primary service is a financial audit of that application, not a software demo review and not a redesign of the dashboard itself.
We start from a named set of dashboard views and work backwards. For each figure in scope we identify the source file or feed, the transformation steps, any manual overlay, and the rule that turns those inputs into the published number. Where a rule cannot be shown, we record that as a finding rather than inferring what the application “probably” does.
Fieldwork is done with the people who operate the application day to day: operations, performance, and the vendor or internal developer who can extract logs and mapping tables. We do not require production passwords. We work from exports, staging copies, and supervised walkthroughs.
The deliverable is a written report with a scope statement, a description of the application boundary, tested items, exceptions, and a graded set of recommendations. Clients use it for internal audit files, vendor discussions, and investment-committee assurance. We remain available to explain the report to a board or audit committee in Klang or by video.