Duplicate rent payment audit: how to find the rent you paid twice

A duplicate rent payment audit is a review of every payment made under a lease, tested against the lease itself rather than against the vendor record, to identify rent and pass-through charges paid more than once. It matters because rent is the one large, recurring, high-volume payment stream in the business that the standard accounts payable control was never designed to govern.

That last point is worth sitting with, because it explains why these keep happening at companies with clean audits and competent finance teams.

Why your ERP's duplicate check cannot see duplicate rent#

Duplicate detection in a typical ERP keys on three fields: vendor ID, invoice number, and amount. Match two or three of them and the system holds the payment. That control works well for procurement, where a vendor sends a numbered invoice against a purchase order.

Rent defeats all three fields at once. There is usually no invoice number, because rent is due under a contract rather than billed against a purchase order, so AP teams invent a reference like RENT-0326 that varies by who keyed it. The payee changes when a building sells or a management company is replaced, which puts the two payments under different vendor IDs. And the amounts often differ, because one payment reflects the monthly estimate and the other reflects a trued-up figure, an escalated rate, or a partial month. Two payments for the same month, to the same property, can be different in every field the control examines.

The substitute control is the lease. The lease specifies who is owed, how much, when, and under what conditions the obligation ends. Match against that and the duplicates become visible immediately. Match against the vendor master and they stay invisible for years.

Where duplicate rent payments come from#

Seven patterns account for most of what a first-pass audit finds. Each one has a specific test, and none of the tests is the one your ERP is already running.

The last pattern is the one most often missed, because the payment itself is not a duplicate. One payment went out, and it was correct in total against the statement. The duplication happened inside the landlord's own accounting, and it only surfaces if someone reads the lines. That is the same discipline a CAM reconciliation review applies to pass-through charges, pointed at the rent line instead.

How to run a duplicate rent payment audit#

Define the population. Pull every disbursement coded to rent and occupancy accounts for the review period, by property and legal entity. Include payments made by property managers, brokers and escrow agents on the company's behalf, which is where AP-only reviews go wrong.

Anchor to the lease, not the vendor. Build the expected payment schedule from the abstracted lease terms: base rent, escalations, estimated pass-throughs, and the dates each obligation begins and ends. The audit is only as good as the abstraction behind it, so confirm the abstractions are current before you trust the variances. See lease abstraction.

Run the rent-specific match keys. Same lease and same period at any amount. Same amount within a ten day window at any payee. Same period with two different payees. Any period with more payments than the schedule calls for. Run these instead of, not in addition to, the vendor-and-invoice-number key.

Test the change events. Expiration, unexercised renewal, site exit, assignment, sublease, landlord sale, executed amendment, reconciliation settlement and remeasurement should each have stopped or changed a payment stream. Where the stream did not change, you have either a duplicate or an overpayment. The accounts payable audit framework for rent covers the full set of change events and the controls around them.

Reconcile at the line level. Compare each landlord statement line against the lease schedule and the exclusions the lease actually names. Totals reconcile; lines do not.

Confirm before you claim. Request the landlord's statement of account for the period. A payment that looks duplicated in your ledger is sometimes a correctly applied credit on theirs, and discovering that after you have sent a demand letter costs goodwill you will want during the next renewal.

Fix the source, not the instance. Every recovery should close with a change to the thing that caused it: the vendor master record, the payment schedule, the notice party, or the date that never triggered.

What the accounting looks like when it happens#

A duplicate rent payment does not announce itself as a missing or excess liability. Under ASC 842 and IFRS 16 the lease liability unwinds on its own amortization schedule, driven by the lease terms rather than by what cash left the bank. Pay twice in March and the liability still steps down by one March payment. The extra cash lands somewhere else: an unexplained prepaid balance, a plug in the rent accrual, or a variance in the cash-to-liability rollforward that someone clears at quarter end because it is small relative to the portfolio.

This is the practical reason duplicates survive audit. They are individually immaterial and collectively significant, and the account they distort is the one nobody reconciles line by line. Reviewing the rollforward variance by property, rather than in aggregate, turns a rounding difference into a list of sites worth investigating. Teams working through this at close will recognize the pattern from closing ASC 842 without surprises.

How much is actually there#

Be careful with the numbers in this category, because the eye-catching ones tend to come from firms selling recovery services and rarely name a primary source. The figure worth citing comes from a state audit office. The Washington State Auditor's Office reported in February 2022 that duplicate payments range from 0.8 to 2 percent of an organization's total payments, and identified three drivers: multiple vendor records for the same vendor, decentralized invoice entry, and inconsistent invoice number entry that bypasses system controls (Washington State Auditor's Office).

That figure covers all payments, not rent specifically, and it is a share of payment count rather than of spend. Apply it to a lease portfolio with judgment rather than arithmetic. What it does establish is that all three named drivers are present, and worse, in rent: duplicate vendor records are routine after landlord sales, entry is decentralized across regions and managing agents, and rent has no vendor-supplied invoice number to be consistent about in the first place.

if a rent-specific duplicate payment rate is required. No credible primary source for one currently exists, which is itself an argument for publishing REAL's own figure once one is cleared.

Recovering it#

Recovery is a contract matter, and the window depends on the lease and the jurisdiction rather than on any general rule, so involve counsel before sending anything that reads as a formal claim. Two practical points hold regardless. First, the audit rights clause in most leases governs disputes over reconciliations and pass-throughs, and it often carries a short window measured in days from the statement date, so a duplicate discovered inside a reconciliation is time-sensitive in a way a duplicated base rent payment usually is not. Second, landlords settle documented duplicates far more readily than contested expense interpretations, because there is nothing to argue about once both ledgers are on the table. Start there, and leave the interpretive disputes for a CAM recovery audit.

Stopping the next one#

Detection is a project. Prevention is a control, and it comes down to one rule: no payment goes out that has not been checked against the lease that authorizes it. In practice that means the charge schedule lives with the lease rather than in a spreadsheet beside it, the notice and remittance party updates when the building sells, the critical date that ends an obligation actually stops the payment stream rather than sending an email to someone on leave, and the reconciliation settlement resets the estimate the same week it is agreed.

Portfolios past a few hundred leases stop being able to do this by hand, which is where checking every charge against the lease before you pay it earns its keep: reading each invoice and landlord statement, splitting it into base rent, CAM, tax and insurance, comparing each line against the lease terms, and routing only the exceptions to a person. The broader control environment around this sits in financial operations, and the dates that should stop a payment sit in critical dates and notices.

The honest summary: most companies do not have a rent duplicate problem because their people are careless. They have one because they applied a procurement control to a contract obligation, and the control has no way to see the thing it is supposed to catch.