The Trip That Was Never Invoiced
Six visits, one day, three invoices. Why a delivery of service still needs a record, what a trip has to carry before it can become an invoice, and what an unallocated 40,000.00 transfer does to a day worth 45,843.00.
A field-service business closes the day. Six visits happened: a washing machine that would not drain, a fridge with a failed compressor, an air conditioner serviced, a cooktop replaced, a television wall-mounted, and a customer who had cancelled by the time the technician arrived. A fuel voucher was signed for. Three invoices were raised during the day, because three of the six visits happened to be remembered at the counter-equivalent. The day is closed, the drawer balances, and there is a document count problem that nobody will notice for three weeks: half the visits produced work and left no document behind, the fuel expense is on the record with no revenue against it, and two thirds of the day's stock movement is attached to invoices while the rest is not attached to anything.
A delivery of service is not a smaller version of a sale. It is a sale, with the same requirement on it, and the reason it is treated differently is that it happened away from the place where documents are made. Nobody in a van is raising an invoice. The visit produced a fact, the fact travelled back to the office in somebody's head, and by the time the office heard about it the context that made the charge obvious had gone: which customer, which parts, which price basis, which date on the tax document, which person did the work. Each of those is a small thing. Together they are the invoice.
This article works one constructed day with the arithmetic shown in full, and then sets out what a trip has to carry before it can become an invoice. It also deals with the visit that should not have been billed at all, because a no-charge visit still needs a decision and a record, and because a day that claims six visits while the billing claims five is a discrepancy that will not explain itself later. Every amount in this article is invented so the arithmetic can be checked by hand, and every proportion is a proportion of the constructed day rather than an average from anywhere else.
The claim underneath it is narrow. Work performed away from the business is still work, and money owed for it is still a debt, so the delivery of a service needs the same chain every other transaction needs: the customer, the line, the price basis, the date, and then an invoice with a payment allocated against it. The companion failure at a larger scale, where people rather than vehicles were deployed for a whole quarter, is in [The Deployment Nobody Billed](/blog/the-deployment-nobody-billed). The general version of work arriving before the record does is in [The Sale That Happened Before the Record Did](/blog/the-sale-that-happened-before-the-record-did), and the allocation problem that follows an under-invoiced day is in [One Payment, Many Invoices: The Allocation Waterfall](/blog/one-payment-many-invoices-allocation).
The scenarioOne day, six visits, three invoices, and the arithmetic of what the day was worth
Take a constructed field-service day, the twelfth of a month, with six visits and a single technician. Each visit has two components: parts consumed and labour charged. The parts are the reason a stock record exists, and the labour is the reason a price basis has to exist. The day is worth the sum of the twelve components, and every one of them is a line somebody has to write down, which is the whole difficulty in one sentence: the value of a service day is not a property of the day, it is a property of twelve written lines.
Three of the six visits are invoiced during the day. One is invoiced the next morning from a note the technician left. Two are never written down at all: an air conditioner that needed nothing more than a service, and a television wall-mount where the customer paid by card at the door into a personal account rather than into the business. The sixth is the cancelled customer, who was visited anyway. So of six visits, three produced an invoice, one produced a promise, and two produced nothing but a memory, and the day closes with the office believing it had a busy day and the records describing a smaller one.
The fuel voucher is the detail that makes the failure visible rather than theoretical. The business spent 640.00 getting the technician across the city and it recorded that as an expense, because expenses are a Nox-Billings record and somebody was disciplined about them. What that expense cannot do is attach itself to the visits that produced it, because the visits are in two places: three in invoices, one in a note, and two nowhere. An expense without revenue behind it is not an error in itself. It is the visible half of an invisible day, and it is the reason the cost side of the business looks healthy while the revenue side is quietly short.
The last visit is worth isolating because it is the one most businesses get wrong in a hurry. The customer cancelled in the morning. The technician was already on the road. The customer was polite, the technician was polite, and nobody mentioned money because there was no agreed call-out fee in any document, because no document had ever been written for this customer. Three honest outcomes exist and all three need a record. Charge the agreed fee if the terms have one, in which case a fee that was never written down is a fee the business will have to argue for. Record it as a goodwill visit with a zero-value line. Or record nothing and accept that the day contains one more visit than the business can charge for. What is not available is the current arrangement, where the visit happens in every system except the ones that matter.
Constructed illustration: what a service day leaves behind depending on where the record was made
Invoiced at the door
The customer, the line, the parts, the price and the date are all captured while the context is still there. The invoice is the least interesting document in the chain and the only one that can be reproduced later by somebody who was not present.
Written down afterwards
A note from the technician carries the customer and roughly what was done. It has to be turned into an invoice by somebody at the office who was not there, which means every figure in that invoice is a reconstruction. The reconstruction is usually right and it is never evidence.
Not written down
The visit existed, the parts left the shelf, the vehicle moved, and no record refers to it. The stock record will show the parts and the billing record will not, and the two disagree by exactly the value of the parts that went into the unrecorded job.
A constructed service day, worked in full. Every amount is invented for this article so the arithmetic can be checked by hand. The 18% GST figure is used only to keep the totals checkable and is not a statement about the rate that applies to your business. NoxOrigin does not file GST returns, generate e-invoices, issue e-way bills, record TDS or TCS, handle reverse charge, determine place of supply, or hold bank credentials.
One technician, six visits, one day. Parts are stock that left the shelf; labour is the charge for the visit.
| Visit | What was done | Parts | Labour | Total before tax |
|---|---|---|---|---|
| V1 | Washing machine would not drain, pump and belt replaced | 3,200.00 | 1,200.00 | 4,400.00 |
| V2 | Fridge compressor replaced | 18,600.00 | 2,400.00 | 21,000.00 |
| V3 | Air conditioner serviced, no parts used | 0.00 | 1,800.00 | 1,800.00 |
| V4 | Cooktop replaced | 6,450.00 | 1,500.00 | 7,950.00 |
| V5 | Television wall-mounted | 1,900.00 | 1,200.00 | 3,100.00 |
| V6 | Customer had cancelled, technician attended anyway, no fee agreed | 0.00 | 600.00 | 600.00 |
| Day totals | six visits | 30,150.00 | 8,700.00 | 38,850.00 |
| GST at 18% on the day, for checkability only | 38,850.00 x 0.18 | 6,993.00 | ||
| What the day was worth | 38,850.00 + 6,993.00 | 45,843.00 |
The parts column is a sum in its own right: 3,200.00 + 18,600.00 + 0.00 + 6,450.00 + 1,900.00 + 0.00 = 30,150.00. The labour column likewise: 1,200.00 + 2,400.00 + 1,800.00 + 1,500.00 + 1,200.00 + 600.00 = 8,700.00. Every one of those twelve numbers is a line somebody has to write down.
What was invoiced, and what was not.
| Group | Arithmetic | Before tax | With tax at 18% |
|---|---|---|---|
| Invoiced visits V1, V2 and V4 | 4,400.00 + 21,000.00 + 7,950.00 | 33,350.00 | 39,353.00, where 33,350.00 x 0.18 = 6,003.00 |
| Visits with no invoice, V3, V5 and V6 | 1,800.00 + 3,100.00 + 600.00 | 5,500.00 | 6,490.00, where 5,500.00 x 0.18 = 990.00 |
| Check against the day | 33,350.00 + 5,500.00 | 38,850.00 | 45,843.00 |
| Share of the day's value with no invoice | 5,500.00 / 38,850.00 = 0.1416 | 14.2% | 6,490.00 / 45,843.00 = 0.1416, so 14.2% |
| Visits that produced work with no document behind them | 6 visits - 3 invoiced | 3 of 6, so 50% |
The stock side, which is the part that can be checked without anybody remembering anything. Parts are purchased and moved in Commerce; the expense and the invoice live in Nox-Billings. The two modules hold different facts about the same day, and the day end compares them rather than assuming they agree.
| Step | Arithmetic | Result |
|---|---|---|
| Parts that left stock across the six visits | 30,150.00 from the parts column above | 30,150.00 |
| Parts attached to the three invoiced visits | 3,200.00 + 18,600.00 + 6,450.00 | 28,250.00 |
| Parts that left stock for a visit with no invoice | 30,150.00 - 28,250.00, which is V5 at 1,900.00 and nil for V3 and V6 | 1,900.00 |
| Share of stock movement with no revenue attached | 1,900.00 / 30,150.00 = 0.0630 | 6.3% |
| Fuel and travel for the day, recorded as an expense | one voucher | 640.00 |
| Cost of the day per visit, derived from the two rows above | 640.00 / 6 = 106.67 | 106.67 |
| Cost of the day as a share of the day's value | 640.00 / 38,850.00 = 0.0165 | 1.6% |
| Revenue recorded against that cost | 33,350.00 invoiced, of which parts were 28,250.00 | 33,350.00 |
The last two rows are the honest summary of a bad day. The business spent 640.00, recorded 640.00, and knows exactly what it earned on three of the six visits, and cannot say anything at all about the other three. It is not that the technician did the work badly. It is that the day had no way to become a document except in a van, and there is no document in the van.
The distinctionWhy a delivery of service still needs a record, and what the payment does next
The reason service work escapes documentation is not that it is small. It is that it is delivered at the customer, away from the document, by a person whose job is to fix something rather than to invoice. The counter has an invoice printer within arm's reach and a queue that makes the invoice a condition of the sale. A van has neither. So the record depends entirely on a habit, and habits are exactly the thing that fails on the day the sixth visit runs long and the customer has already cancelled. A business that wants service work to become documents has to make the document cheap enough to write in a car park, which is a design constraint rather than a discipline problem.
What the record has to carry is short, and every item is missing from at least one of the six visits in the constructed day. The customer, because a name in a technician's memory is not an identity and two customer records for one site is a failure mode of its own. The work line, because a description of what was done is what makes the charge checkable. The parts, because parts consumed is a stock movement in Commerce and it needs to be attached to the visit rather than to the day. The price basis, which is either a quoted figure, a rate card line, or a decision somebody made and recorded. The tax treatment, which is a question for the customer's own accountant and not something the visit can settle. The date, on the document, because an invoice dated a week after the visit is a different document from one dated on the day. And the person, because work without an owner cannot be followed up, disputed or improved.
The payment is the part that turns an under-invoiced day into an unreconcilable one. In the constructed day the customer pays on the second day by one transfer of 40,000.00, believing they have settled the day in full, and the money is 647.00 short of the three invoices that were actually raised. Those three invoices total 39,353.00, so the allocation takes 39,353.00 of the 40,000.00 and leaves 647.00 with nowhere to go. The customer believes the day is closed. The bank agrees that the money arrived. The receivables report says the day was 39,353.00. And 6,490.00 of work that genuinely happened is in no ageing bucket, because a bucket needs an invoice date and that work has no invoice at all.
The three false reassurances are worth naming separately, because each of them is a real fact that points the wrong way. The technician's day is complete, so the work happened. The stock record shows the parts, so materials moved. The customer says they have paid, so money arrived. Every one of those is true and none of them is a claim on what the business is owed. In this constructed day, 14.2% of the value is invisible to the invoice ledger while every other record in the business is satisfied, and that combination is what makes this failure survive a month end without anybody raising it.
Constructed: what a visit has to carry before it can become an invoice, and what happens in the constructed day when it does not
| What the trip has to carry | Why it is required | The constructed visit where it was missing | What the business is left with |
|---|---|---|---|
| The customer, on a single customer record | An invoice has to be addressed to something that can be identified later, and two records for one site split the history | V5, the television wall-mount, where the customer paid at the door into a personal account | Money that is not the business's, and a visit that will be argued about with no document to point at |
| A work line describing what was done | A description is what makes the charge checkable, and it is also what a warranty or a complaint is argued from | V3, the air conditioner service, where nothing was written and nothing needed to be collected | A service that was performed, cannot be invoiced from memory, and will be re-performed free of charge because there is no record that it happened |
| The parts, as a stock movement against the visit | Purchasing and stock movement are in Commerce, and the parts are what the customer was charged for | V5 again, at 1,900.00 of parts that left the shelf with no revenue attached | Stock out, revenue missing, and 6.3% of the day's stock movement that no billing record can explain |
| The price basis, quoted, listed or decided | Without a basis the price is a preference, and a customer's disagreement has nothing to be measured against | V6, the cancelled visit, where labour of 600.00 was recorded and no fee had ever been agreed in writing | A choice between charging a fee nobody agreed to, absorbing it silently, or writing off a visit the technician actually made |
| The tax treatment, taken from the customer's own position | The document has to carry what is correct for that customer, and that is a question for their chartered accountant | The whole day, where the rate used here is a constructed figure for checkability only | A total that can be checked by hand and must still be confirmed by the customer's accountant before it is relied on |
| The date on the document | An ageing report is a claim about time, and a bucket needs a date to count from | V3, V5 and V6, none of which has an invoice date because none of them has an invoice | 6,490.00 that never enters an ageing bucket and therefore never ages |
| The person who did the work | Work without an owner cannot be disputed, followed up or improved | All six visits, because one technician covered the day and the record is a person, not a route | A day that cannot be discussed with the person who did it, which matters most on the visit that went wrong |
The payment, the ageing, and the reconstruction, all derived from the constructed day above. The same tax treatment is used so that every total remains checkable by hand.
| Step | Arithmetic | Result |
|---|---|---|
| Transfer received on the second day | one recorded credit | 40,000.00 |
| Three invoices raised during the day | 33,350.00 x 1.18 | 39,353.00 |
| Allocated against those three invoices | 39,353.00 of 40,000.00 | 39,353.00 |
| Left with no invoice to sit against | 40,000.00 - 39,353.00 | 647.00 |
| That unapplied credit as a share of the money received | 647.00 / 40,000.00 = 0.0162 | 1.6% |
| Invoiced value that ages on the ageing report | 39,353.00 raised, then settled | 0.00 outstanding |
| Value of real work with no invoice and therefore no ageing date | V3 + V5 + V6 with tax, 1,800.00 x 1.18 + 3,100.00 x 1.18 + 600.00 x 1.18 | 6,490.00 |
| Share of the day's value that no ageing bucket can hold | 6,490.00 / 45,843.00 = 0.1416 | 14.2% |
What the reconstruction costs, using the same day. The office decides to raise the three missing invoices in the following week, from a note, a memory and a stock record.
| Step | Arithmetic | Result |
|---|---|---|
| Value reconstructed from a note and a stock movement | 5,500.00 before tax | 5,500.00 |
| Tax added at the same constructed rate | 5,500.00 x 0.18 | 990.00 |
| Reconstructed invoice total | 5,500.00 + 990.00 | 6,490.00 |
| Customer's payment already allocated elsewhere | 39,353.00 | 39,353.00 |
| Additional money the customer must now find | 6,490.00 less the 647.00 unapplied credit, so 6,490.00 - 647.00 | 5,843.00 |
| Documents now needed that did not exist before | three invoices and one allocation | 4 |
| Visits claimed by the day record and by the billing record, before reconstruction | 6 and 3 | a difference of 3 visits |
The 5,843.00 is the number worth remembering. The business is not losing 5,500.00 of work. It is losing the ability to invoice it in the ordinary way, and the cost of that is a collection conversation with a customer who has already paid 40,000.00, believes the account is clear, and is now being told that three of the day's visits were never billed. In the constructed example that conversation ends with 5,843.00 arriving. It could have ended with a dispute about the cancelled visit, and if it had, the firm would have had a technician's recollection and a stock record and nothing else.
The requirementWhat has to happen at the door, and the visit that should not have been billed
The design constraint is that the record has to be creatable in under a minute in a car park, by somebody holding a spanner. That rules out anything that needs a category tree, a reason code chosen from forty options, or a price looked up in a table that has to be navigated. It also rules out the idea that the office will reconstruct it, because the office does not have the information. The realistic shape is a short form tied to the customer record: what was done, the parts, the labour, the date, and a single decision about how the price was arrived at. Everything else about the visit is either already on the customer record or already on the stock record, and duplicating it is what makes the form slow.
The parts are the easiest part of this and the most instructive, because the system already knows them. A part that leaves the shelf is a stock movement in Commerce whether or not anybody bills for it, so the parts figure is the one part of a service visit that the business can reconstruct from a record it already keeps. In the constructed day that is 1,900.00 of parts with no revenue attached, and it is discoverable without a single person remembering anything. Anything that can be recovered from a stock record should be recovered from a stock record, and the effort belongs on the labour, the customer and the date, which only the person at the door knows.
The cancelled visit needs a decision and a written reason, and the reason has to be one of a very small number because the moment it becomes free text it will be filled in differently every time. The three honest outcomes are the same three in every field-service business and none of them is unusual: charge the call-out fee that the terms already allow, in which case the fee has to exist in a document before somebody attends a cancelled job; record the visit as a goodwill visit with a zero-value line so that the day reconciles; or record it as written off, so that the visit is visible as a cost rather than as a mystery. The constructed example used 600.00 of labour for that visit, and the honest answer is that the business cannot bill 600.00 for a visit nobody agreed to pay for, and cannot pretend the visit did not happen either.
And the trip itself is not a tracking problem, which is worth stating because it is often assumed to be one. NoxOrigin has no GPS, no driver app, no route optimisation, no telematics, and no scheduling or dispatch engine. Nothing in the product knows where the vehicle went or how long the drive was, and no invoice in this article depends on that. What the record needs is a date, a customer, a description, a price basis and a person, and all five of those are known at the door. The absence of location data is not what makes service work hard to bill. The absence of a document is.
Constructed illustration: the cancelled visit, handled three honest ways, with the conversation written for this article and not quoted from any real person
| Route | What is said, constructed illustration and not a quotation from any real person | What the record has to do, and what it is worth |
|---|---|---|
| Charge the agreed call-out fee | Customer: 'I cancelled this morning, sorry about the trip.' Technician: 'The call-out fee in your terms covers an attended cancellation, so I will raise 600.00 before tax.' | Raise a zero-parts line for the attendance at 600.00 of labour, which is 708.00 with the tax used to keep the total checkable, and point at the terms that allowed it |
| Record it as a goodwill visit | Customer: 'No charge for this one, you did not have to come.' Technician: 'Understood, I will note it as a goodwill visit so the day still balances.' | Raise a zero-value work record naming the customer and the date. The day then claims six visits, five of which carry value, and the sixth is visible rather than missing |
| Absorb it quietly | Technician's own note: 'Cancelled job, attended anyway, no charge.' | Nothing is raised, the day records six visits and the billing records five, and 600.00 of labour exists only in a note. 600.00 x 1.18 = 708.00 that will never be claimed |
Constructed: what to settle before a service day can close with documents instead of memories
- Fix the definition of a visit in one line that a stranger could repeat, and use the same definition in the work record, the invoice and the day-end report.
- Make the record creatable in under a minute at the door, because a form that takes longer than the job will not be filled in during the job.
- Carry the customer identity on the record rather than in the technician's memory, and settle duplicate detection by hand, since match rules and merge behaviour are a setup decision and nothing merges automatically.
- Attach parts to the visit as a stock movement in Commerce, and let the day end compare that movement against the parts billed in Nox-Billings rather than assuming they agree.
- Record expenses in Nox-Billings with the voucher attached. Purchasing and stock movement are in Commerce, so a service day leaves two records in two modules.
- Give the price basis a place on the record: quoted figure, rate card line, or a decision somebody made and wrote down. All three are acceptable and none of them can be inferred later.
- Put the call-out fee in a document before a technician ever attends a cancelled job, so that the 600.00 in the constructed day would have had a basis.
- Raise the invoice with the date of the visit on it, because an ageing report is a claim about time and an invoice dated a week later answers a different question.
- Allocate every receipt against the invoices it belongs to, and expect an unapplied credit to be the visible symptom rather than the cause. Paid is a projection of allocations, not a stored flag.
- Decide the review rule for zero-value and goodwill visits, and require one. A visit with no value is a decision, and a decision that leaves no record is the same failure as an unrecorded sale.
The handoverWhere this shows up at day end and at month end, and the test that needs no software decision
Day end is where the trip either becomes a document or becomes a story. The close compares what was collected against what was invoiced, and in the constructed day that comparison is clean in the way that makes a failure comfortable: the fuel voucher is recorded, the drawer is not short, the three invoices are paid, and the day's revenue figure is 39,353.00 rather than 45,843.00. Nobody has to look for the discrepancy. It simply is not visible from inside the figures the business already checks, which is why the same day can repeat for a year and produce an annual revenue number that is short by a proportion nobody ever computed.
Month end is where it becomes unfixable cheaply. A service business that bills visits in the week they happened can always catch up. A service business that finds out at month end that 14.2% of its constructed day value was never invoiced has a choice between writing a batch of invoices dated in the past and finding out what that does to the ageing report, or leaving the work as cost. The ageing report is a claim about time, so back-dated invoices produce a picture of customers who owed money for longer than they did, and that picture is then used to make collection decisions that are based on a fiction the business created itself.
There is a second, quieter cost, and it is the one that shows up in the following year rather than this month. A service visit with no record is a service the business has to do again. In the constructed day, V3 is an air conditioner that was serviced and cannot be shown to have been serviced, so the next complaint about that same unit starts from nothing. V5 has parts that left stock and no invoice, so a stock discrepancy at the next count has a candidate explanation and no document. Neither problem is dramatic, and both are downstream of a single missing minute of work at the door.
The test needs no software decision and it can be run on yesterday. Take the last service day. Ask whether the business can produce, for every visit, the document that names the customer, the line, the parts, the price basis, the date and the person. Then ask the harder question about the payment: can it produce the allocation that shows which invoices the money was for, and the arithmetic that shows what is still outstanding. In the constructed day the answer is five visits short of complete, 6,490.00 of value with no document, 1,900.00 of stock with no revenue, and 647.00 of cash with nothing to sit against. None of those four numbers is a benchmark and none of them is a frequency. They are the arithmetic of one invented day, and they are the four numbers a real day will produce too, in whatever proportion the real day happens to be.
Frequently asked questions
Why does a service visit need a record at all if the customer was obviously served?
Because serving the customer settles the work and not the money. An invoice is a claim that money is owed, and a claim has to name a customer, a line, a price basis, a date and a person before it can be collected on or defended. In the constructed day, three of six visits were invoiced and the day was worth 45,843.00 including tax, of which 6,490.00, or 14.2%, existed in no document at all even though the technician had done the work and the parts had left the shelf.
What does a trip have to carry before it can become an invoice?
Seven things, and all seven are known at the door: the customer on a single customer record, a work line describing what was done, the parts consumed as a stock movement, the price basis, the tax treatment the customer's own accountant has confirmed, the date on the document, and the person who did the work. The only part of a service visit the system can recover later without anybody remembering is the parts, because parts movement is a stock record in Commerce. Everything else has to be written down at the door or it does not exist.
Can NoxOrigin track my technician's vehicle and route?
No. There is no GPS, no driver app, no route optimisation, no telematics, and no scheduling or dispatch engine in the product, and no invoice depends on any of them. The absence of location data is not what makes service work hard to bill. What makes it hard is that the document is not created at the point where the work happens, and a short form tied to the customer record is what closes that gap.
The customer paid one transfer for the whole day. Is that allocated now?
Only as far as the invoices go. In the constructed example the transfer was 40,000.00 and the three invoices raised during the day totalled 39,353.00, so 39,353.00 is allocated and 647.00 is left with nothing to sit against. Paid is a projection of allocations rather than a stored boolean, which is exactly why an unapplied credit is the visible symptom here: the money arrived, the day was never fully invoiced, and the two facts are not connected by any document.
What should I do about a visit I attended but cannot charge for?
Three honest routes, and all three need a record. Charge the call-out fee if the terms already allow it, which means the fee has to be in a document before you attend a cancelled job. Record it as a goodwill visit with a zero-value line so the day still reconciles. Or record it as a written-off visit so the cost is visible. In the constructed example that visit carried 600.00 of labour, which is 708.00 with the tax used to keep the total checkable, and the business cannot both claim it and forget it.
Where do parts and travel costs sit for a service day?
Purchasing and stock movement are in Commerce, and expenses are Nox-Billings only, so one service day leaves two records in two modules. The day end compares them rather than assuming they agree. In the constructed day the fuel voucher was 640.00, which is 106.67 across six visits, and 1,900.00 of parts had left stock with no invoice attached, which is 6.3% of the day's stock movement and is discoverable from a record the business already keeps.