Steps

Open the EDI converter. Go to the Client-Side EDI converter page in a modern browser. Open the converter.

Select supported EDI files. Drag and drop supported 835, 837P/I/D, 834, 270, 271, 277CA, 999, 850, 855, 810, 856, 940, 945, 997, 846, or 852 files, or use the file picker.

Choose the output format. Select CSV, Excel, JSON, or XML output and choose whether to combine files or keep one file per input.

Choose mapping and grouping behavior. Use a registered Smart Mapping adapter or source-ordered Raw segment rows; mixed batches are grouped by detected transaction type by default.

Convert and download. Click Convert & Download ZIP, wait for processing to complete, and download the selected CSV, Excel, JSON, or XML files.

FAQs

Do you upload my files?
No. EDI parsing and export generation run in your browser; EDI file contents are not sent to the application server.

What’s supported?
Smart Mapping supports documented versions of 835, 837P, 837I, 837D, 834, 270, 271, 277CA, 999, 850, 855, 810, 856, 940, 945, 997, 846, 852. Exact version and projection boundaries are listed in the data-map documentation; other inputs can be inspected as Raw rows.

What does XML contain?
XML serializes the current Smart Mapping or Raw rows. It is not native X12 hierarchy, an implementation-guide XML schema, or a lossless X12 round trip.

How big can my files be?
Capacity depends on the browser and device memory. If a browser runs out of memory, split the file or process a smaller batch.

Can I de-identify before export?
Yes—de-identification options run locally (mask IDs/names). This is optional and configurable.

Open converter