The Deployment Nobody Billed
A staffing firm sent three people to a client for a quarter and cannot produce the document that says what was agreed, what was deployed and what is owed. A constructed deployment with the arithmetic shown, and the boundary around hours that no system records for you.
A staffing firm puts three people on a client's site in the first week of a quarter. They are good people and they do the work. At the end of the third month the client's finance lead sends a message asking for one consolidated invoice for the quarter, with the deployment dates and the agreed rate against each month, because their own purchase order has expired and the work cannot be paid without a document. The firm has a project record with nine deployment entries on it, a rate card in a spreadsheet, a card statement from three months of fuel and travel, and one bank credit of 300,000.00 with a payment reference that is a phone number. It has no quote. It has no invoice. The message that reaches the client's finance lead is that the work was done, it was good work, and the paperwork is being sorted out. Nobody in that exchange is lying. The document simply does not exist.
The reason this happens is that the work was recorded, and recording the work feels like documenting it. A person was deployed, the project shows it, the client saw it, the deployment is real and it is on the record. What is missing is the part that makes the work billable: a document that says what was agreed before anybody turned up, a document that says what was owed once they had, and a document that shows the difference between the two so a payment can be allocated to something. A deployment entry answers the question did this happen. It does not answer what was it worth, who agreed to that, or what is outstanding, and those are the three questions an invoice has to answer before money can move against it.
This article works that gap with a constructed example and full arithmetic. A deployment month is defined once, a rate is set, nine deployment months are quoted, one transfer arrives, and then the question is asked: what does the business have, what does it owe, and what can it produce when the client asks for the document? Every amount below is invented so the arithmetic can be checked by hand, and the derivations are shown rather than asserted. Where a proportion appears, it is a proportion of the constructed amounts and not a rate from anywhere else.
The argument is narrow and it is about documents rather than people. Work that was performed and money that is owed are both claims, and a claim that nobody can evidence is a claim that will not survive the first serious question. The same failure one step earlier in the chain is covered in [The Quote That Was Never Sent](/blog/the-quote-that-was-never-sent), and the chain-level version of the whole sequence is in [Quote to Cash: What Each Step Has to Carry](/blog/quote-to-cash-what-each-step-has-to-carry). This article stays on the gap between a recorded deployment and an issued invoice, including the part that most systems cannot help with at all: the hours behind the deployment are not recorded, and pretending otherwise would be the one genuinely dishonest thing this article could do.
The scenarioThe quarter that worked, and the three questions the document has to answer
Start with the definition that makes the example checkable, because every number in this article depends on it. A deployment month is one person, on the client's site, for one month. Under that definition, three people for three months is nine deployment months, which is nine units that can be quoted, nine units that can be worked, nine units that can be invoiced, and nine units that can be compared against what was actually delivered. A business that does not define its unit cannot do any of those four things, and the argument about whether a deployment was properly billed is usually an argument about the unit rather than about the bill.
The agreement itself, in the constructed example, was reached in one conversation and confirmed in one message. The message named the rate per deployment month, it named an on-site expense allowance, and it did not name a total, a start date, an end date, a scope, or anything about what would happen if the client wanted another person in the fourth month. From the firm's point of view that is a complete agreement, because everybody knew the rate. From the point of view of the document the business will need in three months, it is a rate with no quote attached to it, and a rate is not a scope.
Then the work happens, and this is where the record is genuinely good. Each of the nine deployment months is a work entry on the client's project: who went, when they went, which client they were at. The fourth month arrives, the client asks for one more person, the person goes, and there is a tenth work entry. If somebody asks the firm what happened this quarter, the system can answer completely and truthfully, and the answer will be about deployment rather than about money. Nine entries, then ten, each with a person and a date, is a real operating record of work performed.
What the system cannot answer is the three questions the client actually asked for. What was agreed: there is no quote, so the answer has to be assembled from a rate card and a memory of a conversation. What was deployed: this one is answerable, with the important limitation that the hours behind each deployment are not recorded, so the cost of the deployment is an assumption rather than a fact. And what was owed: the correct answer is a subtraction from a total that was never issued, which means the business has to build the document it should have raised, three months late, and then send it to a client who has no way to know whether it is a reconstruction or the original.
Constructed illustration: the four records a deployment needs, and what happens when each one is missing
The quote, saying what was agreed
One document that carries the unit, the rate, the allowance, the dates, the scope, and the client it belongs to. In the constructed example it would have totalled 621,270.00 including tax. Without it the business has a rate and a memory, and the two are not the same instrument.
The work record, saying what was deployed
Nine entries and then a tenth, each naming a person, a client and a month. This is the record the firm does have, and it is a good one. It says what happened. It does not say what the hours were, and it was never meant to.
The invoice, saying what was owed
A dated document against the quote, carrying the lines, the tax, and the total. In the constructed example it would have said 621,270.00 and left 321,270.00 outstanding after the one transfer that arrived. Without it there is no balance and no due date.
The payment, allocated against the invoice
A separate dated record that takes 300,000.00 of the 621,270.00 and says so. Paid is a projection of allocations rather than a stored flag, so this record is the only thing that can produce a correct outstanding figure. Without it the transfer is a bank credit against nothing.
Constructed: the three questions the client asked, and what could answer each one on the day they were asked
| Question the client asked | The document that answers it | What the firm could actually produce | Constructed amount behind the gap |
|---|---|---|---|
| What was agreed for the quarter? | A quote with a unit, a rate, an allowance, a scope and dates, on the client's record before anybody deployed | A rate card row of 52,000.00, a message that says the same as last time, and no document at all | Quoted total would have been 468,000.00 + 58,500.00 = 526,500.00 before tax, and 621,270.00 with tax |
| What was actually deployed? | Work entries on the project, one per deployment month, with the person and the month | Nine entries and a tenth, which answers this question honestly and completely | 9 deployment months documented, then 10 once the fourth month was worked, so 1 deployment month with no document |
| How many hours were behind each deployment? | A timesheet or attendance record attached to the deployment, which would let cost be derived rather than assumed | Nothing. There is no timesheet record, no payroll module and no attendance record, so the cost is a management assumption | Assumed cost of 34,000.00 per deployment month, which is 306,000.00 across the nine months and rests on no record |
| What is owed? | An invoice, and a payment allocated against it, so that outstanding is a derivation of two documents | One bank credit of 300,000.00 and a receivables report that shows 0.00 outstanding for this client | Owed and unrecorded: 621,270.00 - 300,000.00 = 321,270.00, which is 51.7% of the constructed contract value |
A constructed deployment, worked in full. Every amount is invented for this article so that the arithmetic can be checked by hand. The 18% GST figure is used only to keep one total checkable and is not a statement about the rate that applies to your business. NoxOrigin does not determine a rate, determine a place of supply, or handle reverse charge.
One staffing firm, one client, three people on the client's site for three months. A deployment month is one person for one month.
| Item | Arithmetic | Result |
|---|---|---|
| Deployment months worked and quoted | 3 people x 3 months | 9 |
| Charge for one deployment month, before tax, a constructed rate card figure | 1 x 52,000.00 | 52,000.00 |
| Charge for the nine deployment months | 9 x 52,000.00 | 468,000.00 |
| On-site expense allowance for one deployment month, constructed | 1 x 6,500.00 | 6,500.00 |
| Allowance for the nine deployment months | 9 x 6,500.00 | 58,500.00 |
| Quoted scope total before tax | 468,000.00 + 58,500.00 | 526,500.00 |
| GST at 18%, for checkability only | 526,500.00 x 0.18 | 94,770.00 |
| Total that a correct invoice would have carried | 526,500.00 + 94,770.00 | 621,270.00 |
| Money actually received, one transfer on the twentieth day of month one | one recorded bank credit | 300,000.00 |
| What would be outstanding if the invoice had been raised | 621,270.00 - 300,000.00 | 321,270.00 |
| What the receivables report shows today, because no invoice exists | no invoice, therefore no balance | 0.00 |
| Share of the constructed contract value that no record can answer for | 321,270.00 / 621,270.00 = 0.5171 | 51.7% |
| Share of the constructed contract value that arrived as money with no document attached | 300,000.00 / 621,270.00 = 0.4829 | 48.3% |
The expenses, because the allowance and the cost are different things. The firm's card statement for the three months shows 41,780.00 of fuel, tolls and travel. Expenses are a Nox-Billings record, and the statement is the evidence a person would attach to it. The allowance is a contracted figure, and money the client did not spend is still money the client owes if the quote says so.
| Step | Arithmetic | Result |
|---|---|---|
| Actual expenses from the card statement across the three months | one statement, itemised by hand | 41,780.00 |
| Expenses per deployment month, derived from the two rows above | 41,780.00 / 9 = 4,642.22 | 4,642.22 |
| Allowance actually contracted, nine months | 9 x 6,500.00 | 58,500.00 |
| Allowance that was contracted but not used | 58,500.00 - 41,780.00 | 16,720.00 |
| Share of the allowance not used | 16,720.00 / 58,500.00 = 0.2858 | 28.6% |
The 28.6% is not a saving anybody managed. It is the difference between a contracted allowance and a constructed cost, and the only reason it can be discussed at all is that the allowance was written down. If the allowance had been a habit rather than a line, the client would be asked for 6,500.00 a month against an argument about fuel, and the argument would be unwinnable because the firm would be quoting its own memory of a fuel price.
The distinctionWhy a deployment record is not an invoice, and what the fourth month costs to leave undocumented
A deployment record and an invoice are the same event seen from two different ends, and confusing them produces a business that knows exactly what it did and nothing about what it is owed. The deployment record is written while the work is happening, it is written by or for the person doing the work, and its subject is a person at a place on a date. The invoice is written after the work, it is addressed to a customer, and its subject is money. A record can be perfectly complete in its own terms and still be worth nothing as evidence of a debt, which is exactly what the nine entries in the constructed example are.
The fourth month is where a scope change usually appears, and it is worth being precise about it because there is a persistent belief that a change to an agreed scope can be recorded as a note against the original quote. There is no change-request record, no milestone record and no deliverable record in NoxOrigin, and there is no contract editor and no e-signature. A scope change is a new quote on the same project. That is not a limitation dressed up as a feature; it is the reason the original quote still says what it said, and the reason the extra person in month four has a document of his own rather than an amended version of somebody else's promise.
So in the constructed example, the fourth month is one person for one month, which is 52,000.00 of charge and 6,500.00 of allowance before tax and 58,500.00 in total, or 69,030.00 with tax at 18% for checkability. The person went, the work entry exists, and the invoice does not. Adding that to what the third month left outstanding gives the full constructed exposure, and it is worth writing it as a single number because a single number is the one an owner can act on.
There is a second cost that does not appear in that total and is harder to argue about. The client has now asked for a consolidated document for a quarter, and the firm is going to build it retrospectively. The reconstructed quote will be dated after the work it describes. The reconstructed invoice will be dated after the work it bills. Every figure in both will be correct if the rate card is right and the memory is right, and neither of those is a record. The client will accept the document or they will not, and if they do not, the firm has no way to show what was actually agreed on the day the first person turned up, because that day left no document at all.
The fourth month, the cost side, and what the system can and cannot carry. All figures continue from the constructed example above, and the same tax treatment is used so the totals remain checkable.
In the fourth month the client asked for one more person for one month. The person went. The work entry is on the project. No document was raised, and the correct instrument is a new quote on the same project.
| Step | Arithmetic | Result |
|---|---|---|
| Fourth month, one person for one deployment month | 1 x 52,000.00 | 52,000.00 |
| Fourth month allowance | 1 x 6,500.00 | 6,500.00 |
| Fourth month before tax | 52,500.00 is not used here; 52,000.00 + 6,500.00 | 58,500.00 |
| GST on the fourth month at 18%, for checkability only | 58,500.00 x 0.18 | 10,530.00 |
| Fourth month total | 58,500.00 + 10,530.00 | 69,030.00 |
| Exposure from the first three months | 621,270.00 - 300,000.00 | 321,270.00 |
| Total constructed exposure once the fourth month is included | 321,270.00 + 69,030.00 | 390,300.00 |
| Deployment months actually worked | 9 + 1 | 10 |
| Deployment months with a document behind them | 9 | 9 |
| Deployment months with no document | 10 - 9 | 1 |
| Share of deployment months with no document | 1 / 10 | 10% |
| Exposure per deployment month, derived from the two rows above | 390,300.00 / 10 = 39,030.00 | 39,030.00 |
The cost side, and the boundary that has to be said plainly rather than worked around. The firm's loaded cost for one deployment month is a constructed management assumption of 34,000.00 per person-month, taken from a spreadsheet, not from a record.
| Step | Arithmetic | Result |
|---|---|---|
| Assumed loaded cost for one deployment month | constructed assumption | 34,000.00 |
| Assumed cost of the nine documented deployment months | 9 x 34,000.00 | 306,000.00 |
| Assumed cost of all ten deployment months worked | 10 x 34,000.00 | 340,000.00 |
| Margin on the documented scope had it been invoiced | 526,500.00 - 306,000.00 | 220,500.00 |
| Scope value if the fourth month had been quoted as well | 526,500.00 + 58,500.00 | 585,000.00 |
| Margin on all the work done had all of it been invoiced | 585,000.00 - 340,000.00 | 245,000.00 |
| Margin that the undocumented fourth month represents | 245,000.00 - 220,500.00 | 24,500.00 |
| Share of the quoted scope resting on an assumption rather than a record | 306,000.00 / 526,500.00 = 0.5813 | 58.1% |
Why the last row matters more than the one above it. NoxOrigin has no timesheet record, no payroll module and no attendance record. The deployment is recorded as work, which is exactly what a deployment is, and the hours behind those nine entries and the tenth are not recorded, are not derivable, and cannot be reconstructed from the product. So a per-hour cost for these three people has to come from somewhere outside the system, and if it comes from a management assumption then the margin row is an assumption as well, not a measurement. In this constructed example 58.1% of the quoted scope value sits on an assumption. That is not a reason not to deploy people. It is a reason to know, before the quarter starts, that the commercial side of the deployment can be made airtight and the labour side cannot, and to price accordingly.
The requirementWhat the record has to carry, and the conversation that happens without one
The first requirement is the quote, and it has to exist before the first person turns up. That is not bureaucracy for its own sake: a quote is the only document that can say what was agreed, and a deployment that starts before one exists has already put the business in the position it will be in at the end of the quarter. The minimum content is a unit the business can count, a rate, an allowance, a scope written so that a stranger could tell whether the work stayed inside it, and a client. A rate card is not a quote, because a rate card does not know which client agreed to it or on what date, and those two facts are the entire difference between a price and a promise.
The second is the line structure on the invoice. Nine deployment months at 52,000.00 plus nine allowances at 6,500.00 is eleven lines, and each line is a separate claim that can be checked against a work entry. This is unglamorous and it is the thing that makes the invoice survive a dispute: a client who receives one line for 526,500.00 has to take the firm's word for three months of work, and a client who receives nine lines each naming a person and a month can check it. The arithmetic is the same in both cases and the defensibility is not.
The third is the allowance, decided before the fact and recorded as a line rather than as a feeling. The constructed example shows why: 6,500.00 a month against 4,642.22 of actual spend looks like a reasonable arrangement when it is a contracted line, and looks like an argument when it is not. The rule is simple and slightly uncomfortable, which is usually a sign it is right. If the client is going to be asked for an allowance, the allowance goes in the quote, and the actual spend goes into expenses as a separate record, and the two are compared rather than reconciled by argument.
The fourth is the fourth month, and the requirement there is a new quote rather than an amendment. A new quote on the same project keeps the first promise intact, gives the client a document for the extra work, and produces a project that can be read as two agreed pieces rather than one ambiguous piece. A business that treats a scope change as an adjustment to the original is relying on everybody remembering the original accurately, which is the same assumption that produced the problem this article started with.
Constructed illustration of the same quarter, and the conversation it produces. Every line is written for this article and none of it is a quotation from a real person
| Moment | What is said, constructed illustration and not a quotation from any real person | What the record has to do at that moment |
|---|---|---|
| Before the first deployment, in a message | Client: 'Send three people for the quarter, same as we discussed.' Firm: 'Three people, three months, at the standard deployment rate plus the on-site allowance.' | Raise a quote carrying the unit, the rate, the allowance, the scope and the dates, so that the answer exists as a document rather than as an agreement to remember |
| End of month one | Client's finance lead: 'Our purchase order closed, can you invoice the quarter together?' Firm: 'We can send one invoice for the three months when the third month is done.' | The quote is already a document, so the invoice is a mechanical consequence of it. In the constructed example nothing needs to be reconstructed |
| Start of month four, an extra person is asked for | Client: 'Can you add one person this month?' Firm: 'Yes, and I will send a separate quote for the extra month.' | Raise a new quote on the same project. There is no change-request record to hold the amendment, and there is no contract editor or e-signature to lean on |
| Month four, the person is sent anyway | Firm's own note: 'Sent one more person, told the client we would send the paperwork after.' | Either raise the quote, or record a decision not to charge. Doing neither leaves a tenth work entry that no document in the business can price |
| Month six, the client asks for the quarter | Client's finance lead: 'Please send the consolidated invoice with deployment dates and the agreed rate.' Firm: 'The work is done and the rate is what we discussed. I will need a few days to send the paperwork.' | Everything in the reply is true and none of it is evidence. The deployment dates exist as work entries and the agreed rate exists as a rate card, and the two have never been joined on a document |
Constructed: what to settle before a deployment can be billed rather than reconstructed
- Define the unit of a deployment in one line that a stranger could repeat, such as one person on site for one month, and use the same unit in the quote, the work entry and the invoice.
- Raise the quote before the first person travels. A rate card, a message and a phone call are not a substitute for a document that names the client and the date.
- Write the allowance into the quote as a line per deployment month, so that unspent allowance is contracted money rather than an argument about fuel.
- Raise one invoice line per deployment month, naming the person and the month, so the client can check the document against what they saw.
- Treat a change in headcount or duration as a new quote on the same project, never as an adjustment to the original promise.
- Record the hours expectation honestly: there is no timesheet record, no payroll module and no attendance record, so per-hour cost is an assumption and should be labelled as one wherever a margin is quoted.
- Keep expenses in Nox-Billings as their own dated records with the statement attached, and compare them against the contracted allowance at month end.
- Allocate every credit received against the invoice it belongs to. Paid is a projection of allocations, so an unallocated transfer produces no outstanding figure at all.
- Decide in advance who can send a reconstructed document and who has to escalate. A document dated after the work it bills is a different instrument and should be treated as one.
- Do not let a deployment be tracked as a location. There is no GPS, no driver app, no telematics and no dispatch engine; the deployment is a work record created by the business, and that is all it claims to be.
The handoverWhere this surfaces at quarter end, and the practical test that needs no software decision
A quarter is where this becomes visible, because a quarter is the first moment anybody outside the business asks for a document that covers several months of work at once. Before that, the deployment sits comfortably in the project record and nobody needs it to be anything more than what it is. The client asks for one invoice, the firm discovers it cannot produce one, and the discovery arrives at the worst possible time, because the answer is not going to be a phone call. It is going to be a reconstruction, a negotiation about a rate, and a client who has a purchase order deadline that does not move.
The figures that make it survivable are all constructed, and all of them are derivations rather than benchmarks. The exposure on the first three months is 321,270.00, the undocumented fourth month is 69,030.00, and together they are 390,300.00 across ten deployment months, which is 39,030.00 per deployment month. The margin that the missing month represents is 24,500.00, and 58.1% of the documented scope rests on an assumed cost rather than a recorded one. None of those numbers tells the firm how common this is, because this article contains no frequency figure and will not invent one. They tell the firm what this particular quarter looks like, which is the only thing a worked example is for.
There is a smaller and sneakier version of the same failure in the payment, and it is worth naming because it hides inside a good month. The bank shows 300,000.00 arriving. The receivables report shows 0.00 outstanding for that client. Neither is false. The money arrived and there is no invoice, so there is no balance, and the gap between the two views of the same quarter is 321,270.00 of work that happened and cannot be claimed. A business that reconciles its bank and trusts its receivables report will conclude that its client owes nothing, and it will be right about the report and wrong about the client.
The practical test needs no software decision and it can be run on the last quarter this afternoon. Pick one deployment, one client, one quarter. Ask whether the business can produce the document that says what was agreed, the record that says what was deployed, and the document that says what was owed, and then ask for the arithmetic that joins the first and the third. If all four exist, the answer will be immediate and the exposure will be visible on a report rather than discovered in a message. If any of them does not exist, then the quarter is a reconstruction waiting for somebody to ask, and the useful thing to know is that today, before the client asks, the size of the reconstruction is still only 390,300.00 in this constructed example and can be raised as a quote on the same project rather than argued about from memory.
The version where the work is delivered but never invoiced is the same failure with the opposite sign. the trip that was never invoiced
Frequently asked questions
A deployment happened and the work is on the project record. Why is that not enough to invoice it?
Because a work entry says a person was deployed on a date, and an invoice says money is owed. The two answer different questions. In the constructed example the nine work entries were complete and correct and there was still 321,270.00 of the quarter that no record could answer for, which is 51.7% of the constructed contract value of 621,270.00. The work record is real; it is just not a debt.
Should a change in headcount or duration be an amendment to the original quote?
It should be a new quote on the same project. There is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature, so an amendment has nothing to live in. A new quote keeps the first promise exactly as issued, gives the extra work its own document, and leaves the project readable as two agreed pieces. In the constructed example the extra person for one month was 52,000.00 plus a 6,500.00 allowance, which is 58,500.00 before tax and 69,030.00 with the tax used to keep the total checkable.
If there is no timesheet, how do I know the deployment was worth doing?
You do not know it from the system, and pretending otherwise would be the dishonest answer. A deployment is recorded as work; the hours, the attendance and the payroll behind it are not recorded. So the commercial side can be made airtight while the labour side stays an assumption. In the constructed example the assumed cost of 34,000.00 per deployment month produced an assumed cost of 306,000.00 across nine months, which is 58.1% of the quoted scope value, and every one of those figures came from a management assumption rather than a record. Price for that when you quote, not afterwards.
The client has already paid 300,000.00. Is the quarter settled?
No, and the reason is structural rather than personal. An invoice and a payment are different records, and paid is a projection of allocations rather than a stored flag. With no invoice raised, that transfer has nothing to allocate against, so the receivables report shows 0.00 outstanding while the constructed amount owed is 321,270.00. The fix is not to trust the bank balance; it is to raise the invoice and allocate the transfer to it, which leaves 621,270.00 - 300,000.00 = 321,270.00 genuinely outstanding and auditable.
Can NoxOrigin tell me where my people or vehicles were during a deployment?
No, and that is a deliberate boundary rather than a gap. There is no GPS, no driver app, no route optimisation, no telematics, and no scheduling or dispatch engine. A deployment is a work record on a client project, created by the business, and it claims nothing about location. What the system does hold is the commercial chain: the quote, the work, the invoice, and the allocation of each payment.
What happens at month end with the expenses on a deployment?
Expenses are a Nox-Billings record with the statement attached, and the day end compares them against the contracted allowance rather than assuming the two agree. Purchasing and stock movement are in Commerce, not Nox-Billings, so a deployment that consumes materials leaves two records in two modules. In the constructed example the allowance was 58,500.00 across nine months and the card statement showed 41,780.00, a difference of 16,720.00 that is only discussable because the allowance was written into the quote.