What the auditor is usually asking for in the first IDR
California, New York, and Texas use different labels for the opening request, but the substance is similar. California may begin with an audit engagement letter and document list, New York may lead with a records review request, and Texas may begin with a questionnaire followed by a formal records request. The record categories are still broadly the same. [1][2][3]
| Category | What the auditor wants | What the brand usually produces |
|---|---|---|
| Sales journals by period | Gross sales population by state and period | Platform or ERP exports showing gross sales, taxable sales, exempt sales, and tax collected |
| Transaction-level calculation logs | How tax was sourced, calculated, and applied line by line | Native tax-engine exports with transaction date, jurisdiction, taxable amount, rate, and tax computed |
| Filed returns and payment support | What was reported and what was paid | Filed returns, confirmation pages, EFT evidence, or CSP filing support where applicable |
| Exemption and resale certificates | Support for transactions claimed exempt | Certificate files organized by buyer, state, and effective period |
| Shipping and delivery records | Destination evidence for sourcing | Carrier records, 3PL exports, or order-level ship-to support |
| Marketplace settlement reports | What marketplaces collected and remitted | Amazon, Walmart, Faire, TikTok Shop, or other channel reports by state and period |
The opening IDR is broad because the auditor is building the base record set for everything that follows. Sampling choices, projection methods, and contested taxability positions often come later, after the auditor sees whether the opening production reconciles.
How to read the opening IDR for audit signals
The opening IDR is not only a checklist. It also signals where the auditor expects the biggest exposure.
If the request leads with exemption and resale certificates, the likely focus is exempt-sale reclassification. The auditor expects to test whether exempt transactions are supported by valid, producible certificates.
If the request leads with transaction-level calculation logs, the likely focus is sourcing or rate accuracy. This is common when the auditor expects local-rate errors, destination-sourcing issues, or jurisdiction mismatches.
If the request emphasizes marketplace settlement reports early, the likely focus is channel offsets. The auditor may be looking for gaps between marketplace-collected tax, credits taken on returns, and direct-channel activity.
The other signal is format specificity. If the auditor asks for a native export rather than a reformatted spreadsheet, that usually means they plan to test that record independently. If the date range stretches beyond the core audit period, that may signal a trailing-nexus or post-period consistency check.
What is negotiable at the IDR stage
The first IDR is still a negotiation point in practice. The brand usually has room to shape three things before fieldwork expands.
Sample period or phased production
The request may ask for the full audit period immediately, but the brand can often propose phased production. The most recent year may go first, with older periods following once the initial reconciliation is complete. That does not deny records. It sequences them.
Native exports versus reformatted extracts
Auditors generally prefer native exports because they want the source record, not the seller’s interpretation of it. For calculation logs in particular, native exports are usually the safer production choice. If context is needed, the better approach is to provide a supplemental reconciliation or cover memo rather than replacing the source file.
Extracts versus system access
Many sellers are asked whether they will provide extracts or limited read access. For most mid-market ecommerce brands, extracts are the safer choice. They create a clearer record of what was produced and reduce the chance that the auditor will pull unrelated periods or categories through open-ended access.
The reconciliation chain behind the production package
The auditor is usually trying to connect four links:
- Sales journals. The gross population by state and period.
- Calculation logs. What tax was computed, where, and at what rate.
- Filed returns. What was reported to the state.
- Payment support. What was actually remitted.
Every mismatch between two adjacent links becomes a question. A transaction in the sales journal that does not appear in the calculation log can look like uncollected tax. A calculated amount that does not appear on the filed return can look underreported. A return with no payment support can look unpaid.
That is why the best production package usually has three pieces:
- An index. A file-by-file inventory by state and period.
- Reconciliation notes. Short explanations for timing differences, refunds, marketplace offsets, or other known gaps.
- Source records. The underlying exports, returns, certificates, and payment support that close the chain.
The opening IDR is often less about raw volume than about whether the seller can make these links understandable on the first pass.
Production format, delivery, and timing
How the production is packaged changes how the auditor reads it. A structured production signals control. A scattered delivery invites more testing.
Three conventions help:
- Consistent file names. State, period, and document type in a sortable format.
- Predictable folder structure. State, then period, then record type.
- One delivery log. A written record of what was sent, when, and through which channel.
Response windows often run from 10 to 30 days depending on the state and the cycle. Extension requests are commonly granted on the first ask, but they generally need to be made before the deadline and documented in writing. [2][3]
What a production-ready operating model looks like
By the time the first IDR arrives, the brand is being graded on record discipline that was built before the notice date. The strongest audit responses usually share three traits.
The records were assembled before they were requested
The company already had a gap list by state, period, and document type, and it had been closing missing items before the audit started.
The reconciliation was tested before production
Sales journals, calculation logs, returns, and payments were already tied out internally, with short explanations prepared for known differences.
Someone owns each record set
Each major folder or state file has a custodian and backup, so retrieval does not turn into a search project under deadline.
TaxCloud is most relevant here as an implementation example, not as the point of the article. If a provider can help produce calculation logs, filing support, or certificate records in audit-ready form, that supports the operating model. The audit response itself still depends on the controller, tax lead, and counsel.