CAM reconciliation software is not just a calculator
For commercial landlords, a year-end CAM reconciliation is rarely difficult because the team cannot subtract estimates from actual expenses. It becomes difficult because every final number has to travel through a chain of lease language, accounting records, allocation rules, amendments, credits, deadlines, and supporting documents.
That is why a spreadsheet can be both familiar and fragile. A workbook may calculate a tenant balance, yet still leave basic questions unanswered:
- Which version of the lease set the recovery rules?
- Did this tenant's pro-rata share use the right rentable area and denominator?
- Which expenses were included, excluded, capped, or grossed up?
- Can the team trace a charge back to the ledger and the underlying support?
- Can a tenant understand the statement without a long series of follow-up emails?
CAM reconciliation software is worth evaluating when it helps keep that chain intact. It should not promise that every expense is recoverable or replace a review of the executed lease. It should help a landlord organize the work, apply documented rules consistently, and produce a record that is easier to explain.
This is operational guidance, not legal or accounting advice. The signed lease, amendments, applicable law, and qualified advisers control the treatment of any particular charge.
Start with the actual failure mode
Before comparing software features, identify what failed in the last reconciliation cycle. The answer usually points to a workflow problem—not a missing button.
The lease data was incomplete or inconsistent
CAM math can be wrong before anyone opens an expense report. A tenant's rentable square footage, the building denominator, exclusions, management-fee language, caps, gross-up rules, audit rights, and notice requirements may be split between the original lease, amendments, abstracts, and emails.
If the team is rebuilding those inputs from scratch every December, the first software requirement is a reliable lease-rule record. The system should let the team identify the source document and effective date for key inputs. It should also make exceptions visible instead of silently applying a property-wide default.
The accounting view did not match the recovery view
The general ledger is a record of business activity. A CAM schedule is a lease-driven recovery calculation. Those are related, but they are not interchangeable.
Good CAM reconciliation software should give the preparer a way to map expense lines into an operating-expense pool, flag exclusions, and preserve a reason for adjustments. The goal is not to hide the accounting detail. It is to create a controlled bridge from the ledger to the tenant calculation.
The allocation math was hard to review
Pro-rata shares sound simple until a property includes vacancies, different definitions of rentable area, tenant-specific exclusions, separate expense pools, or caps on controllable expenses. A software workflow should show the denominator used, the tenant's share, the expense category, and the calculation that leads to the result.
A total that cannot be reconstructed is not a useful total. Reviewers need to see the inputs, not only the output.
The tenant statement created more work
A statement that says only “CAM balance due” may be technically concise, but it is not tenant-friendly. It forces the recipient to ask what changed, which categories rose, whether estimates were credited, and where to find support.
The right workflow should produce a clear statement and make the backup package easy to assemble. That does not mean sending every vendor document by default. It means the team can quickly explain the lease rule, actual expense, allocation, estimate credit, final balance, due date, and permitted path for questions.
What to require from CAM reconciliation software
When evaluating a product, use the following checklist. A demo should show these controls with a realistic lease and a realistic exception—not only a clean sample property.
1. Lease terms connected to the calculation
At minimum, the workflow should surface the terms that affect the reconciliation:
- rentable square footage and the pro-rata denominator
- recoverable and excluded expense categories
- management-fee treatment
- controllable-expense caps and any required calculation method
- gross-up assumptions where applicable
- estimate amounts and credit treatment
- amendment-driven changes and effective dates
- tenant review, audit, notice, and payment deadlines
Ask where each input came from and how a reviewer can tell when it was last updated. The answer should not be “it is in someone’s notes.”
2. Expense-pool controls
The system should help the team separate actual operating expenses from items that need a different treatment. Look for a clear way to:
- map ledger accounts or imported transactions to CAM categories
- mark a line included, excluded, or pending review
- document adjustments without overwriting the original activity
- handle property-level and tenant-specific exceptions
- attach or link supporting invoices, contracts, tax records, or worksheets
This is especially important when a bookkeeper, property manager, and outside accountant each touch the records. The final reconciliation should not depend on one person remembering why a line was moved six months earlier.
3. Transparent allocation and cap math
Do not accept a black-box tenant total. Ask the vendor to show a single tenant’s calculation from the expense pool through the final balance.
The review screen or report should make it possible to inspect:
1. the actual expense amount by category; 2. the applicable allocation basis and pro-rata share; 3. any exclusions, gross-up, or cap calculation; 4. billed estimates or prior credits; and 5. the balance due or credit.
If the workflow cannot show that path clearly, it will be hard for your team to answer a reasonable tenant question without recreating the calculation outside the system.
4. A usable audit trail
An audit trail is not a feature to save for a dispute. It is the everyday record of who changed a calculation, what changed, when it changed, and why.
For CAM work, the trail should cover lease inputs, expense classifications, allocation changes, statement revisions, and the reviewer who approved release. It should preserve the underlying support or a dependable link to it.
This protects the landlord from a last-minute hunt through shared drives and gives a new team member a practical way to understand the file. It also reduces the temptation to “fix the number” in email without updating the source calculation.
5. Tenant-ready statements and backup
The tenant-facing output should be clear enough that the recipient can begin a review without guessing. A useful package typically includes:
- the reconciliation period and property or suite reference
- a summary of the applicable recovery basis
- expense categories and actual amounts
- the tenant's allocation and applicable adjustments
- estimates or credits already received
- the amount due or credit, with the stated deadline
- a contact and process for questions consistent with the lease
Keep the supporting documents organized behind the statement: ledger detail, invoices, service contracts, tax and insurance documentation, calculation worksheets, and the relevant lease extracts. The lease determines what must be provided and when; software should make that package easier to prepare, not presume a universal disclosure rule.
6. Review gates before delivery
Even a good system needs a human review step. Require a workflow that lets someone other than the preparer confirm the active lease, share calculation, caps, expense pool, credits, notice details, and final statement.
The reviewer does not need to reperform every entry. They do need a focused checklist and a record that the package was reviewed before it went to the tenant.
Questions to ask in every vendor demo
Bring one representative lease, a short list of expenses, and at least one exception to the demo. Then ask:
1. Where do lease inputs live, and how do you track amendments? 2. Can we see the original expense record, the adjustment, and the reason for the adjustment? 3. How does the software handle tenant-specific caps, exclusions, and different allocation bases? 4. Can the statement show actual expenses, estimates, and the final balance in plain language? 5. What documents can we attach or link to the reconciliation, and who can access them? 6. Can a reviewer approve the package before delivery, with a record of the review? 7. Can we export the calculation and support if a tenant, buyer, or adviser needs to inspect the file? 8. What has to be maintained monthly so year-end is not a data-cleanup project?
If a vendor can answer these questions only with a manual workaround, factor that labor into the decision. A system that produces a polished statement but still requires a parallel spreadsheet for lease exceptions and backup may not have solved the real problem.
Build the process before the deadline pressure arrives
The best time to improve CAM reconciliation is before the year-end close. Begin with a small cleanup:
- confirm active leases and amendments for each tenant;
- verify property and tenant square-footage records;
- standardize the expense-category mapping;
- identify recurring exclusions, caps, and special rules;
- decide where supporting documents will live;
- set an internal review checklist and calendar.
Then run a sample reconciliation for one property or a small group of tenants. The point is not to make a perfect system on day one. It is to expose missing inputs, ambiguous categories, and weak document links while there is time to fix them.
Choose the workflow that makes the next question easier
The useful test for CAM reconciliation software is not whether it can generate a number. Most tools can do that.
The useful test is whether, months later, a landlord can answer: Which lease rule did we apply? Which records support this expense? How was this tenant’s share calculated? What did we send, and who reviewed it?
When those answers are visible in one controlled workflow, year-end becomes less about rescuing a spreadsheet and more about delivering a clear, supportable reconciliation.
I built PigJet around the commercial workflows that tend to create that last-minute scramble: lease terms, tenant records, CAM calculations, and the documents behind them. If your team is evaluating a new process, start with the controls above and make sure the product can prove the path from lease rule to tenant balance.