@ApratimG

You can handle the 834 file in Pega by using a File Listener plus a Parse rule instead of trying to split everything manually. First, create a File Listener on the folder where the 834 files land and point it to a Service File rule. In the Service File, configure it to use a Parse Delimited (or Parse Structured) rule to break the content. In the Parse Delimited rule, set the record delimiter as ~ so each segment like ISA, GS, INS, REF, etc. comes in as a separate line. Then, inside that parse rule, use * as the field delimiter to map each element in the segment to a property on your work or data class. Start with a few key segments (for example, INS for member, REF for IDs) and map only the fields you really need. If the 834 has repeating loops, create child parse rules or data classes and call them from the main parse rule to keep your logic clean. Finally, test with one sample 834 file in the Service File rule form and check the clipboard pages to confirm that all properties are populated correctly before turning it on in production.