← How lenders decide

Lesson 24 of 25 · 7 min

Portfolio-level exposure: you are one line in a book

The limit that binds can be one you have no part in, because it is measured across every borrower the institution has.

Every limit described so far is measured inside one account. Institutions run a second set measured across all of them at once, and those are the ones that produce changes nobody in the account can explain.

The book-level caps mirror the account-level ones, one layer up. Total lending value supported by any single issuer across every borrower. Total exposure to a sector. Total exposure to any one custody arrangement. Total size of the lending book relative to the funding available to support it. Each has a ceiling, expressed as a percentage of the whole.

When one of these binds, the institution has to reduce exposure across a population rather than in one file. The cheapest instrument for that is the schedule: cut the advance rate on the affected class and every borrower holding it contributes to the reduction proportionally. It is administratively trivial, it is defensible, and it requires no conversation with anyone.

Two features make this hard to see from inside an account. The reduction arrives as a schedule version, indistinguishable from a revision prompted by anything else, so there is no marker recording which cause produced it. And the timing follows the institution's own reporting cycle rather than the market: a ceiling is usually measured at a period end, so the cut can land days or weeks after the exposure that caused it was built, against a backdrop that no longer explains anything.

The revision that removed your capacity may have been caused by portfolios you have never seen, held by people you will never meet, at an institution doing arithmetic on a total you are a rounding error inside.

Key terms

Book-level cap
A ceiling on the institution's total exposure to an issuer, sector or structure, measured across every borrower rather than inside one account.
Proportional reduction
Clearing a book-level breach by cutting an advance rate across a whole class, so every affected borrower absorbs a share of the fix.
Supported value
The total lending value the institution has extended against one issuer or sector. The quantity a book-level cap is written against.

Worked example

A breach measured in millions, a fix measured in thousands

An illustrative book with $4,900,000,000 of total lending value and a 4.0 percent ceiling on support against any single issuer.

Ceiling on single-issuer support
$196,000,000

$4,900,000,000 × 0.040.

Current support against one issuer
$214,000,000
Excess to be cleared
$18,000,000
Advance rate cut applied to the class
58% to 53%

Brings support to $195.6m.

Effect on one borrower's $386,000 holding
$223,880 to $204,580
That borrower's share of the fix
$19,300

An $18,000,000 problem at the top of the institution arrived in one account as $19,300 of capacity, with no explanation attached and none owed.

Check yourself

An institution has $6,200,000,000 of total lending value and caps single-issuer support at 3.5 percent. Support against one issuer has reached $238,000,000. If it clears the breach by cutting that class from a 62 percent advance rate, roughly where does the rate land, and what does it do to a $512,000 holding?

Saved in this browser only. No account, nothing sent anywhere.

Educational only. Nothing in this lesson is investment, legal or tax advice, or a recommendation to enter into any transaction. Figures are illustrative and computed from the inputs stated in the lesson.

Dhruv Intelligence provides informational and educational intelligence only. Nothing on this site constitutes investment, legal, tax, or financial advice, or a recommendation to buy, sell, or hold any security or to enter into any transaction. All decisions remain solely those of the user. Dhruv Intelligence is not a registered investment adviser or broker-dealer.

Dhruv Intelligence™, MACH11™, and Monk Score™ are unregistered trademarks of Dhruv Intelligence, Inc. USPTO intent-to-use applications are pending for Dhruv Intelligence™ and MACH11™. None of the marks has registered. Patent Pending (US Provisional, 2026).

© 2026 Dhruv Intelligence, Inc. All rights reserved. · The fixed point.

New York, NY · San Jose, CA · Miami Beach, FL · Salt Lake City, UT

A SOC 1 and SOC 2 Type 1 audit is in progress with Thoropass, engaged August 13, 2026. No report has been issued. · Contact: info@dhruvintelligence.ai

Institutional Access →