Match vendor invoices to the work actually completed

An invoice can name the right property, come from the right vendor, and still be difficult to approve. Perhaps it includes an extra visit. Perhaps the job covered several units. Or the original approval allowed an inspection while the invoice describes a completed repair.

The useful automation is a comparison that makes those differences obvious. Matching a vendor name and total is too shallow for service work. You need the authorized scope, the work actually accepted, and the charges submitted against it.

This guide covers that evidence check. The separate invoice approval guide covers routing and permissions, while the work-order guide explains how to create reliable upstream records.

Build the match around the job identifier

Ask vendors to include the work-order reference and property or unit reference on invoices. Keep their original invoice number too. Your internal identifier connects the operational records; the vendor's identifier helps track the financial document.

When a reference is missing, the system can propose a likely match using vendor, property, dates, and description. Label it as proposed. A similar invoice from last month is not enough to establish the current job.

Store the original document beside the extracted fields. If AI reads a quantity, rate, or date from a scan, the reviewer needs to see the relevant source rather than trust a clean-looking spreadsheet cell.

A matching record should carry:

Keep currency explicit. Do not compare two amounts merely because the number looks similar. Any conversion or tax treatment belongs in the organization's established finance process.

Adapt matching to service work

Microsoft's invoice matching documentation compares invoice, purchase-order, and receipt information, with configured tolerances for discrepancies. That provides a useful control pattern, but property service work needs its own evidence of receipt.

For a repair, the equivalent may be an accepted work record. For a recurring contracted service, it may be the service period and the required completion record. A photograph of a finished item might support the record, but it does not establish the agreed price or authorization for additional work.

Infor explicitly distinguishes service invoices matched to service purchase orders or contracts. Treat the contract and work-order terms as the starting point rather than forcing every job into a goods-received model.

Define which evidence is required for each service type. An initial diagnostic visit, a repair, and a scheduled routine service can have different acceptance conditions. The matching rule should know which kind of work was authorized.

Compare the lines before the totals

Two invoices can have the same total while charging for different work. Compare descriptions, quantities, rates, and additional charges against the approved scope. Then check the arithmetic and final total.

Here is a hypothetical example, with no tax included to keep the comparison simple:

The record shows a $120 discrepancy. It does not prove the invoice is wrong. The vendor may have performed approved additional work whose authorization hasn't been attached, or the completion record may be incomplete.

Send the reviewer a precise question: "Please confirm the additional hour and callout charge, or attach the scope variation." That is more useful than "Invoice mismatch" and less accusatory than automatically rejecting the vendor's work.

Keep arithmetic deterministic. AI may help map a line description to a work item, but multiplication, totals, and comparisons should use ordinary calculations with consistent rounding rules.

Track variations and partial billing across the job

An approved variation changes the authorized scope. Link it to the work order with its own decision record, then show which invoice lines use that approval.

Property Meld's documented approval response includes a recorded decision and comments. In your own workflow, retain enough detail to connect the decision to the particular work and amount under review.

Partial invoices need cumulative checks. A deposit, an interim bill, and a final bill may each look reasonable alone while exceeding the total agreement when combined. Record what each document covers and what remains to be billed.

For an illustrative $800 approved job, an initial $200 invoice followed by a $600 final invoice totals $800. If the final invoice instead states the full $800 without crediting the first payment or clarifying its treatment, the reviewer needs to resolve the document relationship. The system should not simply approve both because each is within an $800 ceiling.

Keep credits linked to the original invoice and job. A credit document should not disappear into a general vendor balance if the matching screen still claims the original job is fully charged.

Handle repeat visits and multiple properties explicitly

A second visit may be additional approved work, a return to complete the original scope, or a review of a recurring problem. Record which it is before assigning the cost. Don't infer warranty coverage or vendor responsibility from the visit number alone.

When one invoice covers several properties, allocate lines to the relevant jobs and units. Preserve any shared charge separately with the agreed allocation method. Do not duplicate the complete invoice amount across every linked property.

If an invoice description bundles work too broadly, route it for clarification. AI can suggest a breakdown only where the supporting records justify it. It should not invent a split that makes the totals fit.

These records later support vendor spend analysis. Consistent job and service categories make it possible to distinguish expensive individual work from repeated small charges that deserve investigation.

Keep duplicate checks conservative

Check the normalized vendor identity and invoice number, then compare amount, date, and document content. A re-sent PDF should point back to the existing document rather than create another payable record.

But do not use amount alone to reject a document. Recurring services may legitimately have identical totals, and some vendors use invoice numbering practices that require additional context.

Give possible duplicates a review state and preserve both source documents. Show why the system thinks they match. If a vendor sends a corrected version, retain the replacement relationship so reviewers know which version is current.

Keep payment details outside any model-driven update. A changed bank account or remittance instruction should follow the organization's established verification process; a matching result doesn't validate the destination of a payment.

Send a decision packet to the approver

The approver should see the invoice, current approved scope, completion evidence, previous billing, and a concise discrepancy list. If no differences are found, the packet should still expose the records used to reach that result.

Separate matching status from approval status. "Matched" means the defined comparisons passed. It does not mean the expense is correctly coded, the approver has authority, or payment should be released immediately.

Assign each unresolved discrepancy to a person: the maintenance coordinator for missing work evidence, the contract owner for scope questions, or finance for accounting treatment. Give the vendor one coherent clarification request rather than several conflicting messages from different teams.

This handoff is part of the wider operations workflow. Reliable work records reduce invoice reconstruction later.

Measure review effort and missed differences

Track how many invoices arrive with usable references, how often proposed matches need correction, and how much time reviewers spend collecting missing evidence. Sample invoices that passed automatically as well as the flagged ones.

Avoid treating a high match rate as the sole goal. A permissive rule can make the rate look excellent while overlooking added charges. A strict rule can create a queue of trivial rounding differences that hides more material questions.

For a pilot, compare the same service type over a defined period. Record review time, material discrepancies found, incorrect flags, and issues discovered after approval. Use those results to adjust the matching rules and vendor instructions before expanding to more complicated jobs.