FIRE to IRIS Field Mapping: Trace a Sample Record

An amount field is not self-describing. Locate the issuer A record that governs the payee B record, identify the form type, and read the declared amount codes. For Form 1099-NEC, Publication 1220 associates amount code 1 with nonemployee compensation and code 4 with federal withholding. For another form, the meaning of a code can differ. Publication 1220, Part C, issuer and payee layouts.

In your trace sheet, label the source file, payer group, B-record sequence, payment year, and account reference. Use a synthetic or masked recipient label in material shared outside the filing work area. Do not start by searching the XML for a common name: that name may occur under several payers.

Keep the form label beside every amount comparison. The number $1,250.50 is insufficient by itself; the review needs to establish which payer reported it, for which recipient, in which tax year, and in which box.

The example below uses only two slices of a fictional B record. It deliberately omits the other positions, so it is not a complete record suitable for conversion or filing. Position numbers are one-based and inclusive.

Fictional source context: 1099-NEC, tax year 2025
B record positions 55-66:  000000125050
B record positions 91-102: 000000015000

These twelve-character fields encode $1,250.50 and $150.00 respectively. In this FIRE layout, the two rightmost amount positions represent cents. Read the characters first, then normalize the amount once. A second division by 100 would turn $1,250.50 into $12.505, which is a conversion defect. Publication 1220, payment amount fields.

If the captured range is the wrong length or contains an unexpected character, resolve that before comparing XML. Many apparent amount problems actually begin with an off-by-one position or a text editor that changed spacing.

Use a three-column trace so the reviewer can see whether the error arose during parsing or writing. The XML element names below match the site's inspected converter mapping for NEC, but the fragments omit their enclosing groups and namespace. They illustrate a field trace and are not a standalone IRIS document.

Store exact cents or another exact decimal representation in the review calculation. Preserve identifiers and account references as text. The rule used for an amount must not accidentally strip leading zeros from a taxpayer identifier or account number.

Reconcile each field to the appropriate source amount, not to a combined sum. Compensation and withholding are separate reported values. Subtracting the second from the first does not produce a substitute value for either box.

Inspect the issuer name and identifier at the group level, then the recipient name, identifier type, identifier, and address at the return level. A technically valid amount under the wrong issuer is still the wrong result.

Name handling deserves a separate check. A fixed-width source may have business-name lines without reliable first-name and last-name boundaries. Do not assume that splitting on the first space creates an accurate person name. Inspect warnings, compare the source's intended identity, and determine what the receiving workflow supports.

Also review empty and zero values. An absent optional output element, an explicit zero, and a missing required source value are different cases. Record which transformation was intentional. If a field cannot be represented by the selected converter, obtain a supported path instead of accepting silent loss.

Fictional example. A reviewer expects compensation of $1,250.50 and withholding of $150.00. The preview contains both amounts, but they are reversed. The total of the two fields remains $1,400.50 before and after conversion, so an all-box total would miss the defect.

The reviewer checks the raw slices and confirms that they were parsed correctly. The next trace step shows that the output writer assigned code 1 to the withholding element. The correction belongs in the mapping, not in the accounting data. After the software owner fixes it, the reviewer checks both fields and similar NEC records in the same batch.

Run a small boundary set as well: a cents-bearing amount, a large amount within the supported range, and a zero or omitted optional amount where appropriate. Use deliberately synthetic identities for test material. This example describes a review method; it does not assert that the current converter contains that defect.

Save the source specification edition, converter release, target schema version, and the exact field trace. State whether you inspected a fragment, a complete converted file, or a submitted return. This lets another reviewer repeat the comparison after an export-system or schema change.

For A2A, element placement, order, types, and required groups depend on the applicable schema. The IRS release table distinguishes testing and production dates. A familiar element name alone does not prove that the complete document is valid for the receiving environment.

Use the downloadable worksheet to capture one representative ordinary record and each unusual case in the source. Finish by reconciling the full batch by payer and form. Spot checks find mapping patterns; they do not replace batch totals or the later review of the IRS filing outcome.