Validation Gap Analysis

INTERNAL USE ONLY — This document is competitive analysis for internal reference. It compares Flxpector validation behavior against an external validator. Do not publish or share externally.

Flxpector vs External Validator — Validation Gap Analysis

Overview

Flxpoint's EDI guides define specific validation rules, but external validators are sometimes stricter or different than what Flxpoint actually accepts. This document maps every known gap.

The key insight: Things that work in Flxpoint sometimes fail in stricter validators, and vice versa.


Version Standard

AspectFlxpointStedi
Supported version004010VICS only004010VICS (in guides)
5010NOT supportedWould need separate guide

FLX uses 4010 VICS, not 5010. Any files sent as 5010 may be rejected.


Cross-Transaction Gap Summary

Things That PASS in FLX but FAIL in Stedi Inspector

#TransactionIssueWhy It Fails in Stedi
1846QTY03 sent as simple EA elementStedi expects composite C001 structure
2856Missing TD512 service level codeStedi guide may mark it as required in certain configs
3810SAC with only G821 codeStedi validates against broader code list structure
4AllISA Control Numbers not uniqueStedi validates uniqueness; FLX does not require it
5AllLoose element length enforcementStedi strictly validates min/max lengths

Things That PASS in Stedi Inspector but FLX May NOT Process

#TransactionIssueWhy FLX May Reject/Ignore
1810SAC codes other than G821 (AFEE, C310, D240, G740, H750)FLX PDF only supports G821 for shipping charges
2846CTP pricing segment (UCP/WHL)Not in FLX PDF; may be ignored
3810CTP pricing at detail levelNot in FLX PDF; may be ignored
4810SAC at detail level (per-item charges)Not in FLX PDF; only summary-level SAC
5850Multiple PO1 product ID qualifier pairs (up to 6)FLX PDF shows single pair
6850N2 (additional name) segmentNot in FLX PDF
7856Extra ISA qualifier codes beyond ZZFLX typically uses ZZ

Per-Transaction Detailed Gaps

846 Inventory Advice

Segment/ElementFLX PDFStedi GuideGap Type
QTY03 structureSimple element EAComposite C001 with sub-componentsStructural — Stedi may reject simple format
CTP segmentNot presentOptional (UCP/WHL pricing)Stedi-only — FLX ignores
PID max useUnspecified200Limit difference
LIN conditional pairsLIN04-07 optionalSame but with strict conditional enforcementStedi stricter on pairing

850 Purchase Order

Segment/ElementFLX PDFStedi GuideGap Type
PO1 ID pairsSingle pair (PO106/PO107)Up to 6 pairs (PO108-PO117)Stedi more permissive
PO1-08 qualifiersNot in PDFBP, MG, VP, UP, ENStedi-only
N1-03/N1-04Not in PDFOptional ZZ qualifier + ID codeStedi-only
N2 segmentNot in PDFOptional additional name infoStedi-only
PER headingOnly seller phone (EA)EA + NT contact typesStedi broader
TD5 elementsTD505 + TD512 onlyFull TD5 specPDF simplified

856 Ship Notice

Segment/ElementFLX PDFStedi GuideGap Type
TD5 shipping providerRequired (SCAC)Required (SCAC)Match — but missing provider = FAIL in both
TD512 service levelM in PDFOptional in StediFLX stricter
REF/MAN exclusivityDocumented as mutually exclusiveEnforcedMatch
LIN02 qualifiersUP, EN, SK, BPSK, UPStedi has fewer options
BSN05 structure codes0001, 00040001, 0004Match

810 Invoice

Segment/ElementFLX PDFStedi GuideGap Type
REF*DPM (fixed "0000")Optional variantFLX stricter
SAC codesOnly G821 (Shipping)AFEE, C310, D240, G740, G821, H750FLX limited
SAC at detail levelNot supportedPresent in StediStedi-only
CTP at detail levelNot supportedPresent in StediStedi-only
IT1 extra ID pairsSingle pairMultiple pairs possibleStedi more permissive
IT104 formatReal number (15.95)Type R (match)Match
TDS formatImplied decimal N2Implied decimal N2Match
BIG01 date validationCurrent or within 17 monthsSameMatch

Critical Failure Points in Stedi Inspector

These are the most common reasons EDI files fail validation in Stedi but work in FLX:

1. Missing Shipping Provider (856 TD5)

If the SCAC code is missing, the 856 FAILS in Stedi.

  • TD502 must be 2 (SCAC qualifier)
  • TD503 must have a valid SCAC code (e.g., UPSN, FEDX)
  • FLX also requires this, so this is a legitimate failure

2. Strict Conditional Element Enforcement

Stedi strictly validates conditional rules:

  • If PER-03 present → PER-04 required (and vice versa)
  • If ISS-03 present → ISS-04 required
  • If CAD-07 present → CAD-08 required
  • ITD discount field dependencies

3. Control Number Mismatch

  • SE02 must match ST02
  • GE02 must match GS06
  • IEA02 must match ISA13 Both systems enforce this.

4. Element Length Violations

Stedi strictly enforces min/max character lengths:

  • ISA06/ISA08: exactly 15 chars (right-padded with spaces)
  • ISA13: exactly 9 digits (left-padded with zeros)
  • Various ID fields with specific length requirements

Recommendations for Suppliers

  1. Build to FLX PDF spec as the primary reference
  2. Validate against Stedi Inspector for structural correctness
  3. If Stedi rejects but FLX accepts: the file is technically non-compliant but functional
  4. If Stedi accepts but FLX ignores: extra segments (CTP, non-G821 SAC) won't cause errors but won't be processed
  5. Always include: SCAC code in TD5, service level code, matching PO numbers and item codes
  6. Use 004010VICS only — do not send 5010

Something unclear?

Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.