EDI Validation
Validate canonical payloads before submission. The public schemas define required fields, enums, date-time values, monetary fields, line correlation, and extension field expectations.
Required fields
Schemas define the minimum fields DataShift needs to process each canonical document.
- Validate before sending.
- Do not omit envelope fields.
- Check nested line item requirements.
Date and time
Date-time fields should be UTC ISO 8601 strings unless a schema states otherwise.
- Include timezone information.
- Avoid local timestamps without offsets.
- Preserve source event dates separately from processing timestamps.
Currency and tax
Monetary fields should include explicit currency context and separate tax values where available.
- Use ISO 4217 currency codes.
- Keep line and summary totals explicit.
- Do not infer tax from gross values only.
Line correlation
Use uniqueLineKey to correlate PO, POA, ASN, and INV lines.
- Do not use array index.
- Preserve keys downstream.
- Raise manual review when line correlation is ambiguous.
Extension fields
Use extrinsics for partner-specific values that do not belong in the canonical core.
- Keep names stable.
- Avoid credentials or private URLs.
- Do not rely on extrinsics for required canonical behavior.