A calendar year runs January 1 through December 31, while a fiscal year is 12 consecutive months ending on the last day of any other month — with a 52- or 53-week variant available. Pick one, adopt it, and every count after that lands where your records expect it.
- A calendar year is 12 consecutive months from January 1 to December 31; a fiscal year ends on the last day of any month except December 31.
- The fiscal-year family includes a 52- or 53-week variant that can be elected if you keep books and report on that basis.
- Under the periodic inventory system, inventory is updated at the end of the period to match the physical count for the balance sheet.
- In Business Central, one average cost period and one average cost calculation type are allowed in a fiscal year.
- Once adopted, hold the year type steady so counts, closes, and reports stay on the same window year after year.
A stock count only matches your books if both sit on the same 12 months. The calendar year runs January through December. The fiscal year ends on any other month's last day, plus a possible 52- or 53-week variant.
This is for the owner of an independent shop, the manager who schedules the count, and whoever closes the books when the count is done. The choice is one decision with real follow-on effects: when you count, when you close, how average cost behaves, and what the periodic update actually does to inventory numbers.
Before any count is scheduled, two definitions matter, because they set the frame for everything below. A calendar year is 12 consecutive months beginning January 1 and ending December 31, according to the IRS Publication 538 page on accounting periods and methods. A fiscal year is 12 consecutive months ending on the last day of any month except December 31, from that same IRS page. There is also a 52- or 53-week variant inside the fiscal-year family. The IRS page describes a fiscal year, including a period of 52 or 53 weeks, as its own category.
1. Know which of the two year types your shop already runs
Your shop already runs one of the two types, whether or not anyone wrote it down. Check the close dates you have actually used. If every one of your closes fell on December 31, you are on a calendar year. If your closes fell on, say, a June or September boundary, you are on a fiscal year ending that month.
This matters because the year type is not a preference you change each quarter. The IRS page states that if you adopt the calendar year, you must maintain books and records and report income and expenses from January 1 through December 31 of each year. That is a commitment, not a suggestion. Whatever you adopt, your records follow it.
If you have never formalized anything, your default pattern still counts as a pattern. Look at your prior reports. The months you have been closing already tell a reader which type you are running.
Two things people confuse at this stage. Second, a fiscal year may be a period of 52 or 53 weeks; the IRS page notes you can elect to use a 52-53-week tax year if you keep your books and records and report income and expenses on that basis.
2. Write down the 12 months you will count against
Once you know your type, write the exact 12 months on paper. A calendar-year shop writes January 1 through December 31. A fiscal-year shop writes its own start and end dates, ending on the last day of its chosen month.
The IRS page is direct on the calendar-year commitment: you must maintain your books and records and report income and expenses from January 1 through December 31 of each year. If you write those dates where the team can see them, nobody has to guess at count time.
For the fiscal-year shop, the same page gives the boundary rule: a fiscal year is 12 consecutive months ending on the last day of any month except December 31. So a fiscal year ending March 31 starts April 1. Write that pair down. The start date and the end date travel together.
If you are electing the week-based variant, write the closing day of the week as well. The IRS page says you can elect to use a 52-53-week tax year if you keep your books and records and report income and expenses on that basis. The election works only if the reporting follows the same basis.
This is a good moment to give the paper to whoever will close the count. Two people holding different 12-month windows is how a count ends up in the wrong period.
3. Match the count to the period so the periodic update has something to land on
The count itself is an event; the period is the frame that receives it. Under the periodic inventory system, inventory is updated at the end of the period to adjust numbers to match the physical count and provide accurate merchandise inventory values for the balance sheet, according to the OpenStax principles of accounting page on periodic cost of goods sold and ending inventory. Scheduling it there keeps the count and the update in the same frame.
That single sentence from OpenStax carries a practical consequence. If your period ends December 31 and your count happens in November, that November count is an extra look rather than the period-end count that aligns with the update. If your period ends the last day of your fiscal month and your count runs the last week, the count and the update sit together.
Here is how the two year types place that window.
| Year type | 12-month window | Where the periodic update lands | Source |
|---|---|---|---|
| Calendar year | January 1 to December 31 | End of the period (OpenStax) | IRS Publication 538 for the window; OpenStax for the landing point |
| Fiscal year | 12 months ending the last day of any month except December 31 | End of your chosen month (OpenStax) | IRS Publication 538 for the window; OpenStax for the landing point |
| Fiscal year, 52- or 53-week variant | A period of 52 or 53 weeks | End of your chosen week (OpenStax) | IRS Publication 538 for the window; OpenStax for the landing point |
The lead-in is this: the table shows the window each type gives you and where the periodic inventory update is designed to land. The OpenStax page supplies the landing rule for the update itself.
One scheduling note for the fiscal-year shop. Your count window therefore stays in the same season year after year, and your team can plan around it.
4. Set the accounting periods before average cost runs
In Business Central, the Accounting Periods page shows which average cost period and which average cost calculation type is in effect during that period, for each accounting period, according to the Microsoft Learn page on average cost design details.
That page also carries a limit worth reading twice. The Microsoft Learn page says you can only use one average cost period and one average cost calculation type in a fiscal year. One in each fiscal year. If you were hoping to switch calculation types mid-year, that is the boundary.
For a shop that runs inventory through this system, the order of operations is:
- Set the accounting periods to your year type.
- Confirm the average cost period and calculation type shown for each period.
- Count at period end.
- Reconcile the count against the average cost period and calculation type shown for that period.
Each step hands the next one a clean frame. If step one is wrong, every later step sits in the wrong months.
For the shop not using this system, the same principle holds in plain form: whatever periods you close, close them on the boundary your year type declares. The accounting-period page is the system's way of writing that boundary where staff can see it.
5. Decide how often you will physically count
The periodic system updates at period end, which means your physical count has a natural home: the end of your period. A calendar-year shop counts at the end of December. A fiscal-year shop counts at the end of its chosen month. A week-based shop counts at the end of its chosen week.
The OpenStax page frames the update as a period-end event. That framing gives you a scheduling answer without extra work: count where the period closes.
If your shop needs counts more often than once a year, you are choosing a cadence inside the same period structure. The period still closes when the year type says it closes. Additional counts during the period are extra looks at the floor; the period-end update remains the one that aligns inventory numbers with the physical count for the balance sheet.
Practical sequencing for the count itself:
- Freeze movement on the counted aisles.
- Count, and record the count against the period you are closing.
- Reconcile the count to what the system expected before the update.
- Run the update so inventory numbers match the physical count.
That order keeps the count tied to the frame. If the count and the close drift apart, the balance sheet value for merchandise inventory comes out of a period the count never touched.
6. Close the period, then report on the same window
The year type governs reporting the same way it governs counting. If you adopted the calendar year, you report January 1 through December 31, as the IRS page states for books and records. The count feeds the close, and the close feeds the report, all on the same window.
If you elected the week-based variant, the IRS page ties reporting to that basis: you keep books and records and report income and expenses on the 52-53-week basis. The election and the reporting travel together.
A fiscal-year shop reports on its own 12-month window, ending on the last day of its chosen month. The boundary comes from the IRS page. The report, the count, and the accounting periods should all show the same start and end dates when you line them up.
This is the point where the person closing the books should check three documents side by side: the period schedule, the count sheet, and the report window. Same dates on all three means the close is clean.
If your year type and your count schedule have ever disagreed, the close is where you will see it. The fix runs backward: correct the period schedule first, then re-place the count, then re-run the update against the corrected frame.
7. Hold one year type steady while the shop counts
Once set, the year type should stay put while the shop keeps counting. The calendar-year commitment in the IRS page is stated as an ongoing obligation for books, records, and reporting. The week-based election on that page is also tied to keeping books and records and reporting on that basis.
Steadiness is what makes a count comparable year over year. If the period moves, the count lands in different months, and the comparison loses its frame. If the period holds, every count sits in the same season of the business.
For average cost, steadiness has a system-side reason too. The Microsoft Learn page allows one average cost period and one calculation type in a fiscal year. Holding the year type steady keeps that single setting meaningful across the year.
For the team, steadiness means the count instructions can be written once. The window, the cut-off, and the close date repeat the same way each period, and the person running the count does not have to re-derive the plan.
If your shop is considering a change of year type, treat it as a project, not a setting. The change touches the period schedule, the count calendar, the average cost configuration, and the report windows. Line all four up before the next count, not after.
What the two types give a stock-counting shop
A calendar-year shop gets a fixed December close that everyone in the business can plan around. A fiscal-year shop gets an end-of-season close placed where its own cycle is quietest. Both give the periodic update a defined landing point, and both give the person closing the books a single window to report against.
The calendar-year framing comes from the IRS page: 12 consecutive months from January 1 to December 31, with books, records, and reporting on that same span. The fiscal-year framing comes from the same page: 12 consecutive months ending on the last day of any month except December 31.
The update rule comes from the OpenStax page: at period end, inventory numbers adjust to match the physical count, giving accurate merchandise inventory values for the balance sheet. The average-cost constraint comes from the Microsoft Learn page: one average cost period and one calculation type in a fiscal year.
The choice, then, is not about which type is better in the abstract. It is about which 12 months your shop can count against every year without the close, the count, and the report drifting apart.
The sources here do not address how often a shop may change its year type once adopted. Ask your tax adviser or the authority you report to before scheduling such a change around a count.