Now opening: online payments go live shortly. Email support@otrsi.ai and we'll take your request first.
Over The Road SIOTRSI

997 AK4 ... *373*8: invalid date in your 214

The date on a status event isn't a valid calendar date in the format X12 requires, so the 214 is rejected. It often happens only after the 12th of the month, which is a sign that day and month are swapped.

What you see

AK2*214*0001~
AK3*AT7*6**8~
AK4*5*373*8*20262110~
AK5*R*5~
AK9*R*1*1*0~

Reading it: AK3*AT7*6**8 = the AT7 segment, 6th segment from ST, has data element errors. AK4*5*373*8*20262110 = element position 5 (AT7-05), dictionary element 373 (Date), error code 8 (Invalid Date), and the bad value 20262110.

What it means

Element 373 is a DT (date) element: exactly 8 digits, CCYYMMDD. 20262110 would be month 21, day 10, which doesn't exist. The same rule applies everywhere element 373 is used, for example G62 dates in 204/990/214, B306 and B309 in a 210, and GS04.

Why it happens

The exact fix

  1. Send the event date as CCYYMMDD: 4-digit year, then month, then day, with no separators.
  2. If AT7-05 has no real date, don't send the status event until it does. AT7-06 (time) requires AT7-05 (syntax note C0605).
  3. Correct the event in your TMS, regenerate the 214 with new control numbers, and resend.

Before and after

Rejected
AT7*X1*NS***20262110*1430*CT~
Accepted (Oct 21, 2026)
AT7*X1*NS***20261021*1430*CT~

X1 = Arrived at Delivery Location. NS = Normal Status.

Stop it happening again

Not sure this is your error?

Paste your 997, TA1, rejected file, or the broker's error email into the free EDI Reject Checker. It decodes every AK3/AK4/AK5/AK9 and TA1 code and checks counts, control numbers, and dates in seconds. It runs in your browser, so nothing is uploaded.

Fix reports are paid up front; if we can't find the cause, the refund is automatic.

References