Faring System Properties

Review and set faring system properties after fare types have been defined in ancillary data.

Use Faring properties to view or determine the default for fares charged for bookings, no-shows, and cancellations; to activate prepaid faring deductions; and to set overdraft limits.

System properties that affect faring are found in Tools > System Properties, on the Profile tab.

Table 1. Faring System Property Descriptions
System Property Description
Faring > Always deduct penalty when cancel Specifies whether a fare credit should be issued for canceled trips.

If set to Yes, trip cancellations and no-shows will always result in a fare credit to the client’s account.

If set to No, a fare credit less any penalty when a trip is canceled is applied only if the client is set up for Allow Prepayment or Prepayment Required and the Enable Prepaid Faring Deductions property is set to Yes.

By default, this property is set to Yes even though the expected usage for new customers is No.

Faring > Confirm Account Balance on New Booking If set to Yes, a dialog box showing the status of a client’s account is launched when saving a new booking.
Faring > Currency decimal Number of decimal places to be used for fare calculations.

For example, 2 calculates the fare as $1.75, and 4 calculates the fare as $1.7473.

Faring > Deduct Full Fare Only Specifies whether only the full fare can be deducted.

If set to No and the fare is more than the available amount, the available amount will be deducted and any owed fare will go to collection.

If set to Yes and the fare is more than the available amount, no money will be deducted and the full fare amount will go to collection.

The default setting is No.

Faring > Default Client Prepayment Type Specifies the default prepayment type for new client records: Allow Prepayment, Prepayment Required, or Prepayment Not Allowed.

The default setting is Allow Prepayment.

Faring > Default Fare Type Fare type to be selected as the default.

The client’s fare type overrides the default but if the client is not assigned any fare type in the client record, the default is used.

Fare types must be defined before you can set a default fare type.

Faring > Default Over Draft Limit Default amount (in dollars) that a client account is allowed to be overdrawn.

Once an account has exceeded this amount, a warning message is generated to alert you to the account status.

Faring > Default Payment Type Payment type to be automatically selected when no payment type is specified at the funding source or trip booking level.
Faring > Disable Fare Collection If set to Yes, the client is charged for the booking and the fare amount is collected from the client account.

Any client overdraft limits are ignored so that the trip is always charged from the client account.

Faring > Direct Distance calc. method Method that the site uses to calculate distances.

If you are using faring by distance, you must choose one option (point-to-point, triangulation, barriers, or street routing) in order for the system to calculate the fare by measuring distance traveled.

Triangulation is the method most often used.

Faring > Distance Unit Unit of measure the site uses to show and calculate faring by distance (for example, miles, kilometers).
Faring > Enable Prepaid Faring Deductions Specifies whether to automatically deduct the fare from a client account whenever a trip is booked for the client.

If set to No, the system will not automatically deduct the fare but deposits can be made to a client account.

Faring > Fares use clients numPU This property is useful for sites that want the ability to use the number of spaces as a proxy for the number of passengers boarding.

If set to Yes, the total fares are based on the passenger fare multiplied by the number of pick-up spaces typed in Trip Booking.

Faring > FareType if no solutions Used for interface fare calculations.

If the external trip planning solution does not find solutions, PASS uses the fare type specified here for bookings.

The fare types listed in the list are defined in Fare Types ancillary data.

Faring > Interface > Apply Lowest Fare Used for interface fares.

Selecting this option applies the lowest available fare that falls within the criteria specified by the Faring/Interface settings.

Faring > Interface > Time Increment Used for interface fares.

Specifies the frequency the system should check for updated fares.

The default setting is 60 seconds.

Faring > Interface > Time Offset Used for interface fares.

The amount of time between possible start times for a trip when multiple fare cost options are requested from third party providers.

The default setting is -15 minutes.

Faring > Interface > Time Window Used for interface fares.

The maximum amount of time a trip can start before the client’s requested time.

The default setting is 30 minutes.

Faring > Max Amount for FareCollected Specifies the maximum amount (0 to 9999.99) for FareCollected.

Users cannot set FareCollected above the defined amount, unless they are granted the security permission Trapeze4 > Faring > Override Maximum FareCollected Amount.

The default setting is 20.00.

A Tracker Action (PASS/FareCollected) can be defined to log instances where the maximum amount for FareCollected is exceeded.

Faring > Method for Poly Fare Distance Specifies the calculation method to be used when calculating the distance for a trip: Straight, Barrier, or Street Routing.
Faring > Multiple factor for interface type Used for interface fare calculation to specify the multiple factor, which limits interface fare calculation.

The default value is 2. If the fare that ATIS calculates, when multiplied by this factor, exceeds the value specified in the Max. Fare field in the interface fare type, the Max. Fare amount is used for the trip. If the result of the multiplication is less than or equal to the Max. Fare value, that fare is used for the trip.

Faring > NoShow Fares Are Zero If set to Yes, the Fare Amount, Fare Deducted, Fare To Collect, and Fare Collected fields in the Set Time dialog box are set to zero when a user marks a trip as a no-show using any no-show code including Cancel at Door. If the no-show is recorded using the Schedule Editor screen, the Fare Collected field in the Set Time dialog box cannot be edited unless the user is granted permission using the Trapeze4 > Schedule Editor > Edit No Show Fare Collected permission key.
Faring > Polygon type for Crosscheck
Faring > Prepayment Override increases Fare To Collect Clients that have a balance that exceeds the overdraft limit, cannot take their trips. If a supervisor override is allowed, you are prompted to type it. When an overdraft is authorized and this property is set to No (default), the fare amount to collect does not increase. If this property is set to Yes, the overdraft limit is honored and the balance is added to FareToCollect.
Faring > Stop Activation Specifies when prepaid faring subscription trips are activated based on a client’s account status:
No
Activate a client’s subscription trip regardless of account status.
At Zero Balance
Stop activating a client’s subscription trip when the client account’s reaches a balance of zero.
At Overdraft Limit
Stop activating subscription trips when the client account reaches the specified overdraft limit.
Faring > Time Unit Unit of measure for fares calculated by time (hour, minute, or second). For example, if Hour is selected, the Fare Types dialog box allows you to charge a fare for every hour that elapses on a trip.
Faring > Using Fund Source Polygon Specifies whether to prompt for the use of funding source polygons to calculate faring.