Unfiled Return or Previously Submitted Return With Errors? Classify the Job First
· 6 min read
The answer for this situation
Establish what happened to the earlier package before describing the job as a straightforward late filing. An unfinished draft, a completed but unsent package and a package actually submitted with possible errors are different preparation situations. Gather the relevant versions and whatever supports the reported submission history, then write a short status statement identifying what is established and what remains uncertain. A missing copy in the owner's folder does not itself prove that no filing was made, while a file named submitted does not independently establish that event. The official rule about a substantially incomplete Form 5472 is important, but it should not be used to erase the actual history of a submission. Classifying the work first helps prevent a service order from being based on a convenient but unsupported assumption.[1] [2, p.3] [2, p.2]
Which facts change the answer?
The discussion concerns supported Form 5472/pro forma preparation and the distinction between an unfiled matter and a possible correction question. It does not specify an amendment route, prescribe replacement filings or determine how an earlier error must be addressed. Fields expressly not required should not be confused with a substantially incomplete applicable filing. Likewise, identifying an apparent error does not establish the complete scope of the problem or the government's treatment of it. The appropriate procedure for an already submitted package needs relevant official guidance and separate review before anyone represents a standard late-preparation job as sufficient.[1] [2, p.3] [2, p.2]
The official requirements, compared
| Question or field | Official instruction | Conditions and limits | Source |
|---|---|---|---|
| Substantially incomplete is failure | A substantially incomplete Form 5472 is treated as a failure to file. Information under Regulations section 1.6038A-2(b)(3) through (5) that is expressly not required does not, solely by its omission, make a filing substantially incomplete. | The Form 5472 filing obligation applies. Distinguish a substantially incomplete filing from fields that are not legally required. | [1] |
| Records sufficiency | Keep permanent books and records sufficient to establish the correctness of the federal return and the treatment of related-party transactions, together with the detailed requirements of Regulations section 1.6038A-3. | — | [2, p.3] |
| De proforma required | A foreign-owned U.S. DE subject to Form 5472 filing attaches Form 5472 to a pro forma Form 1120 and files by the Form 1120 due date, including a valid extension. | — | [2, p.2] |
| Separate related party form | Prepare a separate Form 5472 for each foreign or U.S. related party with which the reporting corporation had reportable transactions. Item 1g is the total number of Forms 5472 for that tax year. | — | [2, p.3] |
| Reportable transaction trigger | A reporting corporation generally files Form 5472 when it has a reportable transaction with a foreign or U.S. related party during the tax year. Operating revenue alone does not determine the filing requirement. | — | [2, p.2] |
| De tax year | A foreign-owned U.S. DE uses the tax year its owner uses for U.S. tax filing. If the owner does not have such a tax year, the DE uses a calendar year. | — | [2, p.2] |
Read the requirements in context
Failure penalty
Failure to file Form 5472 at the prescribed time and in the prescribed manner, or to maintain required records, can result in a $25,000 penalty. A substantially incomplete form is treated as a failure to file.[2, p.3]
Line1f value
Item 1f is the total U.S.-dollar value of foreign-related-party transactions on that Form 5472, including Part V for a foreign-owned U.S. DE. Do not complete 1f for transactions with a U.S. related party.[2, p.3]
A worked preparation example
This example is hypothetical; it shows how to organize the facts, not an agency decision.
Suppose a hypothetical owner requests late filing because the prior preparer is no longer available. The owner later finds a completed package, an email saying it was sent and a different draft containing another related party. The preparer creates a version register identifying each copy, the period it concerns and the support for any claimed submission. The related-party difference is described as a specific issue, not resolved by choosing the newest filename. The preparer compares the available facts with the relevant reporting questions, including the separate-party and transaction-scope requirements, without assuming that another initial package is automatically the correct answer. If the submission event cannot be confirmed from the available record, that remains an unresolved status. If a particular submitted version can be identified, the possible error is recorded against that version for an appropriate correction review. The hypothetical output is a job-classification record: unfinished preparation, possible unfiled package, submitted package with a defined question or submission status still unknown. It does not invent a Form 5472 amendment procedure, decide that the previous filing was substantially incomplete or guarantee how the IRS will process a later action.[1] [2, p.3] [2, p.2]
Turn the records into a usable filing plan
Before commissioning work, ask the proposed preparer what task is being accepted and what evidence supports that classification. Keep the identified earlier version available so a later reviewer can understand the possible discrepancy in context. Avoid changing a status from unknown to unfiled merely because a service checkout offers a late package. Equally, do not describe a prepared correction draft as filed or accepted without support for those events. SpeedEIN's supported late-return preparation is not a blanket offer to correct every previously submitted package or conduct a penalty dispute. Describe the actual history and the specific suspected error before ordering, so the scope can be assessed honestly. Where the correction procedure is not established by the available sources, the next step is to obtain appropriate guidance, rather than create a filing route from a familiar form name.[1] [2, p.3] [2, p.2]
Three checks before you proceed
- Which exact version was prepared, and what supports any statement that it was actually submitted?
- Is the issue unfinished initial preparation, a possible correction to a known submission or a history that remains unresolved?
- Has the proposed service task been scoped without inventing an amendment route or treating every blank field as a required omission?
Related preparation guides
- Clear the Return Backlog and Keep Penalty Relief as a Separate Workstream
- Missing Statements in a Late-Filing Year: Build an Evidence-Gap Register Instead of Filling Zeros
- Substantially Incomplete Form 5472: Why Submission Alone Does Not Resolve the Risk
Official sources and document versions
Official source versions checked: 2026-11-10
- 26 CFR 1.6038A-4 Monetary penalty for failure to furnish information or maintain records — 2026-11-05
- Instructions for Form 5472 (Rev. December 2024) — Rev. December 2024
Get help with the relevant SpeedEIN service
SpeedEIN provides preparation and support within the scope described on its service pages. Review the supported entity types, required information and current service scope before ordering. IRS decisions, processing and any applicable filing or payment obligations remain governed by the official rules.