Landlord Invoice Routing SOP for Client Accounting Teams

Landlord Invoice Routing SOP for Client Accounting Teams

The single most common reason commercial tenant clients overpay landlords is workflow drift. The lease is in the file. The reconciliation statement is in the inbox. The monthly invoice is in the portal. And the bookkeeper, working through a 200-vendor AP run, processes the landlord invoice exactly the same way they process the office supply invoice. No verification, no comparison to the lease, no flag for the reconciliation true-up that just landed. I built CAMAudit because the analytical side of catching CAM overcharges is structured, but the upstream workflow that gets the right document in front of the right reviewer is what decides whether the analysis ever happens.

This article is the routing SOP for landlord documents inside a client accounting team. It is designed to plug into a standard AP workflow, isolate landlord-specific documents for the verification they need, and produce defensible documentation 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 SOP

A typical commercial tenant client has 30 to 80 vendor relationships. The landlord is one of them, and most months, the landlord invoice looks like the others: a recurring amount, automated entry, code to rent expense, schedule for payment. The casual AP defaults that work for utility bills and software subscriptions break down for landlord invoices in three places.

The reconciliation statement is not a regular invoice. It arrives once a year, contains a true-up that may swing several thousand dollars in either direction, and references calculations the casual AP process cannot verify. Treating it as a standing invoice is how systematic overcharges get paid.

Correspondence often carries economic substance. A notice of CAM estimate revision, an escalation letter, a notice of audit-rights deadline, an amendment proposal: these documents change the expected amounts on future invoices. Filed without review, they leave the abstract out of date and the bookkeeper unable to verify subsequent invoices.

The portal is not a verification system. Many landlords issue invoices through an online portal that allows direct payment. Bypassing the firm's AP process to pay through the portal is faster but skips every verification step.

After testing reconciliation samples through CAMAudit, the firms that catch CAM overcharges consistently are the ones that pull every landlord document through a routing SOP, not the firms that rely on bookkeeper memory or partner-level oversight at year-end.

The four document categories

The SOP starts by classifying every landlord document into one of four categories. The classification happens at intake, before the bookkeeper does any other processing.

Category 1: Standing monthly invoice. The recurring monthly invoice that includes rent, estimated CAM, estimated taxes and insurance, and any other recurring authorized charges. This is the most common document type.

Category 2: Reconciliation statement. The annual (or occasionally semi-annual) statement that reconciles estimated CAM payments against actual landlord operating expenses, producing either an underpayment owed by the tenant or a credit owed by the landlord. This is the highest-stakes document type.

Category 3: Correspondence. Letters, notices, and communications that do not produce a payment but contain economic information that affects future invoices. Examples include CAM estimate revisions, escalation notices, audit-rights notifications, lease amendment proposals.

Category 4: Miscellaneous. Everything else: signage approvals, after-hours HVAC requests, parking confirmations, certificate of insurance requests. These rarely produce direct economic exposure but should be filed for reference.

Routing for each category

Each category has its own routing path. The path is documented in the SOP and trained into the bookkeeping team.

Category 1 routing: Standing monthly invoice

1. Intake (bookkeeper): Log invoice, attach to property file
2. Classification (bookkeeper): Confirm Category 1
3. Variance check (bookkeeper): Tie to lease abstract per the variance review workflow
4. Approval (bookkeeper, if no flag; controller, if flagged): Approve for payment or hold pending review
5. Payment (bookkeeper): Schedule per terms
6. Documentation (bookkeeper): Note "no variance" or attach flag documentation in close package

Category 2 routing: Reconciliation statement

1. Intake (bookkeeper): Log statement, attach lease abstract
2. Classification (bookkeeper): Confirm Category 2
3. Hold (bookkeeper): Do not approve true-up payment; route immediately to controller
4. Findings analysis (controller): Run CAMAudit, review structured findings report, validate against lease
5. Recommendation (controller): Approve, dispute, or extend review
6. Approval (partner, if material): Decide on dispute strategy
7. Payment or dispute (per partner decision)
8. Documentation: Full findings report and decision memo in close package

Category 3 routing: Correspondence

1. Intake (bookkeeper): Log correspondence
2. Classification (bookkeeper): Confirm Category 3
3. Routing (bookkeeper): Forward to controller for review
4. Action (controller): Update lease abstract if economic substance, file if informational, flag to partner if dispute-related
5. Documentation: Note in property file with action taken

Category 4 routing: Miscellaneous

1. Intake (bookkeeper): Log document
2. Classification (bookkeeper): Confirm Category 4
3. File (bookkeeper): Attach to property file for reference
4. 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

Approval authority at each stage

The SOP makes the approval authority explicit. Authority limits prevent both the cases where bookkeepers approve too freely and the cases where partners get 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)

"Material" thresholds are firm-specific, but most firms set the partner-involvement threshold at $5,000 to $10,000 of true-up impact.

Handling electronic landlord portals

Landlord portals create the highest workflow risk because the portal interface is designed for fast direct payment, which bypasses the SOP. The portal-handling rule in the SOP is simple: the portal is a document source, not a workflow.

The bookkeeper downloads the invoice from the portal at the same cadence the portal issues it. The downloaded invoice flows through the SOP exactly like any other invoice. Payment happens through the firm's standard AP process, which routes through the bookkeeper, the variance check, the controller (if flagged), and the payment system. The portal's "pay now" button is not used.

This rule sometimes generates pushback because the portal is faster. The SOP holds because the portal cannot verify what the firm needs to verify.

See the AP exception tracker for accounting firms for the documentation system that supports the SOP, and the CAS firm landlord bill review workflow for the variance check that runs inside Category 1 routing.

Implementation and rollout

For a firm adopting the SOP, the rollout takes about two weeks. Week 1: write the SOP, document the four categories, define approval thresholds, brief the team. Week 2: apply the SOP to every landlord document received in the next close cycle, with the controller spot-checking classification accuracy. After two close cycles, the SOP is part of the firm's standard intake.

The result is a routing structure that catches the high-stakes documents (reconciliations, correspondence) that the casual AP defaults would miss, and processes the routine documents (standing invoices) faster because the variance check has a clear pass/fail outcome.

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.