The Finance Calendar for a Company With a Non-December Year End

Companies end up with a non-December year end for good reasons. The business is seasonal and a December cut lands in the middle of the busy period. The corporation was set up at a particular time and the year end was chosen by whoever filed the incorporation. There was a tax reason at the time, and the reason may or may not still apply.

Whatever the reason, the consequence is structural and it is the thing nobody prices in advance: most of a Canadian company’s annual finance obligations do not move with its fiscal year end. A December year end company has one annual peak. A June year end company has two smaller ones, in different months, run by the same people, and if nobody maps them the second peak arrives as a surprise every single year.

This is the calendar we build for those companies, and the map that shows where the collisions are.

The three clocks

Every recurring annual obligation runs on one of three clocks. Sorting them is the whole exercise.

Clock	Anchored to	What runs on it
Fiscal	Your fiscal year end	Year end close, financial statement preparation, the practitioner’s engagement, the corporate income tax return and its balance, corporate income tax instalments, covenant tests and annual lender deliverables, the budget and planning cycle, inventory count, annual account analysis and reserve reassessment
Calendar	31 December, regardless of your year end	Payroll year end, the annual employment information slips, annual slips for dividends and interest paid, provincial payroll levy annual returns, workplace insurance annual reconciliations, most benefit plan renewals, most insurance renewals, and any obligation defined by a calendar year of remuneration
Period	Your own sales tax reporting period, and your own remitter schedule	Sales tax returns and payments, payroll source deduction remittances, and the annual sales tax reconciliation where one applies

The mistake to avoid is assuming clock two follows clock one. It does not. Payroll is a calendar year concept in Canada and it stays a calendar year concept no matter what your articles say your year end is. A company with an August year end still has a payroll year that closes at the end of December and an annual slip season in the winter that follows.

Note also that clock three may not align with either of the others. A quarterly sales tax reporting period is frequently aligned to the fiscal year and frequently is not, depending on how the account was set up and what has changed since. Confirm your actual reporting periods and remitter schedule with your practitioner and then write them into the calendar as fixed rows rather than deriving them.

Deliberately, no due dates appear anywhere in this piece. Every one of them depends on facts about your specific corporation, and putting a remembered date into a calendar is how a company misses one. Get each date confirmed once, then hard code it.

The collision map

Here is why the year end you have determines how uncomfortable the year is. The table maps the fiscal peak, which sits in the months after year end, against the calendar peak, which sits where it always sits.

Fiscal year end	Fiscal peak lands	Calendar peak lands	Collision
31 December	Winter and early spring	Winter	Full overlap. One enormous peak, and everything competes with everything, including the practitioner’s own busiest season.
31 March	Spring into early summer	Winter	Clean separation. Generally the easiest calendar to staff.
30 June	Late summer into autumn	Winter	Clean separation, with the fiscal peak running into the summer holiday period.
30 September	Late autumn into winter	Winter	Partial overlap. The tail of the year end work runs into the calendar peak. This is the calendar that most often goes wrong.

A December year end concentrates everything. A March or June year end genuinely separates the two peaks, which is the strongest operational argument for a non-December year end and one that rarely gets made when the year end is chosen. A September year end is the one to plan hardest, because the two peaks do not collide head on, they overlap at the edges, which is much easier to underestimate.

There is a second, quieter collision that the table does not show, and it is the one that damages quality rather than schedule. The fiscal peak is judgement work: estimates get revisited, reserves get reassessed, and someone has to think carefully about balances that were rolled forward without much thought for eleven months. The calendar peak is precision work: reconciling remittances to a payroll register and issuing slips that have to be right the first time, because correcting one afterwards is disproportionately painful. Those two modes do not share a brain well. When they land in the same fortnight, the judgement work is what gets compressed, because the precision work has a hard external date attached to it and the judgement work does not. That is how a year end file ends up with an accrual that nobody actually reconsidered.

The master calendar, in months relative to year end

Build the fiscal clock in relative months. Then overlay the calendar clock as fixed months. The result is a single sheet that works for any year end.

Relative month	Activity	Owner	Output
YE minus 3	Year end planning meeting with the practitioner. Confirm engagement type, framework, timetable, fee basis and the requested items list. Confirm any changes in the business that affect presentation.	Controller	Dated timetable, agreed
YE minus 2	Clean up the balance sheet accounts nobody looks at monthly: prepaid expenses, deposits, suspense, intercompany, shareholder accounts, old receivables, unapplied credits	Controller	Account analysis for each
YE minus 1	Confirm inventory count arrangements and instructions. Confirm capital asset additions and disposals are all recorded. Confirm accrual policies for the items that only get judged annually.	Controller and operations	Count instructions issued
YE month	The count. Cut off procedures for revenue, purchases and payroll. Freeze the period as soon as it is defensible.	Everyone	Cut off memo
YE plus 1	The year end close proper. This is not a month end close with more items; the reconciliations go deeper, the estimates get revisited rather than rolled, and every balance sheet account gets a supporting schedule rather than a tie out.	Controller	Working paper file, complete
YE plus 1 to 2	Fieldwork or the practitioner’s file review, depending on engagement type. Respond to queries within an agreed turnaround.	Controller	Queries closed
YE plus 2 to 3	Draft statements reviewed by the company. Management representations. Statements issued.	Owner and controller	Signed statements
YE plus 3	Corporate income tax return and any balance owing. Corporate law annual return, if yours is anchored to the tax year rather than the incorporation anniversary. Confirm which applies.	Practitioner, with company	Filed
YE plus 3	Lender annual deliverables. Reset the covenant calculation on the new audited or reviewed figures.	Controller	Delivered
YE plus 4	Post mortem. What was late, what was asked for that did not exist, and what goes into the monthly close so it is never a year end job again.	Controller	Revised close checklist
YE plus 4 to 5	Budget and plan for the new year. Instalment basis reviewed with the practitioner in light of the year just filed.	Owner and controller	Approved budget

The row that pays for itself is YE plus 4. Every year end produces a list of things the practitioner asked for that took two days to assemble. Every one of those is a schedule that should have been maintained monthly. Move three of them into the monthly close each year and within two years the year end stops being an event.

Overlaying the calendar clock

Now add the fixed rows. These sit in the same months every year regardless of your fiscal calendar.

Fixed activity	Approximate position	Note
Payroll year end procedures and reconciliation of remittances to the payroll register	End of the calendar year, into the early part of the following one	Reconcile before slips are produced, not after
Annual employment information slips	The winter slip season	Confirm the actual deadline each year
Annual slips for dividends and interest paid to shareholders and lenders	The same season	Frequently missed by companies that pay dividends irregularly
Provincial payroll levy annual return, where applicable	Anchored to the calendar year	Applies by province and by payroll size. Confirm applicability.
Workplace insurance annual reconciliation	Anchored to the calendar year	Reconcile to actual assessable earnings
Benefit plan renewal	Plan anniversary, usually calendar aligned	Budget impact lands in the middle of your fiscal year
Commercial insurance renewal	Policy anniversary	Put the renewal date in the calendar, not the broker’s reminder
Minimum wage and employment standards changes	Legislated dates, by province	Payroll and pricing consequence

Two habits make the fixed rows survive staff turnover. The first is to record, beside each row, the source that proves the date rather than the person who remembers it: the plan document, the policy schedule, the practitioner’s confirmation. A calendar whose authority is somebody’s recollection stops being trustworthy the week that person is away. The second is to note the financial consequence beside each row as well, because several of these items land as budget events in the middle of a fiscal year and are treated as surprises when they arrive. A benefit plan renewal that raises employer cost is entirely predictable in timing and entirely unpredictable in amount, and a company that has the timing written down at least gets to ask the question early.

One further row that is easy to forget: any obligation defined by a calendar year of remuneration will also drive a reconciliation of what was remitted against what was owed. Reconcile before the annual slips are produced rather than after. Correcting a remittance is administrative. Correcting a slip that has already gone to an employee is a different and much slower exercise, and it usually surfaces during the exact fortnight the fiscal peak is running.

Staffing the two peaks

The reason to draw all of this is to answer one question: in which months is the finance function oversubscribed?

1. Mark the four months of the fiscal peak on a twelve month grid.
2. Mark the two or three months of the calendar peak on the same grid.
3. Mark every sales tax filing month and every remittance date.
4. Mark statutory holidays and the weeks your key people take leave.
5. Any month carrying two of the first three is a month where nothing discretionary gets scheduled. No system implementations, no chart of accounts changes, no software migrations, no process redesign.

Point 5 is the deliverable. Most failed finance projects at this size failed because they were scheduled in a month that was already full, and nobody had a picture that showed it was full.

A second consequence worth naming: your practitioner has their own peak, and for many Canadian practices it sits in the late winter and early spring. A June or September year end company that books its fieldwork for that window is competing for attention with every December year end client the practice has. Book against your own calendar and theirs, and book it a quarter ahead.

If you are considering changing your year end

Do not treat this as an internal decision. Changing a corporation’s fiscal year end has filing consequences, generally requires approval rather than being a matter of choice, and produces a short fiscal period that complicates every comparative figure you have for the following two years. Lender covenants tested on a trailing basis need attention as well, because a short period changes what “trailing twelve months” means.

The correct sequence is practitioner first, lender second, bookkeeper last. The operational case for a change, which is real, is that a year end sitting three or six months away from the calendar peak turns one impossible month into two manageable ones. Whether that case survives the tax and filing analysis is not something to decide from a calendar.

What we do not do

We do not put a due date in a calendar without confirming it for the specific corporation. We do not assume the sales tax reporting period follows the fiscal year. We do not schedule a system change into a collision month, no matter how quiet the month feels when it is being planned six months out. And we do not run a year end as though it were a bigger month end; the two are different exercises with different evidence standards, and treating the first as the second is the reason year end files come back with queries.