Skip to content
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

spike: EDI record support #773

Open
adamdecaf opened this issue Aug 26, 2020 · 4 comments
Open

spike: EDI record support #773

adamdecaf opened this issue Aug 26, 2020 · 4 comments

Comments

@adamdecaf
Copy link
Member

adamdecaf commented Aug 26, 2020

What were you trying to do?
There are tons of EDI records which are supported and standardized by various vendors. These are in industries like Healthcare and trucking / logistics.

What records are most requested by the community?

See: https://datatrans-inc.com/common-edi-transaction-sets/

What did you expect to see?
Commonly supported, requested, and standardized records should be supported.

Docs

Examples

@ianberryman
Copy link
Contributor

820 is the most common set I've encountered. It's used extensively by corporates and government agencies (state and fed). I've also seen CCD+/PPD+ but, because of the 80 character limit, they typically only include part of a segment (see SSA example). The FRB resource below includes a couple other common sets.

A couple resources:

@SharonAllsup
Copy link

If you go with the 820, others to consider in that basic cycle are:

810 Invoice - Pay us for this
812 Credit/Debit Adjustment - Ooops sorry here's some money back for the defective piece
(820 Remittance Advice - What you're paying us for)
997 Functional Acknowledgement - Thanks for the 820

997 is not restricted to 820s. It can be set up to communicate anything from generic "received" to details on where syntax errors occurred in the original message being acknowledged.

@adamdecaf
Copy link
Member Author

Sounds great. Looks like we would start with 810 and go forward one record at a time. Confirming the struct/formatting looks okay at each PR.

@adamdecaf adamdecaf added this to the Unplanned milestone Jan 12, 2023
@wadearnold
Copy link
Member

We are adding support for EDI 810 in our X12 library. Once added, we can bring it into the ACH addenda parser.
moov-io/x12#16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants