Several Forms 5472 in One Packet: Reconcile the Counts and Combined Totals
· 6 min read
The answer for this situation
A packet containing several Forms 5472 needs a control sheet of its own. Even when each party's draft looks complete in isolation, the packet can contain inconsistent counts, a missing form or a combined total that cannot be traced back to the individual forms. Create a master list with one entry for each proposed related-party form, its party identity, relevant tax year and the applicable transaction-value fields. The purpose is to make the packet internally explainable before it is finalized. This is different from simply repeating the rule that each relevant party has a separate form: the practical task is to connect that rule to the numbers actually appearing across the packet, while keeping a document count distinct from a transaction total.[1, p.1] [2, p.3]
Which facts change the answer?
Item 1g is the total number of Forms 5472 filed for the tax year. Item 1h totals the item 1f amounts on those forms. Item 1f concerns foreign-related-party transaction value on the particular form, including Part V for a foreign-owned U.S. DE; it is not completed for transactions with a U.S. related party. Those scopes matter when the packet includes different party types. Part III is completed even where the relevant party already appears in Part II. Keep the form inventory, identity review and amount reconciliation separate so a successful count check is not mistaken for proof that every amount has been classified correctly.[1, p.1] [2, p.3]
The official requirements, compared
| Question or field | Official instruction | Conditions and limits | Source |
|---|---|---|---|
| Official field 5472 1g: Total number of Forms 5472 filed for the tax year | Enter the total Forms 5472 filed for the tax year, with a separate form for each related party involved in a reportable transaction. | — | [1, p.1] [2, p.3] |
| Official field 5472 1h: Total value of gross payments made or received reported on all Forms 5472. | Total the item 1f amounts on all Forms 5472 for the tax year. | — | [1, p.1] [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] |
| 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] |
| Related party repeat part3 | Every filer completes Part III, even when that related party was already identified in Part II as a 25% foreign shareholder. | — | [2, p.5] |
| 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] |
Read the requirements in context
Official field 5472 1f: Total value of gross payments made or received reported on this Form 5472.
Total the foreign-related-party transactions reported on this form, including Part V for the DE. Do not substitute operating revenue for the transaction total.[1, p.1] [2, p.3]
English usd
Provide Form 5472 information in English and report amounts in U.S. dollars.[1, p.1]
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]
Part5 other de transactions
A foreign-owned U.S. DE checks Part V and attaches a description for other specified transactions not reported in Part IV, including receipts and payments connected with formation, dissolution, acquisition, disposition, contributions and distributions.[2, p.6]
When this applies: Foreign-owned U.S. disregarded entity. The relevant transactions have not been reported in Part IV.
A worked preparation example
This example is hypothetical; it shows how to organize the facts, not an agency decision.
Suppose a hypothetical packet has several party-specific drafts. The preparer gives each draft a stable reference and connects it to the supporting counterparty file rather than identifying it only by page position. The master sheet records which forms belong to the same reporting entity and tax year. Next, it compares the proposed item 1g entries with the actual form inventory. A different section traces item 1h back to the applicable item 1f figures, keeping the U.S.-related-party limitation visible instead of forcing every form to have the same kind of amount entry. If a DE Part V transaction is included, its supporting description is linked to the relevant form rather than appended to the packet with no clear association. A duplicate draft is marked as such so that an extra saved copy does not inflate the form count. The preparer also checks that a revised party name remains connected to the correct supporting file. This exercise does not decide a missing party's status from a count difference or turn an inapplicable field into an invented zero. It produces a master list and a reproducible reconciliation that another reviewer can follow without reconstructing the packet from loose pages.[1, p.1] [2, p.3]
Turn the records into a usable filing plan
Finalize the control sheet only after the underlying party and transaction questions have been addressed. English descriptions, U.S.-dollar values and the records supporting those values should remain connected at both the individual-form and packet levels. If a form is added or removed during review, revisit the count and the combined-total chain instead of updating one number in isolation. A remaining mismatch should generate a specific issue: duplicate draft, missing party evidence, changed form amount or unresolved field applicability. It should not be hidden by adjusting a total to make the packet look consistent. More than one related-party form can also introduce service-scope questions; describe the actual facts when asking whether preparation support is available. SpeedEIN's standard annual-package scope does not imply corporate-return, transfer-pricing, withholding or personal-tax work. The deliverable here is a checked packet inventory and traceable totals, not a guarantee that numerical agreement settles every legal reporting question.[1, p.1] [2, p.3]
Three checks before you proceed
- Does the master list identify every actual party-specific form and distinguish drafts from additional forms?
- Can the item 1g count and item 1h sum be traced to the correct inventory and applicable item 1f amounts?
- Are Part III identity, DE Part V links and U.S.-related-party field limits still clear after packet revisions?
Related preparation guides
- Payment-Processor Statements and Form 5472: Separate Sales Receipts From Owner Transfers
- Personal and LLC Transactions Share a Statement: Build a Reviewable Separation Ledger
- One Reporting Corporation, More Than One Related Party: Organize Separate Forms
Official sources and document versions
Official source versions checked: 2026-11-10
- Form 5472 (Rev. December 2023) — Rev. December 2023
- 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.