edi-energy

EDIFACT parse · validate · build — stateless German energy market library

edi-energy is the low-level EDIFACT processing layer for the German energy market (EDI@Energy / BDEW MaKo). It is a purely stateless library: no async, no I/O, no runtime dependencies. All parsing, validation, and message building happen in-process without allocating threads or network connections.

This crate is the foundation for makod and the mako-* domain crates, but it is also useful standalone for:

• AS4 gateway pre-processing
• Regulatory compliance checking pipelines
• ERP import/export converters
• Testing harnesses for MaKo messages

Message Types

The default feature set enables all 17 message types. Use explicit feature selection to reduce binary size for production tooling.

Quick Start

Add to Cargo.toml:

[dependencies]
edi-energy = "0.6"

Parse and validate

use edi_energy::{parse, ValidationSummary};

let bytes = std::fs::read("message.edi")?;
let msg = parse(&bytes)?;

// Detect what arrived
let pid = msg.detect_pruefidentifikator().map(|p| p.value());
let fv  = msg.detect_release().map(|r| r.to_string());
println!("PID {pid:?}  FV {fv:?}");

// Run AHB + MIG rule enforcement
let report: ValidationSummary = msg.validate()?;
if !report.is_valid() {
    for err in report.errors() {
        eprintln!("[{}] {}", err.rule_id(), err.message());
    }
} else {
    println!("valid ✓");
}

Parse as hard error

use edi_energy::{parse, into_error_result};

let msg = parse(&bytes)?;
into_error_result(msg.validate()?)?;  // returns Err if any validation error

Interchange stream (multiple messages)

use edi_energy::{Platform, parse_interchange};
use std::io::BufReader;

let reader = BufReader::new(std::fs::File::open("bulk.edi")?);
for result in parse_interchange(reader) {
    let msg = result?;
    println!("{}", msg.try_message_type().map_or("?", |t| t.as_str()));
}

Build a UTILMD message

use edi_energy::builders::UtilmdBuilder;
use edi_energy::FormatVersion;

let fv  = FormatVersion::parse("FV2025-10-01")?;
let edi = UtilmdBuilder::new(fv)
    .sender("9900357000004", "500")
    .receiver("9904320000009", "500")
    .pruefidentifikator(55001)
    .marktlokation("51238696782")
    .lieferbeginn("20251001")
    .build()?;

println!("{edi}");

See docs/builders.md for the full builder API and all message types.

Active Format Versions

Both FV2025-10-01 and FV2026-10-01 are simultaneously active in production deployments during the transition window (±7 days around each annual cutover). The profile registry resolves the correct rules from the UNH association code automatically — no per-message format selection is needed.

Features

To enable a minimal build for a single message type:

[dependencies]
edi-energy = { version = "0.6", default-features = false, features = ["utilmd", "serde"] }

Multi-Tenant and Test Isolation

The module-level parse() and parse_interchange() functions use a global profile registry. For test isolation or multi-tenant gateways use Platform directly:

use edi_energy::Platform;

let platform = Platform::with_all_profiles();
let msg = platform.parse(&bytes)?;
let report = msg.validate()?;

Platforms are cheap to clone (profile data is Arc-shared). See docs/platform.md for custom profile subsets, DoS limits, and hot-reload patterns.

Built-In Examples

Run with cargo run --example <name> --all-features:

Documentation

Regulatory Standards

• EDI@Energy UTILMD Strom AHB S2.2 / Gas AHB G1.2 — BDEW, FV2026-10-01
• EDI@Energy MSCONS AHB 3.2 — BDEW, FV2026-10-01
• EDI@Energy APERAK AHB 2.2 — BDEW, FV2026-10-01
• EDI@Energy CONTRL AHB 1.0 + ausserordentliche Veröffentlichung 2025-12-11
• All current MIG/AHB releases as of FV2026-10-01
• BNetzA rulings BK6-24-174, BK6-22-024, BK7-24-01-009 (process scope)