TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
№ 390 Case Study — Tax

Two years of invoices had no HST on them and nobody had noticed

Sampath called us thinking he had a simple registration question. Once we looked at what his cousin's spreadsheets actually showed, it was clear he had been billing well past the point where registration stopped being optional.

Tax8 min readRockland, OntarioRegistration threshold problems
All Tax case studies
ClientSampath, an incorporated consultant advising small commercial cleaning companies
The issueTwo years of invoices billed without HST after crossing the registration threshold, followed by a client refusing to pay it retroactively
ServiceRebuilt the accounting to establish the true numbers, then negotiated the retroactive HST directly with the affected client
ResolutionA partial recovery, with the client covering roughly half the retroactive HST and Sampath absorbing the rest

The situation

Sampath's first call to our office was short. He said he thought he might need to register for HST and wanted to know how to go about doing it. It sounded like a five-minute administrative question, the kind that gets answered and forgotten. It was not one, though neither of us knew that yet, and Sampath least of all.

Sampath had incorporated a small consulting practice a few years earlier, advising commercial cleaning companies around Rockland on scheduling, staffing and contract pricing, work he had learned firsthand from years spent as a commercial cleaner himself before he ever thought about consulting. The business grew slowly at first and then, over about eighteen months, considerably faster, as word spread among a handful of cleaning company owners who liked, very concretely, what his advice did for their margins.

He had never registered for HST at any point. In his first year, revenue was low enough that registration remained optional, and he had simply never circled back to it once it stopped being optional a year or so later, largely because nobody had ever told him plainly that it had. His cousin Dilshan, a factory technician with no bookkeeping background whatsoever, had been helping him track invoices in a shared spreadsheet on evenings and weekends, more out of family loyalty than any real expertise, and the spreadsheet did not distinguish cleanly between years, between clients, or between what had actually been paid versus what had merely been invoiced and was still outstanding.

When Sampath finally asked us the registration question, it took very little digging on our part to see that he had crossed the threshold requiring registration well over a year earlier and had been invoicing every single client since then without charging HST at all. One of those clients, Halina, who ran a cleaning company he had consulted for quite extensively over that stretch, was about to become the center of the entire problem, because retroactively adding HST to work already invoiced and paid in full was not something she was willing to simply accept without a fight.

What the other side was relying on

Once a consultant crosses the small-supplier revenue threshold, registration for HST stops being optional entirely, and tax must be charged on services from that point forward, whether or not the consultant actually gets around to registering on time. Failing to register on schedule does not exempt the amounts already billed during that gap; it simply means the consultant becomes personally responsible for the HST that should have been collected, out of their own pocket, unless it can somehow be recovered after the fact from the clients who were genuinely underbilled at the time.

Sampath's exposure came from roughly a year and a half of invoices sent to several different clients, the largest single share of them to Halina's company, all issued without any HST charged at all. Once he finally registered, the only practical path to limiting his own personal loss was to go back to those clients and ask them to pay the HST that should have been added to those invoices from the start, since as a matter of principle it was always properly their cost to bear as the customer receiving the service, not his to absorb as the consultant providing it.

Halina refused outright. Her position, communicated to us through her own bookkeeper rather than directly, was that every contract she had signed with Sampath specified a flat, all-in project fee, with no separate line item for tax anywhere in the paperwork, and that she had budgeted and paid those fees in full precisely on that understood basis. She argued that going back more than a year later to add HST on top of amounts already fully settled was not something Sampath could simply impose after the fact unilaterally, particularly since some of the relevant invoices covered work that had finished many months earlier.

There was a genuine legal question buried inside that position, not simply a client being stubborn or difficult for its own sake. Whether HST can actually be recovered from a client after the fact, on invoices that never showed it originally, depends heavily on what the underlying contract actually said about pricing and tax at the time, and on what the invoices themselves documented in the moment they were issued. Because Dilshan's spreadsheet did not cleanly show which invoices related to which specific engagements or what exact contract language had governed each one, Halina's side was effectively betting that the underlying paper trail would not support Sampath's claim clearly enough to make a sustained fight worthwhile for either of them.

What we did

  1. Rebuilt the accounting entirely from source documents, going past Dilshan's informal shared spreadsheet to actual bank records, the original signed contracts, and every invoice genuinely sent to every client over the disputed period, because the spreadsheet alone was simply not reliable enough to build a serious claim on and we needed numbers that would hold up firmly if Halina's side chose to push back hard.
  2. Identified the exact date the revenue threshold was crossed, using the newly rebuilt revenue timeline organized month by month, which fixed precisely which invoices fell safely before registration became legally mandatory and which fell squarely after that date, narrowing the genuinely disputed period considerably from what Sampath had originally and rather anxiously assumed, and immediately shrinking the pool of invoices that could realistically be exposed to a retroactive HST claim.
  3. Reviewed every relevant contract's actual pricing language, client by client and clause by clause with real care, and found that most of them, including several of Halina's own signed contracts, described the fees in terms that left real room to argue tax was always intended to be additional, even though it had never once actually been charged that way in practice.
  4. Registered Sampath for HST effective from the correct date we had established through the rebuilt timeline, and filed all the outstanding returns covering the full period since, establishing his own compliance with the tax authority first and cleanly before turning to the considerably harder question of recovering any amount from his clients, since negotiating with Halina while his own filings were still outstanding would have weakened his position from the outset.
  5. Sent a formal written accounting to Halina's company, laying out the rebuilt invoice history in full detail, the specific applicable contract language for each individual engagement, and the exact HST amount attributable to her portion of the total, replacing the informal back-and-forth through bookkeepers with a properly documented and defensible written position that gave her side something concrete to actually respond to.
  6. Opened direct negotiations with Halina's own bookkeeper, deliberately focusing our pressure and our evidence on the specific invoices where the contract language most clearly supported Sampath's position, rather than pressing equally hard on every single invoice regardless of how thin its underlying paperwork actually turned out to be, since spreading the argument evenly across weak and strong invoices alike would have diluted the strongest points we actually had.
  7. Reached a split settlement covering roughly half of the disputed HST from Halina's company directly, reflecting honestly, on both sides, that some invoices carried far stronger paper support than others, and confirmed in writing that the remainder would stay Sampath's own cost to absorb going forward, closing the matter without either side needing to escalate a relationship both wanted to keep working.
  8. Set Sampath up with quarterly bookkeeping check-ins going forward, rather than the annual scramble he had been used to at filing time, so that any future crossing of a revenue threshold would be caught within weeks rather than discovered, as this one was, a year and a half after the fact and already costly, and so his invoicing could be corrected in real time rather than reconstructed after a client complaint.

The outcome

Halina's company ultimately agreed to pay a portion of the retroactive HST, tied specifically and only to the invoices where the contract language gave Sampath the clearest possible footing to insist on it. The remaining amount, tied to invoices with weaker documentation or contract language that read more ambiguously about tax, stayed Sampath's own cost, and he paid it out of pocket as part of bringing his filings fully current with the tax authority. The total genuinely in dispute across the whole matter stayed under fifteen thousand dollars, but for a small, one-person consulting practice, that number mattered a great deal to his cash flow that year.

This was not a full recovery, and we were careful not to frame it to Sampath as one at any point in the negotiation. Roughly half the shortfall came back from the client who owed it in principle; the other half he simply absorbed himself, in part because the accounting, before it was properly rebuilt, could not clearly prove exactly what had been agreed in every individual case. That gap is a real and lasting cost of letting bookkeeping run informally, between family members without training, for as long as his had been allowed to.

Sampath came out of the matter registered, current on every outstanding filing, and with a clean, defensible set of books going forward, prepared now by an actual bookkeeper rather than tracked in a shared spreadsheet passed between family members on evenings and weekends. Dilshan stayed involved in Sampath's life socially exactly as before, but stepped back from the books entirely, at Sampath's own gentle suggestion, once it became clear during the negotiation just how much the gap in the old records had ultimately cost him.

Halina, for her part, kept working with Sampath after the settlement, and the two of them agreed going forward that every new contract would spell out HST as a separate line item rather than folding it into a single flat number, closing off the exact kind of ambiguity that had made this dispute possible in the first place.

What you can learn from this

  • Once your revenue crosses the threshold that requires HST registration, the legal obligation applies from that point forward regardless of whether you actually get around to registering on time.
  • Failing to register on schedule does not erase the tax owing on past invoices already sent; it usually just shifts that cost onto you personally unless it can later be recovered from the clients who should have been charged all along.
  • Whether you can recover HST from a client after the fact often comes down entirely to exactly what your contracts and invoices said about pricing at the time, not to what seems fair to either side in hindsight.
  • Informal bookkeeping between family or friends, done without any real training, tends to blur exactly the details, the dates, the amounts, which contract applied to which job, that matter most once a dispute actually arises.
  • A rebuilt, source-document accounting carries far more weight in any negotiation than an informal spreadsheet ever will, even when the underlying numbers turn out, in the end, to be much the same.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a tax problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →