You are already under audit, and now the examiner has handed you a numbered list of everything they want to see: bank statements, invoices, contracts, reconciliations, maybe even records from years you thought were closed. That list is Form 4564, the Information Document Request — and how you respond to it will shape the rest of your examination.
Here is the part most taxpayers miss: an Information Document Request, usually called an IDR, is exactly what the name says. It is a request, not a court order. You have more options — and more traps — than the form's official tone suggests. Respond well and you keep the audit narrow, short, and boring. Respond poorly and you can expand the examiner's curiosity, waive a privilege you did not know you had, or end up facing a summons enforced by a federal court.
This guide walks through what Form 4564 is, what the IRS can and cannot demand with it, how to put together a response that protects you, and what happens if you refuse.
What Form 4564 Actually Is
Form 4564, Information Document Request, is the standard form examiners use to ask for documents during an audit. Each IDR describes the items requested, states the date your response is due, identifies the IRS representative making the request, and specifies how they want to receive the material.
The form comes in three identical copies: your file copy, a copy you return with your reply, and the requester's file copy. That structure is a hint about how seriously the IRS treats the paper trail around IDRs — every request and every response is logged, and gaps in that trail become evidence later if the case escalates.
Most examinations involve more than one IDR. The first one typically asks for basic books and records plus general information about your business. Later IDRs drill into specific issues the examiner has decided to pursue. Each response you send influences what the next request looks like, which is why the first IDR deserves more care than most taxpayers give it.
The IRS Can Ask for More Than You Expect
The IRS's authority to issue IDRs comes from Sections 7601(a) and 7602 of the Internal Revenue Code. The key language is broad on purpose: the IRS may examine any books, papers, records, or other data that "may be relevant or material" to its inquiry. Note the word "may." The examiner does not have to prove a document matters before asking for it.
That is why IDRs sometimes feel like fishing expeditions. Requests can reach into tax years outside the one under exam, or ask for records whose connection to the audit is not obvious to you. In most cases that is still within bounds. The Internal Revenue Manual generally requires IDRs to focus on the issues being examined, but the opening IDR of an exam — the one requesting your basic books and general business information — is not even required to state an issue.
If a request looks wildly out of scope, you are not powerless. A conversation with the examiner, and if necessary their group manager, can refocus or reprioritize items. Examiners would often rather narrow a request to what they actually need than drown in paper. But approach that conversation as a negotiation about scope and timing, not as a refusal — flat stonewalling is what triggers the enforcement machinery described below.
Read the First IDR as a Road Map
The initial IDR is the closest thing you will get to a preview of the examiner's thinking. The categories of documents requested, the years covered, and the level of detail all signal where the exam is heading. A request heavy on bank records and cash reconciliations points toward an unreported-income concern. One focused on travel logs and vehicle records points toward substantiation of deductions.
Use that preview. If the IDR suggests the examiner is interested in a particular issue, make sure your response on that issue is airtight, and start preparing your supporting position before the follow-up questions arrive. Tax professionals treat the first IDR as a chance to frame the narrative of the exam: a complete, well-organized response signals a cooperative taxpayer with sound records, and examiners calibrate their skepticism accordingly.
How to Build a Response That Helps Your Case
Responding to an IDR is not an administrative chore to delegate to whoever has a free afternoon. It is the first substantial interaction of the audit, it sets the tone for everything after it, and the materials you provide — or withhold — can determine the scope of the entire exam. Treat it that way.
Review everything before it leaves your hands. Every document you hand over will be read closely, and examiners are trained to spot the inconsistency you overlooked. A bank deposit that does not match your reported revenue, a contract date that contradicts your timeline, an invoice total that differs from your return — each one becomes a new question at best and a new issue at worst. Read your own production with adversarial eyes first, so you can prepare explanations instead of being surprised by them.
Keep an exact copy of everything you turn over. When the examiner follows up with questions — and they will — you want to be looking at the identical pages they are looking at, literally and figuratively. Number your pages, label each item to match the IDR line it answers, and keep a log of what was sent and when. If the case later moves to Appeals or to court, that log is your proof of cooperation.
Organize the production; do not dump boxes. Sending a disorganized pile of records invites the examiner to go digging, and digging expands audits. A clean response — a cover letter mapping each IDR item to the enclosed documents, tabbed sections, reconciliations that tie your records to the return — answers questions before they are asked. It also demonstrates that your books are reliable, which is itself a substantive point in your favor.
Meet the deadline, or ask for more time before it passes. The response date on the IDR matters. If a document exists but will take time to assemble, tell the examiner early and request an extension rather than going silent. Examiners routinely grant reasonable extensions when asked in advance; they treat unexplained silence as noncompliance, which starts the escalation clock.
Answer only what was asked. A common mistake is volunteering extra records to look cooperative. Do not. Provide complete responses to the items on the IDR and nothing beyond them. Every additional page is a new surface for questions, and unsolicited documents have expanded more audits than they have ever shortened.
What You Do Not Have to Do
Because an IDR is a request, IDRs are not self-enforcing. You are not under a legal obligation to turn over every item listed, and in some situations the right answer is a partial response or a reasoned decision not to produce a particular document. Three boundaries are worth knowing precisely.
You do not have to create documents that do not exist. If the IDR asks for a reconciliation spreadsheet or a summary schedule you never prepared, you are not required to build it — and the IRS cannot use even a summons to force you to create something from scratch. If the underlying records exist, the examiner can ask for those. Be clear about the distinction: "this document does not exist" is a complete and legitimate answer.
You may decline to produce a specific item — but you must be truthful about it. If you decide not to turn over a document, say so plainly. Never claim you cannot locate something you possess, never pretend a record does not exist when it does, and never alter, backdate, or fabricate anything after receiving an IDR. Misleading the IRS during an examination can turn a civil audit into something far worse than a tax bill. A forthright "we are not producing this item" preserves your credibility and your options; a lie destroys both.
You do not have to surrender privileged material without thinking. Some IDR items may be protected by the attorney-client privilege or by the Section 7525 privilege for communications with a federally authorized tax practitioner such as a CPA or enrolled agent. Handing a privileged document to the examiner will generally waive the privilege — not just for that page, but potentially for the whole subject matter. Before producing anything prepared by or shared with your lawyer or tax adviser, get advice on whether it is protected and whether producing it is wise.
Two warnings about the practitioner privilege in particular. First, it applies only in noncriminal tax matters before the IRS and in federal court — it evaporates entirely if the matter turns criminal. Second, it is narrower than most taxpayers assume: routine tax-return preparation materials and accountants' workpapers generally are not shielded from an IRS summons under long-standing Supreme Court precedent. When sensitive issues are in play, the standard protective structure is to have your attorney engage the accountant directly, so the accounting work is performed as an aid to legal advice rather than as standalone tax service. If your audit involves anything that could look like fraud — unreported income, altered records, a second set of books — talk to a tax attorney before you produce a single page to the examiner.
The Escalation Ladder: Delinquency Notice, Pre-Summons Letter, Summons
Choosing not to respond to an IDR does not end the examination. It starts a formal enforcement process that the IRS follows step by step, and each step raises the stakes.
For most examinations, the graduated process runs through three stages. First comes a delinquency notice giving you a new deadline to complete your response. If the response is still incomplete, the examiner issues a pre-summons letter — typically with a short fuse, often around ten days — warning that a summons is next. If that deadline passes without a complete response, the exam team coordinates with IRS counsel and issues an administrative summons.
A summons is no longer a request. It is a legal command authorized by Congress, and it can compel you — or a third party such as your bank — to produce documents or give testimony. If you do not comply voluntarily, the government can go to federal district court to enforce it, and defying an enforced summons can lead to contempt sanctions. Note the third-party point: refusing to hand over your own bank statements does not keep the IRS from getting them. It just means the IRS gets them from your bank, without your cover letter and without your context, while drawing its own conclusions about why you refused.
There is also a subtler cost to noncooperation that never appears in the manual. Examiners are human. A taxpayer who responds promptly and completely earns the benefit of the doubt on close calls; a taxpayer who stalls, dribbles out partial responses, or forces the examiner to chase every page signals that there is something worth hiding. That signal alone can widen the scope of the audit into areas that would otherwise never have been examined. Stonewalling an IDR rarely outsmarts the system — most of the time, it just tells the examiner where to look.
Common Mistakes That Make Audits Worse
Most IDR damage is self-inflicted, and the patterns repeat across examinations:
- Going silent on the deadline. A missed date with no explanation reads as defiance. A short call asking for two more weeks reads as diligence. The effort is identical; the consequences are not.
- Producing records you have not reviewed. If you have not reconciled the documents to your return, assume the examiner will find the mismatch before you do. Every unexplained discrepancy becomes a new IDR.
- Volunteering material beyond the request. Helpfulness is answering the question asked, completely and clearly. Sending three extra years of records "to be transparent" hands the examiner threads you did not need to provide.
- Producing privileged documents casually. Once privilege is waived by disclosure, it cannot be taken back. Route anything touching your lawyer or tax adviser through a privilege review first.
- Creating or altering records after the fact. Reconstructing a mileage log from calendar entries, honestly labeled as a reconstruction, is one thing. Backdating documents to make them look contemporaneous is another — and it is the fastest known way to convert a routine exam into a criminal referral.
Keep Your Records Audit-Ready From Day One
Every IDR horror story shares a root cause: records that were disorganized long before the auditor arrived. The taxpayer who can answer an IDR in days instead of months is the one whose books already reconcile — bank accounts tied to the return, receipts filed by category, major transactions documented when they happened rather than reconstructed under deadline pressure.
That is a bookkeeping discipline, not an audit tactic. Reconcile your accounts monthly so deposits always tie to reported revenue. Keep contracts, invoices, and substantiation attached to the transactions they support. Review your own financials periodically with fresh eyes — a dashboard view of your numbers, like the visual reports in Fava, surfaces the anomalies an examiner would ask about while there is still time to document them properly.
Simplify Your Financial Management
Responding to an IDR is dramatically easier when your financial records are complete, organized, and transparent from the start. Beancount.io offers plain-text accounting that gives you complete control over your financial data — version-controlled, auditable down to the individual transaction, and ready to produce the reconciliations an examiner asks for. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
