spike: EDI record support

[adamdecaf]

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

• EDI_820_Guide.pdf
• EDI-820-Guide-en.pdf
• BNSF_820v4010.pdf

Examples

• 005010X306 Health Insurance Exchange Related Payments.zip
• ASC X12.zip

[ianberryman]

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:

• FRB EDI Overview: https://www.frbservices.org/assets/financial-services/ach/fedpayments-reporter-fundamentals.pdf
• General EDI Overview: http://www.gxs.com/assets/uploads/pdfs/eBooks/EDI_Basics_GXS_eBook.pdf

[SharonAllsup]

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]

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.

[wadearnold]

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