Browse categories
Explore
Fiverr Pro
English
$
USD
I will convert edi x12 files to excel, CSV or json with a validation report
About this Gig
Send me your EDI file. You get back a spreadsheet you can actually use.
WHAT YOU GET
Excel in two layouts - one wide row per line item for pivoting, and normalised header/detail sheets for loading into a system. CSV and JSON on request. Every code resolved to its meaning, so you see "Prepaid (by Seller)" next to PP, not just PP.
Plus a validation report: mismatched control numbers, wrong segment counts, broken hierarchies. If your file is malformed I tell you before you act on it.
COVERAGE
Fully mapped business format: 850 purchase order, 810 invoice, 856 ASN, 997/999 acknowledgment.
Any other X12 set - 214, 846, 940, 852, 820 and more - comes back as a structured segment-level breakdown: every segment named, every shared code resolved. Readable, but not a mapped conversion. I always tell you which you are getting before you order.
All X12 versions, 3010 through 6020+. EBCDIC, odd delimiters and multi-interchange files are handled.
NOT COVERED
EDIFACT. Healthcare sets (837, 835, 834, 270/271, 276/277, 278) - I do not accept PHI. EDI file generation. AS2/SFTP/VAN setup.
Message me and I will tell you exactly what the output will look like.
Technology:
Excel
•
Python
Expertise:
Data manipulation
•
Transformation
FAQ
What EDI versions do you handle?
All X12 versions - 3010, 4010, 4030, 5010, 6020 and later. Version affects which fields are present, not how the file is read. I have tested against real 3010 and 5010 files as well as 4010.
Can you handle healthcare EDI?
No. I do not accept 837, 835, 834, 270/271, 276/277 or 278. These carry protected health information and HIPAA obligations. My tool refuses them automatically. Please do not send them.
Do you support transaction set X?
Yes. 850, 810, 856 and 997 come back as a clean business-format spreadsheet. Every other X12 set comes back as a structured segment-level breakdown - every segment named, shared codes resolved. I will tell you which you are getting before you order, and price accordingly.
Flat rows or normalized header and detail?
Both, at no extra cost. Flat gives one wide row per line item with header fields repeated - best for pivot tables. Normalized gives separate Header and Line Items sheets joined on document number - best for loading into a system. Tell me which you prefer, or take both.
What about EDIFACT?
Not currently. I handle ANSI X12 only. If you send an EDIFACT file I will tell you straight away rather than returning something wrong.
My partner rejected my file. Can you help?
Yes - send me the 997 they returned. You get a plain-English report: which document failed, which segment and element, what the error code means, and what to change. This is usually a same-day job.
Can you handle a file I have not described here?
Send it. I will run it through my parser and tell you within a few hours exactly what comes out, what tier it falls into, and what it would cost. No charge for that answer, and no obligation to order.
