--- title: "Summer '25 Unmatched EDI Transaction" slug: "summer-25-unmatched-edi-transaction" tags: ["EDI", "Admin", "Expanded Content", "LWC"] updated: 2025-09-03T19:19:08Z published: 2025-11-04T19:05:52Z canonical: "documents.revenova.com/summer-25-unmatched-edi-transaction" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Summer '25 Unmatched EDI Transaction ## **Overview** The Unmatched EDI Transactions Lightning Web Component provides the ability to match inbound EDI 210 and 410 transactions with a Load or Vendor Invoice. For more information on matching logic, see the EDI 210 and 410 documentation here. ## Unmatched EDI Transaction LWC From the App Launcher, search for *Unmatched EDI Transactions*. Select the application from the list of results. For convenience, add the Unmatched EDI Transactions item to the Navigation bar. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/App Launcher - Unmatched EDI.png) Inbound EDI 210 and 410 transactions that do not match to a Load display in the list view as shown below. Select the *Pending* list view from the drop-down to display the Unmatched Transaction records. Add or remove fields from the list view as necessary. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads(1).png) Each Unmatched Transaction record contains a fingerprint of the XML payload. These fingerprints are compared based on multiple field matches. When they do not match, a new Unmatched Transaction record is created with the **Duplicate Indicator** field shown below. The following scenarios describe the circumstances that result in the creation of an Unmatched EDI Transaction record. **Scenario 1 (210 & 410 Invoices)** 1. The Trading Partner (CarrierTradingPartnerId field) does not match a TMS Account record. 2. No Unmatched EDI Transaction record is created without a matching Account. **Scenario 2 (210 & 410 Invoices)** 1. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. Multiple Load **PRO Numbers** match the XML PRO Number. 2. An Unmatched EDI Transaction record is created. **Scenario 3 (410 Rail Invoices)** 1. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. No Load **PRO Number** is matched to the XML Pro Number. 2. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. The TMS attempts to match the XML Waybill Number to the Load **Waybill Number**. 3. If multiple Load records match the **Waybill Number**, an Unmatched EDI Transaction record is created. **Scenario 4 (210 & 410 Invoices)** 1. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. No Load **PRO Number** is matched to the XML Pro Number. 2. No Load **Waybill Number** is matched to the XML Pro Number. 2. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. The TMS searches for a match on the XML Shipment Id to the **Load Number**. 3. No **Load Number** or multiple **Load Numbers** match the XML Shipment Id. 1. An Unmatched EDI Transaction record is created. **Scenario 5 (210 & 410 Invoices)** 1. The Trading Partner (CarrierTradingPartnerId field) matches a TMS Account record. 1. The EDI transaction XML does not contain a PRO Number or a Waybill Number. 2. The TMS searches for a match on the XML Shipment Id to the **Load Number**. 3. No **Load Number** or multiple **Load Numbers** match the XML Shipment Id. 1. An Unmatched EDI Transaction record is created. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction List - Duplicate.png) From the list of Unmatched EDI Transaction records select the record to open it in the LWC. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 2.png) View additional column information for by clicking the caret and selecting *Wrap Text*. Display Loads based on the status in the upper-right corner. In the screenshot below the Loads are all in a status of *Pending*. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EDI Order Update Console - 8.png) When an EDI Transaction is matched to a Load, the status changes to *Invoices Created*. Choose the pencil icon to select a different status. Select *Awaiting Reconciliation* to indicate disputed XML. Click **Save** when finished. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - Change Status.png) Match transactions to Loads by selecting from the list of available Loads below the transaction. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 5.png) Click the filter button to open the modal. Filter Loads by the following criteria to narrow available Loads to a manageable selection. - Carrier - Customer - Load Status A lookup to the Load Number provides the ability to find a specific Load. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 6.png) Select the appropriate Load to match to the transaction by checking the box. Click the **Create New** button to generate a new Vendor Invoice record. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 7.png) Any existing Vendor Invoice records related to the selected Load display below the list of available Loads. Update an existing invoice by selecting the checkbox for the invoice. Click the **Update Invoice** button to update the Vendor Invoice with the new values from the EDI transaction. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 8.png) Once the Vendor Invoice is created or updated the **Status** and **Load** fields change to reflect the match. In the case of an invoice update, changes in the **Payload** field may also be visible. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Unmatched EDI Transaction LWC - with Loads - 9.png) A feature in Salesforce that enhances the user experience by providing interactive and customizable components within Salesforce applications. Revenova uses Lightning Web Components to deliver features that can be tailored to suit your specific needs and preferences.