HubTran

  • Updated on Aug 21, 2025
  • Published on Oct 11, 2023
  • 7 minute(s) read
Prev Next

Setup

HubTran provides an AI-based vendor invoice parsing/reading capability that helps automate the quote/invoice reconciliation process.

HubTran provides “push” status updates to the TMS via a sites-based web service. Inbound load status packets from HubTran are processed by Platform Events.

The HubTranDataLoad batch process controls when load lane/revenue/cost information is sent to HubTran.

Enter Credentials

Enable the HubTran integration by completing the following steps:

  1. Navigate to TMS Admin.

  2. Select Credentials.

  3. Select the Global Services tab.

  4. Find HubTran in the list and open the card.

  5. Check the Enabled box.

  6. Enter the User ID, Password 1, and Password 2 into the text fields.

  7. Click the Save button when finished.

HubTran must provide login credentials to users to access their web portal. Users logged into this portal can review and approve invoices, and manage exceptions related to the auto-parsing of invoices.

Credentials can be group-specific. Set the HubTran Credentials Selector field to use group-based credentials and enter all the credentials from TMS Admin → Credentials.
See examples in the table below.

User ID

Password 1

Password 2

Customer Number

Revenova

Revenova

API Token (Looks like bf5f267000ae8e8e6pe0ef656746588x)

Do NOT enable the HubTran integration in both production and sandbox environments together. Disable HubTran credentials in the sandbox environment before using the integration in production. Identical Loads in production and any sandbox environments negatively impacts the data exchange between HubTran and the TMS.

Inbound Packet IP Ranges: Any load status post-backs from HubTran that do not originate from this IP mask are rejected as a security feature. Any changes to this range are provided by Revenova.

HubTran provides login credentials to users to access their web portal. From the portal, users review and approve invoices, and manage exceptions related to the auto-parsing of invoices and other documents.

Remote Site Settings

Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the HubTran integration URL are up to date.

  1. Click the Setup gear icon in the top right corner.

  2. From the drop-down, click Setup.

  3. In the Quick Find Toolbar type Remote Site Settings and click the link.

  4. From the list of remote sites find HubTran and click the Edit link.

  5. Update the Remote Site URL to match the Service URL below:

ServiceURL: https://api.hubtran.com

Test Service URL: https://api.hubtran.com

Partner Community Setup

The HubTran integration requires a webhook to send tracking information to the TMS. Create an API Site to accept inbound API traffic.

  1. Create a Salesforce Site for API Guest User Access.

  2. Set the public access for the Site.

  3. Activate and Publish the Site.

  4. Enter the API URL into the field for Inbound API Community URL under TMS Admin, in the Configuration section.

    1. Example: https://full-revesc1.cs64.force.com/api

  5. Add the following extension to the end of the URL to match the example below: /services/apexrest/rtms/tmslistener?org=[18-character org id]&source=HubTran&pwd=[credentials code field]

{API Community URL} /services/apexrest/rtms/tmslistener?org= {18-character org id} &source=HubTran&pwd= {credentials code field}

Example: https://revenova.my.site.com/API/services/apexrest/rtms/tmslistener?org= 00D180000008oA9EAI&source=HubTran&pwd=4wGFDgnT950Ovg1

The Salesforce-generated API Community URL is case sensitive.

Send the post-back URL/webhook, the company name, and contact information to support@triumphpay.freshdesk.com.

TMS Admin

Configuration

The following field may be set under TMS Admin → Configuration to use as the group-based credentials when using HubTran.

Confirm the boxes for HubTran and Remote Documents are Checked. When Checked, push events are processed as Platform Events by the TMS.

HubTran Credentials Selector: The picklist field on the Load object that determines which credentials to use.

Click the HubTran Data load button to pre-load Carriers and loads into HubTran. Only loads for participating Carriers are uploaded to HubTran. This button may be pressed multiple times.

Transportation Profile

Set the following fields for each Carrier on their Transportation Profile.

  • Vendor Invoice Processor: For all participating Carriers, set this value to HubTran.

  • Carrier Remit To: When this field is updated, the updated Carrier information is sent to HubTran.

  • Payment Processor: For all participating Carriers, set to TriumphPay.

To maximize the performance of HubTran, populate the SCAC, MC Number, US DOT Number, and Billing Address fields on all participating Carrier Transportation Profiles.

Confirm all Carriers have a contact email address. Incorrect or outdated email addresses causes significant impact to routing and parsing invoices.

The HubTran integration supports multiple stops for the same Account location.

Once invoices are approved in the HubTran web portal, the documents are sent to the TMS. Documents are attached to the appropriate Load record. Once documents are processed, the Carrier Quote Settlement Status field is set to Pending. Set to Approved for Payment.

The Settlement Status field may be set a number of ways.

  • Individually from each Carrier Quote record.

  • Selecting one to many for the Carrier Quote list view.

  • Creating flows or other automation to auto-approve each quote.

When the quote is Approved, an invoice is generated.

Load

Multiple fields that may be populated by HubTran.

  • Bill of Lading Number

  • Vendor Invoice Processor: Set this field to "HubTran." This field can also be set on Carrier Assignment.

Carrier Quote

Vendor quotes are not compatible with the Hubtran integration. Only Accepted Carrier Quotes for Loads are sent to Hubtran. Payloads that return from Hubtran only update the Accepted Carrier Quote for a Load.

Add the following fields to the Carrier Quote record page as Read-Only. HubTran populates these fields.

  • Vendor Invoice Number

  • Vender Settlement Total

  • Vendor Settlement Variance

  • Vendor Invoice Date

Add all Carrier contact emails and ensure they are up to date. The email used for Carrier documents that is sent to HubTran may cause issues in properly routing invoices to/from HubTran.

The Carrier Quote Reference field is sent to HubTran and is stored as the HubTran quote_number field.

  • Changes to the following Load fields automatically triggers field values to resend to HubTran.

    • Sales Status

    • Load Status

    • Weight

    • Distance

    • Customer & Carrier Quote Totals

    • Customer & Carrier Invoice Totals

  • "Flex" reference fields may be added to 2 field sets and passed to HubTran. Load TMS19 and Stop TMS2 field sets may be configured to control which fields are sent.

  • The Accounting Notes field on the Load Object is sent to HubTran.

  • The document "fingerprint" data for a load is maintained for 200 days to prevent duplicate documents saving to the load.

Customer Invoice Documents

It is possible that when using the HubTran integration that Customer Invoice documents are attached to the Load record. However, the Customer Invoice Documents Received checkbox is NOT checked.

Customer Invoice Documents actions may be configured using the related list on the Account page layout. This can prevent the Customer Invoice Documents checkbox field on the Load from populating during HubTran operation.

Review the customer Account page layout and search for the Customer Invoice Documents related list. If records are present in this list, there will be issues. Customer Invoice Documents should only be managed through TMS Admin, Customer Invoice Documents.

Document Processing

Freight Plans

A document is attached to both the Carrier Load and the Customer Load is the presence of zero-to-many related "shipments" associated with the document in the packet. The Carrier Load is the parent record when receiving packets from Hubtran. Within that parent record is an array of document objects. Within each document object is an array of shipments that correspond to the Customer Load(s) Id(s). Those links are made when the Carrier Loads are sent to HubTran. Any Customer Load that is moved by a Carrier Load is included in the shipments array sent with the Carrier Load transfer to Hubtran.

When viewing documents in the HubTran web portal, HubTran/TriumphPay does not allow attaching Delivery Receipt documents to a shipment. Delivery receipts are not customer-facing documents. This setting is a default, but may be changed by the customer in the TriumphPay visibility and required document settings.

  1. In the HubTran/TriumphPay Audit web web portal, navigate to Settings.

  2. Click Document Types.

  3. On the left side, set the value to Visible to Customer for the specific document, such as the Delivery Receipt.

Rerun Transactions

Rerun HubTran transactions that did not process successfully.

  1. Navigate to the Queued Transactions tab/object.

  2. Select the transactions that that did not process successfully or set the Status to Retry Failed or Failed.

  3. Set the transaction Status to Pending.

  4. Save the list.

Is the Customer Invoice Documents Received field populated when all document requirements from the Customer Invoice Document required object are present on the load?

The Customer Invoice Documents field on the Load object is a HubTran related enhancement that only responds properly if the documents are received through HubTran. When HubTran sends the Carrier invoice document with POD documents to Revenova, the TMS looks to see if all required POD documents were received. If all appropriate documents were received according to the customer's Customer Invoice Document Requirements setup, then checkbox on the Load is checked.

Troubleshooting

It is possible that a Carrier is not available in HubTran. From the Carrier Service record, the Carrier (Account) did not have a related Transportation Profile and the Transportation Profile did not have a related Account.

Issue

A Carrier is not in HubTran.

Resolution

The relationship between the Carrier Account and Transportation Profile is not setup properly. From the Carrier Service record, the Carrier (Account) does not have a related Transportation Profile. The Transportation Profile does not have a related Account.

  1. The Transportation Profile must be assigned to the Account referenced in the Carrier Service record.

    1. Use the Transportation Profile lookup field on the Account record.

  2. The Load Status may need to be changed from Delivered to Completed to update information in HubTran.