Return, dishonored Return, and/or contested dishonored Return Entries are in the same batch.

[wadearnold]

Return, dishonored Return, and/or contested dishonored Return Entries are in the same batch.

[wadearnold]

Dishonored Return and Contested Dishonored Return entries need to be supported

 EntryDetail.Category
CategoryDishonoredReturn
CategoryDishonoredReturnContested

[chuckiebluestar]

Rule-wise, the three different kind of returns would not be in the same batch since they flow in different directions.

[wadearnold]

Thanks for the insight @chuckiebluestar ! With 300+ pages of the nacha specification I still get confused.

[chuckiebluestar]

Wade: Thanks for responding. I'm a business-side ACH geek with a little coding knowledge, and I would like to get involved with this project.

…

On Fri, Jun 15, 2018 at 10:58 AM, Wade Arnold ***@***.***> wrote: Thanks for the insight @chuckiebluestar <https://github.com/chuckiebluestar> ! With 300+ pages of the nacha specification I still get confused. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#59 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHRUnyG-PmhCSKBiclrrSiHAT9hZ2ZAPks5t89migaJpZM4LjO3d> .

[wadearnold]

@chuckiebluestar that would be phenomenal! The project has the opposite problem. We are programmers trying to figure out ACH! Our current goal is to make the most complete open source implementation of an ACH reader/writer. Phase two is adding CSV/JSON parsing from the command line and REStful interface to the library so that other languages can leverage the solution. If we can make it that far then we want to make a ach origination platform that would be more inline with a Stripe style interface that abstracts the ach details.

We ♡ business-side