Build an ACA Reporting Evidence File

Create one index for each reporting year and legal employer. Give every item a stable evidence ID, a plain-language description, a controlled storage reference, a version or date, and a responsible owner. The index can refer to existing records without copying sensitive files into another uncontrolled location.

Describe the question each item answers. “Payroll-final-final.xlsx” does not explain whether a file contains historical employment, current addresses, or approved form data. “Employment history used for draft v4, January through December” is more useful.

Separate source evidence, decisions, prepared output, and completion evidence. A preparer's working export should not be mistaken for the original HR record, and a receipt should not be mistaken for the file that was submitted.

Each layer should point to the next with IDs. That allows a reviewer to follow one employee question without opening every file from the reporting season.

For each material exception, retain the original question, affected internal person or employer reference, relevant period, competing facts, and final decision. Record who made the decision and which source supported it. If a reviewer applied a reporting rule, link the applicable tax-year guidance or internal analysis.

Keep factual corrections distinct from judgment calls. A misspelled name resolved against an employment record is different from a question about which offer treatment applies. That distinction helps a future reviewer decide whom to contact and whether a wider population needs review.

Avoid approvals that exist only as chat reactions or unexplained initials. Capture an actual dated approval with its scope. Do not create signatures or imply that a person reviewed material they did not see.

Retain the approved data version, prepared form output, and references connecting them to the filing result. If a vendor supplies the output, ask how its batch ID maps to the employer's packet ID. Record revisions after approval and whether the affected review was refreshed.

The IRS AIR site is the official starting point for electronic-filing resources. Preserve the actual outcome supplied by your filing process with its date and identifiers. Do not relabel a vendor import event as an IRS acceptance or treat acceptance as proof that every underlying source fact was correct.

Track the employee-statement process in a separate evidence entry, including the approach used and the actual handling records available. A single generic “completed” field can hide a filing outcome that still requires action or an unanswered statement request.

Fictional Alder Ridge Labs receives an employee question about a September coverage entry. The coordinator opens the 2025 employer index and searches the internal employee reference. Evidence EX-017 records an administrator update received during preparation and links to source SRC-022.

The source shows the affected effective period. Decision DEC-009 explains the reviewer's resolution. Approval APR-004 identifies prepared output v4, and OUT-004 links that output to the recorded filing outcome. The coordinator now has a traceable packet to send to the authorized reviewer instead of guessing from today's enrollment screen.

The record does not automatically prove that the original entry was correct. It establishes what the employer used and who can assess the question. If the reviewer finds an error, the correction gets a new index entry connected to the original chain.

The 2025 instructions generally require keeping filed information-return copies, or the ability to reconstruct the data, for at least three years from the returns' due date. See Keeping copies. Have the responsible records owner assess other applicable obligations and any active hold before approving disposal; do not use this general rule as an automatic deletion date for every supporting record.

Restrict access according to the sensitivity of the underlying records. A project index can use internal references and controlled links while the detailed employee data stays in approved storage. Identify a backup owner who can retrieve the material if the original coordinator leaves.

At closeout, test one ordinary record and one exception. Ask a colleague to locate the source, decision, approval, and outcome using only the index. Missing links found in that exercise are easier to repair while the reporting team still remembers the work.