UN/EDIFACT Transaction Quality Gate

Validate bounded UN/EDIFACT interchanges before partner transmission, ERP import, or mapping release. The Actor produces stable syntax, envelope, count, narrow message-structure, and optional partner-rule evidence—not just JSON tokenization.

Typical workflow

1. Pin one compatibility target: D96A, D01B, or D20B.
2. Submit one or more inline interchanges and choose strict/tolerant structure handling, hard limits, optional partner overlays, and optional CONTRL output.
3. Route transaction PASS, WARN, or FAIL rows and retain stable finding fingerprints for regression evidence.
4. If enabled, deliver the generated acknowledgement through your existing EDI transport. This Actor does not transmit it.

{
    "directory": "D01B",
    "mode": "strict",
    "generateContrl": true,
    "interchanges": [
        {
            "sourceId": "supplier-a-order-1001",
            "content": "UNB+UNOC:3+SENDER:14+RECEIVER:14+260916:1200+IREF'UNH+1+ORDERS:D:01B:UN'BGM+220+PO-1001+9'DTM+137:20260916:102'NAD+BY+BUYER::9'LIN+1++SKU-1:EN'QTY+21:5'UNT+7+1'UNZ+1+IREF'"
        }
    ],
    "partnerRules": []
}

Supported scope

• Syntax delimiters from UNA plus release-character handling.
• UNOA, UNOB, UNOC, and UNOY syntax identifiers.
• UNB/UNZ and UNH/UNT nesting, reference, and count validation.
• Narrow original structure profiles for ORDERS, INVOIC, DESADV, and CONTRL against compatibility pins D96A, D01B, and D20B.
• Data-driven overlays requiring or forbidding named segments.
• Up to 100 interchanges/run, 10 MB/interchange, 100,000 segments/interchange, and 10,000 messages/interchange within configurable lower defaults.

The Actor does not bundle, transform, or redistribute UNECE UN/EDIFACT directory files. Compatibility pins identify expected UNH versions; the checks are an original bounded subset and are not full official directory conformance.

Output contract

Dataset recordType is transaction, finding, or failed interchange. Transaction rows include message type/directory, references, document number, counts, and final status. Finding rows have a stable code, severity, segment location, message, and fingerprint. Canonical parsed segments are stored in CANONICAL_JSON; optional acknowledgements are in CONTRL_ACKNOWLEDGEMENTS.

No processing timestamp enters canonical evidence. Identical content and sourceId produce identical output.

Failure behavior

Invalid top-level configuration fails before work. A malformed interchange is isolated so other batch items continue. Unsafe syntax, missing terminators, broken nesting, unsupported message/directory, and resource limits fail closed. Envelope and count mismatches remain visible findings on parsed transactions.

Privacy and scope boundary

The Actor sends no EDI content to third parties. Use Apify retention settings appropriate to commercial documents. It does not provide X12, AS2/SFTP, transport, partner onboarding, custom mapping, ERP connectivity, visual mapping, business interpretation, compliance certification, or consulting.

Development

npm install
npm test
npm run quality
npm run benchmark

Changelog

• 0.1.0 — Original tokenizer, envelope/count checks, four narrow message profiles, three directory pins, overlays, stable findings, and CONTRL output.