A change in headcount, site, or period becomes a new quote on the same deployment with its own rate and its own line, so the client can see what the variation did to the bill and not only to the total.
Labour Contractors
Contractors who supply people rather than products, where the client pays monthly against a headcount it may audit, and the difference between a good month and a bad one is what the deployment actually cost against what the contract allowed.
The problem
A labour contractor's money arrives because a client is obliged to keep people on site, and the moment that obligation is audited, an invoice stops being an invoice and becomes evidence. The contract says how many people, for how long, at what rate. The deployment says who actually turned up and where. The bill says what was supplied for the month. The payment says whether the money came. In most contractors those four things live in four different places — a contract file, a WhatsApp group of site supervisors, a tally book, and a bank statement — and the gap between them is exactly where the argument with the client happens. The uncomfortable part is that the number the client audits is a headcount and the number the contractor thinks in is a margin, and the margin between a billed rate and a wage is the entire business, held in one person's head. So the record has to hold the contract, the deployment, the bill, and the collection as one thing, without pretending to be the statutory register the law actually asks for.
A working day
The month is the unit, and the deployment is the thing that moves inside it. At the start of the month the client asks for six people and by the second week it is eight, and the question is whether that is a variation, a second deployment, or a favour nobody will remember granting. A supervisor confirms the headcount at the gate and sends a photograph of the register page; the office has no way to know whether it matches what is about to be billed, because the system holds no muster, no attendance, and no timesheet, so the count is a person's knowledge rather than a record. Someone leaves on the ninth and a replacement is supplied the same afternoon, and the number that goes on the bill changes because of a phone call. A client withholds a part payment over a headcount dispute, and the only way to settle it is to read the contract, the deployment, and the invoice side by side. The month closes with three money questions, and none of them is statutory: which clients paid, which are holding money against a dispute, and which deployment is still running below its rate.
How NoxOrigin fits this business
Every business runs the same sequence, from first contact to money in. NoxOrigin keeps each step tied to the last: Customer → Opportunity → Quote → Project → Work → Invoice → Payment.
The steps are the same. What changes is the words you use for them, the pressure at each one, and who is responsible for it. This is how it reads for labour contractors.
The client and the site as a customer
Customer → Opportunity
A client becomes a customer record with the site, the person who approves the headcount, the contract reference, and the billing cycle, because a contractor usually serves the same client at two sites and the two must not become two accounts that each look complete. The enquiry is often a client asking for a rate for a requirement they do not yet have, so the opportunity carries the trade, the skill, the number of people, and the duration. Merge policy is a setup decision: duplicate detection flags candidates and a person reviews them, since the same corporate client commonly arrives under a site name, a sub-contractor name, and a name taken from a letterhead.
The supply contract
Quote
The quote is the contract: the trade or skill, the number of people, the period, the rate per person per month or day, and the escalation or the terms if there are any, so that adding people or changing the period is a new quote on the same engagement rather than a number someone edited at month end. The rate quoted is the rate a client will hold you to, and the difference between that rate and the wage is the margin — which is why the quote is the only place the commercial terms belong. There is no contract editor and no e-signature record, so the signed agreement stays in the file the client signed it in.
The deployment running against the contract
Project
Once the contract is accepted, the deployment is the live record: the site, the people supplied, the period, and the rate it was accepted at, so a change in headcount or a second site becomes a visible variation instead of a quiet adjustment. A change mid-month is a new quote on the same deployment. There is no change-request record, no milestone record, and no deliverable record, and nothing here verifies anybody's identity, allocates a badge, or manages a shift roster.
The month as supplied
Work
The work is the deployment itself — who was placed, where, and what happened when somebody left, was absent, or was replaced — recorded against the contract so that a payment dispute over a headcount is resolvable from a record rather than from three people's memory. It is the only place the operational reality of a deployment is visible, and it does not reach the client's bill unless a person puts it on one. There is no timesheet record, no payroll module, and no attendance or muster record, so the hours behind a deployment are not measured here, and no statutory contribution is calculated from this record.
The monthly bill for the people supplied
Invoice
The bill carries the headcount, the rate, and the period that were actually agreed, with any approved variation as its own line so a client can see what an extra pair of hands did to the total rather than only seeing the total. An invoice and a payment are different records, and in this trade the distinction is the whole mechanism: a monthly bill is a claim against a period of work, and the claim needs to sit on the invoice that made it rather than in a message thread. The invoice is a tax document; NoxOrigin does not file GST returns, does not generate an e-invoice, and does not determine place of supply or reverse charge.
The client's payment, often part-paid
Payment
Money arrives against a specific invoice, frequently in parts: a part payment against the month's bill, an amount held back over a headcount dispute, a deduction for a replacement, and a balance that lands after the next month starts. Recording the payment against the invoice is what lets the contractor see a client close, and separating a part payment from a settled account matters here because a part payment is usually a signal about the dispute behind it. NoxOrigin holds no bank connection and no bank credentials, so the money is recorded by a person against an invoice they can name.
Month close and the honest book
Reports
Quoted against billed against collected by client and by site, with the number that matters being the margin on a deployment rather than the size of the bill — a large client running below its rate is worse than a small one paying on time. Deductions, credits for replacements, and part payments held against a dispute all need to be records somebody raised, because none of them reduce a billed figure on their own. And the boundary has to stay visible in the report: this book shows what was contracted, supplied, billed, and collected, and it is not the PF, ESI, minimum-wage, or welfare-fund record that the client's audit will ask for.
What changes
What is different by next week.
The deployment stays attached to the contract it was accepted against, so a dispute over a month's headcount is answered by reading two records side by side instead of assembling three accounts of what happened.
A part payment, a deduction, and a settled invoice are three different states rather than one 'paid' tick, so a client holding money against a dispute is distinguishable from a client paying late.
The client, the site, the approver, and the billing cycle live on the customer record together, so two sites of the same corporate client stop looking like two separate businesses in the report.
The commercial rate and the operational headcount sit on the same record chain, so the person who agreed a variation, the supervisor who confirmed the count, and the person who raised the invoice are three named people rather than one anonymous month.
Who does what
Different people need different parts of the same information.
Everyone is looking at the same information. What changes is which part of it they are responsible for.
- Estimator or business developmentFinds the requirement, quotes the trade, the headcount, the period, and the rate, and answers for the commercial terms the client will be held to at month end.
- Site supervisorConfirms who was placed and where, reports a departure or an absence the same day, and holds no pricing or invoice permissions.
- Deployment and compliance deskRuns the paperwork the client's own compliance adviser asks for, outside this system, and keeps the contractor's headcount and wage records where the law expects them.
- AccountsRaises the monthly bill on the contract terms, records each part payment and deduction against the invoice, and ages what each client owes.
- Proprietor or managerDecides which variations to grant, which deployment is still worth running below its rate, and which client to hold to the contract terms.
What software should not decide
NoxOrigin keeps the facts. You still make the decisions.
Keeping the facts in one place ends the argument about what happened. It does not make the decisions that were always yours to make.
- Whether to grant a headcount increase mid-month as a free accommodation. Granting it keeps the client and cedes the margin on work already done; billing it is honest and is the moment a client starts negotiating the rate for next month.
- Whether to bill a period shorter than the deployment actually ran. Billing the full month protects the margin and is defensible on the contract; billing what was genuinely supplied is the practice that gets the renewal.
- Whether to press for the money a client is holding over a headcount dispute. Pressing gets cash and turns a small disagreement into a relationship problem at the next renewal; waiting lets the amount sit against you for a cycle.
- Whether to supply a same-day replacement for a worker who left mid-month at no charge. Absorbing it is what a client remembers when the next tender comes; not absorbing it is a defensible position that belongs in the contract, not in the argument.
- Whether to stay on a contract rate that no longer covers the wage. Continuing protects a relationship the contractor needs; repricing mid-contract is a new quote, and whether the client accepts it is the test of who really holds the relationship.
Free tools
What this trade tends to ask, answered with a calculator.
Retainer profitability calculator
What a monthly supply contract actually leaves once the wage cost is taken out, before the number is agreed in a room. A calculation, not a payroll or wage record, and it knows nothing about statutory contributions.
Scope change cost calculator
What a mid-month change in headcount, site, or period does to the bill, so the variation is quoted as a variation. A calculation, not a change-request record and not an approval.
Receivables aging calculator
Where each client's unpaid month sits by age, so the contractor who always pays on the thirty-first is distinguishable from the one who pays after a dispute. A calculation, not a collection record.
Where to look next
The product areas this depends on.
Customers & CRM
The client, the site, the person who approves the headcount, and the contract reference, so two sites of one client do not become two accounts that each look complete.
Quotes, Billing & Finance
The supply contract quoted as headcount, rate, and period, then the monthly bill raised on those terms with every approved variation as its own line.
Customer Payment Tracking
Part payments, deductions, and balances recorded against the specific invoice, so a client holding money over a dispute is distinguishable from a client paying late.
Project Profitability
Quoted against billed and collected per deployment, so a large client running below its agreed rate is visible before it becomes the reason the year was flat.
Before you look at pricing.
Does it record PF, ESI, minimum wages, or labour welfare contributions?
No. There is no PF record, no ESI record, no minimum-wage register, no labour welfare board contribution, and no wages-register compliance in NoxOrigin, and none of them is its job. Where those are statutory obligations — for the contractor, the client, or both — they belong to your own compliance adviser and your own statutory records. NoxOrigin keeps the contract, the deployment, the invoice, and the payment connected, and it is not a compliance system, a payroll system, or a statutory register.
Does it record attendance, muster roll, or daily deployment?
No. There is no attendance record, no muster roll, no shift roster, no timesheet, and no payroll module, so a headcount cannot be verified from the system and no contribution or wage can be calculated from it. What a deployment record carries is what was placed against which contract, plus the operational events someone raised against it, so a dispute is resolvable from a record rather than from memory. The daily count remains a supervisor's responsibility and, in most contractors, the place a statutory register has to be kept anyway.
How does it handle a headcount or scope change mid-month?
As money, which is the only way it is honest. A change in headcount, site, or period becomes a new quote on the same deployment with its own rate and its own line, and the approved variation appears on the invoice the client is billed, so the client can see what the change did to the bill rather than only to the total. There is no change-request record, no milestone record, no deliverable record, no contract editor, and no e-signature — a written variation stays in the file it was written in.
Can it run payroll, expenses, or purchasing for the contractor?
No. Payroll, timesheets, and attendance are not here at all, and the platform has no expense module — expenses are a Nox-Billings capability. Purchasing and stock movement sit in Commerce, which is not what a manpower supplier needs; a labour contractor buys almost nothing. A dedicated billing deployment such as Nox-Billings is a scoped custom project and does not carry platform pricing, so nothing here should be read as a per-person or per-site charge.
Does it file GST returns or connect to the bank?
No. NoxOrigin does not file GST returns, does not generate e-invoices or e-way bills, does not record TDS or TCS, does not handle reverse charge, and does not determine place of supply. It holds no bank connection and no bank credentials of any kind. Payments are recorded by a person against a specific invoice, and a payment and an invoice remain two records, so 'paid' is a projection of what has been allocated rather than something the system resolves with a bank.