Skip to content

X12 transaction code

X12 990 Response To A Load Tender

X12 990 Response To A Load Tender: explore its business purpose, mapping identifiers, validation tests and 168 partner references across 240 listed channels.

Standard
X12
Code
990
Partner references
168

Implementation guide

X12 990 mapping and validation

X12 990 Response To A Load Tender is used when a carrier responds to a tender. Preserve original load reference, carrier and response so the load-tender response in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record load-tender response

original load reference, carrier and response

  • Define which combination of original load reference, carrier and response identifies one business record, its lines and any later revision.
Update the receiving system Processing the load-tender response

ID assigned by the receiving system and processing result

  • Associate acceptance with the correct version of the load tender.
  • Test a declined tender and ensure it returns to dispatch for reassignment.
Check the processing result Processing status for the load-tender response

Original document reference and matching response

  • Reconcile the load-tender response with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a carrier responds to a tender. Name the operational owner of the load-tender response and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map original load reference, carrier and response. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic load-tender response data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful load-tender response processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 990 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic load-tender response data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out load-tender response without processing it twice.

Document structure

X12 990 Response To A Load Tender at the element level

The X12 990 reference contains 16 segment entries and 108 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
16
Data elements
108
Mandatory elements
38
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
B1 4 1
N9 3 1
N7 24 1
L9 2 2
V9 20 1
K1 2 1
S5 11 2
Key identifiers in 990
  • Shipment Identification Number
  • Reference Identification Qualifier
  • Equipment Number
  • Special Charge or Allowance Code
  • Monetary Amount
  • Event Code
  • Free-Form Message
  • Stop Sequence Number

Find your trading partner for X12 990

168 partners, 240 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 990 Response To A Load Tender appears in this catalog

The largest groups of classified 990 catalog entries are in logistics & transport, grocery & food and retail.

By industry

  • logistics & transport 120 channels
  • grocery & food 48 channels
  • retail 14 channels
  • consumer goods 13 channels
  • building & hardware 10 channels
  • manufacturing & industrial 8 channels

By network

  • E2open 41 channels
  • MercuryGate 35 channels
  • Manhattan Associates 17 channels
  • Ryder 16 channels
  • Blue Yonder 13 channels
  • BluJay 5 channels

FAQ

X12 990 questions

What is X12 990 Response To A Load Tender used for?

990 is used when a carrier responds to a tender. It carries information for the load-tender response. Match it to your business system using original load reference, carrier and response.

Which partners list X12 990?

The directory on this page links 168 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 990?

Start with original load reference, carrier and response and the target load-tender response. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 990 error handling?

Associate acceptance with the correct version of the load tender. Test a declined tender and ensure it returns to dispatch for reassignment. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 990 relate to other EDI messages?

X12 204 Motor Carrier Load Tender; X12 214 Transportation Carrier Shipment Status Message are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 990 and 204?

990 is used when a carrier responds to a tender. 204 is used when a shipper offers a load to a carrier. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.