Handling landlord charge exceptions in outsourced accounting
Routine landlord billing is easy. The estimate comes each month and matches the schedule. The bookkeeper codes it to recurring CAM expense. The books show the period right.
Exceptions are where the work starts. Think of a back-dated adjustment or a special assessment. Think of a code-required upgrade pass-through. Think of a parking lot resurface that should be amortized. Amortized means the cost spreads over the years the asset lasts. Each of these needs a lease check before you can code it right.
A firm with no process for exceptions has two bad options. It delays the close. Or it codes the item to the wrong account.
I built CAMAudit for the lease check. That step is where structured detection saves the most time. But the structure for handling exceptions has to live in your workflow first. No tool can help until it does.
Landlord Charge Exception: Any landlord-issued bill or line item that does not fit the recurring monthly estimate pattern and requires lease validation before it can be coded to a permanent expense account. Common exception categories include special assessments, retroactive adjustments, code-required upgrade pass-throughs, capital improvements, make-ready charges, and unfamiliar billing line items. A defined exception handling workflow ensures these items are validated against the lease, coded correctly, and resolved within a target timeframe rather than disappearing into the recurring expense ledger.
Why exceptions need their own workflow
Exceptions look like one-off events. Across a book of commercial real estate clients, they are not. They add up to steady work that needs a set process.
Picture a firm with 25 commercial real estate clients. Each has two to four leased properties. That firm will see about 30 to 60 landlord charge exceptions a year. With no set process, each one gets handled on the fly. The bookkeeper guesses at the right account. Or asks the controller. Or codes it to recurring CAM and moves on. The first two paths eat time. The third one hides overcharges and warps the books.
The fix is a set workflow. It handles every exception the same way. It scales with the size of your book. And it leaves a record of how each item was resolved.
Use four accounts
The chart of accounts for a client should support exceptions from the start. Four accounts, or sub-accounts, are the smallest setup that works.
Recurring CAM expense. This holds the routine monthly estimate payments. Anything coded here should be a repeat, checked, lease-allowed pass-through. This account is the base for trend analysis, budget compares, and reconciliation tying.
Landlord charge holding account. This holds any non-routine landlord charge until you check it. The bookkeeper codes anything unfamiliar here. The controller reviews and clears it during the month's close. The balance should stay near zero. Items move out within 30 days of receipt.
Special assessment expense. This holds one-time charges the lease allows. Think code-required upgrades, certain repairs, and make-ready charges. Items move here from the holding account once checked.
Capital amortization expense. This holds items the lease says to amortize over their useful life. You do not expense them all at once. The full bill goes to a balance sheet asset account. The periodic amortization flows through this expense account.
These four accounts split the recurring base from the exception traffic. That protects your trend analysis. It also gives you clean working papers for the year-end reconciliation review.
Run the workflow in four steps
The workflow runs in four steps.
Step 1: the bookkeeper spots the exception. During monthly close, the bookkeeper checks each landlord charge against the expected estimate. Anything that does not match gets flagged. That covers a different amount or a different category. It also covers a back-dated line item or a special assessment. The bookkeeper codes it to the holding account. Then they log it in an exception register. The log notes a few things. It notes the date received, the amount, a short description, and the landlord. It also notes why the item is in the holding account.
Step 2: the controller checks it against the lease. This happens during the month's close. For higher-volume clients, use a set weekly review window. The controller pulls the lease and checks each exception. The check answers three questions. Does the lease allow this charge category? At what amount? And what is the right accounting treatment: current expense, special assessment, or capital amortization?
Step 3: the controller clears it. Based on the check, the controller decides what to do. Say the charge is allowed and the amount is right. Then they move it out of the holding account. It goes to the right permanent account. That is special assessment, capital amortization, or in some cases recurring CAM. Say the charge is not allowed or the amount is wrong. Then they flag it for a client call and a possible dispute.
Step 4: resolve and document. The controller updates the exception register with the outcome. Some exceptions need a landlord call. You may need support documents for a special assessment. You may need to dispute an unallowed back-dated adjustment. The controller starts that talk and tracks it. The final outcome closes the register entry.
The full cycle from receipt to resolution should run within 30 days. That holds for routine items. Hard disputes may take longer. But they should be in active motion within 30 days.
Know what to escalate and when
Most exceptions resolve at the controller level. Check it, code it right, document it. Escalating to a partner or specialist makes sense in three cases.
A big dollar amount with a disputed lease reading. Say your reading of the lease differs from the landlord's. And say the dollar amount is big enough to matter. Then you need the partner's judgment. The partner decides the dispute plan. The partner also reads the client's appetite for a fight.
A multi-year error that keeps growing. Say one exception reveals a pattern billed and coded wrong for years. The work shifts from a current-period fix to rebuilding history. That is partner-level work. It may benefit from CAM specialist support.
A capital-versus-operating fight. Say the landlord calls a charge an operating expense. But the lease language points to a capital one, or the reverse. That dispute often turns on accounting method questions. A specialist can help analyze it.
Set the escalation rules ahead of time. Write them into your standard operating procedures. Then the bookkeeper and controller know what to escalate without guessing.
The firms that handle landlord exceptions cleanly share one habit. They never let an exception go straight to recurring CAM expense. A controller checks it first. The holding account is what makes that work. We built CAMAudit to support that check. Reading the lease against an unfamiliar charge tells you one thing. It tells you if the charge is allowed, excluded, or amortizable. That is the exact work the platform automates.
Treat the register as your control document
The exception register is your control document for landlord billing. It should record every exception across every commercial lease you handle. It should give you a clear picture of:
- How many exceptions came in a given month or year
- The outcome mix: checked and coded, disputed, escalated
- The total dollar value moving through exceptions
- The resolution time for each exception
- Patterns: are certain landlords producing more exceptions than others
Review the register each quarter. It surfaces useful signals. A landlord with an unusually high exception count may bill in an inconsistent way. That warrants a structured reconciliation review. A run of exceptions may resolve as unallowed. That can mean a landlord is testing the lease limits. That warrants a direct talk. A run of late resolutions may point to a process problem inside your firm.
How CAMAudit supports the workflow
The platform shrinks the check step. That step eats most of the controller's time on exceptions. For any unfamiliar landlord charge, you upload the lease. Then you run the right detection rules. The output tells you one thing. It tells you if the charge is allowed, excluded, or amortized. It gives you a documented basis for the coding call.
For exceptions that go to dispute, the platform builds the structured findings report. That report backs your dispute letter. You have the lease citations and the math ready for the client. You have the variance analysis ready too. Variance analysis compares what was billed against what the lease allows.
Across a book of clients, the platform gives you consistent output. That lets you standardize your exception records and your client messages. See the white-label partner program for the plans. They are built for accounting firms with different job volumes.
Set up the workflow
If you do not have a process for exceptions yet, setup is simple.
Build the four accounts into the chart of accounts for each client. Create the exception register. Use a shared spreadsheet or a tracker in your practice management software. Train the bookkeeper on the holding account and on how to spot an exception. Set the controller's weekly or monthly review window for the holding account. Write down the escalation rules and share them with the team.
The workflow is plain, not fancy. The cost is the discipline to run it the same way every time. The payoff is cleaner books. You get them for every commercial real estate client you serve.
Frequently Asked Questions
What is a landlord charge exception?
A landlord charge exception is any landlord-issued bill or line item that does not fit the recurring monthly estimate pattern: a special assessment, a retroactive adjustment, a code-required upgrade pass-through, a make-ready charge, or any unfamiliar category that requires lease validation before it can be coded to recurring CAM expense. Exceptions are routine in commercial leasing but require a defined handling process so they don't disappear into the recurring expense ledger without scrutiny.
What's wrong with coding exceptions to the same account as recurring CAM?
Two things go wrong. The recurring CAM expense account becomes inflated by one-time items, which distorts trend analysis, budget assumptions, and any cap calculation that uses the prior year as a baseline. And the firm loses visibility into the exception itself: once it's coded to recurring CAM, the line item is indistinguishable from routine expense, and the issue cannot be revisited without combing through twelve months of journal entries.
What's the right account structure for handling exceptions?
The minimum useful structure has a holding account for unvalidated landlord charges, a special assessments account for one-time items the lease authorizes, a capital amortization account for items the lease requires to be amortized, and the recurring CAM account for routine pass-through. The bookkeeper codes any non-routine item to the holding account, the controller validates against the lease, and the item moves to the appropriate permanent account based on the validation outcome.
How quickly should exceptions be resolved?
A reasonable target is 30 days from the bill receipt to a documented resolution. The bookkeeper's monthly close puts unfamiliar items in the holding account, the controller reviews the holding account during the month's close or in a defined review window, and any item that requires landlord communication or document request is in motion within the month it was billed. Exceptions older than 60 days should be escalated; exceptions older than 90 days are a control failure.
How does CAMAudit support exception handling?
CAMAudit identifies the specific lease provisions that govern any landlord charge category, which lets the firm validate exceptions against the lease faster. For a one-time charge that arrives mid-year, the firm can run the lease through the platform to determine whether the charge category is included in CAM, excluded entirely, or required to be amortized. The structured output gives the bookkeeper or controller a documented basis for the coding decision and the eventual resolution.