Private Credit

Covenant monitoring for private credit and direct lending

Track DSCR, ICR, LTV, and every other financial covenant across your entire loan book. Configure thresholds per counterparty, per facility. Know which covenants are at risk before the next board meeting, not after.

Covenant Summary
1.45x
DSCR
Min 1.20x
2.1x
ICR
Min 1.50x
72%
LTV
Max 75%
2 compliant, 1 at risk
Covenant Engine

Three states. No ambiguity.

Every covenant in CapitalBridge resolves to one of three states: Compliant, At Risk, or Non-Compliant. The At Risk state is the one that matters most. It gives your team time to act before a formal breach, using a configurable headroom percentage that you define per covenant.

Example: DSCR covenant, threshold 1.20x, headroom 15%
COMPLIANT
1.38x
Threshold 1.20x
At Risk below 1.38x
Headroom 15%

Current value exceeds the at-risk threshold. No action required.

AT RISK
1.25x
Threshold 1.20x
At Risk below 1.38x
Headroom used 28%

Still above threshold, but within the headroom band. Your team gets notified now, not after the breach.

NON-COMPLIANT
1.05x
Threshold 1.20x
Breach by -12.5%
Status Breach

Below threshold. Flagged in dashboard, escalation triggered, LP report updated.

This same 3-state logic applies to every covenant type: ICR, LTV, leverage ratios, fixed charge coverage, and any custom metric your credit agreements require. Thresholds and headroom percentages are configured per counterparty, per facility.

The Difference

What changes when you stop using spreadsheets

Before
x
Covenant status unknown between quarters
You only know a covenant is breached when the next quarterly report arrives.
x
Manual threshold checks per counterparty
Each analyst maintains their own spreadsheet with different formulas and different assumptions.
x
No audit trail for covenant decisions
When an LP asks "when did you first know about this breach?", you search your email.
x
LP covenant reports assembled manually
Every quarter, someone spends two days compiling covenant status across the portfolio into a slide deck.
After
At Risk warnings before any breach
Headroom calculations flag counterparties trending toward breach while there is still time to intervene.
Thresholds calculated automatically on submission
When a counterparty submits financial data, every covenant is compared against its configured threshold instantly.
Timestamped record of every state change
Full audit trail: who submitted, when it was reviewed, when the status changed, and who approved it.
Portfolio-wide covenant dashboard, always current
One view showing every counterparty's covenant status. Filter by fund, sector, or risk level. Export for LP reporting.
Setup

From onboarding to live monitoring in four steps

1

Configure your covenant packages

Define which covenants apply to each counterparty or set defaults at the fund/sector level using the cascading scope system. For each covenant, specify the metric (DSCR, ICR, LTV, leverage), the operator (greater than, less than, between), the threshold, and the headroom percentage.

2

Assign reporting requirements

Select which document types each counterparty must submit and on what schedule. Reporting requirements can be assigned at the fund level and overridden per sector or per counterparty. CapitalBridge automatically generates pending submissions 90 days before each due date.

3

Counterparties submit through their portal

Each counterparty gets a self-service portal showing what is due, what has been submitted, and what needs rework. They upload documents and enter financial data directly. A 7-tier automated escalation handles follow-ups so your team does not chase.

4

Covenants calculate, dashboard updates

When financial data is submitted and approved, covenant values are calculated against thresholds. The portfolio dashboard updates in real time: Compliant, At Risk, or Non-Compliant. Your team reviews exceptions, not spreadsheets.

LP Reporting

Show your LPs that covenants are being monitored

Private credit managers report covenant status to their own investors every quarter. CapitalBridge provides the underlying data, audit trail, and dashboard that makes LP reporting credible rather than assembled from memory and email threads.

  • Portfolio-wide covenant summary exportable to PDF or Excel
  • Historical covenant trends per counterparty across reporting periods
  • Full audit trail: who submitted, who reviewed, when status changed
  • Compliance scores by fund, sector, and counterparty
Q4 2025 LP Covenant Report
38
Counterparties
142
Active Covenants
92%
Compliance Rate
DSCR
89%
ICR
95%
LTV
82%
Leverage
97%
3 at risk, 2 non-compliant, 137 compliant
Reporting

Reporting types built for private credit

CapitalBridge includes a library of 27 standard reporting types. Private credit teams typically use 8-12 of these, assigned at the portfolio, sector, or counterparty level. Here are the ones private credit teams use most.

CC Covenant Certificate

Quarterly covenant compliance confirmation signed by the counterparty's CFO or authorized officer. In private credit, this is the primary document that triggers covenant status recalculation.

FCC Financial Covenant Certificate

Detailed financial ratio calculations with supporting data. Shows the actual DSCR, ICR, and LTV computations that the counterparty used to arrive at their covenant compliance claim.

QMA Quarterly Management Accounts

Income statement, balance sheet, and cash flow summary. The raw financial data your team uses to verify covenant calculations and track counterparty performance between annual audits.

AFS Annual Financial Statements

Audited year-end financials with notes and auditor opinion. The annual baseline against which all covenant thresholds are validated and credit assessments are updated.

FM Financial Model

Forward-looking projections and debt service coverage forecasts. Used to assess whether a counterparty trending toward an At Risk state is likely to recover or continue declining.

DSRA Debt Service Reserve Account

Verification of reserve balances against required minimums. Critical in direct lending where DSRA adequacy is often a standalone covenant with its own threshold.

Plus 21 additional types including insurance certificates, operational reports, ESG monitoring, and portfolio-specific documents. Custom types can be added during configuration.

From a portfolio manager

"We used to spend the first two weeks of every quarter just collecting documents. Now counterparties submit through their portal, and we spend that time on analysis instead."

See it configured for your loan book

Book a 30-minute demo. We will set it up with your actual portfolio structure, counterparty list, and covenant packages so you can evaluate it against real data.