IRS notices are moving into the client's portal, not your mailroom

On August 6, 2026, the IRS announced an expansion of Business Tax Account: more digital notices, a downloadable EIN verification notice, and the ability to view and pay an existing payment plan or an Offer in Compromise. On the surface, that looks like a minor product update — a government portal added a few features. But it also changes how information reaches a tax firm, and that part matters more than it looks.

The notices themselves haven't changed. A CP211A still means the same thing it meant last year. What's changed is how the notice reaches the person who has to act on it — and most firm intake processes still assume that path is the mail.

What IR-2026-87 actually added

Three things changed, and they're worth looking at separately — they matter differently for a practitioner.

• More digital notices, including CP081B (We May Have a Refund for You), CP211A (Application to file extension of time approved — for Form 8868, used by exempt organizations filing a Form 990 series return or a related excise tax), and CP134R (Federal tax deposits discrepancy — Due a Refund), among others.
• A downloadable EIN verification notice — Notice CP575 — that the IRS says can replace Letter 147C at banks and financial institutions.
• Payment features: check an existing payment plan's balance and pay against it, or submit a payment toward an Offer in Compromise.

The part that changes your workflow

Business Tax Account belongs to the taxpayer, not the firm. The IRS grants access to sole proprietors with an EIN, individual partners and shareholders with a Schedule K-1 on file, S and C corporations, federal, state, local and tribal governments, and tax-exempt organizations — through a designated official, who can add other designated users.

That list is all people inside the business — not the firm. A practitioner with power of attorney doesn't reach Business Tax Account through Form 2848 or Form 8821; those authorize Tax Pro Account instead, a separate service built for practitioner access. Business Tax Account is where the client gets self-service notices directly, and those notices don't automatically show up in Tax Pro Account or reach the firm — that only happens if the firm has an intentional intake step set up to catch them. So the practical position is this: a notice deposited into a client's Business Tax Account has been delivered, in full, to the client — and has not, by that act, been delivered to you.

A notice in the client's portal has been delivered to the client. It has not, by that act, been delivered to you.

Paper had one advantage nobody designed on purpose: it was inconvenient in a way that forced a handoff. An envelope arrived, the client didn't understand it, and it got scanned and emailed to the firm. That inconvenience was the trigger. A notice sitting in a portal the client checks twice a year has no such trigger. It isn't lost — it's filed correctly, where nobody is looking.

Why this is a review problem, not just an intake problem

The obvious response is to treat this as a document-collection problem: add a step, ask the client to check the portal. That's too small a fix, because the notices most likely to get missed are exactly the ones that change a return position.

Look at the three notices named in the release:

• CP211A confirms a Form 8868 extension was approved. It's narrow in who receives it — exempt organizations filing a Form 990 series return, or a related excise tax on employee benefit plans — but for that client, it sets the date every downstream deadline is measured from.
• CP134R reports a federal tax deposit discrepancy. That means the payroll deposits in the client's books and the deposits the IRS has on record don't agree — and one of them is wrong.
• CP081B says a refund may exist for a period. That implies a filing or a credit the firm's file may not reflect.

None of these is administrative trivia. Each is a fact the return preparer needs, and the reviewer will assume it was checked. A discrepancy notice nobody read doesn't announce itself at review time — it shows up as a payroll reconciliation that ties to the client's books, which is exactly what a reviewer checks, and exactly what won't catch it.

What a firm should actually do about it

• Stop treating "no notices this year" as a good sign. Not getting forwarded mail used to be weak evidence that nothing arrived. Now it's no evidence at all.
• Make the portal check an explicit, named intake step with an owner and a date — not a line in a client letter asking them to forward anything they receive.
• Get authorizations current. Form 2848 and Form 8821 are still how a firm gets standing with the IRS on a client's account, and a lapsed authorization is worth finding in August rather than in March.
• Record what the notice changed, not just that it arrived. A scanned PDF in a folder repeats this problem one layer down: the document is kept, but the conclusion isn't.
• Treat deposit and payment notices as review inputs. If a CP134R exists for the year, the reviewer needs to know before signing off on the payroll reconciliation — not after.

The pattern underneath

This same pattern keeps showing up in tax administration: a process moves from paper to digital, the information becomes easier to get and easier to miss, and the firms that handle it well are the ones that replace an accidental trigger with a deliberate one. E-filing did this to signature pages. Bank feeds did it to statements. Portals are doing it to correspondence now.

The failure isn't carelessness. A workflow depended on friction, the friction was removed as a genuine improvement, and nothing replaced the job that friction used to do. The IRS has made these notices easier to get. Whether they reach the person who needs them is now entirely a question of firm process.

That's the gap Pernee is built for. A notice, the conclusion someone drew from it, and the return line it affects belong together — but in most firms they live in three different places: a portal, an email thread, and a workpaper. Pernee keeps them attached across the tools a firm already runs, so next year's reviewer asking "was there a deposit discrepancy?" gets an answer from the file instead of from whoever happens to remember.