Based on the bank specifications, a printed check needs to have a Transaction Code of 320 and a voided check a Transaction Code of 370 (Transaction Code is the name of the column given by the bank). I have been testing the Transformation Rule to replace the system created Record Type Code for an issued and voided check to the appropriate Transaction Code. For example, by default an issued check will have a Record Type Code of “O”, I want to replace this to 320. Using the Transformation Rule, I am able to successfully, update the Transaction Code.
My problem is that when exporting the Positive Pay file, I receive an error that the Record Type field does not have the length that is required. In the error, my expected field length is 3, but the actual is 5. I then updated the field length to 5 in the Data Exchange Definition. I received a similar error message when running the export that the actual length is greater than the expected.
Only until I enter a length of 15 am I able to successfully export the Positive Pay file. The Positive Pay file includes the correct Transaction Code value, however, there is 12 character gap until the next column value. The field length should only be 3 characters according to the bank specifications. My question is, how can I setup the Data Exchange Definition to successfully display the correct Transaction Code and use only 3 characters?
*This post is locked for comments
You'll need to daisy-chain transformation rules. Add a "next rule" reference for a second rule that changes "V" to "370".
Did you ever get this file setup properly? I am trying to do the same thing, convert transaction codes to 320 and 370. I setup a transformation rule to convert normal check from code O to 320. I do not see how I can add a second rule for the voided checks.
André Arnaud de Cal...
291,979
Super User 2025 Season 1
Martin Dráb
230,848
Most Valuable Professional
nmaenpaa
101,156