Load invoices are sent from and received to the TMS as EDI 210 transactions.
Rail invoices are are received as inbound EDI 410 transactions. Motor Carrier Summary Freight Bill Manifests are received as inbound EDI 224 transactions.
See the EDI Specification Guide for payload examples.
EDI 210
Inbound
Carriers and Vendors send EDI 210 transactions to the Revenova Partner VAN. When the EDIJob batch process runs, the GetLoadInvoices API call is made. All accumulated EDI 210 transactions are returned to the TMS from the Partner VAN in an XML format.
Inbound EDI 210 transaction are received in the TMS and either create a new Vendor Invoice record or match to an existing Vendor Invoice. Individual Carriers may have identical PRO Number so Loads are matched based on the PRO Number and the Carrier (carrierTradingPartnerId).
EDI 210 transactions support the following date formats. If a date does not following one of the following formats an error email is generated and sent with the transaction XML for troubleshooting.
YYYY-MM-DD
MM/DD/YYYY
MMDDYYYY
YYYYMMDD
Inbound 210 Matching Logic
The TMS attempts to create a new or update an existing Vendor Invoice based on the following logic.
EDI 210 transactions are received into the TMS.
The TMS attempts to match the CarrierTradingPartnerId from the transaction XML to an existing EDI Location. The Trading Partner (Account) field of existing EDI Locations is compared. If no match is found, an exception prevents any further logic from matching. When no match is found for the CarrierTradingPartnerId, an email is sent to the EDI Admin. The TMS is unable to create an Unmatched EDI Transaction record without a Carrier account.
A Trading Partner/CarrierTradingPartnerId match is found. The TMS then matches the PRO Number from the transaction XML to the TMS Load PRO Number and Carrier Account Trading Partner fields.
If multiple Loads are matched, an Unmatched EDI Transaction record is created.
When no Load matches to the transaction XML PRO Number, another search is completed with the Shipment Id from the transaction XML. The TMS searches by the Shipment Id and compares to the Load Number.
If no Load Number matches or multiple Load Number matches are found, an Unmatched EDI Transaction record is created.
Inbound EDI 210 transactions that do not contain a PRO Number, the TMS searches for Loads by the Shipment Id and compares to the Load Number.
If multiple Loads or no Loads are matched on this search, an Unmatched EDI record is created.
Any searches that result in no matches create an Unmatched EDI Transaction.
When a transaction is successfully matched to a Load, the TMS compares all Vendor Invoice records for the Load to determine if the EDI 210 transaction matches to an invoice.
If the invoice is in a Pending status, it is updated with the data from the EDI 210.
If the invoice is NOT in a Pending status, the invoice is NOT updated with the data from the EDI 210. A failed EDI 210 transaction is logged.
If no invoice is matched, a new Vendor Invoice is created.
If no match is found the EDI Administrator receives an EDI batch job error email.
The Invoice Date and Invoice Due Date fields must be formatted correctly to properly match. A separator must be included for both fields between the month, day, and year. Example: 2024-08-12.
Manage Unmatched EDI Transaction records with the Unmatched EDI Transaction LWC.
Accounting Seed orgs follow the same matching logic. Instead of Vendor Invoices, Payable records are created or updated.
See the EDI Specification documentation for XML and field information for EDI 210 transactions.
Outbound
The TMS runs the SendLoadInvoices API call and sends the queued EDI 210 transactions to the Partner VAN.
The TMS Admin Configuration EDI Shipment Id field is used primarily for outbound transactions.
The TMS sends Load stop information including those with the same location for multiple stops on a single Load.
EDI 410
The following fields are saved to the Vendor Invoice record from the EDI 410 transaction.
ultimateShipper
ultimateConsignee
billTo
Inbound 410 Matching Logic
The TMS attempts to create a new or update an existing Vendor Invoice based on the following logic.
EDI 410 transactions are received into the TMS.
No Trading Partner Match
The TMS attempts to match the CarrierTradingPartnerId from the transaction XML to an existing EDI Location.
The Trading Partner (Account) field of existing EDI Locations is compared.
If no match is found, an exception prevents any further logic from matching.
When no match is found for the CarrierTradingPartnerId, an email is sent to the EDI Admin.
The TMS is unable to create an Unmatched EDI Transaction record without a Carrier account.
Trading Partner Match
A Trading Partner/CarrierTradingPartnerId match is found.
The TMS then matches the PRO Number from the transaction XML to the TMS Load PRO Number and Carrier Account Trading Partner fields.
If multiple Loads are matched, an Unmatched EDI Transaction record is created.
Trading Partner Match, no PRO Number Match
A Trading Partner/CarrierTradingPartnerId match is found.
No match is made to a Load PRO Number.
The TMS matches the transaction Waybill Number to Load Waybill Number fields.
The TMS checks the CarrierTradingPartnerId with the Trading Partner to confirm the match.
If multiple Loads are matched, an Unmatched EDI Transaction record is created.
No PRO Number or Waybill Number Match
When no Load matches to the transaction XML PRO Number, another search is completed with the Shipment Id from the transaction XML.
The TMS searches by the Shipment Id and compares to the Load Number.
If no Load Number matches or multiple Load Number matches are found, an Unmatched EDI Transaction record is created.
410 Transactions without a PRO Number or Waybill Number
Inbound EDI 410 transactions do not contain a PRO Number.
The TMS searches for Loads by the Shipment Id and compares to the Load Number.
If multiple Loads or no Loads are matched on this search, an Unmatched EDI record is created.
Any transactions that result in no matches create an Unmatched EDI record.
Manage Unmatched EDI Transaction records with the Unmatched EDI Transaction LWC.