What missing building-level spend looks like in a property portfolio
Building-level spend visibility means every facility cost, from service contracts to repairs and supplies, is recorded against the property it serves, so each building's cost to run is known at any point in the year.
Running buildings is a large, recurring bill. BOMA International's 2026 market study counted $274.9 billion in 2025 operating expenditures across privately owned office, retail and industrial buildings in 79 BOMA markets, about $7.78 per square foot.[1] In a portfolio, that spend is spread across dozens of vendors, sites and budgets, and small coding gaps add up quickly.
The everyday version: a regional HVAC contractor services six buildings under one agreement and sends one monthly invoice. AP codes it to a general repairs account. A roof leak at one property is paid on a manager's card. Supplies for three sites ship to the head office. When the asset manager asks which building costs the most per square foot, finance needs two weeks and a spreadsheet to guess.
CFO / Finance Leader
Cannot explain operating expense variance by property until the books close and the year is over.
"Which building is driving the overrun?"Asset Manager
Needs building-level costs to support budgets, hold or sell decisions and owner reporting.
"I need NOI by property, not a portfolio total."Property Manager
Gets blamed for a budget overrun on costs that were coded to their building by default.
"That invoice was never ours."AP Manager
Receives shared invoices with no building reference and splits them by hand every month.
"Which property does this line belong to?"Can you see what each building costs to run right now?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes behind invisible building costs
The data usually exists. It is recorded at the wrong level, or too late, to answer a question about one building.
The property is not captured at purchase
If the request or PO does not name the building, AP has to guess later, and guesses default to whatever account is easiest.
Portfolio contracts produce shared invoices
Janitorial, security and maintenance vendors often bill several buildings on one invoice, with no split rule agreed in the contract.
Spend flows through side channels
Card purchases, emergency repairs and expense claims skip the PO process, so they arrive with no building reference at all.
Vendor records are duplicated
One supplier set up three times by three sites splits the spend, so nobody sees the real total or which buildings it serves.
The chart of accounts describes what, not where
Accounts track the type of cost well. The property dimension is missing, optional or applied differently by each site.
Building reports are assembled by hand
When building views come from spreadsheets rebuilt each quarter, nobody looks until someone asks, usually at year-end.
What a blind spot on building costs costs you
Building operations are one of the largest recurring outlays in commercial real estate, so small visibility gaps compound.
The direct cost is overspend nobody catches in time: a building running over budget for nine months before anyone asks why, or a vendor billing two properties for one visit. The indirect costs are wider: CAM reconciliations that under-recover because costs sat on the wrong property, weaker owner reports, slower budget cycles, and hold or sell decisions made on portfolio averages instead of real building numbers.
Estimate the spend you cannot act on today
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices for building-level cost visibility
Start with the coding rules, then the vendors, then the reports. Each step works in a spreadsheet first, and gets faster once it is built into the purchase process.
"The best of breed market pushes 15 to 20 tools onto one vendor relationship, and property companies add another layer, because each building picks its own. Then the CFO asks which property costs the most and nobody can answer without a month of spreadsheets. Visibility is not a reporting project. It starts when the building is named on the request, because that is the easiest moment to get it right."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Make the building a required field on every purchase
Agree split rules for shared contracts
Clean and merge vendor records
Bring side-channel spend into the same coding
Report cost per square foot by building every month
Investigate the top outliers each month
"At Voonik we had 5,000 to 6,000 suppliers emailing invoices into one inbox. The invoices that caused trouble were the ones that arrived without saying what they were for. A shared facility invoice with no building on it is the same problem. Put the property on the PO, ask the supplier to repeat it on the invoice, and the reporting mostly takes care of itself."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro gives each building its own spend picture
Zapro captures the building at the request, carries it through the purchase order and the invoice, and reports spend by location, vendor and category, so the view builds during the month instead of after the year.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Property not captured at purchase | Procurement: purchase requests and Prompt to buy with Z1 | Requests carry the building and budget from the start, and Z1 drafts them from a plain language description. |
| Shared and uncoded invoices | AP Automation with data extraction and PO matching | Invoices are captured, data is extracted and each invoice is matched to a PO that already carries the building. |
| Duplicate vendor records | Vendor Management: centralized vendor profiles | One profile per vendor across the portfolio, with documents and performance history in one place. |
| Reports assembled by hand | Spend Analytics | Spend by vendor, category and location, with budget tracking, in dashboards that update as transactions happen. |
| Ledger and building codes out of sync | ERP and accounting integration | Two-way sync of vendor and master data keeps legal entities and accounts aligned with your ledger. |
Most teams start by mapping each building to its ledger code and budget, then connect their ERP or accounting system so master data and payment status stay in sync. See Zapro integrations.
A 30, 60, 90 day plan
Days 1 to 30: Map it
- List every building with ledger code and square feet
- Pull 12 months of invoices and card spend
- Tag spend by building and flag untagged lines
- Find the vendors sending shared invoices
Days 31 to 60: Code it
- Make building required on requests and POs
- Agree split rules with shared vendors
- Merge duplicate vendor records
- Code card and emergency spend by building
Days 61 to 90: Use it
- Publish monthly building cost reports
- Review the two biggest outliers each month
- Feed building costs into budgets and owner reports
- Push untagged spend toward zero
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| Building-tagged spend | Facility spend recorded against a specific building divided by total facility spend | Monthly |
| Operating cost per square foot | Facility spend by building divided by rentable square feet | Monthly, by building |
| Budget variance by building | Actual facility spend minus budget, year to date | Monthly, by building |
| PO coverage | Facility invoices backed by a PO with a building code | Monthly |
| Shared invoices split by rule | Shared invoices allocated by an agreed rule divided by all shared invoices | Monthly in AP |
| Time to building report | Working days from month-end to published building cost reports | Monthly |
Go deeper with our guide to procure-to-pay process.
What a Zapro customer saw after moving this work into one workflow
"Implementing Zapro improved our vendor coordination significantly, leading to a substantial reduction in costs and faster vendor onboarding."Akhil Sikri, CTO, Zolo
Why Zapro for this challenge
Building-level visibility is a data capture problem, not a reporting problem. Zapro records the building where the purchase starts and keeps it attached through approval, PO, invoice and report, so each property's cost is visible during the year rather than after it.
The building travels with the transaction
Requests, POs and invoices share one record, so the property code is set once and reused at every step.
Z1 does the matching
Zapro's AI layer reads requests, matches invoices and flags risk, so AP is not splitting and chasing invoices by hand.
One vendor across many properties
Centralized vendor profiles stop the same supplier appearing five times under five buildings.
Unlimited users on every plan
Every property manager can raise requests and work in the system without per-seat costs, with role-based access to what they should see.
When Zapro may not be the right fit
- You own a single building or a small portfolio run from one set of books. Clear account codes and a monthly report may be enough.
- A third-party property manager handles all purchasing and already gives you building-level reports you trust.
- You need full property accounting, rent rolls and tenant billing. Zapro handles procurement, vendors, contracts, AP and spend analytics, and connects to your property accounting system.
Frequently asked questions
How should facility costs be allocated across buildings?
Direct costs should be coded to the building that incurred them at the point of purchase. Shared costs, such as a portfolio janitorial contract or a regional maintenance team, need an agreed allocation basis like square feet, visits or fixed shares. Set the rule before the invoice arrives rather than deciding it each month.
What is a good way to compare costs between buildings?
Normalize by size. Operating cost per square foot, split by category such as cleaning, repairs, security and utilities, lets you compare properties of different sizes and spot outliers. Compare similar building types with each other rather than across the whole portfolio.
Why do we only see building costs at year-end?
Usually because the building is not captured when the purchase is made. Finance then has to reconstruct it during close or audit, which takes enough time that it only happens once a year. Capturing the property on the request fixes the timing.
Does building-level visibility help with CAM reconciliation?
Yes. When costs are tagged to the right property through the year, recoverable expenses are easier to support and less likely to be missed at reconciliation. It also shortens the back and forth with tenants who question a charge.
Can we get building-level spend without new software?
Partly. A required building code on requests, split rules for shared vendors and a monthly spreadsheet report will get a small portfolio most of the way. Software helps when you have many buildings and vendors and AP is splitting invoices by hand. Zapro captures the building at the request and reports spend by location without the spreadsheet step.
About the experts behind this page
Sources
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.