Service Charge Reconciliation Model

Service charge (and CAM) reconciliation matches landlord actual operating costs to budgeted amounts and to the lease rules that govern how those costs are shared among tenants. A reconciliation model drafts that match at scale: it compares posted actuals to budgets, applies lease-specific apportionment logic, highlights misallocations and exceptions, and produces tenant-level draft statements an accountant can review before certification.

The model does not replace professional judgment. It proposes an apportionment and an exception list. A property accountant still certifies the final statements, resolves disputed items, and decides how to treat edge cases the lease does not clearly cover.

When required inputs are missing (actuals, budgets, or lease provisions), the model returns empty output rather than inventing allocations. Incomplete runs stay incomplete until the missing source is supplied.

Three source families must be present and current before a run is useful.

Actuals. Posted operating expenditures for the reconciliation period: utilities, cleaning, security, repairs, insurance, management fees, and other recoverable opex, coded to the chart of accounts the property uses for service charge. Timing matters: accruals, prepaid items, and invoices that straddle period boundaries need consistent treatment, or variance flags will be noise rather than signal.

Budgets. The approved service charge budget for the same period and property (or cost center), including any mid-year revisions the lease or management agreement treats as binding for recovery. Budget lines should map to the same cost categories used for actuals so variance analysis is line-comparable.

Lease provisions. Per-tenancy rules that define recoverability and share: inclusion and exclusion schedules, caps and collars, base years, gross-up methods, pro-rata shares (area, units, or custom keys), and any special agreements (e.g., fixed contributions or landlord-absorbed items). Without lease text or structured lease data, the model cannot decide whether a cost is recoverable or how to split it.

Supporting references help but do not substitute for those three: floor areas and occupancy for the period, prior-year certified statements for continuity checks, and the property’s coding standards for invoice classification.

Once inputs are available, the model typically proceeds in layers.

First it aligns actuals to budget categories and computes variances at the property (or cost pool) level. Large or unexpected variances are candidates for investigation: miscoded invoices, non-recoverable costs booked to recoverable accounts, timing differences, or genuine overspend.

Second it applies lease rules to each recoverable pool. For each tenant it derives a draft share using the lease’s apportionment key, then adjusts for caps, exclusions, base-year logic, and gross-up where the lease requires it. Tenants with non-standard clauses get clause-specific treatment rather than a single property-wide formula.

Third it emits exception candidates: costs that look non-recoverable under common lease language, allocations that exceed a cap, shares that do not sum to 100% of the recoverable pool, tenants whose area or occupancy data is stale, and lines where budget and actual category mapping is ambiguous. Exceptions are for human review, not automatic write-offs.

Fourth it produces draft tenant-level apportionment statements: recoverable totals, share basis, calculated contribution, variance to any estimated on-account payments, and a line-level trail from cost pool to tenant share. The draft is an input to certification, not the certified result.

Machine learning helps where rules alone are brittle: classifying borderline invoices against historical coding decisions, ranking which variances are most likely misallocation versus true cost change, and spotting patterns that repeat across periods (for example, the same supplier always hitting the wrong cost pool). Rule engines still own hard lease math; ML supports prioritization and coding consistency.

Human-in-the-loop means the accountant owns the certified numbers. Typical review steps:

• Confirm the period cut-off and that all material actuals for the period are posted.
• Accept, reclassify, or exclude flagged costs before they enter recoverable pools.
• Verify lease interpretation on caps, exclusions, and special tenants; override model shares where the lease or side letter requires it.
• Check that pro-rata keys and areas match the measurement standard the leases use for that period.
• Reconcile draft tenant balances to on-account service charge collected and to prior certified positions where continuity matters.
• Sign off (or reject) the draft statements and retain the exception log as part of the audit trail.

Empty or partial runs must not be papered over. If actuals, budgets, or lease provisions are missing for a property or tenant set, the model should return no apportionment for that scope. Accountants then fix the data gap and re-run rather than certify from incomplete drafts.

Useful outputs for a bill-stage, cost-focused workflow include:

• Property-level budget vs actual variance summary by cost category.
• Recoverable vs non-recoverable (or excluded) cost splits with rationale tags.
• Tenant-level draft apportionment statements with share basis and calculated amounts.
• Exception and override lists suitable for workpaper retention.
• A lineage record: which actuals, budget version, and lease provision set produced each draft figure.

Auditors and asset managers care that every tenant figure can be traced back to source documents and to the clause that justified the share. The model should preserve that lineage in machine-readable form so a later can re-open the same evidence pack.

Downstream teams may use certified (not draft) balances for billing adjustments, credit notes, or arrears follow-up. Linking recovery shortfalls to collection risk is a separate concern; see .

This model fits multi-tenant assets with material service charge or CAM recovery, heterogeneous lease clauses, and enough historical coding to make exception ranking useful. It is most valuable when reconciliation is periodic, high-volume, and currently dependent on spreadsheet merges that break when leases or budgets change.

It is a poor fit when leases are entirely fixed-fee with no variable recovery, when the property has no reliable actuals or budget for the period, or when lease data is incomplete for a large share of tenants. In those cases, fix data quality first; the correct model behavior is empty output, not a guessed allocation.

Success looks like fewer undetected misallocations, faster accountant review cycles, and statements that survive audit because every draft line is tied to actuals, budget, and lease provisions, and every certified line carries an accountable human sign-off.