Most breaches show up in the data weeks before the covenant test. Spreadsheets just donu2019t put the pieces side by side.
The borrowing base certificate arrives. An analyst rekeys it into the spreadsheet, checks availability, and files it. Next month, the same thing. Each month looks fine on its own.
Then the quarterly covenant test comes in, and the borrower has breached. Looking back, the signs were there: reporting was slipping, ineligibles were creeping up, one customeru2019s share of receivables kept growing. They just sat in different tabs, in different months, reviewed by different people.
A breach rarely comes as a surprise in the data. It comes as a surprise to the team, because nobody saw the full picture in one place. Here are five patterns that usually show up first, and what it takes to catch them while you still have room to act.
Certificates arrive a few days later each month. Supporting agings are missing, or the borrower asks for u201cone more weeku201d on financials.
Nobody tracks the submission date. A late file still gets rekeyed and looks normal once itu2019s in.
With Covarity, borrowers submit through a borrower portal, so every submission is logged in one place. Late or incomplete reporting becomes visible across the whole book, not just to the analyst who chased it.
Receivables past 90 days grow from month to month. A large customer edges toward the cross-aging threshold, which would make its whole balance ineligible.
Each monthu2019s ineligibles are calculated fresh. The trend across six months lives in nobodyu2019s tab.
Covarity applies your eligibility rules and cross-aging tests the same way on every submission, so a rising ineligible balance shows up as a pattern, not a surprise.
A single account debtoru2019s share of receivables climbs toward the concentration limit. If that customer pays slowly or fails, the borroweru2019s availability drops sharply.
Concentration is often checked only at the limit, and only if someone remembers to run it.
Concentration limits are set once in Covarity and checked on every submission, so teams can see an account approaching the limit before it breaches.
Excess availability shrinks month after month. The borrower draws closer to the full line, and requests for overadvances start appearing.
Availability is calculated after the analyst rekeys the certificate, sometimes days later. By then the borrower has already drawn.
Covarity calculates availability when the borrower submits, so credit and relationship teams see the same current number the same day.
The borrower still passes its financial covenants, but by less each quarter. Manual adjustments to the borrowing base also become more frequent.
A pass is a pass. Shrinking headroom and a growing list of adjustments rarely get reported upward until the test fails.
Covarityu2019s covenant monitoring and early warning flag a borrower trending toward a threshold, and the adjustment audit trail shows who changed availability, when, and why.
None of these five patterns needs new information. Your team already collects it every month. Whatu2019s missing is one place where submissions, eligibility, concentrations, availability and covenants sit side by side, checked the same way every time.
Thatu2019s what Covarity does. It gives credit risk teams an early warning view of the whole portfolio, so a drifting borrower gets a conversation now instead of a workout later.
The five signs are standard asset-based lending warning patterns.