Skip to content

Added support for CTX file #16

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.

Sign up for GitHub

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

Jump to bottom
Open
junian wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Added support for CTX file #16

junian wants to merge 3 commits into from

Conversation

@junian
Copy link

@junian junian commented Oct 13, 2015

The current state doesn't handle CTX file correctly. So that is why I made some changes to accomplish this.

  1. Support for character *.~ in addenda record. Currently if there is one of those char in addenda, the string is truncated. CTX uses X12 EDI 820 format and those chars will appear. Source: http://www.1edisource.com/transaction-sets?TSet=820
  2. Added company name in the entry because CTX uses it.
  3. Added addenda record in the entry because CTX uses it.

Complete CTX details can be found here http://www.osc.nc.gov/secp/Bank_of_America_NACHA_File_Specs.pdf

Thanks in advance

Junian added 3 commits October 10, 2015 00:26
Payment information associated with the immediately preceding Entry D…
1b4f4ad 
…etail Record. Must contain NACHA endorsed ANSI ASC X12 data segments or NACHA endorsed banking conventions. The asterisk (“*”) must be the delimiter between the data elements, and the back slash (“\”) must be the terminator between the data segments.
added support for CTX transaction
0c51689
can use negative sign
6214dda
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@junian