Aloan monitors covenants from the record the loan was approved on. A covenant or reporting requirement written as a condition of approval carries the monitor's own terms, becomes active on the relationship the day funding is recorded, and is tested every period by the same Global Cash Flow engine that produced the DSCR in the credit memo. A nightly sweep opens each period's test, asks the borrower and each guarantor for the documents through the portal, and proposes each result once the period's analysis is published. The portfolio manager confirms, waives or records the breach. The Portfolio shows every note with its relationship's compliance state and exports the register.
Covenant monitoring is the post-booking discipline of testing borrower compliance with the financial, reporting and operational covenants in the loan agreement. It begins after the credit memo closes and runs for the life of the loan. Done well, it gives the bank an early warning months before a problem credit shows up in past-due reports. Done badly, it becomes a tickler file the portfolio manager updates after the fact, and the bank learns about a breach when the borrower volunteers it or the file is pulled for an annual review.
The reason it is hard at community-bank scale is capacity. A single portfolio manager often tracks fifty to a hundred active relationships, each with three to six covenants on different reporting cadences. The work repeats per borrower per cycle: pulling the right documents on time, spreading the statements that arrive, calculating each covenant correctly, and surfacing the exception so the credit team can decide what to do. Without automation, the first three consume so much time that the fourth, the judgment work, gets compressed.
This page covers how the covenants get onto the loan, what one monitoring cycle looks like, how the compliance state rolls up to the portfolio, and the two neighbours of covenant work on the same record: collateral and lending limits. For the upstream workflow, see the commercial loan underwriting platform; for the approval that sets the conditions, see approval and closing; for the spreading that powers each calculation, see AI financial spreading software.
Setup
Where the covenants come from
Every covenant belongs to the relationship, whichever credit decision stated it, and each one carries the terms the monitor tracks: for a financial covenant the metric (global DSCR, current ratio, quick ratio, debt to tangible net worth, tangible net worth, working capital), the comparison and the level; for a reporting requirement what is delivered (financial statements, business or personal returns, a personal financial statement, an insurance certificate, agings, a rent roll, a schedule of real estate owned, a debt schedule, a borrowing base or compliance certificate), from whom and how often. Each also carries its cadence, its first period, the days after period end until documents are due, the grace period, the reminder lead and the chase interval, and the party it binds. Covenants reach the relationship three ways.
From the conditions of approval
A covenant or reporting row on the deal's requirements is written in the monitor's vocabulary before the memo is submitted and frozen with the approval. When funding is recorded, every row with complete terms becomes a covenant or deliverable on the relationship, active from booking. A row the memo stated but whose terms do not fit the vocabulary is flagged for the analyst to complete rather than guessed.
From an imported credit memo
A bank brings a relationship onto Aloan from its latest credit memo, renewal or annual review. The import reads the loans as notes, the parties, the spreads, the rating and the covenants the memo states, and pauses on the covenants for the analyst to confirm each one before anything is recorded. A second import updates what is on file rather than duplicating it.
Typed on the relationship
On the relationship's Covenants tab, a covenant or reporting requirement defined by hand, naming the party it binds and, optionally, its first period. A cadence, first-period or deadline change reschedules the open periods.
One period
The monitoring cycle
A covenant test is one period's work on a relationship: every covenant task due for that period end, the documents it asks for, the results decided, and the close. It runs in the order of the work.
The test opens on the calendar. A nightly sweep opens the relationship's covenant test when a task's request date arrives, one test per relationship and period, and it shows up on the relationship page and in the Portfolio's attention line. A portfolio manager can open it early from a task. When a loan review is already open for the period, the review claims the tasks, so nothing is tested twice.
Documents are requested through the portal. Opening the test issues a data request for each reporting task, due on the task's due date: financial statements and business returns to the borrower, a personal financial statement or return to each guarantor. The requests appear in the borrower's portal and the email goes to the relationship's monitoring contact. Each reporting row shows the dated steps its terms set (request when the period ends, reminder before the due date, due, overdue after grace, chased on an interval), with a preview of the email the borrower sees. A document that arrives by any route, the portal, a lender upload or a bulk upload, moves the task to received, or received late past the due date. A document the bank holds in its own files is recorded as received outside Aloan with who confirmed it; a period that does not apply is retired. A reporting task never passes or fails; it is received, outstanding or overdue.
Debt service is confirmed, not assumed. A DSCR divides the period's cash by what each party's debt schedule charges for the period. For a period after the memo that figure came from the system (the memo's after-closing case, the latest stated year carried forward, or a schedule computed from the loan terms), and nothing tells the system whether it is what the borrower actually paid. So the test lists every party whose debt the analysis sums, with the figure and where it came from, and asks the portfolio manager for a yes, or to itemize the period from the facilities and other debt on file. A confirmed year becomes the starting point the next period carries forward from, so monitoring builds on the bank's own figures rather than the memo's forward case.
Results are proposed from the published analysis. The statements are spread as they arrive, with every figure cited to its page. Publishing the period's Global Cash Flow proposes each metric covenant's result for the period under test, bound to its task, with the actual value, the headroom and the direction of travel against prior periods. A column whose period end is still ahead is a projection and is never tested. Each result's panel shows the trend chart over recorded periods, this period's calculation, the saved analysis it read and, where the covenant came from a memo, the memo's wording.
The portfolio manager decides. Confirm a pass. For a failure, request a waiver (the through-date and the case for it, prefilled from the result and the requirement, for the officer to edit) or record the breach without asking for anything. Either confirms the result and opens an exception on the covenant; a waiver request stays a request until an officer grants it, and a granted waiver never turns the result into a pass. Dismiss a proposal that misread something and it is set aside until a recompute proposes again. A confirmed failure makes the loan's compliance badge read breach.
Close the test. Close is live once every reporting task is received or settled, every party's debt service is confirmed, and every metric covenant's result is confirmed over that debt, a failure included. The toolbar says what is still owed until then. Closing settles the period's tasks as passed, failed, waived or received, grants any waiver requested on the test, and frees the relationship for the next period. The period's row on the Covenants tab shows the result with a link back to the test, and every step is logged in the covenant's activity record.
Portfolio
Compliance state and the register
Each relationship carries one compliance state, worked out from its covenants' latest tests and deliveries: compliant, waived, needs review, overdue or breach, with setup for a relationship whose covenants are not yet monitored. The Portfolio shows every note with that state beside it, the open monitoring tasks, and the next date a reporting package or test comes due, sorted so that what needs someone is at the top. One click exports the compliance register as a CSV: every note with its relationship, loan number, monitoring state, covenants passing, next due, commitment, maturity and last confirmed test.
A loan review for a fiscal year takes on the covenant periods ending in that year, tests them from the review's own financials, and writes a Covenant Review section into the review memo; its approval is the sign-off on the rating decision and on any waiver the review requested. On the relationship's Financials tab, the Global DSCR booked at close sits beside the latest confirmed test, so the drift from underwriting is one line.
Collateral
Collateral identification and valuation
Collateral is identified on the deal, valued with its source recorded, advanced against at your bank's rates, and pledged to facilities with a lien position. The collateral worksheet is the deal-level view of everything pledged: values, advance rates, LTV and existing liens.
Identification
Real-world assets (income-producing and owner-occupied real estate, land, construction, equipment, vehicles, agricultural land, livestock and crops) are parties on the deal, with an address, VIN, serial number, parcel number or legal description, so they can link existing debts and match uploaded documents. Aggregate pledges (accounts receivable, inventory, cash, a blanket lien, securities) are worksheet rows. The closing checklist adds title, flood, appraisal, environmental, insurance and the mortgage for each pledged property, and lien searches, a security agreement and the UCC-1 where business assets are pledged.
Valuation
Each row carries a market value and its date, with the source recorded: an appraisal, with the as-is, upon-completion or upon-stabilization scenario chosen; a broker opinion; a borrower-stated value offered from a schedule of real estate owned on the deal, with its date; an estimate; or a manual entry. Appraisal values are read out of the appraisal document; rent rolls are read out of the roll, the offering memorandum or the appraisal and compared column by column. The value is what the bank chose and said where it came from; nothing is set until someone chooses it.
Advance rates and LTV
Your bank sets the advance rate for each asset class under its underwriting conventions (the defaults are 80% for real estate, 50% for equipment and vehicles, 75% for receivables, 10% for inventory, 100% for cash), and a deal or a row can override the rate with a reason. A row's lendable value is its market value times its class's rate. Existing liens are linked to the asset they secure, and LTV puts prior liens in the numerator: (proposed loan + prior liens + any debt at or senior to your position) divided by lendable value, so a $1,000,000 property behind a $150,000 prior lien, with a $500,000 loan, is 65%. Net lendable, the value left to advance against, is shown as its own figure. When several facilities share collateral, LTV is ranked per shared asset from the pledge lien positions, so a loan secured only by real estate never inflates the LTV of an equipment loan. Whether a resulting LTV is acceptable is a rule in your credit policy, tested on the Policy tab.
On the record
The saved collateral analysis is what the credit memo's collateral section cites and what the booking sheet carries to loan operations, with each asset and what it is pledged to. Approval locks the collateral, the pledges and the parties. A property the borrower reports on a schedule of real estate owned, or that an imported memo analyzed on its own, lands on the owner's real estate worksheet with its stated value, loan balance, LTV, equity and occupancy. Where a bank lends on a borrowing base, the borrower sends each period's certificate through one link, and the bank reads it line by line against the aging and inventory listing behind it before approving and funding the period.
Limits
Lending limits and exposure
Officer lending authority is set once and checked at approval. Under Settings, Approvals, each person who can sign carries a total lending limit and an optional unsecured limit, each with a start date and an optional end date. Limits cannot overlap, an ended limit stays read-only, and every change is kept with who made it and why. On the approval chain, a sign-off can require that the signer's limit covers the loan, and a line can apply only when the unsecured amount crosses a level. When no officer's limit covers the loan, or the only eligible officer recused, the chain sends the line to its fallback, such as the loan committee, and the record shows where it went. The limit is checked against the commitments on the deal being approved.
Exposure is on the record. A facility that carries an SBA or other government guaranty, or a participation sold pro rata, shows its net bank exposure beside the commitment: the commitment less the participated share, less the guaranty on what the bank keeps. The memo's exposure tables, its total exposure header and the risk rating net it; debt service, LTV and approval routing keep reading the note the borrower signs; the booking sheet carries both to the core. The relationship page sums commitment and outstanding across the relationship's notes and shows the next maturity.
After booking, the insurance certificate and the rent roll on a pledged property are collected as reporting covenants on the loan's own calendar, and the compliance state on the Portfolio reads from them like any other deliverable.
Why Aloan
How Aloan compares to standalone covenant tracking tools
Most covenant tracking tools handle the schedule and the collection and stop there. They generate the calendar, send the request, and store the documents. The portfolio manager still spreads the financials by hand, calculates each covenant in a spreadsheet, and reconciles the borrower's compliance certificate against it. The promise of automation falls apart at the calculation step, which is where most of the time goes.
Aloan covers the full chain because the same engine that powers commercial loan spreading at underwriting runs at every monitoring cycle. The covenant written as a condition of approval carries the terms the underwriter set, the Global Cash Flow that tests it is the one that produced the memo's DSCR, and the source-page citations that survive examiner review on the original memo apply on every test thereafter. A loan review for the year reads the same tests, and the approval that signs the review memo is the sign-off on the rating and on any waiver.
The specialist covenant-only category has widened: established names like BankStride, Cardo AI, CovenantIQ and Smart Capital Center are joined by StarterStack AI (real-time CRE DSCR and covenant monitoring with LOS integration), CovenantFlow from Catalyze Labs (automated covenant reading with earlier breach detection), Yardi Debt Manager (a CRE debt-monitoring module) and Cync Software (covenant monitoring plus spreading). They are credible category players and make sense for institutions that already have a deep underwriting platform and only need to add monitoring. For community banks looking at underwriting and monitoring together, one platform avoids the handoff that makes covenant compliance drift away from underwriting reality over time.
| Tier | Vendor | Best for |
|---|---|---|
| Tier 1 — Integrated underwriting + monitoring | Aloan | Best for community banks and credit unions that want covenant monitoring to share the same source-cited spreading engine and audit trail as the credit memo. Covenants are recorded as conditions of approval, each test reads the period's published cash flow, and the portfolio manager decides each result with the page-level citations examiners ask for. |
| Tier 2 — Incumbent LOS / enterprise platforms | nCino Continuous Credit Monitoring, Moody’s CreditLens, Finastra Loan IQ | Best for institutions that already run the incumbent stack — nCino at over 2,700 customers, about 1,500 of them depository institutions, Finastra at over 7,000 customers — and want monitoring inside the same platform of record. Implementation and module add-ons are scoped per institution. |
| Tier 3 — Specialist covenant tooling | CovenantIQ, CovenantFlow, BankStride, Cardo AI, Cync Software | Best for lenders that already have an underwriting workflow they intend to keep and only need a covenant tracker bolted on. The catch is the spreading and calculation step usually still runs in spreadsheets, so the calendar gets automated while the math stays manual. |
| Tier 4 — CRE-specific monitoring | StarterStack AI, Yardi Debt Manager, Blooma | Best for CRE-only portfolios where DSCR, debt yield, and rent-roll covenants drive the surveillance program. Coverage typically excludes C&I, owner-occupied, and ABL exposures. |
Aloan is the only AI-native commercial LOS that uses the same source-cited spreading engine for both the credit memo and every covenant test thereafter — the covenant written at approval is the covenant tested at every period, and every calculation links back to the exact page of the borrower’s financial statement.
Best for community banks and credit unions that want to manage covenant compliance, collateral and ongoing credit risk on the same platform they used to underwrite the loan, in production in two to four weeks with no LOS migration, no Salesforce dependency, and no separate covenant-tooling vendor to procure.
Covenant monitoring — FAQ
How do you automate covenant monitoring for commercial loans?
Put the covenants on the loan as records with their terms, then let the calendar run. In Aloan each covenant carries its metric, comparison and level (or, for a reporting requirement, what is delivered and from whom), its cadence, its first period, the days after period end until documents are due, the grace period and the party it binds. A nightly sweep opens a covenant test for the relationship when a period ends, issues the document requests to the borrower and to each guarantor through the portal, and emails the relationship's monitoring contact. As statements arrive they are spread, the Global Cash Flow for the period is published, and each metric covenant proposes its result from that analysis. The portfolio manager confirms the pass, requests a waiver or records the breach, and closes the test. The result, the calculation and the source pages stay on the record.
Where do the covenants come from?
Three places, and none of them is retyping. Conditions of approval: a covenant or reporting requirement written on the deal before approval carries the monitor's own terms, and when funding is recorded it becomes an active covenant on the relationship. An imported credit memo: when a bank brings a relationship onto Aloan from its latest memo, renewal or annual review, the covenants the memo states are read out and paused for the analyst to confirm before they are recorded. Typed on the relationship's Covenants tab: a covenant or reporting requirement defined by hand, naming the party it binds and its first period.
What is covenant monitoring software?
Covenant monitoring software tracks borrower compliance with the financial and operational covenants written into a loan agreement after the loan funds. The useful version does three things: collects required documents on the cadence the loan agreement specifies, calculates each covenant from the source documents instead of trusting borrower-reported numbers, and produces an examiner-ready record when a covenant is tested, breached, waived or amended. Tools that only build a calendar and email the borrower do not solve the underlying problem.
What are the most common covenants in commercial loans?
The most common financial covenants are debt service coverage ratio (DSCR), debt to EBITDA leverage, fixed charge coverage ratio (FCCR), and minimum tangible net worth or liquidity floors. CRE deals add debt yield and loan-to-value. Reporting covenants typically include audited annual financials within 90 to 120 days of fiscal year-end, interim financial statements quarterly, and a compliance certificate from the borrower with each reporting package. Negative covenants restrict additional debt, asset sales, ownership changes, distributions above a threshold, and capital expenditures above a cap. Affirmative covenants require maintaining insurance, paying taxes, and providing access to records.
How does Aloan handle collateral?
Collateral is identified on the deal as a party or a worksheet row, with its address, VIN, serial number or legal description, and valued with the source recorded: an appraisal (as-is, upon completion or upon stabilization), a broker opinion, a borrower-stated value from a schedule of real estate owned, an estimate or a manual entry. The collateral worksheet applies your bank's advance rate for each asset class (real estate, equipment, vehicles, inventory, receivables, cash and so on), links the existing liens secured by each asset, and computes LTV with prior liens in the numerator: (proposed loan + prior liens) divided by lendable value. Net lendable is shown as a separate figure. Pledges carry a lien position per facility, so when several facilities share collateral the LTV is ranked per shared asset. The memo cites the saved collateral analysis, approval locks the collateral and pledges, and the closing checklist adds title, flood, appraisal, environmental, insurance and the mortgage for each pledged property.
Does Aloan manage lending limits?
Officer lending authority, yes. Each person who can sign carries a total lending limit and an optional unsecured limit, each with a start date and an optional end date, and every change is kept in the audit history. A sign-off on the approval chain can require that the signer's limit covers the loan, and when no officer's limit does, the chain sends the line to a fallback such as the loan committee. The limit is checked against the commitments on the deal being approved. Aloan also shows exposure: a facility's net bank exposure after a participation and any SBA or government guaranty, and the relationship's total commitment and outstanding across its notes, with the next maturity.
How does covenant monitoring connect to underwriting?
The same engine runs both. The Global Cash Flow that produced the DSCR in the credit memo is the analysis a covenant test reads from for a later period, with the same add-backs, the same debt schedule and the same source-page citations. The DSCR booked at close sits beside the latest confirmed test on the relationship's Financials tab, so the drift from underwriting is one line. Banks that run separate underwriting and monitoring systems re-key the covenant set and the calculation, which is where the error comes from.
What is the difference between covenant monitoring and annual reviews?
A covenant test is one period's work on a booked loan: the documents in, the debt service confirmed, the results decided, the test closed. It is opened by the calendar. A loan review examines the relationship for a fiscal year: the notes, the parties, the covenant periods ending in the year, fresh financials against the baseline the bank underwrote to, and a review memo that commits to a rating decision. When a review is open for a period, it claims that period's covenant tasks, so the same documents and the same analysis serve both and nothing is tested twice.
Can AI covenant monitoring replace a portfolio manager?
No. Aloan does the document collection, the spreading, the calculation and the proposal of each result, which is the work that scales with portfolio size. The portfolio manager confirms the debt service for the period, decides each result, chooses between a waiver request and a recorded breach, and owns the conversation with the borrower. The combination is what lets a community bank monitor a larger book without a proportionally larger team.
Related
Approval and closing. Where the conditions, covenants and reporting requirements are written and frozen with the approval. See commercial loan approval and closing.
Pipeline and portfolio reporting. The Portfolio, the compliance register export and the record on every deal. See pipeline and portfolio reporting.
Commercial loan underwriting platform. The originating workflow that sets up the covenant data. See commercial loan underwriting platform.
Financial spreading. The spreading engine that powers every covenant calculation. See AI financial spreading software.
Global cash flow analysis. The analysis each covenant test reads from. See global cash flow analysis.
Covenant headroom calculator. Quantify cushion before a breach for DSCR, FCCR, leverage, debt yield, and current ratio. See the covenant headroom calculator.
Covenant monitoring best practices. The operating discipline behind moving a portfolio off spreadsheet trackers onto an automated, source-traceable program. Read the covenant monitoring best practices guide.