3. Processing Files
How to Upload EDI Files
Open Files → Upload in the dashboard. You can:
- Drag and drop one or more EDI files onto the drop zone.
- Click the drop zone to open a file browser.
- Use the
POST /api/v1/documents/outboundendpoint for programmatic sends.
Maximum file size: 10 MB per file. Maximum batch: 25 files at once.
Validation & Processing
After upload, SignalEDI runs a multi-step pipeline:
- Syntax check — verifies ISA/GS envelope structure, segment terminators, and element delimiters.
- Transaction set validation — checks mandatory segments, element formats, and code values against the X12 specification for the identified transaction set.
- Partner matching — matches the ISA06/ISA08 IDs to a configured trading partner in your account.
- Output routing — delivers the processed data per the output mode configured for that partner (EDI passthrough or JSON API).
- 997 acknowledgment — automatically generates a 997 FA back to the sender if configured.
Note: Validation errors produce a
FAILED transaction status. Click any failed transaction to see the specific segment and element that caused the rejection.AI-Assisted Remediation Examples
AI assistance is tied to specific EDI jobs, not a generic chatbot. The examples below show the kind of concrete help an SMB operator should expect while still keeping human approval on business-sensitive changes.
| Trigger | Suggested help | Human checkpoint |
|---|---|---|
| IK3/NM1 validation failure on an 837 | Explain the missing provider identifier, identify the loop, and suggest adding qualifier XX plus provider NPI. | Billing or compliance reviews corrected claim data before resubmission. |
| Retail partner requires 850, 856, and 810 testing | Draft the setup checklist: ISA IDs, sample 850 validation, ASN field mapping, invoice total checks, and AS2 readiness. | Operator confirms partner contacts, deadlines, and certification acceptance. |
| QuickBooks invoice mismatch | Flag duplicate lines, missing PO references, tax/freight mismatch candidates, or remittance reconciliation gaps. | Finance approves the final accounting writeback. |
Supported Formats
| Format | Extensions | Notes |
|---|---|---|
| ANSI X12 | .edi, .x12, .txt, .dat | Envelope versions auto-detected from ISA/GS (broad support across 4010 / 5010 / 6020 / 7030 / 8010 generations — contact support if you need certification for a specific version). |
| EDIFACT | .edi, .txt | Limited support — contact support for EDIFACT partners. |
| Flat File (CSV/TSV) | .csv, .tsv, .txt | Requires a custom map — contact support. |
Output Modes (EDI vs API)
Per trading partner, you choose how processed data is delivered:
| Mode | Description | Best for |
|---|---|---|
| EDI | Processed X12 EDI forwarded to SFTP/AS2 endpoint or available for download. | Partners that require raw EDI output, legacy system integration. |
| API / JSON | EDI converted to clean JSON and POSTed to your webhook URL or available via REST API. | Modern applications, ERP systems, QuickBooks integration. |
Still have questions?
Our support team typically responds within a few hours during business hours.
Contact support