Key takeaways
- Define invoice exceptions before counting them.
- Preserve approved scope and completion evidence as separate sources.
- Report unresolved records instead of silently excluding them.
Source record
3 cited sources
Last verified
2026-09-14
Maintenance invoice review produces useful operational evidence only when the team can reproduce why a charge matched or failed. This framework treats approval, completion, and billing as separate records linked by a stable work-order identifier.
Research question
Which documented differences most often prevent a maintenance invoice from matching the last approved work scope and completion record?
Methodology
Define an eligible record as an invoice tied to a closed or payment-ready rental maintenance work order during a stated review period. Before examining outcomes, publish an exception codebook covering missing approval, amount variance, unapproved scope, duplicate invoice, missing completion evidence, property mismatch, service-period mismatch, and unresolved tax or fee treatment.
Join invoice lines to the last approved scope and completion record. Two reviewers independently classify a sample, compare disagreements, and revise ambiguous instructions before the full review. Preserve the original value, normalized value, decision, reviewer, and decision time. Report the eligible population, excluded records, exception counts, and unresolved counts.
Evidence
The IRS recordkeeping guidance describes the general role of supporting business records. NIST data integrity guidance supplies a definition for guarding against improper modification. The GAO Green Book provides a public internal-control reference. These sources support the record design, not a claim about any portfolio's exception rate.
Source treatment
Retain source documents in their controlled systems and store references in the research table. Record retrieval time and version. Treat vendor descriptions as claims that require comparison with approval and completion evidence. Do not convert missing records into zero values. Remove unnecessary resident information from the analysis copy.
Limitations
Coding quality depends on consistent work-order identifiers and preserved approval versions. One portfolio's contract terms, vendor mix, and maintenance categories may not transfer to another. A documented mismatch does not by itself prove overbilling, poor workmanship, or legal liability. The framework measures record agreement, not repair quality.
Interpretation
Use the findings to locate workflow gaps and choose records for qualified review. Report counts and denominators together. Keep unresolved classifications visible until evidence or an authorized decision closes them.