--- title: "TMS 7.12 EDI 210 Billing/Payable Handling (AS)" slug: "712-edi-210-billing-payable-handling-as" tags: ["Compiled from User Guide", "Admin", "Accounting Seed", "7.12"] updated: 2024-10-29T13:55:10Z published: 2024-10-29T13:55:10Z canonical: "documents.revenova.com/712-edi-210-billing-payable-handling-as" --- > ## 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. # TMS 7.12 EDI 210 Billing/Payable Handling (AS) ## **Overview** For EDI information and setup, see the following documents: - EDI Setup and Processing Summary - EDI Locations Create the Billing record. Manually create Billing records from the Customer Quotes list view. Select the appropriate Customer Quote records and click the **Create Billing** button. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Customer Quote list view - 2.png) ### **Inbound EDI 210 Payable Logic** The TMS attempts to create a new or update an existing Payables based on the following logic. EDI 210 transactions are received into the TMS. 1. 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. 2. 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. 3. If multiple Loads are matched, an Unmatched EDI Transaction record is created. 4. 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**. 5. The Payable matches to a single Load unless no matches or multiple matches are found. In the event of multiple or no matches, an Unmatched EDI Transaction record is created. 6. 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**. 7. If multiple Loads or no Loads are matched on this search, an Unmatched EDI record is created. 8. Any searches that result in no matches result in an email sent to the EDI Administrator by the EDI batch job error email. When a transaction is successfully matched to a Load, the TMS compares all Payable records for the Load to determine if the EDI 210 transaction matches to a Payable. - If the Payable is in a *Pending* status, it is updated with the data from the EDI 210. - If the Payable is NOT in a *Pending* status, the Payable is NOT updated with the data from the EDI 210. A failed EDI 210 transaction is logged. - If no Payable is matched, a new Payable is created. If no match is found the EDI Administrator receives an EDI batch job error email. ## Single Billing EDI Send ### **Outbound EDI 210** The following fields from the Customer Quote/Billing records are generated for the outbound EDI 210. An EDI 210 transaction can be initiated from the Billing record page layout. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Send via EDI.png) Click the **Send via EDI** button.