How to Inspect the Record Sequence in a FIRE File

Confirm which IRS publication and tax year define the file. Publication 1220 covers a particular set of information-return layouts; other legacy FIRE families use different publications. The IRS FIRE page lists those specifications.

Read an unchanged copy with a fixed-width-aware parser or text viewer. Preserve its bytes, spacing, and line-ending representation. Record the file length and any parser warning before attempting to interpret fields.

Do not assume that every physical line equals a tax return. Control records occupy space, and record boundaries must be interpreted using the actual specification. A pasted report or a delimited export may look like text while not being a Publication 1220 file at all.

Use Publication 1220, Part C for the exact layouts and ordering, including when K records apply. This table summarizes roles rather than replacing those layouts.

Fictional schematic example. The following display shows record roles and review notes only. It omits nearly all fields and is not a valid fixed-width file.

01 T  transmitter header
02 A  Payer A / 1099-NEC
03 B  payee return / compensation 1000.00
04 B  payee return / compensation 2500.00
05 C  Payer A control / 2 payees / 3500.00
06 A  Payer B / 1099-NEC
07 B  payee return / compensation 600.00
08 C  Payer B control / 1 payee / 600.00
09 F  end of transmission

The schematic contains nine records and three B-record returns. There are two issuer groups, with compensation totals of $3,500 and $600, for a combined $4,100. The example has no state-control records because it is illustrating only the basic federal group sequence.

A count of nine “returns” would confuse structural records with payee returns. A count of three alone would miss whether the returns stayed under the correct issuer. Review both the hierarchy and the control values.

For each A record, identify the B-record range it governs and the related C control. Look for an unexpected new group before the previous one closes, a B record without issuer context, or a missing final control caused by a truncated transfer.

Publication 1220 uses sequence numbers in positions 500-507 for these records. Compare the sequence field with the actual logical order when reviewing a file built to that specification. A display row number in your editor is a separate reference. Publication 1220, record sequence fields.

Inspect the first and last records of each group, not only a sample from the middle. Boundary mistakes can assign a valid payee record to the wrong payer. If record lengths or sequence values disagree, retain the original and ask the source-system owner to explain or re-export it.

Count B records in each issuer group and compare the relevant control count. Sum each populated payment amount separately and compare the corresponding control amount. Keep form context beside each code because the meaning of an amount code varies by form.

Where K records are present, identify the state and its relationship to the preceding issuer group. Do not interpret a recipient mailing address as proof of state filing selection. Use the specification and actual source reporting intent to review state-related controls.

Internal agreement is useful but limited. A file can balance and still omit an entire batch from the source system. Compare the inspected scope with the expected export report and any historical filing evidence before deciding the archive is complete.

Create an inspection note with the specification, file reference, group ranges, counts, control comparisons, and anomalies. Use stable internal payer labels rather than copying full recipient data into the report.

Classify anomalies: unexpected structure, missing source scope, inconsistent control, or unknown interpretation. Explain which evidence supports the finding and what a source-system owner needs to provide. Do not silently edit the archived submitted file to make a parser accept it.

If a new working reconstruction is needed, label it and retain the original. Then link the inspection to the historical transmission/status evidence separately. Understanding file structure helps investigate a past filing; it does not establish that the IRS received or accepted that exact file.