Is there a way to support both the versions?If file is having CRLF at correct position then B2B will be able to process it but if file generated on Linux is not having CR character itself then it will fail at windows.
I have configured segment delimiter as 0x7e0x0A (tilda and linefeed - linux new line character). However if i send ~LF in the input file, B2B is not recognizing it. However if i send, ~CRLF, B2B recognizes it and processing it correctly.Ideally 0x7e0x0A should work without any issue if file is correct. If you can send me the agreement export with the test payload which you are using then I may quickly verify.