A short tax year covers less than 12 months; intake also needs the period's first and last dates.
Key takeaways
- Collect the period's first day, last day, month count, and reason for the short period.
- Keep week-based dates and calendar month ends distinct in the file.
- Flag depreciation, amortization, and questions about a provision's start date for review.
- Resolve conflicting dates before return work starts.
Why these three facts matter at intake
The tax year is one of the first things intake has to pin down, because a wrong period can carry into other dates in the file. That applies to a new client's first return and to a client that asks to change its year end. Settling the period before any work starts is easier than correcting a file later, after the schedules and workpapers are built.
This post covers three facts from IRS Publication 538, Accounting Periods and Methods (01/2022). Each specific rule, number, and date in it comes from that publication, and each one links to the page where it appears.
The readers here are partners and operations leads, and the work may be split between them. One person may collect the client's dates and another may review them. Either way, both should read the same three facts, because each one changes what goes into the file.
Treat this as general information, not tax advice for a particular client. Confirm the current version of the publication before you rely on it.
Fact 1: Short tax year filing requirements
Under IRS Publication 538, a short tax year is a tax year of less than 12 months. That definition is the first test to run at intake. Do not assume a period is a full year because of the calendar dates it appears to sit on. Count the months in the period itself.
The publication also says how a short year is filed: requirements for filing the return and figuring the tax are generally the same as the requirements for a return for a full tax year (12 months) ending on the last day of the short tax year. The quote uses the word "generally," so read it as a general statement. Do not treat it as a promise that every requirement is identical in every case. For intake, that means the file should show the short period's dates next to the filing requirements the team applies to it, so a reviewer can see both.
The publication's example of a first return shows how the period is stated. The corporation's first tax return will cover the short period from July 1 through December 31. The example is about a corporation. For intake, the useful point is that the example states the period by its first and last dates, which is the same information the intake record needs.
For any first return or year-end change, record these items before work starts:
- The first day of the period the return will cover.
- The last day of that period.
- The number of months in that period, counted from those dates rather than from memory or from the prior year's file.
- Whether the period is a first return, a year-end change, or neither, so the reason for the short period is written down.
Fact 2: Calendar month ends for a 52-53-week tax year
The publication's instruction is: End on the last day of the calendar month ending nearest to the last day of the 52-53-week tax year.
The key word is "nearest." Read the instruction in steps. First, identify the 52-53-week year's last day. Second, find the calendar month ending nearest to that day. Third, the last day of that calendar month is the year end the instruction selects.
At intake, a 52-53-week client needs two dates on file: the week-based last day the client gives you, and the calendar month end the instruction points to. Note which one the return uses and the reason in the file.
Write the two dates side by side and read them against the instruction. If the file shows only one of them, the note is incomplete, and the year end is not yet settled in the file.
The publication gives a separate rule for depreciation. When you figure depreciation or amortization, a 52-53-week tax year is generally considered a year of 12 calendar months. It is limited to depreciation and amortization. Do not carry it into other calculations. When the file includes depreciation or amortization, flag it at intake so the work is checked against this rule. For related asset review, see depreciation methods for client assets.
Fact 3: The July 1 provision example
The publication's example sets up the provision first: assume a tax provision applies to tax years beginning on or after July 1, which (for purposes of this example) happens to be a Sunday. The publication then states: for this purpose, a 52-53-week tax year that begins on the last Tuesday of June, which (for purposes of this example) falls on June 25, is treated as beginning on July 1.
Two details are part of the example and not facts about any year: the June 25 date and the Sunday. Do not carry them into a client's file as facts about that client.
The example is narrow. Keep the treatment within the provision being reviewed.
Read this example as an illustration of the treatment, and check any provision in a client's file against its own rules.
At intake, when a provision in the file depends on whether a tax year begins on or after July 1, record the 52-53-week start date and check it against that provision, not against this example. When the answer is unclear, write the open question in the file note and raise it with the reviewer before the return work depends on it.
Checklist for the intake file
Use these six questions at intake. Each one points back to a fact above.
- Does the period cover fewer than 12 months? (Fact 1)
- What are the first and last days of the period? (Fact 1)
- Is the year a 52-53-week year? If so, what is the week-based last day, and which calendar month end does the publication's instruction point to? (Fact 2)
- Does the file include depreciation or amortization? If so, note the treatment discussed above for those calculations. (Fact 2)
- Does a provision in the file depend on whether the tax year begins on or after July 1? If so, check the start date against that provision. (Fact 3)
- Has the client asked for a year-end change? If so, record the old and new year ends and any period the change creates.
The questions are in order for a reason. The first two settle the length of the period, which decides the label. The next two settle the end date and any depreciation treatment. Question 5 checks the provision; question 6 records the old and new year ends and any period the change creates. If a question cannot be answered from the client's documents, mark it open and do not fill it in from the year-end label on older paperwork.
How to write the file note
Write one file note for each period the team will file, and keep it with the intake record. The note should name the period, the type of year, the dates, and the source. A short structure helps a reviewer follow it:
- Period: the first and last dates, as the client gives them.
- Length: the number of months, and whether the period is shorter than 12 months.
- Year type: a full year, a short year, or a 52-53-week year, with the calendar month end used if the year is 52-53 weeks.
- Special treatments: whether depreciation or amortization is in the file, and whether a provision depends on a start on or after July 1.
- Source: IRS Publication 538 (01/2022), with a link to each page used.
Keep the note short. A reviewer should be able to see what was decided and why without opening every client document. If a note cannot be written because a date is missing, that is a signal to go back to the client rather than to guess. Keep the note with the broader client intake checklist for the handoff.
Illustrative example: Reviewing a short period
Suppose the client's written dates cover 6 months. The intake note records those dates and the month count, then identifies the period as a short year under Fact 1. The reviewer checks the filing requirements against the period's last day. If the client calls it a full year, the team resolves that conflict before return work starts.
Getting the dates from the client
Ask the client for the first and last dates of the period in writing, and compare them with what the return will cover. A verbal answer is easy to misremember, and a written answer gives the reviewer something to check against.
When the dates conflict, hold the work until the conflict is resolved. Record who gave each date, when they gave it, and which document it came from. If the client supplies a week-based date for a 52-53-week year, compute the calendar month end from the publication's instruction (the last day of the calendar month ending nearest to that year's last day), and write that calculation and the resulting date in the file note.
Confirm any date given in a meeting or on a phone call in writing before it goes into the file. Do not fill a gap by copying dates from a prior year's file. The prior year's period may not match the current one, and the three facts here depend on the dates of the period in front of you.
Mistakes to avoid at intake
Four mistakes follow from the facts above.
The first is treating a period as a full year because of its calendar dates. Check the month count before accepting the client's label.
The second is setting the end of a 52-53-week year to its own last day without checking the calendar month end. Keep the reason for the selected date with the intake note.
The third is applying the depreciation treatment to other calculations. Flag those calculations separately for review.
The fourth is taking the June example as a rule for every June year. Review the client's provision before using the example's treatment.
Year-end changes at intake
A year-end change at intake needs the dates on both sides of the change. Record the old year end, the new year end, and the dates of any period the change creates. Use the short-year filing language above when reviewing that period.
If the new year end is a 52-53-week year end, Fact 2 applies to the calendar month end used for that year. Write down which month end the team used and why, the same way you would for any other 52-53-week client. Keep the change as its own item in the file, with its own note, so it is not mixed into the note for the current return.
This post does not explain how to request a change of tax year, what approvals apply, or when a change can be made. Check the current IRS guidance on changing an accounting period before you tell a client what to expect, and keep a note of which guidance the file relies on.
Limits of this post
The copy cited here is dated 01/2022. Check the current version before you rely on any quote in this post, because a later version may say something different.
Next step today
Choose a client file and run the six intake questions above. Write the period's first day, last day, month count, and whether it is a first return, a year-end change, or neither. Mark any unanswered question for the reviewer before return work starts.
Questions at intake
What should happen when client dates conflict?
Hold the work until the conflict is resolved. Keep each date's written source with the file note so the reviewer can trace the decision.
Should the year-end change have its own note?
Keep the change as its own item in the file. This keeps the change separate from the note for the current return.
Source
The only source for this post is IRS Publication 538 (01/2022), Accounting Periods and Methods, at ( Internal Revenue Service).