Commercial Property Accounts Payable: An Approval Workflow for Landlords

A vendor bill can arrive long after the call, email, or site visit that created it. By then, the person opening the invoice may not know which property it concerns, whether the work was authorized, whether it was completed, or how the charge relates to a tenant obligation.

That is where commercial property accounts payable breaks down. The invoice is treated as the beginning of the workflow instead of the evidence that closes one.

For a commercial landlord, a workable approval process should answer a few practical questions before a bill moves to payment: What was purchased? Which property and area does it serve? Who requested or authorized it? Was the work completed as expected? Is there lease, service-contract, or budget context that the reviewer needs to see? Who approved it, and what exactly is being handed off for payment?

The answers do not need to live in one massive system. They do need to be visible, assigned, and retained. Otherwise, the same invoice gets forwarded through inboxes, re-entered in a spreadsheet, and revisited at month-end or during a tenant question.

Why vendor-bill approvals get messy in commercial property

Commercial invoices often have more context than a simple office expense. A landscaping bill may cover a whole retail center. A plumbing invoice may relate to a common-area issue, a tenant suite, or an emergency repair with a cost question still under review. A utility bill may need a property allocation. A recurring service invoice may need a check against the agreed scope and billing period.

When that context is separate from the bill, reviewers have to reconstruct it. They search email threads for the vendor request, ask a property manager whether the work happened, look for a work order, and pull the lease only after someone asks whether the cost can be passed through.

That work creates two common problems:

• Approval becomes a rubber stamp. The approver sees an amount and a vendor name but not the basis for the charge.
• Payment becomes a communication loop. The accounting team receives a bill with an unclear coding note or missing approval and has to send it back to operations.

A better workflow does not promise that every cost question has an automatic answer. It makes the unanswered question explicit before the bill is paid or included in a tenant charge.

Start with an intake record, not an inbox folder

The first control is simple: every bill needs one intake record. Whether the invoice comes by email, portal download, mail scan, or vendor upload, record the source document and enough information to route it without guessing.

At a minimum, capture:

• vendor name and invoice number
• invoice date, due date, amount, and payment terms
• property, building, suite, or common area served
• service period or date of work when shown
• a short description of the goods or work
• the related work order, contract, quote, or approval request when one exists
• the person responsible for resolving missing context

Do not silently correct a bill and discard the original. Keep the invoice as received, then document the clarification or correction that changed the review. That is especially useful when a vendor resubmits an invoice, when two invoices appear similar, or when a bill needs to be questioned before payment.

The intake step should also identify exceptions early. Examples include a missing invoice number, a duplicate amount, an unfamiliar vendor, an overdue bill with no prior record, or a charge assigned to the wrong property. An exception is not proof that the bill is wrong. It is a reason to pause the normal route until an owner answers the question.

Give each bill a property and operating context

“Maintenance” is not enough coding detail for an approver who did not place the call. Before a bill goes forward, attach the operational context that explains why the expense exists.

For one-time work, that may be the request, scope, estimate, work order, site photo, vendor report, or completion confirmation. For recurring work, it may be the service agreement, billing schedule, property roster, and any documented exception from the normal scope.

The goal is not to make a property manager write an accounting memo for every invoice. It is to prevent a reviewer from having to rely on memory. A useful record lets the reviewer see that a sidewalk repair was requested after an inspection, that it was completed at a named location, and that the invoice matches the approved scope closely enough to move forward—or needs a follow-up.

This same discipline improves commercial property work-order management. When the work request, vendor communication, completion record, and invoice can be connected, the bill is not an isolated accounting document.

Separate operational approval from payment release

One person can perform both actions in a very small portfolio, but they are still different decisions.

Operational approval asks whether the invoice reflects authorized work, a valid contract charge, or a documented obligation. The reviewer checks the property, vendor, scope, timing, amount, and completion evidence. If something is unclear, the bill returns to the person who can answer it.

Payment release asks whether the approved bill is ready to enter the accounting and payment process. The reviewer confirms the approved amount, coding, payee, due date, payment method, and any company-specific payment control.

Keeping those questions distinct makes exceptions easier to manage. A property manager may be able to confirm that emergency work was necessary, while an owner or accounting lead needs to decide whether an invoice over a threshold requires additional review. Conversely, accounting may be ready to schedule payment only after a missing contract or tax form is supplied.

Define the roles by decision, not job title. A practical workflow usually identifies:

• the intake owner who records the bill and flags what is missing
• the property reviewer who confirms the work, location, and supporting record
• the financial reviewer who checks coding, budget context, and internal approval rules
• the payment owner who receives a complete, approved handoff
• the exception owner who is responsible when the bill cannot advance

For recurring vendors, the approval level can be based on the agreement, amount, property, or exception type. The point is to make the rule understandable before the invoice arrives, not invent it after a late bill is sitting in the queue.

Make lease-aware coding a review question

In an NNN or other expense-recovery setting, an invoice may later inform operating-expense reporting or tenant billing. That does not mean every vendor bill should be treated as recoverable when it first arrives.

Instead, include a lease-aware review question: What lease, property, and accounting context must be checked before this cost is classified for recovery or allocated to tenants?

Depending on the property and agreements, that can mean checking the affected area, service period, expense category, cost pool, exclusions, caps, allocation method, or supporting documents. It can also mean marking the item for later review rather than making a final recoverability decision at invoice entry.

This is important because an invoice can be valid for payment even when its tenant-treatment question is unresolved. Paying a vendor and deciding how a cost is reported or recovered are related workflows, but they are not the same workflow.

Use a visible status such as “lease review needed,” “awaiting allocation,” or “not included in recoveries” according to your process. A status prevents a pending judgment call from disappearing into a general ledger description. It also creates a useful queue for month-end operating-expense review instead of forcing the team to rediscover the issue during reconciliation.

Lease terms, amendments, accounting policies, and local requirements can differ. Review the applicable agreements and accounting setup with qualified legal and accounting advisors where appropriate; this workflow is an operational framework, not legal or accounting advice.

Use clear approval states and exception paths

An approval queue should tell the team what is happening without opening every document. Avoid a single “pending” status that can mean anything from “new invoice” to “waiting on the owner.”

Consider states such as:

• received and needs intake review
• waiting for property confirmation
• waiting for vendor correction or backup
• ready for financial review
• approved for payment handoff
• on hold pending lease, contract, or allocation review
• paid, with payment reference retained

The label matters less than the next action. Each state should have an owner and a condition for moving forward. For example, “waiting for property confirmation” should name the manager and ask a specific question: Was the storefront glass repair completed at Suite 110 on the stated date, and does the invoice match the quoted amount?

For a disputed or incomplete bill, preserve the original invoice, the communication with the vendor, and the decision that resolved it. If a vendor credit, revised invoice, or partial payment is involved, link it to the original bill. That small discipline keeps an old exception from turning into a duplicate-payment or tenant-communication problem later.

Hand off to payment without losing the approval trail

The payment handoff should not be an email that says “approved” with a PDF attached. A complete handoff identifies the bill, approval decision, coding, payment due date, and remaining exception, if any.

Before sending a bill to the payment owner or accounting system, confirm:

• the invoice is legible and attached to the record
• the vendor and invoice number have been checked for duplicates
• the property and service context are identified
• the responsible reviewer approved the work or contract charge
• the accounting coding and internal approval rule were reviewed
• any lease-aware or allocation question has an owner and status
• the payment amount, due date, and any discount or hold instruction are clear

This is also where a portfolio-specific policy can reduce last-minute confusion. A written rule might specify who can approve a bill, which thresholds need a second review, what evidence is required for emergency work, and when the payment owner should stop and send the bill back. The policy should fit the portfolio’s accounting system and authorization controls rather than copying a generic template.

Review the queue before it becomes a month-end problem

Accounts payable is easier to control when it is reviewed as an operating queue, not only as a batch of bills due this week. A short recurring review can surface bills that are aging without approval, repeat vendor exceptions, work completed without an invoice, invoices received without completion proof, and costs that still need lease or allocation review.

Look for patterns that point to a process fix:

• the same vendor bills the wrong property or period repeatedly
• a recurring invoice keeps arriving without a current service agreement
• property managers are approving work after the invoice arrives because no request record exists
• a cost category routinely reaches reconciliation without enough support
• one approver becomes the bottleneck because the route is not defined

Those patterns are more useful than blaming a person for a late bill. They reveal where the workflow needs a clearer intake field, a required attachment, a recurring review, or a better connection between operations and accounting.

A practical commercial AP approval checklist

Use this checklist when setting up or reviewing your process:

• Capture every vendor bill in one intake record with the original invoice attached.
• Identify the vendor, invoice number, amount, due date, property, and service period.
• Link the bill to the request, work order, contract, quote, or completion evidence when applicable.
• Assign a property reviewer to verify the work or recurring service context.
• Route unclear, duplicate, or disputed bills to a named exception owner.
• Separate the operational approval decision from the payment-release decision.
• Check the coding and identify lease-aware or tenant-allocation questions without assuming the answer.
• Record the approver, decision date, and any hold or follow-up required.
• Hand off complete payment instructions with the supporting record intact.
• Review aging and exception patterns before month-end and before commercial landlord accounting issues become harder to trace.

Build a process people can follow under pressure

The value of an accounts payable workflow shows up when something is missing: the emergency repair invoice, the unfamiliar vendor charge, the bill that arrives after a property manager leaves, or the cost that needs a lease review before it reaches tenant reporting.

If the team can quickly see the property, work, documents, reviewer, decision, and next action, the issue can move without guesswork. If those details are spread across an inbox, a shared drive, and a spreadsheet, every exception becomes a reconstruction project.

PigJet helps commercial landlords keep property records, lease context, vendor documents, tasks, and follow-up work connected. If vendor-bill approvals still depend on forwarding invoices and asking who remembers the work, explore a one-property PigJet pilot to test a clearer operating record.