CAM reconciliation looks like arithmetic. Take the recoverable expenses, apply each tenant’s share, subtract what was already billed in estimates, bill or credit the difference.
In practice, the numbers rarely fall out that cleanly.
A recovery comes in too high. A tenant statement will not tie to the general ledger. A base year calculation looks off by an amount nobody can explain. One tenant’s share is exactly right while the tenant next door is wildly wrong. When that happens in Yardi, it is almost never one error. It is a setup, mapping, timing, or validation problem that stayed invisible all year and finally surfaced at reconciliation.
This guide covers why Yardi CAM recoveries do not match, and how to validate the numbers before statements go out.
What CAM Reconciliation Is Actually Checking
Common area maintenance reconciliation compares estimated recoveries billed to tenants against actual recoverable expenses for the reconciliation period.
The process checks six things:
- Which expenses belong in the recovery pool
- Which tenants participate in that pool
- How each tenant’s share is calculated
- What caps, base years, exclusions, or special lease terms apply
- What was already billed through estimates
- What final adjustment should be charged or credited
For office, retail, and industrial properties this gets complicated fast. Tenants sign different lease clauses, expense stops, caps, and allocation rules, sometimes within the same building. Treat CAM reconciliation as a validation process, not a report you run.
If your team is still building confidence in the platform, a practical guide on how to use yardi shows where lease setup, charges, reports, and reconciliation steps connect.
Why Yardi CAM Recoveries Don’t Match
Seven causes account for most of the variances we see.
1. The expense pool includes the wrong accounts
The most common cause is straightforward: the pool does not contain the expenses that should actually be recoverable.
A GL account missing from the pool underbills the tenant. A non-recoverable account sitting in the pool overbills them. This happens when new expense accounts get added mid-year, when invoices are coded inconsistently, or when the pool was built to match a lease summary rather than the lease.
So before you assume the reconciliation report is wrong, check the pool. Confirm every included account matches a recoverable category in the lease, and that excluded costs are not being pulled in through an account range that quietly grew.
2. Lease-level recovery setup does not match the lease
Reconciliation lives or dies on lease setup. The recovery profile, expense group, pro rata share, base year, cap, and exclusions all have to reflect the signed document.
When the lease says one thing and Yardi says another, the calculation follows Yardi. You get a clean-looking report and an incorrect recovery, which is the worst combination because nothing looks broken.
Setup issues we run into repeatedly:
- The wrong recovery group assigned to the tenant
- Incorrect recovery start or end dates
- An incorrect pro rata share
- Missing base year setup
- A cap applied to the wrong expense category
- Exclusions that never made it into the setup
- Retail or office-specific rules applied inconsistently across the property
This is a system ownership problem as much as a data problem. Where roles, permissions, workflows, and configuration standards are not maintained, the same CAM setup errors repeat across properties and accounting periods. A structured Yardi Voyager System Administration approach is what stops that cycle.
3. Estimated charges were not billed consistently
Reconciliation compares actual expenses against what was estimated and billed. If the estimates were wrong during the year, the final adjustment looks wrong even when the actual expense calculation is perfect.
A tenant misses estimate charges for two months. Another gets billed under the wrong charge code. A tenant who started mid-year has a billing schedule that does not match their recovery period. Each of those distorts the reconciliation without touching the expense side at all.
Process consistency is the fix. Teams handling recurring reconciliations, billing reviews, and tenant charge validation benefit from structured Yardi Training Courses, so the same workflow gets followed every cycle rather than reinvented by whoever is covering.
4. Base years, caps, and expense stops are not validated
Base years and caps generate more reconciliation differences than any other lease term.
A base year clause has the tenant pay only the increase above a defined base amount. A cap limits how much certain controllable expenses can rise. An expense stop shifts only part of the expense burden to the tenant. Each behaves differently, and each has to be applied to the right pool.
Get any of that wrong and the recovery will not match expectations, no matter how clean the expense side is.
The question is not whether Yardi calculated a number. It is whether Yardi calculated the number using the same rules the lease does.
5. Area, occupancy, or date changes affected the allocation
Allocations shift when square footage, occupancy dates, move-ins, move-outs, expansions, contractions, or amendments are not reflected correctly.
A tenant who occupied space for part of the year needs a prorated recovery. A tenant whose rentable area changed mid-year needs a different allocation for each period. Wrong dates or wrong area values, and the system’s answer will not match anyone’s manual expectation.
When you are chasing a variance, check:
- Lease commencement date
- Recovery start date
- Move-out date
- Amendment effective dates
- Rentable square footage
- Occupancy changes
- Proration settings
Small date or area errors produce large reconciliation differences. A three-day error in a commencement date is easy to miss and easy to argue about later.
6. Expenses were posted after the review period
Timing matters more than it gets credit for. Invoices, journal entries, or adjustments posted after the reconciliation review leave the general ledger out of step with the report the statements were built from.
This is especially common when CAM reconciliation starts before year-end accounting is fully closed, which is most years. Later entries change the actual expense total, and the recovery calculation moves with it.
Confirm the accounting period is genuinely ready before finalizing statements and review late adjustments explicitly rather than assuming there were none.
7. Reports do not match the calculation source
Sometimes the recovery calculation is right, and the report is the problem. The report pulls a different date range, a different account group, or a different level of tenant detail than the calculation used.
Then accounting, property management, and leadership review three different reports and expect them to tie out. They will not, and the time goes into arguing about which one is correct instead of into the actual reconciliation.
A custom report earns its keep here. If your team needs cleaner reconciliation reporting, variance review, or tenant-level visibility, Yardi Custom Reporting & Analytics can organize the data into something reviewable.
How to Validate Yardi CAM Reconciliation
Validation happens before statements go out. After is called damage control.
Step 1: Tie expense pools to the general ledger
Start with the recoverable expense pool and tie it back to the GL. Confirm each account in the pool belongs there and that the expense total matches the reporting period.
Watch for unusual changes, missing accounts, miscoded invoices, and large year-over-year swings. A swing you cannot explain is a finding, not a rounding difference.
Step 2: Review tenant recovery setup
Pull a sample of tenants and compare the Yardi setup against the lease. Weight the sample toward tenants with base years, caps, unusual exclusions, partial-year occupancy, or recent amendments, because that is where errors concentrate.
For each one, validate the recovery group, dates, share, cap, base year, and charge codes.
Step 3: Compare estimates billed to final recovery
Review what each tenant was actually billed during the year. Confirm estimate charges posted for the correct period under the correct charge code.
Where estimates were missed, reversed, or posted incorrectly, document it before you look at the final adjustment. Otherwise you will try to explain a variance that has nothing to do with the expenses.
Step 4: Manually test high-risk tenants
For tenants with large variances, run a manual reasonableness check. You do not need to rebuild the calculation from scratch. You do need to be able to explain the major drivers out loud.
Check the actual recoverable expense total, the tenant share, the base year or cap, the estimated billings, and the final charge or credit. If you cannot walk someone through those five numbers, the variance is not resolved yet.
Step 5: Review exception reports and statement output
Before sending, review exceptions and compare the statement output against the adjustment you expect. Make sure the statement is readable and that supporting detail exists for the tenant who calls and asks.
Where the same issues keep recurring cycle after cycle, review practical Yardi troubleshooting tips to work out whether the root cause sits in setup, user process, reporting, data entry, or timing. Recurring problems are process problems.
Connected Systems Can Affect CAM Validation
Reconciliation gets harder when Yardi data connects to outside tools, custom reports, accounting workflows, or BI dashboards.
Where integrations, extracts, or custom data flows are involved, the review has to go past the reconciliation screen. Internal IT or consulting support may need to review yardi voyager api documentation to trace how data moves between systems and where mismatches enter. Access to Yardi’s interfaces runs through licensing, entitlements, and Yardi’s interface partner program rather than open public documentation, so plan for that step to involve your Yardi account team.
This matters because a reconciliation issue does not always start in the CAM setup. It can start with imported data, mapped fields, duplicate entries, or reporting logic well outside the standard workflow, and no amount of staring at the recovery screen will find it.
When to Get Help
If recoveries do not match and your team cannot trace the variance, the problem is probably not a report. It is lease setup, expense pool design, charge codes, GL mapping, data entry, integrations, or the reconciliation workflow itself.
For companies evaluating broader system fit, a realpage vs yardi comparison is worth reviewing before making long-term decisions about platform structure, reporting, and operational workflows.
ND Consulting helps commercial property teams review Yardi setup, validate recovery calculations, troubleshoot reconciliation issues, and tighten reporting controls. A structured review finds where the mismatch starts and what has to be corrected before statements go out.
Conclusion: Validate CAM Recoveries Before Statements Go Out
When Yardi CAM recoveries do not match, the cause is usually setup, data, timing, or a gap between the lease and the configuration. Validate the expense pools, tenant recovery setup, estimate billings, base years, caps, proration rules, and statement output before anything is sent.
The work is the same either way. Doing it first costs a few days. Doing it after costs tenant credibility, accounting delays, and a round of rebilling nobody budgeted for.
If your team needs help reviewing Yardi CAM reconciliation, validating recoveries, or troubleshooting mismatched tenant statements, contact ND Consulting to discuss the issue with a Yardi consulting specialist.
