W17
Warehouse receipt identification: the receipt date and number, and the shipment reference.
A warehouse’s confirmation of inventory received: what arrived, in what quantity and condition. Warehouse or 3PL to the shipper (the owner of the goods). This page covers what the 944 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
The 944 confirms receipt. After inventory announced by a 943 arrives, the warehouse sends the 944 to report what it actually received by item and quantity, noting damage, shortages, or overages against what was expected.
The owner uses it to update inventory at that location and to reconcile against the 943 and the carrier’s documents. It is the document that makes third-party inventory trustworthy.
In document order, the segments that carry the 944's meaning. A partner's implementation guide says which are required and which fields each must hold.
Warehouse receipt identification: the receipt date and number, and the shipment reference.
Parties: the warehouse and the owner.
References such as the 943 shipment id or bill of lading.
Item detail for a warehouse receipt: quantity received, unit, product identifiers, and condition.
Total receipt information: quantities received and, where used, damaged or short.
Received quantities that differ from the 943 without a clear indication of shortage or damage, so the owner’s inventory is corrected days later by email. Receipts posted against the wrong inbound shipment when references are missing.
The 944 rarely moves alone. These are the documents that precede, answer, or settle it.
A shipper’s notice to a warehouse that inbound inventory is on its way to be received.
See The 943A shipper’s instruction to a warehouse or 3PL to ship goods to a customer.
See The 940A warehouse’s confirmation that an order shipped: what, when, by which carrier, with tracking.
See The 945A partner sends the 944 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 944 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 944 that was due never arrives. The full picture is on the EDI software page.
What teams ask about the 944 and how it moves on Files.com.
An EDI 944 is the X12 Warehouse Stock Transfer Receipt Advice. A warehouse sends it to the owner of goods to confirm what inventory it received from an inbound shipment, by item, quantity, and condition.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 944 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 944 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 944 from your system’s export and drops it in the partner’s outbox for delivery.
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 944 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes