What Lenders Actually Check in Your Financials

Checked by: comparing the figures reported on the calculation schedule against the actual financial statements submitted alongside it — a mismatch between a number on the schedule and what the underlying statement shows is the most basic and most commonly caught issue.

Why it comes first: every other item on this list assumes the base figures are correct. A discrepancy here undermines confidence in everything calculated from it, which is why it's typically the first thing a credit analyst checks.

Checked by: comparing the add-backs claimed this quarter against those claimed in prior quarters — an add-back that appears, disappears, and reappears without a documented reason is exactly the pattern a credit team is trained to flag.

Why it's scrutinized closely: add-backs are where a calculated ratio is most easily flattered, intentionally or not. A “one-time” item claimed every quarter stops looking one-time fairly quickly, and lenders know it.

flowparse.io

Checked by: comparing cash flow or debt service figures on the calculation schedule against what actually cleared the borrower's bank accounts for the same period.

Why this matters more than it seems: a lender that also holds the borrower's operating accounts has direct visibility into cash movements, which means a reported figure that doesn't match the bank's own records is unusually easy for them to catch — and unusually hard to explain away if it isn't a genuine timing difference.

Checked by: comparing each covenant's calculated ratio against its threshold over several consecutive quarters, not just the current period in isolation.

Why the trend matters more than the single result: a covenant that technically passes every quarter but with steadily shrinking margin is a different risk profile than one that passes comfortably and consistently, even though both show “pass” on paper — credit teams are trained to watch the trajectory, not just the current pass/fail result.

flowparse.io

Checked by: recomputing a trailing-twelve-month figure from the four underlying quarters, where the covenant is tested on that basis, to confirm the reported total actually sums correctly.

Why it's a common source of quiet errors: a trailing calculation depends on four separate quarters being extracted correctly and consistently — a single misapplied add-back or misread figure anywhere in that chain throws off the whole trailing total, often without being obvious from the final number alone.

Checked by: comparing the debt balance reported at period-end against known draw and paydown activity on the facility, to confirm the balance used in leverage calculations reflects the actual period-end position.

Why timing specifically gets attention: a debt paydown made just before period-end, followed by a new draw just after, can temporarily flatter a leverage ratio in a way that doesn't reflect the facility's typical usage — a pattern credit teams watch for on facilities with revolving components in particular.

flowparse.io

Checked by: comparing this period's treatment of a given line item — revenue recognition timing, expense capitalization — against how the same item was treated in prior periods.

Why it's worth flagging even when legitimate: a genuine accounting method change can shift reported figures in ways that look, on the surface, like a covenant-relevant trend when it's actually a bookkeeping change — credit teams check for this specifically to separate real performance shifts from presentation shifts.

flowparse.io

Checked by: reviewing footnotes and management commentary for transactions with affiliated entities — a management fee paid to an owner-affiliated company, a lease with a related landlord — that might inflate expenses in ways relevant to a covenant calculation.

Why it's specifically watched: related-party terms aren't always set at arm's length, which means they can be adjusted in ways that shift reported EBITDA — credit teams check for disclosure of these relationships specifically because they're a known lever.

Checked by: comparing the ratios, definitions and thresholds used on the submitted calculation schedule against the actual, current text of the credit agreement — including any amendments.

Why this catches more than it seems it should: a borrower using last year's calculation template after an amendment changed a threshold or definition produces a certificate that's internally consistent but doesn't match what the agreement currently requires — an easy mistake to make and an easy one for a credit team to catch by comparing against their own copy of the agreement.

Checked by: confirming the submission date against the deadline the credit agreement specifies, and confirming every required component — financial statements, calculation schedule, officer's certificate — is actually present.

Why it's checked as strictly as the numbers: many credit agreements treat a late or incomplete submission as its own kind of default, independent of whether the underlying financial performance would have passed every test — a detail that surprises borrowers who assume good numbers are enough on their own.

flowparse.io

The ten checks at a glance

Run against your own numbers before a lender does, roughly in the order a credit analyst typically works through them.

A flagged review, walked through

A logistics company with a revolving credit facility submitted four consecutive quarters of compliance certificates, each showing a leverage ratio comfortably under its 4.00x cap. The credit analyst reviewing the fourth quarter noticed something the borrower's own team hadn't flagged: the ratio had moved from 2.85x to 3.10x to 3.35x to 3.60x — passing every quarter, but closing in on the cap at a fairly constant rate.

Nothing in any single quarter's certificate was wrong — each ratio was calculated correctly and passed its test. What triggered a call from the lender was the trend line across four quarters, which is exactly item four on this list in practice: the borrower had been financing seasonal inventory growth with revolver draws without paying down the balance between peaks, a real and explainable business pattern, but one the lender wanted to understand before headroom ran out entirely. The conversation that followed was routine — a borrower who could point to the seasonal pattern and a plan to manage it going into the next peak avoided any negative outcome — but it only went smoothly because the trend, once raised, had a ready explanation rather than requiring one to be constructed on the spot.

flowparse.io

The eleventh thing: how you respond to a question

Not officially part of the checklist, but very much part of how a finding gets treated: whether the borrower can explain a flagged item immediately with documentation, or needs days to reconstruct what happened. A borrower who responds quickly, with a clear explanation and supporting evidence, is generally treated very differently than one who can't answer at all.

This is the one factor entirely within a borrower's control — the ten checks above describe what gets looked at, but how prepared you are to answer a question about any of them is a choice made well before the review ever happens.

Why lenders check this way

None of these ten checks exist to catch a borrower doing something wrong for its own sake — they exist because a covenant package is, functionally, an early-warning system the lender relies on in place of monitoring every transaction directly. A check that catches an inconsistency early is doing exactly what it's designed to do, for both sides of the relationship.

Understood this way, the checklist isn't adversarial by design — it's the mechanism that lets a lender extend credit without watching every wire transfer, and a borrower that internalizes the same checklist internally is simply doing the same verification work the lender would otherwise have to do from outside.

flowparse.io

Why an internal check catches less than you'd think

A finance team reviewing its own compliance package before submission is checking for the same things a lender's credit team checks — but with one structural disadvantage: familiarity. The person who built the calculation schedule already knows why an add-back is there, already expects the trailing figure to look a certain way, and is far less likely to notice something looks off simply because it's the same something that looked fine last quarter too.

A lender's credit analyst has the opposite advantage: no prior assumptions about why any specific figure is what it is, which is precisely what makes a fresh set of eyes catch a pattern the preparer's own familiarity smoothed over. Closing that gap doesn't require hiring an outside reviewer every quarter — it means deliberately checking each of the ten items above as if seeing the numbers for the first time, not as a confirmation that everything looks the same as always.

One concrete way finance teams do this: compare the current quarter's figures against the prior quarter's line by line, rather than glancing at the final ratio and moving on. A side-by-side comparison surfaces a quiet shift — an add-back category that grew, a debt balance that moved unexpectedly — far more reliably than reviewing one quarter's numbers in isolation.

flowparse.io

What good documentation actually looks like

“Document the reasoning” is easy advice to give and vague to act on. In practice, useful documentation for a covenant package is short, specific, and tied to evidence a lender could independently verify — not a narrative explanation, but a pointer to something concrete.

The pattern across all three: a specific figure, a specific source, and a specific reason — exactly the level of detail that turns a follow-up question from a multi-day scramble into an email that gets sent the same afternoon.

It's worth writing this documentation at the time an item is flagged, not weeks later when preparing for a renewal — the specific reasoning behind a judgment call is freshest right after it's made, and reconstructing it months later, from memory, is exactly the scramble good documentation exists to prevent in the first place.

A useful habit: treat every flagged item, no matter how minor it turns out to be, as worth two or three sentences of documentation before moving on — not because most flags need it, but because it's impossible to know in advance which quarter's minor flag becomes next year's lender question, and the cost of documenting something that never gets asked about again is far lower than the cost of not documenting the one thing that does.

None of this needs to be elaborate — a running log with one line per flagged item, the quarter it appeared, and the resolution, is usually enough to satisfy a reviewer asking for history on a specific recurring item.

A related habit worth adopting: date-stamp every documentation note with the quarter it applies to, not just the date it was written. A note explaining an add-back that was written eighteen months ago but never updated can quietly misrepresent the current quarter's reasoning if the underlying facts have since changed — and a reviewer who spots a stale date is far more forgiving of an honest gap than one who discovers the explanation no longer matches what actually happened.

Store this documentation alongside the certificate itself, not in a separate system a future preparer might not think to check — the whole value of the habit collapses if the explanation and the figure it explains end up filed in two different places nobody remembers to cross-reference.

How this differs at a smaller vs. larger lender

A community bank holding a single term loan and a large syndicated credit facility with a lead arranger and several participant lenders check fundamentally the same ten things, but the process around that checking differs enough to be worth knowing in advance.

A community or regional bank relationship manager reviewing a straightforward facility often has direct, personal familiarity with the borrower's business — which can mean a faster, more conversational review, but also means an inconsistency is just as likely to be noticed precisely because the reviewer knows the business well enough to recognize when something doesn't fit the pattern they've come to expect.

A syndicated facility's review runs through a lead arranger's credit team, often using a more formalized, checklist-driven process specifically because the arranger has to represent several participant lenders' interests, not just their own. That formality tends to mean less room for an undocumented explanation to substitute for a written one — exactly the kind of setting where the documentation habits described in the previous section matter most.

Either way, the underlying ten checks don't change. What changes is how forgiving the process is of an answer that isn't already written down, which is one more reason to treat documentation as routine rather than something assembled only once a question is actually asked.

One more practical difference worth knowing: a syndicated facility's formal review cycle is often slower to respond to a raised issue than a single relationship manager would be, simply because a lead arranger frequently needs to circulate a question or an update among participant lenders before responding. That lag isn't a sign of a bigger problem — it's a structural feature of how a syndicate operates — but it's worth building into how quickly you expect a response when something genuinely does need clarifying.

It also changes how a borrower should time a proactive disclosure. Raising a near-miss with a single relationship manager two weeks before a deadline often still leaves time for a same-week conversation. Raising the same issue with a syndicate's lead arranger benefits from more lead time precisely because the internal circulation step adds days that a bilateral relationship simply doesn't have to account for.

Facility size interacts with this too. A borrower with a single small term loan and a borrower carrying several facilities across different lenders face the same ten checks, but the second case multiplies the documentation burden — each lender's covenant package needs the same underlying figures, sometimes presented differently, and an inconsistency between two packages prepared for two different lenders in the same quarter is its own kind of red flag, one that has nothing to do with the underlying financial health and everything to do with process discipline.

A borrower moving from a single relationship-bank facility to a first syndicated deal is often surprised by this shift specifically — the underlying financial discipline hasn't changed at all, but the communication rhythm around it has, and building that extra lead time in from the first quarter avoids a certificate landing later than intended simply because the internal syndicate process took longer than a smaller facility's would have.

flowparse.io

Turning this into a routine, not a scramble

Every one of these ten checks can be run by a finance team on its own, at any point, without waiting for a lender to request the package. Matching figures to source statements and cross-checking against bank records answers the first several points directly; several others are more about documentation discipline — tracking add-backs, noting accounting changes — built up over time rather than reconstructed once a period.

Finance teams that run this checklist as a routine part of closing each period, rather than as a reaction to an upcoming deadline, describe their actual covenant reviews as largely uneventful — not because the lender's process changed, but because there's nothing left for it to discover.

flowparse.io

Frequently asked questions

Keep reading