Unpaid Contractor and Maintenance Invoices: Preparing Your Claim
Connect project instructions, completed work and the outstanding amount.
An unpaid contractor or maintenance invoice can involve more than a late transfer. The customer may question completion, approval, variations or a particular charge. Preparing the claim means connecting the work that was agreed to the work recorded as performed, then showing how the outstanding amount was calculated. This guide focuses on that project-file task. It does not assume that an invoice, certificate or photograph alone settles every dispute about the work.
Identify the agreed scope and payment basis
Gather the contract, quotation, purchase order and any relevant work order. Describe the site, service period and agreed deliverables. Check whether payment relates to a visit, a completed milestone or a wider package of work. Include any agreed approval requirements in the summary. If the invoice description is broader than the original scope, flag the difference for review rather than treating the invoice wording as the agreement itself.
Build a work-order chronology
Create a dated list of instructions, attendance, submitted work and follow-up. Link each entry to a work order or project reference. For maintenance, distinguish routine visits from additional call-outs. For contracting work, identify the milestone or package concerned. Record who instructed the work and who received the report. Where dates differ between internal records and customer correspondence, note the discrepancy so it can be checked before the claim is presented.
Organise completion and delivery records
Keep site reports, completion certificates, inspection notes, relevant photographs and submitted deliverables together. Explain what each record shows and which invoice it relates to. A photograph may illustrate work but leave questions about date, location or scope. Preserve original files where available. If the customer reported defects or requested further work, include that correspondence and the response. A balanced file should make outstanding questions visible rather than conceal them under a large attachment bundle.
Trace approvals to the relevant work
Identify the approval process described in the agreement and the records actually available. Keep signed approvals, emails and other relevant exchanges in context. Distinguish an operational instruction from approval of a price or final completion. If a person’s authority is uncertain, flag it. A site contact’s acknowledgement and a finance department’s payment approval may address different issues. Do not assume that one record answers every question about the work and the amount.
Separate variations and additional work
Prepare a schedule showing the original scope and each claimed addition. Include the instruction, quotation, response, performance record and corresponding charge where available. Mark disputed or undocumented changes clearly. A verbal request should be described honestly, with whatever contemporaneous records exist. Avoid recreating an approval after the event. Separating additions helps the reviewer understand whether the dispute concerns the whole contract or only particular items of additional work.
Reconcile invoices, deductions and payments
Match invoices to the work schedule, include relevant payment applications and identify any retention or deduction recorded in the agreement. Show payments, credit notes and the remaining balance. Explain customer adjustments separately from adjustments your company accepts. Do not simply carry an old ledger total into the claim if later payments or corrections have changed it. A transparent calculation allows the reviewer to focus on the substantive questions instead of rebuilding the account.
Prepare a clear dispute summary
List the customer’s objections using their actual wording where helpful, then point to the records relevant to each point. Identify any rectification undertaken and issues still open. Keep commercial negotiations distinct from technical explanations. Contractor receivables support can help review project records and suitable follow-up. The assessment should consider the documents, the nature of the dispute and the engagement scope rather than promise a fixed recovery result.
Hypothetical example
Imagine a maintenance company claiming for routine servicing and an additional repair. Its service reports support the scheduled visits, while correspondence shows a disagreement about the repair price. The company separates the repair charge, includes the relevant messages and reconciles a partial payment. That preparation helps define the questions for review; it does not guarantee that either part of the claim will be recovered. This example is hypothetical.
Frequently asked questions
Is a completion certificate always enough?
No single record answers every issue. Review it with the agreement, scope, invoices and any objections.
What if extra work was requested verbally?
Identify the missing approval and preserve available contemporaneous records. Seek case-specific review rather than creating a retrospective document.
Where do we submit the file?
Use the business debt claim form with an organised summary and relevant supporting documents.
Further reading: Documents Needed to Assess a Business Debt Claim; Amicable Collection or Legal Action: Choosing the Next Step.
This content is general information, not advice for a particular matter. Each claim depends on its documents and circumstances. No recovery outcome is guaranteed, and submitting a form does not create a professional engagement. Scope and fees must be agreed for the particular instruction.