Check that a service report and invoice refer to the same work by comparing a defined set of identifiers across both documents and the authoritative job record. A shared customer name is insufficient when that customer operates several sites. The useful output is a comparison with source references and explicit unresolved differences.
Before adding software, inspect the matching and document-linking functions in the current job system. A reliable site code carried from job creation through billing may remove much of the ambiguity. A custom review step becomes relevant when external reports or customer references cannot be consistently linked through the existing process.
Compare identity in layers
Fictional Fenwick Services maintains equipment for Rowan Retail. Job J-713 concerns store RR-014 on Market Street. The service report says “Rowan, Market St,” while the invoice says “Rowan Retail head office.” The invoice's billing address may be correct, but it does not establish which service site the charges concern.
| Identity field | Job record | Service report | Draft invoice |
|---|---|---|---|
| Customer account | C-031 | Rowan Retail | C-031 |
| Service site | RR-014 | Market St | Not stated |
| Job reference | J-713 | J713 | J-713 |
| Visit date | 8 October | 8 October | 8 October |
The next action is to confirm the invoice's required site reference, not to replace its billing address automatically. Treat bill-to entity, service location, and correspondence address as separate fields. Similar words can describe different roles.
Normalize only agreed differences
Removing spaces or a known separator from J-713 may be safe if the business confirms that the format is equivalent. Removing leading zeros from site RR-014 may not be safe. Preserve every original value beside its normalized version, and record the rule that produced the comparison.
Use an approved site-alias table for names such as “Market Street Store” and “RR-014.” An alias should have an owner and supporting evidence. If “Market Street” maps to two sites, the result is ambiguous. A high text similarity score cannot supply the missing identity.
Show the reviewer the disagreement
Each comparison should include the document name, version, page or field, extracted value, and proposed interpretation. Microsoft documents that extraction confidence varies by prediction type and model. Confidence can help prioritize review, but it cannot prove that two similarly named sites are the same place.
For Fenwick, a reviewer may confirm that the missing site code should be added to the draft invoice. Record that correction against the invoice version. If the report instead names RR-041, hold the pack and ask the job owner to resolve it. Do not silently prefer whichever document was uploaded last.
Distinguish absence from contradiction
- Missing: the invoice does not state the service site.
- Conflicting: the report identifies a different site from the job.
- Ambiguous: the site name matches several approved records.
- Unreadable: the relevant text cannot be reliably extracted.
- Matched: the agreed identifiers align on the reviewed versions.
These states determine the follow-up. Missing information may need an amended draft. A contradiction may indicate the wrong attachment. Unreadable text may require the original file. Keeping them separate helps staff avoid unnecessary customer contact.
Keep historical site names as dated aliases where the business approves them. A report written before a site rename may be correct, while the same old label on a new visit may need clarification. The visit date helps staff interpret that difference.
Pilot against difficult pairs
Build a test set with multiple sites for one customer, repeated visits, changed site names, similar job numbers, and reports attached to the wrong invoice. Label the correct result before testing. Include genuine matches with harmless formatting differences so the checker is not rewarded for flagging everything.
Measure incorrect matches, unresolved cases, and review time per invoice. For Fenwick, include the customer's agreed site-reference requirement and the approved alias table in the pilot so reviewers can explain each result. Clear Anvil's invoice evidence approach keeps the result at staff-review level, with traceable comparisons rather than automatic billing decisions.
Sources and further reading
- Johnson Controls North America invoice submission requirements
- Microsoft Document Intelligence confidence guidance
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.