r/edi

I worked with EDIs in the past and got tired of two things: every decent viewer is either paid enterprise software, or it wants you to upload your file to some server. Uploading real trading-partner data to a random website never sat right with me. So I built EdiPeek (edipeek.com). You paste raw EDI and it breaks down every segment and element in plain English. It also gives you a business summary of what the transaction actually means, so for an 850 it'll tell you who's ordering what from whom, for how much. It handles both X12 (850, 810, 856, 837, 835, etc.) and EDIFACT (ORDERS, INVOIC, DESADV, etc.). Everything runs locally in your browser, so nothing ever leaves your machine. That was the whole point for me, since a lot of what I look at is confidential. It's completely free, no signup. I also wrote up some guides on reading the common transaction types if that's useful to anyone. Would genuinely appreciate feedback from people who deal with this stuff daily. If there's a transaction type or segment I'm not handling well, let me know and I'll fix it.

https://edipeek.com/x12/

I feel like every post or comment in this thread is about people hating on SPS Commerce, so I am curious as to why its still such a big company and so widely used? Or are the majority to people happy with it, but just no active on this sub

One external vendor is placing 340 files through python script in IBM sterling Mail box path. But for even 5-6 files are also getting dropped no issues with IP and my server can accommodate 20 go files effortlessly.
But my vendor needs all 340 files in 3-4 minutes.
Error message :- Abrupt end of put operation client close before transfer could complete.
We are receiving 4000-5000 transactions but not sure while this files are getting dropped after 5-6 files but IBM team suggested to keep sleep time of 20 s call but they don’t want that.
IBM support also had no answer.
Anyone has similar experience please share your Valuable insights!!!!

We’re building an 835 remittance sync engine and would appreciate feedback from anyone who has worked on ERA processing, payment posting, clearinghouses, or RCM systems.
Some scenarios we’re currently evaluating:
- Adjustment capping that can create negative balances, particularly when reversals and positive remittances are processed out of order.
- Split remittances where adjustments need to be allocated across multiple service lines.
- Service-line matching when payers omit modifiers (e.g., RT/LT) or other identifying information, potentially causing remittances to be applied to the wrong line.
- PR (Patient Responsibility) calculations across resubmissions, denials, duplicate claims, and re-adjudications.
- Reversal remittances where the original payer/remit type is not clearly identifiable.

For those who have implemented remittance posting systems, what other payer behaviors, 835 edge cases, reconciliation challenges, or architectural pitfalls should we be considering?

Looking for both technical and business-process perspectives. Happy to share more details and examples in the comments.

I have to create an 894 output file. Normally we do this from our system as flat files, then map them. It's pretty easy. But in this case, the person who is supplying the data file, literally has the entire thing mapped into a valid 894 5010 UCS file (with proper ISA and GS fields).

Is there a way to load this into GENTRAN:Director? I tried a straight map from 894 to 894, hoping it would pick up the ISA ID and match it, but that didn't work. Then I tried the "process file..." option from the command menu, but that loaded the file in the "?in" drawer not ID'ing the partner it was supposed to be paired to (and more importantly, it's in the ?in not ?out error drawer).

I double checked and made sure I didn't have the ISA06 and ISA08 reversed or something, but ours is in 06 and the partners is in 08.

I'm about to just ask them to export a flat file I can map instead, but I feel thats going backwards, and this SHOULD be easy.

EDIT: Also, I just tried creating an export map for the 894 and mapped it to an inbound type document, flipped the IDs and my map worked fine, giving me a proper inbound document. grrrr.

EDIT 2: Well, I kind of got it working, but I can't believe that this is how its supposed to be done, so if anyone has a better way please let me know. What I did was I used the inbound document version with swapped IDs, changed the map to a turnaround type from an export type, then it generated an 894 in the workspace that was properly formatted for sending.

EDIT 3: Anyone know if theres a way to change the document name via an extended rule instead of standard? if so, whats the proper way to reference it?