TC 961: Reverse Centralized Authorization File Indicator

What the code actually does

IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) titles TC 961 "Reverse Centralized Authorization File Indicator" and defines its core effect plainly: it "reverses TC 960 and zeros module CAF indicator." Where a TC 960 caused notices and refunds to reach an authorized representative, TC 961 turns that off for the module it posts to.

Both codes share Doc Code 77, which is consistent with 961 functioning as the direct, dedicated undo for 960 rather than a general-purpose correction code borrowed from elsewhere.

It does not always mean someone sent a revocation letter

A practitioner seeing a TC 961 tends to assume the client fired them or fired someone else. That is one path, but not the only one. IRM 21.3.7.10, Deletions, Revocations and Withdrawals, describes the deliberate version: "the taxpayer revokes an authorization," annotated "Revoke" on the source document, or a "third-party withdraws," annotated "Withdraw" — either one processed from written correspondence with a current, dated signature.

But the same subsection closes with a reminder that produces the identical transaction without anyone writing a revocation at all: "when a taxpayer signs and files a new authorization (POA/TIA), all prior authorizations of the same type... are systemically revoked for the same tax matter and periods listed on the authorization," unless the client specifically checked the retention box and attached the prior authorization they wanted kept. A new Form 2848 can quietly knock an existing representative off a module — including one who was never told a new form had been filed.

On a business account, it can mean something bigger than a POA change

Doc 6209 splits TC 961 into two different mechanics, and the second one is easy to miss. On an ordinary module it simply "zeros module CAF indicator." But its own next clause reads: "BMF: For Reporting Agents File, posts to the entity, and zeros the RAF-Filing and EFTPS Indicators." ("BMF" is the Business Master File — the account record for a business taxpayer, as opposed to the Individual Master File a person's power of attorney sits on.)

That is not the same event scaled up. A Reporting Agents File authorization lets a payroll service provider file returns and make federal tax deposits on a business's behalf — filing and deposit authority, not just the right to receive copies of correspondence. A TC 961 on that record posts to the entity rather than a single tax module, and it zeros both the RAF-Filing Indicator and the EFTPS (Electronic Federal Tax Payment System, the IRS’s federal tax deposit platform) Indicator together. Losing that pair mid-payroll-cycle is a materially bigger event for a client than a practitioner losing notice copies, and it is worth confirming which kind of authorization actually lapsed before reacting.

What people mistake TC 961 for

People confuse it with a client's deliberate decision to change representatives, when the true cause was a new authorization of the same type, for the same tax matter and periods, that revoked the old one by system.

People also confuse it with routine account maintenance. The same chapter that defines the indicator also documents merge-driven transcripts when two modules each carry one from different campuses, and a reversal in that context reflects a data cleanup rather than anyone's decision to end representation.

And on a business account, people confuse it with an ordinary POA change when it is actually the Reporting Agents File authorization that lapsed — a payroll processing problem, not a correspondence problem.

What to do next

Before assuming a client revoked anything, ask whether a new authorization of the same type (Form 2848 or Form 8821) was filed recently for the same tax matter and periods — that alone can generate this code.

On a business account, confirm which authorization lapsed: a practitioner's module-level CAF indicator, or the entity-level RAF-Filing and EFTPS Indicators tied to a reporting agent.

Per IRM 21.3.7.10.2, expect correspondence to have gone to both the taxpayer and the affected third party — ask whether that letter was received before assuming no one was told.

Where the retention box on a new authorization was not checked, treat that as the likely explanation for an unexpected reversal before treating it as a client decision.

Refile promptly once the cause is identified, and confirm the new TC 960 actually posts to every module the engagement covers.

Read the sequence of TC 960 and TC 961 postings in order with the IRS Transcript Decoder rather than reacting to a single reversal line.