What the Accountant Saw Chapter 4 - How to Hide a House

WHAT THE ACCOUNTANT SAW

Chapter 4 – How to Hide a House

Whislt the normal adage is, there are lies, damn lies and statistics, there are also rules, and then there is the way people live around those rules, and anyone who has spent enough time in small business eventually realises that the space between those two things is where most of the real stories sit. It is rarely the blatant, headline-grabbing fraud that defines the profession; far more often it is the quiet, incremental behaviour that lives in the grey, justified one decision at a time until it becomes something that, when viewed in its entirety, no longer quite fits within the system it was meant to operate under.

This chapter sits in that space, not to sensationalise it, but to acknowledge it for what it is, common, explainable, and deeply human.

The anecdote that gives this chapter its name did not begin with a grand plan to deceive. Like most things of this nature, it began with a series of entirely reasonable steps taken by someone who had worked hard to reach a point where life was becoming a little more comfortable. He was in the building game, not one of the large operators who attract attention, or even an actual builder for that matter, but someone in the periphery who had scraped his way to a level of steady success, enough to start thinking about what came next for his family.

A block of land was purchased, which in itself raised no questions. Plans were drawn, again entirely unremarkable. What followed, however, was not the typical process of engaging trades, costing a project, and building within a clearly defined framework. Instead, over a number of years, a house simply began to appear, gradually taking shape in a way that, if you drove past at any given point, would look no different to any other home being constructed in the suburbs.

The difference was not in what was built, but in how it was built, and more importantly, how it was recorded.

Materials did not arrive in large, identifiable batches tied to a single project. They came through the same supplier accounts the business used every day, ordered in the same way, invoiced in the same way, and paid for in the same way. On the surface, there was nothing to distinguish these transactions from the hundreds of others that flowed through the business as part of its normal operations. Timber, concrete, fittings, fixtures, all of it moved through the system in a manner that appeared entirely consistent with industry norms.

But when you looked more closely, or perhaps more accurately, when you asked the right question, something was missing, and it was not the sort of absence that announced itself loudly. It did not jump off the page like the proverbial “dog’s balls,” as we might say in the vernacular. In fact, to anyone reviewing the file without context, it would have appeared entirely unremarkable, just another set of numbers in an industry where variability is the norm and precision is often more aspirational than real.

What made it different, at least for me, was not something the system told me, but something I already knew.

I knew the client. I knew his business. I had a sense, built over years of conversations and observations, of how his work flowed, what types of jobs he took on, where his margins typically sat, and how his operations translated into numbers. There is a rhythm to a business when you are close enough to it, an underlying pattern that, while never perfectly consistent, tends to move within a recognisable range. And this sat just outside that range.

Not enough to alarm, not enough to trigger any formal concern, but enough to create a quiet dissonance. The sort of feeling that something doesn’t quite line up, even if you can’t immediately point to a single transaction and say, “That’s the issue.”

So you start to ask questions, not in an accusatory sense, but in a way that seeks to reconcile what you expect to see with what is actually there.

What have overall margins fallen? Where is this job? What is driving these material costs? How does this reconcile to the work being invoiced? And when you follow those questions through, what becomes apparent is not what is present, but what is absent.

There was no job file that accumulated the cost of building this house, no central point where all of those inputs came together to tell a coherent story. There was no client to invoice at the end of the process, no debtor sitting on the balance sheet waiting to be converted into income, no moment where the effort translated into revenue. There was no direct margin to recognise, not that this business thrived on that area of reporting, no profit event that would bring the entire exercise into the light of the profit and loss statement.

Instead, the costs simply… dissipated. They were absorbed into the broader activity of the business, spread thinly enough across legitimate jobs that they never created a spike large enough to attract attention. Each individual transaction could be explained, justified, and, in isolation, accepted. It was only when you stepped back and looked for the thread that tied them together that the absence became visible. And that, in many ways, is the point. Because the system is not designed to think; it is designed to process. It relies on patterns, thresholds, and comparisons, looking for deviations that fall outside expected parameters. If the numbers remain within those parameters, even if only just, the likelihood of scrutiny diminishes significantly.

But people do think, or at least they sense.

If I could see it, not because it was obvious, but because it didn’t quite fit with what I knew to be true, then the question naturally follows: why wouldn’t someone else see it? Perhaps not immediately, perhaps not in the same way, but over time, with enough exposure, enough comparison, enough curiosity, these things have a way of surfacing.

That is the risk that sits behind this type of behaviour, not that it is blatant, but that it is just noticeable enough to linger in the mind of someone paying attention. And once it lingers, it invites a closer look, and it is in that closer look that the absence, the missing pieces, begin to form a picture that the numbers alone were never quite telling.

The entity itself never reported a loss. Tax returns were lodged on time. Income was declared, and tax was paid. From the outside, and even from a reasonably competent audit that relied on comparative industry benchmarks, everything appeared to sit within acceptable parameters. It was not an outlier, and in an industry already known for its variability, that in itself was enough to avoid scrutiny.

And so, over time, the house was built, not hidden in the traditional sense, but never quite acknowledged for what it was within the system that had funded it.

What made this particularly interesting was not the mechanics, because once understood, they are neither unique nor especially complex. What lingered was the mindset that sat behind it, the quiet certainty that this was not really wrong, just… efficient. The justification was never framed in terms of avoidance or deception, but rather in terms of fairness, of having paid enough tax already, of using what was available within the structure of the business to achieve a personal outcome.

“I’ve paid my taxes,” was often the line, and in a narrow sense, that was true. Just not on everything that perhaps should have been captured.

This is where the conversation becomes less about accounting and more about interpretation, because the legislation provides rules, but it cannot fully account for intent. It tells you what is deductible, what must be declared, how transactions should be treated, but it does not sit in the room when decisions are made, nor does it hear the internal dialogue that turns a questionable action into a justifiable one.

It would be easy to confine this type of behaviour to industries like construction, where the physical nature of materials and the fluidity of job costing create opportunities for this kind of blending. But that would be missing the broader point, because the principle at play is not tied to bricks and timber; it is tied to proximity. The closer a business sits to the personal life of its owner, the easier it becomes for those boundaries to blur, often without any conscious decision to cross a line.

The medical profession provides a different, but equally telling, example. Here, the inputs are not materials but time, expertise, and access to resources that are tightly controlled and heavily regulated. On paper, it is an environment that should leave very little room for deviation, yet the same human tendencies emerge, just expressed in a different form.

A family member requires treatment, and the consultation is provided without charge. A procedure is performed using the practice’s resources, with no corresponding entry in the billing system. Time is given, care is delivered, and from a human perspective, the decision feels entirely appropriate. After all, family takes precedence, and the idea of formalising that interaction into an invoice can feel almost offensive.

Individually, these actions seem trivial, even commendable. Collectively, however, they begin to resemble the same pattern seen in the builder’s story, the use of business resources for private benefit, the absence of recorded income where services have been provided, and the gradual erosion of the boundary between professional activity and personal life.

The difference lies largely in visibility. A house stands as a tangible outcome, something that can be pointed to and questioned. The medical example exists in moments, in transactions that are small, dispersed, and far less likely to attract attention. Yet the underlying behaviour is remarkably similar, driven by the same blend of justification, convenience, and a belief that the system can accommodate these small deviations without consequence.

This is where the discomfort begins to settle, because the discussion is no longer about a specific client or a particular industry. It becomes a reflection on behaviour that is, in many ways, universal. The small decisions that feel reasonable at the time, the justifications that make them easier to accept, and the gradual shift that occurs when those decisions are repeated often enough to become normal.

As an advisor, these are not easy conversations to navigate, because the questions being asked are rarely as simple as they appear. On the surface, a client may be asking whether something is allowable, whether it fits within the rules, whether it can be justified if challenged. Beneath that, however, sits a different question entirely, one that is rarely stated but always present.

“Where is the line, really?”

For a long time, I found it easier to retreat into the technical, to talk about substantiation, audit risk, and legislative interpretation, because those are areas where the answers, while not always simple, at least feel structured. The numbers provide a language that is clear, defensible, and, most importantly, impersonal.

But the longer you spend in this space, the more you realise that the numbers are often just the vehicle, not the issue. The real conversation sits underneath, in the choices being made and the reasoning that supports them.

The house, in this context, becomes more than just a clever piece of accounting camouflage. It becomes a symbol of that broader dynamic, a physical representation of what happens when enough small, justifiable decisions accumulate over time into something that, while never overtly declared, was always there. And that, perhaps, is the most telling part of all.

You don’t hide a house by concealing it. You hide it by building it in plain sight, ensuring that every individual step looks normal enough that no one feels compelled to step back and look at the whole.

What makes that idea even more confronting is how uncomplicated it actually was. There was no elaborate scheme, no series of shell entities, no labyrinth of transactions designed to confuse or misdirect. In fact, if anything, the simplicity of it is what allowed it to work. Each decision, taken on its own, was almost mundane. A load of timber ordered here, a pallet of bricks there, a few fittings added to an existing supplier account. Nothing unusual, nothing that required explanation beyond the everyday workings of a business that dealt in those very materials.

It was not fraud in the cinematic sense. It was not the sort of behaviour that required planning sessions or secret meetings or a conscious decision to “beat the system.” It was, instead, a series of choices made in response to circumstance, to opportunity, and perhaps most powerfully, to a sense of necessity. The client wanted a home for his family. He had the skills to build it, the access to materials, and a business structure that, with a slight shift in perspective, could accommodate the process.

So he did. One step at a time, without ever needing to declare that this was what was happening. And that is where the discomfort sits, because when stripped back to its essentials, it becomes difficult to point to a single moment and say, “That is where it crossed the line.” There was no defining transaction, no single act that transformed the ordinary into the questionable. Instead, the line was crossed gradually, almost imperceptibly, as each small decision leaned just a fraction further into that grey space than the one before it.

From the client’s perspective, the outcome was straightforward. He ended up with his home, built with his own hands, funded in a way that felt efficient rather than deceptive, and supported by a business that continued to operate, report, and pay tax in a manner that appeared entirely acceptable. There was no sense of having “gotten away with something,” at least not in the way that phrase is usually understood. There was, instead, a quiet satisfaction in having made it work. 

And perhaps that is the part that lingers the longest. Because when the system is navigated in this way, when outcomes are achieved not through confrontation but through subtle alignment of opportunity and structure, it challenges the very idea of where compliance ends and behaviour begins. It forces a recognition that not all deviations from the ideal are driven by intent to deceive; sometimes they are driven by a combination of practicality, proximity, and the human tendency to justify what feels, in the moment, entirely reasonable.

The house still stands, as it always would have. Solid, visible, and entirely unremarkable to anyone who passes by. And yet, for those who understand how it came to be, it carries a different weight. Not because of what was done, but because of how easily it was done, and how many small steps it took to get there without ever drawing attention to itself.

That same ease is what sits at the heart of the cash economy, a space where the rules are not so much ignored as they are quietly negotiated, transaction by transaction, between people who understand exactly what is happening but choose, in that moment, to proceed anyway.

There is no great mystery to it. No one operating in that space is under any illusion about the nature of what they are doing. The language might be softened, “cash price,” “mates’ rates,” “do it off the books”, but the understanding is mutual and immediate. One party offers a discount, the other accepts, and both walk away with a sense of having gained something, even if that gain comes at the expense of a system they both, in other contexts, rely upon.

It is, in many ways, the simplest version of the same behaviour that built the house.

Instead of materials being absorbed quietly into a business, income is quietly kept out of it. The effect, however, is remarkably similar. The numbers tell a story that is close enough to reality to pass without question, but not quite complete. A portion is missing, small enough in isolation to feel insignificant, but meaningful when viewed over time.

And just like the house, it rarely begins with intent to deceive on a grand scale. It begins with convenience. A client asks, “Is there a cash price?”

The tradesman pauses, not because he does not understand the question, but because he is deciding whether this particular moment is one where the rules will be followed strictly or interpreted more loosely. The calculation is immediate and often unspoken. A slightly lower price secures the job, a slightly higher margin, unrecorded, improves the outcome, the paperwork disappears, and the transaction becomes quicker, cleaner, and, on the surface, mutually beneficial.

Everyone wins, at least in the short term, or at least that is the shared assumption that allows the transaction to proceed without too much reflection.

When you begin to examine it more closely, however, the idea of “everyone winning” starts to unravel, particularly when you bring GST into the conversation, because in modern Australia the ten percent GST has effectively become the benchmark for what a “cash discount” looks like. It is rarely articulated that way, but in practice that is what is being offered. The client sees a quoted price, mentally strips out the GST component, and accepts the reduced figure as a saving.

The problem with that thinking is that it assumes the GST is the only element in play.

From the contractor’s perspective, the GST is simply the beginning. By not declaring the transaction, they are not only avoiding remitting the GST; they are also removing the income from their taxable base altogether. That means the profit embedded in that job is not subject to income tax, and depending on the structure they operate through and their marginal rate, that saving can be significant. What is presented as a ten percent discount to the client may in fact represent a far greater benefit to the contractor once the full tax effect is considered.

In that light, the transaction begins to look far less balanced than it first appears. The client receives a modest, immediate saving, while the contractor captures a much larger, largely invisible gain. The symmetry that is implied in the phrase “cash deal” does not really exist; it is weighted, quietly but materially, in favour of the person providing the service.

There is also a second layer that rarely gets discussed, and that is the question of risk. By agreeing to a cash transaction, the client is effectively stepping outside the formal protections that come with a documented job. There is no invoice to rely on, no clear record of what was agreed, and very little recourse if the work does not meet expectations. The contractor, on the other hand, has secured both the job and the enhanced margin, with their primary exposure being the possibility of detection, which in many cases feels distant enough to be discounted.

So the question that emerges is not simply whether the transaction is acceptable, but whether the client is actually achieving what they think they are achieving. If the discount is only reflective of the GST, and the contractor is retaining the benefit of the avoided income tax, then the client is not sharing in the full economic effect of the arrangement. They are participating in it, certainly, but they are not the primary beneficiary.

That raises an uncomfortable but important point. Should a true “cash price,” if such a thing is to exist at all, reflect not just the GST that is avoided, but also the income tax that would have been paid on the profit? And if it did, would the transaction still feel as attractive, or would the economics begin to shift in a way that challenges the underlying justification?

These are not questions that are commonly asked, because the conversation rarely goes beyond the surface. The focus remains on the immediate saving, the convenience, and the shared understanding that this is simply “how things are done.” The deeper mechanics, the imbalance of benefit, and the longer-term implications are either not considered or quietly set aside in favour of the outcome.

The rationalisation that supports this behaviour is remarkably consistent. The system takes enough already, this is just evening things out, everyone operates this way at least to some extent, and therefore it cannot be that serious. Within that framework, the detail becomes less important than the narrative, and the narrative is one of practicality rather than compliance.

It is the same pattern that sat behind the house, just expressed in smaller, more frequent increments. A job here, a payment there, a decision not to issue an invoice, a decision not to request one. Each instance, taken in isolation, feels inconsequential, but over time those decisions accumulate into something much larger, a parallel economy that runs alongside the formal one, visible yet rarely challenged because it is so deeply embedded in everyday behaviour.

From an advisory perspective, this is where the difficulty lies, because the issue is no longer one of technical interpretation. The rules around GST and income tax are clear, and there is little ambiguity about what is required. What is far less clear is how those rules intersect with the lived experience of the people operating within them, and how the perceived benefits of bending those rules are weighed against the obligations they impose.

When a client raises the idea of cash work, they are not usually seeking a lecture on legislation. They are testing alignment. They want to know whether you see the world the way they do, whether you will challenge their thinking or quietly accept it as part of the landscape. Beneath the question sits a deeper one, rarely stated but always present, about whether any of this truly matters in the grand scheme of things.

And that is where the answer becomes uncomfortable, because in isolation it often does not appear to matter. One transaction does not shift the system, one decision does not alter the broader outcome, and the immediate benefit feels real enough to justify the choice. It is only when those decisions are repeated, across thousands of businesses and countless transactions, that the cumulative effect becomes visible.

From the client’s perspective, however, that accumulation is almost impossible to see. Each decision stands alone, each moment is judged on its own merits, and over time what began as an exception becomes routine. Routine becomes expectation, expectation becomes culture, and once it reaches that point, it is no longer questioned. It is simply accepted as the way things are done.

Which brings the discussion back, inevitably, to the house.

Because while the scale is different, the underlying dynamic is identical. A series of decisions, each one small enough to justify, each one subtle enough to avoid scrutiny, combining over time to produce an outcome that sits just beyond the intent of the system. It is not hidden in the traditional sense, nor is it openly declared. It simply exists, supported by a pattern of behaviour that, while individually unremarkable, collectively tells a very different story.

The house stands, solid and unremarkable to anyone passing by, while the cash continues to change hands in countless small transactions that mirror the same logic. In both cases, the line between what is allowed and what is accepted becomes increasingly difficult to define, not because the rules are unclear, but because the behaviour surrounding them has evolved in a way that makes that distinction easier to ignore than to confront.