The filing deadline can pass and still leave a tax office with risky Form 8867 cleanup. The return may already be out the door, but the due diligence file can still be scattered across notes, inboxes, and shared drives. The IRS keeps the rule simple: paid preparers claiming EITC, CTC, ACTC, ODC, AOTC, or head of household filing status must meet due diligence requirements and keep records that support what they did (IRS Form 8867 landing page: https://www.irs.gov/forms-pubs/about-form-8867; IRS due diligence law page: https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). For a small office, that makes Form 8867 cleanup an archive-control problem.
Late June is the right moment to reset the file stack. If the office waits until August, a missing worksheet or an undocumented client answer can turn into another callback.
What a complete Form 8867 file should hold before anyone calls it closed
The IRS due diligence law page describes four requirements: complete and submit Form 8867, compute the credits, satisfy the knowledge requirement, and keep records for three years (https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). The recordkeeping piece is where small offices can lose control because the evidence lives in too many places. The IRS says the office should be able to produce:
1. The completed Form 8867.
2. The completed worksheets used to determine each credit amount.
3. A record of how, when, and from whom the information was received.
4. Any documents the client showed the preparer and the preparer relied on.
5. Any additional information the preparer relied on.
Keeping these five records is required; keeping them does not, by itself, prove the due diligence was performed on time. That is the archive standard. The due diligence law page says that when information appears incorrect, inconsistent, or incomplete, the preparer must make additional reasonable inquiries, keep a record of those questions and answers, and be able to show how each requirement was met, not merely that a form was filed (same source: https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). A file can look finished in the tax software while the due diligence support is split across a CRM note, a scanned record, a text screenshot, and a worksheet on somebody's desktop. That is not one file.
Where offices create penalty exposure after the return is already filed
The IRS page on consequences says a paid preparer can be assessed a penalty for each failure to meet due diligence requirements and that, for returns filed in 2026, the indexed amount is $650 per failure (https://www.irs.gov/tax-professionals/eitc-central/consequences-of-filing-eitc-returns-incorrectly). The same page says the penalty can stack and gives a 2026 example of up to $2,600 per return or claim when multiple failures apply. It also says the employer can face consequences for an employee's failure. That does not mean every archive gap automatically becomes a penalty. It means the office should stop treating archive gaps as harmless cleanup.
Exposure points can be operational: the worksheet exists but nobody can show which version was final; the office asked follow-up questions but the answers were never written into a retained note; the file contains client documents but not the record of how the office used them; or the return moved through two team members and neither note makes clear who resolved the inconsistency. The IRS due diligence requirements make this a recurring discipline, not a one-time formality (https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). The point is to close the quiet gaps before extension volume turns them into expensive confusion.
The four-bucket archive reset that keeps the cleanup honest
Do not start the reset by telling staff to "review the Form 8867 files." That instruction is too fuzzy, and fuzzy instructions create fake completion. Use four buckets instead:
1. Ready. The file has the completed Form 8867 and the supporting worksheets, along with the inquiry record and relied-on client documents where applicable, in one secure place (a recommended consolidation, not an IRS requirement).
2. Missing worksheet. The office cannot show the computation support that backs the claimed credit.
3. Missing inquiry note. Someone asked the extra questions, but the file does not preserve the question, the answer, the date, and who handled it.
4. Missing client document. The file depends on a document the preparer relied on, but the document is not stored with the rest of the record.
That bucket system turns a vague backlog into named next actions: missing worksheets go to workpaper recovery, missing inquiry notes go to documented reconstruction, and missing client documents go to a follow-up request with an owner and due date. Closing a bucket this way restores the archive's completeness; it does not create contemporaneous evidence of the inquiry. Each recovered record should be dated to when it was actually created. Suppose the office pulls 30 returns with Form 8867 exposure and finds 14 ready, 6 missing worksheets, 5 missing inquiry notes, and 5 missing client documents. That is three work streams with different owners and risks, not one generic cleanup list. The office needs a place to track those follow-ups without pretending it solved the tax issue itself: https://www.intaxion.com/tools/form-8867-checklist.
How to review the file without turning the sprint into fake certainty
There is an easy anti-pattern here: offices use the archive reset to re-argue every credit decision from scratch. This sprint is about record completeness, not about improvising new legal or tax advice after filing season. The better review question is: does the file show what the preparer relied on and how the office handled inconsistencies? The due diligence law page says a preparer must not ignore information that appears incorrect, inconsistent, or incomplete, and must keep a record of the additional reasonable inquiries and the client's answers (https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). So the archive review is not "Was the client definitely eligible?" It is "Can this file show the office acted reasonably at the time?" If the file shows the source documents, the worksheet support, and the inquiry trail, the office can close the archive gap. If one of those elements is missing, the office names the gap and assigns follow-up.
A two-hour same-day reset before extension work gets louder
Use one two-hour reset with this sequence:
- Pull the Form 8867 return list and sort each file into the four buckets.
- Verify worksheet support before touching client follow-up.
- Identify inquiry-note gaps while memory is still usable.
- Request missing client documents with a clear owner and date.
- Archive the recovered records in one secure location and log what is still open.
The last point matters as much as the first. The IRS says these records should be kept secure in paper or electronic format for three years (https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements). If the office recovers the missing documents and still leaves them spread across inboxes, the recommended consolidation goal was not achieved.
Intaxion is not the one making the credit determination. It is the workflow layer that helps an office centralize file status, follow-up ownership, and proof trail. If the office needs a place to run the reset, send readers to https://www.intaxion.com/tools/form-8867-checklist.
Source packet
1. Form 8867: https://www.irs.gov/forms-pubs/about-form-8867
2. Instructions: https://www.irs.gov/instructions/i8867
3. Publication 4687 (unverified): https://www.irs.gov/pub/irs-pdf/p4687.pdf
4. Due diligence law: https://www.irs.gov/tax-professionals/eitc-central/due-diligence-law-regulations-and-requirements
5. Consequences: https://www.irs.gov/tax-professionals/eitc-central/consequences-of-filing-eitc-returns-incorrectly
Claim boundaries
- This article is operations guidance for archive control and follow-up visibility, not tax or legal advice.
- Preparers still need to read the official Form 8867 instructions and apply judgment to real facts.
- Intaxion is positioned here as a workflow, documentation, and follow-up layer. It is not tax-preparation software and it does not determine eligibility for a credit or filing status.
- Reconstructing a missing note or document after the fact does not create a valid retroactive cure. Recovered records must be dated to when they were actually created, not backdated to suggest due diligence happened earlier than it did.
Get our free Tax Preparer Compliance Checklist
A practical checklist to ensure you're meeting all IRS due diligence requirements. Download instantly.
We respect your privacy. Unsubscribe at any time.