How to Score Supplier Financial-Health Covenants in Reserved B300 Awards

Consider an illustrative procurement review: two suppliers offer the same reserved Supermicro HGX B300 configuration and delivery window. Both provide inventory documentation. One also supplies current financial statements, a reservation-specific funding forecast, and an obligation to disclose lender defaults. The other offers a parent-company presentation and says financing is “handled.”

The difference is not presentation quality. It is whether procurement can detect a funding problem before it becomes a missed delivery.

Supplier financial-health covenants should answer three questions: Can this counterparty fund its remaining obligations? What changes must it report? What can the buyer do while recovery is still possible?

1. Score five covenant categories, not a credit narrative

Use a 100-point scorecard. For each category, assign 0–4: 0 means absent; 1, unsupported assertion; 2, documented current position; 3, defined covenant with recurring evidence; 4, covenant plus milestone checks, notice duties, and a usable remedy. Multiply the weight by the rating divided by four.

• Liquidity — 25: Unrestricted cash, available committed facilities, borrowing restrictions, and a forecast through delivery and acceptance. Require an agreed minimum liquidity or funding-coverage threshold.
• Leverage and lender headroom — 20: Gross and net debt, maturities, security interests, lender covenant calculations, and headroom. Define leverage consistently; use alternatives when EBITDA is negative or distorted.
• Going-concern and financing risk — 20: Latest audited statements, auditor’s report, interim accounts, going-concern disclosures, refinancing dependencies, and management’s documented response to identified uncertainty.
• Material-adverse-change triggers — 20: Objective triggers tied to delivery capacity: financing withdrawal, acceleration of material debt, insolvency events, or loss of funding needed to perform.
• Reporting and notice rights — 15: Named reporting owner, certificate format, delivery deadlines, event-notice timing, supporting records, and consequences for missing or inaccurate reports.

Do not prescribe one leverage ceiling for every supplier. Set thresholds against its business model, financing structure, and outstanding reservation obligations.

For liquidity, distinguish cash from restricted deposits and genuinely drawable facilities from uncommitted financing. Test forecast funding against remaining procurement, assembly, freight, and support obligations without counting the same facility twice.

Treat refusal to disclose the contracting entity’s finances or accept material-event notice duties as an award gate. A strong aggregate score should not conceal an unmonitorable counterparty.

2. Bind evidence to award and delivery gates

A healthy balance sheet at bid submission does not establish funding at shipment. Put the reporting schedule in the award documents.

• Before award: Obtain financials, debt schedules, a funding forecast, and an authorized-officer certificate identifying exceptions. Set an explicit maximum age for each document.
• At reservation confirmation: Refresh liquidity and confirm that committed financing remains available for the reserved order.
• During the build: Request monthly management accounts and covenant certificates, with more frequent cash reporting if headroom tightens.
• Before shipment and acceptance: Require updated certification and disclosure of intervening events. Any withholding or suspension right must be expressly negotiated.

Specify whether each requirement is an award condition, continuing covenant, or milestone condition. Those labels determine consequences; they are not interchangeable.

Keep this schedule adjacent to the reserved B300 payment-milestone framework, without redesigning payment mechanics. Financial certification checks funding continuity; it does not replace hardware inspection or acceptance evidence.

Use the same configuration and delivery assumptions across the financial review and the reserved GPU capacity planning brief.

3. Test the obligated entity and usable parent support

Request evidence for the entity that owes delivery. Parent consolidated accounts can provide context, but they do not prove a thinly capitalized SPV can access cash.

For an SPV, request standalone cash balances, capitalization, intercompany funding terms, restrictions on transfers, and the timing of committed contributions. If performance depends on parent support, monitor both the support provider and the enforceable funding obligation.

A nonbinding comfort letter should not score like committed support. Equally, strong parent liquidity does not cure transfer restrictions or competing claims on that liquidity.

Keep the structural decision in the parent-guarantee-versus-SPV counterparty guide. Here, score whether the promised support remains measurable and available throughout delivery.

4. Define warnings, cure deadlines, and escalation

Avoid relying solely on “any material adverse change.” Define events, materiality, knowledge standards, notice timing, and evidence required. Counsel should assess both specific triggers and any broader MAC backstop.

An illustrative negotiation position might require notice within two business days after an authorized officer learns of a defined event. Reporting breaches could receive a short administrative cure period; a funding shortfall should require a funded recovery plan before the next exposed milestone.

Distinguish early warnings from defaults. Shrinking lender headroom might trigger weekly reporting. An uncured liquidity breach might permit suspension of further exposure. Insolvency-related rights require jurisdiction-specific review.

Potential cures include equity contributions, committed replacement financing, or additional agreed security. Test whether the cure restores delivery funding—not merely whether a plan was submitted. If it fails, activate negotiated termination or existing step-in provisions, subject to enforceability and third-party consents.

Ask counsel to review all proposed contractual language.

Need to turn these checks into an award scorecard? Book a procurement working session with Pacific Intelligent Technologies, Inc..

5. FAQ: Applying the scorecard

Does a going-concern disclosure automatically disqualify a supplier?

No. Investigate the uncertainty, funding dependencies, and mitigants. Procurement should apply documented risk gates rather than treat disclosure alone as proof of failure.

Can bridge capacity solve supplier financial risk?

It may reduce operational disruption, but it does not repair the supplier’s balance sheet. Assess bridge-capacity options separately from covenant compliance.

Do covenants replace deposit protection?

No. Covenants provide monitoring and contractual responses; escrow and deposit protections address different exposure. For broader procurement context, see Pacific Intelligent Technologies, Inc..