972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 412 Trailer or Container Repair Billing

The X12 document used to invoice the responsible party for repairs to trailers and containers transported by railroads.

Sent by
Repair facility or railroad
Received by
Party responsible for the repair, such as the equipment owner or user
Standard
ANSI ASC X12

What is an EDI 412?

The EDI 412 Trailer or Container Repair Billing is the ANSI X12 transaction set that lets a repair provider invoice the responsible party electronically for repairs to trailers and containers moved by railroads. It identifies the equipment, the damage, the repairs performed with their labor and material costs, and the party billed.

Intermodal trailers and containers are inspected and repaired at ramps and terminals. Responsibility depends on who had the equipment when the damage occurred, so repair bills reference inspection records. Electronic billing lets equipment owners audit large volumes of small repair invoices against their own rules.

How the EDI 412 worksDiagram of the EDI 412 Trailer or Container Repair Billing. Repair facility or railroad sends it to party responsible for the repair, such as the equipment owner or user. It usually follows 228. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: R11 (Beginning Segment for Trailer or Container Repair Billing) and CUR (Currency) and detail: the required R12 loop with R12 (Work Order Information), AMT (Monetary Amount Information), the required N1 loop with N1 (Party Identification) and the required R13 loop with R13 (Line Item Repair) and AMT (Monetary Amount Information). 1 optional loops are listed by their first segment.How the EDI 412 worksTrailer or Container Repair Billing: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS228Equipment InspectionReportEDI 412SENDERRepair facility orrailroadRECEIVERParty responsible forthe repair, such as theequipment owner oruser997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY820PaymentOrder/Remittance Advice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TBGS … GETransaction set 412ST … SEHEADINGR11Beginning Segment for Trailer or Container RepairBillingCURCurrency+ 1 optional loop, starting with:N1DETAILRequired loop R12 · repeats up to 9,999R12Work Order InformationAMTMonetary Amount InformationRequired loop N1 · repeats up to 4N1Party IdentificationRequired loop R13 · repeats up to 50R13Line Item RepairAMTMonetary Amount InformationBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 412. Your trading partner's implementation guide adds its own requirements.
How the EDI 412 worksDiagram of the EDI 412 Trailer or Container Repair Billing. Repair facility or railroad sends it to party responsible for the repair, such as the equipment owner or user. It usually follows 228. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: R11 (Beginning Segment for Trailer or Container Repair Billing) and CUR (Currency) and detail: the required R12 loop with R12 (Work Order Information), AMT (Monetary Amount Information), the required N1 loop with N1 (Party Identification) and the required R13 loop with R13 (Line Item Repair) and AMT (Monetary Amount Information). 1 optional loops are listed by their first segment.How the EDI 412 worksTrailer or Container Repair Billing: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS228Equipment Inspection ReportEDI 412SENDERRepair facilityor railroadRECEIVERPartyresponsible forthe repair, suchas theequipmentowner or user997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY820Payment Order/Remittance Advice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TB (GS … GE)Transaction set 412 (ST … SE)HEADINGR11Beginning Segment for Traileror Container Repair BillingCURCurrency+ 1 optional loop, starting with:N1DETAILRequired loop R12 · repeats up to9,999R12Work Order InformationAMTMonetary AmountInformationRequired loop N1 · repeats upto 4N1Party IdentificationRequired loop R13 · repeats upto 50R13Line Item RepairAMTMonetary AmountInformationBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 412. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 412, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 412 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Billing equipment owners for trailer or container repairs
  • Charging repair costs to the party responsible for damage
  • Supporting audits of repair charges

Where it fits in the document flow

Usually follows 228 Equipment Inspection Report
This document 412 Trailer or Container Repair Billing
Usually followed by 820 Payment Order/Remittance Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 412 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • R11
  • CUR
  • N1
  • R12
  • AMT
  • R13
  • SE

Practical example

The 412 in practice

A container at an intermodal ramp is found with a damaged door seal and is repaired by the ramp's maintenance contractor. The contractor sends the container owner a 412 with the container number, the repair codes, labor hours, parts and total cost, referencing the inspection report. The owner audits the bill against its repair price list and pays it.

Implementation

Implementation considerations for the 412

  • Use standard repair and damage codes that owners can audit.
  • Reference the inspection that identified the damage.
  • Identify equipment by its reporting marks and number.
  • Agree repair price lists to avoid disputes.

How ECOM helps

Automate the 412 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 412?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us