# AGS 4.0.4 vs AGS 4.1 and 4.1.1: what changes for your data

> What moving from AGS 4.0.4 to AGS 4.1 or 4.1.1 means in practice: dictionary changes, client specifications, conversion pitfalls and how to record which version you checked against.

## Short answer

AGS 4.1 and its 4.1.1 revision keep the AGS 4 file structure but update the data dictionary: groups and headings are added, revised or deprecated. Files rarely fail on structure; they fail because a heading, code or rule differs from the version the client specifies. Always confirm the version in the contract and record it in TRAN.

## What stays the same

The AGS 4 file format — GROUP, HEADING, UNIT, TYPE and DATA rows, and the key-field relationships between groups — is common to 4.0.4, 4.1 and 4.1.1. Tools that read AGS 4 structurally can read all three.

## What changes

Each release revises the dictionary: new groups and headings, changes to existing definitions, and deprecated items. The authoritative list is the change log published by the AGS with each release; check it rather than relying on summaries, including this one.

## Common conversion pitfalls

- **Version mismatch** — TRAN states one version while the data uses headings from another.
- **Deprecated headings** — Older templates keep writing headings that the newer dictionary has changed or retired.
- **Client specifications** — Many clients add their own codes and required fields on top of the AGS dictionary. These differ between projects.
- **Silent loss** — Converting by mapping headings one-to-one can drop data that has no direct equivalent. Check row counts before and after.

## How G& handles versions

G& records the reference version each check ran against and keeps the original file alongside the converted record, so a reviewer can see exactly what changed. The client's validator remains the terminal check.

## FAQ

### Is AGS 4.1 backward compatible with 4.0.4?

The file structure is shared, but dictionary changes mean a file can conform to one version and not the other.

### Which version should I submit?

The version named in the client's specification or contract. Record it in TRAN.
