Project economics, client money, receivables, and day-to-day reporting — where quoted, billed, collected, and outstanding are four separate facts, and confusing them is how a profitable-looking month turns out to be a quarter of unpaid invoices.
Most businesses know their revenue figure and almost nothing else. Revenue arrives reliably and means very little alone, because it counts money that was quoted, money that was billed, and money that actually arrived as if they were the same thing. A month can look strong while a large share of it sits unbilled in a project nobody has invoiced, and a client can be called your best account when most of that client’s work is still outstanding. The problem is not a shortage of graphs. It is that the underlying states were collapsed into one number somewhere in a spreadsheet, and nobody remembers where. Once they are kept apart, the questions a business actually needs answered become answerable.
Works with: Customer → Opportunity → Quote → Project → Work → Invoice → Payment
For a client, the four states are read side by side rather than in sequence: what has been quoted, what has been billed, what has been collected, and what remains outstanding. The gap between quoted and billed shows work that was agreed and never invoiced, which is the most commonly missed loss in the whole chain. Because each state is kept in its own right, the comparison is a view rather than a reconstruction.
A project carries what was quoted against what was billed, so the commercial outcome can be discussed against what was actually delivered. This is where a project that was badly scoped becomes visible as a pattern across projects rather than as one unpleasant recollection. It is a margin view on work you have run — not a cost accounting system, and not a replacement for one.
Receivables are read per client and by ageing, so the question of who owes what, and since when, is a queue rather than a monthly reckoning. An amount that has been outstanding for months is visible as an exception instead of being averaged away inside a healthy-looking total. The list is only useful if it has an owner working it, which is a decision rather than a feature.
The commercial numbers are only half the story, so day-to-day reporting sits next to them — activity across the work that produced the money. A drop in billed value and a drop in completed work are different problems with different causes, and reading them together is what stops a revenue decline being explained as a billing failure when it was a delivery one. Everything here is counted from the same work the money came from, rather than from a parallel set of figures.
Every figure in these reports has a path back to its source — the client, the project, the invoice, the payment, or the day-to-day activity behind it. That is the difference between a report you trust and a report you re-check in a spreadsheet before repeating it to anyone. When a number looks wrong, the investigation is a matter of opening the underlying detail rather than rebuilding the calculation.
Quoted, billed, collected, and outstanding stop being one number and become four facts that can be compared.
Agreed work that was never invoiced becomes findable, instead of being written off as churn.
Ageing makes an old receivable an exception rather than a rounding error inside a healthy total.
Profitability becomes a discussable subject because margin can be read per project rather than guessed at.
A number in a report can be defended, because the detail behind it is one click away.
Real captures, not marketing mockups. Configuration and availability are confirmed during setup rather than promised on a page.
These are illustrative workflows, not customer results. We do not publish outcome claims without approved customer material.
A month closes with a revenue total that looks healthy. Reading the four states separately shows that a meaningful share of that value was quoted and delivered but never invoiced, so the cash never arrived. The work is not lost — it is now visible as a billing gap with a client and a project attached, which is a solvable problem in a way that a revenue figure is not.
One project is completed and everyone involved remembers it as a success. The economics view compares what was quoted against what was billed for the same scope and shows the gap. Because the comparison is per project rather than per year, it becomes a scoping conversation for the next similar job instead of a general feeling that the team should try to be more careful.
An invoice from several months ago is buried in a total that looks acceptable because everything else is current. Ageing pulls it out as the oldest line on the outstanding list, and the payment promise attached to it gives the follow-up a date to refer to. Chasing stops depending on who happened to remember.
Every part of NoxOrigin has awkward edges. Naming them now is cheaper than discovering them in month two.
Billed is the value invoiced and outstanding for collection. Collected is the value actually recorded as received. They are separate states on purpose, because the difference between them is receivables — the number most businesses cannot see clearly.
No. Reports covers project economics, client money, receivables ageing, and day-to-day reporting over what NoxOrigin already holds. Statutory accounting, ledgers, and filing stay with the tools built for them, and this is where the data they consume comes from.
Yes — project economics compare quoted value against billed value for the work delivered. It is a commercial view of your own projects, not cost accounting; how much of your cost base is genuinely recorded affects how meaningful the margin is.
Reading reports is a permission, so an admin role can review reporting for a branch or client without being able to raise quotes, invoices, or payments. Money actions stay explicitly gated.
Yes. Every figure has a path to the underlying client, project, invoice, payment, or day-to-day activity, which is what makes a reported number defensible in a conversation rather than merely plausible.