How to Build a Variance Review for Landlord Charges
Firms check sales and costs against a plan. They can check each landlord bill too. I built CAMAudit to make the lease check easy to repeat.
This article is the variance review process. It is designed to fit inside the standing month-end close, produce defensible documentation, and escalate cleanly when something looks systematic.
Landlord charge variance review: A recurring monthly comparison between each landlord invoice and an expected amount derived from the lease abstract or prior period. The review identifies dollar and percentage differences, documents the comparison, and routes flagged items through a defined escalation path. It is bounded by design: the bookkeeper performs the comparison, the controller interprets flagged items, and the partner decides on disputes.
The expected amount comes from the abstract
The variance review depends on having a reliable expected amount for each line on the landlord invoice. That number lives in the lease abstract, which the firm builds once at engagement onboarding and updates only when amendments are signed.
The abstract should produce expected amounts for four invoice categories:
Base rent. The escalation schedule produces a month-by-month expected amount across the lease term. The bookkeeper looks up the current period and ties the invoice to that number.
Estimated CAM. The current-year estimate is whatever the landlord most recently issued. The expected amount is identical month over month inside the year unless the landlord notices a change.
Estimated real estate taxes and insurance. Same logic as CAM: the most recent landlord-issued estimate, repeated monthly.
Other authorized charges. Percentage rent, signage fees, after-hours HVAC, anything else the lease authorizes. The expected amount comes from either the lease formula or the most recent landlord notice.
If the abstract does not produce expected amounts for these four categories, the variance review cannot run. Building the abstract is the prerequisite, and it is a one-time engagement task.
The threshold structure
A firm may use a cash floor and rate floor. Set who checks each one. Write the rule down.
| Variance | Treatment |
|---|---|
| Within the firm's written threshold | Bookkeeper notes the variance in close notes |
| Above the firm's written threshold | Bookkeeper flags it for controller review |
| Any variance needing lease or billing-source review | Controller routes it for the required review |
| Any variance involving management fee, gross-up, base year, controllable cap, or capex passthrough | Bookkeeper flags regardless of size; controller reviews |
A lease term can also force a review. Here is sample math. $180 each month for 18 months is $3,240. Check the rule and math in each file.
The four-step monthly review
For each property, the monthly review follows the same four steps regardless of variance size.
Step 1: Look up expected amounts. The bookkeeper opens the abstract and pulls the four expected amounts for the current period.
Step 2: Compare line-by-line. For each invoice line, the bookkeeper computes the dollar variance and percentage variance against the expected amount.
Step 3: Apply the threshold. Variances clearing both thresholds get logged as "no material variance." Variances exceeding either threshold get flagged with documentation.
Step 4: Document. Pass-through variances log a single line in the close documentation. Flagged variances trigger the documentation template (invoice line, expected amount, variance, landlord communication record, controller routing).
The trailing-pattern check
Individual monthly variances do not always tell the full story. A $200 variance one month is small. A $200 variance every month for nine months is a different problem. The variance review needs a trailing-pattern check to catch these.
A variance that recurs in the same expense category for three consecutive months almost always indicates a methodological error rather than a one-time mistake. The recurrence pattern itself is the diagnostic.
What flagged documentation looks like
A flagged variance produces a single-page documentation entry in the close package:
- Property and lease reference
- Invoice date and number
- Invoice line that flagged
- Expected amount per the abstract
- Actual amount on the invoice
- Variance: dollar and percentage
- Lease provision that governs the line (when known)
- Landlord communication record (email thread, call notes)
- Resolution: paid as billed, paid under protest, held pending review, dispute initiated
The documentation does not need to be elaborate. It needs to be consistent enough that the firm can reconstruct the history six or twelve months later if a reconciliation reveals the variance was the tip of a systematic overcharge.
See the AP exception tracker for accounting firms for the documentation template and how controllers should review CAM reconciliations for the year-end aggregation that uses the variance documentation as input.
When to extend the review to the reconciliation
The variance review is monthly and bounded. The reconciliation review is annual and broader. The handoff between the two happens at year-end.
When the landlord issues the annual reconciliation statement, the controller pulls the variance documentation for the trailing 12 months and reviews each flagged item against the reconciliation. Three things can happen:
- The reconciliation resolves the variance (the landlord capacity the over-billed amount). No further action.
- The reconciliation confirms the variance and adds new findings. The controller runs CAMAudit on the reconciliation and produces a consolidated findings report that includes both the trailing variances and the reconciliation-specific findings.
- The reconciliation contradicts the variance documentation. The controller investigates the discrepancy and decides whether to escalate.
This handoff is what makes the variance review high-value. Without the trailing documentation, the reconciliation review starts from scratch. With it, the controller has a year of paperwork that quantifies the issue and the conversation with the landlord starts from a much stronger position.
Frequently Asked Questions
What is a landlord charge variance review?
This review checks each landlord bill. It uses the lease or past bill. It notes each gap and the result. It is like a plan-to-actual check for one vendor bill.
What variance threshold should the review use?
Set the rule from firm policy and client risk. One part can be a dollar floor. One can be a percent. A bookkeeper can check small gaps. Send larger or risky gaps to a controller. Write the rule in the file.
How is variance documentation structured?
Variance documentation includes the invoice line, the expected amount, the variance dollar and percentage, the landlord communication record (if any), and the resolution outcome. The documentation lives in the firm's working papers attached to the close package. The format does not need to be elaborate, but it does need to be consistent so the firm can reconstruct the history if a reconciliation later reveals a discrepancy.
When does a monthly variance trigger a reconciliation-level review?
A repeating monthly variance, even one each instance of which is below the controller threshold, triggers a reconciliation-level review at year-end. Three months of $200 variance that look small individually represent a $2,400 annual exposure. The variance review process should aggregate across the year and flag trailing patterns, not just individual large variances.
How does CAMAudit fit the variance review?
CAMAudit fits at the reconciliation step, not the monthly variance step. The monthly variance review is fast and abstract-based, designed to catch billing errors quickly. The reconciliation review, where systematic errors live, benefits from the structured findings report CAMAudit produces. The variance review process feeds documentation into the reconciliation review by aggregating the year's variances for controller validation.