Does the X12 viewer upload my EDI to a partner?
No. It is a public evaluation sandbox and does not transmit files to a trading partner. Use only synthetic or scrubbed payloads.
Free X12 viewer
Read X12 EDI without counting asterisks
Paste synthetic or scrubbed X12, or load a bundled 850, 856, 810, healthcare, or acknowledgement sample. Signal identifies the transaction, explains issues, and shows parsed JSON without saving production partner data.
No account requiredParsed JSONSynthetic data only
Verify before you start
Healthcare control readinessAudit trailsSOC 2 readinessService policy
Evaluate without a sales call
Most buyers are not ready to buy on the first visit. Start with a free tool or requirement check — then trial when you are ready.
- Signal sandbox850 / 856 / 810 + missEDI test labTest an EDI file before your partner sees it. Production validators plus a partner simulator — a simulator pass is not partner certification.
- Signal sandboxX12 + ASNCheck with SignalEDI validatorUse the free EDI validator to ask Signal to validate X12, check retail ASN readiness, draft setup checklists, and download sandbox reports before onboarding.
- SandboxX12 to JSONEDI mapping previewPreview how healthcare claims, purchase orders, and invoices map into API-ready JSON before production setup.
- ViewerX12 readerX12 viewer and EDI readerOpen safe X12 samples, inspect envelopes and segments, view parsed JSON, and review validation messages without connecting a partner mailbox.
- Document tool850EDI 850 purchase-order viewerInspect a synthetic 850, trace BEG, N1, and PO1 structure, and preview an order-oriented JSON representation before mapping the buyer packet.
- Document tool856 ASNEDI 856 ASN validatorCheck a safe advance ship notice sample, inspect shipment and HL structure, and open ASN readiness before retailer-controlled testing.
- Document tool810EDI 810 invoice validatorInspect a synthetic invoice, PO reference, line structure, parsed JSON, and fix suggestions before buyer or QuickBooks mapping.
- MappingX12 → JSONX12 to JSON previewTrace synthetic claim, purchase-order, and invoice elements into API-ready objects while keeping partner-specific rules explicit.
- MappingJSON → X12JSON to X12 previewTrace application fields into example X12 segments and safe payloads before implementing and validating a partner-specific outbound map.
- ReadinessBuyer-packet firstEDI requirements checkerTurn a customer mandate and non-sensitive buyer notes into a local readiness checklist without guessing private retailer specifications.
- CalculatorNamed vendorsNamed competitor EDI cost calculatorModel SignalEDI against Orderful Web EDI, SPS Commerce estimates, and healthcare-only Stedi usage pricing with visible assumptions.
- CalculatorTransparent TCOEDI cost savings calculatorCompare your current provider's setup, base, and per-document fees against SignalEDI's published plans using your own volume.
- LibraryTrading partner compatibilityCheck retailer and marketplace document requirements before you commit to a trial.
- IntegrationsConnector catalogBrowse ERP, accounting, and API connectors without booking a sales call.
Key takeaways
- Open common X12 samples and inspect envelope and document structure.
- See parser output, validation messages, and a simulated acknowledgement together.
- Verify every partner-specific field against the current implementation guide.
Check with Signal
0
samples checked this session
Stored in this browser only; no production partner data is persisted.
Retail purchase order with buyer identity and line-item quantity. Retailer response: 997 accepted, ASN required before invoice.
Drop your EDI test file here
or click to browse — it loads straight into the editor below.
Drop a file here, or click to browse — .edi, .x12, .txt, or .dat (under 20KB).
X12 editor preview
1ISAISA*00* *00* *ZZ*SENDERID *ZZ*PAYERID *260504*1430*^*00501*000000001*0*T*:~GS*HC*SENDER*PAYER*20260504*1430*1*X*005010X222A1~ST*837*0001*005010X222A1~BHT*0019*00*CLAIM1042*20260504*1430*CH~NM1*85*2*SIGNAL CLINIC*****XX*1234567893~CLM*CLAIM1042*145.00***11:B:1*Y*A*Y*I~SE*5*0001~GE*1*1~IEA*1*000000001~
- Signal highlights envelopes and document-specific segments before partner simulation.
- Inline markers surface missing loops and date-format issues before partner testing.
- Use synthetic samples or scrubbed payloads only - no production partner data.
Signal result
Needs correction
Score 70/100 · Purchase order · 9 segments
Signal activity
What Signal checked in this sandbox run.
Receivedcomplete
Sample payload received in a sandbox-only validation context.
Parsedcomplete
9 X12 segments detected.
Validatedblocked
2 errors and 0 warnings found.
Ack simulatedwarning
997 rejected for correction
997 rejected for correction
Partner simulation stops before production send and returns the first actionable segment issue.
Signal Fix suggestions
- Populate ISA02
- Populate ISA04
{
"schema": "SignalEDI/1.0",
"transactionSet": "850",
"transactionSetName": "Purchase Order",
"interchangeControl": {
"senderID": "RETAILER",
"receiverID": "SUPPLIER",
"controlNumber": "000000003",
"date": "260504"
},
"segmentCount": 9,
"valid": true,
"recognized": true,
"semanticValidation": "supported",
"purchaseOrder": {
"orderNumber": "PO1001",
"purpose": "00",
"type": "SA",
"orderDate": "20260504",
"buyer": {
"name": "RETAILER",
"qualifier": "92",
"id": "STORE17"
},
"seller": null,
"shipTo": null,
"lineItems": [
{
"lineNumber": 1,
"quantity": 12,
"unitOfMeasure": "EA",
"unitPrice": 19.99,
"basisOfPrice": "",
"productQual": "VN",
"productId": "SKU-100"
}
],
"totalLineItemCount": 1
}
}Free X12 Viewer FAQ
Which X12 documents can I view?
The bundled sandbox includes 837, 835, 850, 856, 810, 999, and 277 examples. Other X12 payloads may be parsed, but partner-specific compliance still requires the current implementation guide.
Is a valid result the same as retailer certification?
No. Local syntax and structure checks prepare your side; the retailer or payer controls its own test cases, approval, and production activation.
Move from a safe sample to a governed workspace
Public tools use synthetic or scrubbed data. Continue to trial when you need saved mappings, partner setup, and operational history.
Explore SignalEDI
Continue with free EDI tools
Pricing, checkout, solutions, support, partner requirements, and trust artifacts stay linked so buyers do not dead-end on a single page.