Managing Landlord Charge Exceptions in Outsourced Accounting

Managing Landlord Charge Exceptions in Outsourced Accounting

Routine landlord billing is easy. The estimate arrives every month, it matches the schedule, the bookkeeper codes it to recurring CAM expense, and the books reflect the period accurately. Exceptions are where the work begins. A retroactive adjustment, a special assessment, a code-required upgrade pass-through, a parking lot resurface that should be amortized: each of these requires lease validation before it can be properly coded, and a firm without an exception-handling process either delays the close or codes the item to the wrong account. I built CAMAudit because the lease validation step is exactly where structured detection saves the most time, but the exception handling structure has to exist in the firm''s workflow before any tool can support it.

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 exception handling is its own workflow

Exceptions look like one-off events. In aggregate, across a portfolio of commercial real estate clients, they''re a recurring volume of work that benefits from a defined process.

A firm with 25 commercial real estate clients, each with two to four leased properties, will see roughly 30 to 60 landlord charge exceptions per year across the portfolio. Without a defined process, each exception is handled ad hoc: the bookkeeper either guesses at the right account, asks the controller, or codes the item to recurring CAM and moves on. The first two paths are time-consuming; the third produces silent overcharges and distorted books.

The fix is a defined workflow that handles exceptions the same way every time, scales with portfolio size, and produces documented resolution for each item.

The four-account structure

The chart of accounts for a commercial real estate client should support exception handling at the source. Four accounts (or sub-accounts) are the minimum useful structure.

Recurring CAM expense. The account that receives the routine monthly estimate payments. Anything coded here should be a recurring, validated, lease-authorized pass-through. The account is the basis for trend analysis, budget comparison, and reconciliation tying.

Landlord charge holding account. The account that receives any non-routine landlord charge until validated. The bookkeeper codes anything unfamiliar here; the controller reviews and disposes within the month''s close cycle. The account should have a near-zero balance at any given time because items move out of it within 30 days of receipt.

Special assessment expense. The account for one-time charges the lease authorizes (code-required upgrades, certain repairs, make-ready charges). Items move from the holding account to this account once validated.

Capital amortization expense. The account for items the lease requires to be amortized over useful life rather than expensed in the period billed. The full bill goes to a balance sheet asset account; the periodic amortization expense flows through this expense account.

This four-account structure separates the recurring expense baseline from the exception traffic, which protects trend analysis and produces clean working papers for the year-end reconciliation review.

The exception handling workflow

The workflow operates in four steps.

Step 1: Bookkeeper identifies the exception. During monthly close, the bookkeeper compares each landlord charge against the expected estimate. Anything that doesn''t match (different amount, different category, retroactive line item, special assessment) is flagged as an exception and coded to the holding account. The bookkeeper logs the item in an exception register: the date received, the amount, the brief description, the source landlord, and a note about why the item is in the holding account.

Step 2: Controller validates against the lease. Within the month''s close cycle (or in a defined weekly review window for higher-volume clients), the controller pulls the lease and validates each exception. The validation answers three questions: Does the lease authorize this charge category? At what amount? What is the correct accounting treatment (current expense, special assessment, or capital amortization)?

Step 3: Disposition. Based on the validation, the controller dispositions the exception. If the charge is authorized and the amount is correct, the controller moves it from the holding account to the appropriate permanent account (special assessment, capital amortization, or in some cases recurring CAM). If the charge is not authorized or the amount is incorrect, the controller flags it for client communication and possible dispute.

Step 4: Resolution and documentation. The exception register is updated with the disposition. For exceptions that require landlord communication (e.g., requesting support documentation for a special assessment, disputing an unauthorized retroactive adjustment), the controller initiates the conversation and tracks the resolution. The final resolution closes the register entry.

The full cycle from receipt to resolution should run within 30 days for routine exceptions; complex disputes may take longer but should be in active motion within 30 days.

What gets escalated and when

Most exceptions resolve at the controller level: validate, code correctly, document. Escalation to a partner or specialist makes sense in three cases.

Material dollar amount with disputed lease interpretation. When the firm''s reading of the lease differs from the landlord''s, and the dollar amount is large enough to matter, the partner''s judgment is needed on dispute strategy and the client''s tolerance for confrontation.

Multi-year compounding error. When an exception turns out to reveal a pattern that has been billed and coded incorrectly for multiple years, the work shifts from current-period exception handling to historical reconstruction. This is partner-level work and may benefit from CAM specialist support.

Capital vs. operating disputes. When the landlord asserts that a charge is operating expense and the lease language supports a capital classification (or vice versa), the dispute often involves accounting methodology questions that benefit from specialist analysis.

The escalation criteria should be defined in advance and documented in the firm''s standard operating procedures, so the bookkeeper and controller know what to escalate without making the call ad hoc.

The firms that handle landlord exceptions cleanly have one habit in common: they never let an exception move directly from the bookkeeper''s queue into recurring CAM expense without controller validation. The holding account discipline is what makes that work. CAMAudit was built to support the validation step, because reading the lease against an unfamiliar charge to determine whether it''s authorized, excluded, or amortizable is exactly the analytical work the platform automates.

The exception register as a control document

The exception register is the firm''s control document for landlord billing. It should record every exception across every commercial lease in the client portfolio and produce a clear picture of:

• How many exceptions arrived in a given month or year
• The disposition mix (validated and coded, disputed, escalated)
• The aggregate dollar value flowing through exceptions
• The resolution time for each exception
• Patterns: are certain landlords producing exceptions disproportionately

Reviewed quarterly, the register surfaces operational signals: a landlord whose exception volume is unusually high may be billing inconsistently, which warrants a structured reconciliation review. A trend of exceptions resolving as unauthorized may signal a landlord who is testing the limits of the lease, which warrants an explicit conversation. A trend of late resolution may signal a process problem inside the firm.

How CAMAudit supports the exception workflow

The platform compresses the validation step that consumes most of the controller''s exception-handling time. For any unfamiliar landlord charge, the firm uploads the lease and runs the relevant detection rules to determine whether the charge category is authorized, excluded, or required to be amortized. The output is a documented basis for the coding decision.

For exceptions that escalate to dispute, the platform produces the structured findings report that supports the dispute correspondence. The firm has the lease citations, the calculations, and the variance analysis ready for the client communication.

Across a portfolio of clients, the platform also produces consistent output structure that lets the firm standardize the exception documentation and the client communication. See the white-label partner program for pricing tiers designed for accounting firms with varying engagement volumes.

Installing the exception workflow

For a firm that doesn''t currently have an exception-handling process, the implementation is straightforward.

Establish the four-account structure in the chart of accounts for each commercial real estate client. Create the exception register (a shared spreadsheet or a tracker in the firm''s practice management software). Train the bookkeeper on the holding-account discipline and the exception identification criteria. Define the controller''s weekly or monthly review window for the holding account. Document the escalation criteria and communicate them to the team.

The workflow is operational, not exotic. The investment is the discipline of running it consistently, and the return is a noticeably cleaner set of books for every commercial real estate client in the portfolio.

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.