The report includes:

• Deposit date and time
• User’s shift location and shift ID
• Username and display name of the user who created the deposits
• User external ID
  
  Filters available: region, date & time range, shift location, and username. This report helps operators reconcile daily deposits and integrate seamlessly with external systems.
  
  You can view the following documentation Shift.

Key capabilities include:

• Manage and organize the 5-day forecast according to this grouping of labels.
  This feature allows you to view informational labels more quickly in the 5-day outlook.
  
  You can view the following documentation Labels.

Key capabilities include:

• Manage and organize schedules with labels.
  This feature allows you to view information labels more quickly in schedules and 5-day outlook.
  
  You can view the following documentation Schedules.

Key capabilities include:

• Apply rules based on the full journey (origin ➝ final destination), with support for connected trips.
• Flexible configuration options:

  Stations All stations
  All stations
  Specific station(s)
  Ability to tie to specific schedules.
  
  This feature allows operators to efficiently scale O&D restrictions across large station networks without managing route-by-route or schedule-by-schedule setups.
  
  You can view the following documentation Paid In Item.

Use Case: Operators and drivers may need to view their upcoming or past trips in different orders depending on operational workflows. For example, viewing the most recent trips first can be useful during end-of-day reviews, while the default earliest-first helps with planning the upcoming schedule.

Configuration: No configuration required. Available by default in the latest version of the driver app.

Make sure to update to the latest driver app to see the latest features.

You can view the following documentation Scanner App.

Two key updates have been made to the Pay Later configuration:

New Setting – Expiration Time Prior to Trip Departure
A new time-based parameter allows you to expire Pay Later reservations X minutes or hours before departure, whichever is earlier between this setting and the existing Maximum Waiting Time. This helps automatically free up held seats if payment is not initiated in time.

Updated Setting Language – Wait Time Departure Offset

New Name: Wait Time Departure Offset
New Tooltip: To permit payment processing to continue past the departure time of a trip, this setting allows the 'waiting for payment' status to extend beyond departure by the offset time specified.

These updates provide greater flexibility and automation in managing seat holds and payments near departure times.

Also updated:

• "Departure Offset" renamed to "Wait time departure offset"
• Tooltip updated for clarity.
  
  You can view the following documentation Payment Providers.

Use Case: Bulk Move now supports seat reassignment based on leg-to-leg availability.
If two passengers are booked on the same seat but for non-overlapping segments (e.g., A > C and C > D on Seat 17), the system will now recognize that both can occupy the same seat without conflict. This enhancement ensures that fully booked trips can be moved efficiently without unnecessary seat rejections.

You can view the following documentation Move.

Use Case: Displaying “Created by” and “Updated by” on the item details page When viewing the details page for an item, users should be able to see who created the item and who last updated it. This improvement increases traceability, allowing users to quickly identify the origin and most recent changes to an item, which facilitates audits and tracking of modifications.

You can view the following documentation Paid In Item.

Use Case:
Allows bulk move of tickets in "Waiting for Payment" status. Prevents the error: “Ticket cannot be moved because it has not been paid.” The ticket’s payment status stays unchanged and can still be completed later

Configuration:
Admin > Sales & Inventory > Operation Settings

You can view the following documentation Move.

Key capabilities include:

• Manage and organize payment on account records in a CSV file.
  This feature allows you to download payment records to a CSV file and then view the information configured in each of them within the system.
  
  You can view the following documentation Payment Providers.

Access via **Intelligence > Transactions.**
Apply filters, download CSV, and review all flexpass activity. Permissions must be enabled.

• Usage Deduction: Redeeming a round trip subtracts 2 uses from the flexpass.
• Validation: The system will prevent selecting a return trip if the flexpass has insufficient remaining uses.
• Implementation: Redemption occurs in a single flow, with safeguards to handle partial failures and ensure no uses are deducted if the process fails.
• Scope: Controlled via a feature flag for safe rollout.
  This improvement simplifies round-trip redemptions and ensures proper usage tracking for flexpasses.

Use Case: An operator sells a 10-use Flex Pass for 1,000 MXN.
Revenue is initially assigned to Operating Company A.

Over time:

• 5 uses are redeemed with services operated by Operating Company B → 5 uses × 100 MXN = 500 MXN goes to OpCo B.
• 3 uses are redeemed with services by Operating Company C → 3 uses × 100 MXN = 300 MXN goes to OpCo C.
• 2 uses remain unused upon expiry. The remaining 200 MXN can be allocated to OpCo A, B, or C, depending on policy.
  
  Operational Control Rules:
• The assigned OpCo is configured in Admin > Operating Companies.
• The assigned OpCo for the Flex Pass:
• Does not need to follow the usual Amenity Group / Brand restrictions, even when the system is configured to enforce OpCo/Amenity Group/Brand mapping.
• Acts as the initial revenue holder when the Flex Pass is sold.
• Revenue distribution occurs dynamically based on:
• The actual usage of the Flex Pass by the customer.
• Any unused uses remaining upon expiry.

• Purpose: Simplifies the sales process by pre-selecting commonly added items.
• Behavior: Passengers or agents can deselect the item if they do not wish to include it.
  This enhancement improves efficiency while maintaining flexibility for customer preferences.
  
  You can view the following documentation Paid-In Items.

• Column Placement: Appears to the right of the existing “Shift Location” column.
• Filter Update: A new dropdown filter for Operating Company is now available, positioned below the “Manifest Date From/To” filters, defaulting to “All.
  This enhancement allows users to easily view and filter items by the assigned operating company.
  
  You can view the following documentation Operating Companies.

• Purpose: Simplifies the sales process by pre-selecting commonly added items.
• Behavior: Passengers or agents can deselect the item if they do not wish to include it.
  This enhancement improves efficiency while maintaining flexibility for customer preferences.
  
  You can view the following documentation Paid-In Items.

• Purpose: Ensures that cash collected from bundle sales is properly allocated to the correct bank for deposits during shift close.
• Impact: Improves accuracy of revenue tracking and deposit reporting for bundle sales. This change ensures redeemable items carry the necessary company information for proper financial reporting and deposit allocation.
  
  You can view the following documentation Bundle Redeemable Item.

• Configurable Limit: Administrators can define the maximum tickets per manifest for each promotion within the Promotions module.
• Sales Enforcement: During ticket sales, the promotion applies only to the allowed number of tickets. Any additional tickets show a message indicating the promotion limit has been reached.
• Usage Tracking: Promotion uses are tracked across sales, cancellations, and ticket changes, ensuring correct application and accounting.
• Reporting: Transaction, ticket, and promotion reports reflect applied promotions and limits.
  
  This enhancement ensures controlled promotion application, preventing overuse while providing flexibility for demand generation campaigns.

Future Limit: Prevents moving a passenger too far into the future beyond their original trip time. Past Limit: Prevents moving a passenger too far back in time before their original trip time.
These configurations ensure that when a passenger is moved, the new trip must fall within a defined time window relative to the original departure, improving control and preventing invalid movements.

You can view the following documentation Move.

Use Case: A user responsible for dispatch or manifest adjustments may need to perform operational tasks across multiple stations. Instead of requiring them to open a shift per station, the system should validate their access based on the assigned shift locations, not the opened shifts. They should be able to dispatch or edit manifests that originate from any of those stations, without opening a shift.

Operational Control Rules:
An open shift is not required to perform manifest actions.
The user must have the origin station of the manifest assigned under their Shift Locations (in Admin > Users > Shift Locations).
The system must not require the user to have an open shift at that station to execute these operations.

The following actions are allowed under this control:

• Dispatch manifest
• Change manifest status
• Change bus assignment
• Change capacity
• Bulk move passengers
  
  You can view the following documentation Manifest.

Use Case: The new busbud_online payment method can be refunded from Busbud, and to avoid confusion, no Betterez emails should be sent when processing refunds for busbud_online.

Configuration:

• In admin/payments, add the ability to configure each payment method so the "Email refund receipts automatically" setting does not trigger.
• Under Options for each payment method, include a new checkbox config: "Prevent automatic emails for refund receipts".
• Leave the existing Busbud payment unchanged.
• Add the new busbud_online payment method and enable the correct Busbud agency (CAD, MXN).
• Ensure refund emails are set to "never" for busbud_online.
  / / Betterez Support Article

Fare Type Availability: The fare type of the original ticket is no longer validated against availability on the new manifest.
Fare Type Limits: Passengers can be moved even if the target manifest has fare type restrictions or has already reached its limit for that fare type.
Previous Issue: Previously, tickets with certain fare types could not be moved to schedules that were restricted or sold out for that fare type. This behavior has been corrected so that movements are now allowed regardless of fare type restrictions.

Betterez Support Article

Use Case: Operators can have drivers sell additional services at bus side, items that may not have been declared or booked at the time of the ticket sale. For example: extra baggage, blankets, bringing a pet carrier on board.

Configuration: Administration -> Scanning, go to "Scanner app sales" subheading

Make sure to update to the latest driver app to see the latest features.

Use Case: Drivers are able to see both the scheduled arrival and departure times for their trip

Make sure to update to the latest driver app to see the latest features.

A manifest with "Operations" status is not sellable in any channel, and can not have passengers moved to the trip (similar to "cancelled" status). The manifest cannot be set to "Operation" status if there are passengers booked on this manifest.

Use Case: Operators who need to move vehicles from one location to another, for logistical planning rather than passenger transport.

Betterez Support Article

Driver Assignment:

• Support multiple drivers per manifest, assigned by origin–destination.
• Validations prevent overlaps, enforce rest times, and check O&D continuity (warnings with bypass options).
• Driver O&D now appears on manifest printouts.
  
  Vehicle Assignment:
• Prevents assigning vehicles to conflicting manifests.
• Enforces vehicle rest times.
  
  Conflict Prevention:
• Blocks driver/vehicle conflicts across manifests.
• Allows multiple drivers on the same trip segment if validations pass.
  
  These updates ensure safer scheduling, accurate tracking, and compliance with rest requirements.

Manifest List View:

• Shows all manifests.
• Non-dispatched = read-only.
• Dispatched = editable (Driver, Mileage, Vehicle).
  
  Filtering: By date, driver, company, vehicle, and dispatch status. Review & Finalize:
• Manifests must be marked Reviewed before export.
• Users select a date range, confirm, then finalize.
• Once finalized, manifests are locked and cannot be resent. Export: Finalized data triggers a webhook and CSV export to SAP.
  
  This ensures accurate payroll, one-time exports, and reliable SAP integration

When enabled, this setting requires that any schedule created or edited must have both a brand and an operating company assigned. This prevents issues where unassigned schedules block integration, such as with the Driver Runs report to SAP, ensuring smooth dispatching and reporting.

The format is as follows:

• First 2 digits: represent the Operating Company (OpCo) (e.g., 02 or 03).
• Next 10 digits: represent the consecutive folio number for tickets.
• IKEY: replaced with our system’s unique ID.
  Additionally, a numeric code for the OpCo will be available to feed through the webhook, allowing external systems to concatenate and process ticket numbers consistently.

Use Case: Ensure there are no omissions to schedule configurations for operating company and brand.

Configuration: Administration > Sales Inventory > Sales Operations, checkbox for Operating company mandatory for schedules and Brand selection mandatory for schedules

Use Case: Operators who prefer to follow their own ticket sequencing and format can opt to use this feature for continuity. Note that when this is enabled, all future tickets will start their numbering sequence and increase by 1 for each ticket issued in the system.

Configuration: Administration -> Sales Inventory -> Sales Operations, checkbox for Allow operating companies to configure their own ticket numbers. Once enabled go to Administration > Operating Companies, create an operating company and go to subheading "Sequences". Ensure all your schedules are assigned an operating company to use sequences correctly.

The system will automatically calculate commission amounts per transaction based on the assigned percentage or fixed value:

• Before taxes: Price before taxes and commissions
• After taxes: Final price with taxes and commissions
• Fixed amount: stored directly without applying a calculation.
  
  Commissions are stored in two new transaction fields and support multi-currency. Totals are also summed to calculate the commission earned per shift.

To ensure accuracy, times are shown according to the time zone of each station, rather than the account’s default time zone.\ This enhancement aligns the Driver App with the manifest display, giving drivers clear and reliable trip timing details across multiple time zone

Use Case: For operators who have configured open return tickets, allow your passengers to redeem the open return for a different origin and destination than was booked on the first leg. Ex: customer can book A -> D and then use the open return to redeem for a C -> B ticket. The value of the open return is paid against the cost of the return for whatever O&D.

Betterez Support Article

Contact support@betterez.com if you want this configured.

Betterez Support Article

Use Case: For trips with seatmaps that have multiple seat classes (ex: VIP seats, and standard seats), operators may want to only sell the "VIP" seats for longer distance trips only to maximize revenue. In this case, create two fare tables, one for VIP where O&D prices are set to only long distance combinations, and another fare table for standard seats with all O&D combinations. Passengers will not be able to book the VIP class seats for the short haul trips that were not priced in the VIP fare table.

Betterez Support Article

Configure your station longitude and latitude, with the ability to enter the google maps URL to pull the longitude and latitude automatically. These coordinates are then used to display the station location when looking at the back office routes and schedules.

Betterez Support Article

Use Case: For operators who run closer to commuter style services. Opt to enable standing passengers to sell additional tickets in excess of your seated capacity. This is only for back office sales channels, and in the trip results we display to capacities, one for seated and one for standing.

Configuration:...

Betterez Support Article

Configuration: Administration -> Product Lines, select the product and configure the days in advance sales setting for back office.

Use Case: …

Configuration:

Use Case: Customer may create multiple profiles over their purchase history. In Betterez you are able to select one profile as the parent, and merge all other profiles into the parent. All history and loyalty points are moved to the main parent profile.

Configuration: The setting is available in any customer details page, the button to “merge” will be at the top right. If this option is not available right now in your account, please reach out to support@betterez.com and request to enable the customer account merge feature.

Betterez Support Article

Use Case: Operators who want to allow drivers more autonomy where an incorrect ticket is scanned, the unredeem ticket option can be enabled in the scanning app.

Configuration: …

Make sure to update to the latest driver app to see the latest features.

Use Case: For operators who have drivers using the app over multiple days, our current settings will retain yesterday's date for the trips view. For operators who want to always default the trips view to today’s date, this configuration will ensure drivers are always looking at their current days trip.

Configuration: …

Make sure to update to the latest driver app to see the latest features.

Use Case: Drivers can now sell trips with seatmaps. The driver app will pull the latest pricing for the seat, including any seat fees when selling the ticket with the driver app.

Configuration: …

Make sure to update to the latest driver app to see the latest features.

Use Case: In each manifest details page, under “comments”, a note of the ticket number and movement is made. This applies to all tickets moved.

Use Case: Allow customers to obtain a voucher that is not limited to an origin and destination when redeeming the voucher.
Betterez Support Article

• Loyalty Points: Tax is applied only to the portion paid with cash/credit, not to the value covered by points.
• Promo Codes: Tax is calculated on the discounted total, not the original fare.
• Mixed Payments: In combined cases (promo code + loyalty points + cash/credit), taxes are applied only to the net payable amount after all discounts and points are applied.
  This ensures accurate tax handling aligned with Transpais’s requirements.

• Configuration: In Reservation Rules, one or multiple brands can be selected for when the fee applies.
• Rules Handling: Time-based rules and fare class rules do not apply to this fee type. These options are greyed out and display the message “Only available for…” for clarity.
• Application in Connection Trips: Each fee is applied only to the brand of the ticket it matches, ensuring accurate brand-based charges across all journey segments.

• Auto 1:1 Matching: Tickets are automatically reassigned if the section, row, seat number, and destination match between the current and target manifest.
• Activation: A new button allows users to trigger the auto-assign process.
• Conflict Handling: If a seat is already taken in the target manifest, the ticket is flagged in red for manual assignment.
  This enhancement speeds up the manifest move process and reduces manual work while preserving flexibility for conflict resolution.

• Previous behavior: Shifts could only be printed immediately after closing; once signed out, agents lost access unless given Shift Reports permission.
• New behavior: After closing a shift, the “My Shift” screen will display the user’s most recently closed shift, allowing them to reopen it for printing.
  This change supports 2-step shift closing process, enabling managers and agents to double-check and print shifts without requiring extra permissions.

• Ticket Sales: Tickets sold from tax-exempt schedules will not include any tax calculation.
• Manual Sales: The same behavior applies when selling tickets manually; totals from tax-exempt schedules remain tax-free.
• Connections: No impact on connections, as this configuration applies only to the individual schedule.
  This enhancement ensures accurate pricing and compliance for services that must operate without tax applied.

Key Capabilities:

• Unified Booking: Customers can book trips involving multiple interline partners in a single transaction with one payment.
• Mappings Configuration: Support for mapping fare types, stations, and terms of service across operators.
• Itinerary Display: Clearly shows interline partners, departure/travel times, and associated brands or operating companies for each leg.
• Pricing: One price applied across the full interline journey.
• User Management: Authorized users can change or cancel their interline journeys (ONTC rules apply).
• Languages: Full English and French support.
  This enhancement simplifies cross-partner travel by removing the need to manually add interline items to the cart, improving the booking and reporting process for both agencies and customers.

• Included in the transaction.completed webhook
• Displayed in the Paid Items Report (new “Operating Company” field)
  This applies to all paid-in items (e.g., cash deposits, cheque exchanges, internal allocations), ensuring accurate reporting and reconciliation.

• By default, filters in Intelligence Reports are hidden after applying.
• A new admin/setup flag allows users to choose whether filters remain visible or hidden after applying, enabling quicker subsequent report edits.

Now, system administrators can configure the maximum number of distinct departure and arrival time options available. This improvement ensures that if the fastest options are unavailable (e.g., sold out), additional trip alternatives can still be displayed to customers, making it easier for them to complete their purchase.

• Bank accounts can now be assigned to a specific shift location and operating company.
• During shift closeout, tickets sold are automatically linked to the assigned bank based on shift location and operating company.
• The deposit amount is automatically calculated based on the above assignment.
• Users are restricted from closing multiple shifts across different locations, ensuring accurate reporting.

• Agents will no longer see the exact expected cash amounts during a shift, protecting against bias in case of surplus or shortage.
• The top-right table now shows only surplus (negative) or shortage (positive) values.
• The bottom table, showing exact amounts, is available only via Shift Settings and intended for manager use, not agents.

• The email field is now optional, allowing vouchers to be created without requiring an email address.

• Users can now be assigned to a specific shift location.
• Once assigned, agents are locked to that shift location and cannot change it manually.

• Each ticket can now be changed a maximum of 4 times. This limit applies to both online changes and those made in the back office.

• When enabled, vouchers (whether created through refunds or manually in operations) can bypass Origin & Destination restrictions, even if those are set.
• This ensures flexibility while still allowing O&D details to be tracked for reporting purposes.

• Shortcode entry with Enter: Users can now type a station shortcode (e.g., VIC) and press Enter to auto-select the connected station.
• Auto field progression: Pressing Enter will automatically move the user to the next field (Origin > Destination > Departure Time).
• Improved dropdown filtering: Stations matching entered shortcodes are prioritized at the top of the dropdown list, ensuring quicker access.

• Seatmap identification: Female-only seats are clearly marked in the seatmap.
• Gender-based validation: During booking, only female passengers can be assigned to those designated seats.