Documentation

What Should an Audit-Ready 179D File Contain?

A well-organized file lets a reviewer trace a tax number back to the building, the installed work, and the governing evidence.

Last reviewed: September 17, 2026

Section 179D | Audit Documentation | Recordkeeping

“Audit-ready” is an organizational objective, not an IRS promise. Books and records must be sufficient to establish entitlement and amount, including signed certification and allocation where relevant. A polished folder structure cannot cure unsupported facts.

Build the file around claims: who owns the building, when the property began construction and entered service, what systems were installed, how savings and area were established, how the amount was limited, and who signed each required document.

Identity and dates

Establish the project and applicable regime

Retain the legal owner, claimant, address, parcel or project identifiers, contracts, and evidence supporting construction start and placed-in-service dates. Keep tax-return dates separate.

Current law excludes property whose construction begins after June 30, 2026. Preserve property-level evidence and do not assume another incentive’s safe harbor applies.

Claim-to-evidence map

Signed required evidence and helpful support serve different purposes.

Review pointEvidence or measureWhy it matters
Certified savingsSigned certificationModel files, software version, and outputs support the conclusion.
Installed conditionsField evidenceObservations, submittals, photos, and change records support reconciliation.
Designer amountSigned allocationAuthorship records and a building-wide ledger support responsibility and amount.
Increased pathLabor evidencePayroll, apprentice, exception, and correction records as applicable.
Editorial organization aid—not an audit safe harbor.

Engineering file

Preserve inputs, model version, inspection, and signed certification

Keep drawings, specifications, schedules, submittals, change records, qualified-software name and version, input and output files, field observations, certifier qualifications, and signed certification.

The ordinary-route inspection follows placement in service. Modeler, designer, and certifier are distinct roles even when their work is coordinated.

Calculation file

Tie area, rates, costs, and prior claims to source records

Support area measurement, applicable tax-year rate, certified savings, eligible property cost, and every limitation. Maintain a building-wide history of prior Section 179D deductions.

A rate multiplied by area is preliminary. The preparer should reconcile cost and the statute’s prior-deduction rules with the claimant and form.

Trace a reported rate backward

Every material number should reach a source.

Return amount

Filed position

Rate + area

Calculation

Certified savings

Signed result

Model + field

Technical source

The same trace should work forward from source to return.

Designer-only records

Connect technical authorship to a reconciled allocation

Retain contracts, issued drawings, specifications, control narratives, responsibility records, and a signed owner allocation. The allocation should contain the information and declarations required under the applicable guidance.

If several designers are involved, maintain one building-wide ledger so signed amounts do not exceed the owner-authorized total.

Increased path

Protect payroll and apprenticeship records

Where the increased path is used, retain installation-start evidence, wage determinations, classifications, payroll and fringe records, contractor and subcontractor data, apprentice hours, ratios, participation, good-faith requests, and correction support as applicable.

These records can contain sensitive identifiers. Restrict access, use redacted indexes for general review, and never display them in public examples.

Return and retention

Preserve the filed position and assign custody

Keep Form 7205, applicable Form 7220, filed return version, calculation workpapers, basis reconciliation, preparer decisions, correspondence, and any later corrections together with the technical file.

There is no one universal retention period stated here. Coordinate duration with tax and legal advisers, identify a custodian, control versions, and ensure records remain accessible after personnel or systems change.

Illustrative gap register

Status labels direct follow-up; they do not predict audit success.

Review pointEvidence or measureWhy it matters
Drawings and modelPresentVersion and custodian recorded.
Signed allocationPresentReconcile against total building amount.
Inspection evidenceMissingInvestigate before treating certification as supported.
Prior-claim scheduleNeeds reviewReconcile building-wide history with preparer.
Hypothetical school file; no client facts or taxpayer identifiers.

Prepare the review

Assign a source, custodian, version, and unresolved issue

  • Legal owner and claimant identity
  • Construction-start and service evidence
  • Applicable regime and reference standard
  • Model inputs, outputs, and software version
  • Inspection and signed certification
  • Area and eligible-cost support
  • Prior-deduction reconciliation
  • Designer responsibility and allocation
  • PWA or exception evidence
  • Forms, return, basis tie-out, and retention owner

Common questions

Practical answers before the review

Does an organized file guarantee an audit outcome?

No. Organization supports review but does not establish entitlement, amount, or IRS acceptance.

Which records differ for designers and owners?

Designers additionally need technical-responsibility evidence and a valid, reconciled owner allocation; claimant-specific tax records also differ.

How long should records be retained?

There is no universal period stated here. Coordinate the project’s retention schedule with tax and legal advisers.

Project review

Bring the project record into one coordinated review.

NABiTax can help organize ownership, design responsibility, allocation, technical analysis, and filing support without assuming an outcome.