A technical default (also called a covenant default or non-monetary default) occurs when a borrower violates a loan agreement's terms — a financial covenant, a reporting requirement, an insurance lapse — without missing a payment. It gives the lender the same remedies as a missed-payment default: acceleration, rate step-up, or collateral enforcement. See occ.gov's Comptroller's Handbook on Loan Portfolio Management for the regulatory framework banks use to classify covenant defaults.
Loan default comes in two forms. A payment (or monetary) default is straightforward: the borrower misses a scheduled payment. A technical default is everything else — a violation of the debt covenants and other obligations spelled out in the loan agreement that has nothing to do with whether payments are current. A borrower can be current on every payment and still be in technical default. The most common triggers are financial-covenant breaches — falling below a minimum DSCR or current ratio, or exceeding a maximum debt-to-equity ratio — and affirmative-covenant lapses, such as failing to deliver financial statements on time, letting required insurance coverage expire, or missing a tax payment. A material adverse change in the borrower's financial condition can also trigger a technical default under a MAC clause, even between scheduled covenant tests. Why lenders bother: a covenant package exists to give the lender an early warning system. Waiting for a missed payment means the lender only finds out about distress after cash has actually run out. A financial-covenant breach — say, DSCR dropping to 1.05x against a 1.20x minimum — flags deteriorating performance while the borrower can often still cure it, well before a payment is actually missed. Once a technical default occurs, the lender's contractual remedies are usually identical to those for a payment default: the loan agreement's cross-default clause can pull other facilities into default too, a notice of default starts a cure-period clock (commonly 30-90 days for non-monetary defaults, longer than the 5-15 days typical for a missed payment), and an unwaived technical default can trigger the loan's default interest rate step-up even though every payment was made on time. In practice, lenders frequently waive isolated technical defaults (a covenant waiver or amendment) rather than exercise remedies, especially for an otherwise-performing borrower — but the lender is not obligated to, and the leverage a technical default hands them in a subsequent negotiation is real.
A payment default means a scheduled payment was missed. A technical default means some other loan-agreement obligation was violated — a financial covenant, a reporting deadline, an insurance requirement — while payments stayed current. Both give the lender contractual remedies, but a technical default can happen even when the borrower has never missed a payment.
Contractually, often yes — most loan agreements don't distinguish between a serious covenant breach and a minor administrative lapse when it comes to available remedies. In practice, lenders usually waive isolated, easily-cured technical defaults (especially reporting delays) rather than accelerate, because foreclosure or collection is expensive and a performing borrower is a better outcome. But the lender isn't required to be lenient, and each technical default resets that leverage in the lender's favor.
It can. Most loan agreements don't limit the default interest rate step-up to missed payments — a covenant breach or other technical default can trigger it too, even though the borrower has been paying on time. Whether the lender actually imposes it, versus waiving the default along with a fee, depends on the relationship and how the loan agreement is written.
It depends on the loan agreement's notice-of-default provisions, but non-monetary (technical) defaults typically get a longer cure period than missed payments — commonly 30-90 days, versus 5-15 days for a payment default — because curing a covenant breach or reporting lapse usually takes more time than simply paying an overdue amount.
Yes, if any of your other credit facilities contain a cross-default clause. Those clauses let a default on one loan (including a technical default) automatically trigger default on another loan, even if that other loan's own payments and covenants are fully current — which is why lenders and borrowers both need to map cross-default exposure across a business's full debt stack.