How PROVEN works, and why it works this way.
What we do, why it's needed now, how it differs from the general ledger and the annual audit, and where it applies across the investment lifecycle.
Independent verification.
Most financial reporting tools start from what management has already reported. PROVEN works independently of management — producing an independent view of the income statement and the statement of cash flows, then reconciling line by line against what management provided.
Where PROVEN fits alongside the general ledger and the annual audit.
PROVEN does not replace the general ledger, and it does not replace the annual audit. It sits alongside them as a third layer, built for a job neither of those two was designed to do.
The general ledger is management's record of what happened, kept by the accounting team for the company's own purposes. It runs continuously, but it runs inside the company.
The annual audit is a once-a-year attestation that the general ledger complies with GAAP or IFRS. It is independent of management, but only at a point in time.
What investors need — and what neither the general ledger nor the audit was designed to provide — is independent visibility into what their portfolio companies actually did, on a cadence that matches how investment decisions are made. That is the layer PROVEN provides.
Used before you commit, and after.
Diligence
Independent verification of the target's reported financials before you commit. The output is built to go straight to investment and credit committees.
Used by: PE deal teams, VC investment committees, private credit underwriters, corporate development teams.
Monitoring
Continuous independent verification throughout the hold period. Variances between reported and verified figures are flagged as they appear, not months later at year-end.
Used by: Portfolio monitoring teams, operating partners, credit surveillance, LP reporting teams.
PROVEN does not model reality. It proves it.
Have specific questions about scope?
Most buyers we talk to have questions before they have a use case. We'd rather answer them in conversation than pitch through them.