Why AP and Lease Data Never Match — and What It's Quietly Costing You

Ask an accounts payable team and a lease administration team to describe the same location's rent obligation, and you'll often get two different numbers. Not because either team is careless — because they're working from two different sources of truth that were never designed to stay in sync.

That gap is one of the most common, and least visible, sources of occupancy cost leakage in multi-location portfolios.

Where the Mismatch Starts

Lease data typically lives with real estate or lease administration — the abstract, the amendments, the escalation schedule. Payment data lives with AP, usually in an accounting or ERP system built around invoices, not lease terms.

The two systems update on different schedules, get maintained by different people, and rarely talk to each other directly. A rent increase gets recorded in the lease file the day the amendment is signed. It may not reach AP until the next invoice arrives — if it reaches AP correctly at all.

What Gets Missed When the Two Diverge

The disconnect rarely shows up as one dramatic error. It shows up as a pattern of small ones:

• An escalation that took effect but was never updated in the payment schedule
• A vendor credit or landlord concession that lease admin knows about but AP never applied
• A lease amended to change CAM responsibility, while AP kept paying the old allocation
• A location that closed or was subleased, with payments continuing on autopilot
• A renewal that changed rent, filed correctly by real estate but not reflected in the next payment run

Individually, each of these looks like a minor administrative gap. Across a portfolio of dozens or hundreds of locations, they add up to real, recurring overpayment — the kind that doesn't show up on a monthly P&L until someone goes looking for it.

Why This Isn't a People Problem

It's tempting to treat AP-lease mismatches as a training issue — remind the team to check the lease file, add a step to the process. That helps at the margins, but it doesn't fix the underlying structure.

The real issue is that lease terms and payment execution sit in different systems, owned by different departments, with no shared, single source of truth between them. As long as that's true, drift is the default outcome, not the exception.

Reconciling AP and Lease Data

Closing the gap doesn't require replacing either system. It requires connecting them:

• Establish one lease abstract as the authoritative record for rent, escalations, and CAM allocations
• Build a recurring reconciliation cadence — quarterly at minimum — comparing what AP is paying against what the current lease says it should be paying
• Assign clear ownership for updating payment instructions whenever a lease is amended or renewed
• Flag payments tied to leases that have changed status — subleased, terminated, or under renegotiation

The Bottom Line

AP and lease data rarely match perfectly on their own — not because anyone is doing their job poorly, but because nothing is actively keeping them aligned. For growing portfolios, that gap is one of the quieter places where occupancy costs leak, and one of the more straightforward ones to close once it's visible.