-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse ACH files to nACH object #10
Comments
Actually, yes, that's something I've been wanting to do for a while. There's two pieces to it. First, add some query capabilities so once you have an ACH file represented in nACH you could query total batch amounts, number of entries in a batch etc. The other addition would be as you suggest, parsing an actual ACH file back into an object. The former is more helpful for us right now, but we will need the ability to parse ACH files back to objects in the future. Is this something that would be helpful? |
To be honest, It probably wouldn't be that difficult. Since all the fields and their respective widths are nicely represented right now, it'd just be a matter of reversing the file generation process. |
it would be extremely helpful! I'm happy to help unit test and what not. you saw http://yawetse.github.io/nachie/ right? |
Ok, not sure what the timetable looks like, but in terms of new additions to nACH I'll keep this one pretty high on the list. And yes, we did. Pretty nifty. I'm glad it's useful. We were pretty surprised when you submitted a pull request. |
sweet, yeah I’m working on a much larger project but working on open sourcing as much as possible, and nACH is an amazing module that allowed for the kind of ACH file generation we needed. We also need to parse ACH receipts them back into a data object that we can make sense of, so it feels natural to use nACH as a solid base.
|
Any news on this feature? It would be a great one for a project I am working on. |
Feel free to submit a pull request @ortimanu ;) |
I plan to take a look at this very soon. |
Will there be any movement on this? |
this isn't a bug, it's more of a question.
have you guys worked on parsing the output back into a nACH object?
The text was updated successfully, but these errors were encountered: