--- title: "ePayments" slug: "epayments" tags: ["EFS MoneyCodes", "Comdata Comcheks", "Admin", "ePayments", "Expanded Content"] updated: 2026-06-09T16:40:13Z published: 2026-06-09T16:40:13Z canonical: "documents.revenova.com/epayments" excludeFromExternalSearch: true --- > ## 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. # ePayments > [!WARNING] > **Why is this the Comdata Comcheks ‘Pre-Production’ for the Spring ‘25 Release? (This issue does not apply to previous TMS releases.)** > > The Revenova QA department executes quality assurance test cases for all product enhancements to validate the new functionality is performing as expected and to fix any bugs that may have been introduced during development. While the specific Revenova-built user interface components and API connections used in this integration have successfully passed our QA test cycle, we experienced intermittent connectivity issues from the Comdata testing environment resulting in unpredictable error responses from their API. Because we have not been given a Comdata production environment for testing, **we cannot guarantee that these same connectivity issues will not arise for customers in production**. As a result, we are classifying this integration as a Pre-Production version in our Spring ‘25 release. > > > > **What does that mean for customers who want to use this integration?** > > This integration can be considered production-ready, as the Revenova-built features have been fully tested and validated. However, customers wanting to take advantage of the integration should contact their Revenova representative to assist with sandbox testing and communicate errors to the Revenova Product Team prior to activating in their production environment. When activating the integration in your production environment, the first few days of usage should be considered under “critical care”. Additionally, there should be a contingency plan for not leveraging this integration (using the Comdata online portal for example), should the connectivity issues encountered during QA testing also manifest in production. ## **ePayments** The ePayments Lightning Web Component (LWC) is found on the Load page layout by default. The ePayment Administration LWC is found on the **TMS Admin** page. To use ePayments, first navigate to **TMS Admin** and select the **EPayment Administration** link. EFS and Comdata are the two supported ePayment formats in the TMS. This LWC also allows for managing Fuel Cards with both the [EFS](/v1/docs/efs) and Comdata integrations. See the [Fuel Card Authority](/v1/docs/epayments#fuel-card-authority) tab for specific functionality. > [!WARNING] > Initial ePayment Configuration > > Enable ePayments from **TMS Admin** and then selecting the **Credentials** link then choosing the **Global Services tab**. Find the link for EFS and confirm that the **Enabled** and **Money Codes** boxes are checked. If using Comdata, complete the same steps from the Comdata link and check **Enabled**. > > When first configuring ePayments: > > 1. Begin with the Settings tab, > 2. then the Transaction Types tab, > 3. then the Users tab. > > There will likely be no data in the Users and Transaction Types tabs. As shown in the screenshot, multiple money code credentials are supported by the TMS. > [!NOTE] > At least one active EFS credentials with the Money Codes option selected, OR an active Comdata credentials is required to configure users for EPayments. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EFS - Credentials - 1.png) Create credentials cards for each EFS Money Code and/or Fuel Card account. 1. Click the plus icon to add another card. 2. *Check* the box if the account uses Money Codes. 3. *Check* the box if the account uses Fuel Cards. An account may have both *Checked*. 4. After entering account information, click **Save**. > [!NOTE] > **Note**: ePayment recipients do not receive an email notification with transaction details. ### **Settings** The Settings tab provides the ability to configure how EPayments operate in the TMS. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Settings - 1.png) #### **Vendor Account Record Mappings** From the **Settings** tab, find Vendor Account Record Mappings and select either *Vendor Invoices/Credit Memos* or *Vendor Payments* from the **Accounting Configuration** picklist. Select *Vendor Invoices/Credit Memos* to create Vendor Invoices and Credit Memos when an ePayment is issued. To create Vendor invoices an EFS or Comdata Vendor account mapping is required. Search for the appropriate account in the text boxes below the Accounting Configuration picklist. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Settings - 2.png) > [!NOTE] > EFS/Comdata Vendor Account Creation > > Create EFS and/or Comdata accounts before configuring ePayment settings. Select *Vendor Payments* from the **Accounting Configuration** picklist removes the EFS and Comdata field lookups. When *Vendor Payments* is selected, a Vendor Payment record is created when an ePayment is issued. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Settings - 3.png) #### Accessorial Record Mappings Next, search in the text boxes for the **ePayment Amount**, **ePayment Charge**, and **ePayment Fee** to map these fields to the an accessorial record. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Accessorial%20Record%20Mappings.png) > [!NOTE] > Accounting Configuration > > Vendor Payments default for TMS Accounting with the Amount, Charge, and Fee fields mapped to accessorial records for Vendor invoices. #### **Fleet Management** If using the Fleet Management component of the TMS, select a **Driver Default EPayment Funding Source** from the picklist. Options include: 1. None 2. Country ISO Code 3. Activation Status 4. CDL Country 5. Confirmation Method 6. Current Duty Status 7. Cycle Override 8. Drivers License Country 9. ELD Brand 10. ELD Day Start Hour 11. Emergency Contact Relationship 12. Employment Status 13. Jurisdiction Override 14. Rest Break Override 15. Restart Override 16. Status 17. Termination Reason 18. Timezone 19. Type 20. CDL State/Province 21. Drivers License State/Province ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Fleet%20Management.png) Click the **Save** button in the upper-right corner. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Settings - 4.png) ### Transaction Types ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Transaction Types - 1.png) Several transaction types are created on the **Transaction Types** tab for to users to create ePayments. To create a Transaction Type: 1. Click **New** 2. Enter a descriptive name for the transaction type - Each Transaction type must have a unique name. 3. From the picklists, select: - Credit/Deduction Amount Default - Credit Memo Amount Default - Fee Type - Charge Type - Currency The **Credit/Deduction Amount Default** defines the credit memos that are created for Vendor invoices when an ePayment is issued. Options include: 1. Amount and Payment Fee 2. Amount Only 3. Payment Fee Only 4. None The **Credit Memo Amount Default** determines whether a user can change the Credit/Deduction Amount setting when issuing an ePayment. Options include: 1. Read-Only (cannot change the setting). 2. Edit (can change the setting). The **Fee Type** is the type of data to enter into the Fees and Charges table for each Transaction Type. Options include: 1. Amount 2. Percentage The **Charge Type** is the type of data to enter into the Fees and Charges table for each Transaction Type. Options include: 1. Amount 2. Percentage For multi-currency orgs, the **Currency** type is a selection that applies to the Charges and Fees for the Transaction Type and for Users. > [!WARNING] > Currency Type Selection > > EFS accepts USD and CAD. Comdata only accepts USD. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Transaction%20Types%20Settings(1).png) The **Fees and Charges** section contains fields for the From and To Payment Amounts, Fee (Amount), and Charge (Amount). The down-arrow button to the right of the Fee Amount contains the *Delete* action to remove a Fee or Charge. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Transaction%20Types%20-%20Fees%20and%20Charges.png) The Fees and Charges table defines the fee and charge values based on the amount of the ePayment. *Prevent gaps when calculating fees and charges.* - The **To Amount** of a record should match the **From Amount** on the following record. - Charges are calculated when the ePayment amount is greater than or equal to the **From Payment Amount** (>=) and less than the **To Payment Amount** (<). See the table below for an example. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Transaction%20Types%20-%20Fees%20and%20Charges%20-%20Table.png) The blue **+** button adds more rows to the Fees and Charges table, as necessary. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Transaction%20Types%20-%20Fees%20and%20Charges%20-%20Table%20Add(1).png) At least one row of Fees and Charges is required for each Transaction Type. Click the **Save** button in the upper-right corner when finished. New **Transaction Types** appear in the list. The **Action** drop-down button contains: - Edit - Clone - Delete the Transaction Type ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Transaction Types - 2.png) ### Advance Payment Authority The list of authorized ePayment users is available with a search for created/authorized users to issue ePayments. To add authorized users, choose the **New** button to the right of the authorized user search box. Choosing **New** displays a search bar in the User Settings section. The field data for existing users is editable by clicking the name link. > [!WARNING] > **Caution**: The TMS supports **one** Advance Payment Authority record per user. If the ePayment **Issue** button does not display for a user, confirm that only one Advance Payment Authority record exists for that user. If a User has more than one Advance Payment Authority record, an error message is displayed about the **Issue** button being unavailable and to contact the system administrator. To view Advance Payment Authority records, add the object to a tab in the org. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Advance Payment Authority - 3.png) The **Action** drop-down button contains: - Edit - Clone - Delete the Transaction Type for the Authorized user entry. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Advance Payment Authority - 2.png) Add all users with the ability to issue ePayments. Enter the user's name in the User text box and select it from the auto-complete list. Optional limits for the **daily monetary amount** and the **per day maximum number** of ePayments is entered when the user is selected. Required fields include: - Per Load Max (%) - Per Load Max Amount - currency type (multi-currency orgs) - Issue Authority Selections for the **Issue Authority** include: 1. Assigned Carrier Only 2. Any Authorized Vendor 3. Assigned Driver Only The Issue Authority validates when an ePayment is issued. Comdata, EFS, or both must be checked. The default source must be selected as either Comdata or EFS. The transaction type of Fuel, Lumper, and/or Other must be selected. Check the **Recipient Required** box for users that must enter a contact for a contact receiving an ePayment. Finish configuring the user ePayment limit settings and click the **Save** button. The TMS supports creating multiple EFS accounts. Once created, Funding Sources options are available in the User Settings. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20Admin%20User%20Settings%20-%20Updated%20Screenshot.jpg) > [!NOTE] > **ePayment Limits** > > Limits for ePayments are validated in a cascading order beginning with: > > 1. Per Day Max Amount, > 2. Per Day (#), > 3. Minimum of the Per Load Max (%), > 4. Per Load Max Amount. > > If there are no values for Per Day Max Amount and Per Day (#), those fields are not considered. #### Issuing Payments from a Load Authorized users can issue ePayments from the Load record on the **EPayments** tab. (TMS default, organization configuration may be different). Click the **New** button to create the ePayment record. Select the ePayment from the list to display the details of that particular ePayment. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20on%20Load%20-%20New%20red(1).png) The user's default **Funding Source** displays when creating a new ePayment. **EFS Money Code** ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20Money%20Code%20-%20Updated%20Screenshot.jpg) **Comdata Comchek** ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20Comchek%20-%20Updated%20Screenshot.jpg) > [!WARNING] > In the Salesforce mobile app, the EPayment LWC can create new ePayments. The funding source for the ePayment defaults to the user, and not the Load. Creating ePayments from the Salesforce mobile app does not provide default Load fields. Enter the required information for either the EFS Money Code or the Comdata Comchek. From the the EPayments tab on the load, that load number pre-populates on the ePayment. The available selections for the **Transaction Type** are those created from the Transaction Type tab. Multi-currency orgs are able to select the appropriate currency. Enter a monetary **Amount**. When the **Transaction Type** and **Amount** are entered, the fee displays to the right of the **Amount**. Search for the Vendor account (usually the Carrier on the load). > [!CAUTION] > - Users may receive a ‘*No rows for assignment to SObject*’ error when issuing a Comdata Comchek. If this occurs, check the Sharing Rules for the TMS Type. Set the **TMS Type** for the Comdata account to *Factoring Company*. > - Users may receive a ‘*There was an error issuing this Comchek - (rtms)*’ error when issuing a Comdata Comchek. Comdata does not recognize *First* or *Last Names* fields containing 3 or fewer characters. Add characters to either the *First* or *Last Name* to correct this error. The Load Contact picklist options includes the following options. 1. Driver 2. Tender Contact 3. Other Search for the Recipient (usually the Driver on the load). When selected, the email address displays to the right of the text box. Add an optional description. The **Funding Source** is the default from the user's Issue Authority record. Users that do not have the **Recipient Required** field checked may issue ePayments without a recipient. While the ePayment is in a Pending status fields may be edited. When complete, choose one of the following actions. 1. **Issue** to send the funds and create the ePayment record. 2. **Cancel** to exit the record. 3. **Save** to create the record without issuing the funds. > [!NOTE] > **EPayment Authorized Field** > > Before an ePayment can be issued to an account, the **EPayment Authorized** picklist field must be enabled with either EFS Money Code or Comdata Comchek selected on the Transportation Profile record. Click **Edit** in the top-right corner of the page to open the ePayment record with all fields in read-only mode. Pending ePayments are still editable. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment%20LWC%20-%20Edit%20EPayment%20Red.png) Actions available on an issued EPayment: 1. **Stop** (Cancel for EFS) 2. **Freeze** (Cancel for Comdata) Example of an Issued Money Code: ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Issued%20Epayment.png) ### Fuel Cards Manage [EFS](/v1/docs/efs) and [Comdata](/v1/docs/comdata-fuel-cards) Fuel Cards and permissions from the Fuel Card Authority tab. > [!NOTE] > The Comdata Fuel Card integration is primarily for use with the [Fleet Management](/v1/docs/fleet-management-2) module. ### Fuel Card Authority Some functionality is only available depending on whether Comdata [credentials](/v1/docs/credentials-1) are enabled. See additional setup information [here](/v1/docs/comdata-fuel-cards). ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EPayment Admin - Fuel Card Authority - 1(1).png) 1. The Comdata Utilities bar contains buttons to complete 3 separate functions. 1. This utilities bar is only visible when Comdata credentials are enabled. 2. The **Secure Card Number Search** button opens a modal to search for a Fuel Card by Card Number. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Secure Card Number Search - 1.png) 1. Enter the Fuel Card number and click the **Search** button to find the Fuel Card record. > [!WARNING] > Comdata Fuel Card Numbers are *NOT* stored in the TMS. To find a Fuel Card, use the **Secure Number Search** modal and enter the Card number provided by Comdata. When a Fuel Card is activated, the **Masked Card Number** field is saved on the Fuel Card record and the last 4 digits of the Card Number may be used in the global search to find the Fuel Card. 3. The **Employee Number Search** button opens a modal to search for Fuel cards by Employee Number. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Employee Number Search - 1.png) 1. Enter the Employee Number and click the Search button to find the Fuel Card record. 4. The **Fuel Card Manager** button opens the Fuel Card Manager modal. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Fuel Card Manager - 1.png) 1. Select the tab for each respecting action. 1. Issue Funds: Search for the Fuel Card, enter an Amount, and add an internal Reference Number for record keeping. Click **Issue Funds** to add funds to the card. 2. Issue One-Time Limit: Search for the Fuel Card, enter an amount, and select the limit is a Cash or Fuel type. Click **Issue One-Time Limit** to add the limit to the card. 1. One-Time Limits can not be a negative value. Issuing a limit with a negative value causes an error. > [!WARNING] > Users attempting to issue funds or a one-time limit to a Comdata Fuel Card without the proper permission receive errors. - Users that do not have the Add Funds permission receive a “The number is too high” error. - Users that do not have the Subtract Funds permission receive a “The number is too low” error. 5. Click the **All** button to *Check* each of the Fuel Card action boxes. 6. The **Control Limits** box is only available when [Comdata](/v1/docs/comdata-fuel-cards) credentials are enabled and the Fuel Card box is *Checked*. 7. Select the User(s) to apply Fuel Card permission(s) by *Checking* the box to the left of the User name. Individual permissions may be added or removed as follows. 1. Activate Card 2. Deactivate Card 3. Place Hold 4. Delete Card 5. Add Funds 6. Subtract Funds 7. Control Limits (Comdata only) 8. Set/Reset PIN 8. Click the **Apply** button when the correct permissions are selected for the User(s). 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.