TMWSuite 2021 release notes

and

You can set up Payment Terms as End of Month (EOM) plus a number of days. You do this setup in Dynamics GP. When you transferred invoices, the invoice due date was set to EOM. If you had set it up with the additional days, they were ignored.

You could not transfer Accounts Receivable or Accounts Payable records to Dynamics GP. The transfer produced "Account not found" errors. This happened if you used fewer than eight columns for your account segments setup.

When using incremental rate tables for Stop pay, the system was incorrectly counting the number of pickup stops. This caused it to select the wrong rate from the table.

Sometimes, the system did not allocate Percent of Revenue pay correctly for split trips. This happened when the rate used mileage-based allocation. The system did not use the correct mileage buckets.

When a minimum charge was applied by the primary rate, secondary percent of revenue rates were calculated incorrectly. The secondary rate was not including the minimum charge.

When a trip is billed incorrectly, the system lets you create a credit memo in the Invoicing application. The system can be set up to reverse the pay details associated with the invoice when the credit memo is saved. After the order is rebilled, you can recalculate the pay in the Trip Settlement Folder.

An error occurred when the system converted date/time data from a character string. This was caused by a rounding error. The error was linked to two settlement sheets and a stored procedure for paperwork tracking.

In the Company profile, the Shipper list and Consignee list was not being updated correctly.

The Shipper list and Consignee list records the shippers and consignees used by the selected company. The lists should be built dynamically as orders are completed.

If you used a custom layout in the Safety Report, the window would become read only. To use the window, you had to reset the layout to the default.

An error was occurring when you saved the batch import. This happened when you had an invoice number that exceeded eight characters in the Truck Stop Invoice No. column.

Now, up to 12 characters are allowed.

If your fuel vendor is COMDATA, a hard coded Bank Identification Number (BIN) prevented you from transferring ONROAD cards from one driver to another. The original driver remained on the card.

When transferring multicurrency invoices from TMWSuite to Dynamics GP, a rounding error caused amounts in the invoice balance to be off by a penny. This also showed in the Allocate Invoice window in TMWSuite.

You could not transfer Pay To profiles to Dynamics GP as vendors. The transfer failed if the Pay To profile’s PayTo Misc 4 field entry was greater than 21 characters.

TMWSuite’s Microsoft Dynamics GP integration lets you process cash receipts in the Invoicing application. When you do, cash receipt records are created in Dynamics GP. If you were also using Multi-Entity Management (MEM) for Dynamics GP, cash receipt records were not created. No message appeared stating that the process was not successful. This happened because the integration could not insert a NULL value in a field required by MEM.

Certain order-based notes entered in TMW Operations were not showing in TMWSuite’s Invoicing application. This was happening when the note’s text was entered in the TextLarge field.

An error message was displaying when you applied a filter in the Notes window in Settlements.

There was a performance issue when you saved new orders in Order Entry or Dispatch. The issue happened if you had [Misc]CopyCompanyNotestoOrder=Y in your TTS50.

A system error occurred when opening the Trip Folder. This happened when you had:

When you changed the stop on an order to a different company, an error would occur when saving the order. If you tried to open the same order in Order Entry an error message stated, "There are no commodity rows found."

Using [FuelServ]AlwaysChargeAdvanceToVendor=Y caused an error. The system sent two different Microsoft Dynamics GP vouchers to the vendor. One amount would also be out of balance.

Some EFS transactions had the tractor fuel amount missing from the distribution.

Processing fuel transactions to Microsoft Dynamics GP took a long time. This happened only in the 2018.4 version.

The system was allowing you to assign disabled invoice output configurations in the Distribution Method window. It should have only allowed you to assign configurations that had the Enabled check box selected in the Billing Output window.

The system was not setting the Pay Leg in the Invoice Details window.

Printing a rebill for a supplemental invoice was not producing the EDI 210 output.

You can specify unique reference number formats for Bill To companies.

Previously, you could save a format with a NULL value in the Attach To field. A NULL value in this field caused the system to skip the Reference number validation process.

Users could not open the Edit Billing Rate Schedule Folder when the RatewareXL General Info Table setting was turned on. It caused an application error.

The system was returning an error when the RatewareXL interface was active. The library path for Dispatch project needed to be updated.

Sometimes the system pulled the wrong fuel price rates. This happened only with rate tables containing a large number of rates.

You could not save a pay detail in the Advances/Misc Labor window without making an additional change to the pay detail. This was happening when the pay detail was based on a pay type that had a quantity greater than zero.

Users were able to Release trips in the Trips on Hold queue without recording the Carrier Invoice Number and Date. This did not affect the manual process of Releasing trips.