The Order Taken by Phone With Nothing on It
The sale happens, the money is promised, and no document exists. What a verbal order needs before it can become an invoice, and why the record of the order and the record of the price agreed are the same document or neither.
The sale happened. The customer said yes, the price was agreed, a date was given, and somebody wrote it on a pad or remembered it or simply began the work. No document exists. Not a bad document and not a missing attachment — no document at all, in any system, anywhere.
This is different from the two failures either side of it in the chain, and the difference matters. An enquiry that never became an opportunity produced nothing, so there is nothing downstream to be wrong. A quote that was never sent left a document behind, imperfect, and the customer at least has a copy. The verbal order is worse than both, because it has a customer, an agreed price, a scope, and a commitment to deliver, and none of it is written down. It is the only failure in the chain where the business knows the deal exists and cannot prove it.
The reason it happens is not carelessness. Verbal acceptance is the fastest possible path from a conversation to work, and in most businesses it is faster than the alternative because the alternative is a form. The customer has already said yes. Sitting down to write the order down costs five minutes and produces nothing visible to either party. So the work starts, and the record arrives later if it arrives, and by the time somebody gets round to it the details have begun to drift.
This is the third of four articles on the weak points of the chain. The first was the enquiry that never became an opportunity, the second the quote that was never sent, and the fourth is the invoice that never reached the customer. The chain as a whole is in [Quote to Cash: What Each Step Has to Carry](/blog/quote-to-cash-what-each-step-has-to-carry). This one is about the moment the business commits to work and the paperwork, if any, comes afterwards.
The mechanismA verbal order is not a draft order. It is a completed sale with a missing document.
The natural assumption is that a verbal order is an incomplete version of a written one, and that all it needs is for somebody to fill in the paperwork properly. That framing is wrong in a way that matters, because it implies the deal is provisional until the paperwork exists. It is not. The deal is complete. The goods are committed, the work is scheduled, the customer is relying on a date, and possibly materials have been bought. The document is the only part that is late, and it is the least load-bearing part of the arrangement in the sense that everything else already depends on it.
That is why a verbal order is unusually vulnerable to drift. Every person who touches it after the call has a slightly different version. The person who was on the call heard a number. The person who starts the work heard a different number, or heard a scope and inferred the rest. The person who eventually raises the invoice looks at both and finds a figure that reconciles with neither, and reasonably concludes that somebody made a mistake, which sets off a search for who is wrong rather than a check of what was agreed.
The details that go are always the same ones, and they are the ones that were least explicit in the conversation. The exact scope, because a phone conversation establishes a shape rather than a list. Whether extras were included, because nobody says 'this excludes the second site' out loud and everybody assumes it. The price, because a discount agreed in the flow of a call is socially awkward to bring up in writing afterwards, and it is easier for both parties to act as though the full number was said. The date, because there are two of them — the date the customer wants and the date somebody thinks is possible — and the one that gets written down is whichever was said last.
And then there is the order the record cannot represent at all: the informal one. The customer who says get started and we will sort the paperwork. The job where the scope grew by conversation over three visits. The customer who has paid an advance in cash with no receipt. These are not failures of discipline, they are how a substantial part of small trade actually happens, and a system that can only hold formal orders will simply not represent them, which means the business's own records will disagree with the business's memory in ways nobody can explain.
Illustrative: what a verbal acceptance leaves behind, and what each part is worth
Left behind, and reliable
The customer said yes. The work is real. Somebody knows roughly what was discussed and roughly what was agreed. The commitment exists and the business is going to honour it. None of this depends on a document and none of it is in doubt.
Left behind, and unreliable
The exact scope, the exact price, whether anything was excluded, which date governs, who approved it, and whether anything has been added since. Every one of these exists in one person's recollection of a phone call, and every one of them becomes an argument later — with the customer, with the person doing the work, or with yourself at invoice time.
The requirementFive things, and only four of them are about the customer
An invoice is a document that asserts a specific set of facts to a specific person: that these things were supplied, at these prices, on these dates, to this customer, and that this is owed. A verbal order contains almost none of those facts in a form that can be asserted. It contains a relationship, an intention, and an approximate scope. Converting it into an invoice is therefore not a formatting exercise. It is the reconstruction of the commercial content of a conversation, and the quality of the invoice is entirely determined by how much of that content was captured while the conversation was still available to be captured from.
The first thing is the customer, and this is where a surprising number of verbal orders go wrong before the conversation even starts. The order is for a company the business has no record of, or has two records of, because the work was done for a name on a gate rather than for an entity. An invoice needs a billing identity, and a billing identity cannot be inferred from a conversation. If the customer record does not exist, it has to be created at the moment of the order, not reconstructed at the moment of the invoice, and the tax identity in particular is not something a system should guess at. Where the correct treatment is not obvious, that is a question for your chartered accountant, not a default a piece of software picks.
The second is the scope, and specifically the scope as the customer understands it rather than as the business understands it. These differ more often than anybody expects, because the business knows what is difficult and the customer knows what they need. A verbal order almost always carries the business's version implicitly and the customer's version explicitly, and it is the customer's version that will be on the invoice and the one they will check the invoice against. Capturing it means writing down what they asked for, in their terms, including the things that were mentioned once and not argued about.
The third is the price, and it has to be the price that was agreed rather than the price that is standard. This sounds trivial and it is the single most common source of an invoice dispute that nobody can resolve, because both parties remember a different conversation and both memories are sincere. The way to protect that conversation is to make the agreed price a field, and the way to make it a field is to enter it immediately, while the number is still the number in the room rather than a reconstruction of it.
The fourth is the exclusions. This is the one nobody thinks about and the one that saves the most argument. Work quoted verbally has edges, and those edges were probably discussed in passing and never written down. A site visit that included travel, a revision round that was included once and then a second round that was not, a licence that was for a year and not a renewal. Every exclusion that is written down before the work is invisible and uncontroversial. Every exclusion that is discovered afterwards is a dispute, because the customer will reasonably read silence as inclusion.
The fifth is the authority, and it is the only one of the five that is not about the customer. Somebody agreed to this. If the business has a person who can agree to a price, that person needs to be on the record, not because the software is watching for fraud but because the business is going to have three questions in six months about whether the right person authorised a discount and it will not be able to answer any of them. Quote approval as a permission and a threshold solves this for written quotes; a verbal order needs the equivalent, which is simply that the person who took the call is named against the order.
Illustrative: the same acceptance, documented and undocumented
| Question | Accepted verbally, nothing on it | Accepted verbally, recorded the same day |
|---|---|---|
| Who is the customer | A name on a gate, or a company the business has no record of | A customer record that exists, with the billing identity settled or flagged for the accountant |
| What was sold | A shape of work that the person on the call remembers | Line items in the customer's own terms, including anything added later |
| What it costs | A number from a conversation, and possibly a discount nobody will mention again | The agreed figure as a field, entered while it is still the number in the room |
| What is not included | Silent, and therefore read as included by the customer | Written before the work, so nobody is surprised afterwards |
| Who agreed it | Whoever happened to be on the call | A named person, so a later question about authority has an answer |
| What the invoice becomes | A reconstruction that has to be reconciled against two memories | A document that restates facts that were established on the day |
| How long the detail survives | About a week, and then it starts to be argued rather than remembered | As long as the record exists, because it is written |
A constructed verbal order, and the invoice that eventually has to be raised from it. All figures constructed for this article so the arithmetic can be checkable by hand. The 18% GST rate is used only to make the invoice total checkable and is not a statement about the rate that applies to your business.
What was agreed on the call, as best three people remember it afterwards. All three recollections are sincere.
| Detail | What the salesperson remembers | What the person starting the work remembers | What the customer remembers |
|---|---|---|---|
| Scope | A two-week build with a handover | A build, plus some fixes to the old site | The new site working, with the old one still reachable |
| Price | 120,000.00, and there was a mention of something for the handover | 120,000.00, no mention of anything extra | 120,000.00 |
| Second site | Not discussed | Possibly included | Not discussed |
| Exclusions | Travel and hosting were said to be extra | Nothing said | Nothing said |
| Date | The customer wanted it before the end of the month | Start next week | Wants it before the end of the month |
Now the invoice has to be raised. The person raising it is a fourth person who was on none of these calls. Here are three invoices that the same set of memories can produce. Every one of them is arithmetically valid and only one of them is the conversation.
| Candidate | Taxable value | GST at 18%, for checkability | Invoice total |
|---|---|---|---|
| A: base build only, nothing extra | 120,000.00 | 120,000.00 x 0.18 = 21,600.00 | 141,600.00 |
| B: base build plus the handover | 120,000.00 + 15,000.00 = 135,000.00 | 135,000.00 x 0.18 = 24,300.00 | 159,300.00 |
| C: base build, handover, and a second site | 135,000.00 + 45,000.00 = 180,000.00 | 180,000.00 x 0.18 = 32,400.00 | 212,400.00 |
Check the spread. The widest reconstruction, 212,400.00, minus the narrowest, 141,600.00, is 70,800.00. That is the size of the hole created by one phone call that was never written down, on a deal that everybody involved believes they remember correctly. Note also that the customer is being invoiced an amount they never agreed to in every candidate except one, and that in candidate C the customer is being invoiced for work that may not have happened at all.
What closes the hole. One sentence written at the end of the call, listing scope, price, exclusions and date. That is the whole intervention, and it is the reason this failure is a design problem rather than a discipline problem: the person on the call already knows all five things. The only thing missing is the eleven seconds in which they write them down.
A worked variant, where somebody did write it down. Same call, same scope, recorded the same day:
| Line | Arithmetic | Result |
|---|---|---|
| Base build, fixed fee, per the agreed line items | as stated on the order | 120,000.00 |
| Handover session and documentation | 15,000.00 | 15,000.00 |
| Line total before tax | 120,000.00 + 15,000.00 | 135,000.00 |
| Taxable value on the order | 120,000.00 + 15,000.00 | 135,000.00 |
| GST at 18%, for checkability only | 135,000.00 x 0.18 | 24,300.00 |
| Invoice total that follows directly from the order | 135,000.00 + 24,300.00 | 159,300.00 |
| Travel and hosting | excluded in writing before the work | 0.00 on the invoice |
| Second site | not on this order | 0.00 on the invoice |
The point of the second table is not that it is cheaper. Candidate B and this order produce the same 159,300.00, and candidate A would have been an under-invoice. The point is that the invoice is now a restatement of a record rather than a fresh act of reconstruction, so the question that comes up in month three — what exactly did we agree — has an answer, and the exclusions are settled before anybody has an opinion about them.
The structural pointThe record of what was ordered and the record of what it costs are one document, or they are neither
A surprising amount of damage in small businesses comes from separating the order from the price. The order says what was agreed. The quotation says what it costs. They are stored apart, maintained by different assumptions, and they are allowed to drift. When they disagree, there is no way to tell which one is authoritative, so the business picks whichever is more convenient that month — usually the one that makes the invoice easier to raise and the conversation easier to have.
This only works if the order and its price are the same record. Not the same page, necessarily, but the same object: a set of line items, each with a description, a quantity, a price, and a tax treatment, which is simultaneously what was ordered and what will be invoiced. The moment those are two records, every later question — did we include travel, was the discount agreed, which site was in scope — becomes a comparison between two documents that were never required to agree, and the comparison is done from memory by whoever is under time pressure.
The reason this matters most for verbal orders specifically is that a verbal acceptance is already an assertion of both. The customer said yes to work at a price. Accepting the work and accepting the price happened in the same breath, in the same conversation, between the same two people. Splitting them afterwards into a scope document and a price document is not a modelling improvement; it is a chance to lose the connection between two things that were never actually separate.
This is also why a scope change cannot be an edit. If the order and the price are the same record, then changing one of them changes the commercial content of the deal, and the version that was agreed before is a fact about the past that both parties may need later. So the change becomes a new quote on the same project, with its own number, its own date, and its own record of what it added or removed. There is no change-request record and no deliverable record in NoxOrigin, and the absence is the design: the chain has exactly one kind of document that says what was agreed and for how much, and adding a second kind would recreate the split this section is about.
What is missing is not a document type. It is eleven seconds at the end of a call, and a place to put the result.
Illustrative: what to have available when a customer accepts on a call
- The customer record, created at the moment of the order rather than at the moment of the invoice, with the billing identity settled or flagged for your chartered accountant.
- A way to write the line items as you talk, so the scope is recorded in the customer's words rather than as an internal summary.
- The price as a field, entered as agreed, including any discount — because a discount nobody will mention again is the hardest number to defend later.
- A written list of exclusions, before the work rather than after. Silence on an exclusion reads as inclusion.
- The customer's own requested date, recorded separately from any date you think is achievable.
- The name of the person who took the call, so a later question about authority has an answer.
- A decision about advances. If money has changed hands, it is a payment against an invoice, and an invoice and a payment are different records.
- A rule for what happens when the scope grows during the work: a new quote on the same project, never a quiet edit.
- A short note on how the work actually went, in the customer's terms, written while it is fresh rather than reconstructed at invoice time.
- The invoice raised from the order rather than typed fresh, so the arithmetic is a consequence of the record instead of a second attempt at it.
The handoverWhat the collection call looks like when the order was documented
The chain from a verbal order to a collection call is short, and every step of it is easier when the order exists. The invoice is raised from the order rather than typed, so the total is arithmetic rather than an opinion. The tax treatment is the treatment that was recorded when the order was created, which is exactly the point at which a chartered accountant can advise on it properly. The payment arrives and is recorded as a separate record that allocates against the invoice, and the invoice's outstanding figure is whatever the allocations say it is — not a field anybody typed.
The part that is not mechanical is the customer's memory. A customer who received an invoice reflecting a conversation they remember differently will dispute it, and the only thing that makes that dispute short is that you can put the order in front of them. Both parties are looking at the same document, dated the same day, saying the same thing. That is the entire return on the eleven seconds.
If the order was not documented, none of this is available, and the alternative is not a firm figure — it is a conversation in which somebody apologises. That is the real cost, and it is paid at the moment it hurts most, which is when you most need the customer to be on side. The [Invoice and Payment Tracking Software](/invoice-payment-tracking-software) page is about the stage after this one, and [The Collection Call You Have to Make](/blog/the-collection-call-you-have-to-make) is about what to have in front of you when the money has not moved.
Frequently asked questions
Is a verbal order treated as provisional until it is written down?
No, and this is the point. The sale is complete: the work is committed and the customer is relying on a date. The document is the late part, and it is the part everything else already depends on. Treating the verbal order as provisional is why it gets written down eventually rather than immediately.
Why should the order and the price be one record?
Because a customer accepting work at a price accepted both in the same breath. If the order and the quotation are separate records, nothing requires them to agree, and a later question about what was included becomes a comparison between two documents reconstructed from memory. One record means the invoice is a restatement rather than a second attempt at the arithmetic.
What happens if the scope grows while the work is being done?
It becomes a new quote on the same project, with its own number and its own date. There is no change-request record, no milestone record and no deliverable record in NoxOrigin, and no contract editor — so the earlier agreed version stays intact as a fact about the past rather than being edited into the new one.
How is an advance paid on a verbal order recorded?
As a payment against an invoice, and an invoice and a payment are different records. There is no stored paid flag: paid is a projection of the allocations you have recorded, so the outstanding figure is something the system works out rather than something somebody types.
What if the customer is a business the company has no record of?
The customer record has to exist before the invoice does, with the billing identity settled or flagged for your chartered accountant. NoxOrigin does not guess a tax treatment or file any statutory return, so the treatment is a question for your accountant and the invoice follows their answer.