How to Export CAM Reconciliation Data from Yardi Voyager
Quick Answer
For Yardi Voyager, export Recovery Analysis, General Ledger Analytics, and Rent Roll with Lease Charges for the same property and reconciliation year. Use detail-level reports, flatten the files to CSV, and verify the export is complete before you trust any reconciliation totals.
This guide is for property accountants and controllers who need a defensible export workflow, not just a report that “looks close enough.” If the file coming out of Yardi is incomplete, every downstream variance discussion gets harder.
The Yardi Export Stack
| Report | Why you need it | Menu path |
|---|---|---|
| Recovery Analysis | Shows what Yardi thinks each tenant owes by pool. | Commercial -> Recovery -> Recovery Analysis |
| General Ledger Analytics | Shows the expense detail feeding the recovery pools. | Accounting -> General Ledger Analytics |
| Rent Roll with Lease Charges | Confirms tenant roster, square footage, and lease timing. | Leasing -> Reports -> Rent Roll with Lease Charges |
| Charge Schedule | Useful for tenant-level estimate billing support. | Commercial -> Recovery -> Charge Schedule |
If your team skips one of the first three, you are no longer validating a full reconciliation.
Before You Export
Confirm four things first:
- the property code is consistent across all reports;
- the reconciliation period is the same on every export;
- the recovery pools are mapped correctly in Yardi;
- the person exporting knows whether your close process relies on posting date or transaction date.
Those checks prevent most “Yardi is wrong” escalations.
Export 1: Recovery Analysis
This is the main reconciliation report. It is where Yardi brings together actual expenses, estimated billings, and tenant allocation logic.
Open Recovery Analysis
Choose the property and year
Select all relevant recovery pools
Use detail mode
Export to Excel and flatten to CSV
What to check immediately
- Tenant names and suites are populated.
- Pool totals are present by tenant.
- Actual, billed, and variance columns all exist.
- The file is flat data, not paginated report output.
Export 2: General Ledger Analytics
This report proves what actually hit the expense pool.
Open General Ledger Analytics
Use the full reconciliation year
Set the correct account scope
Use transaction-level detail
Export and flatten
What to check immediately
- Account codes are visible.
- Transaction descriptions and dates are visible.
- Manual journal entries are not missing.
- Totals broadly agree with the financial statements for the same period.
Export 3: Rent Roll with Lease Charges
This file drives denominator logic and tenant roster validation.
Open the rent roll report
Set the as-of date
Include lease fields
Export and flatten
What to check immediately
- Rentable SF exists for every active tenant.
- Lease start and end dates are populated.
- Suite labels match the recovery export.
- Mid-year move-ins and move-outs are represented correctly.
When to Use Charge Schedule
Use Charge Schedule when the problem is “what did we bill?” rather than “what did we spend?” It is the best supporting export for:
- mid-year estimate changes;
- charge-code disputes;
- invoice-level audit support;
- proving that the billed side of the reconciliation moved when the budget changed.
What Goes Wrong in Practice
1. Summary mode hides the problem
The report totals look plausible, but the export has no line-item support. When a tenant asks why one pool jumped, your team has nothing to trace.
2. Posting-date logic cuts off year-end accruals
A December expense posted in January may belong in the reconciliation year. If the export is filtered the wrong way, Yardi excludes it and your statements do not tie to final close.
3. Recovery pool mappings are stale
The GL has a recoverable expense, but the recovery setup never mapped that account into the pool. Yardi is not “miscalculating.” It is calculating from incomplete setup.
4. The Excel file still contains report furniture
Yardi header rows, page totals, and title bands often survive the export. That is fine for human reading and bad for machine validation.
5. Saved filters are trusted too long
The filter worked last year. The chart of accounts changed this year. The export quietly drops the new accounts.
The QA Sequence That Saves Time
Run this in order:
- compare GL totals to the same-period financial statements;
- confirm Recovery Analysis is detail-level and pool-complete;
- confirm the rent roll has the expected tenant roster and square footage;
- only then inspect gross-up, caps, or pro-rata math.
That order is faster than jumping straight into formulas.
Yardi Export Checklist
- Same property on all files
- Same reconciliation period on all files
- Detail-level output
- Flat CSV, not a report view
- Recoverable GL accounts included
- Year-end accrual logic understood
- Rent roll includes rentable SF and lease dates
If one box is unchecked, fix the export before you debug the reconciliation.
Related Resources
- CAM Export Guide
- How to Export CAM Data from MRI Software
- CAM Gross-Up Calculation Guide
- Pro Rata Share Calculation Guide
Run your Yardi files through a real validation pass
Upload Recovery Analysis, GL detail, and rent roll exports from Voyager. CapVeri maps the files together, checks the setup layer, and flags the gaps before a bad statement goes out.
Start Free TrialFrequently Asked Questions
What Yardi reports do I need for CAM reconciliation?
In most cases you need three core exports: Recovery Analysis, General Ledger Analytics, and Rent Roll with Lease Charges. Charge Schedule is the main supporting export when you need invoice-level estimate history.
Why does my Yardi export look right but still fail reconciliation?
Because Yardi exports often fail in the setup layer, not the math layer. The common causes are summary mode instead of detail mode, posting-date filters instead of transaction-date logic, missing recovery-pool mappings, or Excel files that still contain header rows and totals.