Skip to main content

SignalEDI documentation

API-first EDI docs for onboarding, X12 basics, trading partner setup, billing, REST endpoints, and webhooks — with JSON/CSV intake, instant validation, and real-time visibility.

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/outbound endpoint 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:

  1. Syntax check — verifies ISA/GS envelope structure, segment terminators, and element delimiters.
  2. Transaction set validation — checks mandatory segments, element formats, and code values against the X12 specification for the identified transaction set.
  3. Partner matching — matches the ISA06/ISA08 IDs to a configured trading partner in your account.
  4. Output routing — delivers the processed data per the output mode configured for that partner (EDI passthrough or JSON API).
  5. 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.

TriggerSuggested helpHuman checkpoint
IK3/NM1 validation failure on an 837Explain 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 testingDraft 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 mismatchFlag duplicate lines, missing PO references, tax/freight mismatch candidates, or remittance reconciliation gaps.Finance approves the final accounting writeback.

Supported Formats

FormatExtensionsNotes
ANSI X12.edi, .x12, .txt, .datEnvelope 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, .txtLimited support — contact support for EDIFACT partners.
Flat File (CSV/TSV).csv, .tsv, .txtRequires a custom map — contact support.

Output Modes (EDI vs API)

Per trading partner, you choose how processed data is delivered:

ModeDescriptionBest for
EDIProcessed X12 EDI forwarded to SFTP/AS2 endpoint or available for download.Partners that require raw EDI output, legacy system integration.
API / JSONEDI 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

© 2026 SignalEDI Inc. All rights reserved.