An IRS Electronic Books Request Needs a Preserved, Readable Production Copy

Treat the request as a records-production project

An IRS request for accounting software data can be more consequential than exporting a profit-and-loss statement. The file may contain transaction detail, attachments, customer records, user history, and entries outside the owner’s initial understanding of the audit. Assign one person to coordinate the response with the examination representative and the accounting-system administrator. Record the request, response date, covered entity, periods, format, and any agreed clarification before creating a production copy.

The IRS electronic-records FAQ explains that examiners can request backup files through an Information Document Request and may need administrator access to read the submitted file. It recommends discussing compatibility before submission. This is a request for usable examination records, not a reason to email the company’s ordinary shared login. Plan access for the production file with the examiner and software specialist, using a controlled copy and an approved transmission method.

Preserve the source and explain period boundaries

Freeze a reference copy of the relevant accounting data before assembling the response. Record when the copy was created and which database or company file it represents. Keep routine bookkeeping corrections documented through the normal process; do not silently rewrite historical entries to make the audit file look cleaner. If a reconciliation entry is discovered after preservation, retain its supporting explanation and make the difference between versions visible.

The IRS FAQ says certain transactions outside the examined year can be relevant, including transactions around year-end used to test accrual cutoffs. Therefore, an owner should not assume every later transaction can be removed automatically. Discuss scope concerns with the examiner through the representative before changing the data supplied. Sensitive or potentially privileged material calls for a specific legal review, not an undocumented deletion by the bookkeeper.

Imagine a hypothetical accrual service company with a December invoice for eighty thousand dollars and a January customer payment. The bank deposit alone does not establish the correct income year. A readable accounting file can show the invoice date, receivable entry, collection, and any later credit memo. If the export contains only January bank activity, the examiner may be unable to connect those events. Identify that limitation before treating the export as a complete response.

Test the exact copy that will be delivered

Create a production checklist around the examiner’s agreed format. Include the software name and version, company identifier, file creation date, restoration instructions, and the contact responsible for compatibility questions. Open or restore the exact production copy in a separate test environment where feasible. Confirm that the relevant accounts and reports are readable and that attachments promised in the response are actually included. A file that exists in a folder has not yet passed a usability test.

Keep live-system credentials distinct from access to the submitted backup. The IRS FAQ describes changing an administrator password for a backup and restoring the working-file password afterward. Modern hosted products may use a different mechanism, so confirm the applicable workflow rather than applying a desktop procedure to a cloud service. Use a unique credential with the necessary agreed access and communicate it through a separate approved channel. Document who can access the live business system after production.

Prepare a short reconciliation from the produced books to the filed return. For example, assume book profit is three hundred thousand dollars and the return reports three hundred thirty thousand dollars before owner-level items. The thirty-thousand-dollar difference needs its actual tax adjustments listed, not an unexplained claim that the books are close enough. Label these figures hypothetical. Supply the real depreciation, meals, timing, or other schedules relevant to the company’s reconciliation rather than copying a generic bridge.

Keep a delivery and follow-up record

Preserve the submitted file, cover response, requested-period description, attachment list, and transmission confirmation together. A delivery log should identify the Information Document Request answered and any items still outstanding. If the file failed to upload or could not be opened, record that event and agree on the replacement procedure promptly. Do not mark the request complete merely because an employee clicked send.

Assign each follow-up question to someone who understands the underlying transaction. An accountant can explain an adjusting entry, while an operations manager may need to explain when a service was performed. Keep those explanations tied to preserved invoices, contracts, and payment evidence. Finally, close temporary access when appropriate under the agreed process and retain the production history with the examination file. This gives the owner an auditable account of what was supplied without disrupting the company’s working accounting records.