Solution

How to Track Vendor Spend by Building and Asset

The owner wants spend visibility without losing maintenance context.

Spend needs operational context

A vendor spend total is useful, but it does not explain which building systems consumed that spend.

Asset-level spend helps distinguish normal maintenance from recurring issues.

QuickBooks or another accounting system remains the financial source of truth. Steward should preserve maintenance context around the same invoices.

The goal is not to replace accounting; it is to add building memory.

High spend on one asset should trigger review. Low spend on a critical system may also be a warning if it means no service records exist.

The packet should surface both patterns.

Use this as the next-action pass before opening a spreadsheet, forwarding another invoice, or generating a packet.

Group by building.

Group by asset and category.

Keep vendor totals visible.

Preserve source invoices for each amount.

Steward spend views are operational and should be reconciled with accounting records where financial precision matters.