Engagement model
This is how IndexPortal Hub Advisory runs a financial audit of an application that feeds an investment portfolio dashboard. It is the working pattern behind our letters, not a product tour.
We ask which dashboard views are actually used for decisions, which portfolios and periods matter, and who operates the application when a load fails. You leave with a written outline of what would be in and out of scope. If we are the wrong firm, we say so on that call.
The letter names the application boundary, the views and periods, the addressee of the report, the fee, the deposit, and the planned fieldwork window. Work does not start on a handshake. It starts when the letter is signed and the deposit in the letter is received.
We send a request list: statement extracts, mapping tables, calculation settings, override logs, and a supervised walkthrough. We do not take production passwords. Staging copies and exports are enough for almost every test we run.
Sampling, re-performance, and interviews happen in this window. Awkward items — a large flow, a suspended price, a custodian change — are included on purpose. We raise likely exceptions while fieldwork is open so that operators can find evidence, not after the draft is already frozen.
A draft goes to the addressee for factual comment. We will correct facts. We will not soften a finding because it is inconvenient. The final report states what was tested, what matched, what did not, and which gaps are documentation rather than calculation.
We will walk the report with an audit committee, a family principal, or an operations lead. Remediation and re-testing are a separate letter if you want them. The original report remains the record of what we saw in the period we named.
We will not certify an entire platform. We will not meet a date by skipping the sample. We will not share working papers with a vendor unless the letter allows it. If those limits do not fit, another firm will serve you better.
Enquiry