FIN.12:4.1 - Read the condition as an operative rule

A covenant is a condition of an actual arrangement, with a defined subject, calculation, test time and consequence. Recover the applicable signed terms, amendments and relevant consents. Identify who must satisfy it and which entities, assets or obligations enter the calculation. FDM.3 supplies the event logic, while FDM.1–2 supplies positions and group boundaries. A public description of a typical covenant cannot establish the corporation’s actual obligation.

Translate the rule into the quantities needed for its test. Contractual debt may include or exclude leases, guarantees, subordinated amounts or cash netting. Contractual earnings may use a trailing period, permitted adjustments, caps or a prescribed acquisition treatment. Recover those definitions and reconcile them to the accounts; do not substitute a familiar ratio label. If a term is disputed, retain the alternative interpretations or obtain the responsible specialist’s answer before relying on one.

Distinguish a condition tested periodically from one triggered by a proposed action, and a condition that becomes active only after a stated utilization or other event. A borrower can pass its last quarter-end test yet be unable to draw, acquire or distribute today. Conversely, a projected future breach is not the same as an existing breach. Record the relevant test dates, information cutoffs, certification, notice and remedy dates because they determine when an action remains possible.

The calculation and its consequence are separate. Breach can affect draw permission, pricing, security, repayment or enforcement under the actual terms and applicable rules. A cross-default or cross-acceleration provision can transmit an event into another arrangement, but only if its conditions hold. Do not assume every breach immediately accelerates every liability, or that informal negotiations suspend an obligation.