Find utility charges across systems
Compare direct utility bills with landlord CAM support.
Do not match on amount alone. The property and service period must agree.
The utility service must also agree. Then check the lease payment duty.
A match is only a review candidate. A reviewer must clear or confirm it.
Know the two data sets
Start with direct pay AP records. These show bills paid to utility vendors.
Then use landlord CAM support. These records may include utility cost rows.
The data sets answer different questions. AP shows what the client paid directly.
CAM support shows what the landlord billed back. The lease says who owed the cost.
You need all three sources. No single source proves a duplicate.
Extend duplicate checks
SAP duplicate checks use common invoice fields. Those include supplier, currency, and gross amount.
SAP can also use company and reference. Invoice date can be part of the check.
Those fields help inside one invoice set. They do not prove utility overlap across CAM.
Add these utility fields:
- Canonical property
- Meter or service account
- Utility service type
- Service start date
- Service end date
- Utility vendor
- Gross amount
- Currency
- Direct pay duty
- CAM statement line
- CAM support link
- Match strength
- Review owner
"One property name" means one saved site name. It keeps naming changes from splitting one site.
Preserve direct pay duty
Do not infer duty from payment history.
A client may pay a bill by mistake. A landlord may bill a valid shared service.
Read the signed lease utility clause. Record the duty for each service.
Use plain duty states:
| Duty state | Meaning |
|---|---|
| Client direct pay | Client pays the vendor |
| Landlord pass through | Landlord may allocate the cost |
| Shared duty | Contract splits the cost |
| Unclear | A reviewer must read the clause |
| Disputed | Counsel may need to review meaning |
We propose these work states. They are not legal findings by themselves.
Lease invoice guidance calls for a lease check. It also calls for CAM and utility support.
That source gives work guidance. The signed lease controls each duty.
Normalize property and service
One property may have many names. Create one site record before matching.
Save these property keys:
- Client property code
- Street address
- Suite or unit
- Lease name
- Landlord property name
- AP location code
- CAM statement property name
Do not merge sites on street alone. Separate suites may have different duties.
Next, normalize the utility service. Power and water are not the same service.
Use the meter when it exists. Otherwise use the service account and location.
Compare service periods
Invoice dates do not prove service overlap.
One bill may arrive after service ends. Another may use a year end cost split.
Save both service dates when available. Mark missing dates as missing data.
Use this date logic:
| Period result | Meaning |
|---|---|
| Exact | Start and end dates match |
| Overlap | Some service days overlap |
| Separate | The service periods do not overlap |
| Unknown | One source lacks service dates |
Do not turn "unknown" into "exact." Route unknown periods for document review.
Set match strength
Use four plain result states.
| Strength | Minimum evidence | Action |
|---|---|---|
| Exact | Site, service, period, duty, and amount agree | Send to reviewer |
| Probable | Core fields agree, but one key is missing | Request proof |
| Weak | Only broad fields agree | Keep as a lead |
| Cleared | Evidence shows different costs | Save the reason |
Do not block payment from match strength alone. The client controls payment action.
The reviewer should see both source records. The reviewer should also see the lease clause.
Build the join record
Keep one record for each candidate pair.
| Join field | Direct AP side | CAM side |
|---|---|---|
| Property | AP site code | Statement property |
| Service | Vendor service | CAM line label |
| Account | Meter or service account | Support account when shown |
| Period | Invoice service dates | Support service dates |
| Vendor | Utility vendor | Landlord support vendor |
| Amount | Direct bill amount | Allocated or source amount |
| Duty | Lease direct pay rule | Lease pass through rule |
| Evidence | Invoice and payment | CAM line and support |
Then add these decision fields:
- Match strength
- Missing proof
- Review owner
- Review state
- Finding reason
- Client decision
- Closure evidence
Keep the raw amount and client share apart. They may not be the same measure.
Walk one utility match
This utility example is fictional. The site, vendor, and amounts are made up.
West Lane Cafe pays its own power bill. The lease says the client pays power directly.
AP shows a $1,240 power bill. It covers June at Store 8.
Landlord support lists $1,240 for power. It also names June and Store 8.
The CAM statement includes that support row. The same utility vendor appears on both records.
Build this candidate:
| Field | Entry |
|---|---|
| Property | Store 8 |
| Service | Electric power |
| Period | June, exact dates saved |
| Vendor | Same utility vendor |
| Direct amount | $1,240 |
| CAM support amount | $1,240 |
| Lease duty | Client direct pay |
| CAM line | Utilities |
| Match strength | Exact candidate |
| Review owner | Lease CAM reviewer |
"Exact candidate" is not a final finding. The reviewer checks both source records.
The reviewer also checks cost split details. The landlord row may cover another meter.
If it covers another meter, mark it cleared. Save that meter as closure proof.
If the evidence confirms overlap, record why. Then route the finding to client review.
Handle common errors
Most bad matches come from missing context.
| Error | Why it fails | Better control |
|---|---|---|
| Same amount only | Different services can cost the same | Add service and period |
| Same vendor only | One vendor may serve many sites | Add property and account |
| Invoice date only | Invoice date may trail service | Use service dates |
| Property name only | Names may vary or collide | Use canonical site keys |
| CAM label only | "Utilities" may cover many services | Use support detail |
| Payment history only | Payment does not prove duty | Read the lease clause |
| Automatic payment hold | A candidate may be valid | Require client approval |
Do not force a weak pair into closure. Ask for the missing proof.
Test one property month
Start with a small test set. Do not enable broad alerts first.
Choose one property and service month. Collect both data sets and the lease.
Run these steps:
- Normalize the property.
- Normalize the utility service.
- Save both service periods.
- Link vendor and account data.
- Save direct and CAM amounts.
- Record the lease duty.
- Assign match strength.
- Send possible matches to a reviewer.
- Save each closure reason.
Review false matches before adding more sites. Adjust keys without hiding missing data.
Send each join record to its named reviewer.
The AP consultant pillar places this check in the offer. The landlord invoice guide routes all other issues.
The CAM queue guide stores the review state. The CAM match guide tests the CAM evidence.
Use the system consultant hub for wider system work. The Practice Growth hub shows other firm paths.
Where CAMAudit fits
CAMAudit reviews the join record's supplied CAM evidence. It may flag a possible utility overlap.
| Working record | Next owner |
|---|---|
| Utility join record | AP automation consultant |
It does not scan AP transactions all day. It does not approve or stop payments.
CAMAudit can cite lease and statement lines. It can add checked findings to a branded CAM audit.
Your firm reviews and signs the utility CAM audit. Your client keeps payment control.
CAMAudit may prepare a dispute letter draft from that finding. The draft is not legal advice.
Have counsel review before sending.
Use closed join records in the service line guide.
Ready to add this work to your firm? Get started.