Commercial Property Purchase Order Approval Workflow: Control Spend Before the Invoice

Commercial Property Purchase Order Approval Workflow: Control Spend Before the Invoice

The invoice is a poor place to discover that no one agreed on the scope, price, or property responsibility for a job.

That is exactly how non-routine spending turns into a scramble. A manager asks a vendor to investigate a roof leak. The vendor finds more work than expected. A verbal go-ahead becomes a larger bill. By the time the invoice arrives, the people reviewing it may be trying to reconstruct the request, compare it with a quote, locate the lease context, and decide whether the work was authorized.

A purchase order workflow moves that conversation forward. It creates a record before the commitment is made, not after the cost is already on the invoice.

For a commercial landlord, the goal is not to force every small, recurring purchase through a heavy process. It is to create a dependable path for non-routine work: a repair outside a service contract, a capital project, a replacement purchase, a tenant-related request, or any spend that needs more than one person to review it.

> A purchase order is an operating record, not a substitute for a signed contract, lease interpretation, or professional legal and accounting advice.

Decide which spending needs a purchase order

Start by defining when the workflow applies. If every light bulb, cleaning supply, or recurring contracted service requires the same review as a major repair, the process will be ignored. If no one knows when approval is required, teams will make exceptions by habit.

Set a written rule that fits the portfolio. It can distinguish among:

• recurring services already covered by a current agreement
• routine operating purchases within a manager's assigned authority
• non-routine repairs, replacements, or tenant requests
• emergency work needed to protect people or property
• spending above a specified threshold
• projects that may require owner, lender, partner, or other outside approval

The threshold is not the only test. A smaller job may still deserve review when it affects a tenant relationship, involves a new vendor, changes the scope of a contract, or may have lease-related cost questions. The useful rule is simple: when the decision could be hard to explain later, create the record before work starts.

Start with a request that describes the work

The purchase order should begin with a request, not a vendor invoice. A good request gives the approver enough context to understand what is being bought and why.

Capture the basics in one place:

• property, building, suite, common area, or equipment involved
• requester and the person accountable for moving the request forward
• a plain-language description of the condition or business need
• proposed scope, including what is included and what is not
• requested completion timing and any operational constraint
• estimated cost, supporting quote, or not-to-exceed amount
• photos, inspection notes, work order, or other supporting record when relevant
• whether the work is routine, emergency, tenant-related, recurring, or capital in nature

Do not let a vague description carry the process. “Repair HVAC” may be enough to start a vendor conversation, but it does not tell an approver which unit is affected, what diagnosis was made, or what result the vendor is expected to deliver. A short, specific scope makes it easier to compare quotes, confirm completion, and evaluate a change request later.

For physical work, link the request to the same maintenance record the team uses to track status and follow-up. That keeps a commercial property maintenance tracking process from splitting into one record for the problem and another for the spend.

Add property and lease context before routing approval

An approver should not have to search a shared drive to learn which property the request serves. Identify the location, operating category, and available context before the request moves forward.

For a tenant suite or shared area, record what the team knows without making assumptions:

• Is the work in a tenant premises, a common area, or a building system?
• Is there a service contract, warranty, prior repair, or vendor recommendation tied to the request?
• Does the request relate to a tenant obligation, landlord obligation, or an unresolved question?
• Is the cost expected to be considered for operating-expense recovery, excluded from recovery, or subject to review?

The lease controls the obligations and recovery rules. A purchase order should flag the question and link the relevant commercial lease abstract or source documents; it should not declare who is responsible based on a tracker label alone. When the documents or facts are unclear, assign that review to a qualified decision-maker before treating a cost as tenant-billable.

Check the budget and set the approval route

Approval is more useful when it includes the reason a request is being approved. Before routing the purchase order, compare the proposed commitment with the current operating or project budget and record the result.

The reviewer needs to see whether the spend is:

• within an existing budget category
• within a project authorization or reserve plan
• outside budget but necessary to address a documented issue
• likely to require a reforecast, owner discussion, or further approval

This does not require a perfect annual budget. It requires an honest status. “Budget not yet confirmed” is better than allowing a request to look approved when the team has not checked the available information.

Use a clear routing rule. For example, the property manager may verify scope and site need, an asset manager or owner may approve a larger commitment, and accounting may confirm that the cost has the necessary coding and payment controls. The exact titles vary by portfolio. What matters is that the purchase order identifies the required approver before it becomes urgent.

Select the vendor with the record attached

The vendor-selection step is where a purchase order can prevent later confusion. Attach the quote, proposal, service agreement, or explanation of the selection to the request record.

For a competitive quote process, retain the options considered and the reason for the selection. For an emergency, record why immediate action was needed, who authorized it, and what follow-up review remains. For a trusted existing vendor, identify the applicable agreement or prior authorization instead of relying on memory.

The objective is not to create paperwork for its own sake. It is to make the decision understandable to someone who was not on the call. That becomes especially important when a vendor changes technicians, a property manager changes roles, or the invoice arrives weeks after the work.

Before issuing the purchase order, make the financial guardrails visible:

• approved vendor and contact
• agreed scope and quote version
• approved amount or not-to-exceed limit
• taxes, freight, permits, allowances, or other known additions when applicable
• expected start and completion dates
• required completion evidence, such as photos, sign-off, or a service report
• any instruction not to proceed beyond the approved limit without written approval

Record the approval decision, not just “approved”

An approval record should tell the next person what was decided. A one-word email response is rarely enough once a request is questioned later.

At a minimum, preserve:

• the approver's name and role
• the approval date and approved amount
• the quote, scope, or request version approved
• any conditions, exclusions, hold instructions, or not-to-exceed limit
• any unresolved lease, budget, insurance, contract, or access question
• the person responsible for the next action

This is also the right time to assign a purchase order number or other stable identifier. Use that identifier on vendor instructions and ask the vendor to include it on the invoice. A consistent reference helps connect the request, authorization, work record, invoice, and payment decision without relying on similar vendor names or memory.

Treat change orders as a new decision

Scope changes are normal in property operations. The problem is not that a vendor finds concealed damage or a tenant asks for an added item. The problem is allowing the extra cost to become invisible until billing.

When the scope, price, timing, or materials change, pause the original assumption and create a change record. It should show:

• what changed and why
• the additional or revised amount
• the updated total commitment
• whether the budget status changed
• whether new lease or tenant context needs review
• who approved the change before the vendor proceeds

For a real emergency, the record may follow the immediate action. Document the conditions, authorization, and next review as soon as the situation is stable. Do not use “emergency” as a standing workaround for incomplete planning.

Hand the completed purchase order to invoice review

The purchase order does not replace invoice approval. It gives the invoice reviewer a baseline for checking whether the bill matches the authorized work.

When an invoice arrives, connect it to the purchase order and confirm the key facts before it goes into the payment queue:

• the vendor, property, and purchase order reference match the approved record
• the billed scope and amount align with the approved quote or authorized change
• the work was completed, delivered, or otherwise verified as appropriate
• any retained amount, credit, dispute, or remaining punch-list item is clear
• accounting coding, property allocation, and lease-related questions have an owner
• the invoice has the information needed for the separate payment-release decision

This creates a cleaner bridge to a commercial property accounts payable approval workflow. The purchase order answers, “Should we commit to this work?” The invoice review answers, “Does this bill match the authorized work, and is it ready for payment?” Keeping those decisions connected but distinct helps prevent both surprise invoices and rubber-stamp payments.

A commercial property purchase order checklist

Use this checklist for non-routine commercial-property spending:

• Confirm the request falls within the portfolio's purchase-order rule or document why an exception applies.
• Identify the property, location, requester, business need, and accountable next-action owner.
• Write a specific scope and attach quotes, photos, inspection notes, work orders, or contract context as needed.
• Flag relevant budget, service-contract, warranty, lease, tenant, or recovery questions without assuming the answer.
• Record the budget status and required approval threshold.
• Document the selected vendor, quote version, approved amount, and not-to-exceed limit.
• Preserve the approver, date, conditions, and unresolved follow-up items.
• Give the vendor a stable purchase-order reference and instructions for invoices and change requests.
• Route every change in scope, cost, or timing through a documented approval decision.
• Link the completed work and invoice to the original purchase order before payment review.

Make the record useful when the team changes

The practical value of a purchase-order workflow appears when the person who made the original call is unavailable. Someone else should be able to open one record and see the property, the need, the scope, the selected vendor, the approved limit, the change history, and the invoice handoff.

That visibility protects the relationship with vendors and tenants as much as it protects the budget. It gives the team a faster way to answer basic questions before a cost turns into a dispute, a month-end exception, or a long email thread.

PigJet helps commercial landlords keep property records, lease context, vendor documents, tasks, and follow-up work connected. If non-routine spending still starts in a text thread and ends with a surprise invoice, explore a one-property PigJet pilot to test a clearer operating record.