Overview
Understanding Norfolk Southern integration
Who this is for: Shippers and logistics providers that ship by rail with Norfolk Southern, and the freight payables and cash application teams that receive its freight bills and remit payment.
Scope: Norfolk Southern's public pages describe only billing and remittance EDI. Shipment documents such as the 404 and status messages are not described there and are listed as commonly used in rail EDI.
For most shippers, the first Norfolk Southern exchange that can be automated is billing. Norfolk Southern's billing and financing page describes EDI as the way to receive freight bills electronically (the 410 billing support mailbox handles setup and testing questions) and to remit ACH payments electronically with an 820 addenda record, which it says shortens the payment cycle and avoids cash application errors. A separate cash application mailbox handles EDI remittance questions.
Alongside EDI, Norfolk Southern offers eFreightBill in its AccessNS portal. You can view and download freight bills, create customized summaries and resolve issues there. You register in AccessNS and select eFreightBill, and freight overcharge claims are submitted in the Revenue Claims Center under the Manage tab. An ACH Debit Plan is also described, with dispute cut-off times before the debit date.
Norfolk Southern's public pages reviewed here do not describe shipment-side EDI, such as the 404 shipment instruction or status messages, or connection methods. ECOM maps the 410 into your payables and audit systems, builds the 820 remittance from your payment run, and tests and monitors every file after go-live, as software, as a managed service or both.