IRS Automated Underreporter Practitioner Guide: AUR Matching, CP2501, and Pre-Filing Prevention

Most IRS notices that practitioners receive on behalf of clients do not originate with a revenue agent reviewing a file. They originate with a computer. The IRS Automated Underreporter program is a large-scale matching system that compares the income reported on information returns filed by payers against the income taxpayers report on their federal returns. When those two data sets disagree beyond a threshold, the AUR process begins automatically. Understanding how that matching logic works, what triggers it, and how to prevent it from initiating is among the highest-value competencies a practitioner can develop.

This guide is written for tax practitioners: enrolled agents, CPAs, attorneys, and PTIN-registered preparers who manage client correspondence with the IRS. It focuses on three things the existing ATP CP2000 guide does not cover: how the AUR matching system works and what data it draws from, how to prevent AUR notices before filing, and the CP2501 soft inquiry notice that precedes the CP2000 proposed deficiency in the AUR sequence. For the full CP2000 response workflow once a proposed deficiency is issued, see the ATP CP2000 Notice Practitioner Guide.

All regulatory figures, program descriptions, and procedural notes in this guide should be verified at IRS.gov before relying on them in client engagements. IRS program procedures, notice timelines, and data sources are subject to change by administrative guidance. This guide is informational and does not constitute legal or tax advice.

How the AUR Program Works: Data Sources and Selection Logic

Every year, payers: employers, financial institutions, brokers, partnerships, S corporations, and other entities: file information returns directly with the IRS. W-2s, 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 1099-B, 1099-R, 1099-K, and Schedule K-1 forms all flow into the IRS's information return database. For tax year 2025 returns, 1099-DA (digital asset proceeds) joins that data set as a new category. These filings are not courtesy copies. They are the IRS's primary third-party data source, and they exist independently of anything the taxpayer files.

The AUR matching program compares that third-party data against what appears on the taxpayer's return. The matching is automated and operates at scale. The system does not require a human to select a return for review; it identifies mismatches computationally. When the AUR system detects that income reported to the IRS on an information return does not appear on the taxpayer's return, or appears at a materially lower amount, it flags the discrepancy and initiates the AUR process.

What the matching program looks at

The AUR system does not simply compare a total income figure. It matches at the line level, comparing specific income categories on the return against the corresponding information return type. A 1099-NEC filed by a client's payer is matched against Schedule C or the wages line. A 1099-INT is matched against Schedule B interest income. A 1099-B is matched against Schedule D and Form 8949. A K-1 from a partnership is matched against the ordinary income, capital gain, and other items reported on the individual's return.

The AUR system applies judgment filters, not a raw dollar match. A taxpayer who received a 1099-MISC for $500 and reported that amount in a different income category than the IRS expected may or may not draw an AUR flag, depending on how the system maps the return data. A taxpayer who received a 1099-NEC for $15,000 and reported zero on Schedule C is a straightforward mismatch the system is designed to catch.

The AUR timeline: from matching to notice

AUR notices typically do not arrive in the same year the return is filed. The IRS processes matching after information returns are reconciled and filed, which takes time. Practitioners should expect AUR notices to arrive one to two years after the tax year in question. A 2024 return filed in April 2025 may generate an AUR inquiry in late 2025 or during 2026. This lag means the practitioner needs the original return and all supporting documents readily accessible well beyond filing season.

The IRS has expanded the AUR program's capacity over time, both in the volume of information returns it processes and in the categories of income it matches. Practitioners should not assume that a category of income that was rarely matched in prior years will remain outside the AUR system's reach. The program is designed to grow as information reporting expands.

Most Common AUR Triggers: 1099-NEC, 1099-DA, K-1, and Cash Transactions

Not all mismatches are equally likely to trigger AUR scrutiny, and not all AUR-triggered notices arise from deliberate underreporting. Many originate in reconciliation failures: a 1099 the client forgot to mention, a K-1 that arrived after the return was filed, or a broker-reported gross proceeds figure that does not account for the client's cost basis. Understanding the most frequent trigger categories helps practitioners focus pre-filing review where it matters most.

CP2501 vs. CP2000: Why the Soft Notice Still Demands an Immediate Response

The AUR process follows a defined sequence. Understanding where CP2501 and CP2000 each fall in that sequence, and what distinguishes them, is essential for advising clients correctly when a notice arrives.

What CP2501 is

CP2501 is an inquiry notice. The IRS sends CP2501 when it has identified a potential discrepancy between third-party information returns and what appears on the taxpayer's return, but has not yet completed its analysis to the point of proposing a specific deficiency. The notice identifies the income items in question, provides the amounts from the IRS's information return database, and asks the taxpayer or representative to review the discrepancy and respond with one of three positions: agreement, partial agreement, or disagreement with an explanation.

Because CP2501 precedes any formal deficiency proposal, responding to it gives the practitioner the opportunity to resolve the discrepancy at the inquiry stage. If the income was reported correctly and the IRS's information return data is wrong (for example, a 1099 that was issued in error and corrected, or a nominee situation where the income was reported to the IRS under the client's SSN but actually belonged to another party), the CP2501 response is the right place to make that argument with documentation.

What CP2000 is

CP2000 is a proposed deficiency notice. By the time CP2000 arrives, the IRS has analyzed the discrepancy identified in the CP2501 inquiry (or determined the discrepancy without a prior CP2501 in some cases) and is proposing specific additional tax, plus interest and potentially accuracy-related penalties. The CP2000 is not an assessment; it is a proposal, and the taxpayer still has the opportunity to agree, partially agree, or disagree. But the stakes are higher, the dollar amount is specified, and interest has been accruing from the original due date of the return.

For the complete CP2000 response workflow, including how to structure an agreement, partial agreement, or disagreement response, document the reply, and track the case through the AUR process after CP2000, see the ATP CP2000 Notice Practitioner Guide. This guide focuses on the upstream stages: the CP2501 inquiry and pre-filing prevention.

The structural difference: inquiry vs. proposed deficiency

Responding to a CP2501

A CP2501 requires a written response sent to the IRS address shown on the notice. The notice will identify the tax year in question, the discrepancy items by income type, the information return amounts the IRS has on file, and the response instructions. Read the notice completely before preparing any response: the notice will specify where to send the reply and will identify the contact information for the AUR unit handling the case.

Step 1: Review the notice against the return and the information returns

Pull the original return and compare it line by line against what the CP2501 identifies. The notice will show the income amounts the IRS has from its information return database. For each item the notice identifies, determine whether the income was reported on the return (possibly in a different place than the IRS expected), reported at a different amount, or not reported at all. Also pull the client's wage and income transcript for the year in question. The transcript shows the same information return data the IRS used to generate the notice. See the IRS transcripts guide for practitioners for how to access wage and income transcripts through the Transcript Delivery System.

Step 2: Determine the correct response position

There are three available response positions for a CP2501:

Step 3: Prepare and send the response within the window

The response window for CP2501 is currently 30 days from the notice date; verify the response window in the specific notice you receive, as response windows can change by administrative guidance. Send the response to the address shown on the notice, not to the general IRS mailing address. If Form 2848 is on file authorizing the practitioner to receive and respond to AUR correspondence, the response should include the practitioner's identification. Keep a copy of everything submitted: the response letter, all attachments, and proof of mailing. If the response is sent by mail, use certified mail with return receipt or a similar trackable method to document that the response was timely.

Do not assume the IRS will call or follow up if the response does not arrive. The AUR system moves to the next notice stage if a response is not received within the window. Track the response deadline on the client file and confirm internally that the response was sent.

Escalation to CP2000 When CP2501 Is Ignored

When a CP2501 goes unanswered within the response window, the IRS does not close the matter. It issues a CP2000 proposed deficiency notice. The CP2000 contains the IRS's proposed additional tax calculation based on the same discrepancy identified in the CP2501, with interest accrued from the original due date of the return, and potentially an accuracy-related penalty under IRC Section 6662 (currently 20% of the underpayment attributable to the understatement of income, subject to applicable exceptions and the negligence or reasonable cause analysis).

The interest cost of allowing CP2501 to escalate to CP2000 is not trivial. Interest under IRC Section 6601 accrues from the original return due date, not from the date the CP2000 is issued. A client whose 2023 return was due April 15, 2024 and who receives a CP2000 in mid-2026 has already accumulated over two years of interest on the proposed deficiency amount before the CP2000 even arrives. Responding to the CP2501 at the inquiry stage stops that clock much earlier.

If CP2000 is also ignored, the IRS issues a statutory notice of deficiency (the "90-day letter"). The 90-day letter gives the taxpayer 90 days to petition the Tax Court to challenge the proposed deficiency before it is assessed. If the Tax Court petition is not filed within 90 days, the IRS can assess the deficiency and begin collection. At that point, the matter has moved from an AUR inquiry to a collection case, with all the consequences that entails.

Proactive Filing Strategy to Minimize AUR Exposure

The most effective AUR response is one you never have to write. A return that reconciles cleanly with all available information returns gives the AUR matching system nothing to flag. Building pre-filing reconciliation into the return preparation workflow is the highest-leverage AUR prevention practice.

Reconcile all information returns before signing

Before signing a return, the practitioner should have a complete picture of every information return that has been filed with the IRS under the client's SSN. The wage and income transcript is the most direct way to get that picture. It shows every W-2, 1099, and K-1 the IRS has on file for the client for the year in question. Pull the transcript before finalizing the return and compare it against the return being prepared. Every item on the transcript should either appear on the return or have a documented explanation for why it is not treated as taxable income. See the IRS transcripts guide for practitioners for the transcript access workflow.

How to handle a 1099 the client disputes

Clients frequently dispute 1099s: the amount is wrong, the income was for a prior year, the 1099 was issued under the wrong SSN, or the income was a nominee amount that the client passed through to another party. The practitioner's instinct to accommodate the client by simply leaving the item off the return is, in most cases, the wrong approach.

The AUR system matches against the 1099 in the IRS database, not the 1099 the client believes should have been issued. If the 1099 is in the IRS database at one amount and the return shows a different amount, the AUR system will flag the discrepancy regardless of whether the underlying dispute is legitimate. The correct approach is:

• Report the income on the return at the amount that is actually correct and taxable, with appropriate documentation in the return workpapers.
• If the 1099 is wrong, advise the client to request a corrected 1099 from the payer. If a corrected 1099 arrives before the return is filed, file with the corrected amount. If it arrives after filing, the corrected amount may still reduce or eliminate any AUR discrepancy once the corrected 1099 is in the IRS database.
• If the income was a nominee amount that belongs to another person or entity, report the gross amount on the return and then claim the nominee deduction, and issue a nominee 1099 to the actual recipient. This is the IRS-required treatment for nominee income and avoids the AUR mismatch that would arise from simply omitting the amount.
• Document the dispute analysis in the return file so that if a CP2501 arrives, the response is already organized.

Documenting basis for digital assets before filing

For tax year 2025 and later, digital asset brokers are filing 1099-DA reporting gross proceeds from digital asset dispositions. When 1099-DA data flows into the AUR matching program, the system will be able to identify clients who received 1099-DA proceeds that are not reflected on Form 8949. The basis issue is the core challenge: a 1099-DA reports gross proceeds, and the taxable gain depends on the client's cost basis in the digital assets disposed of. If the basis is not documented and reported on Form 8949, the AUR system may match the gross proceeds against a return that appears to show no corresponding gain calculation.

Before filing a return that includes digital asset activity, the practitioner should have the client's complete transaction history from the broker and any exchanges used, calculate gain and loss using the appropriate cost basis method (FIFO is the default unless a specific identification method is established in writing before the sale), and report every disposition on Form 8949. Do not wait for a 1099-DA; pull the transaction history directly. See the 1099-DA practitioner guide for the full digital asset reporting workflow.

1099 and Third-Party Data Reconciliation Pre-Filing Checklist

The following checklist covers the reconciliation steps that most directly reduce AUR exposure. These are not optional quality control items for complex returns; they are the baseline pre-filing protocol for any return that includes income beyond a single W-2.

Form 2848 and Practitioner Representation Through the AUR Sequence

The AUR process generates notices sent to the taxpayer's address on file with the IRS. Without a Form 2848 Power of Attorney on file authorizing the practitioner to receive AUR correspondence, the client will receive CP2501 and CP2000 notices directly, without the practitioner necessarily being aware. Clients who receive AUR notices without a practitioner's involvement frequently misunderstand the notice, respond inappropriately (or do not respond), or miss the response window entirely before contacting the preparer.

Why Form 2848 should be in place before a notice arrives

A Form 2848 with a properly completed authorization line for AUR matters enables the IRS to send copies of AUR correspondence to the practitioner directly and authorizes the practitioner to call the AUR unit, correspond on the client's behalf, and sign AUR responses. The authorization must specifically cover the tax years and matter types at issue; a Form 2848 that covers "all matters" or that covers a different proceeding type may not reach the AUR unit's records in a way that triggers practitioner copy routing for every AUR notice.

The most effective practice is to have Form 2848 executed and filed with the IRS as part of the return preparation engagement for clients with any meaningful AUR exposure: those with multiple 1099 income sources, pass-through K-1 income, digital asset transactions, or prior AUR history. This gives the practitioner early visibility into any AUR inquiry before the client has had the opportunity to mishandle it.

Note that only credentialed practitioners (enrolled agents, CPAs, and attorneys) may represent clients before the IRS AUR unit under a Form 2848. PTIN-only preparers are not authorized to represent clients in AUR proceedings and must refer clients to a credentialed representative if a CP2501 or CP2000 requires representation. See the Form 2848 Power of Attorney guide for tax preparers for the full authorization workflow, scope of authority, and CAF submission process.

Digital Assets and the AUR Matching Program

Digital asset reporting represents one of the most significant expansions of the IRS's information return infrastructure in many years. Prior to the 1099-DA requirements taking effect, digital asset income was self-reported with no systematic broker-level check against the taxpayer's return. That is changing as the 1099-DA framework takes effect for tax year 2025.

What practitioners should expect

As 1099-DA filings accumulate in the IRS's information return database, AUR inquiries related to digital asset income are expected to increase. The pattern will likely resemble the 1099-B AUR experience: the IRS will have broker-reported gross proceeds figures, and when those figures do not appear on the taxpayer's return (or appear with an unexplained discrepancy), the AUR system will flag the mismatch.

The reconciliation challenge with digital assets is more complex than with traditional securities. A client may have transacted across multiple exchanges, some of which may report under the 1099-DA framework and some of which may not (depending on whether the exchange qualifies as a "broker" under the applicable regulations). The gross proceeds reported on a 1099-DA reflect the sale proceeds without any consideration of the client's cost basis. If the client sold digital assets with a high cost basis, the taxable gain may be much lower than the gross proceeds figure; but if the Form 8949 does not show the corresponding entries, the AUR system will see proceeds without a matching gain calculation.

The basis problem and pre-filing documentation

Basis is the central issue for digital asset AUR prevention. Unlike traditional securities where brokers have tracked cost basis for years, digital asset basis records are often incomplete, inconsistent across exchanges, and dependent on the client having maintained their own transaction records. Before filing any return that includes digital asset dispositions:

• Obtain the complete transaction history from every exchange and wallet the client used during the year, not only from exchanges that issued 1099-DA.
• Calculate gain and loss for each disposition using the chosen cost basis method (document the method selection; the IRS default is FIFO).
• Report every disposition on Form 8949 with the acquisition date, disposition date, proceeds, and basis for each transaction (or use the summary totals with a broker statement attached where permitted).
• Confirm that the total proceeds on Form 8949 reconcile to the 1099-DA proceeds figures where 1099-DA was issued. Document any discrepancy with an explanation.

See the 1099-DA practitioner guide for the full digital asset reporting framework, including the broker definition, the phase-in timeline, and the Form 8949 reporting mechanics.

Statute of Limitations Under the AUR Program

The AUR matching program operates within the IRS's assessment statute of limitations. Understanding the applicable SOL is important for advising clients who receive AUR inquiries for older tax years, and for practitioners evaluating whether an older return warrants protective action.

Standard three-year SOL

Under IRC Section 6501(a), the IRS generally has three years from the later of the return due date or the actual filing date to assess additional tax. For most AUR cases involving returns filed on time, this means the IRS has three years from the April 15 due date (or extended due date if an extension was filed) to issue an assessment. An AUR inquiry that arrives after the three-year SOL has expired cannot result in a valid assessment without falling into an exception.

When a client receives a CP2501 for a year that appears to be approaching or past the three-year SOL, flag that timing immediately. The SOL analysis is a threshold question that must be resolved before deciding how to respond to the notice. If the SOL has expired and no exception applies, the appropriate response is different from a case where the IRS is within its assessment window.

Extended six-year SOL for substantial underreporting

Under IRC Section 6501(e), the SOL is extended to six years when a taxpayer has omitted from gross income an amount that is more than 25% of the gross income stated on the return. This is the "substantial omission" rule. For a client who omitted a large 1099-NEC, a significant K-1 income item, or a material amount of digital asset proceeds, the six-year SOL may apply, giving the IRS twice the standard window to identify and pursue the discrepancy through the AUR process.

For clients with significant unreported income in prior years who are now in filing compliance, the six-year SOL rule is a key planning consideration. The practitioner should evaluate whether any prior-year returns are still open under the extended SOL and whether proactive voluntary disclosure or amended return filing is advisable. These are judgment calls that require a full facts-and-circumstances analysis; consult the applicable SOL rules in IRC Section 6501 and, for complex cases, legal counsel.

Advising clients on SOL when an AUR inquiry arrives for an older year

When a CP2501 arrives for a tax year that is three or more years in the past, the practitioner's first step is to determine whether the return was filed on time and whether the standard or extended SOL applies. If the return was filed on time and the discrepancy does not involve a substantial omission, the three-year SOL may have closed the assessment window before the CP2501 was even issued. In that case, the response should address the SOL directly, with documentation of the return filing date and a calculation of the applicable assessment deadline.

Do not assume the IRS has verified the SOL before issuing the notice. The AUR system generates notices based on matching logic; the SOL analysis is a legal question that the AUR unit may not have applied before sending CP2501. The practitioner's response raising the SOL may be the first time that question is formally presented to the IRS reviewer handling the case.

Return-by-Return AUR Risk Assessment Checklist

The following checklist is designed to be applied to each return before it is signed and filed. It surfaces the return characteristics most likely to generate an AUR inquiry and prompts the pre-filing reconciliation steps that address them. A return that clears this checklist cleanly is a return with materially lower AUR exposure.

Frequently Asked Questions

Related Guides in the AUR and Compliance Cluster

• IRS CP2000 Notice Practitioner Guide: the full CP2000 response workflow once a proposed deficiency is issued, including agreement, partial agreement, and dispute procedures
• IRS Transcripts Guide for Practitioners: how to access wage and income transcripts, account transcripts, and return transcripts through the Transcript Delivery System
• 1099-DA Digital Asset Reporting Guide for Tax Preparers: the full 1099-DA framework, broker definitions, phase-in timeline, and Form 8949 reporting mechanics
• Backup Withholding and B-Notice Guide for Tax Preparers: TIN mismatch correction, CP2100 B-Notice response, and backup withholding compliance
• Form 2848 Power of Attorney Guide for Tax Preparers: completing Form 2848, CAF submission, scope of authority, and representation rights by credential type
• IRS Audit Representation Guide: examination types, notice response, and practitioner representation in audit proceedings