What a financial audit of a portfolio dashboard application actually covers
Clients sometimes arrive expecting a critique of colours, filters, and mobile layout. That is design work. A financial audit of the application behind a portfolio dashboard asks a narrower question: can this figure be supported from sources the organisation already trusts?
We treat the dashboard as a window. The application is the room. Holdings may be loaded from a custodian file, priced from a vendor, adjusted by a corporate-action calendar, and then summarised by a performance engine. Any one of those steps can be sound while another is not. The audit follows the figure, not the screen.
Scope has to be named. “The equity book for March and June, views A and C, base currency MYR” is a scope. “The whole platform” is a wish. Naming the views and periods is what allows sampling, re-performance, and a report that an audit committee can file.
We also draw a boundary around the application. If a warehouse already transforms the custodian file, that warehouse is either in scope or it is an assumed source. Leaving it implicit is how two reviewers later argue past each other.
The report does not certify that every tile is correct. It states what was tested, what matched, what did not, and which gaps are documentation rather than calculation. That distinction matters when a vendor is blamed for a policy the client never wrote down.
If you are commissioning this work for the first time, bring three things to the opening meeting: a list of dashboard views that investment decisions actually use, one month-end pack, and the person who knows how files are loaded when something fails.