204 in. 990 out. 214 out. 210 audited. No manual re-entry.
LogAI handles the EDI transaction sets that matter in freight brokerage: inbound load tenders (204), outbound tender responses (990), status updates to shippers (214), and carrier invoice receipt (210). Structured data flows directly into the load record — without a dispatcher retyping it.
What the EDI integration covers
LogAI handles the four EDI transaction sets that run the day-to-day of a freight brokerage.
EDI 204 — Motor Carrier Load Tender
Inbound EDI 204 transactions from shippers are captured automatically by the LogAI document pipeline. Required segments are validated before a draft load record is created. Missing or malformed segments are flagged in the rejection queue — bad data never silently enters the system.
EDI 990 — Response to a Load Tender
LogAI prepares EDI 990 responses (accept or reject) after a human dispatcher reviews and decides. In v1, EDI 990 responses are always human-approved before transmission — the agent drafts the response, the dispatcher sends it. Auto-response thresholds are on the roadmap.
EDI 214 — Transportation Carrier Shipment Status
Outbound EDI 214 status updates are generated automatically as the load progresses through its lifecycle: tender accepted, picked up, in transit, delivered. Shippers who require 214 updates receive them at each milestone without your team composing a single status email.
EDI 210 — Motor Carrier Freight Details and Invoice
Inbound EDI 210 carrier invoices enter the document pipeline and are routed to the Carrier Invoice Audit agent automatically. The structured data in the 210 is compared line-by-line against the rate confirmation — the same audit that applies to PDF invoices, but without OCR.
Segment-Level Validation
LogAI validates required segments (B2, L11, N1 loops, S5 stops, L5/L0 commodity lines) before accepting a 204 into the load pipeline. Rejected transactions go to a review queue with the segment-level error, not a generic "EDI failed" alert.
No Manual Re-Entry
Shipper name, origin, destination, commodity, declared weight, and required delivery date in a valid EDI 204 flow directly into the draft load record. The same fields that a dispatcher would have typed from an email are pre-populated from the structured EDI transaction.
What each EDI transaction does in LogAI
Each transaction set has a specific direction, purpose, and human-approval rule. LogAI processes them automatically up to the point where a human decision is required.
Motor Carrier Load Tender
Inbound (shipper → LogAI)
Shipper tenders a load to your brokerage. LogAI captures and parses it into a draft load record.
Human approval: Dispatcher reviews draft and confirms before the load enters the active workflow.
Response to a Load Tender
Outbound (LogAI → shipper)
Accept or reject a shipper's tender. LogAI drafts the 990 after dispatcher decision.
Human approval: Always — dispatcher approves before transmission in v1.
Transportation Carrier Shipment Status
Outbound (LogAI → shipper)
Status updates at tender, pickup, in-transit, and delivery milestones.
Human approval: Automated at standard milestones. Exceptions require dispatcher review.
Motor Carrier Freight Details and Invoice
Inbound (carrier → LogAI)
Carrier invoice received via EDI and routed to the Carrier Invoice Audit agent.
Human approval: Dispatcher approves audit result before AP bill is created.
Connect your EDI feed to LogAI
Whether shippers send 204s directly or through a VAN, LogAI captures and processes them. Setup takes one working session.
Get Started