Sales Tax as a Filing Operation, Not a Tax Question
Whether a filing is correct is a tax question, but whether it goes out on time with evidence behind it is an operations question.
Companies worry about the first question and fail at the second. The energy goes into whether a particular sale attracts tax, which is worth worrying about and which somebody qualified has to answer, while the return itself gets prepared in an afternoon by whoever is free, from a report run on dates nobody checked, against a ledger nobody reconciled, and filed by a person who will not be here next year.
Split the two apart and give them to different people. The determination belongs to the accountant who reports on your statements. The filing operation belongs to the finance function, it is a scheduled, evidenced, repeatable process like the payment run, and it should be boring. Nothing below tells you what is taxable, what rate applies, where you are required to be registered or when your particular return is due. Those are facts about your corporation, and an article that guessed at them would be worse than useless.
Who owns which question
Write this table down and give a copy to whoever prepares the return, because the failure it prevents is a capable bookkeeper making a determination in good faith at four in the afternoon.
| Question | Whose it is | How it gets answered |
|---|---|---|
| Is this transaction taxable, where, and at what rate | The company’s accountant | Once, in writing, and recorded in the file so the same answer is applied every period |
| Are we registered everywhere we are required to be | The accountant | Reviewed when the business changes, not when a return is due |
| Which reporting period and which remitter schedule apply to each of our accounts | The accountant confirms, finance records | Confirmed against the actual account, then written into the calendar as a fixed row and never derived again |
| When is this return due | Confirmed once for your accounts | Hard coded. A remembered due date is the most expensive thing on this list |
| Does the tax detail report agree with the ledger | Finance | The monthly reconciliation, before anything is prepared |
| Was the return filed inside the window | Finance | The calendar |
| Was the amount filed the amount paid | Finance | Two numbers, compared, in ninety seconds |
| Who approved this figure | A named person, every period | A signature or its electronic equivalent, kept |
| Where is the evidence in eighteen months | Finance | The period folder |
The top four rows leave the building. The bottom five never do. Most sales tax remediation work I have seen started in the bottom five: a return prepared from an unreconciled ledger, filed on time, wrong in a way nobody could reconstruct afterwards because the report it came from was never saved.
The calendar, anchored to your reporting period
Day 0 is the last day of your reporting period. Counts are business days. The whole sequence has to fit inside the window between period end and the due date for your accounts, so confirm that window once and then set the day numbers below against it rather than the other way round. If the window is genuinely tighter than the sequence, the gate moves earlier. The filing does not move later.
| Day | Step | Owner | Output |
|---|---|---|---|
| Period end minus 10 | The change scan. Anything in the period that is not the ordinary sale of the ordinary thing goes on a list and goes to the accountant | Controller, with the owner | A list, sent, before the return exists |
| Period end minus 3 | Housekeeping. Uncoded transactions cleared to nil, tax sitting in suspense resolved, nothing waiting in a drawer | Preparer | Uncoded queue at zero |
| Day 0 | The period ends. If it ends mid-close, the return waits for the lock | Nobody | A locked period, or a wait |
| Day 1 to 3 | Preparation. The detail report is run on the exact period dates and saved as a file. The return is prepared in the prescribed form. The working file is assembled | Preparer | Return prepared, report saved |
| Day 4 | The reconciliation gate. Binary, owned, and it either clears or it does not | Reviewer | Gate cleared, or an escalation the same day |
| Day 5 | Review by somebody who did not prepare it | Reviewer | Review notes, kept |
| Day 6 | Approval of the figure by the person accountable for it | Owner or officer | Approval, recorded |
| Day 7 | File and pay. Capture the confirmation at the moment it appears on screen | Preparer | Confirmation number, payment reference |
| Day 8 | Evidence and clear down. Everything into the period folder, the payable moved off the accumulation account, the next period opened on the schedule | Preparer | A closed folder |
Two rows carry most of the value and neither of them is the filing.
Period end minus 10 is the row that prevents the expensive kind of error. The list is short and it is written by somebody who knows what happened in the business, not by somebody reading the ledger. A new province of operation. A first sale to a different kind of customer. An intercompany charge that started this quarter. A sale of equipment rather than of what you sell. A new supplier arrangement that changes who is invoicing whom. None of those is a finance judgement and all of them are visible ten days early to anyone who asks. Sending that list to the accountant before the return exists costs ten minutes and converts a determination made under time pressure into a determination made properly.
Day 8 is the row that gets dropped first and matters most eighteen months later. A filed return with no saved report behind it cannot be defended, explained or reproduced. The person who could have explained it from memory has moved on, and the memory was never evidence anyway.
The gate
The gate is not a review of the return. It is a check on whether the return is entitled to exist yet. Six things must be true, and the answer is yes or no.
- The period is locked in the ledger and the trial balance in use was exported after the lock.
- The tax detail report was run on the reporting period dates, not on the calendar month, and it has been saved as a file rather than left re-runnable.
- The control account reconciles, with every difference itemised and no unexplained residual. That reconciliation is its own monthly exercise and it happens whether or not a return is due this period.
- The previous period’s return, its remittance and its confirmation are all in the previous period’s folder.
- Every determination question raised in the change scan has come back with an answer, or the return applies an answer given previously and the open question is written on the file rather than resolved by the preparer.
- The approver has seen the reconciliation, not only the return. An approver who signs the form without the tie-out behind it is a signature, not a control.
If any of the six is false, the gate has not cleared and the escalation happens that day.
When the gate does not clear
The point of putting the gate on day 4 rather than on the due date is that a problem found on day 4 still has choices attached to it. A problem found on the due date has one.
What finance does when the gate fails is fixed, and it is not to make a decision. Write down the amount at issue, what is unresolved, what the deadline is, and what the realistic options appear to be. Send it the same day to the accountant and to the person who approves the filing. Then do what they decide, and record the decision and who made it in the period folder next to the return.
That last part is the piece people skip, and it is the piece that matters in two years. A judgement call made under time pressure and documented is a defensible position. The same call, undocumented, is indistinguishable from carelessness by anybody looking at it later, including the person who made it.
The honest version of this is uncomfortable for small companies and worth saying plainly. If one person prepares the return, approves it, files it, pays it and holds the only copy of the report it came from, you do not have a filing operation. You have a habit, and it ends the week that person leaves. The minimum viable split is that somebody other than the preparer looks at the figure and the tie-out before it goes, even if that somebody is the owner and even if the look takes four minutes. See the segregation matrix for how the same problem is handled everywhere else in the cycle.
The rows that are not every period
A filing calendar that only contains filings goes stale, because the things that make a filing wrong are annual or event driven.
| Row | Trigger | Who |
|---|---|---|
| Confirm the reporting period and remitter frequency on each account | Annually, and immediately on any correspondence from a tax authority that mentions either | Accountant confirms, finance writes it into the calendar |
| Re-run the change scan against the whole year rather than the period | Annually | Owner and controller, sent to the accountant |
| Tie the ledger for the full year to the sum of the returns actually filed | At year end, before the file goes to the practitioner | Finance prepares, accountant reviews |
| Any annual reconciliation or annual return your accounts require | Where one applies. Confirm whether one does | Accountant |
| Review who can file and who can release the payment | Annually and on any departure | Owner |
| Reissue the calendar for the new year with every date reconfirmed | Annually | Controller |
The year-end tie is the one that pays for itself. Twelve monthly reconciliations that each closed cleanly still need to be added up once against the returns, because a difference can be correctly explained in every individual month and still mean the year does not agree with what was filed. Doing it before the file goes out is a morning. Doing it because the practitioner found it is a fortnight, at the worst time of the year.
Where your filing periods sit against the rest of the annual workload is a separate exercise, and it matters more than it sounds, because filing periods do not necessarily follow your fiscal year and frequently do not follow the calendar either. The three clocks and the collision map cover that layout. What belongs here is only the instruction to put every filing period on that grid as a fixed row, taken from the confirmed account rather than assumed from the year end.
What we do not do
We do not determine what is taxable. Not once, not as a favour, not when the answer seems obvious and the deadline is tomorrow.
We do not prepare a return from a period that is still moving, and we do not file one on the basis that the figures will be corrected next period.
We do not accept a due date that came from anywhere other than the account itself, and we do not carry a due date forward from another company because the two look similar.
And we do not let the preparation, the approval and the payment sit with one person where there are two people available, because the tie between what was filed and what was paid is the cheapest control in the whole cycle and it happens automatically the moment those two acts belong to different hands.