Skills / Tax

Filing diff

What it does

Compares two versions of a filing field by field — every field, in both directions — and reports what changed, what appeared, what vanished, and what stayed put when it should have moved.

Four situations need this, and all four are places where a change slips through unnoticed. An amended return, where the "as originally filed" column must agree to what was actually filed rather than to the software's current state of the file — the single most common defect in amended-return work. Changes made after review sign-off, which firms rarely have any way to detect. Carryforwards, where dropped items are the highest-frequency finding in return review and the check is a comparison nobody wants to do by eye. And a software conversion, where the same return in two systems should produce the same numbers.

Matching is on field identifier, never the printed description — descriptions change between software versions and manufacture phantom additions.

What it proves

Seven tests, and no clean diff unless:

  • Every field is accounted for — matched + added + removed must equal the union of fields across both versions. A field present in one version and silently absent from the comparison is the failure this test exists to prevent.
  • Both versions are identified — which is earlier and which later, with dates or labels. A diff with no direction cannot be read.
  • The net numeric effect reconciles — where a total's components are identified, the sum of changes to those components must equal the change in the total. A change that does not propagate is either an error or an override.
  • No change is reported without both values — a field with a new value and no old value is an addition, not a change, and the distinction matters.

Two tests find what an ordinary diff cannot: propagation (a total that did not move while its components did) and suspicious stability (a field that stayed put where a dependent field moved).

What you get

Eight tabs:

  1. Diff Summary — the seven tests, counts of changed, added, removed and unchanged, the net numeric effect, and the changes above materiality. The signable page.
  2. Non-Numeric Changes — identification, status, elections, checkboxes, names, addresses. Deliberately ahead of the numbers, because a changed identification number or election cannot be netted and often matters more than a five-figure movement.
  3. Numeric Changes — every changed field with form, line, old value, new value, delta, and whether it exceeds materiality. Sorted by absolute delta.
  4. Added and Removed — fields present in only one version. A removed field that carried a value is usually the more serious of the two.
  5. Propagation — totals against the sum of their components, with any break.
  6. Carryforward Continuity — prior year as filed against current year carried forward.
  7. Post-Review Changes — where a review timestamp was supplied.
  8. Unchanged Detail — so the field accounting can be re-performed.

Where it stops

It reports what moved; it does not conclude on whether a change was right.

A removed field that carried a value, a total that did not move while its components did, any change to an identification number or filing status or entity type, a carryforward that does not agree to the prior year as filed, any change made after review sign-off regardless of amount, a change to a field that feeds a carryforward into years that may already be filed, an amended return whose "as originally filed" column does not agree to the return as actually filed — each is escalated as a fact.

The largest dollar movement is usually the one everybody already knows about. The findings are the non-numeric changes and the propagation breaks.