At a glance
- CAM reconciliation compares actual recoverable expenses to what tenants were billed and settles the difference as a bill or credit.
- A lease-clause error table maps seven CAM provisions to an error to check for, an automated check, the decision a person makes, and the evidence to keep.
- AI is useful for reading lease language and matching ledger actuals to the right expense pool; deciding how an ambiguous clause applies stays with accounting.
- A pre-send approval checklist keeps a named accountant or controller in the loop before any CAM statement reaches a tenant.
- Confirm directly with your own platform's documentation which CAM reconciliation steps your configuration automates today, rather than assuming from the platform's name.
Can AI do CAM reconciliation?
AI can do real work inside a CAM reconciliation: reading lease language for recovery terms, matching ledger actuals to the right expense pool, and flagging a variance for review. In this workflow, deciding how an ambiguous exclusion applies and resolving a tenant's dispute stay with property accounting and, when a dispute escalates, counsel — your organization's own operating choice.
On a stable lease with clean GL coding, much of the calculation is deterministic: apply the pro-rata formula, cap, and gross-up, then compare tenants' estimated payments against their share of actual expenses[2]. AI adds value on the parts that aren't deterministic — reading an amendment for a changed exclusion, explaining why a line doesn't tie out — and surfacing what needs a second look.
Models help with:
- Extracting recovery terms, caps, exclusions, and gross-up language from the lease — the extraction-and-playbook pattern covered on our document review with human approval page.
- Matching each GL actual to the expense pool the lease defines, and flagging a coding mismatch instead of guessing.
- Drafting a plain-language explanation of why a line item doesn't tie to the prior estimate, for a reviewer to check.
Rules and people still decide:
- Whether an ambiguous or conflicting clause applies to a given expense.
- Every number that appears on a tenant-facing statement.
- How a tenant's dispute over a recovery gets resolved.
The lease-clause error table
The table below maps seven CAM provisions to an error to check for, an automated check, the human decision, and evidence to keep. Use it alongside the lease, not instead of it. A base year sets the comparison year; an expense stop sets a dollar figure the landlord absorbs first — confirm which mechanism the lease uses.
| Provision | Error to check for | Automated check | Human decision | Evidence kept |
|---|---|---|---|---|
| Base year / expense stop | Base-year or expense-stop figure on file doesn't match the lease as amended | Compares the figure on file to the lease's stated figure, as amended | Confirms the base year or expense-stop figure under the lease as amended | Base-year or expense-stop detail and the lease page it's from |
| Expense cap (fixed vs. cumulative) | A cumulative cap applied as if it resets yearly, or a fixed cap applied as if it compounds | Recomputes the cap using the lease's method and compares it to what was billed | Confirms which cap method the lease specifies when the wording is ambiguous | Cap calculation workpaper showing the method used |
| Exclusions (capital, leasing, reserves) | An excluded cost, such as a capital or leasing item, coded into the recoverable pool | Flags GL codes that match an item on the lease's exclusion list | Decides how to treat a cost that doesn't map cleanly to a written rule | GL detail with exclusion flags and the clause each cites |
| Gross-up clause | Variable expenses left at actual occupancy instead of the lease's stated gross-up level | Recalculates variable lines at the stated gross-up occupancy and compares to the pool | Confirms which lines the lease treats as variable, since the split isn't always explicit | Gross-up calculation with the occupancy assumption and clause it's based on |
| Pro-rata share / denominator | A denominator that doesn't reflect current measured area or a mid-year space change | Compares the tenant's stated share to the current rent roll and measured area | Confirms which measurement standard and date apply after a remeasurement or new lease | Rent roll snapshot and area-measurement basis used |
| Administrative / management fee | Fee calculated on the wrong base, such as gross pool instead of a net-of-exclusions base | Recomputes the fee on the lease's base and flags a mismatch | Confirms the fee base when the lease's wording is ambiguous | Fee calculation showing the base amount and clause cited |
| Controllable vs. non-controllable split | A cap applied to the whole pool when the lease caps only controllable items | Tags each GL line per the lease's list, caps only that subset | Resolves a cost that reasonably sits in either category | Line-level tagging (controllable or not) with the clause cited |
Which CAM lease provisions cause the most reconciliation errors?
Check these seven provisions first on every reconciliation: base year, expense caps, exclusions, gross-up, pro-rata share, administrative fees, and the controllable/non-controllable split. No source cited in this article ranks CAM provisions by how often each one causes errors — this order is a recommended check sequence, not a frequency ranking.
IREM's CAM reconciliation webinar description lists "gross-up methodologies and calculations, base year provisions, and expense caps" and "expense pools, prorata calculations, gross-ups, capital expenditure amortization, tenant billing adjustments"[2], overlapping several provisions above. It doesn't name exclusions, administrative fees, or the controllable split as a group.
Pro-rata share depends on the building's measured area, and the measurement basis itself can be a source of error after a remeasurement or a new lease. BOMA International describes itself as the "American National Standards Institute (ANSI) secretariat for a suite of area measurement standards"[1]. Confirm which standard and version the lease's pro-rata language references before recomputing a share.
- A cost technically recoverable under general lease language but on the exclusion list needs the lease's exact wording next to the GL line, not just a matching rule.
- A capital item split across years under an amortization schedule needs the same treatment: schedule and clause, checked together, not assumed from the GL code.
Does Yardi Voyager automate CAM reconciliation?
This couldn't be verified from Yardi's own site, which returned a blocked request on every attempt, so there's no reachable source for what Yardi Voyager does or doesn't automate. Confirm the current capability against your own platform's documentation.
Any platform needs to support the same underlying comparison, however it's configured. MRI Software describes it on its own site as checking actual CAM costs against what tenants were billed: tenants "may be billed for the difference" if costs ran higher, and "might receive a credit" if they ran lower[3]. This article doesn't map where any vendor's native module stops and manual work begins; confirm that boundary yourself.
What should a human approve before tenant CAM statements are sent?
Before any CAM statement reaches a tenant, a property accountant or controller should approve it in full, with attention to figures that vary from the prior estimate, the cap and gross-up math, and any flagged-exception resolution — nothing reaches a tenant's inbox on an automated match alone.
- Confirm the expense pool is complete
Tie the recoverable-expense total to GL actuals for the full period, not a partial extract.
- Verify lease amendments are reflected
Check that every amendment and renewal affecting CAM terms this period is applied, not just the original lease.
- Recompute the pro-rata share
Recheck the tenant's proportional share against the current rent roll, especially after any space change.
- Check cap and gross-up math
Recompute the cap and gross-up using the lease's stated method and occupancy assumption, rather than accepting the system's figure as final.
- Reconcile the prior-year true-up
Confirm last year's balance or credit was applied, and this year's calculation starts from the right carryforward.
- Attach the supporting detail
Include the GL detail, the calculation workpapers, and the clauses relied on, so the statement is defensible on its own.
- Get a named sign-off
Route the finished statement to a property accountant or controller for approval, and record who approved it and when.
Where to start: a first scoped workflow
Start with one lease population where documentation is already in decent shape: buildings where leases are filed with amendments and the chart of accounts maps cleanly to your expense pools. That's where recompute-and-compare catches the most, with the least ambiguous language to interpret.
Scope the first pass around the arithmetic checks before extending into judgment-heavy exclusions and the controllable split. Run it in parallel with your existing process for one full CAM season before relying on it for a tenant-facing statement.
If you're weighing where to add these checks, there are two broad paths: layering AI-assisted checks on the Yardi Voyager or MRI platform you already run, or adopting CAM reconciliation software such as Kardin, which describes itself as "CRE budgeting and reforecasting software that automates CAM reconciliation for commercial property portfolios"[4]. Either path still needs the same checks and named sign-off.
When this doesn't apply
- The lease population is still on paper or has unfiled amendments; there's nothing for a system to read until organized.
- Your CAM policy for caps, exclusions, and gross-up isn't applied consistently; align the policy before automating.
- Volume is low enough that a property accountant already recomputes every lease by hand without a backlog.
- The issue is a disagreement over how a clause should be interpreted; that's a conversation between the tenant, property accounting, and counsel, not a reconciliation check.
Frequently asked questions
How do you document CAM calculations for tenant audits?
Keep the GL detail behind every recoverable line, the calculation workpapers for the cap, gross-up, and pro-rata share, and the lease clause each relies on, filed with the statement itself. When a tenant requests an audit, that package should let their reviewer trace any figure to its source without your team rebuilding it.
How long should a CAM reconciliation take?
We don't publish a target timeline; it depends on lease volume, how consistent your documentation is, and how many exceptions the portfolio generates each season. Measure your own cycle time, from when GL actuals close to when statements go out, across more than one season, before setting a target to improve against.
What belongs in a CAM dispute packet?
The same evidence kept for a routine audit — GL detail, calculation workpapers, and the lease clauses relied on — plus the exception disputed, the reasoning behind its resolution, and who approved it. Dispute resolution stays with property accounting and counsel, as your organization's own operating choice; the packet makes that decision traceable.
How do you handle a lease amendment that arrives mid-reconciliation?
Apply it before recomputing: confirm the amendment's effective date against the lease file, then apply each changed term from that date forward. Whether a changed cap, exclusion, or gross-up term also reaches back across the rest of the period is a lease-interpretation question for property accounting and counsel, not something this article decides.
Should an AI-suggested exception resolution ever auto-send to a tenant?
No. A suggested match, a proposed resolution, or a drafted explanation is a starting point for a property accountant to check, correct, or reject, not something that reaches a tenant-facing statement without review. Every CAM statement needs a named person's sign-off, whatever the system's confidence in its own suggestion.
What's a good error rate to target for CAM reconciliation?
We don't publish a target error rate; averaging across all provisions would hide the ones causing the most disputes. Measure exceptions by provision type — base year, cap, exclusions, gross-up, pro-rata share — against your own closed seasons, and treat a sudden drop after a rule change as a reason to review, not celebrate.
Related reading
- Financial reconciliation automation covers the matching-and-exception pattern this workflow sits inside.
- Financial close automation covers the wider period-end process competing for the same team's time.
- Document review with human approval covers the extraction pattern behind reading CAM recovery language from a lease.
- how AI fits across lease, CAM, AP, and diligence workflows in real estate and property management sets this workflow in the wider picture.
- Reconciliation match rules and exceptions covers match strategy and tolerance-setting beyond CAM specifically.
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsGroup and Folio Billing Audit: Catching the Leak Types a Normal Error Check Misses
A group and folio billing audit for hotel management companies: a leak-type table of rate code mismatches, missing closes, adjustments, orphaned charges.
Hotel Management Companies