Service Invoice
An invoice for maintenance and facilities work, written for maintenance contractors and in-house facilities teams who have to get it reconciled rather than just sent. Every line references a work order and says whether it is covered by the contract, chargeable, or warranty work you are not charging for at all.
- One line per work order, marked contract, chargeable or warranty
- A purchase order field, the commonest reason an invoice is rejected
- Service credits deducted here rather than credited next month
- Retention held and released, with its conditions on the invoice
Service Invoice
Built to be reconciled
| # | WORK ORDERS ON THIS INVOICE | COVERED | NET | REF |
|---|---|---|---|---|
| 1 | WO-1204, gutter joint repair, bay 3 north, chargeable | |||
| 2 | WO-1211, quarterly air handling unit service, contract | |||
| 3 | WO-1218, actuator replaced under warranty, not charged |
The document you will get. Download for the full, editable file.
Who this service invoice is for
One invoice, and three people who each need it to answer something different.
The maintenance contractor raising it
Your interest is getting paid without a query. The work order references and the acceptance section are what move an invoice out of the queue and into the payment run.
The in-house facilities team
You raise these against departments or recharge tenants. The contract and chargeable split is what makes a recharge defensible when somebody asks why they are being billed.
Whoever approves payment
You are checking that the work was accepted, that it was not already covered by the contract, and that the purchase order matches. Three checks, all of them on this page.
Finance or the budget holder
Retention, credits and the undisputed release. These are the lines that decide what actually leaves the account this month rather than what was billed.
Where the split matters most
The structure suits any maintenance billing. What changes is who is being charged and how hard the checking is. If you run one of these, the sector page goes further than the template does.
- FM service providers
Contracted delivery, where the contract and chargeable split is checked line by line before anything is approved.
FM service provider software - Commercial real estate
Recharging tenants through the service charge, where an unexplained line becomes a dispute at certification.
Portfolio maintenance software - Retail and malls
Many small invoices across many sites, where the purchase order is the only thing tying a job to a store.
Retail maintenance software - Corporate facilities
Departmental recharge, where the person approving payment did not raise the job and needs the work order to check it.
Corporate facilities software - Healthcare
Estates billing with strict authorization trails, where acceptance has to be evidenced before payment is released.
Healthcare maintenance software - Education
Term-time work billed against project codes, where the budget reference matters as much as the amount.
Campus maintenance software
What a maintenance service invoice should contain
A service invoice for maintenance work is a bill built to be checked, with every line traced to the work order that produced it. It records the purchase order and who accepted the work, splits lines into contract, chargeable and warranty, itemizes labor, parts and other charges, then deducts credits and retention to reach what is due.
A. The sections that carry the weight
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Invoice details | Number, dates, the period covered, and both parties | Ordinary, with one exception. The site or property the work relates to is what lets a multi-site client route the invoice at all. |
| Purchase order number | The PO this work was raised against | The single commonest reason a facilities invoice is rejected, and it is rejected before anybody reads the figures. A missing PO costs a full payment cycle. |
| The authorization it relies on | Who accepted the work on site, when, and the completion reference | An invoice sent before the work has been accepted goes into a query queue. Fill this in from the completion paperwork, not from the job sheet. |
| Work orders on this invoice | One row per work order with date, site, description and net amount | The heart of it. A client can check a line against their own records, which is the entire difference between an invoice and a request for money. |
| Covered by | Contract, chargeable or warranty, spelled exactly | Counted by the summary. Showing warranty work at zero is worth doing rather than omitting it, because it proves the job was done and not billed. |
| Labor | Date, technician, trade, hours and rate | Itemized so a rate query is about one line rather than the whole invoice. The trade matters because rates usually differ by it. |
| Parts and materials | Part number, description, quantity, unit price and work order | Each part referenced back to its work order, which is what stops parts drifting onto an invoice that had no job to fit them to. |
| Other charges | Callout, out of hours uplift, access equipment, waste, subcontractor, permits | The lines most often disputed, because they are the ones a client did not expect. Naming the basis for each is what prevents that. |
| The deduction chain | Gross, less contract and warranty, less credits, less retention | In that order, on the invoice. Every step is a deduction somebody could otherwise argue should have happened somewhere else. |
| Service credits due under the SLA | Deducted here rather than credited later | A credit note next month is one somebody has to chase and the commonest reason an invoice is queried rather than paid. |
| Retention | The percentage held, the amount, and when it is released | Money the contractor will not see for months, so the release date and its conditions belong on the invoice that created it. |
| Queries and approval to pay | What is disputed, its value, and the undisputed amount released | The section that keeps a relationship intact. One disputed line should not hold an entire invoice. |
Two fields decide whether an invoice is paid on time, and neither of them is a number. The first is the purchase order. A facilities invoice arriving without a PO, or with one that does not match, is usually rejected by a finance system before a human reads it, which costs a full payment cycle and generates a chase that nobody needed. The second is the acceptance record: who signed the work off on site, when, and against which completion reference. An invoice raised from a job sheet rather than from accepted completion paperwork is an invoice that will sit in a query queue while somebody establishes whether the work actually finished. Both are trivial to capture at the time and close to impossible to reconstruct three weeks later, which is exactly when they are asked for. The third habit, less obvious, is listing warranty work at zero rather than leaving it off. It costs nothing and it demonstrates that the job was attended and deliberately not charged, which is a far better position than silence when a client asks why they cannot see it.
B. What it looks like filled in
The deduction chain on one invoice covering four work orders. The gross figure is the one nobody argues about and the last four lines are where invoices actually get delayed.
| Line | Amount |
|---|---|
| Gross total | 531.20 |
| Less work covered by contract or warranty | 0.00 |
| Less service credits due under the SLA | 0.00 |
| Less retention held at 5% | 26.56 |
| Subtotal | 504.64 |
| Total due, with tax at 20% | 605.57 |
Two of these lines are zero this month and both still belong on the invoice. The credits line reads zero because the provider met the SLA, and its value is its position: on the invoice, above retention, deducted before the total. Move it to a credit note next month and it becomes something the client has to chase and the contractor has to remember, which is the most common reason a maintenance invoice is queried rather than paid. The contract and warranty line works the same way. Showing it at zero says the work on this invoice was genuinely chargeable, where leaving it off says nothing and invites the question. Retention is the line with real money in it. Twenty-six fifty-six on five hundred is not large, but it is money the contractor will not see until the release conditions are met, which is why the release date belongs on the invoice that created the deduction rather than in a contract nobody reopens.
Word for a version to put on your own letterhead, Excel for the one that totals labor, parts and other charges and works the deduction chain down to what is due, with an Invoice Register tracking status, queries and payment, and PDF for issuing. Free, and yours to rebrand.
How do you raise a service invoice that gets paid?
Raise it from the completion paperwork rather than from the job sheet, and fill the two fields that decide whether it gets paid before you touch the figures. Six steps.
Get the purchase order and the site right first
The PO this work was raised against, and the site or property it relates to. A missing or mismatched PO gets the invoice rejected by a finance system before anybody reads a single figure.
Record what authorized it
Who accepted the work on site, the date, and the completion or acceptance reference, plus any quotation or variation references. Take these from the completion paperwork, not the job sheet.
List one line per work order
Number, date, site or area, description and net amount. This is what makes the invoice checkable against the client's own records, and it is what a single summary line destroys.
Mark every line contract, chargeable or warranty
Spelled exactly, because the summary counts them. Include warranty lines at zero rather than leaving them off, so the work shows as done and deliberately not charged.
Itemize labor, parts and other charges
Hours and rate by trade, parts against their work order, and each other charge with its basis. Callouts, out of hours uplifts and access equipment are the lines clients query most.
Work the deduction chain, then set the payment terms
Gross, less contract and warranty, less any SLA credits, less retention, then tax. Put the retention release date on the invoice, and if a query arrives, release the undisputed portion.
One line per work order versus a single summary line
The same month's work, billed two ways. One of them can be checked by the person approving it and the other can only be believed or queried.
| Aspect | One line per work order | A single summary line |
|---|---|---|
| What the approver can do | Check each line against their records | Believe it, or query the whole invoice |
| What a dispute is about | One line and its value | The entire invoice |
| Contract and chargeable work | Separated and countable | Blended into one figure |
| Warranty work | Shown at zero, visibly not charged | Invisible, so it looks omitted |
| Time to approve | Fast, because checking is mechanical | Slow, because it needs a conversation |
| What happens on a query | The rest is released and paid | Everything waits |
A summary line is faster to write and slower to get paid, and the gap is usually measured in weeks. The person approving a facilities invoice is rarely the person who raised the job, so their only route to confidence is matching what they are being billed for against what they have a record of. One line per work order makes that mechanical. A line reading maintenance services for the period makes it a conversation, and conversations queue. The same logic drives releasing the undisputed portion when a query does arrive: the disputed line is almost never the whole invoice, and holding the rest hostage to it converts a routine question into a payment dispute that neither side wanted.
When the template starts to feel limiting
The file is built to raise one invoice at a time from paperwork somebody else produced. Four things start to hurt as soon as the volume rises.
Every figure is retyped from somewhere else
Hours, parts and costs already exist against the work orders. Typing them into an invoice is both the effort and where the discrepancies that cause queries come from.
Nothing checks the work was actually accepted
The acceptance fields are free text. An invoice can be raised against a job that was never signed off, and the first thing to notice will be the client.
Retention release depends on memory
The release date sits in a cell on an invoice raised months ago. Nothing reopens it, and unreleased retention is money that quietly stays unclaimed.
The register is only as current as the last update
Status, queries and payment are maintained by hand, so the answer to what is outstanding is always slightly behind what is actually outstanding.
What running this in Facilio looks like
The invoice does not change. What changes is that it is built from the work rather than transcribed alongside it.
Work Order Intelligence
Lines come from the jobs
Hours, parts and costs carry from the work orders themselves, so the invoice matches what was done without anybody retyping it into a spreadsheet.
Audit Report Intelligence
Acceptance is evidenced, not asserted
The completion record sits behind the line, so an invoice cannot be raised against work nobody signed off and a query is answered with the record.
Ops Performance Intelligence
Retention and credits surface on time
Release dates and any SLA credits are held against the contract, so a deduction is applied when it is due rather than when somebody remembers it.
Asset Intelligence
Recharge is defensible
Because each line traces to an asset and a site, a departmental or tenant recharge can be explained from the record instead of from the invoice alone.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a service invoice?
A service invoice bills for work carried out rather than for goods supplied. This one is written for maintenance and facilities work, so every line references the work order that produced it and states whether it is covered by the contract, chargeable, or warranty work being shown at zero.
It also carries the things a general invoice template does not: the purchase order, who accepted the work on site, service credits, retention, and a section for releasing the undisputed portion when a line is queried.
Why does every line need a work order reference?
Because the person approving payment is usually not the person who raised the job. A work order number is the only thing that lets them check what they are being billed for against their own records.
A single line reading maintenance services for the period cannot be checked at all, which means it can only be believed or queried. Queries queue, and the invoice waits.
Why is the purchase order so important?
Because a missing or mismatched PO gets a facilities invoice rejected before anybody reads the figures, usually automatically. It is the commonest reason an invoice bounces and it costs a full payment cycle each time.
It takes seconds to capture when the work is raised and is often impossible to reconstruct weeks later, which is exactly when finance asks for it.
Should service credits be deducted on the invoice?
Yes. Deducting them on the invoice that triggered them is far better than issuing a credit note the following month, because a credit note is something the client has to chase and the contractor has to remember.
It is also one of the commonest reasons a maintenance invoice is queried rather than paid, since a client who is expecting a credit and cannot see one will hold the invoice until somebody explains.
What should happen when part of an invoice is disputed?
Release the undisputed portion and settle the query on the disputed lines separately. The template has a section for exactly this: what is queried, its value, and the amount released for payment.
Holding a whole invoice over one line is how a working contractor relationship turns into a payment dispute, and the disputed value is almost never the majority of the invoice.
What is the difference between this and a work order completion report?
A completion report records what was done on a job: the work carried out, parts fitted, time taken and sign-off. It is the evidence that the job finished.
This invoice bills for it. The two are deliberately separate, and this template asks for the completion reference rather than repeating its detail, because an invoice that tries to double as a completion record satisfies neither reader.
Can in-house facilities teams use this, or is it only for contractors?
Both, and the in-house case is common. Teams use it to recharge departments, to bill tenants through a service charge, or to show a cost center what its requests actually cost.
The contract and chargeable split is what makes an internal recharge defensible, because it separates work already covered by an existing budget from work genuinely being charged on.
Where does the price get agreed in the first place?
Not here. This template invoices work that was already authorized, and it asks for the quotation or proposal reference and any agreed variations rather than setting a price.
If you need to price work before it is approved, that is a work order proposal. Invoicing against a proposal reference is also the single easiest way to avoid a pricing dispute at payment.
In one paragraph
A maintenance service invoice is a bill built to be checked. Capture the purchase order and the acceptance record before the figures, because those two fields decide whether it is paid or bounced. List one line per work order marked contract, chargeable or warranty, and show warranty work at zero rather than leaving it off. Deduct SLA credits and retention on the invoice itself, and if a line is queried, release the rest.
The invoice is the floor, not the ceiling
Raise it from the completion paperwork, keep one line per work order and put the retention release date on it. Once figures are being retyped from work orders every month, or retention is going unclaimed, the spreadsheet has done its job.
