<img alt="" src="https://secure.perceptionastute7.com/784684.png" style="display:none;">

How to Stop Completed Field Service Jobs Going Unbilled

Unbilled jobs

The engineer has finished. The customer has their report. Accounts opens the job and finds an unanswered question: does the purchase order cover the extra work?

The job goes back to the office manager, who is dealing with today's bookings. By Friday, somebody has to ask the engineer what happened on Monday. The information existed; it never reached the person who needed to invoice it.

To stop work going unbilled, make the next billing action visible on each job. Identify when work becomes eligible for invoicing, check what is holding it up and confirm that each invoice reaches the intended accounting record and customer.

Find Where the Job Stopped

Separate work not yet invoiced from invoices already issued but unpaid. They need different action. Chasing a customer will not fix a bill that your office has never sent.

Research commissioned by the Department for Business and Trade and the Office of the Small Business Commissioner estimates that businesses are owed £26 billion in late payments at any given time. That estimate concerns late payments, not completed work waiting to be invoiced. The distinction matters when diagnosing your own cash-flow problem.

Keep overdue-payment chasing separate from the billing queue. For work still in that queue, find the missing approval, record, commercial decision or accounting handover.

man-in-work-van

How to Move Billable Work Through to Accounts

1. Separate Billing Status From Job Progress

Keep operational status and billing status separately understandable. An engineer can complete a visit while a contract remains open. A staged project can reach an agreed billing milestone before the whole project finishes.

Useful billing labels might include awaiting evidence, awaiting approval, ready to invoice, invoice created and invoice handover unresolved. Record customer delivery and payment separately. The labels can differ in your system; what matters is that people agree what each means.

Follow one representative job through the full field service process. Ask who takes the next action after the engineer submits the work. If the answer is “accounts usually notices”, assign an owner.

2. Check Readiness Against the Agreed Billing Basis

Set the invoice check around what you agreed to sell. For fixed-price work, verify the relevant scope or billing trigger and authorised variations against the agreed quote. For time-and-materials work, check the chargeable hours, materials and agreed rates. For milestones, confirm the evidence required by the contract.

Do not hold every fixed-price invoice until all internal costing is finished if the contract does not require that. Equally, an engineer pressing “complete” does not establish that every condition for billing has been met.

Your job sheet should capture the evidence finance needs without asking the engineer to make tax or commercial decisions outside their role. Any signature should state what it acknowledges. A site contact signing an attendance record may have no authority to approve extra charges.

Keep the approval and value of additional work connected to the job. A useful photograph supports the observation; it does not, by itself, authorise a variation.

3. Give Missing Information to the Right Person

Assign each hold to someone who can resolve it. The engineer can clarify work performed. The account contact may need to obtain a purchase order. Finance should decide the appropriate tax treatment and accounting codes.

Capture the bill-to legal entity, customer reference, required PO and recipient early. Confirm which customer rules apply rather than assuming the person who booked the visit is also the invoice recipient.

GOV.UK's invoice guidance sets out required information including an identifying number, supplier and customer details, supply and invoice dates, descriptions and amounts. Contract-specific fields such as a PO are a separate check, not a universal replacement for those requirements.

For the Republic of Ireland, use Revenue's VAT invoice guidance. Transaction-specific rules can differ. Agree the setup with your accountant rather than copying a UK tax code across all Irish work.

4. Verify What Happened in the Accounting System

Check that an invoice exists in the destination system before treating the accounting handover as complete. Retain a reference that connects the job, source invoice and accounting transaction.

An error message can leave you uncertain whether a record was created. Before retrying or manually raising another invoice, search the destination using the stable references and inspect the actual result. Matching customer and amount alone is insufficient where several jobs have the same price.

Follow the connector's documented recovery process. Do not assume a whole batch failed because one item was rejected, or that an accounting success means the invoice email reached the customer.

If you are switching software, include these exception cases in testing. A successful example invoice proves much less than a tested process for resolving an unknown result without duplicating a charge.

5. Deal With Exceptions Without Losing the Audit Trail

Give exceptions an owner and a recorded next action. The following table is an operational starting point, not accounting-system instructions or a universal deadline policy.

Exception

Next Check

Who Should Act

Required PO is missing.

Confirm the contractual requirement and obtain the reference; escalate a continuing hold rather than leaving it unnamed.

Account contact or office coordinator.

Transfer times out.

Check whether the destination transaction exists before an authorised retry.

Finance or the integration owner.

Part of a batch is rejected.

Identify individual successes and failures; correct and retry only through the supported process.

Finance.

Two records might be duplicates.

Compare source and destination identifiers, work covered and transaction states before deciding any correction.

Finance.

Authorised work was omitted.

Establish what has already been issued and follow the approved correction or additional-billing procedure.

Commercial owner and finance.

Invoice email fails.

Confirm the recipient and arrange controlled re-delivery without creating another invoice.

The person responsible for invoice delivery.

Preserve the original document and the reason for any correction. The appropriate treatment depends on the transaction's state, your accounting system and the relevant rules. “Delete and start again” is not a reliable correction policy.

HMRC's VAT record-keeping guidance explains the need for a complete record trail. This article concerns operational handovers; ask your accountant about invoice corrections, VAT timing and other transaction-specific treatment.

6. Reconcile the Same Work Across Both Systems

Compare a defined set of jobs or billing milestones with the invoices issued against them, then verify the accounting handover. Count unique invoices, not every attempt to send the same one.

Check values as well as counts. Two systems can each contain ten invoices while disagreeing about one customer's amount. Keep net, VAT and gross values distinct, compare the same currencies and explain legitimate timing differences.

For staged work, record the authorised value, amount billed to date and remaining amount eligible to bill. Do not assume one completed job should always have exactly one invoice.

Keep job costing alongside this review, but distinguish the questions. An accurately billed job can still make a loss. A profitable job on paper can still be waiting for its invoice.

vat-ireland

One Job With Two Different Billing Problems

Here is an illustrative example using amounts before VAT. A job includes £900 of agreed work and a £300 variation authorised by the appropriate customer contact. The engineer completes both, but the office raises an invoice for £900.

The accounting transfer then times out. There are now two separate issues: £300 of authorised work is absent from the invoice, and the office does not know whether the £900 transaction reached accounts.

Finance first checks the destination record. If it exists, another blind send could create a duplicate. The commercial owner also checks the variation approval, and finance decides how to correct or supplement what has already been issued using the approved procedure.

The job's authorised value is £1,200 before VAT. If £900 has been validly billed, £300 remains to be accounted for in the billing review. That difference should stay visible until resolved; closing the engineer's visit should not clear it.

A Daily Unbilled-Work Check

Review billing-ready work and unresolved handovers at a frequency that suits your volume, with a daily exception check as a practical starting point. A smaller operation may use a different routine, provided ownership and ageing remain visible.

For each item, keep the job or milestone reference, customer, eligibility date, authorised billable value, amount already billed, currency, reason for any hold, owner and next action. Add source and destination invoice references once created.

Suppose a hypothetical week's review identifies 40 billing-ready jobs and 36 validly invoiced jobs. The remaining four are 10% of that defined population. That is an example calculation, not a recommended threshold or proof of lost revenue.

Split those four by cause. A customer approval still pending needs different action from an invoice stuck after a transfer error. Report value and age too; one large unresolved milestone can matter more than several small invoices.

Measure billing-ready-to-invoice time separately from completion-to-invoice time. A legitimate scheduled billing date can explain a gap after completion. It should have a recorded reason rather than being hidden by a blended average.

Give Accounts a Job Record They Can Use

Fieldmotion brings job records, mobile forms, quotes and invoicing into the same platform. Your office can review information captured in the field rather than reconstructing the visit from separate messages.

Use a recent job to check your intended workflow: who confirms billing readiness, who creates the invoice, and how finance verifies its accounting destination. Confirm the connector's supported records and correction behaviour for your setup rather than assuming every status synchronises in both directions.

If you are still choosing tools, the invoicing software guide covers selection. Here, the useful test is narrower: can the next person find the evidence and finish their part of the handover?

man-using-laptop-in-office-Jul-06-2026-11-41-21-2133-AM

Questions About Unbilled Work

Should Every Completed Visit Be Invoiced Immediately?

No. Follow the agreed billing trigger, which may be a milestone, periodic contract charge or completed scope. Avoid unnecessary administrative delay once that trigger is met, and keep legitimate holds separate from missing information.

Is an Unbilled-Work Register the Same as WIP?

Not necessarily. For this operational register, identify work or milestones eligible for billing and what remains uninvoiced. Your accountant may use work-in-progress and unbilled-revenue classifications differently. Agree the reporting definitions rather than treating this register as an accounting valuation.

What Should You Do After an Unknown Sync Result?

Check the destination for the transaction using stable references before retrying or entering it manually. Record the result and follow the supported recovery process. An unknown outcome should remain open until somebody verifies what happened.

Does a Signed Job Sheet Authorise Extra Work?

Only to the extent that the document and the signer's authority support that conclusion. Attendance acknowledgement, work confirmation and approval of additional charges are different matters. Obtain the required authorisation and retain it with the variation.

Start with the oldest billing-ready item in your register. Identify the one unanswered question preventing its invoice, give it to the person who can resolve it and record when they will respond.

Niamh McKay

Niamh is a Marketing Executive at Fieldmotion, combining creativity with strategy, she creates clear, engaging content that connects with the right audiences. Her background in storytelling, research and communication helps her turn complex ideas into accessible, compelling messaging.