What to do when an unexpected landlord bill lands during close week
The annual CAM reconciliation does not warn you it is coming. It arrives between sixty and one hundred eighty days after year end, in a window that depends on the landlord's accounting calendar rather than the tenant's, and it tends to land during the close week of whatever month it lands in. The bookkeeper opens the AP folder, sees a landlord bill three or four times the normal amount, and has to decide what to do with it inside the next two days while the rest of the close runs. For more context, see the accounting firm hub.
Most firms handle this by guessing. The bookkeeper either codes it to rent, codes it to a misc-expense bucket, or routes it to the controller in the middle of the controller's busiest week. The result is either a wrong posting that gets corrected the following month, a delayed close, or a controller who skips review under time pressure and posts something that looks reasonable. None of these is the right answer.
The right answer is a documented decision tree applied at intake, before the bill enters the close queue. I built CAMAudit because the same bills that disrupt the close are the bills where landlord errors are most concentrated, and the close-week chaos is what causes those errors to slip through unreviewed. A short process at intake protects both the close calendar and the accuracy of the posting.
Accrual posting: An accounting entry that records an expense in the period it economically belongs to, based on the firm's best estimate of the amount, when the actual invoice has not yet been received or finalized. Accrual postings are reversed in the following period when the actual invoice posts, with any variance flowing through to that period's results. For close-week landlord bills that require additional review, an accrual based on prior-year data lets the current period reflect the economic activity while preserving time for proper review of the actual bill before it posts.
The decision tree at intake
When an unexpected landlord bill arrives, the bookkeeper does not code it. The bill goes into an exception lane with three possible outcomes, decided by the controller within two business days.
Outcome one: post as billed in the current period. If the bill is reasonable on its face (amount consistent with the prior-year reconciliation, period clearly within the current close period, no unusual line items, supporting backup attached), the controller approves the bill for standard coding. The bookkeeper codes it on the controller's clearance.
Outcome two: accrue in the current period and post the actual in the next period. If the bill is material and the period it covers is in the current close, but the bill requires further review (variance against prior year, missing backup, items that depend on lease-language interpretation), the controller authorizes an accrual based on prior-year data or the run-rate estimate. The accrual hits the current period. The actual bill posts the following period after review is complete, and any variance from the accrual is surfaced in the next period's variance commentary.
Outcome three: defer the posting entirely. If the bill is for a period prior to the current close (an annual reconciliation that covers the prior calendar year, arriving in March or April), the bill does not belong to the current period at all. The controller documents the bill, decides whether the prior-period adjustment is material enough to require a restatement or can be posted in the current period as a prior-period reconciliation item, and proceeds accordingly.
The decision is a controller call. The bookkeeper's job is to route the bill into the lane and not post anything until the controller has cleared it.
How to size the accrual when you choose outcome two
The accrual is an estimate, not a calculation. The firm is not pretending to know the exact bill. The firm is recording the economic activity in the right period and saying "approximately this amount" until the actual is reviewed.
The simplest accrual basis is the prior-year actual for the same bill type. If last year's annual CAM reconciliation produced a balance due of $14,200, the accrual for the current year is approximately $14,200 absent known changes. If the bill that arrived shows $19,400, the accrual is conservative; the variance posts next month. If the bill shows $12,800, the accrual was high; the variance again posts next month.
Adjustments to the prior-year accrual basis are appropriate when something has materially changed: a known property tax increase, an executed amendment, a structural change in occupancy. The adjustment is documented on the close memo so the basis for the accrual is clear.
For pass-through bills outside the annual reconciliation (a real estate tax bill, an insurance pass-through), the accrual is the actual amount on the bill if the bill itself is uncontroversial. Outcome two is for bills where the amount is contested or the bill needs review, not for bills where the amount is fine but timing is awkward.
The communication step that keeps the client calm
The client needs to know that an unusual bill arrived and is being reviewed. The communication is short and factual. It sits in the monthly close email or in the management report variance commentary.
A working template:
"This month's landlord activity included an annual CAM reconciliation covering the year ended December 31, 2025, which arrived on March 14. We have accrued an estimated amount of $14,200 in this month's books based on the prior-year reconciliation balance. The actual bill ($19,400) is under review by the controller, and the variance will post in next month's reporting along with our findings on any items that warrant further attention."
That paragraph does four things. It tells the client the unusual bill arrived. It explains the accounting treatment. It commits to a follow-up. It signals that the firm is reviewing the bill rather than just posting it. Clients who receive that note feel informed. Clients who receive a $19,400 surprise in the management report two weeks later feel ambushed.
"The clients I have seen who lose trust in their accounting team over CAM bills do not lose it because the bill was wrong. They lose it because the bill landed without warning, the firm posted it without explanation, and the variance showed up on a report a week later. The communication step is the part most firms skip and most clients remember." — Angel Campa, Founder of CAMAudit
What review actually looks like in the following week
After close week, the controller has time to do the review the bill required. The review uses the lease abstract, the prior-year reconciliation, any backup the landlord has provided, and the firm's standard tier-two checklist.
The output of the review is a posting recommendation. If the bill is correct as billed, the controller authorizes the actual to post and the variance against the accrual flows through naturally. If the bill is correct in amount but misclassified by the bookkeeper at intake, the controller corrects the coding before posting. If the bill contains items that depend on lease-language interpretation, the controller documents the items, packages the bill with the abstract and prior-year data, and refers the package to a specialist for further analysis. The actual still posts to clear the AP, but the firm has captured the items for follow-up rather than letting them disappear into the books.
The client gets a short note in the next variance commentary explaining what was reviewed, what was posted, and what is being escalated if anything. The cycle closes cleanly.
Why this is faster than coding immediately
The instinct to code immediately during close week comes from the assumption that fast coding is the fast close. It is not. A coded bill that gets corrected next month is two postings, two reviews, and a variance conversation with the client. An accrued bill that posts cleanly the following month is two postings, one review, and a clear variance commentary that the client expected.
The exception lane is also faster across many close cycles than the alternative. A firm that handles unusual landlord bills with an exception process closes faster on average because the close is not interrupted by ad-hoc decisions during close week. The decisions happen the following week, when the controller has time, and the close runs on schedule with the standard bills.
That trade is the right one for almost any commercial-tenant client. The unusual bill gets the review it deserves, the close gets the timeline it needs, and the client gets the communication that turns an unexpected charge into a managed event.