The Report Nobody Opened and the Record Nobody Chased
Reporting nobody reads and follow-up nobody does have the same cause and the same fix. What a system has to do to be worth opening on a Tuesday morning, and why a number requiring no decision is a screen rather than a report.
Two failures sit next to each other in most small businesses and are almost always discussed separately. On one side, a report is generated, sent, filed, and never opened by anybody. On the other, an invoice has been outstanding for a long time and nobody has chased it. Owners treat the first as a reporting problem and the second as a collections problem, and both treatments are wrong, because the two failures have the same cause and the same fix.
The cause is that neither the report nor the record carries anything that requires a decision. They present state. Outstanding is shown as a number, which is the most passive thing a screen can show. Nobody is told what is about to become a problem, by how much, or what happens if nothing is done this week. So the report is closed and the invoice is not chased, and in both cases the person closing the screen had nothing to act on.
This article is about what a system has to do to be worth opening on a Tuesday morning, and why the same properties that make a report readable make an outstanding record chaseable. It is deliberately not a list of features. A feature list cannot fix the fact that a screen shows a number instead of a decision.
One cause, two symptoms
A report nobody opened and an invoice nobody chased look like separate problems because they live in different parts of the business and different parts of the system. They are the same problem, which is that the system reports state instead of proposing an action. State is descriptive. Action is prescriptive, and only one of the two makes somebody move.
There is a second reason the two travel together, and it is less obvious. Both are tasks that nobody owns at the moment they matter. A report with a named recipient and a required response is a task that gets done, whether or not anyone found it interesting. A report with no recipient and no response is a document, and documents do not get done. An invoice that nobody has to follow up on is a record; an invoice assigned to a person with a next action on it is a task, and tasks get chased.
Which is why a business can have a functioning receivables report and still be surprised by a customer who paid late for a fifth time. The report was not wrong. It was correct, complete, and addressed to nobody, on a day when nothing in it required a decision. Correctness was never the missing ingredient.
A worked example, constructed for this article
A worked example, constructed for this article
Every figure below is invented. None of it describes a real business, and none of it is a benchmark.
An invoice dated the third of the month carries a taxable value of 10,000. The 18% GST rate is used here only so the total can be checked by hand:
- 10,000 x 0.18 = 1,800 of tax
- 10,000 + 1,800 = 11,800 invoice total
A payment of 5,000 has been received and allocated against it. An invoice and a payment are different records, so the invoice does not carry a paid field. Whether this invoice is paid is a projection of the allocations recorded against it, and the projection of what is outstanding is:
- 11,800 - 5,000 = 6,800 outstanding
Today is the nineteenth. Days outstanding are 19 - 3 = 16 days, which puts the invoice in the second ageing bucket rather than the first. That is a change of position, and it is the only thing on the screen that has actually happened.
Now the part most ageing reports skip. If somebody wants the tax component of what is still outstanding, dividing the remaining total back down gives:
- 6,800 / 1.18 = 5,762.71 taxable
- 6,800 - 5,762.71 = 1,037.29 tax
The decimals are the point. A partial allocation against a taxed invoice does not split cleanly into a clean taxable remainder and a clean tax remainder, and a report that shows a rounded 900 of tax is showing a number that does not describe anything. Whether that treatment is right for your own books is a question for your chartered accountant, not a question this article answers. What the arithmetic establishes is that the four figures a receivables view displays are not interchangeable, and a reader who cannot see that will add them together.
The obvious fraction is deliberately not printed. The share of invoices not chased is a statistic about a business that does not exist. What can be said is arithmetic: 6,800 of a total of 11,800 is outstanding, 16 days have passed, and the report that displayed all of this asked nobody to do anything.
Look at what the constructed report does not say. It does not say this customer usually pays on time, or that this is the third late payment, or that a call on Monday costs nothing and a call on the twenty-eighth costs the relationship. All of that information may exist somewhere, and none of it is on the screen. The reader is left to convert a correct figure into a judgement, which is work, and work that gets skipped is exactly the behaviour the business is trying to change.
This is also where the two failures converge. A receivables report is a report. A single outstanding invoice, viewed on its own, is a record. Both are correct. Both require a reader to supply the decision. In a business with enough volume, the report gets opened by somebody whose job is reviewing, and the invoice gets chased only if that review happens to reach it. When volume grows, the review becomes the bottleneck, and the items that fall through it are the ones that looked least urgent, which are frequently the ones that turn out to be oldest.
What a system has to do to be worth opening on a Tuesday morning
A Tuesday morning report earns its place by being short and by requiring a decision. Long is not the problem; unfocused is. A page with forty figures is easier to ignore than a page with one, because a page with one makes the reader personally responsible for what happens next, and people are quite good at not being personally responsible for things.
The second property is a position rather than a total. What has changed since the last time anyone looked is the only part of a report that is news. Everything else is context, and context belongs further down where it can be reached if it is needed. A report whose headline is this month's total is a report whose headline has not changed in a month.
The third property is that the answer to so what is visible without a second query. A number that crosses a threshold, an item that has moved bucket, a variance that exceeded what was expected, a record that has no next action attached. Each of those is a reason to open the page, and each of them can be computed from records that already exist rather than from a report somebody has to build.
Four properties that decide whether a screen gets opened
One thing, not forty
A screen that needs a decision should carry one question. A page of figures transfers work to the reader, and transferred work is skipped work. Context can sit underneath; the top of the screen should be the thing that changed and the thing that follows from it.
A position, not a total
The headline should be what is different from the last look: an amount that crossed a line, an item that moved bucket, a variance that grew. A total that has not changed in a month is not news, and readers are accurate about which parts of a screen are news.
A named next action with a date
A record with an owner and a next action on it gets worked. A record without one gets looked at. This is the difference between a collection list and a list of things that are overdue, and it is the cheapest single change in the whole of collections.
A basis you can name out loud
Invoiced, collected, outstanding and quoted are four different quantities. A view that shows them without saying which is which invites a reader to add them, compare them or treat one as the other. Naming the basis costs nothing and prevents the most expensive misreading there is.
Illustrative comparison: a screen that gets opened and a screen that does not
| The screen that gets opened | The screen that does not | |
|---|---|---|
| What is at the top | One item that has changed position, with the amount attached. | The month's total invoiced, which has not moved in three weeks. |
| What the reader has to do | Decide something: call, escalate, write off, or leave it with a reason. | Nothing. The figure can be noted and the page closed. |
| What it says about the basis | Outstanding as a projection of recorded allocations, as at a stated moment. | Collected, invoiced and outstanding on the same screen, unlabelled. |
| What happens on the second week | The item either moved or somebody recorded why it did not. | The same page is generated, and this time it is opened even later. |
| If the figure is wrong | The reader can find the record and correct it. | The reader has no path to the underlying records, so the figure is simply accepted. |
What a record has to carry to be worth chasing on a Tuesday
- An amount, and the basis it is on: invoiced, collected, outstanding or quoted, named rather than implied.
- The allocations behind it. Since paid is a projection rather than a stored field, the outstanding figure has to be reconstructable from the payments recorded against it.
- A date the clock starts from, and days outstanding computed from that date rather than remembered.
- A position in an ageing structure, so a move between buckets is visible as an event rather than inferred at the end of the month.
- A named person who owns the next action, and the date that action is due.
- A history of what was already tried, so the next call is not the first call.
- Enough of the customer's pattern to make the judgement cheap: what they normally do, as far as the records actually show it.
The same reason the invoice was not chased
It is worth saying plainly that this is not primarily a software problem. Most outstanding invoices are not chased because nobody has been made responsible for chasing them, and no screen changes that unless the responsibility is written down somewhere. What the system can do is make the responsible person obvious, make the next action a thing with a date rather than an intention, and make the history of what was tried available to whoever picks it up next.
What the system cannot do is decide when to stop chasing. Writing off, escalating, splitting a payment, or accepting a customer who is going to be slow for a while are all judgements with a commercial cost attached. They belong to a person, and the useful thing a record does is give that person the facts in one place instead of three.
There is one more reason a report can go unread, and it is embarrassing but common: the reader does not trust it. If the last three months of figures have had to be explained, adjusted or quietly not sent, the fourth month will not be opened either, no matter how good it is. Rebuilding that trust is not a formatting exercise. It is a matter of shipping figures that carry their own basis and their own exclusions, so that a reader can check one without having to ask.
What the platform does and does not do here
There is no BI tool here, no dashboard builder, no custom report builder, no scheduled report delivery and no data-warehouse sync. Reporting is a set of standard views over the records. That is a real limitation and it has a consequence worth naming: a report shaped exactly for one business is something we would scope rather than something a customer configures on a Tuesday afternoon. If your Tuesday-morning screen does not exist, it will not appear by configuring a tool that does not exist.
What does exist is a receivables view over real records, where outstanding is a projection of allocations rather than a field somebody typed, and a shift close and day-end reconciliation routine that makes the money side of a day defensible. Reassuring a reader that these are self-serve switches would be dishonest: shift close and
A scope change is a NEW quote on the same project, because there is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature. So a report about delivery cannot show a change agreed mid-project, only the quotes that exist. There is no timesheet record and no payroll module. Expenses live in Nox-Billings only and purchasing in Commerce. Nothing here files GST returns or any other statutory return, so any report that appears to be preparing a filing is not doing that. And there is no onboarding team, no implementation project, no training course, no data-cleaning service and no dedicated support tier beyond the documented platform support; getting a team to open a screen on Tuesday is work, and migration is scoped work.
The test for a Tuesday morning is simple and slightly brutal. Open the screen, and if you cannot say what decision you are making within a minute, the screen is not earning its place. Every figure below that line is context, and context is allowed to be long as long as it is not in the way.
For the mechanics of reading a receivables view properly, see Reading a Receivables Ageing Report. For what to do when the customer disputes rather than pays, see When the Customer Disputes the Invoice. And for the first week of actually using a new system, see What to Do in the First Week with a New System.
Frequently asked questions
Why does nobody open my reports?
Usually because they do not require a decision. A report that shows a total asks the reader to supply the judgement, and work that gets transferred to the reader gets skipped. A screen that leads with one thing that has changed, and makes the next action obvious, gets opened because it is news rather than because somebody was reminded.
Are these two problems really the same problem?
In most businesses, yes. A report nobody opened and an invoice nobody chased are both cases of a correct figure that nobody has to act on. The common cause is that the item has no named owner and no next action with a date attached to it, so the report is a document and the invoice is a record rather than a task.
Why is the tax component of an outstanding invoice not a round number?
Because a partial payment against a taxed invoice does not split cleanly. In the constructed example, 6,800 remaining against a 1.18 inclusive total gives 5,762.71 of taxable value and 1,037.29 of tax. Whether that treatment is correct for your books is a question for your chartered accountant; the arithmetic is shown only so a reader can see why a rounded figure is misleading.
Can I build my own report and schedule it to be sent?
No. There is no BI tool, no dashboard builder, no custom report builder and no scheduled report delivery. Reporting is a set of standard views over the records. A bespoke report is something we would scope rather than something you configure yourself.
Do I need an implementation project to get my team opening these views?
There is no onboarding team, no implementation project, no change-management programme, no training course, no data-cleaning service and no dedicated support tier beyond the documented platform support. Some setup steps, including shift close and day-end reconciliation, are assisted-setup maturity rather than self-serve switches, and merge behaviour is a setup decision with a person reviewing every candidate. Migration is scoped work.
Does this article give tax or compliance advice?
No. The 18% GST rate appears only so a constructed invoice total can be checked by hand, and the worked example deliberately shows a tax figure that does not divide cleanly so the reader can see why rounding is misleading. Filing and classification are questions for your own chartered accountant. NoxOrigin does not file GST returns or any other statutory return.