Documenting Field Mappings for an Integration
A field-mapping document translates business meaning between systems. Column names alone are not enough when units, formats or interpretations differ.

Record meaning and transformation
For each field, describe the source, destination, format and permitted conversion. Include examples for dates, quantities and identifiers. Specify the treatment of empty values and whether a value is required for the destination to accept the record.
Practical checklist
- Explain each field's meaning.
- Record units and formats.
- Define missing-value behaviour.
- Include realistic examples.
How to review the result
Have someone from each system review the same sample. Resolve differences in interpretation before writing a transformation that makes the wrong assumption consistently.