Credit support is one of the most heavily negotiated parts of a commercial lease. A landlord wants protection against a tenant that cannot pay; a tenant wants to avoid tying up capital or carrying a parent guaranty for the full term. The compromise is usually a burn-down: the support starts high and reduces over time or on conditions demonstrating that the tenant has become a better credit.
That compromise creates a set of obligations neither side is well organized to manage. The tenant has to deliver financial statements by a deadline, meet a covenant test, and request the reduction. The landlord has to test the condition, decide, and instruct the reduction. Both of those happen on dates buried in an article of a document that gets read carefully once, at execution.
This guide covers the burn-down structures that appear in practice, the conditions that typically gate them, where the tracking fails on each side, and how to hold the whole arrangement as dated obligations so the reduction happens when it was supposed to. Neither party benefits from the drift, which is unusual and makes this one of the easier things to fix collaboratively.
The structures and what each requires
Burn-down provisions vary in how automatic they are, and the amount of work each creates differs accordingly.
- Scheduled reduction, the support steps down on fixed dates regardless of performance, which is the simplest structure and still requires someone to action the reduction.
- Conditional step-down, reduction occurs on a date only if a financial test is met, which requires statements, a testing method and a decision record.
- Milestone release, the support falls away entirely once a defined event occurs, such as a period of profitability or an equity raise above a threshold.
- Default reset, any monetary or material default during the term suspends or reverses the burn-down, restoring the original level for some period.
- Instrument mechanics, how the reduction is effected, by amendment to a letter of credit, by partial return of a cash deposit or by an amended guaranty, each with its own lead time.
The conditional structures are where the value is and where the failures concentrate. A test date arrives, the statements were due 30 days earlier and were not delivered, and the parties end up arguing about whether the reduction was earned. Neither side benefits from that conversation, and it is entirely avoidable with a diary entry and an owner. The party that tracked the dates arrives at that conversation with a documented position, and the one that did not usually concedes.
Most burn-down provisions require the tenant to request the reduction and provide evidence, and most place no obligation on the landlord to volunteer it. Tenants that do not track their own test dates routinely carry credit support for years longer than they negotiated. From the landlord side, the mirror problem is releasing support without testing the condition, which is a loss of protection that was bargained for.
Where the tracking fails
The failures are symmetrical, which is unusual, and they come from the same root cause on both sides: the terms are in the lease and nowhere else.
- Test dates are not abstracted. Lease abstraction captures rent, term and options, and frequently omits the credit support schedule and its conditions entirely.
- Financial statement deadlines pass. The delivery obligation sits in a covenant article separate from the guaranty, so the two are managed by different people if at all.
- The covenant test is undefined. A test referencing a ratio without defining the components invites disagreement about how it is calculated, particularly where the tenant’s reporting has changed.
- Letter of credit lead time is underestimated. Reducing an instrument requires bank action, and requests made on the test date leave the tenant paying fees on the full amount for another period.
- Defaults are not connected to the schedule. A late payment eighteen months earlier may have reset the burn-down, and nobody links the arrears history to the reduction calculation.
Five steps to make burn-downs work as intended
Step 1, Abstract the credit support terms fully
Capture the initial amount, the instrument type, the reduction schedule, each condition, each test date and the reset or suspension triggers. Standard abstraction templates often stop at the deposit amount, which is the least useful part of the arrangement to know.
Step 2, Define the covenant test in the record
Write down what is being tested, from which financial statements, over what period and calculated how. Where the lease is ambiguous, note the ambiguity now rather than discovering it at the test date, when both parties have an incentive to read it their own way.
Step 3, Diary the statement delivery deadlines
The delivery obligation usually precedes the test date by some weeks and is the more commonly missed of the two. Put it on the record as an obligation with an owner, and treat a missed delivery as an escalation rather than an administrative slip.
Step 4, Build in lead time for the instrument change
Work back from the test date through the request, the decision, the bank amendment and the confirmation. For letters of credit this can be several weeks, and the cost of missing it is carrying the full amount for another cycle.
Step 5, Link the default history to the schedule
Maintain the arrears and default record against the same lease record so that the reset triggers can be checked as part of the reduction decision. Both parties should be able to see the same history, which removes most of the scope for dispute.
See credit support terms as tracked obligations
Watch how burn-down schedules, covenant tests and reduction dates become monitored records with owners.
Why this sits with the rest of the lease data
Burn-down conditions are just another set of dated lease obligations, and they belong in the same place as critical dates, option windows and escalation triggers. Teams that abstract leases well for accounting purposes often stop short of the commercial covenants, which is the gap described in Lease abstraction that holds up under ASC 842. Extending the abstraction to cover credit support and covenant terms costs little once the process exists, and it puts the conditions where the alerting already runs, which is the model set out in Lease Lifecycle Management with Aavenir. For a tenant, the return on capital from a tracked burn-down is often the clearest financial case for improving lease data at all.
Burn-down structure and what it needs
The work each structure creates is quite different, and knowing which one applies determines how much attention a lease needs.
| Structure | Condition | Action required | Lead time |
|---|---|---|---|
| Scheduled reduction | Date only | Instruct the reduction | Short |
| Conditional step-down | Financial test met | Deliver statements, test, instruct | Weeks |
| Milestone release | Defined event occurs | Evidence the event, request release | Weeks |
| Default reset | No default in period | Check arrears history | At each test |
| Letter of credit amendment | Any of the above | Bank amendment and confirmation | Several weeks |
Burn-down provisions are a sensible commercial compromise that frequently fails to deliver what either party negotiated, purely because the conditions sit in a document rather than in a system. The fix is not complicated. Abstract the credit support terms alongside the critical dates, define the test in advance, diary the statement deadline as well as the test date, and leave lead time for the instrument change. Tenants recover capital they already bargained for, and landlords keep protection they are entitled to keep. The terms were negotiated at some cost on both sides, and letting them lapse through inattention wastes that effort entirely.
For related guidance, see ASC 842 and IFRS 16, the lease data auditors test, CRE vendor service contracts and CAM recovery control and Property vendor service contracts, a controls datasheet.
