Every tax return processed by the IRS is tagged with a hidden identifier that most taxpayers never notice—but IRS systems rely on constantly. That identifier is the Document Locator Number, commonly referred to as the DLN.
Understanding the IRS Document Locator Number DLN can help explain where your return is being processed, which IRS service center controls it, and how the IRS finds your return if it is pulled for review.
What Is an IRS Document Locator Number (DLN)?
The Document Locator Number (DLN) is a 14-digit number assigned to every tax document that posts to the IRS Master File.
The DLN acts as:
- A filing “address” inside IRS systems
- A routing identifier for processing pipelines
- A locator for both digital and paper records
Once assigned, the DLN stays with the return throughout its life cycle.
Why the DLN Matters More Than You Think
While taxpayers focus on refund dates and transcript codes, IRS employees rely on the DLN to:
- Identify where a return entered the system
- Determine which service center processed it
- Locate the return during audits, reviews, or corrections
If a return is delayed or pulled for review, the DLN is how the IRS finds it quickly.
Breaking Down the 14 Digits of the DLN
Each section of the DLN has a specific meaning.
1. Service Center Code (First 2 Digits)
The first two digits identify which IRS Service Center originally processed the return.
Examples include:
- 01–09: Legacy service center identifiers
- 10–19 and above: Modernized processing locations
This tells you where your return entered the IRS pipeline.
DLN Service Center Code Table
| DLN Code | IRS Service Center / Campus | Common Notes |
|---|---|---|
| 01 | Andover, MA | Legacy processing campus |
| 02 | Atlanta, GA | Legacy processing campus |
| 03 | Austin, TX | Active campus for individual and business returns |
| 04 | Brookhaven, NY | Legacy processing campus |
| 05 | Cincinnati, OH | Active campus, frequent IMF processing |
| 06 | Fresno, CA | Active campus, high-volume individual returns |
| 07 | Kansas City, MO | Active campus for IMF and BMF |
| 08 | Memphis, TN | Legacy processing campus |
| 09 | Philadelphia, PA | Active campus, notices and adjustments |
| 10 | Detroit, MI | Legacy / reassigned operations |
| 11 | Martinsburg, WV | Enterprise Computing Center (ECC) support |
| 12 | Ogden, UT | Active campus, transcripts and adjustments |
| 13 | Philadelphia, PA | Alternate Philly routing |
| 14 | Richmond, VA | Legacy processing campus |
| 20 | Modernized IMF Routing | Common for CADE2-era processing |
| 89 | Submission Processing Support | Internal routing / special handling |
How to Use This Table
If your DLN begins with:
- 03, 05, 06, 07, 09, or 12 → Your return entered a currently active IRS campus
- 20 → Your return was routed through modernized IMF/CADE2 processing
- 01–14 (legacy) → Your return may have passed through older routing logic or reassigned workloads
This helps explain why two taxpayers who filed on the same day may experience different processing speeds.
Why Service Center Codes Matter During Delays
When a return is:
- Pulled for manual review
- Sent to ERS, IVO, or RIVO
- Adjusted after filing
The service center code determines:
- Which IRS unit owns the case
- Which backlog applies
- Where correspondence originates
This is why IRS agents often reference “the campus” when discussing delays.
2. Tax Class Code (3rd Digit)
This digit identifies the type of tax document.
Common examples:
- 1 = Individual income tax (Form 1040)
- 2 = Business tax
- 3 = Employment tax
3. Document Type (4th–5th Digits)
These digits identify the specific form or return category, such as:
- Original return
- Amended return
- Adjustment or supplemental filing
This helps the IRS distinguish between different filings tied to the same taxpayer.
4. Julian Date (6th–8th Digits)
The Julian date represents the day of the year the return was processed.
For example:
- 032 = February 1
- 120 = April 30
This gives insight into when your return entered active processing.
Julian Date Calendar – 2026
IRS Processing & Transcript Reference
The IRS often uses Julian dates inside systems like DLNs, processing logs, and internal posting schedules. A Julian date represents the day number of the year, from 001 to 365 (2026 is not a leap year).
January 2026
| Date | Julian |
|---|---|
| Jan 1 | 001 |
| Jan 5 | 005 |
| Jan 10 | 010 |
| Jan 15 | 015 |
| Jan 20 | 020 |
| Jan 25 | 025 |
| Jan 31 | 031 |
February 2026
| Date | Julian |
|---|---|
| Feb 1 | 032 |
| Feb 5 | 036 |
| Feb 10 | 041 |
| Feb 15 | 046 |
| Feb 20 | 051 |
| Feb 25 | 056 |
| Feb 28 | 059 |
March 2026
| Date | Julian |
|---|---|
| Mar 1 | 060 |
| Mar 5 | 064 |
| Mar 10 | 069 |
| Mar 15 | 074 |
| Mar 20 | 079 |
| Mar 25 | 084 |
| Mar 31 | 090 |
April 2026
| Date | Julian |
|---|---|
| Apr 1 | 091 |
| Apr 5 | 095 |
| Apr 10 | 100 |
| Apr 15 | 105 |
| Apr 20 | 110 |
| Apr 25 | 115 |
| Apr 30 | 120 |
May 2026
| Date | Julian |
|---|---|
| May 1 | 121 |
| May 5 | 125 |
| May 10 | 130 |
| May 15 | 135 |
| May 20 | 140 |
| May 25 | 145 |
| May 31 | 151 |
June 2026
| Date | Julian |
|---|---|
| Jun 1 | 152 |
| Jun 5 | 156 |
| Jun 10 | 161 |
| Jun 15 | 166 |
| Jun 20 | 171 |
| Jun 25 | 176 |
| Jun 30 | 181 |
July 2026
| Date | Julian |
|---|---|
| Jul 1 | 182 |
| Jul 5 | 186 |
| Jul 10 | 191 |
| Jul 15 | 196 |
| Jul 20 | 201 |
| Jul 25 | 206 |
| Jul 31 | 212 |
August 2026
| Date | Julian |
|---|---|
| Aug 1 | 213 |
| Aug 5 | 217 |
| Aug 10 | 222 |
| Aug 15 | 227 |
| Aug 20 | 232 |
| Aug 25 | 237 |
| Aug 31 | 243 |
September 2026
| Date | Julian |
|---|---|
| Sep 1 | 244 |
| Sep 5 | 248 |
| Sep 10 | 253 |
| Sep 15 | 258 |
| Sep 20 | 263 |
| Sep 25 | 268 |
| Sep 30 | 273 |
October 2026
| Date | Julian |
|---|---|
| Oct 1 | 274 |
| Oct 5 | 278 |
| Oct 10 | 283 |
| Oct 15 | 288 |
| Oct 20 | 293 |
| Oct 25 | 298 |
| Oct 31 | 304 |
November 2026
| Date | Julian |
|---|---|
| Nov 1 | 305 |
| Nov 5 | 309 |
| Nov 10 | 314 |
| Nov 15 | 319 |
| Nov 20 | 324 |
| Nov 25 | 329 |
| Nov 30 | 334 |
December 2026
| Date | Julian |
|---|---|
| Dec 1 | 335 |
| Dec 5 | 339 |
| Dec 10 | 344 |
| Dec 15 | 349 |
| Dec 20 | 354 |
| Dec 25 | 359 |
| Dec 31 | 365 |
5. Daily Sequence Number (Last 6 Digits)
The final digits are a unique sequence number assigned that day.
This ensures that:
- No two returns share the same DLN
- Each return can be precisely located
Think of it as the return’s serial number.
Where You Can Find the DLN
The DLN commonly appears on:
- IRS Account Transcripts
- Adjustment notices
- Audit correspondence
- Internal IRS references
It is usually labeled simply as “DLN” or embedded in transcript entries.
How the DLN Is Used During Reviews and Delays
If a return is:
- Pulled for manual review
- Sent to ERS, IVO, or RIVO
- Converted from digital to paper handling
The DLN tells the IRS technician exactly where the return is stored—digitally or physically.
This is why older or paper-related cases often reference DLNs during correspondence.
DLN vs. Transaction Codes: Different Roles
It is important not to confuse DLNs with transaction codes.
- DLN = Identifies the document
- Transaction Codes (TCs) = Describe actions taken on the account
Both appear on transcripts, but they serve entirely different purposes.
What Happens Next?
Once assigned, the DLN is:
- Stamped permanently on the Master File
- Used for all future references to that return
If your return is pulled for review, the DLN allows the IRS to retrieve the correct digital or physical “folder” instantly.
The IRS Document Locator Number DLN is the IRS’s internal GPS for your tax return.
It tells the IRS:
- Where your return came from
- What type of document it is
- When it entered processing
- How to find it during reviews
While most taxpayers never need to act on a DLN, understanding it adds clarity when returns stall or move into manual handling.
