PTSS journey details will be submitted to DoT via:
- the PTSS mobile app; or
- dispatch equipment that your On-demand Booking Service (ODBS) has integrated with DoT systems, to automatically capture journey details.
DoT will validate all PTSS journeys and pay the subsidy and any co-payment amounts to the ODBS associated with the journey. Journeys that fail validation checks may need manual review by DoT staff – read Journey validation rules below for more information.
PTSS payments on behalf of drivers will be deposited in the bank account nominated by your ODBS.
Your ODBS will be able to view reports in DoTDirect that outline:
- the PTSS journeys included in the payment;
- the value of the subsidy for each PTSS journey; and
- the driver that completed that journey.
ODBSs are responsible for paying the correct amounts to their drivers. ODBSs and drivers will need to consider any financial arrangements regarding passing on subsidy payments – these are private commercial arrangements that DoT is unable to be involved with.
ODBSs are responsible for regularly:
- reconciling the financial payments provided by DoT and the subsidies provided to passengers for the bookings the ODBS has taken or facilitated; and
- reporting any discrepancies or issues to DoT as soon as possible.
Register for PTSS
To enable DoT to make payments on behalf of your drivers, your ODBS must register for PTSS via DoTDirect.
ODBS authorisation applicants will also be required to register for PTSS if they intend to provide taxi services once authorised.
During registration, you will need to nominate a bank account for DoT to deposit PTSS payments on behalf of your ODBS's drivers.
Ensure you enter the correct name associated with your bank account, for example "J Citizen", "John Citizen" or "J Citizen Pty Ltd". Account names like "Savings" or "Personal" may be rejected and lead to payment delays.
Once your ODBS has registered for PTSS, you will receive monthly emails requesting that you submit booking records for PTSS journeys that occurred in the previous month.
Visit PTSS responsibilities for ODBSs for more information about how to register for PTSS.
Journey validation rules
There are a range of checks applied to validate PTSS journeys. Any issues with journey details captured may result in an error or rejection of the journey.
At the time of the journey, the following details are checked:
- PTV, PTD and ODBS authorisations associated with the journey are valid;
- ODBS has an active PTSS registration;
- valid PTSS card number and expiry date; and
- driver and PTV associated with journey does not have other journeys with overlapping times.
Other issues may be flagged by the system, requiring DoT staff to manually review the journeys. Journeys will be manually reviewed if:
- the booking reference number is duplicated;
- the journey start time is after the journey end time;
- the journey is flagged as staged travel;
- they do not occur in a valid region, i.e. outside of Western Australia;
- the fare is not considered reasonable for an on-demand rank or hail (taxi) journey; or
- the photo on the PTSS card is recorded as not matching the participant in the vehicle.
Once the DoT review is complete, the outcome will show on the driver activity report, available via DoTDirect.
Further checks are made when the ODBS submits PTSS journey data to DoT to validate these journeys. PTSS payments may be impacted if there are issues validating any of these details.
Understanding DoTDirect payment dashboards
ODBSs can view reports in DoTDirect that outline:
- the PTSS journeys included in the payment;
- the value of the subsidy for each PTSS journey; and
- the driver that completed that journey.
What is an adjustment?
If the PTSS journey data provided by the ODBS does not match the PTSS journey details recorded at the time of the journey (i.e. via the mobile app or API), DoT may adjust subsequent PTSS payments to ODBSs.
A “credit adjustment” is applied when an additional subsidy amount is credited to the ODBS. A “debit adjustment” is applied when DoT deducts all or part of a subsidy payment to an ODBS.
Payment reports, including details of any adjustments, are available to view via your ODBS’s DoTDirect account.
Manually upload PTSS journey details on behalf of a driver
Details of PTSS journeys will be automatically submitted to DoT via the PTSS mobile app and API, to support ODBSs to provide timely and accurate payments to drivers.
If the PTSS mobile app and API are unavailable, ODBSs may manually upload PTSS journey details on behalf of a driver via their ODBS’s DoTDirect account.
Data must be submitted as a .csv file. Your column names must match the specifications below, however the columns can be in any order. You can use the template below to manually upload PTSS journey details. The below table provides descriptions for each of the column names.
Once submitted, the file will be validated by DoT.
Refer to the user guide below for more information about manually submitting PTSS journey details.
| Column name | Description |
|---|---|
|
JOURNEY ID |
The identification/booking reference number allocated to the journey by the ODBS. |
|
PTD AUTH NUMBER |
The PTD authorisation number of the driver. |
|
PTV PLATE |
The licence plate of the vehicle. |
|
PARTICIPANT CARD NUMBER |
The card number from the PTSS participant's card. |
|
PARTICIPANT CARD EXPIRY DATE |
The expiry date from the PTSS participant's card. |
|
PICK UP DATETIME |
The date and time when the journey commenced. |
|
PICK UP STREET |
If a physical address is supplied, the address where the journey commenced. |
|
PICK UP SUBURB |
If a physical address is supplied, the suburb where the journey commenced. |
|
PICK UP POSTCODE |
If a physical address is supplied, the postcode of the location where the journey commenced. |
|
PICK UP LATITUDE |
If GPS coordinates are supplied, the latitude of the location where the journey commenced. |
|
PICK UP LONGITUDE |
If GPS coordinates are supplied, the longitude of the location where the journey commenced. |
|
DROP OFF DATETIME |
The date and time when the journey was completed. |
|
DROP OFF STREET |
If a physical address is supplied, the address where the journey was completed. |
|
DROP OFF SUBURB |
If a physical address is supplied, the suburb where the journey was completed. |
|
DROP OFF POSTCODE |
If a physical address is supplied, the postcode of the location where the journey was completed. |
|
DROP OFF LATITUDE |
If GPS coordinates are supplied, the latitude of the location where the journey was completed. |
|
DROP OFF LONGITUDE |
If GPS coordinates are supplied, the longitude of the location where the journey was completed. |
|
DISTANCE KMS |
The total distance, in kilometres, or part thereof, of the journey. |
|
TOTAL FARE |
The total value of the fare for the journey. |
|
PASSENGER PAYMENT AMOUNT |
The amount of the total fare that the passenger was required to pay. |
|
SUBSIDY AMOUNT |
The amount of the total fare that is being claimed under the PTSS. |
|
SUBSIDY PERCENTAGE USED |
The subsidy percentage that was used by the booking service when calculating the subsidy amount. |
|
SUBSIDY CAP APPLICABLE |
The subsidy cap that was used by the booking service when calculating the subsidy amount. |
|
WHEELCHAIR CARRIED |
An indication as to whether the participant's wheelchair was carried during the journey. This is only applicable for wheelchair participants of the scheme. Blank means N. |
|
ADDITIONAL PARTICIPANT |
Flag to indicate if this is an additional participant, Y or N, blank means N. |