What a CP166 is
A CP166 tells a business that the IRS tried to collect its monthly installment agreement payment by direct debit and the bank returned it for insufficient funds. The IRS’s own summary: “We couldn’t withdraw your monthly payment because there wasn’t enough money in your bank account.”
That is the whole of the event. No decision has been made about your agreement, no enforcement step has been taken, and nothing has been assessed against you on the strength of this letter.
It is worth being clear about who this letter is for, because the IRS’s own filing is misleading. The explainer page for the CP166 sits under irs.gov/individuals/. The notice specimen’s taxpayer identification field reads “Employer ID number.” The URL is a filing convention; the letter is addressed to a business, and this page is written to the person who runs one.
If you are looking for a notice numbered CP57, stop looking. There is no current IRS page, specimen or Internal Revenue Manual reference for one. A good deal of writing still names a CP57 for this situation; we could not find it published anywhere current, and the live notice in our hands is this one. We are not claiming one replaced the other — only that a CP57 is not something we can point you at today.
Your clock
There is no published interval for the second attempt, and we are not going to estimate one. The notice says “We’ll make a second attempt to withdraw your payment” and stops there. The IRS’s page repeats the substance and adds nothing about timing.
What that means practically is that the account should be funded now rather than by a date. You do not control the timing, the letter does not disclose it, and the gap between the failed debit and the retry is not something either source commits to.
On the notice itself: whatever dates are printed on your letter are yours, and they are what to work from. We are not reproducing a date from the IRS’s published sample of this notice, because that sample is an unpopulated template — its notice date, tax period and phone fields render as placeholders rather than as figures. That cuts both ways, and it is worth saying plainly: we are not telling you the CP166 carries no deadline, either. A blank template is not evidence about the letter on your desk. Read yours.
Sources: IRS Notice CP166 specimen and “Understanding your CP166 notice”, read 21 September 2026.
What happens next
One failed debit is a failed debit. The thing that turns it into a problem is the second one. The notice sets out the consequence in its own words: “If there are insufficient funds at that time, you may default on your agreement, interest will increase, and additional penalties may apply.”
“May default.” Permissive, in the IRS’s own drafting. And default is still not the end of the agreement.
Here is the sequence the letter sits at the front of, with what each step actually permits:
| Step | Notice | What the IRS may do |
|---|---|---|
| Before this | CP521 | The monthly reminder. The plan is running. |
| ▶CP166 — you are here | CP166 | A debit was returned for insufficient funds |
| Repeated failure | A pattern rather than an incident | The agreement may go into default |
| Default | A live agreement not being kept | Under 6159(b)(4): alter, modify, or terminate — three options |
| CP523 | CP523 | The 30-day notice of intent to terminate, and of intent to levy |
| CP504 | CP504 | Notice of intent to levy on a balance no longer under an agreement |
Two things about that table are worth dwelling on.
First, the statute does not oblige the IRS to end an agreement over a missed payment. Section 6159(b)(4) — “Failure to pay an installment or any other tax liability when due or to provide requested financial information” — permits the IRS to alter, modify, or terminate. A payment that has become too large for the business’s cash position is a candidate for the first two.
Second, the IRS cannot get from here to termination without writing to you again. Section 6159(b)(5) bars it from acting unless “a notice of such action is provided to the taxpayer not later than the day 30 days before the date of such action, and such notice includes an explanation why the Secretary intends to take such action.” The exception is a jeopardy finding, which removes both the 30 days and the explanation. Short of that, there is a letter between this one and the end of your plan.
And while the agreement is in effect, a levy on the covered tax is barred outright — section 6331(k)(2)(C). A bounced payment does not end the agreement, so that protection is still running today.
See the full library → · How the plan types differ: IRS payment plans → · If the monthly figure was never realistic: partial pay installment agreements →
What to do this week
Step one takes one phone call to your bank, not to the IRS: find out what the returned item actually cost you. The notice tells you to cover “your monthly payment plus any fees your bank may have charged you for insufficient funds” — and the fee is the part people leave out, because it is the bank’s number rather than the IRS’s and it does not appear anywhere on the letter. An account topped up to the payment amount exactly is an account that can fail the retry by the width of an overdraft charge.
Then:
- Fund the account for the payment and the fee, now, not by a date. The retry's timing is not published and is not yours to schedule.
- Find out why it failed. A timing mismatch between the debit date and the business's receivables is a different problem from a shortfall, and it has a different fix — one is a date change, the other is a payment change.
- If this is the second or third failure, treat it as a plan problem rather than a banking problem. Repeated failures are what produce a default, and a plan that keeps bouncing is usually a plan set at a figure the business cannot carry.
- If the monthly amount no longer fits, ask to change it before it defaults. Modification is on the same statutory ground as termination, and the ask is materially stronger while the agreement is still in good standing.
- Keep every other federal deposit and return current. The limb of 6159(b)(4) that ends most business agreements is not the missed installment — it is "any other tax liability when due."
Step 2 is the one that separates a bad month from a bad plan, and telling them apart is difficult rather than merely tedious. Deciding whether a business’s plan failed because of a cash-flow timing problem or because the payment is structurally too large requires reading the account against the business’s actual cycle, not against a monthly average — and the two look identical for the first couple of failures. Get it wrong in one direction and you move the debit date on a plan that was always going to fail; get it wrong in the other and you renegotiate a payment that only ever needed a different Tuesday.

