Cycle Codes, Transaction Dates and the 23C Date: Reading the Timeline on Your Transcript

"I paid that in April. Why did I get a bill in June?" The answer is often sitting in two columns of the account transcript: the cycle and the date. Learn to read both and a lot of IRS correspondence stops looking random.

What a cycle is

The IRS Master File posts transactions in weekly batches called cycles. Document 6209, Section 16, contains the posting cycle calendars and explains that "ECC cycles are the posted cycles for the transaction that has been input to the system." The same section notes that daily processing runs Friday through Thursday and weekly processing for the master files runs Thursday evening, with results available on IDRS on Monday morning.

The 6209 calendars label cycles by year and week number, for example 202201 for the first cycle of 2022.

Decoding the eight-digit cycle

On taxpayer transcripts the cycle column usually shows eight digits. The Document 6209 glossary explains the format.

For the last two digits, the glossary gives two rules. If the transaction posted through the newer CADE system, the last two digits are the day of the week, with 01 meaning Monday, 02 Tuesday and so on. If the transaction did not post through CADE, the last two digits will always be 08.

So 20240805 means the transaction posted in 2024, in cycle 08, on the fifth day of the week. You do not need the exact calendar day. You need the order.

What the date column is

The date column is the date the IRS assigns to the transaction itself. For a payment, it reflects when the IRS treats the money as paid. For an assessment, it is the assessment date.

That second point deserves its own heading.

The 23C date

Under IRC 6203, an assessment is made by recording the liability in the office of the Secretary. Treasury Regulation 301.6203-1 fills in the mechanics: the assessment is made by an assessment officer signing the summary record of assessment, and "the date of the assessment is the date the summary record is signed by an assessment officer."

Inside the IRS, that date is called the 23C date, after the old form number of the summary record. The Document 6209 glossary defines it as "the date an assessment is posted to the Master File," adding that it is "also the date the first master file notice is sent on a balance due account" and is "commonly referred to as the notice date or assessment date."

Three practical consequences follow.

• The first balance due notice and the assessment share a date. If you got a notice, the assessment it relates to is on your transcript with a matching date.
• The assessment date is the starting point for the 10-year collection period in IRC 6502(a)(1), which allows collection by levy or court proceeding "within 10 years after the assessment of the tax." Each assessment line can start its own clock.
• IRM 21.2.3.2.2 says the tax account transcript shows Master File transactions, and Document 6209 defines assessments such as TC 150 and TC 290 as Master File transactions, so the assessment lines and their dates are there. The IRM's list of what the account transcript displays does not include a collection statute expiration date. You work that out from the assessment dates and any events that suspend the clock.

Why the payment and the bill cross in the mail

Go back to the April payment and the June bill. Look at the payment line, likely a TC 670 subsequent payment. Check its cycle. If it posted in a cycle after the notice cycle, the notice was generated before the payment reached the Master File. The notice simply did not know about it. Then check that the date on the payment line matches the date you actually paid; if it does not, that is a payment-application problem worth raising.

Document 6209 also tells you when interest gets formally assessed. TC 196, interest assessed, is computer generated at first notice time, among other triggers. That is why interest that was accruing quietly suddenly appears as a dated line on the transcript when a notice goes out.

Using cycles to build a timeline

When I review a transcript, I sort the events in cycle order and then annotate them with the transaction dates. Cycle order tells you what the IRS computer knew and when. Transaction dates tell you what legally happened and when. A good case review needs both.

Example: a return posts with TC 150 in one cycle. Two cycles later a TC 971 posts showing a notice. Five cycles after that, a TC 670 payment posts with an earlier transaction date. The sequence tells me the payment was in transit while the notice issued, so the notice balance overstated what was owed by the amount of that payment.

Another example: a TC 420 exam indicator posts in a cycle after the return was processed. Then the refund you were expecting never shows a TC 846. Cycle order makes the connection obvious. See TC 420 and TC 421.

Dates that start other clocks

The 23C date is not the only date on the account that has legal consequences. Two others show up on transcripts often enough to watch for.

The first is the date of a notice of intent to levy. Under IRC 6651(d), the failure-to-pay penalty rate increases from 0.5 percent to 1 percent per month beginning after the day that is 10 days after notice is given under IRC 6331(d), the levy notice provision. If your failure-to-pay penalty seems to accelerate, find the levy notice date.

The second is the date of a Collection Due Process notice. IRC 6330(a) requires the IRS to give written notice of the right to a hearing not less than 30 days before the first levy for a tax period, and the hearing request has to come within that 30-day period. Document 6209 lists TC 971 action code 069 as "Due Process Notice was issued," with related action codes for a signed return receipt (066), a refused or unclaimed delivery (067) and an undeliverable notice (068). When you see those lines, the date column is the date you count from.

A timely hearing request has its own marker. Document 6209 describes TC 971 action code 275 as indicating that a timely Collection Due Process request was received, and says it excludes the module from selection by automated levy programs. Under IRC 6330(e)(1), the levy actions at issue and the running of the collection period are suspended while the hearing and appeals are pending. That suspension is one of the events you have to account for when you work out how much time is left on the collection clock.

Reading the gaps

Gaps between cycles can be as informative as the transactions. An account that shows a return in one cycle and nothing for months afterward, with a balance due, is usually moving through the notice stream. An account that shows a TC 570 hold and then nothing is waiting on someone inside the IRS to finish something. An account that shows a payment every month in the same week is probably on an installment agreement with direct debit.

When a client tells me the IRS "has done nothing" for a year, the cycles usually say otherwise. A TC 971 notice line, a TC 196 interest assessment at notice time, a TC 582 lien indicator: each has a cycle, and the sequence of cycles is the sequence of IRS actions. If you are going to call the IRS, bring that sequence with you. It makes the conversation shorter and the answers better.

Julian dates are something else

There is a third kind of date hiding in IRS records, inside the document locator number. The 6209 glossary defines the Julian date as "the numeric day of the year that the return or document was numbered for processing," found in the sixth, seventh and eighth digits of the DLN. It is not the cycle and not the transaction date. I cover it in The Document Locator Number.

Bottom line

The cycle is when the computer posted it. The date is when the IRS says it happened. The 23C date is when an assessment became official, and it starts the clock. Read all three and the transcript becomes a timeline instead of a puzzle.