Skip ahead to the main page
Partner Huddle
Pages

3 date types in each Washington tax law note

Partner Huddle Editorial Team · Published · 13 min read

When a new tax change is published, partners and operations leads have one question to settle before anything else: does this change reach the client's return or payment? The answer is not always in the headline of the law. It can sit in the notes that follow a statute, where the session law that made the change gives its own dates. Those notes are short, but they can hold several dates, and each date answers a different question.

This post explains three date types you can find in a Washington tax law note. It uses the notes to RCW 82.32.045 as the working example. That section is titled "Taxes—When due and payable—Reporting periods—Verified annual returns—Relief from filing requirements," so it covers when taxes are due, which is the question this post addresses. The three date types are:

  • The effective date, which says when a section takes effect.
  • The return date, which says which returns a section reaches.
  • The payment date, which says which payments a section reaches.

Keep these three apart when you read a note. Each one answers its own question, and a note can give different answers for different parts of the same law.

Some terms first, so the rest reads easily. A session law is the act the legislature passes in a given session, and it is identified by a year and a chapter number, such as "2006 c 256." A section is a numbered part of that act, and a subsection is a numbered part of a section, such as the "(1)" and "(2)" shown in the notes. The notes on the RCW page list the session laws they cite and the dates attached to each one, under headings such as "Effective dates" and "Application."

Everything quoted below comes from the official Washington State Legislature page for RCW 82.32.045. Where a quote is silent on a point, this post is silent too.

The effective date says when a section takes effect

The effective date is the day a section takes effect, and the RCW 82.32.045 notes state it directly. The note for the 2006 session law, chapter 256, is headed "Effective dates—2006 c 256," and it reads: "Sections 1 through 4 of this act take effect August 1, 2006." The words "of this act" point back to the session law, so the date belongs to sections 1 through 4 of that law. The quote does not say that the date applies to the whole RCW section.

Write the date down next to the section numbers it covers. A date with no section numbers beside it leaves you guessing which part of the law starts on that day. A simple log with three columns is one way to keep this straight: the session law, the section numbers, and the effective date. For the 2006 note, one row would read: 2006 c 256, sections 1 through 4, effective August 1, 2006. Add a fourth column for the source link so that anyone who reviews the log can check the note themselves.

The effective date is about the section itself, so it belongs in the log even before you know which return or payment the section might reach.

The 2003 entry shows that one note can carry more than one effective date. Its note is headed "Effective dates—2003 1st sp.s. c 13," and it has two subsections. "1st sp.s." refers to a first special session. Subsection (1) says that sections 8 through 10 take effect August 1, 2003. Subsection (2) says that sections 11 through 16 take effect July 1, 2003. The two groups have different dates, so one date cannot be applied to every section in that note. Read each subsection on its own, and write down the dates separately, as you did for 2006. In the log, that becomes two rows: 2003 1st sp.s. c 13, sections 8 through 10, effective August 1, 2003; and 2003 1st sp.s. c 13, sections 11 through 16, effective July 1, 2003. Two rows keep the two groups from blending into one.

The effective date is the first of the three dates to check, but it is not the last. A section can take effect on one day and then apply to returns or payments due on other days. The next two sections cover those.

The return date says which returns a section reaches

Under the 2006 session law, sections 1 through 3 apply to returns due after July 31, 2006. The note sits under a separate heading, "Application—2006 c 256," and reads: "(1) Sections 1 through 3 of this act apply to returns due after July 31, 2006." The heading is different from the effective date heading, and the two headings answer different questions.

The return date does not say that the sections apply to every return. It names one group of returns, those due after July 31, 2006, and it names one group of sections, sections 1 through 3. For the return side of your question, the test is narrow. Is the return one the note describes as due after July 31, 2006? Is the section one of sections 1 through 3?

Notice that the effective date and the return date are close but not the same. The effective date is August 1, 2006. Sections 1 through 3 apply to returns due after July 31, 2006. The note gives them separately, and they answer different questions. One asks when a section takes effect. The other asks which returns it reaches. Do not merge them into one date because they are a day apart.

The note uses the word "due," so compare the due date of each return with the date in the note. The date you prepared the return, or the date you sent it, is not the wording the note uses. When a return's due date is near the boundary, such as July 31, 2006, read the note's exact words, "after July 31, 2006," rather than a rounded version of them.

The payment date says which payments a section reaches

Section 4 of the 2006 session law applies to payments due after July 31, 2006. The note reads: "(2) Section 4 of this act applies to payments due after July 31, 2006." It sits under the same "Application—2006 c 256" heading as the return date, but it is a separate subsection, numbered (2).

The return rule and the payment rule point to different sections. Sections 1 through 3 cover returns, and section 4 covers payments. Under this note, a section that reaches returns does not, by that fact, reach payments. Check each section against its own rule, and do not carry a conclusion from one rule over to the other.

Section 4 also falls within the range that the effective date note covers, since sections 1 through 4 take effect August 1, 2006. For section 4, then, the note gives both an effective date and a payment date. Keep them apart in the same way you did for returns: one date says when the section takes effect, and the other says which payments it reaches.

The payment rule has the same structure as the return rule: a section list, a date, and a "due after" test. Keep that structure in your log so every row has the same three parts, which makes gaps easy to spot.

The note measures a payment against "payments due after July 31, 2006." A payment is therefore checked against its own due date, not against the return date for the same client. Keep the two columns in your log separate, so a payment date never gets copied into a return row by mistake.

The 2006 note, date by date

The 2006 note gives three dates, and each one answers a different question. The table below sets them side by side, using only the wording of the quotes above.

Date typeSectionsDate in the note Question it answers
Effective dateSections 1 through 4August 1, 2006When does each section take effect?
Return dateSections 1 through 3Returns due after July 31, 2006Which returns does each section reach?
Payment dateSection 4 Payments due after July 31, 2006Which payments does the section reach?

Read across a row and you have one complete answer. Read down a column and you can see that the sections in each row are not the same. Section 4 appears in the first row and the third, but not the second, which is why the return rule and the payment rule must be checked separately.

The 2003 and 2006 dates do not settle a current return

No. The 2003 and 2006 dates in these notes do not settle a current return on their own. They describe what those session laws say. They do not show whether later legislation changed the same sections. The quotes here do not address later changes, so they cannot settle a return or payment that falls in a later year.

Before you apply any of these dates to a current return or payment, check the current text of the statute and any later session law that touched the same sections. The RCW page is the place to start, and its notes list the session laws they cite, such as 2006 c 256 and 2003 1st sp.s. c 13. If the notes cite a later session law, read that law's own text before you rely on the older dates.

Keep the date of your check in the log, along with the source you used. A note that was accurate when you read it may not be accurate later, and a dated entry shows the next reviewer when the check was made.

The page heading carries its own date

The heading of the RCW 82.32.045 page reads "Effective January 1, 2029." That date is not one of the dates in the 2003 or 2006 notes. The quotes here do not say which sections, returns, or payments the heading date applies to, so do not assume it applies to any of them.

Before you rely on the heading date, find the statute text it covers and read that text against your own return or payment. Treat the heading as a question to answer, not as a date you can use on its own. Write it in your log as its own row, with the words from the heading, so that nobody later mistakes it for one of the session law dates. The heading and the notes are two separate parts of the same page, and reading one does not replace reading the other.

How do you read a note in order?

Read the effective date first, then the return date, then the payment date, and match each date to its section numbers before you decide anything. Reading in that order keeps each date tied to the section it describes.

  1. Find the session law the note is about, such as 2006 c 256, and note its year and chapter.
  2. Write down the effective date and the section numbers it covers.
  3. Write down the return date and the sections it names.
  4. Write down the payment date and the sections it names.
  5. For each subsection, check that you are reading the date that belongs to that subsection and not a date from a neighboring one.
  6. Compare the due date of the specific return or payment with the date the note gives, using the note's exact words.
  7. Record which dates you used, which section each one covers, and where you found it.

Step 5 matters most with the 2003 entry, which has two subsections with two different effective dates. Step 6 matters most near a boundary date, such as July 31, 2006, where a small difference in reading can change the answer.

Once a note is logged, read the log once against the quoted text. Check that every date matches its quote word for word, including the month, day, and year, and that every section number matches the subsection it came from. This second read catches the errors that are easiest to miss, such as a section number copied from the row above.

Who on the team uses each date

Partners decide whether a change reaches a client, and operations leads record the dates that support that decision. The split is a suggestion, not a rule, and the two roles can overlap in a small firm. What matters is that each date has a named owner and a written source.

An operations lead can prepare the log described above, enter each date with its section numbers and link, and flag any row where the note's wording is unclear. The partner then reads the flagged rows and decides whether the change reaches the client's return or payment, using the full text and not the log alone.

Writing it this way keeps dates from being passed along as summaries. A summary that says a rule applies from a certain year loses the section numbers and the due-date wording that the notes supply, and those are the parts that decide the question.

Do the notes settle the question alone?

No. The notes give dates and section numbers, but the quoted notes do not describe what each section changes. That means the full session law and the current statute must answer the substance of the question, and the notes can only narrow it to the right sections and the right due dates.

For a partner deciding whether a change reaches a client, the practical result is a shorter list to check. Use the notes to find the sections, the effective dates, and the due-date tests. Then confirm the substance with the full text and with a qualified adviser before you advise the client or change a filing or payment.

Mix-up to avoid: one date as the answer to every question

The most direct mix-up to avoid is treating the effective date as the only test. The 2006 note gives an effective date of August 1, 2006 for sections 1 through 4, and applies sections 1 through 3 to returns due after July 31, 2006. A reader who sees only the first date may miss the second, and a reader who sees only the second may miss the first. Both dates belong in the answer.

The same goes for the payment date. The 2006 note gives a payment date for section 4 only. A reader who copies the return date into a payment row would be applying a rule from a different subsection. Keep the return and payment rules in separate rows, and label each row with the subsection it came from.

When the note leaves a question open, write that down rather than filling the gap. A blank cell in a log is more useful than a guess, because it shows the next reviewer where the text still needs to be checked.

Summary: three dates, three questions

The three date types in a Washington tax law note answer three questions. The effective date answers when a section takes effect. The return date answers which returns a section reaches. The payment date answers which payments a section reaches. In the RCW 82.32.045 notes, the 2006 session law gives all three, with sections 1 through 4 taking effect August 1, 2006, sections 1 through 3 applying to returns due after July 31, 2006, and section 4 applying to payments due after July 31, 2006.

The 2003 entry adds a fourth lesson: a note can have several effective dates, one for each group of sections. The page heading adds a fifth: a date in the heading may not match any of the dates in the notes. Read each one separately, record it with its section numbers, and check the current text before you act on it.

If you keep one rule from this post, keep this one: a date is only useful when it comes with its section numbers, its subsection, and the wording the note uses. Without those three, a date can look like an answer when it is only part of one.

Sources