Conclusion first
There are three ways to put a fair value on a private credit position, and the right choice turns on what the mark is for, not on which provider is “best”:
- An independent advisory opinion. A named third-party valuation, typically quarterly. The deliverable is reputational — an opinion an audit committee and LPs recognise.
- An operations-platform valuation module. Valuation bundled into a broader middle-office or fund-administration suite. Wins when valuation is one line in a wider operations contract.
- A deterministic valuation engine. Software that computes the mark itself — on demand, reproducible to the basis point, with a published method and the full calibration chain stored for audit. This is what Verus is.
Need a named advisory sign-off at period end? That is the advisory model. Need valuation inside a single operations system? That is the platform model. Need frequent, explainable, API-delivered marks with a published method behind them? That is what a deterministic engine is built for.
How the models differ
| Dimension | Independent advisory opinion | Operations-platform module | Deterministic engine (Verus) |
|---|---|---|---|
| What you receive | A named third-party valuation opinion | A valuation feature within a middle-office suite | A computed mark from a published deterministic engine |
| Cadence | Typically quarterly, batch | Periodic, tied to the platform's reporting cycle | On demand — daily or any measurement date |
| Reproducibility | Opinion re-issued each cycle | Depends on the module; often not bit-reproducible | Same inputs + engine version reproduce the mark to the basis point |
| Method transparency | Proprietary advisory methodology | Configurable but rarely published | Published, versioned method; no black-box ML in the pricing path |
| Calibration lineage | Held within the engagement | Varies by module | Day-1 spread + every drift stored and auditable per deal |
| Delivery | PDF / deck deliverable | In-platform; export varies | API into your risk system, plus report export |
| Conflict surface | Often a full-service advisory firm with other mandates | Valuation is secondary to the operations relationship | Valuation-only; no transaction-side interest in the position |
| Economics | Advisory fees, scaling with analyst hours | Bundled into the platform contract | Platform economics, scaling with software |
When an advisory opinion fits
- The deliverable is a named, independent third-party opinion for an audit committee or LP base that expects a recognised valuation adviser.
- The position is bespoke or contested enough that hands-on advisory judgement is the point, not a repeatable computation.
- A periodic opinion meets the requirement and frequency is not a constraint.
When an operations platform fits
- Valuation is one requirement among many — fund accounting, waterfall modelling, covenant tracking — and a single middle-office contract is the priority.
- The buyer is the COO or operations team, and integration across functions matters more than valuation specialisation.
Verus is not an operations suite — it does not run fund accounting or waterfalls — but the controls around the mark ship with it: a covenant register and monitor, IFRS 9 staging, quarterly refresh and period close, IC papers, portfolio risk and stress, and four-eyes review on deals and runs.
When a deterministic engine fits
- You need marks more often than quarterly — monthly NAVs, on-demand repricing, or live sensitivities as conditions move.
- You need reproducibility and explainability: a historical mark that re-runs from its recorded inputs, and every figure traceable to an input or a documented default.
- You want the calibration chain — Day-1 implied spread and its drift history — stored and auditable per deal.
- You want marks delivered into a risk or independent-price- verification system by API, at a cost that scales with software.
- You want a valuation-only relationship with no transaction-side conflict.
Using more than one
The models are frequently complementary. A common pattern: run a deterministic engine for ongoing internal marks, sensitivities and risk-system feeds, and commission an independent advisory opinion at period end where the audit committee wants a named third party. A reproducible engine makes that reconciliation straightforward — the period-end position is the same deterministic output you have marked against all quarter. In Verus the advisory opinion is recorded against the Verus mark inside the platform — price, range, as-of date and the gap in points — so the reconciliation is a stored record on the deal, not a spreadsheet.
The method behind Verus
Verus prices private credit deterministically: contractual cashflows, hazard-rate credit adjustment, OIS discounting, and a facility spread calibrated to the Day-1 transaction price and carried forward on documented market drift. The fair-value classification (IFRS 13 / ASC 820 Level 2 or 3) is resolved in the run output, not asserted by hand.
- Deterministic IFRS 13 valuation — how the mark is built, end to end.
- Methodology — the full equation set, approach router and governance surface.
- Model risk — validation framework, challenger model and the methodology whitepaper under NDA. The SR 11-7 / SS1/23 validation pack is being assembled.
- Sample report — a Verus valuation output, screen by screen.
To see Verus on your own book, book a demo.