How mileage interfaces affect billing
How mileage interfaces affect billing
It is very common to apply billing rates based on the mileage for an order. Such a rate can:
Have a charge type that is based on $/mile.
-and/or-
Have a rate table that is based on mileage ranges.
In many cases, billed miles are determined by miles calculated by a third-party mileage application to which TMWSuite has an interface. To find the mileage between two locations, TMWSuite first looks to its own mileage table. If it cannot find the mileage there, the system tries to find a match in a third-party mileage database. If the mileage is found, it is stored in TMWSuite's own mileage database for future reference.
TMWSuite places mileage figures in separate mileage buckets based on the type of interface used. For example, when looking up ALK Shortest miles, the system saves the mileage amounts to the “ALK Shortest bucket.” Similarly, for lookups of ALK Practical miles, the system places the mileage amounts in the “ALK Practical bucket.” During the rating process, these mileages subsequently can be adjusted for specific rating scenarios.
You must configure the system to use miles from the correct mileage interface when orders are rated. It is common to use multiple mileage interfaces for billing purposes.
The following topics describe how to:
Specify the mileage interface to be used when the system calculates an order's billing miles.
Configure the system to bill based on adjusted mileage amounts, when necessary.