Docs / X12, EDI, and clearinghouse integrations
FOUNDATIONAL / PARTIAL / CUSTOMER CONNECTIVITY REQUIRED
⏱️ 2 min read · 255 words
X12, EDI, and clearinghouse integrations
DenialOS contains X12/EDI processing and clearinghouse connector foundations, including ERA/835 parsing and financial reconciliation workflows.
Current implementation
- ERA/835 intake: IMPLEMENTED
- financial parsing/reconciliation: IMPLEMENTED
- X12 processing foundations: IMPLEMENTED / PARTIAL by transaction type
- clearinghouse connector profiles: PRESENT where configured in the repository
- live clearinghouse customer connectivity: NOT PROVEN
Source boundary
EDI transaction data is treated as source material. Downstream workflows consume parsed, validated financial facts instead of relying on unparsed vendor-specific payloads.
A clearinghouse integration becomes production-enabled only after endpoint/credential setup, test transactions, reconciliation evidence, customer authorization, and operational validation.