Reporting and Compliance

Reporting is the mechanism through which your capital provider learns what is happening to their collateral. Deliver it late, deliver it inconsistently, or deliver a number you cannot reproduce, and you convert a performance conversation into a control conversation. Control conversations lead to tighter eligibility, additional reserves and slower approvals long before they lead to default notices.

The function is not complicated. It is a calendar, a set of documented calculations, a review step and an escalation path. What makes it hard is that it runs every month regardless of what else is happening.

Build the calendar before the first draw

On the day your facility documents are agreed, extract every reporting obligation into a single dated calendar. For each item, record five things: what is due, where the data comes from, who prepares it, who checks it before it leaves, and who receives it.

Do not assume standard deadlines. Delivery periods, certification requirements and testing frequencies are negotiated and vary between facilities. Read yours and put the actual dates in the calendar rather than the dates you remember from a previous deal.

Assign a named individual rather than a team. A deliverable owned by finance is owned by nobody at month end.

Three different sources of obligation

Originators frequently collapse three distinct obligation sets into one mental category called compliance. They behave differently and they fail differently.

Facility obligations come from your credit agreement and related documents. They cover reporting, covenants, certifications and notice requirements. They are negotiated, they are specific to your facility, and they are the ones you can amend by agreement with your provider.

Legal and regulatory obligations come from the law applicable to your product, your entity and your jurisdiction. They are not negotiable with your capital provider, and what applies to you is a question for your compliance adviser and counsel rather than something to infer from what a peer does.

Investor or buyer obligations come from separate contracts: a forward flow purchase agreement, a servicing agreement, or the transaction documents in a term ABS issuance. These can require different data, on different dates, calculated on different bases.

Keep them in one calendar but tagged by source, because when they conflict you need to know which one you are looking at. A definition of delinquency in your facility agreement may differ from the one in a purchase agreement, and reporting the same number to both parties is a mistake even when it feels like consistency.

Borrowing base mechanics: reserve versus cash

The borrowing base is the collateral limit derived from your assets using the formula in your documents. It typically runs eligible collateral, an advance rate, concentration adjustments and reserves, in the order the agreement specifies.

One distinction causes persistent confusion. A reserve stated as a deduction from the borrowing base reduces how much you may borrow. It is not itself a cash account. It can still cost you cash indirectly: if the deduction pushes your borrowing base below drawn debt, you may have to repay the difference. A funded cash reserve is different: it requires actual money to sit in a specified account, usually blocked. Where that money comes from depends on the documents, which may permit funding from collections, from borrowings under the facility, or from your own equity.

Both may appear in the same facility, and they can carry similar names. Check which type each one is when you first read the term sheet, and label them differently in your own model so nobody confuses a formula deduction with a cash requirement.

A month when the base falls short

The following case is fictional and stated in US dollars for a single monthly reporting date.

Eligible collateral is 10.0m. The advance rate is 75%, giving 7.5m. A reserve of 0.3m is deducted in the formula, leaving a borrowing base of 7.2m. Drawn debt is 7.4m. You have a 0.2m shortfall.

Report the 0.2m shortfall as it calculates. Do not stretch an eligibility interpretation to close the gap, do not adjust the reserve to suit the answer, and do not delay the certificate while you look for a favourable reading. The borrowing base certificate is signed by a named officer, and an inaccurate certificate creates consequences well beyond the arithmetic error.

Applying the definition correctly does not mean you can never change a number. If you discover a genuine error in the data or the calculation, correct it, document what changed and why, keep the audit trail, and tell your provider. The distinction is between fixing a mistake you can evidence and reworking the formula until it produces the answer you want.

What happens next depends on your documents. Cure mechanics, cure periods and the remedies available to the provider are drafted terms, and the answer differs between facilities. So does testing frequency: weekly testing surfaces a shortfall earlier than monthly testing, though earlier detection does not guarantee a faster cure, since that depends on what remedies are available and how quickly you can execute them. Note too that some facilities require continuous compliance with the borrowing base regardless of how often you certify, so a monthly certificate does not mean a mid-month shortfall is permitted. Common cure routes include repaying debt to bring drawn amounts within the base, contributing additional eligible collateral, or agreeing a waiver. Which of those you can use is set out in your agreement, and whether a shortfall becomes an event of default if uncured is likewise a documented question.

Escalation on the day you find it

The most costly reporting error is timing. If your eligibility engine shows the base going short on the twelfth of the month, escalate on the twelfth. Do not wait for the month-end certificate to make it official.

Three reasons. First, the agreement determines when a shortfall becomes a breach and when notice is due, rather than the date you choose to report it, and your documents may contain a notice obligation triggered by knowledge rather than by a reporting date. Second, cure options that exist on day twelve may not exist on day thirty, particularly if the cure involves originating or acquiring additional eligible collateral. Third, a provider who learns about a problem from you while you are working on it responds differently from one who finds it in a certificate you delivered without comment.

Build a simple internal trigger: when projected availability falls below a defined buffer, the CFO is notified the same day and a written plan is produced within a set number of days. That plan should state the cause, the size of the gap, the options with their timelines, and the recommended action.

Making the numbers reproducible

A reported number is only useful if you can rebuild it. That means documenting the eligibility logic in a form someone other than the author can follow, keeping the extracted data set that produced each certificate, and retaining the calculation file rather than overwriting last month.

Providers test this during audits and field examinations. The test is simple: pick a certificate from four months ago and rebuild it from source data. If your team cannot, the provider learns something about your controls that no amount of clean reporting since will offset. The upstream data discipline that makes this possible is set out in the loan tape guidance, and the daily operational feeds behind it in servicing requirements.

Fees and cost lines belong in the same discipline. Unused commitment fees, servicing costs and administrative charges accrue on defined bases, and reconciling what you were charged to what the documents provide is a monthly exercise rather than an annual surprise. The mechanics of each cost line are covered in facility fees, and how draw requests interact with these calculations in facility funding.

Who checks the checker

Separate preparation from review. The person who builds the borrowing base should not be the only person who sees it before it goes out, and the reviewer needs enough understanding of the formula to catch a definitional error rather than only an arithmetic one.

Build three review controls, setting the thresholds and frequencies to fit your own risk and reporting cycle. A period-over-period movement check that flags any line moving more than a defined percentage without explanation. A tie-out between the loan-level file and the summary certificate, so the two documents you send cannot disagree. A periodic sample re-performance, on a documented schedule, where someone independent rebuilds a certificate from source data.

Standing up the function

Start with the calendar and named owners. Then document the eligibility logic and the borrowing base calculation, in writing, with worked examples. Then automate the extraction so the same fields produce the same numbers each month. Then add the review controls. Then rehearse a shortfall scenario with your team so that the first time you run the escalation path is not the first time it is needed.

Providers read reporting quality as evidence of operational quality generally. A clean, on-time, reproducible reporting record is one of the few things fully within your control that improves how the next facility conversation starts.