A property manager hands you a dozen buildings scattered from the Energy Corridor to the ship channel. Over a month your crew clears maybe forty work orders across them, and you bill each one the day it closes, because that's how the office has always done it. Clean work, logged tight, out the door.
Then it lands on someone's desk in accounts payable, and the trouble starts. They're not looking at forty tidy jobs. They're looking at forty separate invoices, each one needing its own match to a purchase order, its own line in the system, its own approval click. A few sail through. The rest sit.
By the time you call about the ones that didn't pay, the answer is some mix of "that one's missing a PO," "this one got short-paid," and "that batch missed the approval cutoff, so it rolls to next month." None of it is about your work. It's about the shape of the paper, and you can fix the shape.
Why one statement clears when fourteen invoices stall
The person approving your money usually isn't the person who called you out. They manage a budget, not a boiler. When fourteen invoices show up, that's fourteen things to verify, route, and sign, and each one is a chance to get set aside for a question. A set-aside invoice is a late invoice.
One statement changes the math. It's a single document they can read top to bottom, check against the month's work orders, and approve in one pass. You're not asking for fourteen small yeses. You're asking for one.
What every line needs to stand on its own
A consolidated statement only works if each line answers its own questions. The approver has to tie every charge back to something they authorized, without picking up the phone. Four things do that, every time.
- Site: the building or address, named the way they name it, not the way your techs do.
- PO number: the purchase order that authorized the work. No PO, no match, no pay.
- Work-order number: your ticket, so a question about one line doesn't freeze the rest.
- Date of service: when the work happened, which is what the approval deadline runs against.
Add the dollar amount and a one-line description of what got done, and the approver has everything in a glance. "Rooftop unit 3, no cooling, replaced contactor." They don't need the whole story. They need enough to say yes.
Sort it the way they approve it
Order matters more than most owners expect. A statement dumped in the sequence the jobs happened to close makes the approver do the sorting, and work you hand someone else is work that waits.
Group by site first, then by PO within each site. That mirrors how a property manager thinks: building by building, budget by budget. Subtotal each site so they can check one building against their own records without adding up your lines by hand.
A clean statement has a simple spine:
- A header: your company, their company, the statement month, a statement number, and the total due.
- Each site as its own block, with the site name and a subtotal.
- Under each site, lines grouped by PO, oldest date first.
- A grand total that matches the sum of the site subtotals, so nothing looks fudged.
Flag the missing PO before the statement goes out
The single biggest reason a line gets short-paid or kicked back is a missing or wrong PO. A job your tech ran on a verbal okay, a blanket PO that ran dry mid-month, a number typed into the wrong field: any of these turns a clean line into a dispute.
Catch those in your office, before the statement leaves, not after it bounces. Run the month's work orders against your PO list and pull anything that doesn't match. For each one, you've got a short list of moves.
- A verbal okay with no PO: call your contact and get the number before you bill it.
- A blanket PO that's run dry: ask for a fresh one, or the overage gets denied.
- A number that doesn't fit their format: fix the typo against their PO list.
- A job nobody authorized: decide whether to eat it or chase approval, but don't bury it in the statement and hope.
One line with a question mark on it can hold up the whole statement while AP sorts it out. Better to pull it, fix it, and bill it clean next cycle than to stall the other thirty-nine good lines behind it.
Where software helps, and where it doesn't
Building this by hand once a month is doable. Building it for eight property accounts, each on its own billing cycle, is where the office starts dropping lines. This dull, repeatable sorting is something a computer is genuinely good at.
A simple setup pulls your closed work orders for the month, groups them by account and site, matches each to its PO, and flags the mismatches before anyone hits send. You still read the flagged list and make the calls. The software sorts and checks. It doesn't decide what to do about a missing PO, and it shouldn't.
Be straight about the limits. Software can't invent a PO that was never issued, and it can't tell you a verbal okay was actually authorized. If your work orders don't capture the site and PO at the time of the job, no month-end tool will add them cleanly later. That fix starts in the field, on the ticket. Wiring up the month-end sort is a short job, and it's the kind of thing we set up for Houston shops at AI Agency Houston.
Worth doing this week
You don't need new software to start. You need one account cleaned up by hand, so you can see the difference.
- Pick your biggest multi-site account and pull last month's work orders into one list.
- Check every line for a site, PO, work-order number, and date, and flag the gaps.
- Sort by site, then by PO, and subtotal each building.
- Call your contact on every flagged line before you send a thing.
- Send it as one statement, and ask the approver whether that's easier to sign off. Their answer tells you whether to make it your standard.