Converting a FIRE File with Multiple Payers

List the issuer identifier, legal name, payment year, form type, and filing category for each source group. In Publication 1220, the A record establishes issuer context, the following B records hold payee return data, and C records provide related totals. Use the applicable layout to identify complete groups, including any state control information. Publication 1220, Part C.

The same payer can appear more than once because it reports different forms or categories. Count distinct legal issuers separately from source groups. A file with three A-record groups does not necessarily contain three unrelated businesses.

For the worksheet, create stable labels such as Issuer-A / NEC / original. Keep full identifiers in the controlled filing system and use masked labels in general review notes. Avoid matching payers by display name alone: a trading name may look similar to the name of a related company.

After conversion, choose a return from the beginning and end of each group. Confirm its payer, recipient, form, year, and amount fields. Boundary records are useful because an incorrectly carried-forward issuer context can affect everything after a transition.

If the output combines, splits, or reorders groups, make a crosswalk from source group to output group or file. You do not need identical presentation to have equivalent data, but you do need a reproducible explanation for where each return went.

Do not merge entities solely because they share an address, owner, or payroll team. Likewise, do not split one reporting entity based only on an internal department label. Use the underlying reporting identity and the receiving workflow's supported grouping rules.

A recipient who appears under two different payers is not automatically a duplicate. Review the reporting relationship before deleting anything. Deduplication should use the intended return identity and source business records, not just a repeated name.

For each group, compare recipient return count and each populated box amount. Keep withholding separate from compensation, rents, interest, or other reported amounts. Where relevant, compare state data in additional rows rather than treating it as interchangeable with federal information.

A whole-file count and a whole-file sum are useful closing checks, but they cannot reveal an amount moved from one payer to another. The same is true when one form group gains a return and another loses one.

Use all four levels for a mixed export. Record both the comparison result and the basis for it so the next reviewer can reproduce the check.

Fictional example. A service team prepares NEC returns for Cedar Example LLC and Birch Example Inc. The source contains 3 Cedar returns totaling $18,000 and 2 Birch returns totaling $7,000. The output also has 5 returns totaling $25,000. Those overall checks pass.

The first Birch return was attached to Cedar in the hypothetical output. Reviewing the source-to-output boundary identifies the error. The team fixes the grouping cause, regenerates the file, and repeats the checks for all transitions. It does not simply adjust group totals to make the report balance.

This is a deliberately constructed example of a reconciliation risk, not a report of an observed defect in the site's converter.

If the chosen workflow needs separate input files, assign a unique output label to each split and list the source groups it contains. Record expected count and box totals before exporting the split. Then add the split results back together and compare them with the frozen source.

Avoid cutting text at an arbitrary line count. A valid split may need reconstructed transmitter, issuer, and control records under the source specification, or a new receiving-format document. Have the converter or source system generate supported splits rather than hand-editing control structures.

Keep retries visible in the crosswalk. A second generated file can be a replacement working artifact without representing additional returns to transmit. Before the filing handoff, identify exactly which output version is current and which earlier files have been superseded.

Give the submitter the final source-to-output crosswalk, reconciled totals, and unresolved-exception list. State whether any groups are excluded and how those returns will be handled. The submitter should be able to account for every intended group without reconstructing the review from filenames.

Access also has to match the work. IRS Publication 5718 distinguishes an issuer submitting its own returns from a transmitter submitting for others. Do not assume that possession of a TCC authorizes the multi-business filing arrangement. Publication 5718, participation and third-party arrangements.

After filing, reconcile the resulting acknowledgments back to this crosswalk. A group that converted successfully can still need follow-up later. Keep data conversion status and IRS filing outcome in separate columns so a partial result is not mistaken for completion of every payer.