Skip ahead to the main page
Partner Huddle
Pages

Tax rule sources: 4 checks before quoting a client

Partner Huddle Editorial Team · Published · 12 min read

Before quoting a tax rule, check the relevant IRS instructions, state agency guidance, statute section or revised code, including its update notes.

Key takeaways

  • Match the source to the client's federal or state question.
  • Check revision dates and developments or update notes.
  • Compare translations with the English original.
  • Save the source address and explain any unresolved conflict before answering.

A client wants to know when a payment is due, whether a form applies to their situation, or whether a state rule differs from the federal one. The question often comes in the middle of a busy week, and the answer feels like it should take a minute to look up. That is exactly when a wrong answer slips out.

The difficulty is that tax rules do not come from one place. Federal law is set by Congress and explained by the IRS through forms, instructions, and publications. State rules come from state statutes, codes, and agency guidance, and many state agency pages point back to federal material for the federal piece. Each of these sources is updated on its own schedule. A page can be accurate on the day it was written and still miss a change enacted later.

This post covers four sources to check before you quote a state or federal rule to a client. They are an IRS instructions page, a state revenue agency withholding page, a state statute section, and a state revised code. Each one has a different weak spot. Knowing where that weak spot sits tells you what else to check before you put the rule in writing.

The examples here come from official pages and code sections we reviewed. They show how to check a source. They are not a summary of any tax. Confirm the rule that applies to your client's facts, and if the answer depends on details you do not have, say so to the client instead of guessing.

Start by identifying the layer

Before you open any source, decide what kind of material you need. Many mistakes begin when someone searches for a rule without knowing where it lives. For a state or federal tax question, there are generally three kinds of material.

The first is the statute itself, passed by a legislature. Statutes are the foundation, but they are often written in general terms and can be hard to apply to a specific case.

The second is agency guidance: instructions, publications, notices, and web pages that explain how an agency reads the statute. Guidance is usually easier to use, but it sits one step away from the law, and it can lag behind a new enactment.

The third is a compiled code, which gathers statutes in one place, often with notes about where each section came from and when it was amended.

A good habit is to start with the layer that best matches the question. If the question is what a form asks for, start with the agency instructions. If the question is what the law says, start with the code. Then use the other layers to confirm.

Federal payroll and information reporting questions often lead to IRS form instructions. The instructions for Form 941 are one example. The Instructions for Form 941 page we checked is labeled 03/2026 in its title, and it includes this statement:

> "For the latest information about developments related to Form 941 and its instructions, such as legislation enacted after they were published, go to IRS.gov/Form941."

That sentence matters more than it first appears. Instructions are published at one point in time. If legislation is enacted after publication, the instructions may need to be read alongside later developments. The same note appears in the Instructions for Schedule B (Form 941) page, which is labeled 06/2025. Two related sets of instructions can carry different revision dates, so check each one separately.

A revision date identifies the version you are reading. It does not tell you whether the text still applies to the year in question. Here is a practical routine for IRS instructions:

  • Note the revision date in the title of the instructions you used, and write it down with your answer.
  • Go to the developments page the instructions name before you quote a line number, a form field, or a threshold.
  • If the developments page mentions a law you do not recognize, pause. Ask whoever handles technical questions at your firm before you answer the client.
  • Remember that a form's line numbers can change between revisions. A line reference copied from an old answer may point to the wrong place on the current form.

2. A state agency withholding page

State agencies publish their own guidance, and many of those pages depend on federal rules. The Minnesota Department of Revenue's withholding tax page is a useful example because it shows how state guidance points back to federal material. It says:

> "For more information on withholding requirements, see federal Circular E, IRS Publication 15 and our Withholding Tax Instructions."

This is a lesson in layers. A state page may give you the state-specific piece, but for the federal side of withholding it sends you to federal publications. When you quote a withholding rule to a client, be clear about which layer your answer comes from. A federal point should be checked against the federal publication the state cites. A state point should be checked against the state's own withholding instructions. Mixing the two is a common way to give a client an answer that is right for one layer and wrong for the other.

For related payroll work, use the payroll intake review to organize the questions you need to check.

The same page includes notes about translations, and those notes matter if you or your client work from a translated version. The page says:

> "In the event of a disagreement or discrepancy between the translation and the original English version of this website or any notice or disclaimer, the original version will prevail."

Check the English text, quote from it, and note in your file that you did so. If a client has asked for the answer in another language, you can translate your conclusion for them, but keep the English source attached to the answer.

Agency pages also change in ways that are easy to miss. A page can be reorganized, a link can move, or a notice can be added at the top. When you save a source for your file, save the address and the date you read it. Save the relevant text too, so your record shows what you relied on if the page later changes.

3. A state statute section

When the question is about the text of a state tax law, the statute is the primary source. Virginia's Code is available through the Virginia Law site. The section on returns by dealers, § 58.1-615, sets out a monthly filing schedule. It requires a dealer to transmit a return showing the gross sales, gross proceeds, or cost price for the preceding calendar month, and it says that a like return must be transmitted thereafter:

> "on or before the twentieth day of each month, for the preceding calendar month."

That is a specific deadline, and the section supports it as written, so you can quote it with the link. Still, reading a statute is different from reading a summary. Read the whole section, not just the sentence that answers the question. Check the definitions that apply, any exceptions in the same section, and whether the section refers to another section for details. A deadline that looks simple can depend on a definition found elsewhere in the chapter.

Two cautions apply to almost any code section. The first concerns the history note at the end. The same section page includes this statement:

> "The chapters of the acts of assembly referenced in the historical citation at the end of this section may not constitute a comprehensive list of such chapters and may exclude chapters whose provisions have expired."

In practice, the historical citation is a useful trail, but it may not list every act that touched the section. Do not assume that a section with an old-looking history is unchanged. Also do not assume that a section with a recent-looking history is complete. Before you quote the section as current, check the official status of the law and any amendments that may have followed the version you read.

The second caution is about dates. A statute page is a snapshot taken when someone last updated it. Write down the date you read the section, and use that date in your note to the client. If your answer depends on a rule that took effect on a particular date, check whether the rule applies to the period in question, not just whether it exists.

4. A state revised code

Ohio publishes its Revised Code online, and the Ohio Revised Code page for Section 5739.12 includes a note about how the text is maintained.

> "The Legislative Service Commission staff updates the Revised Code on an ongoing basis, as it completes its act review of enacted legislation."

Read that sentence carefully. It tells you that the code is maintained as staff work through new legislation, which is good news for accuracy over time. It also tells you that the online text may trail the most recent enactments until staff finish their review. So if a client asks about a change from a recent legislative session, do not rely on the online code alone. Check whether the act has been reviewed and reflected in the code, and check the enacted legislation itself to confirm what it says.

If you find a section that seems to conflict with what you expected from news coverage or a client's description, treat the gap as a reason to check the enacted text and the code's update status. Do not pick the version you find easier to explain.

Another practical point: a revised code is an organized collection, so it is easy to read a section in isolation. Look at the surrounding sections and any cross-references. Many state tax provisions depend on terms defined in another part of the code, and an answer based on a single section can miss a condition that applies from elsewhere.

For a related filing question, see the Ohio vendor return guide, then check the official section that applies.

When the sources disagree

An IRS instruction may describe a rule one way, a state page may describe a related rule differently, and a code section may show an older or newer version. When that happens, avoid the instinct to choose the answer that sounds most reasonable. Work through the disagreement in order.

First, identify which layer applies to the question. For a federal filing question, the federal law and the IRS's official developments page should be checked before you rely on the instructions alone. For a state agency withholding question that points to federal publications, you may need both the state page and the federal publication it cites.

Second, check the dates. A disagreement is often just two sources written at different times. If one source is newer, check whether it reflects a change that took effect after the other source was written. If both are old, look for developments or update information before treating either as current.

Third, check whether the disagreement matters to your client. Two sources can differ on wording while agreeing on the result for the client's situation. If they disagree on a deadline, a rate, or a condition that affects your client, treat it as a stop sign. Escalate to someone who can make the call, and tell the client that you are confirming the point before you give a final answer.

Fourth, document the conflict. Write down the sources you compared, their dates, and how you resolved the difference. This record helps explain your answer if the question returns later.

A pre-quote checklist

Before you send a state or federal rule to a client, work through these steps.

  1. Identify the layer. Decide whether the question is about federal law, a federal form, a state statute, or state agency guidance. Each has a different primary source.
  2. Go to the official source. Quote from the agency page, the code section, or the instructions themselves, not from a summary, a forum post, or a memory of last year's answer.
  3. Note the date you read it. Record the revision date on IRS instructions and the date you accessed any state page or code section.
  4. Check the developments or update notes. Look for the IRS developments link, the code's historical note, and any notice on a state agency page that mentions a change.
  5. Confirm the language. If the source you used is a translation, go to the English original and quote from it.
  6. Check the number or deadline against the text. Read the sentence that contains the figure, not just the summary near it, and confirm that it applies to your client's period and facts.
  7. Save the record. Keep the address, the date, and a short note of what you checked, so you can show your work if the rule changes.

If any step turns up a gap you cannot close, tell the client what you have confirmed and what is still open. A partial answer with a clear label is better than a complete-sounding answer that later proves wrong.

Illustrative example: reviewing withholding questions

Group them by whether they concern federal or state requirements. For a federal question, follow the Minnesota page's reference to the federal publication; for a state question, check the state's withholding instructions. Record the source and date beside each answer. If a question remains unresolved, mark it for technical review rather than copying an answer from the other group.

Quoting with care

Quoting a rule is a commitment. Once a client acts on your answer, the source you used becomes part of the reason they acted. If the rule later changes, the client will want to know what you told them and why. The record you keep is the answer to that question.

Today, choose a client answer you are preparing. Open its official source, check its update information, and save the relevant text, address and date before sending it.

Questions before quoting

Where should I start checking a tax rule?

Start with the official source that matches the question. Use form instructions for form mechanics and the relevant code section for statutory text.

What if I cannot resolve a source conflict?

Pause the affected answer and ask whoever handles technical questions at your firm. Tell the client which point you are still confirming.

What should I keep with my answer?

Keep the source address, relevant text, revision or access date, and a short note explaining what you checked.

General information, not legal or tax advice.

Sources