Skip ahead to the main page
Partner Huddle
Pages

Drake state notes: 5 checks before you e-file

Partner Huddle Editorial Team · Published · 12 min read

Drake state notes identify state-specific subjects to review before e-filing; compare four year tags and New Jersey's Note 31 with each return.

Key takeaways

  • Record each title and link, using a year tag for DC, GA, LA, and MA, and Note 31 for New Jersey.
  • Check the full article before changing a return.
  • Compare this season's list with last season's.
  • Assign each state an owner and log decisions.

Why state notes deserve a yearly check

Small firms rarely have a spare person to read every state article. One preparer may handle federal returns, a dozen states, and a client call in the same afternoon. State returns often get the least attention, and that is where a late reject tends to show up. A state return that e-filed without trouble last season can stop at transmission this year. The cause is not always a preparer's error. It can be a change in state rules, a new note from the software vendor, or a reject that looks different from the one you remember.

Drake Software publishes knowledge base articles on state-level issues. Many titles carry a year tag, such as "2025" or "Drake25." That tag tells you which software year or tax year the article was written for. It does not tell you whether the issue still applies to the return on your screen. That check is your job, and it gets easier when you keep a record.

This post looks at five of those notes. All five appear in the titles on Drake's 1065 extension article for Form 7004. We do not restate the rules in each note here. The titles are enough to show you how to compare notes across seasons. The full articles hold the details you need before you change a return, so treat this post as a guide to the routine and the articles as the source. For the related extension workflow, see our business extension checks.

StateSubject named in the title Year tag or note number
DCReject DCSCHI-0007 or EF Message 0152Drake Tax 2025
GANew tax bill non-conformity 2025
LAForm 620, Schedule D, line 24Drake25
MAForm 355-U overpaymentDrake22 and prior
NJ Certain fiscal year corporate returnsNote 31

How to read a year tag

Four of the five titles carry a year tag, and they come in three styles. Some use a full calendar year, such as 2025. Some use Drake's shorter naming, such as Drake25. One uses a range, "Drake22 and prior," which points to an older software version and everything before it. The fifth title, for New Jersey, carries a note number instead.

Read each tag as a question. Which software year does this note cover, and which year is the return I am working on? When the two answers differ, the note may still matter, but it may not match what you see on screen. In that case, open the full article and check whether its scope reaches the return in front of you.

A tag is not a deadline. A note tagged 2025 is not automatically finished in a later year, and it does not automatically apply either. Decide based on the article and the return. A one-line record is enough: the client, the state, the note, and the decision. That record is what helps your team next season, when the same question comes up and nobody remembers the answer.

1. DC: reject DCSCHI-0007 or EF Message 0152

The title reads "Drake Tax – DC – Reject “DCSCHI-0007” or EF Message 0152 (Drake Tax 2025)." It is the only note in this group that names specific reject codes, so it is the first one to open when a District of Columbia return comes back rejected with one of those codes. A reject often looks like a data problem, and the fix may be somewhere other than where you first look.

Rejects can look harmless on screen. The return appears finished, the numbers tie out, and the problem only shows when the state system responds. For that reason, keep a reject log with four columns: the code, the state, the year tag, and the change you made. When the same code shows up next month or next season, search the log before you start digging through the return from scratch. A log also shows whether a fix worked, which is useful when a second preparer takes over the file.

2. GA: new tax bill non-conformity

The title is "Drake Tax – GA – New Tax Bill Non-Conformity (2025)." Use the article to identify the item affected by non-conformity and the returns it covers. The title alone does not tell you what to change.

Before you assume the note is irrelevant, check your Georgia client list for the item the article describes. A quick scan of last year's returns takes far less time than a rejected batch or an amended return. If a client is affected, note it in your file along with the year tag, so the next preparer knows why the return looks the way it does. Keep this note on your list for the season, even if none of your clients are affected this year, because a client's facts can change from one year to the next.

3. LA: Form 620, Schedule D, line 24

The title is "Drake Tax – LA – Form 620, Schedule D, line 24 (Drake25)." This note points to a single line on a single schedule. Narrow notes like this are easy to skip because they look small. They are also easy to misread, because a line number only helps if you look at the same schedule your software prints.

Pull the schedule up in your software, find line 24, and compare it with last year's copy for the same client. If the line changed in a way you did not expect, write that down with the client name and the year. Then ask a second preparer to look at the same line. Two sets of eyes on one line cost very little, and it is the kind of check that catches a copy error before it reaches the state. The "Drake25" tag suggests the note was written for that software year, so confirm your return is in that version before you treat the note as current.

4. MA: Form 355-U overpayment

The title is "Drake Tax – MA – Form 355-U Overpayment (Drake22 and prior)." This is the oldest tag in the group. Older tags are easy to ignore because they look like history, but a firm that still opens returns prepared in an earlier Drake version will keep running into them.

If you open a Massachusetts return that was prepared in Drake22 or earlier, check this note when reviewing Form 355-U overpayment. Compare the prior-version numbers with what the current software produces, and document any gap. Keep this note on your list until your firm no longer works from returns prepared under those versions. Retiring it too early is the easier mistake to make, so wait until the older files are truly out of the workflow.

5. NJ: fiscal year corporate returns

The title is "Drake Tax – NJ – Filing Certain Fiscal Year Corporate Returns (Note 31)." The note carries a number, Note 31, which makes it easier to find again in the knowledge base. It concerns certain fiscal year corporate returns, so identify New Jersey fiscal year corporate clients and read the article to determine which returns it covers.

Build a short list of your New Jersey corporate clients and mark each one's filing period. A spreadsheet column is enough. Mark which clients are fiscal year filers, and attach the note's title and number next to each of those names. When a return for a fiscal year client comes up, the reminder is already in front of the preparer. A calendar year client does not need the same treatment, so keep the note from creating extra work for the whole team.

Set up a season folder

Create one folder for each season. Inside it, keep a copy of each article you rely on, saved as a PDF with the date you pulled it. Articles can be edited after you read them, and your copy shows exactly what you relied on. Name each file with the state, the note title, and the year tag where present, or the note number for New Jersey, so the files sort cleanly. Add a short index file that lists the folder's contents, the owner for each state, and the date the list was last reviewed.

Keep last season's folder next to this one, and do not overwrite it. When this season's copy differs from last season's, the difference is often the most useful thing you will read all season. Ask the owner for that state to explain the change in one or two sentences and add that explanation to the index. Over a few seasons, the index becomes a plain record of how your firm handled each state.

Build the comparison routine

Set the comparison up once and run it at the same points each season. A simple routine works well:

  1. Start a shared spreadsheet with a row for each note. Include the state, the title, the year tag or note number, the link, the date you reviewed it, the owner, and a column for what changed since last season.
  2. Review the list before the state batch starts, not after the first reject. Then review it again when e-file begins and once more after acceptances come back.
  3. Compare each row with last season's version. Mark it as new, unchanged, or changed. If a note disappears from the list, check whether it was truly retired or simply moved to a different place in the knowledge base.
  4. Assign each state one owner. The owner reads the note, decides how it applies, and records the decision. Owners also answer questions from the rest of the team, so pick people who can explain their decisions in plain words.
  5. Keep the list short enough to read in ten minutes. A list that nobody reads is worse than no list, because it creates false confidence.

Illustrative example: sort returns for review

The owner marks those 5 for review and records why the remaining 5 fall outside its coverage. The reviewer checks the named item before transmission. A changed title alone does not justify changing a return.

Handle prior-year files with care

Many firms pull last year's return to start this year's. That habit saves time, but it carries the old software version with it. Before you build on a prior-year file, check which Drake version it was prepared in. If the file came from an older version, check notes whose tags cover that version.

Then compare the new return with the old one in the places the notes cover. Look at the specific lines and items the article names, not the whole return. Record any gap, even when the difference looks small. A small gap that nobody wrote down is the kind that comes back as a question from a reviewer months later. For related file checks, see our workpaper recovery guide.

Add a second review before transmission

Add a second review step for every state return that uses one of these notes. The reviewer does not need to redo the return. They need to check the specific item the note covers, assess the four year tags against the return's software year or tax year, and initial the checklist. Allow a few minutes for each return to check the item from a second preparer's perspective. For a related transmission check, see our signature rules before e-filing.

Keep the review proportional. A reviewer who checks every line of every return will slow the batch down until the deadline passes. Say which item needs review on the checklist so the reviewer knows what to look for.

What operations leads should watch

Operations leads do not need to memorize every state rule. They need to know whether the list is current and whether the team is using it. Ask three questions each week during the season. Did anyone hit a reject that matches a note? Did anyone open a return prepared in an older Drake version and check the matching tag? Is the owner for each state still the right person, and do they have the time for it?

Make the reject log part of your regular team meeting. Keep it short, and talk about the pattern rather than the person who ran into the problem. If preparers fear that logging a reject will reflect badly on them, they will stop logging, and the log will be useless. A log that is used is worth far more than one that looks complete.

Plan for new staff too. A new preparer should read the list in the first week and sit beside an experienced preparer for the first state batch. Hand them the season folder and the index file, not just a login.

Talk to clients when a state issue causes a delay

Some state issues delay a return. When that happens, tell the client what you know and what you are still checking. Avoid promising a date until the article and the return support one. A short, plain update is better than a long explanation with details you will need to revise.

Keep client language simple. Say that the state software flagged an item, that you are checking the item against the current rules, and that you will confirm the next step. If the item is a fiscal year question, ask the client to confirm their filing period so you can work from the right record. Clients accept delays more easily when they know what is being checked and why.

Read with the return beside you

A title is an index entry. It tells you the state, the subject, and the tag, and little else. Note what it covers, what it asks you to check, and whether it refers to any other article. If it does, open that one too.

Read with the return beside you. Find the form and line the article names, look at what your software shows on that line, and decide whether the two match. If they do not match, write down both values and the source of each. A short note like that is far more useful later than a memory of having "fixed something."

Set a response time for rejects

Decide, as a team, how quickly a state reject gets an answer. A simple target works: the owner for that state looks at the reject the same business day, checks the matching note, and posts a one-line status in the reject log. If the owner cannot resolve it that day, the status says what is still open and who will take the next step.

A fixed response time keeps rejects from sitting in a queue while the batch deadline gets closer. It also keeps the owner from becoming a bottleneck. If the same owner is always the one answering, split the states between two or three preparers so that no single person holds the whole list during the busiest weeks.

Start today

Open the linked Drake extension article today, choose a note relevant to a return you handle, and record its title, owner, and review decision.

Common questions

Does a year tag expire?

A year tag identifies scope rather than an expiration date. Use the article and the return to decide whether the note applies.

What should the New Jersey record use?

Use Note 31 instead of a software-year tag. Check the article's coverage against the client's fiscal year corporate return.

Which Massachusetts item needs checking?

Check Form 355-U overpayment for returns prepared in Drake22 or earlier. Keep the comparison focused on that subject.

Sources