Payroll Tax Notices: Assign the Response, Prove the Resolution
Updated: Oct 11
A payroll tax notice can be a bill, a request for information, a change to next year's deposit schedule or a warning that needs an internal correction. Sending every letter to the payroll provider creates a queue without telling anyone what must happen before the agency's deadline.
Start by identifying the agency, employer account, tax form, period and requested action. Assign one person to control the response, preserve each actual deadline, and compare the agency's figures with the relevant return and payment evidence. Keep the case open until its required actions and outcome are documented. A provider ticket marked resolved is useful evidence of the provider's work; the agency account may still need attention.
Use this workflow when a U.S. employer receives tax correspondence that needs a documented response or internal review. The IRS examples explain different routing decisions, with a California example showing why state procedures need their own review. Your actual notice and current agency instructions govern. Involve a qualified tax professional or attorney when the amount, dispute procedure, representation or collection consequences are uncertain.
Table of contents
Decode the requested action before calling it a bill
Read every page, including the explanation, payment instructions and response or appeal information. Preserve the original notice and envelope or the complete digital notice. A scanned first page can omit the instruction that determines the route. Record when the business received it as well as the issue date printed on it.
Use the notice code to find the agency's explanation, then read that explanation against the letter in hand. The IRS notice search uses the CP or LTR number to identify the correspondence. Its general guidance distinguishes agreeing with a requested action, disputing information and having an amount due. A generic online explanation does not establish that the figures on your notice are correct.
The following IRS notices illustrate three substantially different assignments:
CP136: prepare for the deposit requirement. This notice concerns the following year's Form 941 deposit requirements, based on the lookback period. Check the underlying liabilities against original Forms 941. The IRS says amended returns are not included in that lookback calculation. If the notice shows zero tax for a period, the IRS says it has no record of receiving a Form 941 for that period and directs you to file any missing return as soon as possible. Have the tax reviewer check the filing evidence, arrange any required filing and resolve a schedule discrepancy. Carry the confirmed schedule into the operating calendar.
CP134B: investigate a deposit-credit discrepancy and the balance due. The notice compares deposits credited to the account with the amount reported on the return. The IRS directs employers who agree to pay as requested, and employers with payments missing from the notice to contact the number on it. Preserve the pay-by date while investigating the difference.
CP276B: repair the deposit process even without a reply. The IRS says it did not receive the correct amount of timely deposits but did not charge the usual penalty this time. Its explanation says no reply is required, while calling for a review of records and current deposits and correction of the retained tax return and liability schedule copies. Assign those steps to the reviewer. Correcting a retained copy is not, by itself, an instruction to file an amended return; the reviewer must determine whether a separate filing action is needed.
Keep separate routes for a request to supply information, an account-registration problem and a state unemployment tax rate or benefit-charge matter. A worker's levy or garnishment instruction also belongs with the employee deduction and remittance process, even if it arrived from a tax agency. Do not use this employer-account workflow as a substitute for that process.
Verify suspicious correspondence through the agency's official website or an independently established contact route before sharing information or paying. The IRS normally first contacts taxpayers by mail, and its current contact guidance identifies additional authorized channels and scam signals. Do not treat an unexpected email attachment or a caller's urgency as proof of an authentic tax demand.
Start with the action stated in the notice, then assign its reviewer and dates.
Notice support is a service detail to examine before choosing a provider. A free SelectSoftware Reviews advisor consultation is an optional starting point for discussing payroll services. Ask prospective providers who receives letters, supplies filing and payment records, and owns the response.
Give each agency deadline an owner who can act
Choose a case owner with responsibility for seeing the notice through, plus a backup who can retrieve its records. The owner need not prepare every calculation or sign every response. They do need to know whether the tax reviewer, payment approver, provider and agency representative have accepted their parts of the work.
Separate the agency's response date from its payment date, effective date or appeal deadline. A letter may contain more than one. Copy each date and the instruction attached to it into the record. If the deadline is expressed as a period from mailing or another event, retain that language and have the responsible reviewer confirm the calculation. Do not silently replace it with a guessed date based on when payroll saw the scan.
Add an internal review date early enough to prepare and approve the action. That is a company control, not a change to the agency's deadline. For example, a business might request provider evidence within two business days and escalate an unanswered request the following morning. Set that expectation according to the time remaining.
When a notice arrives close to its deadline, contact the qualified reviewer immediately. They should determine the available response, payment or relief options from the notice and the applicable procedure. Keep the original dates active unless a valid extension or other change has been verified and documented. A help-desk ticket, a callback promise or forwarding the letter does not by itself document such a change.
Confirm authority before asking someone to contact the agency. IRS authorizations distinguish representation through a power of attorney from permission to inspect or receive tax information. Check the tax matters and periods covered, the person who may act and whether the chosen authorization permits the intended work. A provider's access to payroll software does not answer those questions.
In a small business, the owner or controller may approve the response while the bookkeeper assembles the evidence and an outside tax professional handles the disputed issue. Name those roles for this case. An instruction addressed only to “finance” can wait while three people assume someone else is handling it.
Trace the difference through the right account and period
Build the comparison around the employer account and tax period shown on the notice. Start with the entity's legal name, federal or state account identifier, tax form and period ending date. Match those to the return and payment records. Similar business names, multiple entities or a recently changed provider can make a report look relevant when it belongs to a different account.
Record three figures separately: what the business reported, what the agency says it has and what the supporting records currently establish. Separate tax, credited payments, penalties and interest when the notice does. An unexplained total variance is difficult to assign; a missing payment credit can be traced to a particular transaction.
For a payment question, gather the confirmation number, method, amount, payment date and intended tax form and period. Reconcile these with bank activity and the provider's transaction details. A debit to fund a provider is not the same record as a deposit credited to the agency. If the provider handles pooled funds, ask it to identify the specific employer transaction behind its claim that the tax was paid.
IRS Topic 651 calls for a copy of an electronic transaction showing the confirmation number and payment method when a payment has not been credited. It also tells taxpayers to send copies rather than original documents. Use the requested evidence to make the trace intelligible; a screenshot showing only an aggregate bank debit may leave the agency unable to identify the payment.
For a return discrepancy, preserve the version actually filed, its filing acknowledgment if available, any rejection or later adjustment, and the supporting liability report. A payroll dashboard's current totals may reflect a correction made after the original filing. Label each version and explain which one answers the notice's question before changing a return or the payroll ledger.
Maintain a short missing-evidence list. Each item should say what fact it would establish, who must provide it and when it is needed. “Obtain filing acceptance for Entity A, Form 941, quarter ended June 30” is a usable request. “Send all tax documents” invites a large file collection that may still omit the decisive acknowledgment.
Build the Notice Response and Resolution Record
Use one record for one notice or a clearly identified set of related notices. Copy the blocks below into a controlled spreadsheet, document or case system. Use a case ID in the ordinary tracking list; keep full account identifiers, employee information and supporting documents in appropriately restricted storage. The record should point to evidence without exposing it to every person who can see the queue.
Block A: the demand and the clocks
Notice identity: agency, notice code and reference, employer entity, account, tax form and period. Record related case IDs rather than merging unrelated entities into one entry.
Receipt: printed issue date, received date and the location of every page and attachment. Name the person who verified the notice through an appropriate official route if authenticity was questioned.
Requested action: payment, information, dispute decision, configuration change or internal review only. Write the actual instruction in a brief description, and retain its source page.
Agency dates: response, payment, appeal or effective dates that apply. Give each its own line with the relevant instruction. Write “none stated, reviewer checking” when an expected date is unclear; do not turn an empty field into permission to wait.
Internal commitments: the review date, provider evidence due date and next escalation time chosen by the business. Keep them visually distinct from the agency dates.
Responsibility: case owner, backup, tax reviewer, response preparer and payment or filing approver. Include the accepted task and necessary agency authorization for an outside representative.
Block B: the comparison and the decision
Agency position: the amount or change stated, split into the components shown. For a nonmonetary notice, record the schedule, account status or requested information instead.
Company position: the amount or status supported by the filed return, transaction record or other relevant evidence. Identify the version and storage reference, not merely a report name.
Open difference: the exact unresolved fact and the evidence request that will answer it. Assign the request and due time. Keep an unconfirmed provider explanation here until the supporting record arrives.
Approved disposition: agree and perform the requested action; dispute with a documented basis; investigate with an immediate protective action approved by the reviewer; or perform the required internal review when no reply is requested. Record who approved the choice, the next action and the evidence required to close the case. These are working descriptions, not legal conclusions or automatic filing instructions.
Block C: the response diary and the outcome
Response entries: date, sender, channel, documents sent, exact requested action and retained transmission evidence. Add phone-contact notes and subsequent instructions as separate dated entries. Preserve a copy of the approved response and its attachments together.
Agency outcome: what the later correspondence or account evidence establishes, the amount or status remaining, and the reviewer who accepted the conclusion. If no agency response was required, record that instruction and the completed internal review instead of waiting for a nonexistent acknowledgment.
Preventive work: a separate owner, due date and completion check for any calendar, account, approval or service change. Keep that work visible even when the notice itself is resolved.
Next review: a specific date and event to check while the response or outcome remains pending. Write what will cause escalation, such as another demand, an approaching agency date or a provider failing to supply the promised trace.
To review the record quickly, ask whether someone covering for the case owner can find the next required action, its actual deadline, the person able to perform it and the evidence needed to confirm it. If any answer is missing, the handoff is incomplete.
Three fictional notices, three different endings
The following examples are fictional operational cases. Their dates, amounts and internal commitments illustrate how to use the record; they do not establish an agency deadline or an entitlement to a particular adjustment.
A balance notice with an unproved payment explanation
A company receives a CP134B showing $24,000 of reported deposits and $18,000 credited, leaving a $6,000 difference. Its fictional letter says to pay by October 28. The payroll provider says the missing amount was deposited to another period. Finance can see a bank debit for the full $24,000, but it has no employer-specific payment confirmation.
The case owner enters October 28 as the agency payment date and sets an earlier internal evidence deadline. Block B shows $6,000 as the open difference. The provider's explanation remains unconfirmed, with a request for the transaction reference, payment method, intended period and evidence supporting the claimed application. The bank debit supports the funding history; it cannot answer every allocation question.
The tax reviewer decides the appropriate agency contact and any action needed before October 28. The response diary records the contact, the supplied evidence and any verified instructions. Finance does not post a correction merely to make the ledger resemble the notice, or automatically pay a second $6,000 because a provider response is late. The reviewer must address the actual demand while the trace is unresolved.
If later agency correspondence or account evidence confirms a corrected credit, record what it establishes and whether an amount remains. Keep a separate preventive task if the provider's evidence arrived too late to support the original review. Closing the credit question does not fix that service failure.
A schedule notice that requires a future operating change
A controller receives a CP136 for the following year. The current payroll configuration is different from the classification shown. The owner asks the tax reviewer to compare the notice with the applicable original Forms 941 and establish the correct schedule. The reviewer also checks filing evidence for any period shown as zero and arranges any missing Form 941 filing as soon as possible. That filing task is recorded separately from the future schedule change.
Once the reviewer confirms the classification, Block B records the approved setup change and its effective year. The provider supplies confirmation of the setting, and finance carries the result into the federal payroll tax deposit calendar. A second person checks the first applicable obligation against the approved classification. This operating check is a company control, not a substitute for establishing the tax rule.
If the source returns do not support the notice, the reviewer determines the contact or correction route. The case stays visible for that unresolved issue. Labeling it “annual notice received” would conceal the decision about which schedule will govern the next year.
A warning with no response requirement
A bookkeeper receives a CP276B and correctly records that the IRS explanation says no reply is required. The case owner still assigns a review of the deposit records and current procedure. The reviewer finds that an internal approval was consistently too late for the company's payment process.
The record documents the finding and a changed approval time, with a backup approver assigned. The reviewer also checks the retained tax return and liability schedule copies and corrects any inaccuracies identified in the review, following the IRS instruction. A later deposit check confirms that the revised handoff was performed as designed. The company can close this internal review without inventing a requirement for an IRS acknowledgment. Preserve the notice and the reasoning for that disposition. If a later letter makes a different demand, open or link the appropriate case and read its own instructions.
Who obtains the missing payment trace, and who keeps the agency response moving? A free SelectSoftware Reviews advisor conversation is an optional starting point for identifying payroll services to question about those notice-support tasks.
Send a focused response and preserve the receipt
Have the authorized reviewer approve the response and channel required for this notice. Identify the employer, reference, form and period; describe the particular disagreement or requested action; and connect each supporting attachment to the fact it establishes. A short explanation with identifiable records is more useful than a folder of unexplained payroll exports.
Keep the approved package together before sending it. Record its version and the attachment list so a backup can reconstruct exactly what the agency received. Retain originals and send the copies the agency requests. Restrict access to account and employee details, and share only the relevant supporting information through the approved channel.
The IRS Document Upload Tool can provide a confirmation after submission of supporting documents. Follow the applicable notice and tool instructions to establish whether that route fits your correspondence. The IRS explicitly says not to submit tax returns through the tool. Uploading notice support is therefore not evidence that a required amended return has been filed.
For another submission route, retain the corresponding transmission evidence and the copy sent. Log a phone contact with the date, person or identifier, issue discussed, documents requested and next instruction. Separate what the caller said from what a written notice or later account record confirms. If promised follow-up affects an imminent date, have the reviewer resolve that uncertainty rather than relying on an undated callback note.
When the reviewer identifies a return correction, create a linked correction task with its preparer, approval, filing route and acknowledgment. Preserve the notice case's dates alongside it. Do not assume that filing a correction answers every part of an existing demand or automatically stops the agency's process.
Use the response diary for follow-up events, not a single overwritten comment. A second letter, a rejected upload or newly obtained payment trace may change the next action. The previous entry should remain available to explain why the team acted as it did at the time.
Confirm what changed before closing the notice
Define the required closing evidence when the reviewer approves the disposition. For a disputed credit, that could be correspondence or account evidence establishing its application and the remaining balance. For a schedule notice, it may be the confirmed classification, effective setup and completed operating check. For a no-reply warning, it is the documented internal review and required corrective work. Different notice types produce different endings.
A submission confirmation answers whether a package was received through that channel. It may not answer whether the agency accepted the explanation or adjusted the account. Keep those records in the response diary and label the unresolved decision separately.
State systems also distinguish submission from determination. California EDD's e-Services guidance describes electronic protests for matters such as unemployment insurance rates and benefit charges, with a confirmation after submission. It separately describes later determinations delivered by mail and available in e-Services. In a California case, preserve both stages and follow the applicable notice's protest instructions. Do not carry that process or its timing over to another state.
When evidence resolves only part of a demand, write the remaining issue explicitly. A payment credit may be corrected while a penalty question remains. The reviewer should identify which obligations are complete, which dates still apply and who owns the unfinished action. Avoid a single closed status that hides an outstanding balance or determination.
Review the open-case list at a cadence that reflects actual deadlines. The notice closest to a required action needs attention even if its dollar amount is small. An older unanswered submission also needs a specific next check, but age alone does not prove that an agency deadline was missed. Use the notice dates and diary to explain the escalation.
Store the final record with its notice, response copies, transmission evidence and closing support under the payroll record retention schedule. Give linked preventive work its own status. A repaired account can be closed while a vendor-report improvement remains assigned; a required configuration change should be completed before the schedule-change case is treated as finished.
For a California protest, retain the submission confirmation and the later determination as separate diary entries.
Make the provider's notice service a specific commitment
Route agency correspondence to a named employer owner. IRS guidance on outsourcing payroll duties says the IRS sends correspondence to the employer's address of record and strongly suggests keeping that address under employer control rather than changing it to the provider's address. In ordinary payroll service arrangements, buying notice support does not by itself transfer the employer's federal tax responsibility. Other arrangements, including certain CPEO situations, can assign liability differently. Have the reviewer confirm the arrangement that applies to this notice before deciding who must respond.
Ask who receives the original correspondence, acknowledges the case, obtains the underlying records, contacts the agency, approves a response and monitors the outcome. Identify the internal person who must act when the provider lacks authorization or needs employer approval. Price that retained work when deciding whether the service matches your team's capacity.
Request a sample notice case from the vendor with confidential details removed. Check whether it distinguishes the agency deadline from a service target, names the employer and period, and preserves the response and outcome. Ask when the employer can obtain those records, including after the contract ends. A status dashboard is helpful only when it leads to the evidence and responsibility your reviewer needs.
A provider transition creates a particular handoff problem: a notice can arrive after the old service stopped running payroll but relate to a period it processed. Assign access to the old filing and payment records, the person coordinating each provider and the route for any continuing representation. Document the boundary by entity, form and period. The new subscription's start date alone cannot establish who has the evidence or authority.
For your next notice, fill Block A from the complete letter, identify the unresolved fact in Block B and have the reviewer approve the next action. Leave Block C ready for each response and its outcome.
Use your completed record to identify the notice tasks your business still owns. Discuss those responsibilities in a free SelectSoftware Reviews advisor consultation, then ask potential services to specify the evidence, approval handoff and follow-up they provide.
Continue with related tools:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
