GASB-87 Compliance: Why Legacy Systems Struggle (And What Airports Must Do About It)

Let's simplify GASB-87 in an airport-friendly way:

GASB-87 requires airports to properly classify, track, amortize, and report all leases - including airline, tenant, concession, and utility agreements.

In more detail, it requires:

• Lease classification
• Right-of-use asset calculation
• Interest & amortization schedules
• Lease modifications
• Termination adjustments
• Discount rate management
• Document evidence
• Renewal & expiration workflows
• Consistent reporting
• Traceable audit trails

If your heart rate went up reading that list… you’re not alone.

Most airport systems were built when:

• Leases were simpler
• Documentation was physical
• Manual reconciliation was acceptable
• Audit standards were lighter
• Financial rules weren't as sophisticated

GASB-87 demands precision and automation, neither of which legacy systems can reliably deliver. Let's break down the major gaps.

Legacy systems often:

• Store summary lease info
• Store incomplete or high-level terms
• Don't track amendments properly
• Don't store version histories
• Don't link documents to terms
• Don't support complex rent structures
• Don't track non-standard agreements
• Don't support detailed interest schedules

Example:

If your system can't tell you:

• Which lease version is current
• When amendments were made
• How rent is structured
• What escalation rules apply
• How options affect valuation

…then you can't produce accurate GASB-87 schedules.

Airports rely on spreadsheets for:

• Lease classification
• Discount rate calculation
• Amortization schedules
• Payment schedules
• Termination adjustments
• Renewal logic
• Asset depreciation
• Balancing reconciliations

Spreadsheets become:

• Fragile
• Error-prone
• Version-conflicted
• Uncontrolled
• “Temporary solutions” that last 5 years

GASB-87 explicitly advises against heavy spreadsheet reliance - with good reason.

Legacy systems cannot:

• Determine whether an agreement qualifies as a GASB-87 lease
• Apply classification rules
• Reclassify leases when terms change
• Track changes to classification logic

Without automated classification, finance teams must manually interpret every lease.

That’s slow. That’s inconsistent. That’s risky.

GASB-87 demands:

• Calculating lease liabilities
• Schedules for right-of-use assets
• Interest expense breakdowns
• Amortization entries
• Adjustments when leases terminate

Legacy systems have trouble creating:

• Accurate amortization schedules
• Updated schedules after modifications
• Time-period calculations that stay consistent
• Supporting documentation auditors can review

That's why so many airports build these schedules by hand.

And it's why auditors keep asking: "Where did this figure come from?"

The GASB Statement no. 87 demands a complete paper trail:

• The original lease agreements
• Modifications made through amendments
• Any addendums added later on
• Summary sheets outlining key terms
• Relevant email and other correspondence
• Explanation for discount rate choices
• Documentation explaining lease classification
• Calculation worksheets to back up the numbers
• Records showing complete version history

The struggles of using a legacy system:

• Files end up getting stored all over the place with no consistency
• There's no link between a file and the lease it relates to
• There's no revision history to track changes made to a file
• Nobody's monitoring when things expire or come up for renewal
• You can't tell which document version was used at a specific time
• No timestamps to submit to auditors as proof

If your documentation is on vacation when auditors come knocking, that is sure to end up in their report.

Lease details change whenever:

• A tenant expands their footprint
• Airlines adjust usage parameters
• Utility agreements are updated
• Contracts are due for renewal
• The occupancy numbers shift

With legacy systems, you're stuck with:

• Back-and-forth email exchanges
• Tiring manual data entry
• Hopping between spreadsheets to stay in sync
• Logging into multiple systems one by one

What GASB-87 actually requires:

• Information that is consistent across all departments
• Complete information with no gaps or inaccuracies
• Numbers that reflect what's happening now
• A clear path to trace all changes

Legacy platforms give you none of this.

When auditors show up, they want to know:

• Who made the change?
• What time and date did it occur?
• Which pieces of information got altered?
• Why was the change necessary?
• What was there originally?
• Was the change authorized?

What older platforms don't track:

• Changes to specific data fields
• Previous versions of records
• Immutable audit logs
• User access levels

The consequences:

• Audit issues
• Undetected financial mistakes
• Extended month-end processes
• Regulatory scrutiny
• Risk of control deficiency citations

Building accurate lease schedules requires pulling information from:

• Your accounting and finance systems
• Revenue tracking tools
• Occupancy record databases
• Utility meter data
• Billing platforms
• Document storage locations

Where legacy systems struggle:

• APIs weren’t part of the design when they were built
• They use monolithic architecture instead of modular components
• No common integration standards link them together
• They weren’t made to handle live data

What happens:

• Schedules show conflicting figures
• Lease liability amounts differ depending on the source
• Amortization math comes out wrong
• Changes in one system don’t carry over to others
• Different departments generate inconsistent reports

Auditors notice these discrepancies immediately.

Clean architecture goes beyond simply upgrading your technology.
It's a game-changing overhaul that makes compliance manageable, accurate, and mostly hands-off.

Here's what changes.

A. Unified Lease Management

Everything consolidates into a single system:

• Primary lease terms
• Amendments over time
• Supplemental addendums
• Space allocation details
• Utility assignments
• All supporting files
• Financial parameters and rates
• Who's occupying what currently
• Billing setup and rules

No more switching between platforms - it all lives in one connected place.

B. Automated Lease Classification

The system classifies leases automatically using GASB-87 rules-no manual work needed.

This removes:

• Different people arriving at different conclusions
• Spreadsheet formulas that are prone to errors
• Worrying about whether you classified things correctly

Your exposure during audits drops substantially.

C. Automated Liability & Asset Calculation

All calculations happen automatically:

• Outstanding lease obligations
• Values for right-of-use assets
• Interest expense broken down by period
• How principal gets paid over time
• Amortization journal entries
• Whatever adjustments are needed

Everything's immediate, accurate, and stands up to audit review.

D. Modern Document Management

The system provides:

• Automatic version tracking
• Monitoring of document uploads
• Alerts when expiration dates approach
• Certificate of insurance management
• Direct links between documents and lease records
• Complete amendment histories
• Secure document storage
• Activity logs for every document

No more scattered files. Everything's organized and traceable.

E. Full Audit Trails

Every change gets documented:

• What specifically was changed
• The exact date and time
• Which user made the modification
• Locked down so nobody can edit it later
• Simple to export into reports
• Organized how auditors like to see it

Auditors need to see the full picture. This shows them exactly that.

F. Real-Time Updates Across Departments

Here's how it flows:

• Operations adjusts something → Finance sees the update seconds later
• A tenant's situation changes → Lease schedules recalculate without anyone touching them
• Utility usage comes in → The system reallocates costs automatically
• Gate usage shifts → Billing rules update in real time
• Something gets billed → The audit record updates at the same moment

GASB-87 depends on everyone working from the same information. Clean architecture ensures that happens.

G. Configurable Rules (No Hard Coding)

Leases don't stay static.

Modern systems let you:

• Adjust business rules as needed
• Have those rules apply automatically
• See exactly how formulas work
• Handle escalations across many years
• Build custom lease arrangements

No more waiting on a vendor to make a simple change to how a lease calculates.

Here's what auditors love:

• Precise data
• Clean schedules
• Clear calculations
• Documented evidence
• Consistent logic
• Full-subledger detail
• Complete change logs
• Result traceability

Clean architecture systems deliver all of this, resulting in:

• Fewer follow-up requests
• Faster audits
• More trust
• Lower audit cost
• Fewer findings
• Fewer management letter comments

They make everyone's life easier.

GASB-87 is complex, but manageable.

Legacy systems make it nearly impossible.

Modernizing goes beyond just checking compliance boxes-it fundamentally improves:

• How accurate your data is
• How efficiently teams work
• How transparent your processes are
• How prepared you are when auditors show up
• The integrity of your financial records
• The burden on your staff
• Operating expenses
• How predictable your outcomes become
• Your ability to manage risk

Clean architecture equips airports with what they need to maintain compliance-reliably, with confidence, and without the usual headaches.