# Service charge (CAM) reconciliation

> Service charge (CAM) reconciliation: Costs recoverable and apportioned Checked: proven by code. Produces year-end statements, balancing charges.

Source: https://www.sumarity.ai/library/service-charge-reconciliation/

Real estate 

# Service charge (CAM) reconciliation

Reads service costs, the apportionment schedule, leases. Produces year-end statements, balancing charges. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Proven by codeBilling and revenue assurance
Start from this workflowMore for real estate  

What it decides

## Narrow questions, each with a check behind it.

Costs recoverable and apportioned
Proven by code: apportionment recomputed. Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.

| Reads | Service costs, the apportionment schedule, leases 
| Produces | Year-end statements, balancing charges 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Billing and revenue assurance 
| Industry | Real estate    

See it run

## Every line, decided where it's safest.

An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.

ReadsService costs, the apportionment schedule, leasesCodeReads, matches, ties out and works out every figure.JudgementCosts recoverable and apportioned. Settles only when it clears the cutoff and code proves it.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesYear-end statements, balancing charges  
Service charge (CAM) reconciliation · example run Example run  

| Ref | Item | Value | Decided by  
| SC-1 | Cleaning, common areasRecoverable, shared by area | 24,000.00 | Code · apportioned 
| SC-2 | Roof repairRepair recoverable · 0.90 | 18,000.00 | Engine · proven 
| SC-3 | Roof replacementCapital or repair? · 0.62 | 60,000.00 | To a person 
| SC-4 | Management feeWithin the lease cap | 9,600.00 | Code · within cap 
| SC-5 | Lift maintenanceGround-floor unit excluded · 0.94 | 6,000.00 | Engine · proven  
|  

Settled 4 To a person 1 Settled wrong 0      Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.    

What it could save

## Your volumes in. Your hours out.

In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.

Items per run 
Runs per month 
Minutes per item by hand 
Cost per hour

Share of items that still need a person: 30%  

By hand today80 ha month 
With Sumarity24 ha month, for the items people decide 
Saved56 hCHF 53,760 a year    

Related

## Start from what's closest.

### Billing and revenue assurance in other work

Asset management

### Management and performance fee check

Fee basis, rates, periods

Proven by codeHealthcare

### Charge capture reconciliation

Services delivered vs billed

Proven by codeRetail and hospitality

### Supplier rebates and promotional allowances

Rebate earned under which agreement

Proven by code

### More for real estate

### Lease abstraction

Terms from the lease: rent, breaks, reviews

Proven by code

### Rent roll to bank reconciliation

Which receipts pay which tenant's rent

Proven by code

### Tenant referencing

Income and references sufficient

Cross-checked  

Questions

## What buyers ask

What happens when Sumarity isn't sure?

Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.

How are its judgements checked?

Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.

Can we change it to fit how we work?

Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.

Does it read our files as they are?

Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.

Where does our data go?

Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.

How does it get better?

Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.

## Start from this workflow. Run it on your data.

A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.

Talk to usBack to the library