Datacat

Insights

2026-10-19 · 6 min

Contractor invoices that match the work — pay only for proven visits

Invoices with no job number, callout fees for visits nobody saw, the same repair billed twice. How multi-site teams pay contractors only for proven work.

Accounts payable has a pile of contractor invoices waiting for sign-off. One says "Attended site, investigated fault, 3 hrs" with no job number. Another charges a callout for a leaking tap the site manager swears was fixed by the cleaner. A third looks familiar, because the same repair at the same site was paid a few weeks ago under a different invoice number.

Someone forwards each one to the site manager, who is busy, who approves most of them so the contractor keeps turning up. Finance closes the books. Nobody can say how much of that spend bought finished work.

This is not a dishonest-contractor problem. Most of your usual contractors bill fairly. It is a matching problem: the invoice arrives in one place, the job lived in another, and the proof, if it exists, is in someone's phone.

Where contractor spend leaks

  • Invoices arrive without a job. No work order number, a vague site name, a description that could cover anything. Matching it to real work takes a phone call, so it usually gets approved instead.
  • Variations happen on site and get billed later. The contractor finds extra work, does it, and the first you hear about it is a bigger invoice. Nobody agreed the extra before the tools came out.
  • Callouts get paid for visits nobody confirmed. A no-access visit, a job closed over the phone, or a visit that never happened all look the same on an invoice.
  • The same work gets billed twice. Two sites raise the same fault, or one invoice gets resubmitted after a query, and both get paid because nobody sees them side by side.
  • Approval sits with the wrong person. A site manager signs off a five-figure repair because it landed in their inbox, while a small recurring overcharge across thirty sites never gets looked at.

What matched contractor invoices look like

Paying contractors properly is not about more scrutiny once invoices have piled up. It is about making sure every invoice lands against a job that already shows what was done, so approval is a check rather than an investigation.

No job, no invoice. Every piece of contractor work starts as a work order with a number, a site, a trade and an expected cost. The invoice attaches to that job, not to an inbox.

Extra work gets approved before it gets done. If a contractor finds more on site, they raise the variation against the job with photos and a price. Someone with the right limit says yes or no then and there, and the invoice can only include what was approved, following the same rules as approvals that don't die in email.

Proof comes before payment. The job is closed out with photos, readings, sign-off and any certificates before the invoice is approved. That is the same work-order proof leadership can trust, pointed at accounts payable instead of the board pack.

Invoices are checked against the job automatically. Amount against quote or approved limit, callout against a confirmed attendance, site and trade against the work order. Anything that does not line up gets flagged with the reason, and everything that does gets through quickly, so good contractors are paid on time.

Duplicates show up before they are paid. Same site, same asset, same fault, similar amount within a few weeks, shown together in one place rather than discovered in an audit.

Approval goes to the right person by amount and type. Small, matched, routine invoices clear without a manager touching them. Large or unmatched ones go to someone who can actually judge them, with the job history in front of them.

Spend is visible by site and contractor. A running view of what each site spent, with which contractor, on what kind of work, tells you where to renegotiate and where a quote from outside your list would have been cheaper.

Signals your invoices are running the show

  • More than a handful of invoices each month need a phone call before anyone knows what they were for.
  • Variations are discovered on the invoice, not approved before the work.
  • Accounts payable cannot tell a paid callout with a fix from a paid callout with no access.
  • Site managers approve contractor invoices to keep the relationship smooth, not because they checked them.
  • You found a duplicate payment in the last year and are not sure it was the only one.

One of those happens to everyone. Three or more means you are paying for work you cannot see.

What accounts payable sees once invoices match the job

  • Every invoice belongs to a work order, so matching takes seconds instead of a phone call.
  • Variations are agreed before the work, so invoices stop surprising anyone.
  • Callouts are paid against confirmed attendance and proof, not a line on a page.
  • Duplicates get caught before payment rather than after an audit.
  • Your usual contractors get paid faster for clean invoices, which keeps the good ones keen to take your jobs first.

OpsChase handles the work-order side of this for multi-site operators. Each job is offered to your usual contractors before anyone new, overdue attendance raises a reminder and then an escalation, and the work order stays open until the photos, readings and sign-off your template asks for are uploaded. Contractors confirm, attend, upload proof and invoice through one portal, so every invoice lands against a proven job, and spend rolls up by site across your whole portfolio. See how invoices land against proven jobs on the OpsChase product page.

Need contractor invoices matched into your finance system, approval limits by role, or spend reporting across a larger property or CRM setup? We build preferred contractor and work order systems, vendor and contractor portals, and ops workflow automation that tie every contractor invoice back to work your sites can prove. If you want to see delivery first, browse selected work. If the invoice problem is not scoped yet, start with paid strategy and discovery, or talk to Datacat about your invoice path.