Hidden Lease Risk in Aerospace: Why Your ERP Isn’t Telling the Full Story

In aerospace and defense, a lease is rarely labeled as one, yet it can materially impact financial statements and contract eligibility.

A power-by-the-hour engine agreement that dedicates a specific asset to your operations? That's a lease. A long-term contract for exclusive hangar space at Melbourne International Airport? That's a lease. A dedicated CNC machine on your production floor that's embedded in a broader service contract? That's a lease too, even if nobody in your finance department has ever classified it as one.

This gap between what's physically happening on the shop floor and what's showing up in the accounting ledger is called Sync Drift. This isn't just a bookkeeping issue, It's a financial reporting risk that touches your balance sheet, your debt covenants, and your contract eligibility.

Here's what makes aerospace uniquely vulnerable.

ASC 842 requires companies to identify and recognize leases that are embedded inside larger service contracts. In most industries, this is a manageable exercise. In aerospace, it's a minefield.

Consider what a typical defense contractor's vendor portfolio looks like: maintenance agreements that dedicate specific test equipment to a facility, logistics contracts that assign particular vehicles or aircraft to a program, service arrangements that include exclusive use of specialized tooling. Every one of these contracts potentially contains an embedded lease that should be on the balance sheet, and most automated lease accounting software will never flag them, because the lease language is buried inside service contract terms that the software isn't designed to extract.

This is where forensic analysis matters. A forensic approach doesn't start with the data an ERP feeds into the system. It starts with the physical contract, reads every clause, and asks: is there an identified asset? Does the lessee control its use? Is there an economic benefit flowing to one party? If the answers are yes, you have a lease,regardless of what the contract calls itself.

Consider a common scenario in this industry. A company leases a complex aerospace asset. An integrated avionics testing platform, for example. The entire arrangement is classified as an operating lease. The rent hits the income statement, EBITDA looks clean, and everyone moves on.

But when you pull the contract apart forensically, you find that the platform contains a high-value specialized component: A proprietary sensor array, a dedicated propulsion testing module, or a classified instrumentation package that meets the criteria for separate lease classification. That component, on its own, triggers finance lease treatment. Suddenly the balance sheet carries additional debt. The debt-to-equity ratio shifts. EBITDA changes. And for a government contractor whose financial ratios affect contract eligibility, that reclassification is operationally consequential.

Most firms don't separate components because their software treats the lease as a single unit. A forensic review asks whether it should be.

In Aerospace, a leased component might be manufactured in one jurisdiction, integrated into a fuselage in another, and deployed operationally in a third. Each of those locations carries different tax treatment for the right-of-use asset.

This is a common pattern on the Space Coast: companies whose headquarters are in one state, whose finance teams process leases from another, but whose leased assets are physically operating in Brevard County, Florida. Sales tax and use tax obligations follow the physical location of the asset, not the mailing address of the lessee. If lease schedules don't track jurisdictional tax obligations at the asset level, the company is either overpaying in one jurisdiction or under-reporting in another. Neither is a good outcome.

For companies operating across the U.S.–Canada corridor, the complexity deepens. The U.S. applies ASC 842. Canada applies IFRS 16. The two standards have converged in many areas, but they diverge on critical points: how "reasonably certain" renewal options are interpreted, how discount rates are selected, and how lease modifications are treated. If a portfolio spans both countries, it requires someone who understands both frameworks at the clause level, not just the summary level.

There's one more layer that makes aerospace lease compliance uniquely challenging: ITAR. Defense contractors subject to the International Traffic in Arms Regulations often require that anyone accessing their facilities, including outside consultants performing lease reviews, meets specific citizenship or residency requirements. This means the pool of professionals who can physically walk into a facility, examine the lease documentation on-site, and perform a hands-on forensic review is smaller than most companies realize. It's not enough to hire a remote consultant who can review digital files. Certain facilities require someone who can be on-site, comparing the physical reality of operations to what the ledger says.

Automated lease accounting software is a powerful tool. But in aerospace, more is required. The embedded leases hiding in service contracts, the component separations that software treats as single units, the jurisdictional tax misalignments that schedules don't track, and the cross-border framework differences that finance teams may not have the bandwidth to reconcile, these are the gaps where financial reporting errors accumulate quietly until an auditor finds them.

A forensic approach starts with the contract, not the spreadsheet. It asks questions that software doesn't know to ask. And in an industry where financial statements affect not just investor confidence but contract eligibility and regulatory compliance, that's not a luxury. It's a necessity.