Landlord Invoice Routing SOP for Client Accounting Teams
Most clients overpay landlords for one reason. The workflow drifts. The lease sits in the file. The reconciliation lands in the inbox. The monthly invoice waits in the portal. The bookkeeper runs a 200-vendor AP batch. AP is the accounts payable run that pays bills. The landlord invoice gets treated like the office supply invoice. No one checks it against the lease. No one flags the true-up. The true-up is the year-end charge that squares estimates against real costs. I built CAMAudit because the math of catching CAM overcharges is clear. CAM means common area maintenance, the shared costs landlords pass to tenants. But the real question is simpler. Does the right document reach the right reviewer? That step decides whether the audit ever happens.
This article is the routing SOP for landlord documents. An SOP is a written step-by-step process your team follows. It plugs into your normal AP workflow. It pulls landlord documents out for a real check. It leaves a clear record at every stage.
Landlord invoice routing SOP: A written standard operating procedure defining the path each landlord-issued document follows through the client accounting team, from intake to payment or filed correspondence. The SOP specifies four document categories (standing invoice, reconciliation statement, correspondence, miscellaneous), the role responsible at each stage, and the verification step that gates each approval. Its purpose is to prevent landlord documents from being processed under the casual AP defaults that work for routine vendor invoices.
Why landlord documents need their own process
A typical client has 30 to 80 vendors. The landlord is just one of them. Most months the landlord invoice looks plain. A set amount. Auto entry. Code to rent. Schedule the payment. The normal AP habits work for utility bills. They break for landlord invoices in three places.
The reconciliation statement is not a normal invoice. It comes once a year. The true-up can swing thousands either way. It rests on math the normal AP run cannot check. Pay it like a standing invoice and overcharges slip through.
Correspondence often hides real money. A CAM estimate change. An escalation letter. An audit-rights deadline. A lease amendment offer. The audit-rights window is the limited time you have to challenge the bill. These letters change future invoices. File them without review and the lease abstract goes stale. The abstract is your short summary of the lease terms. Then the bookkeeper cannot check the next bill.
The portal is not a check. Many landlords bill through an online portal with a pay button. Paying there is fast. It skips every check.
I built CAMAudit and tested reconciliation samples from published audit cases through it. The firms that catch overcharges pull every landlord document through one process. They do not lean on memory or a year-end glance.
The four document types
The process starts by sorting every landlord document into one of four types. You sort it at intake. You do this before any other step.
Type 1 is the standing monthly invoice. It bills rent plus estimated CAM, taxes, and insurance. It can include other approved charges. This is the most common one.
Type 2 is the reconciliation statement. It comes once a year. It checks your CAM estimates against the landlord's real costs. The result is money you owe or a credit you get back. This one carries the most risk.
Type 3 is correspondence. These are letters and notices. They do not bill you, but they carry real money news. Examples are CAM estimate changes, escalation notices, audit-rights notices, and lease amendment offers.
Type 4 is everything else. Signage approvals. After-hours HVAC requests. Parking notes. Insurance certificate requests. These rarely cost money. File them anyway.
Routing for each type
Each type has its own path. You write the path down. You train the team on it.
Type 1 path: Standing monthly invoice
- Intake (bookkeeper): Log invoice, attach to property file
- Classification (bookkeeper): Confirm Type 1
- Variance check (bookkeeper): Tie to lease abstract per the variance review workflow
- Approval (bookkeeper if no flag, controller if flagged): Approve for payment or hold pending review
- Payment (bookkeeper): Schedule per terms
- Documentation (bookkeeper): Note "no variance" or attach flag documentation in close package
Type 2 path: Reconciliation statement
- Intake (bookkeeper): Log statement, attach lease abstract
- Classification (bookkeeper): Confirm Type 2
- Hold (bookkeeper): Do not approve the true-up payment, route to controller right away
- Findings analysis (controller): Run CAMAudit, review structured findings report, validate against lease
- Recommendation (controller): Approve, dispute, or extend review
- Approval (partner, if material): Decide on dispute strategy
- Payment or dispute (per partner decision)
- Documentation: Full findings report and decision memo in close package
Type 3 path: Correspondence
- Intake (bookkeeper): Log correspondence
- Classification (bookkeeper): Confirm Type 3
- Routing (bookkeeper): Forward to controller for review
- Action (controller): Update lease abstract if it changes money, file if informational, flag to partner if dispute-related
- Documentation: Note in property file with action taken
Type 4 path: Miscellaneous
- Intake (bookkeeper): Log document
- Classification (bookkeeper): Confirm Type 4
- File (bookkeeper): Attach to property file for reference
- Action: None unless specifically requested
"The biggest miss in client accounting teams is not the failed analysis at the controller level. It is the document that never made it to the controller because the bookkeeper processed it as routine AP. The routing SOP is what closes that gap, and it does it by classifying the document at intake before any default behavior kicks in." - Angel Campa, Founder, CAMAudit
Who approves at each stage
The process names who can approve what. Clear limits stop two problems. Bookkeepers approving too freely. Partners pulled into routine items.
| Document |
Bookkeeper |
Controller |
Partner |
| Standing invoice (no variance) |
Approves |
(not involved) |
(not involved) |
| Standing invoice (flagged) |
Holds |
Approves or escalates |
(only if escalated) |
| Reconciliation true-up (small) |
Holds |
Approves |
(not involved) |
| Reconciliation true-up (material) |
Holds |
Reviews and recommends |
Approves or disputes |
| Correspondence |
Routes |
Reviews and acts |
(only if escalated) |
| Miscellaneous |
Files |
(not involved) |
(not involved) |
Each firm sets its own "material" line. Most pull the partner in at $5,000 to $10,000 of true-up impact.
Handling landlord portals
Portals carry the most risk. They push fast direct payment. That skips the whole process. The rule is simple. The portal is a document source. It is not a workflow.
The bookkeeper downloads the invoice when the portal posts it. That invoice then flows through the process like any other. Payment runs through your normal AP path. It passes the bookkeeper, the variance check, the controller if flagged, and the payment system. No one uses the portal "pay now" button.
People push back because the portal is faster. The rule holds anyway. The portal cannot check what you need to check.
See the AP exception tracker for accounting firms for the record system behind the process. See the CAS firm landlord bill review workflow for the variance check inside the Type 1 path.
Rolling it out
Most firms set this up in about two weeks. Week 1 is the writing. Write the process. Define the four types. Set approval limits. Brief the team. Week 2 is the test. Run every landlord document through it next close cycle. The controller spot-checks the sorting. After two close cycles, it is just how you intake.
The payoff is real. You catch the risky documents your old habits would miss. Those are reconciliations and correspondence. You also clear routine invoices faster. The variance check gives a clean pass or fail.
Frequently Asked Questions
What is a landlord invoice routing SOP?
A landlord invoice routing SOP is a written standard operating procedure that defines how landlord rent, CAM, and reconciliation invoices flow through a client accounting team from intake to payment. It specifies who receives each document type, how each is classified, what checks happen at each stage, and how exceptions get handled. The SOP exists to ensure no invoice gets paid without verification and no reconciliation gets approved without controller review.
Why does landlord invoice routing need its own SOP?
Landlord invoices are the highest-stakes recurring AP a commercial tenant client receives. Rent is large; CAM reconciliations occasionally produce four-figure or five-figure true-up adjustments; new line items can indicate unauthorized charges. Routing landlord invoices through the same casual AP process used for utilities and supplies produces systematic missed overcharges. A dedicated SOP isolates landlord invoices for the verification they deserve.
What are the document classification categories in the SOP?
The SOP classifies every landlord document into one of four categories: standing monthly invoice (rent + estimated charges), reconciliation statement (annual or partial-year true-up), correspondence (notices, escalation letters, audit-rights communications), and miscellaneous (signage approvals, after-hours requests, anything else). Each category has its own routing path. The classification step is what prevents reconciliation statements from being processed as if they were standing monthly invoices.
Who has approval authority at each stage?
The bookkeeper has approval authority for standing monthly invoices that pass the variance check. The controller has approval authority for reconciliation true-ups and any flagged monthly invoice. The partner has approval authority for any payment over a defined dollar threshold (usually $10,000) or any payment under formal dispute. Correspondence does not produce a payment but requires controller review for content.
How does the SOP handle electronic landlord portals?
The SOP treats landlord portals as a document source, not a workflow. The bookkeeper downloads the invoice from the portal and routes it through the standard SOP exactly as a paper or PDF invoice would flow. Treating the portal as a workflow (paying directly through the portal without routing through the SOP) is the most common path for missed overcharges, because the portal does not enforce verification.